Sample nRF9160: Azure IoT Hub

RE: Sample nRF9160: Azure IoT Hub

Apfelsine — Mon, 12 Oct 2020 14:30:07 GMT

Here we go - Success!

Thank you for the clarification. Sabine Urquhart

RE: Sample nRF9160: Azure IoT Hub

Martin Lesund — Mon, 12 Oct 2020 12:26:41 GMT

Hi Sabine,

In our docs about Azure we point to this link to get the certificates.

In that page there is a link to "Managing test CA certificates for samples and tutorials" which has the scripts used and the explanations you are looking for.

So the following is needed to get it to work with PowerShell-generated certs:

CA certificate: Baltimore CyberTrust Root certificate
Client certificate: <device name>-public.pem
Private key: <device name>-private.pem

"RootCA.pem" has to be uploaded to the IoT Hub and verified.

For bash-generated certs, then the following is needed:

CA certificate: Baltimore CyberTrust Root certificate
Client certificate: certs/new-device.cert.pem
Private key: private/new-device.key

"certs/azure-iot-test-only.root.ca.cert.pem" has to be uploaded to IoT Hub and verified.

Best regards,
Martin L.

RE: Sample nRF9160: Azure IoT Hub

Martin Lesund — Fri, 09 Oct 2020 13:46:04 GMT

Hi Apfelsine,
Still looks like there some issues with the certificates unfortunately.

You can find the Baltimore CyberTrust Root certificate by following the link in the instructions here.

The Server-certificate is this.

The RootCA.pem that you mention is probably the generated certificate, that should be uploaded to the IoT Hub.

"Does Private key equate to file mydevice-private.pem?" - Yes

"Does Device certificate equate to file mydevice-public.pem?" - I think this needs to be chained with the intermediate-certificate.e.g.

-----BEGIN CERTIFICATE-----
<Device cert>
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
<Intermediate cert>
-----END CERTIFICATE-----

RE: Sample nRF9160: Azure IoT Hub

Apfelsine — Wed, 07 Oct 2020 16:46:43 GMT

Here is another thought. Could you please have a look at my Kconfig file. Maybe I am doing something wrong there?

devzone.nordicsemi.com/.../zz_5F00_azure_5F00_iot_5F00_hub.zip

RE: Sample nRF9160: Azure IoT Hub

Apfelsine — Wed, 07 Oct 2020 16:15:00 GMT

Hi Martin,

thank you for looking into this. I did as you suggested I uncommented CONFIG_AZURE_IOT_HUB_LOG_LEVEL_DBG=y in proj.conf and I followed all the steps to provision the certificate more than once. I still receive the same error. I attached the latest log file. What else can I do to troubleshoot?

devzone.nordicsemi.com/.../2020_2D00_10_2D00_06T16_5F00_35_5F00_55.766Z_2D00_log.txt

RE: Sample nRF9160: Azure IoT Hub

Martin Lesund — Wed, 07 Oct 2020 09:50:14 GMT

Hi Sabine,

A project that has the following in prj.conf:

CONFIG_NEWLIB_LIBC=y

Will use the errno table according to newlib.

So the error you are seeing is EOPNOTUPP: "Operation not supported on transport endpoint "

I would also recommend that you enable some debug flags to get some extra Log output messages that could give more descriptive information about issues like this.

Add this in the prj.conf file:

CONFIG_LOG=y
CONFIG_AZURE_IOT_HUB_LOG_LEVEL_DBG=y

This is most likely a certificate issue.
Have you followed all the steps to provision the certificates?

Best regards,

Martin L.