Page 1 of 1

Unexpected reset when BLE scanning and high density of devices

Posted: Thu May 25, 2023 12:27 pm
by andurbal
Dear Sirs

we have founded a problem that is critical in our product.
Suddlenly we have very often (20 or 30 secons) unexpected resets form the BT library. It occurs when we place our product in a high density bluetooth devices.
We use BT Dual Mode as we need both BT Classic and BLE.

Using at this moment ESP IDf v4.4.4-439-gc25d92074e

We sart and stop BT Classic Inquirys (3 secs scan) Stop, Wait some seconds an Start again, for looking near devices.
We also launch BLE Scan for close devices.

As said when we place the product in a hign density bluetooh devices we have started to see BT crashes very very often.

There are some logs of the crashes (not always the same message).

E (29892) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (29892) task_wdt: - IDLE (CPU 0)
E (29892) task_wdt: Tasks currently running:
E (29892) task_wdt: CPU 0: BTC_TASK
E (29892) task_wdt: CPU 1: IDLE
E (29892) task_wdt: Aborting.

[0;31mE (24922) BT_OSI: list_append osi_calloc failed.
�[0;31mE (24923) BT_HCI: host_recv_pkt_cb couldn't aquire memory for inbound data buffer.
�[0;31mE (26816) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:�[0m
�[0;31mE (26816) task_wdt: - IDLE (CPU 0)�[0m
�[0;31mE (26816) task_wdt: Tasks currently running:�[0m
�[0;31mE (26816) task_wdt: CPU 0: BTC_TASK�[0m
�[0;31mE (26816) task_wdt: CPU 1: IDLE�[0m
�[0;31mE (26816) task_wdt: Aborting.�[0m

I Attach the files with the crashses.

Its really urgent to find what is happenuing as this is a Stopper for our product release, and we have some thousands working.