17.05.2015 Views

~ National ~ Semiconductor - Al Kossow's Bitsavers

~ National ~ Semiconductor - Al Kossow's Bitsavers

~ National ~ Semiconductor - Al Kossow's Bitsavers

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.

8.0 Remote Interface and Arbitration System (Continued)<br />

Arbitration Access Termination<br />

REM-RD~~ __________________--J;---<br />

CMD 'lllllI<br />

WZZZ<br />

XACK ' ....._____________ 1<br />

ili 1 '....._-<br />

AD<br />

RIC<br />

TL/F/9336-80<br />

(a) Remote Read Timing (RAE = 0)<br />

Arbitration Access Termination<br />

REM-WR~~ __________________ ~;---<br />

CMD 'lllllI<br />

XACK<br />

ili<br />

AD<br />

,'--____<br />

.J1<br />

I<br />

WZZZ<br />

'....._-<br />

RIC ) ( New RIC<br />

TLiF/9336-81<br />

(b) Remote Write Timing (RAE = 0)<br />

7 6 5 4<br />

BIS SS FBW LR<br />

3 2 1 0<br />

LW lliIi±li±J<br />

Memory Select Bits<br />

00 - Data Memory<br />

01 - Instruction Memory<br />

10 - PC low byte<br />

11 - PC high byte<br />

Reads or writes of Data Memory (DMEM) are preceded by<br />

setting the Memory Select bits in {RICl for a DMEM access:<br />

[MS1,O] = 00. After that, the RP simply reads or<br />

writes to BCP Data Memory as many times as it needs to. A<br />

DMEM access, as well as a {RICl access, can be made<br />

while the BCP CPU is executing instructions. <strong>Al</strong>l other accesses<br />

must be executed with the BCP CPU stopped.<br />

The timing for a Data Memory read and write are shown in<br />

Figure 18. The access is initiated by asserting RAE and<br />

REM-RD or REM-WR while CMD is low. The BCP responds<br />

by bringing its address and data lines into TRI-STATE and<br />

allowing the RP to control DMEM. READ is asserted in the<br />

Access Phase of a Remote Read (a). It will stay low for a<br />

minimum of one T -state, but can be extended by adding<br />

programmable data wait states or by taking WAIT low.<br />

WRITE is asserted in the Access Phase with a remote write.<br />

It too is a minimum of one T-state and can be increased by<br />

adding programmable wait states or by taking WAIT low.<br />

Figure 19(c) shows the data path from the Program Counter<br />

to the AD bus. Both high and low PC bytes can be written or<br />

read through AD. The RP has independent control of the<br />

high and low bytes of the Program Counter-the byte being<br />

accessed is specified in the Memory Select bits. The high<br />

byte of the PC is accessed by setting [MS1-0] = 11. Setting<br />

[MS1-0] = 10 allows access to the low byte of the PC.<br />

After the Memory Select bits are set by a Remote Write to<br />

{RICl, the byte selected can be read or written by the RP<br />

by executing a Remote Access with CMD low. This type<br />

access as well as the instruction memory access must be<br />

executed with the BCP CPU idle. Four accesses by the RP<br />

are necessary to read or write both the high and low bytes<br />

of the PC. Timing for a PC access is shown in Figure 19(aj<br />

and (b). The PC becomes valid on a Remote Read (aj one<br />

T -state after LCL rises and one T -state before XACK rises.<br />

AD is in TRI-STATE while LCL is high for a Remote Write<br />

(bj. Time in the Access Phase is two T-states if WAIT is not<br />

asserted.<br />

(c) RIC to AD Connectivity<br />

TL/F/9336-82<br />

FIGURE 17. Generic RIC Access<br />

2-145

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

Saved successfully!

Ooh no, something went wrong!