nRF9160 reboot during FOTA image download without any crash information

Hi,

I'm implementing a FOTA update procedure for the nRF9160 using the download_client from the nRF Connect SDK 1.9.1 and modem firmware 1.3.1.

In general the image update works without any issues but in about one out of five attempts the nRF9160 reboots during the process. In this case I do not see the usual crash dump written to the console. It looks like this:

[00:01:40.844,146] <inf> download_client: Downloaded 38912/280664 bytes (13%)
[00:01:41.934,875] <inf> download_client: Downloaded 40960/280664 bytes (14%)
[00:01:42.923,980] <inf> download_client: Downloaded 43008/280664 bytes (15%)
[00:01:44.123,016] <inf> download_client: Downloaded 45056/280664 bytes (16%)
[00:01:45.847,869] <inf> download_client: Downloaded 47104/280664 bytes (16%)
*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
Flash regions		Domain		Permissions
00 02 0x00000 0x18000 	Secure		rwxl
03 31 0x18000 0x100000 	Non-Secure	rwxl

Non-secure callable region 0 placed in flash region 2 with size 32.

SRAM region		Domain		Permissions
00 03 0x00000 0x08000 	Secure		rwxl
04 31 0x08000 0x40000 	Non-Secure	rwxl

I see this behaviour on nRF9160 Revision 1 and 2.

I had an Ozone debugger connected with all Vector Catches enabled in the Break&Tracepoints view during the reboot and Ozone did not catch it.

It looks like somehow the fault handler is not called. I also do not see any calls to sys_reboot() in the call path.

Any idea how to analyse this?

Thanks

Andre

Parents
  • Hi Andre,

    Sorry for the confusion.It is just a suggestion as the NCS2.0.0 is an exciting big release I think many improvements are helpful for developers. Of cause, you have the freedom to continue working with NCS1.9.1. ;-)

    I have tested with ncs/v1.9.1/nrf/samples/nrf9160/http_update and could not repeat the issue. If you could not figure out the cause after comparing with the original sample. Next step, I would like to ask you to share a simple minimal sample of your codes that can reproduce the issue or modem trace recordings to have a deeper investigation. 

    Best regards,

    Charlie

Reply
  • Hi Andre,

    Sorry for the confusion.It is just a suggestion as the NCS2.0.0 is an exciting big release I think many improvements are helpful for developers. Of cause, you have the freedom to continue working with NCS1.9.1. ;-)

    I have tested with ncs/v1.9.1/nrf/samples/nrf9160/http_update and could not repeat the issue. If you could not figure out the cause after comparing with the original sample. Next step, I would like to ask you to share a simple minimal sample of your codes that can reproduce the issue or modem trace recordings to have a deeper investigation. 

    Best regards,

    Charlie

Children
No Data
Related