DOCS/VIEWALYZER/THE VIEWS
VIEWALYZER · GPUI EDITION
The views
Each view is a panel in the dock, opened from its card in the top bar. All of them read the recording that is loaded (or streaming); none of them invents data. Where a view needs something extra, its page says so at the top.
| VIEW | ONE LINE | NEEDS |
|---|---|---|
| Timeline | Task, interrupt and user-event lanes over time; the anchor every other view jumps to | a recording |
| Event Table | Every decoded event, searchable, following the cursor | a recording |
| Trace | Your firmware's trace channels as charts, live while recording | a recording or a live capture |
| CPU | Busy gauge, per-task statistics table, scoped to the whole trace or a selection | a recording |
| Analyzer | Findings: priority inversions, jitter outliers, failed operations, domain verdicts | a recording |
| Details | The system at a glance, plus everything about one selected task slice | a recording |
| Overview | The report: file, trace, system and task summary, copy as Markdown | a recording |
| Timers | Kernel timers and deferred work as arm-to-outcome cycles, with lateness | a recording with timer events |
| Comms | Message paths between tasks: queues, semaphores, mutexes, notifications | a recording with kernel-object events |
| Fingerprint | Golden-run baselines: save the recording's metrics, gate later runs, pins and envelopes | a recording |
| Profiler | Statistical PC profile: functions, hotspots, annotated source | PC sampling on, an ELF |
| Symbols | Browse the ELF and poll variables over the debug port, no instrumentation | an ELF |
| Memory | Flash and RAM usage of the build, section by section | an ELF |
| Call Graph | Who calls whom, decoded from the image's code; walk from any root to a depth | an ELF |
| Trace Tune | Node graph that derives new traces from existing ones (filters, PID, math) | traces |
| Trace Domains | Sidebar section and Domain Editor for .vadomain descriptors | optional |
| ITM Console | printf text from the ITM stimulus ports, on the recording's clock | the SWO source, On-chip trace |
| Exception Trace | Interrupt entry / exit / return from the hardware, with durations and nesting | the SWO source, On-chip trace, Exception Trace on |
| Data Trace | Data-watch values as hardware lanes, with the accessing instruction when traced | the SWO source, On-chip trace, a watch |
| Event Counters | The DWT profiling counters and a measured CPU load | the SWO source, On-chip trace, a counter on |
Views listed in the top bar that are not covered here yet (Registers, On-chip Trace) open to a short message saying what they will need. They are on the way; this guide grows with them.
Reading the tables
Tables share one behaviour: click a column header to sort by it, click again to flip the direction. Columns flex to fill the panel and never shrink below their design width; below that the table scrolls sideways (there is a scrollbar under it). Numbers are right-aligned and monospaced.
Chips and pills
Small rectangular chips appear in toolbars and headers. A chip with a highlighted border is active; clicking it toggles a filter, a scope or a view mode, and the panel's status strip says what is in effect.
Hardware trace views
The last four views read the core's own DWT and ITM packets rather than the recorder, and carry a DWT (SWO) pill to say so. What to switch on, what each core supports and how much the SWO pin can carry are on the Hardware trace page.