Hi there!
I have a Thingy:91 which I've registered on the NRF Cloud and verified its operation by flashing the prebuild hex files to my board. After doing this, I can see data coming in on the NRF dashboard.
The files flashed are:
- Modem: mfw_nrf9160_1.3.6.zip
- App: thingy91_asset_tracker_v2_2024-07-04_20471118.hex
In a next step I tried to build the Asset Tracker V2 application myself using vscode, without adjusting anything, resulting in the following build command:
west build --build-dir PROJECT_PATH/Thingy-91/asset_tracker_v2/build PROJECT_PATH/Thingy-91/asset_tracker_v2 --pristine --board thingy91_nrf9160_ns --no-sysbuild -- -DNCS_TOOLCHAIN_VERSION=NONE -DBOARD_ROOT=PROJECT_PATH/thingy-91/asset_tracker_v2 -Dmcuboot_OVERLAY_CONFIG=C:/ncs/v2.5.0/nrf/modules/mcuboot/tfm.conf;C:/ncs/v2.5.0/nrf/modules/mcuboot/fih_low_enable.conf;C:/ncs/v2.5.0/nrf/subsys/partition_manager/partition_manager_enabled.conf;PROJECT_PATH/Thingy-91/asset_tracker_v2/child_image/mcuboot.conf -DCACHED_CONF_FILE=PROJECT_PATH/Thingy-91/asset_tracker_v2/prj.conf;PROJECT_PATH/Thingy-91/asset_tracker_v2/boards/thingy91_nrf9160_ns.conf -DDTC_OVERLAY_FILE=PROJECT_PATH/Thingy-91/asset_tracker_v2/boards/thingy91_nrf9160_ns.overlay
After flashing app_signed.hex to the board using the NRF Desktop Programmer v4.4.0, the board starts up and reboots at random moments, but I can see that it:
- Starts up
- Creates a LTE connection successfully
- Creates a Cloud connection successfully
As a sanity check, I flashed the original precompiled hex file (thingy91_asset_tracker_v2_2024-07-04_20471118.hex) back to the board, and verified that this works just fine.
In the following log from my locally compiled code (with cloud log set to debug), we can see the device connecting to the cloud and rebooting, and afterwards it reboots again but way sooner before while attempting an LTE connection:*** Booting nRF Connect SDK v2.5.0 ***
[00:00:00.269,897] <inf> app_event_manager: APP_EVT_START
[00:00:00.516,693] <inf> app_event_manager: MODEM_EVT_INITIALIZED
[00:00:00.526,550] <dbg> nrf_cloud_transport: nct_client_id_set: client_id = nrf-351901930739010
[00:00:00.526,885] <dbg> nrf_cloud_transport: nct_topics_populate: accepted_topic: nrf-351901930739010/shadow/get/accepted
[00:00:00.526,916] <dbg> nrf_cloud_transport: nct_topics_populate: rejected_topic: $aws/things/nrf-351901930739010/shadow/get/rejected
[00:00:00.526,977] <dbg> nrf_cloud_transport: nct_topics_populate: update_delta_topic: $aws/things/nrf-351901930739010/shadow/update/delta
[00:00:00.527,008] <dbg> nrf_cloud_transport: nct_topics_populate: update_topic: $aws/things/nrf-351901930739010/shadow/update
[00:00:00.527,069] <dbg> nrf_cloud_transport: nct_topics_populate: shadow_get_topic: $aws/things/nrf-351901930739010/shadow/get
[00:00:00.527,099] <dbg> nrf_cloud: nfsm_set_current_state_and_notify: state: 1
[00:00:00.676,300] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
[00:00:01.271,362] <inf> app_event_manager: DATA_EVT_CONFIG_INIT
...
...
[00:01:45.800,323] <dbg> nrf_cloud_transport: nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 15000 result = 0
[00:01:45.800,354] <dbg> nrf_cloud_fsm: cc_tx_ack_handler: Data ACK for user tag: 15000
[00:01:45.800,384] <dbg> nrf_cloud: nfsm_set_current_state_and_notify: state: 7
[00:01:46.120,483] <dbg> nrf_cloud_transport: nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 301 result = 0
[00:01:46.120,513] <dbg> nrf_cloud_transport: nct_dc_connect: nct_dc_connect
[00:01:46.121,307] <dbg> nrf_cloud: nfsm_set_current_state_and_notify: state: 8
[00:01:46.528,381] <dbg> nrf_cloud_transport: nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 101 result = 0
[00:01:46.529,205] <dbg> nrf_cloud: nfsm_set_current_state_and_notify: state: 9
[00:01:46.530,334] <dbg> nrf_cloud_transport: nct_cc_send: mqtt_publish: id = 1000 opcode = 1 len = 145, topic: $aws/things/nrf-351901930739010/shadow/update
[00:01:46.531,585] <inf> app_event_manager: CLOUD_EVT_CONNECTED
[00:01:46.532,592] <inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, MOD_STAT, LOCATION)
[00:01:46.633,422] <inf> app_event_manager: LOCATION_MODULE_EVT_AGNSS_NEEDED
[00:01:46.633,850] <inf> app_event_manager: LOCATION_MODULE_EVT_ACTIVE
*** Booting nRF Connect SDK v2.5.0 ***
[00:00:00.269,866] <inf> app_event_manager: APP_EVT_START
[00:00:00.516,571] <inf> app_event_manager: MODEM_EVT_INITIALIZED
[00:00:00.526,428] <dbg> nrf_cloud_transport: nct_client_id_set: client_id = nrf-351901930739010
[00:00:00.526,763] <dbg> nrf_cloud_transport: nct_topics_populate: accepted_topic: nrf-351901930739010/shadow/get/accepted
[00:00:00.526,794] <dbg> nrf_cloud_transport: nct_topics_populate: rejected_topic: $aws/things/nrf-351901930739010/shadow/get/rejected
[00:00:00.526,855] <dbg> nrf_cloud_transport: nct_topics_populate: update_delta_topic: $aws/things/nrf-351901930739010/shadow/update/delta
[00:00:00.526,885] <dbg> nrf_cloud_transport: nct_topics_populate: update_topic: $aws/things/nrf-351901930739010/shadow/update
[00:00:00.526,947] <dbg> nrf_cloud_transport: nct_topics_populate: shadow_get_topic: $aws/things/nrf-351901930739010/shadow/get
[00:00:00.526,977] <dbg> nrf_cloud: nfsm_set_current_state_and_notify: state: 1
[00:00:00.676,147] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
[00:00:01.271,331] <inf> app_event_manager: DATA_EVT_CONFIG_INIT
[00:00:01.944,854] <inf> app_event_manager: SENSOR_EVT_MOVEMENT_ACTIVITY_DETECTED
%MDMEV: SEARCH STATUS 1
*** Booting nRF Connect SDK v2.5.0 ***
Any ideas what this could be?