[Ovmsdev] unit repeatedly crashing / reverting to factory

Mark Webb-Johnson mark at webb-johnson.net
Mon May 15 09:19:51 HKT 2023


It certainly seems so.

I suggest wipe it all, and re-flash. Or just try to wipe the NVS region and see if it can then boot?

Regards, Mark.

> On 13 May 2023, at 4:11 AM, Derek Caudwell <d.caudwell at gmail.com> wrote:
> 
> The following is the log after resetting, does this indicate the NVS flash is corrupted?
> 
> I (630) esp32wifi: Powering up WIFI driver
> I (640) wifi: wifi driver task: 3ffd05c4, prio:23, stack:3584, core=0
> I (650) wifi: wifi firmware version: 771f1dc
> I (650) wifi: config NVS flash: enabled
> I (650) wifi: config nano formating: disabled
> I (660) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
> I (670) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
> I (690) wifi: Init dynamic tx buffer num: 16
> I (690) wifi: Init data frame dynamic rx buffer num: 16
> I (690) wifi: Init management frame dynamic rx buffer num: 16
> I (690) wifi: Init static rx buffer size: 2212
> I (700) wifi: Init static rx buffer num: 4
> I (700) wifi: Init dynamic rx buffer num: 16
> W (1380) phy_init: failed to load RF calibration data (0xffffffff), falling back to full calibration
> I (1540) phy: phy_version: 3910, c0c45a3, May 21 2018, 18:07:06, 0, 2
> assertion "usedEntries == newPage->getUsedEntryCount()" failed: file "/home/openvehicles/build/esp-idf/components/nvs_flash/src/nvs_pagemanager.cpp", line 175, function: esp_err_t nvs::PageManager::requestNewPage()
> abort() was called at PC 0x401018ef on core 0
> 
> Backtrace: 0x400935d3:0x3ffd02b0 0x4009372b:0x3ffd02d0 0x401018ef:0x3ffd02f0 0x4011cc77:0x3ffd0320 0x4011b8f7:0x3ffd0340 0x4011b6a3:0x3ffd03a0 0x401d75e3:0x3ffd03e0 0x401d7a0f:0x3ffd0420 0x401e296a:0x3ffd0450 0x401e2a04:0x3ffd0480 0x401e2cfa:0x3ffd04b0 0x401e2e67:0x3ffd04e0 0x4008a60c:0x3ffd0500
> 
> Rebooting...
> 
> On Fri, 12 May 2023 at 20:13, Derek Caudwell <d.caudwell at gmail.com <mailto:d.caudwell at gmail.com>> wrote:
>> Recently my 12V battery died, after replacing it the OVMS unit reverted to the factory reset state. Unfortunately it kept crashing in this state with the following:
>> 
>> Last boot was 101 second(s) ago Time at boot: 1970-01-01 00:03:16 GMT This is reset #3 since last power cycle Detected boot reason: EarlyCrash (12/12) Reset reason: Exception/panic (4) Crash counters: 3 total, 3 early Last crash: LoadProhibited exception on core 1 Registers: PC : 0x4008c341 PS : 0x00060030 A0 : 0x8013cc48 A1 : 0x3ffe63d0 A2 : 0x00000000 A3 : 0xfffffffc A4 : 0x000000ff A5 : 0x0000ff00 A6 : 0x00ff0000 A7 : 0xff000000 A8 : 0x00000000 A9 : 0x00000008 A10 : 0x3ffeba1d A11 : 0x3f417d87 A12 : 0x3ffeba25 A13 : 0x3ffe684c A14 : 0x47006c6c A15 : 0x47006c6c SAR : 0x00000010 EXCCAUSE: 0x0000001c EXCVADDR: 0x00000000 LBEG : 0x4008c341 LEND : 0x4008c351 LCOUNT : 0xffffffff Current task on core 0: wifi, 1176 stack bytes free Current task on core 1: OVMS NetMan, 6420 stack bytes free Backtrace: 0x4008c341 0x4013cc45 0x4013ffbe 0x4013fff5 0x4011439b 0x40184ee2 0x4018526b 0x40185ac8 0x40189829 0x401311ed 0x40132221 0x401311ed 0x40131597 0x4013168a 0x40132ff1 0x40133272 0x4012f432 0x4012330f 0x401233bd Version: 3.3.003-423-g68d9aee8/ota_0/main (build idf v3.3.4-849-g6e214dc33 Apr 19 2023 00:11:25) Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1
>> Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1 Firmware: 3.3.003-423-g68d9aee8/ota_0/main (build idf v3.3.4-849-g6e214dc33 Apr 19 2023 00:11:25) Running partition: ota_0 Boot partition: ota_0 Factory image: 3.2.002 OTA_O image: 3.3.003-423-g68d9aee8 OTA_1 image: 3.3.003-419-gfbbf3c0d
>> 
>> Removing the SD card and trying a S2 reset made no difference, so I proceeded to run the following commands to factory reset and boot from the factory firmware:
>> 
>> esptool.py --chip esp32 --port COM3 --baud 921600 erase_region 0xC10000 0x100000
>>  
>> 
>> esptool.py --chip esp32 --port COM3 --baud 921600 erase_region 0xd000 0x2000
>> 
>> Both ran successfully however the unit is now no longer providing the factory wifi access point. What should I try next to restore it?
>> 
>> Cheers Derek
>> 
>> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20230515/b71ed156/attachment.htm>


More information about the OvmsDev mailing list