RP2350 has a "B" variant chip which could conceivably be configured in a board variant (big and small versions) and require its own, separate pins.csv config with the additional pins configured.

This may apply also to W and non-W versions where the CYW43 might needWL_GPIOn pins specified but there are otherwise few meaningful changes to justify entirely separate boards.

Finally the RM2 module support added by#16057 might need optionalWL_GPIOn pins configured for traditionally non-W boards with added support for an external wireless module, though this is contentious since those pins wont be available without an attached module.

This PR is mostly to address point 3, in an effort to make the changeset in#16057 smaller and easier to review.

But it's also counter-intuitive to have support for variants without support for specifying variant versions of config files.

Testing

TODO! This would need a rebase of#16057 assuming this is even the way we want to approach the problem.

Trade-offs and Alternatives

I don't think there are any real downsides to this feature, though it should probably be reflected across all CMake-based ports.

ports/rp2: Make pins.csv configurable.

b3713b0

Allow mpconfigboard.cmake to specify a custom MICROPY_BOARD_PINS tooverride ${MICROPY_BOARD_DIR}/pins.csv.Signed-off-by: Phil Howard <github@gadgetoid.com>

Copy link

github-actionsbot commentedMar 28, 2025

Code size report:

   bare-arm:    +0 +0.000% minimal x86:    +0 +0.000%    unix x64:    +0 +0.000% standard      stm32:    +0 +0.000% PYBV10     mimxrt:    +0 +0.000% TEENSY40        rp2:    +0 +0.000% RPI_PICO_W       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS  qemu rv32:    +0 +0.000% VIRT_RV32