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

Download PDF
ID 848621
Date 4/23/2025
Public
Document Table of Contents
Document Table of Contents x
1. Overview 2. CvP Description 3. CvP Topologies 4. Design Considerations 5. Document Revision History for the Configuration via Protocol (CvP) Implementation User Guide: Agilex™ 3 FPGAs and SoCs
1. Overview x
1.1. Benefits of Using CvP 1.2. CvP System 1.3. CvP Modes
1.3. CvP Modes x
1.3.1. CvP Limitations
1.3.1. CvP Limitations x
1.3.1.1. CvP Error Recovery
2. CvP Description x
2.1. Configuration Images 2.2. CvP Modes 2.3. Compression Features 2.4. Pin Description
2.2. CvP Modes x
2.2.1. CvP Initialization Mode 2.2.2. CvP Update Mode
3. CvP Topologies x
3.1. Single Endpoint 3.2. Multiple Endpoints
4. Design Considerations x
4.1. Designing CvP for an Open System 4.2. Designing CvP for a Closed System
4.1. Designing CvP for an Open System x
4.1.1. FPGA Power Supplies Ramp Time Requirement 4.1.2. PCIe Wake-Up Time Requirement
4.1.2. PCIe Wake-Up Time Requirement x
4.1.2.1. For CvP Initialization Mode 4.1.2.2. For CvP Update Mode
1. Overview
2. CvP Description
3. CvP Topologies
4. Design Considerations
5. Document Revision History for the Configuration via Protocol (CvP) Implementation User Guide: Agilex™ 3 FPGAs and SoCs

1.2. CvP System

A CvP system typically consists of an FPGA, a PCIe* host, and a configuration device.

Figure 1. CvP Block Diagram for Agilex™ 3 FPGA
  1. The FPGA connects to the configuration device using the Active Serial x4 (fast mode) configuration scheme.
  2. The PCIe* Hard IP block located near the SDM block is on the left side and can be used for CvP applications.
  3. PCIe* Hard IP blocks that are not used for CvP can be used for PCIe* application.
Note: For PCIe* design including Configuration via Protocol (CvP), Altera 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, Altera 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.
Level Two Title