Visible to Intel only — GUID: nik1410564777586
Ixiasoft
1. Datasheet
2. Quick Start Guide
3. Parameter Settings
4. Physical Layout
5. 64- or 128-Bit Avalon-MM Interface to the Endpoint Application Layer
6. Registers
7. Reset and Clocks
8. Interrupts for Endpoints
9. Error Handling
10. Design Implementation
11. Throughput Optimization
12. Additional Features
13. Avalon-MM Testbench and Design Example
14. Avalon-MM Testbench and Design Example for Root Port
15. Hard IP Reconfiguration
16. Debugging
A. PCI Express Protocol Stack
B. Transaction Layer Packet (TLP) Header Formats
C. Lane Initialization and Reversal
D. Arria® 10 or Cyclone® 10 GX Avalon® -MM Interface for PCIe* Solutions User Guide Archive
E. Document Revision History
1.1. Arria® 10 or Cyclone® 10 GX Avalon-MM Interface for PCIe Datasheet
1.2. Features
1.3. Release Information
1.4. Device Family Support
1.5. Configurations
1.6. Design Examples
1.7. IP Core Verification
1.8. Resource Utilization
1.9. Recommended Speed Grades
1.10. Creating a Design for PCI Express
3.1. Parameters
3.2. Avalon-MM Settings
3.3. Base Address Register (BAR) Settings
3.4. Device Identification Registers
3.5. PCI Express and PCI Capabilities Parameters
3.6. Configuration, Debug, and Extension Options
3.7. Vendor Specific Extended Capability (VSEC)
3.8. PHY Characteristics
3.9. Example Designs
5.1. 32-Bit Non-Bursting Avalon-MM Control Register Access (CRA) Slave Signals
5.2. Bursting and Non-Bursting Avalon® -MM Module Signals
5.3. 64- or 128-Bit Bursting TX Avalon-MM Slave Signals
5.4. Clock Signals
5.5. Reset, Status, and Link Training Signals
5.6. Interrupts for Endpoints when Multiple MSI/MSI-X Support Is Enabled
5.7. Hard IP Status Signals
5.8. Physical Layer Interface Signals
6.1. Correspondence between Configuration Space Registers and the PCIe Specification
6.2. Type 0 Configuration Space Registers
6.3. Type 1 Configuration Space Registers
6.4. PCI Express Capability Structures
6.5. Intel-Defined VSEC Registers
6.6. CvP Registers
6.7. 64- or 128-Bit Avalon-MM Bridge Register Descriptions
6.8. Programming Model for Avalon-MM Root Port
6.9. Uncorrectable Internal Error Mask Register
6.10. Uncorrectable Internal Error Status Register
6.11. Correctable Internal Error Mask Register
6.12. Correctable Internal Error Status Register
6.7.1.1. Avalon-MM to PCI Express Interrupt Status Registers
6.7.1.2. Avalon-MM to PCI Express Interrupt Enable Registers
6.7.1.3. PCI Express Mailbox Registers
6.7.1.4. Avalon-MM-to-PCI Express Address Translation Table
6.7.1.5. PCI Express to Avalon-MM Interrupt Status and Enable Registers for Endpoints
6.7.1.6. Avalon-MM Mailbox Registers
6.7.1.7. Control Register Access (CRA) Avalon-MM Slave Port
13.5.1. ebfm_barwr Procedure
13.5.2. ebfm_barwr_imm Procedure
13.5.3. ebfm_barrd_wait Procedure
13.5.4. ebfm_barrd_nowt Procedure
13.5.5. ebfm_cfgwr_imm_wait Procedure
13.5.6. ebfm_cfgwr_imm_nowt Procedure
13.5.7. ebfm_cfgrd_wait Procedure
13.5.8. ebfm_cfgrd_nowt Procedure
13.5.9. BFM Configuration Procedures
13.5.10. BFM Shared Memory Access Procedures
13.5.11. BFM Log and Message Procedures
13.5.12. Verilog HDL Formatting Functions
A.4.1. Avalon‑MM Bridge TLPs
A.4.2. Avalon-MM-to-PCI Express Write Requests
A.4.3. Avalon-MM-to-PCI Express Upstream Read Requests
A.4.4. PCI Express-to-Avalon-MM Read Completions
A.4.5. PCI Express-to-Avalon-MM Downstream Write Requests
A.4.6. PCI Express-to-Avalon-MM Downstream Read Requests
A.4.7. Avalon-MM-to-PCI Express Read Completions
A.4.8. PCI Express-to-Avalon-MM Address Translation for 32-Bit Bridge
A.4.9. Minimizing BAR Sizes and the PCIe Address Space
A.4.10. Avalon® -MM-to-PCI Express Address Translation Algorithm for 32-Bit Addressing
Visible to Intel only — GUID: nik1410564777586
Ixiasoft
1.10. Creating a Design for PCI Express
Select the PCIe variant that best meets your design requirements.
- Is your design an Endpoint or Root Port?
- What Generation do you intend to implement?
- What link width do you intend to implement?
- What bandwidth does your application require?
- Does your design require Configuration via Protocol (CvP)?
Note: The following steps only provide a high-level overview of the design generation and simulation process. For more details, refer to the Quick Start Guide chapter.
- Select parameters for that variant.
- For Arria® 10 devices, you can use the new Example Design tab of the component GUI to generate a design that you specify. Then, you can simulate this example and also download it to an Arria® 10 FPGA Development Kit. Refer to the Arria® 10/ Cyclone® 10 GX PCI Express* IP Core Quick Start Guide for details.
- For all devices, you can simulate using an Intel-provided example design. All static PCI Express example designs are available under <install_dir>/ip/altera/altera_pcie/altera_pcie_<dev>_ed/example_design/<dev> . Alternatively, create a simulation model and use your own custom or third-party BFM. The Platform Designer Generate menu generates simulation models. Intel supports ModelSim* - Intel FPGA Edition for all IP. The PCIe cores support the Aldec RivieraPro*, Cadence NCSim*, Mentor Graphics ModelSim*, and Synopsys VCS* and VCS-MX* simulators.
The Intel testbench and Root Port or Endpoint BFM provide a simple method to do basic testing of the Application Layer logic that interfaces to the variation. However, the testbench and Root Port BFM are not intended to be a substitute for a full verification environment. To thoroughly test your application, Intel suggests that you obtain commercially available PCI Express verification IP and tools, or do your own extensive hardware testing, or both.
- Compile your design using the Quartus® Prime software. If the versions of your design and the Quartus® Prime software you are running do not match, regenerate your PCIe design.
- Download your design to an Intel development board or your own PCB. Click on the All Development Kits link below for a list of Intel's development boards.
- Test the hardware. You can use Intel's Signal Tap Logic Analyzer or a third-party protocol analyzer to observe behavior.
- Substitute your Application Layer logic for the Application Layer logic in Intel's testbench. Then repeat Steps 3–6. In Intel's testbenches, the PCIe core is typically called the DUT (device under test). The Application Layer logic is typically called APPS.
Related Information