raspberrypi
RTT is marked "TODO" but works for me
The README states:
TODO Possibly include RTT support
However, I've successfully used the probe with TinyGo in RTT output mode with success.
It seems to me the TODO is fixed, or perhaps I missed something?
What does a log look like? I ran tinygo -target pico2 -serial=rtt -monitor ... and saw output from my program running on a rp2350, through a pico probe.
And if you e.g. do a printf() on the Pico that ends up in an RTT buffer, does that get correctly reproduced on a console on the debug host?
Im using a pico with the firmware from this repo as a debug probe, and a second pico to run my actual software. RTT works very well for me. Ive tested the pico 1 and 2 in all combinations. Works flawless. Im using cargo embed with absolute default config, together with rtt_target, with also default configuration. Using rprintln!("...") shows up just fine in my host-os-terminal.
RTT also seems to work with OpenOCD/GDB. I've run a slightly modified debugprobe firmware (the only changes were values on include/board_pico_config.h) with a Pico 2, and stdout works fine with address 0x200007dc and size 0x30. Though I can only see the output if I start a server from OpenOCD and listen to it, as it doesn't show the output on the console as it does with semihosting for example, and the "rtt start" command must run after stdio_rtt_init has finished.
I have not tested stdin yet, but RTT is at least partially implemented, so being marked as TODO on the readme seems misleading.
