STM32WB BLE Stack 1.23.0 Not Working on STM32WB55CGU6 – Firmware Version Shows v0.0.0.0

[NTH106]

Describe the Setup

Device: STM32WB55CGU6

Tool: STM32CubeProgrammer

Describe the Issue
When attempting to flash the BLE stack version 1.23.0 to the STM32WB55CGU6 using STM32CubeProgrammer, I encountered issues with the following firmware files:

stm32wb5x_BLE_Stack_full_extended_fw.bin

stm32wb5x_BLE_Stack_full_fw.bin

stm32wb5x_BLE_Stack_light_fw.bin

The version information is not displayed in the “Selected File” section of STM32CubeProgrammer. After flashing, the FUS reports version v0.0.0.0, indicating that the firmware may be invalid or improperly formatted. This makes it impossible to proceed with BLE stack initialization or further development.

I would greatly appreciate any clarification on whether these binaries are compatible with the STM32WB55CGU6 and, if not, whether a corrected version of the BLE stack 1.23.0 can be provided.

Additionally, since I’m unable to downgrade the firmware on my device, I would like to kindly ask if it’s possible to release version 1.24.0 of the BLE stack ahead of schedule, as this may help resolve the issue.

Thank you for your support.

 

 

[STTwo-32]

Hello @NTH106 and welcome to the ST Community.

Could you please try using the STM32CubeProgrammer V2.20.0 and use the automatic start address selection feature. Also, if needed try with first install option activated.

Best Regards.

STTwo-32

[NTH106]

Hi ST team,

I'm working with an STM32WB55CGU6. After a power failure during option byte configuration, the device entered SafeBoot.

Now the FUS version shows as v0.0.0.0
FUS state: FUS_ERROR
FUS status: FUS_NOT_RUNNING

I have tried the following:

Wrote 0x00008000 to address 0x5800040C to activate CM0+

Flashed stm32wb5x_FUS_fw.bin to address 0x080EC000 successfully

Reset the board and reconnected via CubeProgrammer

However, FUS is still stuck and cannot be started.
I also previously flashed 0x495_FUS_Operator.bin to 0x08000000 by mistake, which may have caused corruption.

Is there any way to fully recover FUS in this situation?
Can ST provide a low-level recovery method or tool for this case?

Thanks in advance.