You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would need CircuitPython API to select the MCU pins to use.
We also may want to consider adding ssl to boards with enough resources that would not ordinarily have it (this would also expand the set of boards that could use WIZnet ethernet as an SPI peripheral with ssl).
I don't see mention of this module on the Raspberry Pi site, but it is incorporated in 3rd-party products, for example @pimoroni RM2 breakout and Pico Plus 2 W.
The RM2 module incorporates the same mux'ing of its DI, DO, and IRQ pins as the Pico Plus 2 W so building a CP board port for a Pico Plus 2 board with the module SP/CE attached should be straightforward.
Of course that approach leads to a proliferation of board ports, so some means of separately supporting RM2 might be a good thing.
Would need CircuitPython API to select the MCU pins to use.
We also may want to consider adding
ssl
to boards with enough resources that would not ordinarily have it (this would also expand the set of boards that could use WIZnet ethernet as an SPI peripheral withssl
).I don't see mention of this module on the Raspberry Pi site, but it is incorporated in 3rd-party products, for example @pimoroni RM2 breakout and Pico Plus 2 W.
Related:
CircuitPython Bump cyw43-driver module to v1.0.4 plus to match SDK 2.0.0. #9775
MicroPython Pico 2 W changes #16057
The text was updated successfully, but these errors were encountered: