ESP32-S3 Board Design


Reconciled: the executor completed without changing the live result—still 13 airwires and only the J1 warning, with no new copper defects. Since the same worker is stalled on the layer-selection fault, I’m switching to a fresh layout executor to independently diagnose that root cause and attempt the remaining routes without disturbing the clean checkpoint.
The independent recovery pass is still actively working, not stalled or failed. I’m keeping it isolated from the validated USB/power routing and will reconcile its result against live DRC before accepting any changes.
Thought for 4 mins 53 sec
Awaiting 1 background task
Received notification from "PCB Routing Recovery" that it finished — picking the work back up.
The independent PCB routing-recovery executor completed, but I can’t inspect or reconcile its final changes because no ACUs are currently available.
Last verified state before that pass:
  • 12 × 80 mm, four-layer PCB
  • 13 airwires: 12 GPIO nets plus RF net 1
  • 0 dangling traces, copper overlaps, or invalid-layer errors
  • One non-blocking J1 edge-placement warning
Remaining: inspect the recovery report, rerun live DRC, verify USB/RF/crystal/power integrity, and fix or document any residual connections.
Review routing recovery
Check critical routing
Resolve J1 warning
Document routing status

Project Specification
Project Overview
  • Status: Review-ready schematic
  • Minimal production-intent ESP32-S3FN8 bare-chip development board.
  • Native USB-C power and USB Serial/JTAG, external u.FL antenna, compact single-row GPIO breakout.
Intended Use
A narrow development/control board intended for professional four-layer PCB assembly and firmware development over the ESP32-S3 native USB interface.
What the Device Should Do
  • Power from 5 V USB-C as a sink/device.
  • Generate a stable 3.3 V rail for the ESP32-S3FN8.
  • Support native USB Serial/JTAG on GPIO19/GPIO20.
  • Boot normally or enter ROM download mode with RESET and BOOT controls.
  • Connect a 2.4 GHz antenna through u.FL.
  • Expose safe GPIOs in one longitudinal row.
Main Features
  • ESP32-S3FN8, QFN56 with exposed pad and integrated 8 MB QSPI flash.
  • USB4105-GF-A USB-C receptacle.
  • USBLC6-2SC6 USB ESD array and 0805L110WR resettable fuse.
  • TLV62568DBVR 1 A synchronous buck, nominal 3.318 V setpoint.
  • CX2016DB40000D0FLJCC 40 MHz, ±10 ppm crystal.
  • Hirose U.FL-R-SMT-1(10) RF connector.
  • Two compact PTS810 tactile switches.
  • 1×20, 1.27 mm-pitch through-hole socket footprint.
System Architecture
USB-C → VBUS ESD/bypass → PPTC fuse → 1 A buck → 3V3 → ESP32-S3 power domains. USB D+/D− pass through ESD and 0 Ω links to GPIO20/GPIO19. The SoC drives a crystal network and a CLC RF match into u.FL.
Hardware Subsystems
USB / Protection
  • CC1 and CC2 each use 5.1 kΩ Rd to ground.
  • Both connector D+ contacts are joined; both D− contacts are joined.
  • USBLC6-2SC6 protects D+/D−; VBUS is its reference supply.
  • 0 Ω series links and DNP shunt-cap footprints are reserved near the SoC.
  • Connector grounds and shell tabs connect directly to board ground.
Regulator / Power
  • U2: TLV62568DBVR, 2.5–5.5 V input, 1 A.
  • 4.7 µF input, 2.2 µH / 1.8 A inductor, 10 µF output.
  • Feedback: 453 kΩ / 100 kΩ with 6.8 pF feed-forward capacitor.
  • Calculated setpoint: 3.318 V, within the ESP32-S3 3.0–3.6 V operating range.
