IP Library Granted Patent US 9,934,349
Granted Patent B2
US 9,934,349 · App. 14/669,697 · Granted Apr 3, 2018

Method for verifying design rule checks

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,934,349
App. No.
14/669,697
Granted
Apr 3, 2018
Kind
B2
Abstract

A method for design rule verification is provided. The method comprises: providing a design rule check (DRC) deck based on a design rule manual (DRM) having a plurality of design rules; providing a plurality of primitive objects; creating a plurality of collection objects, each collection object using one or more primitive objects; using the plurality of collection objects, creating a plurality of DRM test cases; assigning names to each of the plurality of DRM test cases, each of the names based on a rule name of the plurality of design rules and on an expected pass or fail indication; and using the plurality of named DRM test cases to verify the DRC deck.

Claims (68)

1. A method for design rule verification, the method comprising:

providing a design rule check deck based on a design rule manual (DRM) having a plurality of design rules;

providing a plurality of primitive objects;

creating a plurality of collection objects, each collection object using one or more primitive objects;

using the plurality of collection objects, creating a plurality of DRM test cases;

assigning names to each of the plurality of DRM test cases, each of the names following a naming convention that includes a rule name of the plurality of design rules and an expected pass or fail indication within each of the names;

using the plurality of named DRM test cases to verify the design rule check deck; and

manufacturing an integrated circuit based on the verified design rule check deck.

2. The method of claim 1 , further comprising organizing the plurality of named DRM test cases into a combined database file after assigning names to each of the plurality of DRM test cases.

3. The method of claim 2 , further comprising running the design rule check deck on the DRM test cases in the combined database file.

4. The method of claim 3 , further comprising outputting an error database file as a result of running the design rule check deck on the design rule manual test cases in the combined database file.

5. The method of claim 4 , further comprising:

merging the error database file with the combined database file; and

identifying any unintentional failures in the error database file.

6. The method of claim 5 , further comprising:

determining that there is an unintentional error in the error database file;

modifying the design rule check deck or test cases to correct the unintended failure;

running the modified design rule check deck and test cases;

outputting another error database file merged with the combined database file;

identifying that there are no other unintentional failures; and

determining that the design rule check deck is verified.

7. The method of claim 6 , wherein the verified design rule check deck is used to create a design rule compliant physical layout for an integrated circuit.

8. The method of claim 1 , wherein providing a plurality of primitive objects comprises providing one or more of a square, rectangle, L-shape, or bevel shape.

9. The method of claim 1 , wherein creating a plurality of DRM test cases comprises creating a test case for verifying that an edge spacing between two shapes is greater than or equal to a minimum spacing.

10. A method for design rule verification, the method comprising:

providing a design rule check deck based on a design rule manual (DRM) having a plurality of design rules;

providing a plurality of primitive objects;

creating a plurality of collection objects, each collection object using one or more primitive objects;

using the plurality of collection objects, creating a plurality of DRM test cases;

assigning names to each of the plurality of DRM test cases, each of the names following a naming convention that includes a rule name of the plurality of design rules and an expected pass or fail indication within each of the names;

organizing the plurality of named DRM test cases into a combined database file;

running the design rule check deck on the named DRM test cases in the combined database file;

outputting an error database file as a result of running the design rule check deck on the design rule manual test cases in the combined database file;

merging the error database file with the combined database file;

identifying any unintentional failures in the error database file;

correcting the errors set out in the error database file;

determining that the design rule check deck is verified; and

manufacturing an integrated circuit based on the verified design rule check deck.

11. The method of claim 10 , wherein outputting an error database file and correcting the errors set out in the error database file further comprises:

determining that there is an unintentional error in the error database file;

modifying the design rule check deck or test cases to correct the unintended failure;

running the modified design rule check deck and test cases;

outputting another error database file merged with the combined database file; and

identifying that there are no other unintentional failures.

12. The method of claim 10 , wherein the verified design rule check deck is used to create a design rule compliant physical layout for an integrated circuit.

