Browse Prior Art Database

Method for 2nd and 3rd Order DRC Filtering for Advanced Error Analysis

IP.com Disclosure Number: IPCOM000212398D
Publication Date: 2011-Nov-10
Document File: 2 page(s) / 58K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for 2nd and 3rd order DRC filtering for advanced error analysis.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

Method for 2

22nd and

nd and 333rd Order DRC Filtering for Advanced Error Analysis

rd Order DRC Filtering for Advanced Error Analysis

A critical part of the circuit design process is to run Design Rules Checking (DRC) to verify designs meet ground rule requirements for the technology. Designers iteratively run DRC, look at error logs and reports, and then go back into the graphical layout design to fix fails.

    Currently, designers are only able to filter through the list of DRC fails by rule type. There is not a current method to apply another filter level to parse down the rules any further. For instance, there is no current method to group specific types of topologies within a particular rule type. This article presents a solution that would allow 2nd and possibly 3rd order filtering of DRC fails for advanced circuit analysis.

    Such a feature would be particularly helpful early in the technology when trying to understand if rules are ignoring (or flagging) certain fail types correctly,
or also by allowing one more freedom to parse through a very large number of fails for a particular ground rule.

    The core idea presented aims to establish a methodology by which DRC fails can be filtered beyond rule type by analyzing the error markers for failing instances of a particular ground rule, and allowing one to further filter those failing instances based on given criteria.

    As stated above this makes the task of parsing through large number of fail types for a given rule less cumbersome and much more efficient. Consider someone has 300 fails to the rule GR100 on M2 (a metal spacing rule). They click the rule and go to error marker location to see error (today's normal workflow). Consider that they see this violation in Figure 1 below.

FIGURE 1

    Now consider they want to quantify how many of these violations are due to this exact configuration, without cycling through all 300 violations one at a time. This is where the new thinking comes in.

    After a DRC rule type is selected in the GUI, the designer would be presented with additional options such as "find similar errors" and "find other errors."

Such options could be enabled by right-clicking the error marker, for instance.

1


Page 02...