Raspberry Pi Pico W

The Raspberry Pi Pico W is a dual-core ARM Cortex-M0+ microcontroller at 133MHz with WiFi, BLE 5.2, 2MB flash, and 264KB SRAM for around six dollars. It runs MicroPython or C/C++ — not Linux — and competes directly with the ESP32-C3 as a budget WiFi-enabled microcontroller. The unique PIO state machines enable custom hardware protocols without dedicated peripherals.

Where to Buy

PIO: The Pico's Secret Weapon

The RP2040's Programmable I/O (PIO) subsystem is genuinely unique. Eight state machines run tiny programs independently of the CPU cores, generating precisely timed digital signals. This enables protocols like WS2812 LED control, VGA video output, DPI display interfaces, and custom serial protocols without any CPU overhead. Each PIO state machine executes from a 32-instruction memory, running at up to the system clock speed (133MHz) with deterministic, cycle-accurate timing.

No ESP32 or Arduino has an equivalent feature. The ESP32's RMT (Remote Control Transceiver) peripheral handles WS2812 LEDs and IR protocols, but it is hardwired for specific signal patterns. PIO is a programmable processor — you write tiny assembly programs that define any digital protocol you need. Community examples include HDMI output, SD card interfaces, Ethernet MAC, logic analyzer capture at 100MHz+, and even a USB host stack implemented entirely in PIO. The ability to generate and parse arbitrary digital protocols makes the Pico the go-to board for interfacing with unusual or legacy hardware.

For sensor projects, PIO enables reading from multiple sensors simultaneously without CPU involvement. A typical example: one PIO state machine reads a DHT22 temperature sensor's proprietary single-wire protocol, another drives a string of WS2812 LEDs based on the temperature, and a third handles a custom serial display — all while both CPU cores are free to run your WiFi web server and data logging code. This parallelism is the Pico's real advantage over ESP32 boards, where the CPU must bit-bang non-standard protocols.

MicroPython vs CircuitPython Experience

The Pico W supports both MicroPython and CircuitPython, and the choice matters more than most beginners expect. MicroPython is the official Raspberry Pi recommendation — the Foundation contributed significant WiFi and BLE driver work, and the official documentation (the free "Connect to the Internet with Raspberry Pi Pico W" PDF guide) uses MicroPython exclusively. CircuitPython, maintained by Adafruit, offers a slightly different philosophy: it appears as a USB drive where you drag-and-drop code files, and includes a larger standard library of pre-built sensor drivers.

For WiFi projects, MicroPython on the Pico W has matured significantly since the board's 2022 launch. The network.WLAN interface handles connection management, and the urequests library handles HTTP. MQTT via umqtt connects to Home Assistant, AWS IoT, or any broker. A simple temperature-logging web server takes about 40 lines of MicroPython — readable enough that a beginner can understand every line. The official Raspberry Pi MicroPython documentation is arguably the best-written embedded programming tutorial available, with clear explanations and working code for every peripheral.

The C/C++ Pico SDK provides a third option for users who need maximum performance. The SDK gives direct access to PIO assembly programming, DMA channels, and interrupt handlers that MicroPython abstracts away. For production firmware that must be reliable and efficient, C/C++ compiles to a binary that boots in milliseconds and uses a fraction of the SRAM. The Arduino-pico core by Earle Philhower bridges the gap, letting Arduino IDE users program the Pico W with familiar setup() and loop() syntax while still accessing PIO and WiFi.

WiFi Projects on a $6 Board

The Pico W's CYW43439 radio provides 802.11 b/g/n WiFi and BLE 5.2 on a board that costs roughly six dollars. For that price, you get a capable wireless microcontroller that handles the most common IoT project archetypes: hosting a local web server for sensor dashboards, publishing MQTT telemetry to Home Assistant or AWS IoT, running a MicroPython-based REST API, and acting as a Bluetooth HID keyboard or mouse. The CYW43439 is a Broadcom/Infineon combo chip that handles both WiFi and BLE, freeing the RP2040's dual cores entirely for application logic.

