TWI678658B - Method for updating firmware of data storage device - Google Patents

Abstract

A method for updating firmware of a data storage device, comprising: obtaining a predetermined sequencing mechanism from an electronic fuse, wherein the electronic fuse is placed inside a controller of the data storage device; obtaining a firmware package; The firmware packet obtains a first sorted hash data; performs a hash calculation on the firmware data in the firmware packet to obtain a second hash data; executes the predetermined sorting mechanism on the second hash data to generate a first Two sorted hash data; and if the first sorted hash data is the same as the second sorted hash data, performing firmware update of the data storage device with the firmware data.

Description

   Method for updating firmware of data storage device   

The invention relates to a data storage device and a data storage method, in particular to a data storage device and a data storage method capable of effectively authenticating firmware data.

Flash memory is a universal non-volatile data storage device that is electrically erased and programmed. Take NAND flash as an example, it is often used as a memory card, a universal serial bus flash device (USB flash device), a solid state drive (SSD), and an embedded flash memory. Body module (eMMC), universal flash memory (UFS), etc.

Generally speaking, data storage devices can improve their performance and reliability through firmware upgrades. Firmware updates ensure that data storage devices are kept up-to-date and compatible. However, if the data storage device is updated with incorrect or illegal firmware, it may cause the data storage device to fail to read or write normally, or even cause damage to the data storage device. Therefore, there is a need for a data storage device and a data storage method that can effectively and conveniently authenticate the firmware data to ensure that the firmware data to be updated is legal and correct.

In order to solve the above problems, the present invention proposes a data storage device and a data storage method that can effectively and conveniently authenticate firmware data to ensure that the updated firmware data is correct.

In detail, the present invention provides a secure hash mechanism and a predetermined ordering mechanism for accurately detecting whether the firmware data to be installed is legal and correct. First, the secure hash mechanism encrypts and compresses the firmware data to generate the hash data. Then, the predetermined sorting mechanism reorders the hash data and stores it in a specific location of the data storage device. The above-mentioned predetermined sorting mechanism is set by the manufacturer of the data storage device. By judging whether the firmware data to be installed and its related hash data are the same as the sorted hash data, it is possible to detect whether the firmware data to be installed is the correct and legal firmware certified by the data storage device manufacturer. Profile. According to the data storage device and the data storage method of the present invention, whether the firmware data is correct and legal can be determined to prevent the data storage device from being maliciously damaged.

An embodiment of the present invention provides a method for updating firmware of a data storage device, including: obtaining a predetermined sorting mechanism from an electronic fuse, wherein the electronic fuse is placed inside a controller of the data storage device; Obtain a firmware packet; obtain a first sorted hash data from the firmware packet; perform a hash calculation on the firmware data in the firmware packet to obtain a second hash data; execute the second hash data The predetermined sorting mechanism to generate a second sorted hash data; and if the first sorted hash data is the same as the second sorted hash data, performing firmware update of the data storage device with the firmware data.

An embodiment of the present invention provides a method for updating firmware of a data storage device, including: obtaining a predetermined sorting mechanism from an electronic fuse, wherein the electronic fuse is placed inside a controller of the data storage device; Obtain a firmware packet; obtain a plurality of first-order sub-hash data from the firmware packet; divide a firmware data in the firmware packet into a plurality of sub-firmware data according to a predetermined segmentation mechanism; for each of the Perform a hash calculation on the sub-firmware data to obtain a plurality of sub-hash data; perform the predetermined sorting mechanism on each of the sub-hash data to generate a plurality of second-order sub-hash data; and if the first-order sub-hash data Same as the hash data of the second sorters, the firmware of the data storage device is updated with the firmware data.

An embodiment of the present invention provides a method for updating firmware of a data storage device, including: obtaining a predetermined sorting mechanism from an electronic fuse, wherein the electronic fuse is placed inside a controller of the data storage device; Obtain a firmware packet; obtain a plurality of first-order sub-hash data from the firmware packet; divide a firmware data in the firmware packet into a plurality of sub-firmware data according to a predetermined segmentation mechanism; for each of the Performing a data compression calculation and a hash calculation on the sub-firmware data to obtain a plurality of sub-hash data; performing the predetermined sorting mechanism on each of the sub-hash data to generate a plurality of second-order sub-hash data; and if the first A sorted sub-hash data is the same as the second sorted sub-hash data, and the firmware data is used to update the firmware of the data storage device.

