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

nRF9160 DK cloud error "nRFCode 40001... using a non-JITP certificate"

Hello -

I am trying to set up the nRF9160 DK kit. I successfully updated the firmware and entered the ICCID, PUK, IMEI, and HWID values. When registering for nRF Cloud, in the "Add LTE" screen i get the message "There was an error adding your device: nRFCode 40001: Attempting to verify ownership code for device nrf-xxxxxxxxxxxxxxx using a non-JITP certificate." This is after I enter the IMEI and HWID values. I can confirm that iBasis SIM card that came with the kit is plugged in, and I live in an area with LTE coverage (Philadelphia). Please help. Thank you.

  • Hello, 

    What is the HW version and modem FW version of your kit? 

    There was an error adding your device: nRFCode 40001: Attempting to verify ownership code for device nrf-xxxxxxxxxxxxxxx using a non-JITP certificate.

     This error indicates that you need to update your certificates. Please follow this guide and make sure not to miss one step.

    Kind regards,
    Øyvind

  • Hi Øyvind -

    Thank you for the quick response. I have followed those instructions step by step, but keep getting stuck on step 6 from this page - https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrf91_dk_gsg%2FUG%2Fnrf91_DK_gsg%2Fprovisioning_certificate.html

    I successfully connect to the board with no SIM card plugged in. Only LED3 is blinking on the nRF9160-DK board. When I send the command "AT+CFUN=4", the LTE Link Monitor software states "Error: 'AT+CFUN=4 ' timed out". I tried rebooting my PC and the board, same result. Unfortunately I am stuck from progressing. Please let me know your thoughts. Thank you.

    - Kevin

  • Hi Kevin, 

    The time-out indicates that AT commands are not supported in the application.

    kfmurphy said:
    I send the command "AT+CFUN=4", the LTE Link Monitor software states "Error: 'AT+CFUN=4 ' timed out"

     You mentioned that you successfully updated the FW in your initial post, what FW did you use? Have you updated the modem FW as well?

    Can you please download our precompiled FW package and load the AT Client (images_full/nrf9160dk_at_client_2020-04-29_bc7ade8b.hex). Full list of content:

    These files were built with nRF Connect SDK version v1.2.0-406-gbc7ade8b
    from repository at https://github.com/NordicPlayground/fw-nrfconnect-nrf
    
    Full commit SHA: bc7ade8b14a18265933f713d47e44f4eb50f337c
    
    Package contents:
    images_full/          Full firmware images, updated over debug probe / development kit
    images_dfu_hex/       Application images, updated over USB, HEX format
    images_dfu_bin/       Application images, updated over USB, binary format
    
    images_full/debug     Full firmware images with modem debug tracing enabled, updated over debug probe / development kit
    images_dfu_hex/debug  Application images with modem debug tracing enabled, updated over USB, HEX format
    images_dfu_bin/debug  Application images with modem debug tracing enabled, updated over USB, binary format
    
    File                                                                                             Description
    -----------------------------------------------------------------------------------------------  ------------------------------------------------------------------------------
    images_dfu_bin/debug/nrf9160dk_asset_tracker_dfu_debug_2020-04-29_bc7ade8b.bin                   DEBUG Asset tracker firmware for nRF9160
    images_dfu_bin/debug/nrf9160dk_asset_tracker_nbiot_dfu_debug_2020-04-29_bc7ade8b.bin             Asset tracker firmware for nRF9160, NB-IoT network mode
    images_dfu_bin/debug/nrf9160dk_asset_tracker_nbiot_legacy_pco_dfu_debug_2020-04-29_bc7ade8b.bin  DEBUG Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO mode
    images_dfu_bin/nrf9160dk_asset_tracker_dfu_2020-04-29_bc7ade8b.bin                               Asset tracker firmware for nRF9160
    images_dfu_bin/nrf9160dk_asset_tracker_nbiot_dfu_2020-04-29_bc7ade8b.bin                         Asset tracker firmware for nRF9160, NB-IoT network mode
    images_dfu_bin/nrf9160dk_asset_tracker_nbiot_legacy_pco_dfu_2020-04-29_bc7ade8b.bin              Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO mode
    images_dfu_bin/nrf9160dk_at_client_dfu_2020-04-29_bc7ade8b.bin                                   Firmware for direct modem communication
    images_dfu_hex/debug/nrf9160dk_asset_tracker_dfu_debug_2020-04-29_bc7ade8b.hex                   DEBUG Asset tracker firmware for nRF9160
    images_dfu_hex/debug/nrf9160dk_asset_tracker_nbiot_dfu_debug_2020-04-29_bc7ade8b.hex             Asset tracker firmware for nRF9160, NB-IoT network mode
    images_dfu_hex/debug/nrf9160dk_asset_tracker_nbiot_legacy_pco_dfu_debug_2020-04-29_bc7ade8b.hex  DEBUG Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO mode
    images_dfu_hex/nrf9160dk_asset_tracker_dfu_2020-04-29_bc7ade8b.hex                               Asset tracker firmware for nRF9160
    images_dfu_hex/nrf9160dk_asset_tracker_nbiot_dfu_2020-04-29_bc7ade8b.hex                         Asset tracker firmware for nRF9160, NB-IoT network mode
    images_dfu_hex/nrf9160dk_asset_tracker_nbiot_legacy_pco_dfu_2020-04-29_bc7ade8b.hex              Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO mode
    images_dfu_hex/nrf9160dk_at_client_dfu_2020-04-29_bc7ade8b.hex                                   Firmware for direct modem communication
    images_full/debug/nrf9160dk_asset_tracker_ltem_debug_2020-04-29_bc7ade8b.hex                     DEBUG Asset tracker firmware for nRF9160
    images_full/debug/nrf9160dk_asset_tracker_nbiot_debug_2020-04-29_bc7ade8b.hex                    DEBUG Asset tracker firmware for nRF9160, NB-IoT network mode
    images_full/debug/nrf9160dk_asset_tracker_nbiot_legacy_pco_debug_2020-04-29_bc7ade8b.hex         DEBUG Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO mode
    images_full/nrf9160dk_asset_tracker_ltem_2020-04-29_bc7ade8b.hex                                 Asset tracker firmware for nRF9160
    images_full/nrf9160dk_asset_tracker_nbiot_2020-04-29_bc7ade8b.hex                                Asset tracker firmware for nRF9160, NB-IoT network mode
    images_full/nrf9160dk_asset_tracker_nbiot_legacy_pco_2020-04-29_bc7ade8b.hex                     Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO mode
    images_full/nrf9160dk_at_client_2020-04-29_bc7ade8b.hex                                          Firmware for direct modem communication
    mfwnrf9160120.zip                                                                                Modem firmware, updated through nRF Connect for Desktop
    

    If you have not updated the modem, there is a modem package available as well, and you can use the Programmer app in nRF Connect for Desktop to update it.

    Kind regards,
    Øyvind

  • Hi Øyvind -

    Thank you again for the quick response. I was able to successfully follow your suggestion to download the AT client firmware and was successfully able to update the cloud certificate following these instructions - infocenter.nordicsemi.com/index.jsp

    After that, I tried to add the LTE device in nRF cloud, but I again received the message "There was an error adding your device: nRFCode 40001: Attempting to verify ownership code for device nrf-xxxxxxxxxxxxxxx using a non-JITP certificate." I've noticed on my board now that LED3 is OFF and LED4 is constant ON, which I believe indicates the device has been successfully added to my nRF cloud account according to step #11 in this page - infocenter.nordicsemi.com/index.jsp

    FYI, my modem software is version 1.2.0 (mfw_nrf9160_1.2.0.zip), and the board firmware is nrf9160dk_asset_tracker_ltem_2020-04-29_bc7ade8b.hex.

    Unfortunately, at this point when I go to the "devices" tab in my nRF cloud account, it says "No devices found! Click on the blue "+" button to get started!", so it seems like I am back to where I started with this thread.

    Please let me know your thoughts. Thanks again.

    Regards,
    Kevin

  • Hi Kevin, 

    Sorry to hear that didn't work. Looking through the guide, it seems that it is missing a crucial step. In nRF Cloud, can you please go to Account again and reset your device:

    Kind regards,
    Øyvind

Related