Hi everyone,
I'm experiencing a persistent issue with my OVMS module (purchased around 2020/2021) after attempting to update the firmware.
The Problem
Whenever I install a more recent firmware version (I have tried several different images), the device immediately reboots as soon as I try to connect to the Web UI.
If I revert the module back to the Factory Image (3.2.008), it works perfectly fine, and the Web UI is accessible without any issues.
Background & Observations
-
I have tried various newer firmware images, and the behavior remains consistently the same: stable on 3.2.008, unstable (rebooting on Web UI connect) on newer versions.
-
I have been using this device continuously since I got it.
-
I recall having the exact same issue a while ago. Back then, I tried different firmware versions until one finally worked, and the module ran stable until recently.
-
I suspect the module might have performed an OTA update a few days ago, and the instability started right after that.
Given that the issue is specific to newer firmware versions but consistently goes away on the very old factory image, it makes me wonder if this is an underlying hardware issue that newer firmware is less tolerant of, rather than a bug in the software itself.
Has anyone else encountered this kind of issue, or does anyone have an idea what might be causing the conflict with the newer firmware versions?
Thanks for any help or insights!
Errormessage from console session:
I (10648) webserver: HTTP GET /
I (10708) webserver: HTTP GET /assets/style.css
I (10718) webserver: HTTP GET /assets/script.js
I (10918) webserver: HTTP GET /apple-touch-icon.png
I (11018) webserver: HTTP GET /cfg/firmware
OVMS# Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
Core 1 register dump:
PC : 0x4008c329 PS : 0x00060230 A0 : 0x80141f7c A1 : 0x3ffe8e90
A2 : 0x00000000 A3 : 0xfffffffc A4 : 0x000000ff A5 : 0x0000ff00
A6 : 0x00ff0000 A7 : 0xff000000 A8 : 0x00000000 A9 : 0x00000008
A10 : 0x3ffef7c1 A11 : 0x3f41a0ad A12 : 0x3ffef7c9 A13 : 0x3ffe930c
A14 : 0x5047006c A15 : 0x5047006c SAR : 0x00000008 EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000000 LBEG : 0x4008c329 LEND : 0x4008c339 LCOUNT : 0xffffffff
ELF file SHA256: 6a60774c405fb3fc
Backtrace: 0x4008c329:0x3ffe8e90 0x40141f79:0x3ffe8ea0 0x401452f2:0x3ffe91b0 0x40145329:0x3ffe9250 0x4011018b:0x3ffe9280 0x4018e872:0x3ffe92d0 0x4018ec03:0x3ffe9370 0x4018f468:0x3ffe9390 0x40195e25:0x3ffe93f0 0x40136521:0x3ffe94b0 0x40137555:0x3ffe94f0 0x40136521:0x3ffe9550 0x401368cb:0x3ffe9590 0x401369be:0x3ffe95c0 0x40138325:0x3ffe95f0 0x401385a6:0x3ffe9660 0x40134766:0x3ffe96c0 0x401185fb:0x3ffe96e0 0x401186a9:0x3ffe9730
[OVMS] Current tasks: IDLE0|OVMS NetMan
Rebooting...
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x1b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:4796
load:0x40078000,len:0
load:0x40078000,len:14896
entry 0x40078d74
I (1201) psram: This chip is ESP32-D0WD
What exact version of firmware were you running when the crash happened, and where did you download it from (Dexter or API)? With that information, we can probably check the stack backtrace to identify the problem.
Also note you can use the 'ota' commands to switch between firmware versions. There are always three (factory, ota_1, and ota_2).
Thanks for the quick response and the helpful information about ota commands!
Unfortunately, I cannot specify the exact firmware version that first caused the crash, as it most likely came via an OTA update.
I have now systematically tested several firmware versions downloaded from Dexter.
Here is an overview of my testing results:
Firmware Version Stable (y/n) - Access to Web UI Notes
Tested Yesterday
3.3 - Main n
3.3.002 n
3.3.003 n
Tested Today Installed sequentially starting from 3.2.008
3.2.008 y Factory Image - known working baseline
3.2.018 y
3.3.001 y
3.3.002 y
3.3 - Main n
3.3.003 y Currently stable. I can browse the Web UI.
3.3.004 n
A curious note: I cannot explain why versions 3.3.002 and 3.3.003 failed when I tested them yesterday, but they are both working now after I installed them step-by-step from the stable 3.2.008 version today.
Currently, I am running 3.3.003 and the Web UI is stable.
Module Information
Hardware Version: OVMS V3.2
Manufactured Date: 03.03.2020
Since I was experiencing consistent reboots on the Web UI across various modern versions yesterday, and now some of those versions are suddenly working, I'm still concerned about the stability.
OVMS# boot status
Last boot was 18 second(s) ago
Time at boot: 1970-01-01 00:26:30 GMT
This is reset #6 since last power cycle
Detected boot reason: EarlyCrash (12/12)
Reset reason: Exception/panic (4)
Crash counters: 6 total, 5 early
Last crash: LoadProhibited exception on core 1
Registers:
PC : 0x4008c315 PS : 0x00060230 A0 : 0x8013dea0 A1 : 0x3ffe8400
A2 : 0x00000000 A3 : 0xfffffffc A4 : 0x000000ff A5 : 0x0000ff00
A6 : 0x00ff0000 A7 : 0xff000000 A8 : 0x00000000 A9 : 0x00000008
A10 : 0x3ffef08d A11 : 0x3f419511 A12 : 0x3ffef095 A13 : 0x3ffe887c
A14 : 0x5047006c A15 : 0x5047006c SAR : 0x00000008 EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000000 LBEG : 0x4008c315 LEND : 0x4008c325 LCOUNT : 0xffffffff
Current task on core 0: wifi, 1168 stack bytes free
Current task on core 1: OVMS NetMan, 6364 stack bytes free
Backtrace:
0x4008c315 0x4013de9d 0x40141216 0x4014124d 0x4010d4bb 0x40188182 0x40188517 0x40188d5c 0x4018abc9 0x40132445 0x40133479 0x40132445 0x401327ef 0x401328e2 0x40134249 0x401344ca 0x4013068a 0x40115453 0x40115501
Version: 3.3.004/ota_1/main (build idf v3.3.4-849-g6e214dc335 Mar 23 2024 10:17:01)
Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1; MODEM
OVMS# ota status
Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1; MODEM
Firmware: 3.3.004/ota_1/main (build idf v3.3.4-849-g6e214dc335 Mar 23 2024 10:17:01)
Running partition: ota_1
Boot partition: ota_0
Factory image: 3.2.008
OTA_O image: 3.3.003
OTA_1 image: 3.3.004