Overview

A report-style summary of the loaded recording, written to be read top to bottom and pasted into a bug report.

Needs: a recording. The memory section needs an ELF.

Sections

SECTION	CONTENT
File Information	The file's path and size, and when it was captured
Software Trace	Transport and decode statistics: events, Corrupt Data, Event Loss, the recording's span and clock
Hardware Trace	When PC sampling or exception trace was on: sample counts, source, span
Domain Trace	When enabled Trace Domains contributed channels or verdicts: what they sampled and found
System Information	The RTOS and CPU clock the firmware reported, task and interrupt counts
Task Breakdown	One row per task: CPU share, runs, stack headroom
Memory Summary	Flash and RAM totals of the build, from the ELF set under ELF / Symbols
External Instrument	When a bench instrument's series were merged into the recording: the instrument, its channels and the clock sync figures

Copy

The Copy button puts the whole report on the clipboard as Markdown, with tables that render in an issue tracker or a chat message. It is the fastest way to describe a recording to someone who does not have the file.

Stream integrity

Corrupt Data means bytes arrived but could not be decoded reliably.
Event Loss means the recorder's sequence numbers jumped, proving events did not arrive.

Click ? for the same explanation in the app. Highlights cycles through both kinds, each kind separately, and off. When the recording contains location data, the Timeline, Trace charts, and Event Table show where each incident occurred.

Tips

Stream Integrity is the first thing to check when a recording looks incomplete. Corrupt bytes and missing events are counted separately because they describe different failures.

START HERE EMAIL SUPPORT