Regarding other additional features and advantages of the present invention, those skilled in the art can, without departing from the spirit and scope of the present invention, use the data storage device and data storage method disclosed in the implementation method of this case.

10A, 10A-1, 10A-2, 10A-3, 10A-4, 20A‧‧‧ firmware information

10B, 10B-1, 10B-2, 10B-3, 10B-4, 10B-5, 10B-6, 10B-7, 20B ‧ hash data

10C, 10C-1, 10C-2, 10C-3, 10C-4, 10C-5, 20C

10D‧‧‧ Other Information

10X‧‧‧Firmware packet

100‧‧‧data storage device

120‧‧‧ Controller

122‧‧‧ E-fuse area

122-1 to 122-8‧‧‧ Specific area

140‧‧‧Flash memory

160-16N‧‧‧block

160A, 160Z ... 16NA, 16NZ‧‧‧ pages

180‧‧‧ random access memory

200‧‧‧host

300‧‧‧ Security hashing mechanism

320‧‧‧ scheduled sorting mechanism

340‧‧‧Scheduled split mechanism

360‧‧‧ scheduled recompression mechanism

Complete disclosure according to the following detailed description and accompanying drawings. It should be noted that, according to the general operations of the industry, the illustrations are not necessarily drawn to scale. In fact, the size of the component may be arbitrarily enlarged or reduced for clarity.

FIG. 1 is a schematic diagram showing a data storage device and a host according to an embodiment of the present invention; FIG. 2A is a schematic diagram showing a data storage method for authenticating firmware data according to an embodiment of the present invention; Figure 2B is a schematic diagram showing a data storage method for authenticating firmware data according to another embodiment of the present invention; Figure 2C is a schematic diagram showing the firmware data according to an embodiment of the present invention; Figure 3 It is a schematic diagram showing a data storage method for authenticating firmware data according to an embodiment of the present invention; FIG. 4 is a diagram showing a data storage method for authenticating firmware data according to another embodiment of the present invention Schematic diagram; FIG. 5A is a schematic diagram showing an electronic fuse area for authenticating firmware data according to an embodiment of the present invention.

FIG. 5B is a schematic diagram showing an electronic fuse area for authenticating firmware data according to another embodiment of the present invention.

FIG. 6 is a flowchart illustrating a data storage method for authenticating firmware data according to an embodiment of the present invention.

FIG. 7 is a flowchart illustrating a data storage method for authenticating firmware data according to another embodiment of the present invention.

FIG. 8 is a flowchart illustrating a data storage method for authenticating firmware data according to another embodiment of the present invention.

FIG. 9 is a schematic diagram showing a data storage method for authenticating firmware data according to another embodiment of the present invention.

In order to make the objects, features, and advantages of the present invention more comprehensible, specific embodiments of the present invention are specifically listed below, and described in detail with the accompanying drawings. The purpose is to explain the spirit of the present invention and not to limit the protection scope of the present invention. It should be understood that the following embodiments can be implemented by software, hardware, firmware, or any combination thereof.

FIG. 1 is a schematic diagram showing a data storage device 100 and a host 200 according to an embodiment of the present invention. In one embodiment, the data storage device 100 includes a controller 120, a non-volatile memory, and a random access memory (RAM) 180. The controller 120 includes an e-fuse region 122. The data storage device 100 is coupled to the host 200 to transmit data and instructions or receive data and instructions. Non-volatile memory can be anti-gate flash memory (NAND Flash), magnetoresistive random access memory (Magnetoresistive RAM), ferroelectric random access memory (Ferroelectric RAM), resistive memory (Resistive RAM, RRAM), Spin Transfer Torque-RAM (STT-RAM), etc., so that data can be stored for a long time. In the following description, the flash memory 140 is taken as an example for description, but is not limited thereto. The data storage device 100 conforms to communication standards such as the embedded flash memory module (eMMC) specification, universal flash memory (UFS), serial ATA (SATA), or non-volatile fast memory (NVMe). The host 200 may be various electronic products such as a mobile phone, a tablet computer, a notebook computer, a navigation system, or a vehicle-mounted system.

As shown in FIG. 1, the controller 120 is coupled to the flash memory 140 and the random access memory 180. The random access memory 180 is used to temporarily store and prefetch the data required by the controller 120, or used to temporarily store the data to be written into the flash memory 140 by the host 200 to speed up the access time of the data storage device 100 . The controller 120 performs a read operation on the flash memory 140 by controlling the flash memory 140 to perform a read operation in units of clusters. In addition, the controller 120 is coupled to the flash memory 140 to transmit data and instructions to each other or receive data and instructions.

