Open lure23 opened 1 week ago
Gave it a try with rtt-target
v.0.6 (not yet published) that claims to be defmt compatible.
This feels like the way to do it. Perhaps with changing probe-rs
to cargo embed
so that there is more control of the channels on the host side (well, that's not needed just for reading terminal input).
Stage currently (compiles; doesn't launch):
$ cd basics
$ DEFMT_LOG=debug cargo build --release --features= --example prompt
Finished `release` profile [optimized + debuginfo] target(s) in 0.11s
probe-rs run --log-format '{t:dimmed} [{L:bold}] {s}' /home/ubuntu/target/riscv32imc-unknown-none-elf/release/examples/prompt
Erasing ✔ 100% [####################] 192.00 KiB @ 96.02 KiB/s (took 2s)
Programming ✔ 100% [####################] 20.86 KiB @ 2.17 KiB/s (took 10s) Finished in 9.62s
WARN probe_rs::session: Could not clear all hardware breakpoints: An error with the usage of the probe occurred
Caused by:
0: USB Communication Error
1: device disconnected
WARN probe_rs::session: Failed to deconfigure device during shutdown: Probe(Usb(Custom { kind: Other, error: Disconnected }))
Error: An error with the usage of the probe occurred
Caused by:
0: USB Communication Error
1: device disconnected
esp-hal
Matrix channel:probe-rs
andusb-serial-jtag
will work togetherCheck out:
probe-rs
configuration for this?Eventually, we should be able to (in any example):
defmt
for loggingCurrent state:
i.e. the keyboard input doesn't seem to make it to the MCU.