- Last edited 2 weeks ago ago
DBGMCU internal peripheral
1 Article purpose
The purpose of this article is to:
- briefly introduce the DBGMCU peripheral and its main features
- indicate the level of security supported by this hardware block
- explain how each instance can be allocated to the three runtime contexts and linked to the corresponding software components
- explain, when necessary, how to configure the DBGMCU peripheral.
2 Peripheral overview
The DBGMCU peripheral is used to configure internal peripherals behavior when one of the cores (Cortex®-A7 or Cortex®-M4) enters in debug mode.
For instance, it allows to freeze a watchdog (IWDG) to avoid getting a watchdog reset when the Cortex®-A7 enters in debug mode (via a breakpoint or JTAG break).
Refer to the STM32MP15 reference manuals for the complete list of features, and to the software components, introduced below, to see which features are implemented.
2.2 Security support
The DBGMCU is a non secure peripheral.
3 Peripheral usage and associated software
3.1 Boot time
There is no real runtime support for DBGMCU. Instead, users who need to freeze some peripherals for a debug session should complete the minimal initialization done in the FSBL with their needs.
3.2.2 Software frameworks
| Trace & Debug | DBGMCU | | | | |- |}
3.2.3 Peripheral configuration
The configuration is applied by the firmware running in the context to which the peripheral is assigned. The configuration can be done alone via the STM32CubeMX tool for all internal peripherals, and then manually completed (particularly for external peripherals), according to the information given in the corresponding software framework article.
3.2.4 Peripheral assignment
| rowspan="1" | Trace & Debug | rowspan="1" | DBGMCU | DBGMCU | | | | No assignment |-