Memory Program Sequence Timing Checks for Abnormal Write Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing memory systems face issues with abnormal program sequences due to signal integrity problems, leading to incomplete or invalid program commands that can cause data loss, which are currently addressed through time-consuming and costly manual debugging by firmware teams.

Innovation Solution

A detector is implemented in the memory sub-system to monitor program sequences by using timers and status registers to identify abnormal sequences, triggering error handling mechanisms to protect data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual debugging by firmware teams is used to address abnormal program sequences, then data integrity can be protected, but time consumption and cost increase significantly

Engineering Contradiction:
Improvedata integrityVSAvoiddebugging time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The memory device performs self-diagnosis by automatically detecting abnormal program sequences through internal timing verification. The device compares actual program execution time against expected time ranges and identifies errors without external intervention, enabling the system to protect itself and eliminating the need for time-consuming manual debugging by firmware teams

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The detector implements a feedback mechanism by continuously monitoring program sequence execution and comparing actual timing against predefined expectations. When deviations are detected, the system generates error indicators that trigger automatic error handling mechanisms, creating a closed-loop system that continuously verifies and corrects program execution without manual intervention

Inventive Principle:
Principle #23Feedback

2Loss of time

If detector is implemented to automatically detect abnormal program sequences, then debugging time is reduced, but device complexity increases

Engineering Contradiction:
Improvedebugging timeVSAvoiddetector complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The detector is designed as a multi-functional component that performs multiple tasks: timing verification, error detection, error classification, and triggering appropriate error handling mechanisms. By consolidating these functions into a single universal detector module, the patent avoids the need for separate complex systems for each function, thereby reducing overall device complexity while maintaining comprehensive error detection capabilities

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The detector acts as an intermediary component between the program execution unit and the error handling mechanisms. It monitors program sequences and translates timing deviations into standardized error indicators that can be processed by existing error handling infrastructure, thereby bridging the gap without requiring complete system redesign and minimizing added complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260064529A1Abnormal program sequence detection
Publication Date: 2026.03.05 MICRON TECHNOLOGY INC
  • US20260064529A1 patent drawing
  • US20260064529A1 patent drawing
  • US20260064529A1 patent drawing

AI summary

A system and method for detecting abnormal program sequences on a memory device. In some examples, a timing process is initiated by either starting a timer or recording an initial timer value from the timer. A status register of the memory device is checked in response to initiating the timing process to determine whether the memory device is in a busy state corresponding to performing the program operation. The timer is stopped or a current timer value is recorded from the timer in response to determining that the memory device is not in the busy state. A determination is made to determine an elapsed time of the timer since being started or based on the initial and current timer values to provide a checked operation time. The checked operation time and the defined operation time are evaluated to determine whether the program sequence for implementing the program operation was abnormal.