TW200928979A - System and method for updating firmware - Google Patents

Abstract

A system and a method for updating firmware are provided. The method for updating firmware is used for updating a first image of a first device. The first image has a first header, a first file system and a second file system. The method for updating firmware includes the following steps. Firstly, transporting the first header to a second device which has a second header and a third file system. Then, comparing the first header and the second header at the second device. Afterwards, merging the second header and the third file system into a second image at the second device. Next, outputting the second image to the first device. Then, updating the first file system of the first image into the third file system according to the second image.

Description

200928979 丨30PA IX. Description of the Invention: [Technical Field] The present invention relates to a firmware updating system and method, and in particular to a firmware update information for updating a partial file system SiS and methods. [Prior Art] An embedded system is a computer system that integrates software and hardware and has specific functions. Software for embedded systems is also known as firmware and includes a set of instructions that perform specific functions. Many electronic devices, such as personal digital assistants (PDAs), telephone systems, photocopiers, elevators, etc., are embedded systems. Because of the wide range of applications, and the industry department is committed to the fine-grained style; the new cause 4 such as: update (four) is currently a very important green topic. From the personal computer: connect the electronic device to the personal computer, and then download the complete image file. The ratio = the downloaded image slot and the electronic device. The image of the money is not the same. However, ▲ Μ, and update Disadvantages: The new firmware method has the following, and the entire image of the personal computer needs to know which parts need to be updated and renewed to the embedded system. field. Therefore, when the size of the firmware is increased, the code that does not need to be updated is also prepared and the time is wasted. m wheel to electronic device, so 6

30PA 200928979 First, since the entire floating system is located in the same image file, the parts that are not frequently updated, such as the kernel code or the boot code, are also transmitted to the electronic device and compared. This not only wastes frequency I but also reduces update efficiency. SUMMARY OF THE INVENTION Ο Ο 产 产 — — 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰 饰The file system that needs to be updated. A self-updating module update file system that merges the H-destination broadcast system and transmits it to the first device is placed. According to the present invention, the first and second embodiments include a device and a second body update system, a packet module and a self-updating module. The first - storage ^ purchase second file 荦 system. The transmission module is used to output the first gear. According to the second image, the update is poor, and the ',· is used for the root and the m-like slot. The second device includes a second storage unit and a second two-two: parallel group. The second storage unit is configured to store the second file system. The comparison module is configured to receive the first gear and compare the j head and the second gear. The merge module is used to: System: output the second image file. Self-updating mode Updates the first-slot system to the third-segment system. As for the second aspect of the broadcast, the second aspect of the book is proposed to update the first device. The first image broadcast has the first: 7

30PA 200928979 head, first-standard system and second slot system. The mobile update method is as follows. First, the first header is transmitted to the second device. The first and third file systems. Then in the second device: the second slot head and the second gear head. Then m is placed in combination with the second: the standard system is in the second image file. Secondly, the second image slot is output. Second device. In addition, the first image is updated to the third file system according to the third image file. Field file 糸❹ In order to make the above content of the present invention more obvious and easy to understand, the following examples are optimized and cooperated. The drawings are described in detail below: burdock [Embodiment] Please refer to Fig. 1, which shows a schematic diagram of a reticle updating system according to a preferred embodiment of the present invention. The second device 120. The first device U0 and the second device 120 are respectively a personal device and a personal computer, or for example, a personal and a remote server respectively. The first device 11 includes a first storage unit (1) and a transmission module. Ιΐ2 2 I update the module 113. The first storage unit 111 is, for example, a read-only memory (read-plus 1 y memory), a flash-only memory (f 1 ash brain), or an electrically erasable programmable only Read memory (eleetriealiy_erasabie programmabl e ROM, EEPR0M) The first storage unit ln is used to store the first image file 114. The first image slot 114 has a first slot head ιΐ5, a first file system 116 and a second slot system m. The first standard system The ΐ6 and the second file system 117 are, for example, coded and preferably have different functions.

