.y device keeps restarting multiple times without any warning which causes messages to be delivered multiple times to nrfcloud. I've had 5 messages delivered simultaneously, with each one being identical. This happened with the official release and with latest master. I can see the whole boot sequence occuring in the terminal. Why is this happening?
Here is some more info Martin Lesund and Markus Tacker
For some reason the last post wouldn't let me past more information. This is the output from west update
=== self-updating west: --- west: fetching changes From https://github.com/zephyrproject-rtos/west * branch master -> FETCH_HEAD --- west: checked out d5f8caf2c95c6b79aa87395253be760d63112a60 as detached HEAD === updating fw-nrfconnect-zephyr (zephyr): --- fw-nrfconnect-zephyr: fetching changes --- fw-nrfconnect-zephyr: checked out de69d2df908fc7bccd8c03b106e7645e90b1503b as detached HEAD === updating fw-nrfconnect-mcuboot (mcuboot): --- fw-nrfconnect-mcuboot: fetching changes --- fw-nrfconnect-mcuboot: checked out 59fde9c792bfaa36887c860fb8cd0ca1f1bc4db5 as detached HEAD === updating nrfxlib (nrfxlib): --- nrfxlib: fetching changes --- nrfxlib: checked out 9bcc77b27d12162adc31d8c8c70f4e499338fbdb as detached HEAD
I am getting an error message when running ninja flash
ninja: warning: multiple rules generate C:/PROJECTCODE/ncs/zephyr/subsys/logging/Kconfig.template.log_config. builds involving this target will not be correct; continuing anyway [-w dupbuild=warn]
ninja: warning: multiple rules generate C:/PROJECTCODE/ncs/zephyr/subsys/net/Kconfig.template.log_config.net. builds involving this target will not be correct; continuing anyway [-w dupbuild=warn]
[138/144] Linking C executable zephyr\zephyr_prebuilt.elf
Memory region Used Size Region Size %age Used
FLASH: 168220 B 256 KB 64.17%
SRAM: 53664 B 128 KB 40.94%
IDT_LIST: 120 B 2 KB 5.86%
[143/144] Flashing nrf9160_pca10090ns
Using runner: nrfjprog
Flashing file: C:/PROJECTCODE/ncs/nrf/applications/asset_tracker/build/zephyr/zephyr.hex
Parsing hex file.
Erasing page at address 0x40000.
Erasing page at address 0x41000.
Erasing page at address 0x42000.
Erasing page at address 0x43000.
Erasing page at address 0x44000.
Erasing page at address 0x45000.
Erasing page at address 0x46000.
Erasing page at address 0x47000.
Erasing page at address 0x48000.
Erasing page at address 0x49000.
Erasing page at address 0x4A000.
Erasing page at address 0x4B000.
Erasing page at address 0x4C000.
Erasing page at address 0x4D000.
Erasing page at address 0x4E000.
Erasing page at address 0x4F000.
Erasing page at address 0x50000.
Erasing page at address 0x51000.
Erasing page at address 0x52000.
Erasing page at address 0x53000.
Erasing page at address 0x54000.
Erasing page at address 0x55000.
Erasing page at address 0x56000.
Erasing page at address 0x57000.
Erasing page at address 0x58000.
Erasing page at address 0x59000.
Erasing page at address 0x5A000.
Erasing page at address 0x5B000.
Erasing page at address 0x5C000.
Erasing page at address 0x5D000.
Erasing page at address 0x5E000.
Erasing page at address 0x5F000.
Erasing page at address 0x60000.
Erasing page at address 0x61000.
Erasing page at address 0x62000.
Erasing page at address 0x63000.
Erasing page at address 0x64000.
Erasing page at address 0x65000.
Erasing page at address 0x66000.
Erasing page at address 0x67000.
Erasing page at address 0x68000.
Erasing page at address 0x69000.
Applying system reset.
Checking that the area to write is not protected.
Programming device.
Applying pin reset.
Board with serial number 960072328 flashed successfully.
I will post my results of the debug output momentarily.
Here is the error I get Martin Lesund and Markus Tacker
Error of type ERROR_BSD_RECOVERABLE: 3
I have LED1 and LED3 both flashing and the program halted. I am not sure this is the same error because in normal mode, the device just resets. Maybe this is a function of debug being on.
Here is the output
***** Booting Zephyr OS v1.13.99-ncs1-4741-g1d6219ffec ***** Secure Boot: configure flash Secure Boot: SPU: set region 0 as Secure Secure Boot: SPU: set region 1 as Secure Secure Boot: SPU: set region 2 as Secure Secure Boot: SPU: set region 3 as Secure Secure Boot: SPU: set region 4 as Secure Secure Boot: SPU: set region 5 as Secure Secure Boot: SPU: set region 6 as Secure Secure Boot: SPU: set region 7 as Secure Secure Boot: SPU: set Flash region 8 as Non-Secure Secure Boot: SPU: set Flash region 9 as Non-Secure Secure Boot: SPU: set Flash region 10 as Non-Secure Secure Boot: SPU: set Flash region 11 as Non-Secure Secure Boot: SPU: set Flash region 12 as Non-Secure Secure Boot: SPU: set Flash region 13 as Non-Secure Secure Boot: SPU: set Flash region 14 as Non-Secure Secure Boot: SPU: set Flash region 15 as Non-Secure Secure Boot: SPU: set Flash region 16 as Non-Secure Secure Boot: SPU: set Flash region 17 as Non-Secure Secure Boot: SPU: set Flash region 18 as Non-Secure Secure Boot: SPU: set Flash region 19 as Non-Secure Secure Boot: SPU: set Flash region 20 as Non-Secure Secure Boot: SPU: set Flash region 21 as Non-Secure Secure Boot: SPU: set Flash region 22 as Non-Secure Secure Boot: SPU: set Flash region 23 as Non-Secure Secure Boot: SPU: set Flash region 24 as Non-Secure Secure Boot: SPU: set Flash region 25 as Non-Secure Secure Boot: SPU: set Flash region 26 as Non-Secure Secure Boot: SPU: set Flash region 27 as Non-Secure Secure Boot: SPU: set Flash region 28 as Non-Secure Secure Boot: SPU: set Flash region 29 as Non-Secure Secure Boot: SPU: set Flash region 30 as Non-Secure Secure Boot: SPU: set Flash region 31 as Non-Secure Secure Boot: configure SRAM Secure Boot: SPU: set SRAM region 0 as Secure Secure Boot: SPU: set SRAM region 1 as Secure Secure Boot: SPU: set SRAM region 2 as Secure Secure Boot: SPU: set SRAM region 3 as Secure Secure Boot: SPU: set SRAM region 4 as Secure Secure Boot: SPU: set SRAM region 5 as Secure Secure Boot: SPU: set SRAM region 6 as Secure Secure Boot: SPU: set SRAM region 7 as Secure Secure Boot: SPU: set SRAM region 8 as Non-Secure Secure Boot: SPU: set SRAM region 9 as Non-Secure Secure Boot: SPU: set SRAM region 10 as Non-Secure Secure Boot: SPU: set SRAM region 11 as Non-Secure Secure Boot: SPU: set SRAM region 12 as Non-Secure Secure Boot: SPU: set SRAM region 13 as Non-Secure Secure Boot: SPU: set SRAM region 14 as Non-Secure Secure Boot: SPU: set SRAM region 15 as Non-Secure Secure Boot: SPU: set SRAM region 16 as Non-Secure Secure Boot: SPU: set SRAM region 17 as Non-Secure Secure Boot: SPU: set SRAM region 18 as Non-Secure Secure Boot: SPU: set SRAM region 19 as Non-Secure Secure Boot: SPU: set SRAM region 20 as Non-Secure Secure Boot: SPU: set SRAM region 21 as Non-Secure Secure Boot: SPU: set SRAM region 22 as Non-Secure Secure Boot: SPU: set SRAM region 23 as Non-Secure Secure Boot: SPU: set SRAM region 24 as Non-Secure Secure Boot: SPU: set SRAM region 25 as Non-Secure Secure Boot: SPU: set SRAM region 26 as Non-Secure Secure Boot: SPU: set SRAM region 27 as Non-Secure Secure Boot: SPU: set SRAM region 28 as Non-Secure Secure Boot: SPU: set SRAM region 29 as Non-Secure Secure Boot: SPU: set SRAM region 30 as Non-Secure Secure Boot: SPU: set SRAM region 31 as Non-Secure Secure Boot: configure peripherals Secure Boot: MSP_NS 2002a198 Secure Boot: prepare to jump to Non-Secure image ***** Booting Zephyr OS v1.13.99-ncs1-5561-gde69d2df908f ***** Application started LTE LC config ... NRF_CLOUD_EVT_TRANSPORT_CONNECTED NRF_CLOUD_EVT_USER_ASSOCIATED NRF_CLOUD_EVT_READY NRF_CLOUD_EVT_SENSOR_ATTACHED NRF_CLOUD_EVT_SENSOR_ATTACHED NRF_CLOUD_EVT_SENSOR_ATTACHED NRF_CLOUD_EVT_SENSOR_ATTACHED NRF_CLOUD_EVT_SENSOR_ATTACHED NRF_CLOUD_EVT_SENSOR_ATTACHED NRF_CLOUD_EVT_SENSOR_ATTACHED NRF_CLOUD_EVT_SENSOR_ATTACHED GPS device found Error of type ERROR_BSD_RECOVERABLE: 3
Hi ip,
1. Please try to flash this application, and see if you still get the Error:
using the command line: nrfjprog --program asset_tracker.hex -f nrf91 --sectorerase -r --verify
2. It may be that you have stumbled upon an errata:
Please check this link for more information.
3. Or this may be a bug in the modem firmware which a new version will come very soon that may fix this.
Thank you. I think 2 probably was an issue but I am still getting restarts. Here is the output
In addition, it takes about 20-60 seconds to restart Martin Lesund and Markus Tacker (he/him)
