Asset_tracker V2 run time buffer overflow in LTE

I run the Asstet_tracker V2. The part of LTE log is as below:

.....
2022-05-19T07:58:34.234Z DEBUG modem << [00:00:33.314,788] [0m<dbg> azure_iot_hub_integration: azure_iot_hub_event_handler: AZURE_IOT_HUB_EVT_CONNECTED[0m
2022-05-19T07:58:34.425Z DEBUG modem << [00:00:33.504,974] [0m<dbg> azure_iot_hub_integration: azure_iot_hub_event_handler: AZURE_IOT_HUB_EVT_READY[0m
2022-05-19T07:58:34.441Z DEBUG modem << [00:00:33.514,892] [0m<dbg> cloud_module: cloud_wrap_event_handler: CLOUD_WRAP_EVT_CONNECTED[0m
2022-05-19T07:58:34.444Z DEBUG modem << [00:00:33.523,651] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTED[0m

after this
[00:00:33.530,120] [0m<dbg> ui_module: state_set: State transition STATE_CLOUD_CONNECTING --> STATE_RUNNING[0m
2022-05-19T07:58:34.461Z DEBUG modem << * buffer overflow detected *

I could not understand the reason of the buffer overflow here and it's solution.  If required, I can send complete Log file.

Parents
  • Hello,

    If required, I can send complete Log file.

    Yes, please. Also, you can provide as much information as possible, such as MFW version and NCS version.

  • HI, I added some DBG measages to data_get() function in main.c of asset_tracker_v2. I added bms_module to default code and made changes in every file where required. The get_data() function prepares the list of requested data.  I observed that when

    app_module_event->data_list[count++] = APP_DATA_BMS;

    is added to get_data() functon, the buffer_overflow mesasge appears in LTE a shown in attached log file. When, 

    app_module_event->data_list[count++] = APP_DATA_BMS;

    is not there in get_data() function, then there is no buffer_overflow and works well.

    The code pf get_data() also is shown here below.

    static void data_get(void)
    {
    	static bool first = true;
    	struct app_module_event *app_module_event = new_app_module_event();
    	size_t count = 0;
    
            LOG_DBG(" Main: Entered data_get()");
    
    	/* Set a low sample timeout. If GNSS is requested, the sample timeout will be increased to
    	 * accommodate the GNSS timeout.
    	 */
    	app_module_event->timeout = 1;
    
    	/* Specify which data that is to be included in the transmission. */
    	app_module_event->data_list[count++] = APP_DATA_MODEM_DYNAMIC;
            LOG_DBG(" Modem_dyn requested through data_list[]");
    	app_module_event->data_list[count++] = APP_DATA_BATTERY;
            LOG_DBG(" APP_BATT requested through data_list[]");
    	app_module_event->data_list[count++] = APP_DATA_ENVIRONMENTAL;
            LOG_DBG(" APP_ENV requested through data_list[]");
    
    	if (IS_ENABLED(CONFIG_APP_REQUEST_NEIGHBOR_CELLS_DATA) && !app_cfg.no_data.neighbor_cell) {
    		app_module_event->data_list[count++] = APP_DATA_NEIGHBOR_CELLS;
    	}
    
            LOG_DBG(" APP_NBR_CELLS requested through data_list[]");
    	/* The reason for having at least 75 seconds sample timeout when
    	 * requesting GNSS data is that the GNSS module on the nRF9160 modem will always
    	 * search for at least 60 seconds for the first position fix after a reboot. This limit
    	 * is enforced in order to give the modem time to perform scheduled downloads of
    	 * A-GPS data from the GNSS satellites.
    	 *
    	 * However, if A-GPS data has been downloaded via the cloud connection and processed
    	 * before the initial GNSS search, the actual GNSS timeout set by the application is used.
    	 *
    	 * Processing A-GPS before requesting GNSS data is enabled by default,
    	 * and the time that the application will wait for A-GPS data before including GNSS
    	 * in sample requests can be adjusted via the
    	 * CONFIG_APP_REQUEST_GNSS_WAIT_FOR_AGPS_THRESHOLD_SEC Kconfig option. If this option is
    	 * set to -1, the application module will not request GNSS unless A-GPS data has been
    	 * processed.
    	 *
    	 * If A-GPS data has been processed the sample timeout can be ignored as the
    	 * GNSS will most likely time out before the sample timeout expires.
    	 *
    	 * When GNSS is requested, set the sample timeout to (GNSS timeout + 15 seconds)
    	 * to let the GNSS module finish ongoing searches before data is sent to cloud.
    	 */
    
    	if (first) {
    		if (IS_ENABLED(CONFIG_APP_REQUEST_GNSS_ON_INITIAL_SAMPLING) && request_gnss() &&
    		    !app_cfg.no_data.gnss) {
    			app_module_event->data_list[count++] = APP_DATA_GNSS;
    			app_module_event->timeout = MAX(app_cfg.gnss_timeout + 15, 75);
                            LOG_DBG(" GNSS requested through data_list[]");
    		}
    
    		app_module_event->data_list[count++] = APP_DATA_MODEM_STATIC;
    		first = false;
    	} else {
    		if (request_gnss() && !app_cfg.no_data.gnss) {
    			app_module_event->data_list[count++] = APP_DATA_GNSS;
    			app_module_event->timeout = MAX(app_cfg.gnss_timeout + 15, 75);
                            LOG_DBG(" GNSS requested through data_list[]");
    		}
    	}
    
            app_module_event->data_list[count++] = APP_DATA_BMS;
            LOG_DBG(" BMS requested through data_list[]");
    
    	/* Set list count to number of data types passed in app_module_event. */
    	app_module_event->count = count;
    	app_module_event->type = APP_EVT_DATA_GET;
    
            LOG_DBG("Ready to launch APP_EVT_DATA_GET Event");
    	APP_EVENT_SUBMIT(app_module_event);
            LOG_DBG("Launched APP_EVT_DATA_GET Event");
    }

    Where overflow occurs, I could not understand ?

    2022-05-26T09:51:56.443Z DEBUG modem << *** Booting Zephyr OS build v2.7.99-ncs1-2195-g186cf4539e5a  ***
    2022-05-26T09:51:56.451Z DEBUG modem << [00:00:00.207,336] [0m<inf> at_host: UART check failed: 1. Dropping buffer and retrying.[0m
    2022-05-26T09:51:56.532Z DEBUG modem << [00:00:00.225,830] [0m<dbg> watchdog: watchdog_timeout_install: Watchdog timeout installed. Timeout: 60[0m
    2022-05-26T09:51:56.534Z DEBUG modem << [00:00:00.235,290] [0m<dbg> watchdog: watchdog_start: Watchdog started[0m
    2022-05-26T09:51:56.538Z DEBUG modem << [00:00:00.242,004] [0m<dbg> watchdog: watchdog_feed_enable: Watchdog feed enabled. Timeout: 30000[0m
    2022-05-26T09:51:56.542Z DEBUG modem << [00:00:00.251,373] [0m<inf> app_event_manager: APP_EVT_START[0m
    2022-05-26T09:51:56.545Z DEBUG modem << [00:00:00.257,171] [0m<dbg> gnss_module: state_set: State: STATE_INIT[0m
    2022-05-26T09:51:56.550Z DEBUG modem << [00:00:00.263,763] [0m<dbg> ui_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
    2022-05-26T09:51:56.554Z DEBUG modem << [00:00:00.272,552] [0m<dbg> ui_module: sub_state_set: Sub state: SUB_STATE_ACTIVE[0m
    2022-05-26T09:51:56.557Z DEBUG modem << [00:00:00.280,181] [0m<dbg> ui_module: sub_sub_state_set: Sub state: SUB_SUB_STATE_GNSS_INACTIVE[0m
    2022-05-26T09:51:56.560Z DEBUG modem << [00:00:00.289,154] [0m<dbg> util_module: state_set: State: STATE_INIT[0m
    2022-05-26T09:51:56.581Z DEBUG modem << [00:00:00.296,234] [0m<inf> bms_module: BMS Thread Start successful: 0[0m
    2022-05-26T09:51:56.584Z DEBUG modem << [00:00:00.302,856] [0m<inf> bms_module: State: STATE_INIT[0m
    2022-05-26T09:51:56.591Z DEBUG modem << [00:00:00.308,471] [0m<inf> bms_module: State transition STATE_INIT --> BMS DETECTED[0m
    2022-05-26T09:51:56.594Z DEBUG modem << [00:00:00.316,345] [0m<dbg> cloud_module: state_set: State: STATE_LTE_INIT[0m
    2022-05-26T09:51:56.614Z DEBUG modem << [00:00:00.323,333] [0m<dbg> cloud_module: sub_state_set: Sub state: SUB_STATE_CLOUD_DISCONNECTED[0m
    2022-05-26T09:51:56.625Z DEBUG modem << [00:00:00.332,305] [0m<dbg> data_module: state_set: State: STATE_CLOUD_DISCONNECTED[0m
    2022-05-26T09:51:56.628Z DEBUG modem << [00:00:00.340,454] [0m<dbg> date_time: date_time_core_register_handler: Registering handler 0x47ba3[0m
    2022-05-26T09:51:56.631Z DEBUG modem << [00:00:00.349,609] [0m<dbg> data_module: config_print_all: Device mode: Active[0m
    2022-05-26T09:51:56.652Z DEBUG modem << [00:00:00.356,933] [0m<dbg> data_module: config_print_all: Active wait timeout: 120[0m
    2022-05-26T09:51:56.659Z DEBUG modem << [00:00:00.364,715] [0m<dbg> data_module: config_print_all: Movement resolution: 120[0m
    2022-05-26T09:51:56.661Z DEBUG modem << [00:00:00.372,497] [0m<dbg> data_module: config_print_all: Movement timeout: 3600[0m
    2022-05-26T09:51:56.670Z DEBUG modem << [00:00:00.380,126] [0m<dbg> data_module: config_print_all: GPS timeout: 60[0m
    2022-05-26T09:51:56.673Z DEBUG modem << [00:00:00.387,145] [0m<dbg> data_module: config_print_all: Accelerometer threshold: 10.00[0m
    2022-05-26T09:51:56.688Z DEBUG modem << [00:00:00.395,446] [0m<dbg> data_module: config_print_all: Requesting of neighbor cell data is enabled[0m
    2022-05-26T09:51:56.691Z DEBUG modem << [00:00:00.404,876] [0m<dbg> data_module: config_print_all: Requesting of GNSS data is enabled[0m
    2022-05-26T09:51:56.695Z DEBUG modem << [00:00:00.413,574] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
    2022-05-26T09:51:56.698Z DEBUG modem << [00:00:00.419,982] [0m<dbg> ui_module: sub_state_set: Sub state: SUB_STATE_ACTIVE[0m
    2022-05-26T09:51:56.700Z DEBUG modem << [00:00:00.428,009] [0m<dbg> main: active_mode_timers_start_all: Device mode: Active[0m
    2022-05-26T09:51:56.716Z DEBUG modem << [00:00:00.435,760] [0m<dbg> main: active_mode_timers_start_all: Start data sample timer: 120 seconds interval[0m
    2022-05-26T09:51:56.724Z DEBUG modem << [00:00:00.445,861] [0m<inf> app_event_manager: APP_EVT_ACTIVITY_DETECTION_DISABLE[0m
    2022-05-26T09:51:56.727Z DEBUG modem << [00:00:00.453,979] [0m<dbg> main: state_set: App State transition STATE_INIT --> STATE_RUNNING[0m
    2022-05-26T09:51:56.729Z DEBUG modem << [00:00:00.462,677] [0m<dbg> main: sub_state_set: App Sub state: SUB_STATE_ACTIVE_MODE[0m
    2022-05-26T09:51:56.743Z DEBUG modem << [00:00:00.470,672] [0m<dbg> main: data_get:  Main: Entered data_get()[0m
    2022-05-26T09:51:56.747Z DEBUG modem << [00:00:00.477,233] [0m<dbg> main: data_get:  Modem_dyn requested through data_list[][0m
    2022-05-26T09:51:56.753Z DEBUG modem << [00:00:00.485,107] [0m<dbg> main: data_get:  APP_BATT requested through data_list[][0m
    2022-05-26T09:51:56.764Z DEBUG modem << [00:00:00.492,889] [0m<dbg> main: data_get:  APP_ENV requested through data_list[][0m
    2022-05-26T09:51:56.769Z DEBUG modem << [00:00:00.500,610] [0m<dbg> main: data_get:  APP_NBR_CELLS requested through data_list[][0m
    2022-05-26T09:51:56.775Z DEBUG modem << [00:00:00.508,850] [0m<dbg> main: data_get:  BMS requested through data_list[][0m
    2022-05-26T09:51:56.792Z DEBUG modem << [00:00:00.516,174] [0m<dbg> main: data_get: Ready to launch APP_EVT_DATA_GET Event[0m
    2022-05-26T09:51:56.795Z DEBUG modem << * buffer overflow detected *
    2022-05-26T09:51:56.800Z DEBUG modem << [00:00:00.526,580] [1;31m<err> os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x00000001[0m
    2022-05-26T09:51:56.817Z DEBUG modem << [00:00:00.535,247] [1;31m<err> os: r3/a4:  0x2002590e r12/ip:  0x2001c9c4 r14/lr:  0x00032117[0m
    2022-05-26T09:51:56.821Z DEBUG modem << [00:00:00.543,884] [1;31m<err> os:  xpsr:  0x61000000[0m
    2022-05-26T09:51:56.828Z DEBUG modem << [00:00:00.549,133] [1;31m<err> os: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000[0m
    2022-05-26T09:51:56.830Z DEBUG modem << [00:00:00.559,509] [1;31m<err> os: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000[0m
    2022-05-26T09:51:56.845Z DEBUG modem << [00:00:00.569,885] [1;31m<err> os: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000[0m
    2022-05-26T09:51:56.848Z DEBUG modem << [00:00:00.580,291] [1;31m<err> os: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000[0m
    2022-05-26T09:51:56.851Z DEBUG modem << [00:00:00.590,637] [1;31m<err> os: fpscr:  0x00000000[0m
    2022-05-26T09:51:56.861Z DEBUG modem << [00:00:00.595,855] [1;31m<err> os: Faulting instruction address (r15/pc): 0x00030b9e[0m
    2022-05-26T09:51:56.864Z DEBUG modem << [00:00:00.603,729] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0[0m
    2022-05-26T09:51:56.869Z DEBUG modem << [00:00:00.611,328] [1;31m<err> os: Current thread: 0x20011658 (unknown)[0m
    2022-05-26T09:51:56.881Z DEBUG modem << [00:00:00.618,133] [0m<dbg> util_module: state_set: State transition STATE_INIT --> STATE_REBOOT_PENDING[0m
    2022-05-26T09:51:56.888Z DEBUG modem << [00:00:00.627,685] [0m<dbg> main: data_get: Launched APP_EVT_DATA_GET Event[0m
    2022-05-26T09:51:56.893Z DEBUG modem << [00:00:00.634,826] [0m<dbg> modem_module: state_set: State transition STATE_INIT --> STATE_DISCONNECTED[0m
    2022-05-26T09:51:56.895Z DEBUG modem << [00:00:00.644,439] [0m<dbg> sensor_module: state_set: State: STATE_INIT[0m
    2022-05-26T09:51:56.907Z DEBUG modem << [00:00:00.651,214] [0m<dbg> sensor_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
    2022-05-26T09:51:56.910Z DEBUG modem << [00:00:00.668,060] [0m<dbg> modem_module: configure_low_power: PSM requested[0m
    2022-05-26T09:51:57.404Z DEBUG modem << [00:00:01.160,583] [0m<inf> bms_module: State transition BMS DETECTED --> STATE_RUNNING[0m
    2022-05-26T09:51:57.410Z DEBUG modem << [00:00:01.168,670] [0m<inf> bms_module: BMS Thread: BMS_FOUND[0m
    2022-05-26T09:51:57.412Z DEBUG modem << 
    2022-05-26T09:52:06.351Z DEBUG modem << *** Booting Zephyr OS build v2.7.99-ncs1-2195-g186cf4539e5a  ***
    2022-05-26T09:52:06.353Z DEBUG modem << 
    2022-05-26T09:52:06.355Z DEBUG modem << I: Starting bootloader
    2022-05-26T09:52:06.360Z DEBUG modem << I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
    2022-05-26T09:52:06.366Z DEBUG modem << I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
    2022-05-26T09:52:06.368Z DEBUG modem << 
    2022-05-26T09:52:06.370Z DEBUG modem << I: Boot source: none
    2022-05-26T09:52:06.372Z DEBUG modem << I: Swap type: none
    2022-05-26T09:52:06.459Z DEBUG modem << I: Bootloader chainload address offset: 0x10000
    2022-05-26T09:52:06.464Z DEBUG modem << I: Jumping to the first image slot
    2022-05-26T09:52:06.939Z DEBUG modem << *** Booting Zephyr OS build v2.7.99-ncs1-2195-g186cf4539e5a  ***
    2022-05-26T09:52:06.952Z DEBUG modem << [00:00:00.207,519] [0m<dbg> watchdog: watchdog_timeout_install: Watchdog timeout installed. Timeout: 60[0m
    2022-05-26T09:52:06.956Z DEBUG modem << [00:00:00.217,010] [0m<dbg> watchdog: watchdog_start: Watchdog started[0m
    2022-05-26T09:52:06.964Z DEBUG modem << [00:00:00.223,724] [0m<dbg> watchdog: watchdog_feed_enable: Watchdog feed enabled. Timeout: 30000[0m
    2022-05-26T09:52:06.970Z DEBUG modem << [00:00:00.233,093] [0m<inf> app_event_manager: APP_EVT_START[0m
    2022-05-26T09:52:06.976Z DEBUG modem << [00:00:00.238,891] [0m<dbg> gnss_module: state_set: State: STATE_INIT[0m
    2022-05-26T09:52:06.985Z DEBUG modem << [00:00:00.245,513] [0m<dbg> ui_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
    2022-05-26T09:52:06.987Z DEBUG modem << 
    2022-05-26T09:52:06.992Z DEBUG modem << [00:00:00.254,272] [0m<dbg> ui_module: sub_state_set: Sub state: SUB_STATE_ACTIVE[0m
    2022-05-26T09:52:06.994Z DEBUG modem << 
    2022-05-26T09:52:07.002Z DEBUG modem << [00:00:00.261,901] [0m<dbg> ui_module: sub_sub_state_set: Sub state: SUB_SUB_STATE_GNSS_INACTIVE[0m
    2022-05-26T09:52:07.008Z DEBUG modem << [00:00:00.270,904] [0m<dbg> util_module: state_set: State: STATE_INIT[0m
    2022-05-26T09:52:07.016Z DEBUG modem << [00:00:00.278,015] [0m<inf> bms_module: BMS Thread Start successful: 0[0m
    2022-05-26T09:52:07.021Z DEBUG modem << [00:00:00.284,606] [0m<inf> bms_module: State: STATE_INIT[0m
    2022-05-26T09:52:07.029Z DEBUG modem << [00:00:00.290,252] [0m<inf> bms_module: State transition STATE_INIT --> BMS DETECTED[0m
    2022-05-26T09:52:07.036Z DEBUG modem << [00:00:00.298,126] [0m<dbg> cloud_module: state_set: State: STATE_LTE_INIT[0m
    2022-05-26T09:52:07.044Z DEBUG modem << [00:00:00.305,084] [0m<dbg> cloud_module: sub_state_set: Sub state: SUB_STATE_CLOUD_DISCONNECTED[0m
    2022-05-26T09:52:07.047Z DEBUG modem << 
    2022-05-26T09:52:07.052Z DEBUG modem << [00:00:00.314,086] [0m<dbg> data_module: state_set: State: STATE_CLOUD_DISCONNECTED[0m
    2022-05-26T09:52:07.062Z DEBUG modem << [00:00:00.322,113] [0m<dbg> date_time: date_time_core_register_handler: Registering handler 0x47ba3[0m
    2022-05-26T09:52:07.069Z DEBUG modem << [00:00:00.331,298] [0m<dbg> data_module: config_print_all: Device mode: Active[0m
    2022-05-26T09:52:07.077Z DEBUG modem << [00:00:00.338,623] [0m<dbg> data_module: config_print_all: Active wait timeout: 120[0m
    2022-05-26T09:52:07.080Z DEBUG modem << 
    2022-05-26T09:52:07.085Z DEBUG modem << [00:00:00.346,405] [0m<dbg> data_module: config_print_all: Movement resolution: 120[0m
    2022-05-26T09:52:07.093Z DEBUG modem << [00:00:00.354,187] [0m<dbg> data_module: config_print_all: Movement timeout: 3600[0m
    2022-05-26T09:52:07.099Z DEBUG modem << [00:00:00.361,816] [0m<dbg> data_module: config_print_all: GPS timeout: 60[0m
    2022-05-26T09:52:07.107Z DEBUG modem << [00:00:00.368,835] [0m<dbg> data_module: config_print_all: Accelerometer threshold: 10.00[0m
    2022-05-26T09:52:07.117Z DEBUG modem << [00:00:00.377,166] [0m<dbg> data_module: config_print_all: Requesting of neighbor cell data is enabled[0m
    2022-05-26T09:52:07.119Z DEBUG modem << 
    2022-05-26T09:52:07.126Z DEBUG modem << [00:00:00.386,596] [0m<dbg> data_module: config_print_all: Requesting of GNSS data is enabled[0m
    2022-05-26T09:52:07.133Z DEBUG modem << [00:00:00.395,294] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
    2022-05-26T09:52:07.140Z DEBUG modem << [00:00:00.401,702] [0m<dbg> ui_module: sub_state_set: Sub state: SUB_STATE_ACTIVE[0m
    2022-05-26T09:52:07.148Z DEBUG modem << [00:00:00.409,729] [0m<dbg> main: active_mode_timers_start_all: Device mode: Active[0m
    2022-05-26T09:52:07.158Z DEBUG modem << [00:00:00.417,480] [0m<dbg> main: active_mode_timers_start_all: Start data sample timer: 120 seconds interval[0m
    2022-05-26T09:52:07.172Z DEBUG modem << [00:00:00.427,581] [0m<inf> app_event_manager: APP_EVT_ACTIVITY_DETECTION_DISABLE[0m
    2022-05-26T09:52:07.262Z DEBUG modem << [00:00:00.435,699] [0m<dbg> main: state_set: App State transition STATE_INIT --> STATE_RUNNING[0m
    2022-05-26T09:52:07.268Z DEBUG modem << [00:00:00.444,396] [0m<dbg> main: sub_state_set: App Sub state: SUB_STATE_ACTIVE_MODE[0m
    2022-05-26T09:52:07.292Z DEBUG modem << [00:00:00.452,423] [0m<dbg> main: data_get:  Main: Entered data_get()[0m
    2022-05-26T09:52:07.296Z DEBUG modem << [00:00:00.458,984] [0m<dbg> main: data_get:  Modem_dyn requested through data_list[][0m
    2022-05-26T09:52:07.299Z DEBUG modem << [00:00:00.466,857] [0m<dbg> main: data_get:  APP_BATT requested through data_list[][0m
    2022-05-26T09:52:07.302Z DEBUG modem << [00:00:00.474,639] [0m<dbg> main: data_get:  APP_ENV requested through data_list[][0m
    2022-05-26T09:52:07.306Z DEBUG modem << [00:00:00.482,360] [0m<dbg> main: data_get:  APP_NBR_CELLS requested through data_list[][0m
    2022-05-26T09:52:07.308Z DEBUG modem << [00:00:00.490,600] [0m<dbg> main: data_get:  BMS requested through data_list[][0m
    2022-05-26T09:52:07.314Z DEBUG modem << [00:00:00.497,955] [0m<dbg> main: data_get: Ready to launch APP_EVT_DATA_GET Event[0m
    2022-05-26T09:52:07.317Z DEBUG modem << * buffer overflow detected *
    2022-05-26T09:52:07.322Z DEBUG modem << [00:00:00.508,361] [1;31m<err> os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x00000001[0m
    2022-05-26T09:52:07.327Z DEBUG modem << [00:00:00.517,028] [1;31m<err> os: r3/a4:  0x2002590e r12/ip:  0x2001c9c4 r14/lr:  0x00032117[0m
    2022-05-26T09:52:07.330Z DEBUG modem << [00:00:00.525,665] [1;31m<err> os:  xpsr:  0x61000000[0m
    2022-05-26T09:52:07.333Z DEBUG modem << [00:00:00.530,883] [1;31m<err> os: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000[0m
    2022-05-26T09:52:07.336Z DEBUG modem << [00:00:00.541,290] [1;31m<err> os: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000[0m
    2022-05-26T09:52:07.364Z DEBUG modem << [00:00:00.551,666] [1;31m<err> os: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000[0m
    2022-05-26T09:52:07.367Z DEBUG modem << [00:00:00.562,072] [1;31m<err> os: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000[0m
    2022-05-26T09:52:07.369Z DEBUG modem << [00:00:00.572,418] [1;31m<err> os: fpscr:  0x00000000[0m
    2022-05-26T09:52:07.372Z DEBUG modem << [00:00:00.577,636] [1;31m<err> os: Faulting instruction address (r15/pc): 0x00030b9e[0m
    2022-05-26T09:52:07.375Z DEBUG modem << [00:00:00.585,510] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0[0m
    2022-05-26T09:52:07.377Z DEBUG modem << [00:00:00.593,139] [1;31m<err> os: Current thread: 0x20011658 (unknown)[0m
    2022-05-26T09:52:07.381Z DEBUG modem << [00:00:00.599,945] [0m<dbg> util_module: state_set: State transition STATE_INIT --> STATE_REBOOT_PENDING[0m
    2022-05-26T09:52:07.401Z DEBUG modem << [00:00:00.609,497] [0m<dbg> main: data_get: Launched APP_EVT_DATA_GET Event[0m
    2022-05-26T09:52:07.404Z DEBUG modem << [00:00:00.616,638] [0m<dbg> modem_module: state_set: State transition STATE_INIT --> STATE_DISCONNECTED[0m
    2022-05-26T09:52:07.406Z DEBUG modem << [00:00:00.626,251] [0m<dbg> sensor_module: state_set: State: STATE_INIT[0m
    2022-05-26T09:52:07.410Z DEBUG modem << [00:00:00.633,026] [0m<dbg> sensor_module: state_set: State transition STATE_INIT --> STATE_RUNNING[0m
    2022-05-26T09:52:07.411Z DEBUG modem << [00:00:00.649,963] [0m<dbg> modem_module: configure_low_power: PSM requested[0m
    2022-05-26T09:52:07.429Z DEBUG modem << 
    2022-05-26T09:52:07.881Z DEBUG modem << [00:00:01.142,425] [0m<inf> bms_module: State transition BMS DETECTED --> STATE_RUNNING[0m
    2022-05-26T09:52:07.889Z DEBUG modem << [00:00:01.150,512] [0m<inf> bms_module: BMS Thread: BMS_FOUND[0m
    

  • And what is the MFW version and NCS version?

Reply Children
Related