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

Fullscreen
1
2
3
4
5
6
7
8
SPM: NS image at 0xc000
SPM: NS MSP at 0x2002aa00
SPM: NS reset vector at 0x142f1
SPM: prepare to jump to Non-Secure image.
***** Booting Zephyr OS v1.14.99-ncs2-rc3 *****
Asset tracker started
Connecting to LTE network. This may take several minutes.
Connected to LTE network
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

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 
      Fullscreen
      1
      http https://api.nrfcloud.com/v1/devices Authorization:"Bearer <your API key>"
      XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
      .
    4. Get the devices certificates by running 
      Fullscreen
      1
      http POST https://api.nrfcloud.com/v1/devices/<device ID>/certificates Authorization:"Bearer <API key>"
      XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
      .
    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
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    /*
    * Copyright (c) 2018 Nordic Semiconductor ASA
    *
    * SPDX-License-Identifier: LicenseRef-BSD-5-Clause-Nordic
    */
    #define NRF_CLOUD_CLIENT_ID "my-client-id"
    #define NRF_CLOUD_CLIENT_PRIVATE_KEY \
    "-----BEGIN RSA PRIVATE KEY-----\n" \
    "MIIEpQIBAAKCAQEAzsk/XiDetNx5nDVYbjSxqftIaeYvqCiPoNhWqE9MVyYl84w0\nf3GYQDZYp5VLtP1i5o3pulblCwOO17VWRYzP6MnVxRXheKIaVf3fNw2e4MxV4XSM\n7SZe/YIqiLC18CGrNrkaOZ/SfRuJSWihZLyKndOmoJr59ahVTelL6VTun4sVlo2C\nwPuVELu47QXPfv8aTkKV8Jiz1KyyI9GAMv9HcH8ZO0whf7bsd58gSW68NAppTczv\nE9v/XZ7FctJ0Kw4aDgyNo+GkAWmuo2Tt7NY/o2MwvLcBV3wjV4lEd/pMNDez9K5r\np/9KQMxTpVPEbFOUZ+D+MXJqKUtOvl76nsMSuwIDAQABAoIBAQCqFylzcJAfrpat\nYcfKZreYvSP0T631oN97i1fEe+2sZamj6jiod7SnZMyJlClAx4fZYvPVHXKrG5Mc\nZYGAFfJSZerbgUMEKjqFbxxzOVXtTMZ7e5YL35sU5UO9SbVtvxQJIDqtGYRW+hZz\n9oeCx/8xEQ4nXzKp2XvJaVPSqtTZD2D7Mxr639ZA9OORapnJSqGzj56fUYN0YFmh\n7G61mlychhp4yZmRWvKd0HTeg09pJpnnPp77x4fs5IU1CK5fgzzj3IbB2m00a9/p\n4H29AV8DqC5nC1viK8rpbOkQ+g2bx4TVj8AhlOPBkHagsDEfSI/Q0C6dMhEj2rnY\nLh/4QS1BAoGBAOisXO5lLeanTnfS+P1vrLaYic3ocfGjHedMl0tbidajkaIZgYo1\nraejup6Y10M46obvZ7c4alyNco9+0VNtz25Eofju6808GGaZA0flGBkmVpdgkAdN\nA55UF2jltMIrlaXh+ppLj6tNh/OImhGG4vDmhitG8zLDfQzVN1Amc76bAoGBAOOE\ne1OgTX9zY6siWbMovaYL7WrjB0inru7Ygl9rl2nTK0XG6TSgOM5AyPRylY3r53nw\n02k5ngVSn5cMAr7OXJxu3KlHAzAZQk+sWdVq17uRANS5osgJeZyHcRrjpgea/n6Z\nK4ewg/pYhvpmLYL4/18qo7fAGaA8NeY5TEA4eC5hAoGBAMhv26q+3NjrXgyZYUeq\nUYYHSAdq6+W2mEcuUtNnKwoNZKLZCCAQ9+UHhfekQSS2vkq5qIZNAktyyrLVE+yk\nF2Ktmz8AS4BE+dxAinP/5k+cGFJVrB2t+aUGWhhScfIna8Y4MxOCbmSq6KgiEF9y\n7MOMQx67AzzC7VIFx52zUlhrAoGBAIgOFo34w79eqpCRVyDLUTX11gFgSF/LXtIY\nCUa0mXRAQpVUkOrWkYHNvh5oU0TueJs0R8iaGwRF14fFN/MQhtNJfI2CGMbvo/bv\nMz1ryhyxZtTPOifzepT/bcTNs+DCcEQWprBa/2F7BSTCa57x9gzb+9GLgAeRWg4V\n36Jb4oqhAoGAHC98NvCFRDynaa/ee6u7bUyJC9/r0RIWCh7mtPFXmfDOetNu12iW\nGcUvjh7Bqn/36LUtyGWjxJo0mA7373BcTlgolTFJ2rwjs5UkYmAVn1mg7UG9CLTe\n0Ek/ZOE37BBXEC/MhmE04ZFtzeAmr1nI9w2Yy1UtB0tYZs8KdNikopQ=\n" \
    "-----END RSA PRIVATE KEY-----\n"
    #define NRF_CLOUD_CLIENT_PUBLIC_CERTIFICATE \
    "-----BEGIN CERTIFICATE-----\n" \
    "MIIDWTCCAkGgAwIBAgIUQmboR8hq8jZ/Cus9FaiZybMKLTYwDQYJKoZIhvcNAQEL\nBQAwTTFLMEkGA1UECwxCQW1hem9uIFdlYiBTZXJ2aWNlcyBPPUFtYXpvbi5jb20g\nSW5jLiBMPVNlYXR0bGUgU1Q9V2FzaGluZ3RvbiBDPVVTMB4XDTE5MDcyNDE1MjQ0\nNFoXDTQ5MTIzMTIzNTk1OVowHjEcMBoGA1UEAwwTQVdTIElvVCBDZXJ0aWZpY2F0\nZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAM7JP14g3rTceZw1WG40\nsan7SGnmL6goj6DYVqhPTFcmJfOMNH9xmEA2WKeVS7T9YuaN6bpW5QsDjte1VkWM\nz+jJ1cUV4XiiGlX93zcNnuDMVeF0jO0mXv2CKoiwtfAhqza5Gjmf0n0biUlooWS8\nip3TpqCa+fWoVU3pS+lU7p+LFZaNgsD7lRC7uO0Fz37/Gk5ClfCYs9SssiPRgDL/\nR3B/GTtMIX+27HefIEluvDQKaU3M7xPb/12exXLSdCsOGg4MjaPhpAFprqNk7ezW\nP6NjMLy3AVd8I1eJRHf6TDQ3s/Sua6f/SkDMU6VTxGxTlGfg/jFyailLTr5e+p7D\nErsCAwEAAaNgMF4wHwYDVR0jBBgwFoAUzti6hgs2ZMKjSS19CW8D2s4sxEYwHQYD\nVR0OBBYEFPSvh+NtT6fwIh1HRIkg+Lq/bD+JMAwGA1UdEwEB/wQCMAAwDgYDVR0P\nAQH/BAQDAgeAMA0GCSqGSIb3DQEBCwUAA4IBAQBurwxDeQIjuQxy45YXpob49D1B\nepKjtvm9JJZBgLYaLInZf5mXEXNkSI/rWHexDnLdcubfMKEK4KQvbaDJafMINqms\nYk7YfDCiSmFls+P1qbd/FXOGZPemwo5KKlRZUzRrx/MCq90B+kJcEn/UxpexuLb+\nmN+GTiOUm7oFJufzZ3HGMeZnlIOEsqhAqin63a3ENHEsBAyKtZIuHB6SQVZHH2v2\nJT29lgIn1OV49YyGdjXyMoVjUwKu0gwqZ3eW9EJfizmyfQK0pZY8Vhs58OyrF0uk\ngw0owyoxuP0KhY8+uVh3+Z5BrhsoacYmwiBATyqTFScKEhDfhbXEZN2g8pOb\n" \
    "-----END CERTIFICATE-----\n"
    #define NRF_CLOUD_CA_CERTIFICATE \
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    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

    Is the device still registered to your nRF Cloud account?

    Do you still see it under the list of devices?

  • 0 in reply to Didrik Rokhaug

    No, I deleted my device and tried to reconnect it before I submitted a ticket

  • 0 in reply to octvargas

    I actually see two other devices that I can't delete and not my actual device, but I've had those two devices there for a while.

  • 0 in reply to octvargas

    Ah, OK. That explains why my original procedure did not work.

    I am getting the same error, but due to slightly different reasons. However, I will need to talk to R&D to solve this issue, but I will get back to you as soon as I have an answer.

    Sorry for any inconvenience.

    Best regards,

    Didrik

  • 0 in reply to Didrik Rokhaug

    Thanks Didrik,

    I appreciate it

Reply Children
Terms of service