Closed bplaat closed 1 year ago
This is because we changed the wire format but missed bumping the wire format version. Updating your defmt
should fix this.
The latest version of defmt on crates.io (0.3.4
) still suffers from this issue.
A temporary workaround is using the defmt
repository directly.
defmt-rtt 0.4
requires defmt 0.3.4
, so doing defmt = { git = ... }
won't work. patch.crates-io
can be used instead.
[dependencies]
defmt = "0.3.4"
defmt-rtt = "0.4"
[patch.crates-io]
defmt = { git = "https://github.com/knurling-rs/defmt" }
https://github.com/knurling-rs/defmt/pull/750 adds backwards compatibility for wire format 3. This will get released soon.
Describe the bug I have a small micro-controller Rust project that uses defmt and probe-run. It worked fine with
probe-run 0.3.6
. But when I want to run the program withcargo run --release
withprobe-run 0.3.7
, I got this error:To Reproduce Steps to reproduce the behavior:
Example
src/main.rs
// ..
use {defmtrtt as , panicprobe as };
[entry]
fn main() -> ! { loop { defmt::info!("Test"); } }
config.toml The contents of your project's
.cargo/config.toml
file:Cargo.toml The contents of your project's
Cargo.toml
file:Probe details
Operating System: Windows, on WSL (Ubuntu) I get the same issue
Additional context Maybe I forgot something stupid or maybe the JSON symbol info really is missing a field :|