Memory System Initialization Recovery via Boot Code Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional memory systems fail to initialize operations when initialization data is stored in bad cells or becomes damaged, leading to recognition failures and operational standby signal issues, causing temporary and financial losses, especially during manufacturing.

Innovation Solution

A method for initializing memory systems that involves receiving an initialization signal, executing boot code, loading initialization data, and re-executing the boot code when the operation standby signal is not enabled, followed by erasing and updating the initialization data, and optionally using backup or preliminary data to restore functionality without relying on the faulty initialization data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If initialization data is stored in non-volatile memory device and loaded onto working memory for execution, then the memory system can perform initialization operations, but the system fails when the initialization data is stored in bad cells or damaged

Engineering Contradiction:
Improveinitialization operation reliabilityVSAvoiddamage from abrupt power off during patch update
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The boot code performs preliminary actions by checking whether initialization data is properly stored in the non-volatile memory device before loading it onto the working memory. This preliminary check prevents the system from attempting to execute damaged initialization data, thereby avoiding recognition failures and operational standbys.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The boot code implements feedback by detecting the status of initialization data in the non-volatile memory device and adjusting the initialization process accordingly. When damage or improper storage is detected, the boot code responds by modifying the initialization sequence, thus preventing system failure.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If the boot code executes initialization data from non-volatile memory, then the memory system can be initialized, but the system cannot recover when recognition failure occurs due to damaged initialization data

Engineering Contradiction:
Improveinitialization operationVSAvoidrecovery from recognition failure
Core Design Contradiction:
Ease of operationVSEase of repair

Solution Approach 1:

The boot code performs preliminary verification of initialization data integrity before execution. This preliminary action ensures that only valid initialization data is loaded and executed, preventing recognition failures and enabling easier recovery when issues occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The memory system performs self-diagnosis and self-correction by detecting damaged initialization data and automatically adjusting the initialization process. The boot code can identify when initialization data is problematic and modify its behavior accordingly, enabling the system to recover without external intervention.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If initialization data is updated via patch update, then the memory system can be updated, but abrupt power off during patch update damages the initialization data

Engineering Contradiction:
Improvepatch update capabilityVSAvoidinitialization data integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The boot code performs preliminary checks to verify the integrity of initialization data before loading it for execution. This preliminary verification ensures that even if abrupt power off occurs during patch updates, the system can detect and handle the damaged data appropriately, maintaining reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The boot code implements beforehand cushioning by preparing fallback mechanisms and verification steps before the initialization data is executed. When abrupt power off damages initialization data, the cushioning measures enable the system to detect the damage and recover, preventing complete system failure.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Device complexity

If conventional memory systems load and execute initialization data without verification, then the initialization process is simple, but the system determines recognition failure when initialization data is damaged

Engineering Contradiction:
Improveinitialization process complexityVSAvoidrecognition failure detection
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The boot code performs preliminary verification of initialization data integrity before loading it onto the working memory. This adds a verification step that prevents the system from executing damaged data, thereby avoiding false recognition failures while maintaining relatively simple initialization process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9015459B2Method of initializing operation of a memory system
Publication Date: 2015.04.21 SAMSUNG ELECTRONICS CO LTD
  • US9015459B2 patent drawing
  • US9015459B2 patent drawing
  • US9015459B2 patent drawing

AI summary

Provided is a method of initializing operation of a memory system. The method includes receiving an initialization signal, performing a first initializing operation that uses initialization data in response to the receiving of the initialization signal, setting a forced reset mode when an operation standby signal is not enabled by the first initializing operation, and performing a second initializing operation that does not use the initialization data in response to the setting of the forced reset mode.