P33M

@a-pushkin @newbrain @rewolff @fduxiao thank you for your contributions to this project, however we have a request. Some of your edits were to the file [CMakeLists.txt](https://github.com/raspberrypi/debugprobe/blob/master/CMakeLists.txt) and this file was...

@rewolff Thanks for confirming. probe_oen.pio attribution has been resolved in https://github.com/raspberrypi/debugprobe/commit/9aed4ca509bbe0dc5a60358b51717e37fa72060e pico_sdk_import.cmake has been clarified as to the original file's license in 8f5d6fc I will ping the other authors again...

I have removed the remaining unattributed lines surviving in the project, asked @andygpz11 to do a cleanroom reimplementation of the missing functionality, and have tagged it as MIT licensed. https://github.com/raspberrypi/debugprobe/commit/65b1e73589f7248a6208b0bdcc32c8b8e7e169ee...

I probably should have read this PR before banging my head against tcl in https://github.com/P33M/openocd/commit/a2e24ea5812aa4833a03d0aa4bcc003a1dca1b18. This is a workable implementation - but please fold into the base rp2350.cfg. In effect...

Can you post a log of a successful RTT 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?

QoS for PCIE2 is already set high. I think it's a manifestation of https://github.com/raspberrypi/linux/commit/0a19b5256303d2f35be9272832b01a170c9a039b What happens if you run iperf (or ping flood) on the Pi 5 at the same...

I have a WD PC SN530 256GB w/ firmware 21160001 and it works in the official M2 HAT+. The HAT power cycles the drive across a reboot, this is required...

Does this issue still exist with latest probe firmware and VScode extension?

If you can point to a specified minimum/maximum setup/hold time that a SWD probe should respect and debugprobe violates, I will investigate.