Forum Discussion
Contributor22.1 pro: set_instance_assignment not accepting wildcard?
Actually, you don't have to do a full compilation, just Analysis & Elaboration.
But as mentioned, when you edit the .qsf manually and the design has not been compiled yet, when you use the wildcard, Quartus does not know about that object yet.
If you were to use the GUI instead, you always have to perform at least Analysis & Elaboration first so signals and objects appear in the Pin Planner or the Assignment Editor. It's the same situation here.
Contributor@ShengN_Intel Sorry, I have one more question:
I want to keep Quartus away from my files. I still don't understand why HW vendors think it's a good idea to let the tool modifying the user's files.
I don't want to have anything I can store somewhere else in the .qsf. The pin locations with its constraints is a good example.
I come from Xilinx and Vivado accepts a tcl file containing pin assignments and constraints. I try that with Quartus, the set_location_assignment aren't detected...
Please tell me the way I can keep a single tcl/sdc file containing all the pins and their constraints in a single file that will never be modified by Quartus and loaded when I open the project.
Super ContributorYou have to source the separate file from the .qsf:
source io_assignments.tcl
