RE: Failed to add nrf9160 DK to nRF Cloud

helsing — Thu, 23 Jul 2020 12:17:26 GMT

Hi Dheeraj,

Sorry for the late reply. Many of our team members are on vacation, so please expect a longer delay from us than usual the following few weeks.

[quote user="Dheeraj Bansal"]1. AT Commands failed to respond on LTE Link Monitor.[/quote]

From this image it looks like something is not right. The commands should return "OK" after AT+CFUN=4. If "OK" is not returned, try resetting the board manually with SW2 while connected to Link Monitor? Do you see Zephyr booting? Try the procedure again and it might work. Let us know if you are still unable to see "OK" returned from the commands.

RE: Failed to add nrf9160 DK to nRF Cloud

Dheeraj — Fri, 17 Jul 2020 08:21:02 GMT

Hi Hakon,

We have given a try downloading a fresh copy of the pre-compiled version of the asset tracker from the above given link shared for nRF9160-DK PCA10090 and then programmed the same to our nRF9160-DK board.

https://www.nordicsemi.com/-/media/Software-and-other-downloads/Dev-Kits/nRF9160-DK/nRF9160-SiP-application-firmware/nrf9160dk_fw_2020-04-29_bc7ade8b.zip

We have followed the standard procedure as mentioned above for updating the firmware and device certificates, but still no luck.

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

FYI, We are using latest version of nRF Connect for Desktop v3.4.1

We faced the following issues as follows (Screenshot attached):

1. AT Commands failed to respond on LTE Link Monitor.

2. Error in Updating Certificates.

3. Device failed to add to the cloud.

4. Flashed the asset_tracker application (nrf9160dk_asset_tracker_dfu_2020-04-29_bc7ade8b.hex).

The following logs were observed.

*** Booting Zephyr OS build v2.3.0-rc1-ncs1-1-g7bd90a18c319  ***
[00:00:00.190,277] <dbg> nrf9160_gps.setup: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577
[00:00:00.199,035] <dbg> nrf9160_gps.setup: COEX0 set: AT%XCOEX0=1,1,1570,1580
[00:00:00.206,665] <inf> asset_tracker: Asset tracker started TimeStamp: 206
[00:00:00.214,141] <inf> watchdog: Watchdog timeout installed. Timeout: 10000
[00:00:00.221,649] <inf> watchdog: Watchdog started
[00:00:00.226,959] <inf> watchdog: Watchdog feed enabled. Timeout: 5000
[00:00:00.233,978] <inf> asset_tracker: main() TimeStamp: 233
[00:00:00.240,112] <inf> asset_tracker: main() TimeStamp: 240
[00:00:00.253,356] <dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100219636
[00:00:00.262,451] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100219636/shadow
[00:00:00.273,925] <dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100219636/shadow/get/accepted
[00:00:00.285,247] <dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100219636/shadow/get/rejected
[00:00:00.297,576] <dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100219636/shadow/update/delta
[00:00:00.310,272] <dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100219636/shadow/update
[00:00:00.321,929] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100219636/shadow/get
[00:00:00.333,892] <inf> asset_tracker: Connecting to LTE network.
[00:00:00.340,454] <inf> asset_tracker: This may take several minutes.
lte_lc_init_and_connect() called in lte_lc.c
w_lte_lc_init_and_connect() called in lte_lc.c
w_lte_lc_init() called in lte_lc.c
[00:00:00.358,642] <dbg> lte_lc.lte_lc_system_mode_set: Sending AT command to set system mode: AT%XSYSTEMMODE=1,0,1,0
lte_lc_edrx_req() is called in lte_lc.c
lte_lc_edrx_req() system mode: 4
lte_lc_edrx_req() enable err: 0
[00:00:00.406,799] <dbg> lte_lc.lte_lc_system_mode_set: Sending AT command to set system mode: AT%XSYSTEMMODE=1,0,1,0
+CEREG: 2,"8B3E","0A14590F",7,0,0,"11100000","11100000"
[00:00:01.991,333] <dbg> lte_lc.at_handler: +CEREG notification: +CEREG: 2,"8B3E","0A14590F",7,0,0,"11100000","11100000"

