cargo-rtic-scope
cargo-rtic-scope copied to clipboard
Non-intrusive ITM tracing/replay toolset for RTIC programs with nanosecond timestamp accuracy.
Fixes broken build due to yanked funty release.
Currently, the various packages of rtic-scope require *nix IOTCTL commands for communicating with the TTY and there's some unix socket streams used as a mechanism to move data between the...
This is tracking issue for upstream issues/PRs that must be closed/merged before we can publish v0.3.0 of RTIC Scope to the crate registery. Namely: - [ ] https://github.com/rust-embedded/cortex-m/issues/368 - [x]...
When https://github.com/rtic-scope/atsame-example was implemented software task exit trace packets were not always emitted. https://github.com/rtic-scope/cargo-rtic-scope/commit/c492f82d27b1456c962795641770548749e1fea3 was an attempt to fix this but it did not resolve the issue completely as it...
See https://github.com/atlas-engineer/nyxt/blob/master/.github/workflows/release.yaml for inspiration. When a tag is pushed: - automate a github release; - publish to crate registery
See https://www.brendangregg.com/flamegraphs.html The whole website seems like an interesting read. We can probably find something to help us visualize traces of RTIC applications.
A lot of required fields are now expected in cargo manifest metadata. I predict more will end up there. It may be a better idea to read these parameters from...
https://github.com/rtic-scope/cargo-rtic-scope/blob/20d4b1c0bcd011253439f4beb1c57433bf8e369c/cargo-rtic-scope/src/main.rs#L222-L227
The replay test was disabled in decc2827dfc3ee0a84ef4ebd11237cb5696f7ca8 and should be re-enabled.
That is, return a `Vec` of ready lines instead of the first ready line.