Article ID: 000077104 Content Type: Troubleshooting Last Reviewed: 08/21/2023

Why is tRCD larger than expected with my DDR3 UniPHY controller?

Environment

  • Quartus® II Subscription Edition
  • DDR3 SDRAM Controller with UniPHY Intel® FPGA IP
  • BUILT IN - ARTICLE INTRO SECOND COMPONENT
    Description

    You may see a larger-than-expected tRCD delay in DDR3 UniPHY quarter-rate memory controllers when the transactions are generated by the controller clock, which is running at a quarter of the memory clock rate (1 ctl_clk = 4 mem_ck).

     

    Resolution

    The controller has the ability to issue 2 commands per controller clock, one-row commands like ACTIVATE or PRECHARGE and one-column command like WRITE or READ. When tRCD is 11 that refers to 11 mem_ck or 2.75 (11/4) ctl_clk.

    This value is rounded up to 3 ctl_clk or 12 mem_ck. Additionally, each controller clock can be divided into four phases, a phase for each mem_ck cycle occurring per controller clock. The controller is designed to send row commands during phase one and column commands during phase three of each controller clock cycle. This adds an additional 2 mem_ck of delay to tRCD. For this example, the final delay for tRCD is 12 2 or 14 mem_ck.

    Related Products

    This article applies to 15 products

    Stratix® V GS FPGA
    Arria® V GZ FPGA
    Arria® V SX SoC FPGA
    Cyclone® V ST SoC FPGA
    Cyclone® V SX SoC FPGA
    Cyclone® V GT FPGA
    Stratix® V GX FPGA
    Stratix® V GT FPGA
    Cyclone® V GX FPGA
    Arria® V ST SoC FPGA
    Arria® V GX FPGA
    Arria® V GT FPGA
    Cyclone® V SE SoC FPGA
    Cyclone® V E FPGA
    Stratix® V E FPGA