ESP32 Bit Pirate

Wired network module

W5500 Ethernet module for ESP32

Wire a W5500 Ethernet module to ESP32 or ESP32-S3 and use ESP32 Bit Pirate for DHCP, ping, HTTP, raw TCP, Modbus-oriented checks and recipes.

Start here when wiring a W5500 Ethernet module to ESP32 for SPI link checks, DHCP, ping and Modbus lab tests. Confirm link status before protocol-level debugging.

Ethernet
DHCP
TCP
Modbus

Open recipes Choose a board

workflow

Start with W5500 link and DHCP checks

Confirm SPI wiring, CS, reset/IRQ lines, 3.3 V power and link status before network tests. Start with DHCP or static config, then ping before HTTP, raw TCP or Modbus checks.

01
Wire SPI, CS, IRQ, reset if needed, 3.3 V power and common ground.
02
Connect Ethernet to a known network or isolated test switch.
03
Run config, then connect to acquire DHCP before testing services.
04
Use ping or raw TCP to separate network reachability from application bugs.
05
Use Modbus or HTTP recipes only on networks you own or are authorized to test.

Example CLI flow

mode ethernet
config
connect
status
ping 192.168.1.1
http get http://192.168.1.10/

Use this W5500 sequence for link, IP and ping checks before HTTP, TCP or Modbus traffic.

hardware reminders

W5500 Ethernet wiring notes before link tests

Confirm W5500 SPI wiring, CS, reset or IRQ, 3.3 V power, Ethernet link and network scope before TCP tests.

Wiring View

Generated wiring summary: W5500 to BP SPI. Confirm W5500 SPI pins, reset and Ethernet link before power.

Power and level

Most W5500 modules use 3.3 V logic; confirm regulator and level-shifter details.

Network scope

Run active checks only on owned or authorized networks.

SPI stability

If network tests fail randomly, check SPI wiring and power before blaming TCP.

Before wiring a module or target chip, check pinout, voltage, ground reference and whether the selected ESP32-S3 board has the required pins free.

task-level guides

Detailed W5500 Ethernet module recipes

Use these W5500 guides for SPI link bring-up, IP configuration, ping, HTTP and raw socket checks.

Connect W5500 Ethernet

Task-level guide with wiring, commands and troubleshooting steps.

Check HTTP endpoint

Task-level guide with wiring, commands and troubleshooting steps.

Check open ports with nmap

Task-level guide with wiring, commands and troubleshooting steps.

Open Modbus TCP session

Task-level guide with wiring, commands and troubleshooting steps.

Test raw TCP nc/telnet

Task-level guide with wiring, commands and troubleshooting steps.

what it is

What W5500 is used for

W5500 modules add SPI Ethernet to ESP32-S3 targets for wired network bring-up, service checks and industrial-style TCP workflows.

practical value

Why use W5500 with ESP32 Bit Pirate

ESP32 Bit Pirate can turn a W5500 breakout into a small network bench tool for DHCP, ping, raw TCP, HTTP, nmap-style checks and Modbus TCP sessions.

common symptoms

Common problems with W5500 Ethernet module

W5500 failures usually come from SPI wiring, reset/IRQ lines, 3.3 V power, link state, DHCP or the tested service itself.

No DHCP lease

Check link LEDs, cable, switch, subnet and W5500 power.

Ping works but HTTP fails

The network path is alive; check port, URL and service state.

Random disconnects

Check power, SPI cable length and reset wiring.

pages

Useful W5500 next pages

Use these links for W5500 wiring, DHCP bring-up, ping, HTTP, raw TCP, Modbus and hardware notes.

Ethernet reference for W5500 link, DHCP, ping, TCP and Modbus tests.

SPI

SPI reference for W5500 wiring, chip select and reset/IRQ checks.

ESP32-S3 DevKit

Board-specific notes for using W5500 Ethernet module with ESP32 Bit Pirate.

Connect W5500 Ethernet

Run config/connect, bring up DHCP and basic wired connectivity.

Check HTTP endpoint

Test an HTTP target from the Ethernet module.

Open Modbus TCP session

Start a Modbus TCP workflow over wired Ethernet.

Test raw TCP

Open a raw TCP session for service checks.

Web Serial Terminal

Use Web Serial for W5500 config, DHCP, ping and service checks.

Hardware ecosystem

Dock, adapters, level notes and physical hardware context.

module-specific answers

W5500 Ethernet module FAQ

Quick answers about W5500 wiring, wired link status, DHCP, ping and Modbus/TCP lab checks.

Can ESP32 Bit Pirate use W5500 Ethernet?

Yes, for wired network workflows through the W5500 module path.

Is W5500 required for Wi-Fi?

No. W5500 is wired Ethernet; Wi-Fi uses the ESP32-S3 radio.

Can it test Modbus TCP?

Yes, use Modbus workflows on owned or authorized targets.

What should I test first?

Start with config, connect/status, then ping, then application-level checks.

Which protocol page is related?

Use the Ethernet protocol page and SPI references for the hardware side.

project

W5500 Ethernet inside ESP32 Bit Pirate.

The W5500 page links Ethernet protocol notes, SPI wiring, link checks, IP setup, socket tests and hardware guidance.