The electronic fuse area 122 is mainly used to store important data about the security and access operations of the data storage device 100, such as a second key used to decode a first key. In the normal operation mode, only the controller 120 can read the data stored in the electronic fuse area 122. In the debug mode, the e-fuse area 122 is closed / screened to prevent reading. It should be noted that the firmware data is written into the e-fuse area 122 at one time.

The flash memory 140 includes a plurality of blocks 160 to 16N, where N is a positive integer, such as 2048. In detail, each of the blocks 160 to 16N further includes a plurality of physical pages 160A to 16NZ, where A and Z are positive integers, such as A = 0 and Z = 256. Block 160 includes physical pages 160A ~ 160Z, and block 16N includes physical pages 16NA ~ 16NZ. When the controller 120 performs a data writing or storage operation on the flash memory 140, the controller 120 controls the flash memory 140 to perform data writing or programming operations in units of physical pages.

For the flash memory 140, each of its physical pages 160A-16NZ has a different physical address. In other words, each of the physical pages 160A-16NZ has a physical address, and each of the physical pages 160A-16NZ has a different physical address. When the data storage device 100 performs a write operation, the controller 120 determines a physical address of the flash memory 140 to write or store data. In addition, the controller 120 further records the mapping relationship between the physical address and the logical address of the data. This record is stored in the mapping table H2F. Therefore, for the host 200, the host 200 reads or writes data stored in a certain logical address by the data storage device 100 by using a logical address.

FIG. 2A is a schematic diagram showing a data storage method for authenticating firmware data according to an embodiment of the present invention. The firmware data 10A is generated by a compiler. Then, as shown in FIG. 2A, the firmware data 10A generates a hash data 10B by using a secure hash algorithm (SHA) 300. For example, the firmware data 10A is a hash data 10B with a length of 256 bits by the operation of SHA-256. It should be noted that the above-mentioned SHA is only for illustration and is not intended to limit the present invention.

In one embodiment, the controller 120 receives the firmware data 10A, and performs a secure hash mechanism 300 on the firmware data 10A to generate and receive the hash data 10B. In another embodiment, other devices (such as the host 200) perform a secure hashing mechanism 300 on the firmware data 10A to generate a hash data 10B, and the controller 120 receives the hash data 10B.

In one embodiment, the controller 120 divides the hash data 10B into a plurality of data groups, and sorts the data groups by a predetermined sorting mechanism 320 to generate a sorted hash data 10C. The predetermined sequencing mechanism 320 is stored in the electronic fuse area 122 of the controller 120. For example, the size of the hash data 10B is 8 bytes, and its content is as follows:

Table 1 shows the data for each byte of the hash data 10B. In an embodiment, the controller 120 groups the above 8 byte data to generate a plurality of data groups. For example, the size of each data group is 1 byte, that is, each 1 byte of data becomes a data group. In another embodiment, the size of each data group is 2 bytes, that is, two 1-byte data is a data group. For example, 0x54 and 0x47 in Table 1 are a data group, and 0x28 and 0x00 in Table 1 are another data group. It should be noted that the size of the above data group is only for illustration, and is not intended to limit the present invention. Those skilled in the art can set data groups of other sizes according to the content of the present invention without departing from the spirit and scope of the present invention.

In this embodiment, the size of the hash data 10B is 8 bytes. In another embodiment, the size of the hash data 10B is 32 bytes. If a more complex security hashing mechanism 300 and a predetermined sequencing mechanism 320 are used, or other mechanisms (such as a predetermined partitioning mechanism or a predetermined recompression mechanism) are used, the e-fuse area 122 needs a larger storage capacity to store the above mechanism. The predetermined partitioning mechanism and the predetermined recompression mechanism will be described in detail in FIG. 3 and FIG. 4 respectively.

In this embodiment, each 1 byte of data becomes a data group. In other words, 0x54 in Table 1 is a data group, and 0x28 is another data group. Then, the above-mentioned hash data 10B is sorted in units of data groups by a predetermined sorting mechanism 320 to generate sorted hash data 10C. It should be noted that the predetermined sorting mechanism 300 is stored in a tabular manner in the e-fuse area 122. For example, the predetermined sorting mechanism 300 is shown in Table 2:

