STM32WB55 - FUS_STATE_IMG_NOT_FOUND

[peter627]

Hello all,

I have been running into a lot of issues trying to get the firmware for the BLE onto my board using the STM32WB55RG.

Now I did follow this video and originally got it working, but then I accidently hit delete firmware and was unable to get it on again. Right now any time I try to upgrade my firmware I always get the WARNING: FUS_STATE_IMG_NOT_FOUND.

I have tried doing a mass erase and then re-upgrading as I saw in another post but that also will not work.

Here is the list of steps I take right now:
1. Plug in board

2. Connect via STM32CubeProgrammer

3. Start FUS

4. Read FUS Info

5. Attempt to upgrade stm32wb5x_BLE_Stack_full_fw.bin at 0x080C7000

6. Receive error message

This is a custom board, but I did at one point have the BLE working on it.

Here is my option bytes configuration:

[theARTof1337 · Accepted solution]

I've successfully upgraded FUS and installed wireless stack using STMCubeProgrammer. Try the steps listed in my previuos topic...
https://community.st.com/t5/stm32-mcus-wireless/cannot-flash-ble-wireless-stack-into-stm32wb55cg-usb-dongle-fus/td-p/809775

[peter627]

Dude I love you so much. It worked.

I was fiddling around with this for like 4 hours yesterday after I accidently messed it up and thought I was gonna have to solder on new chips.

[peter627]

So I have uploaded the firmware successfully and when I read it, it seems correct.
And I am able to successfully start the wireless stack from the WB Commands.

But when I try using the same code I did before my BLE is not able to initialize. Not sure if you have used the stm32duinoble library which is what I am using, but if you have, any ideas on what is going on would be appreciated.

I have tried starting the wireless stack before flashing code and it still wont initialize too.

[valilai]

Hi,

for everyone landing on this page where the suggested solution of @theARTof1337 is not working, here is my solution:

The FUS must be installed in the correct order: v0.5.3.0 -> v1.2.0 -> v2.1.0 !
The big problem for me was that (04.11.25) the v0.5.3 seem to be the v1.20... some file/meta data mismatch i guess.

Idk whats happening here because i did get the files from latest github (https://github.com/STMicroelectronics/STM32CubeWB/tree/v1.23.0)

So yea, i needed to do Firmware Upgrade in this order:

1. *fw_0_5_3.bin (aka v1.2.0) on 0x080EC000

2. *fw.bin (aka v2.1.0) on 0x080EE000

I also did before every Firmware Upgrade an "Start FUS" and next "Read FUS infos". Idk if this does something really because it first started to work after i noticed the version mismatch between filename and GUI "Selected file" info.