Schematic Connection Check


Here are the highest-impact improvements I’d make:
  1. Fix known connectivity/layout issues
    • Connect SW13 to an intended ESP32 GPIO.
    • Clear the remaining PCB airwires and dangling traces.
    • Re-check that power and GND are actually routed, not just schematic-connected.
  2. Improve the power system
    • Replace or thermally review the AMS1117; it may dissipate too much heat from USB 5V to 3.3V with ESP32 + audio load.
    • Consider a small buck regulator instead.
    • Correct the suspicious C1 = 1F value.
    • Add/verify proper regulator input/output bulk caps close to U2.
  3. Harden ESP32 boot/reset
    • Add a defined pull-up on IO0 if the boot button pulls it low.
    • Keep EN pull-up and reset cap values intentional.
    • Decide whether RXD0/TXD0 should be exposed for debug/programming.
  4. Improve USB-C robustness
    • Add ESD protection on USB D+/D−.
    • Add a fuse/polyfuse or current limiting on VBUS.
    • If USB data is used, route D+/D− as a short matched differential pair.
  5. Fix WS2812B logic margin
    • Since the LED is powered from 5V but driven by 3.3V ESP32 logic, add a level shifter or power the WS2812B from 3.3V.
  6. Improve audio performance
    • Place MAX98357A decoupling caps very close to its VDD pins.
    • Keep speaker traces short/wide and away from antenna/USB data.
    • Confirm speaker impedance/power is compatible with the amp and 3.3V supply.
  7. ESP32 layout/antenna
    • Enforce the ESP32 module antenna keepout: no copper, traces, or components under/near the antenna region.
    • Put 3.3V decoupling close to the module power pins.
    • Use a solid GND plane with short return paths.
  8. Manufacturing polish
    • Clean up schematic label overlaps for readability.
    • Add test pads for 5V, 3V3, GND, EN, IO0, USB D+/D−, and key I2S/audio signals.
    • Add board revision/date/silkscreen labels.
    • Run ERC/DRC again after routing.
Fix and review issues
Fix SW13 connection
Improve power supply
Clean PCB routing
Add USB protection
Create test points

U2
Manufacturer Part Number
AMS1117-3.3
J1
IC1
Manufacturer Part Number
MAX98357AETE+T
U1
Manufacturer Part Number
ESP32-S3-WROOM-1-N16R8
R3
Resistance
5.1kΩ
C9
Capacitance
100nF
C8
Capacitance
100nF
C1
Capacitance
100nF
R4
Resistance
5.1kΩ
R2
Resistance
10kΩ
C2
Capacitance
22uF
C7
Capacitance
100nF
SW15
SW1
SW19
SW11
SW7
SW13
SW17
SW3
SW8
SW2
SW9
SW10
SW18
SW12
SW16
SW6
SW14
SW5
SW4
SW21
SW20
C4
Capacitance
1uF
D1
C5
Capacitance
10uF
C6
Capacitance
22uF
R5
Resistance
100kΩ
C3
Capacitance
100nF
LS1
Manufacturing Layout / Electrical Review
Read-only review requested: component layout, traces, footprints/orientation risk, and electrical readiness for manufacture. No design changes were made.
Bottom line
I would not send this PCB to manufacture yet. The board has multiple hard DRC failures that can prevent electrical operation or create shorts/opens:
  • 5 airwires: not all schematic nets are physically routed.
  • 4 floating copper issues: copper/traces/vias exist that are not connected to any net.
  • 13 overlapping copper issues: copper geometry is overlapping/shorting or violating clearances.
  • 12 missing manufacturer part numbers for passives/generic parts.
  • 13 ERC floating-pin warnings, including active design concerns on switches and some intentional/no-connect-style pins.
Until the airwires and overlapping copper are fixed, I cannot say it will work electrically after fabrication.
Component footprint / orientation review
U1 — ESP32-S3-WROOM-1-N16R8
  • Footprint appears to be a dedicated ESP32-S3-WROOM module footprint with the expected large module outline and many castellated pads.
  • Placement is on the right side of the board. This is generally good if the PCB antenna end is at/near the board edge and the keepout under/in front of the antenna is honored.
  • Recommendation: verify the antenna keepout against Espressif’s datasheet mechanical drawing. There should be no copper, fills, traces, or components under/in front of the antenna keepout region. If the antenna points inward over copper/components, Wi-Fi/BLE performance may be poor.
  • 3V3 decoupling C1/C2 are near the regulator area rather than immediately at the ESP32 3V3 pad. Electrically it may boot, but for Wi-Fi current bursts the 0.1 µF capacitor should be as close as practical to U1:3V3 with a very short ground path.
J1 — TYPE-C-31-M-12 USB-C receptacle
  • Footprint exposes the expected USB-C pads: VBUS, GND, CC1/CC2, D+/D− duplicated pins, SBU, and shield/mount pads.
  • SBU1/SBU2 floating is acceptable for USB 2.0 device-only designs if intentionally left NC.
  • Recommendation: confirm connector mouth/mechanical edge placement in the 3D/mechanical view. A USB-C receptacle must overhang or align correctly to the board edge/enclosure opening.
  • Recommendation: verify D+ and D− are routed as a short, coupled pair with similar length and no unnecessary stubs. Full 90 Ω differential impedance is ideal, though short USB FS/HS device runs on a small board can tolerate some imperfection.
  • Recommendation: add/verify ESD protection near the USB connector before production if this board will be user-plugged frequently.
U2 — AMS1117-3.3 regulator
  • SOT-223 footprint exposes VIN, VOUT, GND, and TAB(VOUT), consistent with AMS1117-style packages.
  • DRC reports an airwire involving TAB(VOUT), so the regulator output tab may not be fully connected in layout. This is a hard issue because the tab is electrically VOUT and also important for heat spreading.
  • Recommendation: ensure the AMS1117 has the required input/output capacitors placed close to VIN/GND and VOUT/GND. AMS1117 regulators are sensitive to output capacitor ESR/value; verify the selected capacitors against the datasheet and actual MPN.
  • Recommendation: check thermal dissipation. Dropping USB 5 V to 3.3 V with ESP32 Wi-Fi/audio/LED loads can heat a linear regulator substantially.
IC1 — MAX98357AETE+T I2S class-D amplifier
  • Footprint exposes the expected TQFN pins, including VDD_1/VDD_2, GND pins, OUTP/OUTN, BCLK/LRCLK/DIN, GAIN_SLOT, ~SD_MODE, and THERMAL_PAD.
  • The TQFN footprint concept matches the datasheet package style.
  • N.C. pin warnings are not a problem if they are intentionally no-connect.
  • Recommendation: thermal pad must be tied to GND with adequate copper/vias per datasheet. If the thermal pad is not solidly grounded/soldered, thermal and EMI performance can suffer.
  • Recommendation: speaker output traces OUTP/OUTN should be routed as a short, tight pair to LS1 and kept away from the ESP32 antenna and sensitive USB/data lines; class-D edges can radiate.
  • Recommendation: verify amplifier supply voltage choice. MAX98357A supports 2.5–5.5 V; if powered from 3.3 V it will work but with lower maximum speaker power than 5 V.
LS1 — SMS-1508MS-HT-R speaker
  • Footprint includes LEAD(+), LEAD(−), and dummy/mechanical leads, which is plausible for this SMT speaker style.
  • DUMMY_LEAD_1 and DUMMY_LEAD_2 floating is likely acceptable if they are mechanical pads only; mark them intentional NC if needed.
  • DRC reports overlapping copper involving speaker lead pads/traces. This must be resolved before manufacture.
  • Recommendation: confirm speaker acoustic opening/orientation against the datasheet and enclosure. Do not cover the sound port with copper, solder mask-only assumptions, labels, or enclosure material.
D1 — WS2812B
  • Footprint exposes VDD, VSS, DIN, and DOUT, consistent with WS2812B.
  • Prior review noted DOUT was tied to GND. If this remains true, it is not recommended; DOUT should be left no-connect unless chaining another LED.
  • Recommendation: add/verify a local bypass capacitor near VDD/VSS and a modest series resistor on DIN if the trace is long/noisy.
  • Recommendation: confirm LED pin-1/orientation marker in the footprint against the exact WS2812B package variant, since WS2812 variants have common orientation/pinout differences.
SW1–SW21 — TS-1088-AR02016 tactile switches
  • Footprint size reported around 3.08 mm × 5.59 mm, generally consistent with a small SMD tactile switch footprint class.
  • Most switches appear arranged in a usable front-panel grid.
  • ERC still reports SW18:1 and SW19:1 floating. Prior issue also included SW13; current DRC/airwire list still contains generic pad-name airwires that may correspond to switch/button routing.
  • Recommendation: verify each button has one side to GND and one side to a real ESP32 GPIO net, and firmware enables internal pull-ups or external pull-ups are provided.
  • Recommendation: confirm the physical button actuator direction and silkscreen orientation against the TS-1088 datasheet before committing to enclosure/button caps.
Trace / connectivity issues that block manufacturing
Airwires — hard failure
The DRC reports 5 unrouted connections. Named examples include:
  • Trace 612e
  • Pad/name 1 airwires
  • U2 TAB(VOUT) airwire
Recommendation: do not fabricate while any airwires remain. Each one is a missing electrical connection.
Floating copper — hard failure
The DRC reports 4 floating copper traces/islands:
  • Trace 0279
  • Trace 2171
  • Trace 32fc
  • Trace 5259
Recommendation: delete or reconnect these islands. Floating copper can create EMI/coupling issues and may indicate broken routing intent.
Overlapping copper — hard failure
The DRC reports 13 overlapping-copper issues. These include overlaps involving trace/via objects and component pad UIDs, including speaker and ESP32-related geometry.
Recommendation: treat these as possible shorts until proven otherwise. Clear all overlapping-copper DRC errors before ordering boards.
Vias / planes
The board is configured as a 4-layer stackup. If Mid-Layer 2 is intended as a 3V3 plane, verify the copper polygon/fill is assigned to the 3V3 net and all 3V3 stitching vias include Mid-Layer 2 in their connected layers.
Recommendation: keep one internal layer as a mostly continuous GND reference plane if possible; this benefits USB, ESP32 RF, class-D amp return currents, and button/LED signal integrity.
Manufacturing metadata issues
The following components lack MPNs and should be resolved before fabrication/assembly:
  • R2, R3, R4
  • C1, C2, C3, C4, C5, C6, C7, C8, C9
Recommendation: set values, voltage ratings, tolerances, dielectric/package, manufacturer, and MPN for every passive. C9 previously appeared as 104F; that should be corrected to a real capacitance value such as 0.1 µF / 100 nF if intended.
Electrical readiness assessment
The high-level design concept is sound for a programmable ESP32-S3 synth board: USB-C programming/power, ESP32-S3, buttons, WS2812, I2S class-D amplifier, and speaker all fit the intended product.
However, the current PCB/layout is not electrically safe to manufacture yet because there are unresolved opens, shorts/overlaps, and floating copper. Footprints for major ICs appear generally plausible from the available part data, but the final signoff requires clearing DRC/ERC and checking mechanical orientation/keepouts against each datasheet drawing.
Highest-priority recommendations
  1. Clear all overlapping copper errors first; these may be shorts.
  2. Clear all airwires; these are missing connections.
  3. Resolve floating copper by reconnecting or deleting it.
  4. Verify ESP32 antenna keepout against Espressif documentation.
  5. Verify USB-C mechanical edge alignment and D+/D− routing.
  6. Verify MAX98357A thermal pad-to-GND and speaker output trace pairing/clearance.
  7. Fix/confirm WS2812 DOUT and LED orientation.
  8. Confirm SW18/SW19 and any remaining switch input nets.
  9. Assign real passive MPNs and ratings before BOM/export.
  • Bottom line

  • Component footprint / orientation review

  • U1 — ESP32-S3-WROOM-1-N16R8

  • J1 — TYPE-C-31-M-12 USB-C receptacle

  • U2 — AMS1117-3.3 regulator

  • IC1 — MAX98357AETE+T I2S class-D amplifier

  • LS1 — SMS-1508MS-HT-R speaker

  • D1 — WS2812B

  • SW1–SW21 — TS-1088-AR02016 tactile switches

  • Trace / connectivity issues that block manufacturing

  • Airwires — hard failure

  • Floating copper — hard failure

  • Overlapping copper — hard failure

  • Vias / planes

  • Manufacturing metadata issues

  • Electrical readiness assessment

  • Highest-priority recommendations