The Rule Editor Dialog Box is displayed.
This information appears in the window at the bottom of the Rules Wizard.
The next pages allow primitives and conditions for signals and pin conditions to be defined.
The Edit Primitive Value(s) Dialog Box is displayed.
The rule is executed when the primitive is, is not, contains, does not contain, matches, or does not match the values defined in the Operand: field or selected from the list of available values (present depending upon the type of operator).
Regular Expression Filters may be used to specify values. Clicking the arrow next to the Operand: field gives suggestions of commonly used regular expression filters.
Primitive details are added to the window at the bottom of the Rules Wizard.
| Note | |
|
When setting “Allow” rules, any signals or pins which do not qualify the rule will be disallowed by default. If you want all signals and pins to be usable, ensure that you set additional terms to allow those signals and pins to be assigned. This is demonstrated in "Setting a Rule for an FPGA Device". |
|
The rule is created and will be present in the Rules: field in the Rule Editor Dialog Box.
Example 7-1. Setting a Rule for an FPGA Device
The following example creates locate rules for an FPGA device. The intent of the rule is to locate the ALU busses and strobe to banks 6 and 10 in the top left quadrant of the Xilinx Virtex 4 part.
The Set rule name and description page allows you to enter a name for the new rule in the Name field, a description for the rule in the Description field, and in the Failure answer field, you can enter some text that will be returned if the attempted assignment breaks this rule.
This sets the primitive to use all signals that start with “ALU”.
This adds a term to the rule to allow use of signals that don’t start with “ALU”.
Additional terms can also be set up to make more rule assignments for a different set of signals.