So you're a Noob? Post your questions here until you graduate! Don't be shy.

User avatar
By piersfinlayson
#61791
martinayotte wrote:I was talking in the ArduinoESP context, where OTA is managed according to _SPIFFS_start location.
During some tests, I moved the whole SPIFFS above the 4MB, so 12MB of SPIFFS size, the OTA is flashing the firmware, but when e-boot is called to recopy it under right location, which use ROM functions, I got "need boot 1.4+", and hangs forever until doing a erase_flash with esptool.py.
To work around that, we would need to keep OTA location at it usual location so that ROM functions would still work, we need to have Updater using the same location, but not relying on the _SPIFFS_start location.
I will give it a try when I will finally get some free time, "time is the missing ingredient" ...


Don't know much about e-boot, but if it's using the copy_raw function I see then that doesn't support >16MB cos it's not accessing and fiddling with flashchip->chip_size. Looks pretty easy to enhance.