Configuration via Protocol (CvP) Implementation User Guide: Agilex™ 3 FPGAs and SoCs

ID 848621
Date 4/23/2025
Public

1.3. CvP Modes

The CvP configuration scheme supports the following modes:

  • CvP Initialization mode
  • CvP Update mode

CvP Initialization Mode

This mode configures the CvP PCIe* core using the peripheral image of the FPGA through the on-board configuration device. Subsequently, configures the core fabric and all GPIOs that are not dedicated for PERST# signaling through the PCIe* link.

Benefits of using CvP Initialization mode include:

  • Satisfying the PCIe* wake-up time requirement
  • Saving cost by storing the core image in the host memory

CvP Update Mode

The CvP update mode is available after the FPGA enters user mode. You can configure the device through full chip configuration or CvP initialization initially to bring the device into user mode. In user mode, the PCIe* link is available for normal PCIe* applications as well as to perform an FPGA core image update.

The CvP update mode uses the same process as root partition reuse in block-based design, which allows you to reuse the device periphery.

Choose this mode if you want to update the core image for any of the following reasons:

  • To change or modify core FPGA logic functionality
  • To perform standard updates as part of a release process
  • To customize core processing for different components that are part of a complex system
Table 1.  CvP Supported Modes for Agilex™ 3 FPGAs
Note: The Agilex™ 3 FPGA supports monolithic transceiver integrated High-speed Serdes IO (HSSI) Subsystem that includes PCIe Hard IP. The hardware specifications are preliminary, pending the full silicon verification.
Device Supported PCIe Version
A3C 100

PCIe* 3.0 x1

PCIe* 3.0 x2

PCIe* 3.0 x4

Note:
  1. You can only select PCIe* 3.0 in PCIe* Hard IP, but the host can down-train the link to PCIe* 1.0 and PCIe 2.0, if necessary.

  2. PCIe* x4 controller link width can be configured as X1, X2, or X4.
A3C 135