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
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