Unable to connect to Cloud using Asset Tracker on nRF9160 DK

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

mourad — Mon, 22 Aug 2022 08:11:20 GMT

Thanks Albrecht for your answer,

I will buy new version , I think I will have much trouble with this old version.

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Albrecht Markus Schellenberger — Mon, 08 Aug 2022 10:54:39 GMT

Hello Mourad,

[quote user="mourad"]

I uploaded the latest at_client firmware

and this is the log file:

[/quote]

Generally, the log is looking good, although I do not really like this line:

2022-08-05T11:15:43.330Z DEBUG modem << +CESQ: 99,99,255,255,255,255

It confuses me a little as there seems to be no signal power/quality at all, which is wired considering that the modem is connected to a network:

2022-08-05T11:15:43.081Z DEBUG modem >> AT+CEREG? 
2022-08-05T11:15:43.097Z DEBUG modem << +CEREG: 5,5,"C505","01720B04",7,,,"00001010","01001000"

I’m honestly not quite sure what to do here, but I would suggest that you run the HTTPS client and check if APN/IP data traffic is possible.

Cheers,

Markus

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

mourad — Fri, 05 Aug 2022 11:19:37 GMT

I uploaded the latest at_client firmware

and this is the log file:

2022-08-05T11:15:39.863Z INFO Installed JLink version does not match the provided version (V7.58b)
2022-08-05T11:15:42.634Z INFO Modem port is opened
2022-08-05T11:15:42.652Z DEBUG modem >> AT+CFUN?
2022-08-05T11:15:42.687Z DEBUG modem << +CFUN: 1
2022-08-05T11:15:42.694Z DEBUG modem << OK
2022-08-05T11:15:42.718Z DEBUG modem >> AT+CGSN=1
2022-08-05T11:15:42.745Z DEBUG modem << +CGSN: "352656100050676"
2022-08-05T11:15:42.748Z DEBUG modem << OK
2022-08-05T11:15:42.753Z DEBUG modem >> AT+CGMI
2022-08-05T11:15:42.768Z DEBUG modem << Nordic Semiconductor ASA
2022-08-05T11:15:42.779Z DEBUG modem << OK
2022-08-05T11:15:42.786Z DEBUG modem >> AT+CGMM
2022-08-05T11:15:42.802Z DEBUG modem << nRFFFFFFFFF-SICA
2022-08-05T11:15:42.816Z DEBUG modem << OK
2022-08-05T11:15:42.822Z DEBUG modem >> AT+CGMR
2022-08-05T11:15:42.842Z DEBUG modem << mfw_nrf9160_1.2.7
2022-08-05T11:15:42.849Z DEBUG modem << OK
2022-08-05T11:15:42.853Z INFO Nordic Semiconductor ASA nRFFFFFFFFF-SICA [mfw_nrf9160_1.2.7] SerNr: 352656100050676
2022-08-05T11:15:42.862Z DEBUG modem >> AT+CEMODE?
2022-08-05T11:15:42.878Z DEBUG modem << +CEMODE: 2
2022-08-05T11:15:42.881Z DEBUG modem << OK
2022-08-05T11:15:42.910Z DEBUG modem >> AT%XCBAND=?
2022-08-05T11:15:42.932Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2022-08-05T11:15:42.935Z DEBUG modem << OK
2022-08-05T11:15:42.961Z DEBUG modem >> AT+CMEE?
2022-08-05T11:15:42.977Z DEBUG modem << +CMEE: 1
2022-08-05T11:15:42.980Z DEBUG modem << OK
2022-08-05T11:15:42.983Z DEBUG modem >> AT+CNEC?
2022-08-05T11:15:42.999Z DEBUG modem << +CNEC: 24
2022-08-05T11:15:43.003Z DEBUG modem << 
2022-08-05T11:15:43.008Z DEBUG modem << OK
2022-08-05T11:15:43.016Z DEBUG modem >> AT+CGEREP?
2022-08-05T11:15:43.029Z DEBUG modem << +CGEREP: 1,0
2022-08-05T11:15:43.032Z DEBUG modem << OK
2022-08-05T11:15:43.048Z DEBUG modem >> AT+CIND=1,1,1
2022-08-05T11:15:43.063Z DEBUG modem << OK
2022-08-05T11:15:43.067Z DEBUG modem >> AT+CEREG=5
2022-08-05T11:15:43.078Z DEBUG modem << OK
2022-08-05T11:15:43.081Z DEBUG modem >> AT+CEREG?
2022-08-05T11:15:43.097Z DEBUG modem << +CEREG: 5,5,"C505","01720B04",7,,,"00001010","01001000"
2022-08-05T11:15:43.100Z DEBUG modem << 
2022-08-05T11:15:43.102Z DEBUG modem << OK
2022-08-05T11:15:43.120Z DEBUG modem >> AT+COPS=3,2
2022-08-05T11:15:43.136Z DEBUG modem << OK
2022-08-05T11:15:43.146Z DEBUG modem >> AT+COPS?
2022-08-05T11:15:43.160Z DEBUG modem << +COPS: 0,2,"20801",7
2022-08-05T11:15:43.163Z DEBUG modem << OK
2022-08-05T11:15:43.186Z DEBUG modem >> AT%XCBAND
2022-08-05T11:15:43.199Z DEBUG modem << %XCBAND: 20
2022-08-05T11:15:43.201Z DEBUG modem << 
2022-08-05T11:15:43.205Z DEBUG modem << OK
2022-08-05T11:15:43.224Z DEBUG modem >> AT+CGDCONT?
2022-08-05T11:15:43.242Z DEBUG modem << +CGDCONT: 0,"IP","ibasis.iot","10.160.218.50",0,0
2022-08-05T11:15:43.245Z DEBUG modem << OK
2022-08-05T11:15:43.262Z DEBUG modem >> AT+CGACT?
2022-08-05T11:15:43.278Z DEBUG modem << +CGACT: 0,1
2022-08-05T11:15:43.280Z DEBUG modem << OK
2022-08-05T11:15:43.295Z DEBUG modem >> AT%CESQ=1
2022-08-05T11:15:43.310Z DEBUG modem << OK
2022-08-05T11:15:43.314Z DEBUG modem >> AT+CESQ
2022-08-05T11:15:43.330Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2022-08-05T11:15:43.332Z DEBUG modem << OK
2022-08-05T11:15:43.351Z DEBUG modem >> AT%XSIM=1
2022-08-05T11:15:43.364Z DEBUG modem << OK
2022-08-05T11:15:43.367Z DEBUG modem >> AT%XSIM?
2022-08-05T11:15:43.378Z DEBUG modem << %XSIM: 1
2022-08-05T11:15:43.381Z DEBUG modem << 
2022-08-05T11:15:43.383Z DEBUG modem << OK
2022-08-05T11:15:43.398Z DEBUG modem >> AT+CPIN?
2022-08-05T11:15:43.412Z DEBUG modem << +CPIN: READY
2022-08-05T11:15:43.415Z DEBUG modem << OK
2022-08-05T11:15:43.430Z DEBUG modem >> AT+CPINR="SIM PIN"
2022-08-05T11:15:43.443Z DEBUG modem << +CME ERROR: 0
2022-08-05T11:16:33.306Z DEBUG modem >> AT%XOPERID
2022-08-05T11:16:33.323Z DEBUG modem << %XOPERID: 0
2022-08-05T11:16:33.326Z DEBUG modem << OK
2022-08-05T11:16:47.001Z DEBUG modem >> AT%XMONITOR
2022-08-05T11:16:47.024Z DEBUG modem << %XMONITOR: 5,"Orange F","Orange F","20801","C505",7,20,"01720B04",,,,,"","00001010","01001000","01011111"
2022-08-05T11:16:47.029Z DEBUG modem << OK
2022-08-05T11:16:59.809Z DEBUG modem >> AT%XTEMP?
2022-08-05T11:16:59.825Z DEBUG modem << %XTEMP: 32
2022-08-05T11:16:59.828Z DEBUG modem << OK
2022-08-05T11:17:09.743Z DEBUG modem >> AT%CMNG=1
2022-08-05T11:17:09.763Z DEBUG modem << %CMNG: 16842753,0,"0000000000000000000000000000000000000000000000000000000000000000"
2022-08-05T11:17:09.792Z DEBUG modem << %CMNG: 16842753,1,"0101010101010101010101010101010101010101010101010101010101010101"
2022-08-05T11:17:09.805Z DEBUG modem << %CMNG: 16842753,2,"0202020202020202020202020202020202020202020202020202020202020202"
2022-08-05T11:17:09.810Z DEBUG modem << OK

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Albrecht Markus Schellenberger — Fri, 05 Aug 2022 11:03:11 GMT

