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 development bench, illustrating the hardware debug loop an AI agent can now drive, supported in India by GSAS
J-Link SEGGER

An AI Agent That Drives the Debugger: SEGGER and Embedder Connect J-Link to the Loop

SEGGER has given an AI coding agent direct control of J-Link and J-Trace: flash, breakpoints, memory inspection and live RTT on real silicon. The loop only works if the probe can read target RAM while the core runs, and GSAS field engineers know exactly where that breaks first.

13 Sept 2026 · 6 min read
Horizontal stacked bar showing where an ADAS test vehicle's bandwidth budget is spent, split into cameras, lidar, radar and bus traffic, with the logger uplink limit drawn as a vertical rule crossing the bar, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

ADAS Sensor Data Logging: Bandwidth Budgets That Add Up

Every page that tells you an ADAS test vehicle produces terabytes a day states the headline and skips the arithmetic, so you cannot redo it for your own sensor set. This article publishes the arithmetic instead: one formula, every table row derived on the page, a worked eight-hour drive that chains those rows into a sustained write rate, a media count and an offload window, and the five places bandwidth budgets go wrong. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 15 min read
Two test paths leaving the same device under test, one into a conformance suite that returns a passed report and one into a partner node that surfaces a field defect, showing why an ECU can clear a published suite and still fail in a vehicle, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Ethernet Conformance: TC8 and Testing Above It

Summarising TC8 as a layer 1 to layer 4 suite is wrong in both directions. The public OPEN Alliance ECU test documents run from transmitter distortion up to a SOME/IP chapter with its own standardised test stub, and they contain exactly one time synchronisation test case. This is what those documents enumerate, chapter by chapter, what genuinely lives above their boundary, why a passing ECU can still fail against a partner node, and how much pre-compliance work a Tier-1 in India can honestly do in-house before a test house visit. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 12 min read