Runner hangs at resetting device when using async-embedded. about probe-run

[japaric]

Runner hangs at resetting device

Our error handling may be a bit off. This scenario corresponds to the case where RTT logging is not available (or detected as not available) and you should get this message: "No log messages to print, waited for device to halt" before probe-run blocks.

probe-run not correctly detecting the availability of RTT logs may have already been fixed in #25. I probably can make a new release with that included soon. In the meantime I would suggest running optimized programs (cargo run --release); that should help in your case I think.

If running an optimized program still doesn't work could you point to the exact source code you are running? Either that or you could run rust-nm -C target/thumbv7em-none-eabi/debug/app-name (and release folder too) and let me know if _SEGGER_RTT appears in the output.

[matoushybl]

Running the code in release mode worked, both the resulting binaries contain the _SEGGER_RTT section.

Thanks, will try with the new version when available.

[japaric]

@matoushybl is this still an issue with the crates.io version of defmt and/or probe-run v0.1.4?

[matoushybl]

I'll check it asap.

[matoushybl]

I believe that this issue can be closed for now. I ran the async-on-embedded only as an experiment and I don't have the source code now. If I ever try it again and it happens, I'll definitely report it here.