Altera SDC and TimeQuest API - Manual (Page 136)

2–126 Chapter 2: SDC and TimeQuest API Package and Commands
sta
SDC and TimeQuest API Reference Manual © December 2009 Altera Corporation
Description
Reports the status and timing analysis results per timing exception.
For each timing exception, it first reports the status: Complete, Partially Overriden, Fully Overridden, or
Invalid. The status is relative to the paths and analyses coverred by the -from, -to, and other options.
Therefore, a timing exception that reports a status of "Complete" when using the -from and -to options
may not actually be complete with respect to the full design.
Complete: The exception has not been overridden and is valid (i.e., there are paths affected by this
exception).
Partially Overridden: The exception includes some paths that have been overridden by one or more
higher-precedence exceptions.
Fully Overridden: All paths affected by this exception have been overridden by one or more
higher-precedence exceptions.
Invalid: There are no paths applicable covered by this exception. This occurs when a timing exception has
valid -from, -to, or -through collections and there are no actual paths from the -from nodes to the -to nodes.
Use the -setup (default), -hold, -recovery, or -removal options to specify which kind of analysis should be
performed.
The report can be directed to the Tcl console using -stdout (default), a file using -file, the TimeQuest
graphical user interface using -panel_name, or any combination of those three options.
You can limit the analysis performed by this command to specific start and end points, using the -from and
-to options. The anlaysis can be further limited to clocks using the -from_clock and -to_clock options, or to
specific edges of the clock using the -rise_from_clock, -fall_from_clock, -rise_to_clock, and -fall_to_clock
options. Additionally, the -through option can be used to restrict analysis to paths which go through
specified pins or nets.
To determine which timing exceptions override another timing exception when the status is Partially
Overridden or Fully Overridden, use the same -from and -to options that were used with the timing
exception.
Use the -npaths option to limit the number of paths to report per timing exception. If you do not specify
this option, only the single worst-case path per timing exception is provided. Use the -less_than_slack
option to limit output to all paths with slack less than the specified value, up to the number specified by
-npaths.
Use the -nworst option to limit the number of paths reported for each unique endpoint. If you do not
specify this option, the number of paths reported for each destination node is bounded only by the -npaths
option. If this option is used, but -npaths is not specified, then -npaths will default to the same value
specified for -nworst.
Use the -detail option to specify the desired level of report detail. Specifiying "summary" generates a single
table listing only the highlights of each timing exception (status and worst-case slack). "path_summary"
generates a table per timing exception listing only the highlights of each path. "path_only" reports the path
from the source to the destination without any detail about the clock path. Instead, the clock network
delay is shown as a single number. This is the default behavior. "path_and_clock" extends the arrival and
required paths back to the launch and latch clocks. "full_path" will continue tracing back through
generated clocks to the underlying base clock.
Use the -pairs_only option to filter the output further, restricting the results to only unique combinations
of start and end points. This filtering is performed after the number of paths has been generated in
accordance to the -npaths option. As a result, there may be fewer paths displayed than specified by
-npaths, if a particular set of start and end points appeared multiple times.