Why is the PCI express address incorrect when using the Tx Slave Avalon-MM port on the IP Compiler for PCI Express in QSys? - Why is the PCI express address incorrect when using the Tx Slave Avalon-MM port on the IP Compiler for PCI Express in QSys? Description Due to a bug in the IP Compiler for PCI Express ® in versions 11.1, 11.1sp1 and 11.1sp2 of the Quartus® II software, addresses may not be translated correctly when using the TX Avalon ® -MM slave port to generate PCI Express requests when all bits of ByteEnable are not asserted. For example, if PCI Express requests are generated with only the upper dword enabled on the TX Avalon-MM slave port, the PCI express request that is generated will be a single dword request but with the address of the lower dword. This problem will be fixed in a future version of the Quartus II software. Resolution A patch is available to fix this problem for the Quartus II software version 11.1sp1. Download and install patch 1.16 from the appropriate link below. Quartus II 11.1sp1 Patch 1.16 for Windows Quartus II 11.1sp1 Patch 1.16 for Linux Quartus II 11.1sp1 Patch 1.16 Readme file Custom Fields values: ['novalue'] Troubleshooting novalue False ['PCI Express'] ['FPGA Dev Tools Quartus II Software'] novalue 11.1 ['Stratix® IV GX FPGA'] ['novalue'] ['novalue'] ['novalue']