IBM0625164GT3B IBM0625404GT3B
IBM06254B4GT3B IBM0625804GT3B
Advance
256Mb Double Data Rate Synchronous DRAM
Data from any Read burst may be truncated with a Burst Terminate command, as shown on Terminating a
Read Burst: CAS Latencies (Burst Length = 8) on page 26. The Burst Terminate latency is equal to the read
(CAS) latency, i.e. the Burst Terminate command should be issued x cycles after the Read command, where
x equals the number of desired data element pairs.
Data from any Read burst must be completed or truncated before a subsequent Write command can be
issued. If truncation is necessary, the Burst Terminate command must be used, as shown on Read to Write:
CAS Latencies (Burst Length = 4 or 8) on page 27. The example is shown for t
(min). The t
(max)
DQSS
DQSS
case, not shown here, has a longer bus idle time. t
Writes.
(min) and t
(max) are defined in the section on
DQSS
DQSS
A Read burst may be followed by, or truncated with, a Precharge command to the same bank (provided that
Auto Precharge was not activated). The Precharge command should be issued x cycles after the Read com-
mand, where x equals the number of desired data element pairs (pairs are required by the 2n prefetch archi-
tecture). This is shown on Read to Precharge: CAS Latencies (Burst Length = 4 or 8) on page 28 for Read
latencies of 2 and 2.5. Following the Precharge command, a subsequent command to the same bank cannot
be issued until t is met. Note that part of the row precharge time is hidden during the access of the last data
RP
elements.
In the case of a Read being executed to completion, a Precharge command issued at the optimum time (as
described above) provides the same operation that would result from the same Read burst with Auto Pre-
charge enabled. The disadvantage of the Precharge command is that it requires that the command and
address busses be available at the appropriate time to issue the command. The advantage of the Precharge
command is that it can be used to truncate bursts.
©IBM Corporation. All rights reserved.
Use is further subject to the provisions at the end of this document.
29L0011.E36997
10/99
Page 25 of 75
IBM [ IBM ]
