BLE scanning base on lte_ble_gateway and app crash

RE: BLE scanning base on lte_ble_gateway and app crash

Einar Thorsrud — Mon, 25 Nov 2024 18:23:44 GMT

Hi,

I am sorry for the delay. There is a issue with stable communication between the nRF91 and nRF52840 in this sample and inherited by your application, and we are continuing to look into it.

RE: BLE scanning base on lte_ble_gateway and app crash

hogen — Thu, 14 Nov 2024 01:53:44 GMT

Hi, Thank you for your efforts.

I'll try to reduce the scan window to test and see if I can reduce the probability of the problem happening.

RE: BLE scanning base on lte_ble_gateway and app crash

Einar Thorsrud — Wed, 13 Nov 2024 15:09:07 GMT

Hi,

I am sorry for the delay. I have not made much progress on my end. This is n old demo that is a bit unstable under load, and that seems to have always been the case. I am continuing to look into it, but it may take some time. Please let me know if you have any progress on your end as well.

Br,

Einar

RE: BLE scanning base on lte_ble_gateway and app crash

Einar Thorsrud — Wed, 23 Oct 2024 13:14:00 GMT

Hi,

A short update from my. Using your project and nRF Connect SDK 2.2.0 I am able to reproduce the issue, but I do not have an explanation for the cause. I will continue to look into it.

RE: BLE scanning base on lte_ble_gateway and app crash

Einar Thorsrud — Fri, 18 Oct 2024 13:08:38 GMT

Hi,

I am sorry for the delay. I will look into this and get bac to you next week.

RE: BLE scanning base on lte_ble_gateway and app crash

hogen — Mon, 14 Oct 2024 03:14:58 GMT

Hi, I'm sorry for the delay in responding due to my vacation.
I have add the configuration you suggested in the 52840 and test it again. In this test, 9160 starts a 90ms scan every 3000ms. From the log, we can see the nrf9160 starts scan every 3000ms, and the nrf52840 also has some LOG every 3000ms.

1. The following log is the last normal scan before reset. I found every time a peripherial was scanned, nrf52840 will print the following log.
-event_packet_process: LE Meta Event (0x02), len...