[00:00:02.002,960] <dbg> lte_lc.parse_psm_cfg: TAU: -1 sec, active time: -1 sec

+CSCON: 1
[00:00:02.045,806] <dbg> lte_lc.at_handler: +CSCON notification
+CEREG: 5,"8B3E","0A14590F",7,,,"11100000","11100000"
[00:00:04.091,735] <dbg> lte_lc.at_handler: +CEREG notification: +CEREG: 5,"8B3E","0A14590F",7,,,"11100000","11100000"

[00:00:04.103,210] <dbg> lte_lc.parse_psm_cfg: TAU: -1 sec, active time: -1 sec

[00:00:04.111,145] <inf> asset_tracker: Connected to LTE network.
[00:00:04.117,675] <inf> asset_tracker: Connecting to cloud, attempt 1 of 8
[00:00:04.125,091] <inf> asset_tracker: Cloud connection request sent.
[00:00:04.132,019] <inf> asset_tracker: Connection response timeout is set to 30 seconds.
+CEDRXP: 4,"1001","1001","0001"
[00:00:04.143,585] <dbg> lte_lc.at_handler: +CEDRXP notification
[00:00:04.150,085] <inf> asset_tracker: CLOUD_EVT_CONNECTING
[00:00:04.151,763] <dbg> lte_lc.parse_edrx: eDRX value: 163.83, PTW: 2.55
[00:00:04.329,284] <dbg> nrf_cloud_transport.nct_connect: IPv4 address: 52.1.58.201
[00:00:04.337,402] <dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect requesting persistent session
[00:00:04.465,606] <dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect failed -95
[00:00:04.474,090] <inf> asset_tracker: CLOUD_EVT_CONNECTING
[00:00:04.480,163] <err> asset_tracker: Failed to connect to cloud, error -8
[00:00:04.487,854] <err> asset_tracker: Ensure device has a valid CA and client certificate
[00:00:04.496,856] <err> asset_tracker: Device will reboot in 300 seconds
[00:00:04.504,364] <err> asset_tracker: LTE link disconnect
+CEREG: 0,"8B3E","0A14590F",7,0,0,"11100000","11100000"
[00:00:04.540,771] <dbg> lte_lc.at_handler: +CEREG notification: +CEREG: 0,"8B3E","0A14590F",7,0,0,"11100000","11100000"

[00:00:04.552,398] <dbg> lte_lc.parse_psm_cfg: TAU: -1 sec, active time: -1 sec

+CSCON: 0
[00:00:05.869,628] <dbg> lte_lc.at_handler: +CSCON notification
[00:00:07.315,856] <err> asset_tracker: Shutdown modem
[00:00:07.327,972] <err> at_cmd: AT socket recv failed with err -1
[00:00:07.334,991] <err> at_cmd: Unrecoverable reception error (err: 117), thread killed

Please find the above issue and give us some inputs to resolve this issue at your earliest.

RE: Failed to add nrf9160 DK to nRF Cloud

helsing — Thu, 16 Jul 2020 15:38:17 GMT

Hi Dheeraj

From a quick look at the log you provided looks like it is somehow related to Thingy:91(PCA20035). Perhaps you could you please try downloading a fresh copy of the precompiled version of the asset_tracker for nRF9160-DK and then program it to your nRF9160-DK?

nrf9160dk_fw_2020-04-29_bcade8b.zip

https://www.nordicsemi.com/-/media/Software-and-other-downloads/Dev-Kits/nRF9160-DK/nRF9160-SiP-application-firmware/nrf9160dk_fw_2020-04-29_bc7ade8b.zip

Best regards,

Håkon