Sable CPU Module Specification
Sable CPU Module Specification
Sable CPU Module Specification
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Copyright © 1993 Digital Equipment Corporation.<br />
There are special arbitor modes of operation where the bus priority algorithm is<br />
modifed. In particular, a <strong>CPU</strong> or I/O mode can gaurantee exclusive ownership of the<br />
system bus by keeping its appropriate request line aserted. Normal arbitration protocol<br />
requires that the request signal deassert for at least one cycle before reasserting<br />
if exclusive bus ownership is not required. This deassertion and reassertion can occur<br />
during an existing cycle so that back-to-back arbitration is still granted to the<br />
requesting node if there are no other requesters for the system bus.<br />
Both <strong>CPU</strong> and I/O modes may be allowed this mode of operation, however DECchip<br />
21064 and DECchip 21064-A275 implementations will have this feature disabled for<br />
<strong>CPU</strong> requests. Only I/O will be allowed to enter the Exclusive access mode.<br />
During normal operation for <strong>Sable</strong> DECchip 21064 and DECchip 21064-A275 systems,<br />
the <strong>Sable</strong> bus arbitor will monitor bus activity and insert a single idle cycle<br />
after the fifth consecutive back-to-back transaction. This feature gaurantees that a<br />
<strong>CPU</strong> is never locked out of its own backup cache and is gauranteed to make progress.<br />
There is also a debug arbitration feature available by writing to bit in the System<br />
Bus Control Register (CSR6–CBCTL) which forces the injection of two idle bus cycles<br />
between every bus transaction.<br />
Table 52: <strong>Sable</strong> Arbitration Latency<br />
Node Latency (Bus Cycles)<br />
<strong>CPU</strong>0<br />
<strong>CPU</strong>1<br />
<strong>CPU</strong>2<br />
<strong>CPU</strong>3<br />
Latency From EV_Req to Cobra Bus cycle 0<br />
3-4<br />
4-5<br />
4-5<br />
4-5<br />
Node Latency (Bus Cyles)<br />
IO0(T2)<br />
IO1(XIO)<br />
Latency From I/O req to Cobra Bus cycle 0<br />
4.15 System-bus CRESET L Generation<br />
3<br />
3<br />
System-bus CRESET L is generated on Cobra <strong>CPU</strong> 0 module. It is asserted when<br />
either async_reset from the Standard I/O module is asserted, the System-bus or the<br />
21064 oscillator on <strong>CPU</strong> 0 stop, or the 3.3V supply on <strong>CPU</strong> 0 goes under voltage.<br />
The clock detect circuits on the <strong>CPU</strong> module will guarantee that the oscillator generating<br />
the clocks for the module have been running for at least 20ms. This is to allow<br />
enough time to for the oscillators to stabilize.<br />
136 Functions located elsewhere on the <strong>CPU</strong> module