Altera PCI Compiler User Manual
Page 121
Altera Corporation
User Guide Version 11.1
3–47
October 2011
Functional Description
ack64n
signals in the pci_mt64 and pci_t64 functions are asserted
three clock cycles after a valid address is presented on the PCI bus). In all
operations except configuration read/write, one of the lt_tsr[5..0]
signals is driven high, indicating the BAR range address of the current
transaction.
Configuration transactions are always single-cycle 32-bit transactions.
The PCI MegaCore function has complete control over configuration
transactions and informs the local-side device of the progress and
command of the transaction. The PCI MegaCore function asserts all
control signals, provides data in the case of a read, and receives data in
the case of a write without interaction from the local-side device.
Memory transactions can be single-cycle or burst. In target mode, the PCI
MegaCore function supports an unlimited length of zero-wait state
memory burst read or write transactions. In a read transaction, data is
transferred from the local side to the PCI master. In a write transaction,
data is transferred from the PCI master to the local-side device. A
memory transaction can be terminated by either the PCI master or the
local-side device. The local-side device can terminate the memory
transaction using one of three types of terminations: retry, disconnect, or
target abort.
“Target Transaction Terminations” on page 3–77
describes
how to initiate the different types of termination.
1
The PCI MegaCore function treats the memory read line and
memory read multiple commands as memory read. Similarly,
the function treats the memory write and invalidate command
as a memory write. The local-side application must implement
any special requirements for these commands.
I/O transactions are always single-cycle 32-bit transactions. Therefore,
the PCI MegaCore function handles them like single-cycle memory
commands. Any of the six BARs in the PCI MegaCore functions can be
configured to reserve I/O space. Refer to
for more information on how to configure a specific BAR to be
an I/O BAR. Like memory transactions, I/O transactions can be
terminated normally by the PCI master, or the local-side device can
instruct the PCI MegaCore function to terminate the transactions with a
retry or target abort. Because all I/O transactions are single-cycle,
terminating a transaction with a disconnect does not apply.