How to implement high-speed 667 Mbps DDR2 interfaces with FPGAs
By Seyi Verma, Altera
December 05, 2006
To achieve a robust high data rate, such as 667 Mbps in a DDR2 system, a dynamic auto-calibration PHY IP core significantly simplifies the memory interface design.
December 05, 2006
To achieve a robust high data rate, such as 667 Mbps in a DDR2 system, a dynamic auto-calibration PHY IP core significantly simplifies the memory interface design.
DDR2 is the second generation of double data rate (DDR) synchronous dynamic random access memory (SDRAM) capable of significantly higher data bandwidth. DDR2 improvements include lower power consumption, improved signal quality, and on-die termination schemes. Compared to the previous generation single data rate (SDR) SDRAM memories, DDR2 SDRAM memories transfer data on every edge of the clock, use the SSTL18 class II I/O standard with memories from up to 4 Gbits of data, and is widely available as modules such as dual in-line memory modules (DIMMs) or as components.
To read the full article, click here
Related Semiconductor IP
- DDR2 SDRAM Controller
- DDR and DDR2 SDRAM Controller Intel® FPGA IP Core
- DDR and DDR2 SDRAM Controller with ALTMEMPHY Intel® FPGA IP
- DDR2 Monitor Verification IP
- DDR2 Synthesizable Transactor
Related White Papers
- Implementing custom DDR and DDR2 SDRAM external memory interfaces in FPGAs (part 1)
- Redefining Speed: How FPGAs are shaping the future of high-frequency trading
- How to implement *All-Digital* analog-to-digital converters in FPGAs and ASICs
- Choosing serial interfaces for high speed ADCs in medical apps
Latest White Papers
- DRsam: Detection of Fault-Based Microarchitectural Side-Channel Attacks in RISC-V Using Statistical Preprocessing and Association Rule Mining
- ShuffleV: A Microarchitectural Defense Strategy against Electromagnetic Side-Channel Attacks in Microprocessors
- Practical Considerations of LDPC Decoder Design in Communications Systems
- A Direct Memory Access Controller (DMAC) for Irregular Data Transfers on RISC-V Linux Systems
- A logically correct SoC design isn’t an optimized design