check_routability
check_routability
[ -net {s_netName…} ]
[ -region {f_xlo f_ylo f_xhi f_yhi} ]
[ -exclude_net {s_netName…} ]
[ -exclude_type {[power][ground][clock]} ]
[ -clear_annotations ]
[ -error_limit i_count ]
[ -no_blockage_check ]
[ -no_coverobs_check false ]
[ -no_direction_check ]
[ -no_floating_shape_check ]
[ -no_grid_check ]
[ -no_min_space_check ]
[ -no_min_width_check ]
[ -no_out_of_bndry_check ]
[ -no_pin_center_on_track_check ]
[ -no_pin_on_grid_check ]
[ -no_pin_on_track_check ]
[ -no_prbndry_check ]
[ -no_via_check ]
Description
Checks the active design for known conditions that can cause potential routing problems. Design Rule Checks applied to pins and some routability checks are performed primarily to determine the accessibility of pins. Additional routability checks address special issues, such as the presence of differential pair nets. By default, missing cover obstruction checks are excluded and must be enabled using -no_coverobs_check false. All other checks are enabled by default and can be excluded by specifying its respective argument when this command is invoked. Annotations are automatically created for violations, except cover obstruction and PR boundary violations.
If violations are reported, use the Violations Browser (Collaborate—Annotation Browser—Violations) to locate them.
The following table describes the checks that are performed and how they are categorized in the Violations Browser.
A Routability Report is output to the Transcript area that summarizes the violations that are found. For example,
+-------------------------------------------------+
| Routability Report Summary: |
+-------------------------------------------------+
| 0 Min Spacing violation(s) |
| 0 Min width violation(s) |
| 0 Grid violation(s) |
| 10 Via violation(s) |
| 0 Blockage violation(s) |
| 0 Floating shape violation(s) |
| 0 Diffusion shape violation(s) |
| 2 Diff pair nets violation(s) |
+-------------------------------------------------+
| 56 pin(s) found |
| 56 pin(s) checked |
| 0 pin(s) already connected |
| 12 pin(s) not used (skipped) |
+-------------------------------------------------+
More severe issues, such as DRC violations, should be dealt with before attempting to use the data.
Diffusion shapes on the drawing purpose will not be seen by Space-based Router and Chip Optimizer. To be recognized and processed, they must be mapped to either diffusion:blockage or diffusion:pin shapes using map_purpose.
Differential pair nets are not routed in the regular routing flow and require special attention. For more information on routing these nets, refer to Pair Routing Commands.
Arguments
Related Topics
Return to top