Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
No Raspberry Pi computer is required. A regular Windows, macOS, Linux, or other USB-equipped computer can install MicroPython on a Raspberry Pi Pico 2, open its USB serial REPL, and run Python code. The same computer can also build and upload C/C++ programs; the difference is that C/C++ requires a development toolchain, while MicroPython can begin with one board-specific UF2 file.
If you are asking, “Can I program a Raspberry Pi Pico 2 without a Raspberry Pi?”, the answer is yes. The Pico 2 supplies the microcontroller and bootloader; your ordinary computer supplies the download, file copy, terminal, and development tools.
What “without a Raspberry Pi” means
The Pico 2 is a microcontroller board, not a desktop computer. You still need a host computer to download firmware, copy it to the board, and type programs. That host can be a Windows, macOS, Linux, or other computer with USB support; it does not need to be a Raspberry Pi-branded computer.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The first-install process uses the board’s built-in USB bootloader. When the BOOTSEL button is held while the board is connected, the Pico 2 appears as a removable mass-storage volume. Copying a UF2 firmware file to that volume installs the firmware. After the copy completes, the board reboots and the storage volume disappears.
#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'.
This is different from treating the Pico 2 like a USB flash drive for ordinary file storage. The volume exists temporarily so the bootloader can receive firmware. Once the board restarts, you work through USB serial, not by opening the bootloader volume.
What you need
- A Raspberry Pi Pico 2 board.
- A USB cable that fits the board and supports data, not only charging. Raspberry Pi’s Pico-series getting-started requirements specify a micro USB cable; check the connector on the exact board revision and make sure the cable is data-capable.
- A computer with a working USB port.
- An IDE or serial terminal. Thonny is a convenient option for MicroPython, but another program that can connect to USB serial also works.
You do not need a second Raspberry Pi, a Debug Probe, an external programmer, or a separate power supply for the basic UF2 and REPL workflow. A Debug Probe or a second Pico becomes useful later for SWD or UART debugging, not for the initial installation.
The computer needs to be able to download the UF2, show a removable drive when the board enters BOOTSEL mode, and open a USB serial connection after reboot. The board is powered over USB during this procedure, so there is no separate power arrangement to make for the first test.
Recommended Free Tools
Pico 2 hardware in brief
The Pico 2 uses 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’s capabilities; they do not change the computer requirements for installing firmware.
These figures are useful when deciding whether the board suits a project, but they are not prerequisites to learn before setup. You can complete the first MicroPython connection without configuring processor options, memory settings, or a hardware programmer.
Choose the exact board and firmware
Raspberry Pi publishes separate MicroPython UF2 downloads for Pico, Pico W, Pico 2, and Pico 2 W. Select the file whose board name exactly matches the hardware in your hand. A non-wireless Pico 2 must not be flashed with Pico 2 W firmware, and a Pico 2 W should not be treated as a non-wireless Pico 2.
The Pico 2 family also includes versions with presoldered headers. Headers are a physical convenience for breadboards and jumper wires; they are not required for USB programming. Choose the wireless variant only when the project needs its onboard wireless capability. Confirm the exact variant in the board documentation or on the board packaging before downloading firmware or buying accessories.
| Board choice | What changes | What does not change |
|---|---|---|
| Pico 2 | Non-wireless board; standard Pico 2 MicroPython image | USB BOOTSEL installation and serial REPL method |
| Pico 2 W | Wireless capability; use the separate Pico 2 W image | Need for a normal USB-equipped host computer |
| Presoldered-header version | Ready-to-wire physical pins | Firmware transfer procedure |
Do not choose a board because it has headers alone, and do not select wireless firmware simply because it is newer or has more features. The model name on the download must match the model name on the board.
Install MicroPython: the beginner workflow
1. Prepare the board and cable
Disconnect the Pico 2 from USB. Have the downloaded firmware ready on the computer and identify the board’s BOOTSEL button. Use a known-good data cable. Charge-only cables can power a board while preventing both the bootloader volume and the serial connection from appearing.
Remove unnecessary hubs or adapters for the first attempt. A direct connection makes it easier to tell whether a missing volume is caused by the cable, the port, or the board’s button sequence. Leave the computer’s file manager open if you want to see the volume appear immediately.
2. Download the Pico 2 UF2
Open Raspberry Pi’s official MicroPython documentation and choose the download specifically labeled for Pico 2. Do not select the Pico 2 W file unless the board is the wireless model. UF2 is the file format used by the Pico bootloader; it is copied to the board like a file rather than installed through a traditional setup wizard.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Save the file somewhere easy to find, such as the computer’s downloads folder. Before copying it, read the filename and the download page label again. The most common avoidable mistake is using a valid UF2 for a different Pico family member.
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.
3. Enter BOOTSEL mode
- Press and hold the BOOTSEL button on the Pico 2.
- While holding it, connect the board to the computer over USB.
- Release the button when the removable mass-storage volume appears.
For Pico 2, Raspberry Pi identifies this volume as RP2350. The original Pico uses the name RPI-RP2, so seeing the latter can indicate that you connected a different board than expected.
Do not release the button merely because the board has power. Wait for the removable volume to appear. BOOTSEL is a special startup state; connecting the board normally takes it straight to the firmware already installed.
4. Copy the firmware
Open the RP2350 volume in the computer’s file manager and drag or copy the downloaded Pico 2 UF2 file onto it. No special eject command is required for the normal workflow, although waiting for the copy to finish is important. The board automatically reboots after accepting the file. Its removable volume then disappears; that disappearance is the expected transition out of BOOTSEL mode.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not try to open the UF2 and edit it, rename it to a Python file, or copy unrelated files to the volume. The bootloader is looking for a valid firmware image. If the volume closes immediately after a successful copy, that is the normal reboot rather than a failed transfer.
5. Connect to the MicroPython REPL
After the reboot, open Thonny or another USB-serial terminal. Select the Pico 2’s USB serial device when the program asks for an interpreter or port. Raspberry Pi’s MicroPython instructions provide both command-line and Thonny approaches; the essential requirement is a connection to the board’s USB serial interface rather than the temporary RP2350 storage volume.
If the IDE lists several serial devices, unplug other development boards temporarily or identify the new device by disconnecting and reconnecting the Pico 2. Close any second terminal that might already have the port open; two programs cannot reliably use the same serial connection at once.
6. Run a first expression
At the REPL prompt, enter a small expression such as:
print('Pico 2 is ready')If the text is printed back by the board, MicroPython is installed and the interactive connection is working. You can now type statements directly, create a Python file in the IDE, and save it to the board’s flash for later execution.
Start with a short expression before testing a larger script. A successful response proves three separate links at once: the correct firmware was accepted, the board rebooted, and the computer opened the USB serial REPL.
What to do when the board does not appear
No removable volume appears during connection
- Check that the cable carries data and is fully inserted at both ends.
- Try a different USB cable and a different USB port.
- Disconnect the board, hold BOOTSEL before reconnecting, and keep holding it until the volume appears.
- Verify that you are looking for
RP2350, the Pico 2 bootloader volume, rather than expecting the original Pico’sRPI-RP2label.
The official procedure establishes that a correctly connected Pico 2 should present a mass-storage volume in BOOTSEL mode. If repeated cable and port changes do not produce it, remove hubs or adapters from the chain and connect directly to the computer before trying again.
A cable that charges a phone is not automatically a data cable. Test with one known to transfer data. Also make sure the BOOTSEL button is being held before the USB plug is fully connected, rather than pressed after the computer has already started a normal boot.
The volume disappears before you copy the file
If the board leaves BOOTSEL mode unexpectedly, disconnect it and repeat the button-hold sequence. A successful UF2 copy also makes the volume disappear because the board reboots, so distinguish an early disappearance from the normal post-copy reboot.
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)
Check the timing: the expected order is button held, USB connected, RP2350 appears, UF2 copied, then the volume disappears. If the volume disappears at the final step, allow a moment for the USB serial device to re-enumerate before deciding that installation failed.
The UF2 copy finishes but the REPL is missing
Confirm that the UF2 was for Pico 2 or Pico 2 W as appropriate, then reconnect the board normally without pressing BOOTSEL. In Thonny or the terminal, refresh the available serial devices and select the board’s USB serial connection. If the computer still sees nothing, repeat the installation with a verified data cable and the correct board-specific file.
Do not look for the REPL while the board is still mounted as RP2350. That volume is the bootloader interface; the REPL becomes available only after the board has rebooted into MicroPython.
Free tools Windows power users keep installed
One-click scans. No signup required.
The program connects but behaves unexpectedly
Check that the IDE is using the MicroPython interpreter and the Pico 2’s serial port, not a different board or a stale terminal session. Close other programs that may have the serial device open, reconnect the board, and try the short print() expression again before loading a larger script.
If you selected a Pico 2 W image for a non-wireless board, or the reverse, return to the official download page and reinstall the image matching the printed board variant. Firmware selection is a model decision, not a setting to compensate for in the terminal.
Using C and C++ instead
MicroPython is the shortest route to an interactive first program, but the Pico 2 also supports native C and C++ development from a standard computer. Raspberry Pi’s current getting-started guide documents an official Pico extension for Visual Studio Code, along with VSCodium and manual or command-line configurations.
What the C/C++ path adds
- A host development environment and compiler toolchain.
- A project configuration, typically created from an example or template.
- A build step that produces a UF2 file.
- Deployment by copying that compiled UF2 through BOOTSEL, or by using a debugger for an advanced workflow.
The official extension manages toolchain dependencies and can generate example projects such as blink. Manual configuration is possible, but it requires you to install and maintain the compiler and SDK components yourself. This makes C/C++ more involved than copying a ready-made MicroPython UF2.
The normal C/C++ sequence is: install the host tools, create or open a Pico project, configure the target, compile it, locate the generated UF2, enter BOOTSEL, and copy that UF2 to RP2350. The Pico 2 does not need a Raspberry Pi computer for any of those host-side steps.
Use blink as a hardware check
Raspberry Pi provides a C/C++ blink UF2 that supports all Pico variants. Put the board into BOOTSEL mode, copy the blink UF2 to the mounted volume, and allow the board to reboot. A successful installation makes the onboard LED blink.
LED wiring differs by model in the official documentation: Pico and Pico 2 use GP25, while Pico W and Pico 2 W use WL_GPIO0 on the wireless chip. Code written for one LED connection should therefore not be assumed to work unchanged on every variant.
Blink is useful because it tests the complete compiled-firmware path without requiring a sensor, breadboard, or external wiring. If the LED behavior is not what the example expects, first verify the board variant and the corresponding LED definition rather than assuming the USB transfer failed.
MicroPython or C/C++?
| Choice | Best for | Main setup requirement | Trade-off |
|---|---|---|---|
| MicroPython UF2 plus REPL | First use, learning Python, and quick interactive experiments | The correct Pico 2 UF2, USB data connection, and a serial-capable IDE or terminal | Fastest initial setup; it is not the same workflow as compiling an SDK project |
| C/C++ SDK | Native embedded C/C++ projects and SDK examples | A host development environment, compiler/toolchain, and a UF2 or debugger for deployment | More installation and project configuration before the first program runs |
Both approaches ultimately use the Pico bootloader for ordinary UF2 deployment. The practical decision is whether you want an interactive Python environment immediately or the compile-build-debug cycle used by native embedded projects.
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.
MicroPython is a good first choice when the goal is to send commands and see results quickly. C/C++ is the better fit when the project already depends on native SDK examples, a compiled application, or a debugger-led workflow. You can change approaches later by loading the appropriate UF2; choosing MicroPython first does not require owning a Raspberry Pi computer.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When optional debugging hardware is worthwhile
A Raspberry Pi Debug Probe or a second Pico/Pico 2 can provide SWD or UART debugging. These tools can help inspect a running C/C++ program, set breakpoints, or observe serial signals, but they are not prerequisites for installing MicroPython, opening the REPL, or loading a compiled UF2 through BOOTSEL.
For a first project, spend effort verifying the board variant, firmware file, and USB data path before adding debugging hardware. Introduce a probe when the project’s debugging needs justify the additional wiring and configuration.
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 minuteDo not buy a probe simply because the board is new or because BOOTSEL is unfamiliar. The built-in bootloader already handles the basic firmware transfer. Debug hardware addresses a later SWD or UART problem, not a missing first installation step.
How current these instructions are
The official C/C++ getting-started guide cited for this workflow carries a release date of 1 October 2026, and Raspberry Pi’s document portal lists an update of 2 October 2026. The MicroPython and board documentation used for the procedure were accessed on 13 October 2026. Interface labels can change, so use the board name shown by the current Raspberry Pi documentation when selecting downloads.
After the first successful connection
Keep a copy of the known-good Pico 2 UF2 and note which serial device your computer assigns to the board. You can then develop in small increments: test expressions in the REPL, save a short script, disconnect and reconnect normally, and only return to BOOTSEL when replacing the firmware or loading a compiled UF2. The Pico-series Python SDK book is available as an optional step-by-step learning resource, but it is not needed for the installation described here.
When you reconnect for normal programming, do not hold BOOTSEL unless you intend to replace the firmware. A normal connection starts the installed MicroPython image, while holding BOOTSEL deliberately selects the firmware-transfer path. Keeping those two startup modes distinct prevents many first-time mistakes.
Frequently asked questions
Can I program a Raspberry Pi Pico 2 without a Raspberry Pi computer?
Yes. A standard computer with USB can install the board-specific MicroPython UF2, open the USB serial REPL, and run Python. The same computer can build and upload C/C++ projects.
Do I need a Raspberry Pi Debug Probe for setup?
No. The Debug Probe is optional equipment for SWD or UART debugging. Basic MicroPython installation and ordinary UF2 deployment use the Pico 2’s BOOTSEL button and USB connection.
Which firmware should I download for a Pico 2 W?
Use the separate MicroPython UF2 labeled Pico 2 W. Raspberry Pi provides distinct downloads for Pico 2 and Pico 2 W, so do not substitute one for the other.
Why does the drive say RP2350?
RP2350 is the expected Pico 2 bootloader volume. The original Pico uses RPI-RP2; that different label can indicate a different board model.
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 minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Can a charge-only cable install MicroPython?
No. The cable must carry USB data as well as power. A charge-only cable can make the board light up while preventing the bootloader volume and serial connection from appearing.
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
Do presoldered headers affect firmware installation?
No. Headers make breadboard wiring easier but do not change the USB UF2 procedure. They are a physical convenience, not a programming requirement.
Is C/C++ possible without a Raspberry Pi?
Yes. Raspberry Pi documents a Pico extension for Visual Studio Code, VSCodium alternatives, and manual or command-line setups for a normal host computer. You compile a project into a UF2 and copy it through BOOTSEL.
What should I try first if the REPL is absent?
Reconnect normally without BOOTSEL, refresh the serial-device list, select the MicroPython interpreter and Pico 2 port, and close any other program using that port. If necessary, reinstall the matching UF2 with a known-good data cable.
Frequently Asked Questions
Can I program a Raspberry Pi Pico 2 without a Raspberry Pi computer?
Yes. A standard USB-equipped computer is enough for MicroPython or C/C++ development.
What is the minimum hardware for the first setup?
A Pico 2, a compatible USB data cable, and a computer with USB. Thonny or another USB-serial terminal is needed to use the MicroPython REPL.
Do I need a Debug Probe or second Pico?
No. Those are optional for later SWD or UART debugging, not for BOOTSEL firmware installation.
Why is the RP2350 drive not visible?
Check the data cable, try another USB port, hold BOOTSEL before connecting, and connect directly without a hub. Pico 2 should appear as RP2350 in BOOTSEL mode.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Which UF2 file belongs on my board?
Use the exact model-specific download: Pico 2 for the non-wireless board and Pico 2 W for the wireless board. Raspberry Pi lists separate files.
Why does the drive disappear after copying the UF2?
That is normally expected. The board accepts the firmware and reboots, leaving BOOTSEL mode; the USB serial interface should then become available.
Can I use the same computer for C/C++?
Yes. Install the official Pico extension or configure the toolchain manually, build a project into a UF2, and copy it through BOOTSEL.
The Bottom Line
You can set up and program a Raspberry Pi Pico 2 with an ordinary computer. Use a data-capable USB cable, hold BOOTSEL while connecting, copy the correctly matched Pico 2 UF2 to the RP2350 volume, then use USB serial for the MicroPython REPL. Choose the C/C++ toolchain only when you need native SDK development; neither path requires a Raspberry Pi computer.
Free tools Windows power users keep installed
One-click scans. No signup required.
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.
