Source breakpoints
Pause a MicroPython script at a selected source location.
Debug MicroPython on real hardware, inside VS Code
Set a breakpoint on a Raspberry Pi Pico 2 W, pause execution, inspect Python variables and call stacks, step through code, and explore recorded function runtime traces.
This is an on-device MicroPython debugger that works with compatible debugger-enabled firmware. No external JTAG hardware is needed for the supported software-debugging workflow. Normal project work also includes Serial REPL, file upload/download and firmware tools.
Live debugger features
Step and continue
Control script execution while tracing a bug.
Variables and stack
Inspect locals, globals and active call frames.
Runtime trace analysis
See function events and observed elapsed-time shares. This is not a CPU utilisation measurement.
Which boards are supported?
Pico 2 W: a working debugger workflow has been demonstrated on actual hardware. Pico/Pico W/Pico 2: new frozen debugger candidates have passed CI but require board-specific physical acceptance. ESP32-S3: physical Serial REPL plus separate native USB debugger has passed breakpoint and short-RTA tests; full stability checks are pending. ESP32-C3: transport feasibility stage; no debugger image published.
Check the firmware before flashing. The debugger requires a board-matched image. Some existing published Pico firmware uses a legacy setup path; the newer frozen-image workflow is still undergoing acceptance. Download test candidates only with a recovery plan, and never flash an ESP32-S3 image onto an ESP32-C3.
Getting started
- Install MicroPython Studio from the VS Code Marketplace.
- Connect a supported board and verify its MicroPython REPL and normal file upload.
- Follow the instructions for your board's exact debugger-enabled firmware.
- Open your script and start debugging on the separate debugger transport, where the firmware supports one.
- Set a breakpoint, inspect the stack and variables, and try runtime tracing.
Frequently asked questions
Does MicroPython have breakpoints in VS Code?
MicroPython Studio provides source breakpoints and stepping with the matching debugger-enabled firmware on hardware-validated targets such as Pico 2 W. An ordinary stock MicroPython image does not automatically include these features.
Does it need a JTAG probe?
For the supported software-level debugger features, no separate JTAG probe is needed. Target-specific USB transport and firmware requirements still apply.
Does RTA show CPU load?
No. Observed VM time percentages describe shares of recorded execution-segment elapsed time. Sleeping and waiting can affect those measurements.