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

FPGA in the loop verification workflow between Simulink and a Zynq-7000 development board
Technical Guides Digilent

ZedBoard FPGA-in-the-Loop: HDL Verifier vs HDL Coder

Teams asking for FPGA-in-the-Loop on a ZedBoard usually name HDL Coder and SoC Blockset. FIL is actually HDL Verifier. Here is the correct product split, the JTAG versus Ethernet decision, and the 2015-era advice that is still sending Indian teams down the wrong path.

5 Aug 2026 · 9 min read
FADOS MUX test station on an Indian EMS line generating a board test report, GSAS FADOS reporting workflow
FADOS CBT Electronic

FADOS Test Reports and GSAS Agent: Turning Board Test Results into an Auditable Record

A pass or fail on the FADOS screen is not a record. This guide covers what the FADOS test report contains, what GSAS Agent does with it, and how offline, Google Drive and LAN modes put a QR-linked report on the job card for repair shops and EMS lines in India.

4 Aug 2026 · 8 min read
Classification tree and combination table used to design embedded unit test cases in Razorcat's Classification Tree Editor for TESSY, available in India from GSAS Micro Systems
Compliance & Safety Razorcat Automotive & Mobility

Test Case Design with the Classification Tree Method: Deriving Unit Tests You Can Defend in an Audit

Ad-hoc test cases can be perfectly good tests and still fail an audit, because nothing on file records why that particular set was sufficient. The Classification Tree Method derives test cases from the input space instead: identify the test-relevant aspects as classifications, partition each into equivalence classes, then combine leaf classes in a combination table. Razorcat implements CTM in the Classification Tree Editor, available integrated into TESSY or standalone. GSAS Micro Systems is the authorized Razorcat engineering partner for India, the UAE and Sri Lanka.

1 Aug 2026 · 10 min read