ESP32 W5500 Through-Hole

E

ewartm

through hole: 1x ESP32-DevKitC (30 pin), 1x WS5500 (16 pin)

flux

I can’t make project changes right now because AI execution is unavailable due to no available ACUs.
What I understand you want: a through-hole setup using:
  • 1× ESP32-DevKitC, 30-pin module/header footprint
  • 1× W5500 Ethernet module/header, 16-pin footprint
What remains to be done once ACUs are available:
  • Confirm the exact ESP32-DevKitC 30-pin pinout/row spacing and the exact W5500 16-pin module/header pinout.
  • Add through-hole headers or module footprints for both boards.
  • Wire ESP32 ↔ W5500 over SPI, typically SCLK/MOSI/MISO/CS plus RESET/INT if needed.
  • Add 3.3 V and GND connections, and verify voltage compatibility.
  • Run schematic/ERC checks and then proceed to PCB placement/layout if desired.
Show SPI wiring
Find header footprints
Create pinout checklist
Run ERC/DRC
Sign up to send

Files

Schematic

Layout

3D View

could i take this scimatic file to kicad app
H

hatem0866

@copilot could i take this scimatic file to kicad app
1y

copilot

You can import Flux designs into KiCad, but it will require some conversion steps. You will need to export the schematic and PCB layout from Flux in a format that KiCad can understand. Here’s a general approach:
  1. Export from Flux:
    • Export the schematic and layout from Flux to a standard interchange format like EDIF, or as individual netlists and component files. Check if Flux offers a direct export option to one of these formats.
  2. Use Conversion Tools:
    • If Flux provides a way to export to EDIF or another format supported by KiCad, you can import that into KiCad directly.
    • Alternatively, you can export a netlist and manually recreate the schematic in KiCad using the exported netlist.
  3. Import into KiCad:
    • Using KiCad’s import tools, bring the exported files into your KiCad project.
    • You may need to reassign footprints or manually adjust some components if there are discrepancies in libraries or components.
Remember that symbols and footprints might need to be manually assigned or recreated if they don't perfectly match between the systems. Would you like more detailed guidance on any of these steps, or assistance with a specific file format?
1y
3
C4
Capacitance
10uF
R1
Resistance
Resistance
Resistance
10kΩ
C8
Capacitance
10uF
PWR
C6
Capacitance
0.1uF
C7
Capacitance
0.1uF
R4
Resistance
1kΩ
C5
Capacitance
10uF
Q1
U2
U1
IC1
Q2

ESP32-WROOM-32E Reference Design