nRF9160 thingy91 - AWS IOT (sample): Connect errors -11 and -10

Hello All,

This is from an app I had working 1 1/2 months ago - when I've tried recently to get it connected again, I haven't been successful.

The latest asset tracker appears to work find and posts data to the nRF Cloud.

I've seen previous posts - DNS is working - or appears to be ok.

I'm getting the following:

===

+CSCON: 0


RRC mode: Idle


Next connection retry in 30 seconds


AWS_IOT_EVT_CONNECTING


+CSCON: 1


RRC mode: Connected


E: getaddrinfo, error -11


E: client_broker_init, error: -10


AWS_IOT_EVT_CONNECTING


+CSCON: 0


RRC mode: Idle


Next connection retry in 30 seconds


AWS_IOT_EVT_CONNECTING


+CSCON: 1


RRC mode: Connected


E: getaddrinfo, error -11


E: client_broker_init, error: -10


AWS_IOT_EVT_CONNECTING


+CSCON: 0


RRC mode: Idle

====

I can reload the asset tracker and it'll work fine.  I'm running the AWS_IOT sample code.

Thanks in advance as to what -11 and -10 mean - it would appear getting the address fails - I tried to find error codes that make sense but not sure and wanted to ask in case something has changed in the last 1 1/2 months.  This app used to run without issue.

Thanks!
jwest

Parents
  • We will continue to support Segger Embedded Studio, but I recommend you look at the VS Code plugin as it better fits the nRF Connect SDK workflow.

    Didrik,

    From the way this thread reads - Nordic isn't supporting Segger Embedded Studio at all right now - if anyone claims to be using it - any issues are summarily ignored until that person keeps bringing the issue up.

    If we all don't start using VS Code - we don't get support - that's the actual, real message here.  

    If you are still actually supporting Segger Embedded Studio, how do I install the nRF Code Connect applet that helps with the SDK samples like what's in v5.60 in the newly released version 5.66?  I'll start a timer now and see how long it takes for this to be answered and works.  Yes, it'll have to work for the timer to stop.

    Regards,
    johnwest

Reply
  • We will continue to support Segger Embedded Studio, but I recommend you look at the VS Code plugin as it better fits the nRF Connect SDK workflow.

    Didrik,

    From the way this thread reads - Nordic isn't supporting Segger Embedded Studio at all right now - if anyone claims to be using it - any issues are summarily ignored until that person keeps bringing the issue up.

    If we all don't start using VS Code - we don't get support - that's the actual, real message here.  

    If you are still actually supporting Segger Embedded Studio, how do I install the nRF Code Connect applet that helps with the SDK samples like what's in v5.60 in the newly released version 5.66?  I'll start a timer now and see how long it takes for this to be answered and works.  Yes, it'll have to work for the timer to stop.

    Regards,
    johnwest

Children
  • johnwest said:
    how do I install the nRF Code Connect applet that helps with the SDK samples like what's in v5.60 in the newly released version 5.66? 

    The nRF Connec SDK has always used a custom version of Segger Embedded Studio (SES). The latest version of that "Nordic Edition" is v5.60.

    I expect that to be updated with NCS 1.8.0, currently scheduled for the end of this year.

    This is the way it has always been with NCS.

    If you have any problems with SES, we will do our best to help you.

    Speaking of which, I am not quite sure what you mean the current problem with SES is.

Related