CN108733517A - SSD firmware upgrades guard method and device - Google Patents
SSD firmware upgrades guard method and device Download PDFInfo
- Publication number
- CN108733517A CN108733517A CN201810569588.0A CN201810569588A CN108733517A CN 108733517 A CN108733517 A CN 108733517A CN 201810569588 A CN201810569588 A CN 201810569588A CN 108733517 A CN108733517 A CN 108733517A
- Authority
- CN
- China
- Prior art keywords
- firmware
- copy
- copies
- ssd
- written
- 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/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1433—Saving, restoring, recovering or retrying at system level during software upgrading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/654—Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of SSD firmware upgrades guard method and devices, include the following steps：Check firmware list, it is that read-write and oldest firmware version Firmware is copied to filter out read-write properties, determines Firmware Block where Firmware copies；Wipe the Firmware Block；Image file is written to the Firmware Block；It checks whether and is written successfully；If being written successfully, it is set as the Firmware being newly written copies to start copy；If write-in failure, returns and wipes the Firmware Block steps.By the way that multiple and different Firmware copies are arranged, in upgrading selecting one is upgraded, and is started using the firmware after upgrading if success, is otherwise started using original, and being not in firmware upgrade failure SSD can not normally start, or even the problem of lose disk.
Description
Technical field
The present invention relates to SSD firmware upgrades field, a kind of SSD firmware upgrades guard method and dress are especially related to
It sets.
Background technology
SSD (solid state disk) has been widely used in various occasions, since it is in performance, power consumption, environmental suitability etc.
The outstanding index of aspect, just gradually replaces traditional hard disk.Since SSD is very high for data reliability requirement, and user's scene
Complexity occurs so usually having the not covered scene of some close betas；Meanwhile under certain situations, SSD suppliers publication
New algorithm optimization, can promote user experience, in these cases be required for repairing by firmware upgrade, optimizing SSD.
Existing SSD firmware upgrade process is as follows：Host issues firmware upgrade order；SSD receiving hosts are new
Firmware image files；Verify Firmware image files；Wipe all Firmware Block；New Firmware is written
Image file；Firmware mirror images are read, check correctness；If be not correctly written in, repeat the above steps；If correct
Write-in is replied host upgrading and is completed.And during SSD firmware upgrades, if misoperation can lead to hard disk, failure is for example prominent
Other accidents that can not resist so are powered off or sent, can cause SSD data that can not access.
Invention content
In order to solve the defect of the above-mentioned prior art, the object of the present invention is to provide a kind of SSD firmware upgrades guard methods
And device.
In order to achieve the above objectives, the technical scheme is that：
It proposes a kind of SSD firmware upgrades guard method, includes the following steps：
Check firmware list, it is that read-write and oldest firmware version Firmware is copied to filter out read-write properties, is determined
Firmware Block where Firmware copies；
Wipe the Firmware Block；
Image file is written to the Firmware Block；
It checks whether and is written successfully；
If being written successfully, it is set as the Firmware being newly written copies to start copy；
If write-in failure, returns and wipes the Firmware Block steps.
Further, described to set the Firmware being newly written copies to start copy step, including,
The Current Boot Copy in modification NOR start-up parameters region are the Firmware copies being newly written.
Further, described to set after starting copy step the Firmware being newly written copies to, including,
ROM is run, Bootloader is loaded to program Memory and executes
Corresponding Firmware copies are selected according to the Current Boot Copy in NOR start-up parameters region；
Whether correct verify Firmware copies；
If correct, load Firmware and copy and execute；
If incorrect, firmware list is scanned, it is the newest Firmware of read-only and firmware version to filter out read-write properties
Copy, is denoted as Firmware Copy N；
The Current Boot Copy for changing start-up parameter region are Firmware Copy N；
Load Firmware Copy N are simultaneously executed.
Further, the Current Boot Copy in the modification NOR start-up parameters region are the Firmware being newly written
Step is copied, including,
Start-up parameter region is increased newly in NOR, and is had in the storage of start-up parameter region and copied physics comprising all Firmware
Storage address and quantity information, and for determining the Current Boot Copy for starting copy.
Further, the inspection firmware list, it is that read-write Firmware is copied to filter out all read-write properties, choosing
Before selecting the oldest Firmware copy steps of firmware version, including,
Multiple Firmware copies are set, and corresponding access limit is set for each Firmware copies, and is different
The firmware version of Firmware copies is different.
The invention also provides a kind of SSD firmware upgrades protective devices, including：
First screening unit, for checking firmware list, it is that read-write and firmware version is oldest to filter out read-write properties
Firmware is copied, and determines Firmware Block where Firmware copies；
Unit is wiped, for wiping the Firmware Block；
Writing unit, for image file to be written to the Firmware Block；
Inspection unit is written successfully for checking whether；
Start setting unit, if for being written successfully, is set as the Firmware being newly written copies to start copy；
Returning unit returns for if failure to be written and wipes the Firmware Block steps.
Further, the startup setting unit includes starting setup module, for changing NOR start-up parameters region
Current Boot Copy are the Firmware copies being newly written.
Further, further include：
Running unit, for running ROM, loading Bootloader to program Memory and executing
Start unit, for selecting corresponding Firmware according to the Current Boot Copy in NOR start-up parameters region
Copy；
Whether verification unit is correct for verifying Firmware copies；
If first execution unit loads Firmware and copies and execute for correct；
If second screening unit scans firmware list for incorrect, and it is read-only and firmware version to filter out read-write properties
This newest Firmware copy, is denoted as Firmware Copy N；
Unit is changed, the Current Boot Copy for changing start-up parameter region are Firmware Copy N；
Second execution unit, for loading Firmware Copy N and executing.
Further, the startup setting unit further includes newly-increased module, for increasing start-up parameter region newly in NOR, and
In start-up parameter region, storage has copies physical store address and quantity information comprising all Firmware, and is opened for determination
The Current Boot Copy of dynamic copy.
Further, further include pre-seting unit, for multiple Firmware copies to be arranged, and copied for each Firmware
Corresponding access limit is arranged in shellfish, and the firmware version of different Firmware copies is different.
The beneficial effects of the invention are as follows：By the way that the Firmware copies of multiple and different firmware versions are arranged, in firmware updating
When one of them is upgraded, started using the firmware after upgrading successfully if upgrading successfully, if upgrading is unsuccessful
Started using other original Firmware copies, ensure that in firmware upgrade process, at least there is that there are one can be with
The Firmware started copies are normally used for, ensure that the normal use of SSD, are not in cause because of firmware upgrade failure
SSD can not normally start, or even the problem of lose disk.
Description of the drawings
Fig. 1 is a kind of method flow diagram of SSD firmware upgrades guard method of the present invention；
Fig. 2 is a kind of method flow diagram of start-up parameter setting of the present invention；
Fig. 3 is a kind of method flow diagram of SSD firmware upgrades guard method of the present invention；
Fig. 4 is the functional block diagram that one embodiment of the invention SSD starts；
Fig. 5 is a kind of structure diagram of SSD firmware upgrades protective device of the present invention；
Fig. 6 is a kind of structure diagram of the startup setting unit of SSD firmware upgrades protective device of the present invention.
Specific implementation mode
To illustrate the thought and purpose of the present invention, the present invention is done further below in conjunction with the drawings and specific embodiments
Explanation.
Firmware copies also write Firmware Copy.
Firmware Block are for storing Firmware Copy.
Referring to Fig.1-4, a specific embodiment of the invention, a kind of SSD firmware upgrades guard method, including following step are proposed
Suddenly：
S11, firmware list is checked, it is that read-write and oldest firmware version Firmware is copied to filter out read-write properties,
Firmware Block where determining Firmware copies.
S12, the Firmware Block are wiped.
S13, write-in image file to the Firmware Block.
S14, it checks whether and is written successfully.
If S15, being written successfully, it is set as the Firmware being newly written copies to start copy.
If S16, write-in failure, return and wipe the Firmware Block steps.
For step S11, for host after issuing firmware upgrade order, SSD receives the image file for upgrading, accurate
Standby upgrading, by checking (the Firmware copy row of the firmware list Firmware Copy List in NOR start-up parameters region
Table), it is that read-write all Firmware are copied, and obtain the version of above-mentioned all Firmware copies first to filter out read-write properties
This information determines that the Firmware of oldest version is copied according to version information, and determining corresponding Firmware Block,
The Firmware Block are subsequently used to carry out firmware upgrade.
Specifically, read-write properties, can be divided into read-only (R) and two kinds of read-write (RW), the Firmware copies of attribute-readable
It can only be read, new image file can not be written and carry out firmware upgrade, specifically, preserving the Firmware of a read only attribute
Copy, can not just change after manufacture, for carrying out system startup after all Firmware copy failure.And it is readable
Writing the Firmware copies of (RW) attribute can be read, and new image file can also be written and carry out firmware upgrade, after being used for
It is continuous to carry out firmware upgrade, ensure SSD firmware upgrades to the best version of performance.
Further include step S10 before step S11：Multiple Firmware copies are set, and are set for each Firmware copies
Corresponding access limit is set, and the firmware version of different Firmware copies is different.
For step S10, in manufacture, a lot of Firmware copies are pre-set, and be Firmware copy settings
Corresponding access limit, and the firmware version of different Firmware copies is different.Write-in is being copied for all Firmware
After corresponding image file, the read-write properties that one Firmware of setting is copied are read-only (R), can not be changed later, remaining
Read-write properties are all read-write (RW), can carry out firmware upgrade later.It is read-only Firmware that a read-write properties, which are arranged,
Copy, can not just change after manufacture, for carrying out system startup after all Firmware copy failure, avoid
SSD upgrade failures, lose disk.
For step S12, needs to wipe the data on target Firmware Block before image file is written, wipe
New image file is written again later except finishing.
For step S13, after the data on erasing target Firmware Block, you can the mirror image that will be received
File is written on target Firmware Block, carries out firmware upgrade.
For step S14, after image file is written to Firmware Block, in fact it could happen that be written successfully or write
Enter two kinds of failure as a result, it is desirable to check write structure and carry out next step operation according to write-in result.
It, will be on the Firmware Block according to normal flow if image file is written successfully for step S15
Firmware copies the startup copy new as SSD, the Firmware upgraded will can be used to copy when starting next time
Shellfish is started, and entire escalation process is completed.
With reference to figure 2, step S15 includes the following steps：
Step S151：Start-up parameter region is increased newly in NOR, and storage has comprising all Firmware in start-up parameter region
Physical store address and quantity information are copied, and for determining the Current Boot Copy for starting copy.
Step S152：The Current Boot Copy for changing NOR start-up parameters region are that the Firmware being newly written is copied
Shellfish.
For step S151, a region is increased newly in the regions NOR：Start-up parameter region, the interior following information of storage：For
The Firmware Copy Number parameters of all Firmware Copy quantity are indicated, for determining the Current for starting copy
The physical store address of Boot Copy parameters and every part of Firmware copies.It can be by reading Firmware Copy
Number parameters understand the particular number of all Firmware Copy, pass through Current Boot Copy parameters and physical store
Address is determined carries out startup SSD using that Firmware copies.
Image file new will be written after checking that determining new image file write-in is out of question for step S152
Firmware copies are determined as the new startup copies of SSD, specifically, the Current by changing NOR start-up parameters region
Boot Copy are that the Firmware copies being newly written can.
For step S16, in other situations, if write-in is unsuccessful, repeat the above steps S12-S14, weight
Image file is written in the suitable Firmware Block of new selection.
With reference to figure 3, after step S16, including：
S17, operation ROM, load Bootloader to program Memory and execute.
S18, corresponding Firmware is selected to copy according to the Current Boot Copy in NOR start-up parameters region.
Whether S19, verification Firmware copies are correct.
If S20, correct, load Firmware and copy and execute.
If S21, incorrect, firmware list is scanned, it is that read-only and firmware version is newest to filter out read-write properties
Firmware is copied, and is denoted as Firmware Copy N.
S22, the Current Boot Copy for changing start-up parameter region are Firmware Copy N.
S23, load Firmware Copy N are simultaneously executed.
For step S17, with reference to figure 4, the typical Booting sequences of SSD are as follows：After energization, ROM is executed；ROM is loaded from NOR
Bootloader to program Memory jumps to Bootloader operations；Bootloader is (more from storage Firmware Block
It is a) it scans and loads complete portion Firmware copies (Firmware Copy) and arrive program Memory, and start to execute, it is complete
At startup.Specifically, have ROM inside SSD controller, the position for starting to execute for energization post code；Tool inside SSD controller
Standby program Memory, the place executed for load external program；The Bootloader (generally 16KB) simplified is stored on NOR,
To complete system initialization.
For step S18, carried on the Current Boot Copy in NOR start-up parameters region for starting copy
Information selects the copies of the Firmware on corresponding Firmware Block to be started according to Current Boot Copy.
For step S19, before activation, the image file to Firmware Block is needed to verify, it is ensured that mirror image
File is complete reliable, can be used for starting SSD.
For step S20, after being checked, determines that image file is out of question, then load in Firmware Block
Firmware copies and executes startup, completes SSD and starts.
For step S21, when there are when problem, need to find to be used for for the image file on selected Firmware Block
Emergent Firmware copies, that is, read-write properties are that read-only initial Firmware is copied, and are copied using initial Firmware
Shellfish starts SSD, ensures that firmware upgrade goes wrong, but SSD data are normal.After finding initial Firmware copies,
It is denoted as Firmware Copy N.
For step S22, in NOR start-up parameters region, modification Current Boot Copy are Firmware Copy N,
When follow-up SSD startups, the initial Firmware copies of load will be given tacit consent to and started, ensureing SSD, at least one can be a normal
The Firmware of startup is copied, and improves the safety of SSD firmware upgrades.
For step S23, the corresponding initial Firmware copies of load, and execute startup.
By the way that the Firmware copies of multiple and different firmware versions are arranged, one of them is risen in firmware updating
Grade is started if upgrading successfully using the firmware after upgrading successfully, if upgrading is unsuccessful original using other
Firmware copies are started, and ensure that in firmware upgrade process, and at least there are one can be normally used for startup for presence
Firmware is copied, and ensure that the normal use of SSD, is not in cause SSD not open normally because of firmware upgrade failure
The problem of moving, or even losing disk.
The invention also provides a kind of SSD firmware upgrades protective devices, including：
Unit 10 is pre-seted, for multiple Firmware copies to be arranged, and it is corresponding for each Firmware copy settings
Access limit, and the firmware version of different Firmware copies is different.
First screening unit 11 checks firmware list, and it is that read-write and firmware version is oldest to filter out read-write properties
Firmware is copied, and determines Firmware Block where Firmware copies.
Unit 12 is wiped, for wiping the Firmware Block.
Writing unit 13, for image file to be written to the Firmware Block.
Inspection unit 14, is written successfully for checking whether.
Start setting unit 15, if for being written successfully, is set as the Firmware being newly written copies to start copy.
Returning unit 16 returns to erasing unit 12 and wipes the Firmware Block for if failure to be written.
Running unit 17, for running ROM, loading Bootloader to program Memory and executing.
Start unit 18, for corresponding according to the Current Boot Copy selections in NOR start-up parameters region
Firmware is copied.
Whether verification unit 19 is correct for verifying Firmware copies.
If first execution unit 20 loads Firmware and copies and execute for correct.
If second screening unit 21 scans firmware list for incorrect, and it is read-only and firmware to filter out read-write properties
The newest Firmware copies of version, are denoted as Firmware Copy N.
Unit 22 is changed, the Current Boot Copy for changing start-up parameter region are Firmware Copy N.
Second execution unit 23, for loading Firmware Copy N and executing.
For pre-seting unit 10, in manufacture, a lot of Firmware copies are pre-set, and copy for Firmware
Corresponding access limit is set, and the firmware version of different Firmware copies is different.It is copied for all Firmware
It being written after corresponding image file, the read-write properties that one Firmware of setting is copied are read-only (R), can not be changed later,
Remaining read-write properties is all read-write (RW), can carry out firmware upgrade later.One read-write properties of setting are read-only
Firmware is copied, and can not just be changed after manufacture, is opened for carrying out system after all Firmware copy failure
It is dynamic, SSD upgrade failures are avoided, disk is lost.
For the first screening unit 11, for host after issuing firmware upgrade order, SSD receives the mirror image for upgrading
File prepares upgrading, by checking the firmware list Firmware Copy List (Firmware in NOR start-up parameters region
Copy list), it is that read-write all Firmware are copied, and are obtained above-mentioned all Firmware and copied first to filter out read-write properties
The version information of shellfish determines that the Firmware of oldest version is copied according to version information, and determines corresponding Firmware
Block subsequently uses the Firmware Block to carry out firmware upgrade.
Specifically, read-write properties, can be divided into read-only (R) and two kinds of read-write (RW), the Firmware copies of attribute-readable
It can only be read, new image file can not be written and carry out firmware upgrade, specifically, preserving the Firmware of a read only attribute
Copy, can not just change after manufacture, for carrying out system startup after all Firmware copy failure.And it is readable
Writing the Firmware copies of (RW) attribute can be read, and new image file can also be written and carry out firmware upgrade, after being used for
It is continuous to carry out firmware upgrade, ensure SSD firmware upgrades to the best version of performance.
For erasing unit 12, need to wipe the data on target Firmware Block before image file is written,
New image file is written again after erasing finishes.
For writing unit 13, after the data on erasing target Firmware Block, you can by what is received
Image file is written on target Firmware Block, carries out firmware upgrade.
For inspection unit 14, after image file is written to Firmware Block, in fact it could happen that be written successfully
Or two kinds of write-in failure is as a result, it is desirable to check write structure and carry out next step operation according to write-in result.
For starting setting unit 15, if image file is written successfully, according to normal flow by the Firmware
Firmware on Block copies the startup copy new as SSD, by can be using upgrading when starting next time
Firmware copies are started, and entire escalation process is completed.
It includes newly-increased module 51 and startup setup module 52 to start setting unit 15.
Newly-increased module 51, for increasing start-up parameter region newly in NOR, and storage has comprising all in start-up parameter region
Firmware copies physical store address and quantity information, and for determining the Current Boot Copy for starting copy.
Start setup module 52, the Current Boot Copy in modification NOR start-up parameters region are newly written
Firmware is copied.
For increasing module 51 newly, a region is increased newly in the regions NOR：Start-up parameter region, the interior following information of storage：With
In the Firmware Copy Number parameters for indicating all Firmware Copy quantity, start copy for determining
The physical store address of Current Boot Copy parameters and every part of Firmware copies.It can be by reading Firmware
Copy Number parameters understand the particular number of all Firmware Copy, pass through Current Boot Copy parameters and object
Reason storage address is determined carries out startup SSD using that Firmware copies.
For starting setup module 52, after checking that determining new image file write-in is out of question, mirror image text will newly be written
The Firmware copies of part are determined as the new startup copies of SSD, specifically, the Current by changing NOR start-up parameters region
Boot Copy are that the Firmware copies being newly written can.
For returning unit 16, in other situations, if write-in is unsuccessful, returns to erasing unit 12 and select again
Select corresponding Firmware Block write-ins image file.
For running unit 17, the typical Booting sequences of SSD are as follows：After energization, ROM is executed；ROM is loaded from NOR
Bootloader to program Memory jumps to Bootloader operations；Bootloader is swept from storage Firmware Block
It retouches and loads complete portion Firmware and copy program Memory to, and start to execute, complete to start.Specifically, SSD is controlled
Has ROM inside device, the position for starting to execute for energization post code；Have program Memory inside SSD controller, it is outer to load
The place that portion's program executes；The Bootloader (generally 16KB) simplified is stored on NOR, to complete system initialization.
For start unit 18, carried on the Current Boot Copy in NOR start-up parameters region for starting copy
Information, according to Current Boot Copy select the Firmware on corresponding Firmware Block copy started.
For verification unit 19, before activation, the image file to Firmware Block is needed to verify, it is ensured that mirror
As file is complete reliable, can be used for starting SSD.
For the first execution unit 20, after being checked, determines that image file is out of question, then load in Firmware Block
Firmware copy and execute startup, complete SSD and start.
For the second screening unit 21, when the image file on selected Firmware Block is there are when problem, need
It finds and is copied for emergent Firmware, that is, read-write properties are that read-only initial Firmware is copied, using initial
Firmware copies start SSD, ensure that firmware upgrade goes wrong, but SSD data are normal.Finding initial Firmware
After copy, it is denoted as Firmware Copy N.
For changing unit 22, in NOR start-up parameters region, modification Current Boot Copy are Firmware Copy
When N, follow-up SSD start, the initial Firmware copies of load will be given tacit consent to and started, ensureing SSD, at least one can just
The Firmware copies often started, improve the safety of SSD firmware upgrades.
For the second execution unit 23, the corresponding initial Firmware copies of load, and execute startup.
The beneficial effects of the invention are as follows：By the way that the Firmware copies of multiple and different firmware versions are arranged, in firmware updating
When one of them is upgraded, started using the firmware after upgrading successfully if upgrading successfully, if upgrading is unsuccessful
Started using other original Firmware copies, ensure that in firmware upgrade process, at least there is that there are one can be with
The Firmware Solt started are normally used for, ensure that the normal use of SSD, are not in be led because of firmware upgrade failure
The problem of causing SSD not start normally, or even losing disk.
The foregoing is merely the preferred embodiment of the present invention, are not intended to limit the scope of the invention, every utilization
Equivalent structure or equivalent flow shift made by description of the invention and accompanying drawing content is applied directly or indirectly in other correlations
Technical field, be included within the scope of the present invention.
Claims (10)
1. a kind of SSD firmware upgrades guard method, which is characterized in that include the following steps：
Check firmware list, it is that read-write and oldest firmware version Firmware is copied to filter out read-write properties, and determining should
Firmware Block where Firmware copies；
Wipe the Firmware Block；
Image file is written to the Firmware Block；
It checks whether and is written successfully；
If being written successfully, it is set as the Firmware being newly written copies to start copy；
If write-in failure, returns and wipes the Firmware Block steps.
2. SSD firmware upgrades guard method as described in claim 1, which is characterized in that the Firmware that will be newly written
Copy is set as starting copy step, including,
The Current Boot Copy in modification NOR start-up parameters region are the Firmware copies being newly written.
3. SSD firmware upgrades guard method as claimed in claim 2, which is characterized in that the Firmware that will be newly written
Copy is set as after starting copy step, including,
ROM is run, Bootloader is loaded to program Memory and executes
Corresponding Firmware copies are selected according to the Current Boot Copy in NOR start-up parameters region；
Whether correct verify Firmware copies；
If correct, load Firmware and copy and execute；
If incorrect, firmware list is scanned, it is the newest Firmware copies of read-only and firmware version to filter out read-write properties,
It is denoted as Firmware Copy N；
The Current Boot Copy for changing start-up parameter region are Firmware Copy N；
Load Firmware Copy N are simultaneously executed.
4. SSD firmware upgrades guard method as claimed in claim 2, which is characterized in that modification NOR start-up parameters region
Current Boot Copy be newly be written Firmware copy step, including,
Start-up parameter region is increased newly in NOR, and is had in the storage of start-up parameter region and copied physical store comprising all Firmware
Address and quantity information, and for determining the Current Boot Copy for starting copy.
5. SSD firmware upgrades guard method as described in claim 1, which is characterized in that the inspection firmware list filters out
All read-write properties are that read-write Firmware is copied, before the Firmware copy steps for selecting firmware version oldest, packet
It includes,
Multiple Firmware copies are set, and corresponding access limit is set for each Firmware copies, and is different
The firmware version of Firmware copies is different.
6. a kind of SSD firmware upgrades protective device, which is characterized in that including：
First screening unit, for checking firmware list, it is that read-write and firmware version is oldest to filter out read-write properties
Firmware is copied, and determines Firmware Block where Firmware copies；
Unit is wiped, for wiping the Firmware Block；
Writing unit, for image file to be written to the Firmware Block；
Inspection unit is written successfully for checking whether；
Start setting unit, if for being written successfully, is set as the Firmware being newly written copies to start copy；
Returning unit returns for if failure to be written and wipes the Firmware Block steps.
7. SSD firmware upgrades protective device as claimed in claim 6, which is characterized in that the startup setting unit includes opening
Dynamic setup module, the Current Boot Copy for changing NOR start-up parameters region are the Firmware copies being newly written.
8. SSD firmware upgrades protective device as claimed in claim 6, which is characterized in that further include：
Running unit, for running ROM, loading Bootloader to program Memory and executing start unit, for according to NOR
The Current Boot Copy in start-up parameter region select corresponding Firmware copies；
Whether verification unit is correct for verifying Firmware copies；
If first execution unit loads Firmware and copies and execute for correct；
If second screening unit scans firmware list for incorrect, filter out read-write properties be read-only and firmware version most
New Firmware copies, are denoted as Firmware Copy N；
Unit is changed, the Current Boot Copy for changing start-up parameter region are Firmware Copy N；
Second execution unit, for loading Firmware Copy N and executing.
9. SSD firmware upgrades protective device as claimed in claim 7, which is characterized in that the startup setting unit further includes
Newly-increased module for increasing start-up parameter region newly in NOR, and has in the storage of start-up parameter region and is copied comprising all Firmware
Physical store address and quantity information, and for determining the Current Boot Copy for starting copy.
10. SSD firmware upgrades protective device as claimed in claim 6, which is characterized in that further include pre-seting unit, be used for
Multiple Firmware copies are set, and corresponding access limit, and different Firmware are set for each Firmware copies
The firmware version of copy is different.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810569588.0A CN108733517A (en) | 2018-06-05 | 2018-06-05 | SSD firmware upgrades guard method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810569588.0A CN108733517A (en) | 2018-06-05 | 2018-06-05 | SSD firmware upgrades guard method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108733517A true CN108733517A (en) | 2018-11-02 |
Family
ID=63931922
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810569588.0A Pending CN108733517A (en) | 2018-06-05 | 2018-06-05 | SSD firmware upgrades guard method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108733517A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109582225A (en) * | 2018-11-13 | 2019-04-05 | 深圳忆联信息系统有限公司 | A kind of compatible starting of the more particles of SSD, upgrade method and device |
| CN109976958A (en) * | 2019-03-26 | 2019-07-05 | 深圳忆联信息系统有限公司 | Promote the method, apparatus and storage medium of firmware testing efficiency |
| CN111813597A (en) * | 2020-06-08 | 2020-10-23 | 海信（山东）空调有限公司 | Air conditioner |
| CN112199238A (en) * | 2020-10-16 | 2021-01-08 | 深圳佰维存储科技股份有限公司 | Memory firmware updating method and device, storage medium and electronic equipment |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20040008007A (en) * | 2002-07-15 | 2004-01-28 | 에임텍 주식회사 | Method of upgrading firmware for wireless terminal |
| CN1786910A (en) * | 2004-12-09 | 2006-06-14 | 华为技术有限公司 | BIOS on-line upgrading method |
| CN102033790A (en) * | 2010-12-15 | 2011-04-27 | 中兴通讯股份有限公司 | Method and device for upgrading embedded-type system BOOTROM |
| WO2013106276A1 (en) * | 2012-01-15 | 2013-07-18 | Microsoft Corporation | Installation engine and package format for parallelizable, reliable installations |
| JP2014191646A (en) * | 2013-03-27 | 2014-10-06 | Hitachi Kokusai Electric Inc | Firmware update method, television camera device, and monitoring system |
| CN105653299A (en) * | 2014-11-12 | 2016-06-08 | 杭州华三通信技术有限公司 | Firmware upgrade method device |
| US20160299753A1 (en) * | 2015-04-09 | 2016-10-13 | Rex Poway Tseng | Firmware upgrading method for bluetooth electronic scales |
| US20170322798A1 (en) * | 2014-11-26 | 2017-11-09 | Silicon Motion, Inc. | Electronic Device and Method for Firmware Updating Thereof |
-
2018
- 2018-06-05 CN CN201810569588.0A patent/CN108733517A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20040008007A (en) * | 2002-07-15 | 2004-01-28 | 에임텍 주식회사 | Method of upgrading firmware for wireless terminal |
| CN1786910A (en) * | 2004-12-09 | 2006-06-14 | 华为技术有限公司 | BIOS on-line upgrading method |
| CN102033790A (en) * | 2010-12-15 | 2011-04-27 | 中兴通讯股份有限公司 | Method and device for upgrading embedded-type system BOOTROM |
| WO2013106276A1 (en) * | 2012-01-15 | 2013-07-18 | Microsoft Corporation | Installation engine and package format for parallelizable, reliable installations |
| JP2014191646A (en) * | 2013-03-27 | 2014-10-06 | Hitachi Kokusai Electric Inc | Firmware update method, television camera device, and monitoring system |
| CN105653299A (en) * | 2014-11-12 | 2016-06-08 | 杭州华三通信技术有限公司 | Firmware upgrade method device |
| US20170322798A1 (en) * | 2014-11-26 | 2017-11-09 | Silicon Motion, Inc. | Electronic Device and Method for Firmware Updating Thereof |
| US20160299753A1 (en) * | 2015-04-09 | 2016-10-13 | Rex Poway Tseng | Firmware upgrading method for bluetooth electronic scales |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109582225A (en) * | 2018-11-13 | 2019-04-05 | 深圳忆联信息系统有限公司 | A kind of compatible starting of the more particles of SSD, upgrade method and device |
| CN109582225B (en) * | 2018-11-13 | 2022-02-01 | 深圳忆联信息系统有限公司 | SSD multi-particle compatible starting and upgrading method and device |
| CN109976958A (en) * | 2019-03-26 | 2019-07-05 | 深圳忆联信息系统有限公司 | Promote the method, apparatus and storage medium of firmware testing efficiency |
| CN109976958B (en) * | 2019-03-26 | 2022-06-07 | 深圳忆联信息系统有限公司 | Method and device for improving firmware test efficiency and storage medium |
| CN111813597A (en) * | 2020-06-08 | 2020-10-23 | 海信（山东）空调有限公司 | Air conditioner |
| CN112199238A (en) * | 2020-10-16 | 2021-01-08 | 深圳佰维存储科技股份有限公司 | Memory firmware updating method and device, storage medium and electronic equipment |
| CN112199238B (en) * | 2020-10-16 | 2024-05-28 | 深圳佰维存储科技股份有限公司 | Memory firmware updating method and device, storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105094927B (en) | A kind of device firmware upgrade method and apparatus | |
| CN101650662B (en) | Memory device of embedded system and staring method and upgrading of firmware | |
| US8423991B2 (en) | Embedded network device and firmware upgrading method | |
| CN108733517A (en) | SSD firmware upgrades guard method and device | |
| CN102023908B (en) | Method and device for backing up boot program | |
| CN102135927B (en) | Method and device for system booting based on NAND FLASH | |
| US20100058314A1 (en) | Computer System and Related Method of Logging BIOS Update Operation | |
| CN110096300B (en) | FPGA program file backup management system, operation method and upgrading method | |
| CN111562934B (en) | Software system upgrading method based on hot patch, terminal and storage medium | |
| CN101373451A (en) | Computer system for protecting double-basic input /output system program and control method thereof | |
| CN109582332B (en) | System upgrading method and device for Internet camera | |
| CN112015447B (en) | System updating method and device of electronic equipment, electronic equipment and storage medium | |
| CN115357262A (en) | Method for upgrading driver firmware in batch | |
| CN113157303A (en) | Upgrading method, embedded system, terminal and computer storage medium | |
| CN102479124B (en) | Test method | |
| CN114895845A (en) | EMmC data storage control method and embedded mainboard | |
| CN114265603A (en) | System upgrading method and device based on asymmetric partition and electronic equipment | |
| CN117687663A (en) | OTA-based partition dynamic adjustment method, device, equipment and storage medium | |
| US7428635B2 (en) | Method of writing non-volatile memory that avoids corrupting the vital initialization code | |
| CN111124294B (en) | Sector mapping information management method and device, storage medium and equipment | |
| CN113377586A (en) | Automatic server detection method and device and storage medium | |
| CN116301973A (en) | Firmware upgrading method, device, equipment and readable storage medium | |
| CN105278993A (en) | Linux system based drive module upgrading method and apparatus | |
| CN112650513B (en) | Program upgrading method, device, computer equipment and storage medium | |
| CN112764778A (en) | Processing method for remotely upgrading underlying root file system and related equipment |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20181102 |