Memory Command History Logging for Intermittent Failure Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing memory systems lack a mechanism to efficiently track and analyze memory device command history, making it difficult to determine the root cause of failures, especially in critical applications like autonomous driving, which are often intermittent or one-time failures.
Innovation Solution
Implementing a command history manager within the memory device to store and manage information about issued commands, including command type, target information, and status, to facilitate root cause analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a command history manager is implemented to track and store command history data, then the ability to identify failure causes is improved, but the device complexity increases
Solution Approach 1:
The command history manager is designed to serve multiple functions: it tracks command history for failure analysis, stores command type information, target information, and status data, and provides diagnostic capabilities. This multi-functional approach justifies the added complexity by delivering comprehensive reliability improvements across various failure scenarios.
Solution Approach 2:
The command history manager acts as an intermediary component between the memory device operations and the failure analysis process. It captures and stores command history data that would otherwise be lost, providing a bridge that enables post-event diagnostic capabilities without fundamentally altering the core memory operations.
2Measurement precision
If command history data is stored including command type, target information, and status, then the measurement precision of failure analysis is improved, but the loss of time for data collection increases
Solution Approach 1:
The command history manager continuously captures and stores command history data in real-time as commands are executed, rather than collecting data after a failure occurs. This preliminary action ensures that all relevant command type, target, and status information is already recorded when a failure happens, eliminating post-failure data collection delays.
Solution Approach 2:
The system maintains continuous command history recording throughout operation, ensuring that diagnostic data is always available. This continuous action eliminates gaps in data collection and ensures that even intermittent or one-time failures are captured with complete command context information.
3Reliability
If command history tracking is implemented to capture intermittent or one-time failures, then the reliability of critical applications is improved, but the device complexity increases
Solution Approach 1:
The memory device performs self-diagnosis by automatically tracking and storing its own command history. This self-service capability enables the device to independently capture evidence of failures without requiring external monitoring systems, thereby improving critical application reliability while limiting complexity growth to only what is necessary within the device itself.
Data Source
AI summary
A memory device including control logic to identify a command issued to the memory device to execute a memory access operation on one or more memory cells of a memory array of the memory device. The control logic determines a command type associated with the command and identifies, based on the command type, a subset of target information to be stored as part of a set of command information. The control logic stores, in a data store of the memory device, the set of command information associated with the command.