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 verification and unit test workflow, illustrating the economics of finding defects early, supported by GSAS Micro Systems in India
Technical Guides

Verification Economics: What a Late Defect Actually Costs, and What the Evidence Really Says

Finding a defect in month 2 instead of month 14 is a budget decision before it is a quality decision. This sets out what the published evidence supports, what it does not, including the 100x multiplier that traces back to a course handout rather than a study, and how an Indian embedded team builds the case on its own numbers.

21 Sept 2026 · 14 min read
Master and slave roles on a 100BASE-T1 link: the master PHY times its transmitter from a local clock, the slave recovers the clock from the received signal, with the both-master and both-slave misconfigurations that leave the link down, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

100BASE-T1 Link Won't Come Up: A Vendor-Neutral Checklist

A 100BASE-T1 link that will not come up is almost never a mystery, but the answers on the web are written per silicon vendor and do not transfer. This is the ordered bring-up checklist that holds regardless of which PHY, switch or SoC you have: physical layer first, then the PHY over MDIO, then the master and slave pairing, then the causes of a link that comes up and drops. The standards and tooling claims trace to IEEE 802.3 task force records, the Linux ethtool and kernel documentation or published test material. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 14 min read
Storage sizing ladder for automotive data logging: four rungs stepping from an aggregate link rate of 1 Gbit/s to 125 MB per second, then 450 GB per hour, then 3.6 TB per eight-hour shift, then 18 TB per five-day week, in decimal units, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Data Loggers: Capture Without Loss

Search for an automotive data logger and the results split into cheap OBD dongles at one end and enterprise ADAS recorders at the other, with nothing in between explaining the engineering that decides whether you lose frames. This is the loss budget end to end: mirror oversubscription upstream of the logger, encapsulation overhead on the capture path, sustained write rate against burst rate, rotation stalls, and storage arithmetic worked in full so you can redo it with your own numbers instead of trusting ours. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 13 min read