Loading the Violations Database

The errors generated are cross-probed to the accurate schematic location to enable the editing and correction. While analyzing violations using the Annotation Browser, the mode in which a marker cellview is opened depends upon the Annotation Browser options. This means that it is possible that the marker cellview is opened in edit mode even if the top cellview or current design is opened in read-only mode. If a marker cellview is opened in edit mode and you perform any action that attempts to close the marker cellview, you are prompted to save or discard the changes.

To load the violations database, perform the following steps:

1. Choose Power Manager – Load Violations.
   
   
2. Select the appropriate value for the Scope field. The Library, Cell, View, and Instance Path are read-only fields.
3. Specify the file name and click OK. The Annotation Browser displays the violations in the design.
   
   
4. Specify the scope of the violations, which is based on the cellview hierarchy, to be displayed in the Annotation Browser.
   
   
   Annotation Browser provides easy and in-context error browsing mechanism through context menu for the violation nodes.
   Here is the list of the levels until which you can probe for various nodes:
   • Right-click the Always Enabled Level Shifter node. Then, click Probe – Inst/Driver/ Receiver.
   • Right-click the Incompatible Level Shifter Signal node. Then, click Probe – Net/Inst/Driver/ Receiver.
   • Right-click the Incompatible Level Shifter Supply node. Then, click Probe – Inst.
     
     
   • Right-click the Missing Level Shifter node. Then, click Probe – Net/Driver/ Receiver.
   • Right-click the Protected Level Shifter node. Then, click Probe – Inst/Driver/ Receiver.
     
     
   • Right-click the Redundant Level Shifter node. Then, click Probe – Inst.
   • Right-click the Unused Enabled Level Shifter node. Then, click Probe – Inst/Driver/ Receiver.
   • Right-click the Bulk Error node. Then, click Probe – Inst.
   • Right-click the Missing Isolation node. Then, click Probe – Net/Driver/ Receiver.
   • Right-click the Incompatible Isolation signal node. Then, click Probe – Driver/ Receiver.
   • Right-click the Redundant Isolation signal node. Then, click Probe – Inst.

Related Topics

Defining the Severity of Design Checks

Level Shifter Checks

Isolation Checks

Bulk Checks

Checking a Design in Foreground Mode

Checking a Design in Background Mode

Filtering Violations

Generating Signal Information

Return to top