Closed tmplt closed 2 years ago
https://github.com/rtic-scope/cargo-rtic-scope/blob/fadf8793020a79251eb5f75c872fbbec6e36f43f/cargo-rtic-scope/src/sources/probe.rs#L19-L25
The current implementation of RTIC Scope expects the user to configure tracing targets-side by help of cortex-m-rtic-trace. The tracing setup of probe-rs is in either case not up to par with the API of cortex-m.
cortex-m-rtic-trace
probe-rs
cortex-m
https://github.com/probe-rs/probe-rs/issues/727 should be closed before we can reconsider configuring the device from the host-side again.
As the comment describes, Session::setup_swv configures both the probe and target for tracing. We'll need to keep this code.
Session::setup_swv
https://github.com/rtic-scope/cargo-rtic-scope/blob/fadf8793020a79251eb5f75c872fbbec6e36f43f/cargo-rtic-scope/src/sources/probe.rs#L19-L25
The current implementation of RTIC Scope expects the user to configure tracing targets-side by help of
cortex-m-rtic-trace
. The tracing setup ofprobe-rs
is in either case not up to par with the API ofcortex-m
.https://github.com/probe-rs/probe-rs/issues/727 should be closed before we can reconsider configuring the device from the host-side again.