[quote user="mourad"]I use iBasis sim card and yes it's activated [/quote]

Ok thanks, Mourad!

Could you please flash the ../img_app_bl/nrf9160dk_at_client_2022-06-02_880c82db.hex firmware, run through the Testing procedure described in the sample description and share the complete log?

I would like to check some basic modem configurations.

Cheers,

Markus

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

mourad — Fri, 05 Aug 2022 08:20:45 GMT

Hi Albrecht,

I use iBasis sim card and yes it's activated

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Albrecht Markus Schellenberger — Fri, 05 Aug 2022 06:57:05 GMT

Hello Mourad,

[quote user="mourad"]I got this warning when i try to upload the Asset Tracker firmware[/quote]

The secure bootloader chain is enabled by default for nRF9160 DK in Asset Tracker v2. The immutable bootloader stores keys in UICR to verify the MCUboot image during boot, which triggers this warning. It is fine to proceed, though.

[quote user="mourad"]for the latest firmware /img_app_bl/nrf9160dk_asset_tracker_v2_ltem_2022-06-02_880c82db.hex. It still the same problem [/quote]

The modem reports that it has not been able yet to connect to a network, which makes it impossible for the nRF9160 to connect to the nRF Cloud.

2022-08-04T11:19:28.504Z DEBUG modem << +CEREG: 0,"FFFE","FFFFFFFF",7,0,0,"11100000","1110000

Referring to the documentation of +CEREG for your reference.

There appears to be an issue with the modem configuration:

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

But let's start at this point: which SIM card are you using and can you confirm that it is activated?

Cheers,

Markus

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

mourad — Thu, 04 Aug 2022 11:20:25 GMT

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

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

mourad — Thu, 04 Aug 2022 09:06:03 GMT

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

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Albrecht Markus Schellenberger — Thu, 04 Aug 2022 08:49:57 GMT

Thanks a lot for the feedback, Mourad!

[quote user="mourad"]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 [/quote]

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.

[quote user="mourad"]I got this error from the cloud and the log file above from the LTE monitor[/quote]

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

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

mourad — Thu, 04 Aug 2022 08:22:27 GMT

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

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Albrecht Markus Schellenberger — Thu, 04 Aug 2022 07:16:10 GMT

Hello Mourad,

[quote user=""]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.[/quote]

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?

[quote user=""]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[/quote]

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