AR# 59384


DisplayPort TX Subsystem - Release Notes and Known Issues for Vivado 2015.4 and newer tool versions


This answer record contains the Release Notes and Known Issues for the DisplayPort TX Subsystem and includes the following:

  • General Information
  • Known and Resolved Issues
  • Revision History

DisplayPort TX Subsystem Page:


General Information

**This core is now in maintenance mode and it is suggested to update to the DisplayPort 1.4 solution in (Xilinx Answer 70295) if starting a new project**

Supported Devices can be found in the following locations:

For a list of new features and added device support for all versions:

  • Subsystem or IP - See the Change Log included with the core in Vivado.
  • Subsystem or IP - Click on the Change Log links below.
  • Standalone Software Drivers - See the Change Log included with the Doxygen Drivers in Xilinx SDK
  • Standalone Software Drivers - Github Software Driver Repo


Please seek technical support via the Video Board of the Xilinx Community Forums.

The Xilinx Forums are great resource for technical support.

The entire Xilinx User Community is available to help here, and you can ask questions and collaborate with Xilinx experts to get the solutions you need.

Version Table

This table correlates the core version to the first Vivado design tools release version in which it was included.

Table 1: Version

Core VersionVivado Tools VersionSubsystem Change LogSubsystem PatchesStandalone Software Driver Patches
v2.1 (Rev. 8)2020.2(Xilinx Answer 75786)  
v2.1 (Rev. 7)2020.1(Xilinx Answer 73626)  
v2.1 (Rev. 6)2019.2(Xilinx Answer 72923)  
v2.1 (Rev. 5)2019.1(Xilinx Answer 72242)  
v2.1 (Rev. 4)2018.3(Xilinx Answer 71806)  
v2.1 (Rev. 3)2018.2(Xilinx Answer 71212)  
v2.1 (Rev. 2)2018.1(Xilinx Answer 70699)  
v2.1 (Rev. 1)2017.4(Xilinx Answer 70386)  
v2.12017.3(Xilinx Answer 69903)  
v2.0 (Rev. 5)2017.2(Xilinx Answer 69326)(Xilinx Answer 67091) 
v2.0 (Rev. 4)2017.1(Xilinx Answer 69055)  
v2.0 (Rev. 3)2016.4(Xilinx Answer 68369)  
v2.0 (Rev. 2)2016.3(Xilinx Answer 68021)  
v2.0 (Rev. 1)2016.2(Xilinx Answer 67345)  
v2.02016.1(Xilinx Answer 66930)  
v1.02015.4(Xilinx Answer 66004)  

General Guidance

The table below provides Answer Records for general guidance when using the DisplayPort TX Subsystem.

Table 2: General Guidance

Article NumberArticle Title
(Xilinx Answer 71773)Do the DisplayPort Subsystems IPs support active or passive adaptors to HDMI, DVI, or VGA?
(Xilinx Answer 71504)Why is XAPP1271 not available anymore?
(Xilinx Answer 69077)XAPP1271 - Why does a debug build work but not the release build with optimizations?

Known and Resolved Issues

The following table provides known issues for the DisplayPort TX Subsystem, starting with v1.0, initially released in Vivado 2015.4.

Note: The "Version Found" column lists the version the problem was first discovered.

The problem might also exist in earlier versions, but no specific testing has been performed to verify earlier versions.

Table 3: IP

Article NumberArticle TitleVersion FoundVersion Resolved
(Xilinx Answer 72177)Why do I see a flicker when connected to a DELL U2412Mv2.1v2.1 (Rev. 5)
(Xilinx Answer 69683)Why is there sometimes unexpected data skew between lanes when enabling the PRBS-7 option?v2.0 (Rev. 2)N/A
(Xilinx Answer 68860)Why do I get the warning message that the DisplayPort LogiCORE will become obsolete when I am already using the subsystem?v2.0 (Rev. 4)N/A
(Xilinx Answer 69199)Why is the OOC synthesis of the BD always Out of date?v2.0 (Rev 2)v2.0 (Rev. 4)
(Xilinx Answer 67717)Why do I see *tx_vid_pixel0 and *tx_vid_pixel1 inputs even though I have configured the core for single pixel mode?v2.0v2.0 (Rev. 2)
(Xilinx Answer 66286)DisplayPort TX Subsystem IP errors in Generating Outputs : ERROR: [BD 41-1273] Error running post_propagate
TCL procedure: invalid command name "::bd::addr::get_addresses_of" in managed IP project


Software Driver:
Article NumberArticle TitleVersion FoundVersion Resolved
Example Design:
Available 2017.3 and later.
Article NumberArticle TitleVersion FoundVersion Resolved
(Xilinx Answer 72221)The KCU105 example design application displays color disruption on monitor in pass-through modev2.1 (Rev.2)v2.1 (Rev. 5)
(Xilinx Answer 70328)Why can an example design integrated in Vivado not be built on Windows?v2.1v2.1 (Rev. 4)


Revision History: 
01/04/2021Added v2.1 (Rev. 8)
06/28/2020Added v2.1 (Rev. 7)
06/21/2019Added (Xilinx Answer 72242) to revision table
04/19/2019Added v2.1 (Rev. 5) and (Xilinx Answer 71806) to Version table and (Xilinx Answer 72221) and (Xilinx Answer 72177) to known issues tables
11/30/2018Added v2.1 (Rev. 4) to Version table and (Xilinx Answer 71773) to General Guidance Table
10/23/2018Added (Xilinx Answer 70328) to known issues
09/04/2018Added v2.1 (Rev. 3) to Revision Table and (Xilinx Answer 71504) to General Guidance
04/04/2018Added v2.1 (Rev. 1), v2.1 (Rev. 2) to Version Table
11/13/2017Cleanup Version Table. Added v2.1 to Version Table
08/29/2017Added (Xilinx Answer 69683)
06/29/2017Added 2.0 (Rev. 3) to Version Table, (Xilinx Answer 66286), and (Xilinx Answer 69199)
05/12/2017Added (Xilinx Answer 69077)
04/05/2017Added v2.0 (Rev. 1), v2.0 (Rev. 2) to Version Table and (Xilinx Answer 68860)
08/12/2016Added (Xilinx Answer 67717)
04/06/2016Added v2.0 to Version Table
11/24/2015Initial Release

Linked Answer Records

Master Answer Records

Answer Number Answer Title Version Found Version Resolved
56852 Xilinx Multimedia, Video and Imaging Solution Center - Top Issues N/A N/A

Child Answer Records

Associated Answer Records

AR# 59384
Date 01/08/2021
Status Active
Type Release Notes
People Also Viewed