Circuit Level Netlist Generation

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

A computer program listing consisting of a total of 6 microfiche and a total of 483 frames and referenced herein as "the Appendix" was submitted to the Patent and Trademark Office as a microfiche appendix to this patent document, and hereby is incorporated herein by reference. The microfiche appendix contains 21 Parts, as follows:

1. Field of the Invention

The present invention relates to computer aided design of electronic circuits, and more particularly to the generation of a circuit level netlist from a logic level netlist of an integrated circuit.

2. Description of Related Art

The high cost of integrated circuit design has led to the development of circuits that are customized to perform a user-defined function. This class of circuits includes the gate array, which is an integrated circuit that includes an array of unwired logic gates that are customized at the metallization mask stage.

The design and layout sequence 30 for a customer designed gate array, which generally is known as a customer "option," is illustrated in FIG. 1. FIG. 1 also shows a connectivity check step 28 which follows the design and layout sequence 30. Integrated systems for performing the design and layout sequence of FIG. 1 are generally available, and include the FAIRCAD (Trademark) system of National Semiconductor Corporation, Santa Clara, Calif.

The design and layout sequence 30 generally begins with a schematic capture step 10 and the generation of logic netlist 12. The logic netlist 12 is a logic level description of the customer option, specifying the names of each individual occurrence or "instance" of macrocells in the customer option, pin utilization, and connectivity between the various macrocell instances. In the FAIRCAD system, the filename of the logic netlist 12 is GENNET.LIS. In performing the schematic capture step 10, the option designer works with a predetermined set of logical element symbols, interconnecting each instance of a logic element in the customer option as desired and specifying parameters for each instance. These parameters include power requirements and number of inputs and outputs desired. Schematic capture software suitable for operation on workstations or general purpose computers is separately available from such vendors as, for example, Silvar-Lisco, Inc. of Sunnyvale, Calif.

A pre-layout simulation 14 preferably is performed on the logic netlist 12 to confirm the logic functionality of the customer option. If the logic functionality is not satisfactory, the customer option is modified as necessary by repeating the schematic capture step 10. Another pre-layout simulation is performed on the modified logic netlist 12 to confirm the logic functionality of the redesigned customer option. Suitable simulation software systems for use on workstations or general purpose computers include the FAIRLOGS (Trademark) system, which is part of the FAIRCAD system available from National Semiconductor Corporation; and the VERILOGS (Trademark) system, available from Gateway Design Automation Corp., Westford, Mass.

Once the logic functionality of the customer option is confirmed, a placement and routing operation 16 is performed on the customer option, as represented in the logic netlist 12. Several files result from the placement and routing step 16, the most notable of which are a physical connectivity data file 17, a file 18 that provides the bias driver identification associated with every macro instance in the customer option, a file 19 that specifies the names of input I/O macro instances of the customer option using pulldown resistors, and a file 20 specifying the pad to signal name relationships for the customer option. In the FAIRCAD system, these files are known as DESIGN.DFF, DESIGN.BOV, DESIGN.MVA, AND XXAUTOPIN.S50 respectively. The physical connectivity data file 17, the bias driver identification file 18, and the I/O macro pulldown resistor definition file 19 are used in a post-processing step 22, discussed below. The pad - I/O signal relationship file 20 is generally used in a test verification operation that occurs after fabrication of the customer option. Placement and routing software systems for use on workstations or general purpose computers are available separately, and include the GARDS system available from Silvar-Lisco, Inc.

A post-layout simulation preferably is then done to confirm the timing characteristics of the physical connectivity, which is modified as necessary in an iterative process involving placement and routing step 16 and post-layout simulation step 21. The previously mentioned FAIRLOGS system and VERILOGS system are suitable for use in post-layout simulation.

Once the physical connectivity of the file 17 is confirmed, the physical connections are "databased" from the physical connectivity data file 17 in a post-processing operation 22 to produce a physical data base 24. The physical data base 24 preferably is produced in a suitable industry standard format, such as the CV format of the Computervision Corporation of Bedford, Mass. which is now a division of Prime Computer, Inc.; the APL format of the CAD/CAM Division of Schlumberger Technologies, Inc., Ann Arbor, Mich.; and the GDS format of the Calma Company of San Diego, Calif., now a division of Prime Computer, Inc.

The post-processing operation 22 requires many input files. Some of these input files are physical data base files contained in several different libraries. One set of input files is found in the macrocell library 2. The files of this set are for the various types of macrocells corresponding to the logic elements made available to the option designer. A macrocell is an elementary circuit used as a building block in the design of ASIC chips such as gate arrays and standard cells, and may have various power and input/output configurations. Macrocell libraries are available from a number of manufacturers, including National Semiconductor Corporation, which describes an ECL family of macrocells in a publication entitled FGA Series Macro Library for ASPECT (Trademark) ECL Gate Arrays, Revision No. 0.3, 1989. Another set of input files is found in the overlay library 4. The files of this set are for various metallization and contact layer definitions used in customizing an instance of a macrocell to a selected power configuration. Another set of input files is found in the bias generator library 6. The files of this set are for various standard bias generators.

