Viktor Vilhelm Sonesten
Viktor Vilhelm Sonesten
That is, return a `Vec` of ready lines instead of the first ready line.
[cargo-xtask](https://github.com/matklad/cargo-xtask/) seems like a better way to test the `cargo-rtic-scope` binary.
In `RTICScopeError::render` the error must be printed via `{:?}`, but this breaks the layout style. Additionally, diagnostics for some errors (at least `RecoveryError`) are not propagated, and thus not printed.
With the current implementation reported timestamps are different when `tpiu_baud` changes. With `tpiu_freq = 120000000` and `tpiu_baud = 1000000`: ``` Frontend /home/tmplt/.cargo/bin/rtic-scope-frontend-dummy: @2084 ns (+2084) [good]: [Task { name: "app::hardware",...
As mentioned in https://github.com/rtic-scope/cargo-rtic-scope/commit/f2a73dabf540baa20642e0ed9345c79f6397a06e, the new CMSIS-DAP implementation is buggy. Investigate the cause and fix.
[As documented](https://github.com/rtic-scope#why-am-i-getting-an-erroneous-trace) we'll need to investigate the use of the ETB in order to robustly read the trace stream from the target from device start. This will be limited to...
Some `--export-csv` flag should be added to that the resolved trace can easily be piped into whatever post-processing program one can come up with. The CSV will have to be...
This flag is theoretically useless. It's no longer necessary; see #119. Should malformed packets be removed from the API and from `itm` too?
https://github.com/probe-rs/probe-rs/pull/916 has now been merged so we can drop the `feat/swo-read` pin, but for that we need to update to `clap 3.0` in order to apply the updated `probe-rs-util`. This...
We don't need two comparators: we can use a single bit to denote if the task was entered or exited. This leaves 7 bits for the task ID, which is...