Memory Die Initialization Sequence for Failure Record Retention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Non-volatile memory initialization failures often go undetected, leading to potential system instability and prolonged debugging times due to intermittent errors and low failure rates, which can be critical in vehicle and industrial applications.
Innovation Solution
Initializing a volatile memory die before non-volatile memory dies to allow the host to receive executable instructions, enabling the recording and storing of initialization failures, thereby providing a failure record and health report to the host.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If non-volatile memory dies are initialized before volatile memory die, then firmware can be copied to volatile memory for execution, but initialization failures of non-volatile memory dies go undetected and unrecorded
Solution Approach 1:
The patent applies preliminary action by initializing the volatile memory die first before initializing the non-volatile memory dies. This allows the host system to have executable instructions available in volatile memory that can record and store failure information if initialization failures occur during subsequent non-volatile memory initialization, preventing loss of failure data.
Solution Approach 2:
The volatile memory die acts as an intermediary between the host and the non-volatile memory dies. It receives executable instructions, copies them to volatile memory for execution, and enables the host to record failure information about non-volatile memory initialization failures, thus mediating the information flow and failure detection process.
2Reliability
If volatile memory die is initialized first to enable failure recording, then initialization failures can be detected and recorded, but the initialization sequence becomes more complex
Solution Approach 1:
The volatile memory die is initialized in advance before the non-volatile memory dies, establishing a ready state for failure recording. This preliminary initialization simplifies the overall process by ensuring the recording mechanism is prepared before failures can occur, rather than requiring complex post-failure analysis sequences.
Solution Approach 2:
The system uses its own volatile memory resources to record and store failure information about non-volatile memory initialization failures. This self-service approach eliminates the need for external monitoring systems or complex external logging mechanisms, reducing overall system complexity while maintaining reliable failure detection.
3Productivity
If non-volatile memory initialization failures are not recorded, then the system can operate without additional recording mechanisms, but debugging time increases due to intermittent errors and low failure rates
Solution Approach 1:
The patent implements feedback by recording and storing failure information in the volatile memory die when initialization failures occur in non-volatile memory dies. This feedback mechanism provides immediate information about failures, enabling rapid debugging and eliminating the time loss associated with detecting intermittent errors through repeated testing and observation.
Data Source
AI summary
The present disclosure includes apparatuses, methods, and systems for storing non-volatile memory initialization failures. In an example, a method can include initializing a volatile memory die, initializing a first non-volatile memory die in response to initializing the volatile memory die, copying executable instructions from the first non-volatile memory die to the volatile memory die in response to initializing the first non-volatile memory die, initializing the second non-volatile memory die in response to initializing the first non-volatile memory die, and storing a failure record in the first non-volatile memory die in response to an error occurring during the initialization of the second non-volatile memory die.