丨 30PA 200928979 code. The first floor 115 has information on the first standard system 116 and the second floor system 117. In this embodiment, the first file system 116 is a code to be updated and the second file system 117 is a code that does not need to be updated as an example. The transmitting module 112 is configured to output the first gear head 115 to the second device 120. The self-updating module 113 is configured to receive a second image from the second device 12 (not shown) and update the first image 114 according to the second image. The device 120 includes a first storage unit cl, a comparison module 122, and a merge module 123. The second storage unit 121 is configured to store the second gear head 124 and the third slot system 125. The second header 124 has a third telegram system ι25. The third file system 125 is, for example, a code and is the code of the first device 11 to be updated. The comparison module 122 is configured to receive the first head 1丨5 from the first set 11〇 and compare the first head 115 and the second head 124. Combination, mode, and 123 are used to merge the second broadcast header 124 and the third standard system. 25% of the first image file, and output the second image file to the first device 11A. The self-improvement pull group 113 updates the first file system Π6 of the first image file 114 to the third file system 125 according to the second image file. The firmware update system 100 of the present embodiment communicates with the update module 122 and the comparison module 122. The first setting = only the first header U5 is output from the transmitting module 112 to the comparing module 122' of the second device 12A to find the file system that needs to be updated. Therefore, the time taken to compare the file systems of the first device 11 and the second device 120 can be greatly reduced. In addition, the file system and the file header that need to be updated are merged into a new image file by the merge module 123 of the second device 120. The first 9 ίΟΡΑ 200928979 device no self-updating module 113 updates the old image broadcast according to the new image tag. The first device no only receives the slot system and the header that need to be updated, so the update efficiency can be greatly improved. Furthermore, the building (4) that does not need to be updated will not be transmitted to the first device 11', thereby saving update time. In the present embodiment, the first device 11 〇 {column is directly connected to the second device 12 如 through a connection bee (_ port) such as RS-232 or a universal sequence bus (universai bus ’ USB). In addition, the first device 11 can also communicate with the triviai fiie transfer protocol (TFTP) server of the second device 120 through a network interface card (netw〇rk interface(3) ratio, €> NIC). The self-renewing fork group 113 updates the first floor 115 to the third head 131 according to the third file system 125 and the second file system 117 (shown in Fig. 2). The third gear head m, the third slot system 125 and the second file system 117 are second image stops 130 (% shown in Figure 2). Please refer to FIG. 2 and FIG. 3' for a schematic diagram of the third image file, and FIG. 3 for a schematic diagram of the image file recording label of FIG. As shown in Fig. 2, the second image file 13A includes a third file header 131, a third file system 125, and a second file system ι17. In the present embodiment, the third gear header 131 includes an image checksum (132), an identifier (vender) 133, a version (reversi〇n) code 134, an image size 135, and an image. An image record tag 136 and a reverted bit 137. The image file check value 132 is used to check the integrity of the third image file 130. The image file check value 132 is, for example, 4 bits, and the image file check value 132

The number of bits in ^OPA 200928979 is not limited to this. The identification code 133 is used to record the manufacturer information. The identification code is for example a constant. In the present embodiment, the identification code 133 is 4 bits, but the number of bits is not limited thereto. The version code 134 is used to record the version of the third image file 13〇. In the present embodiment, the version code 134 is 4 bits, but the number of bits is limited to this. The image size field 135 is used to record the third image slot 13

small. In the present embodiment, the image size field 135 is 4 bits, and the number of bits is not limited thereto. & image record tag 136 is used to record the information of the third standard system 125 and the 117th. As shown in FIG. 3, the image file record label includes a first-sub-image file mark 138, a first sub-image structure shift position 141, an image file size block (10), and a first-sub-image check value image. The code 142, the second sub-image slot label 143, the J-th shift field 144, the second sub-image size field 145, the 々, the image check value 146, and the second sub-image version code 147. For the second: the image ^ 138 and the second sub-image file label 143 respectively recorded the m system 125 and the second Tan (four) reconciliation 17 = identification program. The first-sub-image 檑 label 138 and the first-sub-two: iron U3 are each a constant. In the present embodiment, and j43 are each 4-bit, but the number of bits is not limited to ^. 125th place; first son: superscript: rotten f 139 used to record the third case system to move the block 144~ use the tt sub-image to use the position 己5 has recorded the younger brother a file 糸 system 117 is located in the third gear head 耵11

Relative position after 30PA 200928979. In the present embodiment, the sub-file shift positions 139 and 144 are respectively 4-bits. However, the number of bits is not limited thereto. The first sub-image size block 140 and the second sub-image size block 145 are used to record the size of the third file system 125 and the second file system 117, respectively. In this embodiment, the sub-image size block 14〇 and the 145 are respectively 4-bit, but the number of bits is not limited thereto. The first sub-image check value 141 and the second sub-image check value 146 are used to check the integrity of the third file system 125 and the second file system 分别7, respectively. In the present embodiment, the sub-image file check values 141 and 146 are = 4 bits. However, the number of bits is not limited thereto. The first sub-image broadcast version code 142 and the second sub-image file version code 147 are used to record the versions of the third file system 125 and the second file system U7'', respectively. In the present embodiment, the sub-image block version codes 142 and 147 are respectively 4-bit units. However, the number of bits is not limited thereto. ‘ Other bits. As shown in Fig. 2, the reserved bit 137 is used to reserve the third file 131 to a fixed size. In this embodiment, the reserved bit 137 retains the first header 131 to 1024 bits, but the reserved bit 137 may remain in the embodiment, and the image record label 136 is in the second gear (138 and 143), two sub-image file shift intercepts 144), two sub-image weight size blocks (mo and; [45), two sub-images & (139 and two sub-images 147) as an example for practical application If the file check value (141 and 146) and the two sub-image file version codes (μ), and

12

In the 30PA 200928979 system, the image record record label 136 further includes a third sub-image file tag, a third sub-image file shift block, a third sub-image size block, a third sub-image check value, and a third sub-image. File version code. In addition, although the third image file 130 is taken as an example here, the first image file 114 and the second image file also have similar data forms. That is, the first image file 114 and the second image file have image file check values, identification codes, version codes, image size field fields, image file record labels, and reserved bits, respectively. Among them, the image file record label includes a sub-image file label, a © sub-image file shift block, a sub-image size block, a sub-image check value, and a sub-image file version code. It is determined whether the first image file 114 needs to be updated, and the version code of the first file header 115 and the version code of the second file header 124 are compared by the comparison module 122. If the first image file 114 needs to be updated, the comparison module 122 compares and records the sub-image file version code of the first file system 116 version, records the sub-image file version code of the second file system 117 version, and records the third file system. The sub-image file version code of version 125 to find out which files need to be updated. The following is a more complete flowchart to illustrate the firmware update method. Please refer to FIG. 4, which is a flow chart showing a method for updating a firmware according to a preferred embodiment of the present invention. Please also match the component numbers in Figures 1 to 3. First, in step S410, the transmitting module 112 of the first device 110 transmits the first gear 115 to the second device 120. Next, in step S420, the comparison module 122 of the second device 120 compares the first gear head 115 and the second gear head 124. 13) 0ΡΑ 200928979 Person, and then, in step S430, the merge module 123 of the second device 120 merges the first file header 124 and the third file system 125 into a second image file. Next, step S440 is implemented to output the second image file to the first device 110. Moreover, in the sieving step S45, the self-updating module 113 of the first device 110 updates the first file system 116 of the first image broadcast 114 to the third file system 125 according to the second image broadcast. Finally, in step S46, according to the second file system 117 and the second, the case system 125 updates the first slot head 115 to the third gear head 131. The first dead head 131, the second file system 125, and the second file system 117 are the third image structure 130. Referring to Fig. 5, the fourth flowchart of Fig. 4 is a detailed flowchart for updating the first header to the third header. First, the implementation step is programmed to update the first sub-image slot of the third header 131 according to the money of the third slot system 125. After the step S462, the third slot system 125 is located. The relative position after the second gear 131 updates the first sub-image shift stop 139 of the third gear head 131. In addition, since the third image marker 13 〇 preferably stores all the broadcast systems continuously, the storage location of the second landmark system ... will also change. Therefore, the step of implementing 63 updates the second sub-map shift field 144 of the first 131 according to the relative position of the second system 117 after the third head 131. Next, step S464' is implemented to update the first sub-image size block 140 of the third head 131 according to the size of the third broadcast system 125. then,

