Image of Board

Pico Expander by Studiolab

The Pico Expander is an expansion board that features a soldered Raspberry Pi Pico 2W, bringing its powerful RP2350 microcontroller to a more accessible form factor. This board breaks out all the Pico 2W pins to Grove connectors, making it easy to connect sensors and peripherals without soldering.

Key Features:

  • Grove Connectors: All GPIO pins are accessible via standard Grove connectors for quick prototyping
  • Neopixel Status LED: Built-in addressable LED for visual feedback
  • User Button: Connected to GPIO 15 for input control
  • Reset Pin: Dedicated reset functionality for convenient board resets
  • I2C Qwiic Connector: Native I2C support for connecting Qwiic-compatible sensors and devices

The Pico Expander retains all the performance benefits of the Pico 2W—double the processing power, RAM, and flash memory compared to the original Pico—while providing a developer-friendly interface for rapid prototyping. Whether you’re building IoT projects, sensor networks, or interactive applications, the Pico Expander simplifies hardware integration and accelerates development in CircuitPython or MicroPython.

Tutorial

Purchase

Contribute

Have some info to add for this board? Edit the source for this page here.

Absolute Newest

Every time we commit new code to CircuitPython we automatically build binaries for each board and language. The binaries are stored on Amazon S3, organized by board, and then by language. These releases are even newer than the development release listed above. Try them if you want the absolute latest and are feeling daring or want to see if a problem has been fixed.

Previous Versions of CircuitPython

All previous releases of CircuitPython are available for download from Amazon S3 through the button below. For very old releases, look in the OLD/ folder for each board. Release notes for each release are available at GitHub button below.

Older releases are useful for testing if you something appears to be broken in a newer release but used to work, or if you have older code that depends on features only available in an older release. Otherwise we recommend using the latest stable release.