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: 

Is it possible to provision a board with Secure Manager using JLINK?

Thatseasy
Associate III

‎2025-04-18 12:07 PM

When I tried it, got the following error:
2025-04-18 14:58:31,172 - DEBUG - Executing command: "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=JLINK debugauth=2
2025-04-18 14:58:31,674 - DEBUG - -------------------------------------------------------------------
2025-04-18 14:58:31,674 - DEBUG - STM32CubeProgrammer v2.19.0
2025-04-18 14:58:31,674 - DEBUG - -------------------------------------------------------------------
2025-04-18 14:58:31,675 - DEBUG -
2025-04-18 14:58:31,678 - DEBUG - Connecting to J-Link/Flasher Probe
2025-04-18 14:58:32,043 - DEBUG - Device=Cortex-M33
2025-04-18 14:58:32,133 - DEBUG - Device ID : 0x484
2025-04-18 14:58:32,134 - DEBUG - Voltage : 3.32V
2025-04-18 14:58:32,135 - DEBUG - Frequency : 4000 KHz
2025-04-18 14:58:32,218 - DEBUG - Flash size : 2 MBytes
2025-04-18 14:58:32,221 - DEBUG - Error: Debug Authentication is not yet supported by J-Link
2025-04-18 14:58:32,250 - ERROR - Command '"C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=JLINK debugauth=2' returned non-zero exit status 1

0 Kudos
2 REPLIES 2
CMYL
ST Employee

‎2025-04-23 3:33 PM

Hi @Thatseasy 

When the Secure Manager (SM) is part of the provisioning:

- As the Secure Manager is provided as a binary image, and as it is a sensible code, the only way to provision the Secure Manager is to use the Secure Firmware Install (SFI), based on a global license.

- This wiki provides the steps for suing SFI STM32H5 with or w/o secure manager provisioning: Security:SFI for STM32H5 - stm32mcu

- In my opinion Jlink is not the issue as you are able to connect the board. For confirmation I will clarify it internally with experts. 

Best regards

 

0 Kudos
Christian Keydel
Associate III
In response to CMYL

‎2025-09-26 2:09 AM

Hi @CMYL 

Any news on this? I am trying the same thing - provisioning the Secure Manager with SEGGER J-Link and I am still getting the same error even with the latest version 2.20:

2025-09-26 10:36:30,829 - INFO -        * Secure Installation:
2025-09-26 10:36:30,829 - DEBUG - Executing command: "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=JLINK debugauth=2
2025-09-26 10:36:30,865 - DEBUG - -------------------------------------------------------------------
2025-09-26 10:36:30,865 - DEBUG - STM32CubeProgrammer v2.20.0
2025-09-26 10:36:30,866 - DEBUG - -------------------------------------------------------------------
2025-09-26 10:36:30,866 - DEBUG -
2025-09-26 10:36:30,869 - DEBUG - Connecting to J-Link/Flasher Probe
2025-09-26 10:36:31,145 - DEBUG - Device=Cortex-M33
2025-09-26 10:36:31,283 - DEBUG - Device ID   : 0x484
2025-09-26 10:36:31,287 - DEBUG - Voltage     : 3.23V
2025-09-26 10:36:31,287 - DEBUG - Frequency   : 4000 KHz
2025-09-26 10:36:31,619 - DEBUG - Flash size  : 2 MBytes
2025-09-26 10:36:31,619 - DEBUG - Error: Debug Authentication is not yet supported by J-Link
2025-09-26 10:36:32,592 - ERROR - Command '"C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=JLINK debugauth=2' returned non-zero exit status 3221225477

AFAICS the important message is

Error: Debug Authentication is not yet supported by J-Link

Is there an ETA for this feature?

 

0 Kudos
Top