Guardian DRC vs. Other DRC Systems, I

1. Introduction

This article begins a series of articles that describe the compatibility of Guardian DRC system[1] in terms of functionality: command set, syntax and implementation with other leading industrial DRC systems. The purpose of this series is to facilitate the usage of Guardian DRC system by the designers who are already familiar with some other DRC systems.

Although basic DRC operations performed by various DRC systems correspond to “natural” operations possible with geometric shapes: Boolean operations, selection, resizing, distance checking, the implementations vary both in syntax and in the way of actual execution. This sometimes may lead to wrong expectations about certain functionalities, unless the designers are aware of these differences..

Guardian DRC system includes automatic DRC rule translators for several popular DRC formats. Nevertheless the knowledge of differences in commands may be useful not only when writing new DRC rules from scratch. For example, it may prove useful for optimization of rule sets, since automatic translation sometimes does not deliver the best possible implementation of certain checks, especially when converting from systems with limited command set. For example, Dracula(TM) DRC system has very limited capabilities to operate with separate edges from shape boundaries. Also, often it is necessary to put additional checks into the DRC deck, to comply with local technology variations and/or limitations of design methodologies..

The goal of Guardian DRC is to provide all the functionality required for performing modern DRC operations. When compared to other DRC systems, Guardian DRC either provides direct counterparts of commands or converts them into groups of several commands. In some cases this way opens possibilities for an additional optimization of execution time.

 

2. Compatibility with Calibre™ DRC System

This section is a general overview of the correspondence of Calibre and Guardian DRC commands. Detailed comparisons of particular commands will be provided in subsequent articles of the series.

 

2.1. Overall Execution and Syntax

The most important differences in DRC rule set execution are the following.

  • Calibre DRC syntax allows layer generation statements to be written later in the DRC rule file, after their use in other commands. DRC rule compiler automatically defines proper order of execution of DRC commands. In Guardian DRC this possibility can be turned on by the setup directive “free_layer_definition_order”
     
  • Calibre merges original layers on input to the DRC system. In Guardian DRC this possibility can be turned on by the setup directive “merge_input”
     
  • The syntax of Guardian DRC is based on pairs “parameter-value”, and commands have an explicit terminator, a semicolon. This provides an additional flexibility in writing down the rule set, at the price of brevity
     
  • Newer versions of Guardian DRC have a simplified syntax for writing the constraints for numerical values in checks and selection operations
     
  • Usually Guardian DRC runs integrated into Expert Layout Editor [2]. By default, Guardian returns all layers, generated during DRC execution, unless their names start with the ampersand (&). This behavior may be flexibly controlled by the setup directive “Update_Layout”
     
  • DRC error reporting in Guardian DRC differs from that of Calibre. This will be covered in a separate article
     
  • Both Calibre and Guardian use layer names in DRC rule sets, that are independent of the names in a layout system. Calibre can define its layers as combinations of original layers. In Guardian DRC, to achieve the same functionality, the rule set must explicitly contain “OR” or “COMBINE” commands

 

2.2. Particular Types of Commands

The commands are classified here in the following main groups: setup directives, connectivity/antenna checks, metric checks and all other operations. Although the Metric Checks group constitute only four commands, the total number of different actual operations performed by the set commands is comparable to the number of all commands, since metric checks are controlled by a large number of parameters.

 

2.2.1. Metric DRC Checks (See Table 1)

The “Rectangle enclosure” command of Calibre is in fact a more efficient implementation of enclosure checks for rectangular shapes. Currently Guardian DRC performs these operations by general means.

The way of actually performing measurements between line segments in Guardian DRC is described in detail in [3]. The described metrics correspond to those used in Calibre DRC system.

An important difference arises from the fact that Guardian DRC does not perform automatic merging of input layers. In certain cases this can lead to time optimization, if it is known that certain layers are created from non-overlapping shapes, e.g., contact or via layers. Therefore to ensure consistency of metric check, one must be sure that the input layers are merged. Notice that many DRC operations with layers provide merged output.

Table 1. Metric DRC Checks

2.2.2. Parameters of Metric Checks (See Table 2)

Metric checks in Calibre and Guardian DRC differ in the way of the output of the results. This difference will be covered in detail in one of the subsequent articles.

Another difference is in the reporting error segments. The way Calibre does it corresponds to Guardian’s option “Report error subsegments”. This option may be set either for each DRC command individually, or globally, by a setup directive.

Table 2. Parameters of Metric DRC Check Commands.

Legend:

= already existed in Guardian DRC
- not implemented yet
+ added
~ difference in implementation exist

 

2.2.2. Connectivity/Antenna Checks (See Table 3)

Antenna checks of Calibre are converted into pairs of operations: obtaining of layer parameters and the subsequent checking of them. This way of implementation allows for optimization of execution time when the same parameters for certain layers are used in several antenna checks.

Table 3. Connectivity/antenna DRC Checks


Legend:

= already existed in Guardian DRC
+ added

 

2.2.3. Other DRC Operations (See Table 4)

The notion of “check” of Calibre rule files is converted into preprocessor “block” notion of Guardian DRC script file.

 

Table 4: Other DRC Operations

Legend:

= already existed in Guardian DRC
- not implemented yet
+ added
~ difference in implementation exist

 

2.2.4. Setup Commands (See Table 5)

Guardian DRC provides the setup for execution of the DRC script in three ways: through user interface, through command line parameters of the batch mode of execution and by means of setup directives of the DRC script itself.

 

Table 5. DRC Setup Commands

Legend:

= already existed in Guardian DRC
- not implemented yet
+ added
~ difference in implementation exist
hier marks commands related to hierarchical execution, not supported in current implementation of Guardian DRC
UI marks commands implemented only by means of user interface of Guardian DRC

 

References

  1. Guardian User’s Manual, Silvaco International.
  2. Expert and ExpertViews User’s manual, Silvaco International.
  3. Measurements in Spacing Checks of Guardian DRC, Simulation Standard, vol. 13, no 9.

 

Download pdf version of this article