US20130185687A1 - Parameterized cell layout generation guided by a design rule checker - Google Patents
Parameterized cell layout generation guided by a design rule checker Download PDFInfo
- Publication number
- US20130185687A1 US20130185687A1 US13/684,496 US201213684496A US2013185687A1 US 20130185687 A1 US20130185687 A1 US 20130185687A1 US 201213684496 A US201213684496 A US 201213684496A US 2013185687 A1 US2013185687 A1 US 2013185687A1
- Authority
- US
- United States
- Prior art keywords
- values
- design rule
- parameters
- violation
- layout
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G06F17/5081—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F30/00—Computer-aided design [CAD]
- G06F30/30—Circuit design
- G06F30/39—Circuit design at the physical level
- G06F30/398—Design verification or optimisation, e.g. using design rule check [DRC], layout versus schematics [LVS] or finite element methods [FEM]
Definitions
- the invention relates in general to a method for layout generation for an integrated circuits (IC), and more particular to a method for layout generation for a parameterized cell of an integrated circuit (IC) guided by design rule checking (DRC).
- IC integrated circuits
- DRC design rule checking
- PCells are design units which use parameter values to calculate IC layouts.
- An example is a PMOS PCell that takes channel width and channel length as parameters. After a user selecting the PMOS PCell and specifying values for the two parameters, a PMOS layout with the specified channel length and width is automatically generated and placed at the location indicated by the user.
- the generated layout satisfies all design rules that are typically described in a technology file which is set along with the definition of PCells initially.
- the generated PCell layout is free of design rule violations, which is also called “DRC clean”.
- PCell generators typically take a conservative approach, namely, using larger dimensions and spacing that can satisfy worst case scenarios. With this approach, the generated layouts are typically less than ideal.
- FIG. 1 is an example for prior art. It shows a MOS layout which a PCell generator may generate.
- the layout consists of polygon 100 on poly layer for the gate of the MOS transistor, polygon 102 on diffusion layer for the source and drain, polygons 104 and 114 on metal layer (metal 1) for source and drain connections, and polygons 106 , 108 , 110 and 112 on contact cut layer (metal 1 to poly cut layer) for metal to diffusion connections.
- Dimensions and locations of the polygons in FIG. 1 may be determined in one of the following ways:
- the horizontal span of polygon 100 is the value of the channel length parameter specified by the user.
- the vertical span of polygon 100 is the sum of channel width parameter value specified by the user plus twice of the minimum value of extension of poly over diff, which is specified in the technology file.
- enclosures 120 and 122 are metal over contact minimum required values, and are specified in the technology file.
- enclosure 120 and enclosure 122 may depend on the dimensions of polygon 104 , dimensions of polygon 114 , the distance between 104 and 114 , and the parallel run length between 104 and 114 . In other words, in order to calculate the optimal values for 120 and 122 , we need to know the dimensions of 104 , 114 , the distance in between, and the parallel run length between 104 and 114 .
- PCell layouts are generated in a sequential manner.
- polygons 100 , 102 and 104 may be generated first; then polygons 106 and 108 are generated.
- the values for metal to contact enclosures will decide where and how many the contact polygons (e.g. polygons 106 , 108 ) are to be generated.
- the value is a function of the dimensions of metals 104 and 114 , the distance in between, and the parallel run length between 104 and 114 .
- polygon 114 is not generated yet, and so its location and dimensions are not known.
- One object of the present invention is to generate a layout for a cell of an integrated circuit (IC) guided by design rule checking (DRC).
- IC integrated circuit
- DRC design rule checking
- a model is defined, wherein the model comprises a plurality of parameters for generating a layout of the cell.
- an initial layout for the cell can be generated according to an initial set of values for the plurality of parameters.
- design rule checking is performed for the initial layout based on a set of design rules. If any violations are found, the corresponding violation reports will be applied to the model.
- a violation report typically contains information such as the name of the design rule violated, the two edges on layout objects where the violation is detected, and the minimum desirable dimension needed to clear the violation, and etc.
- the model comprises associating each design rule with a set of properties to indicate the information of the design rule name, the category of the design rule, the corresponding components/shapes in the PCell related to the violation checking for the design rule.
- the properties will be included in DRC violation reports, and can be used to adjust the set of parameter values.
- the actions for parameter value adjusting disclosed above can be done by executing callback functions.
- callback function names may be specified in properties.
- FIG. 1 illustrates an example to explain how a layout for a PCell is generated in prior art
- FIG. 2 depicts the schematic flow diagram of the current invention
- FIG. 3 shows an example of how to fix the metal 1 to contact enclosure violation
- FIG. 4 shows an example of how to fix the metal spacing violation
- FIG. 5 illustrates a schematic flow diagram of one embodiment which contains the invocation of callback functions.
- FIG. 2 depicts the schematic flow diagram of the current invention for generating a layout for a parameterized cell (PCell) of an integrated circuit (IC).
- the model comprises a plurality of parameters for generating a set of geometry shapes to form the layout of the cell (step 210 ).
- the logics of DRC violation analysis and the corresponding parameter adjustment algorithms are grouped systematically, which will be explained later.
- an initial set of values for the plurality of parameters are assigned (step 220 ).
- an initial layout for the cell can be generated according to the initial set of values for the plurality of parameters (step 230 ).
- a design rule checker is invoked to perform DRC for the initial layout based on a set of design rules (step 240 ). If any violations are found (step 250 ), the corresponding violation reports will be applied to the model (step 270 ). A new set of values for the plurality of parameters will be generated by analyzing the violation reports collectively based on the model. With the new set of values for the plurality of parameters, step 230 ⁇ step 270 are repeated until no violation is found, which means a “DRC clean” layout is generated (step 260 ). In one embodiment, the iteration stops when a pre-defined number of iteration cycles is reached before all violations are resolved.
- violation reports may be in the form of special type objects that the DRC checker generates and stores in the database in which PCell layouts reside.
- violation reports may be in the form of external files that contain the descriptions for each design rule violation that the DRC checker detects, or any other forms.
- the model comprises associating each design rule with a set of properties.
- Each property indicates the information of the design rule name, the category of the design rule, the corresponding components/shapes in the PCell related to the violation checking for the design rule. Thus, when a violation is detected, the corresponding property is attached to the violation report.
- design rules can be categorized as “spacing” rules, “width” rules and “enclosure” rules. Spacing rules control the minimum distance required between two adjacent shapes; width rules control the minimum width a shape can take; and enclosure rules control the extent a shape has to cover over another shape underneath it.
- MOS transistor As for the components/shapes in PCell, taking MOS transistor as an example, it may have “gate”, “source-drain” and “contact” components. Moreover, contacts may consist of “source-drain contact cut” and “metal over source-drain contact cut”. We can name each category of shapes by combining their functionality with its layer name.
- gate components may be referred to as “GatePoly”
- source-drain may be referred to as “ActiveOD” (source-drain are the “active” regions of the transistor and the layer that defines the source-drain area is usually called the OD layer)
- source-drain contact cut may be referred to as “ActiveContact” (for contact cuts over active regions)
- metal over source-drain contact cut may be referred to as “ActiveMetal”.
- rule-name ⁇ rule-category ⁇ device-type shape-category . . . ⁇
- rule name is “M1CO.EN.1” (metal on contact enclosure rule 1. Actual rule names should come from the process technology used); the rule category is “enclosure”; the device type is “XTR” (transistor type PCell); and the two objects involved are of type “ActiveMetal” and “ActiveContact”.
- rule name is “M1.S.1” (metal spacing rule 1); the rule category is “spacing”; the device type is “XTR”; and the two objects involved are both of type “ActiveMetal”.
- the two metal objects are for the connections to source and drain contacts, respectively.
- properties may be specified in a property file.
- current invention reads the design rules from a technology file and properties from a property file. It combines the two files and prepares an input rule deck in a format that the DRC checker supports. Then, it feeds the generated rule deck to the DRC checker.
- FIG. 3 shows an example of how to fix the metal 1 to contact enclosure. To begin with, we may define the property as follows:
- FIG. 4 shows an example of how to fix the metal spacing ( 401 ).
- the active region i.e. source-drain region
- ODlength ( 402 ) determines the length of the OD region on the right-hand side
- contactMetalOriginY determines the location of the contact metal object.
- ODlength ( 402 ) may or may not need fixing. If we have to use the same contact, then ODlength ( 402 ) has to be incremented by the same amount as the displacement of contactMetalOrigin ( 403 ). On the other hand, if we can create a “narrower” contact based on the new location of contactMetalOrigin ( 403 ) and original value of ODlength ( 402 ), then we can leave ODlength ( 402 ) unchanged.
- FIG. 5 illustrates a schematic flow diagram of one embodiment which contains the invocation of callback functions after DRC checking. Most of the steps have been shown in FIG. 2 .
- callback functions are executed in order to apply the DRC violation reports to the model for generating a new set of values for the plurality of parameters.
- callback function names may be specified in properties as shown in below examples:
- each DRC violation report we can find the callback function name, and call the function accordingly.
- the callback function we can pass the DRC violation report object to it.
- the callback functions can decide what parameters to adjust and by how much.
- the shapes when there are multiple objects under the same shape category, we can tag the shapes with unique identifiers so that we can know which specific shape or shapes the violation is pertaining to. For example, when there are multiple fingers (number of poly gate is greater than 1) on a transistor, there will be more than 2 source-drain regions.
- new entries can be added systematically to the property specification file for the new rules and new callback functions should be implemented accordingly.
Abstract
Description
- This application claims the benefit of priority of U.S. Provisional Application No. 61/585,650, filed Jan. 12, 2012, and titled “Parameterized Cell Layout Generation Guided by a Design Rule Checker”, the contents of which are herein incorporated by reference in its entirety.
- 1. Field of the Invention
- The invention relates in general to a method for layout generation for an integrated circuits (IC), and more particular to a method for layout generation for a parameterized cell of an integrated circuit (IC) guided by design rule checking (DRC).
- 2. Description of the Prior Art
- Analog circuit designers typically use parameterized cells (PCells) as building blocks to design analog ICs. PCells are design units which use parameter values to calculate IC layouts. An example is a PMOS PCell that takes channel width and channel length as parameters. After a user selecting the PMOS PCell and specifying values for the two parameters, a PMOS layout with the specified channel length and width is automatically generated and placed at the location indicated by the user. In addition, the generated layout satisfies all design rules that are typically described in a technology file which is set along with the definition of PCells initially. Thus, the generated PCell layout is free of design rule violations, which is also called “DRC clean”.
- As process technology advances, new design rules become so complex that it's very difficult, if not impossible, to generate optimal layouts for PCells that are also DRC clean. The reason is that for many complex design rules, the PCell generator has to estimate the positions and dimensions of some geometry shapes that are yet to be generated. Often times, there is a deviation between the estimate and the actual numbers. So, to play safe,
- PCell generators typically take a conservative approach, namely, using larger dimensions and spacing that can satisfy worst case scenarios. With this approach, the generated layouts are typically less than ideal.
-
FIG. 1 is an example for prior art. It shows a MOS layout which a PCell generator may generate. The layout consists ofpolygon 100 on poly layer for the gate of the MOS transistor,polygon 102 on diffusion layer for the source and drain,polygons polygons FIG. 1 may be determined in one of the following ways: - 1. They may be specified directly by the user. For example, the horizontal span of
polygon 100 is the value of the channel length parameter specified by the user. - 2. They may be determined by user specified values and design rule values specified in the associated technology file. For example, the vertical span of
polygon 100 is the sum of channel width parameter value specified by the user plus twice of the minimum value of extension of poly over diff, which is specified in the technology file. - 3. They may be determined by specifications in the technology file. For example,
enclosures - As process technologies advance, design rules become more and more complex. Design rule values, such as metal over contact enclosures, are no longer simple constant values. Let's take
enclosure 120 andenclosure 122 inFIG. 1 as an example. For advanced design rules,enclosures polygon 104, dimensions ofpolygon 114, the distance between 104 and 114, and the parallel run length between 104 and 114. In other words, in order to calculate the optimal values for 120 and 122, we need to know the dimensions of 104, 114, the distance in between, and the parallel run length between 104 and 114. - Typically, PCell layouts are generated in a sequential manner. In
FIG. 1 for example,polygons polygons e.g. polygons 106, 108) are to be generated. For complex enclosure rules, the value is a function of the dimensions ofmetals polygon 114 is not generated yet, and so its location and dimensions are not known. In order to calculate the values for 120 and 122, we have to estimate the dimensions and the location forpolygon 114. Later, whenpolygon 114 is generated, if it comes out as exact as previously estimated, then everything is good. More often than not, the actual dimensions and location for 114 are different from original estimation, and a DRC violation may occur. To fix the DRC violation, we will need to go back to re-calculate the values for 120 and 122 with a better estimation forpolygon 114, and re-generate portions of the layout. The new result may be all correct, or may be not. If it's not correct, the same steps will have to repeat once more. This makes the layout generation complicated. - Besides the example for enclosure issue shown above, there may be many other advanced design rules that have to be taken care of. Each design rule posts a different challenge and has to be satisfied in the final layout.
- Therefore, what is needed is a systematic way to efficiently and effectively generate layouts that satisfy all the advanced design rules while not relying on the estimation of layout components that are yet to be generated.
- One object of the present invention is to generate a layout for a cell of an integrated circuit (IC) guided by design rule checking (DRC).
- In one embodiment of the present invention, a model is defined, wherein the model comprises a plurality of parameters for generating a layout of the cell. Next an initial layout for the cell can be generated according to an initial set of values for the plurality of parameters. Then design rule checking (DRC) is performed for the initial layout based on a set of design rules. If any violations are found, the corresponding violation reports will be applied to the model. A violation report typically contains information such as the name of the design rule violated, the two edges on layout objects where the violation is detected, and the minimum desirable dimension needed to clear the violation, and etc. By analyzing these pieces of information in violation reports and applying the analysis results to the model, a new set of values for the plurality of parameters can be generated. With the new set of values for the plurality of parameters and above steps repeated until no violation is found, a “DRC clean” layout can be generated.
- In one embodiment, the model comprises associating each design rule with a set of properties to indicate the information of the design rule name, the category of the design rule, the corresponding components/shapes in the PCell related to the violation checking for the design rule. The properties will be included in DRC violation reports, and can be used to adjust the set of parameter values.
- In one embodiment, the actions for parameter value adjusting disclosed above can be done by executing callback functions. Furthermore, callback function names may be specified in properties.
- Other objects, technical contents, features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings wherein are set forth, by way of illustration and example, certain embodiments of the present invention.
- The foregoing aspects and many of the accompanying advantages of this invention will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
-
FIG. 1 illustrates an example to explain how a layout for a PCell is generated in prior art; -
FIG. 2 depicts the schematic flow diagram of the current invention; -
FIG. 3 shows an example of how to fix the metal 1 to contact enclosure violation; -
FIG. 4 shows an example of how to fix the metal spacing violation; and -
FIG. 5 illustrates a schematic flow diagram of one embodiment which contains the invocation of callback functions. - The detailed explanation of the present invention is described as following. The described preferred embodiments are presented for purposes of illustrations and description, and they are not intended to limit the scope of the present invention.
- Please refer to
FIG. 2 which depicts the schematic flow diagram of the current invention for generating a layout for a parameterized cell (PCell) of an integrated circuit (IC). Firstly, a model is defined, wherein the model comprises a plurality of parameters for generating a set of geometry shapes to form the layout of the cell (step 210). In the model, the logics of DRC violation analysis and the corresponding parameter adjustment algorithms are grouped systematically, which will be explained later. Next an initial set of values for the plurality of parameters are assigned (step 220). Thus an initial layout for the cell can be generated according to the initial set of values for the plurality of parameters (step 230). - Then, a design rule checker is invoked to perform DRC for the initial layout based on a set of design rules (step 240). If any violations are found (step 250), the corresponding violation reports will be applied to the model (step 270). A new set of values for the plurality of parameters will be generated by analyzing the violation reports collectively based on the model. With the new set of values for the plurality of parameters, step 230˜
step 270 are repeated until no violation is found, which means a “DRC clean” layout is generated (step 260). In one embodiment, the iteration stops when a pre-defined number of iteration cycles is reached before all violations are resolved. - In one embodiment, violation reports may be in the form of special type objects that the DRC checker generates and stores in the database in which PCell layouts reside. In another embodiment, violation reports may be in the form of external files that contain the descriptions for each design rule violation that the DRC checker detects, or any other forms.
- In one embodiment, the model comprises associating each design rule with a set of properties. Each property indicates the information of the design rule name, the category of the design rule, the corresponding components/shapes in the PCell related to the violation checking for the design rule. Thus, when a violation is detected, the corresponding property is attached to the violation report.
- To depict more details about the properties, in one embodiment, design rules can be categorized as “spacing” rules, “width” rules and “enclosure” rules. Spacing rules control the minimum distance required between two adjacent shapes; width rules control the minimum width a shape can take; and enclosure rules control the extent a shape has to cover over another shape underneath it.
- As for the components/shapes in PCell, taking MOS transistor as an example, it may have “gate”, “source-drain” and “contact” components. Moreover, contacts may consist of “source-drain contact cut” and “metal over source-drain contact cut”. We can name each category of shapes by combining their functionality with its layer name. For example, “gate” components may be referred to as “GatePoly”, “source-drain” may be referred to as “ActiveOD” (source-drain are the “active” regions of the transistor and the layer that defines the source-drain area is usually called the OD layer), “source-drain contact cut” may be referred to as “ActiveContact” (for contact cuts over active regions), and “metal over source-drain contact cut” may be referred to as “ActiveMetal”.
- Following is an exemplary format for design rule properties in accordance with the current invention:
-
{rule-name {rule-category {device-type shape-category . . . }}} - One property example is shown below:
-
{M1CO.EN.1 {enclosure {XTR ActiveMetal ActiveContact}}}. - It indicates that the rule name is “M1CO.EN.1” (metal on contact enclosure rule 1. Actual rule names should come from the process technology used); the rule category is “enclosure”; the device type is “XTR” (transistor type PCell); and the two objects involved are of type “ActiveMetal” and “ActiveContact”.
- Another property example is provided:
-
{M1.S.1 {spacing {XTR ActiveMetal ActiveMetal}}}. - It indicates that the rule name is “M1.S.1” (metal spacing rule 1); the rule category is “spacing”; the device type is “XTR”; and the two objects involved are both of type “ActiveMetal”. The two metal objects are for the connections to source and drain contacts, respectively.
- In one embodiment, properties may be specified in a property file. Upon invocation, current invention reads the design rules from a technology file and properties from a property file. It combines the two files and prepares an input rule deck in a format that the DRC checker supports. Then, it feeds the generated rule deck to the DRC checker.
-
FIG. 3 shows an example of how to fix the metal 1 to contact enclosure. To begin with, we may define the property as follows: -
{M1CO.EN.1 {enclosure {XTR ActiveMetal ActiveContact}}}. - When we get a violation report containing such a property, we know we have to enlarge the enclosure for the specified metal and contact objects. The locations of the two violating edges which can be found in the violation report can lead us to the metal shape object and the contact shape object. The value for the minimum required enclosure is also available in the violation report.
- Please refer to
FIG. 3 . To fix this DRC violation, two parameters EncX (301) and EncY (302) are defined for x-dimensional enclosure and y-dimensional enclosure respectively. Then parameter EncX (301) or parameter EncY (302) can be adjusted according to the minimum enclosure value. We can use the violation edges to decide if it's horizontal EncX (301) or vertical EncY (302) that is to be adjusted. If the two edges are horizontal edges, then it is EncY (302) that is to be adjusted. Otherwise, it's EncX (301). -
FIG. 4 shows an example of how to fix the metal spacing (401). We may define the property as follows: -
{M1.S.1 {spacing {XTR ActiveMetal ActiveMetal}}}. - When we get a violation report containing such a property, we know we have to enlarge the spacing between the two metal objects. This may affect the following two shapes:
- 1.The active region (i.e. source-drain region), and
- 2.The associated contact(s).
- To simplify the fix procedure, we limit the fix to the metal, which is on the “right-hand side”, i.e. moving the shapes having larger X coordinate in the layout, leaving shapes on the “left-hand side” unchanged. To further simplify the fix procedure, we introduce two auxiliary parameters: ODlength (402) and contactMetalOrigin (contactMetalOriginX, contactMetalOriginY) (403). The ODlength (402) value determines the length of the OD region on the right-hand side, and the contactMetalOrigin (403) determines the location of the contact metal object.
- To fix the metal spacing (401), we need to move the contactMetalOrigin (403) to the right. The amount can be readily calculated using the desired spacing value found in the violation report, and the current value in the layout. The other parameter, ODlength (402) may or may not need fixing. If we have to use the same contact, then ODlength (402) has to be incremented by the same amount as the displacement of contactMetalOrigin (403). On the other hand, if we can create a “narrower” contact based on the new location of contactMetalOrigin (403) and original value of ODlength (402), then we can leave ODlength (402) unchanged.
- After the contactMetalOrigin (403) and ODlength (402) are determined, we can re-generate the layout for the transistor. The metal 1 spacing violation should be cleared.
-
FIG. 5 illustrates a schematic flow diagram of one embodiment which contains the invocation of callback functions after DRC checking. Most of the steps have been shown inFIG. 2 . Instep 510, callback functions are executed in order to apply the DRC violation reports to the model for generating a new set of values for the plurality of parameters. - In one embodiment, callback function names may be specified in properties as shown in below examples:
-
{M1CO.EN.1 {enclosure {XTR ActiveMetal ActiveContact {FixContactMetalEnclsoureCB }}}}, -
and -
{M1.S.1 {spacing {XTR ActiveMetal ActiveMetal {FixActiveMetalSpacingCB}}}} - Then, in each DRC violation report, we can find the callback function name, and call the function accordingly. When calling a callback function, we can pass the DRC violation report object to it. Using the properties and attributes associated with the DRC violation report objects, the callback functions can decide what parameters to adjust and by how much.
- By grouping the decision making and parameter value adjusting in callback functions, the flow for layout generation for PCells with the help from a DRC checker becomes well organized.
- In one embodiment, when there are multiple objects under the same shape category, we can tag the shapes with unique identifiers so that we can know which specific shape or shapes the violation is pertaining to. For example, when there are multiple fingers (number of poly gate is greater than 1) on a transistor, there will be more than 2 source-drain regions.
- When a metal 1 spacing rule or metal 1 to OD enclosure rule is violated, we need to know which source-drain region or which pair of source-drain regions is the source of this violation. As disclosed above, by using the information in the violation report, we can find the shape object or objects that cause the violation. Then, by using the tags in the shape objects, we know which parameters to adjust to clear the violation. The same technique can be applied to tagging contact and metal objects.
- In one embodiment, to support new design rules, new entries can be added systematically to the property specification file for the new rules and new callback functions should be implemented accordingly.
- To support changes to existing design rules, we just have to modify the associated callback functions accordingly.
- The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustrations and description. They are not intended to be exclusive or to limit the invention to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to particular use contemplated. It is intended that the scope of the invention be defined by the Claims appended hereto and their equivalents.
Claims (7)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/684,496 US8869084B2 (en) | 2012-01-12 | 2012-11-24 | Parameterized cell layout generation guided by a design rule checker |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201261585650P | 2012-01-12 | 2012-01-12 | |
US13/684,496 US8869084B2 (en) | 2012-01-12 | 2012-11-24 | Parameterized cell layout generation guided by a design rule checker |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130185687A1 true US20130185687A1 (en) | 2013-07-18 |
US8869084B2 US8869084B2 (en) | 2014-10-21 |
Family
ID=48780890
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/684,496 Active US8869084B2 (en) | 2012-01-12 | 2012-11-24 | Parameterized cell layout generation guided by a design rule checker |
Country Status (1)
Country | Link |
---|---|
US (1) | US8869084B2 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105095535A (en) * | 2014-05-04 | 2015-11-25 | 中芯国际集成电路制造(上海)有限公司 | DRC verifying method for parameterized unit in software development kit |
US20160048629A1 (en) * | 2013-04-01 | 2016-02-18 | Freescale Semiconductor, inc.. | Automatic generation of test layouts for testing a design rule checking tool |
US9690898B2 (en) | 2015-06-25 | 2017-06-27 | Globalfoundries Inc. | Generative learning for realistic and ground rule clean hot spot synthesis |
CN106897536A (en) * | 2016-12-30 | 2017-06-27 | 北京华大九天软件有限公司 | A kind of method that parameterized units are abutted based on minimum design rule |
CN112949243A (en) * | 2021-03-12 | 2021-06-11 | 泉芯集成电路制造(济南)有限公司 | Parameter configuration method and device, computer equipment and storage medium |
WO2021118860A1 (en) * | 2019-12-09 | 2021-06-17 | Synopsys, Inc. | Electrical circuit design using cells with metal lines |
US11042806B1 (en) * | 2018-09-25 | 2021-06-22 | Synopsys, Inc. | Deep learning for fixability prediction of power/ground via DRC violations |
CN117371382A (en) * | 2023-10-24 | 2024-01-09 | 深圳市合芯数字科技有限公司 | Standard cell layout processing method, device and storage medium |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6245295B2 (en) * | 2016-03-15 | 2017-12-13 | 日本電気株式会社 | Integrated circuit, design method thereof, design apparatus, design program |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6009251A (en) * | 1997-09-30 | 1999-12-28 | Synopsys, Inc. | Method and system for layout verification of an integrated circuit design with reusable subdesigns |
US6862723B1 (en) * | 2002-10-03 | 2005-03-01 | Taiwan Semiconductor Manufacturing Company | Methodology of generating antenna effect models for library/IP in VLSI physical design |
US6915252B1 (en) * | 2000-01-11 | 2005-07-05 | Sun Microsystems, Inc. | Method and system for ensuring consistency of design rule application in a CAD environment |
US20050223347A1 (en) * | 2004-03-31 | 2005-10-06 | Elpida Memory, Inc. | Automatic LVS rule file generation apparatus, template for automatic LVS rule file generation, and method for automatic LVS rule file generation |
US7506277B1 (en) * | 2005-07-28 | 2009-03-17 | Cadence Design Systems, Inc. | Method and mechanism for implementing DFM aware cells for an electronic design |
US7810051B2 (en) * | 2006-01-11 | 2010-10-05 | Fujitsu Semiconductor Limited | Layout method, CAD apparatus, computer-readable program and computer-readable storage medium |
US8225263B2 (en) * | 2008-03-25 | 2012-07-17 | Nec Corporation | Method of semiconductor integrated circuit, recording medium recording design program of semiconductor integrated circuit, and design support apparatus of semiconductor integrated circuit |
-
2012
- 2012-11-24 US US13/684,496 patent/US8869084B2/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6009251A (en) * | 1997-09-30 | 1999-12-28 | Synopsys, Inc. | Method and system for layout verification of an integrated circuit design with reusable subdesigns |
US6915252B1 (en) * | 2000-01-11 | 2005-07-05 | Sun Microsystems, Inc. | Method and system for ensuring consistency of design rule application in a CAD environment |
US6862723B1 (en) * | 2002-10-03 | 2005-03-01 | Taiwan Semiconductor Manufacturing Company | Methodology of generating antenna effect models for library/IP in VLSI physical design |
US20050223347A1 (en) * | 2004-03-31 | 2005-10-06 | Elpida Memory, Inc. | Automatic LVS rule file generation apparatus, template for automatic LVS rule file generation, and method for automatic LVS rule file generation |
US7506277B1 (en) * | 2005-07-28 | 2009-03-17 | Cadence Design Systems, Inc. | Method and mechanism for implementing DFM aware cells for an electronic design |
US7810051B2 (en) * | 2006-01-11 | 2010-10-05 | Fujitsu Semiconductor Limited | Layout method, CAD apparatus, computer-readable program and computer-readable storage medium |
US8225263B2 (en) * | 2008-03-25 | 2012-07-17 | Nec Corporation | Method of semiconductor integrated circuit, recording medium recording design program of semiconductor integrated circuit, and design support apparatus of semiconductor integrated circuit |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160048629A1 (en) * | 2013-04-01 | 2016-02-18 | Freescale Semiconductor, inc.. | Automatic generation of test layouts for testing a design rule checking tool |
US9916412B2 (en) * | 2013-04-01 | 2018-03-13 | Nxp Usa, Inc. | Automatic generation of test layouts for testing a design rule checking tool |
CN105095535A (en) * | 2014-05-04 | 2015-11-25 | 中芯国际集成电路制造(上海)有限公司 | DRC verifying method for parameterized unit in software development kit |
US9690898B2 (en) | 2015-06-25 | 2017-06-27 | Globalfoundries Inc. | Generative learning for realistic and ground rule clean hot spot synthesis |
CN106897536A (en) * | 2016-12-30 | 2017-06-27 | 北京华大九天软件有限公司 | A kind of method that parameterized units are abutted based on minimum design rule |
CN106897536B (en) * | 2016-12-30 | 2020-02-18 | 北京华大九天软件有限公司 | Method for adjoining parameterized units based on minimum design rule |
US11042806B1 (en) * | 2018-09-25 | 2021-06-22 | Synopsys, Inc. | Deep learning for fixability prediction of power/ground via DRC violations |
WO2021118860A1 (en) * | 2019-12-09 | 2021-06-17 | Synopsys, Inc. | Electrical circuit design using cells with metal lines |
US11334705B2 (en) | 2019-12-09 | 2022-05-17 | Synopsys, Inc. | Electrical circuit design using cells with metal lines |
CN112949243A (en) * | 2021-03-12 | 2021-06-11 | 泉芯集成电路制造(济南)有限公司 | Parameter configuration method and device, computer equipment and storage medium |
CN117371382A (en) * | 2023-10-24 | 2024-01-09 | 深圳市合芯数字科技有限公司 | Standard cell layout processing method, device and storage medium |
Also Published As
Publication number | Publication date |
---|---|
US8869084B2 (en) | 2014-10-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8869084B2 (en) | Parameterized cell layout generation guided by a design rule checker | |
US8176445B1 (en) | Method and system for optimizing integrated circuit layout | |
US9852251B2 (en) | Manipulating parameterized cell devices in a custom layout design | |
US10860769B2 (en) | Method and system for integrated circuit design with on-chip variation and spatial correlation | |
CN102652316B (en) | Optical proximity correction aware integrated circuit design optimization | |
US7971174B1 (en) | Congestion aware pin optimizer | |
Dai et al. | DRC Plus: augmenting standard DRC with pattern matching on 2D geometries | |
US8914760B2 (en) | Electrical hotspot detection, analysis and correction | |
US20110061037A1 (en) | Generating Net Routing Constraints For Place And Route | |
US20150248514A1 (en) | Automatic layout modification tool with non-uniform grids | |
CN102368276A (en) | Flow method for automatically verifying correctness of electric rule file | |
US9454634B1 (en) | Methods, systems, and computer program product for an integrated circuit package design estimator | |
Livramento et al. | A hybrid technique for discrete gate sizing based on lagrangian relaxation | |
US10346579B2 (en) | Interactive routing of connections in circuit using auto welding and auto cloning | |
US7810051B2 (en) | Layout method, CAD apparatus, computer-readable program and computer-readable storage medium | |
Bairamkulov et al. | Power delivery exploration methodology based on constrained optimization | |
WO2013124703A1 (en) | Method and apparatus for performing integrated circuit layout verification | |
US10318685B2 (en) | Management of placement constraint regions in an electronic design automation (EDA) system | |
Mak et al. | Minimum implant area-aware placement and threshold voltage refinement | |
Reimann et al. | Cell selection for high-performance designs in an industrial design flow | |
US8789008B2 (en) | Methods for generating device layouts by combining an automated device layout generator with a script | |
JP2010134775A (en) | Method, program and apparatus for simulating circuit | |
CN110199279A (en) | IC design system | |
US8732638B1 (en) | Verifying proper representation of semiconductor device fingers | |
US7761824B2 (en) | System and method to generate an IC layout using simplified manufacturing rule |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SPRINGSOFT, INC., TAIWAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHUNG, CHIEN-FU;PEI, YUAN-KAI;TANG, SHYH-AN;REEL/FRAME:029344/0650 Effective date: 20121119 Owner name: SPRINGSOFT USA, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHUNG, CHIEN-FU;PEI, YUAN-KAI;TANG, SHYH-AN;REEL/FRAME:029344/0650 Effective date: 20121119 |
|
AS | Assignment |
Owner name: SYNOPSYS TAIWAN CO., LTD., TAIWAN Free format text: ACQUISITION;ASSIGNOR:SPRINGSOFT, INC.;REEL/FRAME:031719/0071 Effective date: 20121203 |
|
AS | Assignment |
Owner name: SYNOPSYS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SPRINGSOFT USA, INC.;REEL/FRAME:031680/0913 Effective date: 20130712 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: SYNOPSYS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SYNOPSYS TAIWAN CO., LTD.;REEL/FRAME:038320/0364 Effective date: 20160324 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551) Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |