Device Randomly Resets During BLE Scanning in Noisy Environments (nRF54L15 + NCS v3.0.2)

[Haresh05]

Hi all,

I'm working on an application using the nRF54L15 with NCS v2.9.0 and Zephyr RTOS. The device performs BLE scanning using the following parameters:

struct bt_le_scan_param scan_param = {
    .type       = BT_LE_SCAN_TYPE_PASSIVE,
    .options    = BT_LE_SCAN_OPT_FILTER_DUPLICATE,
    .interval   = 0x0100,
    .window     = 0x0010,
};

When deployed in a noisy BLE environment (e.g., multiple advertising devices nearby), the device sometimes randomly resets. This happens more frequently with the above scan parameters. Logs don’t show any fatal errors before the reset — it seems like a silent reboot.

However, if I disable BT_EXT_ADV in the configuration of sample application, the issue seems to go away and the device behaves normally even in busy environments.

But in my actual project when I disable BT_EXT_ADV, the scan start failed with error -22.
<wrn> bt_hci_core: opcode 0x200c status 0x12.  To resolve this I enabled  CONFIG_BT_EXT_ADV_LEGACY_SUPPORT and after this my actual project is also behaving normally.

I have attached the sample scan application I am testing.

I am not sure why this different behaviour in both the cases. Any insights or suggestions on this would be really helpful.

scantest.zip

Thanks!

Haresh

[Haresh05]

Hi,

I have made the changes and it seems to work but before that I also changed the SCAN_MSG_MAX_LEN macro to 150 and tried but even then it was getting stuck.
So I am not sure what is the final solution for this or this behaviour is due to the issue you mentioned here?

Vidar Berg said:

I was made aware of this issue by a coworker, and it seems to resemble the same issue you're experiencing: nrfxlib v3.0.2: BLE scanning results stop being reported  . 

Regards,

Haresh

[Vidar Berg]

Hi Haresh,

Yes, it's possible that the buffer overflow was only part of the issue. Have you been able to reproduce the problem after fixing it? The other issue from the linked ticket is still being investigated internally. Hopefully there will be an update on it soon.

Regards,

Vidar