ESP32 W5500 Through-Hole

through hole: 1x ESP32-DevKitC (30 pin), 1x WS5500 (16 pin)
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
could i take this scimatic file to kicad app

@copilot could i take this scimatic file to kicad app
1y
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
D2
ESP_RX
GPIO36
ESP_RX
CC1
ESP_TX
GPIO18
USBDP
USBDN
GPIO15
GPIO14
ESP_TX
GPIO21
USBDP
GPIO34
GPIO34
GPIO25
CC2
GPIO27
ESP_IO0
GPIO25
USBDN
ESP_IO0
GPIO22
GPIO16
GPIO5
ESP_IO0
CC1
USBDP
GPIO13
GPIO17
GPIO12
GPIO35
GPIO16
GPIO18
GPIO33
GPIO12
USBDN
ESP_RX
GPIO33
GPIO19
GPIO4
GPIO36
GPIO32
GPIO15
USBDN
ESP_EN
USBDP
GPIO2
GPIO26
GPIO13
GPIO22
CC2
GPIO2
GPIO4
GPIO39
GPIO26
GPIO19
GPIO39
USBDN
GPIO32
ESP_EN
GPIO14
GPIO21
ESP_TX
ESP_EN
GPIO23
GPIO23
ESP_IO0
GPIO5
GPIO27
ESP_EN
GPIO17
USBDP
GPIO35
D1
C4
Capacitance
10uF
+3V3
C3
Capacitance
10uF
VBUS
R1
Resistance
Resistance
Resistance
10kΩ
C11
Capacitance
0.1uF
+3V3
J1
C8
Capacitance
10uF
+5V
R2
Resistance
Resistance
Resistance
5.1kΩ
+3V3
C6
Capacitance
0.1uF
C7
Capacitance
0.1uF
R4
Resistance
1kΩ
J2
R3
Resistance
Resistance
Resistance
5.1kΩ
+5V
C10
Capacitance
0.1uF
+3V3
C2
Capacitance
0.1uF
C1
Capacitance
0.1uF
VBUS
+5V
+3V3
+3V3
+3V3
+3V3
PWR
C9
Capacitance
10uF
USB1
RST
C5
Capacitance
10uF
BOOT
Q1
U2
U1
IC1
Q2

No files yet

Documents

    Documents are markdown text files which describe project goals, capture details, or even simulation outputs.

    Assets

    ESP32-WROOM-32E Reference Design-removebg-preview.png

    ESP32-WROOM-32E Reference Design-removebg-preview.png

    ESP32-WROOM-32E Reference Design-removebg-previewThumbnail

    ESP32-WROOM-32E Reference Design

    ESP32-WROOM-32E Reference Design thumbnail
    This project is a reference design for an ESP32-WROOM-32E based device. It features USB-C for power and data transfer, onboard voltage regulation, and multiple peripheral connections. It also includes a CH340C for USB to serial conversion #referenceDesign #project #ESP32 #ESP32WROOM #RF #WIFI #MCU #simpleEmbedded #espressif #template

    Pricing & Availability

    Distributor

    Qty 1

    Controls