DisplayPort Intel® FPGA IP User Guide

ID 683273
Date 4/29/2022
Public

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

Document Table of Contents
Give Feedback

4.3.4.5. View the Results

In this step you view the results of the hardware demonstration in the Nios II command shell and on the DisplayPort monitor.

  1. Power-up the connected DisplayPort monitor.
  2. Connect the free end of the Display Port cable that you connected to your PC to the DisplayPort RX on the Bitec daughter card. The PC now has the DisplayPort monitor available as a second monitor. The hardware demonstration loops through and displays the graphic card output as received by the sink core.
    Note: Some PC drivers and graphic card adapters do not enable the DisplayPort hardware automatically upon hot plug detection. You may need to start the adapter’s control utility (e.g., Catalist Control Center, NVIDIA Control Panel) and manually enable the DisplayPort display.
    Figure 10. Loop-through Hardware Demonstration
  3. You can use your graphic card control panel to adjust the resolution of the DisplayPort monitor, which typically results in link training, related AUX channel traffic, and a corresponding new image size on the monitor.
    Note: If you do not see visible output on the monitor, press push button (CPU_RESETN) to generate a reset, causing the DisplayPort TX core to re-train the link.

    Press push button 0 (USER_PB[0]) to retrieve MSA statistics from the source and sink connections. The Nios II Command Shell displays the AUX channel traffic during link training with the monitor.

    Figure 11. MSA Output

    The Nios II AUX printout shows each message packet on a separate line.

    • The first field is the incremental timestamp in microseconds.
    • The second field indicates whether the message packet is from or to the DisplayPort sink (SNK) or source (SRC).
    • The next two fields show the request and response headers and payloads. The DPCD address field on request messages are decoded into the respective DPCD location names.

    When connected and enabled, USER_PB[0] on the development board illuminates to indicate that the DisplayPort receiver has locked correctly.