Memory Safety Interface Module for Boot Time Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current memory testing methods, such as MBIST and STL, are inefficient in verifying memory connectivity and data integrity, leading to increased application boot time, resource consumption, and security vulnerabilities.

Innovation Solution

A memory safety interface module (MSIM) that verifies memory connectivity and data integrity by performing write and read operations in a specific pattern, using error detection codes to confirm data correctness, and operates during mission mode, replacing the need for MBIST and STL.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If MBIST is used to verify memory, then memory itself is tested, but connectivity towards memory and signal paths are not tested

Engineering Contradiction:
Improvememory verificationVSAvoidtesting coverage
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary testing mechanism that operates between the digital logic and memory, allowing verification of both memory and connectivity without requiring full MBIST or STL. This intermediary approach enables targeted testing of signal paths and interconnects while maintaining memory verification capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If MBIST is used to verify entire memory, then memory correctness is ensured, but application boot time significantly increases

Engineering Contradiction:
Improvememory correctnessVSAvoidboot time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial testing by verifying only the portions of memory that are actually used by the application rather than performing exhaustive testing of the entire memory space. This selective approach maintains reliability for critical operations while significantly reducing boot time penalties.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary verification of memory connectivity and signal paths before full memory operations commence. This preliminary action ensures that critical pathways are functional while avoiding the time cost of complete memory testing during boot-up.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If STL testing is performed to test digital logic, then logic correctness is verified, but mission mode stops and context switching is required

Engineering Contradiction:
Improvelogic verificationVSAvoidmission mode continuity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements self-service testing capabilities that allow the system to verify digital logic and memory connectivity during normal mission mode operations without requiring context switches or stopping productivity-critical tasks. The testing mechanism serves itself alongside operational functions.

Inventive Principle:
Principle #25Self-service

4Reliability

If STL testing is performed frequently to meet safety requirements, then fault detection capability is improved, but bandwidth consumption and code size increase

Engineering Contradiction:
Improvefault detectionVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements targeted fault detection that focuses on critical pathways and frequently-used memory regions rather than comprehensive testing of all possible fault conditions. This partial approach maintains safety requirements while reducing bandwidth and code size requirements.

Inventive Principle:
Principle #16Partial or excessive action

5Reliability

If memory is tested without software access to verify interconnect, then connectivity testing is enabled, but security vulnerabilities arise from lack of controlled access

Engineering Contradiction:
Improveinterconnect verificationVSAvoidsecurity vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a controlled intermediary interface that manages access to memory for testing purposes. This intermediary layer enables interconnect verification while maintaining security by controlling and monitoring all access paths, preventing unauthorized or unsafe operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12038812B2Memory safety interface configuration
Publication Date: 2024.07.16 SYNOPSYS INC
  • US12038812B2 patent drawing
  • US12038812B2 patent drawing
  • US12038812B2 patent drawing

AI summary

A memory safety interface module (MSIM) configured to test a memory. The MSIM receives an original data from a digital logic and inverts the bits of the original data to generate an inverted data. It writes the inverted data to the memory address. The MSIM reads the inverted data from the memory address and determines whether the memory address and the inverted data are correct. The MSIM either writes the original data to the memory address in response to the memory address and the inverted data being correct or transmits an error indication in response to at least one of the memory address and the inverted data being incorrect. The MSIM reads the original data from the memory address and determines whether the memory address and the original data are correct or transmits an error indication in response to at least one of the memory address and the original data being incorrect.