-
Notifications
You must be signed in to change notification settings - Fork 882
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
Adding launch.json for the debug probe #401
base: master
Are you sure you want to change the base?
Adding launch.json for the debug probe #401
Conversation
Renamed to reflect the type of debugger. Added openocd parameter so set the correct adapter speed
Includes instructions for the debug probe
See also #349 and #380 and raspberrypi/debugprobe#49 (comment) and raspberrypi/openocd#78 |
Just to be pedantic, https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html is actually the documentation URL; the product URL is https://www.raspberrypi.com/products/debug-probe/ 😉 |
Slight aside, I would be happy to contribute small PRs to the documentation - or is that internal only? |
The documentation at https://www.raspberrypi.com/documentation/ is open for PRs at https://github.com/raspberrypi/documentation/tree/develop The PDF documentation at https://datasheets.raspberrypi.com/ isn't open, but you can submit suggestions at https://github.com/raspberrypi/pico-feedback/issues |
// This may need to be "arm-none-eabi-gdb" for some previous builds | ||
"gdbPath" : "gdb-multiarch", | ||
"serverArgs": [ | ||
"-c", "adapter speed 5000" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, would be great to document about udev rules: https://github.com/raspberrypi/openocd/blob/rp2040-v0.12.0/contrib/60-openocd.rules when using openocd with cortex-debug extension. |
Currently, none of the candidate launch.json files in the ide/vscode folder work with the (relatively new) official Debug Probe. Although similar to the pico-probe, there are some small differences. It took a considerable time to work out the changes needed to get it to work.
The proposal here is to add an additional file (and reference in the readme) with these changes. It is also labelled launch-debug-probe.json to match the product name.
The README is also updated (although I am not sure about including the URL of the product page - is that a stable URL?)