# US 2021/0173987 A1 · Reset crossing and clock crossing interface for integrated circuit generation

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

- Number: US 2021/0173987 A1
- Document ID: US20210173987A1
- Status: Published application
- Kind: A1
- Application number: 17/157,564
- Filed: 2021-01-25
- Published: 2021-06-10
- Earliest claimed: 2019-07-09
- Assignees: SiFive, Inc.
- Applicants: SiFive, Inc.
- Inventors: Henry Cook; Ernest L. Edgar; Ryan Macdonald; Wesley Waylon Terpstra
- Web page: https://patentgrep.com/patent/US20210173987A1

## CPC

- G06F 30/327: Logic synthesis; Behaviour synthesis, e.g. mapping logic, HDL to netlist, high-level language to RTL or netlist
- G06F 1/10: Distribution of clock signals {, e.g. skew}
- G06F 1/24: Resetting means
- G06F 30/333: Design for testability [DFT], e.g. scan chain or built-in self-test [BIST]
- G06F 30/337: Design optimisation
- G06F 30/3312: Timing analysis
- G06F 30/3315: using static timing analysis [STA]
- G06F 30/396: Clock trees
- G06F 30/398: Design verification or optimisation, e.g. using design rule check [DRC], layout versus schematics [LVS] or finite element methods [FEM] (optical proximity correction [OPC] design processes G03F1/36)
- G06F 2115/02: System on chip [SoC] design
- G06F 2119/12: Timing analysis or timing optimisation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods are disclosed for generation and testing of integrated circuit designs with clock crossings between clock domains and reset crossings between reset domains. These may allow for the rapid design and testing (e.g. silicon testing) of processors and SoCs. Clock crossings may be automatically generated between modules, inferring the values of design parameters, such as a signaling protocol (e.g. a bus protocol), directionality, and/or a clock crossing type (e.g., synchronous, rational divider, or asynchronous), of a clock crossing. Reset crossings may be automatically generated in a similar manner. For example, implicit classes may be used to generate clock crossings or reset crossings in a flexible manner. For example, these system and methods may be used to rapidly connect a custom processor design, including one or more IP cores, to a standard input/output shell for a SoC design to facilitate rapid silicon testing of the custom processor design.

## Claims

### Claim 1

A method comprising:
accessing a register-transfer level data structure for an integrated circuit design;
receiving a command to generate a reset crossing between a first module of the register-transfer level data structure and a second module of the register-transfer level data structure;
responsive to the command, automatically determining a signaling protocol identifier for the reset crossing based on data of the second module;
responsive to the command, automatically determining a directionality for the reset crossing based on data of the second module; and
responsive to the command, automatically generating the reset crossing between the first module and the second module based on the signaling protocol identifier and based on the directionality to obtain a modified register-transfer level data structure.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
responsive to the command, automatically determining a reset crossing type for the reset crossing based on a reset domain type of the first module and based on a reset domain type of the second module, wherein the reset crossing is automatically generated based on the reset crossing type.

### Claim 3 (depends on 2)

The method of claim 2, wherein the reset domain type of the first module indicates a first reset duration in clock cycles, the reset domain type of the second module indicates a second reset duration in clock cycles, and the reset crossing type indicates a difference between the first reset duration and the second reset duration.

### Claim 4 (depends on 1)

The method of claim 1, wherein the command includes a parameter specifying a reset crossing type and the reset crossing is automatically generated based on the reset crossing type specified by the command.

### Claim 5 (depends on 1)

The method of claim 1, wherein automatically generating the reset crossing comprises:
generating register-transfer level data implementing logic to suppress one or more outputs of the first module in accordance with a bus protocol identified by the signaling protocol identifier during a reset period for the first module.

### Claim 6 (depends on 1)

The method of claim 1, wherein automatically generating the reset crossing comprises:
generating register-transfer level data implementing logic to stretch a reset signal to meet a minimum reset duration of the first module.

### Claim 7 (depends on 1)

The method of claim 1, wherein automatically generating the reset crossing comprises:
using an implicit class that is invoked using the signaling protocol identifier.

### Claim 8 (depends on 1)

The method of claim 1, wherein the second module is a bus module.

### Claim 9 (depends on 1)

The method of claim 1, wherein the first module includes an IP core and the second module is a component of an input/output shell for a system-on-a-chip design.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
generating a physical design data structure for the integrated circuit based on the modified register-transfer level data structure;
invoking fabrication of the integrated circuit based on the physical design data structure;
invoking tests of the fabricated integrated circuit to obtain a set of test results; and
transmitting, storing, or displaying the set of test results.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
generating a physical design data structure for the integrated circuit based on the modified register-transfer level data structure;
generating a software development kit for the integrated circuit based on the modified register-transfer level data structure;
generating a test plan for the integrated circuit;
invoking tests for the integrated circuit based on the test plan, the modified register-transfer level data structure, the software development kit, and the physical design data structure to obtain a set of test results; and
transmitting, storing, or displaying a design data structure based on the modified register-transfer level data structure, the software development kit, the physical design data structure, and the test results.

### Claim 12

A system comprising:
a network interface;
a memory; and
a processor, wherein the memory includes instructions executable by the processor to cause the system to:
access a register-transfer level data structure for an integrated circuit design;
receive a command to generate a reset crossing between a first module of the register-transfer level data structure and a second module of the register-transfer level data structure;
responsive to the command, automatically determine a signaling protocol identifier for the reset crossing based on data of the second module; and
responsive to the command, automatically generate the reset crossing between the first module and the second module based on the signaling protocol identifier to obtain a modified register-transfer level data structure.

### Claim 13 (depends on 12)

The system of claim 12, wherein the memory further includes instructions executable by the processor to cause the system to:
responsive to the command, automatically determine a reset crossing type for the reset crossing based on a reset domain type of the first module and based on a reset domain type of the second module, wherein the reset crossing is automatically generated based on the reset crossing type.

### Claim 14 (depends on 13)

The system of claim 13, wherein the reset domain type of the first module indicates a first reset duration in clock cycles, the reset domain type of the second module indicates a second reset duration in clock cycles, and the reset crossing type indicates a difference between the first reset duration and the second reset duration.

### Claim 15 (depends on 12)

The system of claim 12, wherein the command includes a parameter specifying a reset crossing type and the reset crossing is automatically generated based on the reset crossing type specified by the command.

### Claim 16 (depends on 12)

The system of claim 12, wherein automatically generating the reset crossing comprises:
generating register-transfer level data implementing logic to suppress one or more outputs of the first module in accordance with a bus protocol identified by the signaling protocol identifier during a reset period for the first module.

### Claim 17 (depends on 12)

The system of claim 12, wherein automatically generating the reset crossing comprises:
generating register-transfer level data implementing logic to stretch a reset signal to meet a minimum reset duration of the first module.

### Claim 18 (depends on 12)

The system of claim 12, wherein automatically generating the reset crossing comprises:
using an implicit class that is invoked using the signaling protocol identifier.

### Claim 19 (depends on 12)

The system of claim 12, wherein the first module includes an IP core and the second module is a component of an input/output shell for a system-on-a-chip design.

### Claim 20

A method comprising:
accessing a register-transfer level data structure for an integrated circuit design;
receiving a command to generate a clock crossing between a first module of the register-transfer level data structure and a second module of the register-transfer level data structure;
responsive to the command, automatically determining a signaling protocol identifier for the clock crossing based on data of the second module; and
responsive to the command, automatically generating the clock crossing between the first module and the second module based on the signaling protocol identifier to obtain a modified register-transfer level data structure.
