From 6f16fb7d0ffece7d4c8f462e41047e39c434c598 Mon Sep 17 00:00:00 2001 From: Markus Werle Date: Thu, 6 Nov 2025 09:01:09 +0100 Subject: [PATCH] Enhance documentation for Raspberry Pi debugging setup For people new to the topic, it is not evident that a combination of hardware and software is meant. This changeset adds links to both. Also, I added some words and rephrased a sentence that lacked a verb. --- src/modm/board/rp_pico/module.lb | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/src/modm/board/rp_pico/module.lb b/src/modm/board/rp_pico/module.lb index 0fbc999389..8572f62226 100644 --- a/src/modm/board/rp_pico/module.lb +++ b/src/modm/board/rp_pico/module.lb @@ -32,16 +32,14 @@ to the mounted virtual disk. ### OpenOCD -Another option is to use Picoprobe and custom version of OpenOCD provided by RPi. +Another option is to use the [Raspberry Pi Debug Probe](https://www.raspberrypi.com/products/debug-probe/) together with the [Raspberry Pi Picoprobe software](https://github.com/raspberrypi/debugprobe) and a custom version of OpenOCD provided by RPi. You would need to build and program one of the boards with the Picoprobe firmware, configure and build RPi OpenOCD, and connect the boards via SWD. -The wiring diagram and detailed description is available in the +The wiring diagram and detailed description are available in the [Pico Documentation](https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf#Appendix%20A:%20Using%20Picoprobe). -The how-to shows steps for building and installing the RPi OpenOCD into your -system globally, however, if you still want to be able to work with other OpenOCD -binaries, you should only install it locally: +The how-to explains how to build and install the RPi OpenOCD globally, but if you want to keep using other OpenOCD binaries, you should install it only locally: ```sh sudo apt install automake autoconf build-essential texinfo libtool libftdi-dev libusb-1.0-0-dev