MCU / Crystal / RF
  • Every power domain and exposed pad is connected.
  • Dedicated decoupling is provided for VDD3P3, VDDA, VDD3P3_RTC, VDD3P3_CPU, and VDD_SPI.
  • RF supply uses a 2.1 nH, 600 mA feed inductor and local 10 µF + 1 µF + two 100 nF capacitors.
  • Crystal uses 24 nH series element and initial 12 pF C0G load capacitors.
  • RF uses initial 1.5 pF – 2.7 nH – 1.5 pF CLC values into a 50 Ω u.FL path.
Reset / Boot
  • CHIP_PU: 10 kΩ pull-up, 1 µF delay capacitor, reset button to ground.
  • GPIO0: 10 kΩ pull-up and boot button to ground.
GPIO Breakout
  • 18 GPIOs: GPIO1, GPIO2, GPIO4–GPIO18, and GPIO21.
  • GPIO15/GPIO16 are presented on the unused XTAL_32K_P/N package pins.
  • One additional pin is 3V3 and one is GND.
  • GPIO0, GPIO3, GPIO19/20, GPIO33–38, JTAG, UART0, strapping pins, and in-package flash interface pins are not exposed.
Interfaces and Connections
  • J1: USB-C USB 2.0 receptacle.
  • J2: 50 Ω u.FL antenna receptacle.
  • J3: single-row 1.27 mm GPIO/power breakout.
  • SW1: reset; SW2: boot/download.
Power and Runtime Expectations
USB-powered only; no battery subsystem. The board must remain within ordinary USB current capability and does not assume USB-PD.
Power Tree and Power Budget
  • ESP32-S3 measured Wi-Fi TX peak: 340 mA at the 3.3 V rail.
  • Espressif recommends a source capable of at least 500 mA for a single supply.
  • Design rail budget: 500 mA continuous design target, with a 1 A regulator for transient and expansion margin.
  • Approximate USB input at 500 mA output and 90% efficiency: 367 mA.
  • A 5 V-to-3.3 V LDO would dissipate about 0.578 W at 340 mA, too high for a tiny narrow-board package without significant thermal copper; therefore a buck was selected.
Manufacturing and Assembly Expectations
  • Four-layer PCB in the next phase.
  • 10–12 mm final width, ≤100 mm length.
  • Components must be placed in a single longitudinal column where practical; no side-by-side architecture across board width.
  • Predominantly 0402 passives; larger packages only for energy storage/current capability.
  • Professional reflow assembly.
Firmware-Relevant Hardware Requirements
  • Native USB Serial/JTAG enabled on GPIO19/20.
  • GPIO0 low during reset enters ROM download mode.
  • GPIO15/16 cannot simultaneously be used for an external 32.768 kHz crystal.
Physical Design Expectations
  • External u.FL is mandatory; no PCB antenna.
  • RF and USB require controlled impedance on the future four-layer stackup.
  • RF matching and crystal load values require final PCB tuning/validation.
Important Design Decisions
  • Buck regulator selected over LDO for thermal margin.
  • External antenna connector selected because of the narrow board.
  • Debug UART and JTAG pins are intentionally not broken out; native USB is the primary programming/debug interface.
Assumptions
  • USB host provides standard 5 V and enough current for the design; no Type-C current-advertisement measurement or PD negotiation is implemented.
  • The 1×20 breakout footprint is represented by a real 1.27 mm through-hole socket-strip footprint and assigned Harwin M50-3032042 sourcing metadata.
Change Notes
  • Initial complete schematic created with 43 components and 40 named nets.
  • ERC, passive, footprint, availability, and manufacturing-part-number checks completed with no unresolved open/warning/error findings.
  • Project Overview

  • Intended Use

  • What the Device Should Do

  • Main Features

  • System Architecture

  • Hardware Subsystems

  • USB / Protection

  • Regulator / Power

  • MCU / Crystal / RF

  • Reset / Boot

  • GPIO Breakout

  • Interfaces and Connections

  • Power and Runtime Expectations

  • Power Tree and Power Budget

  • Manufacturing and Assembly Expectations

  • Firmware-Relevant Hardware Requirements

  • Physical Design Expectations

  • Important Design Decisions

  • Assumptions

  • Change Notes