← PS-1 · FROM CIRCUIT TO SPEC

Pins, rails, and nets

YOU WILL BE ABLE TO
  • Split the Pico's 40 pins into assignable GPIOs and everything else.
  • Explain rails as nets that exist on every board before any peripheral does.
  • Read V4, V5 and V8 rejections and say which rule each one enforces.
  • Trace a net by name through a spec and list its members.

Forty pins leave the Pico socket, but you may only ASSIGN some of them. Ground pins, 3V3, VBUS, VSYS — the power plumbing — are not yours to hand to a peripheral; the generator wires power by construction. Try, and the validator is blunt: a made-up name earns "is not a Pico pin name", and a real power pin earns "is a GND/3V3/power pin, not an assignable GPIO". One detail catches people: the ground pins are named GND1 through GND8, so a bare GND is, to the validator, a made-up name.

Every GPIO may serve exactly ONE peripheral. The pin is a physical piece of silicon; two components soldered to it would fight. The validator tracks every assignment across the whole spec and reports a collision with both names: "SW1: GPIO GP15 already used by D1 — no pin may serve two peripherals". Fixing a conflict sometimes reveals a second one — the validator reports what it can prove against components that exist.

Three pins are special: GP26, GP27 and GP28 carry the analog-to-digital converter. A part that MEASURES a voltage — the light sensor's divider, the pot's wiper — must land on one of them. The message has the same shape for every analog part — "RV1: potentiometer needs an analog pin — GP16 is not an ADC pin (GP26/GP27/GP28)" — naming the part, the pin you offered, and the three that would work. The digital pins cannot read a divider; they see only high and low.

Behind the pins live NETS: named electrical islands. The two you get for free on every board are the rails, 3V3 and GND. When the generator wires an LED's cathode "to ground" it is joining the GND net, and every other ground connection on the board is the same island of copper. This is why the empty board of Lesson 1 already had two traces — the rails exist before any peripheral does.

WORKED EXAMPLE

Net tracing on paper

  1. A spec has an LED on GP15 and a button on GP14 (internal pull-up, active low). List every net and its members.
  2. GP15 net: the Pico's GP15 pad and pin 1 of the generated series resistor.
  3. An unnamed internal net: the resistor's pin 2 and the LED's anode.
  4. GND net: the LED's cathode, one side of the button, and the rail itself.
  5. GP14 net: the Pico's GP14 pad and the other side of the button.
  6. 3V3 net: the rail only — no peripheral on this board draws from it.
  7. Five nets; the two rails exist regardless. Generate it and the engine reports 4 components and 7 traces: 1 + 2 + 1, and 2 + 3 + 2.
Five nets: GP15, the resistor-to-anode net, GND, GP14, and 3V3.

PRACTICE

Q1

Quote the exact message for "pin": "GP99" on an LED with refdes D1.

Q2

Quote it for "pin": "3V3" on the same LED.

Q3

A potentiometer on GP16: which check fires and what are the legal pins?

Q4

An LED (D1) on GP15 and a slide_switch (SW1) also on GP15: what happens, exactly?

Pins, rails, and nets · PS-1 · iLearnSTEM Electronics