![Digital Equipment Alpha 21164PC Hardware Reference Manual Download Page 138](http://html.mh-extra.com/html/digital-equipment/alpha-21164pc/alpha-21164pc_hardware-reference-manual_2498508138.webp)
4–50
Clocks, Cache, and External Interface
29 September 1997 – Subject To Change
21164PC Interface Restrictions
4.9.5.3 FILL to Private READ or WRITE Operation
At the end of the fill, the 21164PC does not begin to drive the data bus until the fifth
cpu_clk cycle after the sysclk that loads the last dack_h (refer to Figure 4–25). The
21164PC does not assert data_ram_oe_l until the fifth cycle after the sysclk that
loads the last dack_h.
Systems requiring more time to turn off their drivers must not send any more
requests and must use idle_bc_h and data_bus_req_h at the end of the fill to pro-
vide adequate write-to-read spacing to avoid data bus contention.
Figure 4–25 FILL to Private READ or WRITE Operation
4.10 21164PC Interface Restrictions
This section lists restrictions on the use of 21164PC interface features.
4.10.1 Fill Operations After Other Transactions
For a system Bcache read operation (Bcache victim or a system-initiated data move-
ment) followed by a fill operation, the earliest assertion of fill_h by the system is
dependent upon the CBOX_CONFIG<BC_REG_REG> bit to avoid a read-to-write
data bus contention. When the BC_REG_REG bit is set, the 21164PC will deassert
data_ram_oe_l a full sysclk cycle after the final dack_h is detected to allow the
system adequate time to sample the Bcache read data. See Section 4.9.5.2 for timing
diagrams and assumptions that must be met by the system.
PCA018
dack_h
index_h<21:4>
cpu_clk
data_h<127:0>
data_ram_oe_l
D0
I0
N
sys_clk_out1_h
I3
D3
N+3
N+1
N+2
N+4
N+5