JackN

Hi @richardeoin ... I will gladly create a pull request. Before I do, I'd like to get your view on something, so that I can fix that at the same...

Hi, I would like to support @sevaa 's request for a release with experimental code. As a user of this, it is better to have a solution that **sometimes** works...

@ctron Can you please provide a little bit of additional information about your environment? For example: - Which RTT libraries are you using `defmt` or basic `rtt-target`? - Which versions...

@lulf When I clone and follow your README to run this, I get this ... ``` error[E0432]: unresolved import `embassy_futures::Either` --> display/src/main.rs:12:31 | 12 | use embassy_futures::{select, Either}; | ^^^^^^...

@lulf Thanks. That works, but all I've managed to prove is that it works on V2 as you said LOL While doing that I confirmed that V2.20 boards are on...

Does this mean the connection remains stable when you have no RTT output?

@TheButlah The problem here is if you try to set a breakpoint on a `defmt` macro that has been optimized out (hence the error message) because of a conflict with...

Important reminder ... The value of`DEFMT_LOG` in your `.cargo/config.toml` file (or whatever is in your environment when you build) determines which macro' code is optimized out of the binary. If...

PS. Finally, with `probe-rs-debugger` you do NOT need the `.cargo.config.toml` setting: ``` "-C", "force-frame-pointers", ``` By deleting this, you will find your binary is both smaller and faster :)

@TheButlah This is running into a situation where the debug info doesn't provide enough information to know where to set a breakpoint for that statement. The code to step correctly...