mychip station pro verification reference manualseloco.com/mycad_/customer/manual/veriproref.pdf ·...

Powerful Design Solution on Windows

MyChip Station Pro Verification

Reference Manual

Version 2011

June 2011

Copyright Information MyChip Station Pro 2011 is produced by SELOCO Incorporated. Unauthorized copying, duplication, or other reproduction is prohibited without the written consent of SELOCO,Inc.. This document is protected by copyright and distributed under licenses restricting its use, copying, and distribution. No part of this document may be reproduced in any form by any means without prior written authorization of SELOCO,Inc and its licensors, if any. Copyright © 1992 – 2011, SELOCO Incorporated. Copyright © 1992 – 2011, MyCAD Incorporated. All rights reserved. Confidential. Online documentation may be printed by licensed customers of SELOCO Incorporated for internal business purposes only. Published : June 2011 SELOCO, Inc. 4F Daegun Bldg, Songpa-dong 27-12 Songpa-gu, Seoul, 138-848 Korea Phone: +82-2-3433-0000 Fax: +82-2-3433-0099 E-mail: [email protected], [email protected] Home page: http://www.seloco.com MyCAD, Inc. 528 E. Weddell Drive, Suite #3 Sunnyvale, California 94089, USA Phone: 408-745-6785 Fax: 408-745-6783 Email: [email protected], [email protected] Home page: http://www.mycad.com

mailto:[email protected]


http://www.seloco.com/



http://www.mycad.com/

MyChip Station Pro 2011 Verification Reference Manual

TABLE OF CONTENTS

INTRODUCTION..........................................................................................1

RUNNING THE VERIFICATION TOOLS .....................................................2 MyDRC ..............................................................................................................3 LayNet................................................................................................................6 MyLVS..............................................................................................................12

DISPLAYING ERRORS .............................................................................16

THE RULE FILE.........................................................................................18

DESCRIPTION Block ......................................................................................19 LAYER Block....................................................................................................20 OPERATION Block ..........................................................................................21 END Block........................................................................................................22

DESCRIPTION BLOCK .............................................................................23

ABORT-SOFTCHK (MyDRC & LayNet) ..........................................................24 CELL-ERROR-REP (MyDRC & LayNet) .........................................................25 CHECK-MODE (MyDRC & LayNet) ................................................................27 DELCEL (MyDRC & LayNet) ...........................................................................29 DISPLAY-FLAG-ERROR (MyDRC & LayNet)* ................................................30 FILTER-OPT (MyLVS) * ...................................................................................31 FLAG-ACUTEANGLE (MyDRC & LayNet) ......................................................33 FLAG-NON45 (MyDRC & LayNet) ..................................................................34 FLAG-OFFGRID (MyDRC & LayNet) ..............................................................35 FLAG-PTH-OFFGRID (MyDRC & LayNet)......................................................36 FLAG-SELFINTERS (MyDRC & LayNet) ........................................................37 FLAG-SELFTOUCH (MyDRC & LayNet).........................................................38 GROUND (MyDRC & LayNet) .........................................................................39 HCELL (MyDRC & LayNet)..............................................................................40 HCELL-FILE (MyDRC & LayNet).....................................................................41 HCELL-RULE (MyDRC) ..................................................................................42 LAMBDA (MyDRC & LayNet) ..........................................................................43

i


LUMPCAP (LayNet).........................................................................................44 MODE (LayNet) ...............................................................................................46 MODEL (MyDRC & LayNet) ............................................................................48 NETLIST-FORMAT (LayNet) ...........................................................................49 NOT-HCELL (MyDRC).....................................................................................50 POWER (MyDRC & LayNet) ...........................................................................51 SHAPE-FILE (LayNet) .....................................................................................52 WINDEL (MyDRC & LayNet) ...........................................................................53 WINDOW (MyDRC & LayNet) .........................................................................54 WINDOW-CUT (MyDRC & LayNet).................................................................55

LAYER BLOCK..........................................................................................56

ATTACH (MyDRC & LayNet) ...........................................................................57 CELLBNDY (MyDRC & LayNet) ......................................................................59 CONNECT-LAYER (MyDRC & LayNet)...........................................................60 IDTEXT (MyDRC & LayNet) ............................................................................62 SUBSTRATE (MyDRC & LayNet)....................................................................63 TEMPORARY-LAYER (MyDRC & LayNet)......................................................64 TEXT-LAYER (MyDRC & LayNet) ...................................................................65 TEXTSEQUENCE (MyDRC & LayNet)............................................................66

OPERATION BLOCK.................................................................................67

AND (MyDRC & LayNet) .................................................................................68 ANGLE (MyDRC).............................................................................................69 AREA (MyDRC & LayNet) ...............................................................................70 ATTRIBUTE CAP (LayNet) ..............................................................................72 CONNECT (MyDRC & LayNet) .......................................................................73 CORNER(MyDRC & LayNet) ..........................................................................77 ECONNECT (LayNet) ......................................................................................79 EDTEXT (MyDRC & LayNet) ...........................................................................81 ELCOUNT (LayNet) .........................................................................................82 ELEMENT BJT (LayNet)..................................................................................84 ELEMENT BOX (LayNet).................................................................................86 ELEMENT CAP (LayNet).................................................................................87 ELEMENT DIO (LayNet)..................................................................................88 ELEMENT LDD (LayNet) .................................................................................89

ii


ELEMENT MOS (LayNet) ................................................................................90 ELEMENT RES (LayNet).................................................................................94 ENC(MyDRC) ..................................................................................................95 ENCLOSE (MyDRC)......................................................................................100 ERROR (MyDRC & LayNet) ..........................................................................104 EXT(MyDRC) .................................................................................................105 FLATTEN (MyDRC) ....................................................................................... 110 GLOBAL-SCONNECT (MyDRC & LayNet) ................................................... 111 GROW(MyDRC & LayNet) ............................................................................ 112 HEDTEXT (MyDRC & LayNet) ...................................................................... 113 INT(MyDRC) .................................................................................................. 114 LCONNECT (LayNet) .................................................................................... 118 LENGTH (MyDRC) ........................................................................................120 LVSCHK (MyLVS) ** ......................................................................................122 MULTILAB (LayNet).......................................................................................123 NDCOUNT (LayNet) ......................................................................................124 NOT (MyDRC & LayNet)................................................................................126 OCTBIAS(MyDRC & LayNet) ........................................................................127 OR (MyDRC & LayNet)..................................................................................128 OVERLAP (MyDRC) ......................................................................................129 PARAMETER CAP (LayNet)..........................................................................132 PARAMETER RES (LayNet)..........................................................................134 PARASITIC CAP (LayNet) .............................................................................135 PARASITIC DIO (LayNet) ..............................................................................136 PATHCHK (LayNet) .......................................................................................138 PLENGTH (MyDRC)......................................................................................140 PROBE (LayNet)............................................................................................142 RELOCATE(MyDRC & LayNet).....................................................................143 SAMELAB (LayNet) .......................................................................................144 SCONNECT (MyDRC & LayNet)...................................................................145 SELECT (MyDRC & LayNet) .........................................................................147 SHRINK(MyDRC & LayNet) ..........................................................................154 SIZE (MyDRC & LayNet) ...............................................................................155 SOFTCHK (MyDRC & LayNet)......................................................................157 SPACE (MyDRC) ...........................................................................................159

iii


iv

STAMP (MyDRC & LayNet) ...........................................................................164 WIDTH (MyDRC) ...........................................................................................166 XOR (MyDRC & LayNet) ...............................................................................170

LVS...........................................................................................................171

BEFORE USING MYLVS ........................................................................................171 REQUIREMENTS ...................................................................................................171 CONTROL STATEMENTS........................................................................................172

GLOBAL Statement .......................................................................................173 EQUIVALENT Statement ...............................................................................174 DEFAULT .......................................................................................................175 PIN .................................................................................................................176 NOPIN............................................................................................................177 LVS Flow Design............................................................................................178 Initial corresponding node pairs.....................................................................180 LVS Options ...................................................................................................181 Special Values................................................................................................186 Tolerance .......................................................................................................187 The LVS error type.........................................................................................188


Introduction

FOR LAYOUT VERIFICATION, MYCHIP STATION PROVIDES MYDRC FOR DESIGN RULE

CHECKING, LAYNET FOR ELECTRICAL RULE CHECK AS WELL AS NETLIST EXTRACTION,

AND MYLVS FOR NETLIST COMPARISON. TO RUN MYLVS, LAYNET IS A PREREQUISITE

TO GENERATE A SPICE NETLIST FROM THE LAYOUT.

In this reference manual, all the verification commands and associated options are described in detail. Each page looks like the following.

POWER (LayNet)*

The POWER command is used to specify the text for the power nodes contained in the layout database. If a user forgot to properly label a non-unique power text string in the layout database, this command allows the non-unique text string to be converted to a power node.

Syntax

POWER = name1, name2, ..., namen

namen : This data item is used to specify which text is to be converted to a power node.

Examples

POWER = VDD1, VDD2

One star denotes newly added command. Two stars denote there are changes in the command usage.

The command

Description of the command

Syntax of the command {} denotes optional field | denotes ‘or’

Examples

Tools in which the command can be used

1


Running the Verification Tools

Rule files should be prepared before running the verification tools. The file should be prepared for each tool except for MyLVS. You can use any text editor to write the rule file.

The following shows the diagram of the data flow occurring through the verification tools. The tools are depicted in the boxes and the circles denote the data that is prepared by the user. The diamonds denotes the data generated during the run. The gray boxes show the verification(including LayEd, CifGDS) tools.

2


MyDRC

MyDRC is a batch DRC. The DRC reads the layout.1 that is generated when you save the layout in LayEd. With the prepared DRC rule file, MyDRC begins the run by making a list of the jobs required for the working cell , or preprocessing, and makes a temporary directory (Drc) under the working cell directory. After the complete run, MyDRC removes the temporary directory and generates the error file (drc_bin.1) that is required to display DRC errors in LayEd using VerificationLoad Result... The error text file (drc.1*) is generated as well. The edges of the polygons are drawn in thick yellow lines if they violate the DRC rules. The messages being displayed in MyDRC window are kept in the drc.log file. This file is overwritten after each run.

3


To invoke MyDRC from LayEd,

1. Choose VerificationDRC…

2. Select the DRC rule file by typing the file path or by clicking the “Browse” button and locate the file if the DRC rule is not defined (in the rule section) in the technology file. If it is defined, the DRC rule file will be shown in the Rule text input box.

3. The “Run” button will become active when you provide all required information. Click the “Run” button to proceed. If DRC run is successful, you will see a message like above at the end of the message window.

Note: If you don’t save the cell before running DRC, the cell is automatically saved and processed.

4


The steps to invoke the DRC with the command Manager;

1. Choose OptionCommand Manager or press the Spacebar to activate the Command Manager.

2. Type drc in the Command Manager and press Enter. (If you want to specify the rule file, type drc rule_filename)

3. Specify the rule file in the rule text input box.

4. Click on “Run”.

If you want to run the DRC from DOS prompt:

mydrc –p project_name –s cell_name –r rule_file {-ok}

If ok is specified, then the drc run will start without clicking the “Run” button and when the completed, the tool will exit without clicking “Close” button.

The input , output and the options for MyDRC are:

Input

- Project_name: Working project to run DRC. Cell_name: The working cell to run DRC on. - Rule_file: DRC rule file. (It will appear automatically if the rule is given

in the rule section in the technology file, otherwise it should be provided.)

Output

- drc.log : log file which contains the messages generated and displayed in MyDRC window through the run.

- drc_bin.1: A binary file which contains the patterns and locations of the errors. It is required to display DRC errors in LayEd using ToolsLoad Result… and DRC radio button on.

- drc.1: A text file which summarizes the DRC errors.

5


LayNet

LayNet is a SPICE netlist extractor and ERC. LayNet is an intermediate step for LVS and generates a SPICE netlist which will be used in MyLVS. LayNet reads the layout.1 that is generated when you save the layout in LayEd. With the prepared extraction rules, LayNet identifies the devices described in the extraction rule from the layout, if ERC commands are included in the extraction rule, LayNet process ERC. After the complete run, LayNet generates the ERC error file (erc_bin.1) that is required to display ERC errors in LayEd using VerificationLoad Result…. The edges of the polygons are denoted with thick yellow lines if they are considered an ERC violation. If the devices are successfully identified, a SPICE netlist will be generated in extract.1 under the specified cell directory. As an option, you can generate the device (devshape.1) and net shape (netshape.1) to be used to display the devices and nets in LayEd using EditFind…. Also these shape files are required to generate LVS error file (lvs_bin.1) later in MyLVS. The messages being displayed in LayNet window are logged in laynet.log. This file is overwritten on every run.

6


To invoke LayNet from LayEd,

1. Choose VerificationExtract & ERC... or VerificationExtract & ERC with Shape... depending on whether you want to generate shape files (devshape.1 and netshape.1).

2. Specify the extraction rule file by typing the extraction rule file with absolute path or by clicking “Browse” button and locate the file if the

7


extraction rule is not defined (in the rule section) in the technology file. If it is defined, the extraction rule file will be shown in Rule text input box.

3. “Run” button will become active when you provide all required information. Click “Run” button to proceed.

4. Include and Output fields are optional. If you want some file such as model parameters to be included in SPICE netlist, provide the file name at Include text input box. The format of include files are:

Two keywords: %%HEADER, %%END and %% denotes the end of HEADER or END block.

%%HEADER Line1

Line2

%%

%%END

Line3

Line4

%%

Line1 and Line2 will appear next to title line of SPICE netlist and Line3 and Line4 will appear at the end of the SPICE netlist.

8


5. Select the include file by typing the include file name with the absoulte path or by clicking “Browse” button in Include text input box and the output file by typing the output file name with the absoulte path or by clicking “Browse” button in Output text input box if you need to. Specify Output file text input box when you want another SPICE netlist in addition to extract.1 or you want to generate the file in another directory.

Note: If you don’t save the cell before running LayNet, the cell is automatically saved and processed.

9


The steps to invoke the LayNet by command bar are;

1. Choose OptionCommand Manager or press the spacebar to activate the Command Bar.

2. Type ext in the Command Bar and press Enter. (If you want to specify the rule file, type ext rule_filename) Type ext to make Generate net and device shapes check box on automatically.

3. Specify the rule file if not defined in the rule section in the tecnology file.

4. Click on “Run”.

If you want to run LayNet from DOS prompt:

laynet –p project_name –s cell_name –r rule_file {–i include_file –o output_file –shape–model} -ok

If -ok is specified, then the drc LayNet will be started without clicking the “OK” button and when completed the tool will exit without clicking the “Close” button. If -shape is specified, then Generate net and device shapes check box will be on. If -model is specified, then the Passive device model name check box will be on.

Input and output files for LayNet are:

Input

- Project_name: Working project to run LayNet. - Cell_name: The working cell to run LayNet on. - Rule_file : Extraction rule. (It will appear automatically if the rule is given

in the rule section in the technlogy file otherwise it should be provided.) - Include_file (optional) : Specify the file which will be inserted in to the

output file. Usually this file contains a SPICE model parameters so that you don’t have to insert them manually in the SPICE output file.

- Output_file (optional) : Specify the SPICE output file if you want to use a different name. Default output file is extract.1 in the current cell directory.

10


Output

- laynet.log : log file which contains the messages generated through the run.

- devshape.1 : binary file which contains the shape of the device corresponding to the SPICE output file.

- netshape.1 : binary file which contains the shape of the net corresponding to the SPICE output file.

- extract.1 : SPICE output file - erc_bin.1 : the binary file which contains the patterns and locations for

error display.

Option

- Generate net and device shapes : If you click this option, devshape.1 and netshape.1 will be created in the working cell directory. In MyLVS, lvs_bin.1 is generated only if there are devshape.1 and netshape.1. This option is automatically on when you select VerificationExtract & ERC with Shape….

- Passive device model name : If you click this option, the resistor and capacitor will have model names in the output netlist file.

11


MyLVS

ㅡ MyLVS is a SPICE netlist comparator. MyLVS reads in any two SPICE netlists: for example, one from layout which may be obtained from LayNet or any external source, and the other from schematic (extension may be .net, .cir, .spc, .spi). With the options given by the rule file or in the MyLVS option window, the comparison is performed. After the complete run, MyLVS generates the discrepancy file (lvs_bin.1) that is required to display discrepancies in LayEd using VerificationLoad Result… Any discrepancy on the Layout side can be denoted with thick yellow lines. The discrepancy file (lvs_bin.1) is generated only if there is devshape.1 and netshape.1 which can be generated by LayNet. The matched devices and nodes are reported in match.1. The detail discrepancy report being displayed in MyLVS window is logged in the specified file (.dis).

12


To invoke MyLVS from LayEd,

1. Choose VerificationLVS….

Click LVS at the Mode field box if you extracted SPICE netlist from LayNet and did not specify the Output text input box when LayNet was run. (It means that SPICE netlist is extract.1 in the working cell directory.)

2. Select the Rule file by typing the extraction rule file with an absolute path or by clicking the “Browse” button and locating the file if the extraction is not defined (in the rule section) in technology file at Rule and Discrepancy field. If it is defined, the extraction rule will be shown in Rule text input box.

3. Specify the Discrepancy file in Disc. text input box.

4. Specify the Schematic netlsit file and its type in the Scehamtic input text box in Schematic or Schematic2 field.

13


Note: MyLVS supports various format of SPICE netlist such as the Standard SPICE (known as Berkeley SPICE), Pspice, Hspice and CDL (by Cadence).

5. If necessory, click the “Option” button on MyLVS to change options for LVS. The option window will reflect the options specified in the extraction rule file.

“Default” button will reset all options. See LVSCHK command for detailed description on options.

6. “Run” button will become active when you provide all required information. Click the “Run” button to proceed.

14


If you want to run MyLVS from DOS prompt:

mylvs –p project_name –s cell_name –r rule_file {–lvs –sch SPICE_from_schematic |–svs –ext external_SPICE_file} -d discre- pancy_file -ok

If ok is specified, then the lvs run will be started without clicking the “Run” button and when completed, run the tool will exit without clicking “Close” button. If –lvs option is specified, LVS mode will be on and –sch SPICE_from_schematic should be specified. If –svs option is specified, SVS mode will be on and –ext external_SPICE file should be specified.

Input and output files for LVS are:

Input

- Project_file: Working project to run LVS. - Cell_name: The working cell to run LVS on. - Rule_file: Extraction rule file. (It is recommended to put

LVSCHK command in extraction rule and use it for both LayNet and MyLVS.)

- Schematic: Specify the SPICE netlist file obtained from schematic.

- Discrepancy (optional): Specify the report file which contains the comparison result of LVS.

- External: The SPICE netlist from external source to run LVS.

Output

- .dis: The discrepancy file being displayed in the message window during the run.

- match.1 : The matched device and node report file. - lvs_bin.1 : A binary file which contains the shape and the

location of the discrepancy.

15


Displaying Errors

