Design Mismatch Management in IC Physical Design
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of digital circuit designs at smaller semiconductor dimensions leads to incomplete, inconsistent, or mismatched data in IC design, causing inefficiencies and increased time and cost in the design and implementation process.
Innovation Solution
A taxonomy of design mismatches is developed, allowing for the repair and recording of mismatches, with user-controllable high-level settings to manage the acceptable level of mismatch, actions taken during discovery, and reporting of the design state, using a system that aggregates mismatch settings into 'prototype', 'normal', and 'tapeout' levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If ad hoc techniques are applied to remediate design mismatches, then the design process can continue with incomplete or inconsistent data, but the design cannot be created successfully and requires additional time and cost for corrections
Solution Approach 1:
The system performs preliminary actions by automatically detecting and classifying design mismatches before they propagate through the design flow. Mismatch detection occurs at source, and the system pre-determines the impact level (blocking vs. non-blocking) before the design process continues, allowing controlled progression while maintaining awareness of data quality issues.
Solution Approach 2:
The system implements feedback mechanisms by continuously monitoring design data for mismatches and providing feedback to the user through reports and warnings. The feedback loop allows users to review mismatch information, understand its impact, and make informed decisions about whether to proceed with the design or correct the issues first.
2Reliability
If design mismatches are detected and reported, then design correctness can be maintained, but the design process becomes slower and more complex
Solution Approach 1:
The system applies partial action by selectively reporting and requiring attention only to mismatches that are deemed blocking or high-impact. Non-blocking mismatches are recorded but do not halt the design process, allowing the system to maintain correctness where needed while avoiding unnecessary delays in areas where mismatches are acceptable or low-risk.
Solution Approach 2:
The system implements local quality by differentiating the treatment of mismatches based on their location and impact. Different mismatch types are handled differently: some require immediate attention, others can be ignored, and some are automatically resolved. This localized approach ensures that design correctness is maintained in critical areas while allowing flexibility in less critical areas.
3Reliability
If a comprehensive mismatch detection system is implemented, then all design issues can be identified, but the system complexity and overhead increase
Solution Approach 1:
The system segments the mismatch detection function into distinct modules that handle different types of mismatches separately. Each module is responsible for specific detection tasks, making the overall system more manageable and easier to implement. The segmentation allows for modular development and easier maintenance of the detection mechanisms.
Solution Approach 2:
The system introduces an intermediary layer between the design tools and the user that handles mismatch detection and reporting. This intermediary component absorbs the complexity of comprehensive detection while presenting a simplified interface to the user. The intermediary processes raw data, identifies mismatches, and provides summarized information, reducing the perceived complexity while maintaining thorough detection.
Data Source
AI summary
Systems and methods allow an IC design process to continue in the face of errors while those errors are being investigated and fixed in the actual design data. Potential mismatches can be categorized and a user can choose which action (if any) to take when a specific mismatch is discovered. A set of potential mismatches and their action settings can be aggregated into a higher level setting that the end user of the system can choose during different stages of a design project. A record of the mismatches that have been encountered, the design elements that are involved in each mismatch, and what action where taken to repair the mismatch is kept and maintained.