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
    • DDR Controller / PHY Split
    • Training & Timing Modes
      • Training & Timing Modes: Concepts
      • Training & Timing Modes: Integration
      • Training & Timing Modes: Debug
      • Training & Timing Modes: Interview
    • Refresh & Bandwidth Efficiency
    • Memory Interface Debug
    • Memory Interfaces (DDR / LPDDR / HBM): Tricky Q&A
  • PCIe & CXL17
  • Embedded Peripherals (I2C / SPI / UART)17
  • High-Speed I/O (USB / Ethernet / MIPI)17
  • Protocol Verification & Compliance21
  • Protocols Interview Prep5
  • Interface Protocols Cheatsheet
Loading lesson

←Memory Interfaces (DDR / LPDDR / HBM)
  1. Topics
  2. Bus Protocols
  3. Memory Interfaces (DDR / LPDDR / HBM)
  4. Training & Timing Modes
On this page

    Interface ProtocolsAll levels

    Training & Timing Modes

    Training is how the PHY finds timing margins that work across voltage, temperature, and process variation.

    • 4topics
    • 4lessons

    What you'll learn

    Training is how the PHY finds timing margins that work across voltage, temperature, and process variation.

    • DDR3/DDR4 write levelling relates DQS to CK; data deskew and centring relate DQ to DQS.

    • Store margins per corner, not just pass/fail.

    • Validate operating corners and follow the selected PHY's tracking/recalibration requirements.

    Connection

    PHY-side complement to controller scheduling. Critical for bring-up engineers.


    Key diagram

    Passing one tap is not measured margin

    Passing one tap is not measured margin. The lesson's sampled tap window is a measurement exercise, not a complete training algorithm or proof across untested corners.
    The lesson's sampled tap window is a measurement exercise, not a complete training algorithm or proof across untested corners.
    Check yourself Which evidence is lost if only the training PASS bit is kept?

    The pass-window boundaries, chosen setting, conditions and distance to failing settings.


    Study this topic

    1. Concepts — rules and mental models

    2. Integration — system contracts

    3. Debug — trace the first divergence

    4. Interview — explain and defend your answer

    PreviousNext: Training & Timing Modes: Concepts

    Up next

    Up nextTraining & Timing Modes: Concepts

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • DDR Controller / PHY Split
    • Refresh & Bandwidth Efficiency
    • Memory Interface Debug