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!

The tools recognize that the FROM-TO with PRIORITY 10 has precedence over the constraint with PRIORITY 11. Is this correct?

Solution

Yes, this is correct.

The PRIORITY keyword can only be used to mitigate constraint overlaps between constraints with the same type and scope. In this particular case, the constraint TS_test has a user-defined FROM group and a pre-defined TO group (FFS), whereas the other constraints in question have both a user-defined FROM and TO group, which gives them higher precedence. Since these constraints have higher precedence (scope), the PRIORITY keyword will have no effect on path coverage between these constraints with different scope.

In the TSI report, you will see the following:

* Constraint coverage over a set of paths is based on the following precedence * * order (lowest to highest precedence): * * * * Unconstrained path analysis * * PERIOD or FREQUENCY, allclocknets * * PERIOD or FREQUENCY, time group * * PERIOD or FREQUENCY, net * * OFFSET IN/OUT, global * * OFFSET IN/OUT, time group * * OFFSET IN/OUT, pad * * MAXDELAY path, with pre-defined FROM and TO groups * * MAXDELAY path, with user-defined FROM or TO group * * MAXDELAY path, with user-defined FROM and TO groups * * MAXDELAY path, with intermediate (THRU) points * * PATH definition * * TIG path *

Note that constraints with user-defined "FROMandTO" groups take precedence over constraints with "FROM or TO" groups (i.e., a constraint with a pre-defined to group).

A user-defined priority associated with a path delay constraint will be used by the Timing Wizard to resolve overlapping or duplicate timing constraints that have a similar scope. For instance, if two MAXDELAY FROM:TO specific.