ESPRainmaker OTA Fail in IDF V5 but not in V4.6
Posted: Thu Dec 21, 2023 1:34 am
Hi.
Does anybody know if there is a “general” OTA update problem in IDF V5.0.2 with ESPRainmaker?
I have an App using rainmaker in V4.6.6 and it works PERFECTLY when making any code change(or just version) and using ESPRainmaker Dashboard to start an OTA job, always finishing with SUCCESS.
The changes made to the app for V5 compatibility are extremely trivial, just changing %ld where %d was used before. Binary size went up from 1.2MB to 1.38MB but the both OTA partitions have a 1.5MB space so no worries there(in theory). As a side note, its quite the opposite of the intention of V5 which was to reduce code size and compilation time at the expense of greater CMAKE directives which were simple in pre V5 versions.
When starting an OTA job to a node, it ALWAYS fails with “invalid image” even if no changes are made to the code, but version change is increase not to be rejected. The code was directly uploaded via UART and runs ok and then tested with OTA but no success.
Thanks
Does anybody know if there is a “general” OTA update problem in IDF V5.0.2 with ESPRainmaker?
I have an App using rainmaker in V4.6.6 and it works PERFECTLY when making any code change(or just version) and using ESPRainmaker Dashboard to start an OTA job, always finishing with SUCCESS.
The changes made to the app for V5 compatibility are extremely trivial, just changing %ld where %d was used before. Binary size went up from 1.2MB to 1.38MB but the both OTA partitions have a 1.5MB space so no worries there(in theory). As a side note, its quite the opposite of the intention of V5 which was to reduce code size and compilation time at the expense of greater CMAKE directives which were simple in pre V5 versions.
When starting an OTA job to a node, it ALWAYS fails with “invalid image” even if no changes are made to the code, but version change is increase not to be rejected. The code was directly uploaded via UART and runs ok and then tested with OTA but no success.
Thanks