Quartus II Settings File (.qsf)

The Quartus II Settings File (.qsf) contains all of the project-wide and entity-level assignments and settings for the current revision of the project. A separate Quartus II Settings File exists for each individual revision. The Quartus II Settings File syntax is based on Tcl script syntax.

When you create assignments and settings using the Quartus II wizards and dialog boxes or Tcl commands, the Quartus II software automatically places the assignment at the end of the Quartus II Settings File. If you modify the Quartus II Settings File directly, any assignments you create are recognized, regardless of where in the file you place them.

All text in the Quartus II Settings File preceded by a pound symbol (#) is considered to be a comment and is not processed. Any comments you create maintain the same relative position in the file when you make changes; comments associated with specific assignments may move when you make changes to assignments. The comments remain even if you delete the associated assignment, and the Quartus II software does not delete or change comments when the design is processed

The following commands are used to create the following types of assignments:

Assignment Type	Command
Global Assignment	set_global_assignment
Instance Assignment	set_instance_assignment
Location Assignment	set_location_assignment
Parameter Assignment	set_parameter

The following options are used to define the assignments.

Option	Example	Description
-name		The QSF keyword for the assignment.
-value	set_global_assignment -name family -value Stratix set_global_assignment -name family Stratix	The value of the assignment. The option -value is optional; the assignment is recognized without the -value option.
-to	set_location_assignment iobank_1 -to chiptrip\|\|accel	The source node for the assignment. Used in single-point and point-to-point assignments.
-from	set_instance_assignment -name multicycle 8 -from clock -to timeo	The destination node for the assignment. Used in point-to-point assignments.
-entity	set_global_assignment -name ll_auto_size on -entity filtref -section Region_0	Specifies the entity for the assignment. This option is recognized in all assignments for which it is required, but is only needed when the assignment is for an entity other than the top-level entity. When the -entity option is required and is not present, the Quartus II software applies the assignment to the top-level entity.
-section_id	set_global_assignment -name eda_map_illegal_characters on -section_id eda_simulation	Specifies the LogicLock region, EDA tool type, clique name, breakpoint name, clock name, debug hub name, I/O bank name, or timegroup name for the assignment.
-comment	set_instance_assignment -name auto_carry_chains on -to accel -comment "Carry chain comment.".	Displays any comments you add to the assignment.
-disable	set_instance_assignment -name auto_global_memory_controls off -to clock -disable	Disables the assignment so that it is not processed.
-tag	set_location_assignment PIN_C22 -to in1 –tag "SOPC Builder"	Indicates the tool that created an assignment if the assignment is created outside the Quartus II software.

When creating assignments, you can call assignments from other Quartus II Settings Files using the source keyword and the Quartus II Settings File name you want to call. Using the source keyword allows you to use assignments from any other Quartus II Settings File without having to import the assignments or transfer them to the current Quartus II Settings File. Any assignment called from another Quartus II Settings File takes precedence over assignments read before the source line in the current Quartus II Settings File. For example, the file chiptrip.qsf uses the source keyword to import assignments from new_assignments.qsf:

 

chiptrip.qsf	new_assignments.qsf
set_global_assignment -name top_level_entity chiptrip set_global_assignment -name family max7000b source new_assignments.qsf	set_global_assignment -name device auto

 

After compilation the assignments in new_assignments.qsf are processed as if they were in the file chiptrip.qsf, but the assignments are not copied into chiptrip.qsf.