17.11.2012 Views

MVME5100 Single Board Computer Programmer's Reference Guide

MVME5100 Single Board Computer Programmer's Reference Guide

MVME5100 Single Board Computer Programmer's Reference Guide

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.

2<br />

Hawk PCI Host Bridge & Multi-Processor Interrupt Controller<br />

AACK_ and TA_ allows the PPC Slave to assert a retry to the processor in<br />

the event that the transaction is unable to complete on the PCI side. It<br />

should be noted that any transaction that crosses a PCI word boundary<br />

could be disrupted after only having a portion of the data transferred.<br />

The PPC Slave cannot perform compelled burst write transactions. The<br />

PPC bus protocol mandates that the qualified retry window must occur no<br />

later than the assertion of the first TA_ of a burst transaction. If the PHB<br />

was to attempt a compelled linkage for all beats within a burst write, there<br />

is a possibility that the transaction could be interrupted. The interruption<br />

would occur at a time past the latest qualified retry window and the PPC<br />

Slave would be unable to retry the transaction. Therefore, all burst write<br />

transactions are posted regardless of the write posting attribute within the<br />

associated map decoder register.<br />

If the PPC Slave is servicing a posted write transaction and the PPC FIFO<br />

can accept the transaction, the assertion of AACK_ and TA_ occurs as soon<br />

as the PPC Slave decode logic settles out and the PPC bus protocol allows<br />

for the assertion. If the PPC FIFO is full, the PPC Slave holds the processor<br />

with wait states (AACK_ will not be asserted) until there is room within the<br />

PPC FIFO to store the pending transaction.<br />

The PPC Slave divides PPC command types into three categories: address<br />

only, write, and read. If a command type is an address only and the address<br />

presented at the time of the command is a valid PHB address, the PPC<br />

slave will respond immediately by asserting AACK_. The PHB will not<br />

respond to address only cycles where the address presented is not a PHB<br />

address. The response of the PPC Slave to command types is listed in<br />

Table 2-1.<br />

Table 2-1. PPC Slave Response Command Types<br />

PPC Transfer Type<br />

Transfer<br />

Encoding<br />

Transaction<br />

Clean Block 00000 Addr Only<br />

Flush Block 00100 Addr Only<br />

SYNC 01000 Addr Only<br />

Kill Block 01100 Addr Only<br />

EIEIO 10000 Addr Only<br />

2-8 <strong>Computer</strong> Group Literature Center Web Site

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

Saved successfully!

Ooh no, something went wrong!