Skip to main content
SEGGER Ozone power profiling timeline showing correlated code execution and current draw

Correlating Power Consumption with Code Execution in SEGGER Ozone's Timeline

GSAS Engineering · · 5 min read

Measuring how much current a device draws is straightforward. Understanding why it draws that current at a specific moment requires correlating power measurements with code execution, knowing which function was running, which peripheral was active, and which RTOS task was scheduled when a power spike occurred. SEGGER Ozone provides this through its Timeline window, which synchronizes power data with code-level execution on a common timescale.

Three Synchronized Panes

Ozone’s Timeline combines three panes sharing the same horizontal time axis:

Data pane. Displays sampled variable values over time. Any global variable, peripheral register, or memory location can be added as a channel, shown as a line graph. Useful for tracking state machines, buffer levels, ADC readings, or GPIO states alongside power.

Power pane. Shows device current consumption over time via the J-Link’s built-in power measurement. Current appears as a continuous waveform, sleep mode entry, peripheral activation, radio transmit bursts, and LED toggling are all visible. A single LED toggle adds roughly 6 mA of step change, providing a clear visual marker.

Code pane. Displays which code was executing at each point in time. With ETM or PTM trace data, it shows the exact program counter history, every function call, branch, and interrupt. This transforms a power measurement from “something happened at time T” into “function X in task Y was executing at time T.”

Because all panes share one timescale, clicking a power spike scrolls Code and Data to the same moment. You see current draw, executing code, and variable state simultaneously.

The panes have different hardware requirements:

Data + Power (J-Link). Any J-Link with power measurement populates the Data and Power panes. J-Link samples variables through background memory access and reads current through its measurement circuit, no additional hardware needed.

Code (J-Trace PRO). Full continuous instruction trace requires a J-Trace PRO connected to the target’s ETM trace port. J-Trace PRO captures the complete instruction stream, streamed to Ozone over USB or optionally Gigabit Ethernet for sustained sessions.

Without J-Trace PRO, the Code pane shows sampled PC values, statistical profiling rather than continuous trace. For power work, continuous trace tells you that the 15 mA spike at T=1.234s was caused by a specific TX function in a specific task. Sampled PC only tells you 40% of time is spent in the radio driver.

Practical Workflow

  1. Connect. Attach J-Link or J-Trace PRO. Open Timeline, add the Power channel and any Data channels for system state variables.

  2. Record. Run the system through operating scenarios, active processing, idle, communication bursts, sleep transitions.

  3. Navigate. Zoom and scroll to power events of interest. Click a spike to see Code and Data at that moment.

  4. Correlate. Does current spike every time a specific task runs? Does the device fail to enter sleep after a particular function? Is a peripheral left enabled too long?

  5. Optimize. Modify firmware, re-record, compare. The Timeline makes it visible whether your change reduced consumption.

Example: Task Switch Correlation

A system with three tasks, sensor, communication, idle (sleep mode). The Power pane shows a repeating pattern: low current (sleep), brief spike (sensor), low current, longer spike (communication), low current.

With Code trace, you verify the idle task actually enters low-power sleep (not a busy-wait consuming full run current). You measure microseconds between sleep entry and wake-up interrupt. You see whether communication enables the radio before data is ready, wasting current during preparation. None of these insights come from power measurement or code debugging alone, only from correlation.

Power Profiling Tools in India

GSAS Micro Systems provides Ozone, J-Link, and J-Trace PRO with INR invoicing and local engineering support. Teams in Bengaluru, Chennai, Hyderabad, Pune, Mumbai, and Delhi NCR can get assistance with setup, configuration, and power optimization workflows.

Explore SEGGER Ozone | View J-Trace PRO | Request a Quote

Interested in SEGGER 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

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
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
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