• State Verified Answer
  • Replies 7 replies
  • Subscribers 74 subscribers
  • Views 1110 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 292211
Options

nRF9160-DK - is F/W Version 1.3.2 100% Compatible w/COAP?

johnwest

Hello All,

We have a new nRF9160 design - and I've updated the 9160 binaries to version 1.3.2 - on a few PCBA's - we're seeing an error like this:



Initializing COAP connection

date_time_set failed for: 00/00/2000-00:00:00 - dow=0, yday=0

ConnectCOAPServer, trying to connect to coap.cardiospire.com

Calling modem_configure ......

LTE Link Connecting ...

LTE Link Connected!

Modem configuration complete, requesting IMEI# ....

Trying to resolve IP for endpoint ingest/352656109806508/lz ....

Call getaddrinfo for Hostname=coap.abcdefghijklmnop.com

ERROR: getaddrinfo failed -11

Failed to resolve server name

ConnectCOAPServer() failed

====

Is is possible the 1.3.2 firmware update failed?

Thanks,
John W.

Parents Reply Children
  • 0 in reply to johnwest

    Hi John, 

    the DevZone team and Nordic Semiconductor are currently in a summer vacation period, some delays in answers must be expected due to lower staffing during this period. We apologize for the inconvenience. 

    The "ERROR: getaddrinfo failed -11" translates to
    #define NRF_EAGAIN 11           /**< Resource unavailable, try again */
    What version of the nRF Connect SDK are you working on? And from what modem FW did you upgrade? Are you able to run e.g. AT client to confirm network connection and that SIM is working as it should? If you are using the nRF9160: nRF CoAP client sample please confirm connection towards a public CoAP server.
    Is is possible the 1.3.2 firmware update failed?

    From the AT command output you provided it looks like it succeeded. 

    Can you please provide a modem trace and full log output from the device?

    Thanks. 

    Kind regards,
    Øyvind

  • 0 in reply to johnwest

    Hello Øyvind,

    What AT command(s) should I run to verify the SIM is working properly?

    (Not an AT command expert regarding LTE-M)

    I've poked at the AT Command document - I've seen enough "not implemented" - so, I need to ask the above.

    Thanks,
    John

  • +1 in reply to johnwest

    John, 

    are you able to send AT commands in your application? If not, I was referring to the AT client sample that you will need to program your device with (overwriting the current application). 
    You can try with AT+CEREG?

    What SIM card are you using in your device? 

    From what modem FW did you upgrade? And did the application work before upgrading?

  • 0 in reply to johnwest

    Hello  Øyvind,

    We have a new board design - based on nRF9160 and nRF52840.  Most PCBA's are fine - work with LTE-M - no problem - those all are running 1.3.2.

    Yes - we have a serial port monitor where I can send AT Commands.

    I backed up to 1.3.1 since we're using AT&T (even though we can stream data to our COAP server with no issue with PCBA's that are working as designed w/1.3.2).

    App works fine on majority of PCBA's - we're just seeing this issue on a few.

    AT+CEREG just returns an ERROR.

    Thanks,
    John

  • 0 in reply to johnwest

    John, thanks for reporting back.

    johnwest said:
    +CEREG: 5,4

    4 – Unknown (for example, out of Evolved Terrestrial Radio Access Network (E-UTRAN) coverage)

    Please provide a modem trace.

    johnwest said:
    I backed up to 1.3.1 since we're using AT&T (even though we can stream data to our COAP server with no issue with PCBA's that are working as designed w/1.3.2).

    Do the failing devices work when you downgrade from 1.3.2 to 1.3.1?

    Kind regards,
    Øyvind

    • Related
    Terms of service