From nrf9160 log, we can see it start scan and the stop scan normal. The log indication that it scaned 16 packet.
----------------------------------------------------------------------------------------------------------
[01:24:54.855,285] [0m<inf> lte_ble_gw: scan_work_callback: start scan success[0m
[01:24:54.935,363] [0m<inf> lte_ble_gw: scan_work_callback: Stop scan success:16, num:3298[0m

From nrf52840 log, it also indication that it scaned 16 packet.
-----------------------------------------------------------------
[01:24:50.418,792] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.410,034] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:53.410,491] <dbg> lpuart: activate_rx: RX: Ready
[01:24:53.410,552] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:53.410,675] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 1
[01:24:53.410,705] <dbg> lpuart: uart_callback: Rx buf released
[01:24:53.410,736] <dbg> lpuart: uart_callback: Rx disabled
[01:24:53.410,766] <dbg> lpuart: api_rx_buf_rsp: buf rsp, state:5
[01:24:53.410,797] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:53.411,132] <dbg> lpuart: activate_rx: RX: Ready
[01:24:53.411,285] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:53.411,407] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 9
[01:24:53.411,499] <dbg> lpuart: uart_callback: Rx buf released
[01:24:53.411,529] <dbg> lpuart: uart_callback: Rx disabled
[01:24:53.411,529] <dbg> lpuart: api_rx_buf_rsp: buf rsp, state:5
[01:24:53.411,590] <dbg> bt_hci_raw: bt_send: buf 0x2000da04 len 9
[01:24:53.411,590] <dbg> sdc_hci_driver: hci_driver_send:
[01:24:53.411,621] <dbg> sdc_hci_driver: cmd_handle:
[01:24:53.411,682] <dbg> sdc_hci_driver: hci_driver_send: Exit: 0
[01:24:53.411,712] <dbg> sdc_hci_driver: event_packet_process: Command Complete (0x2005) status: 0x00, ncmd: 1, len 4
[01:24:53.411,743] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 6
[01:24:53.412,048] <dbg> lpuart: api_tx: tx len:7
[01:24:53.414,367] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.414,489] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.414,886] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:53.415,191] <dbg> lpuart: activate_rx: RX: Ready
[01:24:53.415,252] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:53.415,374] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 1
[01:24:53.415,405] <dbg> lpuart: uart_callback: Rx buf released
[01:24:53.415,435] <dbg> lpuart: uart_callback: Rx disabled
[01:24:53.415,435] <dbg> lpuart: api_rx_buf_rsp: buf rsp, state:5
[01:24:53.415,496] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:53.415,802] <dbg> lpuart: activate_rx: RX: Ready
[01:24:53.415,954] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:53.416,076] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 10
[01:24:53.416,137] <dbg> lpuart: uart_callback: Rx buf released
[01:24:53.416,168] <dbg> lpuart: uart_callback: Rx disabled
[01:24:53.416,198] <dbg> lpuart: api_rx_buf_rsp: buf rsp, state:5
[01:24:53.416,229] <dbg> bt_hci_raw: bt_send: buf 0x2000da04 len 10
[01:24:53.416,259] <dbg> sdc_hci_driver: hci_driver_send:
[01:24:53.416,259] <dbg> sdc_hci_driver: cmd_handle:
[01:24:53.416,320] <dbg> sdc_hci_driver: hci_driver_send: Exit: 0
[01:24:53.416,381] <dbg> sdc_hci_driver: event_packet_process: Command Complete (0x200b) status: 0x00, ncmd: 1, len 4
[01:24:53.416,412] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 6
[01:24:53.416,717] <dbg> lpuart: api_tx: tx len:7
[01:24:53.418,945] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.419,036] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.419,433] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:53.419,738] <dbg> lpuart: activate_rx: RX: Ready
[01:24:53.419,799] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:53.419,921] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 1
[01:24:53.419,952] <dbg> lpuart: uart_callback: Rx buf released
[01:24:53.419,982] <dbg> lpuart: uart_callback: Rx disabled
[01:24:53.419,982] <dbg> lpuart: api_rx_buf_rsp: buf rsp, state:5
[01:24:53.420,043] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:53.420,349] <dbg> lpuart: activate_rx: RX: Ready
[01:24:53.420,471] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:53.420,562] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 5
[01:24:53.420,623] <dbg> lpuart: uart_callback: Rx buf released
[01:24:53.420,654] <dbg> lpuart: uart_callback: Rx disabled
[01:24:53.420,684] <dbg> lpuart: api_rx_buf_rsp: buf rsp, state:5
[01:24:53.420,745] <dbg> bt_hci_raw: bt_send: buf 0x2000da04 len 5
[01:24:53.420,776] <dbg> sdc_hci_driver: hci_driver_send:
[01:24:53.420,776] <dbg> sdc_hci_driver: cmd_handle:
[01:24:53.420,928] <dbg> sdc_hci_driver: hci_driver_send: Exit: 0
[01:24:53.420,959] <dbg> sdc_hci_driver: event_packet_process: Command Complete (0x200c) status: 0x00, ncmd: 1, len 4
[01:24:53.420,989] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 6
[01:24:53.421,295] <dbg> lpuart: api_tx: tx len:7
[01:24:53.423,553] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.423,675] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.425,384] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (37)
[01:24:53.425,415] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 39
[01:24:53.425,689] <dbg> lpuart: api_tx: tx len:40
[01:24:53.427,886] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.428,314] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.428,680] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (42)
[01:24:53.428,710] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 44
[01:24:53.428,985] <dbg> lpuart: api_tx: tx len:45
[01:24:53.429,718] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (43)
[01:24:53.429,748] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 45
[01:24:53.431,152] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.431,640] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.431,701] <dbg> lpuart: api_tx: tx len:46
[01:24:53.434,051] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.434,539] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.435,699] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (43)
[01:24:53.435,729] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 45
[01:24:53.436,004] <dbg> lpuart: api_tx: tx len:46
[01:24:53.438,201] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.438,690] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.445,373] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (42)
[01:24:53.445,404] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 44
[01:24:53.445,678] <dbg> lpuart: api_tx: tx len:45
[01:24:53.446,105] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (37)
[01:24:53.446,136] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 39
[01:24:53.448,028] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.448,547] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.448,577] <dbg> lpuart: api_tx: tx len:40
[01:24:53.449,645] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (42)
[01:24:53.449,676] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 44
[01:24:53.450,927] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.451,385] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.451,416] <dbg> lpuart: api_tx: tx len:45
[01:24:53.453,796] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.454,284] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.457,794] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (37)
[01:24:53.457,824] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 39
[01:24:53.458,099] <dbg> lpuart: api_tx: tx len:40
[01:24:53.460,479] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.460,906] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.462,249] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (42)
[01:24:53.462,310] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 44
[01:24:53.462,585] <dbg> lpuart: api_tx: tx len:45
[01:24:53.464,752] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.465,240] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.466,339] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (36)
[01:24:53.466,400] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 38
[01:24:53.466,674] <dbg> lpuart: api_tx: tx len:39
[01:24:53.468,841] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.469,207] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (42)
[01:24:53.469,268] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.469,299] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 44
[01:24:53.469,573] <dbg> lpuart: api_tx: tx len:45
[01:24:53.471,740] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.472,229] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.479,858] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (30)
[01:24:53.479,888] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 32
[01:24:53.480,163] <dbg> lpuart: api_tx: tx len:33
[01:24:53.482,543] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.482,910] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.484,283] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (37)
[01:24:53.484,313] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 39
[01:24:53.484,588] <dbg> lpuart: api_tx: tx len:40
[01:24:53.486,785] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.487,213] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.487,945] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (42)
[01:24:53.487,976] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 44
[01:24:53.488,281] <dbg> lpuart: api_tx: tx len:45
[01:24:53.490,447] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.490,936] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.495,056] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (43)
[01:24:53.495,086] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 45
[01:24:53.495,361] <dbg> lpuart: api_tx: tx len:46
[01:24:53.497,711] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.498,229] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.498,291] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (38)
[01:24:53.498,321] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 40
[01:24:53.498,596] <dbg> lpuart: api_tx: tx len:41
[01:24:53.498,687] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:53.498,779] <dbg> lpuart: activate_rx: RX: Ready
[01:24:53.498,870] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:53.498,962] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 1
[01:24:53.498,992] <dbg> lpuart: uart_callback: Rx buf released
[01:24:53.499,023] <dbg> lpuart: uart_callback: Rx disabled
[01:24:53.499,053] <dbg> lpuart: api_rx_buf_rsp: buf rsp, state:5
[01:24:53.499,084] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:53.499,145] <dbg> lpuart: activate_rx: RX: Ready
[01:24:53.499,237] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:53.499,359] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 5
[01:24:53.499,420] <dbg> lpuart: uart_callback: Rx buf released
[01:24:53.499,450] <dbg> lpuart: uart_callback: Rx disabled
[01:24:53.499,481] <dbg> lpuart: api_rx_buf_rsp: buf rsp, state:5
[01:24:53.499,542] <dbg> bt_hci_raw: bt_send: buf 0x2000da04 len 5
[01:24:53.499,542] <dbg> sdc_hci_driver: hci_driver_send:
[01:24:53.499,572] <dbg> sdc_hci_driver: cmd_handle:
[01:24:53.499,694] <dbg> sdc_hci_driver: hci_driver_send: Exit: 0
[01:24:53.499,786] <dbg> sdc_hci_driver: event_packet_process: Command Complete (0x200c) status: 0x00, ncmd: 1, len 4
[01:24:53.499,816] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 6
[01:24:53.500,762] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.501,220] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:53.501,251] <dbg> lpuart: api_tx: tx len:7
[01:24:53.503,631] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:53.503,753] <dbg> lpuart: tx_complete: TX completed, pin idle

