Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Mon, 17 Jul 2023 14:50:19 GMT

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/436503"]Have you had your HW reviewed by us?[/quote]

Excellent idea, thanks, Now Im going to open a private ticket and reference this public ticket for the hw review,

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/436503"]How is your board powered? Have you tried to look at the supply voltage to make sure it doesn't drop too low when the modem tries to transmit?[/quote]

by powering a battery. well, you will see in the schematic, I have two different power supply LDO for nrf9160 for the vdd_gpio of 1.8V and vdd of 3.3V, Modem supplied by VDD 3.3V, right? so, have a 3.3 LDO, I check there is no significant voltage drop.

Thank you for your help

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

Didrik Rokhaug — Fri, 14 Jul 2023 13:28:06 GMT

Hi, and sorry for the late reply.

Because of summer vacations, we are a bit short on staff, which makes it harder to reply to everyone in a timely manner.

[quote user="zsn"]Would you mind analyzing and telling me whats wrong with this log file, please?[/quote]

This log is taken with modem FW v1.3.4, and I couldn't see any resets in it. Are you sure this is the right log?

[quote user="zsn"]

additional test: instead of the atv2 application I just used the at_client app, ran "at" command manually and here is the result when I set at+cfun=1, the system crashed again...

I have two exactly the same boards, one of them has mfw 1.3.5 and the other 1.3.4

at+cfun=1 crash on the board has mfw 1.3.5.

[/quote]

This is interesting...

Could you take a modem trace when using the at_client and modem FW v1.3.5?

Also, if you could enable CONFIG_NRF_MODEM_LIB_LOG_LEVEL_DBG and CONFIG_LOG, that might also be of help.

[quote user="zsn"] I believe all these pieces of evidence show some things are wrong with mfw 1.3.5 or mfw 1.3.5 has a different functionality/approach(are not mentioned in the change log) and my board doesn't support it. The first thing that popped into my head is high power consumption during at+cfun=1 but my supply can support up to 1A. So i dont think it is a power supply issue. So, Could you please verify all these points?[/quote]

There shouldn't be any changes when it comes to power consumption, etc. between mfw 1.3.4 and 1.3.5 as far as I am aware.

I also haven't heard of anyone else with similar problems, so I find it hard to believe that the modem FW is faulty.

Have you had your HW reviewed by us?

If not, could you open a new private ticket where you upload your HW schematics so that we can take a look at them?

How is your board powered? Have you tried to look at the supply voltage to make sure it doesn't drop too low when the modem tries to transmit?

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Tue, 11 Jul 2023 12:23:26 GMT

Hi Didrik Rokhaug Would you mind analyzing and telling me whats wrong with this log file, please?

devzone.nordicsemi.com/.../data_2D00_logging_2D00_11_2D00_07_2D00_23_2D00_13_2D00_00.log

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Sun, 09 Jul 2023 00:03:16 GMT

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/434269"]What happens when this event is triggered? Could there be something in this event that triggers the reset?[/quote]

I am 100% sure, the issue is not because of this event. I am currently out of ideas and don't know what can I do else to fix. I removed everything even sensor modules and related to that event. So I have still the same issue.

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/434269"]

The stock Asset Tracker v2 works with mfw 1.3.5, so the error is probably somewhere in your code.

[/quote]

If so, how can this code work even on the dk board without doing anything else, I just compiled with the dk board dts file and it worked. But the same code doesn't work on my board has mfw1.3.5. its funny :(

So What I am doing now, I am comparing the log outputs of two boards which one of them has mfw1.3.5(the code doesnt work) and mwf1.3.4 (works)

the code on the board has mfw 1.3.5 has restart before printing this +CSCON: 1

[00:00:07.224,609] <dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -90
+CEREG: 2,"9FF7","0016155A",9
[00:00:07.237,335] <dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"9FF7","0016155A",9

[00:00:07.247,344] <dbg> lte_lc_helpers: parse_cereg: Network registration status: 2
[00:00:07.255,462] <dbg> lte_lc_helpers: parse_cereg: LTE mode: 9
[00:00:07.261,993] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:07.270,538] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AA1
[00:00:07.279,815] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A79
[00:00:07.288,513] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053ED9
[00:00:07.297,302] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x000386A9
[00:00:07.306,030] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
[00:00:07.313,354] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:07.321,929] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AA1
[00:00:07.330,688] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A79
[00:00:07.339,447] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053ED9
[00:00:07.348,205] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x000386A9
[00:00:07.356,964] <dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 1447258, Tracking area: 40951
[00:00:07.367,584] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
[00:00:07.374,847] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:07.383,422] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AA1
[00:00:07.392,181] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A79
[00:00:07.400,939] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053ED9
[00:00:07.409,698] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x000386A9
[00:00:07.418,457] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
[00:00:07.425,842] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
*** Booting Zephyr OS build v3.2.99-ncs1 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0xf5...73
Firmware signature verified.
Firmware version 5
Booting (0x8200).

the code on the board has mwf1.3.4

[00:00:09.565,704] <dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -102
+CEREG: 2,"2332","05869021",9
[00:00:09.578,491] <dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"2332","05869021",9

[00:00:09.588,439] <dbg> lte_lc_helpers: parse_cereg: Network registration status: 2
[00:00:09.596,557] <dbg> lte_lc_helpers: parse_cereg: LTE mode: 9
[00:00:09.603,057] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:09.611,572] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AA1
[00:00:09.620,727] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A79
[00:00:09.629,394] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053ED9
[00:00:09.638,122] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x000386A9
[00:00:09.646,850] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
[00:00:09.654,144] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:09.662,689] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AA1
[00:00:09.671,417] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A79
[00:00:09.680,145] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053ED9
[00:00:09.688,873] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x000386A9
[00:00:09.697,631] <dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 92704801, Tracking area: 9010
[00:00:09.708,190] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
[00:00:09.715,423] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:09.723,968] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AA1
[00:00:09.732,696] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A79
[00:00:09.741,455] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053ED9
[00:00:09.750,183] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x000386A9
[00:00:09.758,911] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
[00:00:09.766,265] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
+CSCON: 1
[00:00:10.197,540] <dbg> lte_lc: at_handler_cscon: +CSCON notification
[00:00:10.204,559] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:10.213,073] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AA1
[00:00:10.221,801] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A79
[00:00:10.230,529] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053ED9
[00:00:10.239,257] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x000386A9
[00:00:10.247,985] <dbg> modem_module: lte_evt_handler: RRC mode: Connected
[00:00:10.255,340] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
+CGEV: ME PDN ACT 0,0
[00:00:12.102,844] <dbg> modem_module: pdn_event_handler: PDN_EVENT_ACTIVATED
[00:00:12.110,382] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTED
[00:00:12.117,675] <dbg> modem_module: state_set: State transition STATE_CONNECTING --> STATE_CONNECTED
[00:00:12.127,502] <dbg> aws_iot_integration: aws_iot_event_handler: AWS_IOT_EVT_CONNECTING
[00:00:12.136,230] <inf> app_event_manager: CLOUD_EVT_CONNECTING
+CNEC_ESM: 50,0
[00:00:12.145,416] <err> modem_module: Event: PDP context 0, PDN type IPv4 only allowed
%MDMEV: SEARCH STATUS 2
[00:00:12.246,490] <dbg> lte_lc: at_handler_mdmev: %MDMEV notification
[00:00:12.253,387] <dbg> lte_lc_helpers: parse_mdmev: Occurrence found: SEARCH STATUS 2

[00:00:12.261,932] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:12.270,477] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AA1
[00:00:12.279,205] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A79
[00:00:12.287,902] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053ED9
[00:00:12.296,630] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x000386A9
[00:00:12.305,358] <dbg> modem_module: lte_evt_handler: Modem domain event, type: Search done
[00:00:12.314,239] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
+CEREG: 5,"2332","05869021",9,,,"00001010","11000001"

In deeper, I noticed that I have a restart a few seconds after setting at+cfun = 1

lte_lc_func_mode_set(LTE_LC_FUNC_MODE_NORMAL)

, I put a breakpoint in the at_handler_cereg func but the app didn't allow me to go through the line by line. because crashes after setting cfun=1. normally program flow shouldve stayed on the breakpoint line. it means maybe something happens simultaneously on the modem side after setting cfun=1. So I also tried to print in the function and I put the print sequence like this and after printing "333333444444" doesn't go beyond this print. Because reg_status is 2 , so it is not

LTE_LC_NW_REG_REGISTERED_ROAMING and LTE_LC_NW_REG_REGISTERED_HOME.

it means at_handler_cereg funct. works fine.

Log output:

%CESQ: 48,2,23,3
[00:00:09.340,332] <dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -92
+CEREG: 2,"9FF7","0016155A",9
[00:00:09.353,088] <dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"9FF7","0016155A",9

[00:00:09.363,037] <dbg> lte_lc_helpers: parse_cereg: Network registration status: 2
[00:00:09.371,185] <dbg> lte_lc_helpers: parse_cereg: LTE mode: 9
reg_stt: 2 1447258
1111111111
[00:00:09.380,432] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:09.389,007] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AB9
[00:00:09.398,193] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A91
[00:00:09.406,890] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053EF1
[00:00:09.415,649] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
2222222222
[00:00:09.423,980] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:09.432,586] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AB9
[00:00:09.441,345] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A91
[00:00:09.450,073] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053EF1
[00:00:09.458,831] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
33333333333
[00:00:09.467,254] <dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:
[00:00:09.475,830] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00052AB9
[00:00:09.484,588] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053A91
[00:00:09.493,347] <dbg> lte_lc_helpers: event_handler_list_dispatch:  - handler=0x00053EF1
[00:00:09.502,105] <dbg> lte_lc_helpers: event_handler_list_dispatch: Done
3333344444 2
*** Booting Zephyr OS build v3.2.99-ncs1 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.

additional test: instead of the atv2 application I just used the at_client app, ran "at" command manually and here is the result when I set at+cfun=1, the system crashed again...

I have two exactly the same boards, one of them has mfw 1.3.5 and the other 1.3.4

at+cfun=1 crash on the board has mfw 1.3.5.

Sir Didrik Rokhaug : I believe all these pieces of evidence show some things are wrong with mfw 1.3.5 or mfw 1.3.5 has a different functionality/approach(are not mentioned in the change log) and my board doesn't support it. The first thing that popped into my head is high power consumption during at+cfun=1 but my supply can support up to 1A. So i dont think it is a power supply issue. So, Could you please verify all these points?

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/434269"]

You can disable TF-Ms usage of UART 1 by disabling CONFIG_TFM_SECURE_UART. However, it should be disabled by default, so I don't think this is the cause of your problem.

Otherwise, yes, you would not be able to use I2C1 from the non-secure application if UART1 is configured as secure.

[/quote]

Got it, thank you for this clarification.

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

Didrik Rokhaug — Mon, 03 Jul 2023 15:03:24 GMT

[quote user="zsn"]and also one more notice, normally when the device is in a reset loop, normally modem was going into restriction mode for 30min. But I can't see it anymore, is this situation normal?[/quote]

You can read more about the reset loop restriction here: https://infocenter.nordicsemi.com/topic/nwp_042/WP/nwp_042/intro.html

It is meant to trigger when the application fails repeatedly shortly after it starts the modem, so yes, it is expected that it triggers if you let the application run in a reset loop.

[quote user="zsn"]yes, I have added it.[/quote]

What happens when this event is triggered? Could there be something in this event that triggers the reset?

Do you still get the resets if you don't do anything when you get this event?

The stock Asset Tracker v2 works with mfw 1.3.5, so the error is probably somewhere in your code.

[quote user="zsn"]if I am not mistaken, UART1 is disabled on the dk device tree config, because it is used by default in TF-M . But on my board, I am using I2C1 instead of UART1 which shares the same memory location. So Maybe this the issue? What do you think?[/quote]

You can disable TF-Ms usage of UART 1 by disabling CONFIG_TFM_SECURE_UART. However, it should be disabled by default, so I don't think this is the cause of your problem.

Otherwise, yes, you would not be able to use I2C1 from the non-secure application if UART1 is configured as secure.

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Thu, 29 Jun 2023 22:43:50 GMT

Hi Didrik Rokhaug After a long time of debugging, I'd like to ask one point, I suspect two points related to our hardware design, I ran the same application on the dk board built with nrf9160dk devicetree, and it worked well, So, in this case,

1. on our hw design we are not using nrf9160' gnss functionality so we left gnss pin (67) floating and also, COEX0,1,2 pulled them down. I wonder if there are any dependencies related to these pins in the mfw 1.3.5?

In my config file, I am using

lte configuration without gnss like this

CONFIG_LTE_NETWORK_MODE_LTE_M_NBIOT=y
CONFIG_LTE_MODE_PREFERENCE_NBIOT_PLMN_PRIO=y

2. The second point I suspect is the device tree design for my board.

if I am not mistaken, UART1 is disabled on the dk device tree config, because it is used by default in TF-M . But on my board, I am using I2C1 instead of UART1 which shares the same memory location. So Maybe this the issue? What do you think?

one more additional point, During debugging I observed that when the device run

err = nrf_modem_at_printf("AT+CFUN=%d", mode); sub function in lte_lc_func_mode_set function in the lte.lc.c file then the device crashed and restarted.

Thanks, Kind regards

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Thu, 29 Jun 2023 16:14:59 GMT

after enabling lte_link control_debug mode,

I started seeing crashes sometimes after publishing messages to the cloud, it was normally right away after MODEM_EVT_LTE_CELL_UPDATE. it means the issue is dynamic, not exactly on the one point.