Some of the input files to the post processing step 22 are generated in the placement and routing step 16, as described above. One of these files is the physical connectivity file 17 (DESIGN.DFF). Another input file, the bias driver identification file 18 (DESIGN.BOV), contains an identification of the bias netlist utilized by each single macro instance. Another input file, the I/O macro pulldown file 19 (DESIGN.MVA), defines the pulldown resistor utilization of the various input macros.

To ensure correct implementation of the customer option, a physical connectivity check must be done on the layout. Traditionally, physical connectivity checking was performed manually in a process called "plot checking." The physical data base files are used to print composite plots 26, which are reviewed by an integrated circuit engineer in a connectivity checking operation 28. Unfortunately, a plot check of, for example, an ECL (emitter-coupled logic) gate array design of 15,000 gate level complexity at a component level is time and resource intensive and subject to human error. The plot check is further complicated by the option designer's use of different configurations of each macrocell, due to different requirements for power and input/output combinations throughout the customer option.

The macrocell library 2, the overlay library 4, and the bias generator library 6 generally are created as follows. A circuit level netlist is prepared, either by being written directly by an engineer or generated automatically from a circuit schematic prepared by an engineer. The macrocell is laid out using computer tools, such as, for example, the SCALD (Trademark) system with the LED and LED2STREAM software, which is available from Valid Logic Systems, Inc. of San Jose, Calif. The resulting physical data base is compared with the circuit level netlist, also commonly with computer tools, to ensure consistency in continuity. Commercially available software suitable for performing the comparison includes the "Layout versus Schematic" system available from Cadence Design Systems, Inc. of Santa Clara, Calif.; and the "Network Consistency Check" system available from Silvar-Lisco, Inc.

Unfortunately, this technique is not effective for use on large circuit designs. The manual generation of a circuit schematic or a circuit level netlist for an entire customer option, which generally includes many macrocell instances in complex arrangements, is time and resource intensive and subject to human error. For an ECL (emitter-coupled logic) gate array design of 15,000 gate level complexity, for example, the manual generation of a circuit schematic netlist may be commercially impracticable.

The present invention simplifies such activities as connectivity checking by providing an easily implemented technique for generating a circuit schematic level netlist from a logic level netlist. When implemented on a computer, the invention achieves a rapid and automatic generation of the circuit schematic level netlist.

These and other advantages are achieved by the present invention, which in one embodiment is a method for generating a circuit level netlist from a customer logic design of an application specific integrated circuit. In this method, a first set of files is acquired that corresponds to reoccurring combinations of components present in a set of macrocells, the macrocells of which correspond to the logic elements available for use by the designer of the customer option. A second set of files is acquired that corresponds to the macrocells of the macrocell set. The component combinations are represented in this second set in high level symbology. A logic netlist that identifies macrocell instances in said design and defines the connectivity therebetween is acquired. Then, a circuit level netlist of the customer option is constructed from the logic netlist and the first and second sets of files. This circuit level netlist may be compared with the physical data base of the customer option to check connectivity.

In a further embodiment, the second set of files corresponding to the macrocells of the macrocell set is acquired by the following steps. Programmable input and output circuits used in the macrocells of the macrocell set are identified, and the occurrences of the identified input and output circuits are omitted. A third set of files corresponding to the identified input and output circuits is acquired. Then, the circuit level netlist of the customer option is constructed from the logic netlist and the first, second and third sets of files.

In the drawings, where like reference numerals indicate like parts,

FIG. 1 is a flow diagram showing process flow and data flow for a prior art integrated circuit design, layout and connectivity checking sequence;

FIG. 2 is a flow diagram showing process flow and data flow for a connectivity checking sequence in accordance with the present invention;

FIG. 3 is a logic symbol for a 5-input, 2-output OR gate;

FIG. 4 is a circuit schematic of the OR gate of FIG. 3;

FIG. 5 is a partitioned circuit level netlist of the OR gate of FIG. 4;

FIG. 6 is a partitioned circuit level netlist of a variation of the OR gate of FIG. 4;

FIGS. 7A-7K are sets of base skeleton files and I/O skeleton files derived from two power levels of the OR gate of FIG. 3;

FIGS. 8A-8F sets of subcircuit files used in the MDL netlists of FIGS. 5 and 6;

FIG. 9 is a flow chart of a computer program for generating a skeleton file library;

FIGS. 10-26 include examples of base skeleton files and I/O skeleton files, as well as of the MDL netlists from which they were derived;

FIGS. 27A-27C are flow diagrams of a computer program for generating a circuit level netlist from a skeleton file library and a subcircuit library, and

FIGS. 28-29 are flow diagrams of two different computer programs for performing the comparison step of FIG. 2; and

FIGS. 30A-30F are listings of program EDTEXT.TXT.

