DTS internal peripheral: Difference between revisions

Latest revision as of 10:27, 26 June 2025↑

Applicable for

STM32MP13x lines, STM32MP15x lines, STM32MP21x lines, STM32MP23x lines, STM32MP25x lines

1. Article purpose[edit | edit source]↑

The purpose of this article is to:

briefly introduce the DTS peripheral and its main features,
indicate the peripheral instances assignment at boot time and their assignment at runtime (including whether instances can be allocated to secure contexts),
list the software frameworks and drivers managing the peripheral,
explain how to configure the peripheral.

2. Peripheral overview[edit | edit source]↑

The Digital temperature sensor (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.

Refer to the STM32 MPU reference manuals for the complete list of features, and to the software frameworks and drivers, introduced below, to see which features are implemented.

3. Peripheral usage[edit | edit source]↑

This chapter is applicable in the scope of the OpenSTLinux BSP running on the Arm^® Cortex^®-A processor(s), and the STM32CubeMPU Package running on the Arm^® Cortex^®-M processor.

3.1. Boot time assignment[edit | edit source]↑

3.1.1. On STM32MP1 Series[edit | edit source]↑

The DTS peripheral is not used at boot time.

3.1.2. On STM32MP2 unknown microprocessor device[edit | edit source]↑

3.1.2.1. For A35-TD flavor [edit | edit source]↑

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
Domain	Peripheral	Instance	Cortex-A35 secure (ROM code)	Cortex-A35 secure (TF-A BL2)	Cortex-A35 nonsecure (U-Boot)	Comment
Power & Thermal	DTS	DTS		⬚	⬚

3.1.2.2. For M33-TD flavor [edit | edit source]↑

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
Domain	Peripheral	Instance	Cortex-A35 secure (ROM code)	Cortex-A35 secure (TF-A BL2)	Cortex-A35 nonsecure (U-Boot)	Cortex-M33 secure (MCUboot)	Comment
Power & Thermal	DTS	DTS		⬚	⬚	⬚

3.2. Runtime assignment[edit | edit source]↑

3.2.1. On STM32MP13x lines [edit | edit source]↑

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
Domain	Peripheral	Instance	Cortex-A7 secure (OP-TEE)	Cortex-A7 nonsecure (Linux)	Comment
Power & Thermal	DTS	DTS		☐

3.2.2. On STM32MP15x lines [edit | edit source]↑

Click on to expand or collapse the legend...

STM32MP15 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 possiblities might be described in STM32MP15 reference manuals.

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

3.2.3. On STM32MP21 unknown microprocessor device and STM32MP23 unknown microprocessor device[edit | edit source]↑

The tables below are applicable to any TD flavor (A35-TD or M33-TD) .

Click on to expand or collapse the legend...

STM32MP21 internal peripherals

STM32MP23 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 STM32MP21 reference manuals and in STM32MP23 reference manuals.

Domain	Peripheral	Runtime allocation					Comment
Domain	Peripheral	Instance	Cortex-A35 secure (OP-TEE / TF-A BL31)	Cortex-A35 nonsecure (Linux)	Cortex-M33 secure (TF-M)	Cortex-M33 nonsecure (STM32Cube)	Comment
Power & Thermal	DTS	DTS	⬚^{TF-A BL31} ⬚^OP-TEE	☐	⬚	⬚

3.2.4. On STM32MP25 unknown microprocessor device[edit | edit source]↑

The tables below are applicable to any TD flavor (A35-TD or M33-TD) .

Click on to expand or collapse the legend...

STM32MP25 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 STM32MP25 reference manuals.

Domain	Peripheral	Runtime allocation						Comment
Domain	Peripheral	Instance	Cortex-A35 secure (OP-TEE / TF-A BL31)	Cortex-A35 nonsecure (Linux)	Cortex-M33 secure (TF-M)	Cortex-M33 nonsecure (STM32Cube)	Cortex-M0+ (STM32Cube)	Comment
Power & Thermal	DTS	DTS	⬚^{TF-A BL31} ⬚^OP-TEE	☐	⬚	⬚

4. Software frameworks and drivers[edit | edit source]↑

Below are listed the software frameworks and drivers managing the DTS peripheral for the embedded software components listed in the above tables.

Linux^®: thermal framework

5. How to assign and configure the peripheral[edit | edit source]↑

The peripheral assignment can be done via the STM32CubeMX graphical tool (and manually completed if needed).
This tool also helps to configure the peripheral:

partial device trees (pin control and clock tree) generation for the OpenSTLinux software components,
HAL initialization code generation for the STM32CubeMPU Package.

The configuration is applied by the firmware running in the context in which the peripheral is assigned.

@@ Line 1: / Line 1: @@
+{{ApplicableFor
+|MPUs list=STM32MP13x, STM32MP15x, STM32MP21x, STM32MP23x, STM32MP25x
+|MPUs checklist=STM32MP13x, STM32MP15x, STM32MP21x, STM32MP23x, STM32MP25x
+}}
+==Article purpose==
+The purpose of this article is to:
+* briefly introduce the DTS peripheral and its main features,
+* indicate the peripheral instances assignment at boot time and their assignment at runtime (including whether instances can be allocated to secure contexts),
+* list the software frameworks and drivers managing the peripheral,
+* explain how to configure the peripheral.
 ==Peripheral overview==
-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.<br />
+The '''Digital temperature sensor (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.
-===Features===
+Refer to the [[STM32 MPU resources#Reference manuals|STM32 MPU reference manuals]] for the complete list of features, and to the software frameworks and drivers, introduced below, to see which features are implemented.
-Refer to the [[STM32MP13 resources#Reference manuals|STM32MP13 reference manuals]] or [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]] for the complete list of features , and to the software components, introduced below, to see which features are implemented.<br>
-===Security support===
+==Peripheral usage==
-The DTS is  a '''non secure''' peripheral.
+This chapter is applicable in the scope of the '''OpenSTLinux BSP''' running on the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A processor(s), and the '''STM32CubeMPU Package''' running on the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-M processor.
-==Peripheral usage and associated software==
+===Boot time assignment===
-===Boot time===
+====On {{MicroprocessorDevice | device=1}}====
-DTS is not used at boot time.
+The DTS peripheral is not used at boot time.
-===Runtime===
+====On {{MicroprocessorDevice | device=2}}====
-====Overview====
+=====For {{TrustedDomainFlavor|flavor=A35-TD}}=====
-The monitoring is done from the Cortex-A7 non-secure context with Linux<sup>&reg;</sup> [[Thermal overview|thermal management framework]].
+{{#lst:STM32MP2_internal_peripherals_assignment_table_template|stm32mp2_a35_boottime}}
+<section begin=stm32mp21_a35_boottime/><section begin=stm32mp23_a35_boottime/><section begin=stm32mp25_a35_boottime/>
+| rowspan="1" | Power & Thermal
+| rowspan="1" | [[DTS internal peripheral | DTS]]
+| DTS
+|
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span>
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span>
+|
+|-
+<section end=stm32mp21_a35_boottime/><section end=stm32mp23_a35_boottime/><section end=stm32mp25_a35_boottime/>
+|}
+=====For {{TrustedDomainFlavor|flavor=M33-TD}}=====
+{{#lst:STM32MP2_internal_peripherals_assignment_table_template|stm32mp2_m33_boottime}}
+<section begin=stm32mp21_m33_boottime/><section begin=stm32mp23_m33_boottime/><section begin=stm32mp25_m33_boottime/>
+| rowspan="1" | Power & Thermal
+| rowspan="1" | [[DTS internal peripheral | DTS]]
+| DTS
+|
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span>
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span>
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span>
+|
+|-
+<section end=stm32mp21_m33_boottime/><section end=stm32mp23_m33_boottime/><section end=stm32mp25_m33_boottime/>
+|}
-====Software frameworks====
+===Runtime assignment===
-===== On {{MicroprocessorDevice | device=13}} =====
+====On {{MicroprocessorDevice | device=13}}====
-{{:STM32MP13 internal peripherals software table template}}
+{{#lst:STM32MP1_internal_peripherals_assignment_table_template|stm32mp13_runtime}}
- | Power & Thermal
+<section begin=stm32mp13_runtime />
- | [[DTS internal peripheral|DTS]]
- |
- | [[Thermal overview|Linux thermal framework]]
- |
- |-
- |}
-===== On {{MicroprocessorDevice | device=15}} =====
-{{:Internal_peripherals_software_table_template}}
- | Power & Thermal
- | [[DTS internal peripheral|DTS]]
- |
- | [[Thermal overview|Linux thermal framework]]
- |
- |
- |-
- |}
-====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.
-====Peripheral assignment====
-===== On {{MicroprocessorDevice | device=13}} =====
-{{:STM32MP13_internal_peripherals_assignment_table_template}}
-<section begin=stm32mp13 />
   | rowspan="1" | Power & Thermal
   | rowspan="1" | [[DTS internal peripheral|DTS]]
@@ Line 51: / Line 62: @@
   |
   |-
-<section end=stm32mp13 />
+<section end=stm32mp13_runtime />
- |}
+|}
-===== On {{MicroprocessorDevice | device=15}} =====
-{{:Internal_peripherals_assignment_table_template}}
+====On {{MicroprocessorDevice | device=15}}====
-<section begin=stm32mp15 />
+{{#lst:STM32MP1_internal_peripherals_assignment_table_template|stm32mp15_runtime}}
+<section begin=stm32mp15_runtime />
   | rowspan="1" | Power & Thermal
   | rowspan="1" | [[DTS internal peripheral|DTS]]
@@ Line 61: / Line 73: @@
   |
   | <span title="assignable peripheral" style="font-size:21px">☐</span>
-  |
+  | <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span>
   |
   |-
-<section end=stm32mp15 />
+<section end=stm32mp15_runtime />
- |}
+|}
+====On {{MicroprocessorDevice | device=21}} and {{MicroprocessorDevice | device=23}}====
+The tables below are applicable to any {{TrustedDomainFlavor | flavor=Any-TD}}.
+{{#lst:STM32MP2_internal_peripherals_assignment_table_template|stm32mp21_23_runtime}}
+<section begin=stm32mp21_a35_runtime /><section begin=stm32mp21_m33_runtime />
+<section begin=stm32mp23_a35_runtime /><section begin=stm32mp23_m33_runtime />
+| rowspan="1" | Power & Thermal
+| rowspan="1" | [[DTS internal peripheral | DTS]]
+| DTS
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span><sup>TF-A BL31</sup><br /><span title="assignable peripheral but not supported" style="font-size:21px">⬚</span><sup>OP-TEE</sup>
+| <span title="assignable peripheral" style="font-size:21px">☐</span>
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span>
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span>
+|
+|-
+<section end=stm32mp23_a35_runtime /><section end=stm32mp23_m33_runtime />
+<section end=stm32mp21_a35_runtime /><section end=stm32mp21_m33_runtime />
+|}
+====On {{MicroprocessorDevice | device=25}}====
+The tables below are applicable to any {{TrustedDomainFlavor | flavor=Any-TD}}.
+{{#lst:STM32MP2_internal_peripherals_assignment_table_template|stm32mp25_runtime}}
+<section begin=stm32mp25_a35_runtime /><section begin=stm32mp25_m33_runtime />
+| rowspan="1" | Power & Thermal
+| rowspan="1" | [[DTS internal peripheral | DTS]]
+| DTS
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span><sup>TF-A BL31</sup><br /><span title="assignable peripheral but not supported" style="font-size:21px">⬚</span><sup>OP-TEE</sup>
+| <span title="assignable peripheral" style="font-size:21px">☐</span>
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span>
+| <span title="assignable peripheral but not supported" style="font-size:21px">⬚</span>
+|
+|
+|-
+<section end=stm32mp25_a35_runtime /><section end=stm32mp25_m33_runtime />
+|}
-==References==
+==Software frameworks and drivers==
-<references/>
+Below are listed the software frameworks and drivers managing the {{Green|DTS}} peripheral for the embedded software components listed in the above tables.
+* '''Linux<sup>&reg;</sup>''': [[Thermal overview|thermal framework]]
+==How to assign and configure the peripheral==
+The peripheral assignment can be done via the [[STM32CubeMX]] graphical tool (and manually completed if needed).<br />
+This tool also helps to configure the peripheral:
+* partial device trees (pin control and clock tree) generation for the OpenSTLinux software components,
+* HAL initialization code generation for the STM32CubeMPU Package.
+The configuration is applied by the firmware running in the context in which the peripheral is assigned.
 <noinclude>
 [[Category:Power and Thermal peripherals]]
+{{ArticleBasedOnModel| Internal peripheral article model}}
 {{PublicationRequestId | 8855 | 2018-09-21 | BrunoB}}
-{{ArticleBasedOnModel| Internal peripheral article model}}
 </noinclude>