Attachments (1) Download All
Nordic Case Info
  • Case ID: 232426
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

asset_tracker does not work with firmware v1.0.0

Yusuke

Environment

- DK 0.8.2 in which SB44 is cut, and P1 and P2 are connected
- firmware v1.0.0
- program : asset_tracker
- SIM: iBasis

Before updating firmware, asset_tracker worked fine. 

However, after updating, LED3 is always blinking and LED4 is off.
What I do is to write the program to DK, push reset button, and wait for more than 5 min.
at_client program and LTE Link Monitor works out with v1.0.0.

this is log

Any idea to solve this?

Parents
  • +1

    Hi.

    Edit: This procedure has been deprecated by an update to the nRF Cloud API. For a new procedure, see devzone.nordicsemi.com/.../nrf-cloud-certificate-update

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------

    If your device has been registered at nRF Cloud earlier, you can recover your certificates by following this procedure:

    1. Install httpie.
    2. Get your API key from nRF Cloud (you can find it at your account page).
    3. Get the device ID by running 
      .
    4. Get the devices certificates by running 
      .
    5. Get Amazon's root CA certificate: https://www.amazontrust.com/repository/AmazonRootCA1.pem
    6. Write the certificates to the modem
      1. By writing certificates to the modem using AT command:
        1. Root CA cert: AT%CMNG=0,16842753,0,"< Amazon root CA >"
        2. Client cert:     AT%CMNG=0,16842753,1,"< Client cert >"
        3. Private key:    AT%CMNG=0,16842753,2,"< Private key >"
      2. Or by adding the certificates and your client ID to certificates.h (in the asset tracker sample) and adding CONFIG_NRF_CLOUD_PROVISION_CERTIFICATES=y to your prj.conf

    Best regards,

    Didrik

  • 0 in reply to Didrik Rokhaug

    I attempted running the AT commands in the Link Monitor, but it kept giving me a time out error. 

    I then proceeded to add the to the certificates header file, I hope that I edited it correctly

    Fullscreen certificates.txt Download

    I then proceeded to build the application and run it again. I no longer get the -111 error but now it permanently

    stays at this state

    It seems to connect to LTE as I do get a network, but LED 3 continues blinking and LED 4 remains off. 

    Please advise

  • 0 in reply to octvargas

    Can you add these options to your prj.conf and send me the log from the link monitor?

    CONFIG_LOG=y
    CONFIG_LOG_BACKEND_SHOW_COLOR=n

  • 0 in reply to Didrik Rokhaug

    odd, when i try to reply here, it looks to start a new child thread. I have a print of the log on my previous reply

  • 0 in reply to octvargas

    Hi , sorry for the delayed response.

    Have you previously paired your DK to nRF Cloud, i.e. gotten a sequence of buttons and switches to press?

    Best regards,

    Didrik

  • 0 in reply to Didrik Rokhaug

    Hi Didrik,

    Yes, I've been able to connect my DK to the nRF Cloud service before, but can't right now for some reason

  • 0 in reply to octvargas

    Is the device still registered to your nRF Cloud account?

    Do you still see it under the list of devices?

Reply Children
Terms of service