|
|
|
|
|
The UCF file is an ASCII file specifying constraints on the logical design. You create this file and enter your constraints in the file with a text editor.
Note: You can also use the Constraints Editor to create constraints within a UCF file. Refer to the Constraints Editor Guide for details.
These constraints affect how the logical design is implemented in the target device. The file can also be used to override constraints specified during design entry, earlier in the design flow.
There are several types of logical constraints in the UCF file.
These constraints and the syntax for entering them in the UCF are described in the “Attributes, Constraints, and Carry Logic” chapter of the Libraries Guide. A more detailed description of timing constraints can be found in the “Using Timing Constraints” chapter of this manual, the Development System Reference Guide.
The UCF file is an input to NGDBuild (see the “UCF File Flow” figure). The constraints in the UCF file become part of the information in the NGD file produced by NGDBuild. Some of these constraints are used when the design is mapped by MAP and some of the constraints are written into the PCF (Physical Constraints File) produced by MAP. The constraints in the PCF file are used by the each of the physical design tools (for example, PAR and the timing analysis tools), which are run after your design is mapped.
Figure 5.1 UCF File Flow