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

nrf9160 DK AWS IoT cloud connection issue

Sobaha Azam

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  

  • 0

    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

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

    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

    Fullscreen modem_debug_noconnect.txt Download 
    00> *** Booting Zephyr OS build v2.7.0-ncs1  ***
00> <inf> <mflt>: Reset Reason, RESETREAS=0x0
00> <inf> <mflt>: Reset Causes: 
00> <inf> <mflt>:  Power on Reset
00> <inf> <mflt>: GNU Build ID: 8de9aee36569f6939ca966c34abdf52b064fd7fe
00> I: [WD] No Dump
00> I: [WD] Watchdog Init to 1000 ms timeout
00> W: [WD] NOT Ready - Keep Active
00> I: 3 Sectors of 4096 bytes
00> I: alloc wra: 0, f78
00> I: data wra: 0, 38
00> E: [NVS] Settings read from MEM failed SYS:0 MEM:0 CLOUD:0
00> I: [MAIN] MEMO Init V: vX.X.X
00> I: [MAIN] Software is in Test
00> I: [MAIN] Reset Reason 0, Button:0 Software:0 WD:0
00> I: [MAIN] Reboot Counter: 1
00> W: [INIT] UART0 is Disabled
00> I: [MODEM] Modem Band Lock Set 
00> I: [MODEM] Version: 1.3.1
00> I: [CHARGER] Bat Power OK: 1
00> I: [CHARGER] Battery is Connected
00> I: [MAIN] Start First Init
00> I: [BUTTON] Silent Mode: 1
00> I: [PROXY] Load Cal from Mem
00> I: [INIT] Set Tray to Unknown
00> I: [INIT] Hardware OK
00> W: [MAIN] Startup Check - Bat: 3993
00> I: [USB] DISCONNECTED
00> E: [AWS] Send Message: AWS is not Init
00> I: [MODEM] sim_id: 901405102318251
00> I: [MODEM] client_id: nrf-352656106701W: [AWS] iot_reconnect - wait 30 s connect try: 2/30
00> I: [AWS] IOT_EVT_CONNECTING
00> E: getaddrinfo, error -11
00> E: client_broker_init, error: -10
00> I: [AWS] IOT_EVT_CONNECTING
00> I: [MODEM] Network registration status: Connected - roaming
00> I: [MODEM] PSM parameter update: TAU: 1116000, Active time: -1
00> I: [AWS] iot_reconnect - Restart Once after network back
00> W: [AWS] iot_reconnect - wait 30 s connect try: 3/30
00> I: [AWS] IOT_EVT_CONNECTING
00> E: getaddrinfo, error -2
00> E: client_broker_init, error: -10
00> I: [AWS] IOT_EVT_CONNECTING
00> W: [AWS] iot_reconnect - wait 30 s connect try: 4/30
00> I: [AWS] IOT_EVT_CONNECTING
00> E: getaddrinfo, error -2
00> E: client_broker_init, error: -10
00> I: [AWS] IOT_EVT_CONNECTING
00> I: [AWS] iot_reconnect Restart Modem
00> I: [AWS] CFUN4: 
00> I: [AWS] CFUN1: 
00> W: [AWS] iot_reconnect - wait 30 s connect try: 5/30
00> I: [AWS] IOT_EVT_CONNECTING
00> E: getaddrinfo, error -11
00> E: client_broker_init, error: -10
00> I: [AWS] IOT_EVT_CONNECTING
00> I: [AWS] iot_reconnect - Restart Once after network back
00> W: [AWS] iot_reconnect - wait 30 s connect try: 6/30
00> I: [AWS] IOT_EVT_CONNECTING
00> E: getaddrinfo, error -11
00> E: client_broker_init, error: -10
00> I: [AWS] IOT_EVT_CONNECTING
00> I: [AWS] iot_reconnect - Restart Once after network back
00> W: [AWS] iot_reconnect - wait 30 s connect try: 7/30
00> I: [AWS] IOT_EVT_CONNECTING
00> E: getaddrinfo, error -11
00> E: client_broker_init, error: -10
00> I: [AWS] IOT_EVT_CONNECTING
00> I: [MODEM] Network registration status: Connected - roaming
00> W: [AWS] iot_reconnect - wait 30 s connect try: 8/30
00> I: [AWS] IOT_EVT_CONNECTING
00> E: getaddrinfo, error -2
00> E: client_broker_init, error: -10
00> I: [AWS] IOT_EVT_CONNECTING
(Connection lost)

  • 0 in reply to danielboe

    Hi,

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

    Best regards,
    Dejan

  • 0 in reply to dejans

    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

Related
Terms of service