(ZEPHYR + BL651 chip) CPU continuous looping in k32src_wait and hence advertising doesn't get enabled

[laird_user]

Hello

Our custom board has two chip configurations for BLE stack.
The two chips communicate with each other through UART. Both chips are running zephyr with two chip configuration.

Problem - The board is not discover able.

Analysis -
The reason came out to be that the controller (which has hci_uart code) was stuck in k32src_wait (controller/ll_sw/ctrl.c) during radio_adv_enable.
After commenting k32src_wait, board was very well discover able.

So my question is, Should the line k32src be commented or the problem is somewhere else?

Thanks!

[awneil]

laird_user said:

BL651 chip (sic?)

Do you mean the BL651 module  - from Laird ?

https://connectivity.lairdtech.com/wireless-modules/bluetooth-modules/bluetooth-5-modules/bl651-series

[laird_user]

Yes BL651 module from Laird

[Øyvind]

Hello,

The Zephyr HCI example "hci_uart", running on the nRF52 platform, is qualified and listed on bluetooth.org, which means that it operates per. the Bluetooth test and qualification requirements. I'd recommend asking the Zephyr community about this:

https://www.zephyrproject.org/developers/how-to-contribute/

Kind regards,
Oeyvind