This answer record contains the Release Notes and Known Issues for the DisplayPort TX Subsystem and includes the following:
DisplayPort TX Subsystem Page:
Supported Devices can be found in the following three locations:
For a list of new features and added device support for all versions, see the Change Log file available with the core in Vivado.
This table correlates the core version to the first Vivado design tools release version in which it was included.
Table 1: Version
|Core Version||Vivado Tools Version|
|v2.0 (Rev. 4)||2017.1|
|v2.0 (Rev. 3)||2016.4|
|v2.0 (Rev. 2)||2016.3|
|v2.0 (Rev. 1)||2016.2|
The table below provides Answer Records for general guidance when using the DisplayPort TX Subsystem.
Table 2: General Guidance
|Article Number||Article Title|
|(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 Number||Article Title||Version Found||Version Resolved|
|(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 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.0||N/A|
|05/12/2017||Added (Xilinx Answer 69077)|
|04/05/2017||Added v2.0 (Rev. 1), v2.0 (Rev. 2), v2.0 (Rev. 3) and v2.0 (Rev. 4) to Version Table and (Xilinx Answer 68860)|
|08/12/2016||Added (Xilinx Answer 67717)|
|04/06/2016||Added v2.0 to Version Table|