Non-Volatile Memory Updating with Integrated Booting Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing non-volatile memory updating methods for battery management systems in battery packs face challenges in ensuring updating reliability and efficiency, particularly due to the inconvenience of managing specific areas for flag recording and the potential for system errors from flag value errors.
Innovation Solution
A non-volatile memory updating apparatus and method that utilizes a central processing unit to record application code in a volatile memory, then transfers it to a non-volatile memory, and includes a booting indicator to confirm complete recording, eliminating the need for a separate flag and minimizing system errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a flag with a specific value is recorded to a specific area of the non-volatile memory to check whether the program is normally recorded, then the updating reliability can be checked, but it is inconvenient to separately create a specific area of the non-volatile memory and to continuously manage the specific area
Solution Approach 1:
The patent combines the flag checking function with the booting indicator into a single integrated mechanism. The booting indicator serves dual purposes: it indicates whether the system should boot and simultaneously serves as the verification flag for successful program recording. This eliminates the need for a separate specific area dedicated to flag management, as the booting indicator area fulfills both functions.
Solution Approach 2:
The booting indicator is designed to perform multiple functions: it acts as both a booting control signal and a verification flag for program recording success. By making this single element universal, the patent eliminates the need for separate flag management structures, thereby improving operational convenience while maintaining updating reliability.
2Reliability
If a booting indicator is read after confirming that the application code is normally recorded by checking the flag, then the application code can be executed, but it is inconvenient to read the booting indicator separately
Solution Approach 1:
The patent merges the flag checking process and the booting indicator reading process into a single unified operation. When the system checks the booting indicator, it simultaneously verifies both the successful program recording and the authorization to execute. This eliminates the need for separate sequential operations of reading a flag and then reading a booting indicator, thereby improving operational convenience while maintaining execution reliability.
3Reliability
If a separate flag area is created in the non-volatile memory, then the program recording status can be verified, but the device complexity increases due to continuous management requirements
Solution Approach 1:
The patent combines the verification function previously requiring a separate flag area into the booting indicator mechanism. The booting indicator area now serves both as the booting control signal and as the verification record for successful program recording. This integration eliminates the need for separate flag management structures, thereby reducing device complexity while maintaining recording verification capability.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
A non-volatile memory updating apparatus updates an application code stored in a non-volatile memory. The non-volatile memory updating apparatus includes: a volatile memory configured to store the application code; and a central processing unit configured to record the application code recorded in the volatile memory and a booting indicator indicating booting information of the application code in the non-volatile memory.