- Last edited 6 months ago ago
STM32MP15 ETZPC internal peripheral
1 Article purpose
The purpose of this article is to:
- briefly introduce the ETZPC peripheral and its main features
- indicate the level of security supported by this hardware block
- explain how it can be allocated to the runtime contexts and linked to the corresponding software components
- explain, when necessary, how to configure the ETZPC peripheral.
2 Peripheral overview
The ETZPC peripheral is used to configure TrustZone security in a SoC having bus masters and slaves with programmable-security attributes (securable resources) such as:
- on-chip RAM/ROM with programmable secure region size
- AHB and APB peripherals to be made secure
- AHB masters to be granted secure rights
The ETZPC peripheral also allows peripheral isolation. With MCU isolation, some peripherals can be assigned to Cortex-M4 context execution only. Those peripherals will not be accessible for Cortex-A7 contexts (secure and non-secure).
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 ETZPC is a secure peripheral.
3 Peripheral usage and associated software
3.1 Boot time
The ETZPC is configured at boot time to setup the platform security.
The ETZPC is a system peripheral and is controlled by the Arm® Cortex®-A7 secure.
3.2.2 Software frameworks
|Security||ETZPC||TF-A(BL32) or OP-TEE ETZPC driver Read/Write access||U-Boot
Read only access
|Resource Manager Utility Read only access||Configuration made by A7 secure.|
U-Boot updates the Linux device tree.
3.2.3 Peripheral configuration
The configuration is applied by the firmware running in a secure context.
3.2.4 Peripheral assignment
Click on the right to expand the legend...
Check boxes illustrate the possible peripheral allocations supported by STM32 MPU Embedded Software:
- ☐ means that the peripheral can be assigned (☑) to the given runtime context.
- ⬚ means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
- ✓ is used for system peripherals that cannot be unchecked because they are statically connected in the device.
Refer to How to assign an internal peripheral to a runtime context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possiblities might be described in STM32MP15 reference manuals.
4 How to go further
The ETZPC is an STMicroelectronics extension of the Arm® peripheral: TrustZone Protection Controller