report_timing:
To report detailed timing report.below are the few options and values which most useful in this PT command
-delay_type delay_type
Specifies the type of path delay to be reported. Valid values are max (the default), min, min_max,max_rise, max_fall, min_rise, or min_fall. The "rise" or "fall" in the delay_type specifies a rising or falling transition at the path endpoint.
-slack_lesser_than lesser_slack_limit
Indicates that only those paths with a slack less (more negative) than lesser_slack_limit are to be shown. To show paths within a specific slack range, use this option together with -slack_greater_than.
-nosplit
Most of the design information is listed in fixed-width columns. If the information in a given field exceeds the column width, the next field begins on a new line, starting in the correct column. The -nosplit option prevents line-splitting, which is useful for scripts that extract information from the report output.
-nworst paths_per_endpoint
Specifies the number of worst paths to be reported per endpoint. Allowed values are 1 to 2000000; the default is 1.
-max_paths count
Specifies the maximum total number of paths to be reported among all path groups. If you specify -max_paths greater than 1, and you did not explicitly specify -slack_lesser_than, PrimeTime automatically sets -slack_lesser_than to 0 and reports violating paths only. Allowed values are 1 to 2000000; the default is equal to the -nworst setting.
-path_type format
Specifies the format of the path report and how the timing path is displayed. The allowed values are
- short - Displays only start and endpoints in the timing path.
- full (the default) - Displays the full path.
- full_clock - Displays full clock paths in addition to the full timing path.
- full_clock_expanded - Displays full clock paths between a primary clock and a related generated clock in addition to the full_clock timing path.
- end - Generates a report with a column format that shows one line for each path and shows only the endpoint path total, required-time, slack and CRP (clock reconvergence pessimism value) when thetiming_remove_clock_reconvergence_pessimism variable is set to true
- summary - Displays only the path without the accompanying required-time and slack calculation
-nets
Indicates that nets are to be shown in the path report. The default is not to show nets.
-crosstalk_delta
Indicates that annotated delta delay and delta transition time is reported. The deltas are computed during crosstalk signal integrity analysis, or they can be annotated manually using the set_annotated_delay -delta_only and set_annotated_transition -delta_only commands. Note that the -crosstalk_delta option only reports the calculated or annotated deltas; it does not initiate crosstalk analysis. Only deltas on input pins are shown. Delta transition time is shown only with the -transition_time option. The -crosstalk_deltaoption automatically sets the -input_pins option.
-pba_mode none | path | exhaustive
This option controls path-based analysis.
- none (the default) - Path-based analysis is not applied.
- path - Path-based analysis is applied to paths after they have been gathered.
- exhaustive - An exhaustive path-based analysis path search algorithm is applied to determine the worst path-based analysis path set in the design. If you use exhaustive, you cannot use the -start_end_pair or path_collection options.
-from from_list
Specifies that only paths from the named pins, ports, nets, cell instances, or startpoints clocked by named clocks are to be reported. If from_list is not specified, the default behavior reports the longest path to an output port if the design has no timing constraints. Otherwise, the default behavior is to report the path with the worst slack if the design has timing constraints.
-to to_list
Specifies that only paths to the named pins, ports, nets, cell instances, or endpoints clocked by named clocks are to be reported. If to_list is not specified, the default behavior reports the longest path to an output port if the design has no timing constraints. Otherwise, the default behavior is to report the path with the worst slack if the design has timing constraints. If a clock object is to be specified with the -to option, it must be specified as a collection (that is, using [get_clocks clock_name].
-through through_list
Specifies that only data paths through the named pins, ports, cell instances, or nets are to be reported. You cannot use this option to report clock paths. If the through_list option is not specified, the default behavior reports the longest path to an output port if the design has no timing constraints. Otherwise, the default behavior reports the path with the worst slack if the design has timing constraints.
No comments:
Post a Comment