Domain Crossing Verification Using Assumption Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current domain crossing analysis tools in integrated circuit (IC) design lack a mechanism to verify assumptions made by circuit designers, particularly before synthesis, and are not linked to implementation verification tools, leading to potential system errors due to unresolved domain crossing issues.

Innovation Solution

A technique that involves receiving a data object representation of an electrical circuit, performing domain crossing checks, receiving an indication of assumptions for identified issues, converting the representation to a synthesized form, and determining verification checks based on these assumptions to validate the circuit design.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If domain crossing checks are performed on RTL representation before synthesis, then potential system errors can be identified early, but there is no mechanism to verify assumptions made by designers and the checks are not linked to implementation verification

Engineering Contradiction:
Improveerror detection capabilityVSAvoidverification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges domain crossing analysis with implementation verification by integrating the assumption verification mechanism into the existing verification flow. The verification engine that performs implementation verification is extended to also verify domain crossing assumptions, combining two previously separate functions into a unified system that reduces overall complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent performs domain crossing checks and assumption verification at the RTL representation stage before synthesis occurs. By conducting verification actions preliminarily, the system identifies and resolves potential errors early in the design process, preventing them from propagating to later implementation stages.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If assumption verification is integrated into the verification flow, then the likelihood of system errors is reduced, but the verification process becomes more complex

Engineering Contradiction:
Improveassumption verification accuracyVSAvoidverification process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The verification engine is designed to perform multiple functions: both traditional implementation verification and the new domain crossing assumption verification. This multi-functional approach avoids creating a separate verification system, thereby managing complexity while enhancing reliability through comprehensive verification.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Loss of time

If domain crossing analysis is performed at RTL level, then verification can be done before synthesis, but the analysis tools lack integration with implementation verification tools

Engineering Contradiction:
Improveverification timingVSAvoidtool integration complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent establishes a feedback mechanism where the verification engine uses information from implementation verification to validate assumptions made during RTL-level domain crossing analysis. This feedback loop ensures consistency between early-stage analysis and later implementation, enabling timely verification while managing integration complexity through structured information flow.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20230110701A1Techniques for design verification of domain crossings
Publication Date: 2023.04.13 TEXAS INSTRUMENTS INC
  • US20230110701A1 patent drawing
  • US20230110701A1 patent drawing

AI summary

A technique for domain crossing verification including receiving a first data object representation of an electrical circuit, performing a domain crossing check on the first data object representation to identify a domain crossing issue, receiving an indication of an assumption for the identified domain crossing issue, converting the first data object representation of the electrical circuit to a second data object representation of the electrical circuit, wherein the second data object representation is synthesized based on the first data object representation, determining one or more verification checks based on the second data object representation and the assumption for the identified domain crossing issue, and performing the one or more verification checks on the second data object representation of the electrical circuit.