nrf9160 DK AWS IoT cloud connection issue

RE: nrf9160 DK AWS IoT cloud connection issue

dejans — Fri, 06 May 2022 14:17:16 GMT

Hi,

You should not post your private key on the Internet.
You should generate a new one.

Best regards,
Dejan

RE: nrf9160 DK AWS IoT cloud connection issue

dejans — Fri, 06 May 2022 06:48:48 GMT

Hi,

There are several indented lines. You could try removing the indentation in the two lines below the line which contains #define, as well as in the last line.
Please check the documentation related to the certificates in the modem key management.

Best regards,
Dejan

RE: nrf9160 DK AWS IoT cloud connection issue

Sobaha Azam — Thu, 05 May 2022 20:12:53 GMT

I added every other line \n" \ but still it is not working. Now, what should I do to make it work?

Best regards

Sobaha

RE: nrf9160 DK AWS IoT cloud connection issue

dejans — Thu, 05 May 2022 12:36:23 GMT

Hi,

You could try as suggested. Afterwards, you can get back with the result.

Best regards,
Dejan

RE: nrf9160 DK AWS IoT cloud connection issue

Sobaha Azam — Wed, 04 May 2022 21:02:44 GMT

So I simply need to include those symbols, and it won't throw any errors at me, correct?
or do I need to do something extra to ensure that I don't get any errors and that I get the output like everything is connected?

Best regards,

Sobaha Azam

RE: nrf9160 DK AWS IoT cloud connection issue

dejans — Wed, 04 May 2022 14:25:02 GMT

Hi,

You would need to change how you write the certificate.

Required changes include adding '\n' and '\' symbols into their proper places, as shown below.

First two lines should be
#define ... \
"--- BEGIN CERTIFICATE---\n" \

Other lines should also have '\n', and '\' at the end.

Last line should have '\n' as well.
"---END CERTIFICATE---\n"

Best regards,
Dejan

RE: nrf9160 DK AWS IoT cloud connection issue

Sobaha Azam — Tue, 03 May 2022 20:02:31 GMT

devzone.nordicsemi.com/.../trace_2D00_2022_2D00_05_2D00_03T19_2D00_34_2D00_54.167Z.bin

#define AWS_IOT_CLIENT_PRIVATE_KEY \

"-----BEGIN RSA PRIVATE KEY-----"

---------------------------------------------------------

"-----END RSA PRIVATE KEY-----"

#define AWS_IOT_CLIENT_PUBLIC_CERTIFICATE

"-----BEGIN CERTIFICATE-----"

-------------------------------------------------

"-----END CERTIFICATE-----"

#define AWS_IOT_CA_CERTIFICATE

"-----BEGIN CERTIFICATE-----"

----------------------------------------------

"-----END CERTIFICATE-----"

This is how I wrote in the VSCode, and I simply copied and pasted it into the modem as it was like

"------BEGIN CERTIFICATE-----"

--------------------------------------

"--------END CERTIFICATE------"

I've also provided the RAW trace file. Now can you please help me to resolve this issue?

Best regards

Sobaha

RE: nrf9160 DK AWS IoT cloud connection issue

dejans — Tue, 03 May 2022 09:28:33 GMT

Hi,

In order to get more information from the trace, could you send RAW trace file as well?

In addition, could you precisely describe how you write the certificates to the modem?

Best regards,
Dejan

RE: nrf9160 DK AWS IoT cloud connection issue

Sobaha Azam — Mon, 02 May 2022 17:24:42 GMT

I am able to capture data using trace collector v2, but I'm not sure what I need to do next to resolve my problem. How do I get AWS IOT EVT CONNECTED instead of AWS IOT EVT CONNECTING? How do I resolve Error -111? The deadline is approaching, and I need to do this as quickly as possible. The fact is that I've been fighting this problem for about a month. You can help me out by providing a detailed step-by-step lesson this time so that I can figure out what's wrong. I've also provided a copy of my log file also capturing trace file.

devzone.nordicsemi.com/.../new2022_2D00_05_2D00_02T17_5F00_07_5F00_34.444Z_2D00_log.txt

devzone.nordicsemi.com/.../trace_2D00_2022_2D00_05_2D00_02T19_2D00_04_2D00_28.483Z.pcapng

Best regards

Sobaha

RE: nrf9160 DK AWS IoT cloud connection issue

danielboe — Mon, 02 May 2022 15:40:27 GMT

Ah I may got you wrong. I used the nrf trace (not v2, its not capturing any data)

RE: nrf9160 DK AWS IoT cloud connection issue

danielboe — Mon, 02 May 2022 15:00:43 GMT

you need to set CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y and you need to map the uart1 as the debug serial port to your debug device ( so map it to the right pins) in your .overlay file. if you use dev-board I think you dont need to change the .overlay file

RE: nrf9160 DK AWS IoT cloud connection issue

dejans — Mon, 02 May 2022 14:43:46 GMT

Hi,

Could you specify how you have got the trace .bin file?

Best regards,
Dejan

RE: nrf9160 DK AWS IoT cloud connection issue

danielboe — Mon, 02 May 2022 14:21:19 GMT

Attached is a log of my issue with connection to aws with trace data. also a log of the RTT of the situation

Edit: the trace v2 is not capturing any data with the same setup.

devzone.nordicsemi.com/.../trace_2D00_2022_2D00_05_2D00_02T14_2D00_14_2D00_04.176Z.bin

devzone.nordicsemi.com/.../modem_5F00_debug_5F00_noconnect.txt

RE: nrf9160 DK AWS IoT cloud connection issue

dejans — Mon, 02 May 2022 12:23:02 GMT

Hi,

Setting the option CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y in prj.conf would be correct. However, you should not put the same option inside the Link Monitor, as this is what caused the error.
After you set this option in prj.conf, you should be able to use Trace Collector v2 to provide pcap log of the connection.

Best regards,
Dejan

RE: nrf9160 DK AWS IoT cloud connection issue

danielboe — Mon, 02 May 2022 08:27:55 GMT

I want to join here. I have the same error. We develop a device based on nrf91 and since 28.04.2022 most devices connect not anymore. We use 1nce provider and we are in contact. 1nce can see the connection but also can see that there are 0 Bytes of data transmission. they claim there is no issue on their site. I will add more info and log data later. The issue is very urgent for us

Thanks and best regards

Daniel