# US 2009/0276738 A1 · Method and apparatus for executing a hardware simulation and verification solution

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2009/0276738 A1
- Document ID: US20090276738A1
- Status: Published application
- Kind: A1
- Application number: 12/112,222
- Filed: 2008-04-30
- Published: 2009-11-05
- Earliest claimed: 2008-04-30
- Assignees: Synopsys, Inc.
- Inventors: Manish Jain; Subha S. Chowdhury; Sridhar Seshadri
- Web page: https://patentgrep.com/patent/US20090276738A1

## CPC

- G06F 30/3308: using simulation
- G06F 30/30: Circuit design
- G06F 30/33: Design verification, e.g. functional simulation or model checking
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

One embodiment of the present invention provides systems and techniques to execute a hardware simulation and verification solution on a multiprocessor system. The hardware simulation and verification solution can be partitioned into different modules which can include a simulation kernel to simulate changes in signal values, a value change dump module to store the changes in the signal values on a computer-readable storage medium, a functional coverage module to check functionality, a toggle coverage module to check signal toggling, an assertion engine to check complex behaviors, and a testbench module to generate test scenarios. Embodiments of the present invention can execute different modules on different processors, thereby improving performance.

## Claims

### Claim 1

A method for executing a hardware simulation and verification solution on multiple processors which includes a simulation kernel to simulate changes in signal values, and a value change dump (VCD) module to store the changes in the signal values on a computer-readable storage medium, the method comprising:
executing the simulation kernel on a first processor, thereby causing the first processor to:
generate value change data which represents changes in a set of signal values; and
store the value change data so that a second processor, which is different from the first processor, is able to access the value change data; and
executing the VCD module on the second processor, thereby causing the second processor to:
compress the value change data; and
store the compressed value change data in the computer-readable storage medium for subsequent analysis.

### Claim 2 (depends on 1)

The method of claim 1, wherein prior to executing the simulation kernel, the method comprises:
receiving source files which describe a design under test (DUT); and
compiling the source files to obtain the simulation kernel.

### Claim 3 (depends on 2)

The method of claim 2,
wherein the simulation kernel exposes a callback interface which is used to install callback functions which are invoked when specific events occur;
wherein compiling the source files includes installing a first callback function which is invoked whenever the simulation kernel generates the value change data; and
wherein the first callback function includes:
instructions for collecting the value change data; and
instructions for storing the value change data so that the second processor can access the value change data.

### Claim 4 (depends on 2)

The method of claim 2, wherein the source files describe the DUT using a standardized, non-proprietary hardware description language (HDL), and wherein the simulation kernel and the VCD module execute in separate processes.

### Claim 5

A method for executing a hardware simulation and verification solution on multiple processors which includes a simulation kernel to simulate changes in signal values, and a functional coverage module to check coverage for a design under test (DUT), the method comprising:
executing the simulation kernel on a first processor, thereby causing the first processor to:
generate value change data which represents changes in a set of signal values which are used in a functional coverage model for the DUT; and
store the value change data so that a second processor, which is different from the first processor, is able to access the value change data; and
executing the functional coverage module on the second processor, thereby causing the second processor to:
determine a functional coverage metric using the functional coverage model and the value change data; and
report the functional coverage metric to a user.

### Claim 6 (depends on 5)

The method of claim 5, wherein prior to executing the simulation kernel, the method comprises:
receiving source files which describe the DUT; and
compiling the source files to obtain the simulation kernel.

### Claim 7 (depends on 6)

The method of claim 6,
wherein the simulation kernel exposes a callback interface which is used to install callback functions which are invoked when specific events occur;
wherein compiling the source files includes installing a first callback function which is invoked whenever the simulation kernel generates the value change data; and
wherein the first callback function includes:
instructions for collecting the value change data; and
instructions for storing the value change data so that the second processor can access the value change data.

### Claim 8 (depends on 6)

The method of claim 6, wherein the source files describe the DUT using a standardized, non-proprietary hardware description language (HDL), and wherein the simulation kernel and the functional coverage module execute in separate processes.

### Claim 9

A method for executing a hardware simulation and verification solution on multiple processors which includes a simulation kernel to simulate changes in signal values, and a toggle coverage module to check signal toggling for a design under test (DUT), the method comprising:
executing the simulation kernel on a first processor, thereby causing the first processor to:
generate value change data which represents changes in a set of signal values which are used in a toggle coverage model for the DUT; and
store the value change data so that a second processor, which is different from the first processor, is able to access the value change data; and
executing the toggle coverage module on the second processor, thereby causing the second processor to:
determine a toggle coverage metric using the toggle coverage model and the value change data; and
report the toggle coverage metric to a user.

### Claim 10 (depends on 9)

The method of claim 9, wherein prior to executing the simulation kernel, the method comprises:
receiving source files which describe the DUT; and
compiling the source files to obtain the simulation kernel.

### Claim 11 (depends on 10)

The method of claim 10,
wherein the simulation kernel exposes a callback interface which is used to install callback functions which are invoked when specific events occur;
wherein compiling the source files includes installing a first callback function which is invoked whenever the simulation kernel generates the value change data; and
wherein the first callback function includes:
instructions for collecting the value change data; and
instructions for storing the value change data so that the second processor can access the value change data.

### Claim 12 (depends on 10)

The method of claim 10, wherein the source files describe the DUT using a standardized, non-proprietary hardware description language (HDL), and wherein the simulation kernel and the toggle coverage module execute in separate processes.

### Claim 13

A method for executing a hardware simulation and verification solution on multiple processors which includes a simulation kernel to simulate changes in signal values, and an assertion engine to check complex behaviors for a design under test (DUT), the method comprising:
executing the simulation kernel on a first processor, thereby causing the first processor to:
notify the assertion engine on a second processor as soon as a simulation time slot begins, wherein the second processor is different from the first processor;
simulate changes in signal values of the DUT during the simulation time slot; and
wait for the assertion engine to evaluate the assertions on the second processor; and
executing the assertion engine on the second processor, thereby causing the second processor to:
in response to receiving a notification from the simulation kernel that the simulation time slot has begun, evaluate assertions using signal values which were determined during previous time slots;
report results of evaluating the assertions; and
notify the simulation kernel once the assertions have been evaluated.

### Claim 14 (depends on 13)

The method of claim 13, wherein prior to executing the simulation kernel, the method comprises:
receiving source files which describe the DUT; and
compiling the source files to obtain the simulation kernel.

### Claim 15 (depends on 14)

The method of claim 14, wherein compiling the source files includes generating instructions to notify the assertion engine on the second processor that the simulation time slot has begun.

### Claim 16 (depends on 14)

The method of claim 14, wherein the source files describe the DUT using a standardized, non-proprietary hardware description language (HDL), and wherein the simulation kernel and the assertion engine execute in separate threads.

### Claim 17

A method for executing a hardware simulation and verification solution on multiple processors which includes a simulation kernel to simulate changes in signal values, and a testbench module to generate test scenarios for a design under test (DUT), the method comprising:
executing the simulation kernel on a first processor, thereby causing the first processor to:
notify the testbench module on a second processor to generate test signals for testing the DUT, wherein the second processor is different from the first processor;
receive the test signals from the testbench module on the second processor; and
use the test signals to simulate changes in signal values of the DUT during a simulation time slot; and
executing the testbench module on the second processor, thereby causing the second processor to:
in response to receiving a notification from the simulation kernel to generate test signals, generate the test signals for testing the DUT; and
send the test signals to the simulation kernel on the first processor.

### Claim 18 (depends on 17)

The method of claim 17, wherein prior to executing the simulation kernel, the method comprises:
receiving source files which describe the DUT; and
compiling the source files to obtain the simulation kernel.

### Claim 19 (depends on 18)

The method of claim 18, wherein compiling the source files includes generating instructions to notify the testbench module on the second processor to generate the test signals.

### Claim 20 (depends on 18)

The method of claim 18, wherein the source files describe the DUT using a standardized, non-proprietary hardware description language (HDL), and wherein the simulation kernel and the testbench module are executed in separate processes.
