Currently, for Raspberry Pi RP2040, we have two repos that use the Arduino ecosystem.
Official ArduinoCore-mbedfrom Arduino that is based on
Arduino APIsrunning on top of
Earle Philhower's Arduino-Picobased on the
Arduino APIsand uses the
Official Raspberry Pi Pico SDKand a custom
GCC 10.3/Newlib 4.0 toolchain.
At the moment only the
Official ArduinoCore-mbed is supported by PlatformIO.
I don’t know how much of an effort it would be to add
PlatformIO support for the
Earle Philhower's Arduino-Pico as an additional RP2040 framework but it would make a great addition.
I suspect (and hope) that since the
Arduino-Pico core is based on the Arduino ecosystem, the integration may not be too involved.
Raspberry PI Pico SDK based
Arduino-Pico core has a number of potential advantages over the
Official ArduinoCore-mbed core. The chief being that as Raspberry Pi Organisation updates their SDK, we can leverage the new features, PIO enhancements, as well as existing SDK features that may not necessarily be in the
Official ArduinoCore-mbed core.
At the same, the
Arduino-Pico can use the same Arduino APIs as the Official ArduinoCore-mbed` except for the specific Mbed-OS features.
I’m sure a lot of Raspberry PI RP2040 users would, very much, welcome PlatformIO to support the Raspberry Pi Pico SDK. The best of both worlds!
Further down the line, we’ll get
RP2040 Zephyr-RTOS support. There is already an early alpha for the Raspberry Pi RP2040 in
zephyrproject-rtos/zephyr. Although there has been a demo of the
hello_world running on a
Adafruit_qt_py_rp2040 under Zephyr v2.5.0, there is much to do on the devicetree & soc. No doubt, we’ll get Zephyr onto the RP2040.
What are your thoughts on adding PlatformIO support for Earle Philhower’s Arduino-Pico? Please review for consideration. Thank you.