Unable to connect to Cloud using Asset Tracker on nRF9160 DK

[mourad]

Hello,

I have an nRF9160 DK revision 1 with ibasis esim.

I wanted to  connect to cloud using the precompiled asset tracker lte files in your website :https://www.nordicsemi.com/Products/Development-hardware/nRF9160-DK/Download?lang=en#infotabs

I tried the nRF9160-DK application and modem firmware latest version (2022-06-02_880c82db) without any success ,the board keep resetting and all leds are off.

I switched to older version( 2020-04-29_bc7ade8b )like in this video : https://www.youtube.com/watch?v=rMvW3HXLErk&ab_channel=NordicSemiconductor

this time Led 3 toggled first then it switches off and Led 4 is on and got this error :nrf_cloud_transport: nct_input: failed -134

this is lte link monitor:

and this is the log file:

2022-08-03T15:45:05.044Z DEBUG Application data folder: /home/mourad/.config/nrfconnect/pc-nrfconnect-linkmonitor
2022-08-03T15:45:05.144Z INFO Using nrf-device-lib-js version: 0.4.11
2022-08-03T15:45:05.145Z INFO Using nrf-device-lib version: 0.11.8
2022-08-03T15:45:05.145Z INFO Using nrfjprog DLL version: 10.15.4
2022-08-03T15:45:05.146Z INFO Using JLink version: JLink_V7.68c
2022-08-03T15:45:05.170Z DEBUG App pc-nrfconnect-linkmonitor v2.0.1 official
2022-08-03T15:45:05.171Z DEBUG App path: /home/mourad/.nrfconnect-apps/node_modules/pc-nrfconnect-linkmonitor
2022-08-03T15:45:05.171Z DEBUG nRFConnect 3.11.1, required by the app is (^3.8.0)
2022-08-03T15:45:05.171Z DEBUG nRFConnect path: /tmp/.mount_nrfcon44k7vm/resources/app.asar
2022-08-03T15:45:05.171Z DEBUG HomeDir: /home/mourad
2022-08-03T15:45:05.172Z DEBUG TmpDir: /tmp
2022-08-03T15:45:05.175Z INFO Installed JLink version does not match the provided version (V7.58b)
2022-08-03T15:45:12.009Z INFO Modem port is opened
2022-08-03T15:45:12.028Z DEBUG modem << *** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
2022-08-03T15:45:17.840Z DEBUG modem << [00:00:00.006,866] [0m<inf> mcuboot: Starting bootloader[0m*** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
2022-08-03T15:45:17.854Z DEBUG modem << [00:00:00.006,805] [0m<inf> mcuboot: Starting bootloader[0m
2022-08-03T15:45:17.868Z DEBUG modem << [00:00:00.015,106] [0m<inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3[0m
2022-08-03T15:45:17.884Z DEBUG modem << [00:00:00.028,228] [0m<inf> mcuboot: Boot source: none[0m
2022-08-03T15:45:17.890Z DEBUG modem << [00:00:00.035,369] [0m<inf> mcuboot: Swap type: none[0m
2022-08-03T15:45:18.203Z DEBUG modem << [00:00:00.436,340] [0m<inf> mcuboot: Bootloader chainload address offset: 0x10000[0m
2022-08-03T15:45:18.217Z DEBUG modem << [00:00:00.444,091] [0m<inf> mcuboot: Jumping to the first image slot[0m
2022-08-03T15:45:18.224Z DEBUG modem << *** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
2022-08-03T15:45:18.236Z DEBUG modem << Flash regionsDomainPermissions
2022-08-03T15:45:18.243Z DEBUG modem << 00 02 0x00000 0x18000 Securerwxl
2022-08-03T15:45:18.250Z DEBUG modem << 03 31 0x18000 0x100000 Non-Securerwxl
2022-08-03T15:45:18.260Z DEBUG modem << Non-secure callable region 0 placed in flash region 2 with size 32.
2022-08-03T15:45:18.404Z DEBUG modem << SRAM regionDomainPermissions
2022-08-03T15:45:18.416Z DEBUG modem << 00 07 0x00000 0x10000 Securerwxl
2022-08-03T15:45:18.421Z DEBUG modem << 08 31 0x10000 0x40000 Non-Securerwxl
2022-08-03T15:45:18.425Z DEBUG modem << PeripheralDomainStatus
2022-08-03T15:45:18.429Z DEBUG modem << 00 NRF_P0               Non-SecureOK
2022-08-03T15:45:18.432Z DEBUG modem << 01 NRF_CLOCK            Non-SecureOK
2022-08-03T15:45:18.440Z DEBUG modem << 02 NRF_RTC0             Non-SecureOK
2022-08-03T15:45:18.446Z DEBUG modem << 03 NRF_RTC1             Non-SecureOK
2022-08-03T15:45:18.448Z DEBUG modem << 04 NRF_NVMC             Non-SecureOK
2022-08-03T15:45:18.453Z DEBUG modem << 05 NRF_UARTE1           Non-SecureOK
2022-08-03T15:45:18.467Z DEBUG modem << 06 NRF_UARTE2           SecureSKIP
2022-08-03T15:45:18.471Z DEBUG modem << 07 NRF_TWIM2            Non-SecureOK
2022-08-03T15:45:18.474Z DEBUG modem << 08 NRF_SPIM3            Non-SecureOK
2022-08-03T15:45:18.480Z DEBUG modem << 09 NRF_TIMER0           Non-SecureOK
2022-08-03T15:45:18.482Z DEBUG modem << 10 NRF_TIMER1           Non-SecureOK
2022-08-03T15:45:18.485Z DEBUG modem << 11 NRF_TIMER2           Non-SecureOK
2022-08-03T15:45:18.488Z DEBUG modem << 12 NRF_SAADC            Non-SecureOK
2022-08-03T15:45:18.501Z DEBUG modem << 13 NRF_PWM0             Non-SecureOK
2022-08-03T15:45:18.504Z DEBUG modem << 14 NRF_PWM1             Non-SecureOK
2022-08-03T15:45:18.507Z DEBUG modem << 15 NRF_PWM2             Non-SecureOK
2022-08-03T15:45:18.511Z DEBUG modem << 16 NRF_PWM3             Non-SecureOK
2022-08-03T15:45:18.512Z DEBUG modem << 17 NRF_WDT              Non-SecureOK
2022-08-03T15:45:18.513Z DEBUG modem << 18 NRF_IPC              Non-SecureOK
2022-08-03T15:45:18.514Z DEBUG modem << 19 NRF_VMC              Non-SecureOK
2022-08-03T15:45:18.517Z DEBUG modem << 20 NRF_FPU              Non-SecureOK
2022-08-03T15:45:18.518Z DEBUG modem << 21 NRF_EGU1             Non-SecureOK
2022-08-03T15:45:18.526Z DEBUG modem << 22 NRF_EGU2             Non-SecureOK
2022-08-03T15:45:18.529Z DEBUG modem << 23 NRF_DPPIC            Non-SecureOK
2022-08-03T15:45:18.531Z DEBUG modem << 24 NRF_GPIOTE1          Non-SecureOK
2022-08-03T15:45:18.535Z DEBUG modem << 25 NRF_REGULATORS       Non-SecureOK
2022-08-03T15:45:18.537Z DEBUG modem << SPM: NS image at 0x1c200
2022-08-03T15:45:18.539Z DEBUG modem << SPM: NS MSP at 0x2002f080
2022-08-03T15:45:18.542Z DEBUG modem << SPM: NS reset vector at 0x252f1
2022-08-03T15:45:18.545Z DEBUG modem << SPM: prepare to jump to Non-Secure image.
2022-08-03T15:45:18.712Z DEBUG modem << *** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
2022-08-03T15:45:18.721Z DEBUG modem << [00:00:00.192,077] [0m<dbg> nrf9160_gps.setup: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577[0m
2022-08-03T15:45:18.731Z DEBUG modem << [00:00:00.201,019] [0m<dbg> nrf9160_gps.setup: COEX0 set: AT%XCOEX0=1,1,1570,1580[0m
2022-08-03T15:45:18.735Z DEBUG modem << [00:00:00.208,801] [0m<inf> asset_tracker: Asset tracker started[0m
2022-08-03T15:45:18.752Z DEBUG modem << [00:00:00.222,198] [0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100050676[0m
2022-08-03T15:45:18.764Z DEBUG modem << [00:00:00.231,506] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100050676/shadow[0m
2022-08-03T15:45:18.782Z DEBUG modem << [00:00:00.243,255] [0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100050676/shadow/get/accepted[0m
2022-08-03T15:45:18.788Z DEBUG modem << [00:00:00.254,852] [0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100050676/shadow/get/rejected[0m
2022-08-03T15:45:18.801Z DEBUG modem << [00:00:00.267,486] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100050676/shadow/update/delta[0m
2022-08-03T15:45:18.813Z DEBUG modem << [00:00:00.280,487] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100050676/shadow/update[0m
2022-08-03T15:45:18.831Z DEBUG modem << [00:00:00.292,419] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100050676/shadow/get[0m
2022-08-03T15:45:18.838Z DEBUG modem << [00:00:00.304,687] [0m<inf> asset_tracker: Connecting to LTE network. [0m
2022-08-03T15:45:18.840Z DEBUG modem << [00:00:00.311,492] [0m<inf> asset_tracker: This may take several minutes.[0m
2022-08-03T15:45:18.855Z DEBUG modem << [00:00:00.326,477] [0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0[0m
2022-08-03T15:45:20.602Z DEBUG modem << +CEREG: 2,"C505","01720B04",7,0,0,"11100000","11100000"
2022-08-03T15:45:20.621Z DEBUG modem << [00:00:02.082,275] [0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2[0m
2022-08-03T15:45:21.967Z DEBUG modem << +CEREG: 5,"C505","01720B04",7,,,"11100000","11100000"
2022-08-03T15:45:21.988Z DEBUG modem << [00:00:03.447,357] [0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 5[0m
2022-08-03T15:45:21.991Z DEBUG modem << [00:00:03.455,780] [0m<inf> asset_tracker: Connected to LTE network[0m
2022-08-03T15:45:22.080Z DEBUG modem << [00:00:03.551,849] [0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0x1791e803[0m
2022-08-03T15:45:22.091Z DEBUG modem << [00:00:03.559,936] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect requesting persistent session[0m
2022-08-03T15:45:25.266Z DEBUG modem << [00:00:06.735,534] [0m<dbg> aws_fota.aws_fota_mqtt_evt_handler: Previous session valid; skipping FOTA subscriptions[0m
2022-08-03T15:45:25.278Z DEBUG modem << [00:00:06.746,398] [0m<inf> aws_fota: Created notify_next_topic $aws/things/nrf-352656100050676/jobs/notify-next[0m
2022-08-03T15:45:25.287Z DEBUG modem << [00:00:06.757,049] [0m<inf> aws_fota: Created get_topic $aws/things/nrf-352656100050676/jobs/$next/get/#[0m
2022-08-03T15:45:25.299Z DEBUG modem << [00:00:06.766,876] [0m<inf> aws_fota: previously subscribed to notify-next topic[0m
2022-08-03T15:45:25.304Z DEBUG modem << [00:00:06.774,688] [0m<inf> aws_jobs: Publish topic: $aws/things/nrf-352656100050676/jobs/$next/get[0m
2022-08-03T15:45:25.315Z DEBUG modem << [00:00:06.784,088] [0m<inf> aws_jobs: Publish payload {"clientToken": ""}[0m
2022-08-03T15:45:25.321Z DEBUG modem << [00:00:06.792,877] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_CONNACK[0m
2022-08-03T15:45:25.336Z DEBUG modem << [00:00:06.801,116] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 2[0m
2022-08-03T15:45:25.341Z DEBUG modem << [00:00:06.808,959] [0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED[0m
2022-08-03T15:45:25.353Z DEBUG modem << [00:00:06.817,291] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTED[0m
2022-08-03T15:45:25.357Z DEBUG modem << [00:00:06.823,455] [0m<inf> asset_tracker: Persistent Sessions = 1[0m
2022-08-03T15:45:25.362Z DEBUG modem << [00:00:06.829,925] [0m<dbg> nrf_cloud_fsm.connection_handler: Previous session valid; skipping nct_cc_connect()[0m
2022-08-03T15:45:25.383Z DEBUG modem << [00:00:06.840,393] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 4[0m
2022-08-03T15:45:25.386Z DEBUG modem << [00:00:06.848,175] [0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 5678 opcode = 0 len = 0[0m
2022-08-03T15:45:25.392Z DEBUG modem << [00:00:06.859,100] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
2022-08-03T15:45:25.687Z DEBUG modem << [00:00:07.157,226] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 25926 result = 0[0m
2022-08-03T15:45:25.699Z DEBUG modem << [00:00:07.167,602] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 5678 result = 0[0m
2022-08-03T15:45:25.706Z DEBUG modem << [00:00:07.177,795] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
2022-08-03T15:45:25.720Z DEBUG modem << [00:00:07.185,791] [0m<dbg> aws_fota.on_publish_evt: Received topic: $aws/things/nrf-352656100050676/jobs/$next/get/accepted[0m
2022-08-03T15:45:25.737Z DEBUG modem << [00:00:07.197,448] [0m<inf> aws_fota: Checking for an available job[0m
2022-08-03T15:45:25.740Z DEBUG modem << [00:00:07.204,101] [0m<dbg> aws_fota.get_job_execution: Job doc: {"clientToken":"","timestamp":1659541525}[0m
2022-08-03T15:45:25.754Z DEBUG modem << [00:00:07.214,324] [0m<dbg> aws_fota.get_job_execution: Got only one field[0m
2022-08-03T15:45:25.769Z DEBUG modem << [00:00:07.221,466] [0m<inf> aws_fota: No queued jobs for this device[0m
2022-08-03T15:45:25.820Z DEBUG modem << [00:00:07.289,489] [0m<dbg> aws_fota.on_publish_evt: Received topic: nrf-352656100050676/shadow/get/accepted[0m
2022-08-03T15:45:25.833Z DEBUG modem << [00:00:07.299,713] [0m<dbg> aws_fota.on_publish_evt: received an unhandled MQTT publish event on topic: nrf-352656100050676/shadow/get/accepted[0m
2022-08-03T15:45:25.852Z DEBUG modem << [00:00:07.313,018] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBLISH: id = 15404 len = 209[0m
2022-08-03T15:45:25.867Z DEBUG modem << [00:00:07.324,127] [1;31m<err> nrf_cloud_codec: Deprecated state. Delete device from nrfCloud and update device with JITP certificates.[0m
2022-08-03T15:45:25.870Z DEBUG modem << [00:00:07.336,975] [1;31m<err> nrf_cloud_fsm: nrf_cloud_decode_requested_state Failed -134[0m
2022-08-03T15:45:25.873Z DEBUG modem << [00:00:07.345,581] [1;31m<err> nrf_cloud_fsm: Handler failed! state: 5, type: 3[0m
2022-08-03T15:45:25.886Z DEBUG modem << [00:00:07.353,149] [1;31m<err> nrf_cloud_transport: nct_input: failed -134[0m

[Albrecht Markus Schellenberger]

Hello Mourad, 

I tried the nRF9160-DK application and modem firmware latest version (2022-06-02_880c82db) without any success ,the board keep resetting and all leds are off.

From which folder in the application and modem firmware package did you pick the Asset Tracker v2 image and which one of the available did you choose? 

this time Led 3 toggled first then it switches off and Led 4 is on and got this error :nrf_cloud_transport: nct_input: failed -134

I’m not quite sure if I can read that out of your description: but have you managed to add your DK to the nRF Cloud, as described in this chapter? Point 8 states that the device only can be added when the Asset Tracker v2 firmware is in provisioning state. 

Regards, 

Markus 

[mourad]

Hi Albrecht,

for the latest version I uploaded this file "img_app_bl/nrf9160dk_asset_tracker_v2_ltem_2022-06-02_880c82db.hex"

with the modem firmware 1.3.2.( I did some research and I found that my devise is V0.8.2 so I can't upload the modem firmware 1.3.2, so I'm stuck with 1.2.x).

when i try register the the device in nrf cloud with the old firmware :"images_full/nrf9160dk_asset_tracker_ltem_2020-04-29_bc7ade8b.hex" and modem firmware 1.2.0 

I got this error from the cloud and the log file above from the LTE monitor

 

[Albrecht Markus Schellenberger]

Thanks a lot for the feedback, Mourad! 

mourad said:

when i try register the the device in nrf cloud with the old firmware :"images_full/nrf9160dk_asset_tracker_ltem_2020-04-29_bc7ade8b.hex" and modem firmware 1.2.0 

Although you have to remain on mfw 1.2.x, I still recommend you to use the latest Asset Tracker firmware image, which is /img_app_bl/nrf9160dk_asset_tracker_v2_ltem_2022-06-02_880c82db.hex. Additionally, you should upgrade to mfw v1.2.3 or v1.2.7. 

mourad said:

I got this error from the cloud and the log file above from the LTE monitor

Can you confirm that the UE is in provisioning state, as described in point 8, when you try to add the device to your nRF Cloud account? 

"Wait up to three minutes for the device to find the cellular network and connect to the nRF Cloud server.

At this stage, the device is provisioned on nRF Cloud, but not yet associated with your nRF Cloud account. When the DK has connected, the LED3 double pulse blinks to indicate that user association is required and you can move to the next step."

Cheers, 

Markus 

[mourad]

Thanks for your answer Albrecht,

I uploaded the mfw to 1.2.7 and the Asset Tracker firmware image /img_app_bl/nrf9160dk_asset_tracker_v2_ltem_2022-06-02_880c82db.hex. 

I got this warning when i try to upload the Asset Tracker firmware

after uploading I got only led 1 toggling and this is the log file

2022-08-04T09:03:21.722Z DEBUG modem << *** Booting Zephyr OS build v3.0.99-ncs1  ***
2022-08-04T09:03:21.724Z DEBUG modem << Attempting to boot slot 0.
2022-08-04T09:03:21.735Z DEBUG modem << Attempting to boot from address 0x8200.
2022-08-04T09:03:21.738Z DEBUG modem << Verifying signature against key 0.
2022-08-04T09:03:21.740Z DEBUG modem << Hash: 0xc5...87
2022-08-04T09:03:21.759Z DEBUG modem << Firmware signature verified.
2022-08-04T09:03:21.773Z DEBUG modem << Firmware version 1
2022-08-04T09:03:21.776Z DEBUG modem << Booting (0x8200).
2022-08-04T09:03:22.018Z DEBUG modem << *** Booting Zephyr OS build v3.0.99-ncs1  ***
2022-08-04T09:03:22.020Z DEBUG modem << I: Starting bootloader
2022-08-04T09:03:22.034Z DEBUG modem << I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2022-08-04T09:03:22.039Z DEBUG modem << I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2022-08-04T09:03:22.052Z DEBUG modem << I: Boot source: none
2022-08-04T09:03:22.055Z DEBUG modem << I: Swap type: none
2022-08-04T09:03:22.059Z DEBUG modem << I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2022-08-04T09:03:22.078Z DEBUG modem << I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2022-08-04T09:03:22.082Z DEBUG modem << I: Boot source: none
2022-08-04T09:03:22.085Z DEBUG modem << I: Swap type: none
2022-08-04T09:03:22.139Z DEBUG modem << I: Bootloader chainload address offset: 0x28000
2022-08-04T09:03:22.156Z DEBUG modem << I: Jumping to the first image slot
2022-08-04T09:03:22.859Z DEBUG modem << *** Booting Zephyr OS build v3.0.99-ncs1  ***
2022-08-04T09:03:22.875Z DEBUG modem << [00:00:00.525,512] [0m<inf> app_event_manager: APP_EVT_START[0m
2022-08-04T09:03:22.889Z DEBUG modem << [00:00:00.526,641] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2022-08-04T09:03:22.907Z DEBUG modem << [00:00:00.530,853] [1;31m<err> modem_module: lte_lc_modem_events_enable failed, error: -14[0m
2022-08-04T09:03:22.924Z DEBUG modem << [00:00:00.530,853] [1;31m<err> modem_module: Failed setting up the modem, error: -14[0m
2022-08-04T09:03:22.928Z DEBUG modem << [00:00:00.530,944] [0m<inf> app_event_manager: MODEM_EVT_ERROR - Error code -14[0m
2022-08-04T09:03:22.943Z DEBUG modem << [00:00:00.531,616] [0m<inf> app_event_manager: UTIL_EVT_SHUTDOWN_REQUEST[0m
2022-08-04T09:03:22.946Z DEBUG modem << [00:00:00.532,196] [0m<inf> app_event_manager: UI_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:22.948Z DEBUG modem << [00:00:00.532,348] [1;33m<wrn> modules_common: Module "ui" shutdown registered[0m
2022-08-04T09:03:22.964Z DEBUG modem << [00:00:00.532,470] [0m<inf> app_event_manager: GNSS_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:22.966Z DEBUG modem << [00:00:00.532,684] [1;33m<wrn> modules_common: Module "gnss" shutdown registered[0m
2022-08-04T09:03:22.968Z DEBUG modem << [00:00:00.533,264] [0m<inf> app_event_manager: APP_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:22.983Z DEBUG modem << [00:00:00.533,416] [1;33m<wrn> modules_common: Module "app" shutdown registered[0m
2022-08-04T09:03:22.985Z DEBUG modem << [00:00:00.534,179] [0m<inf> app_event_manager: CLOUD_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:23.000Z DEBUG modem << [00:00:00.534,515] [1;33m<wrn> modules_common: Module "cloud" shutdown registered[0m
2022-08-04T09:03:23.003Z DEBUG modem << [00:00:00.534,851] [0m<inf> app_event_manager: SENSOR_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:23.006Z DEBUG modem << [00:00:00.535,003] [1;33m<wrn> modules_common: Module "sensor" shutdown registered[0m
2022-08-04T09:03:23.049Z DEBUG modem << +CEREG: 0,"FFFE","FFFFFFFF",7,0,0,"11100000","11100000"
2022-08-04T09:03:24.048Z DEBUG modem << [00:00:00.707,183] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2022-08-04T09:03:24.055Z DEBUG modem << [00:00:00.715,606] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2022-08-04T09:03:24.069Z DEBUG modem << [00:00:00.715,850] [1;33m<wrn> modules_common: data: Message could not be enqueued, error code: -35[0m
2022-08-04T09:03:24.072Z DEBUG modem << [00:00:00.715,850] [1;31m<err> data_module: Message could not be enqueued[0m
2022-08-04T09:03:24.089Z DEBUG modem << [00:00:00.716,278] [0m<inf> app_event_manager: DATA_EVT_ERROR - Error code -35[0m
2022-08-04T09:03:24.095Z DEBUG modem << [00:00:00.925,231] [0m<inf> app_event_manager: MODEM_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:24.111Z DEBUG modem << [00:00:00.925,567] [1;33m<wrn> modules_common: Module "modem" shutdown registered[0m
2022-08-04T09:03:52.870Z DEBUG modem << [00:00:30.531,372] [1;31m<err> util_module: Rebooting![0m
2022-08-04T09:03:52.875Z DEBUG modem << *** Booting Zephyr OS build v3.0.99-ncs1  ***
2022-08-04T09:03:52.886Z DEBUG modem << Attempting to boot slot 0.
2022-08-04T09:03:52.889Z DEBUG modem << Attempting to boot from address 0x8200.
2022-08-04T09:03:52.891Z DEBUG modem << Verifying signature against key 0.
2022-08-04T09:03:52.895Z DEBUG modem << Hash: 0xc5...87
2022-08-04T09:03:52.917Z DEBUG modem << Firmware signature verified.
2022-08-04T09:03:52.919Z DEBUG modem << Firmware version 1
2022-08-04T09:03:52.926Z DEBUG modem << Booting (0x8200).
2022-08-04T09:03:53.171Z DEBUG modem << *** Booting Zephyr OS build v3.0.99-ncs1  ***
2022-08-04T09:03:53.173Z DEBUG modem << I: Starting bootloader
2022-08-04T09:03:53.193Z DEBUG modem << I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2022-08-04T09:03:53.195Z DEBUG modem << I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2022-08-04T09:03:53.198Z DEBUG modem << I: Boot source: none
2022-08-04T09:03:53.213Z DEBUG modem << I: Swap type: none
2022-08-04T09:03:53.215Z DEBUG modem << I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2022-08-04T09:03:53.231Z DEBUG modem << I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2022-08-04T09:03:53.234Z DEBUG modem << I: Boot source: none
2022-08-04T09:03:53.236Z DEBUG modem << I: Swap type: none
2022-08-04T09:03:53.291Z DEBUG modem << I: Bootloader chainload address offset: 0x28000
2022-08-04T09:03:53.305Z DEBUG modem << I: Jumping to the first image slot
2022-08-04T09:03:54.012Z DEBUG modem << *** Booting Zephyr OS build v3.0.99-ncs1  ***
2022-08-04T09:03:54.038Z DEBUG modem << [00:00:00.525,482] [0m<inf> app_event_manager: APP_EVT_START[0m
2022-08-04T09:03:54.041Z DEBUG modem << [00:00:00.526,611] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2022-08-04T09:03:54.054Z DEBUG modem << [00:00:00.530,822] [1;31m<err> modem_module: lte_lc_modem_events_enable failed, error: -14[0m
2022-08-04T09:03:54.057Z DEBUG modem << [00:00:00.530,822] [1;31m<err> modem_module: Failed setting up the modem, error: -14[0m
2022-08-04T09:03:54.072Z DEBUG modem << [00:00:00.530,914] [0m<inf> app_event_manager: MODEM_EVT_ERROR - Error code -14[0m
2022-08-04T09:03:54.078Z DEBUG modem << [00:00:00.531,585] [0m<inf> app_event_manager: UTIL_EVT_SHUTDOWN_REQUEST[0m
2022-08-04T09:03:54.082Z DEBUG modem << [00:00:00.532,165] [0m<inf> app_event_manager: UI_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:54.100Z DEBUG modem << [00:00:00.532,318] [1;33m<wrn> modules_common: Module "ui" shutdown registered[0m
2022-08-04T09:03:54.117Z DEBUG modem << [00:00:00.532,440] [0m<inf> app_event_manager: GNSS_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:54.119Z DEBUG modem << [00:00:00.532,653] [1;33m<wrn> modules_common: Module "gnss" shutdown registered[0m
2022-08-04T09:03:54.121Z DEBUG modem << [00:00:00.533,233] [0m<inf> app_event_manager: APP_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:54.140Z DEBUG modem << [00:00:00.533,386] [1;33m<wrn> modules_common: Module "app" shutdown registered[0m
2022-08-04T09:03:54.144Z DEBUG modem << [00:00:00.534,149] [0m<inf> app_event_manager: CLOUD_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:54.148Z DEBUG modem << [00:00:00.534,484] [1;33m<wrn> modules_common: Module "cloud" shutdown registered[0m
2022-08-04T09:03:54.166Z DEBUG modem << [00:00:00.534,820] [0m<inf> app_event_manager: SENSOR_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:54.168Z DEBUG modem << [00:00:00.534,973] [1;33m<wrn> modules_common: Module "sensor" shutdown registered[0m
2022-08-04T09:03:54.202Z DEBUG modem << +CEREG: 0,"FFFE","FFFFFFFF",7,0,0,"11100000","11100000"
2022-08-04T09:03:55.201Z DEBUG modem << [00:00:00.707,153] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2022-08-04T09:03:55.210Z DEBUG modem << [00:00:00.715,576] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2022-08-04T09:03:55.227Z DEBUG modem << [00:00:00.715,820] [1;33m<wrn> modules_common: data: Message could not be enqueued, error code: -35[0m
2022-08-04T09:03:55.251Z DEBUG modem << [00:00:00.715,820] [1;31m<err> data_module: Message could not be enqueued[0m
2022-08-04T09:03:55.285Z DEBUG modem << [00:00:00.716,247] [0m<inf> app_event_manager: DATA_EVT_ERROR - Error code -35[0m
2022-08-04T09:03:55.287Z DEBUG modem << [00:00:00.925,201] [0m<inf> app_event_manager: MODEM_EVT_SHUTDOWN_READY[0m
2022-08-04T09:03:55.290Z DEBUG modem << [00:00:00.925,537] [1;33m<wrn> modules_common: Module "modem" shutdown registered[0m

and it's not in provisioning state

[mourad]

I found that my device has a certificate when I send the command AT+CMNG=1

so I deleted all the certificates with AT+CMNG=3,... and re-uploaded an other certificate and now i got this error while running the old Asset Tracker firmware

2022-08-04T11:28:11.851Z DEBUG modem << [00:00:04.086,822] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect requesting persistent session[0m
2022-08-04T11:28:15.893Z DEBUG modem << [00:00:08.143,798] [1;31m<err> asset_tracker: Socket error: POLLHUP

for the latest firmware /img_app_bl/nrf9160dk_asset_tracker_v2_ltem_2022-06-02_880c82db.hex. It still the same problem 

2022-08-04T11:19:28.315Z DEBUG modem << *** Booting Zephyr OS build v3.0.99-ncs1  ***
2022-08-04T11:19:28.336Z DEBUG modem << [00:00:00.525,512] [0m<inf> app_event_manager: APP_EVT_START[0m
2022-08-04T11:19:28.341Z DEBUG modem << [00:00:00.526,641] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2022-08-04T11:19:28.360Z DEBUG modem << [00:00:00.530,853] [1;31m<err> modem_module: lte_lc_modem_events_enable failed, error: -14[0m
2022-08-04T11:19:28.375Z DEBUG modem << [00:00:00.530,853] [1;31m<err> modem_module: Failed setting up the modem, error: -14[0m
2022-08-04T11:19:28.387Z DEBUG modem << [00:00:00.530,944] [0m<inf> app_event_manager: MODEM_EVT_ERROR - Error code -14[0m
2022-08-04T11:19:28.400Z DEBUG modem << [00:00:00.531,616] [0m<inf> app_event_manager: UTIL_EVT_SHUTDOWN_REQUEST[0m
2022-08-04T11:19:28.403Z DEBUG modem << [00:00:00.532,196] [0m<inf> app_event_manager: UI_EVT_SHUTDOWN_READY[0m
2022-08-04T11:19:28.408Z DEBUG modem << [00:00:00.532,348] [1;33m<wrn> modules_common: Module "ui" shutdown registered[0m
2022-08-04T11:19:28.415Z DEBUG modem << [00:00:00.532,470] [0m<inf> app_event_manager: GNSS_EVT_SHUTDOWN_READY[0m
2022-08-04T11:19:28.426Z DEBUG modem << [00:00:00.532,684] [1;33m<wrn> modules_common: Module "gnss" shutdown registered[0m
2022-08-04T11:19:28.429Z DEBUG modem << [00:00:00.533,264] [0m<inf> app_event_manager: APP_EVT_SHUTDOWN_READY[0m
2022-08-04T11:19:28.432Z DEBUG modem << [00:00:00.533,416] [1;33m<wrn> modules_common: Module "app" shutdown registered[0m
2022-08-04T11:19:28.433Z DEBUG modem << [00:00:00.534,149] [0m<inf> app_event_manager: CLOUD_EVT_SHUTDOWN_READY[0m
2022-08-04T11:19:28.444Z DEBUG modem << [00:00:00.534,515] [1;33m<wrn> modules_common: Module "cloud" shutdown registered[0m
2022-08-04T11:19:28.447Z DEBUG modem << [00:00:00.534,851] [0m<inf> app_event_manager: SENSOR_EVT_SHUTDOWN_READY[0m
2022-08-04T11:19:28.459Z DEBUG modem << [00:00:00.535,003] [1;33m<wrn> modules_common: Module "sensor" shutdown registered[0m
2022-08-04T11:19:28.504Z DEBUG modem << +CEREG: 0,"FFFE","FFFFFFFF",7,0,0,"11100000","11100000"
2022-08-04T11:19:29.503Z DEBUG modem << [00:00:00.707,275] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2022-08-04T11:19:29.510Z DEBUG modem << [00:00:00.715,698] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2022-08-04T11:19:29.521Z DEBUG modem << [00:00:00.715,942] [1;33m<wrn> modules_common: data: Message could not be enqueued, error code: -35[0m
2022-08-04T11:19:29.530Z DEBUG modem << [00:00:00.715,972] [1;31m<err> data_module: Message could not be enqueued[0m
2022-08-04T11:19:29.543Z DEBUG modem << [00:00:00.716,369] [0m<inf> app_event_manager: DATA_EVT_ERROR - Error code -35[0m
2022-08-04T11:19:31.022Z DEBUG modem << [00:00:02.225,097] [0m<inf> app_event_manager: MODEM_EVT_SHUTDOWN_READY[0m
2022-08-04T11:19:31.029Z DEBUG modem << [00:00:02.225,463] [1;33m<wrn> modules_common: Module "modem" shutdown registered[0m