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

I3C FAQ for firmware teams covering MIPI I3C bus fundamentals, tooling and adoption in India, from GSAS
Technical Guides Binho Semiconductor Design

I3C FAQ for Firmware Teams: What the Bus Is, What Changes, and What You Need on the Bench

MIPI Alliance describes I3C as the successor to I2C, with legacy compatibility so that I3C and I2C devices can coexist on the same bus, a two-wire interface that supports in-band interrupts to reduce pin count, plus multi-controller support and dynamic addressing. This FAQ answers the questions firmware teams actually ask before adopting it.

31 Jul 2026 · 8 min read
Binho Supernova running in I3C target mode to emulate a device against a customer controller, supported in India by GSAS
Technical Guides Binho Semiconductor Design

Running the Binho Supernova as an I3C Target: Emulating a Device Against Your Own Controller

Binho specifies the Supernova's I3C role as Controller or Target, which means the same adapter can stand in as the device under test rather than only driving one. That second direction is how a team validates its own I3C controller, its ENTDAA implementation and its interrupt handling, before the target silicon exists.

31 Jul 2026 · 7 min read
Functional verification engineer in India reviewing RTL waveforms, coverage charts and a regression dashboard, Siemens Questa One and the Questa Prime to Questa One rename explained by GSAS
Questa Siemens EDA Semiconductor Design

What Happened to Questa Prime and ModelSim?

Siemens has consolidated its Questa verification line under a single brand. The Questa product hub now returns a 301 redirect to the Questa One page, the ModelSim URL redirects to Questa One Sim, and Questa Prime no longer appears on any Siemens public product page. Here is what Questa One actually contains, what Siemens says the word One means, and what Indian verification teams should check before treating this as only a name change.

31 Jul 2026 · 11 min read