Table of Contents
Advertisement
The optional use of the EXTEND signal has been added to the interface to facilitate interfacing slower,
older DMA controller designs. EXTEND may only be used in single transfer read cycles to extend the
time valid data is on the data bus. During an access with EXTEND asserted, the DRAM controller
presents valid data on the bus with READY asserted. The valid data remains on the bus and READY
remains asserted until the DRAM controller samples EXTEND negated at a rising edge of the PMCLK.
The controller then terminates the read cycle.
Assert BLAST throughout the cycle. Using EXTEND during a burst access is not allowed and will
cause the DRAM controller to function improperly.
EXTEND should be used during write cycles. Squall II Module logic can be used to delay the assertion
of ADS until valid data is on the bus, making the use of EXTEND unnecessary. The DRAM controller
will not function correctly if EXTEND is asserted during write cycles.
Name
Minimum
Maximum
t1
3
t2
10
t3
0
t4
5
t5
3
t7
10
t8
0
t9
0
t10
0
t11
0
Figure 5-7, Squall II Master Read and Write Timing Diagram shows one wait state accesses.
The number of wait states depends on the clock frequency and memory speed. Refresh cycles may
delay READY up to 10 additional clock cycles. Squall II Modules should be designed to handle fewer
wait states. Future base boards may incorporate faster memory systems.
Table 5-5. Squall II Module Master Timing
10
Clock to Output SQBG
--
Setup to clock rising edge for SQBR, S_ADS, S_BLAST, S_A31:2, S_W/R,
S_BE3:0
20
Clock to output D31:0, Read Cycle
--
D31:0 hold from clock, Read Cycle
10
Clock to Output READY
--
Write Data Setup to Clock
--
Write Data Hold from Clock
30
SQBG Inactive to control signals three-stated
--
Hold from clock rising edge for SQBR, S_ADS, S_BLAST, S_A31:2,
S_W/R, S_BE3:0
--
SQBR asserted to control outputs driven
SQUALL II MODULE INTERFACE
Comment
5-13
Advertisement
Table of Contents