2. The following logs shows that nrf9160 encountered error and reset.
nrf9160 log
---------------------------
[01:24:57.945,251] [0m<inf> lte_ble_gw: scan_work_callback: start scan success[0m
[01:24:58.019,958] [1;31m<err> bt_driver: process_tx: TX interrupt but no pending buffer![0m
ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:329

The following is the corresponding log for nrf52840. It seens that NRF52840 received a start scan request and start scan success.
It shows that nrf52840 has been scanning continuously and scaned 187 peripherial packet. I thins it because 52840 does not receive stop scan request from nrf9160.

Also In this log, a large number of logs were dropped, I thorough it may because 9160 was reset. I tried manually resetting 9160 during the 52840 scanning process, there will also be a large number of dropped log.
-----------------------------------------------------------------
[01:24:56.499,969] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:56.500,427] <dbg> lpuart: activate_rx: RX: Ready
[01:24:56.500,488] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:56.500,610] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 1
[01:24:56.500,640] <dbg> lpuart: uart_callback: Rx buf released
[01:24:56.500,671] <dbg> lpuart: uart_callback: Rx disabled
[01:24:56.500,701] <dbg> lpuart: api_rx_buf_rsp: buf rsp, state:5
[01:24:56.500,732] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:56.501,037] <dbg> lpuart: activate_rx: RX: Ready
[01:24:56.501,220] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:56.501,342] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 9
[01:24:56.501,403] <dbg> lpuart: uart_callback: Rx buf released
[01:24:56.501,434] <dbg> lpuart: uart_callback: Rx disabled
[01:24:56.501,464] <dbg> lpuart: api_rx_buf_rsp: buf rsp, state:5
[01:24:56.501,495] <dbg> bt_hci_raw: bt_send: buf 0x2000da04 len 9
[01:24:56.501,525] <dbg> sdc_hci_driver: hci_driver_send:
[01:24:56.501,525] <dbg> sdc_hci_driver: cmd_handle:
[01:24:56.501,586] <dbg> sdc_hci_driver: hci_driver_send: Exit: 0
[01:24:56.501,647] <dbg> sdc_hci_driver: event_packet_process: Command Complete (0x2005) status: 0x00, ncmd: 1, len 4
[01:24:56.501,678] <dbg> bt_hci_raw: bt_recv: buf 0x2000dc50 len 6
[01:24:56.501,953] <dbg> lpuart: api_tx: tx len:7
[01:24:56.504,302] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.
[01:24:56.504,394] <dbg> lpuart: tx_complete: TX completed, pin idle
[01:24:56.504,791] <dbg> lpuart: rdy_pin_handler: RX: Request detected.
[01:24:56.505,096] <dbg> lpuart: activate_rx: RX: Ready
[01:24:56.505,157] <dbg> lpuart: rdy_pin_handler: RX: End detected.
[01:24:56.505,279] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 1
--- 19 messages dropped ---
[01:24:56.509,826] <dbg> lpuart: uart_callback: RX: Ready buf:0x20004bb4, offset: 0,len: 1
--- 17 messages dropped ---
[01:24:56.511,230] <dbg> lpuart: api_tx: tx len:7
--- 13 messages dropped ---
[01:24:56.523,651] <dbg> lpuart: tx_complete: TX completed, pin idle
--- 15 messages dropped ---
[01:24:56.535,247] <dbg> sdc_hci_driver: event_packet_process: LE Meta Event (0x02), len (30)
--- 21 messages dropped ---
[01:24:56.547,668] <dbg> lpuart: tx_complete: TX completed, pin idle
--- 9 messages dropped ---
[01:24:56.554,779] <dbg> lpuart: req_pin_handler: TX: Confirmed, starting.

