We have several units deployed with v3.0 application. Just completed the code migration to 4.1.
Now we are testing the in-field update procedure to be able to update those units without visiting each site.
Each application version had its own method to perform the update from an SD card. The code for 3.0 is working OK for a long time and has performed several updates. As for 4.1 seems to be working too.
The fact is that we are unable to migrate an unit from 3.0 to 4.1 using systemupdate.
- on the 3.0 app we deployed an SD card with these files: clr.hex, clr2.hex, config.hex, tinybooter.ghi, app.hex and managedbootloader.hex
- WriteFirmware is being called for all files except tinybooter which goes with WriteTinyBooter
- when running the update method, it does take some time and shows activity, but after rebooting the application is still the same
I’m missing something here? Can the v3.0 SystemUpdate handle a complete self-update to 4.1?
Appreciate your help on this. Tanks.