Wiznet makers

1. Title

How to Build a Commercial High-Performance MicroPython Ethernet Node with WIZnet W5500 on ESP32?

2. Summary

This article explains a commercial-oriented MicroPython Ethernet node using an ESP32-class MCU and the WIZnet W5500, with the focus on performance rather than only basic connectivity. The W5500 acts as the Ethernet offload device: the MCU runs the MicroPython application, while W5500 handles the hardwired TCP/IP stack, 10/100 Ethernet MAC/PHY, socket state, and internal Tx/Rx buffering. The original CSDN Wenku answer page could not be directly fetched during verification, so the implementation discussion is grounded in accessible W5500 MicroPython reference material, official WIZnet documentation, and official Microchip ENC28J60 product information.

3. What the Project Does

The accessible W5500 MicroPython reference pattern shows an ESP32 connected to a W5500 module through SPI and running MicroPython code that initializes the WIZnet interface, checks chip/network information, resolves DNS, and uses a requests-style HTTP client through a W5500 socket layer. The repository describes the target as connecting an ESP32 to a W5500 Ethernet module and using Python requests as an HTTP client. It also lists the required MicroPython driver files and the ESP32-to-W5500 wiring for CS, SCK, MOSI, MISO, reset, power, and ground.

For a commercial product, this becomes a wired Ethernet endpoint for telemetry, configuration, monitoring, or local control. The ESP32 executes the application logic in MicroPython: reading sensors, formatting payloads, handling configuration, running a local protocol, or pushing data to an HTTP/MQTT endpoint. The W5500 provides the network-facing behavior: Ethernet link, TCP/UDP protocol handling, socket state, and packet buffers.

The performance goal is not only raw throughput. In an embedded commercial system, useful performance means predictable connection behavior, lower firmware complexity, reduced MCU-side network stack load, bounded memory use, stable socket recovery, and repeatable behavior after cable removal, server timeout, or gateway failure. W5500 helps by moving TCP/IP handling into the Ethernet controller instead of forcing the MicroPython application and MCU RAM to carry the full network stack.

4. Where WIZnet Fits

The WIZnet product in this architecture is W5500. WIZnet describes W5500 as a hardwired TCP/IP stack Internet controller that connects to an external MCU through SPI up to 80 MHz. It integrates a 10/100 Ethernet MAC and PHY, supports TCP, UDP, ICMP, IPv4, ARP, IGMP, and PPPoE, provides eight independent sockets, and includes 32 KB internal memory for Tx/Rx buffers.

From a performance perspective, the important point is the division of labor. With W5500, the MCU does not need to run a full software TCP/IP stack for normal Ethernet communication. The MCU communicates with W5500 over SPI and uses socket-level operations, while the chip maintains Ethernet protocol behavior and socket state. This reduces the amount of network processing that must be performed directly inside MicroPython.

The practical limits still matter. W5500 has eight sockets and finite internal buffer memory, so a commercial firmware design should define socket ownership and buffer expectations. For example, one socket may be reserved for telemetry upload, one for local configuration, one for diagnostics, and one for firmware or service recovery. If the product opens sockets casually and leaves cleanup to garbage collection or reboot behavior, performance will degrade under real network faults.

5. Implementation Notes

Because the exact Wenku page returned a fetch error, this section does not claim any code from that page. The accessible ESP32/W5500 MicroPython repository provides a verified reference pattern. Its README.md shows an ESP32-W5500 setup using WIZNET5K, SPI, CS, reset, a W5500 socket module, and a requests wrapper.

Verified reference pattern from README.md / main.py style usage:

from wiznet5k import WIZNET5K
from machine import Pin, SPI
import wiznet5k_socket as socket
import sma_esp32_w5500_requests as requests

spi = SPI(2)
cs = Pin(5, Pin.OUT)
rst = Pin(34)
nic = WIZNET5K(spi, cs, rst)

requests.set_socket(socket, nic)

This matters because the application is not written as a raw Ethernet frame processor. It initializes the W5500 over SPI, binds a socket implementation to the W5500 interface, and then lets the application use higher-level network operations.

The same repository also shows a performance-relevant bring-up sequence: print chip version, print MAC address, print local IP address, perform DNS lookup, and then attach the socket layer to the requests wrapper. These checks are not just debug messages. In a commercial device, they become production diagnostics: confirming W5500 detection, MAC availability, IP acquisition, DNS function, and socket interface readiness before sending application data.