Power consumption with WiFi active sits around 40mA average during periodic transmissions, spiking to roughly 200mA during TX bursts. In deep sleep with the WiFi radio off, the Pico W draws approximately 1.3mA — usable for USB-powered projects but impractical for coin-cell battery deployments. By contrast, the ESP32-C3 achieves 5uA in deep sleep, a 260x advantage that translates to years of battery life versus weeks. If your project lives on a desk, plugged into a USB charger or power bank, the Pico W's sleep current is irrelevant. If it lives outdoors on a battery, the ESP32-C3 is the only rational choice.

The comparison to the ESP32-C3 at a similar price point is instructive. The ESP32-C3 offers more SRAM (400KB vs 264KB), more flash (4MB vs 2MB), BLE 5.0 with better range, and a vastly more power-efficient sleep mode. The Pico W counters with PIO state machines (no equivalent on any ESP32), superior MicroPython documentation from Raspberry Pi, deterministic timing for custom protocols, and the broader Raspberry Pi ecosystem including official tutorials, forums, and the Pico SDK. The Pico W wins when your project needs PIO for driving WS2812 LEDs, generating VGA signals, or implementing custom serial protocols — tasks where cycle-accurate, CPU-independent timing is non-negotiable. It also wins when you value documentation quality and beginner-friendliness over raw specs.

Pico W vs ESP32-C3: The Budget Showdown

Both cost around $6-7 and offer WiFi with dual cores (the ESP32-C3 is single-core RISC-V, but the price comparison holds). The ESP32-C3 wins on power efficiency (5uA vs 1.3mA deep sleep — a 260x difference), SRAM (400KB vs 264KB), flash (4MB vs 2MB), and mature BLE capability. The Pico W wins on PIO state machines, MicroPython documentation quality, and the Raspberry Pi community's beginner-friendliness.

For battery projects, the ESP32-C3 is the clear winner. The 1.3mA deep sleep on the Pico W is not a sleep mode in any practical sense — it drains a standard 2000mAh lithium battery in about 64 days even while doing nothing. The ESP32-C3 at 5uA can last over a year on the same battery. If your project plugs into USB power permanently (a desk weather display, a smart home sensor hub, a WiFi-controlled LED installation), the Pico W's higher sleep current is irrelevant.

For general WiFi IoT, both are capable — choose based on which ecosystem you prefer. The Raspberry Pi Foundation's documentation, community forums, and tutorial quality are unmatched. Espressif's ESP-IDF framework is more powerful but has a steeper learning curve. Projects like WiFi thermometers, MQTT sensor nodes, web-controlled relays, and simple REST API servers work equally well on either platform. The Pico W's real edge is when you need PIO for non-standard hardware protocols, and the ESP32-C3's real edge is when battery life or BLE peripheral mode matters.

Common Gotchas

The Pico W has NO analog inputs with WiFi active by default — the ADC and WiFi share the same internal bus, causing noise on analog readings when WiFi is transmitting. If your project needs both WiFi and accurate analog sensor readings, you need to pause WiFi during ADC reads or use an external I2C ADC like the ADS1115.

MicroPython's WiFi library (network module) handles reconnection poorly. If the WiFi connection drops, the default behavior is to silently fail rather than auto-reconnect. You need to implement your own reconnection logic in a background task or watchdog timer.

The RP2040 has NO EEPROM and NO built-in filesystem on the 2MB flash. To store persistent data (WiFi credentials, calibration values, sensor logs), you need to partition the flash and use littlefs or write raw bytes — this is not as simple as Arduino's EEPROM.write(). MicroPython handles this transparently with its built-in filesystem, but C/C++ SDK users need to set it up manually.

The Pico W's onboard temperature sensor reads the RP2040 die temperature, not ambient temperature. It consistently reads 5-15°C higher than room temperature due to chip self-heating. Don't use it for environmental monitoring — add an external sensor (BME280, DHT22) for actual temperature readings.

Full Specifications

Who Should Buy This

Frequently Asked Questions

Related Products

• Raspberry Pi Pico 2 W
• ESP32-C3-DevKitM-1
• Raspberry Pi Zero 2 W