[riot-notifications] [RIOT-OS/RIOT] cpu/rpx0xx: port RIOT to the Raspberry Pi RP2040 MCU (#16609)

Marian Buschsieweke notifications at github.com
Thu Jul 8 09:13:53 CEST 2021

@maribu commented on this pull request.

> +![Pinout Diagram of RPi Pico](https://projects-static.raspberrypi.org/projects/getting-started-with-the-pico/f009ad94826c2f0cd7573a295897e76955301096/en/images/Pico-R3-Pinout.png)
+## Flashing the Board
+### Flashing the Board Using OpenOCD
+Currently (June 2021), only two methods for debugging via OpenOCD are supported:
+1. Using a bit-banging low-level adapter, e.g. via the GPIOs of a Raspberry Pi 4B
+2. Using a virtual CMSIS-DAP adapter provided by the second CPU core via
+   https://github.com/majbthrd/pico-debug
+Since option 2 requires no additional hardware, this is currently the default. However, you need to
+first "flash" the gimme-cache variant of [pico-debug](https://github.com/majbthrd/pico-debug)
+into RAM using the UF2 bootloader. This will result in the Raspberry Pi Pico showing up as
+CMSIS-DAP debugger. Afterwards run:

The pico-debug .uf2 firmware needs to be copied into the virtual FAT flash drive. Upon unmounting that, the virtual flash drive will disappear and a CMSIS debugger will pop up. I could extend the documentation in this regard a bit, but I'd personally rather just keep the reference to pico-debug and let users read the upstream documentation.

This is not handled by the build system.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210708/647dbd09/attachment.htm>

More information about the notifications mailing list