1. DisplayPort IP Design Example Quick Start Guide
2. DisplayPort IP Design Examples
3. DisplayPort SST Parallel Loopback without PCR Design Example
4. DisplayPort SST Parallel Loopback with AXI4-S Video Interface Design Example
5. DisplayPort SST TX-Only Design Example
6. DisplayPort SST RX-Only Design Example
7. Document Revision History for the GTS DisplayPort FPGA IP Design Example User Guide
1.5.1. Compiling and Testing the Design Using Agilex™ 3 FPGA and SoC C-Series Development Kit
1.5.2. Compiling and Testing the Design Using Agilex™ 5 E-Series 065B Premium Development Kit
1.5.3. Compiling and Testing the Design Using Agilex™ 5 E-Series 065B Modular Development Kit Connector with No FMC Mode
1.5.4. Compiling and Testing the Design Using Agilex™ 5 E-Series 065B Modular Development Kit Connector with Bitec Rev 8 Daughter Card
4.2. Functional Description
For the DisplayPort SST parallel loopback with AXI4-S video interface design example.
Figure 11. Agilex™ 3 and Agilex™ 5 DisplayPort SST Parallel Loopback with AXI4-S Video Interface
- In this variant, the DisplayPort source and sink parameter, select AXIS-VVP FULL in Enable Active Video Data Protocols to enable AXI-Stream Video Data Interface.
- The DisplayPort sink receives video and or audio streaming from external video source such as GPU and decodes it into parallel video interface.
- The DisplayPort Sink converts video data stream into AXI4-Stream video data and drives the DisplayPort source AXI-Stream video data interface through video and vision Frame Buffer IP. The DisplayPort Source then converts AXI-Stream video data into DisplayPort main link before transmitting it to the monitor.
Note:
- Because of restrictions of the Agilex™ 5 Modular Development Kit, the FPGA clock routes are not sufficient to support both the EMIF and SystemPLL transceiver modes simultaneously. This limitation does not apply to the Premium development kit.
- When targeting the Agilex™ 5 Modular Development Kit, turning on System PLL in the design example GUI generates an error message. The design example does not support this combination, because of device routing limitations.