MyDRC andLayNet produces a list of errors and location of errors for the working cell in drc_bin.1 and erc_bin.1, respectively. MyLVS produces a discrepancy file and location of the discrepancy in the layout in lvs_bin.1. With generated error files, the errors can be displayed in the LayEd window. You can also correct the layout while the errors are being displayed. The errors are displayed in yellow lines as the default.

To display the errors in the LayEd window,

1. Choose VerificationLoad Result...

2. The following window will pop up. Click the error type among DRC, ERC or LVS. DRC is chosen as default.

16


3. Type the search pattern for trimming down the error message lists. You can use regular expression. An asterisk(*) is the default.

4. Click the “Load” button to retrieve the list of errors on the specific tool.

5. Click the error you want to display on the LayEd screen from the list of errors. Leave Scroll to error check if you want to automatically locate the error.

To change the colors of errors, there are two ways to do it.

1. Create a new layer called ‘error’ and assign the color for error layer.

Select OptionTechnology Editor…. Type error in the Layer name text input box. Select a stipple in the Stipples list box and the color in the Colormaps list box. Click the “Insert Layer” button at the bottom of Layers list box.

2. Change error color in Technology Editor.

Select OptionTechnology Editor… Select the error color in the set system color menu and change the color by sliding the RGB knobs or color panel.

17


The Rule File

The rule file for each verification tools has the same cell. The rule file is divided into four blocks: DESCRIPTION, LAYER, OPERATION and END. The tool recognizes the start of the block by an asterisk (*) followed by a keyword. In the rule file, the comment is a semicolon (;).

The available commands in DESCRIPTION block are the mode for MyDRC, another mode for LayNet, DELCEL, FLAG-ACUTEANGLE, FLAG-NON45, FLAG-OFFGRID, FLAG-PTH-OFFGRID, LAMBDA, LUMPCAP, MODEL, POWER, GROUND, SHAPE-FILE(SHAPEFILE) and NETLIST-FORMAT(FORMAT).

The commands in LAYER block are SUBSTRATE, CONNECT-LAYER, TEMPORARY-LAYER, TEXT-LAYER, TEXTSEQUENCE and ATTACH.

The commands in OPERATION block are AND, NOT, OR, SELECT, CONNECT, SCONNECT, STAMP, SIZE, CORNER, GROW, RELOCATE, SHRINK, OCTBIAS, ENC(ENCLOSE), EXT(SPACE), WIDTH, INT(OVERLAP), AREA, LENGTH, PLENGTH, ANGLE, ELEMENT MOS, ELEMENT CAP, PARASITCI CAP, ELEMENT DIO, ELEMENT RES, PARASITIC RES, ATTRIBUTE CAP , PARASITIC DIO, ELEMENT BOX, ELEMENT LDD, ECONNECT, ELCOUNT, LCONNECT, NDCOUNT, MULTILAB, SAMELAB, PATHCHK, PROBE and LVSCHK.

The commands, options and layer names are all case insensitive:

ELEMENT mos[p] Pgate POLY psd nwell

is treated as the following in the programs.

ELEMENT MOS[P] PGATE POLY PSD NWELL

18


DESCRIPTION Block

The DESCRIPTION block starts the rule file. This block must be the first block in a rule file. The block specifies the mode of processing, the model name for extraction, power or ground nodes and so forth.

Syntax

*DESCRIPTION

Examples

*DESCRIPTION

MODE=FLATTEN

MODEL = MOS[N], cmosn MOS[P], cmosp

POWER = VDD

19


LAYER Block

The LAYER block defines the mask sequence, if required, and the layer to attach the text.

Syntax

*LAYER

Examples

*LAYER

CONNECT-LAYER = PSUB NWELL PSD NSD POLY METAL

ATTACH MET.TXT TO METAL

20


OPERATION Block

The OPERATION block defines the derived layers, the design rule checking commands or the ERC commands.

Syntax

*OPERATION

Examples

*OPERATION

AND POLY DIFF POLY

CONNECT METAL POLY BY MC1

...

21


END Block

The END block denotes the end of a rule file. The rule file must end with the END Block.

Syntax

*END

Examples

*DESCRIPTION

...

*LAYER

...

*OPERATION

...

*END

22


DESCRIPTION Block

This block describes how to process the rule check, the mode of the capacitance, the model for the extraction, the nodes for the power or the ground and so forth.

LayNet Commands: LUMPCAP, MODE, NETLIST-FORMAT, SHAPE-FILE

MyDRC & LayNet Commands : DELCEL, FLAG-ACUTEANGLE, FLAG-NON45, FLAG-OFFGRID, FLAG-PTH-OFFGRID, GROUND, LAMBDA, MODEL, POWER

23


ABORT-SOFTCHK (MyDRC & LayNet)

The command will abort if any soft connection violations are found in SOFTCHK commands. The default is NO.

Syntax

ABORT-SOFTCHK = [YES|NO]

YES : Aborts the verification program when a soft connection violation occurs.

NO : default

Example

ABORT-SOFTCHK = YES

24


CELL-ERROR-REP (MyDRC & LayNet)

Specifies the format of cell-based error segments generated from MyDRC and LayNet. The default is ONCE.

Syntax

CELL-ERROR-REP = [ONCE|HIER|ALL]

ONCE : The errors associated with HCELLs are reported for only a single instance of that HCELL. All errors associated with HCELLs will be located at the instance of the HCELL closest to 0,0 along X-axis.

HIER : The errors associated with HCELLs are reported at all locations where the HCELL is instantiated.

ALL : Every error encountered will be reported, regardless of the number of times an identical error is repeated. This form of output is similar to flat CHECK-MODE.

The following shows what format of cell-based error segments generated by

FLAT, CELL, HIER, and COMP checks in ONCE, HIRE and ALL options.

Example

*DESCRIPTION

CHECK-MODE = …

CELL-ERROR-REP = …

HCELL = C1

HCELL = C2

*OPERATION

ERROR lay1 OUTPUT ERR 10

ERROR lay2 OTUPUT ERR 20

*END

25


Example * DESCRIPTION CHECK-MODE = HIER CELL-ERROR-REP = ONCE *OPERATION EXT poly LT 0.5 OUTPUT polyerr 12 …

The PRIMARY in result.gds contains two cells: POLYERR12 and INV_CELL as HCELL. Errors within the cell INV are displayed at the first instance.

26


CHECK-MODE (MyDRC & LayNet)

The command specifies the mode in which hierarchical MyDRC and LayNet operates. The default is flat mode.

Syntax

CHECK-MODE = [FLAT|CELL|HIER|COMP]

FLAT : The entire layout is expanded and no hierarchical information is retained. CELL : It is equivalent to a flat check on each of the cells. The cell defined as

HCELLs will be checked. The top cell is not checked. Errors will be reported for each HCELL.

HIER : Generates a complete cell mode check of the layout. The HCELL data is checked one time regardless of the number of placements.

COMP : The layout, which was expanded to the top cell, is checked. All cells which is not defined as HCELLs will be expanded.

Example

CHECK-MODE = HIER

The user may define any cell to be a HCELL, regardless of the hierarchical, or nesting level of the cell. But, it is important to understand that once HCELLs are defined, the original hierarchy of the layout may be changed. For example, suppose the below layout hierarchy. All cell nested within s HCELL will be expanded and brought up to HCELL level (CELL plane). All cell which are not declared HCELLs and which are not nested within a HCELL will be expanded and brought up to the top level (COMPOSITE plane).

27


28


DELCEL (MyDRC & LayNet)

Removes a cell from processing, conserving system resources. You can specify up to 1,024 cells using the DELCEL command.

Syntax

DELCEL = cell-name1 cell-name2 …

cell-name : Name of the cell to remove from processing

Examples

DELCEL = inverter

29


DISPLAY-FLAG-ERROR (MyDRC & LayNet)*

This command flags the reported coordinates by FLAG-ACUTEANGLE, FLAG-NON45, FLAG-OFFGRID, FLAG-PTH-OFFGRID, FLAG-SELFINTERS and FLAG-SELFTOUCH commands as the verification errors.

Syntax

DISPLAY-FLAG-ERROR = [Yes|No]

Yes : Flags acute-angle polygons.

No : default.

Examples

DISPLAY-FLAG-ERROR = YES

30


FILTER-OPT (MyLVS) *

The FILTER-OPT command sets a filtering option for using with MyLVS process. The command internally overrides the LVSCHK command.

Syntax

FILTER-OPT = [Options]

