MQTT Connect Error: -95 in nrf9160: AWS_IoT sample

[harisahmed]

Hi,

I have been trying to run nrf9160: AWS_IoT sample on Thingy91 but have been getting the following output in the serial terminal: 

I couldn't figure out what mqtt_connect, error: -95 actually means since it is not present in the following: https://github.com/intel/zephyr/blob/master/lib/libc/minimal/include/errno.h

Can someone please help me figure out what this error actually means?

Thank you.

[Øyvind]

Hello, 

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

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

Talking to one of the developers, this is most likely a certificate issue. Have you followed the AWS IoT documentation and especially the certificate chapter?

Kind regards,
Øyvind

 
 

[harisahmed]

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.

[Øyvind]

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

[harisahmed]

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.

[Øyvind]

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

[harisahmed]

I haven't modified the sample apart from what had been stated in the documentation. Didn't add anything from myself.

I was building for non-secure.

I will try to see the faulty instruction from the information you provided but in the meantime I had setup Cloud Client sample to communicate with the AWS IoT Core and it seems to be working fine for me.