Honored Contributor
Honored ContributorI have not yet found a way to get Quartus project parameters from the SDC file. It's a feature that I would definitely like to see added.
So as a workaround here is what I did. 1 - Define a "project_settings.v" file that contains your top level macro definitions and parameters. This file should contain all parameters needed to control your project. Include this file from your top level. 2 - From your SDC script, open the "project_settings.v" file and read your settings. Then generate your timing constraints based on those settings. So for example, I have a project that has 4 DDR3 controllers. The "project_settings.v" file determines which of those are actually enabled using "`define" statements. My project code knows whether or not to compile in each controller based on the macro setting. The timing script also reads the file and determines whether or not to perform timing analysis for each controller based off the settings in the file. Not the ideal solution but it works well enough for me. Jake
