Viktor Vilhelm Sonesten

After a quick look at the source code of the crate and [itmdump](https://github.com/rust-embedded/itm/blob/v0.3.1/src/bin/itmdump.rs#L96-L102), I do not think extension packet arbitration is handled correctly which may be the cause of the...

Additionally, I believe sync packets are incorrectly handled. c.f. https://github.com/rtic-scope/itm-decode/blob/400447e8e01260c2fafc463c742646f2107a2ad6/src/lib.rs#L667-L683

Another planned feature is the [bookkeeping of instrumentation packets](https://github.com/rtic-scope/itm-decode/issues/19). The API is also being refactored to mimic that of this crate (i.e., read data from a `Stream`).

Following from https://github.com/tmplt/masters-thesis/commit/70ce53f7b5724c34fd394246a10ac3b95ce7dbc4 it may be apt to inquire ARM whether the clock relationship should be interpreted as device-specific.

Ideally, the API should allow us to add an adapter upon `iter::{Timestamps,Singles}`.

Known error. Resolved in #16. Try installing with `--locked` which forces the build of yanked releases. Otherwise `HEAD` of `master`. The latter is recommended: 0.6 is no longer maintained.

`itm-decode` should also be extended to support decoding of strings in these packets.

I'm waiting for a v0.8 release of `cortex-m` (https://github.com/rust-embedded/cortex-m/issues/368) from which a singular structure is used IIRC. A quick fix would be to just copy the implementation verbatim for now,...

> Do you know what is blocking the cortex-m release? I do not. But the crate depends on `cortex_m::peripheral::itm::LocalTimestampOptions` and `cortex_m::peripheral::scb::VectActive`. However, IIRC the `VectActive` implementation used in the patched...

Addendum: the API of `itm` has been redesigned in favor of iterators, but I don't think this will be a major pain point for probe-rs.