--- Quote Start ---
1) Which commands should definitely be placed in the .sdc file? I'm trying to determine if there which commands to use, since the .sdc file is used for both timing-driven place and route and for timing analysis. It seems to be that all clock (including PLLs, etc) and I/O constraints should be placed in the .sdc file, and all other report_timing commands should be placed in separate .tcl scripts.
--- Quote End ---
Your last sentence is what Altera recommends. In addition, SDC commands like false-path exceptions belong in the .sdc file, and commands like create_timing_netlist should be in a .tcl file for a scripted setup.
--- Quote Start ---
2) I'm familiar with Synopsys PrimeTime, so using TimeQuest is fairly straight-forward. However, there are differences in usage. Has anyone generated scripts or docs that described using the TimeQuest commands? I'm particularly interested in constraints applied to PLLs and to I/O.
--- Quote End ---
The examples that immediately come to mind are in training material, but this should also be covered in the Quartus handbook and examples at
www.altera.com. The handbook has a chapter specifically on TimeQuest. The following chapter on switching to TimeQuest might also have some good examples. TimeQuest might be included in the training that you can access for free through the web site.
If you haven't found derive_pll_clocks yet, look up that one. It's covered in the Quartus on-line help.
Honored Contributor
