- Fri May 15, 2015 3:38 pm
#17501
anakod wrote:Sming OTA update is different:
* Format spiffs area
* Download all requried files in that place
* Copy from that area to main program space in special RAM located method
Thanks for your reply, but could you explain the process a little bit more? Is the bootloader involved in the process or even needed? What in the case of failed upgrade - the way I understand it: you're screwed, there's no other version you can even try to rollback to.
What about using the spiffs for upgrade? The way I see it, i want to keep my files (html, configs) and just update the binary part. Loosing the spiffs data is in my opinion not an option - I need to store data about my user or some other preferences somewhere... Is it possible to use the watchdog and dual binary image idea to build something at least a little bit error-proof? Like run one binary file, upgrade the other, restart the device and if the watchdog won't signal that the software is working, restart and go back to the previous version? I think something like that would awesome
One more thing: @anakod, did you think about using some small size mobile frameworks for web (like
http://purecss.io/ - 4kB zip and
http://zeptojs.com/)? This could spare a few kB on spiffs.