When triggering a restart from the mobile app via Bluetooth on a Heltec V4 Expansion Kit running MeshCore 1.17.1, the device enters an infinite bootloop with a
Guru Meditation Error: Core 1 panic'ed (LoadProhibited).
Unplugging the battery/USB (cold boot) does not resolve the issue, suggesting configuration/filesystem corruption in LittleFS (as indicated by vfs_api.cpp:182 remove() error in the log). The only way to recover the device is a full Erase Flash and re-flashing.
There is also an SPI pin initialization warning: spiAttachMISO(): HSPI Does not have default pins on ESP32S3!.
Attention, the problem does not appear immediately, but usually after several hours of operation - not immediately after reflashing and restoring the settings.
I have attached the serial console log screenshot.
Thanks
When triggering a restart from the mobile app via Bluetooth on a Heltec V4 Expansion Kit running MeshCore 1.17.1, the device enters an infinite bootloop with a
Guru Meditation Error: Core 1 panic'ed (LoadProhibited).
Unplugging the battery/USB (cold boot) does not resolve the issue, suggesting configuration/filesystem corruption in LittleFS (as indicated by vfs_api.cpp:182 remove() error in the log). The only way to recover the device is a full Erase Flash and re-flashing.
There is also an SPI pin initialization warning: spiAttachMISO(): HSPI Does not have default pins on ESP32S3!.
Attention, the problem does not appear immediately, but usually after several hours of operation - not immediately after reflashing and restoring the settings.
I have attached the serial console log screenshot.
Thanks