Presentation is loading. Please wait.

Presentation is loading. Please wait.

Waiving Known DRC Violations from Layout IP John Ferguson Technical Marketing Engineer Mentor Graphics Corp.

Similar presentations


Presentation on theme: "Waiving Known DRC Violations from Layout IP John Ferguson Technical Marketing Engineer Mentor Graphics Corp."— Presentation transcript:

1 Waiving Known DRC Violations from Layout IP John Ferguson Technical Marketing Engineer Mentor Graphics Corp.

2 AE Training – mbDRC – Advanced Checks are simple 2 The Problem n Due to Process Limitations the Number of DRC Rules is Growing — Rule Complexity is Also Growing n Difficulty in Defining Rules to Capture Failure Configuration Leads to Over Constrainment — Many ‘Errors’ Can Actually Yield Well n Meeting all Design Rules is Difficult if Not Impossible 350nm 250nm 180nm130nm 90nm65nm 45nm Additional Metal DRC Rules 3 Layer Metal DRC Rules

3 AE Training – mbDRC – Advanced Checks are simple 3 Manifestation: DRC “Waivers” n Waivers = Real DRC Violations That are Allowed in a Design Layout for Mask and Chip Manufacturing n Examples: — Historic IP Block Has Been Manufactured Clean for Years. Now with New DRC Rules, It Fails. — Certain Blocks (Memories) Take Advantage of Rigid Design Approach. Fail Standard Logic Rules, But Will Manufacture at a Reasonable Yield. — Block is DRC Clean, but Has “Recommended Rule Violations” that Cannot be Fixed Without Generating DRC Violations

4 AE Training – mbDRC – Advanced Checks are simple 4 Fabless (e.g. Broadcom, Qualcomm, etc.) Foundry (e.g. TSMC, UMC, etc.) Traditional IP Waivers Dilemma Runs DRC Gets Results Phones Foundry Delivers IP to Customer Can I waive these? Sure, why not. Designer: Integrates IP into Design Gets Results Manually Reviews All Why so many in IP?? Phones Foundry Phones IP Provider Can I waive these? What?!? Heck No!! What is with this IP you sold me!!. What do you mean? Foundry said I could waive! Let’s call him together and waste tons of your time sorting thi out! IP Provider (e.g. ARM, Virage, etc.)

5 AE Training – mbDRC – Advanced Checks are simple 5 Historic Approaches to Try to Solve the Problem n Black-Box the IP During DRC — Fast RunTimes — False Results Eliminated — Missed Real Errors n Remove Results Per Block Per Cell — At DRC Runtime or Post-Process — No Missed Real Errors — Many False Errors Still Exist

6 AE Training – mbDRC – Advanced Checks are simple 6 Issue: Interaction Errors Between Waived Cells Can be Incorrectly Waived Waived Cell Waived Result Identify Blue Inside Waived Cell Waive Spacing Errors Between Identified Shapes Errors from Interactions Also Waived X = M1 NOT INSIDE CELL A Y = M1 INSIDE CELL A Check {EXTERNAL X <.2 EXTERNAL X Y <.2}

7 AE Training – mbDRC – Advanced Checks are simple 7 Result Promotion Waived Cell Waived Result Unique Errors Reported at Top Results Not Consistent with All Instances: Reported at Top Results No Longer Associated with Waived Cell Waivers Do Not Apply

8 AE Training – mbDRC – Advanced Checks are simple 8 Proposed DRC Waiver Flow n The Waiver Flow is a 2-Step Process 1. Waiver classification: Identify Waived Results within Cells Waiver_flow Cell Characterization Rules Chip GDSII Results Final Results Waived Results Unused waivers 2. Chip level run: Merge chip database with waived results Distinguish waived results by waiver requirements during DRC Remaining results output Also capture all waived results for record keeping Waiver Setup File Cell Library Cell Library W/ Waivers Chip Verification

9 AE Training – mbDRC – Advanced Checks are simple 9 Fabless (e.g. Broadcom, Qualcomm, etc.) Foundry (e.g. TSMC, UMC, etc.)IP Provider (e.g. ARM, Virage, etc.) Solving the IP Waiver Dilemma Runs DRC Gets Results Phones Foundry Delivers IP to Customer Can I waive these? Sure, why not. Designer: Integrates IP into Design Gets Results Waived Results Removed! Goes Home Early for the Day!

10 AE Training – mbDRC – Advanced Checks are simple 10 Typical Flows Representing 3 rd Party Foundry & IP Provider Purchased / Reused IP IP Block Containing Errors to Waive waiver_flow Cell Characterization Foundry Golden Rules Waiver Setup File Waiver Description File DRC Chip Verification Rules from Foundry Other Files Created by IP Provider Waivers Merged with IP By IP Provider IP with Waivers and Waiver Files Passed to Customer By IP Provider 3 rd Party IP with Waivers Embedded into Design Waivers Stripped from Final Results Using Info from Waiver Files

