You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The formulas seen in the `make_metric` macro invocation are computed by the host and will thus have zero impact on the targets performance. The `set` method on the metrics object is simply a volatile store which is quite cheap. The host will then read that value using the debug probe at regular intervals and update the graph on any changes.
@@ -54,8 +58,8 @@ cd examples/simple
54
58
cargo run # Let it flash and then cancel (Ctrl+C) to let the target continue running in the background while giving up access to the probe
55
59
56
60
cd ../probe-plotter-tools
57
-
cargo run ../examples/simple/target/thumbv7em-none-eabihf/debug/simple stm32g474retx
58
-
# Rerun will open with a graph showing all created metrics objects
61
+
cargo run --bin custom-viewer ../examples/simple/target/thumbv7em-none-eabihf/debug/simple stm32g474retx
62
+
# Rerun will open with a graph showing all created metrics objects and a panel with settings at the right hand side
0 commit comments