cancel
Showing results for 
Search instead for 
Did you mean: 

Nucleo-WB55RG BLE Not Working on Zephyr

umut373
Associate

Hi everyone,

I am encountering an issue while trying to run the Zephyr Bluetooth peripheral sample on a Nucleo-WB55RG board.

I am currently working with the Zephyr main branch (specifically commit v4.3.0-2267-g3be4c4c5a819).

Hardware & Firmware Setup:

  • Board: Nucleo-WB55RG

  • FUS Version: V2.2.0.0

  • Wireless Stack: V1.20.0.2 (stm32wb5x_BLE_HCILayer_fw)

  • Zephyr Version: v4.3.0-2267-g3be4c4c5a819

I have explicitly started the Wireless Stack on the M0+ core (using STM32CubeProgrammer), but upon booting the Zephyr application on the M4 core, I get a kernel oops regarding an HCI command timeout after like 10 seconds.

Error Log:

*** Booting Zephyr OS build v4.3.0-2267-g3be4c4c5a819 ***
[00:00:00.017,000] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.017,000] <inf> fs_nvs: alloc wra: 0, fe8
[00:00:00.017,000] <inf> fs_nvs: data wra: 0, 0
ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:506
        Controller unresponsive, command opcode 0xfc0c timeout with err -11
[00:00:10.018,000] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x00000002
[00:00:10.018,000] <err> os: r3/a4:  0x00000003 r12/ip:  0x00000010 r14/lr:  0x08005b6b
[00:00:10.018,000] <err> os:  xpsr:  0x01000000
[00:00:10.018,000] <err> os: Faulting instruction address (r15/pc): 0x08005b78
[00:00:10.018,000] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:10.018,000] <err> os: Current thread: 0x20001428 (unknown)
[00:00:10.056,000] <err> os: Halting system

I selected Wireless Stack V1.20.0.2 based on the compatibility table provided in the zephyrproject-rtos/hal_stm32 repository: https://github.com/zephyrproject-rtos/hal_stm32/blob/2c18f2b49d66d23cabfbd20dd7dbbaef8ee9520b/lib/stm32wb/README.rst

 

The error opcode 0xfc0c seems to point to ACI_HAL_WRITE_CONFIG_DATA, suggesting a communication issue between the Host (Zephyr) and the Controller (M0+ Coprocessor) during initialization.

Has anyone experienced this timeout with the recent Zephyr main branch on STM32WB? Is there a specific configuration or a different stack version required for the latest main branch?

Thanks in advance for your help.

0 REPLIES 0