4.1.6 · D1Memory Technologies

Foundations — SDRAM and DDR (DDR2 - 3 - 4 - 5) evolution

1,760 words8 min readBack to topic

This page assumes nothing. If you have never seen "MHz", "64-bit bus", "ns", or "", start here and read top to bottom. Every symbol used in the parent topic is built below, in the order you need them.


1. A bit, a byte, and a bus width

Figure — SDRAM and DDR (DDR2 - 3 - 4 - 5) evolution

Why the topic needs : bandwidth is "how many bytes per second". Wider bus = more bytes per single transfer. To turn bits into bytes we divide by 8, which is why you will always see in the formulas.


2. Time, seconds, and the nanosecond (ns)

Why the topic needs ns: the parent note keeps quoting "the array access time is ~15 ns". That is the time the slow charge-buckets take to hand over their data. Holding this number lets you see how slow the core really is compared to the interface.


3. Frequency, Hertz, and the clock

Figure — SDRAM and DDR (DDR2 - 3 - 4 - 5) evolution

A clock is a square wave — it rises to "high", stays, falls to "low", stays, and repeats. This shape has two special moments per cycle: the rising edge (going up) and the falling edge (going down). Remember these two edges — the entire DDR ("Double Data Rate") trick lives on them.


4. Scientific notation: reading

Why the topic needs it: every bandwidth number is millions or billions. When the parent writes MB/s, it is just (100 million transfers) × (8 bytes each) = 800 million bytes per second.


5. Transfers per second, and MT/s

Why the topic splits "clock" from "transfers": for old SDR memory there is exactly one transfer per clock cycle, so transfers/sec . But DDR fires on both edges, giving two transfers per cycle. So transfers/sec . The label "DDR-400" is 400 MT/s, meaning the clock is only MHz.

Figure — SDRAM and DDR (DDR2 - 3 - 4 - 5) evolution

6. The slow core vs the fast interface, and "prefetch "

Why the topic needs : the master relationship of the whole page is The core clock stays put; the prefetch and I/O clock multiply the data rate up.


Prerequisite map

bit and byte

bus width w

nanosecond ns

slow array ~15 ns

clock and frequency f_clk

rising and falling edges

transfers per second

bandwidth = transfers x bytes

scientific notation 10^6

core vs interface split

prefetch n

DDR generation evolution

Read it as: bits and clocks at the top feed into transfers and bandwidth; the slow-array fact feeds the prefetch idea; together they explain the DDR evolution in the parent topic.


Equipment checklist

Test yourself — hide the right side and answer each.

How many bits are in a byte?
Exactly 8.
What does a 64-bit bus mean for the symbol ?
: 64 wires carry 64 bits (= 8 bytes) per transfer.
How do you turn a bus width into bytes-per-transfer?
Divide by 8, giving .
How long is 1 nanosecond in seconds?
s (one billionth of a second).
What does stand for?
The clock frequency of the memory bus, in Hz/MHz.
What is MHz in ticks per second?
One million () cycles per second.
What are the two special moments in each clock cycle?
The rising edge and the falling edge.
What is the period of a 200 MHz clock?
ns.
What does mean as an ordinary number?
1,000,000 (one million).
What is the difference between MHz and MT/s?
MHz counts clock ticks/sec; MT/s counts transfers/sec. For DDR, MT/s = 2 × MHz.
Why does DDR give 2 transfers per clock cycle?
It fires on both the rising and falling edge.
What is prefetch ?
How many bits per wire are grabbed from the slow array in parallel per access.
Which part of a DRAM chip stayed ~constant in speed, and which sped up?
The array (core, ~15 ns) stayed constant; the I/O interface sped up.

Connections