Automated IBIS Model Generation from SPICE Netlists

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The generation of IBIS models from SPICE netlists is cumbersome due to the need for manual preparation of multiple templates and simulations, with existing approaches requiring extensive manual effort and understanding of complex IBIS keywords, leading to inefficiencies in resolving dependencies and creating model variants.

Innovation Solution

A computer-implemented method and system that allows users to select and analyze portions of a SPICE netlist, render schematic symbols, and translate operations into simulation commands, providing a graphical user interface for labeling pins and assigning parameters, thereby automating the process of generating IBIS models and reducing manual effort.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual preparation of multiple templates and simulations is used to generate IBIS models, then model accuracy can be ensured, but the time and effort required increases significantly

Engineering Contradiction:
Improvemodel accuracyVSAvoidtime and effort required
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables automatic generation of IBIS models by having the software perform simulations and template creation autonomously based on SPICE netlists, eliminating the need for manual intervention while maintaining model accuracy through automated dependency resolution and simulation execution

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary analysis of SPICE netlists to automatically identify required nodes, dependencies, and simulation parameters before generating IBIS models, thereby preparing all necessary information in advance and eliminating iterative manual adjustments

Inventive Principle:
Principle #10Preliminary action

2Extent of automation

If existing template-based approaches are used, then model generation can be automated, but the complexity of understanding and using the templates increases

Engineering Contradiction:
Improvemodel generation automationVSAvoidtemplate complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system introduces a graphical user interface that acts as an intermediary between the user and the complex simulation processes, translating user-friendly selections into automated simulation commands and template generation, thereby hiding the complexity while maintaining automation

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system automatically generates and manages multiple template copies for different model variants based on a single SPICE netlist analysis, eliminating the need for users to manually create and understand multiple complex templates while maintaining full automation

Inventive Principle:
Principle #26Copying

3Reliability

If multiple simulations and trials are performed to resolve dependencies, then model completeness can be ensured, but the manual effort and preparation time increase

Engineering Contradiction:
Improvemodel completenessVSAvoidmanual effort and preparation time
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements automated feedback loops that monitor simulation results and automatically perform additional simulations or adjustments when dependencies are not fully resolved, ensuring model completeness without requiring manual intervention or preparation

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10528688B1System and method for schematic-driven generation of input/output models
Publication Date: 2020.01.07 CADENCE DESIGN SYST INC
  • US10528688B1 patent drawing
  • US10528688B1 patent drawing
  • US10528688B1 patent drawing

AI summary

Embodiments include herein are directed towards a method for generating an input/output model from a SPICE (Simulation Program with Integrated Circuit Emphasis) netlist. Embodiments may include receiving, using a processor, a SPICE netlist associated with an electronic design and selecting at least a portion of the SPICE netlist for analysis. Embodiments may further include reading the selected portion of the SPICE netlist and rendering a schematic symbol corresponding to the selected portion of the netlist. Embodiments may also include performing one or more operations associated with the schematic symbol and translating the one or more operations into simulation commands.