UPGRADE YOUR BROWSER

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!

cancel
Showing results for 
Search instead for 
Did you mean: 
Adventurer
Adventurer
8,646 Views
Registered: ‎09-10-2008

WARNING:Route:466 - Unusually high hold time violation

Hi all,

 

I have a warning here that I can't fix. When this warning shows up, PAR takes extra time to try to work around it, making my implementation very time-consuming.

 

I believe this is all related to the chipscope blocks I put in and the block RAMs they're consuming. Anyway, here is the warning message:

 

WARNING:Route:466 - Unusually high hold time violation detected among 60 connections. The top 20 such instances are

   printed below. The router will continue and try to fix it

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_12:Q2 -> i_ila_1/i_dt1/1/data_and_trig_dly1_47:AX -2688

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_03:Q2 -> i_ila_1/i_dt1/1/data_and_trig_dly1_35:DX -2682

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_11:Q2 -> i_ila_1/i_dt1/1/data_and_trig_dly1_43:DX -2674

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_12:Q4 -> i_ila_1/i_dt1/1/data_and_trig_dly1_15:AX -2674

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_07:Q2 -> i_ila_1/i_dt1/1/data_and_trig_dly1_39:DX -2665

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_13:Q4 -> i_ila_1/i_dt1/1/data_and_trig_dly1_15:BX -2653

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_08:Q1 -> i_ila_1/i_dt1/1/data_and_trig_dly1_59:AX -2649

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_11:Q3 -> i_ila_1/i_dt1/1/data_and_trig_dly1_27:DX -2649

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_07:Q3 -> i_ila_1/i_dt1/1/data_and_trig_dly1_23:DX -2649

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_11:Q4 -> i_ila_1/i_dt1/1/data_and_trig_dly1_11:DX -2648

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_11:Q1 -> i_ila_1/i_dt1/1/data_and_trig_dly1_59:DX -2644

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_13:Q2 -> i_ila_1/i_dt1/1/data_and_trig_dly1_47:BX -2637

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_03:Q3 -> i_ila_1/i_dt1/1/data_and_trig_dly1_19:DX -2626

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_00:Q4 -> i_ila_1/i_dt1/1/data_and_trig_dly1_3:AX -2619

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_08:Q3 -> i_ila_1/i_dt1/1/data_and_trig_dly1_27:AX -2613

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_04:Q1 -> i_ila_1/i_dt1/1/data_and_trig_dly1_55:AX -2612

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_04:Q4 -> i_ila_1/i_dt1/1/data_and_trig_dly1_7:AX -2607

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_09:Q4 -> i_ila_1/i_dt1/1/data_and_trig_dly1_11:BX -2607

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_07:Q1 -> i_ila_1/i_dt1/1/data_and_trig_dly1_55:DX -2590

SDR_4TO1_16CHAN_RX_0/ISERDES_RX_DATA_04:Q2 -> i_ila_1/i_dt1/1/data_and_trig_dly1_39:AX -2538

 

This warning occurs if I route a global clock to the ILA block. If I route a local clock, the design will fail and complain that the design could not be fit and then it would also mention the related blocks shown above.

 

What can I do to fix this?

 

Thank you. 

0 Kudos
2 Replies
Adventurer
Adventurer
6,176 Views
Registered: ‎10-25-2009

Re: WARNING:Route:466 - Unusually high hold time violation

hi i m getting same problem. can u tell me how to fix this problem.

thank u

0 Kudos
Xilinx Employee
Xilinx Employee
6,167 Views
Registered: ‎01-03-2008

Re: WARNING:Route:466 - Unusually high hold time violation

The original poster said

This warning occurs if I route a global clock to the ILA block. If I route a local clock, the design will fail and complain that the design could not be fit and then it would also mention the related blocks shown above.

And it isn't clear if you have this same problem or not.

 

First, clocks should only be connected the ILA clock port.  Connecting them TRIGGER or DATA ports will not result in any meaningfull data as the ILA logic samples these ports with the clock connected to the clock port and will result in a static value.

 

Second, these warning messages appear to be from an IOB ISERDES to the DATA port of the ILA block and the likely cause is different clocks were used on the ISERDES CLKDV and the ILA clock port.

 

Third, when posting please include the software version and fpga device that you are using as there are numerous differences between versions and FPGA families.

------Have you tried typing your question into Google? If not you should before posting.
Too many results? Try adding site:www.xilinx.com
0 Kudos