CN1317641C - Firmware update method and device for checking program content to ensure compatibility of firmware update - Google Patents

Abstract

The invention provides a method and a related device for updating firmware in an electronic system. The electronic system has one host and one peripheral device, and the peripheral device has one control circuit and one flash memory, and the control circuit executes the first program code recorded in the flash memory to receive the control command of the host and control the operation of the peripheral device. Before replacing/updating the first program code with the second program code, a checking step is carried out to check whether the content of the second program code conforms to a preset content so as to judge the compatibility of the second program code. The checking step can be performed by the host and/or the control circuit, and the checking step can check whether a part of constant values and strings recorded in the second code conform to preset values, or/and check whether instructions and data at preset addresses in the second code conform to preset instructions and data, so as to determine the compatibility of the second code.

Description

Firmware update method and device for checking program content to ensure compatibility of firmware update

technical field

The present invention provides a firmware update method and a related device, especially a method and a related device for checking the contents of firmware program codes for updating to judge its compatibility and applicability before the firmware update.

Background technique

In a modern information society, information, images, and data are transmitted, stored, and processed in the form of electronic signals, and various electronic systems and devices used to access electronic signals, ranging from mobile phones to large Even computers have become the key foundation of information construction. Generally speaking, most electronic devices are provided with a control circuit to uniformly control various operations of the electronic device; however, in electronic devices with complex functions and various functions, since the control procedures are relatively complicated, specific program codes are used to record The relevant steps and processes of various control programs; the control circuit executes the program codes to realize different functions of the electronic device. Such program codes are called firmware program codes; most of the firmware program codes are stored in non-volatile memory (such as flash memory) in the electronic device, which is convenient for the control circuit to read and execute. In addition, in electronic systems with more complex and diverse functions like computer systems, various peripheral devices of the computer themselves have control circuits and corresponding firmware program codes; the host computer itself only needs to send high-level control commands to the peripheral devices The control circuit will execute the firmware program code of the peripheral device itself to control the actual operation of the peripheral device. For example, the optical disc drive in the computer system itself has its control circuit and corresponding flash memory for storing the firmware program code of the optical disc drive itself. When the host computer of the computer wants to read the data on an optical disc, it only needs to specify the address of the data on the optical disc to the optical disc drive, and the control circuit of the optical disc drive will execute its own firmware program code to coordinate such as the motor ( spindle), laser pick-up head (pick-up head) and other electromechanical components (such as the motor must reach a specific speed, the pick-up head must move, lock to a specific position, receive the laser reflected on the optical disc, etc.), The actual implementation of the host's requirements.

Please refer to Figure 1. FIG. 1 is a functional block diagram of a typical electronic system 10 . The electronic system 10 may be a computer system, which includes a host 12 and one or more peripheral devices (two peripheral devices 14 and 15 are represented in FIG. 1 ). The peripheral device can be a CD-ROM, a CD recorder, a hard disk, an external flash memory, etc.; the peripheral device 14 is used as an example to illustrate the configuration of a typical peripheral device, and the peripheral device 14 is provided with a control circuit 16, a Buffer memory 18 , a storage memory 20 and a servo hardware 22 . If the electronic system 10 is a computer system, the typical configuration of the host computer 12 is as shown in FIG. graphics card 32A and display 32B. The central processing unit 26 is used to control the operation of the host computer 12, the memory 30 is used to temporarily store necessary data and data during the operation of the central processing unit 26, and the graphics card 32A is used to process image data to display the operation status of the host computer 12 on on display 32B. The north bridge circuit 28A is used to manage and control the data transmission between the central processing unit 26 and the graphics card 32A and the memory 30; The host 12 is an interface for exchanging data. Through the electrical connection between the south bridge circuit 28B and the peripheral devices 14 and 15 (such as via a bus), the host computer 12 and the peripheral devices 14 and 15 can exchange data with each other. On the other hand, in the peripheral device 14 , the control circuit 16 is used to receive control commands from the host 12 to control the operation of the peripheral device 14 . The servo hardware 22 is controlled by the control circuit 16 to realize the functions of the peripheral device 14 . For example, if the peripheral device 14 is an optical disc drive, the servo hardware 22 includes electromechanical components such as a motor to rotate the optical disc, a laser pickup head, etc., to access data on an optical disc. The buffer memory 18 and the storage memory 20 are used to support the operation of the control circuit 16 ; the buffer memory 18 is a volatile memory (such as a random access memory) for temporarily storing data and data during the operation of the control circuit 16 . The storage memory 20 is a non-volatile memory (such as a flash memory) used to record a firmware program code 24; as mentioned above, when the control circuit 16 of the peripheral device 14 controls the peripheral device 14, Various control programs will be performed according to specific firmware program codes, and the program code 24 is this firmware program code, which is used to record the ways in which different control programs are carried out. The control circuit 16 executes the program code 24 to control the operation of the peripheral device 14 according to the control command of the host 12 .

Of course, when each peripheral device leaves the factory, the firmware program code has been written into the storage memory as preset firmware. After the peripheral device is connected to the host, the control circuit in the peripheral device can control the operation of the peripheral device according to the preset firmware. However, the preset firmware may have some control program errors (bugs), which are not discovered until the peripheral device leaves the factory. In addition, firmware developers will continue to develop new control programs and firmware codes even after the peripheral devices leave the factory, so as to improve the operating performance of the peripheral devices or expand the application range of the peripheral devices. Taking the optical disc drive as an example, with different control programs, the optical disc drive may be able to lock the position of the laser pickup head faster, so as to more stably read data on a specific part of the optical disc. Or, when there is an optical disc that uses a data format of a newer specification to record data, update the way in which part of the control program in the firmware program code is carried out, and the optical disc drive may be able to read the optical disc with a newer data format smoothly, expanding its support CD-ROM data format. In the various situations discussed above, it is necessary to update the firmware program code in the peripheral device, and replace the existing firmware program code in the peripheral device with the new firmware program code, so as to solve the errors in the preset firmware program code and improve Improve the performance of peripheral devices and expand the application range of peripheral devices. In modern peripheral devices, most of the firmware program codes are stored in rewritable non-volatile storage memory (such as flash memory, or electrically erasable programmable read-only memory EEPROM), as long as the The original preset firmware program code in the storage memory is erased, and the new firmware program code is written in, so that the old preset firmware program code can be replaced with the new firmware program code, and the firmware update is completed. When the control circuit in the peripheral device executes the new firmware program code stored in the memory, the operation of the peripheral device can be controlled by the new control program.

Generally speaking, to update the firmware program code in the peripheral device, the host also needs to perform corresponding operations. Please refer to Figure 2 (and also refer to Figure 1). The process 100 in the flow chart of FIG. 2 is the process of coordinating operations between the host computer 12 and the peripheral device 14 when the electronic system 10 needs to update the firmware of the peripheral device 14 in the known technology. The steps in the left half of FIG. 2 represent the steps performed by the host 12 , and the steps in the right half represent the steps performed by the peripheral device 14 . The known process 100 has the following steps in sequence:

Step 102: start. When updating the firmware program code of the peripheral device 14, the central processing unit 26 will start to execute a firmware update application program 34, start the entire firmware update process 100, and continue to control the progress of the firmware update process in subsequent steps. As shown in FIG. 1 , the application program 34 is loaded into the memory 30 of the host 12 , and the CPU 26 executes the application program 34 to update the firmware of the peripheral device 14 . The purpose of the firmware update is to replace the existing program code 24 in the peripheral device 14 with a new program code 36 .

Step 104 : After the host 12 executes the application program 34 , it first performs device identification on the peripheral device 14 to determine that the application program 34 is an application program matched with the peripheral device 14 and can correctly control the peripheral device 14 to perform firmware update. As mentioned above, the host 12 may be connected to a plurality of different peripheral devices, and the structures and functions of each peripheral device are different. To control different peripheral devices to perform firmware updates respectively, the application programs to be executed by the host 12 are of course also different. Same; to correctly update the firmware of a peripheral device, the application program corresponding to the peripheral device must be used. And this step is to determine that the application program 34 is the correct application program corresponding to the peripheral device 14 . Generally speaking, a firmware identification code is recorded in the firmware program code of each peripheral device, which may include the name (vendor ID) of the firmware developer, the model name (model name) of the peripheral device to which the firmware program code is applicable, Or version information of the firmware program code and the like. As the existing program code 24 in the peripheral device 14, a firmware identification code 24I is recorded. And when the host 12 is executing the application program 34, it can send a device identification control command to the peripheral device 14 according to the instruction of the application program 34, requiring the peripheral device 14 to send the relevant data in the firmware identification code 24I (or other identifiable peripheral device 14 data, signal) to the host 12.

Step 106 : The peripheral device 14 responds to the request of the host 12 in step 104 , and returns the relevant data of the firmware identification code 24I (or other identification data) to the host 12 .

Step 108 : When the host 12 executes the application program 34 , it can judge whether the peripheral device 14 is a device matched with the application program 34 according to the identification data returned by the peripheral device 14 . In fact, when the host 12 and the peripheral device 14 perform device identification, it is very likely that several data and command exchanges will be performed. Without affecting the technical discussion of the present invention, the flow chart in FIG. 2 has partially simplified the device identification. details. According to the data exchange between the peripheral device 14 and the host 12, if the host 12 judges that the application program 34 can indeed be compatible with the peripheral device 14, the host 12 can continue the firmware update process and issue a control command to inquire about the current operating status of the peripheral device 14. Whether a firmware update can be performed. Because when the host computer 12 executes the application program 34 of the firmware update, the peripheral device 14 may be performing some operations (for example, the peripheral device 14 of the CD player may be accessing the data on the optical disc), so the firmware update cannot be performed. Therefore, in this step, the host 12 needs to inquire about the current operating status of the peripheral device 14 . At the same time, the host 12 can also load the new program code 36 used for firmware update into the memory 36 , ready to be transmitted to the peripheral device 14 .

Step 110 : the peripheral device 14 responds to the query of the host, and returns the current operating status of the peripheral device 14 to the host 12 .

Step 112 : If the operating status returned by the peripheral device 14 indicates that it can perform firmware update, the host 12 can transmit the new program code 36 temporarily stored in the memory 30 to the peripheral device 14 . Just like a typical network transmission, when the host 12 transmits the new program code 36, it will execute a preset checksum generation algorithm, calculate a checksum (checksum) 36C according to the content of the new program code 36, and compare it with The new program code 36 is also transmitted to the peripheral device 14 .

Step 114 : the peripheral device 14 receives the new program code and check code from the host 12 and temporarily stores them in the buffer memory 18 . The new program code 37 and check code 37C temporarily stored in the buffer memory 18 of the peripheral device 14 in FIG. 1 are the new program code and check code received by the host computer 12 by the peripheral device 14 .

Step 116: The control circuit 16 will also execute the check code generation algorithm, calculate another check code 39C according to the new program code 37 it receives, and combine this check code 39C with the check code 37C sent by the host computer 12 Compare. The check code generation algorithm used by the control circuit 16 is the same as the check code generation algorithm that the host computer 12 generates the check code 36C according to the new program code 36; There is no data transmission error, the new program code 37 received by the peripheral device 14 should be equal to the new program code 36 to be transmitted by the host computer 12, and the check code 39C calculated by the control circuit 16 should also be equal to the received program code 39C. Check code 37C. Conversely, if the check code 39C calculated by the control circuit 16 is inconsistent with the received check code 37C, it means that a data transmission error occurs during the host 12 transmitting the new program code/check code to the peripheral device 14 . If it is found that the check code 39C is consistent with the check code 37C in this step, then proceed to step 118 ; otherwise, if the two check codes are inconsistent, then proceed to step 120 .

Step 118: In the known technology, after the control circuit 16 judges that the transmission of the new program code 37 is correct in step 116, the existing program code 24 in the storage memory 20 will be erased (erase), and will be temporarily stored in the buffer The new program code 37 in the memory 18 is overwritten into the storage memory 20; in this way, the firmware update of the peripheral device 14 is completed. Then the control circuit 16 can execute the new program code 37 written into the storage memory 20 to control the operation of the peripheral device 14 . Of course, after the firmware update is successful, the peripheral device 14 can also send back the success of the update to the host computer 12; and the host computer 12 can also request the peripheral device 14 to transmit the firmware identification code in the new program code to the host computer 12 to confirm the firmware update success. The details of the above operations have been omitted in FIG. 2 without affecting the technical discussion of the present invention.

Step 120: If the control circuit 16 compares and finds that the check codes 37C and 39C are inconsistent in step 116, necessary error handling can be performed. For example, the control circuit 16 may require the host computer 12 to retransmit the new program code 36 once, and perform the check code comparison in step 116 again; or return the error situation to the host computer 12, and the host computer 12 determines the subsequent operation .

Step 122: End the process of firmware update.

To sum up, when firmware update is performed with the known process 100 in FIG. The program code 36 is transmitted to the peripheral device 14 , and the peripheral device 14 performs a firmware update after confirming that the transmission of the new program code is correct after performing the check code comparison in step 116 . One of the main disadvantages of the above known process is that it is impossible to ensure whether the content of the new program code used for firmware update is really the firmware program code suitable for the application of the peripheral device 14 . Generally speaking, the new program code 36 for firmware update is obtained by the user of the host 12 (for example, downloaded from the Internet), and then loaded into the memory 30 of the host 12 by the application program 34 during the firmware update process. However, it is possible for the user to make mistakes during the process of obtaining the new program code 36 , so that the new program code 36 itself is a firmware program code that does not conform to the application of the peripheral device 14 . For example, the user of the host computer 12 may obtain the new program code 36 by downloading from the network, but network transmission errors may occur during the network download process, making the new program code 36 itself incomplete. Alternatively, the user may misjudge the version of the firmware program code. As mentioned above, firmware developers may continuously release new versions of firmware program codes, and the peripheral device 14 may have built-in a newer version of preset program codes when it leaves the factory, but users may want to use it without realizing it. The new program code 36 of the older version is used to update the firmware of the peripheral device 14; in other words, in this case, the existing program code 24 in FIG. is an older version. If the firmware is "updated" at this time, the firmware program code will be downgraded instead. In addition, the user may mistakenly obtain the firmware program code that is not suitable for the application of the peripheral device 14 as the new program code 36 . For example, the new code 36 obtained by the user may not be the firmware code for the peripheral device 14 at all. Especially in the modern society with rapid technological development, the same manufacturer may launch many different types of peripheral devices of the same type with different functions. For example, in a common computer system peripheral device such as a CD-ROM, there are various CD-ROMs with different reading speeds, or some CD-ROMs can only read the data of CD-ROMs, and some CD-ROMs can also burn data. to CD-ROMs; some CD-ROMs support reading data from more CD-ROMs in different formats. Although R&D manufacturers will release different update firmware program codes for different types of peripheral devices, users may obtain new program codes 36 completely inconsistent with the peripheral device 14 to perform firmware update for the peripheral device 14 without noticing them. In addition, there may be some malicious saboteurs who intentionally provide wrong firmware program codes as the new program code 36, intending to implant the wrong firmware program codes into the peripheral device 14 in the process of firmware update, so as to paralyze the Normal operation of the peripheral device 14 .

In the various situations mentioned above, the new program code 36 to be used by the host computer 12 for firmware update is not suitable for the application of the peripheral device 14; but in the known firmware update process 100, the new program code 36 cannot be detected. Is it applicable. In the known process 100, although the host 12 will perform device identification in step 104 and check the firmware identification code 24I of the existing program code 24 through the peripheral device 14, what the host 12 checks is the firmware program of the peripheral device 14 that is already in operation. Code (that is, the existing program code 24 of the peripheral device 14), will not check whether the new program code 36 is suitable for the application of the peripheral device 14. In addition, the control circuit 16 of the peripheral device 14 will check the check code related to the new program code 36 in step 116, but this step can only check whether data transmission occurs when the new program code 36 is transmitted between the host computer 12 and the peripheral device 14. error, also can not check out whether the new program code 36 is applicable. Even if the new program code is an inapplicable firmware program code, as long as there is no problem in the data transmission between the host 12 and the peripheral device 14, the process 100 will still go through step 116 to write the inapplicable new program code into the storage memory. In other words, in step 116, even if the check code matches, it only means that the host computer 12 completely and correctly transmits the inapplicable new program code 36 to the peripheral device 14 to become a new program code 37 (see FIG. 2 ). The inapplicable nature of code 37 still does not change, nor can it be checked out in step 116. Although the control circuit 16 will calculate the check code 39C according to the new program code 37 in step 116, so that the check code 39C can reflect the content of the new program code 37, another check code 37C used to compare the check code 39C in step 116 It is also calculated according to the new program code 36, and cannot represent the check code that the "applicable" firmware program code should have (especially when the new program code 36 itself is an inapplicable firmware program code). In other words, when the known process 100 is performing step 116, the control circuit 16 itself cannot know what the check code corresponding to the "applicable" firmware program code is, and of course it cannot check and compare the new program code 37 in step 116. Is it applicable. If wrong or inapplicable firmware program codes are mistakenly implanted into the peripheral device 14 during the firmware update process, not only the purpose of firmware update will not be achieved, but the peripheral device 14 will not operate correctly.

Contents of the invention

Therefore, the main purpose of the present invention is to provide a new firmware update method and related device, which can screen out whether the new firmware program code for update is really applicable, so as to overcome the shortcomings of the known technology.

In the known technology, it is impossible to check whether the new program code used for firmware update is suitable for the actual application of the peripheral device, no matter at the host end or at the device end of the peripheral device. erroneously implanted in a peripheral device during the firmware update process.

In the present invention, a host-side check step and/or a device-side check step are added to the process of updating the firmware of a peripheral device, and a part of the content of the new firmware program code for updating is compared with a preset content, To actually judge whether the new firmware program code is applicable. In actual implementation, it is possible to check whether the firmware identification code (including the name of the firmware developer and the model name of the peripheral device to which the firmware code is applicable) in the new firmware program code is consistent with the existing peripheral program code in the peripheral device. The firmware identification code of the new firmware is consistent, and it is also possible to check whether the new firmware program code contains specific instructions and constants. In addition, it is also possible to check whether the instructions and data of specific addresses in the new firmware program code are in line with the expected instructions and data, or to search whether the address of specific instructions and data in the new firmware program code is located at the preset address to determine whether the firmware is updated. Whether the new firmware code used corresponds to the correct firmware for the peripheral device application. The above inspection steps can be carried out independently on the host side and the device side to ensure that the new firmware code used for firmware update is the applicable firmware code, and avoid implanting inapplicable firmware code into the peripheral device by mistake during the firmware update process .

Description of drawings:

FIG. 1 is a schematic diagram of a configuration of a host computer and peripheral devices in a typical electronic system.

FIG. 2 is a schematic flowchart of firmware update performed by the electronic system in FIG. 1 in a known process.

FIG. 3 is a schematic diagram of the configuration of the host computer and peripheral devices in the electronic system of the present invention.

FIG. 4 is a schematic flowchart of firmware update performed by the electronic system in FIG. 3 using the process of the present invention.

5A to 5E are schematic diagrams of different embodiments of the host-side/device-side checking steps in FIG. 4 .

Explanation of the symbols in the diagram:

10, 50 Electronic system 12, 52 Host

14-15, 54-55 Peripherals

16, 56 Control circuit 18, 58 Buffer memory

20, 60 Storage memory 22, 62 Servo hardware

24, 64 program code

24I, 64I, 76I, 77I Firmware identification code

26, 66 CPU

28A, 68A North Bridge Circuit 28B, 68B South Bridge Circuit

30, 70 memory 32A, 72A graphics card

32B, 72B Display 34, 74 Application

36-37, 76-77, 84 New program code

36C, 37C, 39C, 76C, 77C, 79C check code

56B Inspection module

80, 82 Default content 86 Source code

88, 89 Firmware program code 90A-90D Program fragment

Part of 92A-92C, 92D1, 92D2

94 Command Code 95 Data

100, 200 process

102-122, 202-224 steps

Detailed ways

Please refer to Figure 3. FIG. 3 is a schematic functional block diagram of the configuration of the electronic system 50 of the present invention. The electronic system 50 is provided with a host 52 and one or more cooperating peripheral devices (two peripheral devices 54 and 55 are represented in FIG. 3 ) to expand the functions of the host 52 itself. The electronic system 50 can be a computer system; in this case, a central processing unit 66, a north bridge circuit 68A, a south bridge circuit 68B, a memory 70, a graphics card 72A and a display 72B can be arranged in the main frame 52; the peripheral devices 54, 55 then It could be a CD drive, CD recorder, hard drive, etc. Take the peripheral device 54 as an example to illustrate the configuration in the peripheral device; the peripheral device 54 is provided with a control circuit 56, a servo hardware 62 for realizing the function of the peripheral device 54, and a buffer for temporarily storing data in a volatile manner A memory 58 (such as a random access memory), and a storage memory 60 (such as a flash memory) for storing data in a non-volatile manner; and a check module 56B in the control circuit 56 . In the host computer 12, the central processing unit 66 is used to control the operation of the host computer 52, and the graphics card 72A can convert the operation status and results of the host computer 52 into image signals and display them on the display 72B. The volatile memory 70 (such as random access memory) is used to temporarily store program codes and related data and materials necessary for the operation of the CPU 66 . The north bridge circuit 68A is used to manage the data transmission between the CPU 66, the memory 70 and the graphics card 72A. Through the south bridge circuit 68B electrically connected to the north bridge circuit 68A, the host computer 12 can exchange instructions and data with each peripheral device 54, 55; wherein the south bridge circuit 68B and each peripheral device can use a bus (such as IDE, EIDE and other buses) interconnected. Regarding the peripheral device 54, as previously discussed, in order to control the peripheral device 54 to carry out various operations, a firmware program code will also be used to record various control program implementation methods; in FIG. 3, it is stored in the storage memory 60 Existing program code 64 in is exactly this firmware program code. After the control circuit 56 receives the control instruction from the host 52 , it can execute the program code 64 stored in the memory 60 to control the servo hardware 62 to realize the functions required by the host 52 . The buffer memory 58 is used to temporarily store data during the operation of the peripheral device 54 . For example, if the peripheral device 54 is an optical disc recorder, the servo hardware 62 will include electromechanical components such as motors and optical pick-up heads; The servo hardware 62 actually writes the data temporarily stored in the buffer memory 58 to the optical disk; and the data read by the servo hardware 62 from the optical disk will also be temporarily stored in the buffer memory 58, and then arranged by the control circuit 56, these The data is sent back to the host 52 .

As discussed earlier, peripheral devices may require firmware updates. Please refer to Figure 4 (and also refer to Figure 3). FIG. 4 shows the process 200 of firmware update in the electronic system 50 according to the present invention; the steps on the left in FIG. 4 are performed by the host 52 , and the steps on the right are performed by the peripheral device 54 . The process 200 has the following steps:

Step 202: start. When the electronic system 50 is to update the firmware of the peripheral device 54, the central processing unit 66 in the host computer 52 will load a firmware update application program 74 into the memory 70 (please refer to FIG. 3 together), and start to execute The application program 74 is used to start the entire firmware update process 200 and continue to control the progress of the process 200 in subsequent steps. The purpose of the firmware update is to replace the existing firmware program code 64 in the peripheral device 54 with a new program code 76 .

Step 204: The host 52 requests the peripheral device 54 to perform device identification. As mentioned above, a firmware identification code is recorded in the firmware code of each peripheral device, which records the name (vendorID) of the firmware developer and the model name (model name) of the peripheral device to which the firmware code is applicable. As shown in FIG. 3 , the existing program code 64 of the peripheral device 54 before the firmware update also records the firmware identification code 64I corresponding to the program code 64 . When performing device identification, the host computer 52 can issue a control command to require the peripheral device 54 to return the relevant data of the firmware identification code 64I to confirm that the application program 74 is the correct program for matching with the peripheral device 54, and can be correctly identified in subsequent steps. Cooperate with peripheral device 54 for firmware update.

Step 206 : After the control circuit 56 in the peripheral device 54 receives the control command from the host 52 in step 204 , it will return the data related to the firmware identification code 64I in the firmware code 64 to the host 52 .

Step 208 : The host 52 can determine whether the application program 74 can cooperate with the firmware update of the peripheral device 54 according to the firmware identification code 64I data sent back by the peripheral device 54 (or other identification data required by the host 52 ). If the host 52 confirms that the application program 74 can indeed be matched with the peripheral device 54 , the host computer 52 will continue to execute the application program 74 to perform subsequent steps of updating the firmware of the peripheral device 54 . At the same time, the CPU 66 can also load the new program code 76 for firmware update into the memory 70 (as shown in FIG. 3 ). During the process of device identification, the host 52 and the peripheral device 54 may exchange data several times; without affecting the technical disclosure of the present invention, the details of device identification have been appropriately omitted in FIG. 4 .

In addition to device identification, in order to further confirm that the content of the new program code 76 is a firmware program code suitable for the application of the peripheral device 54, the present invention will additionally perform a host-side checking step to judge the new program code 76 according to the content of the new program code 76. Whether the program code 76 is an applicable firmware program code. The manner in which the host-side checking step is performed can have several embodiments. For example, since the new program code 76 is a firmware program code, it certainly also records a firmware identification code 76I (please also refer to FIG. 3 ), just as the existing program code 64 in the peripheral device 54 also has a corresponding Firmware identification code 64I. In this host-side checking step, the host computer 12 can check whether the firmware identification code 76I in the new program code 76 matches the firmware identification code 64I in the existing program code 64, to verify whether the new program code 76 is consistent with the peripheral device 54 The existing program code 64 is also developed by the same firmware developer, or is applicable to the same type of peripheral device. In addition, the firmware research and development manufacturer can also record preset control instructions or character strings and data at fixed addresses in the firmware program code in advance to form a preset content 80 (see FIG. 3 ); It is possible to check whether the new program code 76 has a preset content 80 (as shown in FIG. 3 ) in the fixed address, so as to judge the applicability of the new program code 76 . Or, the host computer 52 can also search for a part with preset content in the new program code 76, and then check whether the address of this part is in the address preset by the firmware R&D manufacturer, so as to judge the applicability of the new program code 76. The various methods and principles of the host-side check step will be further discussed later.

If the host 52 judges that the new program code 76 is an applicable correct program code after performing the host-side check step, the firmware update process can continue. Next, the host 52 can issue a command to inquire whether the status of the peripheral device 54 is ready for firmware update.

Step 210 : The peripheral device 54 responds to the query of the host in step 208 , and returns the current status of the peripheral device 54 to the host 52 .

Step 212: The host 52 receives the signal that the peripheral device 54 responds in step 210; if the peripheral device 54 is in a state where the firmware can be updated, the host 52 can start to transmit the new program code 74 loaded into the memory 70 to the peripheral device 54. Like the device identification in steps 204 and 206, the device status inspection of the peripheral device 54 in steps 210 and 212 may also carry out several data transfers between the host computer 52 and the peripheral device 54; without affecting the technical disclosure of the present invention case, the relevant details have been appropriately simplified in Figure 4. As shown in FIG. 3, before the host computer 52 transmits the new program code 76 to the peripheral device 54, a preset check code generation algorithm is used to calculate a check code based on the content of the new program code 76. 76C, append it to the checksum 76, and transmit it to the peripheral device 54 together with the checksum 76.

Step 214: The peripheral device 54 receives the new program code and the additional check code from the host 52, and temporarily stores them in the buffer memory 58, that is, the new program code 77 and the check code 77C shown in FIG. 3 . Step 216: the control circuit 56 of the peripheral device 54 will use the check code generation algorithm to calculate a check code 79C (see FIG. 3 ) according to the content of the new program code 77, and verify the check code 79C and the peripheral device 54 by the host computer 52. Whether the received check code 77C is the same. If the two are the same, it means that the host 52 has no data transmission error during the process of transmitting the new program code to the peripheral device 54 .

After confirming that the new program code used for firmware update has been completely transmitted from the host computer 52 to the peripheral device 54, the present invention also performs a device-side inspection step in the peripheral device 54, and the control circuit 56 realizes the function of the inspection module 56B. To check whether the new program code 77 temporarily stored in the buffer memory 58 is an applicable firmware program code. For example, the control circuit 56 can compare whether the new program code 77 temporarily stored in the buffer memory 58 has the same firmware identification code as the existing program code 64 in the storage memory 60 . Because the new program code 77 was transmitted by the host computer 52, under the situation that the data transmission is correct, the new program code 77 also has the same firmware identification code 77I as the firmware identification code 76I; the control circuit 56 compares the firmware identification code 77I with the existing Whether the firmware program code 64I of the firmware program code 64 is consistent can determine whether the new program code 77 is a firmware program code suitable for the peripheral device 54 . Similar to the host-side check step, the device-side check step carried out in the peripheral device 58 can also check whether the partial content at a specific preset address in the new program code 77 conforms to a predetermined content 82 (as shown in FIG. 3 ) ; Or search whether some default content exists in the new program code 77, or whether it is located at some specific addresses. As for the details and principles of the inspection step at the device end of the present invention, further description will be made later.

Of course, if the control circuit 56 finds that the check code 77C does not match the check code 79C calculated by the control circuit 56 before performing the device-side check step of the present invention, it means that the new program code is transmitted from the host computer 52 to the peripheral device 54. Error in data transmission. At this time, the control circuit 56 can return the error situation to the host 52, or require the host 52 to retransmit the new program code until the new program code is completely transmitted to the peripheral device 54, and then perform the device-side checking step of the present invention.

Step 218 : If the control circuit 56 judges that the new program code 77 is indeed suitable for the peripheral device 54 after performing the device-side checking step, proceed to step 220 ; otherwise, proceed to step 222 .

Step 220: After passing the verification of the check code and the verification of the device-side inspection step of the present invention, the peripheral device 54 can confirm that it has correctly received the new program code 77 sent by the host 52 on the one hand, and can also confirm the new program on the other hand. The code 77 is the applicable firmware program code for the peripheral device 54. At this time, the control circuit 56 can erase the program code 64 originally used as the firmware program code in the storage memory 60, and write the new program code 77 into the storage memory 60. To replace the original program code 64, complete the firmware update. Then the control circuit 60 can execute the new program code 77 stored in the memory 60 to control the operation of the peripheral device 54 with the new control program. Of course, after the firmware update is completed, the peripheral device 54 can also report the completion of the firmware update to the host computer 52, and the host computer 52 can also request the peripheral device 54 to return the relevant information of the firmware identification code in the new firmware program code again to confirm the firmware update Done etc. In the case of not affecting the technical disclosure of the present invention, the detailed flow of this part has been omitted in FIG. 4 .

Step 222: If it is found that the new program code 77 is not an applicable firmware program code during the device-side checking step of the present invention in step 216, the control circuit 56 will perform error handling. The control circuit 56 can report back to the host 52 that the new program code is not applicable, and the user of the host 52 decides the next steps. Most importantly, at this time, the control circuit 56 will not overwrite the inapplicable new program code to the storage memory 60, so that the control circuit 56 will not control the peripheral device 54 according to the inapplicable new program code in the subsequent process, And the operation of the peripheral device 54 will not be affected by the unsuitable firmware program code in the firmware update process.

Step 224: End the firmware update process of the present invention.

As can be seen from the above description of the firmware update process of the present invention, the process 200 of the present invention not only performs device identification and check code confirmation during the firmware update process, but also additionally performs host-side checking steps and device-side checking steps. The former can first check whether the new program code 76 is a firmware program code suitable for the peripheral device 54 before the host computer 52 transmits the new program code 76 for firmware update to the peripheral device 54 . After the new program code 76 is successfully transmitted to the peripheral device 54 to become the new program code 77, the peripheral device 54 also performs a device-side inspection step, so that the program code is checked before the program code 77 is actually written into the storage memory 60. 77 is applicable to the peripheral device 54. Through the implementation of the checking steps at the host/device side of the present invention, it will be further confirmed that the firmware update process will not mistakenly implant inapplicable firmware program codes into the peripheral device. As for the manner in which the checking step of the host/device side is performed in the present invention, there may be several embodiments, which will be discussed one by one below.

First, please refer to FIG. 5A (and refer to FIG. 3 together). FIG. 5A is a schematic diagram of one embodiment of the host/device checking step in the present invention. As mentioned above, firmware developers define some data about the firmware itself in the firmware program code, such as the name of the firmware developer (vendor ID), the model name of the peripheral device (model name) to which the firmware program code is applicable. ), or even serial number (serial number) or version information, form a firmware identification code. Even in different versions of firmware program codes, these information will be uniformly recorded. As shown in FIG. 5A, whether it is the existing firmware program code 64 of the peripheral device 54 before the firmware update, or the new program code 76 (or new program code 77) used for the firmware update, as long as it is commonly applicable to the peripheral device 54 firmware code, it should have the same form of firmware identification code. Generally speaking, in the firmware program code, the relevant signal of the firmware identification code is recorded in a section of constant (constant) in the firmware program code. As known to those skilled in the art, firmware developers use a higher-level programming language to write various control programs for peripheral devices into a source code, and then compile through a compiler (complier) software ( After compile), it becomes the firmware program code of binary code executable by the control circuit in the peripheral device. Firmware R&D manufacturers usually use a constant array (array)_pbTBL Inquiry[] in the source code of the firmware program code to compile the content of the firmware identification code. The content can be directly expressed in numerical values, such as 0x05, or edited in characters. For example, 'A' represents the ASCII code known to those skilled in the art. After being compiled by a compiler into a binary code firmware program code executable by the control circuit in the peripheral device, a corresponding binary code constant exists in the firmware program. code. Therefore, in the firmware program code, some content must be used to define the content value of this constant. For example, as shown in FIG. 5A, in the firmware identification code 64I of the existing program code 64, part of the content is to define the value of the constant -pbTBL Inquiry as {0x05, 0x80, ...,' in binary code mode. A', 'b', ..., 'd', 'M', ..., 'k', 'm', ..., ...}, where "Abcdefgh" represents the name of the firmware developer, and "Modelikmh" represents the model name, other data can be used to represent other data such as firmware version. Similarly, if the new program code 76 used for firmware update is an applicable firmware program code, there must also be a firmware identification code 761, which is also used to define the value of the constant _pbTBL Inquiry[]. When carrying out the host-side inspection step of the present invention, the host computer 52 can execute the application program 74 (as shown in FIG. 3 ) for updating the firmware and search for the new program code 76 to check whether some content in the new program code 76 is used to define The constant _pbTBLInquiry, and this constant is defined as a specific value. At the same time, the host 52 may also request the peripheral device 54 to return the value of the constant _pbTBL Inquiry in the existing program code 64 . Of course, if this constant is not defined at all in the new program code 76, it must not be a normal firmware program code. If this constant is indeed defined in the new program code 76, and the value of this constant in the new program code 76 matches the value defined in the existing program code 64 (as the name of the firmware research and development manufacturer is the same, the model name is the same), the host computer 52 will The new program code 76 can be determined as applicable firmware program code in the host-side checking step. In addition, in the host-side check step, the host 52 can further judge whether the new program code 76 (relative to the existing program code 64) is a newer version of firmware according to the version information in the new program code 76; The version of the program code 76 is rather old, and the host computer 52 can also determine that the new program code 76 is an inapplicable firmware program code. To further extend the concept of this comparison, the present invention can also check whether the value of a certain constant in the new program code is within a specific range of a preset value. As in the above example, it is to check whether the version recorded in the new program code is greater than the version of the existing program code.

In addition to comparing the firmware identification code 76I in the new program code 76 with the firmware identification code 64I in the existing program code 64 to perform the host-side checking step, the firmware developer can also release the application program 74 used for firmware update, Directly record the due format and value (or the reasonable range of its value) of constant _pbTBL Inquiry in the application program 74; The requirement of the constant _pbTBL Inquiry directly judges whether the new program code 76 is an applicable firmware program code, and does not need to be a benchmark for comparison based on the information in the firmware identification code 64I. According to the above reason, the control circuit 56 in the peripheral device 54 can also use the definition of the constant _pbTBL Inquiry in the existing program code 64 to check the new program code temporarily stored in the buffer memory 58 when performing the device-side inspection step. Whether 77 is applicable firmware code. In the same way, when the peripheral device 54 leaves the factory, the firmware manufacturer can also pre-set the standard format, content value or reasonable range of the content value of the constant _pbTBL Inquiry in the control circuit 56 (such as the version number should be greater than a certain preset value). Setting value), when the control circuit 56 performs the device-side inspection step in the future, it can independently judge whether the new program code 77 has the correct _pbTBL Inquiry constant definition. In the current information industry, it is a standard practice to add a firmware identification code into the firmware program code, and the present invention can also conveniently directly use the firmware identification code to judge whether the new firmware program code used for firmware update is applicable.

Please continue to refer to FIG. 5B (and FIG. 3 ). FIG. 5B is a schematic diagram of another embodiment of the host/device checking step in the present invention. In addition to using the commonly defined firmware identification codes in firmware codes to judge the applicability of firmware codes, firmware developers can also pre-insert specially defined strings and data in firmware codes to identify firmware codes in the future. Basis for Applicability. As known to those skilled in the art, firmware developers use a higher-level programming language to write various control programs for peripheral devices into a source code, and then compile through a compiler (complier) software ( After compile), it becomes the firmware program code of binary code executable by the control circuit in the peripheral device. Firmware R & D manufacturers can compile a specially defined string and data in the source code of the firmware program code with a constant array (array), and the content can be directly represented by a numerical value, such as 0x06, or edited by a character (character), such as 'A' represents the ASCII code known to those skilled in the art. After being compiled by the compiler into the executable binary code of the firmware program code of the control circuit in the peripheral device, a corresponding binary code constant exists in the firmware program code middle. As shown in the embodiment of FIG. 5B , the firmware R&D manufacturer can add additional program segments 90A and 90B to the source code 86 of the firmware program code to define a string _pbSpecString (the content of which is 'M', 'e') respectively. , 'd', 'i', 'a', 't', 'e', 'k') and a constant _pbSpecValue. Please note that the program fragment 90B not only defines the value of the constant -pbSpecValue, but also defines that the constant value should be stored in a specific address 0xFFE0 (that is, the address FFE0 in hexadecimal) by the instruction "_at_0xFFE0". According to this instruction, the compiler will place this constant value at that specific address during compilation. After the source code 86 is compiled into the firmware program code 88 of the binary code, corresponding to the program segment 90A in the source code 86, there must be a part of the content 92A in the firmware program code 88 to record the defined value of the constant -pbSpecString in binary code; Corresponding to the program segment 90B, starting from the address 0xFFE0 of the firmware program code 88, there is also a part of the content 92B that records the defined value of the constant _pbSpecValue in binary code. After the firmware program code 88 is released, it becomes a new program code for firmware update (as shown in the new program code 76 in Figure 3). By using the specially defined character strings and constants in the new program code, the host/device side checking steps in the present invention can be implemented. For example, when the host 52 and the control circuit 56 are performing the checking steps of the host and the device, they can respectively check whether the string "Mediatek" is recorded in the new program code 76, 77 to define the string _pbSpecString. Because the applicable new program code released by the firmware developer must have part of the content used to record "Mediatek" to define the string _pbSpecString, if it is found that the new program code does not record "Mediatek" during the host/device side inspection steps, it will be Indicates that the new program code is an inapplicable program code. Similarly, the host 52 and the control circuit 56 can also check whether the new program code has a correct defined value of the constant _pbSpecValue at the address 0xFFE0 in the host/device checking step. If the address 0xFFE0 recorded in the new program code is not the correct defined value of the constant _pbSpecValue, it means that the new program is not applicable firmware program code. Alternatively, when performing the host/device side check step, check whether the defined value of the constant _pbSpecValue exists at the specific address 0xFFE0 of the new program code. Of course, when implementing the host/device inspection steps of the present invention in the above-mentioned manner, the firmware manufacturer will pre-set the control circuit 56 ( FIG. 3 ) before the peripheral device 54 leaves the factory, so that the control circuit 56 will be installed in the future. During the terminal inspection step, the target (that is, the preset content 82 in Fig. 3 ) can be known to be compared; if "Mediatek" is to be searched in the new program code, or which specific addresses should be stored at that specific address of the new program code value). Similarly, before the firmware update application 74 is released, the firmware manufacturer should pre-record in the application 74 the targets to be compared in the host-side device inspection step, so that the host 52 can follow the above-mentioned comparison after executing the application 74. The principle is to perform the host-side check step.

Please refer to Figure 5C. FIG. 5C is a schematic diagram of another embodiment of the host/device checking step of the present invention. In addition to performing the checking steps of the present invention with the above-mentioned constants and fixed-value strings specifically defined in the firmware program code, the checking steps of the present invention can also be performed according to specific instructions in the firmware program code. As shown in FIG. 5C, when the firmware R&D manufacturer writes the source code 86 of the firmware program code, he can add a program segment 90C, and compile a section of preset command code 94 to address FF80H (that is, sixteen carry address FF80). What is defined in the instruction code 94 can be a meaningful and practical control program, or some redundant operations that have no practical use (such as exchanging the values of two variables and then returning them). Instruction code 94 shown in Fig. 5C, its first row " MOV DRTP, #0800H " promptly is used for allowing a pointer (pointer) DRTP to point out an address 0800H (hexadecimal address 0800) in the buffer memory; The second row "MOVX A, @DRTP" moves the value stored in a temporary register A to the address pointed to by the pointer DRTP, and so on. After the source code 86 is compiled into the firmware program code 88, according to the address FF80H specified by the program segment 90C, the firmware program code 88 will record the command code in the form of binary code in the part of the content 92C starting from the address FF80H 94. After the firmware program code 88 is released as the new program code used for firmware update, it can be based on whether the new program code has a part of the content 92C corresponding to the instruction code 94 at the address FF80H (or whether the search part of the content 92C starts at the address FF80H) , to perform the checking step of the host/device side of the present invention to determine whether the new program code is the applicable firmware program code released by the firmware research and development manufacturer. Similar to the situation of the embodiment in Fig. 5B, the application program 74 and the control circuit 56 should also set the target to be compared in advance (such as the specified address, what is the binary code corresponding to the instruction code 94), so as to facilitate future host/device It is used as the basis for inspection during the terminal inspection step.

Please refer to Figure 5D. FIG. 5D is a schematic diagram of another embodiment of the host/device side checking steps of the present invention. As shown in FIG. 5D , the firmware developer can also add a program segment 90D in the source code 86 of the firmware program code, so as to add a specific value to a specific address in the firmware program code 88 after compilation. For example, in the program segment 90D among Fig. 5D, the command "CSEG AT 0005H" and the "DBE1H" of the next line specify that the data of one byte (the content is E1 in hexadecimal) be recorded in the firmware program code 88 The address 0005H in (hexadecimal address 0005); the command "CSEG AT FFFEH" and the next line "DB E2H" will record the value E2 of a byte in the address FFFEH. After the source code 86 is compiled into the firmware program code 88, the firmware program code 88 will record the hexadecimal value E1 in binary code at part of the content 92D1 at address 0005H, and record the hexadecimal value at 92D2 at the address FFFEH The value of E2. When performing the checking step of the host/device side of the present invention, it is possible to check whether the new program code has a specific value recorded at a specific address (such as whether it is a value E1 at the address 0005H), so as to determine whether the new program code is developed by firmware Applicable firmware code released by the manufacturer.

Please refer to Figure 5E. FIG. 5E is a schematic diagram of another embodiment of the host/device checking step of the present invention. In addition to inserting specific data and instructions into the source code as a basis for judging whether the new program code is applicable, the present invention can also insert specific data into the compiled firmware program code as a basis for checking steps . As shown in Figure 5E, generally speaking, after the source code 86 of firmware program code is compiled and become firmware program code 88, firmware program code 88 will also be left in addition to being used for recording instruction, the part content of data (such as constant value). The next number of unused segments (unusedsegment). These unused segments are filled with specific padding data. As in Fig. 5E, in the parts marked with slashes in some contents 92E1 to 92E4, meaningful programs and binary codes corresponding to instructions are recorded, the so-called program code segment (code segment); The part of the hexadecimal "F" is the so-called unused segment, which is not used to record any programs and instructions. For example, between the partial contents 92E2 and 92E3, there are unused sections. In addition, since the firmware program code 88 will probably be compiled into a program code with a fixed size (such as 512Kbyte) to facilitate recording in the storage memory in the peripheral device, there must be some redundant and unused records at the end of the firmware program code 88 Unused section of any program, instruction. When the control circuit in the peripheral device is executing the firmware program code, it will jump to read instructions between each program section, and will not execute to the unused section, so the present invention can also be used in the unused section of the firmware program code 88. Inserting specific data into the segment as a mark not only does not affect the operation of the peripheral device to execute the firmware program code, but the inserted mark can also be used as the basis for checking during the checking step of the host side/device side of the present invention. As shown in Figure 5E, after inserting several pieces of data 95 in the unused section of the firmware program code 88, it becomes the firmware program code 89; and the firmware program code 89 is the new program code officially released by the firmware developer. . When the checking step of the host/device side of the present invention is to be performed, it is possible to search for inserted data at specific addresses in the unused section of the new program code to determine whether the new program code is applicable. Similar to the embodiment of the present invention in FIG. 5B, C, and D, the firmware R&D manufacturer also needs to set the application program 74 and the control circuit 56 for firmware update in advance, so that the host computer 52 and the peripheral device 54 can know when the checking steps are performed. The target of the comparison, such as what data should be at that address in the end of the unused area. Compared with the embodiment of FIG. 5E , the marked data is inserted into the unused segment. In the embodiments of FIGS. 5A to 5D , the data used as the basis for the host-side/device-side check steps will be located in the program code area. part.

In addition to the above-mentioned methods, there are several other methods in the host-side/device-side checking steps of the present invention as follows. For example, when performing the checking step, it is possible to search for the address of a specific instruction data (such as a character string, a constant) in the new program code, and calculate a new address by shifting a section of the preset shifting address from the address, Then check whether the content of the new program code at the new address matches another preset content. In other words, when the firmware R&D manufacturer releases the firmware program code, it not only needs to add instruction data in the program code, but also adds the preset content at the place where the address of the instruction data is shifted by the translation address, so as to be included in the program code. After the code is released, cooperate with the customer to carry out the host-side/device-side inspection steps. In addition, when performing the checking step, it is also possible to check whether different constants in different preset addresses in the new program code conform to a preset value after undergoing preset calculations. For example, it can be checked whether the addition of the constants respectively located at two different addresses in the new program code is a predetermined value. As mentioned above, the check step can check the value of the firmware version in the firmware identification code as the basis for whether the firmware program code is applicable, but malicious saboteurs may also tamper with the firmware version when tampering with the program code. In order to evade the inspection of the inspection step, the tampered firmware program code is implanted into the peripheral device during the firmware update process. In view of this situation, the firmware R&D manufacturer can embed another checking constant in another preset address in the real new program code, and after adding the checking constant and the firmware version value of the new program code, it becomes A preset fixed value; in other words, in newer, firmware version codes with larger values, this checking constant also becomes smaller. When performing the host-side/device-side checking steps, the host/peripheral device can find the constant for checking at the preset address in addition to checking whether the value of the firmware version is greater than the value of the existing firmware version, and check the constant for checking Whether the value added to the firmware program version recorded in the new program code is a preset value. In this way, it is possible to further confirm whether the firmware version value itself is correct.

Extending from the above discussion, the checking step of the host end/device end of the present invention can also first search the two addresses where the data of the two preset contents are respectively located, and then check whether the program code between the two addresses has a certain preset characteristic. For example, when a firmware developer releases the applicable program code, a series of values can be recorded between two preset content data, and the value of this series of values added is a certain value (or according to a preset rule increment or decrement); or the data between two preset content data can obtain a preset standard value after being processed by a preset algorithm. In this way, when performing the check step of the host side/device side, the host computer/peripheral device can check whether the data between the two preset content data in the new program code conforms to the preset law, or whether it can be used in the new program code. It is assumed that the preset standard value is obtained after processing by the algorithm. Under this approach, the firmware developer can add different data between the two preset content data in different versions of the firmware program code, but the added data can get the same standard value after going through the preset algorithm. In this way, the comparison standard of the applicable program code is avoided to be exposed in the program code. Because in different versions of the applicable program code, the data between the two preset content data will be different, even if malicious saboteurs analyze different versions of the applicable program code, it is difficult to summarize specific rules to avoid the screening of the inspection step of the present invention. check.

From the above discussion of the checking steps of the host/device side of the present invention, it can be seen that the present invention compares whether there is preset content data (such as character string, data) in the new program code, or whether there is preset content in the preset address data (or whether the preset data is at the preset address), so as to determine whether the new program code used for the firmware update is an applicable program code during the firmware update process. When implementing the present invention (especially the embodiment of FIG. 5B to FIG. 5E ), the firmware research and development manufacturer can first draw up the overall strategy for the host/device side inspection step, so that before the peripheral device leaves the factory and releases the application program for firmware update, First set the comparison target when the host/device side checking steps are carried out, and when the firmware program code for updating is released successively in the future, the comparison data should be correspondingly added to the firmware program code. In this way, when the peripheral device needs to update the firmware, it can be ensured that the applicable firmware code released by the firmware developer can pass the host/device side check step, and the unsuitable firmware code will be screened in the check step out, so that inapplicable firmware code will not be mistakenly implanted into the peripheral device during the firmware update process. When setting the comparison target of the control circuit 56 of the peripheral device 54, since the control circuit 56 operates according to the existing program code, the comparison target and the way the device-side inspection steps are carried out can also be recorded in the peripheral device 54 preset. built firmware code. When implementing the present invention, various implementation methods in FIG. 5A to FIG. 5E can be used alone, or multiple methods can be combined for implementation, and the host-side/device-side checking steps can also use different comparison targets. For example, the host 52 can use the embodiment in FIG. 5B to check whether there is a specific character string in the new program code to implement the host-side checking step, and the control circuit 56 can use the embodiment in FIG. 5A to identify the code with the firmware. The device-side inspection step is carried out on the basis to determine whether the new program code is applicable. Of course, in this case, the applicable firmware program code must not only have a firmware identification code to support the implementation of the embodiment in FIG. 5A, but also have a specific character string to support the implementation of the embodiment in FIG. 5B. Just because the checking basis of the checking step of the host end/device end of the present invention is preset by the firmware research and development manufacturer, an accurate comparison target can be provided, and inapplicable firmware program codes can be checked out reliably. In contrast, although the known process 100 in FIG. 2 calculates a checksum using a checksum generation algorithm based on the new program code for firmware update, it is impossible to know the checksum corresponding to the applicable firmware program code due to the known process. , so the inapplicable new program code cannot be checked out by using the check code.

Although the process 200 shown in FIG. 4 of the present invention performs the check steps on the host end and the device end respectively at the host end and the device end, the present invention can also only perform the check steps on the host end by the host 52, or only use the peripheral device 54. The control circuit 56 performs a device-side checking step. When performing the host-side check step, it is not necessary to perform the host-side check step before the device status check as shown in FIG. Generally speaking, as long as the host-side check step is performed before the host 52 transmits the new program 76 to the peripheral device 54, it can prevent unsuitable firmware program codes from being transmitted to the peripheral device 54, and further prevent unsuitable firmware program codes from being transmitted to the peripheral device 54. Misplaced in a peripheral device. On the other hand, performing the device-side inspection step in the peripheral device 54 can serve the purpose of final check. As mentioned above, in addition to the misuse of the new program code by the user, there may also be malicious saboteurs who intend to paralyze the operation of the peripheral device 54 with an inapplicable new program code. After implementing the present invention, even if inapplicable new program codes are transmitted to the peripheral device 54, the device-side checking step in the peripheral device 54 can still prevent the inapplicable new program codes from replacing the existing firmware program codes. As for the present invention, the inspection module 56B (see FIG. 3 ) used to perform the device-side inspection step can be an actual hardware circuit, or the (existing) firmware program code executed by the control circuit 56 itself to realize the function of the inspection module 56B , to perform the device-side check step. In addition, as mentioned above, many independently operated devices, such as mobile phones and digital cameras, are also operated by the control circuit executing firmware program codes. Although these devices usually operate independently, when firmware updates are to be performed, most of them still need to cooperate with a host (as connected to a personal computer with a USB cable) to obtain new program codes for firmware updates and perform firmware updates. While the present invention can of course also be applied in this case, protecting these independently operated devices from being implanted with inapplicable firmware code during the firmware update process; especially in device-side checks performed by the device itself Steps that proactively ensure that the device itself is not mistakenly implanted with inappropriate firmware code.

In the known firmware update process, the content of the new program code used for the firmware update cannot be checked, so it is also impossible to prevent the inapplicable new program code from being mistakenly implanted into the peripheral device during the firmware update process. In contrast, the present invention adds a host/device-side inspection step in the firmware update process, which can determine whether the new program code is applicable based on the content of the new program code, and prevents the inapplicable new program code from being mistakenly implanted into the peripheral device . In addition, the present invention also facilitates the integration of firmware update procedures among different peripheral devices. Since the present invention can confirm whether the new program code for firmware update is applicable through the host/device side checking step, a single firmware update application program can be used on the host side as an interface for firmware update of different peripheral devices. When the host performs device identification, it can identify the type of peripheral device that needs to be updated with firmware, and the application program selects the host-side check steps corresponding to the peripheral device to confirm that the new program code obtained by the user is the applicable firmware code ; and different peripheral devices have their own built-in corresponding device-side inspection step implementation methods, which can further confirm that the new program code sent by the host is an applicable program code. In this way, the firmware update process between different peripheral devices can be integrated. Even if the same firmware update application is used, the firmware update of multiple peripheral devices can be managed, making it easier and more convenient for users to perform firmware updates. .

The above descriptions are only preferred embodiments of the present invention, and all equivalent changes and modifications made according to the claims of the present invention shall fall within the scope of the present invention.

Claims (27)

1. A method for updating program code in an electronic system, wherein the electronic system includes a host and a peripheral device; The peripherals include: A control circuit, used to execute a first program code to control the operation of the peripheral device according to the control command sent by the host; And this method contains: obtain a second program code; and Before replacing the first program code of the peripheral device with the second program code, a host-side check step is performed to use the host to check whether part of the second program code complies with a preset content, if the second program Part of the content of the code conforms to a preset content, then replace the first program code with the second program code; Wherein the preset content is a part of the first program code, or a constant recorded in the first program code; and when performing the checking step at the host end, check whether the second program code contains the first program code Part of a program code, or check whether the value of the constant recorded in the second program code is equivalent to the value of the constant in the first program code, or check whether the value of the constant recorded in the second program code is within the The value of the constant in the first program code is within a preset range. 2. The method according to claim 1, wherein the peripheral device further comprises a storage memory for storing the first program code in a non-volatile manner; and when the first program code is to be replaced by the second program code When, the first program code is erased from the storage memory, and the second program code is written into the storage memory. 3. The method as claimed in claim 1, wherein when performing the host side checking step before replacing the first program code with a second program code, the control circuit executes the second program code to control the peripheral device Before operation, perform this host-side check step. 4. The method of claim 1, wherein the default content is a fixed content, so that when the second program code changes, the default content will not change. 5. The method according to claim 1, wherein when performing the host-side checking step, the host reads a part of the content at a preset address in the second program code to check whether the part of the content conforms to the preset content, Or search whether the default content exists in the second program code. 6. The method of claim 1, further comprising: After performing the host-side checking step, if part of the second program code does not conform to the preset content, stop replacing the first program code with the second program code. 7. The method of claim 1, further comprising: After performing the checking step on the host side, if part of the content of the second program code matches the preset content, the second program code is used to replace the first program code, so that the control circuit can execute the second program code to achieve Control the operation of the peripheral device. 8. A method for updating program code in an electronic system, wherein the electronic system includes a host and a peripheral device; The peripherals include: a control circuit for executing a first program code to control the operation of the peripheral device; And this method contains: transmitting a second program code from the host to the peripheral device; and Before replacing the first program code with the second program code, a device-side checking step is performed to use the control circuit to check whether part of the second program code complies with a preset content, if the second program code If part of the content matches a preset content, the first program code is replaced with the second program code; Wherein the default content is a part of the first program code, or a constant recorded in the first program code; and when performing the device-side checking step, check whether the second program code has the first program code Part of a program code, or check whether the value of the constant recorded in the second program code is equivalent to the value of the constant in the first program code, or check whether the value of the constant recorded in the second program code is within the The value of the constant in the first program code is within a preset range. 9. The method according to claim 8, wherein the peripheral device further comprises a non-volatile storage memory for storing the first program code in a non-volatile manner; and when the second program code is to be replaced When the first program code is used, the first program code is erased from the storage memory, and the second program code is written into the storage memory. 10. The method according to claim 8, wherein when performing the device-side checking step before replacing the first program code with a second program code, the control circuit executes the second program code to control the peripheral device Before operation, perform this device-side inspection procedure. 11. The method of claim 8, wherein the default content is a fixed content, so that when the second program code changes, the default content will not change. 12. The method as claimed in claim 8, wherein when performing the device-side checking step, the control circuit reads a part of the content at a preset address in the second program code to check whether the part of the content matches a preset content , or search whether the default content exists in the second program code. 13. The method of claim 8, further comprising: After performing the device-side checking step, if part of the second program code does not conform to the preset content, stop replacing the first program code with the second program code. 14. The method of claim 8, further comprising: After performing the device-side checking step, if part of the second program code matches the preset content, the second program code is used to replace the first program code, so that the control circuit can execute the second program code to Control the operation of the peripheral device. 15. The method as claimed in claim 8, wherein the peripheral device further comprises a buffer memory for storing data in a volatile manner; and when performing the device-side checking step, the control circuit uses the second program code Temporarily stored in the buffer memory to read part of the second program code to perform the device-side checking step. 16. The method according to claim 15, wherein the peripheral device further comprises a non-volatile storage memory for storing the first program code in a non-volatile manner; and when the second program code is to be replaced When the device side checking step is performed before the first program code, the device side checking step is performed before the first program code is erased and before the second program code is written into the storage memory. 17. The method of claim 8, wherein the peripheral device is an optical disk drive. 18. A peripheral device comprising: a control circuit for executing a first program code to control the operation of the peripheral device; And the control circuit is provided with a checking module, and the checking module can check whether part of the content of the second program code conforms to a preset content before the control circuit replaces the first program code with a second program code, if the Part of the content of the second program code conforms to a preset content, then the second program code is used to replace the first program code; Wherein the preset content is part of the first program code, or a constant recorded in the first program code; Part of the program code, or check whether the value of the constant recorded in the second program code is equivalent to the value of the constant in the first program code, or check whether the value of the constant recorded in the second program code is within the first program code The value of the constant in a program code is within a preset range. 19. The peripheral device according to claim 18, further comprising a non-volatile storage memory for storing the first program code in a non-volatile manner; and when the control circuit is replaced by the second program code When the first program code is used, the first program code is erased from the storage memory, and the second program code is written into the storage memory. 20. The peripheral device according to claim 18, wherein when the control circuit replaces the first program code with a second program code and is inspected by the checking module, the control circuit executes the second program code to control the Before the operation of the peripheral device, it is checked by the check module. 21. The peripheral device as claimed in claim 18, wherein the preset content will not change when the second program code is changed. 22. The peripheral device according to claim 18 , wherein when the check module checks, the control circuit reads part of the content at the preset address in the second program code, so that the check module checks whether the part of the content complies with A default content, or search whether the default content exists in the second program code. 23. The peripheral device according to claim 18, wherein if the check module detects that part of the second program code does not conform to the preset content, the control circuit stops replacing the first program code with the second program code . 24. The peripheral device according to claim 18 , wherein if the check module checks that part of the second program code matches the preset content, the control circuit will replace the first program code with the second program code, so that The control circuit can execute the second program code to control the operation of the peripheral device. 25. The peripheral device as claimed in claim 18, further comprising a buffer memory for storing data in a volatile manner; and the control circuit temporarily stores the second program code in the buffer memory, and reads Part of the content of the second program code is checked by the checking module. 26. The peripheral device according to claim 24, which is used in an electronic system, in which a host is further provided, and the second program code is transmitted from the host to the peripheral device. 27. The peripheral device as claimed in claim 24, further comprising a non-volatile storage memory for storing the first program code in a non-volatile manner; and when the control circuit needs to use the second program code When the checking module checks before replacing the first program code, the checking module checks before the first program code is erased and the second program code is written into the storage memory.

Images