13. The method of claim 10 , wherein providing a plurality of primitive objects comprises providing one or more of a square, rectangle, L-shape, or bevel shape.

14. The method of claim 10 , wherein creating a plurality of DRM test cases comprises creating a test case for verifying that an edge spacing between two objects is greater than or equal to a minimum spacing.

15. The method of claim 10 , wherein creating a plurality of DRM test cases comprises creating a test case for verifying that a corner-to-corner spacing between two objects is greater than or equal to a minimum spacing.

16. A method for design rule verification, the method comprising:

providing a design rule check deck based on a design rule manual (DRM) having a plurality of design rules;

providing a plurality of primitive objects;

creating a plurality of collection objects, each collection object using one or more primitive objects;

using the plurality of collection objects, creating a plurality of DRM test cases;

assigning names to each of the plurality of DRM test cases, each of the names following a naming convention that includes a rule name of the plurality of design rules and an expected pass or fail indication within each of the names;

organizing the plurality of named DRM test cases into a combined database file;

running the design rule check deck on the named DRM test cases in the combined database file;

determining that there is at least one unintentional error in the error database file;

modifying the design rule check deck or test cases to correct the at least one unintended failure;

running the modified design rule check deck and test cases;

outputting another error database file merged with the combined database file;

identifying that there are no other unintentional failures;

correcting the errors set out in the error database file;

determining that the design rule check deck is verified; and

manufacturing an integrated circuit based on the verified design rule check deck.

17. The method of claim 16 , wherein the verified design rule check deck is used to create a design rule compliant physical layout for an integrated circuit.

18. The method of claim 16 , wherein providing a plurality of primitive objects comprises providing one or more of a square, rectangle, L-shape, or bevel shape.

19. The method of claim 16 , wherein creating a plurality of DRM test cases comprises creating a test case for verifying that an edge spacing between two objects is greater than or equal to a minimum spacing.

20. The method of claim 16 , wherein creating a plurality of DRM test cases comprises creating a test case for verifying that a corner-to-corner spacing between two objects is greater than or equal to a minimum spacing.

Assignments (7)
CORRECTIVE ASSIGNMENT TO CORRECT THE REMOVE APPLICATION 11759915 AND REPLACE IT WITH APPLICATION 11759935 PREVIOUSLY RECORDED ON REEL 040925 FRAME 0001. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST. Recorded Feb 17, 2020
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: NXP, B.V. F/K/A FREESCALE SEMICONDUCTOR, INC.
Reel/Frame 052917/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE REMOVE APPLICATION 11759915 AND REPLACE IT WITH APPLICATION 11759935 PREVIOUSLY RECORDED ON REEL 040928 FRAME 0001. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST. Recorded Jan 17, 2020
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: NXP B.V.
Reel/Frame 052915/0001 →
RELEASE OF SECURITY INTEREST Recorded Sep 10, 2019
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: NXP B.V.
Reel/Frame 050744/0097 →
CORRECTIVE ASSIGNMENT TO CORRECT THE NATURE OF CONVEYANCE PREVIOUSLY RECORDED AT REEL: 040626 FRAME: 0683. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER AND CHANGE OF NAME EFFECTIVE NOVEMBER 7, 2016. Recorded Jan 12, 2017
From: NXP SEMICONDUCTORS USA, INC. (MERGED INTO); FREESCALE SEMICONDUCTOR, INC. (UNDER)
To: NXP USA, INC.
Reel/Frame 041414/0883 →
CHANGE OF NAME Recorded Nov 16, 2016
From: FREESCALE SEMICONDUCTOR INC.
To: NXP USA, INC.
Reel/Frame 040626/0683 →
RELEASE OF SECURITY INTEREST Recorded Nov 7, 2016
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: NXP B.V.
Reel/Frame 040928/0001 →
RELEASE OF SECURITY INTEREST Recorded Sep 21, 2016
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: NXP, B.V., F/K/A FREESCALE SEMICONDUCTOR, INC.
Reel/Frame 040925/0001 →