The predetermined sorting mechanism 320 changes the address of the content of the hash data 10B. As shown in FIG. 9, 0x54 is changed from the position of Byte 6 to Byte 5, 0x28 is changed from the position of Byte 4 to Byte 1, and 0x47 is changed from The position of Byte 2 was changed to the position of Byte 0, and finally the sorted hash data 10C was generated.

In detail, the data storage method of the present invention provides dual protection mechanisms, namely a secure hash mechanism 300 and a predetermined ordering mechanism 320. The hash data 10B (as shown in Table 1) generated by the secure hashing mechanism 300 is rearranged into sorted hash data 10C (as shown in Table 3) by the predetermined sorting mechanism 320. If a third person wants to update the illegal firmware data to the data storage device 100, the hash data generated by the illegal firmware data through other secure hashing mechanisms will be different from the sorted hash data 10C in this case. Therefore, the controller 120 can judge that the above-mentioned hash data is illegal, and refuse to install or update the illegal firmware data to the data storage device 100.

FIG. 2B is a schematic diagram showing a data storage method for authenticating firmware data according to another embodiment of the present invention. In this embodiment, the sorted hash data 10C and the firmware data 10A form a firmware packet 10X. Then, the predetermined sorting mechanism 320 reversely sorts the sorted hash data 10C to generate the hash data 10B.

In one embodiment, the generation method or storage location of the hash data 10B is set by the manufacturer of the data storage device 100. Since the third person does not know the generation method or storage location of the hash data 10B, the controller 120 can detect whether the other firmware data is legal and correct. Therefore, the data storage method of the present invention can avoid installing or updating illegal firmware data, so as to ensure that the data storage device 100 will not be maliciously damaged.

In one embodiment, the predetermined sorting mechanism 320 is set by a manufacturer of the data storage device 100. For example, a third person learns the secure hash mechanism 300 from illegal means, and knows the storage location of the hash data 10B, and forms another firmware data with the hash data 10B to form a firmware package. The other firmware data is updated to the data storage device 100. Since the third person does not know the predetermined sorting mechanism 320, the firmware packet contains the hash data 10B, rather than the sorted hash data 10C generated through the predetermined sorting mechanism 320. Therefore, the controller 120 can easily determine that the sorted hash data 10C is different from the hash data 10B, and further determine that the firmware data is illegal, and refuse to install or update the illegal firmware data to the data storage device 100. In order to prevent the data storage device 100 from being maliciously damaged.

FIG. 2C is a schematic diagram showing firmware data according to an embodiment of the present invention. As shown in FIG. 2C, in one embodiment, the sorted hash data 10C is stored on the firmware data 10A. In addition, the firmware data 10A stores other firmware-related data 10D. In other words, the firmware packet 10X includes firmware data 10A, sorted hash data 10C, and other data 10D. For example, the other data 10D includes the firmware version, the version of the security hash mechanism 300, and other security information that the customer wants to store. It is conceivable that the sorted hash data 10C can also be stored under the firmware data 10A.

When the data storage device 100 receives the firmware packet 10X, the controller 120 performs a secure hash mechanism 300 on the firmware data 10A of the firmware packet 10X to obtain the hash data 20B, and then executes a predetermined sorting mechanism 320 to obtain the sorted hash data. 20C. In one embodiment, the controller 120 compares the sorted hash data 20C with the sorted hash data 10C stored in the firmware packet 10X. If the comparison result is the same, it means that the firmware data 10A is legal and correct. If the comparison result is different, it means that the firmware data 10A is illegal.

In another embodiment, when the storage device 100 receives the firmware packet 10X, the controller 120 performs a secure hash mechanism 300 on the firmware data 10A of the firmware packet 10X to obtain the hash data 20B. Then, the controller 120 performs a reverse ordering sorting mechanism 320 on the sorted hash data 10C stored in the firmware packet 10X to obtain the hashed data 10B. Then, the controller 120 compares the hash data 20B and the hash data 10B stored in the firmware packet 10X. If the comparison result is the same, it means that the firmware data 10A is legal and correct. If the comparison result is different, it means that the firmware data 10A is illegal.

