Hardware Measurements - Hardware Measurements - 1.0 English - PG353

Versal Adaptive SoC Soft DDR4 SDRAM Memory Controller LogiCORE IP Product Guide (PG353)

Document_ID
PG353
Release_Date
2025-06-25
Version
1.0 English

If the design is stuck in the Write Latency stage, the issue could be related to either the write or the read. Determining whether the write or read is causing the failure is critical. The following steps should be completed.

  1. To trigger on the start of Write Latency Calibration, set the trigger to (cal_r*_status[28] = R for Rising Edge).
  2. To trigger on the end of Write Latency Calibration, set the trigger to (cal_r*_status[29] = R for Rising Edge). To look at each byte, additionally add a trigger on dbg_cmp_byte and set to the byte of interest.
  3. To ensure the writes are correct, observe the write DQS to write DQ relationship at the memory using high quality scope and probes. During Write Latency, a write is followed by a read so care needs to be taken to ensure the write is captured. If there is a failing bit, determining the write DQS to write DQ relationship for the specific DQ bit is critical. The write ideally has the DQS center-aligned in the DQ window. Misalignment between DQS and DQ during Write Calibration points to an issue with Write DQS Centering calibration. Review the Debugging Write DQS to DB/DBI Centering Failures section.
  4. If the DQ-DQS alignment looks correct, next observe the we_n to DQS relationship at the memory during a write again using high quality scope and probes. The we_n to DQS delay must equal the CAS Write Latency (CWL).
  5. Using high quality scope and probes, verify the expected pattern (FF00AA5555AA9966) is being written to the DRAM during a write and that the expected pattern is being read back during the first Write Calibration read. If the pattern is correct during write and read at the DRAM, verify the DQS-CK alignment. During Write Calibration, these two signals should be aligned. Write Leveling aligned these two signals which has successfully completed before Write Latency.
  6. Probe ODT and we_n during a write command. For ODT to be properly powered on in the memory, ODT must assert before the write command.
  7. Probe DM to ensure it is held low during calibration. If a board issue exists causing DM to improperly assert, incorrect data can be read back during calibration causing a write calibration failure. An example of a board issue on DM is when DM is not used and tied low at the memory with improper termination.
  8. Using the Vivado Hardware Manager and while running the Memory IP Example Design with Debug Signals enabled, set the trigger.
    • To trigger on the start of Write Latency Calibration, set the trigger to (cal_r*_status[28] = R for Rising Edge).
    • To trigger on the end of Write Latency Calibration, set the trigger to(cal_r*_status[29] = R for Rising Edge). To look at each byte, additionally add a trigger on dbg_cmp_byte and set to the byte of interest.

The following simulation examples show how the debug signals should behave during successful Write Latency Calibration.

Figure 1. RTL Debug Signals during Write Latency Calibration #1
Figure 2. RTL Debug Signals during Write Latency Calibration #2