-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update needed to "Raspberry Pi Debug Probe" for PICO 2 #4003
Comments
Someone pointed out on Raspberry PI Forums that instructions for building openocd for PICO 2 is are included in Appendix A of https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf. I think that information belongs with the rest of the Debug Probe documentation here: https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html. |
See also #3831
That's a good point. @P33M and @XECDesign we currently have openocd 0.12.0-1+rpt1 (which supports RP2040) in our APT repos, but it probably ought to be updated to a version that supports RP2350 ? |
I haven't heard anything from any maintainer of our OpenOCD fork asking for the package to be updated, so I assume it's not ready yet. |
I guess the process for updating openocd for raspberry pi os would include upstreaming the RP2350 changes to the main openocd repo and then waiting for an official version. In the meantime I think it would be sufficient to update the debug probe documentation providing a link to appendix A of "Getting started with Raspberry Pi". I wasted a couple of finding raspberry pi openocd repo and figuring out how to build it. Lastly, I agree with issue #3831. |
I see two issues that need to be addressed.
There is no PICO2 H. Need to describe manually installing headers.
The openocd version available on the PI 4 bookworm does not support the 2350.
I eventually found the repo https://github.com/raspberrypi/openocd/tree/sdk-2.0.0 and built openocd.
Not trivial.
You need to either provide a detailed recipe or provide downloadable binaries.
The text was updated successfully, but these errors were encountered: