STM32WB55 FUS issue ==> firmware not authentic or reconnexion issue during upgrade

[bboulet]

Hello,

I' trying to update the FUS on my STM32WB55CG (1M), I have the latest STM32Cube_FW_WB_V1.3.0, I followed the Release_Notes in the STM32WB_Copro_Wireless_Binaries :

for information I use this chip on my own board (not a nucleo)

I switched the MCU in bootloader

then

• STEP 3 : Delete current wireless stack :
  • STM32_Programmer_CLI.exe -c port=usb1 -fwdelete

then

STEP 4 : Read and upgrade FUS Version

• STM32_Programmer_CLI.exe -c port=usb1 -r32 0x20030030 1
  • 0x20030030 : 00050300 : FUSv0.5.3 => Must be updated using STEP 5.
  • 0x20030030 : 01000100 or 01000200 : FUSv1.0.x => Up to date, you can download the new wireless stack using STEP6.

so I need to update it

STEP 5 : Download new FUS :

• STM32_Programmer_CLI.exe -c port=usb1 -fwupgrade [FUS_Binary] [Install@] firstinstall=0

in my case

STM32_Programmer_CLI.exe -c port=usb1 -vb 2 -fwupgrade stm32wb5x_FUS_fw.bin 0x080EC000 firstinstall=0

I increse the verbose mode to 2 (I join the log file flash_FUS_VB2)

most of the time the upgrade fail during the reconnecting process after Deleting firmware...

if this part pass I have a firmware not authentic at the end

Reconnecting...

Reconnected

Reconnected !

sending an abort request

setting the address pointer to address: 0xffff0054

sending an abort request

FUS state is FUS_UPGRADE_ONGOING

FUS status is FUS_IMAGE_NOT_AUTHENTIC

Error: Firmware not authentic!

and obviously because of this I can't upload the BLE stack.

Your help would be really appreciate, we have a nice project based on this and we would like move forward on this topic.

regards,

Benjamin

[Vyacheslav]

Hi, Benjamin.

In AN5185, "Table 1" is written:

If an STM32WB5xG device has FUS V1.0.1, then there is no need to upgrade to V1.0.2, since it does not bring any new feature/change vs. V1.0.1.

In case FUS V1.0.2 installation is started by user on an STM32WB5xG device with FUS V1.0.1, FUS returns FUS_STATE_IMG_NOT_AUTHENTIC error and discard the upgrade.

Best regards,

Vyacheslav.

[bboulet]

Hello Vyacheslav,

I agree with you but in my case the stm32wb55cg has FUSv0.5.3 installed, and I have this problem when I try to upgrade in FUS1.0.1.

regards,

Benjamin

[Vyacheslav]

Oh, sorry.

It happens to me too.

I try to fill in the FUS several times with the firstinstall value I set it to 0 or to 1.

But I did not notice the logic when a successful update occurs.

[bboulet]

I also selected 0 then 1 but the result is :

if firstinstall is 1 :

most of the time the upgrade fail during the reconnecting process after Deleting firmware.

if firstinstall is 0:

FUS status is FUS_IMAGE_NOT_AUTHENTIC

Error: Firmware not authentic!

[Vyacheslav]

How about to try to load FUS ver 1.0.1 from SDK 1.1.0 ?

[bboulet]

Good idea, I gonna try !

[bboulet]

It worked, but I'm not comfortable to understand why, and I would do this only on one board I don't have more in provious version anymore

[Vyacheslav]

It’s the same with me.

After I put the fus 1.0.1, I don’t touch it anymore 🙂

It seems to me, that this is due to the first revisions of stones that have some kind of glitches.

[bboulet]

Finally I understood my problem, the boot pin SHALL be pull to VDD during ALL the update