Non-Volatile Memory Driver Download for Boot Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional boot processes for portable information communication devices require costly and time-consuming updates of non-volatile memory driver programs when replacing non-volatile memory, as the driver programs are typically stored in boot memory and need to be modified for compatibility with new memory types.
Innovation Solution
A method and system where the non-volatile memory driver program is downloaded from a host device, allowing the system program to be adjusted dynamically without modifying the boot program, using two separate download paths to ensure compatibility with different non-volatile memory types, thereby eliminating the need for boot memory updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the non-volatile memory driver program is stored in boot memory, then the system can initialize and operate the non-volatile memory, but the cost and complexity increase when updating or replacing non-volatile memory due to the need to modify the boot program
Solution Approach 1:
The patent extracts the non-volatile memory driver program from the boot memory and relocates it to the non-volatile memory itself. This separation allows the boot memory to remain generic and unchanged, while the driver program moves with the non-volatile memory, eliminating the need to modify boot memory when updating or replacing non-volatile memory devices.
Solution Approach 2:
The patent implements a dynamic loading mechanism where the non-volatile memory driver program is loaded into volatile memory during system initialization based on the detected non-volatile memory type. This dynamic approach allows the system to adapt to different memory configurations without requiring pre-configured boot memory for each memory type.
2Reliability
If the boot memory is updated to support replacement non-volatile memory, then compatibility is ensured, but the time and cost for mask updates increase
Solution Approach 1:
The patent performs preliminary action by storing the non-volatile memory driver program in the non-volatile memory itself before it is needed. During system initialization, the driver program is automatically detected and loaded based on the memory type, eliminating the need for time-consuming boot memory updates when replacing non-volatile memory.
3Device complexity
If a generic boot memory is used for multiple configurations, then device complexity is reduced, but the ability to support specific non-volatile memory types is limited
Solution Approach 1:
The patent introduces volatile memory as an intermediary that temporarily holds the non-volatile memory driver program during system initialization. This mediator allows the generic boot memory to load the appropriate driver program dynamically based on the detected non-volatile memory type, bridging the gap between generic boot capability and specific memory support.
Data Source
AI summary
A system and method thereof are provided. The example method may include downloading first information, from a host device, associated with an operation of a non-volatile memory and downloading second information associated with an operation of the system including the non-volatile memory, the second information downloaded based on the operation of the non-volatile memory in accordance with the downloaded first information. The example system may include a host device configured to provide first information associated with an operation of a non-volatile memory and second information associated with an operation of the system, the system including the non-volatile memory, the second information downloaded based on the operation of the non-volatile memory in accordance with the downloaded first information.