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
    • PCIe Layering & TLPs
    • Enumeration & Link Training
      • Enumeration & Link Training: Concepts
      • Enumeration & Link Training: Integration
      • Enumeration & Link Training: Debug
      • Enumeration & Link Training: Interview
    • CXL Attach Modes
    • PCIe / CXL Debug
    • PCIe & CXL: Tricky Q&A
  • Embedded Peripherals (I2C / SPI / UART)17
  • High-Speed I/O (USB / Ethernet / MIPI)17
  • Protocol Verification & Compliance17
  • Protocols Interview Prep5
  • Interface Protocols Cheatsheet
Loading lesson

←Enumeration & Link Training
  1. Topics
  2. Bus Protocols
  3. PCIe & CXL
  4. Enumeration & Link Training
  5. Enumeration & Link Training: Debug
On this page

    Interface ProtocolsAll levels

    Enumeration & Link Training: Debug

    Debug for Enumeration & Link Training.

    Primary debug scenario

    Symptom: Endpoint enumerates at x1 Gen3 instead of expected x4 Gen4. Same chip works on eval board.

    Triage steps

    1. Read LTSSM state history — where did width negotiation fail?

    2. Per-lane margin report: which lane(s) failed EQ?

    3. Compare package/board SI between eval and product.

    4. Check if retimer or switch in path has independent training issues.

    5. Compare physical margin, configured speed/width limits, reset and firmware settings before assigning the cause.

    Common pitfalls

    • Blaming software enumeration when PHY margin is the cause.

    • Skipping LTSSM history and lane margin reports.

    • Ignoring package/board differences between eval and product.

    Previous

    87 / 154

    Next: Enumeration & Link Training: Interview

    Up next

    Up nextEnumeration & Link Training: Interview

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Enumeration & Link Training: Concepts