Hi,
Just received a new nRF9160-DK 0.9.0. After upgrading modem firmware to 1.2.0 and inserting a local SIM card, the modem connects nicely to NBIoT (as shown in the Link Monitor). Tested also UDP traffic to my server using Serial LTE Modem without problems. All applications compiled and downloaded via Segger 4.52
However, when downloading asset tracker I get hte below error. LED4 remains ON at the end.
[00:00:00.190,216] [0m<dbg> nrf9160_gps.init: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577[0m
[00:00:00.199,401] [0m<dbg> nrf9160_gps.init: COEX0 set: AT%XCOEX0=1,1,1570,1580[0m
[00:00:00.207,397] [0m<inf> asset_tracker: Asset tracker started[0m
[00:00:00.220,977] [0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100385247[0m
[00:00:00.230,621] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100385247/shadow[0m
[00:00:00.242,797] [0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100385247/shadow/get/accepted[0m
[00:00:00.254,821] [0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100385247/shadow/get/rejected[0m
[00:00:00.267,913] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100385247/shadow/update/delta[0m
[00:00:00.281,341] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100385247/shadow/update[0m
[00:00:00.293,731] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100385247/shadow/get[0m
[00:00:00.306,518] [0m<inf> asset_tracker: Connecting to LTE network. [0m
[00:00:00.313,598] [0m<inf> asset_tracker: This may take several minutes.[0m
[00:00:00.329,284] [0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=0,1,1,0[0m
[00:00:02.341,217] [0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2[0m
[00:00:03.981,750] [0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 1[0m
[00:00:03.990,447] [0m<inf> asset_tracker: Connected to LTE network[0m
[00:00:04.342,193] [0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0x165fca22[0m
[00:00:30.680,480] [0m<inf> aws_jobs: Subscribe: $aws/things/nrf-352656100385247/jobs/notify-next[0m
[00:00:30.690,917] [0m<inf> aws_jobs: Subscribe: $aws/things/nrf-352656100385247/jobs/$next/get/#[0m
[00:00:30.701,049] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_CONNACK[0m
[00:00:30.709,564] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 2[0m
[00:00:30.717,620] [0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED[0m
[00:00:30.726,135] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTED[0m
[00:00:30.732,482] [0m<dbg> nrf_cloud_transport.nct_cc_connect: nct_cc_connect[0m
[00:00:30.741,119] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 3[0m
[00:00:31.419,433] [0m<inf> aws_fota: subscribed to notify-next topic[0m
[00:00:31.426,513] [0m<inf> aws_jobs: Publish topic: $aws/things/nrf-352656100385247/jobs/$next/get[0m
[00:00:31.436,187] [0m<inf> aws_jobs: Publish payload {"clientToken": ""}[0m
[00:00:32.054,443] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 2114 result = 0[0m
[00:00:32.312,469] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 1234 result = 0[0m
[00:00:32.322,906] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 4[0m
[00:00:32.330,963] [0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 5678 opcode = 0 len = 0[0m
[00:00:32.341,796] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
[00:00:32.793,731] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 47301 result = 0[0m
[00:00:33.118,713] [0m<dbg> aws_fota.on_publish_evt: Received topic: $aws/things/nrf-352656100385247/jobs/$next/get/accepted[0m
[00:00:33.130,645] [0m<inf> aws_fota: Checking for an available job[0m
[00:00:33.137,542] [0m<dbg> aws_fota.get_job_execution: Got only one field: {"clientToken":"[0m
[00:00:33.146,575] [0m<inf> aws_fota: No queued jobs for this device[0m
[00:00:33.380,676] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 5678 result = 0[0m
[00:00:33.391,082] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
[00:00:33.672,760] [0m<dbg> aws_fota.on_publish_evt: Received topic: nrf-352656100385247/shadow/get/acceptedext/get/accepted[0m
[00:00:33.684,692] [0m<inf> aws_fota: received an unhandled MQTT publish event on topic: nrf-352656100385247/shadow/get/acceptedext/get/accepted[0m
[00:00:33.698,425] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBLISH: id = 15964 len = 44[0m
[00:00:33.709,289] [1;31m<err> nrf_cloud_codec: Deprecated state. Delete device from nrfCloud and update device with JITP certificates.[0m
[00:00:33.722,290] [1;31m<err> nrf_cloud_fsm: nrf_cloud_decode_requested_state Failed -134[0m
[00:00:33.731,140] [1;31m<err> nrf_cloud_fsm: Handler failed! state: 5, type: 3[0m
[00:00:33.739,044] [1;31m<err> nrf_cloud_transport: nct_input: failed -134[0m
Furthermore, I am not able to add the LTE board to nRF cloud, as the following message keeps showing up. Cannot reset the device either with a similar message.
I have followed the procedure to update the certificate (https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update) without improvement, although the update seems succesfull (already increased the CMD buffer size to 3000).
Manually deleting the certificates (AT%CMNG=3, ...) and re-uploading did not help either.
Your help is highly appreciated.
Thanks!
