Skip to main content
fo_it
Associate II
August 14, 2025
Question

FUS_STATE_IMG_NOT_AUTHENTIC during upgrading the FUS

  • August 14, 2025
  • 4 replies
  • 456 views

Hello,

We try to upgrade the BLE stack to the latest 1.23.0. This version requires FUS v.2. We are unable to do this due to the FUS_STATE_IMG_NOT_AUTHENTIC error. We're using STM32CubeProgrammer v. 2.12.0. We have also tried with STM32CubeProgrammer v. 2.20.0following the steps in the release note of the binary files with the same result. 

Currently:

- FUS version: 1.2.0.0

- BLE stack version: 1.8.0.3.

 

We tried on both out custom board and on NUCLEO-WB44 with the same result. Could someone guide us to a solution?

Thanks in advance.

 

4 replies

STTwo-32
Technical Moderator
August 14, 2025

Hello @fo_it 

Could you please try to do that using the STM32CubeProgrammer V2.20.0.

Best Regards.

STTwo-32

fo_it
fo_itAuthor
Associate II
August 14, 2025

Hello @STTwo-32 

I've tried  following on NUCLEO-WB55 using STM32CubeProgrammer v. 2.20.0:

- Upgrade to FUS v1.2.0 for verifying the process: Success

- Upgrade to FUS v2.0.0: Success

- Upgrade to FUS v2.1.0: Success

On our custom board none of the above was succeeded. We only get FUS_STATE_IMG_NOT_AUTHENTIC error.

STTwo-32
Technical Moderator
August 14, 2025

Could you please send the values of your option bytes, the current version of your FUS/STACK (on a screenshot from the STM32CubeProgrammer if possible) , the exact reference of your MCU and the files that you are using exactly. 

Best Regards.

STTwo-32

fo_it
fo_itAuthor
Associate II
August 15, 2025

The option bytes are:

STM32WB55RGV6 - Option Bytes.png

and the FUS information is:

STM32WB55RGV6 - FUS Information.png

We use both the FUS firmware and the stack firmware from stock firmware downloaded by the STM32CubeIDE. The MCU is STM32WB55RGV6.

fo_0-1755238981767.png

 

STTwo-32
Technical Moderator
August 15, 2025

Hello @fo_it 

Are you sure you are trying to flash the FUS to the correct address. If so, could you please perform a Mass erase before uploading any FUS file.

Best Regards.

STTwo-32

fo_it
fo_itAuthor
Associate II
August 15, 2025

I do it  in exactly same way as I do with NUCLEO-WB55. I load the FUS v2.0.0.3 in the STM32CubeProgrammer v. 2.20.0 with the "Start address automatic determination" active. With the stack v1.22.0.2 already installed, the programming of FUS returns FUS_STATE_IMG_NO_SPACE. When the stack is deleted, then programming of FUS returns FUS_STATE_IMG_NOT_AUTHENTIC.

I've also tried with the start address 0x080EE000 manually with the same result.

STTwo-32
Technical Moderator
September 15, 2025

Hello @fo_it 

Could you please try to:

  • Set the RDP from level 0 to level 1 and set it back to level 0. After that update your FUS and Stack.
  • Upload a simple code to the board (GPIO_Toggle comme exemple) and try to update the FUS and stack after that.

Best Regards.

STTwo-32