Difference between revisions of "STM internal peripheral"

[quality revision] [quality revision]
m
 
m
 


Template:ArticleMainWriter Template:ArticleApprovedVersion


1 Article purpose[edit]

The purpose of this article is to:

  • briefly introduce the STM peripheral and its main features
  • indicate the level of security supported by this hardware block
  • explain how each instance can be allocated to the three runtime contexts and linked to the corresponding software components
  • explain, when necessary, how to configure the STM peripheral.

2 Peripheral overview[edit]

The STM peripheral is used to log STM trace into the embedded trace FIFO (ETF). This trace can include hardware events (the list is given in the STM32MP15 reference manuals) or direct 'printf like' log from the Cortex®Template:Sup-A7. Once in the ETF buffer, the trace can directly be dumped from the Cortex®Template:Sup-A7 or to the trace port interface unit (TPIU), connected to an external probe able to decode it.

2.1 Features[edit]

Refer to the STM32MP15 reference manuals for the complete list of features, and to the software components, introduced below, to see which features are really implemented.

2.2 Security support[edit]

The STM is a non secure peripheral.

3 Peripheral usage and associated software[edit]

3.1 Boot time[edit]

The STM is not used at boot time.

3.2 Runtime[edit]

3.2.1 Overview[edit]

The STM can be assigned to the Cortex®Template:Sup-A7 non-secure for using in Linux with coresight framework.
This driver allows to select the hardware events (listed in the STM32MP15 reference manuals) to log via the STM peripheral into the ETF and dump it in the Linux console for analysis.

3.2.2 Software frameworks[edit]

Domain Peripheral Software frameworks Comment
Cortex-A7
secure
(OP-TEE)
Cortex-A7
non-secure
(Linux)
Cortex-M4

(STM32Cube)
Trace & Debug STM Linux Coresight framework

3.2.3 Peripheral configuration[edit]

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.

3.2.4 Peripheral assignment[edit]

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
Instance Cortex-A7
secure
(OP-TEE)
Cortex-A7
non-secure
(Linux)
Cortex-M4

(STM32Cube)
Trace & Debug STM STM

4 References[edit]

<noinclude>

{{ArticleBasedOnModel | [[Internal peripheral article model]]}}
{{ArticleMainWriter | GeraldB}}
{{ArticleApprovedVersion| GeraldB | AlexandreT | No previous approved version | BrunoB - 19Oct'18 - 9288 | 24'May18}} 
[[Category:Trace and debug peripherals]]</noinclude>

==Article purpose==
The purpose of this article is to:
* briefly introduce the STM peripheral and its main features
* indicate the level of security supported by this hardware block
* explain how each instance can be allocated to the three runtime contexts and linked to the corresponding software components
* explain, when necessary, how to configure the STM peripheral.

==Peripheral overview==
The '''STM''' peripheral is used to log STM trace into the embedded trace FIFO (ETF). This trace can include hardware events (the list is given in the [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]]) or direct 'printf like' log from the Cortex{{sup|&reg;</sup>}}-A7. Once in the ETF buffer, the trace can directly be dumped from the Cortex{{sup|&reg;</sup>}}-A7 or to the trace port interface unit (TPIU), connected to an external probe able to decode it.<br />


===Features===
Refer to the [[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 really implemented.<br>


===Security support===
The STM is a '''non secure''' peripheral.

==Peripheral usage and associated software==
===Boot time===
The STM is not used at boot time.

===Runtime===
====Overview====
The STM can be assigned to the Cortex{{sup|&reg;</sup>}}-A7 non-secure for using in Linux with [[Coresight overview|coresight framework]]. <br />

This driver allows to select the hardware events (listed in the [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]]) to log via the STM peripheral into the ETF and dump it in the Linux console for analysis.

====Software frameworks====
{{:Internal_peripherals_software_table_template}}
 | Trace & Debug
 | [[STM internal peripheral|STM]]
 | 
 | [[Coresight overview|Linux Coresight 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====
{{:Internal_peripherals_assignment_table_template}}<onlyinclude>

 | rowspan="1" | Trace & Debug
 | rowspan="1" | [[STM internal peripheral|STM]]
 | STM
 |
 | <span title="assignable peripheral" style="font-size:21px"></span>

 |
 |
 |-</onlyinclude>

 |}

==References==<references/>

<noinclude>

{{ArticleBasedOnModel | Internal peripheral article model}}
{{PublicationRequestId | 9288 | 2018-10-19 | BrunoB}}
[[Category:Trace and debug peripherals]]</noinclude>
Line 1: Line 1:
<noinclude>
 
{{ArticleBasedOnModel | [[Internal peripheral article model]]}}
 
{{ArticleMainWriter | GeraldB}}
 
{{ArticleApprovedVersion| GeraldB | AlexandreT | No previous approved version | BrunoB - 19Oct'18 - 9288 | 24'May18}}
 
[[Category:Trace and debug peripherals]]
 
</noinclude>
 
 
 
==Article purpose==
 
==Article purpose==
 
The purpose of this article is to:
 
The purpose of this article is to:
Line 14: Line 7:
   
 
==Peripheral overview==
 
==Peripheral overview==
The '''STM''' peripheral is used to log STM trace into the embedded trace FIFO (ETF). This trace can include hardware events (the list is given in the [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]]) or direct 'printf like' log from the Cortex{{sup|&reg;}}-A7. Once in the ETF buffer, the trace can directly be dumped from the Cortex{{sup|&reg;}}-A7 or to the trace port interface unit (TPIU), connected to an external probe able to decode it.<br />
+
The '''STM''' peripheral is used to log STM trace into the embedded trace FIFO (ETF). This trace can include hardware events (the list is given in the [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]]) or direct 'printf like' log from the Cortex<sup>&reg;</sup>-A7. Once in the ETF buffer, the trace can directly be dumped from the Cortex<sup>&reg;</sup>-A7 or to the trace port interface unit (TPIU), connected to an external probe able to decode it.<br />
   
 
===Features===
 
===Features===
Line 28: Line 21:
 
===Runtime===
 
===Runtime===
 
====Overview====
 
====Overview====
The STM can be assigned to the Cortex{{sup|&reg;}}-A7 non-secure for using in Linux with [[Coresight overview|coresight framework]]. <br />
+
The STM can be assigned to the Cortex<sup>&reg;</sup>-A7 non-secure for using in Linux with [[Coresight overview|coresight framework]]. <br />
 
This driver allows to select the hardware events (listed in the [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]]) to log via the STM peripheral into the ETF and dump it in the Linux console for analysis.
 
This driver allows to select the hardware events (listed in the [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]]) to log via the STM peripheral into the ETF and dump it in the Linux console for analysis.
   
Line 61: Line 54:
 
==References==
 
==References==
 
<references/>
 
<references/>
  +
  +
<noinclude>
  +
{{ArticleBasedOnModel | Internal peripheral article model}}
  +
{{PublicationRequestId | 9288 | 2018-10-19 | BrunoB}}
  +
[[Category:Trace and debug peripherals]]
  +
</noinclude>