• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 74 subscribers
  • Views 1677 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289883
Options

nrf9160 connect client error -111 ECONNREFUSED

AndriesTuinhof

Hello, we are trying to get software running on our custom board.

Last week we tried to test the software written on a development kit of the NRF9160 on to our custom board. The chip is able to connect with the network and gives message about this. but it does not connect to AWS itself. The same software does work on the DK. The software breaks at the connect_client function in aws_iot.c. the error code is -111 which apparently means that something is wrong with the certifcates. The custom board is programmed in the same except for that i was not able to upload the certficates through the AT client. Because the board gets programmed through j link. I tried new cerficates. But again it worked on the DK but not on the custom board. I tried testing everything twice with no avail.

The only thing that i can think of is that with the DK I followed the tutorial that said i had to program the certficates with the AT client. Which have done with the DK but not with the custom board.

I tried looking into the matter but no concrete answered if the certficates had to programmed through that or the certificates.h header file. 

So i was wondering what the official way this done because in a latter state it would be interesting to have the certicates uploaded easier.

 

Furthermore I appreciate any suggestions on this matter.

 

Parents
  • 0

    So in the end the problems was that the certifcates were not in the device. I was not able to do this through the 'certificates.h' file but i had to do it through the AT client. To make it work i had to adjust the pins of the uart that is being used by the code. This is because the custom board is using other pins. I was able to do this with an overlay. The correct way to fix this is with a custom board with its own devicetree from what i understand. But that is a lot of efferot for later. Futher i though i was not able to use the NRF Link monitor with the serial. But much later i found out that i had to turn of the checkbox 'show only supported devices'. With this i was able to quickly insert the certificates with the cerficate manager (only works if your follwing the instructions at the top correctly).

    Thanks for the help, now the next step is making the can work on the NRF9160 using the MCP2515 

Reply
  • 0

    So in the end the problems was that the certifcates were not in the device. I was not able to do this through the 'certificates.h' file but i had to do it through the AT client. To make it work i had to adjust the pins of the uart that is being used by the code. This is because the custom board is using other pins. I was able to do this with an overlay. The correct way to fix this is with a custom board with its own devicetree from what i understand. But that is a lot of efferot for later. Futher i though i was not able to use the NRF Link monitor with the serial. But much later i found out that i had to turn of the checkbox 'show only supported devices'. With this i was able to quickly insert the certificates with the cerficate manager (only works if your follwing the instructions at the top correctly).

    Thanks for the help, now the next step is making the can work on the NRF9160 using the MCP2515 

Children
No Data
Related
Terms of service