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–6 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
.
1 The PCI Express Base Specification 2.1 states that receivers may optionally check the
address translation (AT) bits in byte 2 of the header and flag the received TLP as
malformed if AT is not equal to is 2b’00. The Cyclone V Hard IP for PCI Express IP
core does not perform this optional check.
Avalon-ST RX Interface
Table 7–3 describes the signals that comprise the Avalon-ST RX Datapath. The RX data
signal can be 64 or 128 bits.
Figure 7–4. Qword Alignment
.
.
.
0x0
0x8
0x10
0x18
Header Addr = 0x4
64 bits
PCB Memory
Valid Data
Valid Data
Table 7–3. 64- or 128-Bit Avalon-ST RX Datapath (Part 1 of 4)
Signal Width Dir
Avalon-ST
Type
Description
rx_st_data
6412
8
O
data
Receive data bus. Refer to the figures below for the mapping of
the Transaction Layer’s TLP information to
rx_st_data
and
examples of the timing of this interface. Note that the position
of the first payload dword depends on whether the TLP address
is qword aligned. The mapping of message TLPs is the same as
the mapping of TLPs with 4 dword headers. When using a 64-
bit Avalon-ST bus, the width of
rx_st_data
is 64. When using
a 128-bit Avalon-ST bus, the width of
rx_st_data
is 128.
rx_st_sop
1O
start of
packet
Indicates that this is the first cycle of the TLP when
rx_st_valid
is asserted.
rx_st_eop
1O
end of
packet
Indicates that this is the last cycle of the TLP when
rx_st_valid
is asserted.
rx_st_empty
1O
empty
Indicates the number of empty qwords in
rx_st_data
. Not
used when
rx_st_data
is 64 bits.
When asserted, indicates that the upper qword is empty, does
not contain valid data.
rx_st_ready
1I
ready
Indicates that the Application Layer is ready to accept data. The
Application Layer deasserts this signal to throttle the data
stream.
If
rx_st_ready
is asserted by the Application Layer on cycle
<n>, then <n +
readyLatency
> is a ready cycle, during which
the Transaction Layer may assert
valid
and transfer data.
The RX interface supports a
readyLatency
of 2 cycles.