I recently published itm-decode before stumbling upon this crate just now. Comparing the two after a cursory dive, itm seems a bit more general with its application of traits; itm-decode has a more granular error enum, to help with trace streams that diverge from the specification; #34 is being implemented, and an ITM encoder may eventually be implemented for testing purposes with some other tools I'll be implementing as part of my master's. I have yet to compare the test benches. bin/itm-decode.rs shares some features with itmdump.

Perhaps the crates should be merged?