Compared with ENC28J60, the key architectural difference is that ENC28J60 is a 10Base-T Ethernet controller with SPI interface. Microchip describes it as a stand-alone Ethernet controller designed to serve as an Ethernet network interface for any host MCU. It provides the Ethernet interface, but it does not provide the same W5500-style hardwired TCP/IP socket engine. Therefore, more protocol work usually remains in the MCU firmware or external software stack when using ENC28J60.

6. Practical Tips / Pitfalls

• SPI clock is not the only performance variable. W5500 supports high-speed SPI, but real application performance also depends on MicroPython overhead, driver efficiency, socket buffer size, payload size, and how often the firmware polls socket state.
• Use fewer long-lived sockets deliberately. W5500 supports eight independent sockets, but commercial firmware should reserve sockets by function and close/reopen them predictably after timeout, remote disconnect, or link failure.
• Size payloads around buffer behavior. The 32 KB internal Tx/Rx memory is useful, but not unlimited. Avoid unbounded HTTP responses, oversized JSON, and large blocking transfers unless the firmware explicitly chunks data.
• Check link and IP before application traffic. Treat PHY link, IP address, gateway, DNS, and server reachability as separate diagnostic steps. This makes field support easier than a single generic “network failed” message.
• Reset W5500 intentionally. Add a controlled reset path for W5500 when socket state becomes stale. A commercial product should recover the Ethernet controller without relying only on a full MCU reboot.
• Benchmark with the actual workload. A telemetry product, local TCP server, HTTP client, and MQTT client stress the network path differently. Measure connection time, reconnect time, request latency, sustained transfer, and memory use under the real payload format.
• Do not compare W5500 and ENC28J60 only by BOM cost. ENC28J60 can be useful for simple 10Base-T designs, but W5500’s hardwired TCP/IP stack, socket engine, 10/100 MAC/PHY, and internal buffers can reduce firmware burden and improve commercial maintainability.

7. FAQ

Why use WIZnet W5500 for this project?
W5500 is suitable when the product needs wired Ethernet with predictable socket behavior and less MCU-side TCP/IP work. It provides a hardwired TCP/IP stack, 10/100 Ethernet MAC/PHY, eight sockets, and internal Tx/Rx buffer memory.

How does W5500 connect to the platform?
In the verified ESP32 MicroPython reference, W5500 connects over SPI. The shown wiring uses ESP32 GPIO5 for CS, GPIO18 for SCK, GPIO23 for MOSI, GPIO19 for MISO, and GPIO34 for reset, plus 3.3 V and ground. Pin choices can change by board, but the required interface remains SPI plus chip-select and reset.

What role does W5500 play in this project?
W5500 is the Ethernet performance and offload boundary. The ESP32 runs the MicroPython application and high-level logic, while W5500 handles Ethernet MAC/PHY behavior, hardwired TCP/IP protocols, socket state, and packet buffering.

Can beginners follow it?
Yes for a basic HTTP or socket demo, because the MicroPython flow is direct: upload the driver files, wire SPI, initialize WIZNET5K, confirm IP information, and use socket or requests-style code. For commercial use, beginners should not stop at the demo; they need diagnostics, watchdog recovery, link checks, timeout handling, and clear socket ownership.

How does W5500 compare with ENC28J60?
ENC28J60 is a stand-alone 10Base-T Ethernet controller with SPI interface, intended to provide Ethernet network-interface hardware to a host MCU. W5500 is a 10/100 Ethernet controller with a hardwired TCP/IP stack, eight sockets, and internal socket buffers. In practice, W5500 usually fits better when MicroPython firmware needs higher-level socket behavior with less software stack burden, while ENC28J60 requires more MCU-side protocol handling.

8. Source

Original CSDN Wenku answer page:
https://wenku.csdn.net/answer/8bm96fihuc
The page could not be directly fetched during verification; the request returned a 521 fetch error. Therefore, no project-specific code or claims are taken from that exact page.

Accessible W5500 MicroPython reference:
Ayyoubzadeh ESP32-Wiznet-W5500-Micropython, which shows ESP32, W5500/W5100, MicroPython firmware, wiring, required driver files, and example WIZNET5K initialization.

