User guide
Table Of Contents
- Cyclone V Hard IP for PCI Express User Guide
- Contents
- 1. Datasheet
- 2. Getting Started with the Cyclone V Hard IP for PCI Express
- 3. Getting Started with the Avalon-MM Cyclone Hard IP for PCI Express
- Running Qsys
- Customizing the Cyclone VHard IP for PCI Express IP Core
- Adding the Remaining Components to the Qsys System
- Completing the Connections in Qsys
- Specifying Clocks and Interrupts
- Specifying Exported Interfaces
- Specifying Address Assignments
- Simulating the Example Design
- Simulating the Single DWord Design
- Understanding Channel Placement Guidelines
- Adding Synopsis Design Constraints
- Creating a Quartus II Project
- Compiling the Design
- Programming a Device
- 4. Parameter Settings for the Cyclone V Hard IP for PCI Express
- 5. Parameter Settings for the Avalon-MM Cyclone V Hard IP for PCI Express
- 6. IP Core Architecture
- Key Interfaces
- Protocol Layers
- Multi-Function Support
- PCI Express Avalon-MM Bridge
- Avalon-MM Bridge TLPs
- Avalon-MM-to-PCI Express Write Requests
- Avalon-MM-to-PCI Express Upstream Read Requests
- PCI Express-to-Avalon-MM Read Completions
- PCI Express-to-Avalon-MM Downstream Write Requests
- PCI Express-to-Avalon-MM Downstream Read Requests
- Avalon-MM-to-PCI Express Read Completions
- PCI Express-to-Avalon-MM Address Translation for Endpoints
- Minimizing BAR Sizes and the PCIe Address Space
- Avalon-MM-to-PCI Express Address Translation Algorithm
- Single DWord Completer Endpoint
- 7. IP Core Interfaces
- Cyclone V Hard IP for PCI Express
- Avalon-MM Hard IP for PCI Express
- Physical Layer Interface Signals
- Test Signals
- 8. Register Descriptions
- Configuration Space Register Content
- Altera-Defined Vendor Specific Extended Capability (VSEC)
- PCI Express Avalon-MM Bridge Control Register Access Content
- Avalon-MM to PCI Express Interrupt Registers
- PCI Express Mailbox Registers
- Avalon-MM-to-PCI Express Address Translation Table
- Root Port TLP Data Registers
- Programming Model for Avalon-MM Root Port
- PCI Express to Avalon-MM Interrupt Status and Enable Registers for Root Ports
- PCI Express to Avalon-MM Interrupt Status and Enable Registers for Endpoints
- Avalon-MM Mailbox Registers
- Correspondence between Configuration Space Registers and the PCIe Spec 2.1
- 9. Reset and Clocks
- 10. Transaction Layer Protocol (TLP) Details
- 11. Interrupts
- Interrupts for Endpoints Using the Avalon-ST Application Interface
- Interrupts for Root Ports Using the Avalon-ST Interface to the Application Layer
- Interrupts for Endpoints Using the Avalon-MM Interface to the Application Layer
- Interrupts for End Points Using the Avalon-MM Interface with Multiple MSI/MSI-X Support
- 12. Optional Features
- 13. Flow Control
- 14. Error Handling
- 15. Transceiver PHY IP Reconfiguration
- 16. SDC Timing Constraints
- 17. Testbench and Design Example
- Endpoint Testbench
- Root Port Testbench
- Chaining DMA Design Examples
- Test Driver Module
- Root Port Design Example
- Root Port BFM
- BFM Procedures and Functions
- 18. Debugging
- A. Transaction Layer Packet (TLP) Header Formats
- Additional Information

7–46 Chapter 7: IP Core Interfaces
Avalon-MM Hard IP for PCI Express
Cyclone V Hard IP for PCI Express December 2013 Altera Corporation
User Guide
RX Avalon-MM Master Signals
This Avalon-MM master port propagates PCI Express requests to the Qsys
interconnect fabric. A separate Avalon-MM master port corresponds to each BAR for
up to six BARs. For the full-featured IP core, the Avalon-MM master port propagates
requests as bursting reads or writes. Table 7–21 lists the RX Master interface signals. In
Table 7–21, <n> is the BAR number.
64- or 128-Bit Bursting TX Avalon-MM Slave Signals
This optional Avalon-MM bursting slave port propagates requests from the
interconnect fabric to the full-featured Avalon-MM Cyclone V Hard IP for PCI
Express. Requests from the interconnect fabric are translated into PCI Express request
packets. Incoming requests can be up to 512 bytes. For better performance, Altera
recommends using smaller read request size (a maximum of 512 bytes).
Table 7–21. Avalon-MM RX Master Interface Signals
Signal Name I/O Description
RxmWrite_<n>_o
O Asserted by the core to request a write to an Avalon-MM slave.
RxmAddress_<n>_o[31:0]
O The address of the Avalon-MM slave being accessed.
RxmWriteData_<n>_o[<w>-1:0]
O
RX data being written to slave. <w> = 64 or 128 for the full-featured IP
core. <w> = 32 for the completer-only IP core.
RxmByteEnable_<n>_o[15:0 or
7:0]
O Byte enable for write data.
RxmBurstCount_<n>_o[6:0 or 5:0]
O
The burst count, measured in qwords, of the RX write or read request. The
width indicates the maximum data that can be requested. Because the
maximum data per burst is 512 bytes,
RxmBurstCount
is 6 bits for the
64-bit interface and 5 bits for the 128-bit interface.
RxmWaitRequest_<n>_o
I Asserted by the external Avalon-MM slave to hold data transfer.
RxmRead_<n>_o
O Asserted by the core to request a read.
RxmReadData_<n>_i[<w>-1:0]
I
Read data returned from Avalon-MM slave in response to a read request.
This data is sent to the IP core through the TX interface. <w> = 64 or 128
for the full-featured IP core. <w> = 32 for the completer-only IP core.
RxmReadDataValid_<n>_i
I
Asserted by the system interconnect fabric to indicate that the read data on
is valid.
RxmIrq_<n>_i[<m>:0]
I
Indicates an interrupt request asserted from the system interconnect fabric.
This signal is only available when the CRA port is enabled. Qsys-generated
variations have as many as 16 individual interrupt signals (<m> 15).
if
RxmIrq_<n>_i[<m>:0]
is asserted on consecutive cycles without the
deassertion of all interrupt inputs, no MSI message is sent for subsequent
interrupts. To avoid losing interrupts, software must ensure that all
interrupt sources are cleared for each MSI message received.