50PA 200928979 Implementation step S465, the image of the root flute-131 is updated to the third header by the size of the ten-dimensional three-channel slot 130, > Then, the solid half-image check value 14^S466' is based on the integrity of the third broadcast system 125 as determined in step S467 according to the first sub-portion of the third play head 131. This value 132 checks the first: dry second, according to the image of the third gear head 131 check no can read the integrity of the 13G to ensure that the first device subscribes to the second image 130. Ο Next, the third slot header 13 1 is not ' according to the second file system 125 as shown in step S469. Then, F, ten, and 1, the version code 134 of the third header 131 is updated. 〇中,第“装"^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ In addition, the second dream office compares the file system and the file headers that need to be updated into the first:,: and the core group will only need to update the file system, "image block" and transmit to the first device. - Water's brother--the device's _ 毋 毋 this > and that π L I update the group can update the 笫 image edge according to the second image file. Therefore, there are some advantages of the τ column: (4) Update the younger - the ruler can decide Find out the files that need to be updated. The production-hundred size is extremely small, so by the threat K (four) line. The new system of the file system is quite fast ^ "- slotted way to find out that it needs to be more The second device only transmits the reverse: the size of the file system is increased to increase the update efficiency. The size of the broadcast system is reduced. This field ^2^ can effectively rate. More effective to increase the update effect 15

