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: 

Error 0xF6F6F6F6 when executing SFI command with STM32_Programmer_CLI from GitLab Runner

mikel-m
Associate III

‎2025-07-11 3:13 AM - edited ‎2025-07-11 3:15 AM

Hi,

I'm encountering an issue while trying to install an SFI using STM32_Programmer_CLI within a GitLab pipeline.

Context:

  • I'm using a GitLab runner with executor = shell (cmd), so the commands are executed directly on the PC where the microcontroller is physically connected.
  • I'm executing the following command:
STM32_Programmer_CLI.exe -c port=SWD mode=HOTPLUG -sfi %SFI% %HSM_LICENSE% -rsse enc_signed_RSSe_sfi_U5_2M.bin
  •  %SFI% and %HSM_LICENSE% refer to the corresponding .sfi file and HSM license. The AES key and nonce used to generate the RSSe are also the same in all cases.

Issue:

The command fails with the following error:

Error: Execution of RSS CMD failed, returned value = 0xF6F6F6F6

 Additional Info:

  • I’m running the same command on another PC with a different GitLab runner, using the same HSM license and the same AES key and nonce, but with a different RSSe file (in this case, a basic LED test for the microcontroller) — and it works fine there.

  • Both target microcontrollers are the same STM32U5 series and are connected via SWD.

Does anyone know what the return code 0xF6F6F6F6 means? Could it be related to some environment setup issue, the state of the MCU, or a missing tool/configuration on the failing PC?

Thanks in advance!

This is the full code of the GitLab pipeline error message:

Starting SFI 
Processing license...
Error: Execution of RSS CMD failed, returned value = 0xF6F6F6F6 
Error: Failed to Process License!
Error: C:\Users\...\SBSFU_U575.sfi SFI file Install Operation Failure! Please, try again.
Press a key to continue . . .

 

0 Kudos
1 REPLY 1
STSec
ST Employee

‎2025-07-22 8:27 AM

Hello Mikel,

It seems that the license you are using is not correct for your target board.

Be aware that the license is specific to a device and not to a series. Each STM32U575 has its own certificate provisioned. Therefore, a license generated for a specific device can only be used on that specific device.

I suggest generating another license if you change your device, even if it is a device from the same series.

I hope this helps.

0 Kudos
Top