This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ERROR: Problem in adding the new nRF9160 DK (PCA10090) device in nRF Cloud

Hi, 

I have a Thingy91 (PCA20035) device added to my nRF cloud account and accessing without issues. 

But today I have got a new nRF9160 DK (PCA10090) along with a new SIM etc,

I can verify the SIM without issue, but facing issues while adding it to the "Add  LTE Device". 

ERROR: "There was an error adding your device. You might be trying to upgrade an older nRF91 development kit. Unless you update your device, you will have to click the "Have an old devkit without a PIN?" Link Below ". 

Please find the same in the screenshot attached and help me to add the new nRf9160 DK (PCA10090) to my nRF cloud account. 

Thank you.  

  • Hi! 

    Your device has been shipped with an old version of the asset_tracker sample. You will need to update the firmware before adding the device to nRF Cloud. Please use the Programmer application in nRF Connect to flash the below .hex file to your device.

    nrf91dk_asset_tracker.hex

    Side note: what appears when you press the "update your device" link?

    Best regards,

    Heidi

  • Hi, 

    Thank you for your reply. As suggested I have flashed the "nrf91dk_asset_tracker.hex" (above) using nRF Connect V3.2.0 (Erase & Write)

    But I am able to see the below logs:   (Crash logs, continuous rebooting the device) :

    ****************************** nRF Connect V3.2.0 Flashing logs *************************************
    
    [Erase All, Erase & Write]: I did NOT see any issues. 
    
    
    
    
    
    2019-11-11T11:04:33.110Z INFO Recovery procedure finished
    2019-11-11T11:04:33.112Z INFO Using nrfjprog to communicate with target
    2019-11-11T11:04:34.349Z INFO Using J-Link Software version 6.50
    2019-11-11T11:04:35.355Z INFO Segger serial: 960041169
    2019-11-11T11:04:35.355Z INFO Segger speed: 2000 kHz
    2019-11-11T11:04:35.355Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Feb 14 2019 14:03:18
    2019-11-11T11:04:35.359Z INFO Probed: 960041169.
    2019-11-11T11:04:35.359Z INFO Model: Unknown model.
    2019-11-11T11:04:35.359Z INFO RAM: 256KiB.
    2019-11-11T11:04:35.359Z INFO Flash: 1024KiB in pages of 4KiB.
    2019-11-11T11:04:35.615Z INFO Device type is unknown. It may be a new version of product from Nordic Semiconductor.
    2019-11-11T11:04:35.615Z INFO Please check device list supported by nrfjprog.
    2019-11-11T11:04:36.587Z INFO Reading device non-volatile memory. This may take a few seconds.
    2019-11-11T11:04:45.558Z INFO Non-volatile memory has been read. 1 non-empty memory blocks identified.
    2019-11-11T11:06:55.183Z INFO Recovery procedure finished
    2019-11-11T11:06:55.185Z INFO Using nrfjprog to communicate with target
    2019-11-11T11:06:56.464Z INFO Using J-Link Software version 6.50
    2019-11-11T11:06:57.453Z INFO Segger serial: 960041169
    2019-11-11T11:06:57.453Z INFO Segger speed: 2000 kHz
    2019-11-11T11:06:57.453Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Feb 14 2019 14:03:18
    2019-11-11T11:06:57.456Z INFO Probed: 960041169.
    2019-11-11T11:06:57.456Z INFO Model: Unknown model.
    2019-11-11T11:06:57.456Z INFO RAM: 256KiB.
    2019-11-11T11:06:57.456Z INFO Flash: 1024KiB in pages of 4KiB.
    2019-11-11T11:06:57.727Z INFO Device type is unknown. It may be a new version of product from Nordic Semiconductor.
    2019-11-11T11:06:57.727Z INFO Please check device list supported by nrfjprog.
    2019-11-11T11:06:58.710Z INFO Reading device non-volatile memory. This may take a few seconds.
    2019-11-11T11:06:59.018Z INFO Writing procedure starts
    2019-11-11T11:07:13.467Z INFO Write procedure finished
    2019-11-11T11:07:13.469Z INFO Using nrfjprog to communicate with target
    2019-11-11T11:07:14.699Z INFO Using J-Link Software version 6.50
    2019-11-11T11:07:15.702Z INFO Segger serial: 960041169
    2019-11-11T11:07:15.702Z INFO Segger speed: 2000 kHz
    2019-11-11T11:07:15.702Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Feb 14 2019 14:03:18
    2019-11-11T11:07:15.707Z INFO Probed: 960041169.
    2019-11-11T11:07:15.707Z INFO Model: Unknown model.
    2019-11-11T11:07:15.707Z INFO RAM: 256KiB.
    2019-11-11T11:07:15.707Z INFO Flash: 1024KiB in pages of 4KiB.
    2019-11-11T11:07:15.963Z INFO Device type is unknown. It may be a new version of product from Nordic Semiconductor.
    2019-11-11T11:07:15.963Z INFO Please check device list supported by nrfjprog.
    2019-11-11T11:07:16.952Z INFO Reading device non-volatile memory. This may take a few seconds.
    2019-11-11T11:07:25.946Z INFO Non-volatile memory has been read. 4 non-empty memory blocks identified.
    
    

    ****************************** nRF9160 DK (PCA10090) Crash Logs ********************************
    
    
    SPM: NS image at 0x18200
    SPM: NS MSP at 0x2002e5a0
    SPM: NS reset vector at 0x20195
    SPM: prepare to jump to Non-Secure image.
    ***** Booting Zephyr OS build v2.0.99-ncs1-rc1-11-g9be97c63368a *****
    
    [00:00:00.352,050] <err> nrf9160_gps: Could not confiugure MAGPIO, error: -8             ==> This may causing the device continious reboot. 
    
    
    Asset tracker started
    
    [00:00:00.362,426] <dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100219636
    [00:00:00.371,520] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100219636/shadow
    [00:00:00.382,995] <dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100219636/shadow/get/accepted
    [00:00:00.394,317] <dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100219636/shadow/get/rejected
    [00:00:00.406,677] <dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100219636/shadow/update/delta
    [00:00:00.419,342] <dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100219636/shadow/update
    [00:00:00.430,999] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100219636/shadow/get
    Connecting to LTE network. This may take several minutes.
    [00:00:00.448,516] <dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0
    LTE link could not be established.
    ***** Booting Zephyr OS build v2.0.99-ncs1-rc1-11-g9be97c63368a *****
    [00:00:00.007,141] <inf> mcuboot: Starting bootloader
    [00:00:00.015,350] <inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
    [00:00:00.028,106] <inf> mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
    [00:00:00.040,222] <inf> mcuboot: Boot source: primary slot
    [00:00:00.051,208] <inf> mcuboot: Swap type: none
    [00:00:00.469,329] <inf> mcuboot: Bootloader chainload address offset: 0xc000
    [00:00:00.476,837] <inf> mcuboot: Jumping to the first image slot
    ***** Booting Zephyr OS build v2.0.99-ncs1-rc1-11-g9be97c63368a *****
    Flash region Domain Permissions
    00 0x00000 0x08000 Secure rwxl
    01 0x08000 0x10000 Secure rwxl
    02 0x10000 0x18000 Secure rwxl
    03 0x18000 0x20000 Non-Secure rwxl
    04 0x20000 0x28000 Non-Secure rwxl
    05 0x28000 0x30000 Non-Secure rwxl
    06 0x30000 0x38000 Non-Secure rwxl
    07 0x38000 0x40000 Non-Secure rwxl
    08 0x40000 0x48000 Non-Secure rwxl
    09 0x48000 0x50000 Non-Secure rwxl
    10 0x50000 0x58000 Non-Secure rwxl
    11 0x58000 0x60000 Non-Secure rwxl
    12 0x60000 0x68000 Non-Secure rwxl
    13 0x68000 0x70000 Non-Secure rwxl
    14 0x70000 0x78000 Non-Secure rwxl
    15 0x78000 0x80000 Non-Secure rwxl
    16 0x80000 0x88000 Non-Secure rwxl
    17 0x88000 0x90000 Non-Secure rwxl
    18 0x90000 0x98000 Non-Secure rwxl
    19 0x98000 0xa0000 Non-Secure rwxl
    20 0xa0000 0xa8000 Non-Secure rwxl
    21 0xa8000 0xb0000 Non-Secure rwxl
    22 0xb0000 0xb8000 Non-Secure rwxl
    23 0xb8000 0xc0000 Non-Secure rwxl
    24 0xc0000 0xc8000 Non-Secure rwxl
    25 0xc8000 0xd0000 Non-Secure rwxl
    26 0xd0000 0xd8000 Non-Secure rwxl
    27 0xd8000 0xe0000 Non-Secure rwxl
    28 0xe0000 0xe8000 Non-Secure rwxl
    29 0xe8000 0xf0000 Non-Secure rwxl
    30 0xf0000 0xf8000 Non-Secure rwxl
    31 0xf8000 0x100000 Non-Secure rwxl
    Non-secure callable region 0 placed in flash region 2 with size 32.
    
    
    SRAM region Domain Permissions
    00 0x00000 0x02000 Secure rwxl
    01 0x02000 0x04000 Secure rwxl
    02 0x04000 0x06000 Secure rwxl
    03 0x06000 0x08000 Secure rwxl
    04 0x08000 0x0a000 Secure rwxl
    05 0x0a000 0x0c000 Secure rwxl
    06 0x0c000 0x0e000 Secure rwxl
    07 0x0e000 0x10000 Secure rwxl
    08 0x10000 0x12000 Non-Secure rwxl
    09 0x12000 0x14000 Non-Secure rwxl
    10 0x14000 0x16000 Non-Secure rwxl
    11 0x16000 0x18000 Non-Secure rwxl
    12 0x18000 0x1a000 Non-Secure rwxl
    13 0x1a000 0x1c000 Non-Secure rwxl
    14 0x1c000 0x1e000 Non-Secure rwxl
    15 0x1e000 0x20000 Non-Secure rwxl
    16 0x20000 0x22000 Non-Secure rwxl
    17 0x22000 0x24000 Non-Secure rwxl
    18 0x24000 0x26000 Non-Secure rwxl
    19 0x26000 0x28000 Non-Secure rwxl
    20 0x28000 0x2a000 Non-Secure rwxl
    21 0x2a000 0x2c000 Non-Secure rwxl
    22 0x2c000 0x2e000 Non-Secure rwxl
    23 0x2e000 0x30000 Non-Secure rwxl
    24 0x30000 0x32000 Non-Secure rwxl
    25 0x32000 0x34000 Non-Secure rwxl
    26 0x34000 0x36000 Non-Secure rwxl
    27 0x36000 0x38000 Non-Secure rwxl
    28 0x38000 0x3a000 Non-Secure rwxl
    29 0x3a000 0x3c000 Non-Secure rwxl
    30 0x3c000 0x3e000 Non-Secure rwxl
    31 0x3e000 0x40000 Non-Secure rwxl
    
    Peripheral Domain Status
    00 NRF_P0 Non-Secure OK
    01 NRF_CLOCK Non-Secure OK
    02 NRF_RTC1 Non-Secure OK
    03 NRF_NVMC Non-Secure OK
    04 NRF_UARTE1 Non-Secure OK
    05 NRF_UARTE2 Secure SKIP
    06 NRF_TWIM2 Non-Secure OK
    07 NRF_SPIM3 Non-Secure OK
    08 NRF_TIMER0 Non-Secure OK
    09 NRF_TIMER1 Non-Secure OK
    10 NRF_TIMER2 Non-Secure OK
    11 NRF_SAADC Non-Secure OK
    12 NRF_PWM0 Non-Secure OK
    13 NRF_PWM1 Non-Secure OK
    14 NRF_PWM2 Non-Secure OK
    15 NRF_PWM3 Non-Secure OK
    16 NRF_WDT Secure SKIP
    17 NRF_IPC Non-Secure OK
    18 NRF_VMC Non-Secure OK
    19 NRF_FPU Non-Secure OK
    20 NRF_EGU1 Non-Secure OK
    21 NRF_EGU2 Non-Secure OK
    22 NRF_DPPIC Non-Secure OK
    23 NRF_GPIOTE1 Non-Secure OK
    24 NRF_REGULATORS Secure SKIP
    
    **************************************** /* End of nRF9160 DK (PCA10090) Crash logs */ ***********************************

    I believe this is because of "nRF91DK was NOT configured on Cloud successfully". 

    Please help me to get the device back and HOW can I register DK with cloud ..?? 

    NOTE: I have already a thingy91 (PCA20035) device registered in my nRF cloud account. 

    This is nRF9160 DK (PCA10090) would be the second device on the same nRF Cloud account. 

    Side note: what appears when you press the "update your device" link?

    When I press "Update your device" it redirecting me to " https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update"

    Please help me, as its road BLOCK for me. 

    Thank you. 

  • Hi, the asset_tracker sample does not crash just because the device isn't added to nRF Cloud, so this isn't the root cause of your issue.

    Could you try running through the tutorial you linked to and then try adding the device to nRF Cloud again?

    If it doesn't work please share a screenshot of the error message again and the terminal output.

  • Hi again!

    I can see from GSMA's deployment map that neither LTE-M nor NB-IoT has been deployed in your country, which is why your device can't get an LTE connection and is restarting. 

    Best regards,

    Heidi

  • Hi, 

    Actually, nRF9160 DK (10090) is in USA (California). I am remotely working on it. 

    Note that, I am also working on Thnigy91 (PCA20035), where I do NOT have any issues. 

    I am able to successfully build and flash (mcumgr) without any issues on Thingy91 (PCA20035).

    Since we have issues to flash nRF52840 (PCA20035), we have bought a new nRF9160 DK (10090), which unfortunately

    NOT working.

    I have tried all possible ways to get it back, but no luck. it is continuously rebooting.   

    Followed "  https://devzone.nordicsemi.com/f/nordic-q-a/54272/issue-nrf9160-dk-pca10090-is-rebooting  " 

    Please help me with this issue, as its blocking my development activity. 

    Thank you.  

Related