11 AE Training – mbDRC – Advanced Checks are simple 11 Proposed Waiver Flow DRC Debug DRC n The Proposed Waiver Flow Provides a Automated Communication Channel Between Foundry, IP Providers and Designers for Significantly Reducing Design Debug Time by Eliminating the Reporting of Known and Waived Errors from IP Blocks n Unlike Historic Approaches, The Waiver Flow Requires Little Effort by the Designer and Minimizes the Risk of Missed Real Errors without Increasing the Reporting of False Errors

12 Waiver_Flow: Capturing the Waivers at the IP Level

13 AE Training – mbDRC – Advanced Checks are simple 13 waiver_flow: Capturing the Cell Results to Waive rules Chip or Cell Lib AALL Bfoo Cbar waiver_flow waiver_setup./Waiver_results/A/ DRC_RES.db All Rule Results AB./Waiver_results/B/ DRC_RES.db All Rule Results C./Waiver_results/C/ DRC_RES.dbAll Rule Results Ascii Result May be Edited to Selected Results Only Waiver.gds Waived Results Only Optionally Create New Library with Original Lib and Waivers Merged

14 AE Training – mbDRC – Advanced Checks are simple 14 Minimizing Reserved Layers n Creates Empty Cell for Each Waived Cell Name n Instantiates Child Cell into Waived Cell — _ _ — Once Cell For Each Waived Check — All Results on Specified Layer from waiver_setup n Subsequent DRC Differentiates Results by Cell Name n Only One Reserved Layer Required! n Output Library GDS Files Merges Waiver.gds with Original Cell Data — Waiver Cells Instantiated — Added Cell Naming Convention Remains Intact Cell Nand2_2x Cell = waive$$_PO.W.R.2_in_Nand2_2x Cell = waive$$_PO.W.S.5_in_Nand2_2x

15 Waiving from Chip Level

16 AE Training – mbDRC – Advanced Checks are simple 16 Removal of Waivers n The Removal of Waived Results from Real Results is Done at the Time of Running DRC — Determined by Pattern Matching Previously Captured IP Waivers to Chip Level Results for the Same Rule — DRC Hierarchical Engine Resolves Issues of Results Promotion n The Pattern Matching is Determined through the Setup File — As Qualified Per Check by the Foundry or Fab

17 AE Training – mbDRC – Advanced Checks are simple 17 Pattern Matching Criteria: Handling Multiple Overlaps IP Block Original IP Generated Waivers Context Parent Level Results (pre-waived) Should Final Result be Waived? Waiver Setup Specifies Handling of Multiple Overlaps

18 AE Training – mbDRC – Advanced Checks are simple 18 Tolerances for Waiver Overlap? IP Block IP Waiver Chip Should the Green Results Still Be Waived? Waiver Setup Specifies Required IP Waiver to Chip Error Pattern Matching

19 AE Training – mbDRC – Advanced Checks are simple 19 Allowing Tolerances for Waiving IP Block IP Waiver Chip Chip level result Allowable Difference? n Waiver Setup Specifies Chip Error to IP Waiver Pattern Matching Criteria n A Result is Either Fully Waived or Not Waived — No chopping of results

20 AE Training – mbDRC – Advanced Checks are simple 20 Example 1 A single waiver interacts with the result inv_1inv_1 in Layout The waiver matches the result exactly The result matches the waiver exactly Full-chip result m1_space_waiver

21 AE Training – mbDRC – Advanced Checks are simple 21 Example 2 A single waiver interacts with the result inv_1inv_1 in Layout The result is fully covered by the waiver Full-chip result The waiver is not fully covered by the result m1_space_waiver n Waiving Will Depend On the Specification of the Waiver to Result Matching

22 AE Training – mbDRC – Advanced Checks are simple 22 Example 3 inv_1inv_1 in Layout Full-chip result m1_space_waiver n Waiving Will Depend On the Specification of the Result to Waiver Matching

23 AE Training – mbDRC – Advanced Checks are simple 23 Example 4 inv_1inv_1 in Layout m1_space_waiver n Waiving Will Depend On the Specification of the Waiver to Result Matching AND Count Tolerance

24 AE Training – mbDRC – Advanced Checks are simple 24 Summary n The Proposed Waiver Flow Provides Significant Value Over Historic Automated Approaches to Waiving DRC Violations — All Waived Results Automatically and Accurately Waived at DRC Run Time — Enables Passing of IP Between 3 rd Parties with Waiver Information in Tact — Enables Foundry to Specify Acceptable Waiving Tolerances Per Rule Per IP — Eliminates Need for Rule File Modifications — Works from Standard GDSII, No Proprietary Formats — All Waived Results Captured for Final Review and Tracking

25 AE Training – mbDRC – Advanced Checks are simple 25


Download ppt "Waiving Known DRC Violations from Layout IP John Ferguson Technical Marketing Engineer Mentor Graphics Corp."

Similar presentations


Ads by Google