IPR-SDRAM/DDR2 Altera, IPR-SDRAM/DDR2 Datasheet - Page 43

• Manufacturer Part Number: IPR-SDRAM/DDR2
• Description: IP CORE Renewal Of IP-SDRAM/DDR2
• Manufacturer: Altera
• Type: MegaCorer

Specifications of IPR-SDRAM/DDR2

• Software Application: IP CORE, Memory Controllers, SDRAM
• Supported Families: Cyclone, HardCopy, Stratix
• Features: Data Mask Signals For Partial Write Operations, Bank Management Architecture
• Core Architecture: FPGA
• Core Sub-architecture: Cyclone, HardCopy, Stratix
• Rohs Compliant: NA
• Function: DDR2 SDRAM Controller
• License: Renewal License
• Lead Free Status / RoHS Status: na
• Lead Free Status / RoHS Status: na

Chapter 3: Functional Description
Device-Level Description
© March 2009 Altera Corporation
Designing Your Own Controller
The state machine that issues the read commands generates control_doing_rd
and it starts when the read command is issued to the memory and stays asserted for
the length of the burst. It is delayed inside the controller to cope with the following
options:
■
■
■
The datapath is generated with a pipeline to cope with CAS latency in each DQS
group rather than inside the controller. Duplicating this pipeline across the
bytegroups makes timing easier to meet on the critical postamble logic—the last
register in this pipeline feeds the postamble control register. If you design you own
controller, you need to generate the datapath for the right CAS latency, otherwise this
pipeline is the wrong length.
The enabling and disabling of the capture registers (controlled by the
control_doing_rd signal) is disabled in RTL simulation because it relies so heavily
on timing in the system to work. So in RTL simulation, the capture registers are
always enabled and varying the timing of the control_doing_rd signal does not
change the behavior of the datapath.You should use gate-level simulations to test the
exact timings of this signal if you design your own controller.
The same source that generates control_doing_rd generates the
local_rdata_valid signal and it is delayed inside the controller by the same
amount. In addition, it is delayed to take the following datapath options into account:
■
■
The local_rdata_valid signal is also delayed by 4 + R cycles, where R is the
resynchronization cycle as predicted by the wizard. For example, if the
resynchronization cycle is 2, Reclock resynchronized data to the positive edge is
turned on, and Insert intermediate resynchronization registers is turned off, the
local_rdata_valid signal should be seven cycles later than the
control_doing_rd signal (4 + 2 + 1 + 0 = 7).
The control_doing_wr signal controls the output enables on the DQ and DQS
pins. The state machine that issues the write commands generates it and it is delayed
inside the controller to cope with the following options:
■
■
■
For DDR SDRAM, the write latency is fixed at 1 clock cycle. You should issue the
control_doing_wr signal so that it starts when you issue the write command to the
memory and ensure it stays asserted for the length of the burst.
For DDR2 SDRAM, the write latency varies with the CAS latency, which the
controller takes into account and it delays the control_doing_wr signal to match.
You should issue the control_doing_wr signal (CAS latency – 2) clock cycles after
the write command and ensure it stays asserted for the length of the burst.
Insert pipeline registers on address and command outputs
Registered DIMM
Insert extra pipeline registers in the datapath
Reclock resynchronized data to the positive edge
Insert intermediate resynchronization registers
Insert pipeline registers on address and command outputs
Registered DIMM
Insert extra pipeline registers in the datapath
DDR and DDR2 SDRAM Controller Compiler User Guide
3–7