DTS internal peripheral

This message will disappear after all relevant tasks have been resolved.

Semantic MediaWiki

There are 1 incomplete or pending task to finish installation of Semantic MediaWiki. An administrator or user with sufficient rights can complete it. This should be done before adding new data to avoid inconsistencies.

1. Peripheral overview[edit source]

The DTS peripheral is used to monitor the device temperature and take some preventive action (like frequency scaling or peripheral disabling) in case it is becoming too high and before destroying the component.

1.1. Features[edit source]

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.

1.2. Security support[edit source]

The DTS is a non secure peripheral.

2. Peripheral usage and associated software[edit source]

2.1. Boot time[edit source]

DTS is not used at boot time.

2.2. Runtime[edit source]

2.2.1. Overview[edit source]

The device cannot warm up if the Cortex^®-M4 is running alone, as a consequence the monitoring is only done from the Cortex-A7 non-secure context with Linux^® thermal management framework.

2.2.2. Software frameworks[edit source]

Domain	Peripheral	Software components			Comment
Domain	Peripheral	OP-TEE	Linux	STM32Cube	Comment
Power & Thermal	DTS		Linux thermal framework

2.2.3. Peripheral configuration[edit source]

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.

2.2.4. Peripheral assignment[edit source]

Internal peripherals

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.
✓ 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.

Domain	Peripheral	Runtime allocation				Comment
Domain	Peripheral	Instance	Cortex-A7 secure (OP-TEE)	Cortex-A7 non-secure (Linux)	Cortex-M4 (STM32Cube)	Comment
Power & Thermal	DTS	DTS		☐