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: 
Highlighted
Visitor bonsaipappel
Visitor
7,218 Views
Registered: ‎03-24-2010

Exclude Paths from TIG Constraint

Jump to solution

Hello,

 

in my design there are several clock domains. Most of the Paths crossing this domains (around 95%) leading through fifos so I applied the TIG constraint like:

TIMESPEC "TS_clk100_to_sdr_clk" = FROM "TNM_clk_100" TO "sdr_clk" TIG;

 But there are one or two paths I would need to apply a Time Constraint like:

INST "u_data_if_a/u_data_if_control/o_ddr_align*" TNM = TNM_ddr_sdr_allign;
INST "u_data_if_a/u_data_if_control/o_sdr_align*" TNM = TNM_ddr_sdr_allign;
INST "u_data_if_a/lane[*].u_data_if_lane/data_rr*" TNM = TNM_lane_data_rr;
TIMESPEC "TS_data_if_ddr_sdr_allign" = FROM "TNM_ddr_sdr_allign" TO "TNM_lane_data_rr" "TS_sdr_clk";

 

My problem is that the "TS_data_if_ddr_sdr_allign" time spec has now analyzed paths in the timing report and all paths which belongs to this constraint are still covered by the TIG constraint.

 

The question is:

Is there a statement to tell the Timing Analyzer that the TIG constraint should apply, except the paths of the "TS_data_if_ddr_sdr_allign" constraint?

 

I already tried to apply the PRIORITY keyword to the both constraints but I got an error for the TIG Constraint. It seems that the PRIORITY keyword cannot be applied after a TIG statement.

 

Best regards,

Volker

0 Kudos
1 Solution

Accepted Solutions
Xilinx Employee
Xilinx Employee
10,775 Views
Registered: ‎07-16-2008

Re: Exclude Paths from TIG Constraint

Jump to solution

TIG constraint has the highest priority. So PRIORITY keyword is not applicable for two constraints with different level.

 

As Ajmir points out, you can exclude the time groups from TIGed group by using EXCEPT.

 

Suppose "TNM_ddr_sdr_allign" is within group "sdr_clk" and "TNM_lane_data_rr" within "TNM_clk_100",

 

TIMEGRP "TNM_clk_100_TIG" = "TNM_clk_100" EXCEPT "TNM_lane_data_rr";

TIMEGRP "sdr_clk_TIG" = "sdr_clk" EXCEPT "TNM_ddr_sdr_allign";

TIMESPEC "TS_clk100_to_sdr_clk" = FROM "TNM_clk_100_TIG" TO "sdr_clk_TIG" TIG;

-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
3 Replies
Xilinx Employee
Xilinx Employee
7,210 Views
Registered: ‎05-14-2008

Re: Exclude Paths from TIG Constraint

Jump to solution

You may exclude some group from another group using EXCEPT.

 

Please see page 57 of http://www.xilinx.com/support/documentation/sw_manuals/xilinx13_4/ug612.pdf

 

What is 

TS_sdr_clk ?
0 Kudos
Xilinx Employee
Xilinx Employee
10,776 Views
Registered: ‎07-16-2008

Re: Exclude Paths from TIG Constraint

Jump to solution

TIG constraint has the highest priority. So PRIORITY keyword is not applicable for two constraints with different level.

 

As Ajmir points out, you can exclude the time groups from TIGed group by using EXCEPT.

 

Suppose "TNM_ddr_sdr_allign" is within group "sdr_clk" and "TNM_lane_data_rr" within "TNM_clk_100",

 

TIMEGRP "TNM_clk_100_TIG" = "TNM_clk_100" EXCEPT "TNM_lane_data_rr";

TIMEGRP "sdr_clk_TIG" = "sdr_clk" EXCEPT "TNM_ddr_sdr_allign";

TIMESPEC "TS_clk100_to_sdr_clk" = FROM "TNM_clk_100_TIG" TO "sdr_clk_TIG" TIG;

-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Visitor bonsaipappel
Visitor
7,195 Views
Registered: ‎03-24-2010

Re: Exclude Paths from TIG Constraint

Jump to solution

Thank for the Reply,

 

I read about the EXCEPT keyword but was not sure how to use it. With the examples it is clear now and working.

 

Thanks again.

0 Kudos