Conversation
beautified ota output, try to look like the flash tool output added option to provide server from lua added option to provide a project name from lua so that one ota server can serve several different projects added option to verify the written image. if verification fails then the system will not be rebooted. added option to not reboot after a successful ota
|
@jolivepetrus added to the wiki at the bottom of https://github.com/the0ne/Lua-RTOS-ESP32/wiki/OTA-updates |
|
This PR have collateral efects with the Whitecat Ecosystem services. I think that your idea about "project" is covered by the current idea of type / subtype defined in KConfig. |
|
having the lua part define the project opens the possibility to share binaries between projects, yet still being able to "split" them later - without having to touch the device. I didn't realize the the whitecat ide does read+analyze the output of the ota update. |
|
I think that there's a lot of benefit from the added information and the much more structured output. @jolivepetrus if possible please let me know the Whitecat Ecosystem services requirements so I can try to find a way to achieve compatibility. |
Please note that those parameters are completely optional. |
|
I just want to point out that branches are still not merged, and the wiki has already been updated and does not correspond to the current project. |
beautified ota output, try to look like the flash tool output
added option to provide server from lua
added option to provide a project name from lua so that one ota server
can serve several different projects
added option to verify the written image => if verification fails then the system will not be rebooted.
added option to not reboot after the ota was done successfully