Visible to Intel only — GUID: iap1490996024020
Ixiasoft
1. Overview
2. CvP Description
3. CvP Topologies
4. Design Considerations
5. CvP Driver and Registers
6. Understanding the Design Steps for CvP Initialization and Update Mode in Stratix® 10
7. Stratix® 10 Configuration via Protocol (CvP) Implementation User Guide Archives
8. Document Revision History
5.3.1. Vendor Specific Capability Header Register
5.3.2. Vendor Specific Header Register
5.3.3. Intel Marker Register
5.3.4. User Configurable Device/Board ID Register
5.3.5. CvP Status Register
5.3.6. CvP Mode Control Register
5.3.7. CvP Data Registers
5.3.8. CvP Programming Control Register
5.3.9. CvP Credit Register
Visible to Intel only — GUID: iap1490996024020
Ixiasoft
1.2. CvP System
A CvP system typically consists of an FPGA, a PCIe* host, and a configuration device.
Figure 1. CvP Block Diagram
- The FPGA connects to the configuration device using the Active Serial x4 (fast mode) configuration scheme.
- CvP and other applications use the PCIe* Hard IP block (bottom left).
Note: For information about the location of the PCIe* Hard IP blocks, refer to Table: PCIe Hard IP channel mapping across all tiles in Channel Availability section of the Intel Stratix 10 H-Tile and L-Tile Avalon Memory Mapped Hard IP for PCI Express* User Guide.
-
Many Stratix® 10 FPGAs include more than one Hard IP block for PCI Express* . The CvP configuration scheme can only utilize the bottom left PCIe* Hard IP block on each device. You must configure this as an Endpoint.
-
- PCIe* Hard IP tile (non-bottom left tile) can only be used for PCIe* applications and cannot be used for CvP.
Note: To avoid configuration failure, you must provide a free running and stable reference clock source to PCIe* IP core before you start the configuration.
Note: For PCIe design including Configuration via Protocol (CvP), Intel recommends you to use Micron QSPI flash in order to load the initial configuration firmware faster to meet the PCIe wake up time for host enumeration. This is because boot ROM reads the initial configuration firmware using x4 mode when using the Micron QSPI flash. For a non-Micron flash, the boot ROM reads the firmware using x1 mode. If you need to use the non-Micron QSPI flash for PCIe design, Intel recommends you to assert PERST# signal low for a minimum of 200 ms from the FPGA POR to ensure the PCIe end point enter link training state before PERST# deasserted.