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

Chapter 17: Testbench and Design Example 17–21
Root Port BFM
December 2013 Altera Corporation Cyclone V Hard IP for PCI Express
User Guide
The functionality of each of the modules included in Figure 17–4 is explained below.
■ BFM shared memory (altpcietb_bfm_shmem_common Verilog HDL include
file)—The Root Port BFM is based on the BFM memory that is used for the
following purposes:
■ Storing data received with all completions from the PCI Express link.
■ Storing data received with all write transactions received from the PCI Express
link.
■ Sourcing data for all completions in response to read transactions received
from the PCI Express link.
■ Sourcing data for most write transactions issued to the PCI Express link. The
only exception is certain BFM write procedures that have a four-byte field of
write data passed in the call.
■ Storing a data structure that contains the sizes of and the values programmed
in the BARs of the Endpoint.
A set of procedures is provided to read, write, fill, and check the shared memory from
the BFM driver. For details on these procedures, see “BFM Shared Memory Access
Procedures” on page 17–35.
■ BFM Read/Write Request Functions(altpcietb_bfm_driver_rp.v)—These
functions provide the basic BFM calls for PCI Express read and write requests. For
details on these procedures, see “BFM Read and Write Procedures” on page 17–28.
■ BFM Configuration Functions(altpcietb_bfm_driver_rp.v)—These functions
provide the BFM calls to request configuration of the PCI Express link and the
Endpoint Configuration Space registers. For details on these procedures and
functions, see “BFM Configuration Procedures” on page 17–34.
■ BFM Log Interface(altpcietb_bfm_driver_rp.v)—The BFM log functions provides
routines for writing commonly formatted messages to the simulator standard
output and optionally to a log file. It also provides controls that stop simulation on
errors. For details on these procedures, see “BFM Log and Message Procedures”
on page 17–37.
■ BFM Request Interface(altpcietb_bfm_driver_rp.v)—This interface provides the
low-level interface between the
altpcietb_bfm_rdwr
and
altpcietb_bfm_configure
procedures or functions and the Root Port RTL Model.
This interface stores a write-protected data structure containing the sizes and the
values programmed in the BAR registers of the Endpoint, as well as, other critical
data used for internal BFM management. You do not need to access these files
directly to adapt the testbench to test your Endpoint application.
■ Avalon-ST Interfaces (altpcietb_bfm_vc_intf.v)—These interface modules handle
the Root Port interface model. They take requests from the BFM request interface
and generate the required PCI Express transactions. They handle completions
received from the PCI Express link and notify the BFM request interface when
requests are complete. Additionally, they handle any requests received from the
PCI Express link, and store or fetch data from the shared memory before
generating the required completions.