Skip to main content
Generating the most optimized code for Cortex-M enabled processor cores., featured image

Generating the most optimized code for Cortex-M enabled processor cores.

GSAS Engineering · · 3 min read

The processor debug is implemented by Embedded Trace Macrocells (ETM trace unit) depending on the target processor. Each ETM trace unit is specific to the processor it is designed for.

The feature set varies depending on the use cases anticipated for the different processors, but all CoreSight ETM trace units which use an AMBA Trace Bus (ATB) output can be combined in a system. Trace units might support the following:

  1. Processor execution trace in varying degrees of detail
  2. Resource logic often used as an extension to processor performance monitoring resources
  3. Filtering logic to reduce the amount of non-interesting data which is captured

The Keil Uvision Performance Analyzer utility makes use of the instruction trace collected from ETM. With the help of a real-time trace, the performance analyzer can help you identify the hot-spots in your application precisely.

The instruction trace from ETM also helps the user perform software verification and validation. The step that is mandatory for a product developed for functional safety. The trace information can be useful for customers working in the Industrial, Automotive, Medical, and Railway domains.

Timing:

Thursday, 24th September 2020 | 02:30 PM to 03:30 PM

The attendees will get to learn the following.

1. Collection of instruction trace from the ETM unit.

2. Real-time performance analysis of the embedded application.

3. Software Verification and Validation.

Event Completed

LEARN MORE ABOUT Arm Tools

Recorded webinar

Also appears in:

Interested in Arm tools?

Talk to our application engineers for personalized tool recommendations.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.

Related Articles

Embedded engineering bench in India, illustrating the hardware a developer can act on today, supported by GSAS
Technical Guides Arm

Arm's Agentic AI Push: What Indian Embedded Teams Can Actually Use Today

Arm has set out its platform strategy for the agentic era, putting inference everywhere it has compute. Indian embedded teams can start on that direction this quarter with the Cortex-M toolchain they already own: Helium, CMSIS-NN, Ethos-U and Vela, on boards you can order today.

13 Sept 2026 · 7 min read
Side by side comparison of a 10BASE-T1S multidrop mixing segment, one balanced pair with four nodes on short stubs and a termination at each end, against a point to point star of four separate links into switch ports, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

10BASE-T1S and PLCA: Multidrop Ethernet Explained

10BASE-T1S is the one member of the T1 single-pair Ethernet family that keeps a shared medium, and PLCA is the reconciliation sublayer that stops the nodes on it from colliding. This article covers what IEEE 802.3cg standardises, how the beacon and transmit opportunities schedule a cycle, the node count and segment length figures the OPEN Alliance interoperability test suite works to, and the failure modes that put a segment quietly back into contention while every link still looks up. Written by the GSAS Micro Systems engineering team in India for teams bringing up multidrop segments on the bench.

29 Aug 2026 · 12 min read
The bench to harness adapter path drawn left to right: the ECU connector, a test lead, a media converter or pluggable T1 module, RJ45, and the host, showing where each connector family sits between the device under test and the laptop, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Ethernet Connectors: H-MTD, MATEnet, MQS

An ECU arrives on the bench with a connector nobody has a mate for, and the day is gone. Search the family names and you get connector product pages that describe their own part and stop there. This article puts the families side by side in one table using only what their public pages state, then makes the point those pages leave out: the IEEE link segment definition, not the connector, is what sets reach and loss limits, and shielding is a channel decision rather than a preference. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 12 min read