You can import a constraint file as either a source file or an auxiliary file. For details on how to import constraints files, refer to Importing Files.
Import constraints file as source files if they were created with external tools that will be tracked (audited). This helps to coordinate the design changes better. For details on how to import source files, refer to Importing source files.
The following table shows different constraints format files that can be imported as source files for specific families.
|
Source Files |
File Type Extension
|
Family |
|
ProASIC Constraint File (ProASICPLUS, ProASIC) |
*.gcf
|
ProASIC PLUS , ProASIC Note: GCF timing constraints are not supported for ProASIC PLUS |
|
Physical Design Constraint File (ProASIC3/E, Axcelerator) |
*.pdc
|
Fusion, ProASIC3/E, Axcelerator |
|
Synopsys Constraint File |
*.sdc |
Fusion, ProASIC3/E, Axcelerator, |
|
PIN file |
*.pin |
eX, SX-A, SX, 3200DX, 1200XL, MX, ACT3, ACT2, ACT1 |
When you import a constraint file as an auxiliary file, it is not audited and is treated more as one-time data-entry or data-change events, similar to entering data using one of the interactive editors. For details on how to import auxiliary files, refer to Importing Auxiliary files.
The following table shows different constraints format files that can be imported as auxiliary files for specific families.
|
Auxiliary Files |
File Type Extension |
Family |
|
PIN |
*.pin |
ACT1, ACT2, ACT3, MX, 1200XL, 3200DX, SX, SX-A, eX |
|
SDC |
*.sdc |
Fusion, ProASIC3/E, SX-A, eX, Axcelerator, |
|
Physical Design Constraint** |
*.pdc |
Fusion, ProASIC3/E and Axcelerator |
|
Design Constraint File
|
*.dcf
|
ACT1, ACT2, ACT3, MX, 1200XL, 3200DX, SX, SX-A, eX |
|
Switching Activity Intermediate File/Format |
*.saif |
Fusion, ProASIC3/E, Axcelerator, ProASIC,
|
|
Value Change Dump file |
*.vcd |
Fusion, ProASIC3/E, Axcelerator, ProASIC,
|
(*) When you import SDC as an auxiliary file, you can specify only one file in the File > Import Auxiliary Files dialog box.
(**) Not all PDC commands are supported when a PDC file is imported as an auxiliary file; some must be imported as source files. When importing a PDC file as an auxiliary file, the new or modified PDC constraints are merged with the existing constraints. The software resolves any conflicts between new and existing physical constraints and displays the appropriate message. Most PDC commands can be imported as auxiliary files. PDC commands that are not supported when the PDC file is imported as an auxiliary file are noted in their respective help topics.
You can either overwrite or retain your existing timing and physical constraints. For details on how to preserve the existing timing constraints, refer to Keep existing timing constraints in SDC files. For details on how to preserve the existing physical constraints, refer to Keep existing physical constraints.