As shown in FIG. 2, a netlist generation step 32 results in a circuit level netlist file 36 for the entire customer option. A number of conventionally generated files are used in producing the circuit level netlist 36, including the logic netlist 12, the bias driver identification file 18, the I/O macro pulldown resistor definition file 19, and the pad - I/O signal relationship file 20. Two unique file libraries also are used in generating the circuit level netlist 36, viz. a skeleton file library 34 and a subcircuit library 36. The contents and derivation of the skeleton file library 34 and the subcircuit library 36 are discussed below. A physical connectivity check is performed automatically in step 38, in which the circuit level netlist 36 is compared with the physical data base 24. The results of the comparison step 38 is a verification of the physical connectivity of the physical data base 24 for the customer option.

The skeleton file library 34 includes base skeleton files and input/output ("I/O") skeleton files. The base skeleton files correspond to the various types of macrocells that can be obtained from the macrocell library 2 and the overlay library 4. A macrocell "type" is considered to be a macrocell defined by logic function and power. Each base skeleton file contains only those netlist elements that are "fundamental" to the macrocell; the concept of "fundamental" is explained below. The netlist elements of the base skeleton files are components, including standard components and high level components. The I/O skeleton files correspond to the various types of input and output circuits that are "programmable" by the designer, meaning that the designer determines whether such I/O circuits are included in a macrocell instance. The netlist elements of the I/O skeleton files are components, including standard and high level components.

To derive the skeleton file library 34, the circuit schematics of the macrocells in the macrocell library of interest are studied with the objective of defining the macrocells as combinations of standard components and high level components. Standard components include individual resistors and transistors. High level components are subcircuits common to at least some of the macrocell types. The objective in defining high level components is to achieve a balance between minimizing the number of components in each base skeleton file, while maximizing the instances of high level components across the skeleton file library 34. Within these criteria, discretion exists in defining the high level components.

The subcircuits corresponding to the high level components are collected into a set. This set becomes the subcircuit library 36.

Once the high level components are identified, a circuit level netlist file defining each type of macrocell is created in a suitable language such as the MDL ("Master Data Language") language. This circuit level netlist file includes standard component symbology and, as appropriate, high level component symbology. The netlists defining the various types of macrocells are created in a "partitioned" form. Partitioned form means that each netlist is expressed in as many high level components as possible, with standard components being used only when no high level components are suitable for replacing them. This part of the netlist is known as the "redefined" macro. Definitions for the high level components are included in the netlist, following the redefined macro.

The redefined macros then are distilled to respective base skeleton files for each type of macrocell. Each base skeleton file contains only those components that will be consistently present in every instance of the macrocell type in the customer options, regardless of the number of programmable inputs and outputs and regardless of the manner of interconnection. Accordingly, the distillation of an redefined macro to form a base skeleton file involves deleting the programmable I/O circuit definitions.

The programmable I/O circuit definitions are not lost, however. Purged of redundant definitions, they collectively form a set of I/O skeleton files which are included in the skeleton library 34.

To better understand the process for forming the skeleton library 34, consider as an example a 5-input, 2-output OR gate shown in logic symbology in FIG. 3. The circuit schematic diagram for a low power version 39 of the OR gate is shown in FIG. 4. An OR gate can be defined as having a current switch with programmable inputs and outputs, existing in various power configurations. Specifically, the low power OR gate 39 includes a low power current switch 46, five inputs 41-45, and a low power output stage 48 with two outputs. Two high level components are present in the low power current switch 46: a load resistor 50 and a current source 52. It will be appreciated that load resistors and current sources are frequently present in ECL circuits (although generally not connected together), and that by defining these as high level components, the complexity of the netlists representing the ECL circuits in which they are found is considerably reduced. Two nodes are identified, node 54 and node 56. The switching transistor 40 is a standard component. The inputs to the current switch 46 are five standard components, viz. the NPN transistors 41-45. Two high level components are present in the output stage: emitter followers with respective outputs Z and ZL.

Having identified the high level components, one now generates a partitioned netlist file in a suitable language such as the MDL language. A partitioned MDL circuit level netlist file OR05DL.MDL for OR gate 39 is shown in FIG. 5. The MDL commands are created either by directly writing the MDL code, or by converting the circuit schematic of FIG. 4 with a suitable software system such as the MDL generator available from Silvar-Lisco, Inc. If the conversion is performed automatically, the high level components initially are defined to the software system, which then partitions the netlist accordingly.

Various structures of the MDL netlist of FIG. 5 are identifiable. The redefined macro includes fundamental components 40, 50, and 52 and nodes 54 and 56, which correspond to #RQNPN.sub.-- 1 (switching transistor, NPN type), #IRLH.sub.-- 1 (low power load resistor), #IQCSH.sub.-- 1 (low power current source), $NET1 (net) and $NET2 (net) respectively in the OR05DL macro MDL file of FIG. 5. The programmable inputs to the current switch 46 are the five standard components 41-45, which receive inputs A1-A5 respectively and correspond to NPN transistors #QNPN.sub.-- 2, #QNPN.sub.-- 5, #QNPN.sub.-- 4, #QNPN.sub.-- 3, and #QNPN.sub.-- 1 respectively in the OR05DL macro MDL file of FIG. 5. It should be noted that inputs not used merely are excluded from the circuit schematic netlist file, which physically corresponds to maintaining certain switching transistors unconnected in the physical data base 24. The programmable outputs of the current switch 46 are the two high level components 60 and 62, which correspond to output emitter followers #IQOEFL.sub.-- 1 and #IQOEFL.sub. -- 2 respectively in the OR05DL macro MDL file of FIG. 5.

