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

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
Split panel diagram comparing one control message on a shared multidrop CAN bus with one sensor stream on a switched point to point Ethernet link, labelled shared bus arbitration, node, point to point link, switch, control message and sensor stream, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

CAN vs Automotive Ethernet: When to Use Each

CAN and automotive Ethernet answer different questions, so the useful comparison is a decision table rather than a winner. This guide from GSAS Micro Systems sets CAN and CAN FD figures from CAN in Automation next to the IEEE 802.3bw objectives for 100BASE-T1, covers arbitration against switch queues, cost and harness consequences, failure modes on both sides, and what changes on an India bench team's setup when a project adds Ethernet next to the CAN it already runs.

29 Aug 2026 · 14 min read
Side by side vehicle outlines comparing a domain E/E architecture grouped by function against a zonal E/E architecture grouped by physical location, with zone controllers on an Ethernet backbone into central compute, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Domain vs Zonal E/E Architectures Explained

Domain architectures group ECUs by function, zonal architectures group them by where they sit in the vehicle. This guide is the engineer's read on the difference: what physically moves, what the in-vehicle network has to become, and what happens to diagnostics, rest bus simulation and time sync. It also refuses to repeat the harness mass and ECU-count figures that circulate without a public source, and says exactly which claims are citable and which are not. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 13 min read