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
    • MIPI CSI / DSI Overview
    • High-Speed I/O Debug
      • High-Speed I/O Debug: Concepts
      • High-Speed I/O Debug: Integration
      • High-Speed I/O Debug: Debug
      • High-Speed I/O Debug: Interview
    • High-Speed I/O (USB / Ethernet / MIPI): Tricky Q&A
  • Protocol Verification & Compliance17
  • Protocols Interview Prep5
  • Interface Protocols Cheatsheet
Loading lesson

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

    Interface ProtocolsAll levels

    High-Speed I/O Debug: Debug

    Debug for High-Speed I/O Debug.

    Primary debug scenario

    Symptom: 100G Ethernet works on eval board. 40% throughput on product with CRC errors.

    Triage steps

    1. Compare PHY per-lane margin: eval vs product.

    2. Compare package/board channel models and measured configuration against the eval path.

    3. Check if all lanes have similar margin — one outlier?

    4. Try lower speed — does CRC clean up?

    5. Correlate MAC/PCS/PHY counters, clocks, resets, lane mapping, receiver settings and identical traffic before assigning the board as cause.

    Common pitfalls

    • Picking maximum or geometric-centre EQ without a cornered sweep.

    • Treating CRC/FCS errors as proof of a PHY fault.

    • Ignoring temperature corner testing.

    Previous

    129 / 154

    Next: High-Speed I/O Debug: Interview

    Up next

    Up nextHigh-Speed I/O Debug: Interview

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • High-Speed I/O Debug: Concepts