Soft launch: OTA updates stretch goal
Posted: Sun Apr 09, 2017 9:17 pm
Unfortunately, this stretch goal took much longer than expected, and follows a pattern of being "soft launched" without being fully tested and/or having user-facing documentation. Long story short, I spent Xmas/NY holidays to elaborate, test, and implementation various features in OTA bootloader (which was worked on since last autumn, tracked at https://github.com/micropython/micropython/issues/2535). But when it came to the actual "production mode" testing with a smarthome device out of easy reach, it literally busted (be careful with those 110/220V things!). Then I had several travels, and then some personal issues which keep me less productive than I'd want.
That said, we've setup all the basic infrastructure, and I know that some people tried it. So, it only makes sense to announce it, even if in "soft launch" mode, so more advanced of the users tried it and shared their opinion whether it work at all or not .
So, at the end of ESP8266 section at http://micropython.org/download#esp8266, you will find official daily (not release!) builds of OTA-enabled firmware. There're 2 types of OTA-related images:
Please share your experiences here.
If you find OTA updates useful - already, or would like it to be elaborated further, don't forget to star yaota8266 project on Github - relative priority among other tasks will be judged based on that .
That said, we've setup all the basic infrastructure, and I know that some people tried it. So, it only makes sense to announce it, even if in "soft launch" mode, so more advanced of the users tried it and shared their opinion whether it work at all or not .
So, at the end of ESP8266 section at http://micropython.org/download#esp8266, you will find official daily (not release!) builds of OTA-enabled firmware. There're 2 types of OTA-related images:
- Initial image, which contains OTA bootloader and MicroPython build adapted to work with this OTA bootloader. This should be programmed as usual via serial to enable future OTA capabilities.
- Signed OTA update. This should be programmed using tools from the yaota8266 bootloader project (https://github.com/pfalcon/yaota8266), specifically ota_client.py: https://github.com/pfalcon/yaota8266/tr ... ota-client
Please share your experiences here.
If you find OTA updates useful - already, or would like it to be elaborated further, don't forget to star yaota8266 project on Github - relative priority among other tasks will be judged based on that .