PHASE 08BRINGUP
Power the board for the first time — carefully, rails first — and prove each one before you trust the next.
Bring-up is where the board either comes alive or teaches you something. Do it in order — no shorts, then the rail, then the chip — and let your multimeter, not optimism, tell you each step is safe.
The safest power-on is the one you've already de-risked with a meter.
With no power applied, run a check between VBUS and GND — it must NOT beep — and confirm the grounds are tied together. A solder bridge found with a meter costs you a minute; the same bridge found by plugging in costs you the board.
Why check VBUS-to-GND continuity before plugging in USB? A short there turns the first power-up into the last — the meter finds it while it's still harmless.
Trust the 3.3 V rail only after you've measured it.
Power the board over USB and measure the rail at the test points: 3.3 V at TP1 (red), ground at TP2 (black). Confirm it reads 3.3 V — give or take a little — before assuming anything downstream is alive. The red power LED (LED1) should light. Glance at the input current too: a healthy idle board draws modestly, while a sudden spike means a fault you should chase before going any further.
| Ref | Part | Role |
|---|---|---|
| TP1 | Red test point | Probe the 3.3 V rail here |
| TP2 | Black test point | Ground reference for your meter |
The board powers but TP1 reads 4.9 V, not 3.3. What failed? Likely the LDO (U2) — its output is sitting at the input voltage, so it's mis-soldered, mis-oriented, or its enable isn't asserted. Stop before you connect 3.3 V logic to 5 V.
▸Deep dive· Reading the rail voltage like a diagnostician
The number on the meter at TP1 tells you where the fault is. A healthy ~3.3 V means the is regulating — move on. 4.9 V (basically the USB input) means the regulator isn't regulating at all and is passing its input straight through: it's mis-oriented, mis-soldered, or its enable pin isn't pulled high — and you must NOT connect 3.3 V parts to that rail. 0 V means either no power is reaching it (a broken joint upstream) or something is dragging it down (a short). Around 3.3 V but LED1 stays dark points at the LED or its resistor, not the rail. The regulator also needs its input to sit comfortably above 3.3 V plus its , so a sagging USB cable can starve it — measure the input too whenever the output looks low.
Now make the S3 talk.
Plug USB into a host — the native-USB S3 should show up (enumerate) as a device. To load firmware, use the : hold BOOT (GPIO0 low), tap EN to reset, then release BOOT to drop into USB download mode and flash. A blink on LED2 afterward proves the GPIO, your toolchain, and the whole chain end to end.
The board powers fine but won't enter flash mode. The button move? Hold BOOT (GPIO0 low), pulse EN (reset), then release BOOT — sampling GPIO0 low at reset selects USB download.
▸Deep dive· Strapping pins: why holding BOOT picks download mode
A few pins do double duty: at the instant the chip comes out of reset it samples its to decide how to start, and then they go back to being ordinary . On the ESP32-S3, GPIO0 is the one that matters here — sampled HIGH (its resting default) the chip boots your firmware; sampled LOW it drops into USB download mode, ready to be flashed. That's the entire button dance: hold BOOT to force GPIO0 low, tap EN to reset the chip so it re-reads the strap, then release BOOT. Because the level is only read at that one instant, you can let go right after. It's also why you don't hang a heavy load on GPIO0 — pull it the wrong way at power-up and the board boots into the wrong mode all on its own.
Quick check — bring-up
Capture the bring-up measurements and log, then mark each board BROUGHT_UP (or QUARANTINED). That closes the build.