Official WIZnet W5500 documentation and product page:
Used for W5500 hardwired TCP/IP stack, SPI up to 80 MHz, 10/100 Ethernet MAC/PHY, supported protocols, eight sockets, and 32 KB Tx/Rx buffer memory.

Official Microchip ENC28J60 product page and datasheet reference:
Used for ENC28J60 status, 10Base-T Ethernet controller description, SPI interface, and stand-alone Ethernet controller role.

Editorial workflow and source-handling rules followed the uploaded WIZnet UCC Curator Handover Notes.

9. Tags

WIZnet, W5500, ESP32, MicroPython, Ethernet, TCP/IP, Performance, SPI, Socket Programming, Commercial IoT, ENC28J60, Wired Networking

1. 제목

ESP32에서 WIZnet W5500을 사용해 상용 고성능 MicroPython Ethernet 노드를 구축하는 방법

2. 요약

이 글은 ESP32 계열 MCU와 WIZnet W5500을 사용한 상용 지향 MicroPython Ethernet 노드를 설명하며, 단순 연결성보다 성능에 초점을 둔다. W5500은 Ethernet offload device 역할을 한다. MCU는 MicroPython application을 실행하고, W5500은 hardwired TCP/IP stack, 10/100 Ethernet MAC/PHY, socket state, 내부 Tx/Rx buffering을 처리한다. 원본 CSDN Wenku 답변 페이지는 검증 과정에서 직접 가져올 수 없었으므로, 구현 설명은 접근 가능한 W5500 MicroPython reference material, 공식 WIZnet documentation, 공식 Microchip ENC28J60 product information을 기반으로 정리한다.

3. 프로젝트가 하는 일

접근 가능한 W5500 MicroPython reference pattern은 ESP32가 SPI를 통해 W5500 module에 연결되고, MicroPython code가 WIZnet interface를 초기화하며, chip/network information을 확인하고, DNS를 resolve한 뒤, W5500 socket layer를 통해 requests-style HTTP client를 사용하는 구조를 보여준다. 해당 repository는 목표를 ESP32를 W5500 Ethernet module에 연결하고 Python requests를 HTTP client로 사용하는 것으로 설명한다. 또한 필요한 MicroPython driver files와 ESP32-to-W5500 wiring, 즉 CS, SCK, MOSI, MISO, reset, power, ground 연결을 나열한다.

상용 제품에서는 이 구조가 telemetry, configuration, monitoring 또는 local control을 위한 wired Ethernet endpoint가 된다. ESP32는 MicroPython에서 application logic을 실행한다. 예를 들어 sensor reading, payload formatting, configuration handling, local protocol 실행, HTTP/MQTT endpoint로 data push를 수행한다. W5500은 network-facing behavior를 제공한다. 여기에는 Ethernet link, TCP/UDP protocol handling, socket state, packet buffer가 포함된다.

성능 목표는 단순한 raw throughput만이 아니다. Embedded commercial system에서 유용한 성능이란 predictable connection behavior, 낮은 firmware complexity, 줄어든 MCU-side network stack load, bounded memory use, 안정적인 socket recovery, cable removal, server timeout, gateway failure 이후의 반복 가능한 동작을 의미한다. W5500은 TCP/IP 처리를 Ethernet controller 내부로 이동시켜 MicroPython application과 MCU RAM이 전체 network stack을 직접 부담하지 않도록 돕는다.

4. WIZnet이 들어가는 위치

이 architecture에서 사용하는 WIZnet 제품은 W5500이다. WIZnet은 W5500을 외부 MCU와 최대 80 MHz SPI로 연결되는 hardwired TCP/IP stack Internet controller로 설명한다. W5500은 10/100 Ethernet MAC과 PHY를 통합하고, TCP, UDP, ICMP, IPv4, ARP, IGMP, PPPoE를 지원하며, 8개의 independent socket과 Tx/Rx buffer용 32 KB internal memory를 제공한다.

성능 관점에서 중요한 점은 역할 분담이다. W5500을 사용하면 MCU가 일반 Ethernet 통신을 위해 전체 software TCP/IP stack을 실행할 필요가 없다. MCU는 SPI를 통해 W5500과 통신하고 socket-level operation을 사용하며, W5500은 Ethernet protocol behavior와 socket state를 유지한다. 이 구조는 MicroPython 내부에서 직접 수행해야 하는 network processing 양을 줄여준다.

