Intel® Quartus® Prime Pro Edition User Guide: Design Optimization
A newer version of this document is available. Customers should click here to go to the newest version.
Visible to Intel only — GUID: mwh1391807302568
Ixiasoft
Visible to Intel only — GUID: mwh1391807302568
Ixiasoft
6.5.8.13.4. Tips for Creating a .tcl Script to Monitor Critical Paths Across Compiles
This behavior happens in high speed designs where many register-to-register paths have very little slack. Different placements can then result in timing failures in the marginal paths.
- In the project directory, create a script named TQ_critical_paths.tcl.
- After compilation, review the critical paths and then write a generic report_timing command to capture those paths.
For example, if several paths fail in a low-level hierarchy, add a command such as:
report_timing –setup –npaths 50 –detail path_only \ –to “main_system: main_system_inst|app_cpu:cpu|*” \ –panel_name “Critical Paths||s: * -> app_cpu”
- If there is a specific path, such as a bit of a state-machine going to other *count_sync* registers, you can add a command similar to:
report_timing –setup –npaths 50 –detail path_only \ –from “main_system: main_system_inst|egress_count_sm:egress_inst|update” \ –to “*count_sync*” –panel_name “Critical Paths||s: egress_sm|update -> count_sync”
- Execute this script in the Timing Analyzer after every compilation, and add new report_timing commands as new critical paths appear.
This helps you monitor paths that consistently fail and paths that are only marginal, so you can prioritize effectively