FIG. 3 is a schematic diagram showing a data storage method for authenticating firmware data according to an embodiment of the present invention. In this embodiment, the data storage method further includes a predetermined segmentation mechanism 340 to promote authentication of the firmware data and improve security. As shown in FIG. 3, the predetermined segmentation mechanism 340 divides the firmware data 10A into four firmware data 10A-1, 10A-2, 10A-3, and 10A-4 (that is, sub-firmware data). In other words, the sum of the four firmware data 10A-1, 10A-2, 10A-3, and 10A-4 is the original firmware data 10A.

It should be noted that the segmentation of the above 4 pieces of firmware data 10A-1 to 10A-4 is only for illustration, and is not intended to limit the present invention. Those skilled in the art can divide the firmware data into other quantities based on the content of the present invention without departing from the scope of the present invention.

Then, the secure hashing mechanism 300 performs a hash operation on the four firmware data 10A-1, 10A-2, 10A-3, and 10A-4, and generates four hash data 10B-1, 10B-2, and 10B-3, respectively. And 10B-4 (that is, the child hash). The sum of the four hash data 10B-1, 10B-2, 10B-3, and 10B-4 is the hash data 10B.

In one embodiment, the predetermined sorting mechanism 320 sorts the four hash data 10B-1, 10B-2, 10B-3, and 10B-4, and generates four sorted hash data 10C-1, 10C-2, 10C-3 and 10C-4. The sum of the 4 sorted hash data 10C-1, 10C-2, 10C-3, and 10C-4 is the sorted hash data 10C. In another embodiment, the predetermined sorting mechanism 320 sorts all four hash data 10B-1, 10B-2, 10B-3, and 10B-4 at the same time, and generates a sorted hash data 10C.

FIG. 4 is a schematic diagram showing a data storage method for authenticating firmware data according to another embodiment of the present invention. In this embodiment, the data storage method further includes a predetermined recompression mechanism 360 for encrypting and compressing the firmware data 10A more than twice to promote authentication of the firmware data 10A and improve security. As shown in FIG. 4, the predetermined segmentation mechanism 340 divides the firmware data 10A into four firmware data 10A-1, 10A-2, 10A-3, and 10A-4.

Then, a predetermined recompression mechanism 360 is arranged to perform multiple compressions (i.e., more than two encryptions and compressions) on the four firmware materials 10A-1, 10A-2, 10A-3, and 10A-4. As shown in FIG. 4, the predetermined recompression mechanism 360 arranges the firmware data 10A-1 and 10A-2 into one group, and arranges the firmware data 10A-3 and 10A-4 into another group. Then, the two sets of firmware data are encrypted and compressed by the secure hash mechanism 300, and two hash data 10B-5 and 10B-6 (the first sub-hash data) are generated respectively. In other words, the hash data 10B-5 is generated from the firmware data 10A-1 and 10A-2, and the hash data 10B-6 is generated from the firmware data 10A-3 and 10A-4.

Then, as shown in FIG. 4, the two hash data 10B-5 and 10B-6 are compressed a second time by the secure hash mechanism 300 to generate a hash data 10B-7 (second sub-hash data). Then, in this embodiment, the predetermined sorting mechanism 320 sorts the hash data 10B-7, and generates a sorted hash data 10C-5. Since this embodiment uses the security compression mechanism 300 more than twice, the reliability and accuracy of identifying whether the firmware data is correct can be further improved.

It should be noted that the segmentation and secondary compression of the above 4 pieces of firmware data 10A-1 to 10A-4 are for illustration only, and are not intended to limit the present invention. Those with ordinary knowledge in the technical field may divide into other quantities of firmware data or perform other times of encryption and compression according to the content of the present invention without departing from the scope of the present invention.

FIG. 5A is a schematic diagram showing an electronic fuse area 122 for authenticating firmware data according to an embodiment of the present invention. In one embodiment, the e-fuse region 122 includes a plurality of specific regions 122-1 to 122-8 for storing specific data, respectively. As shown in FIG. 5A, the predetermined sorting mechanism 320 is stored in the specific area 122-1. In other words, the specific area 122-1 can only be used to store the predetermined sorting mechanism 320, and cannot store other mechanisms or other data. In addition, the above-mentioned predetermined sorting mechanism 320 is written into the e-fuse area 122 at a time, and only the controller 120 can read it.

