Loading the figure…
Stopped · Your code isn't running yet. Until you press Run, the board runs the program already on it.
Nothing printed yet. Press Run.
Not checked yet
Run your code to check it. The checks replay a fixed script on a virtual clock, so the same code always gets the same result.
Each fault really happens in the simulation. Trigger one, watch the figure, then read why.
Play the world: press, slide and turn the parts while the code runs.
Change a value here or click a chip in the code.
Read a button with the internal pull-up and the RP2040's own temperature sensor, and print both every second.
| Pin | Connects to | What it does |
|---|---|---|
GP14 | Button, other side to GND | Digital input with pull-up |
GP15 | 330 Ω resistor and LED | Digital output |
GND | Button and LED cathode | Return |
Sensors and actuators this board drives, with the real connections.
A 5 mm LED from GP15 through a 330 Ω resistor to GND: (3.3 - 2.0) / 330 ≈ 4 mA for a red LED, within the pin's default 4 mA drive.
| Part pin | Board pin |
|---|---|
| A | GP15Wire colour orange |
| K | GNDWire colour black |
Never leave out the resistor: the pin would try to drive far more than 12 mA.
A 6 x 6 mm button from GP14 to GND with Pin.PULL_UP: it reads 0 while pressed. Straddle the breadboard's centre gap.
| Part pin | Board pin |
|---|---|
| 1 | GP14Wire colour yellow |
| 3 | GNDWire colour black |
On early Pico 2 boards (RP2350 A2) do not rely on the internal pull-down: erratum E9 lets the pin float high.