JohnK1987
commented
1 year ago From my point of view there are no special actions required. It is same like when you have any other target based on same MCU. For example STM32F411. So same logic will be applied to RP2040. Our responsibility is just update target.json and wiki page (this section is exactly for this case) for every target what we will want to add officially, the rest could be custom targets. I have already Nano RP2040 Connect on my table, but I am doing on STM32H5 at this moment.
There are a number of different boards with the RP2040 device mounted; you can actually see them defined in the pico SDK under pico-sdk\src\boards\include\boards. Most of them are pretty similar, but some of them have different LED pins, default SPI pins, or oscillator settings. Additionally, some of them have larger flash chips than the default 2MB, and some of them need different secondary bootloaders (SBLs).
We need to come up with some way to handle these variant boards in Mbed CE. Likely this would mean creating a new entry in targets.json for each board that we want to support with the appropriate settings.