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.

~ r-----------------------------------------------------------------------,<br />

-=:I'<br />

-=:I'<br />

CO)<br />

co<br />

a..<br />

C<br />

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

In addition, WAIT can delay the rising edge of XACK indefinitely.<br />

One T-state after XACK rises, (RIC) will once again<br />

be active on AD. Timing is similar for a Remote Write. AD is<br />

in TRI-STATE while LCL is high. LCL is asserted for a minimum<br />

of three T-states, but can be extended by instruction<br />

wait states and the WAIT pin. IWR clocks the instruction<br />

into memory during the write of the high byte. The Instruction<br />

Address (PC) is incremented about one T-state after<br />

LCL falls on a high byte access for both Remote Reads and<br />

Writes.<br />

Soft-loading Instruction Memory is accomplished by first<br />

setting the BCP Program Counter to the starting address of<br />

the program to be loaded. The Memory Select bits are then<br />

set to IMEM. BCP instructions can then be moved from the<br />

Remote Processor to the BCP-Iow byte, high byte-until<br />

the entire program is loaded.<br />

INTERFACE MODES<br />

The BCP will support TRI-STATE buffers or latches between<br />

the Remote Processor and the BCP. The choice between<br />

buffers and latches depends on the type of system<br />

that is being interfaced to. Latches will help the faster system<br />

from slowing to the speed of the slower system. Buffers<br />

can be used if the Remote Processor (RP) requires that<br />

data be handshaked between the systems.<br />

Figure 21 shows the timing of Remote Reads via a buffer (a)<br />

and a latch (b) (called a Buffered Read and Latched Read).<br />

The main difference in these modes is in the Termination<br />

Phase. The Buffered Read handshakes the data back to the<br />

RP. When the BCP deasserts XACK, data is valid and the<br />

RP can deassert REM-RD. Only after REM-RD goes high is<br />

LCL removed. In the Latched Read (b) XACK rises at the<br />

same time, but the Termination Phase completes without<br />

waiting for the rising edge of REM-RD. One half T-state after<br />

XACK rises, INT-READ rises and one half T-state later<br />

LCL falls. The BCP can use the buses one T -state after LCL<br />

falls. The minimum time (no wait states, no arbitration delay)<br />

the BCP CPU could be prevented from using the bus is four<br />

T-states in the Latched Read Mode.<br />

A Buffered Read prevents the BCP CPU from using the bus<br />

during the time RP is allocated the buses. This time period<br />

begins when LCL rises and ends when REM-RD is removed.<br />

If the REM-RD is asserted longer than the minimum<br />

Buffered Read execution time (four T-states), then the BCP<br />

may be unnecessarily prevented from using the buses.<br />

Therefore, if there are no overriding reasons to use the Buffered<br />

Read Mode, the Latched Read Mode is preferable.<br />

There are three Remote Write Modes-two require buffers<br />

and one requires latches. The timing for the writes utilizing<br />

buffers are shown in Figure 22. The Slow Buffered Write (a)<br />

is handshaked in the same manner as the Buffered Read<br />

and thus has the same timing. The Fast Buffered Write has<br />

similar timing to the Latched Read. This timing similarity exists<br />

because the BCP terminates the remote access without<br />

waiting for the RP to deassert REM-WR.<br />

In both cases, XACK falls a short delay after REM-WR falls<br />

and LCL rises when the RP is given the buses. One T-state<br />

after LCL rises, INT-WRITE falls. The termination in the<br />

Slow Buffered Write mode keys off REM-WR rising, as<br />

shown in Figure 22{a). INT-WRITE rises a prop-delay later<br />

and LCL falls on the next rising edge of the CPU-CLK. The<br />

Fast Buffered Write, shown in Figure 22{b), begins the Termination<br />

Phase with the rising edge of XACK. INT-WRITE<br />

rises at the same time as XACK, and LCL falls one T-state<br />

later. The BCP can begin a local access one T-state after<br />

IC[ transitions.<br />

A Fast Buffered Write is preferable to the Slow Buffered<br />

Write if RP's write cycles are slow compared to the minimum<br />

Fast Buffered Write execution time. The Fast Buffered<br />

Write assumes, though, that data is available to the BCP by<br />

the time INT-WRITE rises.<br />

REM - RD<br />

fo<br />

XACK<br />

/<br />

I<br />

ill / '--\.<br />

INT- READ \ '-Y<br />

Arbitration Access Termination<br />

(a) Buffered Read<br />

TLiF/9336-91<br />

~<br />

FIGURE 21. Read from Remote Processor<br />

---.I \<br />

\ /<br />

Arbitration Access Termination<br />

/<br />

(b) Latched Read<br />

I<br />

TL/F/9336-92<br />

2-148

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

Saved successfully!

Ooh no, something went wrong!