ToolSphere
All perfboard layouts

ESP32 LEDs and Button Perfboard Layout

A 38-pin ESP32-DevKitC V4 uses an external 3.3 V regulator, LEDs on GPIO25/26 and a button on GPIO27. Schematic-verified, not prototype-tested.

ESP32 + 3.3 V regulator, LEDs and button perfboard layoutA1 ESP32-DevKitC V4U1 LD1117V33J1 5V INPUTC1 10uC2 10uC3 100nC4 100nR1 1kD1 RED LEDR2 1kD2 RED LEDJ2 BUTTONR3 10k
Open this layout in the simulator Connection check: no shorts, 8 named nets

Red wires carry power, white is ground, yellow and blue are signals. Every hole is an isolated pad; connections are the wires shown. In the simulator you can move parts, add your own and re-run the check.

Parts list

As an Amazon Associate, ToolSphere earns from qualifying purchases.

How it works

This footprint is specifically the Espressif ESP32-DevKitC V4, with its antenna end toward the top of the drawing. Check the actual header labels and spacing before fitting sockets. A 30-pin clone, ESP32-C3 or ESP32-S3 is not interchangeable. Leave the antenna area clear of wiring, metal and copper; verify radio performance after assembly.

J1 accepts regulated 5 V. U1 is an ST LD1117V33 in TO-220, not a 7805 or an arbitrary 1117-family substitute. Its pin order is GND, OUT, IN; the layout overrides the generic regulator labels accordingly. C1 bypasses the input and C2 is the output stability capacitor. Use the capacitor type and effective capacitance required by the ST LD1117 datasheet, including its minimum 10 µF output requirement. The two 100 nF capacitors add local bypassing; they do not replace C2.

The regulator output goes directly to A1's 3V3 pin. Never connect USB or feed the DevKit's 5V pin while this external supply is connected. Espressif's DevKitC power guidance requires a single power option. For USB programming, remove the DevKit from its sockets first so USB cannot backfeed the external regulator. All three exposed DevKit ground pins share the supply return.

Do not choose a supply or heatsink from an idle-current reading. At an explicitly assumed 300 mA regulator load, the site's power library computes 0.51 W for (5 − 3.3) × 0.3, excluding regulator quiescent loss. Actual wireless current varies. Verify transient headroom and junction temperature under the intended workload; the package current rating alone is insufficient. The regulator tab is output-connected: check insulation before attaching metal hardware.

Each red LED has its own 1 kΩ series resistor and a grounded cathode. Assuming an ideal 3.3 V GPIO high and a 2 V LED drop, the Ohm's law library gives 1.3 mA per LED. Real current depends on the LED and output voltage. Configure GPIO25 and GPIO26 as outputs; neither LED is a bare load across a pin.

J2 connects an external normally open button from GPIO27 to ground. R3 pulls that input up to 3.3 V when released. Pressed, its nominal current is 0.33 mA. Configure GPIO27 as an input, read LOW as pressed and debounce in software. Keep all GPIO signals at 3.3 V logic levels. Spare module pins remain open intentionally.

This is isolated-pad perfboard with insulated jumpers and no track cuts. Wire crossings do not connect unless they share an endpoint. A passing continuity check cannot verify regulator stability, RF clearance, supply transients or physical assembly.

Building it, step by step

  1. Verify the exact 38-pin DevKitC V4 pinout. Fit two socket rows with the antenna end oriented as shown; keep the DevKit removed.
  2. Fit the LD1117V33 after checking GND/OUT/IN and its tab connection. Wire J1, input/output electrolytics and common ground with short local leads.
  3. With the DevKit removed, check for shorts, apply current-limited 5 V and measure the regulator output before connecting it to 3V3. Remove power.
  4. Fit both LED resistors and red LEDs, cathodes to ground. Wire GPIO25 and GPIO26 to their separate resistor inputs.
  5. Wire R3 from 3.3 V to GPIO27 and J2 from that signal to ground. Connect an external normally open button; verify its terminal pairs with a meter.
  6. Insert the preprogrammed DevKit with power off, then test the external supply alone. Read the button with software debounce and monitor regulator temperature and supply dips under wireless activity.

Tools for this build

Frequently asked questions

Can I use any ESP32 development board?

No. Verify the 38-pin Espressif DevKitC V4 header arrangement and physical spacing. Other variants and clones need their own footprint and wiring check.

Can USB stay connected with the external regulator?

No. Use one DevKit power option only. Remove the DevKit from this carrier for USB programming, with external power off.

Does the button need the internal pullup?

R3 already provides an external 10 kΩ pullup to 3.3 V. Read GPIO27 as an input: released is high, pressed is low. Debounce it in software.

Why is this regulator wired differently from a 7805?

The specified ST LD1117V33 TO-220 pin order is GND, OUT, IN. Verify the exact part datasheet; a generic TO-220 package does not imply a universal pinout.