Hi,
we are using nrf9160 custom board. Modem connected to LTE network but it is not connected to AWS cloud service. It's giving the -111 error, means connection refused. But with same esim card connected to AWS modem version of 1.2.3.
Hi,
we are using nrf9160 custom board. Modem connected to LTE network but it is not connected to AWS cloud service. It's giving the -111 error, means connection refused. But with same esim card connected to AWS modem version of 1.2.3.
Hi Jagadish,
The issue is similar to (+) nRF9160: AWS IoT (mqtt_connect, error: -111) - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com).
Dear Charlie,
i have looked into this post and we already add all certificates and configuration but still we are getting same error -111 in my custom borard,
when i try same code in nrf9160dk board its working fine but its not working in my custom board.
please let us know any solution ASAP.
Thank you
Hi Jagadish,
I assume you are playing NCS2.2.0 nRF9160: AWS IoT with your custom board. If yes, please check if you are using nRF9160 Rev2 and confirm you have updated the modem firmware to MFW v1.3.4.
Please share the full log printout and modem trace recording, so we would be able to help you analyse more details on the communication traffic.
Best regards,
Charlie
Hi charlie,
My custom board modem firmware version is 1.3.2. Yes, it is NCS2.2.0 nRF9160: AWSIoT.
And my nrf9160 development kit MFW is 1.3.2 Our aws_iot code is working in my development kit and i have another nrf9169 custom board with MFW is 1.3.2 in this also aws_iot code is working
But is not working our new nrf9160 custom board which is MFW is 1.3.2
I will try to upgrade the modem firmware also and i will update you the response.
please let me know is their any other reason why our new nrf9160 custom is not working when i use aws_iot.
thank you
Hi Charalie,
is their any document available to update modem firmware in nrf9160 custom board using J-tag or any other way
Thank you