DRAM & Memory Design · All levels

Vref, Eye Margin, and Calibration Closure: Review Checklist

Review Checklist for Vref, Eye Margin, and Calibration Closure.

Review checklist

Review Checklist for Vref, Eye Margin, and Calibration Closure focuses on Voltage-time eye center offsets and pass-region width from margin sweeps around trained operating points.. The purpose is to turn memory observations into mechanism-backed actions with explicit owners and release-safe validation.

  • Workload scope and SLA targets are explicit.

  • Environment tags are locked and reproducible.

  • First failing transition is proven by command-level evidence.

  • Owner and rollback criteria are documented.

  • Validation matrix covers performance, stability, and reliability.

  • Owners signed: DDR PHY architect, SI/PI engineer, post-silicon validation owner, memory controller owner, reliability owner.

DRAM deep dive

PHY training quality sets real timing margin through write leveling, read gate alignment, and Vref calibration.

Concept diagram

diagram
DDR PHY TRAINING FLOW

write leveling -> read gate -> per-bit deskew -> Vref calibration -> margin validate

Metric graph

diagram
MARGIN EROSION SOURCES

channel skew drift    █████
voltage/temperature   ████
board SI noise        ███

Reports and artifacts

  • training margin histogram

  • DQ/DQS skew log

  • Vref sweep report

  • retrain trigger incident timeline

Mini case study

A board spin passed cold boot but failed warm retrain due to narrowed DQ eye margins on one byte lane.

Debug branches

  • Compare byte-lane margins across thermal corners

  • Correlate retrain events with power-state transitions

  • Confirm SI fixes before loosening PHY timing guards

Senior review question

Ask: which latency, bandwidth, and reliability evidence proves this DRAM topic is closed under real traffic?

Key takeaways

  • Always tie controller and PHY counter shifts to application latency and throughput outcomes.

  • Lock firmware timing profile, thermal condition, and DIMM state before comparing DRAM captures.

Common pitfalls

  • Chasing peak bandwidth while ignoring p99 latency and fairness tails.

  • Changing timing guardbands without separating SI noise from scheduling issues.

  • Declaring closure without reliability gates, fault injection, and regression replay.

Review checklist explanation

A checklist here protects against false closure. Every item should map to a known memory failure mode.

For Vref, Eye Margin, and Calibration Closure, minimum checklist: workload scope, Voltage-time eye center offsets and pass-region width from margin sweeps around trained operating points., artifact evidence (Margin shmoo plots (delay x Vref), eye-width/eye-height summary tables, and calibration decision logs.), bottleneck class, owner, rollback path, and corner-matrix validation.

If controller or firmware changed, include fairness and RAS checks. If PHY or package assumptions changed, include SI/PI and thermal guardband evidence.