nrf9160 DK AWS IoT cloud connection issue

I used Modem firmware version 1.3.1

In order to connect the nrf9160 DK to the AWS cloud, I am encountering errors such as AWS_ IOT_ EVT _CONNECTING, when it should be AWS_ IOT_EVT_CONNECTED, as well as error -111 when executing the code. I attempted to use the trace collector v2 preview, but it did not work. I then attempted to add the line CONFIG NRF MODEM LIB TRACE ENABLE to my prj.conf, but this resulted in an error as well as before. Can you possibly assist me in resolving this issue by providing a step-by-step tutorial? 

Best regards 

Sobaha  

  • 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

  • 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

  • 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. 

    trace-2022-05-02T14-14-04.176Z.bin

  • Hi,

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

    Best regards,
    Dejan

  • 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

1 2 3