FOTA Firmware is not kept after Reset

RE: FOTA Firmware is not kept after Reset

danielboe — Fri, 15 Oct 2021 16:47:50 GMT

Hi Charlie,

thanks for the feedback. I experimented a bit and the OTA is not working as soon as the NCS version changes from 1.5.1 to 1.6.0 so this is the issue here. I think my request is solved now and I will stick to your recomendations if it comes to the release for production.

best regards

Daniel

RE: FOTA Firmware is not kept after Reset

Charlie — Thu, 14 Oct 2021 09:11:53 GMT

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

RE: FOTA Firmware is not kept after Reset

danielboe — Tue, 12 Oct 2021 15:43:15 GMT

one more investigation: I can change the mamory maps in common.dts and also in partition_conf.dts to identical, the issue is not solved. so the problem seems not these maps

RE: FOTA Firmware is not kept after Reset

danielboe — Tue, 12 Oct 2021 14:08:22 GMT

Okay, some new Infos, first I was wrong the Firmware came from SDK 1.5.1 so I reproduced everything by compiling and testing. I did a small protocol :

Modem 1.2.3, Steps:

1. Erase All
2. Flash via JLINK Firmware: 1.2.13 (SEGGGER RTT. SDK 1.5.1)
3. Boot Works -> Log 1
4. OTA via AWS to Firmware: 1.4.6 (Compiled SDK 1.7.0) -> Log2
5. Boot after OTA -> Log 3
6. Reset via Button
7. Boot after Reset (after some time, loads old Fimrware) -> Log 4

In Common DTS File there is a change that may can be an issue

Also here is my prj.conf files with some differences:

Left is 1.2.13 right is 1.4.6

https://editor.mergely.com/t0iSkJDJ/

Thanks for your help here and best regards

Daniel

RE: FOTA Firmware is not kept after Reset

danielboe — Mon, 11 Oct 2021 21:58:14 GMT

can also other settings changes in prj.conf cause this issue? I will investigate more tomorrow and share the data

RE: FOTA Firmware is not kept after Reset

Charlie — Mon, 11 Oct 2021 15:11:16 GMT

Hi Daniel,

I did a quick check, there is no issue on my side when I FOTA NCS v1.6.1 to NCS v1.7.0 nrf9106/http_update/application_update sample. Just share my log with you. I added "printk("Current APP version:%d\n",CONFIG_APPLICATION_VERSION);" to make it easy to find the version change.

devzone.nordicsemi.com/.../5314.log.txt

Can you retry with freshly new NCS installations? Please share the log file if you still have the issue.

Best regards,

Charlie