Can not flash stm32wb5x_Zigbee_FFD_fw.bin

[Exeu]

Hi,

i have a bit of situation here.

I wanted to try a zigbee example from cube mx (On/off ED).

So i first flashed the FUS v2.2.0 on the device.

But now it turns out that i can not flash the desired FW anymore : stm32wb5x_Zigbee_FFD_fw.bin.

It only errors :(

I have the feeling that this FW is not working with FUS 2.2?

If so - I am right that i can not downgrade FUS anymore once it is updated?

This basically would mean i wasted hundreds of EURs for those dev boards.

[Exeu]

[Issamos]

Hello @Exeu 

It should work fine with the FUS 2.2.0. Are you sure about the starting address you are setting. Are you using the last STM32Cubeprogrammer. If so, could you please share the result of reading the FUS and stack version using the Read FUS Version button on the CubeProgrammer and the error message you are having. Also, what is  the complete part number of your MCU?

Best Regards.

II

[Exeu]

Hi @Issamos 

sure

Here is FUS Info - Before Update

 Then the file i have choosen + the correct start address which should be: 0x0809F000 - According to the release notes.

Since i am using the Nucleo board it should be the WB55RG mcu.

Then the error:

This error does not come when i flash any FUS_v2_only binaries - See the screenshot of my reply above with the List coming from the releasenotes file.

The borad is the following: https://www.st.com/en/evaluation-tools/p-nucleo-wb55.html

 

[Alan PORTE · Accepted solution]

Hello @Exeu,

I was able to install stm32wb5x_Zigbee_FFD_fw.bin v1.24.0 with FUS 2.2.0 on my Nucleo-WB55RG.
Using STM32CubeProgrammer v2.21.0:

You are getting error message "failed to erase memory", thus I would recommend to check the configuration of your option bytes. Check if there is no RDP / PCROP / Write Protection enabled.

You should have something similar to this:

Best Regards,
Alan Porte
ST MCU Support Team

[Exeu]

Hi @Alan PORTE 

I dunno what is the difference from what I tried but it seems to work now.

What is interesting: I tried with the automatic address determination.

This was running through but it also putted the stack on a different address as mentioned in the release notes?

It was up an running then.

After doing this I was also able to flash it with the address which should be the real one..

Have no idea why :face_with_tears_of_joy: