# US 2025/0165334 A1 · Functional safety bist with system vitals

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

- Number: US 2025/0165334 A1
- Document ID: US20250165334A1
- Status: Published application
- Kind: A1
- Application number: 18/953,162
- Filed: 2024-11-20
- Published: 2025-05-22
- Earliest claimed: 2023-11-21
- Assignees: Signature IP Corporation
- Applicants: Signature IP Corporation
- Inventors: Kishore Mishra; Parag Bhatt; Purna Mohanty
- Web page: https://patentgrep.com/patent/US20250165334A1

## CPC

- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- G06F 11/27: Built-in tests
- G06F 11/0739: {in a data processing system embedded in automotive or aircraft systems}
- G06F 11/2205: {using arrangements specific to the hardware being tested}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Built-in self-test (BIST) execution is enabled in various applications, including embedded systems, such as those found in vehicles, medical equipment, avionics, and/or other systems of critical importance. An automotive subsystem within a motor vehicle is accessed. The automotive subsystem includes a system-on-a-chip (SoC). The SoC includes a network-on-a-chip (NoC). The SoC is coupled to a communications bus. The communications bus includes a bus controller. The SoC is coupled to a functional safety test environment (FUSATE). The FUSATE is awakened from a low power mode by a timer. The FUSATE a test sequence to one or more logic components within the SOC. The test sequence includes a functionality check of the one or more logic components. The FUSATE receives a first response from the one or more logic components within the SoC and records the first response. The FUSATE reenters the low power mode, resetting the timer.

## Claims

### Claim 1

A processor-implemented method for testing comprising:
accessing an automotive subsystem within a motor vehicle, wherein the automotive subsystem includes a system-on-a-chip (SoC), wherein the SoC includes a network-on-a-chip (NoC), wherein the SoC is coupled to a communications bus, wherein the communications bus includes a bus controller, and wherein the SoC is coupled to a functional safety test environment (FUSATE);
awakening, by a timer, the FUSATE from a low power mode;
sending, by the FUSATE, to one or more logic components within the SOC, a test sequence, wherein the test sequence includes a functionality check of the one or more logic components;
receiving, by the FUSATE, a first response from the one or more logic components within the SoC;
recording, by the FUSATE, the first response that was received; and
reentering, by the FUSATE, the low power mode, wherein the reentering includes resetting the timer.

### Claim 2 (depends on 1)

The method of claim 1 wherein the FUSATE is external to the SOC, wherein the FUSATE is coupled to the bus controller and the communications bus.

### Claim 3 (depends on 2)

The method of claim 2 further comprising arbitrating, by the bus controller, between the test sequence and one or more functional transactions on the communications bus.

### Claim 4 (depends on 2)

The method of claim 2 wherein the receiving occurs over the communications bus.

### Claim 5 (depends on 4)

The method of claim 4 wherein the first response is interleaved, by the bus controller, with one or more functional transactions.

### Claim 6 (depends on 5)

The method of claim 5 wherein the first response includes a packetized communication.

### Claim 7 (depends on 2)

The method of claim 2 wherein the receiving occurs over a test response bus.

### Claim 8 (depends on 1)

The method of claim 1 wherein the timer is at or above a first threshold.

### Claim 9 (depends on 8)

The method of claim 8 wherein the first threshold is programmable.

### Claim 10 (depends on 1)

The method of claim 1 wherein the recording includes sending, to a remote server, the first response.

### Claim 11 (depends on 10)

The method of claim 10 wherein the sending is based on a number of responses recorded, wherein the number is above a second threshold.

### Claim 12 (depends on 10)

The method of claim 10 further comprising accessing, by a software program, the first response on the remote server, wherein the accessing is based on an application programming interface (API).

### Claim 13 (depends on 12)

The method of claim 12 further comprising analyzing the first response, wherein the analyzing detects a malfunction of the automotive subsystem.

### Claim 14 (depends on 13)

The method of claim 13 further comprising alerting a user of the malfunction.

### Claim 15 (depends on 1)

The method of claim 1 further comprising reawakening the FUSATE from the low power mode, wherein the reawakening is based on the resetting the timer.

### Claim 16 (depends on 15)

The method of claim 15 wherein the receiving includes a second response.

### Claim 17 (depends on 1)

The method of claim 1 further comprising examining, by the FUSATE, the first response that was recorded, wherein the examining detects a malfunction of the automotive subsystem.

### Claim 18 (depends on 17)

The method of claim 17 further comprising notifying an automotive controller of the malfunction.

### Claim 19 (depends on 1)

The method of claim 1 further comprising programming the FUSATE, wherein the programming is accomplished with a test instruction set architecture (TISA).

### Claim 20 (depends on 19)

The method of claim 19 further comprising providing programming access through a test port of the FUSATE.

### Claim 21 (depends on 1)

The method of claim 1 wherein the test sequence targets a connectivity of the NOC.

### Claim 22 (depends on 1)

The method of claim 1 wherein the recording includes an identification number for the automotive subsystem.

### Claim 23 (depends on 1)

The method of claim 1 wherein the recording includes an identification of the one or more logic components.

### Claim 24 (depends on 1)

The method of claim 1 wherein the recording includes a motor vehicle identification.

### Claim 25

A computer program product embodied in a non-transitory computer readable medium for testing, the computer program product comprising code which causes one or more processors to perform operations of:
accessing an automotive subsystem within a motor vehicle, wherein the automotive subsystem includes a system-on-a-chip (SoC), wherein the SoC includes a network-on-a-chip (NoC), wherein the SoC is coupled to a communications bus, wherein the communications bus includes a bus controller, and wherein the SoC is coupled to a functional safety test environment (FUSATE);
awakening, by a timer, the FUSATE from a low power mode;
sending, by the FUSATE, to one or more logic components within the SOC, a test sequence, wherein the test sequence includes a functionality check of the one or more logic components;
receiving, by the FUSATE, a first response from the one or more logic components within the SoC;
recording, by the FUSATE, the first response that was received; and
reentering, by the FUSATE, the low power mode, wherein the reentering includes resetting the timer.

### Claim 26

A computer system for testing comprising:
a memory which stores instructions;
one or more processors coupled to the memory wherein the one or more processors, when executing the instructions which are stored, are configured to:
access an automotive subsystem within a motor vehicle, wherein the automotive subsystem includes a system-on-a-chip (SoC), wherein the SoC includes a network-on-a-chip (NoC), wherein the SoC is coupled to a communications bus, wherein the communications bus includes a bus controller, and wherein the SoC is coupled to a functional safety test environment (FUSATE);
awaken, by a timer, the FUSATE from a low power mode, wherein the timer is at or above a first threshold;
send, by the FUSATE, to one or more logic components within the SOC, a test sequence, wherein the test sequence includes a functionality check of the one or more logic components;
receive, by the FUSATE, a first response from the one or more logic components within the SoC;
record, by the FUSATE, the first response that was received; and
reenter, by the FUSATE, the low power mode, wherein the reentering includes resetting the timer.
