This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF9160DK 150 sec delayed bootup

I have a nRF9160 DK (sn 000960004886) that has been working fine, I've tested out to build and load some of the application samples (blinky, hello_world) and they all worked fine.

Then considering the asset_tracker I tried to update the modem firmware (to latest 1.3.1 with the Programmer), and also installed the asset_tracker from your latest application firmware download (2021-12-15) (nrf9160dk_asset_tracker_ltem_2021-12-15_cfedfdfa.hex) and after that my DK does not start (after reset) as normal.


I have log output to terminal, and the log output stops after this log line: "SPM: prepare to jump to Non-Secure image."
After some 150 seconds however, the log output continues: "*** Booting Zephyr OS build v2.7.0-ncs1  ***", and the program continues.
Also the first log output shows this timestamp: "[00:02:30.838,073] ...".

All applications I try to run now have this "feature", a 150sec delay at boot, also those that was running fine before the modem update (e.g. blinky).
Can this be due to the modem not working?

With the at_client program installed and running the LTE Link Monitor that shows only AT command timeouts (e.g. "Error: 'AT ' timed out").

The asset_tracker program also log a lot of errors, see this log output:

*** Booting Zephyr OS build v2.7.0-ncs1  ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS build v2.7.0-ncs1  ***
Flash regions		Domain		Permissions
00 03 0x00000 0x20000 	Secure		rwxl
04 31 0x20000 0x100000 	Non-Secure	rwxl

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

SRAM region		Domain		Permissions
00 07 0x00000 0x10000 	Secure		rwxl
08 31 0x10000 0x40000 	Non-Secure	rwxl

Peripheral		Domain		Status
00 NRF_P0               Non-Secure	OK
01 NRF_CLOCK            Non-Secure	OK
02 NRF_RTC0             Non-Secure	OK
03 NRF_RTC1             Non-Secure	OK
04 NRF_NVMC             Non-Secure	OK
05 NRF_UARTE1           Non-Secure	OK
06 NRF_UARTE2           Secure		SKIP
07 NRF_TWIM2            Non-Secure	OK
08 NRF_SPIM3            Non-Secure	OK
09 NRF_TIMER0           Non-Secure	OK
10 NRF_TIMER1           Non-Secure	OK
11 NRF_TIMER2           Non-Secure	OK
12 NRF_SAADC            Non-Secure	OK
13 NRF_PWM0             Non-Secure	OK
14 NRF_PWM1             Non-Secure	OK
15 NRF_PWM2             Non-Secure	OK
16 NRF_PWM3             Non-Secure	OK
17 NRF_WDT              Non-Secure	OK
18 NRF_IPC              Non-Secure	OK
19 NRF_VMC              Non-Secure	OK
20 NRF_FPU              Non-Secure	OK
21 NRF_EGU0             Non-Secure	OK
22 NRF_EGU1             Non-Secure	OK
23 NRF_EGU2             Non-Secure	OK
24 NRF_EGU3             Non-Secure	OK
25 NRF_EGU4             Non-Secure	OK
26 NRF_EGU5             Non-Secure	OK
27 NRF_DPPIC            Non-Secure	OK
28 NRF_REGULATORS       Non-Secure	OK
29 NRF_PDM              Non-Secure	OK
30 NRF_I2S              Non-Secure	OK
31 NRF_GPIOTE1          Non-Secure	OK

SPM: NS image at 0x20200
SPM: NS MSP at 0x200218b8
SPM: NS reset vector at 0x29df1
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.7.0-ncs1  ***
[00:02:30.837,982] <err> at_cmd: Failed to open AT socket (err:-117)
[00:02:30.845,062] <wrn> at_notif: Already initialized. Nothing to do
[00:02:30.852,386] <inf> asset_tracker: Asset tracker started
[00:02:30.858,581] <inf> watchdog: Watchdog timeout installed. Timeout: 60000
[00:02:30.866,180] <inf> watchdog: Watchdog started
[00:02:30.872,192] <err> nrf_cloud_client_id: Failed to obtain IMEI, error: -1
[00:02:30.880,126] <err> nrf_cloud_transport: Could not obtain configured client ID, error: -1
[00:02:30.889,556] <err> asset_tracker: Cloud backend could not be initialized, error: -1
[00:02:30.898,590] <err> asset_tracker: LTE link disconnect
[00:02:30.905,029] <err> asset_tracker: lte_lc_power_off failed: -14
*** Booting Zephyr OS build v2.7.0-ncs1  ***down modem
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS build v2.7.0-ncs1  ***
Flash regions		Domain		Permissions
00 03 0x00000 0x20000 	Secure		rwxl
04 31 0x20000 0x100000 	Non-Secure	rwxl

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


Other programs however (e.g. a blinky sample with more logging in the main loop) runs fine, but after the 150 sec "hang" during boot.

Any suggestions on what this startup delay can be, can it be that modem is malfunctioning?

Parents
  • Hello,

    First of all, modem firmware v1.3.x is not supported for nRF9160 DK versions older than v0.9.0. So you might want to doublecheck that.

    Otherwise, my first guess would be that the firmware update of the modem didn’t finish successfully. I would recommend you to try it one more time.

    A good way to confirm the functionality after a modem update is to run through the Testing procedure of the AT Client sample. If the modem does not respond on AT commands, something probably went wrong during the firmware update.

    Regards,

    Markus

  • Hi Markus,

    Spot on, I found out I have a DK version 0.8.3, so installing MF v1.2.7 did the trick, no more 150 sec boot delay!

    The AT client sample also now works nice together with the LTE link monitor, will continue to try out the asset tracker.

    Thanks for swift and accurate support!

    BR

    -Alf

Reply Children
No Data
Related