Visible to Intel only — GUID: mwh1410470989443
Ixiasoft
2.1.2.1. Specify Instance-Specific Constraints in Assignment Editor
2.1.2.2. Specify NoC Constraints in NoC Assignment Editor
2.1.2.3. Specify I/O Constraints in Pin Planner
2.1.2.4. Plan Interface Constraints in Interface Planner and Tile Interface Planner
2.1.2.5. Adjust Constraints with the Chip Planner
2.1.2.6. Constraining Designs with the Design Partition Planner
Visible to Intel only — GUID: mwh1410470989443
Ixiasoft
2. Constraining Designs
The design constraints, assignments, and logic options that you specify influence how the Intel® Quartus® Prime Compiler implements your design. The Compiler attempts to synthesize and place logic in a manner than meets your constraints. In addition, design constraints also have an impact on how the Timing Analyzer and the Power Analyzer influence synthesis, placement, and routing.
You can specify design constraints in the GUI, with scripts, or directly in the files that store the constraints. The Intel® Quartus® Prime software preserves the constraints that you specify in the GUI in the following files:
- Intel® Quartus® Prime Settings file (<project_directory>/<revision_name>.qsf)—contains project-wide and instance-level assignments for the current revision of the project, in Tcl syntax. Each revision of a project has a separate .qsf file.
- Synopsys* Design Constraints file (<project_directory>/<revision_name>.sdc)—the Timing Analyzer uses industry-standard Synopsys* Design Constraint format and stores those constraints in .sdc files.
What's New In This Version
- The current version of the Intel® Quartus® Prime Pro Edition software now supports the Hard Memory Network-on-Chip (NoC) for designs targeting Intel Agilex® 7 M-Series FPGAs only. Refer to Interface Planner NoC Tool Flow and Specify NoC Constraints in NoC Assignment Editor.
- The Intel Agilex device family now has multiple members, as this document reflects throughout.