30PA 200928979 Third, configuration flexibility. Developers can configure some of the file systems they want to update or change, thus increasing the flexibility and efficiency of development. Fourth, save bandwidth. The second device only needs to transmit the file system to be updated by the first device, so that the bandwidth can be effectively saved. In view of the above, the present invention has been disclosed in a preferred embodiment, and is not intended to limit the present invention. It is to be understood by those skilled in the art that various changes and modifications can be made without departing from the spirit and scope of the invention. Therefore, the scope of the invention is defined by the scope of the appended claims. 16

30PA 200928979 [Simplified Schematic] FIG. 1 is a schematic diagram of a firmware update system according to a preferred embodiment of the present invention; FIG. 2 is a schematic diagram of a third image file; FIG. 3 is a second diagram FIG. 4 is a flow chart showing a method for updating a firmware according to a preferred embodiment of the present invention;

Figure 5 is a detailed flow chart showing the update to the third configuration in Figure 4. [Main component symbol description]

100 firmware update system 110 first device 111 first storage unit 112 transfer module 113 self-updating module 114 first image mark 115 first file header 116 first file system 117 second file system 120 second device 121 second Storage unit 122 comparison module 123 merge module 124 second file header 17 10?Α 200928979 125: third file system 130: third image file 131: third file header 132: image file check value 133: identification code 134 : Version code 135: Image size field 136: Image file record label 137 137: Reserved bits 138, 143: Sub-image file labels 139, 144: Sub-image file shift stops 140, 145: Sub-image size block 141, 146: sub-image file check value 142, 147: sub-image file version code

18

Claims (1)