Subcircuits are identifiable. The high level load resistor 50 is defined by subcircuit 51. The high level current source 52 is defined by subcircuit 53. Note that the power of the current switch 46 is controlled by the values of the load resistor 50 and the current source 52. The high level components 60 and 62 are defined by subcircuit 61. Pulldown resistors 64 and 66 are represented by "RBASE E1 $NET1," where E1 is the emitter of transistor 68 and $NET1 is the net defined for the resistor-to-resistor node in the emitter follower IQOEFH of FIG. 6. Pulldown resistors 65 and 67 are represented by "RBASE $NET1 E." Note that the power of the emitter followers 60 and 62 is determined by the value of the pulldown resistors 64-67 and the number of output transistors 68 and 69.

To better understand how various power options influence the derivation of the skeleton library 34 and subcircuit library 36, consider the partitioned MDL netlist OR05DH.MDL of FIG. 6 for a high power version of the 5-input, 2-output power OR gate of FIG. 3. The circuit from which FIG. 6 is derived includes a high power current switch, five inputs, and a high power output stage having two emitter followers with respective outputs.

Various structures of the MDL netlist of FIG. 6 are identifiable. The redefined macro includes fundamental components 70, 76, and 82 and two circuit nodes, which correspond to RQNPN.sub.-- 1 (switching transistor, NPN type), IRLHH.sub.-- 1 (high power load resistor), IQCSHH.sub.-- 1 (high power current source), $NET1 (net) and $NET2 (net). The programmable inputs to the current switch are the five standard components 71-75, which receive inputs A1-A5 respectively and correspond to NPN transistors #QNPN.sub.-- 2, #QNPN.sub.-- 5, #QNPN.sub.-- 4, #QNPN.sub.-- 3, and #QNPN.sub.-- 1 respectively in the OR05DL macro MDL file of FIG. 6. It should be noted that inputs not used merely are excluded from the circuit schematic netlist file, which physically corresponds to maintaining certain switching transistors unconnected in the physical database 24. The programmable outputs of the current switch are the two high level components 78 and 80, which correspond to output emitter followers IQOEFH.sub.-- 1 and IQOEFH.sub.-- 2 respectively in the OR05DH macro MDL file of FIG. 6.

Subcircuits are identifiable. The high level high power load resistor 76 is defined by subcircuit 77, which is two resistors in parallel. The high level high power current source 82 is defined by subcircuit 83, which are two parallel resistors and two parallel transistors. Note that the power of the current switch is controlled by the values of the load resistor 76 and the current source 82. The high level high power emitter followers 78 and 80 are defined by subcircuit 79. A pulldown resistor is represented by "RBASE E1 E" and an output transistor is represented by "QNPN C B E1." Note that the power of the emitter followers 78 and 80 is determined by the value of the pulldown resistors and the number of output transistors.

Where high and low MDL netlists exist for a given logic type, care must be taken to name all interconnect nets associated with the I/O pins consistently. The reason for this is to ensure that all power level current switches correctly interface with all power level output emitter followers. Generally, four power combinations of base power and output power are available: high base power with high output power, high base power with low output power, low base power with high output power, and low base power with low output power. To avoid net naming errors, the net names must be identical between the high and low power skeleton files. For example, in the MDL netlists for macros OR05DL and OR05DH of FIGS. 5 and 6, $NET2 consistently represents the interface point between the current switch and the at least one output emitter follower present in the low and high power OR gates.

The base circuit skeleton files obtained from the low and high power versions of the OR gate of FIG. 3 are shown in FIG. 7, and the subcircuit files corresponding to the low and high power versions of the OR gate of FIG. 3 are shown in FIG. 8. These files can be prepared manually or automatically. A computer program for preparing these files automatically on a workstation or general purpose computer is listed in Parts 19 and 20 of the Appendix, and illustrated in FIG. 9.

Initially, the desired high power MDL and low power MDL macrocell netlists are collected. All of the collected netlists must have zero NCC errors, with false errors having been eliminated by the inclusion of components in the MDL netlist that reflect a one-to-one correspondence to all components in the layout of the macros.

The collected netlists are processed by program SKELSM.C;3, which is listed in Part 19 of the Appendix. Program SKELSM.C;3 performs five operations on the collected MDL netlists, as illustrated in FIG. 9. In step 100, the variable `NETWORK` is changed to `DEFINE` in the MDL netlists. In step 102, the `&` character at the end of the output statement `O` is deleted from the MDL netlists. In step 104, the power supply statement `S` is deleted from the MDL netlists. In step 106, variable `VCC` is substituted for the variables `VCC01,` `VCC02,` `VCC03,` `AND `VCCA` in the MDL netlists. In step 108, the redefined macro is isolated by deleting all lines of each MDL netlist after the first `ENDMACRO` statement encountered in the file. Initial low power and high power skeleton files 110 result.

It will be appreciated that the lines deleted from the MDL netlists contain subcircuit information. The subcircuit information exists separately without redundancy in the subcircuit library 36. The subcircuits used in the low power and high power configurations of the OR gate of FIG. 3 are IRLH, IRLHH, IQCSH, IQCSHH, IQOEFL, and IQOEFH, which are shown in FIG. 8.

Next, program SKELGEN.C;6, which is listed in Part 20 of the Appendix, is used to produce the skeleton library 34. The input files to program SKELGEN.C;6 are the initial skeleton files 110 and file `MACRO`.OVR (112), which contains a list of the programmable input and output pin names. File `MACRO`.OVR is generated by the program PSON.PAS;21 from the ASCII file produced by the SCALD system of Valid Logic Systems, Inc. after execution of the LED program. The program listing for PSON.PAS;21 is given in Part 21 of the Appendix. The program SKELGEN.C;6 executes steps 114, 116, 118, and 120 leading to the generation of the skeleton file library 34. Under some circumstances, an additional step 122 is performed manually, although it could be automated if desired.

In step 114, the programmable inputs and outputs are extracted from each redefined macro based on the pin names contained in file `MACRO.`OVR. The netlists remaining after extraction are the base skeleton files. For example, the base skeleton files for the low and high power configurations of the OR gate of FIG. 3 are OR05DL.LSK and OR05DL.HSK, which are shown in FIGS. 7A and 7B respectively. The base skeleton netlist file for OR05DL includes the MDL expression of switching transistor 40 (#RQNPN.sub.-- 1), low power load resistor 50 (#IRLH.sub.-- 1), and low power current source 52 (IQCSH.sub.-- 1). The base skeleton netlist file for OR05DH includes the MDL expression of switching transistor 70 (#RQNPN.sub.-- 1), high power load resistor 76 (#IRLHH.sub.-- 1), and high power current source 82 (IQCSHH.sub.-- 1).

The I/O skeleton files for the low and high power configurations of the OR gate of FIG. 3 are obtained from the extracted I/O files. These are shown in FIGS. 7C-7K, and are respectively OR05D.LA5 and OR05D.HA5 (transistors 45 and 75), OR05D.LA1 and OR05D.HA1 (transistors 41 and 71), OR05D.LA4 and OR05D.HA4 (transistors 44 and 74), OR05D.LA3 and OR05D.HA3 (transistors 43 and 73), OR05D.LA2 and OR05D.HA2 (transistors 42 and 72), OR05D.LZ (output emitter follower 60), OR05D.LZL (output emitter follower 62), OR05D.HZ (output emitter follower 80), and OR05D.HZL (output emitter follower 78).

A certain file naming convention is used for the skeleton files. The high power base skeleton file is known as "macroname.HSK," and the low power base skeleton file is known as "macroname.LSK." For naming the output skeleton files, the conventions "macroname.HXX" and "macroname.LXX" are used, where "XX" is the name of the programmable output. For naming the input skeleton files, the conventions "macroname.HYY" and "macroname.LYY" are used, where "YY" is the name of the programmable input.

The program required dummy (blank) files for any non-programmable inputs and outputs. These are inputs and outputs which the option designer is not permitted to specify. Dummy files for non-programmable I/O pins are assigned names in step 116, in accordance with the previously described naming convention.

Where high and low MDL netlists exist for a given logic type, care must be taken to name all interconnect nets associated with the I/O pins consistently. The reason for this is explained above. As is apparent, $NET2 is consistently used in files OR05DL.MDL and OR05DH.MDL of FIGS. 5 and 6.

Some of the redefined macros may have hardwired outputs. Not all of the hardwired outputs of a redefined macro may be used by the option designer, however. Accordingly, two sets of skeleton files are used for the hardwired outputs of an redefined macro. For the first set, the I/O skeleton files `macroname`.HXX and the `macroname`.LXX files are generated as discussed above. In addition, a second set of files named in accordance with the convention `macroname`.NHXX and `macroname`.NLXX are created. This set is identical to the first set, except that the hardwired output names are preceded by the `$` character. This set is needed because unused hardwired output names in the MDL netlist must be preceded with the `$` character.

The input I/O macros are processed in step 118 by extracting their output pins in accordance with the naming convention for extracted I/O files discussed above. Since I/O macros are hardwired, a second set of extracted files is created. The filename is preceded with the `$` symbol if a pin is not designated for use. The naming convention for these files is `macro`.NPinname. Notice that the power is replaced by an `N`.

The output I/O macros are processed in step 120 by extracting their input pins in accordance with the naming convention for extracted I/O files discussed above. Since I/O macros are hardwired, a second set of extracted files is created. The filename is preceded with the `$` symbol if a pin is not designated for use. The naming convention for these files is `macro`.NPinname. Notice that the power is replaced by an `N`.

The program SKELGEN.C;6 is not suitable for processing bidirectional output pins, so that the skeleton files for a macrocell having a bidirectional output pin is modified manually in step 122. For example, consider FZ and Z as the output pins of a transmitter. FZ is the bidirectional pin. Pin Z is connected by an internal net. Z must be moved to the input section `I(. . . Z)` and files `macro`.HZ and `macro`.NZ are created.

To further illustrate the methodology explained above, the MDL netlists and the skeleton files derived therefrom for a representative sample off logic elements from the FGA series macro library for ASPECT gate arrays of National Semiconductor Corporation are shown in FIGS. 10-26. While the derivation of these skeleton files from their respective MDL netlists is generally apparent in view of the prior discussion, a few additional aspects of the methodology emerge from this representative sample.

FIGS. 10, 11, and 12 show respectively a logic representation, a low power MDL netlist, and a high power MDL netlist for a 2-input AND/NAND gate type ANIO2, available from National Semiconductor Corporation. The skeleton files obtained from the MDL netlists of FIGS. 11 and 12 are shown in FIG. 13. Note, for example, the presence of dummy files ANIO2.HA;1, ANIO2.HB;1, ANIO2.LA;1 and ANIO2.LB;1, which represent non-programmable inputs A and B.

FIGS. 14, 15, and 16 show respectively a logic representation, a low power MDL netlist, and a high power MDL netlist for a 4:1 multiplexer with enable type MXI04, available from National Semiconductor Corporation. Note two new high level components in FIG. 15C: component IRLL (reference numeral 130), which is a low power load resistor configuration; and component IQDIFF, which consists of two transistors and provides four inputs (two bases and two collectors) and one output (tied emitters). The skeleton files obtained from the MDL netlists of FIGS. 15 and 16 are shown in FIG. 17. Note, for example, the presence of dummy files MXIO4.HI0, MXIO4.HI1, MXIO4.HI2, MXIO4.HI3, MXIO4.HS0, and MXIO4.HS1.

FIGS. 18 and 19 show respectively a logic representation and a high power MDL netlist for a 2-input OR gate type OR250X2, available from National Semiconductor Corporation. Note a new high level components in FIG. 19B: component 5DIO (reference numeral 134), which is a temperature compensation component consisting of two diodes and a resistor. Note that while four diodes are shown as part of component 134, in fact two of the diodes are unconnected at one of their end terminals. The skeleton files obtained from the MDL netlist of FIG. 19 is shown in FIG. 20. Note the presence of two unused inputs OR250X2.NA1 and OR250X2.NA2.

FIGS. 21, 22 and 23 show respectively a logic representation, a low power MDL netlist, and a high power MDL netlist for a D type positive edge-triggered master/slave flip-flop type DF104, available from National Semiconductor Corporation. The skeleton files obtained from the MDL netlist of FIGS. 22 and 23 is shown in FIG. 24. Note the presence of dummy input files DFI04.HCP and DFI04.HD, and dummy output files DFI04.HQ and DFI04.HQN.

FIGS. 25 and 26 are examples of skeleton files of bias drivers for, respectively, a 4K array and a 14K array. Note that the skeleton files are the MDL netlists for these circuits. This is the normal convention for bias drivers.

In the netlist generation step 32, several files generated in the design and layout sequence 30, viz. the logic netlist file 12, the bias driver identification file 18, the I/O macro pulldown resistor file 19, and the pad-I/O signal relationship file 20, are used in conjunction with the skeleton library 34 and the subcircuit library 36 to create a circuit level netlist 36 for the entire customer option. Circuit level netlist 36 represents the exact utilization of every macrocell in the customer option.

One approach to implementing the circuit level netlist generator step 32 is on a workstation or general purpose computer using suitable software. The flow diagram of FIG. 27 illustrates the operation and general content of one such suitable software system, which is listed in Parts 1-8 and 10-18 of the Appendix. This program, or netlist generation system, is suitable for ASPECT FGA1.3K, FGA 4K, and FGA 14K customer options.

Steps 200 and 202 are obtaining the necessary files for the netlist generation. For the customer option, these are GENNET.LIS, the logic netlist file 12; DESIGN.BOV, the bias driver identification file 18; DESIGN.MVA, the I/O macro pulldown resistor file 19; and XXAUTOPIN.S50, the pad-I/O signal relationship file 20, which are obtained from the conventional design and layout sequence 30. The system resident files are the files of the skeleton library 34 (hereinafter "*.SK"); and the files of the subcircuit library (hereinafter "SUBCKT.MDL"). Libraries 34 and 36 are obtained as discussed above. File CHIP.DEF is obtained manually by coding the actual coordinates of every pad of the chip as measured from an actual array plot.

Step 204 is the creation of netlist generation system input files for the customer option. The files GENNET.LIS, DESIGN.BOV, DESIGN.MVA, and XXAUTOPIN.S50 simply are copied and renamed OPTION.sub.-- GENNET.LIS, OPTION.sub.-- DES.BOV, OPTION.MVA, and OPTION.sub.-- APIN.S50, where "OPTION" is the name of the customer option.

Steps 206 and 208 are executed by the program AUTOIO.C;52, which is listed in part 1 of the Appendix. In step 206, OPTION CHIP.IO files are generated. These files specify the external pin I/O signal names for the customer option. In step 208, the format of file OPTION APIN.S50 is modified; the character "-" is substituted for the character "/" in accordance with the signal name convention used in the netlist generation system.

Program GET.sub.-- TOKEN is a line parser that skips over blank Spaces and tab delimiters, and returns a valid token of a text line. Program MASKNAME masks out old I/O signal names from XXAUTOPIN.S50 with new I/O signal names. Program READS50 generates a new $50 file with correct signal names.

Programs GET.sub.-- TOKEN (Part 7 of the Appendix), MASKNAME (Part 8 of the Appendix), and READS50 (Part 18 of the Appendix) are sub-programs called by program AUTOIO as needed.

Step 210 is executed by the program DEFGEN (Part 2 of the Appendix), which generates the text file OPTION.DEF specifying the physical coordinate of each I/O signal and power pad in the customer option. This information is used in appending the I/O signal names to their respective pads in the physical data base of the customer option. The input files to program DEFGEN are OPTION.sub.-- CHIP.IO, OPTION.sub.-- APIN.S50, CHIP.DEF, and the skeleton library files 34.

Step 212 is executed by the program FIXGENNET (Part 3 of the Appendix), which creates an output file OPTION.sub.-- GEN.LIS that is similar to file OPTION.sub.-- GENNET.LIS modified by extracting two specific macro types that are not relevant to the netlist generating step 32. These macro types, IN00X2/3 and OUT00X2/3, physically represent only a piece of metal layer. The input files to program FIXGENNET are OPTION.sub.-- CHIP.IO, OPTION.sub.-- GENNET.LIS, and the skeleton library files 34.

Step 214 is executed by the program NEWGENNET. Note that a different NEWGENNET program is used for each type of array, although the functions performed by the programs are identical. Programs NEWGENNET.sub.-- 4K, NEWGENNET.sub.-- 13K, NEWGENNET.sub.-- 14K, and NEWGENNET.sub.-- 14KRAM are used for 4K arrays, 1.3K arrays, 14K arrays, and 14K arrays with RAM respectively, and are listed in Parts 14, 15, 16 and 17 respectively of the Appendix. Program NEWGENNET generates a complete logic netlist of the customer option suitable for the circuit level netlist generating system by adding the I/O connectivity netlist information and the bias driver connectivity information for the customer option to the file OPTION.sub.-- GEN.LIS. The input files to program NEWGENNET are OPTION.sub.-- GEN.LIS, OPTION.sub.-- CHIP.IO, OPTION.sub.-- DES.BOV, and the skeleton library files 34.

Step 216 is executed by program GENBIO (Part 4 of the Appendix), which defines for each macro instance the names of the utilized inputs, the names of the utilized outputs, the base power of the macro instance, the output power of each of the utilized outputs, and the names of the inputs and outputs that are not utilized. This information is stored in file OPTION.sub.-- INST.DAT. Another output file called OPTION.sub.-- LAY.BOV containing external slave bias identification and overlay utilization information is generated also. The input files to the program GENBIO are OPTION.sub.-- NGEN.LIS and the skeleton library files 34.

Step 218 is executed by program GENMDL. Note that a different GENMDL program is used for each type of array, although the functions performed by the programs are identical. Program GENMDL 4K is used for 4K and 1.3K arrays, while program GENMDL.14K is used for 14K arrays and 14K arrays with RAM. Programs GENMDL.sub.-- 4K AND GENMDL.sub.-- 14K are listed in Parts 5 and 6 respectively of the Appendix. Program GENMDL generates a MDL circuit level netlist for every macrocell instance in the customer option by providing the appropriate base skeleton file and appending the appropriate I/O skeleton files for each macrocell instance, as specified by the macrocell instance. These netlists are collected in file OPTION.sub.-- MAC.MDL. Program GENMDL also generates file OPTION.sub.-- IPIN.DAT containing I/O pin information suitable for determining the connectivity between the various macrocell instances in the customer option. The input files for program GENMDL are OPTION.sub.-- INST.DAT, OPTION.sub.-- NGEN.LIS, OPTION.sub.-- LAY.BOV and the skeleton library files 34.

Step 220 is executed by program MERGEMDL. Note that a different MERGEMDL program is used for each type of array, although the functions performed by the programs are identical. Programs MERGEMDL.sub.-- 4K, MERGEMDL.sub.-- 13K, MERGEMDL.sub.-- 14K, and MERGEMDL.sub.-- 14KRAM are used for 4K arrays, 1.3K arrays, 14K arrays, and 14K arrays with RAM respectively, and are listed in Parts 10, 11, 12 and 13 respectively of the Appendix. Program MERGEMDL completes the circuit level MDL netlist by adding connectivity information to the collection of MDL circuit level netlists for every macrocell instance in the customer option. A working file called OPTION.sub.-- INET.MDL specifying the signal connectivity between macro instances is created. The complete netlist, which now contains MDL netlists for each instance and specifies the connectivity between the various instances, is further supplemented by subcircuit MDL files, which are merely appended from file SUBCKT.MDL, the subcircuit library 36. The resulting file is OPTION.MDL. The input files for program MERGEMDL are OPTION.sub.-- IPIN.DAT, OPTION.sub.-- MAC.MDL, SUBCKT.MDL, and OPTION.sub.-- NGEN.LIS.

Step 222 completes a check on the file OPTION.MDL. An electrical rules check is performed to ensure that the connections are properly made, and a further check is made to ensure that no typographical or syntactical errors are present. Suitable software is available for executing step 222 on workstations or general purpose computers, and includes the ERC ("Electrical Rule Check") software system available from Silvar Lisco Inc.

In the comparison step 38, the circuit schematic netlist file 36 is compared against the physical database 24 to determine whether the physical connectivity of the overlay files agrees with the physical connectivity as dictated by the circuit level netlist 36. One approach to implementing the comparison step 38 is on a workstation or general purpose computer using a suitable software program. Suitable comparison software includes the "Layout versus Schematic" system (hereinafter "LVS (Trademark) system") available from Cadence Design Systems, Inc., and the "Network Consistency Check" system (hereinafter "NCC (Trademark) system") available from Silvar-Lisco Corporation of Santa Clara, Calif.

FIG. 28 illustrates the comparison step 38 when performed with the Network Consistency Check system. Several principal input files are used. The physical data base file 24 for the customer option is obtained in step 230. This file name is OPTION.CV, which is one of three file formats available from the design and layout sequence 30. The circuit level netlist 36 is obtained in step 232. File OPTION.MDL is the name of the circuit level netlist obtained as discussed above, and for the purposes of the comparison step 38 the file is copied and renamed CHIP.MDL. To enable the I/O signal names to be appended to their respective pads in the physical data base of the customer option, the text file OPTION.DEF specifying the physical coordinate of each I/O signal and power pad in the customer option is obtained in step 234. File OPTION.DEF is generated in step 210 by the program DEFGEN, as discussed above. The file OPTION.DEF is appended to the customer option physical data base file OPTION.CV in step 236 to form the file CHIPNCC.CV, which is the full physical data base file, including the I/O signal name text, for the customer option.

The physical data base for the customer option, as represented by file CHIPNCC.CV, is compared with the circuit netlist file for the entire customer option, as represented by file CHIP.MDL, in step 238. The comparison is performed by the NCC software, in accordance with procedures established by Silvar-Lisco Corporation and set forth in its manuals. The NCC software generates an intermediate file CHIPMDL.LIS, which is essentially the same as file CHIP.MDL except that it contains line numbers for the purpose of debugging. This intermediate file is useful for entering the NCC system at an intermediate point, provided that the full NCC system is run at least once, that other intermediate files from the NCC system are not tampered with, and that only the OPTION.MDL file is modified (files OPTION.CV and OPTION.DEF are original).

The files ERCERR.LIS and CHIPERR.LIS are generated in step 238. File ERCERR.LIS specifies if any power pads are shorted in the OPTION.CV file due to errors in the customer option or in the OPTION.DEF file. File CHIPERR.LIS is the error report specifying the discrepancies, if any, between the OPTION.MDL and the OPTION.CV files. Files ERCERR.LIS and CHIPERR.LIS are analyzed in accordance with the Electrical Rules Check Users Manual and the Network Consistency Check User Guide, which are available from Silvar-Lisco Corporation.

FIG. 29 illustrates the comparison step 38 when performed with the Layout versus Schematic system. Several principal input files are used. The physical database file 24 for the customer option is obtained in step 240. This file name is OPTION.GDS, one of three different formats available from the design and layout sequence 30. To enable the I/O signal names to be appended to their respective pads in the physical database of the customer option, the text file OPTION.DEF specifying the physical coordinate of each I/O signal and power pad in the customer option is obtained in step 242. File OPTION.DEF is generated in step 210 by the program DEFGEN, as discussed above.

As the circuit netlist file OPTION.MDL generated in step 220 is written in the MDL format, translation of the netlist file 36 from the MDL format to the CDL (Trademark) format recognized by Cadence Design Systems, Inc. software is performed in step 244. The program MDL2CDL.C listed in Part 9 of the Appendix is suitable for performing this conversion. Alsoin step 244, file OPTION.DEF is converted to file EDTEXT.TXT, using the program DEF2KTXT, which is listed in FIG. 30.

The physical database for the customer option, which is obtained from input files OPTION.GDS and EDTEXT.TXT, is compared with the circuit netlist file for the entire customer option, which is obtained from input file OPTION.CDL, in step 246. The comparison is performed by the LVS software, in accordance with procedures established by Cadence Design Systems, Inc. and set forth in its DRAFULA I & II User Manual. The output file OPTION.LVS is the error report specifying the discrepancies, if any, between the customer option and the circuit netlist generated for the option. File OPTION.LVS is analyzed in accordance with the DRACULA I & II User's Manual.

While our invention has been described with respect to the embodiments set forth above, other embodiments and variations not described herein are within the scope of our invention. For example, our invention should not be limited to any particular computer, file structure, or computer language. Accordingly, other embodiments and variations not described herein are to be considered within the scope of our invention as defined by the following claims.