---
title: "Wiznet W6100 Spin2 driver usage"
url: "https://maker.wiznet.io/Lihan__/projects/wiznet-w6100-spin2-driver-usage/"
markdown_url: "https://maker.wiznet.io/Lihan__/projects/wiznet-w6100-spin2-driver-usage/md"
type: "UCC: User Created Content"
author: "Rayman"
author_url: "https://forums.parallax.com/discussion/177801/wiznet-w6100-spin2-driver-usage"
editor: "WIZnet"
editor_url: "https://maker.wiznet.io/"
original_author: "Rayman"
original_url: "https://forums.parallax.com/discussion/177801/wiznet-w6100-spin2-driver-usage"
published: "2025-11-23"
language: "en"
likes: 0
views: 369
comments: 0
source: "WIZnet Makers (https://maker.wiznet.io/)"
---

# Wiznet W6100 Spin2 driver usage

> Wiznet W6100 Spin2 driver usage

Original author: Rayman (source: https://forums.parallax.com/discussion/177801/wiznet-w6100-spin2-driver-usage)

## Article

## **1. Why Parallax Propeller(P2) is different and still used despite limited references**

#### **How it differs from typical MCUs8 independent cores (COGs)** → true parallel processing without interrupts

**Precise timing control** → excellent for audio, video, and signal generation

**Uses its own language (Spin2)** → very different from common ARM-based MCUs

#### **Why people still use itParallel processing is extremely easyIdeal for timing-critical tasksCan generate many signals in software without extra hardwareFun and experimental platform for makers/education**

➡️ **In short: it excels at precise timing + parallel tasks that normal MCUs struggle with.**

---

## **2. Why references and resources are limitedSmall user base** (mainly hobbyists/education)

**Custom language + unique architecture** slows adoption

**No large ecosystem like ARMSmaller company → fewer official libraries/docs**

➡️ **It’s a niche MCU, so naturally the documentation is limited**

---

### 📄 **Parallax P2 + W6100 Integration Technical Summary**

This document is a **technical case study summarizing real-world issues and solutions encountered while integrating the WIZnet W6100 Ethernet chip with the Parallax Propeller 2 (P2) MCU**.
It covers multiple problems that occur when using W6100’s SPI/Parallel interface on P2’s unique architecture (COGs, byte-aligned I/O), and provides practical insights gained from resolving those issues.

---

## Issues (Short Statements)

**W6100 SPI/Parallel pin configuration confusionWeb server failing to serve HTML/image files correctlyFilesystem stops sending after the first fileDHCP randomly fails to obtain an IPParallel bus byte alignment issue causing incorrect W6100 ID read**

---

## Solutions for Each Issue

#### **① W6100 SPI/Parallel pin configuration confusionSolution:** Adjust pin definitions in W6100drv.spin2 to match the actual hardware

**Note:** Default pins conflict with uSD pins; A0/A1 interpreted incorrectly in SPI mode

---

#### **② HTML/Image file serving issueSolution:** Use `index.htm` instead of `index.html`, include `favicon.ico`, consider Edge browser behavior

**Note:** Edge does not treat index.html as the default document in this driver setup

---

#### **③ Filesystem stops sending after first fileSolution:** Remove `W6100.isdisconnected()` from the loop termination condition

**Note:** Incorrect disconnect detection prematurely ended file transfers

---

#### **④ DHCP instabilitySolution:** Add automatic retry every 5 seconds when no response is received

**Note:** Original driver lacked retry/time-out logic

---

#### **⑤ Parallel bus byte alignment issueSolution:**

Align DATA0 pin to a byte boundary (0/8/16/24)

Fix DPINS to match actual port byte index

**Note:** Wrong byte was read from INA, causing ID $61,$00 to become corrupted as $F7,$F7

---

## 3. Key Insights

**W6100’s parallel BUS is highly sensitive to MCU port structure (especially P2’s byte-oriented INA/OUTA).P2’s parallel COG architecture is powerful for Ethernet handling, but driver accuracy is critical.Real user feedback provides valuable data for improving WIZnet drivers and documentation.The P2 + W6100 combination is strong for real-time industrial protocols such as Modbus TCP.This case confirms that WIZnet Ethernet chips operate reliably even with non-standard MCUs.**

---

---

Source: https://maker.wiznet.io/Lihan__/projects/wiznet-w6100-spin2-driver-usage/