I thought you were flashing from dexter’s 3.2.014 and 3.2.015? I did a quick check of modules reporting to api.openvehicles.com, but can’t see anything similar to yours in recent days. Regards, Mark
On 5 Sep 2020, at 11:57 PM, sharkcow <sharkcow@gmx.de> wrote:
Thanks for the hint, but I double checked and I definitely booted from the factory partition...
Anyway, all is good now. It seems like there was a problem with marxx' repository, maybe that was the culprit.
sharkcow
Am 05.09.20 um 16:36 schrieb Michael Balzer: sharkcow,
if you flashed via USB, you probably flashed the factory partition. If you want to run that, you also need to set that as the boot partition if you're currently booting an OTA partition.
See: https://docs.openvehicles.com/en/latest/userguide/factory.html#module-factor...
Regards, Michael
Am 05.09.20 um 10:43 schrieb sharkcow:
OK it's running again now, sorry for the confusion.
In the meantime I saw a very early error message about corrupt boot data, so I bit the bullet and did a full reflash, which didn't help either.
Tried my previously working ota and now it's running again (I guess I got mixed up with the versions earlier).
So my only remaining question is why doesn't flashing a factory image help in this case? The way I see it, it was just a bad build?
sharkcow
Am 05.09.20 um 10:16 schrieb sharkcow:
Hi all,
I hope this is the right place to ask...
Since flashing a new build yesterday, my OVMS doesn't boot normally anymore. What I see in the USB console are 5 early crashes (reason 12 for both CPUs), then the module falls back to running without auto init.
What I have tried: switching to previously working ota, flashing & booting factory images 3.2.15 and 3.2.14 from dexter. Removed SD card since reason 12 may point to a vfs problem.
What else can I try? In my understanding it doesn't make sense to do a full reflash incl. boot loader, since booting as such works... or am I mistaken?
Is any other information necessary to tell what's wrong?
Thank you!
sharkcow
--- dump from 3.2.14:
I (121) boot: Initialising BOOT (1100) I (125) boot: Boot #4 reasons for CPU0=12 and CPU1=12 I (131) boot: Reset reason Exception/panic (4) E (136) boot: Early crash #4 detected I (141) events: Initialising EVENTS (1200) ... I (3250) housekeeping: Auto init vehicle (free: 133748 bytes) Guru Meditation Error: Core 1 panic'ed (StoreProhibited). Exception was unhandled. Core 1 register dump: PC : 0x401642d9 PS : 0x00060530 A0 : 0x801643a7 A1 : 0x3ffc3050 A2 : 0x3ffb8190 A3 : 0x3ffc30e0 A4 : 0x00000001 A5 : 0x3ffc30a8 A6 : 0x3ffc3090 A7 : 0x3ffb732c A8 : 0x801642d3 A9 : 0x3ffc3020 A10 : 0x00000000 A11 : 0x3ffc30e0 A12 : 0x3ffc3050 A13 : 0x0000ff00 A14 : 0x00ff0000 A15 : 0xff000000 SAR : 0x00000008 EXCCAUSE: 0x0000001d EXCVADDR: 0x0000000e LBEG : 0x4008be55 LEND : 0x4008be65 LCOUNT : 0xfffffffb
ELF file SHA256: 01e6f0fccd1fb186 Backtrace: 0x401642d9:0x3ffc3050 0x401643a4:0x3ffc3090 0x400f7e83:0x3ffc3110 0x400f7a92:0x3ffc3180 0x400f8eb6:0x3ffc31c0 0x400f9051:0x3ffc31f0 0x400f9138:0x3ffc3240 0x400f9199:0x3ffc3270 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev