描述
Version Found: 3.0 (Rev 1)
Version Resolved and other Known Issues: (Xilinx Answer 65443)
The tactical patch attached to this Answer Record addresses the following issues / enhancements:
- Issue with generation of ack for interrupts when multiple MSI-X vectors are pointing to the same MSI-X entry
- Issue with PCIEBAR translation for BYPASS BAR
- Issue with the XDMA_CONTROL parameter when AXI-LITE BAR is set to 64 bits
- Issue with the interrupts when only MSI-X is selected for UltraScale+ devices
- Issue with the Dword alignment when Bridge - Rootport mode is selected
- Issue with the output signal axi_aresetn where it is being generated based on axi_aresetn from dma_top; it is now generated based on user_reset
- Issue with simulations where 256-bit data was compared for 512-bit simulations
- Added support for 128 bytes DMA transactions
- Issue with the continuous assertion of usr_irq signal in the legacy interrupt mode.
- Freed-up reserved 64K BAR space when MSI-X is not enabled in AXI_Bridge mode
This article is part of the PCI Express Solution Centre
(Xilinx Answer 34536) Xilinx Solution Center for PCI Express
解决方案
This is a known issue to be fixed in a future release of the core, please install the tactical patch attached as described below:
METHOD 1:
- Navigate to the $XILINX_VIVADO/patches directory (create this directory if it does not exist)
- Extract the contents of the ".zip" archive to a directory starting with the name AR68512
Note: most extraction tools will allow you to automatically create a directory with the same name as the zip file - Run Vivado software tools from the original install location.
METHOD 2:
- Create a separate directory for the patched files
- Extract the contents of the ".zip" archive to the desired patch directory location
- Set the MYVIVADO environment variable to point to the Vivado directory under this patch directory
For example:
set MYVIVADO=C:\MYVIVADO\vivado-patch-AR68512\vivado\ - Run Vivado software tools from the original install location.
Note: The "Version Found" column lists the version the problem was first discovered.
The problem also exists in earlier versions, but no specific testing has been performed to verify earlier versions.
Revision History:
02/03/2017 - Initial Release