Change path name in qsf to sdc

There are no .qsf timing settings used by TimeQuest. That setting is for the Classic Timing Analyzer.

My guess is you're using "derive_pll_clocks" which names the PLL outputs with the long hierarchical pin name. Note that you can go to TimeQuest's Info messages at the bottom, and where this assignment is called out, it shows the individual "create_generated_clock" assignments for each PLL output. You can cut and paste these into your .sdc and change the -name option to something more readable. The only major downside with this is that if you change your PLL, you need to manually change these assignments to match them.

Personally, I've seen that mistake happen to often and just accept the longer PLL names. (I think Altera plans on having a better workaround for long PLL names someday, but it's something that should have been done years ago...)

Hi,

yes , I use "derive_pll_clocks -create_base_clocks" in sdc.

popurse of using is Mega_wizard setting reflect automaticaly in sdc.

I hesitated to use "create_generated_clock".

and,I want to change more readable any signal in sdc.

example is

//**********************************************************************

1.

set_multicycle_path -end -setup -from

[get_keepers {average_calc:average_calc|r_avr_data

[*]}] -to

[get_keepers {average_calc:average_calc|r_mul_data

[*]}] 2

2.

set_output_delay -max 2 -clock pll|altpll_component|pll|clk[1] [get_ports out_data

[*]]

//**********************************************************************

How can I make shorter "average_calc:average_calc|r_avr_data

[*]"

and "pll|altpll_component|pll|clk[1]"?

You can use a Tcl variable:

set fast_clk {pll|altpll_component|pll|clk[1]}

Then use the variable like so:

set_input_delay -clock $fast_clk ...

You might have to work with it a little to get wildcards like the average_calc example.

Also, for exact names, TimeQuest doesn't need the entity name. Notice that the PLL name doesn't do entity_name:instane|entity_name:instance|... for each hierarchy, and instead just does the instance name between pipes. I don't think you can mix this nomenclature with wildcards though, but not certain.