F-Tile DisplayPort Intel® FPGA IP Design Example User Guide

Download PDF
ID 709308
Date 11/03/2023
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents
Document Table of Contents x
1. DisplayPort Intel® FPGA IP Design Example Quick Start Guide 2. DisplayPort Intel® FPGA IP Design Examples 3. HDCP Over DisplayPort Design Example 4. Document Revision History for F-Tile DisplayPort Intel® FPGA IP Design Example User Guide
1. DisplayPort Intel® FPGA IP Design Example Quick Start Guide x
1.1. Directory Structure 1.2. Hardware and Software Requirements 1.3. Generating the Design 1.4. Simulating the Design 1.5. Compiling and Testing the Design 1.6. DisplayPort Intel® FPGA IP Design Example Parameters
1.5. Compiling and Testing the Design x
1.5.1. Regenerating ELF File
2. DisplayPort Intel® FPGA IP Design Examples x
2.1. Intel Agilex® 7 F-Tile DisplayPort SST Parallel Loopback Design Features 2.2. Intel Agilex® 7 F-Tile DisplayPort SST TX-only Design Features 2.3. Intel Agilex® 7 F-Tile DisplayPort SST RX-only Design Features 2.4. Design Components 2.5. Clocking Scheme 2.6. Interface Signals and Parameters 2.7. Simulation Testbench
3. HDCP Over DisplayPort Design Example x
3.1. High-bandwidth Digital Content Protection (HDCP) 3.2. HDCP Over DisplayPort Design Example Architecture 3.3. Nios® II Processor Software Flow 3.4. Design Walkthrough 3.5. Protection of Encryption Key Embedded in FPGA Design 3.6. Debug Guidelines
3.4. Design Walkthrough x
3.4.1. Set Up the Hardware 3.4.2. Generate the Design 3.4.3. Include HDCP Production Keys 3.4.4. Compile the Design 3.4.5. View the Results
3.4.3. Include HDCP Production Keys x
3.4.3.1. Store plain HDCP production keys in the FPGA (Support HDCP Key Management = 0) 3.4.3.2. Store encrypted HDCP production keys in the external flash memory or EEPROM (Support HDCP Key Management = 1)
3.4.3.1. Store plain HDCP production keys in the FPGA (Support HDCP Key Management = 0) x
3.4.3.1.1. HDCP Key Mapping from DCP Key Files 3.4.3.1.2. hdcp1x_tx_kmem.v and hdcp1x_rx_kmem.v files 3.4.3.1.3. hdcp2x_rx_kmem.v file 3.4.3.1.4. hdcp2x_tx_kmem.v file
3.4.3.2. Store encrypted HDCP production keys in the external flash memory or EEPROM (Support HDCP Key Management = 1) x
3.4.3.2.1. Intel KEYENC 3.4.3.2.2. Key Programmer
3.4.5. View the Results x
3.4.5.1. LED Functions
3.5. Protection of Encryption Key Embedded in FPGA Design x
3.5.1. Security Considerations
3.6. Debug Guidelines x
3.6.1. HDCP Status Signals 3.6.2. Modifying HDCP Software Parameters 3.6.3. Frequently Asked Questions (FAQ)
1. DisplayPort Intel® FPGA IP Design Example Quick Start Guide
2. DisplayPort Intel® FPGA IP Design Examples
3. HDCP Over DisplayPort Design Example
4. Document Revision History for F-Tile DisplayPort Intel® FPGA IP Design Example User Guide

2.4. Design Components

The DisplayPort Intel® FPGA IP design example requires the following components.
Table 5.  Core System Components
Module Description
Core System (Platform Designer)

The core system consists of the Nios® II Processor and its necessary components, DisplayPort RX and TX core sub-systems.

This system provides the infrastructure to interconnect the Nios® II processor with the DisplayPort Intel FPGA IP (RX and TX instances) through Avalon® memory-mapped interface within a single Platform Designer system to ease the software build flow.

This system consists of:

  • CPU Sub-System
  • RX Sub-System
  • TX Sub-System
RX Sub-System (Platform Designer)

The RX sub-system consists of:

  • Clock Source—The clock source to the DisplayPort RX core. This sub-system has two clock sources integrated: 100 MHz and 16 MHz.
  • Reset Bridge—The bridge that connects the external signal to the sub-system. This bridge synchronizes to the respective clock source before it is used.
  • DisplayPort RX Core—DisplayPort Sink IP core, VESA DisplayPort Standard version 2.0.
  • Debug FIFO—This FIFO captures all DisplayPort RX auxiliary cycles, and prints out in the Nios® II Debug terminal.
  • PIO—The parallel I/O that triggers the MSA capture, and prints out when the on-board push button (PB) is pressed.
  • Avalon® memory-mapped Pipeline Bridge—This Avalon® memory-mapped bridge interconnects the Avalon® memory-mapped interface between components within the RX sub-system to the Nios® II processor in the Core sub-system.
  • EDID—The EDID RAM is only used to store the desired EDID value in the RAM and connect to the DisplayPort Sink IP core. This component is only used when you disable the Enable GPU Control option in the RX core.
TX Sub-System (Platform Designer)

The TX sub-system consists of:

  • Clock Source—The clock source to the DisplayPort TX core. This sub-system has two clock sources integrated: 100 MHz and 16 MHz.
  • Reset Bridge—The bridge that connects the external signal to the sub-system. This bridge synchronizes to the respective clock source before it is used.
  • DisplayPort TX Core—DisplayPort Source IP core, VESA DisplayPort Standard version 2.0.
  • Debug FIFO—This FIFO captures all DisplayPort TX auxiliary cycles, and prints out in the Nios® II Debug terminal. This component is only used when the TX_AUX_DEBUG parameter is turned on.
  • PIO—The parallel I/O that triggers the DPTX register update in software (tx_utils.c).
  • Avalon® memory-mapped Pipeline Bridge—This Avalon® memory-mapped bridge interconnects the Avalon® memory-mapped interface between components within the TX sub-system to the Nios® II processor in the Core sub-system.
Table 6.  DisplayPort RX PHY Top and TX PHY Top Components
Module Description
Rx Phy Top

TThe RX PHY top level consists of the components related to the receiver PHY layer.

  • DisplayPort DirectPHY Building Block (RX)—The transceiver block that receives the serial data from an external video source and deserializes it to 20-bit (HBR2 and below) or 40-bit (HBR3 and UHBR10) parallel data to the DisplayPort sink IP core. This block supports up to 10 Gbps (UHBR10) data rate with 4 channels. DP Reconfiguration management are implemented within this Building Block.
  • FIFO – To manage Parallel Data transfer crossing between LS_CLK domain and SYS_PLL clock domain.
Tx Phy Top

The TX PHY top level consists of the components related to the transmitter PHY layer.

  • Transceiver Native PHY (TX)—The transceiver block that receives 20-bit or 40-bit parallel data from the DisplayPort Intel® FPGA IP and serializes the data before transmitting it. This block supports up to 10 Gbps (UHBR10) data rate with 4 channels. DP Reconfiguration management are implemented within this Building Block.
  • FIFO – To manage Parallel Data transfer crossing between LS_CLK domain and SYS_PLL clock domain.
Table 7.  Top-Level Common Blocks
Module Description
System PLL DisplayPort Design Example is using System PLL as Transceiver reference clock source.
  • The minimum System PLL output frequency to support all DisplayPort rate is 320 MHz. This design example uses a 900 MHz (highest) output frequency so that SysPLL refclk can be shared with rx/tx refclk_link which is 150 MHz.
Level Two Title