Arm CoreSight overview

Revision as of 14:12, 6 January 2021 by Registered User (→‎Software frameworks)


Renaming.png This page is a candidate for renaming (move).
The requested new name is: Arm CoreSight peripheral .
The supplied reason is: NSA : remove the 'S' at the end of peripheral, to be confirmed by MT .
-- Registered User (-) 09:13, 6 January 2021 (CET).
Wiki maintainers: remember to update the pages that link this page before renaming (moving) it.


1. Article purpose[edit source]

The purpose of this article is to give information about the Arm® CoreSight subsystem.
It explains what are the principle peripherals of this subsystem.

2. Peripheral overview[edit source]

Arm® CoreSight products include a wide range of trace macrocells for Arm® processors, system and software instrumentation and a comprehensive set of IP blocks to enable the debug & trace of the most complex, multi-core SoCs. Arm® has defined an open CoreSight architecture to allow SoC designers to add debug & trace capabilities for other IP cores in to the CoreSight infrastructure.

Alternate text
CoreSight overview

2.1. Components description[edit source]

The debug features are based on Arm® CoreSight™ components:
• SWJ-DP: JTAG/Serial-wire debug port
• AXI-AP: AXI access port
AHB-AP: AHB access port
APB-AP: APB access port
ITM: Instrumentation Trace Macrocell
• DWT: Data Watchpoint and Trace
ETM: Embedded Trace Macrocell
• ETF: Embedded Trace FIFO
• TPIU: Trace Port Interface Unit
• SWO: Serial Wire Output
• CTI: Cross Trigger Interface
• CTM: Cross Trigger Matrix
• TSGEN: Timestamp Generator
STM: System Trace Macrocell
More information about these components can be found in the Arm® documents referenced [1]

2.2. 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 really implemented.

2.3. Security support[edit source]

The Arm® CoreSight is a non secure peripheral.

3. Peripheral usage and associated software[edit source]

3.1. Boot time[edit source]

The Arm® CoreSight is not used at boot time.

3.2. Runtime[edit source]

3.2.1. Overview[edit source]

Internal peripheral generates a trace stream, namely instruction traces, depending on instructions and events happening when CPUs are executing a program. This encoded stream can be then stored in a dedicated SRAM via a buffer and/or extracted through an external port.

3.2.2. Software frameworks[edit source]

Internal peripherals software table template

| Trace & Debug
|  Arm CoreSight 
| 
| 
| 
|
|-
|}

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

4. References[edit source]

  1. [1. IHI 0031C (ID080813) - Arm® Debug Interface Architecture Specification ADIv5.0 to ADIv5.2, Issue C, 8th Aug 2013.
    2. DDI 0480F (ID100313) - Arm® CoreSight™ SoC-400 r3p1 Technical Reference Manual, Issue F, 26th Sept 2013.
    3. DDI 0461B (ID010111) - Arm® CoreSight™ Trace Memory Controller r0p1 Technical Reference Manual, Issue B, 10 Dec 2010
    4. DDI 0314H - Arm® CoreSight™ Components Technical Reference Manual, Issue H, 10 July, 2009
    5. DDI 0403D (ID100710) - Arm® v7-M Architecture Reference Manual, Issue Derrata2010_Q3, November 2010
    6. DDI 0468A (ID101712) - Arm® CoreSight™ ETM™-A7 r0p0, Issue A, 12 Sept 2011
    7. DDI 0440C (ID070610) - Arm® CoreSight™ ETM™-M4 r0p1 Technical Reference Manual, Issue C, 29 June 2012
    8. DDI 0528B (ID062514) - Arm® CoreSight™ STM-500 System Trace Macrocell r0p1 Technical Reference Manual, Issue B, 11 March 2014
    9. DDI 0464F (ID051113) - Arm® Cortex®-A7 MPCore™ r0p5 Technical Reference Manual, Issue F, 11 April 2013],Arm® documents referenced