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]

Hurrah!!!! Was able to update FUS to 1.1 version. A big thank you to Remi QUINTIN. Now I test some functions and trouble Remi QUINTIN again in case of any issues:grinning_face:. I am giving below my experience. Maybe it will help someone who is looking to update.

I followed Remi QUINTIN suggestions, which can be read in the above posts. I used Cube programmer and not CLI. After selecting and deleting all blocks I tried to update FUS version to 1.0.2 but I saw the programmer entering an infinite loop. Waited for several minutes before closing the application. Disconnected the board from PC. Started afresh. This time I checked the first install and tried again. Programmer showed me 50% complete and stopped. Waited for some time and again closed the application, pulled out the board from USB and started afresh and read the FUS version through Cube Programmer. I was pleasantly surprised to see new version 1.0.2. Now I did the same steps for version 1.1.0. Check first install, start programming. Cube will stop at 50%. Wait for a while, disconnect everything. Connect again and read FUS version. Viola you are there!!! New version is 1.1.0

You will get version 1.0.2 from STM32Cube_FW_WB_V1.1.1 which will be in your repository folder and you will find two FUS files in the latest version 1.8. Please read the release notes which describes the files.

Now I need to update the dongle. Hope it also goes through as Nucleo board went. A bit jittery :sad_but_relieved_face:

[Parmin Nayani]

Hi all,

Back again with a problem !!!

I was able to get FUS 1.1.0.0 loaded. I then loaded "stm32wb5x_BLE_Stack_full_fw.bin". I had to follow same procedure of checking first install etc. Again Cube programmer stopped at 50%. I waited for some time disconnected and connected again. Thereafter programmed the application "BLE_p2pServer_reference.hex".

Now I opened the ST BLE Sensor app on my mobile. The app is searching for BT devices and not detecting the Nucleo board. I checked FUS status through programmer. It shows FUS_IDLE, no errors and version to be v1.1.0.0 . How to know if the application in the Nucleo board is running or not? Thanks for your help.

[Remi QUINTIN]

As usual, the right to start from is to check the options bytes on your dongle.

I assume you checked the box​ "start stack after upgrade"

[Parmin Nayani]

Yes sir. I did. The yellow LED on the ST-Link side blinks but not the other three LEDs that are supposed to be used by the application. Also curious to know, though the board shows ST-Link why is it that programmers sees only USB1? Is there anything I am missing? Thank you for your time.

Best regards

[Parmin Nayani]

Hi Remi QUINTIN,

I tried to read the binary file memory location 0x080CB000. The connection gets lost and I need to restart afresh. However I am able to read code from 0x8000000.

[Remi QUINTIN]

​Could you please download the option bytes.

You won't be able to read above address 0x080CB000. This area is protected from all read/write accesses once the SFSA is set to 0xCB. Hence the importance to know what are the option bytes.

CubeProgrammer tool can use either SWD or USB ports (or UART). It depends pn how you set the Nucleo board.

[Parmin Nayani]

Hi Remi QUINTIN,

Here are the option bytes.

RDP - AA

BOR_LEV - 0

User configuration screenshot is here -

SFSA - 0xf4

Should I post other options too? Thank you.

[Remi QUINTIN]

So obviously there is no RF stack programmed on the dongle.

So first perform a mass erase (it should generate an error that you won’t consider) or erase all sectors up to the 0xF4 one.

Then program the RF stack. If it is successful,  check the SFSA option byte. It should be set to 0xCB if the RF stack is correctly installed

If it is, just finalize your configuration, programming the application at the address 0x08000000.

It should work.

So perform a mass erase (this will generate an error that you should not consiere) or you erase all ectors up to the 0xF4 one and above.

[Parmin Nayani]

Hi Remi QUINTIN,

Thank you for the reply. Will mass erase delete FUS firmware also? Do I need to program it again?

Best regards

[Remi QUINTIN]

​No  The FUS is located in the secure area. This area is defined as all sectors above the SFSA pointer.

This area is protected against any read/write/erase access.

This is why this SFSA pointer is updated with a much lower value (for example 0xCB) when the RF stack (BLE stack for example) is correctly installed.