^OPA 200928979 X. Patent application scope: 1. A firmware update method for updating one of the first devices - an image file. The first image file has a first header, - 歹:: The case system and a second slot system, the lion update method includes: "" transmitting the first gear to a second device, the first having a second gear and a third file system; ❹ Ο (b) Comparing the second device with the first header and the second header; (C) combining the second header and the third file system with the second device into a second image; /~, (d Outputting the second image file to the first device; and (e) updating the file system to the third file system according to the second image file. The first "I. The object updating method according to Item 1 of the patent scope, wherein the 5th step (b) comprises the following steps: a version of the head and a version of the second head; and a comparison 兮1^#社 version and material _ The same version of the forest, then i: the version of the case system, the version of the second file system and the version of the spear one tea system 3. If the second paragraph of the patent application scope includes the following H-body update method, the first-order third-term system describes the m-th system, and the new field is the third-order head, the third file. The head, the 兮 产 产 及 及 及 及 及 及 及 及 及 及 及 及 及 及 及 及 及 及 及 19 19 19 19 19 19 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 The method, wherein the step (f) comprises the following steps: the code of the early second slot system 'updates the first sub-image file label of one of the third headers. The new method described in the second == item in V, It is more: the shape (four) relative position according to the second case = the image and the third bit head of the first bit after the first bit of the second bit "the second image file, the displacement field. 6. For example, the third step of the scope of the patent application scope (1) includes the following H-return (four) update method, according to the third trough case, a sub-image size, the position r is small, and the third structure is updated. 7. If the scope of the patent application is stipulated, the step (1) includes the following steps: the firmware update method, which is based on the version of the second file system of the 5H-sub-image file version code. Updating one of the second gears of the second section. 8. In the third paragraph of the patent application, the step (1) includes the following steps: the method for updating the object according to the third gear, which is based on the completeness of the third file system. Sex. The sub-image file check value is checked. The step (1) in the second part of the patent application scope includes the following steps: 31, the method for updating the service body, and 20 30PA 200928979 updating the version number of the third play head. 10. The step (1) of claim 3 includes the following steps: an update method that updates the block size block based on the size of the second image. - ^ One image U. As in the third paragraph of the patent application, the step (1) includes the following steps: the secret update method, and its refinement according to the third broadcaster left. Tian Shuo's private check value, verifying the completion of the third image file. 12. The firmware update system includes: the device, comprising: a first storage unit for storing a first image file having a first梓海's two-fold deposit $-image file system; a younger brother 33 ’s, a first broadcast system and a first. The-file-transmission module for outputting the first-player, ❹ and 自我 self-updating mode a second device for updating the second device, including: _ _ a second storage unit for storing - the __ second file system; a first head and a first matching module for receiving the first slot head and the second gear head; and the first module is configured to merge the second head and 4 The case system outputs the second image file, and the self-updating module root 21 I0PA 200928979 is updated to the third file system according to the δ 弟 一 映像 image. 13. As claimed in claim 12, wherein the comparison module updates the system, the version of the system, the version of the third file system, and the file system of the second file than the first standard (4). Version to find out what needs to be updated ❹ 14. If the patent application scope is the 12th top, the self-updating module updates the first-slot head to the third-order second brother according to the first system, and the case system and the third instance system are A third = header " wherein the ^^范(四)14 朗 ❹ 更新 更新 更新 更新 更新 更新 更新 更新 image image image image image image image image image image image image image image image image image image image image image image image image 。 。 The firmware update system is configured to record the third image file. 16. The scope of the third slot includes: a version (reversion) code, version. 17. The firmware update system of claim 5, wherein the third file header comprises: an image size block for recording the size of the third image file. 18. The firmware update system of claim 14, wherein the third file header comprises: 22) 0? Α 200928979 an identification code (vender) for recording manufacturer information; and a reservation (reversed) a bit to reserve the third header to a fixed size. 19. The firmware update system of claim 14, wherein the third gear header further comprises: an image record tag for recording the second file system and the third file system News. 20. The firmware update system of claim 19, wherein the image record label comprises: a first sub-image tag for recording the code of the third file system And a second sub-image file tag for recording the code of the second file system. 21. The firmware update system of claim 19, wherein the image record tag comprises: a first sub-image offset block, and ◎ to record the third file system a relative position after the third gear head; and a second sub-image shifting displacement position for recording a relative position of the second file system after the third gear head. 22. The firmware update system of claim 19, wherein the image record tag comprises: a first sub-image size field for recording the third file system Size; and 23 30PA 200928979 A second sub-image size of the shelf 'used to record the size of the second standard system. 23. The firmware update system of claim 19, wherein the image mark record includes: a first sub-image checksum for checking the third file system Integrity; and a second sub-image check value to check the integrity of the second file system.韧 24. The firmware update system of claim 19, wherein the image broadcast record comprises: a first sub-image reversion code for recording the third file system a version; and a second sub-image version code for recording the version of the second file system. 〇 24