breadboard
blog

BlogEngineering

Engineering · 08 Nov 2026

New Pico sessions run on our own RP2040 core

Why we moved Pico and Pico W off the JavaScript emulator we started with, and how the new core skips idle time without changing what the firmware sees.

The Breadboard team2 min read

Raspberry Pi Pico board
Raspberry Pi Pico board
In this post 4 sectionsOne engine for every boardSkipping time, exactlyWhat we measuredYour saved work

Every Pico you place on the bench runs real firmware, built for the real chip. Until this week, a JavaScript emulator ran that firmware. Now new Pico and Pico W sessions run on an RP2040 core we wrote ourselves.

That emulator is rp2040js, the open-source RP2040 emulator from Wokwi, and it got us a long way. It boots MicroPython, CircuitPython and the pico-sdk, and it taught us a lot about the chip. We thank the Wokwi team for it. But it lived outside the engine that runs our other boards, so work on that engine never reached the Pico.

One engine for every board

With this switch, every microcontroller on the bench runs on one Rust core of our own: the Arduino family, the ESP32 family, the STM32 family and the Raspberry Pi Pico family.

That matters for more than speed. Improvements to that engine now reach the Pico too, and a Pico on a mixed bench runs in the same engine as the boards beside it.

Skipping time, exactly

Most firmware spends most of its time waiting. A blink loop sleeps for half a second. MicroPython waits at its prompt for you to type. On real silicon the CPU keeps running through those waits, and an emulator that runs every one of those instructions spends your laptop's time on nothing.

main.py · Python
from machine import Pin
import time

led = Pin(25, Pin.OUT)      # the Pico's on-board LED
while True:
    led.toggle()
    time.sleep_ms(500)      # half a second of waiting

The new core recognises when firmware is only waiting, and moves straight on to the next thing that matters.

The firmware cannot tell. That is the rule every shortcut has to pass.

Registers, timers and pins end up exactly where they would be if every instruction had run. We check that on every benchmark run.

Pico blink · Raspberry Pi PicoRead-only bench
Pico blink · Raspberry Pi Pico, on the Breadboard bench
Boots the real firmware in this page. Nothing loads until you press Run.On a phone, the bench opens in the workbench.Open in the workbench
Figure 1. The Pico blink example, now on the new core.

What we measured

We ran eight real workloads on both emulators, from two Pico Ws talking over Bluetooth LE to a CircuitPython boot, and timed how long each took to simulate the same firmware work. Each workload ran twelve rounds on one quiet machine.

8 of 8
workloads faster on the new core
12 of 12
rounds faster, in every workload
Up to 9.55×
median speed-up, at the MicroPython prompt. The smallest was 1.35×, on PIO and DMA.
Source: Our RP2040 benchmark, 7 November 2026. Medians of twelve rounds per workload, wall time to simulate the same work.
WorkloadJavaScriptOur coreSpeed-up
MicroPython prompt0.561 s0.059 s9.55×
Rust blink0.217 s0.027 s7.99×
Two Pico Ws over Bluetooth LE11.007 s2.497 s4.41×
CircuitPython boot1.500 s0.461 s3.26×
Pico W Wi-Fi scan2.172 s0.865 s2.51×
C program, USB serial0.120 s0.075 s1.59×
pico-sdk dual-core test0.053 s0.039 s1.36×
PIO and DMA0.034 s0.025 s1.35×

On the bench, a Pico still runs at real time: one simulated second for every second on the clock. The speed-up shows up as headroom. Your laptop does less work to keep the Pico on time, which leaves room for the rest of the circuit.

Your saved work

Saved circuits do not change. A project names the board, not the emulator, so every saved Pico project opens on the new core.

Time-travel recordings made before the switch still play back exactly as they were recorded.

The switch also fixed things the old path lacked. The physical BOOTSEL button now works, you can inspect the PIO state machines, and a watchdog reset now shows a notice that names it.

The Breadboard team · Published 08 Nov 2026

  • RP2040
  • Pico W
  • Emulation

Try it, on the bench

Open the Pico blink example and press Run.

Open the example