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.
17267 Discussions

why the same path have different clock delay ?

Altera_Forum
Honored Contributor II
1,541 Views

why the same path have different clock delay ? 

 

The "Data Arrival Path" and the "Data Required Path" route the same path ,from "PLLREFCLKSELECT_X0_Y7_N0" to "CLKCTRL_G5", but why the time Incr are different ? 

 

thanks for your help. 

https://www.alteraforum.com/forum/attachment.php?attachmentid=7448
0 Kudos
4 Replies
Altera_Forum
Honored Contributor II
825 Views

Within a given timing model(say slow 100) there are two sub-models, a slow and fast sub-model. This accounts for the fact that even if the die is at a given corner, individual paths will vary, which is generally called On-Die Variation. When doing setup analysis on a path, the Data Arrival will use the slow sub-model and Data Required will use the fast. This then flips if you do hold analysis on the exact same path. 

But in your case, it's a single clock path, how can it vary? It can't, which is why a thing called Common Clock Path Pessimism Removal will remove this variation. If you scroll further down the Data Required Path, you should see a line-item call pessimisim. It is added to the Data Required Path, which helps timing(makes the slack better), and counteracts this on-die variation modeling on a common clock path.  

On alterawiki.com there is TimeQuest User Guide I put together that talks about this. (Although it's not a lot more than what I've said here.)
0 Kudos
Altera_Forum
Honored Contributor II
825 Views

 

--- Quote Start ---  

Within a given timing model(say slow 100) there are two sub-models, a slow and fast sub-model. This accounts for the fact that even if the die is at a given corner, individual paths will vary, which is generally called On-Die Variation. When doing setup analysis on a path, the Data Arrival will use the slow sub-model and Data Required will use the fast. This then flips if you do hold analysis on the exact same path. 

But in your case, it's a single clock path, how can it vary? It can't, which is why a thing called Common Clock Path Pessimism Removal will remove this variation. If you scroll further down the Data Required Path, you should see a line-item call pessimisim. It is added to the Data Required Path, which helps timing(makes the slack better), and counteracts this on-die variation modeling on a common clock path.  

On alterawiki.com there is TimeQuest User Guide I put together that talks about this. (Although it's not a lot more than what I've said here.) 

--- Quote End ---  

 

 

Hi Rysc: 

 

Why you said it is a common clock path? It is apparent a data path from the image! The TimeQuest just show the data path's time information!
0 Kudos
Altera_Forum
Honored Contributor II
825 Views

The Data Arrival Path is showing the Source Clock Path + Data Path. The Data Required Path is showing the Destination Clock Path. The part shown in the screen-shots is just the clock path portion of each one. (I believe it's an older version of Quartus, as the newer ones have a more clear demarcation in the Data Arrival Path of which part is Clock and which part is Data).

0 Kudos
Altera_Forum
Honored Contributor II
825 Views

thank you for your help, Rysc, and I am reading your <TimeQuest User Guide >, it is excellent !!

0 Kudos
Reply