Registered User mNo edit summary |
Registered User mNo edit summary |
||
Line 3: | Line 3: | ||
|MPUs checklist=STM32MP13x,STM32MP15x | |MPUs checklist=STM32MP13x,STM32MP15x | ||
}}</noinclude> | }}</noinclude> | ||
{{ReviewsComments|-- [[User:Jean Christophe Trotin|Jean Christophe Trotin]] ([[User talk:Jean Christophe Trotin|talk]]) 10:07, 12 April 2023 (CEST)<br />This version takes into account the "new" [[Contributors:Internal_peripheral_article_model|internal peripheral model]]: | |||
* Take the opportunity of this review by the experts to verify that the content is still pertinent | |||
* Cross-check particularly the assignment tables | |||
The main writer of the article takes the ownership of the review by the experts.<br /> | |||
Remove this comment at the latest before the article is published.}} | |||
== | ==Article purpose== | ||
The DTS | 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 | ==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. | |||
DTS is | |||
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. | |||
== | ==Peripheral usage== | ||
This chapter is applicable in the scope of the '''OpenSTLinux BSP''' running on the Arm<sup>®</sup> Cortex<sup>®</sup>-A processor(s), and the '''STM32CubeMPU Package''' running on the Arm<sup>®</sup> Cortex<sup>®</sup>-M processor. | |||
=== | ===Boot time assignment=== | ||
The | The DTS peripheral is not used at boot time. | ||
=== | ===Runtime assignment=== | ||
====On {{MicroprocessorDevice | device=13}}==== | |||
{{: | {{#lst:STM32MP1_internal_peripherals_assignment_table_template|stm32mp13_runtime}} | ||
<section begin= | <section begin=stm32mp13_runtime /> | ||
| rowspan="1" | Power & Thermal | | rowspan="1" | Power & Thermal | ||
| rowspan="1" | [[DTS internal peripheral|DTS]] | | rowspan="1" | [[DTS internal peripheral|DTS]] | ||
Line 55: | Line 39: | ||
| | | | ||
|- | |- | ||
<section end= | <section end=stm32mp13_runtime /> | ||
|} | |||
{{: | ====On {{MicroprocessorDevice | device=15}}==== | ||
<section begin= | {{#lst:STM32MP1_internal_peripherals_assignment_table_template|stm32mp15_runtime}} | ||
<section begin=stm32mp15_runtime /> | |||
| rowspan="1" | Power & Thermal | | rowspan="1" | Power & Thermal | ||
| rowspan="1" | [[DTS internal peripheral|DTS]] | | rowspan="1" | [[DTS internal peripheral|DTS]] | ||
Line 68: | Line 53: | ||
| | | | ||
|- | |- | ||
<section end= | <section end=stm32mp15_runtime /> | ||
|} | |||
== | ==Software frameworks and drivers== | ||
< | Below are listed the software frameworks and drivers managing the {{Green|XXX}} peripheral for the embedded software components listed in the above tables. | ||
* '''Linux<sup>®</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> | <noinclude> | ||
[[Category:Power and Thermal peripherals]] | [[Category:Power and Thermal peripherals]] | ||
{{ArticleBasedOnModel| Internal peripheral article model}} | |||
{{PublicationRequestId | 8855 | 2018-09-21 | BrunoB}} | {{PublicationRequestId | 8855 | 2018-09-21 | BrunoB}} | ||
</noinclude> | </noinclude> |
Revision as of 09:07, 12 April 2023
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 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]
The DTS peripheral is not used at boot time.
3.2. Runtime assignment[edit | edit source]
3.2.1. On STM32MP13x lines [edit | edit source]
Click on the right to expand the legend...
Domain | Peripheral | Runtime allocation | Comment | ||
---|---|---|---|---|---|
Instance | Cortex-A7 secure (OP-TEE) |
Cortex-A7 non-secure (Linux) | |||
Power & Thermal | DTS | DTS | ☐ |
3.2.2. On STM32MP15x lines [edit | edit source]
Click on the right to expand the legend...
Domain | Peripheral | Runtime allocation | Comment | |||
---|---|---|---|---|---|---|
Instance | Cortex-A7 secure (OP-TEE) |
Cortex-A7 non-secure (Linux) |
Cortex-M4 (STM32Cube) | |||
Power & Thermal | DTS | DTS | ☐ |
4. Software frameworks and drivers[edit | edit source]
Below are listed the software frameworks and drivers managing the XXX 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.