Mentor v8.6_4 ユーザーズマニュアル
Command Dictionary
Analyze Drc Violation
FastScan and FlexTest Reference Manual, V8.6_4
2-131
Analyze Drc Violation
Tools Supported: DFTInsight, FastScan, and FlexTest
Scope: Setup and Atpg modes
Prerequisites: This command operates only after the design rules checker
encounters a rule violation.
Usage
ANAlyze DRc Violation rule_id-occurrence#
DFTInsight Menu Path:
Analyze > Drc Violation...
Description
Generates a netlist of the portion of the design involved with the specified rule
violation number.
violation number.
When you issue the Analyze Drc Violation command, the tool includes different
simulation data into the netlist depending on the type of rule violation. Even
though DFTInsight displays the simulation data, the gate reporting data within the
tool session does not change, unless you use the DFTInsight Setup >
GateReport >... menu option.
simulation data into the netlist depending on the type of rule violation. Even
though DFTInsight displays the simulation data, the gate reporting data within the
tool session does not change, unless you use the DFTInsight Setup >
GateReport >... menu option.
If you invoke DFTInsight before you issue the Analyze Drc Violation command,
the viewer automatically displays the graphical representation of the netlist and
marks key instances in the schematic view. Otherwise, DFTInsight is
automatically invoked, displaying the netlist.
the viewer automatically displays the graphical representation of the netlist and
marks key instances in the schematic view. Otherwise, DFTInsight is
automatically invoked, displaying the netlist.
Arguments
•
rule_id-occurrence#
A literal and integer argument pair that specifies the exact design rule violation
(including the occurrence) that you want to analyze. The tool traces the
violation back to the probable cause and then the schematic viewer displays all
the gates in that trace. The argument must include the design rules violation ID
(rule_id), the specific occurrence number of that violation, and the hyphen
between them. For example, you can analyze the second occurrence of the C3
rule by specifying C3-2. The tool assigns the occurrences of the rules
(including the occurrence) that you want to analyze. The tool traces the
violation back to the probable cause and then the schematic viewer displays all
the gates in that trace. The argument must include the design rules violation ID
(rule_id), the specific occurrence number of that violation, and the hyphen
between them. For example, you can analyze the second occurrence of the C3
rule by specifying C3-2. The tool assigns the occurrences of the rules