The attachment are the log file of 52840 and 9160, lpuart prj file, and the project of lte_ble_gateway. The log file for 52840 is quite large, so I have cropped the rest of the content.

devzone.nordicsemi.com/.../test_5F00_log.zip

RE: BLE scanning base on lte_ble_gateway and app crash

Einar Thorsrud — Fri, 04 Oct 2024 10:10:21 GMT

dHi,

If the reset you shows in the nRF52840 (the BT Controller) is expected, then there is nothing specificaly indicating an issue on that side. But both asserts you get on the nRF91 are caused by communication issues, where the BT host implementation on the nRF91 is not ablet o communicate with the BT controller. The samples for both deviceds use LPUART with ASYNC uart with HW byte counting (CONFIG_UART_x_NRF_HW_ASYNC), so the UART communication should be stable in itself.

Then there is the fact that you see this issue more often when there are more BT devices, which points in a different direction. Perhaps soem buffer or queue gets full and that is not handled properly. Based on the asserts you see on the 91, this points to the nRF52. So it would be interestin to add some BT debug logging on the nRF52840 and see if that will tell us more. Do you see anything interesting if you add CONFIG_BT_DEBUG_LOG=y to the hci_lpuart prj.conf? You can refer to or use the debug configuration for the sample.

RE: BLE scanning base on lte_ble_gateway and app crash

Einar Thorsrud — Thu, 03 Oct 2024 14:37:50 GMT

Hi,

I am sorry for the late reply. I am looking into this and will get back to you tomorrow.

RE: BLE scanning base on lte_ble_gateway and app crash

hogen — Mon, 30 Sep 2024 01:41:14 GMT

Thank you for your suggestion. I have change the prj file of the hci_lpuart project like follow:
# Segger RTT enable
CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_LOG_BACKEND_RTT=y

I have enabled UART log tracking for hci_lpuart, but I found that when there is an exception in the lte_ble_gateway, hci_lpuart only has one restart log. I think this is because the lte-ble_gateway reset it. Do I need to enable the debug log for hci_lpuart?

the log of hci_lpuart

-----------------------------------

