We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 32234

Aurora 8B/10B for Virtex-4 FX FPGAs v3.1 - Release Notes and Known Issues for ISE 11.1


This Answer Record contains the Release Notes for the Aurora 8B/10B for Virtex-4 FX FPGAs v3.1 Core, released in ISE 11.1, and includes the following:

- General Information

- New Features

- Bug Fixes

- Known Issues

For installation instructions, general CORE Generator known issues, and design tools requirements, see the IP Release Notes Guide at:



General Information

The LogiCORE Aurora 8B/10B for Virtex-4 FPGAs requires a license to generate and implement the core. There is no charge for this license.

To generate the license, visit the product page at:


New Features

- ISE 11.1 software support

Bug Fixes

- Insufficient simulation time (CR 479527).

- Timing violation at 6.25 Gb/s for 2-byte configuration (CR 479528).

The maximum line rate for 2-byte interface is restricted to 5 Gb/s since the maximum fabric frequency supported in Virtex-4 FX devices is 250 MHz.

Known Issues

Oversampling support has been removed.

- The valid line rates have changed with the removal of oversampling support. This change was due to low demand in order to reduce test burden, not due to a known issue with oversampling in previous cores.

Timing failure is observed at line rate above 4 Gb/s when transceivers are selected across columns.

- The issue is due to cross-column selection of transceivers. It is recommended to select transceivers in a single column.

Simplex timer option is tested only for line rate of 3.125 Gb/s.

- The Simplex timer value is set only for line rate of 3.125 Gb/s. To use simplex timer for other line rates, you should modify the timer value accordingly.

(Xilinx Answer 22845) - Design does not work in simulation at certain line rates. RXNOTINTABLE and RXRUNDISPERR observed at these line rates. This is a problem in GT11 swift model and simulator resolution. To work around the problem, select the reference clock frequency which results in integer VCO time period value in picoseconds.

(Xilinx Answer 24656) - Incorrect settings for RXVCODAC_INIT, VCODAC_INIT, TXCPSEL, RXCPSEL, and RXRCPADJ

Revision History

4/24/09 - Initial Release

6/30/09 - Added note about oversampling support

8/6/09 - Added AR 24656, corrected Description section

AR# 32234
日期 12/15/2012
状态 Active
Type 综合文章