Viktor Vilhelm Sonesten

Relevant snippets from documentation:  

Also related, on account of the different groupings (singular task events in the first output, back-to-back events in the second output): 

Do we see this because state transitions between tracing instances? That is, are we supposed to power cycle the device each time?

> Do we see this because state transitions between tracing instances? This is defenitely the case when using the system clock as the local timestamp clock. Timestamps of an initial...

`itm-decode` also yield different timestamps when using different baud rates on the SWO pin, set via SWOSCALER: 1Mbps: ``` ExceptionTrace { exception: Interrupt { irqn: 12 }, action: Entered }...

With a smaller prescaler more events are then considered to be back-to-back (no idle time) and insight into the exact timestamps of singular events are lost, but a higher throughput...

But why would timestamp resolution change becauce `SWOSCALER` is changed? 

[ARM IHI 0029E]: > CoreSight systems can include the following trace sinks: > - *Trace Port Interface Units* (TPIUs) > - *Embedded Trace Buffers* (ETBs) > - *Trace Memory Controllers*...

All echoes that aren't CSV will have to be done to `stderr`.

Some thoughts: - should we just drop the messy frontend implementation is favor of simply talking CSV? Doing so would increase modularity and decrease complexity and code that need to...