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.  

Parents Reply Children
  • Could you try the things I suggested in my previous reply?

    Running through the tutorial you linked to and then adding the device to nRF Cloud. And attaching a screenshot of the error message if it doesn't work. 

  • Hi Heidi, 

    I have followed the steps mentioned in the link  [ https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update  ] above. 

    Due to the continuous rebooting device (nRF9160_pca10090 DK), NOT able to execute the AT+CFUN=4 command. 

    I have tried flashing the "nrf9160dk_at_client_09-10-2019_c9c833b1.hex", but no luck. 

    Eventually, updating the certificate on the nRF9160 (PCA10090) board is  FAILED and NOT able to add to the Cloud account and still rebooting. 

    Please find the screenshot attached and do needful. 

    Thank you. 

  • Ok, so just to clarify, even though you successfully flashed the at_client sample to the device, you could not set the modem in offline mode (AT+CFUN=4) because the device keeps continuously rebooting. 

    This happened to my device once and what worked was updating the modem firmware (even if you are using the correct version). 

    I see from your other posts that you are trying to program the Thingy:91. Note that the nRF9160 on the nRF91DK does not have to be functioning for you to use the nRF91DK as a debugger to program the Thingy:91.

    Best regards,

    Heidi

  • Hi, 

    Ok, so just to clarify, even though you successfully flashed the at_client sample to the device, you could not set the modem in offline mode (AT+CFUN=4) because the device keeps continuously rebooting. 

    Correct. 

    This happened to my device once and what worked was updating the modem firmware (even if you are using the correct version). 

    Here, I have tried to update the mode firmware on nRF9160 DK (10090) device, but I am getting the following errors. 

    nrfjprog --eraseall -f nrf91

    nrfjprog --program firmware.update.image.segments.1.hex --sectorerase -r -f nrf91 --verify Parsing hex file.
    ERROR: The file specified is not a valid hex file, has data outside valid areas
    ERROR: or does not have data invalid areas.

    (Same issue was observed while flashing with nRF Connect v3.2.0)

    I have downloaded modem firmware from " https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF9160-DK/Download#infotabs "

    (mfw_nrf9160_1.0.1 -->firmware.update.image.segments.1.hex & firmware.update.image.segments.0.hex)

    If I am wrong, pl let me know the correct modem firmware Image. 

    I see from your other posts that you are trying to program the Thingy:91. Note that the nRF9160 on the nRF91DK does not have to be functioning for you to use the nRF91DK as a debugger to program the Thingy:91.

    Just for your information: I did NOT connect thingy91 (PCA20035) to nRF9160 DK (10090) device, as DK (10090) itself NOT stable yet. I am NOT trying to flash thingy91 (PCA20035) using nRF91 DK (10090) for now. 

    After all, now I am able to see the new ERROR Message while adding nRF9160 (10090) to the cloud account. 

    Please find the screenshot attached. 

    Thank you. 

     

     

  • Hi Heidi,

    I have an update, 

    1. I have successfully flashed mode firmware v1.1.0 and flashed at_client application as well. 

    2. Update certificate the certificate successfully. 

    "

    AT+CFUN=4

    OK

    AT%CMNG=0,16842753,0,"-----BEGIN CERTIFICATE-----

    -----END CERTIFICATE-----"OK

    AT%CMNG=0,16842753,1,"-----BEGIN CERTIFICATE-----

    -----END CERTIFICATE-----"OK

    AT%CMNG=0,16842753,2,"-----BEGIN RSA PRIVATE KEY-----

    -----END RSA PRIVATE KEY-----"OK

    AT+CGSN=1

    +CGSN: "352656100219636"

    OK

    AT+CGMR

    mfw_nrf9160_1.0.1

    OK

    ISSUES: 

    1. After all, I have flashed asset_tacker application ( nrf9160dk_asset_tracker_09-10-2019_c9c833b1.hex ) ,

    Still I can see reboot issue, with different logs.  

    ***************** 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.376,739] <dbg> nrf9160_gps.init: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577
    [00:00:00.385,375] <dbg> nrf9160_gps.init: COEX0 set: AT%XCOEX0=1,1,1570,1580
    Asset tracker started
    [00:00:00.395,629] <dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100219636
    [00:00:00.404,724] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100219636/shadow
    [00:00:00.416,259] <dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100219636/shadow/get/accepted
    [00:00:00.427,581] <dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100219636/shadow/get/rejected
    [00:00:00.439,971] <dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100219636/shadow/update/delta
    [00:00:00.452,667] <dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100219636/shadow/update
    [00:00:00.464,355] <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.481,933] <dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0
    +CEREG: 2,"1F00","00798102",7,0,0,"11100000","11100000"
    [00:00:02.544,006] <dbg> lte_lc.at_handler: recv: +CEREG: 2,"1F00","00798102",7,0,0,"11100000","11100000"

    [00:00:02.554,260] <dbg> lte_lc.parse_nw_reg_status: Network registration status: 2
    +CEREG: 5,"1F00","00798102",7,,,"11100000","11100000"
    [00:00:03.898,956] <dbg> lte_lc.at_handler: recv: +CEREG: 5,"1F00","00798102",7,,,"11100000","11100000"

    [00:00:03.909,057] <dbg> lte_lc.parse_nw_reg_status: Network registration status: 5
    Connected to LTE network
    [00:00:04.242,889] <dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0xd7e20034
    [00:00:10.482,025] <inf> aws_jobs: Subscribe: $aws/things/nrf-352656100219636/jobs/notify-next
    [00:00:10.492,004] <inf> aws_jobs: Subscribe: $aws/things/nrf-352656100219636/jobs/$next/get/#
    [00:00:10.501,770] <dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_CONNACK
    [00:00:10.509,826] <dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 2
    [00:00:10.517,456] <dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED
    CLOUD_EVT_CONNECTED
    [00:00:10.527,313] <dbg> nrf_cloud_transport.nct_cc_connect: nct_cc_connect
    [00:00:10.535,583] <dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 3

    Socket error: POLLHUP
    LTE link disconnect
    +CEREG: 0,"1F00","00798102",7,0,0,"11100000","11100000"
    Shutdown modem


    ***** Booting Zephyr OS build v2.0.99-ncs1-rc1-11-g9be97c63368a *****
    [00:00:00.007,171] <inf> mcuboot: Starting bootloader
    [00:00:00.015,411] <inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
    [00:00:00.028,198] <inf> mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
    [00:00:00.040,344] <inf> mcuboot: Boot source: primary slot
    [00:00:00.051,361] <inf> mcuboot: Swap type: none
    [00:00:00.470,275] <inf> mcuboot: Bootloader chainload address offset: 0xc000
    [00:00:00.477,813] <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 logs */ **********************************

    2. Still NOT able to add nRF9160 DK (10090), to the nRF Cloud account. Please find the attached screenshot. 

    Thank you. 

Related