FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Unable to start FUS. FUS version is 0.0.0.0 and FUS_STATE_ERR_UNKNOWN

KKIM.6
Senior II

‎2024-03-12 2:25 PM - edited ‎2024-03-12 2:34 PM

I'm trying to fix a P-Nucleo-WB55 board using CubeProgrammer.

However, the board shows a 0.0.0.0 version of FUS and Stack and I cannot start FUS.

I don't know why there is no version because the FUS cannot be deleted forever in the FUS upgrade document.

So, How can I update FUS in this version?

The SBRV option byte is 0x3ffff is it common?

KKIM6_0-1710278560335.png

KKIM6_1-1710278589868.png

KKIM6_2-1710278620227.png

 

 

Labels:
0 Kudos
6 REPLIES 6
STTwo-32
ST Employee

‎2024-03-13 2:30 AM - last edited on ‎2024-03-14 3:16 AM by

Hello @KKIM.6 

According to the SBRV value, FUS is not running. I suggest you try to update your firmware Following this wiki and using the last version (included in the version 1.18.0 of the STM32CubeWB).

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

0 Kudos
KKIM.6
Senior II
In response to STTwo-32

‎2024-03-13 9:36 AM

Could you send the link again?

 

I'm trying to upgrade FUS following the "STM32WB Firmware Upgrade Service wiki" but there is no description when FUS does not exist.

 

0 Kudos
KKIM.6
Senior II
In response to STTwo-32

‎2024-03-19 6:36 PM

I couldn't solve this problem yet...

0 Kudos
Remi QUINTIN
ST Employee

‎2024-04-12 10:08 AM

The SBRV value is pointing on the safeboot which means something went badly wrong during the update.

I assume the SFSA value to be FFFF protecting the last sector.

Did you already program this board? 

I would be nice to get the ESE and SFSA values.

 

Then one thing that may work to recover your board in a manufactory state is to write the value 0x00008000 at the address 0x5800040C. This should work if ESE option byte is checked.

 

0 Kudos
Yash_Agrawal
Associate

‎2025-02-24 12:16 AM

Hello,

I encountered a similar issue where the FUS became unresponsive after sending an event signal. STM32CubeProgrammer now reports the FUS and wireless stack versions as v0.0.0.0.

I am unsure what caused this issue. Multiple recovery attempts, including updating the FUS firmware, did not work.

Were you able to fix the issue? How can I avoid this in the future? Any guidance would be appreciated.

Thanks!

0 Kudos
Lubos KOUDELKA
ST Employee

‎2025-02-25 4:37 AM

Step by step guidance for restoring option bytes corruption as defined in AN5185, page 10.

  • Connect MCU using Stlink USB and start STM32CubeProgrammer
  • If there is problem to connect using STM32CubeProgrammer, add jumper to BOOT0 pin

1.set RDP AA (will remove the PCROP as well)

  • Ensure PCROP and RDP is not active

2.set OB to boot in System Flash (nBoot0 = 0)

3.reboot

4.connect STM32CubeProgrammer with hotplug

5.start CPU2 using write 0x00008000 at 0x5800040C

Top