search

whitecatboard / Lua-RTOS-ESP32

Lua RTOS for ESP32
Other
1.19k stars 221 forks source link

improve ota #238

Open the0ne opened 5 years ago

the0ne commented 5 years ago

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

the0ne commented 5 years ago

@jolivepetrus added to the wiki at the bottom of https://github.com/the0ne/Lua-RTOS-ESP32/wiki/OTA-updates

jolivepetrus commented 5 years ago

@the0ne,

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.

the0ne commented 5 years ago

@jolivepetrus,

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. the idea of the changes was to make the terminal output nice, easy and informative. please let me know the Whitecat Ecosystem services requirements so I can possibly find a way to achieve both targets.

the0ne commented 5 years ago

I think that there's a lot of benefit from the added information and the much more structured output.

/ > net.ota(nil, nil, false, true)
Connecting to https://sdkconfig-ota-server.tld ...
Current firmware commit is 09d7592cf183fdc138428c756e0ec124ea043a01
Running from ota_0 at offset 0x000a0000
Writing to   ota_1 at offset 0x00250000 - capacity is 1.69 MB
Starting OTA update, downloading partition image with 1.14 MB
Writing chunk at 0x00373d50... (100 %)
OTA update finished
Successfully changed boot partition
/ >

@jolivepetrus if possible please let me know the Whitecat Ecosystem services requirements so I can try to find a way to achieve compatibility.

the0ne commented 2 years ago

@the0ne,

This PR have collateral effects with the Whitecat Ecosystem services. I think that your idea about "project" is covered by the current idea of type / subtype defined in KConfig.

Please note that those parameters are completely optional. So there shouldn't be a negative effect to the Whitecat Ecosystem services.

progerstar commented 1 year ago

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.