[09:10:36.310] RX←◆[00:00:00.000,152] [0m<inf> board_control: vcom0_pins_routing is ENABLED[0m
[00:00:00.000,213] [0m<inf> board_control: vcom2_pins_routing is ENABLED[0m
[00:00:00.000,244] [0m<inf> board_control: led1_pin_routing is ENABLED[0m
[00:00:00.000,305] [0m<inf> board_control: led2_pin_routing is ENABLED[0m
[00:00:00.000,335] [0m<inf> board_control: led3_pin_routing is ENABLED[0m
[00:00:00.000,366] [0m<inf> board_control: led4_pin_routing is ENABLED[0m
[00:00:00.000,427] [0m<inf> board_control: switch1_pin_routing is ENABLED[0m
[00:00:00.000,457] [0m<inf> board_control: switch2_pin_routing is ENABLED[0m
[00:00:00.000,518] [0m<inf> board_control: button1_pin_routing is ENABLED[0m
[00:00:00.000,549] [0m<inf> board_control: button2_pin_routing is ENABLED[0m
[00:00:00.000,610] [0m<inf> board_control: nrf_interface_pins_0_2_routing is ENABLED[0m
[00:00:00.000,640] [0m<inf> board_control: nrf_interface_pins_3_5_routing is ENABLED[0m
[00:00:00.000,701] [0m<inf> board_control: nrf_interface_pins_6_8_routing is disabled[0m
[00:00:00.000,732] [0m<inf> board_control: GPIO reset line enabled on pin P1.02, holding...[0m
[00:00:00.000,762] [0m<inf> board_control: Board configured.[0m
*** Booting Zephyr OS build v3.2.99-ncs1 ***
[00:00:00.001,251] [0m<inf> sdc_hci_driver: SoftDevice Controller build revision:
6d 90 41 2a 38 e8 ad 17 29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
1f 85 d8 e1 |.... [0m
[00:00:00.001,861] [0m<inf> bt_hci_raw: Bluetooth enabled in RAW mode[0m

[09:26:50.049]RX←◆[00:00:00.000,152] [0m<inf> board_control: vcom0_pins_routing is ENABLED[0m
[00:00:00.000,213] [0m<inf> board_control: vcom2_pins_routing is ENABLED[0m
[00:00:00.000,274] [0m<inf> board_control: led1_pin_routing is ENABLED[0m
[00:00:00.000,305] [0m<inf> board_control: led2_pin_routing is ENABLED[0m
[00:00:00.000,335] [0m<inf> board_control: led3_pin_routing is ENABLED[0m
[00:00:00.000,396] [0m<inf> board_control: led4_pin_routing is ENABLED[0m
[00:00:00.000,427] [0m<inf> board_control: switch1_pin_routing is ENABLED[0m
[00:00:00.000,488] [0m<inf> board_control: switch2_pin_routing is ENABLED[0m
[00:00:00.000,518] [0m<inf> board_control: button1_pin_routing is ENABLED[0m
[00:00:00.000,579] [0m<inf> board_control: button2_pin_routing is ENABLED[0m
[00:00:00.000,610] [0m<inf> board_control: nrf_interface_pins_0_2_routing is ENABLED[0m
[00:00:00.000,671] [0m<inf> board_control: nrf_interface_pins_3_5_routing is ENABLED[0m
[00:00:00.000,701] [0m<inf> board_control: nrf_interface_pins_6_8_routing is disabled[0m
[00:00:00.000,732] [0m<inf> board_control: GPIO reset line enabled on pin P1.02, holding...[0m
[00:00:00.000,762] [0m<inf> board_control: Board configured.[0m
*** Booting Zephyr OS build v3.2.99-ncs1 ***
[00:00:00.001,251] [0m<inf> sdc_hci_driver: SoftDevice Controller build revision:
6d 90 41 2a 38 e8 ad 17 29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
1f 85 d8 e1 |.... [0m
[00:00:00.001,861] [0m<inf> bt_hci_raw: Bluetooth enabled in RAW mode[0m

the log of lte_ble_gateway

-------------------------------------------------------------------

[09:10:32.618]RX←◆*** Booting Zephyr OS build v3.2.99-ncs1 ***

[09:10:33.623]RX←◆[00:00:00.543,884] [0m<inf> lte_ble_gw: LTE Sensor Gateway sample started[0m
[00:00:00.544,097] [0m<inf> lte_ble_gw: Initializing Bluetooth..[0m

[09:10:37.327]RX←◆[00:00:04.250,335] [1;33m<wrn> bt_hci_core: opcode 0x0000 pool id 3 pool 0x2000de4c != &hci_cmd_pool 0x2000deb4[0m
[00:00:04.346,374] [0m<inf> lte_ble_gw: Bluetooth ready[0m
[00:00:04.346,405] [0m<inf> lte_ble_gw: Scanning...[0m

[09:10:42.437]RX←◆[00:00:09.359,863] [0m<inf> lte_ble_gw: start scan success[0m
[00:00:09.449,188] [0m<inf> lte_ble_gw: Stop scan success:28, num:2[0m

[09:10:43.526]RX←◆[00:00:10.449,920] [0m<inf> lte_ble_gw: start scan success[0m
[00:00:10.540,069] [0m<inf> lte_ble_gw: Stop scan success:31, num:4[0m

[09:10:44.616]RX←◆[00:00:11.539,886] [0m<inf> lte_ble_gw: start scan success[0m
[00:00:11.637,542] [0m<inf> lte_ble_gw: Stop scan success:28, num:6[0m

[09:10:45.706]RX←◆[00:00:12.629,943] [0m<inf> lte_ble_gw: start scan success[0m
[00:00:12.713,134] [0m<inf> lte_ble_gw: Stop scan success:27, num:8[0m

... I have omitted some same logs

..............................................................

[09:26:29.630]RX←◆[00:15:56.593,475] [0m<inf> lte_ble_gw: start scan success[0m
[00:15:56.676,361] [0m<inf> lte_ble_gw: Stop scan success:21, num:1740[0m

[09:26:30.720]RX←◆[00:15:57.683,502] [0m<inf> lte_ble_gw: start scan success[0m
[00:15:57.787,109] [0m<inf> lte_ble_gw: Stop scan success:34, num:1742[0m

[09:26:31.812]RX←◆[00:15:58.773,529] [0m<inf> lte_ble_gw: start scan success[0m
[00:15:58.857,940] [0m<inf> lte_ble_gw: Stop scan success:21, num:1744[0m

[09:26:32.901]RX←◆[00:15:59.86
[09:26:32.940]RX←◆3,525] [0m<inf> lte_ble_gw: start scan success[0m
[00:15:59.971,649] [0m<inf> lte_ble_gw: Stop scan success:37, num:1746[0m

[09:26:33.991]RX←◆[00:16:00.953,613] [0m<inf> lte_ble_gw: start scan success[0m
[00:16:01.041,534] [0m<inf> lte_ble_gw: Stop scan success:28, num:1748[0m

[09:26:35.081]RX←◆[00:16:02.043,640] [0m<inf> lte_ble_gw: start scan success[0m
[00:16:02.140,380] [0m<inf> lte_ble_gw: Stop scan success:31, num:1750[0m

[09:26:36.171]RX←◆[00:16:03.133,636] [0m<inf> lte_ble_gw: start scan success[0m
[00:16:03.221,740] [0m<inf> lte_ble_gw: Stop scan success:29, num:1752[0m

[09:26:37.260]RX←◆[00:16:04.223,663] [0m<inf> lte_ble_gw: start scan success[0m
[00:16:04.311,218] [0m<inf> lte_ble_gw: Stop scan success:26, num:1754[0m

[09:26:38.352]RX←◆[00:16:05.313,781] [0m<inf> lte_ble_gw: start scan success[0m
[00:16:05.400,054] [0m<inf> lte_ble_gw: Stop scan success:26, num:1756[0m

[09:26:39.440]RX←◆[00:16:06.403,686] [0m<inf> lte_ble_gw: start scan success[0m
[00:16:06.480,438] [1;31m<err> bt_driver: TX interrupt but no pending buffer![0m
[00:16:06.480,438] [1;31m<err> bt_driver: TX interrupt but no pending buffer![0m

[09:26:48.518]RX←◆ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:329
k_sem_take failed with err -11
[00:16:16.489,959] [1;33m<wrn> bt_driver: Discarding event 0x3e[0m
[00:16:16.491,088] [1;31m<err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x00000000[0m
[00:16:16.491,088] [1;31m<err> os: r3/a4: 0x00016e71 r12/ip: 0x00000000 r14/lr: 0x00010677[0m
[00:16:16.491,119] [1;31m<err> os: xpsr: 0x41000000[0m
[00:16:16.491,119] [1;31m<err> os: Faulting instruction address (r15/pc): 0x00010682[0m
[00:16:16.491,149] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0[0m
[00:16:16.491,180] [1;31m<err> os: Current thread: 0x200108f8 (unknown)[0m
[00:16:16.542,175] [1;31m<err> fatal_error: Resetting system[0m\0
[09:26:49.351]RX←◆*** Booting Zep
[09:26:49.384]RX←◆hyr OS build v3.2.99-ncs1 ***

[09:26:50.354]RX←◆[00:00:00
[09:26:50.376]RX←◆.501,708] [0m<inf> lte_ble_gw: LTE Sensor Gateway sample started[0m

RE: BLE scanning base on lte_ble_gateway and app crash

Einar Thorsrud — Thu, 26 Sep 2024 08:10:00 GMT

Hi,

I am sorry for the delay.

The log here shows an assert that also indicate a problem on the controller side (nrf52). Have you been able to enable logging on that side? It may be simplest to enable debugging of the nRF and select RTT as logg backend in this case. The question is what happens on the nRF52 side and next, what we can do about it.

PS: the nRF52840 on the nRF9160 DK mainly functions as a board controller, and the gateway sample was made as a demo for the Thingy:91 that can also be built on the DK. So it should be regarded more as a proof of concept than anything else.

RE: BLE scanning base on lte_ble_gateway and app crash

hogen — Thu, 19 Sep 2024 01:13:12 GMT

Hi, my entire project files is as follows:

devzone.nordicsemi.com/.../lte_5F00_ble_5F00_gateway_5F00_test.zip

RE: BLE scanning base on lte_ble_gateway and app crash

hogen — Thu, 19 Sep 2024 01:09:16 GMT

Hi,

I have added the following configuration on nrf91, increasing TX COUNT to 12. After a period of Bluetooth scanning, the app still crashed. Is there any other possible reason? thanks!

//project configuration:
CONFIG_LOG_BUFFER_SIZE=8192
CONFIG_BT_BUF_CMD_TX_COUNT=12
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_DEBUG_HCI_CORE=y
Disabled LTE calling in the test:
//work_init();
//cloud_init();
//modem_configure();
//cloud_connect(NULL);

crash log

----------------------------------------------------------------

[00:04:10.581,329] [0m<dbg> bt_hci_core: process_events: ev->state 0[0m
[00:04:10.581,481] [0m<dbg> bt_hci_core: hci_tx_thread: Calling k_poll with 2 events[0m
[00:04:11.263,366] [1;33m<wrn> lpuart: uart_callback: Uart events flipped.[0m
ASSERTION FAIL [data->rx_state == RX_ACTIVE] @ WEST_TOPDIR/nrf/drivers/serial/uart_nrf_sw_lpuart.c:435
[00:04:17.907,989] [1;31m<err> os: esf_dump: r0/a1: 0x00000004 r1/a2: 0x000001b3 r2/a3: 0x00000000[0m
[00:04:17.907,989] [1;31m<err> os: esf_dump: r3/a4: 0x00018211 r12/ip: 0x00000000 r14/lr: 0x0001929b[0m
[00:04:17.908,020] [1;31m<err> os: esf_dump: xpsr: 0x41000041[0m
[00:04:17.908,050] [1;31m<err> os: esf_dump: Faulting instruction address (r15/pc): 0x0002c320[0m
[00:04:17.908,081] [1;31m<err> os: z_fatal_error: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0[0m
[00:04:17.908,081] [1;31m<err> os: z_fatal_error: Fault during interrupt handling
[0m
[00:04:17.908,142] [1;31m<err> os: z_fatal_error: Current thread: 0x200107e8 (unknown)[0m
[00:04:17.966,949] [1;31m<err> fatal_error: k_sys_fatal_error_handler: Resetting system[0m
*** Booting Zephyr OS build v3.2.99-ncs1 ***

devzone.nordicsemi.com/.../lte_5F00_ble_5F00_gateway_5F00_debug_5F00_log_5F00_0919.txt

RE: BLE scanning base on lte_ble_gateway and app crash

Einar Thorsrud — Fri, 13 Sep 2024 11:00:36 GMT

Hi,

If there was an error on the controller side (nRF52), I would have expected that you would see an error and typically a reset in the log. The assert that you see on the nRF91 (host) is related to a mtimeout on senidng a HCI command though, so somethig is causing a breakdown of communication between the hos tand controller. Perhasp it would make sense to increase the CONFIG_BT_BUF_CMD_TX_COUNT?

If not, then I suggest enabling more logging on both sides to see if we can learn more about what is happening. Perhaps start with CONFIG_BT_HCI_CORE_LOG_LEVEL_DBG=y on the nRF91?

RE: BLE scanning base on lte_ble_gateway and app crash

hogen — Thu, 12 Sep 2024 08:54:09 GMT

Hi, thanks for your replay.

We did some testing and monitored the nrf52840 logs, but nothing seemed to be wrong. Do I need to enable other log configuration? The details are as follows.

We started the test at 14:56. At 15:08, nrf52840 detected the reset indication and then reset. This reboot should be caused by the reset of nrf9160 lte_ble_gateway.

I guess it might be the uart interface, nrf52840 sends a large number of scanned advertisements, causing nrf9160 to handle abnormally?

During our test, If there are few BLE devices around, this problem generally does not occur.

---------------------

nrf52840 log
------------------------------------------------------
[14:56:43.288]RX←◆*** Booting Zephyr OS build v3.2.99-ncs1 ***
[00:00:00.000,152] [0m<inf> board_control: init: vcom0_pins_routing is ENABLED[0m
[00:00:00.000,213] [0m<inf> board_control: init: vcom2_pins_routing is ENABLED[0m
[00:00:00.000,274] [0m<inf> board_control: init: led1_pin_routing is ENABLED[0m
[00:00:00.000,305] [0m<inf> board_control: init: led2_pin_routing is ENABLED[0m
[00:00:00.000,366] [0m<inf> board_control: init: led3_pin_routing is ENABLED[0m
[00:00:00.000,396] [0m<inf> board_control: init: led4_pin_routing is ENABLED[0m
[00:00:00.000,457] [0m<inf> board_control: init: switch1_pin_routing is ENABLED[0m
[00:00:00.000,518] [0m<inf> board_control: init: switch2_pin_routing is ENABLED[0m
[00:00:00.000,549] [0m<inf> board_control: init: button1_pin_routing is ENABLED[0m
[00:00:00.000,610] [0m<inf> board_control: init: button2_pin_routing is ENABLED[0m
[00:00:00.000,671] [0m<inf> board_control: init: nrf_interface_pins_0_2_routing is ENABLED[0m
[00:00:00.000,732] [0m<inf> board_control: init: nrf_interface_pins_3_5_routing is ENABLED[0m
[00:00:00.000,762] [0m<inf> board_control: init: nrf_interface_pins_6_8_routing is disabled[0m
[00:00:00.000,793] [0m<inf> board_control: reset_pin_configure: GPIO reset line enabled on pin P1.02, holding...[0m
[00:00:00.000,823] [0m<inf> board_control: init: Board configured.[0m
[00:00:00.005,462] [0m<inf> sdc_hci_driver: hci_driver_open: SoftDevice Controller build revision:
6d 90 41 2a 38 e8 ad 17 29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
1f 85 d8 e1 |.... [0m
[00:00:00.006,072] [0m<inf> bt_hci_raw: bt_enable_raw: Bluetooth enabled in RAW mode[0m

[15:08:53.686]RX←◆GPIO reset line asserted, device reset.
Bye @ cycle32 23876461
[15:08:54.384]RX←◆*** Booting Zephyr OS build v3.2.99-ncs1 ***
[00:00:00.000,152] [0m<inf> board_control: init: vcom0_pins_routing is ENABLED[0m
[00:00:00.000,213] [0m<inf> board_control: init: vcom2_pins_routing is ENABLED[0m
[00:00:00.000,274] [0m<inf> board_control: init: led1_pin_routing is ENABLED[0m
[00:00:00.000,305] [0m<inf> board_control: ini

devzone.nordicsemi.com/.../sdk2.2_5F00_nrf9160_5F00_lte_5F00_ble_5F00_gateway_5F00_log.txt devzone.nordicsemi.com/.../sdk2.2_5F00_nrf52840_5F00_hci_5F00_lpuart_5F00_log.txt

RE: BLE scanning base on lte_ble_gateway and app crash

Einar Thorsrud — Wed, 11 Sep 2024 08:35:47 GMT

Hi,

The logs yuou have shown here from the nRF9160 side indicate that there is no longer communication with the Bluetooth controller, which runs on the nRF52840 on the DK, so the next step is to look into what is happening there. Can you retrieve logs from the nRF52840?

RE: BLE scanning base on lte_ble_gateway and app crash

hogen — Tue, 10 Sep 2024 02:31:53 GMT

Sorry, we added a function in hci_core.c that resulted in incorrect numbering.
I have re-downloaded Version SDK 2.2.0. We have retested and there are still issues.
In this test, We did not make any modifications to the prj.conf file and overlay file. Keeping UART at the default rate of 1000000 and not modifying the ACL_SX size. To avoid the influence of LTE modems, we have comments the LTE section.

Test condition:
-SDK version: v2.2.0
-tools: nrf9160dk, hardware version: v1.1.3
-hci_lpuart:
* not change prj.conf and overlay file
-lte_ble_gateway
* replace the ble.c file
* comments the lte code
void main(void)
{
LOG_INF("LTE Sensor Gateway sample started");

buttons_leds_init();
ble_init();

//work_init();
//cloud_init();
//modem_configure();
//cloud_connect(NULL);
}

Error log on sdk 2.2:

devzone.nordicsemi.com/.../sdk2.2_5F00_error_5F00_log.txt

We also conducted a test on SDK 2.6. We did not make any modifications to the prj.conf file and overlay file. Keeping UART at the default rate of 1000000 and not modifying the ACL_SX size, but kept the LTE code. During testing, some errors were also encountered.

Test condition:
-SDK version: v2.6.0
-tools: nrf9160dk, hardware version: v1.1.3
-hci_lpuart:
* not change prj.conf and overlay file
-lte_ble_gateway
* replace the ble.c file

Error log on SDK2.6.0:

devzone.nordicsemi.com/.../sdk_5F00_v2.6_5F00_error_5F00_log.txt

RE: BLE scanning base on lte_ble_gateway and app crash

Einar Thorsrud — Mon, 09 Sep 2024 14:41:21 GMT

Hi,

Can you double check which SDK version you are using, and if you have any changes on your end? I ask as there is no assert on line 335 in zephyr/subsys/bluetooth/host/hci_core.c in nRF Connect SDK 2.2.0.

That said, it looks like communication issues with the network core. Do you have logs for the network core as well? If so, can you share those?

Br,

Einar

RE: BLE scanning base on lte_ble_gateway and app crash

hogen — Sun, 08 Sep 2024 07:17:05 GMT

Sorry, I missed some content in my description above. I have added the following configuration items to the prj.conf file of hci_lpuart:

#increase mtu
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251

#add tx power control support
CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y
CONFIG_BT_HCI_VS=y
CONFIG_BT_HCI_VS_EXT=y

------------------------------------------------

After repeated testing, we found that in addition to the above-mentioned crashes, sometimes the following crashes may occur:

[11:23:33.358]RX←◆[00
[11:23:33.385]RX←◆:19:04.338,867] [0m<inf> lte_ble_gw: start scan success[0m
[00:19:04.456,756] [0m<inf> lte_ble_gw: Stop scan success:18, num:2090[0m

[11:23:34.441]RX←◆[00:19:05.421,875] [0m<inf> lte_ble_gw: start scan success[0m
[00:19:05.497,192] [1;33m<wrn> bt_driver: Unable to send H:4 type[0m

[11:23:35.555]RX←◆[00:19:06.535,491] [0m<inf> lte_ble_gw: GNSS NMEA data ready[0m

[11:23:43.516]RX←◆ASSERTI
[11:23:43.544]RX←◆ON FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:335
k_sem_take failed with err -11
[00:19:15.508,422] [1;31m<err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x00000000[0m
[00:19:15.508,453] [1;31m<err> os: r3/a4: 0x000178cd r12/ip: 0x00000000 r14/lr: 0x000110cf[0m
[00:19:15.508,453] [1;31m<err> os: xpsr: 0x41000000[0m
[00:19:15.508,483] [1;31m<err> os: Faulting instruction address (r15/pc): 0x000110da[0m
[00:19:15.508,514] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0[
[11:23:43.583]RX←◆0m
[00:19:15.508,544] [1;31m<err> os: Current thread: 0x2000eef8 (unknown)[0m
[00:19:15.553,466] [1;31m<err> fatal_error: Resetting system[0m\0