20.02.2013 Views

Sable CPU Module Specification

Sable CPU Module Specification

Sable CPU Module Specification

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 62: WRITE BLOCK<br />

Cycle<br />

sysClkOut1_h<br />

adr_h<br />

RAM Ctl<br />

data_h<br />

check_h<br />

cReq_h<br />

cWMask_h<br />

dOE_l<br />

dWSel_h<br />

cAck_h<br />

0 1 2 3 4 5<br />

Copyright © 1993 Digital Equipment Corporation.<br />

6<br />

LJ-01868-TI0<br />

1. The cReq_h pins are always idle in the system clock cycle immediately before<br />

the beginning of an external transaction. The adr_h pins always change to their<br />

final value (with respect to a particular external transaction) at least one <strong>CPU</strong><br />

cycle before the start of the transaction.<br />

2. The WRITE_BLOCK cycle begins. The 21064 has already placed the address of<br />

the block on adr_h. The 21064 places the longword valid masks on cWMask_h<br />

and a WRITE_BLOCK command code on cReq_h. The 21064 will clear dataA_<br />

h[4..3] and tagCEOE_h no later than one <strong>CPU</strong> cycle after the system clock edge<br />

at which the transaction begins. The 21064 clears dataCEOE_h[3..0] at least one<br />

<strong>CPU</strong> cycle before the system clock edge at which the transaction begins.<br />

3. The external logic detects the command, and asserts dOE_l to tell the 21064 to<br />

drive the first 16 bytes of the block onto the data bus.<br />

4. The 21064 drives the first 16 bytes of write data onto the data_h and check_h<br />

busses, and the external logic writes it into the destination. Although a single<br />

stall cycle has been shown here, there could be no stall cycles, or many stall<br />

cycles.<br />

<strong>CPU</strong> <strong>Module</strong> Transactions 151

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!