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–24 Chapter 7: IP Core Interfaces
Cyclone V Hard IP for PCI Express
Cyclone V Hard IP for PCI Express December 2013 Altera Corporation
User Guide
To ensure proper operation when sending Configuration Type 0 transactions in Root
Port mode, the application should wait for the Configuration Type 0 transaction to be
transferred to the Hard IP for PCI Express Configuration Space before issuing another
packet on the Avalon-ST TX port. You can do this by waiting for the core to respond
with a completion on the Avalon-ST RX port before issuing the next Configuration
Type 0 transaction.
ECRC Forwarding
On the Avalon-ST interface, the ECRC field follows the same alignment rules as
payload data. For packets with payload, the ECRC is appended to the data as an extra
dword of payload. For packets without payload, the ECRC field follows the address
alignment as if it were a one dword payload. Depending on the address alignment,
Figure 7–7 on page 7–10 through Figure 7–14 on page 7–14 illustrate the position of
the ECRC data for RX data. Figure 7–18 on page 7–19 through Figure 7–26 on
page 7–22 illustrate the position of ECRC data for TX data. For packets with no
payload data, the ECRC corresponds to the position of Data0 in these figures.
Clock Signals
Table 7–5 describes the clock signals that comprise the clock interface.
Refer to Chapter 9, Reset and Clocks for more information about the clock interface.
Table 7–5. Clock Signals Hard IP Implementation
(1)
Signal I/O Description
refclk
I
Reference clock for the Cyclone V Hard IP for PCI Express. It must have the frequency
specified under the System Settings heading in the parameter editor.
If your design meets the following criteria:
■ It enables CvP
■ Includes an additional transceiver PHY connected to the same Transceiver Reconfiguration
Controller
then you must connect
refclk to the mgmt_clk_clk signal of the Transceiver
Reconfiguration Controller and the additional transceiver PHY. In addition, if your design
includes more than one Transceiver Reconfiguration Controller on the same side of the FPGA,
they all must share the
mgmt_clk_clk signal.
pld_clk
I Clocks the Application Layer. You must drive this clock with
coreclkout_hip
.
coreclkout_hip
O
This is a fixed frequency clock used by the Data Link and Transaction Layers. To meet PCI
Express link bandwidth constraints, this clock has minimum frequency requirements as listed
in Table 9–2 on page 9–6.
Note to Table 7–5:
(1) Figure 9–5 on page 9–5 illustrates these clock signals.