Start here / MicroPython Studio v2.6.0

From USB cable to running Python.

Install the VS Code extension, connect a supported MicroPython board, open its REPL and run a small script. Debugging is an optional next step and needs board-specific firmware.

For Windows, macOS and Linux with VS Code. The VSIX is the public approved release; commits merged to main do not automatically appear in the Marketplace.

Your first working REPL

Start with the normal USB serial connection. It is independent of optional Wi-Fi/WebREPL and of the frozen debugger.

01

Install the extension

Install MicroPython Studio in VS Code from the Marketplace. Alternatively, open the Command Palette and choose Extensions: Install from VSIX… after downloading the verified stable file above.

02

Connect your board over USB

Use a USB data cable, not a charging-only lead. Check that the serial device appears in your operating system. Start with the board's own supported MicroPython firmware; do not flash a debugger image until you have confirmed the exact model.

03

Prepare the workspace

In VS Code, press Ctrl + Shift + P (or the Command Palette shortcut on your OS) and run MicroPython: Setup Development Environment. Then choose MicroPython: Create New Project or open an existing project.

04

Open the shell and verify the interpreter

Choose the board's USB REPL serial port and run MicroPython: Open Device Shell. You should see a >>> prompt. Try this:

import sys
print(sys.platform)
print("MicroPython Studio connected")
05

Run a script

Save a file such as hello.py and use MicroPython: Run Script on Device. When that works, try MicroPython: Refresh Device Files to browse the board.

from machine import Pin
import time

print("Hello from MicroPython Studio")
for count in range(3):
    print("Loop", count)
    time.sleep(0.5)
Milestone: If the REPL responds and the script prints three loop messages, your normal USB workflow is ready. You do not need special debugger firmware for this first test.

Ready for real-device debugging?

Source breakpoints, stepping, locals, call stacks and runtime tracing need a compatible board-specific debugger image and a separate debugger transport. Do not select the same serial COM port for both REPL and debugger.

01

Confirm your board

Check the exact label: Pico W, Pico 2 W, ESP32-S3 and ESP32-C3 are not interchangeable.

02

Read firmware status

Choose a hardware-tested release only for its matching board. Preview firmware requires an explicit test plan.

03

Connect both ports

Use the board-specific REPL and debugger ports. Start with a basic breakpoint before testing RTA.