Understanding Priority of Wildcard LogicLock Region Membership Assignments

You can create conflicting membership assignments between LogicLock regions with wildcard assignments. To avoid this, the Quartus^® Prime Standard Edition software prioritizes assignments as follows:

• Highest priority— node assignments
• Second priority— wildcard assignments
• Lowest priority— entity assignments

These rules of precedence are applied in a manner analogous to the rules of algebra. Just as the rules of algebra specify that multiplication operations are performed before addition operations, these rules specify that node assignments be applied before wildcard or entity assignments. Similarly, wildcard assignments are applied before entity assignments.

The following example illustrates how priorities are determined. Consider a project with the following compilation hierarchy:

Assume the following node, wildcard, and entity assignments:

The above assignments result in the regions being populated as follows: