TW594571B - Upgrade control method of intelligent firmware - Google Patents

Abstract

The present invention provides an upgrade control method of intelligent firmware, which includes: generating a hardware confirmation code; generating a firmware confirmation code; and upgrading firmware program based on the inspection and comparison between the hardware confirmation code and firmware confirmation code. A set of encoding scheme capable of managing the software/hardware version of product is employed to inspect the firmware confirmation code and compare the hardware confirmation code based on the encoded data, and check the integrity and correctness for the firmware upgraded by the user, so as to ensure that the firmware files are not modified due to carelessness or deliberation and are matched with hardware specification, thereby avoiding burning improper firmware version into the product. Furthermore, before upgrading the firmware, it is able to detect whether the system resource is sufficient to complete the upgrade process, so as to avoid a failure during the upgrade process.

Description

594571 V. Description of the invention α) --- [Field of the invention] The present invention relates to a program upgrade control method, in particular to an intelligent firmware upgrade control method. [Background of the Invention] The software on the read-only memory in which the blade body γ is written in the hardware of the device contains computer programs and data that cannot be changed in the user's environment. It is one of the most critical components of the lightning brain system. Body again. After a product is launched, it is often necessary to update the firmware in the product due to the addition of new features or the correction of original errors. Therefore, upgrading the firmware in hardware products has become the current development trend. It is an effective method to extend the life of hardware products. It is an investment protection for users and it also makes the hardware more durable. ', —However' there are two conflicting requirements for the upgrade of the moving body: (the work should be well protected, once it is destroyed after modification, the entire system does not work; (2) it should be easy It is modified to allow real-time upgrades, and to improve or clear software faults. ▲ When performing the initial upgrade, you should be very careful and consider that the process of upgrading and modification is very easy. However, if an operation error occurs accidentally in this ^ 2 5 or the incorrect firmware 2 is upgraded, the consequences will be very serious, and sometimes it will cause the entire system. However, existing firmware upgrades provide any Prevention mechanism and control mistakes, or in the selection process, did not address the above-mentioned dangerous control methods, users often operate the wrong firmware version and cause upgrades

594571 V. Description of the invention (2) Failure or even system failure. [Objective and Summary of the Invention] The present invention is to provide an intelligent firmware upgrade control method in order to solve the above problems. The main purpose of the invention is to use a set of encoding methods that can manage the software and hardware versions of the product. The integrity and correctness of the firmware upgraded by the user are checked to ensure that the firmware file has not been modified due to negligence or human or animal will, and that it matches its hardware specifications to prevent the improper firmware version from being burned into the product At the same time, before the firmware upgrade, you can & detect whether the system resources are sufficient to complete the upgrade and prevent the upgrade from failing midway. ^ The present invention provides a smart firmware upgrade control method, which includes: generating a firmware identification code by identifying the ^ I code; and upgrading the firmware program based on a verification comparison of the firmware confirmation code and the bathroom confirmation code. 〃 In order to explain the details of the present invention, the structural features, and the functions of the present invention, as follows: [Detailed description of the implementation examples] The intelligent body upgrade control method disclosed by Γ Γ has been designed into two types: :: ϊ Ϊ = encoding method of version. The product version is divided into software-related versions, hardware versions " and software upgrade-related ones. The following is a description of a preferred embodiment: Its rough cooking version is used to identify the compatibility between hardware and moving bodies.

V. Description of the invention (3)

Yender / Product ID

V C P Η

Weigh

Vender / Product ID: It is used to identify the manufacturer and product name. V ·· Use 1 byte to record the manufacturer information. C · Use a 1-bit group to record CPU data. Since the CPU is an important component in the product, different CPUs will use different firmware versions. Tuple records P · Use 1 byte to record product code data. Η ·· Use 1 byte to record hardware (circuit board) data. R: 1 byte is reserved for future extended use. For example: ν Companies usually issue hardware components (such as CPUs) with screens. "Zhan Ge Yue 糸 / quote"… maybe it is expected that the hardware version of the block (the H road board has different modifications) .All can be done by ϊίϋ !. At the same time, if it is foundry for other manufacturers, it can also be used by V in the hardware version (manufacturer can also be used by customers, avoiding producing 0 ^ j ^; Vender) fields for Α customers. Different. In order to protect their own rights and the rights of foundry customers / customers, they can be burned into the production of customer B, accounting for 594,571. 5. Description of the invention (4) 2. Software version: used on the same hardware, different firmware versions. The difference between the data formats includes the following fields:

plus). BBB's first byte · Fixed important program error (BUG). BBB's second and third bytes: Fixed minor bug (BUG). CC: Special versions are recorded in one byte (such as different OEM customers or versions made for specific purposes). For example: Edge A B B B C 1 0 3 4 0 1 'Cao. Please refer to "Fig. 1" for the flow chart of the upgrade control method of the intelligent firmware of the present invention. First, generate a hardware confirmation code (step 1 0 1); then, generate a firmware confirmation code (step 10 2); and finally, upgrade the firmware program based on the comparison between the firmware confirmation code and the hardware confirmation code. (Step 1 0 3) ° Please refer to "Picture 2" for the flow of generating the hardware confirmation code of the present invention

5W / i Fifth, the invention description (i '--- ~ ---- Chengtu. Ying Zhi. (Step' confirm the hardware version code (step 2 〇 1): determine the password confirmation two ΐΛ〇2); OK Fill in the code (Salt) (step 203); then, calculate the unitary method (step 204); then, according to the algorithm, add m 4 to each code value and use the result as a hardware confirmation code (step 2 0 5); Finally, write the hardware confirmation code of 填, ^, ^ together into the hardware (step 206). The password is saved by the product developer and is not public. The code added with 2 4 (Salt) is randomly generated. , And each time the operation is performed = "produced once, 'every time is different', so the calculated hardware is indeed = :, which will be different, so you need to add the code used for this operation to add the hardware of the result The stone identification code is written into the product hardware for verification and comparison when upgrading the blade body. The algorithm can use various algorithms. In this embodiment, the "hardware version code" is used. " "Password" and "Fill Code" constitutes the final hardware confirmation code according to each byte XOR, which is simple, fast, and has The advantages of security, etc. The following is an example: Shi M »GIGABYTE 4 0 1 G c B 1 0 (HEX Street (M7 (M9 047 (Ml (M2 0x59 0x54 M5 0x30 oei 0x47 (M3 (M2 0x31 _ XCR ⑽1 ⑽2 0 ^ 3 _ 0x05 Secret (M) 7 (M) 8 _ (kOA OxDB QxOC OxOD (M) E QxOF (MO XCR Filling force σδ Horse (Salt) (kOA QxOA QxOA (kOA QxOA QxOA QxOA QxOA QxOA QxOA QxOA QxOA (kOA QxOA (kOA QxOA m confirmation code Qx4C (Ml (k4E 0x4F (k4D 0x55 0x59 (M7 mi 030 0x30 (k41 om (M6 lai 0x2 ^

594571 V. Description of Invention (6)

The writing the filling code and the hardware confirmation code together into the hardware may be burning it into a piece of non-volatile memory in the hardware, such as CPLD (Complex Programmable Logic Device, complex programmable logic device) ) Or EEPROM (Electrically Erasable

Programmable Read Only Memory). Please refer to "Figure 3" for the flow chart of generating the firmware confirmation code of the present invention. First, fill in the software version code and hardware version code (step 301), calculate the difference and fill in the hardware confirmation code and fill-in code (step 3 002); calculate and fill the checksum of the whole firmware audit ( Checksum) (step 303), fill in randomly generated random numbers in the unused space (step 304) ° where 'can be a fixed hardware version and password value, and the padding code generated by the random numbers (S a 11) to calculate the hardware confirmation code. Because each time a different padding code is used, a different hardware confirmation code is generated, and then the padding code and the hardware confirmation code are stored in the firmware confirmation code, which can increase the difficulty of cracking the hardware confirmation code. Calculate the checksum (Checksum), you can choose different checksum (Checksum) algorithm. In this embodiment, the entire firmware content that has been filled in the hardware confirmation code is generated as a byte in the form of X 0 R. Confirmation code. Fill in the unused space with random numbers, the purpose of which is to increase the difficulty of cracking the hardware confirmation code. Since each "Sa 11" is random number, the generated hardware confirmation code and random number are impossible. Resolution, in the unused space

Page 9 594571

After filling in random numbers, a malicious person trying to crack the hardware version will report a difficulty by observing the firmware file to crack the hardware version algorithm. '' The data format of the complete firmware confirmation code is: 0 1 1 丨 2 丨 3 4 5 6 7 TfTTT B c DEF 20h Vi 1 1 ender / Product ID V c PHR 30h CS Rand 1 salt H (version (20h- 2Fh)? K ey, salt (: 33h) 40h Software Dynamic Version | Rand2%

Vender / Product ID: Used to identify the product manufacturer and product name

V: Use 1 byte to record the manufacturer information. C: Use 1 byte to record the data of the central processing unit (CPU). Since the central processing unit (CPU) is an important component in the product, different central processing units (c PU) will use different firmware versions. Byte Record. P: Use 1 byte to record the product code information. Η: Use 1 byte to record hardware (circuit board) data. R: 1 byte is reserved for future extended use.

C S · Use 1 byte to record n c h e c k s u m '' data.

Sal t ·· Use 1 byte to record "Sal t" data. Η (): Use 1 byte to record hardware confirmation code data.

Software dynamic version: Use 6 bytes to record software version data.

Page 10 594571 V. Description of the invention (8) R a n d 1, R a n d 2: Fill in random numbers in the unused space. The following uses an example to explain the process of generating the firmware confirmation code. 1. Enter the software plaintext version, and the hardware plaintext version. 0 1 2 3 4 5 6 7 8 9 ABCDEF 20h GIGABYTE 4 0 1 GCB 1 30h (40h 1 0 1 2 3 4 Calculate and fill in the hardware confirmation code version, fill in the code (Sa 11) 0 1 2 3 4 5 6 7 8 9 ABCDEF 20h GIGABYTE 4 0 1 GCB 1 0 30h salt H (version (20h-2Fh), key, salt (33h)), 40h 1 0 1 2 3 4 Calculate and fill in the checksum of the complete weird body slot case (checksum 0 1 2 3 4 5 6 7 8 9 ABCDEF 20h GIGABYTE 4 0 1 G c B 1 M 3 Oh CS salt H (version (20h-2Fh), key, salt (33h)) 40h 1 0 1 2 3 4

Page 11 594571 V. Description of the invention (9) 4. Fill in the unused space with a randomly generated simple L number.

Rand2 ~ ▲, please refer to "Figure 4", according to the present invention's verification and comparison based on the firmware confirmation code, the process of upgrading the firmware program is sufficient to confirm that the code system is 1 and the system resources are sufficient to store and load the new firmware. (Step ^ Figure. First, make sure that the new firmware is loaded (Step 402), and check the calibration of the new firmware); then, (Checks ·) is correct (Step 403); The data in the product matches with the product's hardware in the bean and early knife body ▲ 丄 U 4), compared with the hardware confirmation code of the nose and the 吝 >, human, and moon bean exactly side code (step 40 5 ); Roots. Dagger ratio: "# 果 'flashes the new firmware file to the question memory (n = h Memory), and automatically restarts (step 4 06). When the user is notified that the system resource is insufficient, M displays a warning If the verification result of the message 卞 ... informs the user ^ new ^ ^ if the result is not green, a warning message will also be displayed. [Achieved effect] The present invention is a known beneficial effect of the 9 · W firmware upgrade control method It can reach 594571. V. Invention Description (10) '--- 1 The case of ¥ blade body slot was confirmed by Checksum to ensure that the content of the file will not be modified by intentional or negligence. 2. By comparing the loaded firmware with the internal version of the hardware, you can determine whether the firmware version matches the hardware specifications and product type. Prevent users from intentionally or unintentionally upgrading the incorrect version. 3. Load firmware Before the file is saved, it will first detect whether the system resources (such as memory space) are sufficient and proactively remind the user to avoid upgrading failure due to insufficient system resources. 4. Easy to identify the firmware version, which can be directly identified in the firmware Firmware This' applicable product type and hardware specifications will not jeopardize the accuracy of the Wei blade upgrade. 5. For trying to crack the hardware confirmation code to upgrade the illegal Wei blade (using the customer's firmware, burn to B Users in the product) are designed with multiple mechanisms to protect the firmware file. (1) The entire firmware file has a checksum. Any changes to the data in it will cause a checksum calculation error. (2) The algorithm for calculating the hardware confirmation code requires a set of passwords. This password is not public. (3) Since each calculation uses a random random number Sa 11, the hardware confirmation code generated each time and Random random numbers are indistinguishable, and unused spaces in the firmware are filled with random numbers. Except for the hard and soft versions of the plain text, it will be difficult to guess which bytes are the hardware confirmation code and the addition code (S a 11 ), It will increase the difficulty of cracking the hardware confirmation algorithm. # 6, You can flexibly change the hardware confirmation code algorithm and checksum algorithm as needed. If you consider effective and fast, you can

Page 13 594571 V. Description of the invention (11) Use XOR calculation. If you need stronger security considerations, you can use more complicated calculation methods, such as MD5 or other cryptographic methods. Although the present invention is disclosed above with the foregoing preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some modifications and retouching without departing from the spirit and scope of the present invention. The scope of protection of the invention shall be determined by the scope of the attached patent application.

Page 594571 Brief description of the diagram. The first diagram is a flowchart of the intelligent firmware upgrade control method of the present invention. The flowchart of the diagram, and the verification with the hardware confirmation code. The second diagram is the generation of the present invention. Figure 3 of the hardware confirmation code is a flowchart of generating a firmware confirmation code of the present invention. Figure 4 is a flowchart of upgrading the firmware program according to the firmware confirmation code verification and comparison of the present invention. [Illustration of graphical symbols] Step 1 0 1 Step 1 0 2 Step 1 0 3 Step 201 Step 2 0 2 Step 2 0 3 Step 2 0 4 Step 2 0 5 Step 2 0 6 Step 3 0 1 Step 302 Step 3 0 3 Step 3 0 4 Generate a hardware confirmation code. Generate a moving body confirmation code. According to the firmware confirmation code and comparison, upgrade the firmware. Determine the hardware version code. Determine the password and add code. (S a 11 Determine the algorithm. As the hardware confirmation code, you will add the code and hardware confirmation to fill in the software version code and calculate and fill in the hardware confirmation calculation and fill in the complete and complete (Checksum) checksum calculation of the number of hardware confirmation codes in the unused space. The result identification code is written into the hardware version code identification code and the checksum of the code file.

Page 594 571 Brief description of the diagram Step 401 Determine the system Step 402 Load the new firmware Step 403 Check whether the new firmware is correct Step 404 Confirm by the new firmware product Hardware Hardware Step 4 0 5 Compare to the storage of the meter Step 406 Calculate the code according to the data burned to the fast 5 and sufficient resources to store the checksum (Checksum) of the new firmware loaded. It is the data in the firmware confirmation code combined with the original filling code stored in the firmware to calculate the code. If the calculated hardware confirmation code is the same as the product hardware confirmation code and compare the results, restart the new firmware file flash memory (F 1 ash M em 〇ry).

Page 16

Claims (1)

• An intelligent firmware upgrade control method, including: generating a hardware confirmation code; generating a firmware confirmation code; and a firmware program based on a check ratio of the moving body confirmation code and the hardware confirmation code. Regarding the "upgrade", the intelligent firmware upgrade method described in item i of the scope of the patent application, wherein the steps of generating the hardware confirmation code are more inclusive: 4 steps: 1. Have the following steps to determine the hardware version code; determine the password; confirm Fill in the code; Determine the algorithm; Compute the code values according to the algorithm to recognize the code; and ,,,, and σ as the hardware Make sure that the fill code and the hardware confirmation code are written into the hard-to-finish range. The above-mentioned wisdom is described in the method of generating toughness & π into α pk system: 4 steps to generate the initial body real encounter code include the following steps: / Ma pregnant body version code and hardware version code; calculate and Fill in the hardware confirmation code and: = write, == in the body slot case; and ^ t It # # .J m @ $, which is based on the hardware confirmation code and hardware: Yes: code level pair 'upgrade firmware program The steps include the following steps: Make sure that the system resources are sufficient to store the new firmware loaded; load the new firmware; verify that the checksum of the new firmware is correct; confirm the firmware of the new firmware with the firmware of the new firmware The data is matched with the original filling code stored in the hardware of the hired goods to calculate the hardware. Confirmation code; Compare whether the calculated hardware confirmation code is the same as the hardware confirmation code stored in the product hardware and software; and burn the new firmware file to the flash Lu Jiyi body based on the checksum comparison result And restart automatically. For example, the smart plastic firmware upgrade control method described in item 2 or item 3 of the patent scope is declared, wherein the data format of the hardware version code is: Vender / Product ID V cTF l Η Among them, Vender / Product ID: used to identify the product manufacturer and product name; V: use 1 byte to record the manufacturer's information; C · use 1 byte to record the central processing unit (cpu ) Data, because the central processing unit (CPU) is an important component in the product, different central processing units (CPU) will use different firmware versions, so recorded in i-bytes; 594571 6. Scope of patent application P • Use 1-value tuple to record product code data; use 1-junction tuple to record hardware (circuit board) data; and & reserve 1-byte for future extended use. As described in item 3 of the patent scope, the intelligent firmware upgrade control method No. 8 described in the data format of the software version code is: BC where A: record the main version with one byte; =: Ϊ one byte: correct important program errors ⑽G); ⑽G: brother two third byte: correction: owed program error CC: use one Byte Record Special Edition. As described in the patent application scope item i, item 3 or item 4, the firmware upgrade control method, wherein the firmware confirms that 9 :, early blade is · J negative material type 0 1 2 3 4 5 6 7 8 9 A 20h Vender / ProductID 30h CS Randl salt H (version (20h-2Fh), key, 40h Software E) ynamic Version Rand2 HR Page 19 594571 6. Scope of Patent Application Among them, Vender / Product ID ·· Used to identify the product manufacturer and product name, V uses 1 byte to record manufacturer data; C uses 1 byte to record central processing unit (CPU) data; P uses 1 byte Record product code information; Η Use 1 byte to record hardware (circuit board) information; R reserves 1 byte for future extended use; CS: Use 1 byte to record π checksum &data; Sa 11: Use 1-byte to record the data of "add code"; Η (): Use 1-byte to record the hardware confirmation code data; Software dynamic version: Use 6-byte to record the software version data; and Randl, Rand2: Not used Fill in random numbers in the space. 8 · The intelligent firmware upgrade control method as described in item 2, 3, or 4 of the scope of patent application, wherein the filling code is generated randomly and automatically, and it is generated randomly once for each operation, and each time the same. 9 · Smart and flexible as described in the scope of patent application No. 2, 3 or 4 Volume upgrade control method, wherein the algorithm used for the calculation is X0R operation. I 〇 The intelligent firmware upgrade control method according to item 2, 3, or 4 of the scope of patent application, wherein the calculation algorithm used is MD5 operation. II · Intelligent firmware upgrade control method as described in item 2 of the scope of patent application Page 20 594571 6. The scope of the patent application, where writing the fill code and the hardware confirmation code together into the hardware is to burn them together into a piece of non-volatile memory in the hardware. 12 The intelligent firmware upgrade control method according to item 11 of the scope of patent application, wherein the non-volatile memory is CPLD (Complex Programmable Logic Device, complex programmable logic device 1 3) The intelligent firmware upgrade control method described in the above item, wherein the non-volatile memory is EEPROM (Electrically Erasable Programmable Read Only Memory, electronically erasable, programmable, read-only memory). 1 4 The intelligent firmware upgrade control method according to item 4, wherein the step of determining that the system resource is sufficient to store the loaded new firmware, and if it detects that the system resource is insufficient, a warning message is displayed to notify the user to reboot. 1 5 · If the fourth item of the patent application scope describes the intelligent initial body upgrade control method, wherein the verification result or the comparison result is incorrect, a warning message is displayed to notify the user to restart. Page 21