• State Not Answered
  • Replies 15 replies
  • Subscribers 26 subscribers
  • Views 635 views
  • Users 0 members are here
Attachments (5) Download All
Nordic Case Info
  • Case ID: 288401
Options

nrf9160 DK AWS IoT cloud connection issue

user114092

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  

Parents
  • 0

    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

  • 0 in reply to user111786

    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.

     

     

     

    Best regards

    Sobaha 

  • 0 in reply to user114092

    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

  • 0 in reply to user111786

    #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
Reply
  • 0 in reply to user111786

    #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
Children
Related
Terms of service