-
-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App crash on SPIFFS when booting rom slot 1 #2103
Comments
@kmihaylov Try to flash the same APP on rom 0 and then on rom 1 over OTA. The stack trace points to a problem in the smartconfig code / WIFI and not in the flash reading/writing. |
@slaff would you please try the attached project (1st post)? Try OTA several times with the same firmware. |
@kmihaylov Are you still having this issue with the latest |
@slaff with the latest develop f2bcf79 and the new Ota updater everything works fine. With few versions earlier (with the bit older now rBoot updater) everything works fine too, given that I use rom0 and rom1 images for flashing the appropriated slots. I have made a mistake to use only rom0 for flashing both slot0 and slot1. |
When application is using only one SPIFFS address space for both roms (in my case 0x1....), the second (or newly flashed) rom fails to boot (probably because spiffs_mount problem).
If separate addressing is used for SPIFFS partition for rom 0 and rom 1 (0x1xxxx and 0x3xxxx), no problem occurs.
Also if the app uses only one SPIFFS partition located at 0x3xxxx, again no problem occurs (multiple OTA updates and successfull boots from both slot 0 and slot 1).
The decoded stacktraces are below!
Attached is the Basic_rBoot example with minor changes, that shows similar, but not the same behaviour (it successfully updates and switches to slot 1, mounting it from 0x8200 for some reason, but breaks when OTA-ing slot 0).
rboot_spiffs.tar.gz
Here I'm pasting my serial output, including the bootloader messages and other information:
Decode stack-trace of the first dump:
Decoded stack-trace after the WDT reset:
The text was updated successfully, but these errors were encountered: