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
SW15
SW1
SW19
R4
Resistance
5.1kΩ
SW11
SW7
SW13
D1
R2
Resistance
10kΩ
SW17
SW3
SW8
SW2
SW9
SW10
SW18
SW12
SW16
SW6
SW14
SW5
SW4
SW21
SW20
C8
Capacitance
100nF
C1
Capacitance
100nF
C4
Capacitance
1uF
C2
Capacitance
22uF
C5
Capacitance
10uF
C6
Capacitance
22uF
R5
Resistance
100kΩ
C7
Capacitance
100nF
C3
Capacitance
100nF
LS1
Schematic Review — ESP32-S3 Programmable Music Synth
Verdict
The schematic is directionally sensible for a programmable ESP32-S3 music synth: it has an ESP32-S3-WROOM module, native USB-C wiring for programming, reset/boot controls, many tactile inputs to GPIOs, a MAX98357A I2S Class-D amplifier, an onboard speaker, and a WS2812B LED.
However, I would not call it production-ready yet. The remaining issues are mostly connectivity cleanup, manufacturing metadata, and a few design choices that should be confirmed before layout/fab.
What Looks Good
ESP32-S3 Core
  • U1 is powered from the 3.3 V rail, Net 12.
  • All ESP32 ground pins are tied to GND.
  • EN has a pull-up path through R2 to 3V3 and reset switch SW20 to GND.
  • BOOT uses IO0 with SW21 to GND, which is the expected ESP32 bootloader entry mechanism.
USB-C / Programming
  • USB-C VBUS feeds the regulator input through Net 3.
  • USB D+ and D- are wired to ESP32-S3 native USB pins:
    • J1 DP1/DP2 → U1 IO20
    • J1 DN1/DN2 → U1 IO19
  • CC1 and CC2 each have 5.1 kΩ pull-down resistors to GND, appropriate for a USB-C sink/device.
3.3 V Power
  • AMS1117 output feeds Net 12, which powers U1 and IC1.
  • Local bulk/decoupling capacitors are present on 3V3.
Audio Path
  • MAX98357A is powered from 3V3.
  • I2S signals are connected:
    • BCLK → U1 IO17
    • DIN → U1 IO16
    • LRCLK → U1 IO18
  • Speaker LS1 is connected differentially to OUTP/OUTN.
Controls
  • Most tactile buttons have one side to GND and the other side to ESP32 GPIO, which works well with internal pull-ups.
Issues / Risks To Fix
1. Some Switch Connections Are Still Broken
ERC reports:
  • SW18:1 floating
  • SW19:1 floating
  • SW13:1 is on a single-pin net, Net 39
This means not all user buttons are correctly connected after the recent edits. Reconnect these to intended GPIOs and rerun ERC.
2. WS2812B DOUT Is Tied To GND
D1:DOUT is currently connected to GND. If this is a single LED and DOUT is unused, it should be left no-connect, not tied to ground. If more LEDs will be chained later, route DOUT to the next LED DIN or a test pad.
D1 itself otherwise makes sense:
  • VDD → 5V / VBUS net
  • VSS → GND
  • DIN → ESP32 IO48
But because WS2812B is powered at 5 V and ESP32 outputs 3.3 V logic, logic-high margin may be marginal. It often works with short traces and same-board wiring, but production robustness is better with either 3.3 V-powered addressable LED variant or a level shifter.
3. MAX98357A Thermal Pad Is Floating
The MAX98357A thermal pad should normally be tied to GND copper for thermal and electrical performance. Current ERC flags IC1:THERMAL_PAD floating.
4. MAX98357A No-Connect Pins Need Explicit No-Connects
IC1 N.C._1 through N.C._4 are floating warnings. If the datasheet marks them as no-connect, mark them explicitly as no-connect in Flux to clear ERC.
5. Speaker Dummy Leads Need Handling
LS1 dummy leads are floating. If they are mechanical-only pins, mark them no-connect. If the footprint expects mechanical pads only, confirm they are not electrically tied internally.
6. USB Serial UART Pins Are Floating
U1 RXD0/TXD0 are floating. This is acceptable if programming is only via native USB, but add test pads or a header if you want UART debug/programming fallback.
7. Regulator Choice / Thermal Margin
AMS1117 from USB 5 V to 3.3 V is simple but inefficient. For ESP32-S3 Wi-Fi bursts plus MAX98357A audio current, estimate thermal dissipation before production:
P ≈ (5 V - 3.3 V) × load current.
At 300 mA, that is about 0.51 W in the regulator, which can get hot depending on copper area. Consider a buck regulator if the board will drive audio loudly, LEDs, and Wi-Fi simultaneously.
8. C9 Value Looks Wrong
C9 is shown as 104F, which likely means 0.1 µF code “104”, not 104 farads. Set it explicitly to 0.1 µF or 100 nF with an appropriate voltage rating.
9. Manufacturing Metadata Missing
R2/R3/R4 and C1/C2/C3/C4/C5/C6/C7/C8/C9 are missing MPNs. This blocks reliable manufacturing/BOM export.
Recommendation
The architecture is valid for a programmable ESP32-S3 synth board, but fix the remaining button nets, D1:DOUT-to-GND, MAX98357A thermal/no-connect handling, passive MPNs, and C9 value before considering the schematic complete.
  • Verdict

  • What Looks Good

  • ESP32-S3 Core

  • USB-C / Programming

  • 3.3 V Power

  • Audio Path

  • Controls

  • Issues / Risks To Fix

  • 1. Some Switch Connections Are Still Broken

  • 2. WS2812B DOUT Is Tied To GND

  • 3. MAX98357A Thermal Pad Is Floating

  • 4. MAX98357A No-Connect Pins Need Explicit No-Connects

  • 5. Speaker Dummy Leads Need Handling

  • 6. USB Serial UART Pins Are Floating

  • 7. Regulator Choice / Thermal Margin

  • 8. C9 Value Looks Wrong

  • 9. Manufacturing Metadata Missing

  • Recommendation