Debug Reopening And Stirot; Stm32H5 Debug Reopening Support; Cli Commands For Reopen Debug Command; Table 5. Stm32H5 Debug Reopening Support - ST STM32H5 Series Getting Started

In this product state, the user cannot establish a debug connection neither in secure nor in nonsecure whatever
the HDP level.
By using the debug reopening service, the user requests STM32H5 to reopen the debug in nonsecure with HDP
level 3. Nonsecure with HDP level 3 is the debug reopening context request.
With such a request, the user can connect via debug to STM32H5 when it is only running in a nonsecure domain
with HDP level equal to 3. Before being able to establish such a debug connection, STM32H5 must complete the
following boot path to reach the debug reopening context request:
• STM32H5 starts in the secure domain with HDP level set to 1 (secure boot, for example, iROT, usual
context). STM32H5 does not reach the debug reopening context request, users cannot connect to
STM32H5 via debug.
• iROT jumps to uROT and increments the HDP level to 2. STM32H5 does not reach the debug reopening
context request, the user cannot connect to STM32H5 via debug.
• uROT jumps to the secure application and increments the HDP level to 3. STM32H5 does not reach the
debug reopening context request, the user cannot connect to STM32H5 via debug.
• Secure application jumps to nonsecure application. STM32H5 reaches the debug reopening context
request, the user can connect to STM32H5 via debug.
Note: When the debug reopening context request targets an HDP level n, the user can establish a debug connection
in an HDP level x with x higher or equal to n and x lower or equal to 3.
For example, with a debug reopening context request set to secure HDP level 1, thanks to debug authentication
reopening service, the user can establish a debug connection in secure HDP level 1, 2, and 3.
The user cancels the debug reopening effect by applying a power cycle on the STM32H5 (power off and power
on). After such an action, the STM32H5 debug state comes back to the one driven by the STM32H5 product
state. That also means that the debug opening is persistent to reset.
The debug reopening service can be launched from every product state except locked.
3.4.2

Debug reopening and STiROT

When the user sets the STM32H5 boot entry on STiROT within the STM32H5 system flash memory, the debug
reopening service does not grant reopening debug with the debug reopening context request set to the secure
HDP level 1.
3.4.3

STM32H5 debug reopening support

STM32H573xx
STM32H563xx/STM32H562xx
STM32H503xx
3.4.4

CLI commands for reopen debug command

In order to reopen debug from HDPL1 secure, use the following command:
In order to re-open debug from HDPL1 Secure, use the following command :
In order to reopen debug from HDPL2 secure, use the following command:
.\STM32_Programmer_CLI.exe -c port=SWD speed=fast per=f key=.\key.pem cert=.\certificate_chai
n debugauth=1
In order to reopen debug from HDPL3 secure, use the following command:
.\STM32_Programmer_CLI.exe -c port=SWD speed=fast per=g key=.\key.pem cert=.\certificate_chai
n debugauth=1
In order to reopen debug from HDPL1 nonsecure, use the following command:
.\STM32_Programmer_CLI.exe -c port=SWD speed=fast per=h key=.\key.pem cert=.\certificate_chai
n debugauth=1
AN6008 - Rev 1
Table 5. STM32H5 debug reopening support
Part number
STM32H5 debug authentication services description
Debug reopening supported
Yes
Yes
No
AN6008
page 8/25