Unable to connect to nRF Cloud - Error -128

Hello,

I'm trying to run the BLE LTE sample following this guide on an nRF9160 DK. I get the following error:

[00:00:04.942,413] <inf> nrf_cloud_info: Modem FW: mfw_nrf9160_1.3.7
[00:00:04.942,443] <inf> nrf_cloud_info: Protocol: MQTT
[00:00:04.942,474] <inf> nrf_cloud_info: Download protocol: HTTPS
[00:00:04.942,474] <inf> nrf_cloud_info: Sec tag: 16842753
[00:00:04.942,504] <inf> nrf_cloud_info: Host name: mqtt.nrfcloud.com
[00:00:05.147,460] <err> nrf_cloud_transport: Could not connect to nRF Cloud MQTT Broker mqtt.nrfcloud.com, port: 45858. err: -111

-----------------------------------

I found this post on the forum and followed the answer to onboard the device.

FYI: before following the guide, I followed nRF9160 DK getting started guide to try the nRF Cloud MQTT multi-service and successfully get the nRF9160 DK connected to the cloud via LTE and sending data.

Back to the onboard the device, I followed exactly everything in Onboarding a device without the nRF Cloud Provisioning Service. Get the certificate, successfully onboard the device with this message log:

Devices to be onboarded: 1

Onboarding API call result: 202 - Accepted

Response: {"bulkOpsRequestId":"<request id>"}

Fetching results for bulkOpsRequestId: <request id>

Waiting 5s...

Onboarding status: SUCCEEDED

-----------------------------------

I am able to see the new onboard device on nRF Cloud with the tag "unknown-pre-onboarding" sub type. But now, theh 9160 DK was not able to connect to the nRF Cloud at output this message. It is running the nRF Cloud MQTT multi-service sample, I did not modify anything. Here is the error message:

*** Using Zephyr OS v3.7.99-ca954a6216c9 ***
[00:00:00.257,385] <inf> main: nRF Cloud multi-service sample has started, version: 1.0.0, protocol: MQTT
[00:00:00.257,415] <inf> application: Reset reason: 0x10001
[00:00:00.257,659] <inf> cloud_connection: Enabling connectivity...
[00:00:00.533,355] <inf> cloud_connection: Setting up nRF Cloud library...
[00:00:00.542,144] <inf> nrf_cloud_info: Device ID: nrf-<my device id>
[00:00:00.542,602] <inf> nrf_cloud_info: IMEI: <number>
[00:00:00.543,029] <inf> nrf_cloud_info: Modem FW: mfw_nrf9160_1.3.7
[00:00:00.543,060] <inf> nrf_cloud_info: Protocol: MQTT
[00:00:00.543,121] <inf> nrf_cloud_info: Download protocol: HTTPS
[00:00:00.543,151] <inf> nrf_cloud_info: Sec tag: <sec tag>
[00:00:00.543,182] <inf> nrf_cloud_info: Host name: mqtt.nrfcloud.com
[00:00:00.640,136] <inf> nrf_cloud_credentials: Sec Tag:<sec tag>; CA: Yes, Client Cert: Yes, Private Key: Yes
[00:00:00.640,197] <inf> nrf_cloud_credentials: CA Size: 1791, AWS: Likely, CoAP: Likely
[00:00:00.640,228] <inf> cloud_connection: Waiting for network ready...
+CEREG: 2,"2CED","0D78F115",7
+CSCON: 1
+CGEV: ME PDN ACT 0,0
+CNEC_ESM: 50,0
%MDMEV: SEARCH STATUS 2
+CEREG: 5,"2CED","0D78F115",7,,,"00001010","00000011"
%XTIME: "8A","5240827195108A","01"
[00:00:04.543,365] <inf> cloud_connection: Network connectivity gained!
[00:00:05.543,579] <inf> cloud_connection: Network is ready
[00:00:05.543,579] <inf> cloud_connection: Connecting to nRF Cloud
[00:00:09.834,869] <err> nrf_cloud_transport: MQTT input error: -128
[00:00:09.834,960] <err> nrf_cloud_transport: Error disconnecting from cloud: -128
[00:00:09.834,991] <inf> cloud_connection: Disconnecting from nRF Cloud
[00:00:09.835,021] <err> cloud_connection: Could not connect to nRF Cloud

-----------------------------------

The LTE BLE gateway sample still displays the same error as noted above as well.

Any help is appreciated. It seems like I'm going in circles and not getting and good result.

Best regards,

Yun

Parents
  • Hi! It looks like you are on the right track. The latest error is -ECONNREFUSED, indicating that the sample has trouble getting internet. Unfortunately, this sample is no longer maintained and we cannot help you fix it. It's likely that some code change inside the sample is required. Could you elaborate your use case so we can try to find a sample that is better suited for you?

  • Hi, thank you for your response.

    For the use case, I have the nRF9160 DK connects to the nRF Cloud via LTE, I'm trying to remote control it by sending commands from the Cloud. Once the nRF9160 DK receives the command, it'll control the onboard 52840 SOC to do BLE advertising.

    The commands don't need to happen right away. For example, I'll have the 52840 SOC on a schedule to advertise every 5 hours for 10 minutes. The commands could be to change the interval to every 10 hours instead.

    I tried to started with the LTE BLE Gateway because it seems like the closest sample to my need. Eventually, I'll have the nRF9160DK controls the nRF52840 DK instead (via UART) so that I could add the nRF21540 EK shield on the nRF52840DK to amplify the transmit power and range. The setup is kind of redundant, but I'm trying to evaluate the potential of using these SOC and SIP on my own custom board.

Reply
  • Hi, thank you for your response.

    For the use case, I have the nRF9160 DK connects to the nRF Cloud via LTE, I'm trying to remote control it by sending commands from the Cloud. Once the nRF9160 DK receives the command, it'll control the onboard 52840 SOC to do BLE advertising.

    The commands don't need to happen right away. For example, I'll have the 52840 SOC on a schedule to advertise every 5 hours for 10 minutes. The commands could be to change the interval to every 10 hours instead.

    I tried to started with the LTE BLE Gateway because it seems like the closest sample to my need. Eventually, I'll have the nRF9160DK controls the nRF52840 DK instead (via UART) so that I could add the nRF21540 EK shield on the nRF52840DK to amplify the transmit power and range. The setup is kind of redundant, but I'm trying to evaluate the potential of using these SOC and SIP on my own custom board.

Children
No Data
Related