Options : AB, AE, B, BA, C, D, E, F, FY, G, GY, H, H`, I, J, K, L, M, N, P, Q, U, V, S,

T, Z, R

AB: Drain, gate and source tied to together AE: Gate, source, and drain all are floating B: 1. Gate is floating and source or drain is floating 2. Gate has no path to pad through source/drain path including power or ground

and source or drain is floating BA: Gate is connected to pad and source or drain is floating C: Gate is connected to power or ground and source or drain is floating . D: Gate is floating and source and drain have only power path and no paths to

any other pads through source/drain path E: Gate is floating and source and drain have only ground path and no paths to

any other pads through source/drain path F: Gate of MOS[N] tied to ground FY Filters out MOS[N] whose gate tied to ground and reconnects source and

drain of the filtered device. G: Gate of MOS[P] tied to power GY: Filters out MOS[P] whose gate tied to power and reconnects source and

drain of the filtered device H: Drain and source tied to power . H’: Not supported I: Drain and source tied to ground J: Gate tied to power or ground and source and drain tied to together. K: Drain and source have no path to any pad including power or ground through

source/drain path L: Source or drain is floating M: Filters out MOS[P] whose gate tied to ground and reconnects source and

drain of the filtered device N: Filters out MOS[N] whose gate tied to power and reconnects source and drain

of the filtered device

31


P: Drain, gate and source have no path to any pad including power or ground

through general path Q: Drain, gate and source have no path to any pad except power and ground

through general path U: Source and drain are floating V: Gate is floating and source or drain is floating and non-floating terminal tied to

power or ground S: At least two terminals of BJT are floating T: Emitter and collector tied to together and do not connect to other devices Z: 1 Base, Emitter and collector are floating

2. Anode and cathode of diode and cathode are floating 3. Two terminals of resistor are floating

R: At least one terminal of diode, capacitor and diode is floating

Example 1

*DESCRIPTION

FILTER-OPT = AB

*END You can use two filtering options (FILTER-OPT and LVSCHK[F]).

Example 2

*DESCRIPTION

FILTER-OPT = AB

*OPERATION LVSCHK[F]

*END

32


FLAG-ACUTEANGLE (MyDRC & LayNet)

Reports the coordinates of acute-angle polygons. FLAG-ACUTEANGLE reports polygons in the drc.sum or laynet.sum file. This command processes the polygons and reports the x, y coordinates of the polygon vertices, the layer name, and the associated cell name. It checks the polygon in each cell before merging the layout data.

Syntax

FLAG-ACUTEANGLE = [Yes|No]

Yes : Flags acute-angle polygons.

No : default.

Examples

FLAG-ACUTEANGLE = Yes

33


FLAG-NON45 (MyDRC & LayNet)

Reports the coordinates of non45-angle polygons. FLAG-NON45 reports polygons in the drc.sum or laynet.sum file. This command processes the polygons and reports the x, y coordinates of the polygon vertices, the layer name, and the associated cell name. It checks the polygon in each cell before merging the layout data.

Syntax

FLAG-NON45 = [Yes|No]

Yes : Flags non-45 degree angle polygons.

No : default.

Examples

FLAG-NON45 = Yes

34


FLAG-OFFGRID (MyDRC & LayNet)

Reports the coordinates of cell placements and polygons that have vertices off the grid. FLAG-OFFGRID reports cell placements and polygons whose vertices are off the grid and off-grid cell placements in the drc.sum or laynet.sum file. This command processes the polygons and reports the x, y coordinates of the polygon vertices, the layer name, and the associated cell name. It checks the polygon in each cell before merging the layout data.

Syntax

FLAG-OFFGRID = [Yes|No] {grid-value}

Yes : Flags all cell placements and polygons that are off grid.

No : default.

Grid-value : Specifies the grid. Value must be a real number greater than 0.0 but less than 1.0

Examples

FLAG-OFFGRID = Yes 0.05

35


FLAG-PTH-OFFGRID (MyDRC & LayNet)

Reports the coordinates of paths that have vertices off the grid. FLAG-OFFGRID reports cell placements and polygons whose vertices are off the grid and off-grid cell placements in the drc.sum or laynet.sum file. This command processes the polygons and reports the x, y coordinates of the polygon vertices, the layer name, and the associated cell name. It checks the polygon in each cell before merging the layout data.

Syntax

FLAG-PTH-OFFGRID = [Yes|No]

Yes : Flags all paths that are off grid.

No : default.

Examples

FLAG-PTH-OFFGRID = Yes

36


FLAG-SELFINTERS (MyDRC & LayNet)

Reports the coordinates of polygons that have self-intersecting vertices. FLAG-SELFINTERS reports polygons whose vertices are self-intersecting in the drc.sum or laynet.sum file. This command processes the polygons and reports the x, y coordinates of the polygon vertices, the layer name, and the associated cell name. It checks the polygon in each cell before merging the layout data. If you specify FLAG-SELFINTERS = YES FULL, MyDRC and/or LayNet flags polygons that are reentrant as illegal.

Syntax

FLAG-SELFINTERS = [YES|NO] {FULL}

YES : Flags self-intersecting polygons.

NO : default

FULL : Flags reentrant polygons as illegal.

Example

FLAG-SELFINTERS = YES

37


FLAG-SELFTOUCH (MyDRC & LayNet)

Reports the coordinates of polygons that have touching vertices. FLAG-SELFINTERS reports polygons whose vertices are touching in the drc.sum or laynet.sum file. This command processes the polygons and reports the x, y coordinates of the polygon vertices, the layer name, and the associated cell name. It checks the polygon in each cell before merging the layout data.

Syntax

FLAG-SELFTOUCH = [YES|NO]

YES : Flags self-touching polygons.

NO : default

Example

FLAG-SELFTOUCH = YES

38


GROUND (MyDRC & LayNet)

The GROUND command is used to specify the text for the ground nodes contained in the layout database. If a user forgot to properly label a non-unique ground text string in the layout database, this command allows the non-unique text string to be converted to a ground node.

Syntax

GROUND = name1, name2, ..., namen

namen : This data item is used to specify which text is to be converted to a ground node.

Examples

GROUND = VSS1, VSS2

These text strings (as they actually appear in the layout database) will be converted to a ground node and MyDRC/LayNet will treat these nodes as a ground.

39


HCELL (MyDRC & LayNet)

The commands specifies layout cells to be used as HCELLs. User may define any cell to be an HCELL.

Syntax

HCELL = cell_name {logic_name}

cell_name : The layout cell name that is used as a HCELL. logic_name : The name of the logic circuit in the schematic that represents the sub

circuit description.

Example

HCELL = inv

MyDRC uses HCELL commands with its automatic selection algorithm to determine which layout cell to use as HCELLs. LayNet use the HCELL command as the only way to determine which HCELLs to use. User can use multiple HCELL commands and also specify a number of HCELL specifications using the HCELL-FILE command. MyDRC automatically defines a cell to be a HCELL if it meets these requirements.

- The cell must be placed at least twice in the top cell. - The cell must consist of a minimum number of edges. The minimum number is

determined with the formula: Minimum number = 4 * I where I is equal to the total edge number of the checked layers in the rule file. A HCELL may not be placed within another HCELL.

40


HCELL-FILE (MyDRC & LayNet)

Specifies a file containing a set of HCELL command statements. The format of each statement is the same as that of the HCELL command except that the keyword HCELL is left out of each line.

Syntax

HCELL-FILE = filename

filename : The name of the file containing the HCELL commands.

Example

HCELL-FILE = hcell.tab

Contents of hcell.tab Inv Nand

41


HCELL-RULE (MyDRC)

The command is used to modify the default requirements for automatic HCELL selection. The user may change two of the default requirements for HCELL definition using this command.

Syntax

HCELL-RULE = num_place1,num_edge1, num_place2, num_edge2 … num_placen, num_edgen

num_place : the minimum number of cell placements required for a cell to be a HCELL candidate. Default is 2.

num_edge : the minimum polygon edge count required for a cell to be a HCELL candidate. Default is four times the number of the edges.

Example

HCELL-RULE = 5,300

num_place and num_edge act as requirement pairs. When multiple requirement pairs are specified, cell meeting any of the requirement pairs qualify as HCELL candidates.

42


LAMBDA (MyDRC & LayNet)

The value of lambda is a floating number. When LAMBDA is used in the DESCRIPTION block, all the value of the checking commands and sizing commands are treated as lambda instead of micron meter. The numbers used in CORNER, GROW, RELOCATE, SHRINK, SIZE, ENCLOSE, SPACE, WIDTH, OVERLAP, AREA, LENGTH, ENC, EXT, INT, PLENGTH are treated as lambda.

Syntax

LAMBDA=n

N is a positive floating number and its unit is in micron meters.

LAMBDA must be declared in the description block.

43


LUMPCAP (LayNet)

There are two ways to report parasitic capacitance; lumped or coupled. The LUMPCAP command allows the LayNet to report the parasitic capacitance in lumped or coupled mode.

Syntax

LUMPCAP = [Yes|No]

Yes : Turns on lumped mode capacitance.

No : Turns off lumped mode capacitance and uses the regular flow. Default.

Lumped capacitance means that all parasitic capacitances that are associated with a particular node will be added together to form the total capacitance value of that node.

Examples

Node 1 capacitance CN1 = C12 + C13




They are reported in the output netlist as:

44


C1 1 0 C N1

C2 2 0 C N2

C3 3 0 C N3

C4 4 0 C N4

Coupled capacitance would be chosen if the designer wanted all the parasitic capacitance to be reported individually, rather than lumped.

Example:

The capacitance between node 1 and 2 in coupled mode would be listed as:

C1 1 2 CTOTAL

where CTOTAL = C11 + C12

45


MODE (LayNet)

There are two ways to report parasitic capacitance; lumped or coupled. The MODE command allows the LayNet to report the parasitic capacitance in lumped or coupled mode.

Syntax

MODE mode

Refer LUMPCAP command.

Lumped capacitance means that all parasitic capacitances that are associated with a particular node will be added together to form the total capacitance value of that node.

Examples





46


They are reported in the output netlist as:

C1 1 0 C N1

C2 2 0 C N2

C3 3 0 C N3

C4 4 0 C N4

Coupled capacitance would be chosen if the designer wanted all the parasitic capacitance to be reported individually, rather than lumped.

Example:

The capacitance between node 1 and 2 in coupled mode would be listed as:

C1 1 2 CTOTAL

Where CTOTAL = C11 + C12

47


MODEL (MyDRC & LayNet)

The MODEL command is used to associate the circuit element MOS and diode, LDD, BJT, CAP, RES with the corresponding circuit simulation model name. These model names will appear in the SPICE formatted listing generated by LayNet. This command must be specified in order to execute LayNet.

Syntax

MODEL = (Layout element, Circuit simulation model)*

Layout element: This item can either be a MOS transistor, a diode with a model type. Circuit simulation model : This item will be the model name of the layout when it is extracted to the SPICE netlist. ( )* denotes that there can be more than one pair of the fields inside the parenthesis.

Examples

MODEL = MOS[N], CMOSN MOS[P], CMOSP

The example above shows that the designer associates the n-type MOS[N] transistor (p-type MOS[P]) with the CMOSN (CMOSP) circuit simulation name.

48


NETLIST-FORMAT (LayNet)

The format specifies the extracted passive element of SPICE netlist.

Syntax

NETLIST-FORMAT = [SPICE | HSPICE]

Example

In SPICE format, the capacitor and the resistor with model name extracted as

Cxx anode cathode value

Rxx node1 node2 value

In HSPICE format, the capacitor and the resistor with model name extracted as

Cxx anode cathode value $ [model]

Rxx node1 node2 value $ [model]

49


NOT-HCELL (MyDRC)

The command specifies the layout cell that are not to be selected as HCELLs.

Syntax

NOT-HCELL = cell_name1 cell_name2, … cell_namen

cell_name: layout cell name not to be considered a HCELL candidate,

Example

NOT-HCELL = cnt_cell

50


POWER (MyDRC & LayNet)

The POWER command is used to specify the text for the power nodes contained in the layout database. If a user forgot to properly label a non-unique power text string in the layout database, this command allows the non-unique text string to be converted to a power node.

Syntax

POWER = name1, name2, ..., namen

namen : This data item is used to specify which text is to be converted to a power node.

Examples

POWER = VDD1, VDD2

These text strings (as they actually appear in the layout database) will be converted to a power node and MyDRC/LayNet will treat these nodes as a power supply.

51


SHAPE-FILE (LayNet)

The SHAPE-FILE command will control whether to generate netshape.1 and devshape.1 files. These files are required to display the devices and nets in LayEd using “EditFind…”. Also, these shape files are required to generate LVS error files (lvs_bin.1) later in MyLVS. However, the extraction time (processing time for LayNet) is greatly reduced it these shape files are not generated.

Syntax

SHAPE-FILE [YES|NO]

52


WINDEL (MyDRC & LayNet)

Deletes an area within a window from processing. Multiple window areas (maximum number of 50) can be specified. This commands keeps data that lies outside or across WINDEL coordinate lines according to WINDOW-CUT mode. When checking using CHECK-MODE=FLAT or HIER, the command keeps data that lies across WINDEL coordinate lines unless a user specifies WINDOW-CUT=EDGE in rule file. When checking using CHECK-MODE=CELL or COMP, the layout which lies across WINDOW coordinate lines is cut unless a user specifies WINDOW-CUT=TRAPEZOID in rule file. The WINDOW command works on the polygon data not instances or text.

Syntax

WINDEL = xmin ymin xmax ymax

xmin : the minimum x coordinate of window to delete from processig ymin : the minimum y coordinate of window to delete from processig xmax : the maximum x coordinate of window to delete from processig ymax : the maximum y coordinate of window to delete from processig

Examples

*DESCRIPTION

WINDEL = 0.0 0.0 10.0 10.0

WINDEL = 0.0 10.0 10.0 20.0

…

53


WINDOW (MyDRC & LayNet)

This command specifies a window to process. Multiple window areas (maximum number of 50) can be specified. This commands keeps data that lies inside or across WINDEL coordinate lines according to WINDOW-CUT mode. When checking using CHECK-MODE=FLAT or HIER, the command keeps data that lies across WINDOW coordinate lines unless a user specifies WINDOW-CUT=EDGE in rule file. When checking using CHECK-MODE=CELL or COMP, the layout which lies across WINDOW coordinate lines is cut unless a user specifies WINDOW-CUT=TRAPEZOID in rule file. The WINDOW command works on the polygon data not instances or text.

Syntax

WINDOW = xmin ymin xmax ymax

xmin : the minimum x coordinate of window to process ymin : the minimum y coordinate of window to process xmax : the maximum x coordinate of window to process ymax : the maximum y coordinate of window to process

Examples

*DESCRIPTION WINDOW = 0.0 0.0 10.0 10.0 WINDOW = 0.0 10.0 10.0 20.0 …

54


WINDOW-CUT (MyDRC & LayNet)

The WINDOW-CUT command will control whether to keep or cut the portion of a polygon that lies across the coordinate lines specified in a WINDOW or WINDEL command.

Syntax

WINDOW-CUT = [TRAPEZOID|EDGE]

TRAPEZOID : Keeps the polygon if it lies across the window boundary. This is default for FLAT and HIER checking mode.

EDGE : Cuts the polygon along the window edge and keeps the portion outside if a user specified WINDEL command or inside the window if WINDOW command. This is default for CELL and COMP checking mode.

55


LAYER Block

This block describes the commands which define the mask order and attach the text to nodes. ATTACH command which attaches the text to one specific layer for the label. CONNECT-LAYER command which specifies the mask order determined by the IC process.

Note: In this version, the LAYER block is now used for both MyDRC and LayNet.

56


ATTACH (MyDRC & LayNet)

The ATTACH command is used to attach the text to the object at one specific layer. In order for MyDRC and LayNet to run successfully, it is required that some electrical nodes be labeled in the layout database. If a unique text, which represents part of the layout data for an electrical node, is attached to the geometry, it becomes the label of this node. These text strings are required in order to identify specific circuit components such as the power supply, ground, etc. The text strings are also used to identify nodes of interest, virtual connections, and to assist in the definition of the various circuit elements. Specifically, the text string in ATTACH command is used by MyDRC and LayNet for the following purposes:

1. To specify the power supply node and the ground node for LayNet. If power is specified as VDD, VCC, PWR, or POWER, LayNet will automatically recognize these text strings as power. The text strings VSS, VGG, GND, GROUND will be recognized as ground.

2. To specify a virtual connection or wire between individual pieces of geometry. For example, two separate VCC nodes could be handled as if they were part of the same node. This capability enables a partial layout (i.e., a cell or a layout excluding memory arrays) to be properly checked.

3. To specify the nodes that may be probed by the PROBE command, only nodes that are labeled “TEXT” are able to be probed.

A text can only be attached to the object in one specific layer. If there are no objects this layer could be attached to, the text will be discarded. A text is attached to an object if and only if the text point (x, y location) is inside, at the edge, or on the vertex of the object.

Syntax

ATTACH text_layer TO layer

57


text_layer : This data item is the layer name of in which the text is to be attached. layer : This data item is the layer name of the object to which the text is attached to.

Examples

ATTACH MET.TXT TO METAL

The example above shows that the text strings of the MET.TXT layer is attached to the object in the METAL layer.

Important: ATTACH command must be defined after CONNECT-LAYER is defined.

Note: ATTACH command now allows the text layer to attach to the derived layer.

In your layout, if you drew two polygons labeled VDD1:P, VDD2:P, respectively, then VDD1 and VDD2 will be considered connected even though they are not physically connected. Any node name with :P are all considered connected each other and considered as power nodes. Same applies to :G for ground nodes. If you want any two polygons not connected to each other but to be considered virtually connected (virtual wiring), you should use same label with the same type. (ie. IN1:I)

58


CELLBNDY (MyDRC & LayNet)

The command is used to build a cell boundary. If the command is not specified, the bounding box surrounds the minimum and maximum geometries of a HCELL and is always a rectangle. The command allows a rectilinear cellbox. The SUBSTRATE and CELLBNDY commands affect the formation of the substrate layer.

Syntax

CELLBNDY = lname

lname : layer name

Example

CELLBNDY = cbound

The CELLBNDY command is useful if you have non-rectangular cells. Using the default bounding box for HCELLs, the pin texts may be discarded and lost pins.

59


CONNECT-LAYER (MyDRC & LayNet)

The CONNECT-LAYER command is used to define the mask order, which is specified in the sequence according to the IC process steps. This command is required if a CONNECT command is used in the OPERATION block. Only the layers that appear in the CONNECT command (excluding the layers for making the connection between two conductor layers and the actual contact layers) must be specified in the CONNECT-LAYER command. Layer names may be included on single CONNECT-LAYER line or specified in multiple CONNECT-LAYER lines.

Syntax

CONNECT-LAYER = layer1 layer2 ... layern

layer: This data item is the layer name that appears in the CONNECT operation (excluding the contact layer) in the OPERATION block and is the conductor layer for the process.

Examples

*LAYER

CONNECT-LAYER = SRCDRN POLY METAL

...

*OPERATION

CONNECT METAL POLY BY CONT

CONNECT METAL SRCDRN BY CONT

CONNECT POLY SRCDRN BY EPI

...

*END

60


The mask order of CONNECT-LAYER command is very important for MyDRC and LayNet. All conductor layers are defined in the CONNECT-LAYER command. The contact layer can only have one master layer. Therefore, the contact layer can only connect from the master layer to any other layers but cannot connect from another contact layer. The master layer is the layer connected to the contact layer and appears later than the contact layer in the CONNECT-LAYER command.

61


IDTEXT (MyDRC & LayNet)

This command will be used for you to add label (text) to layers for identification purposes. These layers are independent of connectivity. User can select polygons by idtext names from a specific idtext layer.

The IDTEXT command is useful only with SELECT LABEL {[T] | [T’]} command.

Syntax

IDTEXT = layer text-layer

layer : The IDTEXT layer name in the rule file.

text-layer : The layer name from which label is extracted for layer

Examples

*LAYER

IDTEXT = poly idtxt

…

*OPERATION

SELECT metal BY idtxt LABEL [T] RES1 RES2 RES3 idres

…

IDTEXT layer, idtxt, extract labels from poly layer. And SELECT command will create the new layer, idres, which has the RES1, RES2, and RES3 labels.

62


SUBSTRATE (MyDRC & LayNet)

The SUBSTRATE command is used to generate the substrate layer if is not drawn in the layout. The substrate layer is a rectangle area oversized by 1 micron than the rectangle which encloses all of the layout data.

Syntax

SUBSTRATE = layer_name

layer_name : This data item is used to assign a name to the generated rectangle. The layer-name can only have up to seven characters and no special characters are allowed. The first character must be alpha.

Examples

SUBSTRATE = BULK

The example above shows that the program has generated a substrate layout data called BULK.

63


TEMPORARY-LAYER (MyDRC & LayNet)

Some DRC and LayNet commands such as Logical Operation Commands and Geometric Shape Checking Commands generate derived layers as their operation results. The TEMPORARY-LAYER command specifies temporary layers for such generated derived layers.

The TEMPORARY-LAYER command is useful for generating a derived layer which is used only for temporary purpose to get the succeding final layer.

Syntax

TEMPORARY-LAYER=LAYER_NAME1 LAYER_NAME2 …

layer_name : This layer is the temporary layer to keep the data for further processing.

Examples

* DESCRIPTION

…

TEMPORARY-LAYER = TEMP

…

* OPERATION

…

AND TEMP ABC TEMP

…

Note: If “AND TEMP ABC TEMP” is used without defining TEMP in TEMPORARY-LAYER, MyDRC & LayNet will flag error and stop the run immediately.

64


TEXT-LAYER (MyDRC & LayNet)

This command will be used for label (text). You can still attach text to any layer not specified in TEXT-LAYER command, by using ATTACH xx to me1.

The difference is that if you use ATTACH xx to metal1 and xx is not specified in the TEXT-LAYER command, xx will be attached to only metal1 and cannot be used to attach to some other layer, say, metal2.

Syntax

TEXT-LAYER = layer1 layer2 … layern

Example

TEXT-LAYER = me1txt me2txt

CONNECT-LAYER = poly metal1 metal2

ATTACH me2txt to metal2

The me2txt layer is used to attach to metal2 only. Even if the labels in me2txt layer are inside of metal1 or poly objects, they are ignored.

The labels (texts) in me1txt are attached to the layers in the reverse order of CONNECT-LAYER which is metal2, metal1 and poly. Suppose, the labels in me1txt are on the overlapping region among metal2, metal1 and poly, the labels are treated being attached to metal2 first, and if no metal2, then metal1 and poly in that order.

65


TEXTSEQUENCE (MyDRC & LayNet)

This command modifies the priority of the layer to be attached. As a default when TEXTSEQUENCE is not used, the label (text) is attached in the reverse order of the layer list in CONNECT-LAYER.

In this case you want to change the order, TEXTSEQUENCE can be used

Important: TEXTSEQUENCE command must be defined after CONNECT-LAYER is defined. TEXTSEQUENCE command should always accompany TEXT-LAYER definition.

Syntax

TEXTSEQUENCE = layer1 layer2 … layern

Example

TEXT-LAYER = me1txt me2txt

CONNECT-LAYER = poly metal1 metal2

ATTACH me2txt TO metal2

TEXTSEQUENCE = metal1 metal2

Me2txt is attached only to metal2.

If the labels in me1txt are on the overlapping region of metal2, metal1 and poly, the lables are attached to metal1 and if there is no metal1, then it is attached to metal2. The labels which is not attached to metal1 or metal2 is discared.

66


OPERATION Block

This block describes the commands which define the various functions. The OPERATION block is broken down into the following six categories of commands;

1. Logical Operation Commands: AND, NOT, OR, SELECT, XOR

2. Electrical Node Extraction Commands: CONNECT, SCONNECT, STAMP

3. Resizing Operation Commands: CORNER, GROW, OCTBIAS, RELOCATE, SHRINK, SIZE

4. Geometrical Checking Commands: ANGLE, AREA, ENC(ENCLOSE), ERROR, EXT(SPACE), INT(OVERLAP), LENGTH, PLENGTH, WIDTH, WLENGTH

5. Circuit Element Extraction Commands: ATTRIBUTE, ELEMENT, PARACITIC, PARAMETER

6. Electrical Rule Checking Commands: ECONNECT, ELCOUNT, LCONNECT, MULTILAB, NDCOUNT, PATHCHK, PROBE , SAMELAB

7. LVS Checking Commands: LVSCHK

67


AND (MyDRC & LayNet)

The AND command is a logical operation which can be used to create a new layer from two other layers. The new layer consists of the region shared by the two defined layers and excludes the portions of the layers which are not in common. The order of the two input layers is irrelevant, but affects the electrical node information.

Syntax

AND layer1 layer2 output_layer {OUTPUT cell_name layer-number {data_type_number}}

layer1: The first input layer name. layer2: The second input layer name. output_layer: This data item is the layer which is created by the logical operation. The electrical node information is automatically stamped on this generated layer from the first layer name only after nodal information is set up by using the CONNECT command on the involved layer1. cell_name: The cell name to be outputted in the GDS file. layer-number: The number can be 0 ~ 255. data_type_number: The number can be 0 ~ 255. Default is 0. If you used OUTPUT, the GDS file will be created and the name of GDS file is result.gds. The resultant geometries are written with cell name as cell_name + layer-number.

Examples

AND layer1 layer2 result_layer OUTPUT out_layer 3 0

The GDS file result.gds with cell name out_layer3.

68


ANGLE (MyDRC)

It checks if the polygon has specified angled edges.

Syntax

ANGLE layer Angles {output_layer} {"message"} {OUTPUT cell-name layer-number {data-type-number}}

layer : The input layer name.

Angles:

ALL: Any two edges forming the angle will be flagged. 90: Any two edges that form the angle of multiples of 90 degrees will be flagged. NON-90: Any two edges that form angle other than multiples of 90 degrees will be flagged. 45: Any two edges that form the angle of multiples of 45 degrees will be flagged. NON-45: Any two edges that form angle other than multiples of 45 degrees will be flagged. ACUTE: Any two edges that form acute angle will be flagged. NON-ACUTE: Any two edges that do not form acute angle will be flagged.

message: The message to be displayed will be enclosed in double quotation marks.

output_layer : Specifies the layer name when we perform ANGLE command. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255.

If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds. This example shifts the data in the metal layer by a negative 5 units in the x direction. Ouput the data to the met5 layer. Does not magnify.

69


AREA (MyDRC & LayNet)

The AREA command makes dimensional checks that are used to perform area check

Syntax

AREA layer Range {output-layer} {“message”} {OUTPUT cell-name layer-number {data-type-number}}

Layer : The input layer name. Range :

EQ n: Flags the polygons of the layer whose areas are equal to n microns. LT n: Flags the polygons of the layer whose areas are less than n microns. LE n: Flags the polygons of the layer whose areas are less than or equal to n microns. GT n: Flags the polygons of the layer whose areas are greater than n microns. GE n: Flags the polygons of the layer whose areas are greater than or equal to n microns. NE n: Flags the polygons of the layer whose areas are not equal to n microns RANGE n1 n2: Flag the polygons of the layer whose areas are greater than n1 microns and less than n2 microns.

output_layer: This data item is the layer which is created by the command. message: Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds. This example shifts the data in the metal layer by a negative 5 units in the x direction. Ouput the data to the met5 layer. Does not magnify.

70


Examples

AREA CONTACT LT 4.0 "AREA(CONTACT) < 4.0"

AREA contact LT 4.0 scontact

71


ATTRIBUTE CAP (LayNet)

The ATTRIBUTE CAP command is used to associate the geometry data of a PARASITIC CAP with the corresponding process-dependent electrical properties. An ATTRIBUTE CAP command must follow the PARASITIC CAP command.

Syntax

ATTRIBUTE CAP{[type]} value1 value2

type: The type code is specified in the PARASITIC CAP[type] device. value1: The capacitance per unit area between layer1 and layer2. The unit of value1 is pF/um2. value2: The capacitance per unit perimeter between layer1 and layer2. The unit of value2 is pF/um.

Examples

CONNECT-LAYER = POLY1 POLY2 METAL

AND POLY1 POLY2 POLYCAP

CONNECT METAL POLY1 BY CONT


PARASITIC CAP[P] POLYCAP POLY1 POLY2

ATTRIBUTE CAP[P] 0.04 0.0

72


CONNECT (MyDRC & LayNet)

The CONNECT command is an operation used to define the interlayer connectivity. The basic function is to connect two layers by a specified set of contacts. Each and every layer used in the CONNECT-LAYER commands must have a corresponding CONNECT command to tell MyDRC/LayNet all the possible types of connection to other conductor layers.

Syntax

CONNECT layer1 layer2 BY contact_layer

layer1: The first input layer name. layer2: The second input layer name. contact_layer: This is a layer which has been previously defined and consists of the contacts which will connect layer1 to layer2. The contact_layer can only have one master layer (common) and can connect from the master layer to any other layers.

Note: The same contact_layer may not be used to connect a subsequent layer to another new layer. If you use the SELECT LABEL command, you may need to specify the connection with the CONNECT command.

Every contact layer used in the CONNECT commands will be assigned a master layer by the CONNECT-LAYER commands. All layers connected by a particular contact will be examined and the highest priority layer according to the CONNECT-LAYER commands will become the master layer for that contact. All CONNECT-LAYER commands that specify this contact must also include its master layer as one of the conductor fields.

73


Examples

*LAYER

CONNECT-LAYER = DIFFUS POLY METAL

...

*OPERATION


CONNECT METAL DIFFUS BY CONT

CONNECT POLY DIFFUS BY BC

...

*END

74


CONNECT-LAYER = PSUB NWELL PSD NSD POLY MET1 MET2

CONNECT MET2 MET1 BY VIA

CONNECT MET1 POLY BY CONT

CONNECT MET1 NSD BY CONT

CONNECT MET1 PSD BY CONT

CONNECT NWELL NSD BY CONT (Not allowed)

CONNECT PSUB PSD BY CONT (Not allowed)

In the CONNECT commands, MET2 is the master layer for the VIA, and MET1 is the master layer for the CONT. However, the example above is attempting to connect two conductor layers, NWELL and NSD or PSUB and PSD, with the CONT without including the master layer of the CONT. In this situation, the designer must create a pseudo contact in order to connect the two conductor layers.

75


CONNECT-LAYER = PSUB NWELL PSD NSD POLY MET1 MET2

AND PSUB PSD PCONT

AND NWELL NSD NCONT

CONNECT MET2 MET1 BY VIA

CONNECT MET1 POLY BY CONT

CONNECT MET1 NSD BY CONT

CONNECT MET1 PSD BY CONT

CONNECT NWELL NSD BY NCONT (Allowed)

CONNECT PSUB PSD BY PCONT (Allowed)

When establishing connectivity of the substrate or wells, it is recommended that you create a pseudo contact by ANDing the substrate with the substrate-tap and the well with the well-tap.

76


CORNER(MyDRC & LayNet)

Recognizes polygon corners and reports them to the specified output layer for special DRC checking.

Syntax

CORNER {[option]} layer {Relation1} {Relation2} {CORNER-SIZE n} output_layer {OUTPUT cell_name layer-number {data_type_num}}

option : If you do not specify any options, this command works for Manhattan angles.

A : Reports 90 degree angles. Default. B : Reports 45 degree angles. C: Reports any angle.

layer : Input layer name.

Relation1 : INSIDE : creates a rectangle the size of sCORNER-SIZE on the inside of shapes. OUTSIDE : creates a rectangle the size of CORNER-SIZE at all corners on the outside of shapes.

Relation2: INNER : creates a rectangle the size of CORNER-SIZE on the inside edge of all corners. OUTER : creates a rectangle the size of CORNER-SIZE on the outside edge of all shapes.

CORNER-SIZE n : Corner size in user units (n). If you do not specify this option, the default value is 2 times the resolution unit.

output_layer : Output layer name. cell_name: The cell name to be outputted in the GDS file. layer-number: The number can be 0 ~ 255.

77


data_type_number: The number can be 0 ~ 255. Default is 0. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds. This example shifts the data in the metal layer by a negative 5 units in the x direction. Ouput the data to the met5 layer. Does not magnify.

Examples

78


ECONNECT (LayNet)

The ECONNECT command checks the elements to determine if they are connected (or disconnected) from a labeled node through a specified layer.

Syntax

ECONNECT element{[type]} terminal Condition label OUTPUT message {&} or

ECONNECT element{[type]} terminal Condition label {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}

element: The type of element being checked; this element must be defined by an ELEMENT command. type: A two character code used to denote the type of device that is checked. The first character must be from A to Z and second character may be from A to Z or from 0 to 9 but is optional. term: The terminal layer through which the connections are being checked. A term name of "ALL" may be used to indicate that all of the conductor layers defined in the ELEMENT command for the "element" and "type" are to be checked.

Condition

CONN: CONN indicates that a connection to the labeled node is considered a violation. DISC: DISC indicates that a disconnection from the labeled node is considered a violation. label: This is the text label of the node to be checked. It must be labeled as text in the layout database conforming to the text rules. message: The message to be reported. &: This indicates that this operation is part of a conjunctive rule. The conjunctive rule option is placed at the end of the command line. It can be conjoined to the other ECONNECT and NDCOUNT commands.

message: Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255.

79


Examples


ECONNECT MOS[P] POLY CONN VDD OUTPUT ERC01

The check above will flag all P-type MOS with the POLY terminal connected to VDD.

This command can be conjoined with itself and/or NDCOUNT. Again, a conjunctive rule is one which requires more than one command to achieve the desired results. The following check will flag all MOS[N] with the source and drain connected directly across the power supplies.

ELEMENT MOS[N] NGATE POLY NSD PWELL

ECONNECT MOS[N] NSD CONN VDD &

ECONNECT MOS[N] NSD CONN VSS OUTPUT ERC01

80


EDTEXT (MyDRC & LayNet)

The command specifies to use text from a text coordinate file in addition to text in the layout database. The text coordinate file is an external ASCII file.

Syntax

EDTEXT = file_name

file_name : text coordinate file name

Example

EDTEXT = TEXT.TXT

Each line specifies one text label, its x, y coordinates, and, optionally, its attached layer name. The text coordinate file can contain comment starter(:) in the first column of a line. The program ignores all text after the comment starter. The following is a syntax of EDTEXT file.

Syntax text X=x_coordinate Y=y_coordinate {ATTACH=layer_name}

text : The text string that will be attached. x_coordinate, y_coordinate : X, Y coordinate on layout where text will be attached. layer_name : The layer within the layout the text will attach to.

The following is an example of a text coordinate file.

Example VSS x=0.5 Y=0.5 ATTACH=METAL1 VDD x=0.5 Y=100 ATTACH=METAL1 IN x=10 Y=25

OUT x=100 Y=25

81


ELCOUNT (LayNet)

The ELCOUNT command counts, for an individual node, the total number of elements connected through specified layers. The nodes with element counts equal to the condition are reported as errors.

Syntax

ELCOUNT element{[type]} term Condition OUTPUT message {&} or

ELCOUNT element{[type]} term Condition {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}


Condition

LT n: An element count less than the number n. LE n: An element count less than or equal to the number n. EQ n: An element count equal to the number n. NE n: An element count not equal to the number n. GT n: An element count greater than the number n. GE n: An element count greater than or equal to the number n. message: The message to be reported. &: This indicates that this operation is part of a conjunctive rule. This conjunctive rule option is placed at the end of the command line. It can be conjoined to the other ELCOUNT and PROBE commands.


82


Examples


ELCOUNT MOS[P] ALL EQ 1 OUTPUT ERC01

The check above will flag all the nodes that have only one P-type MOS element attached. The areas of errors will contain all the conducting area defined by NODE A and B.

This command can be conjoined with itself and/or PROBE. Again, a conjunctive rule is one which requires more than one command to achieve the desired results. The following check will flag the VDD node to which only one PMOS element is attached.


ELCOUNT MOS[P] ALL EQ 1 &

PROBE VDD OUTPUT ERC01

83


ELEMENT BJT (LayNet)

The ELEMENT BJT command is a circuit element definition command, used to define BJT devices in the layout database.

Syntax

ELEMENT BJT{[type]} layer collector base emitter {substrate}

type: A two character code used to denote the type of BJT device. The first character must be from A to Z and second character may be from A to Z or from 0 to 9 but is optional. This code is used to differentiate BJT devices from other implants. layer: Device layer, one region per device. collector: Collector layer base: Base layer. emitter: Emitter layer. subtrate: Subtrate layer.

Examples

For extracting vertical npn,

NOT PPLUS NPLUS CHEESE

SELECT NPLUS HOLE CHEESE NPNEMIT

NOT NPLUS NPNEMIT NCOLLEC

CONNECT METAL NPNEMIT BY CONTACT

CONNECT METAL NCOLLEC BY CONTACT

CONNECT METAL PPLUS BY CONTACT

CONNECT NCOLLECT BURIED BY SINKER

ELEMENT BJT[NP] NPNEMIT BURIED PPLUS NPNEMIT

84


For extracting lateral pnp,

AREA PPLUS RANGE 224 226 LPNEMIT

SIZE LPNEMIT BY 9 OLPEMIT

SELECT PPLUS CUT OLPEMIT LPNCOLL

STAMP LPNEMIT BY PPLUS

STAMP OLPEMIT BY LPNEMIT

ELEMENT BJT[PL] LPNCOLL PPLUS BURIED OLPEMIT

85


ELEMENT BOX (LayNet)

The ELEMENT BOX command is a circuit element definition command used to define special devices (that is, element types other MOS, BJT, RES, CAP, or DIO).

Syntax

ELEMENT BOX{[type]} layer1 layer2 {layer3} {layer4} {layer5}

type: A two character code used to denote the type of BOX device. The first character must be from A to Z and second character may be from A to Z or from 0 to 9 but is optional. This code is used to differentiate the resistor devices. layer1: Device layer, one region per device, that touches or overlaps the device conductor layers. layer2: Terminal conductor layer. This layer is the conductor layer for the position NO.1 terminal and must carry node information. layer3: Terminal conductor layer. This layer is the conductor layer for the position NO.1 terminal and must carry node information. layer4: Terminal conductor layer. This layer is the conductor layer for the position NO.1 terminal and must carry node information. layer5: Substrate terminal layer. This subtrate layer is optional.

86


ELEMENT CAP (LayNet)

The ELEMENT CAP command is a circuit definition command used to define a capacitor device in the layout database.

Syntax

ELEMENT CAP{[type]} layer1 layer2 layer3 {layer4}

type: A two character code used to denote the type of CAP device. The first character must be from A to Z and second character may be from A to Z or from 0 to 9 but is optional. This code is used to differentiate capacitor devices. layer1: Device layer, one region per device. This layer is used to define the capacitor region which touches or overlaps the capacitors conductor layers. layer2: Terminal conductor layer. This layer is the conductor layer for one side of the capacitor and this layer must carry node information. layer3: Terminal conductor layer. This layer is the conductor layer for one side of the capacitor and this layer must carry node information. layer4: Substrate terminal layer. This subtrate layer is optional.

Examples





ELEMENT CAP[P] POLYCAP POLY1 POLY2

87


ELEMENT DIO (LayNet)

The ELEMENT DIO command is a circuit element definition command used to define the P-N junction diode in the layout database.

Syntax

ELEMENT DIO{[type]} layer1 layer2 layer3 {layer4}

type: A two character code used to denote the type of DIO device. The first character must be from A to Z and second character may be from A to Z or from 0 to 9 but is optional. This code is used to differentiate the diode devices. layer1: Device layer, one region per device. This layer is used to define the diode region which touches or overlaps the anode and cathode conductor layers. layer2: Anode conductor layer. This layer is the conductor layer for the anode terminal, usually the p+ diffusion or p-well, and this layer must carry node information. layer3: Cathode conductor layer. This layer is the conductor layer for the cathode terminal, usually the n+ diffusion or n-substrate, and this layer must carry node information. layer4: Substrate terminal layer. This subtrate layer is optional.

Examples

CONNECT-LAYER = NWELL PSD METAL

AND PSD DIODE PDIO

CONNECT METAL PSD BY CONT

ELEMENT DIO[P] PDIO PSD NWELL

88


ELEMENT LDD (LayNet)

Defines a MOS element whose source and drain cannot be swapped.

Syntax

ELEMENT LDD{[type]} layer1 layer2 layer3 layer4 {layer5}

type: A two character code used to denote the type of RES device. The first character must be from A to Z and second character may be from A to Z or from 0 to 9 but is optional. This code is used to differentiate the resistor devices. layer1: Device layer, one region per device. This layer is used to define the resistor region which touches or overlaps the resistor conductor layers. layer2: Gate conductor layer. This layer must carry node information. layer3: Lightly doped drain conductor layer. This layer must carry node information. layer4: Source conductor layer. This layer must carry node information. layer5: Substrate conductor layer. This subtrate layer is optional.

89


ELEMENT MOS (LayNet)

The ELEMENT MOS command is a circuit element definition command, used to define MOS devices in the layout database.

Syntax

ELEMENT MOS{[type]} layer1 layer2 layer3 {layer4}

type: A two character code used to denote the type of MOS device. The first character must be from A to Z and second character may be from A to Z or from 0 to 9 but is optional. This code is used to differentiate MOS devices from other implants. For example, CMOS pull-up devices are of type[P] and pull-down devices are of type[N]. layer1: Device layer, one region per device. For silicon gate MOS, this is the channel region layer usually defined by the overlapped area of polysilicon and diffusion. layer2: Gate conductor layer. For silicon gate MOS, this is the polysilicon layer. layer3: Source/drain conductor layer. For silicon gate MOS, this is the self-aligned diffusion layer, usually defined by the diffusion layer excluding the channel regions. layer4: Substrate conductor layer. This substrate layer is optional. For MOS, this is usually n-well, p-well, n-substrate or p-substrate.

90


Examples

AND POLY PDIFF PGATE

AND POLY NDIFF NGATE

NOT PDIFF PGATE PSD

NOT NDIFF NGATE NSD

MOS[P] PGATE POLY PSD NWELL

MOS[N] NGATE POLY NSD PWELL

91


LayNet can extract the parameters of channel width and length in MOS transistor. The channel width (W) is computed as one half of the total length that the transistor has in common with the source and drain. The channel length (L) is computed as the area of the gate divided by W. This calculation gives good results for serpentine transistors of either type. The figure below illustrates how to calculate the channel width and length of MOS transistors.

92


Each layer can contribute to the capacitance of an electrical signal or node in proportion to its area and perimeter. However, capacitors formed by diffusion need to be extracted separately, because capacitance varies considerably with voltage. The LayNet keeps track of the source/drain layers separately and includes the area and perimeter of the nodes on this layer as part of the transistors. LayNet automatically generates the following SPICE parameters: AS (area of source), AD (area of drain), PS (perimeter of source), PD (perimeter of drain). When two or more transistors have either their source or drain connected to a node, the total area and perimeter of the source is divided among the transistors in proportion to their width (W). Figure below illustrates how to calculate the areas and perimeters of source of MOS transistors.

93


ELEMENT RES (LayNet)

The ELEMENT RES command is a circuit element definition command used to define a resistor device in the layout database.

Syntax

ELEMENT RES{[type]} layer1 layer2 {layer3}

type: A two character code used to denote the type of RES device. The first character must be from A to Z and second character may be from A to Z or from 0 to 9 but is optional. This code is used to differentiate the resistor devices. layer1: Device layer, one region per device. This layer is used to define the resistor region which touches or overlaps the resistor conductor layers. layer2: Terminal conductor layer. This layer is the conductor layer usually defined by a conductor layer excluding the resistor region and this layer must carry node information. layer3: Substrate terminal layer. This subtrate layer is optional.

Examples

CONNECT-LAYER = NPOLY METAL

AND POLY RESMASK POLYRES

NOT POLY POLYRES NPOLY

CONNECT METAL NPOLY BY CONT

ELEMENT RES[P] POLYRES NPOLY

94


ENC(MyDRC)

The ENC command checks if polygons of layer1 are partially or fully enclosed by polygons of layer2. It measures between the outer edges of the polygons of layer1 and the inner edges of polygons of layer2.

Syntax

ENC{[Options]} layer1 layer2 Range {output_layer} {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}

layer1 : The first layer’s name containing the enclosed polygons. layer2 : The second layer’s name containing the enclosing polygons.

Options:

C : Flags the edge-pair when they are parallel. C’ : Inverse of C option. Flags the edge-pair when they are not parallel. E : Flags layer1’s polygons which are polygons completely outside of layer2. N : Does not flag violations on the enclosed and the enclosing polygons if they are part of the same node. N’ : Flags violations on the enclosed polygons and the enclosing polygons if they are part of the same node. O : Flags layer1 and layer2 polygons that cut/overlap each other. The violation flag covers the edge segments of layer2 that intersects layer1. ‘O’ option cannot used in the command with conjunctive OUTPUT P : Flags the edge segments that are projected onto each other. P’: Flags the edge segments that are not projected onto each other. R : Generates a new layer of quadrilateral regions. Each of the quadrilateral regions has error edge pairs as their two opposite sides and of minimum area. The new layer can be used as an input layer of other DRC commands for further checking. R’: Generates a new layer of rectangles. Each of the reatangles are of the same height as an error edge segment and of zero width. The new layer can be used as an input layer of other DRC commands for further checking. S: Flags the edge segments that are within a square boundary of the another edge. T : Flags the outer segments of the polygons of layer1 that touch the outer segments of the polygons of layer2.

Range:

95


LT n : Flags the edge segments if the distance between them is less than n microns. It does not flag an error if they touch or overlap. LE n : Flags the edge segments if the distance between them is less than or equal to n microns. It does not flag an error if they touch or overlap. RANGE n1 n2 : Flags the edge segments if the distance between them is greater than n1 microns and less than n2. If you do not want to flag acute-angle errors, then specify the RANGE measurement. SELGT n : First finds layer1’s polygons such that the distance between one of their edges and edges of layer2 is less than n microns. And then, makes such polygons a new layer specified by output_layer. The new layer can be used as an input layer of other DRC commands for further checking. SELGE n : First finds layer1’s polygons such that the distance between one of their edges and edges of layer2 is greater than or equal to n microns. And then, makes such polygons a new layer specified by output_layer. The new layer can be used as an input layer of other DRC commands for further checking. SELLT n : First finds layer1’s polygons such that the distance between one of their edges and edges of layer2 is less than n microns. And then, makes such polygons a new layer specified by the output_layer. The new layer can be used as an input layer of other DRC commands for further checking. SELLE n : First finds layer1’s polygons such that the distance between one of their edges and edges of layer2 is less than or equal to n microns. And then, makes such polygons a new layer specified by output_layer. The new layer can be used as an input layer of other DRC commands for further checking. SELRA n1 n2 : First finds layer1’s polygons such that the distance between one of their edges and edges of layer2 is greater than n1 microns and less than n2. And then, makes such polygons a new layer specified by output_layer. The new layer can be used as an input layer of other DRC commands for further checking.

message : Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. output_layer : Specifies the layer name when we perform ENC command with SELGE, SELGE, SELLT, SELLE, and SELRA options. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. & : Indicates a conjunctive rule.

96


Example 1

ENC pplus met1 LT 1.0 "ENC (METAL1, PPLUS) < 1.0"

Example 2

ENC[T] pplus met1 LT 0.01 “ENC touch error”

97


Example 3

ENCLOSE[O] pplus met1 LT 0.01 “ENC overlap error”

Example 4

ENC[E] pplus met1 LT 0.01 “ENC outside error”

98


COMPATILIBTY

The ENC command works same function like ENCOSE command in spite of command usage are differences. All options supported in the ENCLOSE command are available in the ENC command.

For example:

ENC layer1 layer2 RANGE “message” {OUTPUT c-name l-name} &

ENCLOSE layer2 layer1 RANGE “message” {OUTPUT c-name l-name} &

The above two commands work the same thing on the design rule file.

99


ENCLOSE (MyDRC)

The ENCLOSE command makes dimensional checks related to polygons of layer1 which are partially or fully enclose polygons of layer2. It measures between the outer edges of the polygons of layer2 and the inner edges of the polygons of layer1.

Syntax

ENCLOSE{[Options]} layer1 layer2 Range {output_layer} {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}

layer1: The first layer name containing the enclosing polygons. layer2: The second layer name containing the polygons being enclosed.

Options:

C : Flags the edge-pair when they are parallel. C’ : Inverse of C option. Flags the edge-pair when they are not parallel. E : Flags layer1’s polygons which are polygons completely outside of layer2. N : Does not flag violations on the enclosed and the enclosing polygons if they are part of the same node. N’ : Flags violations on the enclosed polygons and the enclosing polygons if they are part of the same node. O : Flags layer1 and layer2 polygons that cut/overlap each other. The violation flag covers the edge segments of layer2 that intersects layer1. ‘O’ option cannot used in the command with conjunctive OUTPUT P : Flags the edge segments that are projected onto each other. P’: Flags the edge segments that are not projected onto each other. R : Generates a new layer of quadrilateral regions. Each of the quadrilateral regions has error edge pairs as their two opposite sides and of minimum area. The new layer can be used as an input layer of other DRC commands for further checking. R’: Generates a new layer of rectangles. Each of the reatangles are of the same height as an error edge segment and of zero width. The new layer can be used as an input layer of other DRC commands for further checking. S: Flags the edge segments that are within a square boundary of the another edge. T : Flags the outer segments of the polygons of layer1 that touch the outer segments of the polygons of layer2.

100


Range:


message : Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. output_layer : Specifies the layer name when we perform ENCLOSE command with SELGE, SELGE, SELLT, SELLE, and SELRA options. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. & : Indicates a conjunctive rule.

101


Example 1

ENCLOSE met1 pplus LT 1.0 "ENCLOSE(MET1, PPLUS) < 1.0"

Example 2

ENCLOSE[T] met1 pplus LT 0.01 “ENCLOSE touch error”

102


Example 3

ENCLOSE[O] met1 pplus LT 0.01 “ENCLOSE overlap error”

Example 4

ENCLOSE[E] met1 pplus LT 0.01 “ENCLOSE outside error”

103


ERROR (MyDRC & LayNet)

It generates the error message for the specified layer. It is useful to locate the specified layers.

Syntax

ERROR layer {output_layer} {"message"} {OUTPUT cell-name layer-number {data-type-number}}


message: Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. output_layer: This data item is the layer which is created by the command. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255.

If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds. This example shifts the data in the metal layer by a negative 5 units in the x direction. Ouput the data to the met5 layer. Does not magnify.

Example

AND nactive poly ngate

ERROR ngate “This is ngate layer”

104


EXT(MyDRC)

The EXT commands check the distance between the outer edges of the polygons of the input layers. If layer1 and layer2 are specified as arguments, then they check the distance between the outer edges of the polygons of layer1 and the outer edges of the polygons of layer2. If only layer1 is specified, the commands check the distances between the outer edges of the polygons of layer1.

Syntax

EXT{[Option]} layer1 {layer2} Range {output_layer} {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}

layer1 : The first layer’s name. layer2 : The second layer’s name.

Options:

C : Flags the parallel edge-pairs. C’ : Flags the non-parallel edge-pairs. E : Flags the polygons of layer1 that are fully enclosed by a polygon in layer2 and the polygons of layer2 that are fully enclosed by a polygon in layer1. H : Checks the notch pattern. It flags adjacent edges in the same layer whose outer angles are less than 90 degrees. It also flags non adjacent edges in the same layer whose distances are satisfied with the given range condition. N : Does not flag violations on the polygons that are part of the same node. N’ : Flags violations on the polygons that are part of the same node. O : Flags the layer1 and layer2 polygons that cut/overlap each others. The violation flag covers the edge segments within layer1 and layer2 that outline the overlapping area of the two polygons. ‘O’ option cannot used in the command with conjunctive OUTPUT P : Flags the edge segments that project onto each other. P’: Flags the edge segments that do not project onto each other. R : Generates a new layer of quadrilateral regions. Each of the quadrilateral regions has error edge pairs as their two opposite sides and of minimum area. The new layer can be used as an input layer of other DRC commands for further checking. R’: Generates a new layer of rectangles. Each of the reatangles are of the same height as an error edge segment and of zero width. The new layer can be used as an input layer of other DRC commands for further checking.

105


S: Flags the edge segments that are within a square boundary of the another edge. T : Flags the outer segments of the polygons of layer1 that touch the outer segments of the polygons of layer2.

Range: LT n : Flags the edge segments if the distance between them is less than n microns. It does not flag an error if they touch or overlap. LE n : Flags the edge segments if the distance between them is less than or equal to n microns. It does not flag an error if they touch or overlap. RANGE n1 n2 : Flags the edge segments if the distance between them is greater than n1 microns and less than n2. If you do not want to flag acute-angle errors, then specify the RANGE measurement. SELGT n : First finds layer1’s polygons such that the distance between one of their edges and edges of layer2 is less than n microns. And then, makes such polygons a new layer specified by output_layer. The new layer can be used as an input layer of other DRC commands for further checking. SELGE n : First finds layer1’s polygons such that the distance between one of their edges and edges of layer2 is greater than or equal to n microns. And then, makes such polygons a new layer specified by output_layer. The new layer can be used as an input layer of other DRC commands for further checking. SELLT n : First finds layer1’s polygons such that the distance between one of their edges and edges of layer2 is less than n microns. And then, makes such polygons a new layer specified by the output_layer. The new layer can be used as an input layer of other DRC commands for further checking. SELLE n : First finds layer1’s polygons such that the distance between one of their edges and edges of layer2 is less than or equal to n microns. And then, makes such polygons a new layer specified by output_layer. The new layer can be used as an input layer of other DRC commands for further checking. SELRA n1 n2 : First finds layer1’s polygons such that the distance between one of their edges and edges of layer2 is greater than n1 microns and less than n2. And then, makes such polygons a new layer specified by output_layer. The new layer can be used as an input layer of other DRC commands for further checking.

message : Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. output_layer : Specifies the layer name when we perform EXT command with SELGE, SELGE, SELLT, SELLE, and SELRA options. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255.

106


& : Indicates a conjunctive rule.

Examples

EXT met1 pplus LT 1.0 “SPACE error” OUTPUT outerr 10

EXT[O] met1 pplus LT 0.01 “SPACE[O] error”

107


EXT[E] met1 pplus LT 0.01 “SPACE[E] error”

WIDTH met1 LT 2.0 “width error” &

EXT met1 poly LT 2.0 “Conj. SPACE error”

108


EXT[H] metal LT 1.2 "notch pattern error"

Important: If two layers are given for EXT command, you have to be cautious of the order. EXT layer1 layer2 and EXT layer2 layer1 is different. If the polygons are overlapped each other, second layer overlapped with first layer will be excluded from the checking for EXT layer1 layer2. Also note that H and H’ option can be used only in one layer EXT command. Therefore, EXT layer1 layer2 is not allowed. The previous P and P’ option has been changed to C and C’ respectively. New P’ is added.

COMPATILIBTY

The EXT command works same function like SPACE command. All options supported at SPACE command are available at EXT command.

For example:

EXT layer1 layer2 RANGE “message” {OUTPUT c-name l-name} &

SPACE layer1 layer2 RANGE “message” {OUTPUT c-name l-name} &


109


FLATTEN (MyDRC)

The command HCELL data and places it in a flattened layer. In flat CHECK-MODE, the command copies one layer to another.

Syntax

FLATTEN layer1 layer2

layer1 : The input layer name layer2 : The output layer name

Example

FLATTEN cont cont1

In flat CHECK-MODE, layer cont1 consists of the data from cont. And you can use cont1 in any OPERATION block command. In hierarchical CHECK-MODE, cont is a hierarchical layer and cont1 is the flattened layer.

110


GLOBAL-SCONNECT (MyDRC & LayNet)

The command specifies a global majority rule for SCONNECT. When a region has multiple nodes, SCONNECT chooses one of multiple nodes randomly. If a global majority rule is specified, SCONNECT chooses the node with the smallest node number. The default is NO.

Syntax

GLOBAL-SCONNECT = [YES|NO]

YES : Activates global majority rule for SCONNECT conflict resolution.

NO : Specifies random choice for SCONNECT conflict resolution.

Example

GLOBAL-SCONNECT = YES

111


GROW(MyDRC & LayNet)

Oversizes a single side of a layer. You can specify two different directions within a single command.

Syntax

GROW layer dx dy {dx2 dy2} output_layer {OUTPUT cell_name layer-number {data_type_number}}

layer : The name of the input layer.

dx, dy : the amount you want to size the layer. dx > 0.0 : Right edge grows dx = 0.0 : No growth dx < 0.0 : Left edge grows dy > 0.0 : Top edge grows dy = 0.0 : No growth dy < 0.0 : Bottom edge grows

dx2, dy2 : a second size amount. All values must be positive.

output_layer : Output layer name. cell_name: The cell name to be outputted in the GDS file. layer-number: The number can be 0 ~ 255. data_type_number: The number can be 0 ~ 255. Default is 0. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

Examples

Grow lay1 –0.5 –0.0 lay2

112


HEDTEXT (MyDRC & LayNet)

The command specifies the HCELL text file name. This command is similar to the EDTEXT command, except it is used for labeling hierarchical cells.

Syntax

HEDTEXT = file_name

file_name : text coordinate file name

Example

HEDTEXT = CTEXT.TXT

The following is a syntax of HEDTEXT file.

Syntax text X=x_coordinate Y=y_coordinate {ATTACH=layer_name} cell_name

text : The text string that will be attached. x_coordinate, y_coordinate : X, Y coordinate within the HCELL where text will be

attached. layer_name : The layer within the HCELL the text will attach to. cell_name : The HCELL the text will be attached to

The following is an example of a hierarchical text coordinate file.

Example: VSS x=0.5 Y=0.5 ATTACH=METAL1 INV VSS x=10.5 Y=100 ATTACH=METAL1 NAND

IN x=10 Y=25 ALU

113


INT(MyDRC)

The INT commands check the depth of which the polygons of two layers overlap. The inner edges between the polygons of two layers are checked. They check the distances between the inner edges of the polygons of layer1 and the inner edges of the polygons of layer2.

Syntax

INT{[Options]} layer1 layer2 Range {output_layer} {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}

layer1: The first input layer name. layer2: The second input layer name..

Options

C : Flags the parallel edge-pairs. C’ : Flags the non-parallel edge-pairs. N : Does not flag violations on the polygons that are part of the same node. N’ : Flags violations on the polygons that are part of the same node. P : Flags the edge segments that project onto each other. P’: Flags the edge segments that do not project onto each other. R : Generates a new layer of quadrilateral regions. Each of the quadrilateral regions has error edge pairs as their two opposite sides and of minimum area. The new layer can be used as an input layer of other DRC commands for further checking. R’: Generates a new layer of rectangles. Each of the reatangles are of the same height as an error edge segment and of zero width. The new layer can be used as an input layer of other DRC commands for further checking. S: Flags the edge segments that are within a square boundary of the another edge. T : Flags the outer segments of the polygons of layer1 that touch the outer segments of the polygons of layer2.

114


Range:


message : Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. output_layer : Specifies the layer name when we perform INT command with SELGE, SELGE, SELLT, SELLE, and SELRA options. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. & : Indicates a conjunctive rule. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

115


Examples

INT[T] met1 pplus LT 0.01 “Overlap[T] error”

116


COMPATILIBTY

The INT command works same function like OVERLAP command. All options supported at OVERLAP command are available at INT command.

For example:

INT layer1 layer2 RANGE “message” {OUTPUT c-name l-name} &

OVERLAP layer1 layer2 RANGE “message” {OUTPUT c-name l-name} &


117


LCONNECT (LayNet)

The LCONNECT command checks to determine whether the areas at the specific layers are part of a labeled node. The areas that satisfy the specified condition are reported and put into errors.

Syntax

LCONNECT layer Condition label OUTPUT message or

LCONNECT layer Condition label {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}

layer: The name of the layer that is being checked; this layer must be a conductor layer and be defined in the CONNECT-LAYER and the CONNECT commands.

Condition :

CONN: CONN indicates that the areas which are part of the labeled node are to be reported. DISC: DISC indicates that the areas which are not part of the labeled node are to be reported. label: This is the text label of the node to be checked. It must be labeled as text in the layout database conforming to the text rules.

message: Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

118


Examples

CONNECT-LAYER = NSD METAL

CONNECT METAL NSD BY CONT

LCONNECT METAL CONN VSS OUTPUT ERC01

The example above will check all the geometries on the metal layer to see if there are any that are connected to the labeled node VSS. The output for this check will be all the polygons on the specified layer that carry the particular nodal information.

119


LENGTH (MyDRC)

The LENGTH command makes dimensional checks that are used to perform a length dimension spacing check.

Syntax

LENGTH layer Range {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}

layer: The input layer name.

Range

EQ n: Flags the edge segments of polygons of the input layer whose lengths are equal to n microns. LT n: Flags the edge segments of polygons of the input layer whose lengths are less than n microns. LE n: Flags the edge segments of polygons of the input layer whose lengths are less than or equal to n microns. GT n: Flags the edge segments of polygons of the input layer whose lengths are greater than n microns. GE n: Flags the edge segments of polygons of the input layer whose lengths are greator than or equal to n microns. NE n: Flags the edge segments of polygons of the input layer whose lengths are not equal to n microns. RANGE n1 n2: Flags the edge segments of polygons of the input layer whose lengths are greater than n1 microns and less than n2 microns.

message: Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. & : Indicates a conjunctive rule. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

120


Examples

SIZE ACTIVE BY 4.0 OACT

AND OACT METAL ACTMET

LENGTH ACTMET GT 15.0 "ACTIVE TOO CLOSE TO METAL"

121


LVSCHK (MyLVS) **

The LVSCHK command is used to compare the SPICE netlist. LVSCHK command is enough for LVS to run.

Syntax

LVSCHK{[options]} {tolerances}

Options (when specifying options, they must be bracketed.):

C: CMOS reduce option (NOR, NAND, AOI and OAI) L: CMOS reduce option (NOR and NAND) F: All unused devices will be filtered from checking. K: All parallel devices will remain unsmashed. S: All the parallel MOS-series with the same I/O will be smashed. X: No swapping of inputs will be allowed. U: Only the unmatched devices on matched node will be reported. R: All series and parallel resistors will be smashed. A: All series capacitors will be smashed. P: The capacitor polarity will be checked.

B:Bulk nodes will be compared.

Tolerances:

WPERCENT: The tolerance percentage of a transistor width. LPERCENT: The tolerance percentage of a transistor length. CAPAREA: The tolerance percentage of a capacitor area. CAPVAL: The tolerance percentage of a capacitor value. DIOAREA: The tolerance percentage of a diode area. DIOPERI: The tolerance percentage of a diode perimeter. RESVAL: The tolerance percentage of a resistor value.

Example

LVSCHK[SUR] WPERCENT=9 LPERCENT=8.5 CAPAREA=7

Note: The percentage now can be fraction numbers.

122


MULTILAB (LayNet)

The MULTILAB command checks to determine if one node has been labeled with different text string. This condition usually occurs when two or more labeled nodes are shorted to each other. For example, if one node has the label VCC as well as the label VSS, then the power supply node and the ground node have been shorted somewhere. To locate where these nodes have been shorted, LayNet will trace the closest path between the different labels. Focusing on this generated path, errors may then be easily located.

Syntax

MULTILAB OUTPUT message or

MULTILAB {“message”} {OUTPUT cell-name layer-number {data-type-number}}

message: Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

Examples

MULTILAB OUTPUT ERC01

LayNet will output the most direct path between the two shorted text strings and prune off all other portions of the shorted nodes. If multiple shorts are detected on a single node, only one short will be outputted per run.

123


NDCOUNT (LayNet)

The NDCOUNT command counts, for an individual element, the total number of different nodes being connected to the element through specific terminal layers. Those elements with node counts which satisfy certain conditions are reported and put into errors.

Syntax

NDCOUNT element{[type]} term Condition OUTPUT message {&} or

NDCOUNT element{[type]} term Condition {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}


Condition

LT n: A node count less than the number n. LE n: A node count less than or equal to the number n. EQ n: A node count equal to the number n. NE n: A node count not equal to the number n. GT n: A node count greater than the number n. GE n: A node count greater than or equal to the number n.

message: Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. &: This indicates that this operation is part of a conjunctive rule. This conjunctive rule option is placed at the end of the command line. It can be conjoined to the other NDCOUNT and ECONNECT commands.

124


Examples


NDCOUNT MOS[P] ALL EQ 1 OUTPUT ERC01

The above check will flag all P-type MOS with their gate, source, and drain tied together. The areas of errors will contain the element recognition area of all the P-type MOS transistors that satisfied the criteria. This command can be conjoined with itself and/or the check above will flag all P-type MOS with their gate, source, and drain tied together.

This command can be conjoined with itself and/or ECONNECT. Again, a conjunctive rule is one which requires more than one command to achieve the desired results. The following check will flag all MOS[P] with 2 source/drains, and all terminals still equal to 2.


NDCOUNT MOS[P] PSD EQ 2 &

NDCOUNT ALL EQ 2 ERC01

125


NOT (MyDRC & LayNet)

The NOT command is a logical operation which may be used to create a new layer from two other layers. The new layer consists of the portion of the first input layer minus the region shared by both input layers. The order of the two input layer arguments is very important and it affects the electrical node information.

Syntax

NOT layer1 layer2 output_layer {OUTPUT cell_name layer-number {data_type_number}}

layer1: The first input layer name. layer2: The second input layer name. output_layer: This data item is the layer which is created by the logical operation. The electrical node information is automatically stamped on this generated layer from the first layer name only after nodal information is set up by using the CONNECT command on the involved layer1. cell_name: The cell name to be outputted in the GDS file. layer-number: The number can be 0 ~ 255. data_type_number: The number can be 0 ~ 255. Default is 0. If you used OUTPUT, the GDS file will be created and the name of GDS file is result.gds. The resultant geometries are written with cell name as cell_name + layer-number.

Examples

NOT layer1 layer2 result_layer

126


OCTBIAS(MyDRC & LayNet)

Cuts all Manhattan corners on the input layer into octagonal corners with a radius of n1 and outputs the results to a new layer.

Syntax

OCTBIAS inlayer BY n1 output_layer {OUTPUT cell_name layer-number {data_type_number}}

inlayer : Name of the input layer. n1 : Radius of the octagonal corners. output_layer : Output layer name. cell_name: The cell name to be outputted in the GDS file. layer-number: The number can be 0 ~ 255. data_type_number: The number can be 0 ~ 255. Default is 0. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

Example

OCTBIAS metal by 5 omet OUTPUT omet 50

127


OR (MyDRC & LayNet)

The OR command is a logical operation which may be used to create a new layer from two other layers. The new layer consists of the total region defined by both input layers. The order of the two input layers is irrelevant. The resulting layer doesn't have the electrical node information.

Syntax

OR layer1 layer2 output_layer {OUTPUT cell_name layer-number {data_type_number}}

layer1: The first input layer name. layer2: The second input layer name. output_layer: This data item is the layer which is created by the logical operation. cell_name: The cell name to be outputted in the GDS file. layer-number: The number can be 0 ~ 255. data_type_number: The number can be 0 ~ 255. Default is 0. If you used OUTPUT, the GDS file will be created and the name of GDS file is result.gds. The resultant geometries are written with cell name as cell_name + layer-number.

Examples

OR layer1 layer2 result_layer

128


OVERLAP (MyDRC)

The OVERLAP command makes dimensional checks that determine the depth to which polygons of two layers overlap into each other. This checks the overlap distance of the inside edges of layer2 polygons into layer1 polygons.

Syntax

OVERLAP{[Options]} layer1 layer2 Range {output_layer} {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}

layer1: The first input layer name. layer2: The second input layer name.

Options

C : Flags the parallel edge-pairs. C’ : Flags the non-parallel edge-pairs. N : Does not flag violations on the polygons that are part of the same node. N’ : Flags violations on the polygons that are part of the same node. P : Flags the edge segments that project onto each other. P’: Flags the edge segments that do not project onto each other. R : Generates a new layer of quadrilateral regions. Each of the quadrilateral regions has error edge pairs as their two opposite sides and of minimum area. The new layer can be used as an input layer of other DRC commands for further checking. R’: Generates a new layer of rectangles. Each of the reatangles are of the same height as an error edge segment and of zero width. The new layer can be used as an input layer of other DRC commands for further checking. S: Flags the edge segments that are within a square boundary of the another edge. T : Flags the outer segments of the polygons of layer1 that touch the outer segments of the polygons of layer2.

129


Range:


message : Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. output_layer : Specifies the layer name when we perform OVERLAP command with SELGE, SELGE, SELLT, SELLE, and SELRA options. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. & : Indicates a conjunctive rule. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

130


Examples

OVERLAP[T] met1 pplus LT 0.01 “Overlap[T] error”

131


PARAMETER CAP (LayNet)

The PARAMETER CAP command is used to input the capacitance per unit area and capacitance per unit perimeter. The PARAMETER CAP command works in conjunction with the ELEMENT CAP command. If no PARAMETER CAP command is specified for a given ELEMENT CAP, the default is set to zero.

Syntax

PARAMETER CAP{[type]} value1 value2

type: The type of CAP device is specified in the ELEMENT CAP[type] command. value1: The capacitance per unit area of layer1 that exists between layer2 and

layer3 of the ELEMENT CAP command. The unit of value1 is pF/um2. value2: The capacitance per unit perimeter of layer1 of the ELEMENT CAP command. The unit of value2 is pF/um.

132


Examples





ELEMENT CAP[P] POLYCAP POLY1 POLY2

PARAMETER CAP[A] 0.01 0.0

133


PARAMETER RES (LayNet)

The PARAMETER RES command is used to input the sheet resistance value of the resistors defined by a corresponding ELEMENT RES command. The PARAMETER RES command works in conjunction with the ELEMENT RES command. If no PARAMETER RES command is specified for a given ELEMENT RES, the default is set to zero.

Syntax

PARAMETER RES{[type]} value

type: The type of RES device specified in the ELEMENT RES[type] command. value: The sheet resistance of layer1.

Examples

CONNECT-LAYER = NPOLY METAL

AND POLY RESMASK POLYRES

NOT POLY POLYRES NPOLY

CONNECT METAL NPOLY BY CONT

ELEMENT RES[P] POLYRES NPOLY

PARAMETER RES[P] 20

134


PARASITIC CAP (LayNet)

The PARASITIC CAP command is an parasitic element definition command used to define parasitic capacitor devices in the layout database. An ATTRIBUTE CAP command must follow the PARASITIC CAP command and is used to associate the geometry data with the corresponding process-dependent electrical properties.

Syntax

PARASITIC CAP{[type]} layer1 layer2 layer3

type: A two character code used to denote the type of parasitic CAP device. The first character must be from A to Z and second character may be from A to Z or from 0 to 9 but is optional. This code is used to differentiate the parasitic capacitor devices. layer1: Device layer, one region per device. This layer is used to define the parasitic capacitor region which touches or overlaps the capacitors conductor layers. Also, this device layer must carry the same nodal information of terminal conductor layer2. layer2: Terminal conductor layer. This layer is the conductor layer for one side of the capacitor and this layer must carry node information. layer3: Terminal conductor layer. This layer is the conductor layer for one side of the capacitor and this layer must carry node information.

Examples

CONNECT-LAYER = P11 P12 METAL

AND METAL POLY METPOLY


PARASITIC CAP[MP] METPOLY METAL POLY

135


PARASITIC DIO (LayNet)

The PARASITIC DIO command is an parasitic element definition command used to define the parasitic P-N and N-P junction diodes in the layout database.

Syntax

PARASITIC DIO{[type]} layer1 layer2 layer3

type: A two character code used to denote the type of parasitic DIO device. The first character must be from A to Z and second character may be from A to Z or from 0 to 9 but is optional. This code is used to differentiate the parasitic diode devices. layer1: Device layer, one region per device. This layer is used to define the parasitic diode region which touches or overlaps the anode and cathode conductor layers. Using this device layer would result in extracting the diode area and perimeter. This device layer must have the same layer name as the anode or cathode conductor layer -- depending whether it is a P-N or N-P junction diode. It must also carry the nodal information. layer2: Anode conductor layer. This layer is the conductor layer for the anode terminal. It must also carry node information. For a P-N diode, this layer name must have the same name as layer1. layer3: Cathode conductor layer. This layer is the conductor layer for the cathode terminal and must carry node information. For a N-P diode, this layer name must have the same name as layer1.

136


Examples

CONNECT-LAYER = PWELL NSD PSD POLY METAL

AND PSD PWELL PTWELL


CONNECT METAL PSD BY CONT

CONNECT PSD PWELL BY PTWELL

AND NSD PWELL NDIO

PARASITIC DIO[N] NDIO PWELL NDIO

137


PATHCHK (LayNet)

The PATHCHK command is a technology dependent electrical rule check applied ONLY to MOS circuits where a node is supposed to have a path to both the power and ground through one or more source/drain of the MOS device and resistor device. Nodes without a proper path to either power or ground are assigned an error level code depending on the nature of the connections. There are 4 levels of the PATHCHK command and each level checks for a particular condition.

Syntax

PATHCHK Level OUTPUT message or

PATHCHK Level {“message”} {OUTPUT cell-name layer-number {data-type-number}}

Level:

LEVEL 1: Nodes with a path only to the ground but not to the power. LEVEL 2: Nodes with a path only to the power but not to the ground. LEVEL 3: Nodes without a path to neither the power nor the ground. LEVEL 4: Nodes without a path to neither the power nor the ground and a path

to a labeled node will be excluded. message: Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255..

138


Examples

PATHCHK LEVEL 1 OUTPUT ERC01




ERC01 : Node 5

ERC02 : Node 4

ERC03 : Node 1, 2, 3, 6, 7, 8, 9

ERC04 : Node 1, 2, 3, 6, 7, 8

139


PLENGTH (MyDRC)

Instead of just checking the length of an edge, the PLENGTH command checks the length of a series of connected edges.

Syntax

PLENGTH layer Range {output-layer} {“message”} {OUTPUT cell-name layer-number {data-type-number}}


Range

EQ n: Flags the polygons whose sum of connected edge lengths are equal to n microns. LT n: Flags the polygons whose sum of connected edge lengths are less than n microns. LE n: Flags the polygons whose sum of connected edge lengths are less than or equal to n microns. GT n: Flags the polygons whose sum of connected edge lengths are greater than n microns. GE n: Flags the polygons whose sum of connected edge lengths are greater then or equal to n microns. NE n: Flags the polygons whose sum of connected edge lengths are not equal to n microns. RANGE n1 n2: Flag the polygons whose sum of connected edge lengths greater than n1 microns and less than n2 microns.

message: Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. output_layer: This data item is the layer which is created by the command. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

140


Examples

AND DIFFUS POLY GATE

PLENGTH GATE LT 8.0 "GATE TOO NARROW"

141


PROBE (LayNet)

The PROBE command is used to probe all nodes which have been labeled. Input text must be provided in the layout database to label the node of interest. The output for this command will be all the polygons on the specified layer that carry a particular nodal information with a labeled node.

Syntax

PROBE label OUTPUT message {&} or

PROBE label {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}

label: This is the text label of the node to be checked. It must be labeled as text in the layout database and be conformed to the text rules. message: Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. &: This indicates that this operation is part of a conjunctive rule. This conjunctive rule option is placed at the end of the command line. It can be conjoined to the other PROBE and ELCOUNT commands.

If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

Example

PROBE VDD OUTPUT ERC01

The check above will flag only the VDD node as error.

142


RELOCATE(MyDRC & LayNet)

Creates a new layer from a layer which is consists of data from the layer shifted a new x, y position or with each of vertices multiplied by the specified scale.

Syntax

RELOCATE layer BY dx dy output_layer {MAG=scale} {OUTPUT cell_name layer-number {data_type_number}}

layer : Input layer name.

dx dy : New location of layer data that is shifted by natural units specified for X and Y.

scale : Optional magnification factor. Default is 1.0

output_layer : Output layer name. cell_name: The cell name to be outputted in the GDS file. layer-number: The number can be 0 ~ 255. data_type_number: The number can be 0 ~ 255. Default is 0. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds. This example shifts the data in the metal layer by a negative 5 units in the x direction. Ouput the data to the met5 layer. Does not magnify.

Examples

RELOCATE metal BY –5 0 met5

This example shifts the data in the metal layer by a negative 5 units in the x direction. Ouput the data to the met5 layer. Does not magnify.

143


SAMELAB (LayNet)

The SAMELAB command detects the case where the same label has been assigned to multiple nodes. This condition usually concurs when the layout of a node is not complete, there are missing contacts, gaps are present, or other errors. Multiple nodes with the same label are reported and put into errors.

Syntax

SAMELAB OUTPUT message or

SAMELAB {“message”} {OUTPUT cell-name layer-number {data-type-number}}



Examples

SAMELAB OUTPUT ERC01

144


SCONNECT (MyDRC & LayNet)

The SCONNECT command is an operation used to pass the nodal information in ONLY one direction; from a conductor layer to any other layers or upper layer to lower layer, but not the reverse. The CONNECT command passes nodal information in either direction.

Syntax

SCONNECT layer1 layer2 BY contact_layer

layer1: First input layer name layer2: Second input layer name contact_layer: contact layer will connect layer1 to layer2, but must be previously defined.

Examples

CONNECT-LAYER = PWELL NWELL PSD NSD POLY METAL

AND PWELL PSD PCONT

AND NWELL NSD NCONT



CONNECT METAL PAS BY CONT

SCONNECT PSD PWELL BY PCONT

SCONNECT NSD NWELL BY NCONT

145


In this example node information is passed from PSD to PWELL but not from PWELL to PSD, and from NSD to NSUB but not from NSUB to NSD. Suppose there is more than one NSD in NWELL, one had a connection to VDD through metal and contact and the other did not. By using CONNECT commands nodal information of VDD is passed from one NSD to NWELL and from the NWELL up to the other NSD, from that NSD to METAL and from the METAL to the source of the transistor with no hard connection to VDD, thus a floating PSD has node information of VDD. With SCONNECT this does not happen.

When a region has multiple node numbers, SCONNECT chooses one node number.To use the global majority rule for SCONNECT conflict resolution, use GLOBAL-SCONNECT command.To report the violation geometries, use SOFTCHK command.To stop the verification for soft connection violations, use ABORT-SOFTCHK command.

146


SELECT (MyDRC & LayNet)

The SELECT command is an operation which selects a group of polygons out of a layer under certain conditions and creates a new layer. The SELECT command is an area which meets the relational condition imposed on layer1 and layer2. Some selective operations that cannot be done by logical operations, sizing, geometrical checking, and conjunctive rules can be performed by this command. The SELECT command doesn’t output a polygon if there is no polygon of layer1 and/or layer2.

Syntax(1)

SELECT {[N]} {NOT} layer1 Relation layer2 output-layer {OUTPUT cell-name layer-number {data-type-number}}

N : Turns on node-based instead of polygon-based selection. This option must be used after the circuit connection is established. Polygon of layer1 that are part of the same node as layer1 that satisfy the relation to layer2 will be selected. NOT : complementary option layer1: The layer to be selected from. layer2: The layer to be related to. Relations: INSIDE : Any polygon of layer1 that is totally inside any polygon of layer2. Polygon of layer1 that is inside and inside touch layer2 will be selected. OUTSIDE : Any polygon of layer1 that is totally outside any polygon of layer2. Polygon of layer1 that is outside and outside touch layer2 will be selected. HOLE : Any polygon of layer1 that is entire outside surface exactly touching by the outside surface of layer2. A polygon of layer1 that exactly fits in the hole of a donut-shaped polygon of layer2 is an example. These selected polygons of layer1 are also outside and touch. output-layer: This data item is the layer which is created by the SELECT operation. The electrical node information is automatically stamped on this generated layer from the first layer name only after nodal information is set up by using the CONNECT command on the involved layer1. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255.

147


data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

Syntax(2)

SELECT {[N]} {NOT} layer Relation {[n1:n2]} layer2 output-layer {OUTPUT cell-name layer-number {data-type-number}}

N : Turns on node-based instead of polygon-based selection. This option must be used after the circuit connection is established. Polygon of layer1 that are part of the same node as layer1 that satisfy the relation to layer2 will be selected. NOT : complementary option layer: The layer to be selected from. [n1:n2] : the range of instances that satisfy the selective condition. Relations: CUT : Any polygon of layer1 that has portions both inside and outside of layer2 TOUCH : Any polygon of layer1 that only touches the outside edge of any layer2 polygon. This touch condition will exclude polygon of layer1 that both touch and cut polygon(s) of layer2. ENCLOSE : Any polygon of layer1 that encloses any polygon(s) of layer2. This enclose condition also includes polygon of layer1 that inside-touch of layer2. OVERLAP : Any polygon of layer1 that has the relation of touch, cut, inside, hole and enclose with polygons of layer2. output-layer: Name of the output layer. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

148


Syntax(3)

SELECT {NOT} layer LABEL {[R]} name output-layer {OUTPUT cell-name layer-number {data-type-number}}

NOT : complementary option layer: The layer to be selected from. LABEL : Any polygon of layer1 that has the specified label on it. To use

LABEL, you may need to provide nodal information on the polygon using the ATTACH and CONNECT command.

R : Select the polygon on the layer that best satisfies the nodal condition, instead of polygons that satisfy the nodal condition. You must specify the ATTACH command for layer in LAYER block.

name : the node name. output-layer: Name of the output layer. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

Syntax(4)

SELECT {NOT} layer ISLAND output-layer {OUTPUT cell-name layer-number {data-type-number}}

NOT: complementary option layer: The layer to be selected from.

ISLAND: Any polygon of layer that exists in the entire outside of other layers. output-layer: Name of the output layer. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

149


Syntax(5)

SELECT {NOT} layer VERTEX [n1:n2] output-layer {OUTPUT cell-name layer-number {data-type-number}}

NOT : complementary option layer: The layer to be selected from. [n1:n2] : the range of vertex count. output-layer: Name of the output layer. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255.


Syntax(6)

SELECT {NOT} layer ANGLE[n] output-layer {OUTPUT cell-name layer-number {data-type-number}}

NOT : complementary option layer: The layer to be selected from.

n: Specifies which angled geometries to separate. You can specify one of the following options: 90 : For Manhattan geometries. (All edges are either vertical or horizontal.) 45 : For 45-degree geometries. (All edges are either 45 degrees, or edges are Manhattan and contain at least one 45degree edge.) -90 : For non-Manhattan geometries. (At least one edge is not vertical or horizontal.) -45 : For non-45 degree geometries. (Angles are other than Manhattan and 45 degree.) output-layer: Name of the output layer. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255.

150


data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255.

Syntax(7)

SELECT {NOT} layer1 BY layer2 LABEL {[T] | [T’]} {label | label-list} output-layer {OUTPUT cell-name layer-number data-type-number}}

NOT : complementary option layer1 : The layer to be selected form. layer2 : IDTEXT layer name. BY LABEL : Use this command when you specify the IDTEXT command in

LAYER block. T : Selects objects texted by the given labels.

T’ : Selects objects that are not texted by the given labels.

label : text string

label-list : A list of up to maximum of 20 of labels.

output-layer : Name of the output layer

OUTPUT : Sends the results of the operation to an output cell.

cell-name : The name of output cell

layer-number : The layer number for GDSII. Values can range from 0 to 255.

data-type-number : Data type number associated with the layer number

(layer-number) of the output cell. It can have an integer value raging from 0 to

255.

151


Examples 1

SELECT layer 1 INSIDE layer 2 new ; 1,2

SELECT layer 1 OUTSIDE layer 2 new ; 3,4

SELECT layer 1 TOUCH layer 2 new ; 4,9

SELECT layer 1 CUT layer 2 new ; 5,6,7,8

SELECT layer 1 ENCLOSE layer 2 new ; 6,7

SELECT layer 1 HOLE layer 2 new ; 9

SELECT layer1 LABEL VDD vdd_metal

SELECT layer1 VERTEX[4:4] rectangle

SELECT layer1 OVERLAP layer2 new; 1,2,4-9

152


Example 2

SELECT met1 VERTEX[5:6] sel_vertex

ERROR sel_vertex

Example 3

SELECT met1 ISLAND tmp1 OUTPUT errisland 8

ERROR tmp1

153


SHRINK(MyDRC & LayNet)

Undersizes a single side of a layer. You can specify two different directions within a single command.

Syntax

SHRINK layer dx dy {dx2 dy2} output_layer {OUTPUT cell_name layer-number {data_type_number}}

layer : The first input layer name.

dx, dy : the amount you want to undersize the layer. dx > 0.0 : Right edge shrinks dx = 0.0 : No sizing dx < 0.0 : Left edge shrinks dy > 0.0 : Top edge shrinks dy = 0.0 : No sizing dy < 0.0 : Bottom edge shrinks

dx2, dy2 : a second undersize amount. All values must be positive.

output_layer : Output layer name. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds. This example shifts the data in the metal layer by a negative 5 units in the x direction. Ouput the data to the met5 layer. Does not magnify.

Examples

Shrink layer1 1 1.5 layer2

154


SIZE (MyDRC & LayNet)

The SIZE command is an operation used to create a new layer from another layer. The new layer is oversized or undersized by a specified number of micron units. The sides of the polygon are moved perpendicular to their original location. The sign of the specified units will determine if the polygon is to be oversized (positive) or undersized (negative). When SIZE is executed, the resulting layer no longer carries nodal information.

Syntax

SIZE layer BY n output_layer {OUTPUT cell_name layer-number {data_type_number}}

layer: The input layer name. n: This data item indicates the number of micron units by which the input layer will be oversized (positive), undersized (negative), or copied(zero). output_layer: The layer name which is created by the resizing operation. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds. This example shifts the data in the metal layer by a negative 5 units in the x direction. Ouput the data to the met5 layer. Does not magnify. When the layer is oversized, automatic OR commands are involved to get a merged layer when oversizing may generate some overlapped area. Since OR commands are occurred before shrinking or oversizing, the objects drawn separately but adjacent becomes one shrunken object.

155


Examples

SIZE poly BY -1 unpoly

SIZE poly BY 1 ovpoly

156


SOFTCHK (MyDRC & LayNet)

The command is used to check regions on a layer defined in SCONNECT that connect to more than one node. The command works only if you’ve used the SCONNECT command.

Syntax

SOFTCHK layer {output_layer} OUTPUT[U|A] cell_name layer-number {data_type_number}

layer : layer defined in SCONNECT that you are checking from which you need to generate the soft connection violation outputs.

output_layer : The output layer name which is created for soft connection violation.

OUTPUT : Sends the result of the operation to an output cell. Output cell will contain all regions of the layer in the drawing.

A : It will create an additional output cell containing both the minorityand majority contact layer from the soft connection violation. This cell will have the same name as the OUTPUT statement,proceeded by a U.

U : It will create an additional output cell containing the minoritycontact layer from the soft connection violation. This cell will have the same name as the OUTPUT statement, proceeded by a U.

cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds. This example shifts the data in the metal layer by a negative 5 units in the x direction.Ouput the data to the met5 layer. Does not magnify.

157


Example

CONNECT-LAYER = PSUB NWELL PSD NSD POLY METAL ….

AND NWELL NSD NCONT AND PSUB PSD PCONT

CONNECT METAL POLY BY CONTACT CONNECT METAL PSD BY CONTACT CONNECT METAL NSD BY CONTACT SCONNECT NSD NWELL BY NCONT SCONNECT PSD PSUB BY PCONT SOFTCHK NWELL OUTPUT[U] SOFTCON 10 In this example, NWELL be assigned with the majority node n the NSD layer in SCONNECT. The multiple node within a NWELL problem is caught with SOFTCHK. There will be two output cells created with SOFTCHK command. One cell will be SOFTCON10 which will contain all the NWELL’s like the one in the drawing. The other cell, created due to the OUTPUT[U], will be USOFTCON10. Because of ‘U’ option, output only the minority contacts.

158


SPACE (MyDRC)

The SPACE command checks the distance between outside edges of polygons. If layer1 and layer2 are specified as arguments, then the outside edges of layer1 are checked against the outside edges of layer2. If only layer1 is specified, the outside edges of that layer are checked against each other. Unless the specific options are given, the edges of polygon to be overlapped aren't checked against each other.

Syntax

SPACE{[Options]} layer1 layer2 Range {output_layer} {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}

layer1: The first input layer name. layer2: The second input layer name.

Options:

C : Flags the parallel edge-pairs. C’ : Flags the non-parallel edge-pairs. E : Flags the polygons of layer1 that are fully enclosed by a polygon in layer2 and the polygons of layer2 that are fully enclosed by a polygon in layer1. H : Checks the notch pattern. It flags adjacent edges in the same layer whose outer angles are less than 90 degrees. It also flags non adjacent edges in the same layer whose distances are satisfied with the given range condition. N : Does not flag violations on the polygons that are part of the same node. N’ : Flags violations on the polygons that are part of the same node. O : Flags the layer1 and layer2 polygons that cut/overlap each others. The violation flag covers the edge segments within layer1 and layer2 that outline the overlapping area of the two polygons. ‘O’ option cannot used in the command with conjunctive OUTPUT P : Flags the edge segments that project onto each other. P’: Flags the edge segments that do not project onto each other. R : Generates a new layer of quadrilateral regions. Each of the quadrilateral regions has error edge pairs as their two opposite sides and of minimum area. The new layer can be used as an input layer of other DRC commands for further checking. R’: Generates a new layer of rectangles. Each of the reatangles are of the same height as an error edge segment and of zero width. The new layer can be used as an input layer of other DRC commands for further checking.

159


S: Flags the edge segments that are within a square boundary of the another edge. T : Flags the outer segments of the polygons of layer1 that touch the outer segments of the polygons of layer2.


message : Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. output_layer : Specifies the layer name when we perform SPACE command with SELGE, SELGE, SELLT, SELLE, and SELRA options. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255.

160


& : Indicates a conjunctive rule.

Examples

SPACE met1 pplus LT 1.0 “SPACE error” OUTPUT outerr 10

SPACE[O] met1 pplus LT 0.01 “SPACE[O] error”

161


SPACE[E] met1 pplus LT 0.01 “SPACE[E] error”

WIDTH met1 LT 2.0 “width error” &

SPACE met1 poly LT 2.0 “Conj. SPACE error”

162


SPACE[H] metal LT 1.2 "notch pattern error"

Important: If two layers are given for SPACE command, you have to be cautious of the order. SPACE layer1 layer2 and SPACE layer2 layer1 is different. If the polygons are overlapped each other, second layer overlapped with first layer will be excluded from the checking for SPACE layer1 layer2. Also note that H and H’ option can be used only in one layer SPACE command. Therefore, SPACE layer1 layer2 is not allowed. The previous P and P’ option has been changed to C and C’ respectively. New P’ is added.

163


STAMP (MyDRC & LayNet)

The STAMP command is an operation used to flag generated layers that are part of an electrical node but are not defined within the CONNECT command. The STAMP command must be used after the circuit connection is established.

Syntax

STAMP layer1 BY layer2 {OUTPUT cell-name layer-number {data-type-number}}

layer1: This data item is the layer name of the previously generated layer which is to be stamped with the electrical node specification. layer2: This data item is the layer name of a layer which contains the electrical node labeling information. It may result from a previous CONNECT, STAMP, or logical command. OUTPUT : Sends the multiple-stamped geometries to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds. The stamping process only occurs for polygons in the stamped layer which are overlapped by polygons in the stamping layer. Designers must be very careful in choosing the appropriate layer to be stamped. Only a singular node overlap is allowed.

164


Examples

CONNECT MET POLY BY CONT

STAMP CONT BY MET

In the figure below numbers 1 and 2 are internal node numbers of layer MET and -1 represents either no STAMPED node number or conflicting node number.

165


WIDTH (MyDRC)

The WIDTH command makes dimensional checks between inside edges of polygons in the same layer.

Syntax

WIDTH{[Options]} layer1 Range {output_layer} {“message”} {OUTPUT cell-name layer-number {data-type-number}} {&}


Options

D : Disable Acute angle check. C : Flags the parallel edge-pairs. C’ : Flags the non-parallel edge-pairs. L : Length check. Useful for exact contact check. P : Flags the edge segments that are projected onto each other. P’: Flags the edge segments that are not projected onto each other. R : Generates a new layer of quadrilateral regions. Each of the quadrilateral regions has error edge pairs as their two opposite sides and of minimum area. The new layer can be used as an input layer of other DRC commands for further checking. R’: Generates a new layer of rectangles. Each of the reatangles are of the same height as an error edge segment and of zero width. The new layer can be used as an input layer of other DRC commands for further checking. S: Flags the edge segments that are within a square boundary of the another edge.

166



message : Specifies a text string that is enclosed in double quotation marks. It is displayed in the Layed with the related error. output_layer : Specifies the layer name when we perform WIDTH command with SELGE, SELGE, SELLT, SELLE, and SELRA options. OUTPUT : Sends the results of the operation to an output cell. cell-name : The name of output cell layer-number : The layer number for GDSII. Values can range from 0 to 255. data-type-number : Data type number associated with the layer number (layer-number) of the output cell. It can have an integer value ranging from 0 to 255. & : Indicates a conjunctive rule. If you used OUTPUT, the GDS file will be created and the name of GDS file is cell_name+layer-number.gds.

167


Examples

WIDTH met1 LT 0.01 “Acute Angle”

WIDTH met1 LT 0.9 “width (m1) < 0.9” OUTPUT perr00 88

WIDTH[P] met1 LT 0.9 “width[p] (m1) < 0.9” OUTPUT perr00 89

168


WIDTH pwell LT 3 “width(pwell) < 3.0” &

EXT pwell nwell LT 1.0 “ext.(p, nwell)” OUTPUT drc22 10

169


XOR (MyDRC & LayNet)

The XOR command performs boolean “xor” operation for the given two layers and then generates a new layer as its operation result. The new layer consists of the mutually exclusive regions in both of the input layers.

Syntax

XOR layer1 layer2 output-layer {OUTPUT cell-name layer-number {data-type-number}}

layer1: The first input layer name. layer2: The second input layer name. output_layer: This data item is the layer which is created by the logical operation. cell_name: The cell name to be output in the GDS file. layer-number: The number can be 0 ~ 255. data_type_number: The number can be 0 ~ 255. Default is 0. If you used OUTPUT, the GDS file will be created and the name of GDS file is result.gds. The resultant geometries are written with cell name as cell_name + layer-number.

Examples

XOR layer1 layer2 result_layer

* LayNet doesn’t support XOR command.

170


LVS

Before using MyLVS

You should check the following items in order for LVS to function properly.

Initial corresponding node pair: You should provide ample node names to execute LVS and it’s recommended that you have same node names for both the schematic and layout netlist. Power nodes and ground nodes are not considered as initial node pair. You need to provide at least one node other than power and ground node to begin with.

Check that all devices are connected properly. Make sure that all devices are connected to at least one node but no more than two nodes.

Check for any short circuits. Use the MULTILAB in the LayNet.

Check for any open circuits. Use the SAMELAB and ELCOUNT in the LayNet.

Requirements

Layout Data

Schematic SPICE netlist

MyLVS options from extraction rule (LVSCHK command)

171


Control Statements

Statements may be added to the netlist which apply to MyLVS but not to the simulator. These statements supply information to MyLVS when compiling the netlist. An asterisk (“*”) preceding a statement indicates that the line should be read by MyLVS and not by the circuit simulator.

172


GLOBAL Statement

Declares global nodes such as power, ground or any nodes whuch are not defined as IOs to .SUBCKTs, but should be considered IOs if that node exists within the .SUBCKT.

Example

*.GLOBAL VDD VSS

Declaration of Power Node

VDD, VCC, PWR and POWER are the reserved power nodes and simply put them at .GLOBAL line entitles them as power node. To declare the other node as power node, use :P suffix at the end of node name.

Example *.GLOBAL VDD MyPower:P VDD2:P

Declaration of Ground Node

VSS, VGG, GND and GROUND are the reserved ground nodes and simply putting them at .GLOBAL line entitles to be ground nodes. To declare the other nodes as ground nodes, use :G suffix at the end of node the name.

Example *.GLOBAL VSS MyGround:G VSS2:G

Note: The last declaration is recognized and accepted when there is duplicate declaration of the node.

Example *.GLOBAL MyPWR:P

*.GLOBAL MyPWR

MyPWR node is recognized as a regular node, not as a power node.

Most cases that the reduction does not occur even though the reduction option (L or C) is chosen are due to the improper declaration of power and ground nodes.

173


EQUIVALENT Statement

The *.EQUIVALENT statement has two uses in MyLVS.

At first, it is to equate the node names to the corresponding node names or numbers in the netlist.

Example

*.EQUIVALENT VCC=1 VSS=0

Secondly, it is to equate the model name to the corresponding model name in the netlist.

Example

*.EQUIVALENT P=MP N=MN

M1 1 A VDD VDD MP W=10 L=1 M2 2 B VSS VSS MN W=10 L=1

174


DEFAULT

The *.DEFAULT statement allows user to assign a default width and length value to all transistors in the netlist that have no W and L specification.

Example

*.DEFAULT W=10 L=2.5

175


PIN

The *.PIN statement is used in a netlist to define those HCELL I/O’s which are not defined as I/O’s in the .SUBCKT definition for a HCELL, but which are required to complete the initial correspondence between that layout HCELL and the schematic HCELL. This command is used in conjunction with the *.GLOBAL command, as any node defined by the *.PIN command must have been previously defined as a *.GLOBAL node.

If the *.PIN command is issued outside of a .SUBCKT, then all HCELL .SUBCKT’s will have these I/O’s associated with them. If the *.PIN command is issued within a .SUBCKT definition, the I/Os are associated with that .SUBCKT only.

Example

*.GLOBAL VDD VSS

*.PIN VDD VSS

.SUBCKT INV IN OUT

…

.ENDS

176


NOPIN

The *.NOPIN statement is used in a netlist within a .SUBCKT to override HCELL I/O’s that were previously defined the *.PIN command.

Example

*.GLOBAL VDD VSS

*.PIN VDD VSS

.SUBCKT INV IN OUT

…

.ENDS

.SUBCKT CFR A B

*.NOPIN VDD

…

.ENDS

177


LVS Flow Design

In this flow diagram, you can see how the design data are transferred and used in each individual tool in MyCAD.

Schematic Capture/Editor

SchEd(MyAnalog Station)

SPICE Netlist Extraction

Logic2SPICE(MyAnalog Station)

spice.spc

Full CustomIC

LayEd(MyChip Station)

Layout NetlistExtraction

LayNet(MyChip Station)

extract.1

netshape.1

devshape.1

MyLVS

Schematic Netlist

Layout Data

(Schematic Data) (Layout Data)

Rule Editor(MyChip Station

Rule File Generation

Rule File

error file

lvs_bin.1

lvs error data

178


The schematic netlist used in the LVS should be in SPICE netlist format. To prepare the schematic netlist, we use the schematic editor tool, SchEd from MyLogic Station. To transform the schematic data into a SPICE netlist, we use Logic2Spice from MyAnalog Station. The files generated from this process is “spice.spc”.

The netlist generated from the layout, “extract.1”, resides under its cell directory. This file is automatically generated by the LayNet tool (by Extract & ERC command in LayEd pull-down menu) from MyChip Station. The file, “layout.1” is created when the user draws the layout and saves it using LayEd from MyChip Station. The file, “extract.1” is generated based on “layout.1” by running LayNet. In addition to “extract.1”, “netshape.1” and “devshape.1” are generated and these two files are used to generate lvs_bin.1 for displaying LVS errors on the LayEd screen.

Running LVS requires options from the rule, a schematic netlist and the layout data. After running LVS, the differences between the schematic netlist and layout netlist are saved in a discrepancy report file and a graphic data file (lvs_bin.1). By using the coordinate information of all devices generated from LayNet, LVS print (X,Y) coordinate of reported devices in a discrepancy file.

179


Initial corresponding node pairs

To run LVS, a starting point to compare is needed. We provide the starting point by matching the node names from the layout netlist to the node names from the schematic netlist.

A

B

C

SUM

CARRY

VDD VSS

The layout netlist should have the node names: A, B, C, SUM, CARRY, VDD, VSS.

The respective nodes above are a good starting point for the LVS. For large and complicated circuits, the more nodes the better. LVS speed is directly correlated to the number of nodes provided in the starting point.

180


LVS Options

No CMOS reduce

It will not recompose the circuits into NOR, NAND, AOI and OAI except INV and parallel and series of smashing devices such as PUP, SUP, PUPI, SUPI, SDW, PDW, SDWI, PDWI. It will compare the netlist as it is. It is exclusive with C and L options and without C or L option, no CMOS reduce happens.

C: CMOS reduce option (NOR, NAND, AOI and OAI)

It will recompose the circuits into NOR, NAND, AOI and OAI. Circuits that are celld differently but produce the same logic are considered to be the same.

L: CMOS reduce option (NOR and NAND)

This option is the same as C except the fact that it will recompose only NOR and NAND.

TRAINSISTORLEVEL DATABASE layout & schematic

REDUCE

CMOSREDUCE

CMOSREDUCE

NANDNORAOIOAI

NANDNOR

default

RECOGNIZINGEXCEPT AOI'S

AND OAI'S

RECOGNIZINGNOR, NAND,

AOI'S AND OAI'S

PUP SDWSUP PDWPUPI SDWISUPI PDWI

181


F: All unused devices will be filtered from checking

By filtering out the devices that are not being used, the time to run LVS is reduced. Floating devices and devices that are not properly connected are filtered out. Following devices would be filtered out.

VDD

VDD

P

VSS

VSS

N

ANY

ANY

P

ANY

ANY

NVSS

VDD

1) 2) 3)

4) 5) 6)

1), 2) The MOS with a floating gate which the source and the drain are connected to POWER or GROUND and the gate is floating. 3), 4) The MOS of which the gate is connected to POWER or GROUND. 5) The MOS of which the drain, the gate and the source are connected to one node. 6) The MOS of which the drain, the gate and the source are all floating. 7) The bipolar of which the collector, base and emitter are all floating.

182


K: All parallel devices will remain unsmashed

As default, all parallel devices are smashed while processed by MyLVS. Use this option if you DO NOT want them to be smashed. This option applies to bipolar devices as well.

DEFAULT =

WITH THIS OPTION =

W1 / L1

=>W2 / L1 W1 + W2 / L1

=>

183


S: All parallel series with the same I/O will be smashed.

This options will smash the serially connected parallel devices which has the same I/O.

DEFAULT =

WITH THIS OPTION =

=>

A

B

OUT

A

B

OUT

=>

A

B

OUT

A

B

OUT

X: No swapping of inputs will be allowed.

With this option even if swapping of inputs produce the same logic, the swapping of inputs is not allowed.

U: Only the unmatched schematic and unmatched layout devices on matched nodes will be reported.

184


As a default, all unmatched devices with matching nodes that are connected will be reported as a discrepancy. Use this option if you want to see the unmatched devices ONLY.

DEFAULT ******************** DISCREPANCY 1 ******************** --- NODE A7 --- WITH EXTRA LAYOUT DEVICES --- DEV1 MOS P ---- M3 <==> DEV2 MOS P ---- M3 A3, A6, A7 A3, A6, A7 DEV2 MOS P ---- M2 <==> DEV3 MOS P ---- M2 A2, A5, A7 A2, A5, A7 DEV3 MOS P ---- M1 <==> DEV4 MOS P---- M1 A1, A4, A7 A1, A4, A7 ****** UN-MATCHED ****** <==> ?DEV1 MOS P ---- M4 B1, B2, A7 WITH THIS OPTION ******************** DISCREPANCY 1 ******************** --- NODE A7 --- WITH EXTRA LAYOUT DEVICES --- ****** UN-MATCHED ****** <==> ?DEV1 MOS P ---- M4 B1, B2, A7

R: All series/parallel resistors will be smashed.

All series or parallel resistors will be smashed.

A: All series capacitors will be smashed.

All series capacitors will be smashed.

P: The capacitor polarity will be checked.

The capacitor polarity will be checked.

B: Bulk nodes will be reported

The Bulk nodes will be compared.

185


Special Values

LISTUNMATCH

This value controls the number of unmatched layout and schematic devices in the report file. The default is 100

MULDELW

This value controls the effective channel width of parallel MOS transistors.

The width and the length are calculated as follows when MULDELW=0 and n parallel transistors are smashed to one transistor.

W=ƴA *C

L=ƴA/C

A=W(1)*L(1)+W(2)*L(2)+...+W(n)*L(n) C=W(1)/L(1)+W(2)/L(2)+...+W(n)/L(n) The width and the length are calculated as follows when MULDELW0 and n parallel transistors are smashed to one transistor. Weff=Wactual+(N-1)*MULDELW L=A/C Weff=effective MOS width Wactual=sum of all width of parallel fingered devices N=number of smashed parallel fingers of the transistor

186


Tolerance

The following is the range of tolerance to be considered as the same. The tolerance can be fraction.

WEFFECT=n1 : A tolerance of perent of tr. Effective width

This value controls the tolerance for the effective MOS width of the smashed parallel MOS devices. If MULDELW is 0, the MOS width tolerance is the value of WPERCENT. If MULDELW is not 0, the MOS width tolerance is the value of WEFFECT.

WPERCENT=n2 : A tolerance of percent for transistor width

LPERCENT=n3: A tolerance of percent for transistor length

CAPAREA=n4 : A tolerance of percent for capacitor area

CAPVAL=n5 : A tolerance of percent for capacitor value

DIOAREA=n6 : A tolerance of percent for diode area

DIOPERI=n7 : A tolerance of percent for diode perimeter

RESVAL=n8 : A tolerance of percent for resistor value

The tolerance is specified as percentage. If the width of transistor in schematic is 1.0 and is 0.8 in layout is and WPERCENT=10, then it is considered as a different device.

187


The LVS error type

There are 15 LVS error types.

1. Matched node connected to no device

This error occurs when the nodes are NOT connected to any devices.

** WARNING ** SCHEM PAD : D CONNECTED TO NOTHING

2. Matched device but unmatched node

This error occurs when the device and some of the nodes are matched but has a few unmatched nodes.

?A

A2

A1

A2

SCHEMATIC LAYOUT

2 2

188


******************** DISCREPANCY 1 ******************** --------------------------MATCHED DEVICE UN-MATCHED NODE---- DEV1 SDW <==> DEV1 SDW 2, A1, A2 2, ?A, A2

3. Inconsistently matched device

This error is similar to error #2.

A

A2

A1

A2

SCHEMATIC LAYOUT

2 2

******************** DISCREPANCY 1 ******************** --------------------------INCONSISTENTLY MATCHED DEVICE----- DEV1 SDW <==> DEV1 SDW 2, A1, A2 2, A, A2

189


4. Matched node but extra devices in layout (missing schematic devices)

This error occurs when the devices are matching but more devices are connected in the layout netlist.

A1

SCHEMATIC LAYOUT

A2 A3

A7

A1 A2 A3 B1

A7

A4 A5 A6 A4 A5 A6 B2

P P P P PP P

******************** DISCREPANCY 1 ******************** --- NODE A7 --- WITH EXTRA LAYOUT DEVICES --- DEV1 MOS P ---- M3 <==> DEV2 MOS P ---- M3 A3, A6, A7 A3, A6, A7 DEV2 MOS P ---- M2 <==> DEV3 MOS P ---- M2 A2, A5, A7 A2, A5, A7 DEV3 MOS P ---- M1 <==> DEV4 MOS P---- M1 A1, A4, A7 A1, A4, A7 ****** UN-MATCHED ****** <==> ?DEV1 MOS P ---- M4 B1, B2, A7

190


5. Matched node but extra devices in schematic (missing layout devices)

This error occurs when the devices are matching but more devices are connected in the schematic netlist.

A1

SCHEMATIC LAYOUT

A2 A3

A7

A1 A2 A3 C1

A7

A4 A5 A6 A4 A5 A6 C2

P P P P PP PB1

B2

P

******************** DISCREPANCY 1 ******************** --- NODE A7 --- WITH UN-MATCHED DEVICES --- DEV2 MOS P ---- M3 <==> DEV3 MOS P ---- M3 A3, A6, A7 A3, A6, A7 DEV3 MOS P ---- M2 <==> DEV4 MOS P ---- M2 A2, A5, A7 A2, A5, A7 DEV4 MOS P ---- M1 <==> DEV5 MOS P ---- M1 A1, A4, A7 A1, A4, A7 ?DEV1 MOS P ---- M4 <==> ****** UN-MATCHED ****** B1, B2, A7 ****** UN-MATCHED ****** <==> ?DEV2 MOS P ---- M4 C1, C2, A7

191


6. Matched node but unmatched layout and schematic device

This error occurs when there are some matched nodes but a few unmatched devices.

A1

SCHEMATIC LAYOUT

A2 A3

A7

A1 A2 A3 C1

A7

A4 A5 A6 A4 A5 A6 C2

P P P P PP PB1

B2

P

******************** DISCREPANCY 1 ******************** --- NODE A7 --- WITH UN-MATCHED DEVICES --- DEV2 MOS P ---- M3 <==> DEV3 MOS P ---- M3 A3, A6, A7 A3, A6, A7 DEV3 MOS P ---- M2 <==> DEV4 MOS P ---- M2 A2, A5, A7 A2, A5, A7 DEV4 MOS P ---- M1 <==> DEV5 MOS P ---- M1 A1, A4, A7 A1, A4, A7 ?DEV1 MOS P ---- M4 <==> ****** UN-MATCHED ****** B1, B2, A7 ****** UN-MATCHED ****** <==> ?DEV2 MOS P ---- M4 C1, C2, A7

192


7. Other unmatched layout devices

This error occurs when layout devices are unmatching because the comparison between matching nodes cannot be completed or devices are considered unmatching due to different nodes.

********** UN-MATCHED LAYOUT DEVICES ********** ********** (LIST UP TO 100 ) ********** ****** UN-MATCHED ****** <==> ?DEV1 MOS NSS ---- M5 C2, ?2, C1 ****** UN-MATCHED ****** <==> ?DEV2 MOS P ---- M4 C1, C2, A7

8. Other unmatched schematic devices

This error occurs when layout devices are unmatching because the comparison between matching nodes cannot be completed or devices are considered unmatching due to different nodes.

********** UN-MATCHED SCHEMATIC DEVICES ********** ********** (LIST UP TO 100 ) ********** ?DEV1 MOS NSS ---- M5 <==> ****** UN-MATCHED ****** ?A, ?2, OUT ?DEV2 MOS P ---- M4 <==> ****** UN-MATCHED ****** B1, B2, A7

193


9. Device subtype mismatch

This error occurs when the cells of devices are the same but of a different type.

A1

SCHEMATIC LAYOUT

A2

A3

[P]A1

A2

A3

[N]

******************** DISCREPANCY 1 ******************** DEV5 MOS N ---- M1 <==> DEV5 MOS P ---- M1 A1, A3, A2 A1, A3, A2 SUB-TYPE = N SUB-TYPE = P

194


10. MOS device size (W, L) mismatch

This error occurs when the width or length of MOS is different above the threshold of the tolerance.

A1

SCHEMATIC LAYOUT

A2

A3

L = 2A1

A2

A3

L = 2

W = 8 W = 14

******************** DISCREPANCY 1 ******************** DEV5 MOS N ---- M1 <==> DEV5 MOS N---- M1 A1, A3, A2 A1, A3, A2 W = 8.00 L = 2.00 W = 14.00 L = 2.00

11. MOS reversibility error (Not supported)

195


12. MOS substrate connection mismatch

This error occurs when the connection of MOS substrate is different.

A1

SCHEMATIC LAYOUT

A2

A3

VDDPA1

A2

A3

VSSN

******************** DISCREPANCY 1 ******************** DEV5 MOS N ---- M1 <==> DEV5 MOS N---- M1 A1, A3, A2 A1, A3, A2 SUBSTRATE = VSSN SUBSTRATE = VDDP

196


13. MOS power connection mismatch

This error occurs when there are more than one power source driving the devices.

A1

SCHEMATIC LAYOUT

A2

A3

VDDPA1

A2

A3

VSSN

******************** DISCREPANCY 1 ******************** DEV5 MOS N ---- M1 <==> DEV5 MOS N---- M1 A1, A3, A2 A1, A3, A2 SUBSTRATE = VSSN SUBSTRATE = VDDP

A1

SCHEMATIC LAYOUT

VCC2 : P

A2

A1

VCC1 : P

A2

197


A1

A3

A1

A2

A3

A2

10 / 3

20 / 3

BA

30 / 3BA

******************** DISCREPANCY 1 ******************** DEV5 MOS N ---- M1 <==> DEV5 MOS N ---- M1 A1, A2, VCC1 A1, A2, VCC2 POWER = VCC1 POWER = VCC2

14. Reduced layout parallel devices

This error occurs when the K option (All parallel devices will remain unsmashed) is selected and there are parallel devices being smashed. It will not be written in the log file (discrepancy). Instead, you can display it on the LayEd screen.

198


15. Filtered out layout MOS devices

This error occurs when F option (All unused devices will be filtered from checking) is selected and the unused devices are found. It will not be written in the log file. Instead, you can display it on the LayEd screen.

199


Index A ABORT-SOFTCHK..........................................................................................24, 146 ACUTE ....................................................................................................................69 ALL ..................................................................................25, 69, 79, 82, 83, 124, 125 AND... 18, 21, 64, 67, 68, 72, 76, 87, 88, 91, 94, 104, 121, 133, 134, 135, 137, 141,

145, 158 ANGLE ................................................................................................18, 67, 69, 150 AREA.........................................................................................18, 43, 67, 70, 71, 85 ATTACH ........................................................18, 20, 56, 57, 58, 65, 66, 81, 113, 149 ATTRIBUTE CAP ......................................................................................18, 72, 135

C CAPAREA .....................................................................................................122, 187 CAPVAL ........................................................................................................122, 187 CDL .........................................................................................................................14 CELL .........................................................................................25, 26, 27, 53, 54, 55 CELLBNDY .............................................................................................................59 CELL-ERROR-REP ..........................................................................................25, 26 CHANNEL .................................................................................................90, 92, 186 CHECK-MODE........................................................................25, 26, 27, 53, 54, 110 CMOS REDUCE ...........................................................................................122, 181 COMP..............................................................................................25, 27, 53, 54, 55 CONJUNCTIVE79, 80, 82, 83, 95, 96, 100, 101, 105, 107, 115, 120, 124, 125, 130,

142, 147, 159, 161, 167 CONNECT. 18, 20, 21, 56, 58, 60, 61, 65, 66, 67, 68, 72, 73, 74, 75, 76, 84, 87, 88,

94, 118, 119, 126, 133, 134, 135, 137, 145, 146, 147, 149, 158, 164, 165 CONNECT-LAYER18, 20, 56, 58, 60, 61, 65, 66, 72, 73, 74, 75, 76, 87, 88, 94, 118,

119, 133, 134, 135, 137, 145, 158 CORNER...............................................................................................18, 43, 67, 77 CUT.......................................................................................53, 54, 55, 85, 148, 152

D DEFAULT ......................................................................................................175, 185 DELCEL ................................................................................................18, 23, 29, 30 DESCRIPTION..................................................18, 19, 22, 23, 25, 26, 43, 53, 54, 64 DEVICE SHAPE..........................................................................6, 7, 11, 12, 52, 179 DIOAREA ......................................................................................................122, 187 DIOPERI........................................................................................................122, 187

200


DISCREPANCY...................................................................12, 15, 16, 179, 185, 198 DISPLAY-FLAG-ERROR.........................................................................................30 DRC LOG..............................................................................................................3, 5 DRC SUMMARY .......................................................................33, 34, 35, 36, 37, 38

E ECONNECT ..........................................................................18, 67, 79, 80, 124, 125 EDTEXT .......................................................................................................... 81, 113 ELCOUNT .............................................................................18, 67, 82, 83, 142, 171 ELEMENT BJT........................................................................................................84 ELEMENT BOX.................................................................................................18, 86 ELEMENT CAP.................................................................................18, 87, 132, 133 ELEMENT DIO..................................................................................................18, 88 ELEMENT LDD .................................................................................................18, 89 ELEMENT MOS ............................................................................18, 80, 83, 90, 125 ELEMENT RES.........................................................................................18, 94, 134 ENC...............................................................................18, 43, 67, 95, 96, 97, 98, 99 ENCLOSE .......................... 18, 43, 67, 96, 97, 98, 99, 100, 101, 102, 103, 148, 152 END.....................................................................................................................8, 22 EQUIVALENT........................................................................................................174 ERROR .......................................................................................25, 26, 67, 104, 153 EXT ................................................ 18, 26, 43, 67, 81, 105, 106, 107, 108, 109, 169 EXTRACTED NETLIST...............................................................6, 9, 10, 11, 13, 179

F FILTER-OPT......................................................................................................31, 32 FLAG-NON45........................................................................................18, 23, 30, 34 FLAG-OFFGRID .............................................................................18, 23, 30, 35, 36 FLAG-PTH-OFFGRID ...........................................................................18, 23, 30, 36 FLAG-SELFINTERS ...................................................................................30, 37, 38 FLAG-SELFTOUCH..........................................................................................30, 38 FLAT................................................................................................25, 27, 53, 54, 55 FLATTEN......................................................................................................... 19, 110

G GLOBAL................................................................................ 111, 146, 173, 176, 177 GLOBAL-SCONNECT .................................................................................. 111, 146 GROUND ..............................................................................18, 23, 39, 57, 173, 182 GROW................................................................................................. 18, 43, 67, 112

201


H HCELL...........................................25, 26, 27, 40, 41, 42, 50, 59, 110, 113, 176, 177 HCELL-FILE......................................................................................................40, 41 HCELL-RULE..........................................................................................................42 HEDTEXT.............................................................................................................. 113 HIER..........................................................................................25, 26, 27, 53, 54, 55 HOLE.......................................................................................................84, 147, 152 HSPICE...................................................................................................................49

I IDTEXT............................................................................................................62, 151 INSIDE ....................................................................................................77, 147, 152 INT................................................................................18, 43, 67, 114, 115, 116, 117 ISLAND .........................................................................................................149, 153

L LABEL .......................................................................................62, 73, 149, 151, 152 LAMBDA......................................................................................................18, 23, 43 LayEd ............................................. 2, 3, 4, 5, 6, 7, 12, 13, 16, 17, 52, 179, 198, 199 LAYER18, 20, 22, 56, 58, 60, 61, 62, 64, 65, 66, 72, 73, 74, 75, 76, 87, 88, 94, 118,

119, 133, 134, 135, 137, 145, 149, 151, 158 LayNet ... 1, 6, 7, 9, 10, 12, 13, 15, 18, 23, 24, 25, 27, 29, 30, 33, 34, 35, 36, 37, 38,

39, 40, 41, 43, 44, 46, 48, 49, 51, 52, 53, 54, 55, 56, 57, 59, 60, 61, 62, 63, 64, 65, 66, 68, 70, 72, 73, 77, 79, 81, 82, 84, 86, 87, 88, 89, 90, 92, 93, 94, 104, 111, 112, 113, 118, 123, 124, 126, 127, 128, 132, 134, 135, 136, 138, 142, 143, 144, 145, 147, 154, 155, 157, 164, 170, 171, 179

LAYNET LOG...................................................................................................... 6, 11 LAYNET SUMMARY .................................................................33, 34, 35, 36, 37, 38 LCONNECT ...................................................................................... 18, 67, 118, 119 LENGTH......................................................................................18, 43, 67, 120, 121 LISTUNMATCH.....................................................................................................186 LPERCENT ...................................................................................................122, 187 LUMPCAP.............................................................................................18, 23, 44, 46 LVSCHK ....................................................................14, 15, 18, 31, 32, 67, 122, 171

M MASTER LAYER.........................................................................................61, 73, 75 MODE....................................................................19, 23, 25, 26, 27, 46, 53, 54, 110 MODEL..................................................................................................18, 19, 23, 48 MULDELW.....................................................................................................186, 187

202


MULTILAB.........................................................................................18, 67, 123, 171 MyDRC.. 1, 3, 4, 5, 16, 18, 23, 24, 25, 27, 29, 30, 33, 34, 35, 36, 37, 38, 39, 40, 41,

42, 43, 48, 50, 51, 53, 54, 55, 56, 57, 59, 60, 61, 62, 63, 64, 65, 66, 68, 69, 70, 73, 77, 81, 95, 100, 104, 105, 110, 111, 112, 113, 114, 120, 126, 127, 128, 129, 140, 143, 145, 147, 154, 155, 157, 159, 164, 166, 170

MyLVS.......................1, 2, 6, 11, 12, 13, 14, 15, 16, 31, 52, 122, 171, 172, 174, 183

N NDCOUNT ............................................................................18, 67, 79, 80, 124, 125 NET SHAPE............................................................................................ 6, 11, 12, 52 NET SHAPE......................................................................................................7, 179 NETLIST-FORMAT .....................................................................................18, 23, 49 NON-ACUTE...........................................................................................................69 NOPIN...................................................................................................................177 NOT.................. 18, 50, 67, 84, 91, 94, 126, 134, 147, 148, 149, 150, 151, 183, 188 NOTCH..........................................................................................105, 109, 159, 163 NOT-HCELL ............................................................................................................50

O OCTBIAS...................................................................................................18, 67, 127 ONCE................................................................................................................25, 26 OPERATION .............................................18, 21, 22, 25, 26, 60, 62, 64, 67, 74, 110 OR.....................................................................................................18, 67, 128, 155 OUTSIDE ................................................................................................77, 147, 152 OVERLAP ................................... 18, 43, 67, 115, 116, 117, 129, 130, 131, 148, 152

P PARAMETER RES................................................................................................134 PARASITIC CAP .............................................................................................72, 135 PARASITIC DIO ......................................................................................18, 136, 137 PATHCHK..........................................................................................18, 67, 138, 139 PIN ................................................................................................................176, 177 PLENGTH ...................................................................................18, 43, 67, 140, 141 POWER...............................................................1, 18, 19, 23, 51, 57, 173, 182, 198 PROBE....................................................................................18, 57, 67, 82, 83, 142 PSEUDO CONTACT.........................................................................................75, 76

R RAMETER CAP ............................................................................................132, 133 RELOCATE .........................................................................................18, 43, 67, 143 RESVAL ........................................................................................................122, 187

203


204

S SAMELAB .........................................................................................18, 67, 144, 171 SCONNECT .............................................................. 18, 67, 111, 145, 146, 157, 158 SELECT ........................... 18, 62, 67, 73, 84, 85, 147, 148, 149, 150, 151, 152, 153 SHAPE-FILE ...............................................................................................18, 23, 52 SHRINK...............................................................................................18, 43, 67, 154 SIZE ........................................................................18, 43, 67, 77, 85, 121, 155, 156 SOFTCHK .......................................................................................24, 146, 157, 158 SPACE ............................... 18, 43, 67, 106, 107, 108, 109, 159, 160, 161, 162, 163 SPICE..............................1, 6, 8, 9, 10, 11, 12, 13, 14, 15, 48, 49, 93, 122, 171, 179 STAMP ........................................................................................18, 67, 85, 164, 165 SUBSTRATE...............................................................................18, 59, 63, 196, 197 SUBSTRATE-TAP...................................................................................................76

T TEMPORARY-LAYER .......................................................................................18, 64 TEXT-LAYER...............................................................................................18, 65, 66 TEXTSEQUENCE.............................................................................................18, 66 TOUCH..........................................................................................................148, 152

V VERTEX................................................................................................150, 152, 153 VIRTUAL CONNECT ..............................................................................................57 VIRTUAL WIRING...................................................................................................58

W WEFFECT.............................................................................................................187 WELL-TAP...............................................................................................................76 WIDTH........................................................ 18, 43, 67, 108, 162, 166, 167, 168, 169 WINDEL ......................................................................................................53, 54, 55 WINDOW.....................................................................................................53, 54, 55 WINDOW-CUT............................................................................................53, 54, 55 WPERCENT..................................................................................................122, 187

X XOR.................................................................................................................67, 170

mychip station pro verification reference manualseloco.com/mycad_/customer/manual/veriproref.pdf ·...

Documents