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

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

Any idea to solve this?

[Didrik Rokhaug]

Hi, octvargas, We are working on a better way to get back the certificates. In the meantime, if you open a private case and give us the IMEI number of your nRF9160 we will give you a set of working certificates.

Best regards,

Didrik

[Markus Tacker (he/him)]

Note that version 1.8.0 of the nRF Connect for Cloud API was released last week changed this specific endpoint. It is no longer possible to generate certificates without proof of ownership.

POST ​/devices​/{deviceId}​/certificates

Creates a certificate for a device. This is a JITP (just-in-time-provisioning) certificate. For it to work properly the device must not yet be provisioned (created) on our platform. If you are creating a certificate for a device that you have already connected to our platform, please delete the device using the DELETE /devices/{deviceId} endpoint before using this certificate. For a Nordic Semiconductor product such as an nRF9160-DK or a Thingy-91, the `deviceId` is `nrf-IMEI`, e.g., `nrf-111222333444555`. The IMEI can be found on your product's label. If you want to create a certificate for a non-Nordic device, any `deviceId` is sufficient that does not start with `nrf-` (we recommend using a GUID).

The respective call with httpie looks like this:

echo -n <ownership code> | http https://api.nrfcloud.com/v1/devices/nrf-<device ID>/certificates \ 
 Authorization:"Bearer <your API key>"

You will find your deviceId and the PIN on a sticker on DKs and Thingys that support this method.

 

Example deviceId: 351234567890123

Example ownership code (PIN): 123456

httpie request with example data:

echo -n 123456 | http https://api.nrfcloud.com/v1/devices/nrf-351234567890123/certificates \
  Authorization:"Bearer <your API key>"

[Jeffery]

Hi Markus

Since my Thingy91 lost nrf cloud certificates, I tried to rewrite the certificates.

1. I tried the httpie request command with my Thingy91 PIN code, device iD and nRF Cloud API key.  It got 

    failed.

2. For this request command, it needs PIN code. However, The sticker of my DK board (v0.8.2/0.8.3) only

    have IMEI code. How to request certificates for older DK?

[Didrik Rokhaug]

Hi.

1. The echo command appends a newline, which trips up the API endpoint. We have reported this error internally. In the meantime, the easiest workaround is to use Linux (or possibly mac), and append the -n flag to the echo command.

2. I am working on a procedure for DKs without a PIN.

Best regards,

Didrik

[Jeffery]

Hi Didrik

For Q1, I used Windows 7. How to send this httpie request? Thanks.

For unknown factors, my Thingy91 started log "nrf_cloud_connect failed: -111".

I flashed AT client example and tried "AT%CMNG=1" to see certificates tag list. But, it shows nothing.

So, I think the certificates were lost.