Wiznet makers

ruilixin6

Published August 22, 2026 ©

117 UCC

0 VAR

0 Contests

0 Followers

0 Following

Original Link

Illustrated Ethernet Protocol: Error Types and Auto‑Negotiation

It covers common Ethernet errors and the auto‑negotiation workflow.

COMPONENTS
PROJECT DESCRIPTION

【Preliminary Note】The original hardware example in this article was written based on the RP2040. The actual hardware used in this hands-on demonstration features the W55RP20 as the main controller chip. The circuit logic and UF2 flashing operation principles are universally applicable, with only the main controller model differing. The original chip model mentioned in the circuit descriptions below is provided for reference purposes only.

Common Ethernet Error Types

Ethernet is one of the core technologies for modern network communication. Nevertheless, various errors may occur during actual operation. Below are common Ethernet error types and their descriptions:

Collision Collisions happen when two or more devices attempt to transmit data at the same time. This occurs frequently in half‑duplex Ethernet networks such as hub‑based networks.

Frame Error A data frame gets corrupted during transmission, resulting in mismatched checksum such as FCS.

Jumbo Frame Data frames exceeding the standard Ethernet frame length of 1518 bytes.

Runt Frame Frames shorter than 64 bytes, usually caused by collisions or hardware malfunctions.

CRC Error Cyclic Redundancy Check Error Mismatched frame CRC checksum, indicating data corruption during transmission.

Dropped Frame Frames are discarded when the buffer of a switch or router is full.

Duplex Mismatch Two ends of a network link are configured with different duplex modes, one port full‑duplex and the other half‑duplex.

  1. Auto‑Negotiation

Auto‑Negotiation is a feature defined in Ethernet standards. It automatically determines optimal connection parameters such as speed and duplex mode between Ethernet devices. This feature helps network devices communicate at the best possible performance and reduces manual‑configuration mistakes.

Workflow of Auto‑Negotiation is shown below:

1280X1280.JPEG

Auto‑Negotiation data frame

Initial Connection When two network devices such as a computer and a switch get connected, they exchange Auto‑Negotiation frames through the PHY physical layer to start the auto‑negotiation procedure.

Capability Exchange Each device sends capability frames advertising its supported speed and duplex modes. These frames are known as FLP Fast Link Pulse.

Select Optimal Configuration Based on exchanged capability frames, both devices select the highest mutually‑supported speed and the best available duplex mode, either full‑duplex or half‑duplex.

Apply Connection Parameters Devices configure their respective network interfaces according to negotiation results and start regular data communication.

Documents
Comments Write