FUS default version programmed in STM32WB5CG has been upgraded to 1.1.0？

[lbo.1]

I got some STM32WB55CG samples from st office and the date code is 034. The read out FUS version is 1.1.0. Has the default firmware been upgraded? So the customer doesn't have to upgrade FUS anymore?

​

​

​

D:\Program Files\STMicroelectronics\stm32cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe -c port=SWD mode=HOTPLUG -r32 0x20030030 4 -r32 0x20030024 50

     -------------------------------------------------------------------

                      STM32CubeProgrammer v2.5.0

     -------------------------------------------------------------------

​

ST-LINK SN : 32FF6C063047463341421351

ST-LINK FW : V2J37S7

Board      : --

Voltage    : 3.23V

SWD freq   : 4000 KHz

Connect mode: Hot Plug

Reset mode : Software reset

Device ID  : 0x495

Revision ID : Rev Y

Device name : STM32WBxx

Flash size : 1 MBytes

Device type : MCU

Device CPU : Cortex-M0+/M4

​

​

Reading 32-bit memory content

 Size         : 4 Bytes

 Address:     : 0x20030030

​

0x20030030 : 01010100

​

​

​

Reading 32-bit memory content

 Size         : 52 Bytes

 Address:     : 0x20030024

​

0x20030024 : A94656B9 00000001 01010000 01010100

0x20030034 : 00000006 00000000 00000000 00000000

0x20030044 : 00000000 00000000 00658473 0080E126

0x20030054 : 00000496

[Parmin Nayani]

Hi Remi QUINTIN,

Thank you so much for immediate reply. Helps a lot. Will post the bits so you can guide further.

Best Regards

NPS

[Parmin Nayani]

Hi Remi QUINTIN,

Here are the screenshots.

[Parmin Nayani]

Not able to upload many files simultaneously

[Parmin Nayani]

One more

[Parmin Nayani]

Last one

[Remi QUINTIN]

​OK. So according to the SFSA value (0xF6), your FUS version is still V0.5.3 which is the very first version of FUS.

You have to upgrade it to be able to program one of the RF stack of the latest CubeWB FW pacakage.

Please use the last CubeWB FW package v1.9.

Perform a mass erase of the flash memory. Dont worry , you will get an error when the tool tries to erase the FUS protected sectors (above SFSA location).  But in the end, the user part of the memory becomes clean.

Then perform a fwdelete. Here you may not need it as there is no RF stack on your chip curently.

Then program the stm32wb5x_FUS_fw_1_0_2.bin  binary (= FUS V1.0.2)

Then program the stm32wb5x_FUS_fw..bin binary (= FUS V1.1.0)

Then program the RF stack you want using the start address listed in the release notes.

Finnaly program your application at 0x08000000.

Normally it should work!!! anyhow cross the fingers, it may help :)

[Parmin Nayani]

Thank you very much. Will do and update.

Best regards

[Parmin Nayani]

Missed to post FUS readings. Here they are

[Remi QUINTIN]

​Yes! You can either select the sectors up to F6 not included or select a full chip erase. This will generate an error but it is in fact a warning indicating that not all sectors have been erased. but it is ok.

[Parmin Nayani]

Yes sir. Got it. Thank you. Will follow your earlier post and update. Regards.

[Mecanix]

@Remi QUINTIN​ 

In STM32CubeIDE; can you remind us how and where to verify we are running the latest CubeWB FW package please. You mentioned that FW package v1.9 is out and I did not know that, neither wouldn't be able to tell if STM32CubeIDE is using the latest APIs from 1.9.

What is the ST guidance on remaining updated with the STM32WB? or is this something that is carried out automatically via background downloads from/by STM32CubeIDE?

Thanks

[Mecanix]

ok, I get it, I think. 1.9 released on the Github repo, however not yet supported within STM32CubeIDE. Is this correct?

ps. just found out how to manually check for package updates. Spoiled by the automatic updates of CubeIDE, I got lazy in checking I'm guessing ;)

[Remi QUINTIN]

​CubeWB FW package V1.8 is for sure supported by CubeIDE. I need to check for V1.9

[Remi QUINTIN]

​The usual way to start a project is to use CubeMX tool. You can check for any CubeFW  package update each time you want to configure your project. (see picture below)

[Mecanix]

Appreciate the reply and confirmation. I'll get the MX toolchain dwloaded and updated and see how that goes.

So far, and all of what has been developed onto the STM32WB SoC, was entirely done on STM32CubeIDE at my end.

Btw. thanks for the continuous and invaluable support you provide us with here. Your comments in several other posts saved us a whole lot of trouble and solved quite a few mysteries we were facing. Thought I'd take this opportunity to say thanks!

All the best