Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17268 Discussions

Question about Example 1-22 of Quartus Prime TimeQuest Timing Analyzer Cookbook

Altera_Forum
Honored Contributor II
‎10-31-2017 01:57 PM
1,117 Views

In Example 1-22 of "Quartus Prime TimeQuest Timing Analyzer Cookbook", the latency of clk_a and clk_b is specified. clk_a and clk_b are in the different clock_groups. However, if is normal that they are not used in set_input_delay and set_output_delay. Why should the latency and clock_groups for clk_a and clk_b be specified if they are used in the set_input_delay and set_out_delay?  

 

Also  

set input_max [expr $Td_max + $Tco_max] 

 

set input_min [expr $Td_min + $Tco_min] 

 

# Create the input delay constraints when clk_a is selected 

 

set_input_delay  

-clock virtual_source_clk_a  

 

-max $input_max  

 

[get_ports datain] 

 

set_input_delay  

 

-clock virtual_source_clk_a  

 

-min $input_min  

 

[get_ports datain] 

 

 

Are there the differences in the clock paths missing in $input_max and $input_min?  

 

Thanks
0 Kudos

Link Copied

0 Replies
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.