RE: nRF9160 Asset tracker constant reboot

JdK — Thu, 28 Nov 2019 14:54:42 GMT

Hi Håkon,

Creating an new certificate was the solution for the -95 error. However, the "cloud backend not found" error came back. I removed the whole "build_nrf9160_pca10090ns" folder and now I am able to use the nrfcloud.

Thanks for the support, I will mark your solution as verified answer.

RE: nRF9160 Asset tracker constant reboot

Håkon Alseth — Wed, 27 Nov 2019 15:26:29 GMT

Hi JdK,

An error of -95 normally indicate that the certificates for nrfcloud are missing.

Could you try generating new certificates and load them into your device? Here's a guide on that:

https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update

Kind regards,

Håkon

RE: nRF9160 Asset tracker constant reboot

JdK — Wed, 27 Nov 2019 13:45:53 GMT

Hi Hakon,

In the file prj.conf was CONFIG_NRF_CLOUD=y.

I deleted the whole ncs folder from my pc and installed the folder again according the Getting Started assistant step 2. Now the cloud backend not found error is disappeared.

But now I got the following errors:

2019-11-27T13:36:38.939Z INFO Modem port is opened
2019-11-27T13:36:38.947Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-11-27T13:36:38.966Z DEBUG modem << 00222333/shadow/get/rejected\x1B[0m\x0D\x0A
2019-11-27T13:36:38.969Z DEBUG modem << [00:00:00.358,337] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100222333/shadow/update/delta\x1B[0m\x0D\x0A
2019-11-27T13:36:38.971Z DEBUG modem << [00:00:00.371,032] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100222333/shadow/update\x1B[0m\x0D\x0A
2019-11-27T13:36:38.978Z DEBUG modem << [00:00:00.382,690] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100222333/shadow/get\x1B[0m\x0D\x0A
2019-11-27T13:36:38.997Z DEBUG modem << Connecting to LTE network. This may take several minutes.\x0D\x0A
2019-11-27T13:36:39.001Z DEBUG modem << [00:00:00.407,714] \x1B[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0\x1B[0m\x0D\x0A
2019-11-27T13:36:40.340Z DEBUG modem << +CEREG: 2,"FBF7","01398F0B",7,0,0,"11100000","11100000"\x0D
2019-11-27T13:36:40.349Z DEBUG modem << \x0A
2019-11-27T13:36:40.353Z DEBUG modem << [00:00:01.757,354] \x1B[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2\x1B[0m\x0D\x0A
2019-11-27T13:36:41.705Z DEBUG modem << +CEREG: 1,"FBF7","01398F0B",7,,,"11100000","11100000"\x0D\x0A
2019-11-27T13:36:41.713Z DEBUG modem << [00:00:03.121,978] \x1B[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 1\x1B[0m\x0D\x0A
2019-11-27T13:36:41.717Z DEBUG modem << Connected to LTE network\x0D\x0A
2019-11-27T13:36:41.881Z DEBUG modem << [00:00:03.288,787] \x1B[0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0xf4adc522\x1B[0m\x0D\x0A
2019-11-27T13:36:42.056Z DEBUG modem << cloud_connect failed: -95\x0D\x0A
2019-11-27T13:36:42.061Z DEBUG modem << LTE link disconnect\x0D\x0A
2019-11-27T13:36:42.114Z DEBUG modem << +CEREG: 0,"FBF7","01398F0B",7,0,0,"11100000","11100000"\x0D\x0A
2019-11-27T13:36:43.562Z DEBUG modem << Shutdown modem\x0D\x0A
2019-11-27T13:36:43.573Z DEBUG modem << ***** Booting Zephyr OS build v2.0.99-ncs1-rc1-764-gb687d5d02214 *****\x0D\x0A
2019-11-27T13:36:43.580Z DEBUG modem << [00:00:00.005,706] \x1B[0m<inf> mcuboot: Starting bootloader\x1B[0m\x0D\x0A

This is just one sequence, but this happened several times until I closed the device.

RE: nRF9160 Asset tracker constant reboot

Håkon Alseth — Wed, 27 Nov 2019 12:59:03 GMT

Hi,

That is an error that is shown when NRF_CLOUD is not enabled (CONFIG_NRF_CLOUD=y required in your prj.conf)

Have you done any alterations to asset_tracker, specifically in prj.conf? What revision of "nrf" are you running? Latest official one is "v1.1.0-branch" - try checking that one out.

Kind regards,

Håkon