OTA-Update strategy (regarding IDF updates, bootloader etc.)
Posted: Wed Nov 22, 2017 8:26 pm
This concerns a topic we have been discussing internally for a while.
Imagine you have hundreds of devices deployed in a remote place that can only be accessed by a technician about once per year. A few devices are available for local testing, some are installed in facilities that can be accessed within a year or so.
We develop on IDF master and our customer demands sometimes updates to the devices.
Should we work with a constant IDF or may we update IDF when compiling the OTA update APP. Could there be breaking changes in the app with respect to a then potentially outdated bootloader (which cannot be updated via OTA), e.g. some peripherals disabled which are expected to be present by new app?
I'd love to see an official guide or some best practices collection with respect to IDF updates (use master or use release versions? why?) and how to ensure OTA updates are compatible to the bootloaders of all devices?
Imagine you have hundreds of devices deployed in a remote place that can only be accessed by a technician about once per year. A few devices are available for local testing, some are installed in facilities that can be accessed within a year or so.
We develop on IDF master and our customer demands sometimes updates to the devices.
Should we work with a constant IDF or may we update IDF when compiling the OTA update APP. Could there be breaking changes in the app with respect to a then potentially outdated bootloader (which cannot be updated via OTA), e.g. some peripherals disabled which are expected to be present by new app?
I'd love to see an official guide or some best practices collection with respect to IDF updates (use master or use release versions? why?) and how to ensure OTA updates are compatible to the bootloaders of all devices?