CN113127252A - Intelligent firmware repairing method in memory device - Google Patents
Intelligent firmware repairing method in memory device Download PDFInfo
- Publication number
- CN113127252A CN113127252A CN202110527946.3A CN202110527946A CN113127252A CN 113127252 A CN113127252 A CN 113127252A CN 202110527946 A CN202110527946 A CN 202110527946A CN 113127252 A CN113127252 A CN 113127252A
- Authority
- CN
- China
- Prior art keywords
- firmware
- data
- damaged
- recorded
- damage
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0727—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a storage system, e.g. in a DASD or network based storage system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Techniques For Improving Reliability Of Storages (AREA)
Abstract
The invention belongs to the field of firmware repair, in particular to an intelligent firmware repair method in a memory device, which aims at solving the problem that the existing damage frequency of firmware is inconvenient to analyze and the use quality of the firmware cannot be known, and provides the following scheme, comprising the following steps: s1: checking normal firmware and recording check data; s2: writing the firmware into a memory device for use; s3: checking the used firmware and recording check data; s4: comparing the data in the S1 with the data in the S3, and if the difference occurs in the comparison, indicating that the firmware is damaged; s5: repairing the damaged firmware according to the data in the S1; s6: recording the time of firmware damage, and analyzing the damage frequency of the firmware; s7: according to the method and the device, the use quality of the firmware in different time periods is analyzed according to the damage frequency, the damage frequency of the firmware can be analyzed, and the use quality of the firmware can be effectively known.
Description
Technical Field
The invention relates to the technical field of firmware repair, in particular to an intelligent firmware repair method in a memory device.
Background
Firmware is a program written in EPROM (erasable programmable read only memory) or EEPROM (electrically erasable programmable read only memory). The firmware refers to a device "driver" stored in the device, and through the firmware, the operating system can implement the operation of a specific machine according to the standard device driver, for example, the optical disc drive and the recorder have internal firmware. Firmware is software that acts as the most basic and bottom layer of a system. In the hardware device, the firmware is the soul of the hardware device, and because some hardware devices are not composed of other software except the firmware, the firmware determines the functions and performances of the hardware device, and the firmware is damaged during use and needs to be repaired.
In the prior art, it is inconvenient to analyze the damage frequency of the firmware, and the quality of the firmware cannot be known, so we propose an intelligent firmware repair method in a memory device to solve the above problems.
Disclosure of Invention
The invention aims to solve the defects that the damage frequency of firmware is inconvenient to analyze and the use quality of the firmware cannot be known in the prior art, and provides an intelligent firmware repairing method in a memory device.
In order to achieve the purpose, the invention adopts the following technical scheme:
an intelligent firmware repair method in a memory device, comprising the steps of:
s1: checking normal firmware and recording check data;
s2: writing the firmware into a memory device for use;
s3: checking the used firmware and recording check data;
s4: comparing the data in the S1 with the data in the S3, and if the difference occurs in the comparison, indicating that the firmware is damaged;
s5: repairing the damaged firmware according to the data in the S1;
s6: recording the time of firmware damage, and analyzing the damage frequency of the firmware;
s7: and analyzing the use quality of the firmware in different time periods according to the damage frequency.
Preferably, in S6, the time of the firmware damage is recorded, the number of times of the firmware damage in the previous 1-3 months is recorded, then the number of times of the firmware damage in the previous 4-6 months is recorded, and so on, the number of times of the firmware damage is recorded every three months, which can effectively analyze whether the number of times of the firmware damage increases with the increase of the time.
Preferably, in S3, the checking period is preset, and may be 1-15 days when the firmware is not damaged, and 1 day when the firmware is damaged.
Preferably, in S5, the damaged firmware is repaired according to the data in S1, and after the repair is successful, the firmware is checked again, and the data comparison is performed again until the data comparison is consistent.
Preferably, in S5, the damaged firmware is repaired according to the data in S1, and when the firmware is repaired, the timer starts to count time, and after the repair is completed, the data on the timer is read, the repair time is recorded, and the flag is stored.
Preferably, in S5, the damaged firmware is repaired according to the data in S1, the repaired content is recorded, and the recorded data is uploaded and stored in a classified manner.
Preferably, in S5, the damaged firmware is repaired according to the data in S1, and the repair record is uploaded and stored.
Preferably, in S5, the damaged firmware is repaired according to the data in S1, and when the firmware is repaired, a user is reminded to ensure the safety of the repair environment.
Compared with the prior art, the invention has the beneficial effects that:
according to the scheme, the time of firmware damage is recorded, the damage frequency of the firmware is analyzed, the use quality of the firmware in different time periods is analyzed according to the damage frequency, and the use quality of the firmware can be controlled;
when the scheme is used for repairing, the timer starts to time, and data on the timer is read until the repairing is finished, so that the repairing time is recorded and is marked for storage, and the repairing efficiency can be monitored;
the invention can analyze the damage frequency of the firmware and effectively know the use quality of the firmware.
Detailed Description
The technical solutions in the embodiments of the present invention are clearly and completely described below, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments.
Example one
An intelligent firmware repair method in a memory device, comprising the steps of:
s1: checking normal firmware and recording check data;
s2: writing the firmware into a memory device for use;
s3: checking the used firmware and recording check data;
s4: comparing the data in the S1 with the data in the S3, and if the difference occurs in the comparison, indicating that the firmware is damaged;
s5: repairing the damaged firmware according to the data in the S1;
s6: recording the time of firmware damage, and analyzing the damage frequency of the firmware;
s7: and analyzing the use quality of the firmware in different time periods according to the damage frequency.
In the invention, in S6, the firmware damage time is recorded, the damage times in the previous 1 month are recorded, then the damage times in 4 months are recorded, and by analogy, the damage times are recorded every three months, so that whether the damage times of the firmware increase along with the increase of the time can be effectively analyzed.
In the present invention, in S3, the checking period is preset, and when the firmware is not damaged, the checking period may be 1 day.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, after the repair is successful, the firmware is checked again, and the data comparison is performed again until the data comparison is consistent.
In the present invention, in S5, the damaged firmware is repaired according to the data in S1, and when repairing, the timer starts to count time, and after the repair is finished, the data on the timer is read, the repair time is recorded, and the flag is stored.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, the repaired content is recorded, and the recorded data is uploaded and stored in a classified mode.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, and the repair record is uploaded and stored.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, and when the firmware is repaired, a user is reminded to ensure the safety of the repair environment.
Example two
An intelligent firmware repair method in a memory device, comprising the steps of:
s1: checking normal firmware and recording check data;
s2: writing the firmware into a memory device for use;
s3: checking the used firmware and recording check data;
s4: comparing the data in the S1 with the data in the S3, and if the difference occurs in the comparison, indicating that the firmware is damaged;
s5: repairing the damaged firmware according to the data in the S1;
s6: recording the time of firmware damage, and analyzing the damage frequency of the firmware;
s7: and analyzing the use quality of the firmware in different time periods according to the damage frequency.
In the invention, in S6, the firmware damage time is recorded, the damage times in the first 2 months are recorded, then the damage times in 4 months are recorded, and so on, and the recording is performed every two months, so that whether the damage times of the firmware increase along with the increase of the time can be effectively analyzed.
In the present invention, in S3, the checking period is preset, and may be 10 days when the firmware is not damaged, and 1 day when the firmware is damaged.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, after the repair is successful, the firmware is checked again, and the data comparison is performed again until the data comparison is consistent.
In the present invention, in S5, the damaged firmware is repaired according to the data in S1, and when repairing, the timer starts to count time, and after the repair is finished, the data on the timer is read, the repair time is recorded, and the flag is stored.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, the repaired content is recorded, and the recorded data is uploaded and stored in a classified mode.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, and the repair record is uploaded and stored.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, and when the firmware is repaired, a user is reminded to ensure the safety of the repair environment.
EXAMPLE III
An intelligent firmware repair method in a memory device, comprising the steps of:
s1: checking normal firmware and recording check data;
s2: writing the firmware into a memory device for use;
s3: checking the used firmware and recording check data;
s4: comparing the data in the S1 with the data in the S3, and if the difference occurs in the comparison, indicating that the firmware is damaged;
s5: repairing the damaged firmware according to the data in the S1;
s6: recording the time of firmware damage, and analyzing the damage frequency of the firmware;
s7: and analyzing the use quality of the firmware in different time periods according to the damage frequency.
In the invention, in S6, the firmware damage time is recorded, the damage times in the previous 3 months are recorded, then the damage times in 6 months are recorded, and by analogy, the damage times are recorded once every three months, so that whether the damage times of the firmware increase along with the increase of the time can be effectively analyzed.
In the present invention, in S3, the checking period is preset, and may be 15 days when the firmware is not damaged, and 1 day when the firmware is damaged.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, after the repair is successful, the firmware is checked again, and the data comparison is performed again until the data comparison is consistent.
In the present invention, in S5, the damaged firmware is repaired according to the data in S1, and when repairing, the timer starts to count time, and after the repair is finished, the data on the timer is read, the repair time is recorded, and the flag is stored.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, the repaired content is recorded, and the recorded data is uploaded and stored in a classified mode.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, and the repair record is uploaded and stored.
In the invention, in S5, the damaged firmware is repaired according to the data in S1, and when the firmware is repaired, a user is reminded to ensure the safety of the repair environment.
The invention can analyze the damage frequency of the firmware by the intelligent repair method of the firmware in the memory device provided by the first, second and third embodiments, and effectively know the use quality of the firmware, wherein the second embodiment is the best embodiment.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art should be considered to be within the technical scope of the present invention, and the technical solutions and the inventive concepts thereof according to the present invention should be equivalent or changed within the scope of the present invention.
Claims (8)
1. An intelligent firmware repair method in a memory device is characterized by comprising the following steps:
s1: checking normal firmware and recording check data;
s2: writing the firmware into a memory device for use;
s3: checking the used firmware and recording check data;
s4: comparing the data in the S1 with the data in the S3, and if the difference occurs in the comparison, indicating that the firmware is damaged;
s5: repairing the damaged firmware according to the data in the S1;
s6: recording the time of firmware damage, and analyzing the damage frequency of the firmware;
s7: and analyzing the use quality of the firmware in different time periods according to the damage frequency.
2. The method as claimed in claim 1, wherein in S6, the time of firmware damage is recorded, the number of damages in the previous 1-3 months is recorded, then the number of damages in 4-6 months is recorded, and so on, and every three months is recorded, so as to effectively analyze whether the number of damages of firmware increases with the increase of time.
3. The method according to claim 1, wherein in S3, the checking period is preset, and the checking period may be 1-15 days when the firmware is not damaged, and is 1 day when the firmware is damaged.
4. The method as claimed in claim 1, wherein in S5, the damaged firmware is repaired according to the data in S1, and after the repair is successful, the firmware is checked again and the data comparison is performed again until the data comparison is consistent.
5. The method as claimed in claim 1, wherein in S5, the damaged firmware is repaired according to the data in S1, and when repairing, the timer starts counting time, and after repairing, the data on the timer is read, the repairing time is recorded, and the flag is stored.
6. The method according to claim 1, wherein in S5, the damaged firmware is repaired according to the data in S1, the repaired content is recorded, and the recorded data is sorted and uploaded for storage.
7. The method according to claim 1, wherein in S5, the damaged firmware is repaired according to the data in S1, and the repair record is uploaded and stored.
8. The method as claimed in claim 1, wherein in S5, the damaged firmware is repaired according to the data in S1, and when the damaged firmware is repaired, a user is reminded to ensure the safety of the repair environment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110527946.3A CN113127252A (en) | 2021-05-14 | 2021-05-14 | Intelligent firmware repairing method in memory device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110527946.3A CN113127252A (en) | 2021-05-14 | 2021-05-14 | Intelligent firmware repairing method in memory device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113127252A true CN113127252A (en) | 2021-07-16 |
Family
ID=76781854
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110527946.3A Pending CN113127252A (en) | 2021-05-14 | 2021-05-14 | Intelligent firmware repairing method in memory device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113127252A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20080023841A (en) * | 2006-09-12 | 2008-03-17 | 카시와야마 토요히테 | The method of firmware upgrade and automatic firmware recovery system |
| CN102857358A (en) * | 2011-06-29 | 2013-01-02 | 环旭电子股份有限公司 | Customer premise equipment capable of repairing firmware and firmware repairing method of customer premise equipment |
| CN103823723A (en) * | 2014-02-19 | 2014-05-28 | 惠州Tcl移动通信有限公司 | Mobile terminal touch screen firmware restoration method and device |
| CN108205446A (en) * | 2017-10-24 | 2018-06-26 | 中兴通讯股份有限公司 | Firmware restorative procedure and device |
-
2021
- 2021-05-14 CN CN202110527946.3A patent/CN113127252A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20080023841A (en) * | 2006-09-12 | 2008-03-17 | 카시와야마 토요히테 | The method of firmware upgrade and automatic firmware recovery system |
| CN102857358A (en) * | 2011-06-29 | 2013-01-02 | 环旭电子股份有限公司 | Customer premise equipment capable of repairing firmware and firmware repairing method of customer premise equipment |
| CN103823723A (en) * | 2014-02-19 | 2014-05-28 | 惠州Tcl移动通信有限公司 | Mobile terminal touch screen firmware restoration method and device |
| CN108205446A (en) * | 2017-10-24 | 2018-06-26 | 中兴通讯股份有限公司 | Firmware restorative procedure and device |
Non-Patent Citations (2)
| Title |
|---|
| 崔梅等: "固态硬盘固件可靠性测试", 《信息与电脑(理论版)》 * |
| 陆廷孝 等: "《可靠性设计与分析》", 30 September 1995 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103578568B (en) | The performance test methods of solid state hard disc and device | |
| TWI410976B (en) | Reliability test method for solid storage medium | |
| CN106776095A (en) | SSD solid state hard disc data reliability intelligent detecting methods and detection means | |
| CN103186471B (en) | The management method of bad block and system in storage device | |
| CN109918022B (en) | SSD open card bad block table inheritance method | |
| KR100243314B1 (en) | Error log method using defect list | |
| CN106502583A (en) | A kind of method for reducing solid state hard disc operating lag | |
| EP3079067A1 (en) | Method and apparatus for using solid state disk | |
| CN109376046A (en) | A kind of method for testing hard disk, device, equipment and computer readable storage medium | |
| CN105137227A (en) | Testing device and method for power-down protection of intelligent card | |
| CN113673004A (en) | Data destruction method based on classification | |
| CN110764960B (en) | Solid state disk firmware testing method | |
| CN112542203A (en) | Bad block repairing method and device for nonvolatile memory, storage medium and terminal | |
| CN114356792B (en) | Electric energy meter frozen data storage method based on FLASH pre-erasing technology and electric energy meter | |
| CN112270945B (en) | Method, device, storage medium and terminal for recording power failure during erasing | |
| CN107818025A (en) | Hard disk cold data method of calibration, device, equipment and computer-readable recording medium | |
| CN113127252A (en) | Intelligent firmware repairing method in memory device | |
| CN101076786A (en) | Method for processing mistake come from execution of mistake processing program | |
| CN107316659B (en) | Memory power-down time period positioning method and system power-down protection method | |
| US7484221B2 (en) | Method and apparatus for logging the execution history of an operating system kernel | |
| US20070277059A1 (en) | Storage device, control device, and error reporting method | |
| CN101286142B (en) | Magnetic disc operating protecting method and disk control unit | |
| CN109885342A (en) | A kind of system program restorative procedure of law-enforcing recorder | |
| CN116185706A (en) | Data backup method and device, computing and storage medium and electronic equipment | |
| CN108648778B (en) | Solid state disk reading system and method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210716 |
|
| RJ01 | Rejection of invention patent application after publication |