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
    • 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

←Bus Protocols
  1. Topics
  2. Bus Protocols
  3. Memory Interfaces (DDR / LPDDR / HBM)
On this page

    Interface ProtocolsAll levels

    Memory Interfaces (DDR / LPDDR / HBM)

    Controller/PHY split, training, timing modes, refresh, bank conflicts, bandwidth efficiency, and memory subsystem debug.

    • 5topics
    • 17lessons

    Section overview

    Controller/PHY split, training, timing modes, refresh, bank conflicts, bandwidth efficiency, and memory subsystem debug.

    Topics

    1. DDR Controller / PHY Split

    2. Training & Timing Modes

    3. Refresh & Bandwidth Efficiency

    4. Memory Interface Debug

    Related topics

    • Protocols course hub

    After this section

    Try the section checkpoint, then review the Q&A

    Section context

    DDR bandwidth is scheduler + PHY: rows, banks, refresh, and turnarounds eat headline data rate.

    Illustrative review scenario

    Illustrative review: a video replay's long-run bandwidth looked sufficient, but a measured service gap overflowed its ingress buffer. Controller events, arbitration, backpressure and low-power/refresh state remained hypotheses until correlated on one timeline.

    PreviousNext: DDR Controller / PHY Split

    Up next

    Up nextDDR Controller / PHY Split

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • How to Use This Course
    • Protocol Metrics Reference
    • Protocols Glossary