하지만 practical limit은 여전히 중요하다. W5500은 8개의 socket과 제한된 internal buffer memory를 제공하므로, 상용 firmware design에서는 socket ownership과 buffer expectation을 정의해야 한다. 예를 들어 socket 하나는 telemetry upload용, 하나는 local configuration용, 하나는 diagnostics용, 하나는 firmware 또는 service recovery용으로 예약할 수 있다. 제품이 socket을 임의로 열고 cleanup을 garbage collection이나 reboot behavior에 맡기면 실제 network fault 상황에서 성능이 저하된다.

5. 구현 참고 사항

정확한 Wenku page는 fetch error를 반환했기 때문에, 이 section은 해당 page의 code를 주장하지 않는다. 접근 가능한 ESP32/W5500 MicroPython repository는 검증된 reference pattern을 제공한다. 그 README.md는 WIZNET5K, SPI, CS, reset, W5500 socket module, requests wrapper를 사용하는 ESP32-W5500 setup을 보여준다.

README.md / main.py style usage의 검증된 reference pattern:

from wiznet5k import WIZNET5K
from machine import Pin, SPI
import wiznet5k_socket as socket
import sma_esp32_w5500_requests as requests

spi = SPI(2)
cs = Pin(5, Pin.OUT)
rst = Pin(34)
nic = WIZNET5K(spi, cs, rst)

requests.set_socket(socket, nic)

이 점이 중요한 이유는 application이 raw Ethernet frame processor로 작성되지 않기 때문이다. Firmware는 SPI를 통해 W5500을 초기화하고, socket implementation을 W5500 interface에 연결한 뒤, application이 higher-level network operation을 사용하게 한다.

동일한 repository는 성능과 관련 있는 bring-up sequence도 보여준다. Chip version 출력, MAC address 출력, local IP address 출력, DNS lookup 수행, socket layer를 requests wrapper에 연결하는 순서이다. 이러한 확인은 단순 debug message가 아니다. 상용 장치에서는 production diagnostics가 된다. 즉 application data를 보내기 전에 W5500 detection, MAC availability, IP acquisition, DNS function, socket interface readiness를 확인하는 절차가 된다.

ENC28J60과 비교하면 핵심 architecture 차이는 ENC28J60이 SPI interface를 가진 10Base-T Ethernet controller라는 점이다. Microchip은 ENC28J60을 host MCU용 Ethernet network interface로 사용하기 위한 stand-alone Ethernet controller로 설명한다. 그러나 ENC28J60은 W5500과 같은 hardwired TCP/IP socket engine을 제공하지 않는다. 따라서 ENC28J60을 사용할 경우 일반적으로 더 많은 protocol work가 MCU firmware 또는 외부 software stack에 남는다.

6. 실용 팁 / 주의점

SPI clock만이 성능 변수가 아니다. W5500은 high-speed SPI를 지원하지만, 실제 application performance는 MicroPython overhead, driver efficiency, socket buffer size, payload size, firmware가 socket state를 polling하는 빈도에도 영향을 받는다.

장기 유지 socket은 적고 명확하게 사용한다. W5500은 8개의 independent socket을 지원하지만, 상용 firmware에서는 function별로 socket을 예약하고 timeout, remote disconnect, link failure 이후 예측 가능하게 close/reopen해야 한다.

Buffer behavior에 맞춰 payload size를 정한다. 32 KB internal Tx/Rx memory는 유용하지만 무제한은 아니다. Firmware가 명시적으로 chunking하지 않는다면 unbounded HTTP response, oversized JSON, large blocking transfer는 피하는 것이 좋다.

Application traffic 전에 link와 IP를 확인한다. PHY link, IP address, gateway, DNS, server reachability를 각각 별도의 diagnostic step으로 다뤄야 한다. 그래야 field support에서 단순한 “network failed” message보다 원인을 쉽게 파악할 수 있다.

W5500 reset을 의도적으로 설계한다. Socket state가 stale 상태가 되었을 때 W5500을 controlled reset할 수 있는 경로를 추가한다. 상용 제품은 전체 MCU reboot에만 의존하지 않고 Ethernet controller를 복구할 수 있어야 한다.

