STM32MP13 peripherals overview

Applicable for

STM32MP13x lines

---

This article lists all internal peripherals embedded in STM32MP13x lines  and shows the assignment possibilities to the execution contexts for each one of them.
From this article, you can also access to individual peripheral articles with information related to the overview and configuration aspects.

Important

This article has be written in scope of STM32 MPU OpenSTLinux Embedded software. For the STM32CubeMP13 Package (running on the Arm® Cortex®-A7 processor), the peripheral assignment table is also applicable. All supported peripherals are, by default, assigned to the secure context, and it is possible to assign them to the non-secure context thanks to STM32CubeMX. or The default peripheral assignments for STM32CubeMP13 are described in Arm® Cortex®-A secure column of this table. As usual, the customer can change this configuration to switch in Arm® Cortex®-A non-secure context using STM32CubeMX

1. Internal peripherals overview

The figure below shows all peripherals embedded in STM32MP13x lines , grouped per functional domains that are reused in many places of this wiki to structure the articles.

Several execution contexts exist on STM32MP13x lines , corresponding to the Arm Cortex-A7 security modes:

•  Arm Cortex-A7 secure  (Trustzone), running ROM code and TF-A BL2 at boot time, and running OP-TEE at runtime
•  Arm Cortex-A7 non secure , running U-Boot at boot time, and running Linux at runtime

Some peripherals can be strictly assigned to one execution context, this is the case for most of the peripherals, like USART or I2C.
Other ones can be shared between several execution contexts, this is the case for system peripherals like PWR or RCC.

The legend below shows how assigned and shared peripherals are identified in the assignment diagram that follows.

Both the diagram below and the following summary table (in Internal peripherals runtime assignment and Internal peripherals boot time assignment chapters below) are clickable in order to jump to each peripheral overview article and get more detailed information (like the software frameworks used to control them). They list STMicroelectronics recommendations. The STM32MP13 reference manual may expose more possibilities then what is shown here.

STM32MP13 internal peripherals overview

2. Internal peripherals runtime assignment

Click on to expand or collapse the legend...

STM32MP13 internal peripherals

Check boxes illustrate the possible peripheral allocations supported by the OpenSTLinux BSP:

• ⬚ means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in OpenSTLinux BSP.
• ☐ means that the peripheral can be assigned to the given runtime context.
• ☑ means that the peripheral is assigned by default to the given runtime context and that the peripheral is mandatory for the OpenSTLinux BSP.
• ✓ is used for system peripherals that cannot be unchecked because they are hardware connected in the device.

Refer to How to assign an internal peripheral to an execution context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possibilities might be described in STM32MP13 reference manuals.

Domain	Peripheral	Runtime allocation			Comment
		Instance	Cortex-A7 secure (OP-TEE)	Cortex-A7 nonsecure (Linux)
Core	RTC	RTC	☑	☐	RTC is mandatory to resynchronize STGEN after exiting low-power modes.
Core	SYSCFG	SYSCFG	☑	☑
Power & Thermal	RCC	RCC	✓	✓
Security	ETZPC	ETZPC	✓	✓
Security	HASH	HASH	☐	☐	Assignment (single choice)
Security	RNG	RNG	☐	☐	Assignment (single choice)
Security	TAMP	TAMP	☑	☑

3. Internal peripherals boot time assignment

Click on to expand or collapse the legend...

Check boxes illustrate the possible peripheral allocations supported by the OpenSTLinux BSP:

• ⬚ means that the peripheral can be assigned to the given boot time context, but this configuration is not supported in OpenSTLinux BSP.
• ☐ means that the peripheral can be assigned to the given boot time context.
• ☑ means that the peripheral is assigned by default to the given boot time context and that the peripheral is mandatory for the OpenSTLinux BSP.
• ✓ is used for system peripherals that cannot be unchecked because they are hardware connected in the device.

The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possibilities might be described in STM32 MPU reference manuals.

Domain	Peripheral	Boot time allocation				Comment
		Instance	Cortex-A7 secure (ROM code)	Cortex-A7 secure (TF-A BL2)	Cortex-A7 nonsecure (U-Boot)
Core	RTC	RTC			☐
Core	SYSCFG	SYSCFG	✓	☑	☑
Power & Thermal	RCC	RCC	✓	✓	✓
Security	ETZPC	Any instance	✓	✓	✓	ETZPC configuration is set by OP-TEE
Security	HASH	HASH	✓	☑
Security	RNG	RNG	✓	☑	☐	Required for DPA peripheral protection
Security	TAMP	TAMP	✓	☑	☑

Microprocessor unit

Arm^® is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.

Cortex^®

Board support package

Open portable trusted execution environment

Linux^® is a registered trademark of Linus Torvalds.

Real time clock

System configuration

Reset and clock control

Extended trustzone protection controller

Random number generator

Tamper

Read only memory

Trusted firmware for Arm^® Cortex^®-A

Boot loader stage 2

Das U-Boot -- the universal boot loader (see U-Boot)

Differential power analysis