P-NUCLEO-WB55 BLE stack and FUS programming problems

Andrea_Mutti · ‎2025-09-24

Hi all,

i'm working on a project involving BLE and I wanted to use the P-NUCLEO-WB55 board as a BLE sniffer as described here: https://wiki.st.com/stm32mcu/wiki/Connectivity:STM32_Sniffer_for_BLE_Setup_guide#Hardware

I managed to find a P-NUCLEO-WB55 board used by a colleague for old projects and I was trying to follow the guide at previous link to set-up the board but I cannot download the BLE stack, nor update the FUS.

I am using STM32CubeProgrammer 2.20.0, and by reading FUS infos I get the following reply:

The option bytes are set as listed in the attached file.

I tried also to follow the procedure shown in this video (How to program a STM32WB55 with STM32CubeProgrammer ) having the following result:

Is it possible to restore the stack on this board?

Kind regards,

Andrea

Christophe Arnal · ‎2025-09-30

Hello,

I guess the device is likely part of some demo board that has been provided is some show room when the product has been launched. At this time, very few unsecure boards were provided to run some demonstration. Obviously, there is no ST assets there (no FUS, no Key used for authentication).

Unfortunately, the only thing you can do with this board is to have fun with a Dual core product but there is no way to restore any wireless firmware there.

The reason why I can confirm the above point is that the option bytes dump you provided showed the ESE bit set to '0' which means "Device not secure" and all memories (SRAM, FLASH are not secured - FSD, BRSD, NBRSD).

Regards.

View solution in original post

STTwo-32 · ‎2025-09-24

Hello @Andrea_Mutti and welcome to the ST Community

Could you please try to:

Open the STM32CubeProgrammer V2.20.0.
Go to the FUS tab, select the path of the stm32wb5x_FUS_fw_for_fus_0_5_3.bin from the STM32CubeWB V1.23.0(make sure to use the last STM32CubeWB version), make sure to select the Start address automatic determination option and click on the Firmware Upgrade button.
If this works fine, do the same as step 2 with the stm32wb5x_FUS_fw.bin.
After that, go and upload the Stack you want (same process as .bin files of the FUSs).
Read FUS infos to check if it is well installed and use the Start wireless Stack to be able to use your board without issues on a Wireless application.

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Andrea_Mutti · ‎2025-09-26

Hello @STTwo-32 ,

unfortunately the update using stm32wb5x_FUS_fw_for_fus_0_5_3.bin file does not work.

I attach an image with the log I get from STM32CubeProgrammer:

STTwo-32 · ‎2025-09-26

Reading the FUS info (using the Read FUS info button). What do you have?

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Andrea_Mutti · ‎2025-09-26

I get the following:

Christophe Arnal · ‎2025-09-30

Hello,

I guess the device is likely part of some demo board that has been provided is some show room when the product has been launched. At this time, very few unsecure boards were provided to run some demonstration. Obviously, there is no ST assets there (no FUS, no Key used for authentication).

Unfortunately, the only thing you can do with this board is to have fun with a Dual core product but there is no way to restore any wireless firmware there.

The reason why I can confirm the above point is that the option bytes dump you provided showed the ESE bit set to '0' which means "Device not secure" and all memories (SRAM, FLASH are not secured - FSD, BRSD, NBRSD).

Regards.

Andrea_Mutti · ‎2025-09-30

Hello @Christophe Arnal ,

thank you for your help.

I guess I'll need a new board, then.

Regards,

Andrea