Host bridge operation, Using the pci megacore function as a host bridge, Host bridge operation –127 – Altera PCI Compiler User Manual

Page 201

Advertising
background image

Altera Corporation

User Guide Version 11.1

3–127

October 2011

Functional Description

Host Bridge
Operation

This section describes using the pci_mt64 and pci_mt32 MegaCore
functions as a host bridge application in a PCI system. The pci_mt64
and pci_mt32 functions support the following advanced master
features, which should be enabled when using the functions in a host
bridge application:

Use in host bridge application

Allow internal arbitration logic

The host bridge features can be enabled through the Advanced PCI
MegaCore Function Features

page of the Parameterize - PCI Compiler

wizard.

Using the PCI MegaCore Function as a Host Bridge

Turning on Use in Host Bridge Application hardwires the master enable
bit of the command register (bit[2]) to a value of 1, which permanently
enables the master functionality of the pci_mt64 and pci_mt32
MegaCore functions. Additionally, the Use in Host Bridge Application
option also allows the pci_mt64 or pci_mt32 master device to generate
configuration read and write transactions to the internal configuration
space. With the Use in Host Bridge Application option, the same logic
and software routines used to access the configuration space of other PCI
devices on the bus can also configure the pci_mt64 or pci_mt32
configuration space.

1

To perform configuration transactions to internal configuration
space, the idsel signal must be connected following the PCI
specification requirements.

PCI Configuration Read Transaction from the pci_mt64 Local Master
Device to the Internal Configuration Space

Figure 3–46

shows the behavior of the pci_mt64 master device

performing a configuration read transaction from internal configuration
space. The local master requests a 32-bit transaction by asserting the
lm_req32n

signal. When requesting a configuration read transaction,

the pci_mt64 function will automatically perform a single-cycle
transaction. The local master signals are asserted as if the pci_mt64
master is completing a single-cycle, 32-bit memory read transaction,
similar to

Figure 3–44

in the Master Mode Operation section. The

pci_mt64

function’s internal configuration space will respond to the

transaction without affecting the local side signals.

Figure 3–46

applies to

both the pci_mt64 and pci_mt32 MegaCore functions, excluding the
64-bit extension signals as noted for the pci_mt32 function.

Advertising