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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

PPC Bus Interface<br />

Functional Description<br />

All PCI originated PPC bound transactions utilize the PCI Slave and PPC<br />

Master functions for maintaining bus tracking and control. During both<br />

write and read transactions, the PCI Slave places command information<br />

into the PCI FIFO. The PPC Master draws this command information from<br />

the PCI FIFO when it is ready to process the transaction. During write<br />

transactions, write data is captured from the PCI bus within the PCI Input<br />

block. This data is fed into the PCI FIFO. The PPC Output block removes<br />

the data from the FIFO and presents it to the PPC60x bus. During read<br />

transactions, read data is captured from the PPC60x bus within the PPC<br />

Input block. From there, the data is fed into the PCI FIFO. The PCI Output<br />

block removes the data from the FIFO and presents it to the PCI bus.<br />

The MPIC is hosted by the PHB. A custom MPIC Interface is provided to<br />

allow write data and control to be passed to the MPIC and to allow read<br />

data to be passed back to the PHB. The MPIC Interface is controlled<br />

exclusively by the PCI Slave.<br />

The data path function imposes some restrictions on access to the MPIC,<br />

the PCI Registers, and the PPC Registers. The MPIC and the PCI Registers<br />

are only accessible to PCI originated transactions. The PPC Registers are<br />

only accessible to PPC originated transactions.<br />

The PHB has several small blocks that support various PPC functions.<br />

Arbitration is provide by the PPC Arbiter block. Cache line locking (via<br />

PCI Lock) is handled by the PPC Lock block. Finally, a timer function is<br />

implemented in the PPC Timer block.<br />

The PHB also provides miscellaneous support for various PCI functions.<br />

Arbitration on the PCI bus is handled by the PCI Arbiter block. Parity<br />

checking and generation is handled within the PCI Parity block.<br />

The PPC Bus Interface connects directly to one MPC750 or MPC7400<br />

microprocessor and one peripheral PPC60x master device. It uses a subset<br />

of the capabilities of the PPC bus protocol.<br />

http://www.motorola.com/computer/literature 2-5<br />

2

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

Saved successfully!

Ooh no, something went wrong!