Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
16654 Discussions

How to use wildcard to report all timing path in TimeQuest

NuvKFC
New Contributor I
548 Views

Following picture shows the design.

Due to lacking of clock, the design use LCELL to generate a pulse to wake up  system clock.

 

The design:

NuvKFC_0-1658731246512.png

 

I use follow command to report the delay between LCELLs because I had constrained "set_min_delay" as follows.

 

constraint:

set_min_delay 0.5 -from [ get_pins {top|IP_*|Inp_dly*|dly*d|combout}] \

                                  -to      [ get_pins {top|IP_*|Inp_dly*|dly*d|data*}]

 

report command:

report_path -from [ get_pins {top|IP_*|Inp_dly*|dly*d|combout}] \

                       -to      [ get_pins {top|IP_*|Inp_dly*|dly*d|data*}]

                       -npaths 1000 -panel_name LCELLs_delay

 

After using the report command in TimeQuest, there only report the delay from "Inp_dly1|dly1d|combout" to "Inp_dly2|dly4d|data*".

 

How to report all delay between LCELLs?

 

Thank you very much.

0 Kudos
1 Solution
RichardTanSY_Intel
533 Views

The report_path reports the longest delay paths and the corresponding delay value. That could be reason why only path from "Inp_dly1|dly1d|combout to "Inp_dly2|dly4d|data*" is reported.

Try to specify the start and end point if want to check the delay between the specific LCELL.


Reference: https://www.intel.com/content/www/us/en/docs/programmable/683432/21-3/tcl_pkg_sta_ver_1.0_cmd_report_path.html


View solution in original post

0 Kudos
6 Replies
RichardTanSY_Intel
534 Views

The report_path reports the longest delay paths and the corresponding delay value. That could be reason why only path from "Inp_dly1|dly1d|combout to "Inp_dly2|dly4d|data*" is reported.

Try to specify the start and end point if want to check the delay between the specific LCELL.


Reference: https://www.intel.com/content/www/us/en/docs/programmable/683432/21-3/tcl_pkg_sta_ver_1.0_cmd_report_path.html


0 Kudos
NuvKFC
New Contributor I
526 Views

Hi RichardTanSY_Intel

    Oh, I get it. Thank you, RichardTanSY_Intel, so much.

 

Can I ask another question?

 

You said that "specify the start and end point if want to check the delay between the specific LCELL."

 

Could I use "report_path" command twice to report the delay into the same panel? 

 

Ex.

(1)

report_path -from [ get_pins {top|IP_1|Inp_dly1|dly1d|combout}] -to [ get_pins {top|IP_1|Inp_dly1|dly2d|data*}]

                       -npaths 1000 -panel_name LCELLs_delay

 

(2)

report_path -from [ get_pins {top|IP_1|Inp_dly1|dly2d|combout}] -to [ get_pins {top|IP_1|Inp_dly1|dly3d|data*}]

                       -npaths 1000 -panel_name LCELLs_delay

 

There use "report_path" command twice.

Could the second  "report_path" command report the delay that append into the same "LCELLs_delay" panel, but not overwrite? 

 

Thank you very much.

0 Kudos
RichardTanSY_Intel
523 Views

You can use the report_path command multiple time but you will need to use a different panel name else it will be overwritten.


0 Kudos
NuvKFC
New Contributor I
518 Views

Hi RichardTanSY_Intel

    OK, I understand it. Thank you, RichardTanSY_Intel, so much.

0 Kudos
RichardTanSY_Intel
510 Views

I’m glad that your question has been addressed. With that, I will now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.


Best Regards,

Richard Tan


p/s: If any answer from the community or Intel support are helpful, please feel free to give Kudos and select the best solution. 


NuvKFC
New Contributor I
444 Views

Hi RichardTanSY_Intel

    OK. Thank you, RichardTanSY_Intel, so much.

0 Kudos
Reply