FIG. 5B is a schematic diagram showing an electronic fuse area for authenticating firmware data according to another embodiment of the present invention. In some embodiments, the data storage method includes a predetermined partitioning mechanism 340 and a predetermined recompression mechanism 360 in addition to the predetermined sorting mechanism 320. It should be noted that if one or more of the above mechanisms are more complicated, two or more specific areas may be used to store one mechanism. As shown in FIG. 5B, the predetermined sorting mechanism 320 is stored in the specific region 122-1, the predetermined partitioning mechanism 340 is stored in the specific region 122-2, and the predetermined recompression mechanism 360 is stored in the specific region 122-3.

FIG. 6 is a flowchart illustrating a data storage method for authenticating firmware data according to an embodiment of the present invention. In step S602, the controller 120 reads the predetermined sequencing mechanism 320 from the e-fuse area 122. Then, in step S604, the controller 120 obtains the firmware data and the related first sorted hash data, wherein the firmware data and the first sorted hash data are obtained from the firmware packet. In step S606, the controller 120 executes the secure hashing mechanism 300 on the firmware data to generate the second hash data. In step S608, the controller 120 executes a predetermined sorting mechanism 320 on the second hash data to generate a second sort hash data. In step S610, the controller 120 determines whether the second sorted hash data is the same as the first sorted hash data. If the comparison result is negative, step S614 is executed to terminate the execution of the data storage method of the present invention for authenticating firmware data. If the comparison result is yes, step S612 is performed, and the controller 120 updates the firmware of the data storage device 100 with the firmware data. It can be seen that in step S610, by determining whether the second sorted hash data is the same as the first sorted hash data obtained in step S604, it is possible to detect whether the firmware data to be installed is the manufacture of the data storage device 100. The correct and legal firmware information certified by the company. According to the data storage device and the data storage method of the present invention, whether the firmware data is correct and legal can be determined to protect the data storage device 100.

In another embodiment, step S608 can be changed to the controller 120 to perform a reverse ordering mechanism 320 on the first sorted hash data to generate the first hash data; step S610 can be changed to the controller 120 to determine whether the second hash data is the same For the first hash information. The main difference between this embodiment and the above-mentioned embodiment lies in the reasons for executing the predetermined sorting mechanism 320 and the execution method. If the target is the second hash data, a predetermined sorting mechanism 320 is performed on the second hash data. If the target is the first sorted hash data, a reverse predetermined sorting mechanism 320 is performed on the first sorted hash data. The remaining steps are the same.

FIG. 7 is a flowchart illustrating a data storage method for authenticating firmware data according to another embodiment of the present invention. In step S702, the controller 120 obtains a predetermined sequencing mechanism 320 from the e-fuse area 122. In step S704, the controller 120 receives the firmware data and the first sorted hash data, wherein the firmware data and the first sorted hash data are obtained from the firmware packet, and the first sorted hash data includes a plurality of first sub-sorts. Hash information. In step S706, the controller 120 divides the firmware data into a plurality of second sub-firmware data by using a predetermined division mechanism. In step S708, the controller 120 executes the security hashing mechanism 300 on each of the plurality of second sub-firmware data to generate a plurality of second sub-hash data. In step S710, the controller 120 performs a predetermined sorting mechanism 320 on each of the second sub-hash data to generate a plurality of second-order sub-hash data. In step S712, the controller 120 determines whether the second sorting sub-hash data is the same as the first sorting sub-hash data. If the comparison result is negative, the execution of the data storage method for authenticating firmware data of the present invention is suspended. If the comparison result is yes, step S714 is executed, and the controller 120 updates the firmware of the data storage device 100 with the firmware data.

FIG. 8 is a flowchart illustrating a data storage method for authenticating firmware data according to another embodiment of the present invention. In this embodiment, steps S802 to S806 are the same as steps S702 to S706 in FIG. 7, so they are not repeated here. In step S808, the controller 120 performs a predetermined recompression mechanism 360 and a security hash mechanism 300 on each of the plurality of second sub-firmware data to generate a plurality of second sub-hash data. The predetermined recompression mechanism 360 is stored in a third specific area of the e-fuse area 122.

Then, in step S810, the controller 120 performs a secure hashing mechanism 300 on each second sub-hash data to generate a third sub-hash data. In step S812, the controller 120 executes a predetermined sorting mechanism 320 on the third sub-hash data to generate a second order sub-hash data. In step S814, the controller 120 determines whether the second sorting sub-hash data is the same as the first sorting sub-hash data. If the comparison result is no, step S818 is executed to terminate the execution of the data storage method of the present invention for authenticating firmware data. If the comparison result is yes, step S816 is performed, and the controller 120 updates the firmware of the data storage device 100 with the firmware data.

