How do I add nrf9160 modules to nrfcloud

[peter.min]

1. I have an nrf9160 module, patched on the customer's own board.
2. I want to connect this board to nrfcloud
3. I read the imei of this nrf9160 module through the software
4. But I don't know where to look for PIN or HWID
5. Please tell me where to get PIN or HWID to add module to nrfcloud's background

[Håkon Alseth]

Hi,

 

Only Thingy:91 and nRF9160-DKs have preloaded certificates matching the IMEI, and a HWID/pin.

 

However; you can generate your own certificates, just not name them with "nrf-"prefix.

If you follow this guide, then generate a new certificate which isn't named nrf-*:

https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update

 

Follow the guide as you would if it were a nRF9160-DK or a thingy, just that you have given it a new name and pin number.

The "pin/hwid" field can also be freely chosen, just remember it for when you should add the device to your cloud account.

 

Before compiling the asset_tracker sample, you define "NRF_CLOUD_CLIENT_ID" to match your newly generated certificate name and compile/flash the project to your device.

If you want to add this define directly to your prj.conf, it would look like this (note the string starts and ends with \" and \" symbols):

CONFIG_COMPILER_OPT="-DNRF_CLOUD_CLIENT_ID=\"my-new-nrf9160-cloud-certificate-name\""

 

Kind regards,

Håkon

[peter.min]

My device IMEI is: 352656100782559

I generate certificates with custom:
Device ID:352656100782559
PIN/HWID: 123456
I prj.conf is configured as: CONFIG_COMPILER_OPT"-DNRF_CLOUD_CLIENT_ID""352656100782559"

My test results are:
As follows

The resulting certificates are as follows:

352656100782559.cert.rar

How to connect to nrfcloud with your own modules

[Håkon Alseth]

Hi,

The errno you are seeing is this one: https://github.com/eblot/newlib/blob/master/newlib/libc/include/sys/errno.h#L147

This is normally because certificates were not properly provisioned, or in some cases; the SIM card is out of data.

  

Did you provision certificates, as described under "Provision certificates" in the linked blog post?

 

Kind regards,

Håkon