--- title: "RIOT OS W5100/W5500 driver" url: "https://maker.wiznet.io/viktor/projects/riot-os-w5100-w5500-driver/" markdown_url: "https://maker.wiznet.io/viktor/projects/riot-os-w5100-w5500-driver/md" type: "UCC: User Created Content" author: "RIOT" author_url: "https://doc.riot-os.org/group__drivers__w5500.html" editor: "WIZnet" editor_url: "https://maker.wiznet.io/" original_author: "RIOT" original_url: "https://doc.riot-os.org/group__drivers__w5500.html" published: "2025-12-11" language: "en" hardware: ["WIZnet W5500"] likes: 0 views: 375 comments: 0 source: "WIZnet Makers (https://maker.wiznet.io/)" --- # RIOT OS W5100/W5500 driver > RIOT W5100/W5500 driver Original author: RIOT (source: https://doc.riot-os.org/group__drivers__w5500.html) ## Components - **WIZnet W5500** x 1 ([docs](https://docs.wiznet.io/Product/Chip/Ethernet/W5500)) WIZnet parts: W5500 ([Datasheet](https://docs.wiznet.io/Product/Chip/Ethernet/W5500/datasheet?utm_source=maker&utm_medium=project&utm_campaign=w5500), [product hub](https://maker.wiznet.io/products/w5500/)) ## Article ## **RIOT OS Provides Official Driver Support for the WIZnet W5500 Ethernet Controller** ### **Introduction** RIOT OS continues to establish itself as one of the most developer-friendly operating systems for resource-constrained IoT devices. Built with a microkernel architecture, modern networking capabilities, and an active open-source community, RIOT is rapidly becoming a preferred choice for academic research, low-power IoT devices, and hobbyist innovation. ![](https://maker.wiznet.io/upload/ckeditor5/201746982%5F1765467780%2Epng) The availability of an official **WIZnet W5500 driver** inside RIOT OS further expands its hardware ecosystem, giving developers access to reliable, SPI-based Ethernet connectivity for embedded devices. Before continuing, it is important to clarify: 👉 **This driver and its documentation are not created by WIZnet, and WIZnet does not claim any rights or ownership.** We are simply highlighting community work that benefits developers who use WIZnet hardware. --- ### **About RIOT OS — A Growing Platform for the IoT Era** RIOT OS positions itself as the “Linux of the IoT,” offering a POSIX-like API, full IPv6 networking, and modular drivers designed specifically for low-power MCUs. ![](https://maker.wiznet.io/upload/ckeditor5/201746982%5F1765467795%2Epng) Key indicators of RIOT's growth include: - **Hundreds of active contributors** across industry and academia - **Dozens of supported IoT hardware platforms**, from ARM Cortex-M to ESP32 to RISC-V - Used by **thousands of researchers**, developers, and students globally Backed by organizations such as the HAW Hamburg, INRIA, Freie Universität Berlin, and a vibrant open-source community RIOT’s networking stack (GNRC) is widely studied and used in research on low-power IPv6, 6LoWPAN, CoAP, and mesh protocols — making native Ethernet support especially valuable for testing and hybrid network topologies. --- ### **Author / Maintainer Introduction** RIOT’s W5500 driver is maintained by contributors within the RIOT OS networking and drivers community. These contributors specialize in: - lightweight networking stacks - low-power communication interfaces - SPI-based peripheral integration - embedded hardware abstraction While individual contributors may vary over time, the driver reflects the collaborative effort typical of RIOT’s well-structured open-source workflow. [![](https://maker.wiznet.io/upload/ckeditor5/201746982%5F1765467920%2Epng)](https://summit.riot-os.org/2025/) --- ### **Project Description — W5500 Driver for RIOT OS** RIOT OS offers a dedicated driver module for the **WIZnet W5500**, enabling Ethernet communication through a simple SPI interface. Key capabilities include: - Initialization and configuration of the W5500 chip - Sending and receiving Ethernet frames - Integration with RIOT’s GNRC networking subsystem - Support for buffer allocation, interrupt handling, and socket abstraction - Example applications demonstrating TCP/UDP communication using RIOT APIs #### **Important Note on TOE Support** Although the W5500 chip includes a **TCP/IP Offload Engine (TOE)**, the current RIOT driver primarily operates in **MACRAW or frame-level mode**, similar to many lightweight RTOS integrations. This means: - The driver exposes Ethernet frames to the RIOT networking stack - RIOT handles TCP/IP through its own software stack - TOE hardware acceleration is not fully leveraged in the current implementation The documentation acknowledges this design choice, and future enhancements could explore deeper integration with the W5500’s hardware sockets. --- ### **Why WIZnet Is Used in This Project** #### ✔ **Simple and Reliable SPI-Based Ethernet** The W5500 provides a stable, well-documented Ethernet interface without requiring complicated MAC/PHY integration. #### ✔ **Ideal for Low-Power MCUs** Because the chip offloads TCP/IP, it reduces processing overhead — even if the current driver uses MACRAW, the hardware capability remains valuable for future expansions. #### ✔ **Long-Term Industrial Stability** WIZnet chips are widely used in products requiring predictable, long-term uptime. #### ✔ **Perfect Match for RIOT’s Modular Design** RIOT’s driver system integrates well with SPI peripherals, making the W5500 a natural fit. --- ### **How This Can Benefit WIZnet** #### ⭐ **Presence in a Highly Academic and Research-Driven Community** RIOT is popular in universities, research labs, and experimental networking projects. Being part of its official driver set increases exposure among next-generation engineers. #### ⭐ **Strengthens WIZnet's Role in IoT and low-power networking** Developers exploring Ethernet connectivity for constrained devices can easily experiment using WIZnet hardware. #### ⭐ **Encourages future enhancements, including TOE-based integrations** As the RIOT community evolves, contributors may extend the driver to leverage full TCP/IP offload, increasing WIZnet’s visibility as a hardware-accelerated networking solution. #### ⭐ **More prototypes, publications, and open-source projects using WIZnet** RIOT is often used in: - academic prototypes - networking research papers - conference demonstrations - teaching material in embedded coursework --- Source: https://maker.wiznet.io/viktor/projects/riot-os-w5100-w5500-driver/