[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:06:20 CEST 2021


@maribu commented on this pull request.



> +
+(*) Since the switch is connected to the chip-select pin of the QSPI interface the flash chip RIOT
+is running from via XIP, the switch is difficult to read out from software. This is currently not
+supported.
+
+### Pinout
+
+![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

Theoretically yes, practically no. The issue is that multi-core CPUs need multi-drop support. And this needs to be implemented for every OpenOCD backend. E.g. the J-Link EDU mini can debug the RP2040 with the proprietary tool (so the hardware is capable), but fails to do so with OpenOCD due to missing multi-drop support in the JLink driver.

Currently, the situation is pretty dire regarding multi-drop support in OpenOCD. But this is likely going to change soon, with the RP2040 being relatively popular.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/16609#discussion_r665925263
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210708/35088066/attachment.htm>


More information about the notifications mailing list