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# 66852

VIVADO 2015.4 (or) earlier - Aurora 64B66B - Channel up failure due to de-assertion of RXCDRLOCK


As per the GT user guide, RXCDRLOCK is a reserved port.

Aurora 64B66B fails to achieve stable Channel_up with some channels because the core is initiating reset due to RXCDRLOCK output from the GT being LOW. However, RXDATA output from the GT is error free.

This Answer Record provides an update to remove the dependency on the RXCDRLOCK signal during core re-initialization.


Make the following code update in the aurora_64b66b_0_multi_wrapper.v file:

Change from the following:

   assign gtwiz_userclk_rx_reset_in = ~(&rxpmaresetdone_int)  ||

Change to the following:

assign gtwiz_userclk_rx_reset_in = ~(&rxpmaresetdone_int) ;

Revision History:

03/22/2016 - Initial Release

AR# 66852
Date Created 03/18/2016
Last Updated 03/29/2016
Status Active
Type General Article
  • Kintex UltraScale
  • Virtex UltraScale
  • Vivado Design Suite - 2015.4.2
  • Vivado Design Suite - 2015.4.1
  • Vivado Design Suite - 2015.4
  • Aurora 64B/66B