asset-tracker v2 on custom PCB/board - Device cannot connect to nRF Cloud, even after provisioning and flashing certificates

RE: asset-tracker v2 on custom PCB/board - Device cannot connect to nRF Cloud, even after provisioning and flashing certificates

user102811 — Wed, 30 Mar 2022 08:07:10 GMT

Hi @Floyd

I have flashed the AT_client example onto my board, connected a UART to USB converter to the board's UART pins and then I've run this python script. https://github.com/nRFCloud/utils/blob/master/python/modem-firmware-1.3%2B/device_credentials_installer.py

You would need a CA certificate along with others to generate the device certificates on your computer and then flash it to your board using the device_credentials_installer.py script. I followed the guide on this page https://docs.nrfcloud.com/Guides/GettingStarted/Devices/ , under "Generating credentials on a computer". You may need to follow other guides on the same page to generate your own certificates (CA and others).

I have used this command to the generate the device certificates and flash them onto my board.

python device_credentials_installer.py -A -S 16842753 -d --port /dev/ttyUSB1 --ca 0xxxxxxxxxxxxxxxxxxxxx_ca.pem --ca_key 0xxxxxxxxxxxxxxxxxxxxxxx_prv.pem --csv provision.csv

This script then generates the csv file which you could then upload to nrflcoud.

The .pem files are your CA and private keys, that you could generate with github.com/.../create_ca_cert.py

I've also used the information on this github page
https://github.com/nRFCloud/utils/tree/master/python/modem-firmware-1.3%2B

Hope it helps :)

Makkash

RE: asset-tracker v2 on custom PCB/board - Device cannot connect to nRF Cloud, even after provisioning and flashing certificates

user109336 — Wed, 30 Mar 2022 01:33:57 GMT

The connection status on the device page is for devices connecting via MQTT and running an application like asset_tracker_v2. So you can probably ignore it.

The provisioning step completed successfully, which is why your device now appears in your nRF cloud account. You should be able to now access nRF cloud from your device using MQTT or REST.

RE: asset-tracker v2 on custom PCB/board - Device cannot connect to nRF Cloud, even after provisioning and flashing certificates

user32317 — Wed, 30 Mar 2022 01:03:47 GMT

Hi Justin,

I tried according to your instruction. I can see my device in nRF Cloud. But it is "disconnected".

And in the Provision Devices page, the status is "Successed". Any idea why? The main reason I need to connect to the nRF Cloud is to use its A-GPS data.

Regards,

Floyd

RE: asset-tracker v2 on custom PCB/board - Device cannot connect to nRF Cloud, even after provisioning and flashing certificates

user32317 — Tue, 29 Mar 2022 22:35:18 GMT

Thank you Justin. Will give that a go.

RE: asset-tracker v2 on custom PCB/board - Device cannot connect to nRF Cloud, even after provisioning and flashing certificates

user109336 — Tue, 29 Mar 2022 21:16:55 GMT

the API documentation displays a some examples of the csv file format.
https://api.nrfcloud.com/v1#operation/ProvisionDevices

Here is the example which uses the device ID (required), FOTA capabilities (not required), and device certificate (required):

f69c0e45-7f04-4949-8def-bb2215b4223e,,,APP|MODEM,"-----BEGIN CERTIFICATE-----
MIIB7DCCAZMCFD...Av3CVgjzn5BLS03X7lyf4w==
-----END CERTIFICATE-----
"

The first item is the device ID. This example uses a UUID format for the device ID. Replace with your device's ID.

The APP|MODEM text indicates FOTA capabilities for your device. You can remove the text if you do not want to include that capability.

Copy and paste your device certificate in PEM format; it should include the newlines. Note the required trailing newline.

Here is a full example for a device with an nrf-<IMEI> formatted device ID with no FOTA capabilities enabled:

nrf-352656100300204,,,,"-----BEGIN CERTIFICATE-----
MIICzTCCAbUCCQC0PqjeoGxT9TANBgkqhkiG9w0BAQsFADCBizELMAkGA1UEBhMC
Tk8xDzANBgNVBAgMBk5vcndheTESMBAGA1UEBwwJVHJvbmRoZWltMR0wGwYDVQQK
DBROb3JkaWMgU2VtaWNvbmR1Y3RvcjE4MDYGA1UECwwvZWxpdmFnYXItcHJvZC1w
Y2ExMDA5MC11cC10by0xOTA5MDItdGhpbmctZ3JvdXAwIBcNMjIwMzI5MjEwNzIx
WhgPMjA1MjAzMjEyMTA3MjFaMIGNMQswCQYDVQQGEwJOTzESMBAGA1UECAwJVHJv
bmRlbGFnMRIwEAYDVQQHDAlUcm9uZGhlaW0xITAfBgNVBAoMGE5vcmRpYyBTZW1p
Y29uZHVjdG9yIEFTQTEcMBoGA1UEAwwTbnJmLTM1MjY1NjEwMDMwMDIwNDEVMBMG
A1UELhMMRTk2NDA3RTAzRTVGMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEiGQ6
MgMwhr7xVE7nBn42XDDGSBzQhrN6PIYH9hpQbKFF+jLAN/coMdl5FGcKZ3d3MjDk
wjV7bciIHB7CMGUPyzANBgkqhkiG9w0BAQsFAAOCAQEAP56rTVFPLB1CRpmlAr8o
W6wHOjQVAkfHEEIybVQ1oTT/9qEF9zZd/cYnyuC6W2A+BuuW1xbGo33MpB5fyVCH
Fhv736b4pdpisF/H+ZplkSOYnO0yUBpF6STURB5OkFPEjl9gmAQmGWgRBO6MmRxI
jU0AjK/4RnwB9N0xfbDPGB3X6SSOsyoFssQBKtzJGhdR6OM32N6bmR1BP29I3Vbx
retSi6rfJkNeX21fBIyLNwtOz87MH7VT3Mzue5kqLk/u3AQIEuY++GrzPVHI6QL6
bTeGRyEbu3iP+Wn/i37K0bABvzW7Rdx253bGHSjFLlK6glbBsjz6SXe3FFnOffSq
og==
-----END CERTIFICATE-----
"

You can upload your csv file using the website: https://nrfcloud.com/#/provision-devices
Or you can use the REST API as described by the API documentation.

RE: asset-tracker v2 on custom PCB/board - Device cannot connect to nRF Cloud, even after provisioning and flashing certificates

user32317 — Tue, 29 Mar 2022 20:46:52 GMT

Hi Makkash,

Do you mind sharing with me how to create the provision.csv file? I generated and downloaded all certificates to my board. I can see (16842753,0), (16842753,1) and (16842753,2) certificates when I used the command at%cmng=1. But I kept failing provisioning my device to the nRF Cloud. You help is very much appreciated.

Thank you,

Floyd

RE: asset-tracker v2 on custom PCB/board - Device cannot connect to nRF Cloud, even after provisioning and flashing certificates

user102811 — Fri, 05 Nov 2021 17:37:25 GMT

Thank you very much! After hours of flashing certificates and provisioning devices in nRF Cloud, the asset tracker v2 works on my PCB!

RE: asset-tracker v2 on custom PCB/board - Device cannot connect to nRF Cloud, even after provisioning and flashing certificates

user109336 — Fri, 05 Nov 2021 16:17:22 GMT

It looks like you have done all the required steps... one last thing would be to check the dependency for using the internal UUID:

config NRF_CLOUD_CLIENT_ID_SRC_INTERNAL_UUID
	bool "Modem internal UUID value"
	depends on MODEM_JWT
	help
		Requires modem firmware version 1.3 or later.

You probably just need to add CONFIG_MODEM_JWT=y to your prj.conf