Getting started with debug authentication (DA) for STM32H5 MCUs
Introduction
This document describes the debug authentication (DA) security service of the
The STM32 debug authentication controls the product life cycle, such as regressions (for more details about the life cycle, refer
to the reference manual), and debug reopening:
•
Regression
The user leverages the regression service to erase the user firmware and data within the user flash memory, SRAM, and
option-byte keys (OBK) when OBK are supported by STM32H5. After a regression, STM32 falls back in product state
open. There are two kinds of regression: full regression and partial regression. Refer to
authentication services description
•
Debug reopening
The user leverages the debug reopening to safely reopen the debug on STM32 when it is in a product state different than
open.
When the STM32 product state is not open, the user can trigger the debug authentication services by sending a password or a
certificate chain to STM32.
These two options are named the debug authentication methods.
The debug authentication protocol uses the STM32 debug access port 0 (DAP0) and the DBGMCU IP for communication.
The STM32 debug authentication implements the Arm
®
The Arm
PSA ADAC protocol is based on the certificate chain and the challenge/response principle.
AN6008 - Rev 1 - December 2023
For further information contact your local STMicroelectronics sales office.
for more details.
Figure 1.
Debug authentication interface
Debug port
Probe
/ DBGMCU
®
PSA ADAC (authenticated debug access control) specification.
STM32H5
series.
Section 3: STM32H5 debug
STM32H5
Debug
Authentication
AN6008
Application note
www.st.com
Need help?
Do you have a question about the STM32H5 Series and is the answer not in the manual?
Questions and answers