Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Protocol Metrics Reference
  • Protocols Glossary
  • Reading Path
  • Protocol Fundamentals25
  • AMBA Family (APB / AHB / AXI)17
  • Coherence Fabrics (ACE / CHI)17
  • Memory Interfaces (DDR / LPDDR / HBM)17
  • PCIe & CXL17
  • Embedded Peripherals (I2C / SPI / UART)17
  • High-Speed I/O (USB / Ethernet / MIPI)17
    • USB Link & Packet Model
    • Ethernet MAC / PHY Basics
      • Ethernet MAC / PHY Basics: Concepts
      • Ethernet MAC / PHY Basics: Integration
      • Ethernet MAC / PHY Basics: Debug
      • Ethernet MAC / PHY Basics: Interview
    • MIPI CSI / DSI Overview
    • High-Speed I/O Debug
    • High-Speed I/O (USB / Ethernet / MIPI): Tricky Q&A
  • Protocol Verification & Compliance17
  • Protocols Interview Prep5
  • Interface Protocols Cheatsheet
Loading lesson

←Ethernet MAC / PHY Basics
  1. Topics
  2. Bus Protocols
  3. High-Speed I/O (USB / Ethernet / MIPI)
  4. Ethernet MAC / PHY Basics
  5. Ethernet MAC / PHY Basics: Debug
On this page

    Interface ProtocolsAll levels

    Ethernet MAC / PHY Basics: Debug

    Debug for Ethernet MAC / PHY Basics.

    Primary debug scenario

    Symptom: Ethernet link up at 100G. High CRC error rate. TCP retransmits. Throughput 40% of line rate.

    Triage steps

    1. Measure MAC FCS/CRC errors over a defined interval and correlate them with PHY/PCS counters and captured traffic.

    2. PHY status: per-lane BER, eye margin, temperature.

    3. For a lane-specific error pattern, compare channel margin, lane mapping, clocks and receiver configuration before deciding the cause.

    4. Try lower speed (50G/25G) — does CRC improve?

    5. Treat narrow margin as a hypothesis to test with controlled settings and traffic; clean counters may reflect the observation point or test duration.

    Common pitfalls

    • Assigning FCS errors to the PHY without correlating PCS, interface, configuration and physical evidence.

    • Link up doesn't mean clean link — check error counters.

    • Ignoring per-lane margin in multi-lane Ethernet.

    Previous

    121 / 154

    Next: Ethernet MAC / PHY Basics: Interview

    Up next

    Up nextEthernet MAC / PHY Basics: Interview

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Ethernet MAC / PHY Basics: Concepts