실제 workload로 benchmark한다. Telemetry product, local TCP server, HTTP client, MQTT client는 network path에 서로 다른 부하를 준다. 실제 payload format을 사용해 connection time, reconnect time, request latency, sustained transfer, memory use를 측정해야 한다.

W5500과 ENC28J60을 BOM cost만으로 비교하지 않는다. ENC28J60은 단순 10Base-T design에 유용할 수 있다. 그러나 W5500의 hardwired TCP/IP stack, socket engine, 10/100 MAC/PHY, internal buffer는 firmware 부담을 줄이고 상용 유지보수성을 높이는 데 도움이 된다.

7. FAQ

왜 이 프로젝트에 WIZnet W5500을 사용하나?
W5500은 제품에 wired Ethernet, predictable socket behavior, 낮은 MCU-side TCP/IP workload가 필요한 경우 적합하다. W5500은 hardwired TCP/IP stack, 10/100 Ethernet MAC/PHY, 8개의 socket, internal Tx/Rx buffer memory를 제공한다.

W5500은 platform과 어떻게 연결되나?
검증된 ESP32 MicroPython reference에서 W5500은 SPI로 연결된다. 표시된 wiring은 ESP32 GPIO5를 CS로, GPIO18을 SCK로, GPIO23을 MOSI로, GPIO19를 MISO로, GPIO34를 reset으로 사용하며, 여기에 3.3 V와 ground가 추가된다. Board에 따라 pin 선택은 달라질 수 있지만, 필요한 interface는 SPI plus chip-select and reset이라는 점은 동일하다.

이 프로젝트에서 W5500의 역할은 무엇인가?
W5500은 Ethernet performance와 offload boundary 역할을 한다. ESP32는 MicroPython application과 high-level logic을 실행하고, W5500은 Ethernet MAC/PHY behavior, hardwired TCP/IP protocols, socket state, packet buffering을 처리한다.

초보자도 따라 할 수 있나?
Basic HTTP 또는 socket demo 수준에서는 가능하다. MicroPython flow가 직접적이기 때문이다. Driver file을 upload하고, SPI wiring을 구성하고, WIZNET5K를 초기화하고, IP information을 확인한 뒤, socket 또는 requests-style code를 사용하면 된다. 하지만 commercial use에서는 demo에서 멈추면 안 된다. Diagnostics, watchdog recovery, link check, timeout handling, clear socket ownership이 필요하다.

W5500은 ENC28J60과 어떻게 다른가?
ENC28J60은 SPI interface를 가진 stand-alone 10Base-T Ethernet controller로, host MCU에 Ethernet network-interface hardware를 제공하기 위한 장치이다. W5500은 hardwired TCP/IP stack, 8개의 socket, internal socket buffer를 가진 10/100 Ethernet controller이다. 실제로 MicroPython firmware가 더 적은 software stack 부담으로 higher-level socket behavior를 필요로 한다면 W5500이 더 적합한 경우가 많고, ENC28J60은 MCU-side protocol handling이 더 많이 필요하다.

8. 출처

원본 CSDN Wenku answer page:
https://wenku.csdn.net/answer/8bm96fihuc
검증 과정에서 이 page는 직접 fetch할 수 없었으며, request가 521 fetch error를 반환했다. 따라서 이 정확한 page에서 project-specific code나 claim을 가져오지 않았다.

접근 가능한 W5500 MicroPython reference:
Ayyoubzadeh ESP32-Wiznet-W5500-Micropython. 이 repository는 ESP32, W5500/W5100, MicroPython firmware, wiring, required driver files, example WIZNET5K initialization을 보여준다.

공식 WIZnet W5500 documentation 및 product page:
W5500 hardwired TCP/IP stack, 최대 80 MHz SPI, 10/100 Ethernet MAC/PHY, supported protocols, 8 sockets, 32 KB Tx/Rx buffer memory 정보에 사용했다.

공식 Microchip ENC28J60 product page 및 datasheet reference:
ENC28J60 status, 10Base-T Ethernet controller description, SPI interface, stand-alone Ethernet controller role 확인에 사용했다.

Editorial workflow와 source-handling rule은 업로드된 WIZnet UCC Curator Handover Notes를 따랐다.

9. 태그

WIZnet, W5500, ESP32, MicroPython, Ethernet, TCP/IP, Performance, SPI, Socket Programming, Commercial IoT, ENC28J60, Wired Networking