MQTT Connect Error: -95 in nrf9160: AWS_IoT sample

Hello, 

according to this errno.h, error -95 means: 

Thank you for your response.

I am sorry but in the errno.h file I linked the following is defined:

#define EOPNOTSUPP 45      /* Operation not supported on socket */

Which is different from what you wrote:

#define EOPNOTSUPP 95 /* Operation not supported on transport endpoint */

Am I looking at the wrong errno.h file?

Yes, I have followed the documentation and the certificates chapter but possibly could have made a mistake. I will try to see if I have skipped some step or did something wrong.

Thank you.

Sorry for the confusion. 

A project that has the following in prj.conf

CONFIG_NEWLIB_LIBC=y

Will use the errno table according to newlib, see this table.

While the errno table you are referring to is the C minimal library in Zephyr. Read more here

harisahmed said:

I will try to see if I have skipped some step or did something wrong.

 Yes, please verify your steps and let me know how it goes!

Kind regards,
Øyvind

Hello,

So after retracing my steps and the AWS_IoT documentation, I was able to establish a connection with AWS_IoT core but there was a problem. My nrf9160dk was just resetting again and again and I could see the following output on the console: 

Can you please help me figure out why this is happening and how can I debug this issue?

Thank you.

Have you edited the sample in any way, other than what the documentation states? Added anything to the sample? 

The GNU Arm Embedded Toolchain includes a tool (arm-none-eabi-addr2line.exe) which you can use to find the faulting instruction on address 0x0002d65c

arm-none-eabi-addr2line.exe -e zephyr.elf 0x0002d65c

Where zephyr.elf is found under aws_iot\build\zephyr\zephyr.elf

You may also find some answers here.

Are you building for secure or non-secure?

Kind regards,
Øyvind