2023-06-29T14:35:23.522Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:35:23.524Z DEBUG modem << [00:00:03.581,848] [0m<inf> main: i setting pin high ----1111-----[0m
2023-06-29T14:35:24.490Z DEBUG modem << [00:00:04.588,256] [0m<inf> main: i set nrf select pin high -----222----[0m
2023-06-29T14:35:24.556Z DEBUG modem << [00:00:04.595,397] [0m<inf> app_event_manager: APP_EVT_START[0m
2023-06-29T14:35:24.559Z DEBUG modem << [00:00:04.601,928] [0m<dbg> data_module: state_set: State: STATE_CLOUD_DISCONNECTED[0m
2023-06-29T14:35:24.566Z DEBUG modem << [00:00:04.610,107] [0m<dbg> modem_module: state_set: State transition STATE_INIT --> STATE_DISCONNECTED[0m
2023-06-29T14:35:24.570Z DEBUG modem << [00:00:04.619,628] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2023-06-29T14:35:24.574Z DEBUG modem << [00:00:04.626,983] [0m<dbg> sensor_module: state_set: State: STATE_INIT[0m
2023-06-29T14:35:24.579Z DEBUG modem << [00:00:04.633,789] [0m<dbg> ext_sensors: sensor_settings_set: Settings key: state, size: 1, sizeofJobDef 1[0m
2023-06-29T14:35:24.582Z DEBUG modem << [00:00:04.643,615] [0m<dbg> ext_sensors: sensor_settings_set: SZ: 1[0m
2023-06-29T14:35:24.586Z DEBUG modem << [00:00:04.650,024] [0m<inf> ext_sensors: yic status: 1[0m
2023-06-29T14:35:24.669Z DEBUG modem << [00:00:04.655,364] [0m<dbg> ext_sensors: load_sensor_settings: SETTINGS: 0[0m
2023-06-29T14:35:24.676Z DEBUG modem << [00:00:04.662,353] [0m<dbg> ext_sensors: ext_sensors_init: ACCEL adxl362@0 initialized![0m
2023-06-29T14:35:24.679Z DEBUG modem << [00:00:04.670,867] [0m<dbg> lte_lc: init_and_config: System mode (6) and preference (4) are already configured[0m
2023-06-29T14:35:24.682Z DEBUG modem << [00:00:04.683,380] [0m<dbg> ext_sensors: ext_sensors_init: CONFIGURE ACCCCCCC1111[0m
2023-06-29T14:35:24.771Z DEBUG modem << [00:00:04.691,925] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:35:24.780Z DEBUG modem << [00:00:04.702,026] [0m<dbg> aws_iot_integration: cloud_wrap_init: The Asset Tracker v2 has started[0m
2023-06-29T14:35:24.783Z DEBUG modem << [00:00:04.711,212] [0m<dbg> aws_iot_integration: cloud_wrap_init: Version: 0.0.18[0m
2023-06-29T14:35:24.785Z DEBUG modem << [00:00:04.719,299] [0m<dbg> aws_iot_integration: cloud_wrap_init: Client ID: 351516173341025[0m
2023-06-29T14:35:24.788Z DEBUG modem << [00:00:04.728,118] [0m<dbg> aws_iot_integration: cloud_wrap_init: Cloud: AWS IoT[0m
2023-06-29T14:35:24.789Z DEBUG modem << [00:00:04.736,267] [0m<dbg> aws_iot_integration: cloud_wrap_init: Endpoint: a2hkw2qiy12x93-ats.iot.eu-west-1.amazonaws.com[0m
2023-06-29T14:35:24.795Z DEBUG modem << [00:00:04.747,802] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:35:24.798Z DEBUG modem << [00:00:04.758,697] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 331000.000000V[0m
2023-06-29T14:35:24.800Z DEBUG modem << [00:00:04.769,378] [0m<dbg> ext_sensors: ext_sensors_init: bq27z561@55 fuel gauge initialized succesfully 433V [0m
2023-06-29T14:35:24.802Z DEBUG modem << [00:00:04.779,632] [0m<dbg> ext_sensors: ext_sensors_init: Set up hall-effect at gpio@842500 pin 21[0m
2023-06-29T14:35:24.876Z DEBUG modem << [00:00:04.788,787] [0m<dbg> ext_sensors: config_gnss: GNSS CONFIG ALREADY SET[0m
2023-06-29T14:35:24.879Z DEBUG modem << [00:00:04.796,264] [0m<dbg> sensor_module: gnss_client_callback: GNSS_SEARCH_EVT_STARTED[0m
2023-06-29T14:35:24.883Z DEBUG modem << [00:00:04.805,175] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 331000.000000V[0m
2023-06-29T14:35:24.886Z DEBUG modem << [00:00:04.815,887] [0m<inf> app_event_manager: SENSOR_EVT_BATTERY_DATA_READY[0m
2023-06-29T14:35:24.889Z DEBUG modem << [00:00:04.823,455] [0m<dbg> modem_module: configure_low_power: PSM requested[0m
2023-06-29T14:35:24.892Z DEBUG modem << [00:00:04.865,356] [0m<dbg> lte_lc: lte_lc_func_mode_set: CFUN monitor callback: 0x52219[0m
2023-06-29T14:35:24.893Z DEBUG modem << [00:00:04.874,267] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2023-06-29T14:35:24.895Z DEBUG modem << [00:00:04.881,713] [0m<dbg> modem_module: state_set: State transition STATE_DISCONNECTED --> STATE_CONNECTING[0m
2023-06-29T14:35:25.515Z DEBUG modem << [00:00:05.610,107] [0m<dbg> data_module: setup: Failed retrieveing the device configuration from flash in time[0m
2023-06-29T14:35:25.588Z DEBUG modem << [00:00:05.620,239] [0m<inf> data_module: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:35:25.591Z DEBUG modem << [00:00:05.626,556] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:35:25.595Z DEBUG modem << [00:00:05.634,338] [0m<dbg> data_module: config_print_all: Device mode: Active[0m
2023-06-29T14:35:25.599Z DEBUG modem << [00:00:05.641,662] [0m<dbg> data_module: config_print_all: Active wait timeout: 180[0m
2023-06-29T14:35:25.602Z DEBUG modem << [00:00:05.649,475] [0m<dbg> data_module: config_print_all: Movement resolution: 120[0m
2023-06-29T14:35:25.605Z DEBUG modem << [00:00:05.657,287] [0m<dbg> data_module: config_print_all: Movement timeout: 3600[0m
2023-06-29T14:35:25.608Z DEBUG modem << [00:00:05.664,916] [0m<dbg> data_module: config_print_all: Location timeout: 300[0m
2023-06-29T14:35:25.611Z DEBUG modem << [00:00:05.672,454] [0m<dbg> data_module: config_print_all: Accelerometer act threshold: 4.00[0m
2023-06-29T14:35:25.613Z DEBUG modem << [00:00:05.681,030] [0m<dbg> data_module: config_print_all: Accelerometer inact threshold: 4.00[0m
2023-06-29T14:35:25.698Z DEBUG modem << [00:00:05.689,819] [0m<dbg> data_module: config_print_all: Accelerometer inact timeout: 60.00[0m
2023-06-29T14:35:25.706Z DEBUG modem << [00:00:05.698,486] [0m<dbg> data_module: config_print_all: Requesting of neighbor cell data is enabled[0m
2023-06-29T14:35:25.708Z DEBUG modem << [00:00:05.707,946] [0m<dbg> data_module: config_print_all: Requesting of GNSS data is enabled[0m
2023-06-29T14:35:25.797Z DEBUG modem << [00:00:05.716,644] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
2023-06-29T14:35:25.801Z DEBUG modem << [00:00:05.723,663] [0m<dbg> data_module: requested_data_status_set: Data already encoded and sent, abort.[0m
2023-06-29T14:35:25.807Z DEBUG modem << [00:00:05.733,459] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED_DATA_READY[0m
2023-06-29T14:35:25.810Z DEBUG modem << [00:00:05.741,882] [0m<dbg> sensor_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
2023-06-29T14:35:25.812Z DEBUG modem << [00:00:05.751,007] [0m<dbg> sensor_module: on_state_init: on_state_init battery sampling...[0m
2023-06-29T14:35:28.573Z DEBUG modem << %CESQ: 52,2,23,3
2023-06-29T14:35:28.583Z DEBUG modem << [00:00:08.678,710] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -88[0m
2023-06-29T14:35:28.662Z DEBUG modem << +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:35:28.759Z DEBUG modem << [00:00:08.691,436] [0m<dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:35:28.767Z DEBUG modem << [0m
2023-06-29T14:35:28.770Z DEBUG modem << [00:00:08.701,385] [0m<dbg> lte_lc_helpers: parse_cereg: Network registration status: 2[0m
2023-06-29T14:35:28.774Z DEBUG modem << [00:00:08.709,503] [0m<dbg> lte_lc_helpers: parse_cereg: LTE mode: 9[0m
2023-06-29T14:35:28.777Z DEBUG modem << [00:00:08.716,064] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:28.780Z DEBUG modem << [00:00:08.724,578] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:28.783Z DEBUG modem << [00:00:08.733,856] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:28.785Z DEBUG modem << [00:00:08.742,553] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:28.788Z DEBUG modem << [00:00:08.751,312] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:28.790Z DEBUG modem << [00:00:08.760,070] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:28.793Z DEBUG modem << [00:00:08.767,364] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:28.870Z DEBUG modem << [00:00:08.775,939] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:28.875Z DEBUG modem << [00:00:08.784,698] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:28.881Z DEBUG modem << [00:00:08.793,426] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:28.884Z DEBUG modem << [00:00:08.802,185] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:28.888Z DEBUG modem << [00:00:08.810,974] [0m<dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 1447258, Tracking area: 40951[0m
2023-06-29T14:35:28.891Z DEBUG modem << [00:00:08.821,563] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:28.894Z DEBUG modem << [00:00:08.828,826] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:28.896Z DEBUG modem << [00:00:08.837,402] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:28.898Z DEBUG modem << [00:00:08.846,160] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:28.900Z DEBUG modem << [00:00:08.854,919] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:28.903Z DEBUG modem << [00:00:08.863,647] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:28.905Z DEBUG modem << [00:00:08.872,406] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:28.908Z DEBUG modem << [00:00:08.879,791] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-06-29T14:35:29.814Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:35:29.900Z DEBUG modem << Attempting to boot slot 0.
2023-06-29T14:35:29.997Z DEBUG modem << Attempting to boot from address 0x8200.
2023-06-29T14:35:30.002Z DEBUG modem << Verifying signature against key 0.
2023-06-29T14:35:30.008Z DEBUG modem << Hash: 0x0f...ad
2023-06-29T14:35:30.011Z DEBUG modem << Firmware signature verified.
2023-06-29T14:35:30.013Z DEBUG modem << Firmware version 5
2023-06-29T14:35:30.016Z DEBUG modem << Booting (0x8200).
2023-06-29T14:35:34.069Z DEBUG modem << [00:00:02.486,816] [0m<inf> ADXL362: NetFeasa: Accelerometer Self Test Starting...[0m
2023-06-29T14:35:35.129Z DEBUG modem << [00:00:03.548,370] [0m<inf> ADXL362: ACCELEROMETER SELF-TEST PASS[0m
2023-06-29T14:35:35.214Z DEBUG modem << [00:00:03.557,037] [0m<inf> ADXL362: INT1 set at GPIO port gpio@842500 pin 6[0m
2023-06-29T14:35:35.219Z DEBUG modem << [00:00:03.572,723] [0m<inf> bq274xx: Device ID: 0xffa5[0m
2023-06-29T14:35:35.224Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:35:35.227Z DEBUG modem << [00:00:03.581,970] [0m<inf> main: i setting pin high ----1111-----[0m
2023-06-29T14:35:36.170Z DEBUG modem << [00:00:04.588,378] [0m<inf> main: i set nrf select pin high -----222----[0m
2023-06-29T14:35:36.176Z DEBUG modem << [00:00:04.595,520] [0m<inf> app_event_manager: APP_EVT_START[0m
2023-06-29T14:35:36.263Z DEBUG modem << [00:00:04.602,050] [0m<dbg> data_module: state_set: State: STATE_CLOUD_DISCONNECTED[0m
2023-06-29T14:35:36.268Z DEBUG modem << [00:00:04.610,229] [0m<dbg> modem_module: state_set: State transition STATE_INIT --> STATE_DISCONNECTED[0m
2023-06-29T14:35:36.273Z DEBUG modem << [00:00:04.619,781] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2023-06-29T14:35:36.276Z DEBUG modem << [00:00:04.627,105] [0m<dbg> sensor_module: state_set: State: STATE_INIT[0m
2023-06-29T14:35:36.279Z DEBUG modem << [00:00:04.633,941] [0m<dbg> ext_sensors: sensor_settings_set: Settings key: state, size: 1, sizeofJobDef 1[0m
2023-06-29T14:35:36.281Z DEBUG modem << [00:00:04.643,768] [0m<dbg> ext_sensors: sensor_settings_set: SZ: 1[0m
2023-06-29T14:35:36.284Z DEBUG modem << [00:00:04.650,177] [0m<inf> ext_sensors: yic status: 1[0m
2023-06-29T14:35:36.372Z DEBUG modem << [00:00:04.655,517] [0m<dbg> ext_sensors: load_sensor_settings: SETTINGS: 0[0m
2023-06-29T14:35:36.378Z DEBUG modem << [00:00:04.662,506] [0m<dbg> ext_sensors: ext_sensors_init: ACCEL adxl362@0 initialized![0m
2023-06-29T14:35:36.381Z DEBUG modem << [00:00:04.671,020] [0m<dbg> lte_lc: init_and_config: System mode (6) and preference (4) are already configured[0m
2023-06-29T14:35:36.385Z DEBUG modem << [00:00:04.683,532] [0m<dbg> ext_sensors: ext_sensors_init: CONFIGURE ACCCCCCC1111[0m
2023-06-29T14:35:36.388Z DEBUG modem << [00:00:04.692,077] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:35:36.391Z DEBUG modem << [00:00:04.702,178] [0m<dbg> aws_iot_integration: cloud_wrap_init: The Asset Tracker v2 has started[0m
2023-06-29T14:35:36.475Z DEBUG modem << [00:00:04.711,395] [0m<dbg> aws_iot_integration: cloud_wrap_init: Version: 0.0.18[0m
2023-06-29T14:35:36.478Z DEBUG modem << [00:00:04.719,451] [0m<dbg> aws_iot_integration: cloud_wrap_init: Client ID: 351516173341025[0m
2023-06-29T14:35:36.484Z DEBUG modem << [00:00:04.728,302] [0m<dbg> aws_iot_integration: cloud_wrap_init: Cloud: AWS IoT[0m
2023-06-29T14:35:36.488Z DEBUG modem << [00:00:04.736,450] [0m<dbg> aws_iot_integration: cloud_wrap_init: Endpoint: a2hkw2qiy12x93-ats.iot.eu-west-1.amazonaws.com[0m
2023-06-29T14:35:36.491Z DEBUG modem << [00:00:04.747,985] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:35:36.493Z DEBUG modem << [00:00:04.758,911] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 931000.000000V[0m
2023-06-29T14:35:36.495Z DEBUG modem << [00:00:04.769,561] [0m<dbg> ext_sensors: ext_sensors_init: bq27z561@55 fuel gauge initialized succesfully 393V [0m
2023-06-29T14:35:36.498Z DEBUG modem << [00:00:04.779,815] [0m<dbg> ext_sensors: ext_sensors_init: Set up hall-effect at gpio@842500 pin 21[0m
2023-06-29T14:35:36.501Z DEBUG modem << [00:00:04.788,970] [0m<dbg> ext_sensors: config_gnss: GNSS CONFIG ALREADY SET[0m
2023-06-29T14:35:36.503Z DEBUG modem << [00:00:04.796,447] [0m<dbg> sensor_module: gnss_client_callback: GNSS_SEARCH_EVT_STARTED[0m
2023-06-29T14:35:36.505Z DEBUG modem << [00:00:04.805,358] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 931000.000000V[0m
2023-06-29T14:35:36.605Z DEBUG modem << [00:00:04.816,070] [0m<inf> app_event_manager: SENSOR_EVT_BATTERY_DATA_READY[0m
2023-06-29T14:35:36.610Z DEBUG modem << [00:00:04.823,669] [0m<dbg> modem_module: configure_low_power: PSM requested[0m
2023-06-29T14:35:36.616Z DEBUG modem << [00:00:04.865,539] [0m<dbg> lte_lc: lte_lc_func_mode_set: CFUN monitor callback: 0x52219[0m
2023-06-29T14:35:36.620Z DEBUG modem << [00:00:04.874,450] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2023-06-29T14:35:36.623Z DEBUG modem << [00:00:04.881,896] [0m<dbg> modem_module: state_set: State transition STATE_DISCONNECTED --> STATE_CONNECTING[0m
2023-06-29T14:35:37.195Z DEBUG modem << [00:00:05.610,229] [0m<dbg> data_module: setup: Failed retrieveing the device configuration from flash in time[0m
2023-06-29T14:35:37.308Z DEBUG modem << [00:00:05.620,361] [0m<inf> data_module: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:35:37.311Z DEBUG modem << [00:00:05.626,708] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:35:37.313Z DEBUG modem << [00:00:05.634,460] [0m<dbg> data_module: config_print_all: Device mode: Active[0m
2023-06-29T14:35:37.316Z DEBUG modem << [00:00:05.641,784] [0m<dbg> data_module: config_print_all: Active wait timeout: 180[0m
2023-06-29T14:35:37.318Z DEBUG modem << [00:00:05.649,597] [0m<dbg> data_module: config_print_all: Movement resolution: 120[0m
2023-06-29T14:35:37.321Z DEBUG modem << [00:00:05.657,409] [0m<dbg> data_module: config_print_all: Movement timeout: 3600[0m
2023-06-29T14:35:37.323Z DEBUG modem << [00:00:05.665,039] [0m<dbg> data_module: config_print_all: Location timeout: 300[0m
2023-06-29T14:35:37.326Z DEBUG modem << [00:00:05.672,607] [0m<dbg> data_module: config_print_all: Accelerometer act threshold: 4.00[0m
2023-06-29T14:35:37.328Z DEBUG modem << [00:00:05.681,182] [0m<dbg> data_module: config_print_all: Accelerometer inact threshold: 4.00[0m
2023-06-29T14:35:37.330Z DEBUG modem << [00:00:05.689,941] [0m<dbg> data_module: config_print_all: Accelerometer inact timeout: 60.00[0m
2023-06-29T14:35:37.332Z DEBUG modem << [00:00:05.698,638] [0m<dbg> data_module: config_print_all: Requesting of neighbor cell data is enabled[0m
2023-06-29T14:35:37.334Z DEBUG modem << [00:00:05.708,068] [0m<dbg> data_module: config_print_all: Requesting of GNSS data is enabled[0m
2023-06-29T14:35:37.414Z DEBUG modem << [00:00:05.716,796] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
2023-06-29T14:35:37.419Z DEBUG modem << [00:00:05.723,815] [0m<dbg> data_module: requested_data_status_set: Data already encoded and sent, abort.[0m
2023-06-29T14:35:37.422Z DEBUG modem << [00:00:05.733,612] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED_DATA_READY[0m
2023-06-29T14:35:37.424Z DEBUG modem << [00:00:05.742,034] [0m<dbg> sensor_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
2023-06-29T14:35:37.426Z DEBUG modem << [00:00:05.751,190] [0m<dbg> sensor_module: on_state_init: on_state_init battery sampling...[0m
2023-06-29T14:35:38.813Z DEBUG modem << %CESQ: 54,2,24,3
2023-06-29T14:35:38.823Z DEBUG modem << [00:00:07.238,739] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -86[0m
2023-06-29T14:35:38.901Z DEBUG modem << +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:35:38.988Z DEBUG modem << [00:00:07.251,464] [0m<dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:35:38.994Z DEBUG modem << [0m
2023-06-29T14:35:39.000Z DEBUG modem << [00:00:07.261,444] [0m<dbg> lte_lc_helpers: parse_cereg: Network registration status: 2[0m
2023-06-29T14:35:39.002Z DEBUG modem << [00:00:07.269,561] [0m<dbg> lte_lc_helpers: parse_cereg: LTE mode: 9[0m
2023-06-29T14:35:39.005Z DEBUG modem << [00:00:07.276,092] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:39.008Z DEBUG modem << [00:00:07.284,637] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:39.010Z DEBUG modem << [00:00:07.293,914] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:39.012Z DEBUG modem << [00:00:07.302,612] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:39.014Z DEBUG modem << [00:00:07.311,370] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:39.016Z DEBUG modem << [00:00:07.320,129] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:39.017Z DEBUG modem << [00:00:07.327,423] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:39.096Z DEBUG modem << [00:00:07.335,998] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:39.101Z DEBUG modem << [00:00:07.344,757] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:39.106Z DEBUG modem << [00:00:07.353,515] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:39.111Z DEBUG modem << [00:00:07.362,274] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:39.114Z DEBUG modem << [00:00:07.371,032] [0m<dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 1447258, Tracking area: 40951[0m
2023-06-29T14:35:39.116Z DEBUG modem << [00:00:07.381,622] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:39.118Z DEBUG modem << [00:00:07.388,885] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:39.119Z DEBUG modem << [00:00:07.397,460] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:39.122Z DEBUG modem << [00:00:07.406,219] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:39.125Z DEBUG modem << [00:00:07.414,978] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:39.128Z DEBUG modem << [00:00:07.423,736] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:39.131Z DEBUG modem << [00:00:07.432,495] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:39.215Z DEBUG modem << [00:00:07.439,849] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-06-29T14:35:40.054Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:35:40.134Z DEBUG modem << Attempting to boot slot 0.
2023-06-29T14:35:40.220Z DEBUG modem << Attempting to boot from address 0x8200.
2023-06-29T14:35:40.225Z DEBUG modem << Verifying signature against key 0.
2023-06-29T14:35:40.230Z DEBUG modem << Hash: 0x0f...ad
2023-06-29T14:35:40.234Z DEBUG modem << Firmware signature verified.
2023-06-29T14:35:40.237Z DEBUG modem << Firmware version 5
2023-06-29T14:35:40.239Z DEBUG modem << Booting (0x8200).
2023-06-29T14:35:44.311Z DEBUG modem << [00:00:02.486,724] [0m<inf> ADXL362: NetFeasa: Accelerometer Self Test Starting...[0m
2023-06-29T14:35:45.370Z DEBUG modem << [00:00:03.548,278] [0m<inf> ADXL362: ACCELEROMETER SELF-TEST PASS[0m
2023-06-29T14:35:45.483Z DEBUG modem << [00:00:03.556,945] [0m<inf> ADXL362: INT1 set at GPIO port gpio@842500 pin 6[0m
2023-06-29T14:35:45.487Z DEBUG modem << [00:00:03.572,631] [0m<inf> bq274xx: Device ID: 0xffa5[0m
2023-06-29T14:35:45.491Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:35:45.494Z DEBUG modem << [00:00:03.581,878] [0m<inf> main: i setting pin high ----1111-----[0m
2023-06-29T14:35:46.411Z DEBUG modem << [00:00:04.588,287] [0m<inf> main: i set nrf select pin high -----222----[0m
2023-06-29T14:35:46.417Z DEBUG modem << [00:00:04.595,428] [0m<inf> app_event_manager: APP_EVT_START[0m
2023-06-29T14:35:46.509Z DEBUG modem << [00:00:04.601,959] [0m<dbg> data_module: state_set: State: STATE_CLOUD_DISCONNECTED[0m
2023-06-29T14:35:46.514Z DEBUG modem << [00:00:04.610,137] [0m<dbg> modem_module: state_set: State transition STATE_INIT --> STATE_DISCONNECTED[0m
2023-06-29T14:35:46.517Z DEBUG modem << [00:00:04.619,659] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2023-06-29T14:35:46.519Z DEBUG modem << [00:00:04.627,014] [0m<dbg> sensor_module: state_set: State: STATE_INIT[0m
2023-06-29T14:35:46.525Z DEBUG modem << [00:00:04.633,819] [0m<dbg> ext_sensors: sensor_settings_set: Settings key: state, size: 1, sizeofJobDef 1[0m
2023-06-29T14:35:46.527Z DEBUG modem << [00:00:04.643,646] [0m<dbg> ext_sensors: sensor_settings_set: SZ: 1[0m
2023-06-29T14:35:46.529Z DEBUG modem << [00:00:04.650,054] [0m<inf> ext_sensors: yic status: 1[0m
2023-06-29T14:35:46.531Z DEBUG modem << [00:00:04.655,395] [0m<dbg> ext_sensors: load_sensor_settings: SETTINGS: 0[0m
2023-06-29T14:35:46.534Z DEBUG modem << [00:00:04.662,384] [0m<dbg> ext_sensors: ext_sensors_init: ACCEL adxl362@0 initialized![0m
2023-06-29T14:35:46.537Z DEBUG modem << [00:00:04.670,898] [0m<dbg> lte_lc: init_and_config: System mode (6) and preference (4) are already configured[0m
2023-06-29T14:35:46.540Z DEBUG modem << [00:00:04.683,410] [0m<dbg> ext_sensors: ext_sensors_init: CONFIGURE ACCCCCCC1111[0m
2023-06-29T14:35:46.637Z DEBUG modem << [00:00:04.691,955] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:35:46.642Z DEBUG modem << [00:00:04.702,056] [0m<dbg> aws_iot_integration: cloud_wrap_init: The Asset Tracker v2 has started[0m
2023-06-29T14:35:46.646Z DEBUG modem << [00:00:04.711,242] [0m<dbg> aws_iot_integration: cloud_wrap_init: Version: 0.0.18[0m
2023-06-29T14:35:46.744Z DEBUG modem << [00:00:04.719,329] [0m<dbg> aws_iot_integration: cloud_wrap_init: Client ID: 351516173341025[0m
2023-06-29T14:35:46.748Z DEBUG modem << [00:00:04.728,179] [0m<dbg> aws_iot_integration: cloud_wrap_init: Cloud: AWS IoT[0m
2023-06-29T14:35:46.756Z DEBUG modem << [00:00:04.736,328] [0m<dbg> aws_iot_integration: cloud_wrap_init: Endpoint: a2hkw2qiy12x93-ats.iot.eu-west-1.amazonaws.com[0m
2023-06-29T14:35:46.759Z DEBUG modem << [00:00:04.747,863] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:35:46.761Z DEBUG modem << [00:00:04.758,758] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 932000.000000V[0m
2023-06-29T14:35:46.763Z DEBUG modem << [00:00:04.769,439] [0m<dbg> ext_sensors: ext_sensors_init: bq27z561@55 fuel gauge initialized succesfully 393V [0m
2023-06-29T14:35:46.765Z DEBUG modem << [00:00:04.779,693] [0m<dbg> ext_sensors: ext_sensors_init: Set up hall-effect at gpio@842500 pin 21[0m
2023-06-29T14:35:46.768Z DEBUG modem << [00:00:04.788,848] [0m<dbg> ext_sensors: config_gnss: GNSS CONFIG ALREADY SET[0m
2023-06-29T14:35:46.772Z DEBUG modem << [00:00:04.796,325] [0m<dbg> sensor_module: gnss_client_callback: GNSS_SEARCH_EVT_STARTED[0m
2023-06-29T14:35:46.774Z DEBUG modem << [00:00:04.805,236] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 932000.000000V[0m
2023-06-29T14:35:46.776Z DEBUG modem << [00:00:04.815,948] [0m<inf> app_event_manager: SENSOR_EVT_BATTERY_DATA_READY[0m
2023-06-29T14:35:46.778Z DEBUG modem << [00:00:04.823,547] [0m<dbg> modem_module: configure_low_power: PSM requested[0m
2023-06-29T14:35:46.877Z DEBUG modem << [00:00:04.865,417] [0m<dbg> lte_lc: lte_lc_func_mode_set: CFUN monitor callback: 0x52219[0m
2023-06-29T14:35:46.880Z DEBUG modem << [00:00:04.874,328] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2023-06-29T14:35:46.885Z DEBUG modem << [00:00:04.881,774] [0m<dbg> modem_module: state_set: State transition STATE_DISCONNECTED --> STATE_CONNECTING[0m
2023-06-29T14:35:47.437Z DEBUG modem << [00:00:05.610,137] [0m<dbg> data_module: setup: Failed retrieveing the device configuration from flash in time[0m
2023-06-29T14:35:47.442Z DEBUG modem << [00:00:05.620,269] [0m<inf> data_module: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:35:47.449Z DEBUG modem << [00:00:05.626,586] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:35:47.548Z DEBUG modem << [00:00:05.634,368] [0m<dbg> data_module: config_print_all: Device mode: Active[0m
2023-06-29T14:35:47.554Z DEBUG modem << [00:00:05.641,693] [0m<dbg> data_module: config_print_all: Active wait timeout: 180[0m
2023-06-29T14:35:47.559Z DEBUG modem << [00:00:05.649,505] [0m<dbg> data_module: config_print_all: Movement resolution: 120[0m
2023-06-29T14:35:47.562Z DEBUG modem << [00:00:05.657,318] [0m<dbg> data_module: config_print_all: Movement timeout: 3600[0m
2023-06-29T14:35:47.565Z DEBUG modem << [00:00:05.664,947] [0m<dbg> data_module: config_print_all: Location timeout: 300[0m
2023-06-29T14:35:47.567Z DEBUG modem << [00:00:05.672,515] [0m<dbg> data_module: config_print_all: Accelerometer act threshold: 4.00[0m
2023-06-29T14:35:47.570Z DEBUG modem << [00:00:05.681,091] [0m<dbg> data_module: config_print_all: Accelerometer inact threshold: 4.00[0m
2023-06-29T14:35:47.573Z DEBUG modem << [00:00:05.689,849] [0m<dbg> data_module: config_print_all: Accelerometer inact timeout: 60.00[0m
2023-06-29T14:35:47.577Z DEBUG modem << [00:00:05.698,516] [0m<dbg> data_module: config_print_all: Requesting of neighbor cell data is enabled[0m
2023-06-29T14:35:47.580Z DEBUG modem << [00:00:05.707,977] [0m<dbg> data_module: config_print_all: Requesting of GNSS data is enabled[0m
2023-06-29T14:35:47.583Z DEBUG modem << [00:00:05.716,674] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
2023-06-29T14:35:47.691Z DEBUG modem << [00:00:05.723,693] [0m<dbg> data_module: requested_data_status_set: Data already encoded and sent, abort.[0m
2023-06-29T14:35:47.698Z DEBUG modem << [00:00:05.733,489] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED_DATA_READY[0m
2023-06-29T14:35:47.705Z DEBUG modem << [00:00:05.741,912] [0m<dbg> sensor_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
2023-06-29T14:35:47.707Z DEBUG modem << [00:00:05.751,068] [0m<dbg> sensor_module: on_state_init: on_state_init battery sampling...[0m
2023-06-29T14:35:49.052Z DEBUG modem << %CESQ: 52,2,24,3
2023-06-29T14:35:49.160Z DEBUG modem << [00:00:07.236,694] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -88[0m
2023-06-29T14:35:49.255Z DEBUG modem << +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:35:49.268Z DEBUG modem << [00:00:07.249,420] [0m<dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:35:49.271Z DEBUG modem << [0m
2023-06-29T14:35:49.274Z DEBUG modem << [00:00:07.259,368] [0m<dbg> lte_lc_helpers: parse_cereg: Network registration status: 2[0m
2023-06-29T14:35:49.277Z DEBUG modem << [00:00:07.267,486] [0m<dbg> lte_lc_helpers: parse_cereg: LTE mode: 9[0m
2023-06-29T14:35:49.281Z DEBUG modem << [00:00:07.274,047] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:49.284Z DEBUG modem << [00:00:07.282,592] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:49.286Z DEBUG modem << [00:00:07.291,839] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:49.288Z DEBUG modem << [00:00:07.300,567] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:49.290Z DEBUG modem << [00:00:07.309,326] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:49.292Z DEBUG modem << [00:00:07.318,054] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:49.294Z DEBUG modem << [00:00:07.325,378] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:49.297Z DEBUG modem << [00:00:07.333,953] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:49.299Z DEBUG modem << [00:00:07.342,681] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:49.391Z DEBUG modem << [00:00:07.351,470] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:49.399Z DEBUG modem << [00:00:07.360,198] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:49.403Z DEBUG modem << [00:00:07.368,988] [0m<dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 1447258, Tracking area: 40951[0m
2023-06-29T14:35:49.405Z DEBUG modem << [00:00:07.379,577] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:49.409Z DEBUG modem << [00:00:07.386,840] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:49.412Z DEBUG modem << [00:00:07.395,416] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:49.417Z DEBUG modem << [00:00:07.404,174] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:49.422Z DEBUG modem << [00:00:07.412,933] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:49.425Z DEBUG modem << [00:00:07.421,691] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:49.427Z DEBUG modem << [00:00:07.430,450] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:49.429Z DEBUG modem << [00:00:07.437,835] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-06-29T14:35:50.295Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:35:50.299Z DEBUG modem << Attempting to boot slot 0.
2023-06-29T14:35:50.301Z DEBUG modem << Attempting to boot from address 0x8200.
2023-06-29T14:35:50.304Z DEBUG modem << Verifying signature against key 0.
2023-06-29T14:35:50.307Z DEBUG modem << Hash: 0x0f...ad
2023-06-29T14:35:50.407Z DEBUG modem << Firmware signature verified.
2023-06-29T14:35:50.413Z DEBUG modem << Firmware version 5
2023-06-29T14:35:50.419Z DEBUG modem << Booting (0x8200).
2023-06-29T14:35:54.550Z DEBUG modem << [00:00:02.486,755] [0m<inf> ADXL362: NetFeasa: Accelerometer Self Test Starting...[0m
2023-06-29T14:35:55.610Z DEBUG modem << [00:00:03.548,309] [0m<inf> ADXL362: ACCELEROMETER SELF-TEST PASS[0m
2023-06-29T14:35:55.714Z DEBUG modem << [00:00:03.556,976] [0m<inf> ADXL362: INT1 set at GPIO port gpio@842500 pin 6[0m
2023-06-29T14:35:55.718Z DEBUG modem << [00:00:03.572,662] [0m<inf> bq274xx: Device ID: 0xffa5[0m
2023-06-29T14:35:55.723Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:35:55.726Z DEBUG modem << [00:00:03.581,909] [0m<inf> main: i setting pin high ----1111-----[0m
2023-06-29T14:35:56.650Z DEBUG modem << [00:00:04.588,317] [0m<inf> main: i set nrf select pin high -----222----[0m
2023-06-29T14:35:56.656Z DEBUG modem << [00:00:04.595,458] [0m<inf> app_event_manager: APP_EVT_START[0m
2023-06-29T14:35:56.760Z DEBUG modem << [00:00:04.601,989] [0m<dbg> data_module: state_set: State: STATE_CLOUD_DISCONNECTED[0m
2023-06-29T14:35:56.765Z DEBUG modem << [00:00:04.610,168] [0m<dbg> modem_module: state_set: State transition STATE_INIT --> STATE_DISCONNECTED[0m
2023-06-29T14:35:56.772Z DEBUG modem << [00:00:04.619,689] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2023-06-29T14:35:56.776Z DEBUG modem << [00:00:04.627,014] [0m<dbg> sensor_module: state_set: State: STATE_INIT[0m
2023-06-29T14:35:56.779Z DEBUG modem << [00:00:04.633,850] [0m<dbg> ext_sensors: sensor_settings_set: Settings key: state, size: 1, sizeofJobDef 1[0m
2023-06-29T14:35:56.782Z DEBUG modem << [00:00:04.643,676] [0m<dbg> ext_sensors: sensor_settings_set: SZ: 1[0m
2023-06-29T14:35:56.784Z DEBUG modem << [00:00:04.650,085] [0m<inf> ext_sensors: yic status: 1[0m
2023-06-29T14:35:56.787Z DEBUG modem << [00:00:04.655,426] [0m<dbg> ext_sensors: load_sensor_settings: SETTINGS: 0[0m
2023-06-29T14:35:56.790Z DEBUG modem << [00:00:04.662,384] [0m<dbg> ext_sensors: ext_sensors_init: ACCEL adxl362@0 initialized![0m
2023-06-29T14:35:56.793Z DEBUG modem << [00:00:04.670,928] [0m<dbg> lte_lc: init_and_config: System mode (6) and preference (4) are already configured[0m
2023-06-29T14:35:56.796Z DEBUG modem << [00:00:04.683,410] [0m<dbg> ext_sensors: ext_sensors_init: CONFIGURE ACCCCCCC1111[0m
2023-06-29T14:35:56.799Z DEBUG modem << [00:00:04.691,955] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:35:56.915Z DEBUG modem << [00:00:04.702,056] [0m<dbg> aws_iot_integration: cloud_wrap_init: The Asset Tracker v2 has started[0m
2023-06-29T14:35:56.921Z DEBUG modem << [00:00:04.711,242] [0m<dbg> aws_iot_integration: cloud_wrap_init: Version: 0.0.18[0m
2023-06-29T14:35:56.924Z DEBUG modem << [00:00:04.719,299] [0m<dbg> aws_iot_integration: cloud_wrap_init: Client ID: 351516173341025[0m
2023-06-29T14:35:56.927Z DEBUG modem << [00:00:04.728,149] [0m<dbg> aws_iot_integration: cloud_wrap_init: Cloud: AWS IoT[0m
2023-06-29T14:35:57.035Z DEBUG modem << [00:00:04.736,297] [0m<dbg> aws_iot_integration: cloud_wrap_init: Endpoint: a2hkw2qiy12x93-ats.iot.eu-west-1.amazonaws.com[0m
2023-06-29T14:35:57.039Z DEBUG modem << [00:00:04.747,833] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:35:57.047Z DEBUG modem << [00:00:04.758,728] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 289000.000000V[0m
2023-06-29T14:35:57.049Z DEBUG modem << [00:00:04.769,378] [0m<dbg> ext_sensors: ext_sensors_init: bq27z561@55 fuel gauge initialized succesfully 428V [0m
2023-06-29T14:35:57.051Z DEBUG modem << [00:00:04.779,602] [0m<dbg> ext_sensors: ext_sensors_init: Set up hall-effect at gpio@842500 pin 21[0m
2023-06-29T14:35:57.053Z DEBUG modem << [00:00:04.788,757] [0m<dbg> ext_sensors: config_gnss: GNSS CONFIG ALREADY SET[0m
2023-06-29T14:35:57.059Z DEBUG modem << [00:00:04.796,234] [0m<dbg> sensor_module: gnss_client_callback: GNSS_SEARCH_EVT_STARTED[0m
2023-06-29T14:35:57.062Z DEBUG modem << [00:00:04.805,175] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 289000.000000V[0m
2023-06-29T14:35:57.063Z DEBUG modem << [00:00:04.815,826] [0m<inf> app_event_manager: SENSOR_EVT_BATTERY_DATA_READY[0m
2023-06-29T14:35:57.066Z DEBUG modem << [00:00:04.823,394] [0m<dbg> modem_module: configure_low_power: PSM requested[0m
2023-06-29T14:35:57.069Z DEBUG modem << [00:00:04.865,264] [0m<dbg> lte_lc: lte_lc_func_mode_set: CFUN monitor callback: 0x52219[0m
2023-06-29T14:35:57.194Z DEBUG modem << [00:00:04.874,176] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2023-06-29T14:35:57.208Z DEBUG modem << [00:00:04.881,591] [0m<dbg> modem_module: state_set: State transition STATE_DISCONNECTED --> STATE_CONNECTING[0m
2023-06-29T14:35:57.675Z DEBUG modem << [00:00:05.610,168] [0m<dbg> data_module: setup: Failed retrieveing the device configuration from flash in time[0m
2023-06-29T14:35:57.681Z DEBUG modem << [00:00:05.620,300] [0m<inf> data_module: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:35:57.688Z DEBUG modem << [00:00:05.626,647] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:35:57.786Z DEBUG modem << [00:00:05.634,399] [0m<dbg> data_module: config_print_all: Device mode: Active[0m
2023-06-29T14:35:57.792Z DEBUG modem << [00:00:05.641,723] [0m<dbg> data_module: config_print_all: Active wait timeout: 180[0m
2023-06-29T14:35:57.796Z DEBUG modem << [00:00:05.649,536] [0m<dbg> data_module: config_print_all: Movement resolution: 120[0m
2023-06-29T14:35:57.798Z DEBUG modem << [00:00:05.657,348] [0m<dbg> data_module: config_print_all: Movement timeout: 3600[0m
2023-06-29T14:35:57.800Z DEBUG modem << [00:00:05.664,978] [0m<dbg> data_module: config_print_all: Location timeout: 300[0m
2023-06-29T14:35:57.802Z DEBUG modem << [00:00:05.672,515] [0m<dbg> data_module: config_print_all: Accelerometer act threshold: 4.00[0m
2023-06-29T14:35:57.805Z DEBUG modem << [00:00:05.681,091] [0m<dbg> data_module: config_print_all: Accelerometer inact threshold: 4.00[0m
2023-06-29T14:35:57.808Z DEBUG modem << [00:00:05.689,849] [0m<dbg> data_module: config_print_all: Accelerometer inact timeout: 60.00[0m
2023-06-29T14:35:57.810Z DEBUG modem << [00:00:05.698,516] [0m<dbg> data_module: config_print_all: Requesting of neighbor cell data is enabled[0m
2023-06-29T14:35:57.812Z DEBUG modem << [00:00:05.707,977] [0m<dbg> data_module: config_print_all: Requesting of GNSS data is enabled[0m
2023-06-29T14:35:57.815Z DEBUG modem << [00:00:05.716,705] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
2023-06-29T14:35:57.916Z DEBUG modem << [00:00:05.723,693] [0m<dbg> data_module: requested_data_status_set: Data already encoded and sent, abort.[0m
2023-06-29T14:35:57.921Z DEBUG modem << [00:00:05.733,489] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED_DATA_READY[0m
2023-06-29T14:35:57.926Z DEBUG modem << [00:00:05.741,912] [0m<dbg> sensor_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
2023-06-29T14:35:57.929Z DEBUG modem << [00:00:05.751,068] [0m<dbg> sensor_module: on_state_init: on_state_init battery sampling...[0m
2023-06-29T14:35:59.293Z DEBUG modem << %CESQ: 53,2,23,3
2023-06-29T14:35:59.412Z DEBUG modem << [00:00:07.237,579] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -87[0m
2023-06-29T14:35:59.419Z DEBUG modem << +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:35:59.429Z DEBUG modem << [00:00:07.250,305] [0m<dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:35:59.434Z DEBUG modem << [0m
2023-06-29T14:35:59.437Z DEBUG modem << [00:00:07.260,284] [0m<dbg> lte_lc_helpers: parse_cereg: Network registration status: 2[0m
2023-06-29T14:35:59.441Z DEBUG modem << [00:00:07.268,402] [0m<dbg> lte_lc_helpers: parse_cereg: LTE mode: 9[0m
2023-06-29T14:35:59.443Z DEBUG modem << [00:00:07.274,932] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:59.446Z DEBUG modem << [00:00:07.283,477] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:59.449Z DEBUG modem << [00:00:07.292,724] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:59.452Z DEBUG modem << [00:00:07.301,452] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:59.454Z DEBUG modem << [00:00:07.310,211] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:59.457Z DEBUG modem << [00:00:07.318,939] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:59.460Z DEBUG modem << [00:00:07.326,263] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:59.462Z DEBUG modem << [00:00:07.334,808] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:59.464Z DEBUG modem << [00:00:07.343,566] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:59.570Z DEBUG modem << [00:00:07.352,325] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:59.576Z DEBUG modem << [00:00:07.361,083] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:59.580Z DEBUG modem << [00:00:07.369,842] [0m<dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 1447258, Tracking area: 40951[0m
2023-06-29T14:35:59.583Z DEBUG modem << [00:00:07.380,432] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:59.588Z DEBUG modem << [00:00:07.387,695] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:35:59.591Z DEBUG modem << [00:00:07.396,270] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:35:59.686Z DEBUG modem << [00:00:07.405,029] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:35:59.691Z DEBUG modem << [00:00:07.413,787] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:35:59.695Z DEBUG modem << [00:00:07.422,546] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:35:59.698Z DEBUG modem << [00:00:07.431,274] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:35:59.701Z DEBUG modem << [00:00:07.438,659] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-06-29T14:36:00.534Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:36:00.537Z DEBUG modem << Attempting to boot slot 0.
2023-06-29T14:36:00.542Z DEBUG modem << Attempting to boot from address 0x8200.
2023-06-29T14:36:00.545Z DEBUG modem << Verifying signature against key 0.
2023-06-29T14:36:00.548Z DEBUG modem << Hash: 0x0f...ad
2023-06-29T14:36:00.644Z DEBUG modem << Firmware signature verified.
2023-06-29T14:36:00.648Z DEBUG modem << Firmware version 5
2023-06-29T14:36:00.656Z DEBUG modem << Booting (0x8200).
2023-06-29T14:36:04.785Z DEBUG modem << [00:00:02.486,755] [0m<inf> ADXL362: NetFeasa: Accelerometer Self Test Starting...[0m
2023-06-29T14:36:05.845Z DEBUG modem << [00:00:03.548,339] [0m<inf> ADXL362: ACCELEROMETER SELF-TEST PASS[0m
2023-06-29T14:36:05.948Z DEBUG modem << [00:00:03.557,006] [0m<inf> ADXL362: INT1 set at GPIO port gpio@842500 pin 6[0m
2023-06-29T14:36:05.954Z DEBUG modem << [00:00:03.572,692] [0m<inf> bq274xx: Device ID: 0xffa5[0m
2023-06-29T14:36:05.958Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:36:05.961Z DEBUG modem << [00:00:03.581,909] [0m<inf> main: i setting pin high ----1111-----[0m
2023-06-29T14:36:06.886Z DEBUG modem << [00:00:04.588,317] [0m<inf> main: i set nrf select pin high -----222----[0m
2023-06-29T14:36:06.892Z DEBUG modem << [00:00:04.595,458] [0m<inf> app_event_manager: APP_EVT_START[0m
2023-06-29T14:36:07.013Z DEBUG modem << [00:00:04.601,989] [0m<dbg> data_module: state_set: State: STATE_CLOUD_DISCONNECTED[0m
2023-06-29T14:36:07.020Z DEBUG modem << [00:00:04.610,168] [0m<dbg> modem_module: state_set: State transition STATE_INIT --> STATE_DISCONNECTED[0m
2023-06-29T14:36:07.026Z DEBUG modem << [00:00:04.619,689] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2023-06-29T14:36:07.028Z DEBUG modem << [00:00:04.627,014] [0m<dbg> sensor_module: state_set: State: STATE_INIT[0m
2023-06-29T14:36:07.033Z DEBUG modem << [00:00:04.633,850] [0m<dbg> ext_sensors: sensor_settings_set: Settings key: state, size: 1, sizeofJobDef 1[0m
2023-06-29T14:36:07.036Z DEBUG modem << [00:00:04.643,676] [0m<dbg> ext_sensors: sensor_settings_set: SZ: 1[0m
2023-06-29T14:36:07.038Z DEBUG modem << [00:00:04.650,085] [0m<inf> ext_sensors: yic status: 1[0m
2023-06-29T14:36:07.041Z DEBUG modem << [00:00:04.655,426] [0m<dbg> ext_sensors: load_sensor_settings: SETTINGS: 0[0m
2023-06-29T14:36:07.044Z DEBUG modem << [00:00:04.662,384] [0m<dbg> ext_sensors: ext_sensors_init: ACCEL adxl362@0 initialized![0m
2023-06-29T14:36:07.047Z DEBUG modem << [00:00:04.670,898] [0m<dbg> lte_lc: init_and_config: System mode (6) and preference (4) are already configured[0m
2023-06-29T14:36:07.049Z DEBUG modem << [00:00:04.683,410] [0m<dbg> ext_sensors: ext_sensors_init: CONFIGURE ACCCCCCC1111[0m
2023-06-29T14:36:07.052Z DEBUG modem << [00:00:04.691,955] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:36:07.055Z DEBUG modem << [00:00:04.702,056] [0m<dbg> aws_iot_integration: cloud_wrap_init: The Asset Tracker v2 has started[0m
2023-06-29T14:36:07.057Z DEBUG modem << [00:00:04.711,242] [0m<dbg> aws_iot_integration: cloud_wrap_init: Version: 0.0.18[0m
2023-06-29T14:36:07.185Z DEBUG modem << [00:00:04.719,299] [0m<dbg> aws_iot_integration: cloud_wrap_init: Client ID: 351516173341025[0m
2023-06-29T14:36:07.193Z DEBUG modem << [00:00:04.728,149] [0m<dbg> aws_iot_integration: cloud_wrap_init: Cloud: AWS IoT[0m
2023-06-29T14:36:07.197Z DEBUG modem << [00:00:04.736,297] [0m<dbg> aws_iot_integration: cloud_wrap_init: Endpoint: a2hkw2qiy12x93-ats.iot.eu-west-1.amazonaws.com[0m
2023-06-29T14:36:07.199Z DEBUG modem << [00:00:04.747,802] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:36:07.319Z DEBUG modem << [00:00:04.758,728] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 329000.000000V[0m
2023-06-29T14:36:07.325Z DEBUG modem << [00:00:04.769,378] [0m<dbg> ext_sensors: ext_sensors_init: bq27z561@55 fuel gauge initialized succesfully 432V [0m
2023-06-29T14:36:07.333Z DEBUG modem << [00:00:04.779,632] [0m<dbg> ext_sensors: ext_sensors_init: Set up hall-effect at gpio@842500 pin 21[0m
2023-06-29T14:36:07.335Z DEBUG modem << [00:00:04.788,787] [0m<dbg> ext_sensors: config_gnss: GNSS CONFIG ALREADY SET[0m
2023-06-29T14:36:07.339Z DEBUG modem << [00:00:04.796,234] [0m<dbg> sensor_module: gnss_client_callback: GNSS_SEARCH_EVT_STARTED[0m
2023-06-29T14:36:07.341Z DEBUG modem << [00:00:04.805,175] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 329000.000000V[0m
2023-06-29T14:36:07.347Z DEBUG modem << [00:00:04.815,887] [0m<inf> app_event_manager: SENSOR_EVT_BATTERY_DATA_READY[0m
2023-06-29T14:36:07.350Z DEBUG modem << [00:00:04.823,455] [0m<dbg> modem_module: configure_low_power: PSM requested[0m
2023-06-29T14:36:07.352Z DEBUG modem << [00:00:04.865,356] [0m<dbg> lte_lc: lte_lc_func_mode_set: CFUN monitor callback: 0x52219[0m
2023-06-29T14:36:07.354Z DEBUG modem << [00:00:04.874,267] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2023-06-29T14:36:07.356Z DEBUG modem << [00:00:04.881,683] [0m<dbg> modem_module: state_set: State transition STATE_DISCONNECTED --> STATE_CONNECTING[0m
2023-06-29T14:36:07.911Z DEBUG modem << [00:00:05.610,168] [0m<dbg> data_module: setup: Failed retrieveing the device configuration from flash in time[0m
2023-06-29T14:36:08.008Z DEBUG modem << [00:00:05.620,300] [0m<inf> data_module: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:36:08.014Z DEBUG modem << [00:00:05.626,617] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:36:08.019Z DEBUG modem << [00:00:05.634,399] [0m<dbg> data_module: config_print_all: Device mode: Active[0m
2023-06-29T14:36:08.022Z DEBUG modem << [00:00:05.641,723] [0m<dbg> data_module: config_print_all: Active wait timeout: 180[0m
2023-06-29T14:36:08.025Z DEBUG modem << [00:00:05.649,505] [0m<dbg> data_module: config_print_all: Movement resolution: 120[0m
2023-06-29T14:36:08.028Z DEBUG modem << [00:00:05.657,318] [0m<dbg> data_module: config_print_all: Movement timeout: 3600[0m
2023-06-29T14:36:08.031Z DEBUG modem << [00:00:05.664,947] [0m<dbg> data_module: config_print_all: Location timeout: 300[0m
2023-06-29T14:36:08.033Z DEBUG modem << [00:00:05.672,485] [0m<dbg> data_module: config_print_all: Accelerometer act threshold: 4.00[0m
2023-06-29T14:36:08.035Z DEBUG modem << [00:00:05.681,091] [0m<dbg> data_module: config_print_all: Accelerometer inact threshold: 4.00[0m
2023-06-29T14:36:08.038Z DEBUG modem << [00:00:05.689,819] [0m<dbg> data_module: config_print_all: Accelerometer inact timeout: 60.00[0m
2023-06-29T14:36:08.040Z DEBUG modem << [00:00:05.698,486] [0m<dbg> data_module: config_print_all: Requesting of neighbor cell data is enabled[0m
2023-06-29T14:36:08.042Z DEBUG modem << [00:00:05.707,946] [0m<dbg> data_module: config_print_all: Requesting of GNSS data is enabled[0m
2023-06-29T14:36:08.146Z DEBUG modem << [00:00:05.716,674] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
2023-06-29T14:36:08.150Z DEBUG modem << [00:00:05.723,663] [0m<dbg> data_module: requested_data_status_set: Data already encoded and sent, abort.[0m
2023-06-29T14:36:08.155Z DEBUG modem << [00:00:05.733,459] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED_DATA_READY[0m
2023-06-29T14:36:08.157Z DEBUG modem << [00:00:05.741,882] [0m<dbg> sensor_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
2023-06-29T14:36:08.159Z DEBUG modem << [00:00:05.751,037] [0m<dbg> sensor_module: on_state_init: on_state_init battery sampling...[0m
2023-06-29T14:36:09.532Z DEBUG modem << %CESQ: 50,2,22,3
2023-06-29T14:36:09.651Z DEBUG modem << [00:00:07.241,729] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -90[0m
2023-06-29T14:36:09.655Z DEBUG modem << +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:36:09.668Z DEBUG modem << [00:00:07.254,455] [0m<dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:36:09.670Z DEBUG modem << [0m
2023-06-29T14:36:09.673Z DEBUG modem << [00:00:07.264,404] [0m<dbg> lte_lc_helpers: parse_cereg: Network registration status: 2[0m
2023-06-29T14:36:09.677Z DEBUG modem << [00:00:07.272,521] [0m<dbg> lte_lc_helpers: parse_cereg: LTE mode: 9[0m
2023-06-29T14:36:09.680Z DEBUG modem << [00:00:07.279,083] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:09.683Z DEBUG modem << [00:00:07.287,597] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:09.687Z DEBUG modem << [00:00:07.296,875] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:09.691Z DEBUG modem << [00:00:07.305,572] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:09.693Z DEBUG modem << [00:00:07.314,331] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:09.695Z DEBUG modem << [00:00:07.323,059] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:09.697Z DEBUG modem << [00:00:07.330,383] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:09.699Z DEBUG modem << [00:00:07.338,958] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:09.701Z DEBUG modem << [00:00:07.347,686] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:09.830Z DEBUG modem << [00:00:07.356,445] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:09.840Z DEBUG modem << [00:00:07.365,203] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:09.845Z DEBUG modem << [00:00:07.373,962] [0m<dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 1447258, Tracking area: 40951[0m
2023-06-29T14:36:09.850Z DEBUG modem << [00:00:07.384,552] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:09.854Z DEBUG modem << [00:00:07.391,815] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:09.858Z DEBUG modem << [00:00:07.400,390] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:10.010Z DEBUG modem << [00:00:07.409,149] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:10.016Z DEBUG modem << [00:00:07.417,907] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:10.018Z DEBUG modem << [00:00:07.426,666] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:10.021Z DEBUG modem << [00:00:07.435,394] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:10.023Z DEBUG modem << [00:00:07.442,779] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-06-29T14:36:10.774Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:36:10.778Z DEBUG modem << Attempting to boot slot 0.
2023-06-29T14:36:10.781Z DEBUG modem << Attempting to boot from address 0x8200.
2023-06-29T14:36:10.784Z DEBUG modem << Verifying signature against key 0.
2023-06-29T14:36:10.789Z DEBUG modem << Hash: 0x0f...ad
2023-06-29T14:36:10.896Z DEBUG modem << Firmware signature verified.
2023-06-29T14:36:10.901Z DEBUG modem << Firmware version 5
2023-06-29T14:36:10.904Z DEBUG modem << Booting (0x8200).
2023-06-29T14:36:15.031Z DEBUG modem << [00:00:02.486,755] [0m<inf> ADXL362: NetFeasa: Accelerometer Self Test Starting...[0m
2023-06-29T14:36:16.092Z DEBUG modem << [00:00:03.548,309] [0m<inf> ADXL362: ACCELEROMETER SELF-TEST PASS[0m
2023-06-29T14:36:16.100Z DEBUG modem << [00:00:03.556,976] [0m<inf> ADXL362: INT1 set at GPIO port gpio@842500 pin 6[0m
2023-06-29T14:36:16.220Z DEBUG modem << [00:00:03.572,662] [0m<inf> bq274xx: Device ID: 0xffa5[0m
2023-06-29T14:36:16.226Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:36:16.231Z DEBUG modem << [00:00:03.581,878] [0m<inf> main: i setting pin high ----1111-----[0m
2023-06-29T14:36:17.131Z DEBUG modem << [00:00:04.588,317] [0m<inf> main: i set nrf select pin high -----222----[0m
2023-06-29T14:36:17.280Z DEBUG modem << [00:00:04.595,458] [0m<inf> app_event_manager: APP_EVT_START[0m
2023-06-29T14:36:17.287Z DEBUG modem << [00:00:04.601,989] [0m<dbg> data_module: state_set: State: STATE_CLOUD_DISCONNECTED[0m
2023-06-29T14:36:17.294Z DEBUG modem << [00:00:04.610,168] [0m<dbg> modem_module: state_set: State transition STATE_INIT --> STATE_DISCONNECTED[0m
2023-06-29T14:36:17.297Z DEBUG modem << [00:00:04.619,689] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2023-06-29T14:36:17.301Z DEBUG modem << [00:00:04.627,014] [0m<dbg> sensor_module: state_set: State: STATE_INIT[0m
2023-06-29T14:36:17.305Z DEBUG modem << [00:00:04.633,850] [0m<dbg> ext_sensors: sensor_settings_set: Settings key: state, size: 1, sizeofJobDef 1[0m
2023-06-29T14:36:17.309Z DEBUG modem << [00:00:04.643,676] [0m<dbg> ext_sensors: sensor_settings_set: SZ: 1[0m
2023-06-29T14:36:17.312Z DEBUG modem << [00:00:04.650,085] [0m<inf> ext_sensors: yic status: 1[0m
2023-06-29T14:36:17.315Z DEBUG modem << [00:00:04.655,426] [0m<dbg> ext_sensors: load_sensor_settings: SETTINGS: 0[0m
2023-06-29T14:36:17.319Z DEBUG modem << [00:00:04.662,414] [0m<dbg> ext_sensors: ext_sensors_init: ACCEL adxl362@0 initialized![0m
2023-06-29T14:36:17.321Z DEBUG modem << [00:00:04.670,928] [0m<dbg> lte_lc: init_and_config: System mode (6) and preference (4) are already configured[0m
2023-06-29T14:36:17.323Z DEBUG modem << [00:00:04.683,441] [0m<dbg> ext_sensors: ext_sensors_init: CONFIGURE ACCCCCCC1111[0m
2023-06-29T14:36:17.326Z DEBUG modem << [00:00:04.691,955] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:36:17.328Z DEBUG modem << [00:00:04.702,056] [0m<dbg> aws_iot_integration: cloud_wrap_init: The Asset Tracker v2 has started[0m
2023-06-29T14:36:17.331Z DEBUG modem << [00:00:04.711,242] [0m<dbg> aws_iot_integration: cloud_wrap_init: Version: 0.0.18[0m
2023-06-29T14:36:17.333Z DEBUG modem << [00:00:04.719,329] [0m<dbg> aws_iot_integration: cloud_wrap_init: Client ID: 351516173341025[0m
2023-06-29T14:36:17.336Z DEBUG modem << [00:00:04.728,149] [0m<dbg> aws_iot_integration: cloud_wrap_init: Cloud: AWS IoT[0m
2023-06-29T14:36:17.457Z DEBUG modem << [00:00:04.736,297] [0m<dbg> aws_iot_integration: cloud_wrap_init: Endpoint: a2hkw2qiy12x93-ats.iot.eu-west-1.amazonaws.com[0m
2023-06-29T14:36:17.462Z DEBUG modem << [00:00:04.747,833] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:36:17.466Z DEBUG modem << [00:00:04.758,728] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 330000.000000V[0m
2023-06-29T14:36:17.468Z DEBUG modem << [00:00:04.769,409] [0m<dbg> ext_sensors: ext_sensors_init: bq27z561@55 fuel gauge initialized succesfully 433V [0m
2023-06-29T14:36:17.473Z DEBUG modem << [00:00:04.779,632] [0m<dbg> ext_sensors: ext_sensors_init: Set up hall-effect at gpio@842500 pin 21[0m
2023-06-29T14:36:17.477Z DEBUG modem << [00:00:04.788,787] [0m<dbg> ext_sensors: config_gnss: GNSS CONFIG ALREADY SET[0m
2023-06-29T14:36:17.586Z DEBUG modem << [00:00:04.796,264] [0m<dbg> sensor_module: gnss_client_callback: GNSS_SEARCH_EVT_STARTED[0m
2023-06-29T14:36:17.592Z DEBUG modem << [00:00:04.805,206] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 330000.000000V[0m
2023-06-29T14:36:17.596Z DEBUG modem << [00:00:04.815,856] [0m<inf> app_event_manager: SENSOR_EVT_BATTERY_DATA_READY[0m
2023-06-29T14:36:17.599Z DEBUG modem << [00:00:04.823,425] [0m<dbg> modem_module: configure_low_power: PSM requested[0m
2023-06-29T14:36:17.602Z DEBUG modem << [00:00:04.865,295] [0m<dbg> lte_lc: lte_lc_func_mode_set: CFUN monitor callback: 0x52219[0m
2023-06-29T14:36:17.606Z DEBUG modem << [00:00:04.874,206] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2023-06-29T14:36:17.609Z DEBUG modem << [00:00:04.881,652] [0m<dbg> modem_module: state_set: State transition STATE_DISCONNECTED --> STATE_CONNECTING[0m
2023-06-29T14:36:18.156Z DEBUG modem << [00:00:05.610,168] [0m<dbg> data_module: setup: Failed retrieveing the device configuration from flash in time[0m
2023-06-29T14:36:18.163Z DEBUG modem << [00:00:05.620,300] [0m<inf> data_module: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:36:18.273Z DEBUG modem << [00:00:05.626,617] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:36:18.279Z DEBUG modem << [00:00:05.634,368] [0m<dbg> data_module: config_print_all: Device mode: Active[0m
2023-06-29T14:36:18.282Z DEBUG modem << [00:00:05.641,723] [0m<dbg> data_module: config_print_all: Active wait timeout: 180[0m
2023-06-29T14:36:18.287Z DEBUG modem << [00:00:05.649,505] [0m<dbg> data_module: config_print_all: Movement resolution: 120[0m
2023-06-29T14:36:18.291Z DEBUG modem << [00:00:05.657,318] [0m<dbg> data_module: config_print_all: Movement timeout: 3600[0m
2023-06-29T14:36:18.293Z DEBUG modem << [00:00:05.664,947] [0m<dbg> data_module: config_print_all: Location timeout: 300[0m
2023-06-29T14:36:18.296Z DEBUG modem << [00:00:05.672,485] [0m<dbg> data_module: config_print_all: Accelerometer act threshold: 4.00[0m
2023-06-29T14:36:18.298Z DEBUG modem << [00:00:05.681,091] [0m<dbg> data_module: config_print_all: Accelerometer inact threshold: 4.00[0m
2023-06-29T14:36:18.300Z DEBUG modem << [00:00:05.689,819] [0m<dbg> data_module: config_print_all: Accelerometer inact timeout: 60.00[0m
2023-06-29T14:36:18.302Z DEBUG modem << [00:00:05.698,516] [0m<dbg> data_module: config_print_all: Requesting of neighbor cell data is enabled[0m
2023-06-29T14:36:18.304Z DEBUG modem << [00:00:05.707,946] [0m<dbg> data_module: config_print_all: Requesting of GNSS data is enabled[0m
2023-06-29T14:36:18.307Z DEBUG modem << [00:00:05.716,644] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
2023-06-29T14:36:18.309Z DEBUG modem << [00:00:05.723,663] [0m<dbg> data_module: requested_data_status_set: Data already encoded and sent, abort.[0m
2023-06-29T14:36:18.419Z DEBUG modem << [00:00:05.733,459] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED_DATA_READY[0m
2023-06-29T14:36:18.424Z DEBUG modem << [00:00:05.741,851] [0m<dbg> sensor_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
2023-06-29T14:36:18.429Z DEBUG modem << [00:00:05.751,007] [0m<dbg> sensor_module: on_state_init: on_state_init battery sampling...[0m
2023-06-29T14:36:19.772Z DEBUG modem << %CESQ: 52,2,25,3
2023-06-29T14:36:19.888Z DEBUG modem << [00:00:07.235,992] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -88[0m
2023-06-29T14:36:19.894Z DEBUG modem << +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:36:19.904Z DEBUG modem << [00:00:07.248,718] [0m<dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:36:19.907Z DEBUG modem << [0m
2023-06-29T14:36:19.909Z DEBUG modem << [00:00:07.258,697] [0m<dbg> lte_lc_helpers: parse_cereg: Network registration status: 2[0m
2023-06-29T14:36:19.911Z DEBUG modem << [00:00:07.266,815] [0m<dbg> lte_lc_helpers: parse_cereg: LTE mode: 9[0m
2023-06-29T14:36:19.914Z DEBUG modem << [00:00:07.273,345] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:19.916Z DEBUG modem << [00:00:07.281,890] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:19.918Z DEBUG modem << [00:00:07.291,137] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:19.921Z DEBUG modem << [00:00:07.299,865] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:19.922Z DEBUG modem << [00:00:07.308,593] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:19.924Z DEBUG modem << [00:00:07.317,352] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:19.926Z DEBUG modem << [00:00:07.324,645] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:19.930Z DEBUG modem << [00:00:07.333,221] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:19.934Z DEBUG modem << [00:00:07.341,979] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:20.049Z DEBUG modem << [00:00:07.350,738] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:20.053Z DEBUG modem << [00:00:07.359,466] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:20.058Z DEBUG modem << [00:00:07.368,255] [0m<dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 1447258, Tracking area: 40951[0m
2023-06-29T14:36:20.062Z DEBUG modem << [00:00:07.378,814] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:20.067Z DEBUG modem << [00:00:07.386,077] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:20.177Z DEBUG modem << [00:00:07.394,653] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:20.182Z DEBUG modem << [00:00:07.403,411] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:20.185Z DEBUG modem << [00:00:07.412,170] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:20.188Z DEBUG modem << [00:00:07.420,928] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:20.190Z DEBUG modem << [00:00:07.429,656] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:20.197Z DEBUG modem << [00:00:07.437,042] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-06-29T14:36:20.200Z DEBUG modem << +CSCON: 1
2023-06-29T14:36:20.202Z DEBUG modem << [00:00:07.506,591] [0m<dbg> lte_lc: at_handler_cscon: +CSCON notification[0m
2023-06-29T14:36:20.204Z DEBUG modem << [00:00:07.513,641] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:20.206Z DEBUG modem << [00:00:07.522,186] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:20.318Z DEBUG modem << [00:00:07.530,944] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:20.321Z DEBUG modem << [00:00:07.539,703] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:20.327Z DEBUG modem << [00:00:07.548,461] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:20.331Z DEBUG modem << [00:00:07.557,189] [0m<dbg> modem_module: lte_evt_handler: RRC mode: Connected[0m
2023-06-29T14:36:20.334Z DEBUG modem << [00:00:07.564,575] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:20.857Z DEBUG modem << %CESQ: 54,2,30,4
2023-06-29T14:36:20.973Z DEBUG modem << [00:00:08.320,983] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -86[0m
2023-06-29T14:36:23.659Z DEBUG modem << +CGEV: ME PDN ACT 0,0
2023-06-29T14:36:23.667Z DEBUG modem << [00:00:11.123,138] [0m<dbg> modem_module: pdn_event_handler: PDN_EVENT_ACTIVATED[0m
2023-06-29T14:36:23.777Z DEBUG modem << [00:00:11.130,706] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTED[0m
2023-06-29T14:36:23.782Z DEBUG modem << [00:00:11.138,000] [0m<dbg> modem_module: state_set: State transition STATE_CONNECTING --> STATE_CONNECTED[0m
2023-06-29T14:36:23.785Z DEBUG modem << [00:00:11.147,857] [0m<dbg> aws_iot_integration: aws_iot_event_handler: AWS_IOT_EVT_CONNECTING[0m
2023-06-29T14:36:23.789Z DEBUG modem << [00:00:11.156,616] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2023-06-29T14:36:23.792Z DEBUG modem << +CNEC_ESM: 50,0
2023-06-29T14:36:23.797Z DEBUG modem << [00:00:11.166,137] [1;31m<err> modem_module: Event: PDP context 0, PDN type IPv4 only allowed[0m
2023-06-29T14:36:23.912Z DEBUG modem << %MDMEV: SEARCH STATUS 2
2023-06-29T14:36:23.918Z DEBUG modem << [00:00:11.267,150] [0m<dbg> lte_lc: at_handler_mdmev: %MDMEV notification[0m
2023-06-29T14:36:23.923Z DEBUG modem << [00:00:11.274,078] [0m<dbg> lte_lc_helpers: parse_mdmev: Occurrence found: SEARCH STATUS 2
2023-06-29T14:36:23.926Z DEBUG modem << [0m
2023-06-29T14:36:23.929Z DEBUG modem << [00:00:11.282,653] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:23.931Z DEBUG modem << [00:00:11.291,229] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:23.934Z DEBUG modem << [00:00:11.299,987] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:23.938Z DEBUG modem << [00:00:11.308,746] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:23.941Z DEBUG modem << [00:00:11.317,504] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:23.943Z DEBUG modem << [00:00:11.326,263] [0m<dbg> modem_module: lte_evt_handler: Modem domain event, type: Search done[0m
2023-06-29T14:36:23.946Z DEBUG modem << [00:00:11.335,174] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:23.949Z DEBUG modem << +CEREG: 5,"9FF7","0016155A",9,,,"00010000","11000001"
2023-06-29T14:36:23.957Z DEBUG modem << [00:00:11.347,259] [0m<dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 5,"9FF7","0016155A",9,,,"00010000","11000001"
2023-06-29T14:36:23.960Z DEBUG modem << [0m
2023-06-29T14:36:23.963Z DEBUG modem << [00:00:11.359,375] [0m<dbg> lte_lc_helpers: parse_cereg: Network registration status: 5[0m
2023-06-29T14:36:23.966Z DEBUG modem << [00:00:11.367,523] [0m<dbg> lte_lc_helpers: parse_cereg: LTE mode: 9[0m
2023-06-29T14:36:24.097Z DEBUG modem << [00:00:11.374,084] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:24.100Z DEBUG modem << [00:00:11.382,629] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:24.106Z DEBUG modem << [00:00:11.391,387] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:24.110Z DEBUG modem << [00:00:11.400,146] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:24.113Z DEBUG modem << [00:00:11.408,874] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:24.116Z DEBUG modem << [00:00:11.417,663] [0m<dbg> modem_module: lte_evt_handler: Network registration status: Connected - roaming[0m
2023-06-29T14:36:24.256Z DEBUG modem << [00:00:11.427,520] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:24.264Z DEBUG modem << [00:00:11.435,638] [0m<dbg> lte_lc_helpers: parse_psm: TAU: 1152000 sec, active time: 32 sec[0m
2023-06-29T14:36:24.269Z DEBUG modem << [00:00:11.444,183] [0m<dbg> lte_lc: lte_lc_psm_get: TAU: 1152000 sec, active time: 32 sec[0m
2023-06-29T14:36:24.274Z DEBUG modem << [00:00:11.452,484] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:24.279Z DEBUG modem << [00:00:11.461,059] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:24.283Z DEBUG modem << [00:00:11.469,818] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:24.288Z DEBUG modem << [00:00:11.478,576] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:24.293Z DEBUG modem << [00:00:11.487,335] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:24.297Z DEBUG modem << [00:00:11.496,093] [0m<dbg> modem_module: lte_evt_handler: PSM parameter update: TAU: 1152000, Active time: 32[0m
2023-06-29T14:36:24.300Z DEBUG modem << [00:00:11.506,256] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:24.304Z DEBUG modem << %XTIME: "40","32609241633240","00"
2023-06-29T14:36:24.308Z DEBUG modem << [00:00:11.516,845] [0m<inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
2023-06-29T14:36:24.312Z DEBUG modem << [00:00:11.524,169] [0m<inf> app_event_manager: DATA_EVT_DATE_TIME_OBTAINED[0m
2023-06-29T14:36:25.670Z DEBUG modem << %CESQ: 54,2,24,3
2023-06-29T14:36:25.788Z DEBUG modem << [00:00:13.133,422] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -86[0m
2023-06-29T14:36:29.227Z DEBUG modem << %CESQ: 54,2,29,4
2023-06-29T14:36:29.355Z DEBUG modem << [00:00:16.691,223] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -86[0m
2023-06-29T14:36:30.371Z DEBUG modem << [00:00:17.827,087] [0m<dbg> aws_iot_integration: aws_iot_event_handler: AWS_IOT_EVT_CONNECTED[0m
2023-06-29T14:36:31.091Z DEBUG modem << [00:00:18.547,058] [0m<dbg> aws_iot_integration: aws_iot_event_handler: AWS_IOT_EVT_READY[0m
2023-06-29T14:36:31.213Z DEBUG modem << [00:00:18.555,389] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTED[0m
2023-06-29T14:36:31.221Z DEBUG modem << [00:00:18.562,347] [0m<inf> app_event_manager: APP_EVT_DATA_GET_PRIVATE - Requested data types (MOD_DYN, BAT, ENV, DOOR_STATUS, ACCEL, MOD_STAT, LOCATION)[0m
2023-06-29T14:36:31.225Z DEBUG modem << [00:00:18.576,934] [0m<dbg> data_module: state_set: State transition STATE_CLOUD_DISCONNECTED --> STATE_CLOUD_CONNECTED[0m
2023-06-29T14:36:31.228Z DEBUG modem << [00:00:18.587,829] [0m<inf> data_module: sattat chang: 1[0m
2023-06-29T14:36:31.231Z DEBUG modem << [00:00:18.593,292] [0m<inf> app_event_manager: DATA_EVT_CLOUD_STATUS_CHANGED_DETECTED[0m
2023-06-29T14:36:31.234Z DEBUG modem << [00:00:18.601,745] [0m<inf> data_module: CLOUD_EVT_CONNECTED[0m
2023-06-29T14:36:31.237Z DEBUG modem << [00:00:18.607,543] [0m<dbg> data_module: requested_data_list_set: requested_data_list_set CNT: 7[0m
2023-06-29T14:36:31.239Z DEBUG modem << [00:00:18.616,424] [0m<dbg> data_module: on_all_states: timeout: 435 [0m
2023-06-29T14:36:31.242Z DEBUG modem << [00:00:18.623,107] [0m<inf> app_event_manager: DATA_EVT_CLOUD_STATUS_CHANGED_READY[0m
2023-06-29T14:36:31.245Z DEBUG modem << [00:00:18.631,347] [0m<dbg> data_module: on_cloud_state_connected: DATA_EVT_RESTART_DETECTED_DATA_READY OR DATA_EVT_CLOUD_STATUS_CHANGED_READY[0m
2023-06-29T14:36:31.247Z DEBUG modem << [00:00:18.644,195] [0m<dbg> data_module: send_boot_info: GET TRIG[0m
2023-06-29T14:36:31.250Z DEBUG modem << [00:00:18.651,092] [0m<inf> cloud_codec: encoded....[0m
2023-06-29T14:36:31.252Z DEBUG modem << [00:00:18.659,576] [0m<dbg> data_module: send_boot_info: DEV_ERROR data encoded successfully[0m
2023-06-29T14:36:31.254Z DEBUG modem << [00:00:18.668,151] [0m<inf> app_event_manager: DATA_EVT_DEVICE_STATUS_CHANGED_DATA_SEND[0m
2023-06-29T14:36:31.371Z DEBUG modem << [00:00:18.677,154] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2023-06-29T14:36:31.374Z DEBUG modem << [00:00:18.685,119] [0m<dbg> ext_sensors: get_door_status: get door status: 1[0m
2023-06-29T14:36:31.380Z DEBUG modem << [00:00:18.692,321] [0m<inf> app_event_manager: SENSOR_EVT_DOOR_STATUS_READY[0m
2023-06-29T14:36:31.383Z DEBUG modem << [00:00:18.699,951] [0m<inf> app_event_manager: CLOUD_EVT_DATA_SEND_QOS[0m
2023-06-29T14:36:31.386Z DEBUG modem << [00:00:18.707,458] [0m<dbg> data_module: requested_data_status_set: requested_data_status_set datatype: 0[0m
2023-06-29T14:36:31.505Z DEBUG modem << [00:00:18.717,224] [0m<dbg> data_module: requested_data_status_set: requested_data_status_set datatype: 2[0m
2023-06-29T14:36:31.509Z DEBUG modem << [00:00:18.727,844] [0m<dbg> ext_sensors: ext_sensors_accelerometer_get: x: 0.00, y: 0.00, z: 0.00 (m/s^2)
2023-06-29T14:36:31.515Z DEBUG modem << [0m
2023-06-29T14:36:31.518Z DEBUG modem << [00:00:18.737,609] [0m<inf> app_event_manager: SENSOR_EVT_ACCEL_DATA_READY[0m
2023-06-29T14:36:31.520Z DEBUG modem << [00:00:18.745,727] [0m<dbg> data_module: requested_data_status_set: requested_data_status_set datatype: 3[0m
2023-06-29T14:36:31.523Z DEBUG modem << [00:00:18.757,293] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 922000.-536810240V[0m
2023-06-29T14:36:31.525Z DEBUG modem << [00:00:18.768,310] [0m<inf> app_event_manager: SENSOR_EVT_BATTERY_DATA_READY[0m
2023-06-29T14:36:31.527Z DEBUG modem << [00:00:18.775,756] [0m<dbg> sensor_module: sensor_gnss_search_start: GNSS STARTED[0m
2023-06-29T14:36:31.529Z DEBUG modem << [00:00:18.783,355] [0m<dbg> ext_sensors: gnss_search_start: STARTED..... SEARCH GNSS[0m
2023-06-29T14:36:31.531Z DEBUG modem << [00:00:18.791,290] [0m<inf> app_event_manager: SENSOR_MODULE_YIC_GNSS_EVT_ACTIVE[0m
2023-06-29T14:36:31.533Z DEBUG modem << [00:00:18.799,804] [0m<dbg> data_module: requested_data_status_set: requested_data_status_set datatype: 6[0m
2023-06-29T14:36:31.536Z DEBUG modem << [00:00:18.837,493] [0m<inf> app_event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY[0m
2023-06-29T14:36:31.657Z DEBUG modem << [00:00:18.845,916] [0m<dbg> data_module: requested_data_status_set: requested_data_status_set datatype: 4[0m
2023-06-29T14:36:31.661Z DEBUG modem << [00:00:18.889,190] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2023-06-29T14:36:31.667Z DEBUG modem << [00:00:18.897,583] [0m<dbg> data_module: on_all_states: MODEM_EVT_MODEM_DYNAMIC 1[0m
2023-06-29T14:36:31.670Z DEBUG modem << [00:00:18.905,242] [0m<dbg> data_module: requested_data_status_set: requested_data_status_set datatype: 5[0m
2023-06-29T14:36:31.798Z DEBUG modem << [00:00:19.105,285] [0m<dbg> aws_iot_integration: aws_iot_event_handler: AWS_IOT_EVT_PUBACK[0m
2023-06-29T14:36:37.716Z DEBUG modem << +CSCON: 0
2023-06-29T14:36:37.882Z DEBUG modem << [00:00:25.179,809] [0m<dbg> lte_lc: at_handler_cscon: +CSCON notification[0m
2023-06-29T14:36:37.888Z DEBUG modem << [00:00:25.186,859] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:37.897Z DEBUG modem << [00:00:25.195,404] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:37.903Z DEBUG modem << [00:00:25.204,132] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:37.908Z DEBUG modem << [00:00:25.212,890] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:37.913Z DEBUG modem << [00:00:25.221,649] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:37.918Z DEBUG modem << [00:00:25.230,377] [0m<dbg> modem_module: lte_evt_handler: RRC mode: Idle[0m
2023-06-29T14:36:37.922Z DEBUG modem << [00:00:25.237,335] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:38.083Z DEBUG modem << %CESQ: 51,2,23,3
2023-06-29T14:36:38.089Z DEBUG modem << [00:00:25.457,458] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -89[0m
2023-06-29T14:36:40.429Z DEBUG modem << %CESQ: 50,2,28,4
2023-06-29T14:36:40.565Z DEBUG modem << [00:00:27.893,737] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -90[0m
2023-06-29T14:36:42.658Z DEBUG modem << [00:00:30.114,074] [0m<dbg> sensor_module: gnss_client_callback: GNSS_SEARCH_EVT_TIMEOUT[0m
2023-06-29T14:36:42.793Z DEBUG modem << [00:00:30.122,344] [0m<inf> sensor_module: LAT:0,lon:0, alt:0,acc:0, speed:0, heeding:0, sattrck:0, stim:11 fxty 0 comfrm 8 [0m
2023-06-29T14:36:42.797Z DEBUG modem << [00:00:30.133,666] [0m<inf> sensor_module: LAT2:0,lon2:0, alt2:0,acc2:0, speed2:0, heeding2:0, sattrck2:0, stim2:537017608, fxty2 8[0m
2023-06-29T14:36:42.801Z DEBUG modem << [00:00:30.145,629] [0m<inf> app_event_manager: SENSOR_EVT_YIC_GNSS_DATA_READY[0m
2023-06-29T14:36:42.807Z DEBUG modem << [00:00:30.153,228] [0m<dbg> ext_sensors: gnss_search_client_turn_off: gnss_pin has been reset[0m
2023-06-29T14:36:42.811Z DEBUG modem << [00:00:30.161,895] [0m<dbg> data_module: requested_data_status_set: requested_data_status_set datatype: 8[0m
2023-06-29T14:36:42.814Z DEBUG modem << [00:00:30.171,600] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
2023-06-29T14:36:42.817Z DEBUG modem << [00:00:30.178,497] [0m<dbg> data_module: data_encode: No neighbor cells data to encode, error: -61[0m
2023-06-29T14:36:42.819Z DEBUG modem << [00:00:30.206,481] [0m<dbg> data_module: data_encode: Batch data encoded successfully[0m
2023-06-29T14:36:42.822Z DEBUG modem << [00:00:30.214,447] [0m<inf> app_event_manager: DATA_EVT_DATA_SEND_BATCH[0m
2023-06-29T14:36:42.824Z DEBUG modem << [00:00:30.221,862] [0m<inf> app_event_manager: CLOUD_EVT_DATA_SEND_QOS[0m
2023-06-29T14:36:44.373Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:36:44.492Z DEBUG modem << Attempting to boot slot 0.
2023-06-29T14:36:44.623Z DEBUG modem << Attempting to boot from address 0x8200.
2023-06-29T14:36:44.627Z DEBUG modem << Verifying signature against key 0.
2023-06-29T14:36:44.634Z DEBUG modem << Hash: 0x0f...ad
2023-06-29T14:36:44.636Z DEBUG modem << Firmware signature verified.
2023-06-29T14:36:44.639Z DEBUG modem << Firmware version 5
2023-06-29T14:36:44.641Z DEBUG modem << Booting (0x8200).
2023-06-29T14:36:48.630Z DEBUG modem << [00:00:02.486,663] [0m<inf> ADXL362: NetFeasa: Accelerometer Self Test Starting...[0m
2023-06-29T14:36:49.690Z DEBUG modem << [00:00:03.548,217] [0m<inf> ADXL362: ACCELEROMETER SELF-TEST PASS[0m
2023-06-29T14:36:49.821Z DEBUG modem << [00:00:03.556,884] [0m<inf> ADXL362: INT1 set at GPIO port gpio@842500 pin 6[0m
2023-06-29T14:36:49.826Z DEBUG modem << [00:00:03.572,570] [0m<inf> bq274xx: Device ID: 0xffa5[0m
2023-06-29T14:36:49.832Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:36:49.835Z DEBUG modem << [00:00:03.581,787] [0m<inf> main: i setting pin high ----1111-----[0m
2023-06-29T14:36:50.730Z DEBUG modem << [00:00:04.588,195] [0m<inf> main: i set nrf select pin high -----222----[0m
2023-06-29T14:36:50.865Z DEBUG modem << [00:00:04.595,336] [0m<inf> app_event_manager: APP_EVT_START[0m
2023-06-29T14:36:50.871Z DEBUG modem << [00:00:04.601,867] [0m<dbg> data_module: state_set: State: STATE_CLOUD_DISCONNECTED[0m
2023-06-29T14:36:50.875Z DEBUG modem << [00:00:04.610,046] [0m<dbg> modem_module: state_set: State transition STATE_INIT --> STATE_DISCONNECTED[0m
2023-06-29T14:36:50.878Z DEBUG modem << [00:00:04.619,567] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2023-06-29T14:36:50.881Z DEBUG modem << [00:00:04.626,922] [0m<dbg> sensor_module: state_set: State: STATE_INIT[0m
2023-06-29T14:36:50.883Z DEBUG modem << [00:00:04.633,728] [0m<dbg> ext_sensors: sensor_settings_set: Settings key: state, size: 1, sizeofJobDef 1[0m
2023-06-29T14:36:50.887Z DEBUG modem << [00:00:04.643,554] [0m<dbg> ext_sensors: sensor_settings_set: SZ: 1[0m
2023-06-29T14:36:50.890Z DEBUG modem << [00:00:04.649,963] [0m<inf> ext_sensors: yic status: 1[0m
2023-06-29T14:36:50.892Z DEBUG modem << [00:00:04.655,303] [0m<dbg> ext_sensors: load_sensor_settings: SETTINGS: 0[0m
2023-06-29T14:36:50.896Z DEBUG modem << [00:00:04.662,292] [0m<dbg> ext_sensors: ext_sensors_init: ACCEL adxl362@0 initialized![0m
2023-06-29T14:36:50.900Z DEBUG modem << [00:00:04.670,806] [0m<dbg> lte_lc: init_and_config: System mode (6) and preference (4) are already configured[0m
2023-06-29T14:36:50.904Z DEBUG modem << [00:00:04.683,319] [0m<dbg> ext_sensors: ext_sensors_init: CONFIGURE ACCCCCCC1111[0m
2023-06-29T14:36:50.906Z DEBUG modem << [00:00:04.691,864] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:36:50.909Z DEBUG modem << [00:00:04.701,965] [0m<dbg> aws_iot_integration: cloud_wrap_init: The Asset Tracker v2 has started[0m
2023-06-29T14:36:50.912Z DEBUG modem << [00:00:04.711,151] [0m<dbg> aws_iot_integration: cloud_wrap_init: Version: 0.0.18[0m
2023-06-29T14:36:50.915Z DEBUG modem << [00:00:04.719,238] [0m<dbg> aws_iot_integration: cloud_wrap_init: Client ID: 351516173341025[0m
2023-06-29T14:36:51.044Z DEBUG modem << [00:00:04.728,057] [0m<dbg> aws_iot_integration: cloud_wrap_init: Cloud: AWS IoT[0m
2023-06-29T14:36:51.048Z DEBUG modem << [00:00:04.736,236] [0m<dbg> aws_iot_integration: cloud_wrap_init: Endpoint: a2hkw2qiy12x93-ats.iot.eu-west-1.amazonaws.com[0m
2023-06-29T14:36:51.055Z DEBUG modem << [00:00:04.747,772] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:36:51.059Z DEBUG modem << [00:00:04.758,666] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 336000.000000V[0m
2023-06-29T14:36:51.063Z DEBUG modem << [00:00:04.769,317] [0m<dbg> ext_sensors: ext_sensors_init: bq27z561@55 fuel gauge initialized succesfully 433V [0m
2023-06-29T14:36:51.184Z DEBUG modem << [00:00:04.779,571] [0m<dbg> ext_sensors: ext_sensors_init: Set up hall-effect at gpio@842500 pin 21[0m
2023-06-29T14:36:51.188Z DEBUG modem << [00:00:04.788,726] [0m<dbg> ext_sensors: config_gnss: GNSS CONFIG ALREADY SET[0m
2023-06-29T14:36:51.194Z DEBUG modem << [00:00:04.796,203] [0m<dbg> sensor_module: gnss_client_callback: GNSS_SEARCH_EVT_STARTED[0m
2023-06-29T14:36:51.198Z DEBUG modem << [00:00:04.805,114] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 336000.000000V[0m
2023-06-29T14:36:51.200Z DEBUG modem << [00:00:04.815,826] [0m<inf> app_event_manager: SENSOR_EVT_BATTERY_DATA_READY[0m
2023-06-29T14:36:51.203Z DEBUG modem << [00:00:04.823,425] [0m<dbg> modem_module: configure_low_power: PSM requested[0m
2023-06-29T14:36:51.205Z DEBUG modem << [00:00:04.865,295] [0m<dbg> lte_lc: lte_lc_func_mode_set: CFUN monitor callback: 0x52219[0m
2023-06-29T14:36:51.208Z DEBUG modem << [00:00:04.874,206] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2023-06-29T14:36:51.211Z DEBUG modem << [00:00:04.881,622] [0m<dbg> modem_module: state_set: State transition STATE_DISCONNECTED --> STATE_CONNECTING[0m
2023-06-29T14:36:51.756Z DEBUG modem << [00:00:05.610,046] [0m<dbg> data_module: setup: Failed retrieveing the device configuration from flash in time[0m
2023-06-29T14:36:51.888Z DEBUG modem << [00:00:05.620,178] [0m<inf> data_module: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:36:51.891Z DEBUG modem << [00:00:05.626,495] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:36:51.897Z DEBUG modem << [00:00:05.634,277] [0m<dbg> data_module: config_print_all: Device mode: Active[0m
2023-06-29T14:36:51.900Z DEBUG modem << [00:00:05.641,601] [0m<dbg> data_module: config_print_all: Active wait timeout: 180[0m
2023-06-29T14:36:51.902Z DEBUG modem << [00:00:05.649,383] [0m<dbg> data_module: config_print_all: Movement resolution: 120[0m
2023-06-29T14:36:51.905Z DEBUG modem << [00:00:05.657,196] [0m<dbg> data_module: config_print_all: Movement timeout: 3600[0m
2023-06-29T14:36:51.908Z DEBUG modem << [00:00:05.664,825] [0m<dbg> data_module: config_print_all: Location timeout: 300[0m
2023-06-29T14:36:51.910Z DEBUG modem << [00:00:05.672,363] [0m<dbg> data_module: config_print_all: Accelerometer act threshold: 4.00[0m
2023-06-29T14:36:51.912Z DEBUG modem << [00:00:05.680,969] [0m<dbg> data_module: config_print_all: Accelerometer inact threshold: 4.00[0m
2023-06-29T14:36:51.915Z DEBUG modem << [00:00:05.689,727] [0m<dbg> data_module: config_print_all: Accelerometer inact timeout: 60.00[0m
2023-06-29T14:36:51.917Z DEBUG modem << [00:00:05.698,394] [0m<dbg> data_module: config_print_all: Requesting of neighbor cell data is enabled[0m
2023-06-29T14:36:51.919Z DEBUG modem << [00:00:05.707,824] [0m<dbg> data_module: config_print_all: Requesting of GNSS data is enabled[0m
2023-06-29T14:36:51.921Z DEBUG modem << [00:00:05.716,552] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
2023-06-29T14:36:51.924Z DEBUG modem << [00:00:05.723,541] [0m<dbg> data_module: requested_data_status_set: Data already encoded and sent, abort.[0m
2023-06-29T14:36:51.926Z DEBUG modem << [00:00:05.733,337] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED_DATA_READY[0m
2023-06-29T14:36:51.929Z DEBUG modem << [00:00:05.741,760] [0m<dbg> sensor_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
2023-06-29T14:36:52.064Z DEBUG modem << [00:00:05.750,915] [0m<dbg> sensor_module: on_state_init: on_state_init battery sampling...[0m
2023-06-29T14:36:55.612Z DEBUG modem << %CESQ: 52,2,23,3
2023-06-29T14:36:55.782Z DEBUG modem << [00:00:09.477,416] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -88[0m
2023-06-29T14:36:55.786Z DEBUG modem << +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:36:55.797Z DEBUG modem << [00:00:09.490,142] [0m<dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:36:55.800Z DEBUG modem << [0m
2023-06-29T14:36:55.802Z DEBUG modem << [00:00:09.500,122] [0m<dbg> lte_lc_helpers: parse_cereg: Network registration status: 2[0m
2023-06-29T14:36:55.805Z DEBUG modem << [00:00:09.508,239] [0m<dbg> lte_lc_helpers: parse_cereg: LTE mode: 9[0m
2023-06-29T14:36:55.807Z DEBUG modem << [00:00:09.514,801] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:55.810Z DEBUG modem << [00:00:09.523,315] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:55.812Z DEBUG modem << [00:00:09.532,592] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:55.815Z DEBUG modem << [00:00:09.541,290] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:55.818Z DEBUG modem << [00:00:09.550,048] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:55.821Z DEBUG modem << [00:00:09.558,807] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:55.823Z DEBUG modem << [00:00:09.566,101] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:55.825Z DEBUG modem << [00:00:09.574,676] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:55.828Z DEBUG modem << [00:00:09.583,435] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:55.830Z DEBUG modem << [00:00:09.592,193] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:55.833Z DEBUG modem << [00:00:09.600,952] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:55.836Z DEBUG modem << [00:00:09.609,710] [0m<dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 1447258, Tracking area: 40951[0m
2023-06-29T14:36:55.839Z DEBUG modem << [00:00:09.620,300] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:55.843Z DEBUG modem << [00:00:09.627,563] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:36:55.846Z DEBUG modem << [00:00:09.636,138] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:36:56.008Z DEBUG modem << [00:00:09.644,897] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:36:56.011Z DEBUG modem << [00:00:09.653,656] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:36:56.017Z DEBUG modem << [00:00:09.662,414] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:36:56.022Z DEBUG modem << [00:00:09.671,173] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:36:56.024Z DEBUG modem << [00:00:09.678,527] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-06-29T14:36:56.854Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:36:56.859Z DEBUG modem << Attempting to boot slot 0.
2023-06-29T14:36:57.018Z DEBUG modem << Attempting to boot from address 0x8200.
2023-06-29T14:36:57.025Z DEBUG modem << Verifying signature against key 0.
2023-06-29T14:36:57.155Z DEBUG modem << Hash: 0x0f...ad
2023-06-29T14:36:57.161Z DEBUG modem << Firmware signature verified.
2023-06-29T14:36:57.167Z DEBUG modem << Firmware version 5
2023-06-29T14:36:57.170Z DEBUG modem << Booting (0x8200).
2023-06-29T14:37:01.107Z DEBUG modem << [00:00:02.486,663] [0m<inf> ADXL362: NetFeasa: Accelerometer Self Test Starting...[0m
2023-06-29T14:37:02.168Z DEBUG modem << [00:00:03.548,248] [0m<inf> ADXL362: ACCELEROMETER SELF-TEST PASS[0m
2023-06-29T14:37:02.177Z DEBUG modem << [00:00:03.556,915] [0m<inf> ADXL362: INT1 set at GPIO port gpio@842500 pin 6[0m
2023-06-29T14:37:02.346Z DEBUG modem << [00:00:03.572,601] [0m<inf> bq274xx: Device ID: 0xffa5[0m
2023-06-29T14:37:02.354Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:37:02.356Z DEBUG modem << [00:00:03.581,848] [0m<inf> main: i setting pin high ----1111-----[0m
2023-06-29T14:37:03.208Z DEBUG modem << [00:00:04.588,256] [0m<inf> main: i set nrf select pin high -----222----[0m
2023-06-29T14:37:03.369Z DEBUG modem << [00:00:04.595,397] [0m<inf> app_event_manager: APP_EVT_START[0m
2023-06-29T14:37:03.375Z DEBUG modem << [00:00:04.601,928] [0m<dbg> data_module: state_set: State: STATE_CLOUD_DISCONNECTED[0m
2023-06-29T14:37:03.381Z DEBUG modem << [00:00:04.610,107] [0m<dbg> modem_module: state_set: State transition STATE_INIT --> STATE_DISCONNECTED[0m
2023-06-29T14:37:03.385Z DEBUG modem << [00:00:04.619,628] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2023-06-29T14:37:03.388Z DEBUG modem << [00:00:04.626,983] [0m<dbg> sensor_module: state_set: State: STATE_INIT[0m
2023-06-29T14:37:03.392Z DEBUG modem << [00:00:04.633,789] [0m<dbg> ext_sensors: sensor_settings_set: Settings key: state, size: 1, sizeofJobDef 1[0m
2023-06-29T14:37:03.394Z DEBUG modem << [00:00:04.643,615] [0m<dbg> ext_sensors: sensor_settings_set: SZ: 1[0m
2023-06-29T14:37:03.397Z DEBUG modem << [00:00:04.650,024] [0m<inf> ext_sensors: yic status: 1[0m
2023-06-29T14:37:03.400Z DEBUG modem << [00:00:04.655,364] [0m<dbg> ext_sensors: load_sensor_settings: SETTINGS: 0[0m
2023-06-29T14:37:03.404Z DEBUG modem << [00:00:04.662,353] [0m<dbg> ext_sensors: ext_sensors_init: ACCEL adxl362@0 initialized![0m
2023-06-29T14:37:03.406Z DEBUG modem << [00:00:04.670,867] [0m<dbg> lte_lc: init_and_config: System mode (6) and preference (4) are already configured[0m
2023-06-29T14:37:03.409Z DEBUG modem << [00:00:04.683,380] [0m<dbg> ext_sensors: ext_sensors_init: CONFIGURE ACCCCCCC1111[0m
2023-06-29T14:37:03.414Z DEBUG modem << [00:00:04.691,925] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:37:03.420Z DEBUG modem << [00:00:04.702,026] [0m<dbg> aws_iot_integration: cloud_wrap_init: The Asset Tracker v2 has started[0m
2023-06-29T14:37:03.422Z DEBUG modem << [00:00:04.711,212] [0m<dbg> aws_iot_integration: cloud_wrap_init: Version: 0.0.18[0m
2023-06-29T14:37:03.425Z DEBUG modem << [00:00:04.719,299] [0m<dbg> aws_iot_integration: cloud_wrap_init: Client ID: 351516173341025[0m
2023-06-29T14:37:03.428Z DEBUG modem << [00:00:04.728,118] [0m<dbg> aws_iot_integration: cloud_wrap_init: Cloud: AWS IoT[0m
2023-06-29T14:37:03.433Z DEBUG modem << [00:00:04.736,267] [0m<dbg> aws_iot_integration: cloud_wrap_init: Endpoint: a2hkw2qiy12x93-ats.iot.eu-west-1.amazonaws.com[0m
2023-06-29T14:37:03.597Z DEBUG modem << [00:00:04.747,802] [0m<dbg> aws_iot_integration: cloud_wrap_init: ********************************************[0m
2023-06-29T14:37:03.604Z DEBUG modem << [00:00:04.758,728] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 932000.000000V[0m
2023-06-29T14:37:03.608Z DEBUG modem << [00:00:04.769,378] [0m<dbg> ext_sensors: ext_sensors_init: bq27z561@55 fuel gauge initialized succesfully 393V [0m
2023-06-29T14:37:03.614Z DEBUG modem << [00:00:04.779,632] [0m<dbg> ext_sensors: ext_sensors_init: Set up hall-effect at gpio@842500 pin 21[0m
2023-06-29T14:37:03.619Z DEBUG modem << [00:00:04.788,787] [0m<dbg> ext_sensors: config_gnss: GNSS CONFIG ALREADY SET[0m
2023-06-29T14:37:03.623Z DEBUG modem << [00:00:04.796,264] [0m<dbg> sensor_module: gnss_client_callback: GNSS_SEARCH_EVT_STARTED[0m
2023-06-29T14:37:03.626Z DEBUG modem << [00:00:04.805,175] [0m<dbg> ext_sensors: ext_sensors_bq275xx_gauge_get_voltage: BT_VOLTAGE: 0.000000 932000.000000V[0m
2023-06-29T14:37:03.630Z DEBUG modem << [00:00:04.815,887] [0m<inf> app_event_manager: SENSOR_EVT_BATTERY_DATA_READY[0m
2023-06-29T14:37:03.786Z DEBUG modem << [00:00:04.823,455] [0m<dbg> modem_module: configure_low_power: PSM requested[0m
2023-06-29T14:37:03.793Z DEBUG modem << [00:00:04.865,325] [0m<dbg> lte_lc: lte_lc_func_mode_set: CFUN monitor callback: 0x52219[0m
2023-06-29T14:37:03.798Z DEBUG modem << [00:00:04.874,237] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2023-06-29T14:37:03.801Z DEBUG modem << [00:00:04.881,652] [0m<dbg> modem_module: state_set: State transition STATE_DISCONNECTED --> STATE_CONNECTING[0m
2023-06-29T14:37:04.233Z DEBUG modem << [00:00:05.610,107] [0m<dbg> data_module: setup: Failed retrieveing the device configuration from flash in time[0m
2023-06-29T14:37:04.239Z DEBUG modem << [00:00:05.620,239] [0m<inf> data_module: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:37:04.407Z DEBUG modem << [00:00:05.626,556] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED[0m
2023-06-29T14:37:04.415Z DEBUG modem << [00:00:05.634,338] [0m<dbg> data_module: config_print_all: Device mode: Active[0m
2023-06-29T14:37:04.419Z DEBUG modem << [00:00:05.641,662] [0m<dbg> data_module: config_print_all: Active wait timeout: 180[0m
2023-06-29T14:37:04.422Z DEBUG modem << [00:00:05.649,444] [0m<dbg> data_module: config_print_all: Movement resolution: 120[0m
2023-06-29T14:37:04.425Z DEBUG modem << [00:00:05.657,257] [0m<dbg> data_module: config_print_all: Movement timeout: 3600[0m
2023-06-29T14:37:04.428Z DEBUG modem << [00:00:05.664,886] [0m<dbg> data_module: config_print_all: Location timeout: 300[0m
2023-06-29T14:37:04.430Z DEBUG modem << [00:00:05.672,424] [0m<dbg> data_module: config_print_all: Accelerometer act threshold: 4.00[0m
2023-06-29T14:37:04.433Z DEBUG modem << [00:00:05.681,030] [0m<dbg> data_module: config_print_all: Accelerometer inact threshold: 4.00[0m
2023-06-29T14:37:04.436Z DEBUG modem << [00:00:05.689,758] [0m<dbg> data_module: config_print_all: Accelerometer inact timeout: 60.00[0m
2023-06-29T14:37:04.439Z DEBUG modem << [00:00:05.698,455] [0m<dbg> data_module: config_print_all: Requesting of neighbor cell data is enabled[0m
2023-06-29T14:37:04.442Z DEBUG modem << [00:00:05.707,885] [0m<dbg> data_module: config_print_all: Requesting of GNSS data is enabled[0m
2023-06-29T14:37:04.445Z DEBUG modem << [00:00:05.716,613] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
2023-06-29T14:37:04.448Z DEBUG modem << [00:00:05.723,602] [0m<dbg> data_module: requested_data_status_set: Data already encoded and sent, abort.[0m
2023-06-29T14:37:04.450Z DEBUG modem << [00:00:05.733,398] [0m<inf> app_event_manager: DATA_EVT_RESTART_DETECTED_DATA_READY[0m
2023-06-29T14:37:04.454Z DEBUG modem << [00:00:05.741,821] [0m<dbg> sensor_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
2023-06-29T14:37:04.457Z DEBUG modem << [00:00:05.750,946] [0m<dbg> sensor_module: on_state_init: on_state_init battery sampling...[0m
2023-06-29T14:37:05.853Z DEBUG modem << %CESQ: 53,2,23,3
2023-06-29T14:37:06.003Z DEBUG modem << [00:00:07.239,776] [0m<dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -87[0m
2023-06-29T14:37:06.011Z DEBUG modem << +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:37:06.020Z DEBUG modem << [00:00:07.252,502] [0m<dbg> lte_lc: at_handler_cereg: +CEREG notification: +CEREG: 2,"9FF7","0016155A",9
2023-06-29T14:37:06.026Z DEBUG modem << [0m
2023-06-29T14:37:06.031Z DEBUG modem << [00:00:07.262,481] [0m<dbg> lte_lc_helpers: parse_cereg: Network registration status: 2[0m
2023-06-29T14:37:06.035Z DEBUG modem << [00:00:07.270,599] [0m<dbg> lte_lc_helpers: parse_cereg: LTE mode: 9[0m
2023-06-29T14:37:06.040Z DEBUG modem << [00:00:07.277,130] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:37:06.043Z DEBUG modem << [00:00:07.285,675] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:37:06.045Z DEBUG modem << [00:00:07.294,921] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:37:06.048Z DEBUG modem << [00:00:07.303,649] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:37:06.051Z DEBUG modem << [00:00:07.312,408] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:37:06.055Z DEBUG modem << [00:00:07.321,136] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:37:06.059Z DEBUG modem << [00:00:07.328,460] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:37:06.063Z DEBUG modem << [00:00:07.337,005] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:37:06.065Z DEBUG modem << [00:00:07.345,764] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:37:06.067Z DEBUG modem << [00:00:07.354,522] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:37:06.070Z DEBUG modem << [00:00:07.363,281] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:37:06.073Z DEBUG modem << [00:00:07.372,039] [0m<dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 1447258, Tracking area: 40951[0m
2023-06-29T14:37:06.076Z DEBUG modem << [00:00:07.382,629] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:37:06.232Z DEBUG modem << [00:00:07.389,892] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Dispatching events:[0m
2023-06-29T14:37:06.238Z DEBUG modem << [00:00:07.398,437] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x0005264D[0m
2023-06-29T14:37:06.241Z DEBUG modem << [00:00:07.407,196] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053625[0m
2023-06-29T14:37:06.244Z DEBUG modem << [00:00:07.415,954] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00053A85[0m
2023-06-29T14:37:06.247Z DEBUG modem << [00:00:07.424,713] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: - handler=0x00038209[0m
2023-06-29T14:37:06.249Z DEBUG modem << [00:00:07.433,441] [0m<dbg> lte_lc_helpers: event_handler_list_dispatch: Done[0m
2023-06-29T14:37:06.251Z DEBUG modem << [00:00:07.440,826] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-06-29T14:37:07.093Z DEBUG modem << *** Booting Zephyr OS build v3.2.99-ncs1 ***
2023-06-29T14:37:07.097Z DEBUG modem << Attempting to boot slot 0.
2023-06-29T14:37:07.100Z DEBUG modem << Attempting to boot from address 0x8200.
2023-06-29T14:37:07.287Z DEBUG modem << Verifying signature against key 0.
2023-06-29T14:37:07.467Z DEBUG modem << Hash: 0x0f...ad
2023-06-29T14:37:07.472Z DEBUG modem << Firmware signature verified.
2023-06-29T14:37:07.475Z DEBUG modem << Firmware version 5
2023-06-29T14:37:07.478Z DEBUG modem << Booting (0x8200).

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Thu, 29 Jun 2023 14:01:24 GMT

Hi Didrik, Thanks for your reply,

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/433625"]Thanks for the trace. I cannot see anything obvious that is wrong in the trace, so the problem is probably on the application side.[/quote]

Ok, I'll focus on the app side, but just wondering, why this issue happened after upgrading mwf. And also I waited for a long time and noticed that I dont know how but the device stopped crashing and worked as it should.

and also one more notice, normally when the device is in a reset loop, normally modem was going into restriction mode for 30min. But I can't see it anymore, is this situation normal?

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/433625"]One of the last things that happens in the trace is that it finds a cell that it tries to connect to, and sends a +CEREG: 2 notification to the application, so the handling of that is probably a good place to start looking in the application.[/quote]

Nice information thanks this will make easier my investigation, actually sounds makes sense because I was seeing a crash in the stage of MODEM_EVT_LTE_CELL_UPDATE,

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/433625"]

I'm sorry, but I don't understand what you mean here. Could you clarify?

[/quote]

No please ignore this, I was thinking the log file might be missing something because I didn't see any log on the rtt viewer terminal screen.

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/433625"]

Is the UNKNOWN_CELL_ID event something you have added?

[/quote]

yes, I have added it.

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/433625"]You could try to set CONFIG_LOG_MODE_IMMEDIATE=y. That should make all the logs be handled immediately (like printk), instead of being deferred to later, when the application isn't doing anything else.[/quote]

I have already had this config but it seems it is not exactly working like printk, I am not quite sure but as far as I see it is.

I have no changes on the modem module of the atv2 app. So i thought the issue may be because of a lack of memory size for modem module, So I increased the memory size of it by using config.

CONFIG_MODEM_THREAD_STACK_SIZE = 2048 to 4096

But it doesn't work as well. anyway, I have to fix this issue, any thoughts will be appreciated.

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

Didrik Rokhaug — Thu, 29 Jun 2023 09:00:15 GMT

Thanks for the trace. I cannot see anything obvious that is wrong in the trace, so the problem is probably on the application side.

One of the last things that happens in the trace is that it finds a cell that it tries to connect to, and sends a +CEREG: 2 notification to the application, so the handling of that is probably a good place to start looking in the application.

[quote user="zsn"]I dont know why the terminal screen stack is in there(highlighted line in the picture ) but I hope the log file is ok.[/quote]

I'm sorry, but I don't understand what you mean here. Could you clarify?

Is the UNKNOWN_CELL_ID event something you have added?

[quote user="zsn"]When I used printk instead of LOG, I could see the error where it happened, is there any possibility of converting all logs to printk?[/quote]

You could try to set CONFIG_LOG_MODE_IMMEDIATE=y. That should make all the logs be handled immediately (like printk), instead of being deferred to later, when the application isn't doing anything else.

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Mon, 26 Jun 2023 17:18:09 GMT

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/432743"]If you don't have any UARTs available, you can also try to collect the trace over RTT. See the note here for instructions how, but please share the raw file, and don't the .pcap.[/quote]

Nice to see this, I follow these instructions and generated a log file for you, I hope everything is in it, which to see what the issue is.

in prj.conf

CONFIG_NRF_MODEM_LIB_TRACE=y
CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT=y
CONFIG_NRF_MODEM_LIB_TRACE_LEVEL_FULL=y

how to use jlink rtt logger for windows:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_gsg_ses%2FUG%2Fgsg%2Fconnect_rtt_linux.html

I dont know why the terminal screen stack is in there(highlighted line in the picture ) but I hope the log file is ok.

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/432743"]Instead, you would have to write 1.3.4 with a debugger, which it sounds like you did.[/quote]

I did it but it still didn't work, I flashed back mfw 1.3.4 by debugger but no chance. The same code is working on the board which I didn't have mfw 1.3.5 upgrade

devzone.nordicsemi.com/.../data_2D00_logging_2D00_26_2D00_06_2D00_23_2D00_18_2D00_00.log

Thanks

here I also added uart log output:devzone.nordicsemi.com/.../2023_2D00_06_2D00_26T17_5F00_24_5F00_50.704Z_2D00_log.txt

Line 0 to 393 belong to the board doesn't work which had mfw 1.3.5

Line 456 to the end belongs to the board works well which didn't have any mfw upgrade

When I used printk instead of LOG, I could see the error where it happened, is there any possibility of converting all logs to printk?

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

Didrik Rokhaug — Fri, 23 Jun 2023 15:17:04 GMT

Hi, and sorry for the late reply.

[quote user="zsn"]I cannot collect any modem trace data on my custom board because hw config of it doesn't allow me to do it.[/quote]

If you don't have any UARTs available, you can also try to collect the trace over RTT. See the note here for instructions how, but please share the raw file, and don't the .pcap.

[quote user="zsn"]

the board works with modem fw 1.3.5

Fullscreen

[/quote]

These should be the same HW revision of the SiP.

[quote user="zsn"]here is the modem trace data on the unmodified atv2 on the board, which modem fw 1.3.5 didn't work: trace-2023-06-20T09-44-47.053Z.bin[/quote]

Unfortunately, that trace is not valid. Almost all bytes in the file are 0, and there is not information in it.

Could you try again, using one of the precompiled images you can find on our website?

https://www.nordicsemi.com/Products/Development-hardware/nRF9160-DK/Download?lang=en#infotabs

Make sure that you use an image from the img_app_bl/debug folder, as those images have modem traces enabled (the img_app_bl folder are for images written to the DK via the debugger).

[quote user="zsn"]And also is there any way to downgrade mdm fw 1.3.5 to 1.3.4?[/quote]

It is not possible to do downgrades of the modem FW, only roll back upgrades. I.e. if you did a modem delta upgrade from 1.3.4 to 1.3.5, you could roll back that upgrade, but if you used a debugger to write 1.3.5, you cannot roll back to 1.3.4. Instead, you would have to write 1.3.4 with a debugger, which it sounds like you did.

[quote user="zsn"]I just wrote mdm fw 1.3.4 but now I still have the same issue for mdm fw1.3.4.[/quote]

That is strange

Can you also share the application log from the application starts, until the reset happens?

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Wed, 21 Jun 2023 08:57:03 GMT

And also is there any way to downgrade mdm fw 1.3.5 to 1.3.4? I just wrote mdm fw 1.3.4 but now I still have the same issue for mdm fw1.3.4.

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Tue, 20 Jun 2023 10:16:06 GMT

Hi Didrik, I cannot collect any modem trace data on my custom board because hw config of it doesn't allow me to do it. So I have two nrf9160dk boards and tried the unmodified atv2 app sequently on them. mdm1.3.5 worked on one of them but didn't work on the other.

I checked hw version:

the board works with modem fw 1.3.5

> AT%HWVERSION
%HWVERSION: nRF9160 SICA B1A

the board didn't work with modem fw 1.3.5

AT%HWVERSION
%HWVERSION: nRF9160 SICA BQA

here is the modem trace data on the unmodified atv2 on the board, which modem fw 1.3.5 didn't work: devzone.nordicsemi.com/.../trace_2D00_2023_2D00_06_2D00_20T09_2D00_44_2D00_47.053Z.bin

with mdm1.3.5: I got this errors as well.

2023-06-20T09:38:34.639Z DEBUG modem << %MDMEV: SEARCH STATUS 1
2023-06-20T09:39:36.310Z DEBUG modem << %MDMEV: SEARCH STATUS 2
2023-06-20T09:39:36.410Z DEBUG modem << +CEREG: 2
2023-06-20T09:39:37.423Z DEBUG modem << [00:01:09.154,785] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-06-20T09:40:28.800Z DEBUG modem << [00:02:01.519,653] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2023-06-20T09:40:28.811Z DEBUG modem << [00:02:01.520,294] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, MOD_STAT, LOCATION)[0m
2023-06-20T09:40:28.822Z DEBUG modem << [00:02:01.520,935] [0m<inf> app_event_manager: LOCATION_MODULE_EVT_ACTIVE[0m
2023-06-20T09:40:28.826Z DEBUG modem << [00:02:01.521,942] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2023-06-20T09:40:28.839Z DEBUG modem << [00:02:01.528,076] [0m<inf> app_event_manager: LOCATION_MODULE_EVT_AGPS_NEEDED[0m
2023-06-20T09:40:28.842Z DEBUG modem << [00:02:01.529,846] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2023-06-20T09:40:28.856Z DEBUG modem << [00:02:01.529,876] [1;31m<err> modem_module: modem_info_params_get, error: -22[0m
2023-06-20T09:40:28.859Z DEBUG modem << [00:02:01.529,937] [0m<inf> app_event_manager: MODEM_EVT_MODEM_STATIC_DATA_NOT_READY[0m
2023-06-20T09:40:28.865Z DEBUG modem << [00:02:01.532,928] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2023-06-20T09:40:28.876Z DEBUG modem << [00:02:01.532,928] [1;31m<err> modem_module: modem_info_params_get, error: -22[0m
2023-06-20T09:40:28.881Z DEBUG modem << [00:02:01.533,020] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2023-06-20T09:40:29.890Z DEBUG modem << [00:02:01.622,863] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2023-06-20T09:40:29.904Z DEBUG modem << [00:02:01.622,894] [1;31m<err> modem_module: modem_info_params_get, error: -22[0m
2023-06-20T09:40:29.907Z DEBUG modem << [00:02:01.622,955] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2023-06-20T09:41:31.980Z INFO Modem port is closed

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

Didrik Rokhaug — Tue, 20 Jun 2023 09:23:23 GMT

I am not able to reproduce that crash that you are seeing.

Could you try with an unmodified version of the Asset Tracker v2, to see if you get the same crash then?

Also, if you could take a modem trace when the crash happens, that would let us see if the crash is caused by the modem or not.

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Fri, 16 Jun 2023 10:55:27 GMT

it is the same result, I have still restart the crash.

[00:00:08.233,459] <dbg> modem_module: modem_rsrp_handler: Incoming RSRP status message, RSRP value is -89
+CEREG: 2,"9FF7","0016155A",9
[00:00:08.246,856] <dbg> modem_module: lte_evt_handler: LTE cell changed: Cell ID: 1447258, Tracking area: 40951
[00:00:08.257,507] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
*** Booting Zephyr OS build v3.2.99-ncs1 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0x41...d6
Firmware signature verified.
Firmware version 5
*** Booting Zephyr OS build v3.2.99-ncs1 ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x28000

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

Didrik Rokhaug — Fri, 16 Jun 2023 10:49:58 GMT

[quote user="zsn"]This is the undefined symbol RESET_ON_FATA_ERROR[/quote]

My appologies, that was a typo on my end. It should be CONFIG_RESET_ON_FATAL_ERROR=n

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

zsn — Fri, 16 Jun 2023 10:46:50 GMT

Hi Didrik Rokhaug

Thanks for your quick reply.

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/431449"]CONFIG_RESET_ON_FATA_ERROR[/quote]

This is the undefined symbol RESET_ON_FATA_ERROR

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/431449"]

Have you made any changes to the ATv2 code or configuration?

[/quote]

Yes, I have lots of changes on it. But the thing is until mdm fw upgrading, everything was working well. And after upgrading, as it is seen in the log when the device has MODEM_EVT_LTE_CELL_UPDATE, the reset occurs.

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/431449"]CONFIG_THREAD_NAME=y [/quote]

I just built the project again with only this config. But there is no additional log, everything is the same.

[quote userid="81181" url="~/f/nordic-q-a/100914/modem-fw-upgrading-from-1-3-4-to-1-3-5-issue-on-atv2-app/431449"] see if we get any more information about the crash?[/quote]

honestly speaking, I have been looking for a long time this how to get more info during crash, but I couldn't find anything about what is the best practises to collect crash reports

if I can gues where is the issue approximately, I am using printk instead of LOG_DBG. that works to find out exact point of the issue.

RE: Modem fw upgrading from 1.3.4 to 1.3.5 issue on ATV2 app

Didrik Rokhaug — Fri, 16 Jun 2023 10:34:33 GMT

Hi,

[quote user=""]So after that, I am getting an error below.[/quote]

Just to be sure, are you talking about the reset?

Could you set CONFIG_RESET_ON_FATA_ERROR=n and CONFIG_THREAD_NAME=y in your prj.conf, and see if we get any more information about the crash?

Have you made any changes to the ATv2 code or configuration?

Best regards,

Didrik