In another embodiment, the firmware data 10A may also be encrypted by using an encryption mechanism, such as an Advanced Encryption Standard (AES) or an RSA encryption algorithm, to generate the encrypted data 10B. .

The method of the present invention, or a specific form or part thereof, may exist in the form of a code. The code can be stored in physical media, such as floppy disks, CD-ROMs, hard disks, or any other machine-readable (such as computer-readable) storage media, or it is not limited to external computer program products. When the code is loaded and executed by a machine, such as a computer, the machine becomes a device for participating in the invention. The code can also be transmitted through some transmission media, such as wire or cable, optical fiber, or any transmission type. Where the code is received, loaded, and executed by a machine, such as a computer, the machine becomes used to participate Invented device. When implemented in a general-purpose processing unit, the code in combination with the processing unit provides a unique device that operates similar to an application-specific logic circuit.

The ordinal numbers in this specification and the scope of patent application, such as "first", "second", "third", etc., do not have a sequential relationship with each other, they are only used to indicate that two have the same Different components of the name. The term "coupled" in the present specification refers to various direct or indirect electrical connection methods. Although the present invention is disclosed as above with a preferred embodiment, it is not intended to limit the scope of the present invention. Any person skilled in the art can make some modifications and decorations without departing from the spirit and scope of the present invention. The protection scope of the present invention shall be determined by the scope of the attached patent application.

Claims (9)

A method for updating firmware of a data storage device, comprising: obtaining a predetermined sequencing mechanism from an electronic fuse, wherein the electronic fuse is placed inside a controller of the data storage device; obtaining a firmware package; The firmware packet obtains a first sorted hash data; performs a hash calculation on the firmware data in the firmware packet to obtain a second hash data; executes the predetermined sorting mechanism on the second hash data to generate a first Two sorted hash data; and if the first sorted hash data is the same as the second sorted hash data, performing firmware update of the data storage device with the firmware data; wherein the predetermined sorting mechanism adjusts the second hash data Sequence of plural data groups. The firmware updating method according to item 1 of the patent application scope, wherein the firmware packet is obtained from a memory device. The firmware updating method according to item 1 of the scope of the patent application, wherein the first sorted hash data and the second sorted hash data have the same data length. The firmware update method according to item 1 of the scope of the patent application, wherein the firmware data is stored in a memory device of the data storage device to complete the firmware update of the data storage device. A method for updating firmware of a data storage device, comprising: obtaining a predetermined sequencing mechanism from an electronic fuse, wherein the electronic fuse is placed inside a controller of the data storage device; obtaining a firmware package; The firmware packet obtains a plurality of first-order sub-hash data; divides a piece of firmware data in the firmware packet into a plurality of sub-firmware data according to a predetermined segmentation mechanism; and performs a hash on each of the sub-firmware data Calculating to obtain a plurality of sub-hash data; performing the predetermined sorting mechanism on each of the sub-hash data to generate a plurality of second-order sub-hash data; and if the first-order sub-hash data is the same as the second sort-hash data The hash data is used to update the firmware of the data storage device using the firmware data; wherein the predetermined ordering mechanism adjusts the sequence of the plural data groups in each of the sub-hash data. The firmware updating method according to item 5 of the patent application scope, wherein the firmware packet is obtained from a memory device. The firmware updating method as described in item 5 of the scope of the patent application, wherein each of the first sorter hash data and each of the second sorter hash data have the same data length. The firmware updating method according to item 5 of the scope of the patent application, wherein the firmware data is stored in a memory device of the data storage device to complete the firmware update of the data storage device. A method for updating firmware of a data storage device, comprising: obtaining a predetermined sequencing mechanism from an electronic fuse, wherein the electronic fuse is placed inside a controller of the data storage device; obtaining a firmware package; The firmware packet obtains a plurality of first-order sub-hash data; divides a piece of firmware data in the firmware packet into a plurality of sub-firmware data according to a predetermined segmentation mechanism; and executes a data for each of the sub-firmware data Compression calculation and a hash calculation to obtain a plurality of sub-hash data; performing the predetermined sorting mechanism on each of the sub-hash data to generate a plurality of second-order sub-hash data; and if the first-order sub-hash data is the same as the The second sorted sub-hash data is used to update the firmware of the data storage device using the firmware data; wherein the predetermined sorting mechanism adjusts the order of the plural data groups in each of the sub-hash data.