Data Sheet.
HY[B/E]18L512160BF-7.5
512-Mbit Mobile-RAM
2.4.6.4
WRITE to READ
A WRITE burst may be followed by, or truncated with a READ command. The READ command can be performed to the same
or a different (active) bank. With the registration of the READ command, data inputs will be ignored and no WRITE will be
performed, as shown in Figure 33.
FIGURE 33
WRITE to READ Timing
#,+
72)4%
./0
./0
2%!$
./0
./0
./0
./0
#OMMAND
!DDRESS
"A !ꢀ
#OL N
"A !ꢀ
#OL B
#,ꢃꢉ
(IGHꢋ:
$) N
$) N
$) Nꢈꢊ
$) Nꢈꢊ
$) Nꢈꢉ
$/ B
$/ Bꢈꢊ
$/ Bꢈꢉ
$1
$1
7RITE DATA
ARE IGNORED
#,ꢃꢇ
(IGHꢋ:
$) Nꢈꢉ
$/ B
$) Bꢈꢊ
"A !ꢀ #OL N ꢁBꢂ ꢃ BANK !ꢀ COLUMN N ꢁBꢂ
$) N ꢃ $ATA )N TO COLUMN Nꢄ $/ B ꢃ $ATA /UT FROM COLUMN Bꢄ
"URST ,ENGTH ꢃ ꢅ IN THE CASE SHOWNꢆ
ꢃ $ONgT #ARE
ꢇ SUBSEQUENT ELEMENTS OF $ATA )N ꢁ/UTꢂ ARE PROVIDED IN THE PROGRAMMED ORDER FOLLOWING $) N ꢁ$/ Bꢂꢆ
$) Nꢈꢇ IS IGNORED DUE TO 2%!$ COMMANDꢆ .O $1- MASKING REQUIRED AT THIS POINTꢆ
2.4.6.5
WRITE to PRECHARGE
A WRITE burst may be followed by, or truncated with a PRECHARGE command to the same bank, provided that Auto
Precharge was not activated. This is shown in Figure 34.
The PRECHARGE command should be issued tWR after the clock edge at where the last desired data element of the WRITE
burst was registered. Additionally, when truncating a WRITE burst, DQM must be pulled to mask input data presented during
tWR prior to the PRECHARGE command. Following the PRE-CHARGE command, a subsequent ACTIVE command to the
same bank cannot be issued until tRP is met.
In the case of a WRITE 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 WRITE burst with Auto Precharge enabled. The
disadvantage of the PRECHARGE command is that it requires that the command and address busses to 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.
Rev. 1.22, 2006-12
34
01132005-06IU-IGVM
QIMONDA [ QIMONDA AG ]
