Recommended Free Tools
You do not need a Raspberry Pi computer to set up a Raspberry Pi Pico 2. A regular computer with a USB port and a data-capable USB cable is enough to install MicroPython and open the board’s Python prompt. The quickest beginner route is to load the Pico 2’s UF2 firmware file in BOOTSEL mode, then connect to the board over USB serial.
This guide walks through that setup, explains how to tell the Pico 2 firmware apart from Pico 2 W firmware, and outlines the alternative C/C++ development path. A Raspberry Pi Debug Probe or second Pico is for later debugging—not a prerequisite for getting started.
As an Amazon Associate I earn from qualifying purchases.
What you need—and what you do not
For the basic MicroPython setup, you need a Pico 2, a computer, and a USB cable that both fits the board and carries data. Your computer can be a Windows, macOS, or Linux machine; the essential point is that it can connect to the board over USB, copy a file to a mounted drive, and run a serial terminal or IDE.
You do not need another Raspberry Pi board or computer. Raspberry Pi’s Pico setup instructions explicitly allow connecting the board to a Raspberry Pi or another computer over USB. The firmware transfer uses a file-copy step rather than a special Raspberry Pi-only feature.
#1 Best Overall
- The Raspberry Pi Pico is a beginner-friendly microcontroller board that uses MicroPython to give you a taste of the Internet of Things and microcontrollers. The RP2040 is a well-designed microprocessor that can be utilized in almost any Internet of Things project. It has enough power to complete the task quickly.
- 【Raspberry Pi RP2040 Microcontroller】Raspberry Pi Pico features Dual-core ARM Cortex M0+ processor, flexible clock running up to 133 MHz. With 264KB of SRAM, and 2MB of on-board Flash memory.Supports up to 16 MB of off chip flash memory via a dedicated QSPI bus
- 【Multiple Software Support】Pico has rich and complete software support, it comes with a complete Rasberry Pi official C/C++ SDK, Micropython SDK.The programming and burning of Pico need to be carried out on the computer. Supported operating systems and computers include:Raspberry Pie with Raspberry Pi OS,Other platforms equipped with Debian based Linux system Computer with MacOS, Computers with Windows, etc.
- 【Rich Hardware Interface】Raspberry Pi Pico has 30 GPIO pins, 4 pins for analog signal input and 26 × multi-function GPIO pins, 2 × SPI, 2 × I2C, 2 × UART, 3 × 12-bit ADC, 16 × controllable PWM channels.USB 1.1 supported by host and device, The installation mode can be flexibly selected by users to facilitate welding with other development boards.
- 【Build Project in Tiny Size】Only 2.1cm*5.1cm ( as small as your thumb). Pico has been designed to use either soldered 0.1" pin-headers or can be used as a surface-mountable 'module'.
- Pico 2: the microcontroller board you want to program.
- USB data cable: check that the connector matches your board and that the cable supports data, not just charging.
- Computer: needed to download firmware, copy it to the board, and access a USB serial connection.
- MicroPython UF2: the firmware file for the exact Pico 2 model you own.
Raspberry Pi’s C/C++ getting-started guide lists a Pico-series device, a micro USB cable, and a computer among its requirements. Still, check the connector on your particular board and cable instead of assuming that every cable with a USB plug will fit. A charge-only cable may power the board without allowing the file transfer or serial connection you need.
Quick preflight checklist
Before downloading anything, identify the label printed on the board and check the cable ends. Put the board on a nonconductive surface, have the BOOTSEL button accessible, and close any serial program that might already be trying to claim the USB device. Keep the downloaded UF2 in an easy-to-find folder. These small checks make it easier to tell whether a problem is caused by the board, the cable, the selected firmware, or the terminal program.
The Pico 2 is built around the RP2350 microcontroller. Raspberry Pi’s current Pico-series documentation lists dual Cortex-M33 or Hazard3 processors running at up to 150 MHz, 520 KB of SRAM, and 4 MB of onboard flash. Those specifications describe the board; they do not change the basic steps for installing MicroPython.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choose the right Pico 2 firmware
Before downloading firmware, identify which board you have. Raspberry Pi publishes separate MicroPython UF2 downloads for Pico, Pico W, Pico 2, and Pico 2 W. Select the entry for your exact model: a standard Pico 2 and a Pico 2 W are different board variants, and their wireless capabilities differ.
Use Raspberry Pi’s official MicroPython documentation and select the Pico 2 UF2 for a standard Pico 2. If the board is labeled Pico 2 W, select the Pico 2 W file instead. Do not choose a file merely because its name contains “Pico”; the original Pico, Pico W, Pico 2, and Pico 2 W are distinct options on the download page.
A UF2 is the firmware file you copy to the board while it is in BOOTSEL mode. For this first-use workflow, you do not need to install a compiler or build the MicroPython firmware yourself. Download the board-specific file to your computer and leave it somewhere easy to find, such as the Downloads folder.
Firmware selection is the most important model-specific step. The board will not become a wireless board simply because a W image was selected, and a standard Pico 2 should not be treated as interchangeable with Pico 2 W. If you are unsure, read the model marking on the PCB and compare it with the names on Raspberry Pi’s download page before copying anything.
Rank #2
- RPi Pico 2 W Microcontroller Board (pre-soldered header (color-coded)), Based on Official RP2350 Chip, Dual-core & Dual-architecture Design. Upgraded hardware from Pico 2 with wireless communication, onboard antenna, features 2.4GHz 802.11n WIFI and Bluetooth 5.2.
- Adopts unique dual-core and dual-architecture design: dual-core Arm Cortex-M33 processor and dual-core Hazard3 RISC-V processor, flexible clock running up to 150 MHz.
- Onboard Infineon CYW43439 wireless chip, supports WIFI 4 wireless and Bluetooth 5.2.
- 520KB of SRAM, and 4MB of on-board Flash memory.
- Castellated module allows soldering direct to carrier boards. USB 1.1 with device and host support. Low-power sleep and dormant modes. Drag-and-drop programming using mass storage over USB.
Install MicroPython in BOOTSEL mode
- Disconnect the Pico 2 from USB. Start with the board unplugged so you can hold its BOOTSEL button as you connect it.
- Hold BOOTSEL while plugging in the board. Keep the button pressed as you connect the Pico 2 to the computer with the USB data cable.
- Wait for the board’s storage volume. Release BOOTSEL when a mass-storage volume appears on the computer. Raspberry Pi identifies the Pico 2 volume as
RP2350; the original Pico uses the nameRPI-RP2. - Copy the correct UF2 to the volume. Drag or copy the Pico 2 MicroPython UF2 you downloaded onto the mounted
RP2350volume. Do not copy the Pico 2 W file to a standard Pico 2, or vice versa. - Let the board restart. The storage volume disappears as the Pico 2 reboots. That is the expected transition after the UF2 has been copied; you do not need to keep the board in BOOTSEL mode for normal MicroPython use.
- Open a USB serial connection. Use an IDE such as Thonny or a suitable serial terminal to connect to the Pico 2 over USB serial. Raspberry Pi’s MicroPython documentation includes instructions for accessing the board through both Thonny and the command line.
The key distinction is that BOOTSEL is for loading firmware, while the REPL is where you interact with a running MicroPython installation. The board should leave the mass-storage mode after the UF2 copy and then be available for serial communication. To check that the REPL is responding, enter a simple Python expression such as 1 + 1 in the connected prompt and confirm that it returns 2.
What the computer should show at each stage
There are two deliberately different USB states. While BOOTSEL is held during connection, the computer sees a removable mass-storage volume named RP2350. After the UF2 is accepted, that volume disappears because the board reboots into MicroPython. In the normal running state, your IDE or terminal sees a USB serial interface instead. Looking for the wrong state is a common source of confusion: do not wait for the storage drive to remain mounted after installation.
Copy the file rather than opening it as a document or renaming it. The UF2 extension tells the bootloader what to load. If the copy finishes and the drive vanishes, leave the board connected and move to the serial step.
Use the MicroPython REPL
REPL stands for “read-evaluate-print loop”: the board reads a command, runs it, and displays the result. It gives you a quick way to confirm the firmware installation and try Python without first creating a full project. Once the serial connection is open, enter an expression and press Enter. If the board returns a result, you have established a working interactive connection.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteAn IDE can make that first connection easier by providing a serial connection interface and a place to type Python. Thonny is one option named in Raspberry Pi’s MicroPython instructions. A serial terminal is another route, provided it can open the USB serial connection exposed by the board. The exact connection steps and labels depend on the application and computer, so follow the instructions for the tool you choose rather than assuming every IDE uses the same menus.
If you want to experiment interactively, the REPL is useful for small expressions and short checks. For larger programs, use an editor or IDE to write a script and transfer it to the board through the tool’s supported workflow. Keep firmware installation separate from program development: copying a UF2 installs MicroPython, while your later Python code is what you run on that firmware.
A sensible first session is deliberately small. Connect to the serial interface, run 1 + 1, and then try another harmless expression or a short print statement. If the prompt echoes a result, the USB path, firmware, and terminal are all working together. Only after that should you move on to saving a script or following a hardware tutorial.
Rank #3
- Latest Version: Higher core clock speed, double memory, more powerful Arm cores, optional RISC-V cores (compared to the 1 series) (This W version has onboard wireless LAN and Bluetooth)
- Switchable Cores: Allows users to choose between dual industry-standard Arm Cortex-M33 cores and dual open-hardware Hazard3 cores
- Compatibility: Delivers a significant performance boost, while retaining software- and hardware-compatible with the 1 series
- Detailed Tutorial: Provides step-by-step guide with MicroPython, C and Processing (Java) Code (The download link can be found on the product box) (No paper tutorial)
- Example Projects: Each project has schematics, wiring diagrams, complete code and detailed explanations (Need extra items)
If the board does not appear
When the expected drive or serial connection is missing, identify which stage failed before repeating everything. A board that never appears as storage has not reached the visible BOOTSEL transfer stage; a board that disappears after copying the UF2 may simply have rebooted as expected.
- No RP2350 volume appears: disconnect the board and retry while holding BOOTSEL before plugging it in. Release the button only after the mass-storage volume appears.
- The board powers on but the computer does not see it: check that the cable is data-capable, then try another USB port or a different data cable. A charge-only cable can supply power without providing the data connection needed for setup.
- The wrong or no firmware is installed: return to Raspberry Pi’s MicroPython download page and check the model name. Pico 2 and Pico 2 W have separate UF2 downloads.
- The drive vanishes after copying: this is the expected reboot behavior. After the board restarts, look for its USB serial connection in the IDE or terminal instead of expecting the BOOTSEL storage volume to remain mounted.
- The REPL does not respond: confirm that the application is connected to the Pico 2 over USB serial, rather than waiting for the BOOTSEL drive. If necessary, reconnect the board and establish the serial connection again.
Raspberry Pi’s documented workflow establishes the expected storage-volume appearance and reboot behavior; it does not specify a universal troubleshooting sequence for every computer or serial application. The checks above focus on the common points where the documented steps can fail: cable, BOOTSEL timing, model-specific firmware, and the distinction between storage and serial access.
Common setup pitfalls to avoid
Do not press BOOTSEL after the board is already plugged in and expect the same result; start with the board disconnected and hold the button before making the USB connection. Do not infer that a powered LED proves data connectivity, because a charge-only cable can provide power. Do not keep copying firmware repeatedly just because the storage volume disappeared—rebooting is the intended result. Finally, do not troubleshoot a serial problem by looking only at the file manager: once MicroPython is running, the useful connection is the USB serial device in your IDE or terminal.
MicroPython or C/C++?
Both routes work from a regular computer, but they serve different starting points. MicroPython is the shorter path to a running board because Raspberry Pi provides a ready-to-copy UF2 and an interactive REPL. C/C++ is appropriate when you want to develop native embedded projects using the Pico C/C++ SDK and are prepared to set up a development environment and compile code.
| Approach | Best suited to | Main setup | Trade-off |
|---|---|---|---|
| MicroPython UF2 and REPL | First use, learning Python, interactive experiments | Correct Pico 2 UF2, USB connection, and serial terminal or IDE | Quick initial setup; it is not the same workflow as compiling a C/C++ SDK project. |
| C/C++ SDK | Native embedded C/C++ projects and SDK examples | Computer-based development environment and toolchain; UF2 or debugger for deployment | More setup than copying a ready-made MicroPython firmware file. |
Raspberry Pi’s current C/C++ getting-started guide documents the official VS Code extension as well as manual and command-line alternatives; it also describes VSCodium as an alternative editor. The extension manages toolchain dependencies and can create example projects, including a blink project. The guide covers project creation, compilation, and loading the resulting UF2 through BOOTSEL.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFor a basic C/C++ check, Raspberry Pi’s documentation describes loading a blink UF2: enter BOOTSEL mode, copy the UF2 to the mounted volume, and let the board reboot. The onboard LED should blink if the procedure succeeds. The documented LED pin differs by board family: it is GP25 on Pico and Pico 2, while Pico W and Pico 2 W use WL_GPIO0 on the wireless chip.
C/C++ therefore still does not require a Raspberry Pi computer, but it does require more preparation on the host computer. You install or configure the editor and toolchain, create a project, compile it, and then deploy the resulting UF2. For a first successful interaction, MicroPython avoids that build step; move to C/C++ when native code, SDK examples, or a compiled application is the reason you bought the board.
Rank #4
- RPi Pico 2 microcontroller board (with yellow Pre-Soldered Header) is powered by Official RP2350 microcontroller chip, with unique dual-core and dual-architecture design, running up to 150 MHz, embedded 520KB of SRAM and 4MB of on-board Flash memory, as well as 26x multi-function GPIO pins
- Adopts unique dual-core and dual-architecture design: dual-core Arm Cortex-M33 processor and dual-core Hazard3 RISC-V processor, flexible clock running up to 150 MHz
- 520KB of SRAM, and 4MB of on-board Flash memory
- 26 × multi-function GPIO pins. 2 × SPI, 2 × I2C, 2 × UART, 3 × 12-bit ADC, 24 × controllable PWM channels
- Castellated module allows soldering direct to carrier boards. USB 1.1 with device and host support. Low-power sleep and dormant modes.
The official C/C++ getting-started guide’s release history is dated 1 October 2026, and Raspberry Pi’s document portal lists the guide as updated on 2 October 2026. That is relevant if you are following a current toolchain guide: its interface and setup sequence may be newer than older tutorials. For a first successful interaction with a Pico 2, the MicroPython UF2 route avoids the additional build environment required for C/C++.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Do you need a Debug Probe or a second Pico?
No—not for the basic MicroPython install or REPL. The USB UF2 method is enough to load firmware, and USB serial is enough to interact with MicroPython. A Raspberry Pi Debug Probe or a second Pico/Pico 2 is optional equipment for later SWD or UART debugging, when a project calls for those debugging connections.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
It is useful to keep that distinction clear when choosing what to buy: the board, a compatible data cable, and access to a computer cover the basic setup described here. Debugging equipment expands what you can do later, but it does not replace the BOOTSEL firmware-copy workflow or make a Raspberry Pi computer necessary.
Choosing between Pico 2 board variants
The Pico 2 family includes a standard non-wireless board and Pico 2 W, which adds wireless capability. Variants are also available with presoldered headers. Choose the W model when your project needs its onboard wireless features; choose a presoldered-header version if you want the headers ready for breadboard wiring rather than fitting them yourself.
Wireless capability and headers are project and convenience choices. Neither determines whether you need a Raspberry Pi computer: both standard Pico 2 and Pico 2 W can be set up from another computer, using the UF2 for the exact model. Before ordering a particular variant, verify its name and hardware details against Raspberry Pi’s board documentation, especially if your project depends on wireless functions or header installation.
If you already have a Pico 2, you can proceed with the matching MicroPython firmware rather than replacing it with a different variant just to set it up. If you are deciding what to buy, make the variant decision based on the project’s wireless needs and whether you want headers already fitted—not on the mistaken assumption that a Pico board requires a Raspberry Pi host.
What to try after setup
Once the REPL responds, you can use it to confirm that commands reach the board before moving on to a larger program. Start with a basic expression, then follow a MicroPython tutorial or create a small script in your chosen IDE. Raspberry Pi documents a Pico-series Python SDK book as a step-by-step MicroPython learning resource, but you do not need the book to complete the firmware installation.
Best Value
- Compatible models: Raspberry Pi Pico / Pico H / Pico W / Pico WH / Pico 2 / Pico 2 W (NOT included in this kit)
- GPIO status LED: LED on if GPIO outputs / inputs high level, LED off if GPIO outputs / inputs low level
- Independent LED: The status LED is driven by the chip instead of the GPIO so the GPIO will not be affected
- Terminal block and header: Connect to all pins of the main board, 2.54 mm (0.1 inch) pitch
- Pin name: The name of each pin is printed next to it
For readers choosing C/C++ instead, the official getting-started guide provides a path from project creation through compilation and UF2 deployment. Its blink example is a useful first target because it makes successful programming visible through the onboard LED. Keep the model-specific LED pin in mind when adapting examples across standard and wireless board variants.
Frequently asked questions
These answers cover the decisions that most often cause confusion during a first setup.
Frequently Asked Questions
Can I program a Raspberry Pi Pico 2 without a Raspberry Pi computer?
Yes. A Windows, macOS, or Linux computer with USB, a data-capable cable, the correct Pico 2 UF2, and a serial terminal or IDE is sufficient. The Raspberry Pi computer is optional.
What is the difference between BOOTSEL and the REPL?
BOOTSEL is the startup mode used to expose the RP2350 as a removable drive and receive a UF2 file. The REPL is the USB serial Python prompt available after MicroPython has rebooted.
Why did the RP2350 drive disappear?
The UF2 copy caused the board to reboot, so the BOOTSEL mass-storage volume closed. That is expected. Look for the board’s USB serial connection in Thonny or your terminal instead.
Can I use Pico 2 W firmware on a standard Pico 2?
No. Raspberry Pi provides separate UF2 downloads for Pico 2 and Pico 2 W. Select the file matching the model printed on your board.
Do I need a Debug Probe or a second Pico to install MicroPython?
No. Those are optional tools for later SWD or UART debugging. Basic UF2 installation and REPL access use the board’s USB connection.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Which is easier for a first project, MicroPython or C/C++?
MicroPython is usually the shorter first step because you copy a ready-made UF2 and use the REPL. C/C++ is the better fit for native SDK projects, but it requires a host development environment, toolchain, compilation, and UF2 deployment.
Does Pico 2 have the same LED pin as Pico 2 W?
The official C/C++ documentation lists GP25 for Pico and Pico 2. Pico W and Pico 2 W use WL_GPIO0 on the wireless chip, so examples may need a board-specific LED definition.
The Bottom Line
Bottom line: a Raspberry Pi computer is not required. Use a USB data cable and an ordinary computer to put the Pico 2 into BOOTSEL mode, copy the matching MicroPython UF2 to the RP2350 volume, wait for the reboot, and connect through USB serial. Choose Pico 2 W only for wireless projects, treat headers as a convenience option, and add a Debug Probe or C/C++ toolchain only when your project needs them.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
