FOTA Firmware is not kept after Reset

Question

Hi, 
 Today I realized something interesting for our devices: The Update from an older Software Version build with SDK 1.6.X was on it and I updated via AWS FOTA to new version build with some changes and SDK 1.7.0 . The Update works fine and the firmware works perfect. The Image gets also confirmed via boot_write_img_confirmed(); 
 After reset the device waits some time (like it does after the reboot after OTA) and then it starts again the old Image. I dont know how I can debug because it is always described that "boot_write_img_confirmed();" keeps the current image. 
 
 What can be the reason for this? 
 
 Thanks and best regards

Charlie · Accepted Answer

Hi Daniel, 
 I realized you have done lots of modifications to the configuration files. It increased the risk of FOTA failure. 
 On product development, you should choose a fixed SDK version as the basement of your development and only update if it has critical bugs fixed or new features you need are added, because a new version may introduce new issues. The best practice of FOTA usage should also keep an NCS major version like v1.7.x and only update your application's codes for bug fixing once you have released your products. 
 If you have to do such a FOTA on your setup, please start with the original NCS examples, and add the new configuration piece by piece to invest in the cause of failure. The result is unpredictable and you should avoid this on your real product. 
 Best regards, 
 Charlie

FOTA Firmware is not kept after Reset

Top Replies