200841245 TW3367PA β 九、發明說明： 【發明所屬之技術領域】 本發明是有關於一種通用序列匯流排（Un i ver sa 1 serial bus，USB)周邊裝置之韌體更新方法，且特別是 有關於一種可同時更新多個通用序列匯流排周邊裝置之 韌體之韌體更新方法。 【先前技術】 通用序列匯流排（Universai serial bus，USB)儲 子衣置之早刃體，當因生產問題導致錯誤，或因勃體過時等 種_素:可能需要進行更新。#腿儲存裝置之動體需 進=更新時，係以傳統韌體更新方法來更新USB儲存裝置 2韌體。應用傳統韌體更新方法，工廠操作員一次僅能對200841245 TW3367PA β IX. Description of the Invention: [Technical Field] The present invention relates to a method for updating a firmware of a peripheral device of a universal serial bus (USB), and particularly relates to a method A firmware update method for firmware of a plurality of universal serial bus peripheral devices can be simultaneously updated. [Prior Art] The Universal Servo Bus (USB) store is placed on the early blade, when it is caused by a production problem, or because it is out of date, etc.: It may need to be updated. When the mobile device of the leg storage device needs to be updated, the firmware of the USB storage device 2 is updated by the traditional firmware update method. With traditional firmware update methods, plant operators can only
们USB儲存裝置進行更新。然而，當需要大量更新MR 褚存裝置％•，上述傳統韌體更新方法十分耗時，使得生產 效率大大降低。 【發明内容】 本發明提出一種韌體更新方法，用於一多執行緒 ^ulti-thread)之作業系統，用以更新複數個通用序j ^流排（Universal serial bus，USB)周邊裝置之韌體 =括·（a)偵測該些通用序列匯流排周邊裝置；（b)取得』 用序列匯流排周邊裝置之管線（pipe)控制權；以』 C)更新該些通用序列匯流排周邊裝置之韌體。 20084 1245tw336tpa " 本發明另提出一種韋刃體更新方法，用於一多執行緒 (Muni-thread)之作業系統，用以更新複數個通用序列 匯流排（Universal serial bus，USB)周邊裝置之勒體， 包括··（a)偵測該些通用序列匯流排周邊裝置；（b)取得該 些通用序列匯流排周邊裝置之管線（pipe)控制權；（c) 更新該些通用序列匯流排周邊裝置之韌體；（d)判別各該 '些通用序列匯流排周邊裝置之韌體是否更新完成；（幻重 置該些通用序列匯流排周邊裝置中，更新完成之USB周邊 • 裝置；（f)重新偵測該些更新完成之通用序列匯流排周邊 裝置；（g)取得該些更新完成之通用序列匯流排周邊裝置 之控制權；以及（h)讀取並驗證各該些更新完成之通用序 列匯流排儲存裝置中之韌體正確與否。 為讓本發明之上述内容能更明顯易懂，下文特舉·一較 佳實施例，並配合所附圖式，作詳細說明如下： 【實施方式】 第1圖繪示本發明實施例之韌體更新方法之流程 圖。此韌體更新方法係用於一多執行緒（Multi_thread) 之作業系統，用以更新數個通用序列匯流排（Universal serial bus，USB)周邊裝置之韌體。本發明實施例之韌 體更新方法係以用於視窗作業系統χρ版（Wind〇ws χρ) 為例。本發明實施例之韌體更新方法係以更新USB儲存裝 置’例如是非及閘快閃記憶體（NA_ fiash)，的韌體為 例作說明。 200841245rW3367PA ——————---------------------- B 茲說明本發明實施例之韌體更新方法。請參考第1 圖。首先，在步驟110中，偵測USB周邊裝笔。對於每個 USB周邊裝置，當其插入（piug-in)時，視窗作業系統會 透過USB周邊裝置的控制端點（control endpoint)來價 測並辨識出USB周邊裝置。在本發明實施例中，視窗作業 系統會辨識出此USB周邊裝置為USB儲存裝置。 之後’在步驟120中，取得USB周邊裝置之管線（Pipe ) 控制權。在本發明實施例中，使用一視窗驅動模型 • (Windows driver model，WDM)低階過濾驅動程式（WDM lower filter driver)來取得USB周邊裝置的控制權。 由於視窗作業系統在偵測到所插入的USB周邊裝置 後，即會將USB周邊裝置的管線（Pipe)控制權交至視窗 作業系統之對應之内建驅動程式，由此内建驅動程式來控 制USB儲存裝置。如此一來，便無法更新usb周邊裝置的 韌體。 因此，在本發明實施例中，當視窗作業系統一偵测出 ⑩所插入的USB周邊裝置後，在視窗作業系統之内建驅動程 式取得USB周邊裝置之管線控制權之前，即使用上述低階 過濾驅動程式來攔截取得USB周邊裝置之管線控制權。在 本發明實施例中，此管線即為USB儲存裝置在收送資料 (bulk in / out)時所使用的管線。 對於每個USB周邊裝置，在上述低階過濾驅動程式取 得其管線控制權後，始得以更新其韌體。在步驟13〇中， 更新USB周邊裝置之韌體。由於視窗作業系統為多執行緒 200841245rW3367PA s_____ _______ .作業系統，因此本發明實施例之勃體更新方法可設計為以 多執行緒方式，執行步驟1 1 〇至1 。 m' 如此一來’本發明實施例之韋刃體更新方法，可以同時 更新數個周邊裝置之勃體。當需大量更新USB周邊裝 置之拿刃體時，本發曰月實施例之勃體更新方法可大幅節省時 間。 在對s肖邊裝置進行韋刃體更新之後，本發明實施例 之早刃體更新方法更可用以驗證周邊裝置更新過後的韋刃 •體資料是否正確。在步驟140中，SUSB聽裝置之章刀體 更新完成，重t USB胃邊裝置。#騰周邊裝置之勒體更 新完成後，USB周邊裂置之已更新過的勤體係對腦周邊 裝置本身進行重置。 之後，在步驟15〇中，重新偵測USB周邊裝置。同樣 地’ USB周邊裝置違行重置後，視窗作業系統會透過脱 周邊裝置的控制端點來偵測並辨識出USB周邊裝置。 鲁 在步驟160中，同樣地，重新取得USB周邊裝置之控 制權。在本發明實施例中，同樣使用WDM低階過濾驅動程 式來取得USB周邊襞置的控制權。在視窗作業系統之内建 驅動程式取得USB周邊裝置之管線控制權之前，即使用上 述低階過濾驅動程式來攔戴取得USB周邊裝置之管線控制 權。 在上述低階過濾驅動程式取得USB周邊裝置之管線 控制權後，始得以讀取USB周邊裝置之韌體的資料。在步 驟170中，讀取並驗證USB周邊裝置之韌體資料正確與Our USB storage device is updated. However, when a large number of MR memory devices are required to be updated, the conventional firmware update method described above is time consuming, resulting in greatly reduced production efficiency. SUMMARY OF THE INVENTION The present invention provides a firmware update method for a multi-threaded [ulti-thread] operating system for updating the integrity of a plurality of universal serial bus (USB) peripheral devices. Body = (a) detecting the peripheral devices of the general-purpose serial bus; (b) obtaining the control of the pipeline using the peripheral devices of the serial bus; updating the peripheral devices of the universal serial bus with "C) Firmware. 20084 1245tw336tpa " The invention further provides a method for updating the blade body for a multi-threaded operation system for updating a plurality of universal serial bus (USB) peripheral devices. The body includes: (a) detecting the peripheral devices of the universal sequence bus; (b) obtaining pipeline control of the peripheral devices of the universal sequence bus; (c) updating the peripherals of the universal sequence bus The firmware of the device; (d) discriminating whether the firmware of each of the peripheral devices of the universal serial bus is updated; (the resetting of the peripheral devices of the universal serial bus, the updated USB peripheral device; Re-detecting the updated universal sequence bus peripherals; (g) obtaining control of the peripherals of the universal sequence bus that are completed; and (h) reading and verifying the generalization of each of the updates Whether the firmware in the serial bus storage device is correct or not. In order to make the above content of the present invention more obvious and understandable, the following is a detailed description of the preferred embodiment and the detailed description of the present invention. The following is a description of the following: [Embodiment] FIG. 1 is a flowchart of a method for updating a firmware according to an embodiment of the present invention. The firmware update method is used for a multi-thread operating system for updating a plurality of general-purpose functions. The firmware of the peripheral device of the serial bus (USB). The firmware update method of the embodiment of the present invention is used for the Windows operating system (Wind〇ws χρ) as an example. The firmware of the embodiment of the present invention The update method is described by updating the firmware of the USB storage device, for example, the firmware of the flash memory (NA_Fiash). 200841245rW3367PA ——————------------- --------- B Describes the firmware update method of the embodiment of the present invention. Please refer to Figure 1. First, in step 110, the USB peripheral is installed. For each USB peripheral device, When it is inserted (piug-in), the window operating system will measure and recognize the USB peripheral device through the control endpoint of the USB peripheral device. In the embodiment of the present invention, the window operating system recognizes the USB. The peripheral device is a USB storage device. In step 120, the pipeline control of the USB peripheral device is obtained. In the embodiment of the present invention, a Windows driver model (WDM lower filter driver) is used to obtain the USB. Control of the peripheral device. Since the Windows operating system detects the inserted USB peripheral device, it will control the pipeline of the USB peripheral device to the corresponding built-in driver of the Windows operating system. Built-in drivers to control USB storage devices. As a result, the firmware of the usb peripheral device cannot be updated. Therefore, in the embodiment of the present invention, after the window operating system detects 10 inserted USB peripheral devices, the low-order step is used before the built-in driver of the window operating system obtains the pipeline control right of the USB peripheral device. Filter the driver to intercept pipeline control for the USB peripherals. In the embodiment of the present invention, the pipeline is the pipeline used by the USB storage device when bulk in / out. For each USB peripheral device, after the above-mentioned low-order filter driver obtains its pipeline control rights, its firmware can be updated. In step 13A, the firmware of the USB peripheral device is updated. Since the Windows operating system is a multi-threaded 200841245rW3367PA s_____ _______. operating system, the Bobbin updating method of the embodiment of the present invention can be designed to perform steps 1 1 〇 to 1 in a multi-threaded manner. m' Thus, the method of updating the blade in the embodiment of the present invention can simultaneously update the plurality of peripheral devices. When it is necessary to update the blade body of the USB peripheral device in a large amount, the method of updating the body of the present invention can save a lot of time. After the s-edge device is updated, the early blade updating method of the embodiment of the present invention can be further used to verify whether the updated blade data of the peripheral device is correct. In step 140, the chapter of the SUSB listening device is updated, and the USB stomach device is re-t. After the completion of the refresher of the #腾 peripheral device, the updated peripheral system of the USB peripheral splicing resets the brain peripheral device itself. Then, in step 15〇, the USB peripheral device is re-detected. Similarly, after the USB peripheral device is reset, the Windows operating system detects and recognizes the USB peripheral device through the control terminal of the peripheral device. In step 160, similarly, the control of the USB peripheral device is regained. In the embodiment of the present invention, the WDM low-order filter driver is also used to obtain the control of the USB peripheral device. Before the built-in driver of the Windows operating system obtains the pipeline control of the USB peripheral device, the above-mentioned low-order filtering driver is used to block the control of the pipeline for obtaining the USB peripheral device. After the low-order filter driver obtains the pipeline control right of the USB peripheral device, the firmware of the USB peripheral device can be read. In step 170, the firmware information of the USB peripheral device is read and verified correctly.
200841245 TW3367PA • 否。在本發明實施例中，比對由USB周邊裝置取得的更新 後的韌體資料與於步驟130寫入的韌體資料是否相同，進 而驗證USB周邊裝置之更新後之韌體資料正確與否。 第2圖繪示本發明另一實施例之韌體更新方法之流 程圖。在步驟210中，偵測數個USB周邊裝置，例如是USB 儲存裝置。在步驟220中，取得USB周邊裝置之管線控制 權。在步驟230中，更新USB周邊裝置之韌體。在步驟240 中，分別判斷USB周邊裝置之韌體是否更新完成。 ⑩ 對於韌體更新完成之USB周邊裝置，確認其更新之後 的韌體是否正確。在步驟250中，重置更新完成的USB周 邊裝置。步驟260中，重新偵測更新完成之USB周邊裝置。 在步驟270中，取得更新完成之USB周邊裝置之控制權。 在步驟280中，讀取並驗證各個更新完成之USB儲存裝置 中之韌體正確與否。 在步驟290中，對於在步驟240中判斷為未更新完成 之USB周邊裝置，以及在步驟280中判斷為更新韌體錯誤 _ 之USB儲存裝置，顯示其為韌體更新失敗。對於更新完成、 且更新後之初體為正確的USB儲存裝置，即表示其為韋刃體 更新成功。 上述兩實施例之USB儲存裝置係為SST ( 39VF010) -multi-purpose flash。 上述兩實施例之韌體更新方法係以用於視窗作業系 統XP版為例。實際應用上，可以用於任何支援多執行緒 之作業系統，例如LINUX，或其它版本之視窗作業系統。200841245 TW3367PA • No. In the embodiment of the present invention, whether the updated firmware data obtained by the USB peripheral device is the same as the firmware data written in step 130 is the same, thereby verifying whether the updated firmware information of the USB peripheral device is correct or not. FIG. 2 is a flow chart showing a method for updating a firmware according to another embodiment of the present invention. In step 210, a plurality of USB peripheral devices, such as a USB storage device, are detected. In step 220, the pipeline control of the USB peripheral device is obtained. In step 230, the firmware of the USB peripheral device is updated. In step 240, it is determined whether the firmware of the USB peripheral device is updated. 10 For the USB peripheral device whose firmware has been updated, confirm that the firmware after the update is correct. In step 250, the updated USB peripheral device is reset. In step 260, the updated USB peripheral device is re-detected. In step 270, control of the updated USB peripheral device is obtained. In step 280, the correctness of the firmware in each of the updated USB storage devices is read and verified. In step 290, for the USB peripheral device determined to have not been updated in step 240, and the USB storage device determined to update the firmware error _ in step 280, it is displayed as firmware update failure. For the updated USB storage device after the update is completed and updated, it means that the update is successful. The USB storage device of the above two embodiments is SST (39VF010) - multi-purpose flash. The firmware update method of the above two embodiments is taken as an example for the Windows operating system XP version. In practice, it can be used in any operating system that supports multiple threads, such as LINUX, or other versions of Windows operating systems.
200841245 TW3367PA 上述兩實施例之韌體更新方法雖以更新USB餘存事 置為例，實際應用上並不限於此。任何USB周邊裝置，例 如USB視訊攝影機（web-cam)、USB印表機，均可使用本 發明實施例之韌體更新方法，以多執行緒方式進行章刃體更 新0 由於視窗作業系統為多執行緒作業系統，因此上述兩 實施例之韌體更新方法可設計為以分時多工的多執行緒 方式來執行。因此，應用本發明實施例之韌體更新方法，200841245 TW3367PA The firmware update method of the above two embodiments is an example of updating the USB residual event, and the practical application is not limited thereto. Any USB peripheral device, such as a USB video camera (cam-cam) or a USB printer, can use the firmware update method of the embodiment of the present invention to perform chapter edge update in a multi-thread mode. The thread operating system, so the firmware updating method of the above two embodiments can be designed to be executed in a multi-threaded manner of time division multiplexing. Therefore, applying the firmware update method of the embodiment of the present invention,
可同時對數個USB周邊裝置進行韌體更新，並驗證更新後 的韌體資料正確與否。當需更新大量USB周邊裝置時，本 發明實施例之物體更新方法，可大幅節省所需的更新時 間。 、二上所述，雖然本發明已以一較佳實施例揭露如上 並非用以限定本發明。本發明所屬技術領域中具有土 ο識者在不脫_本發明之精神和範圍内，當可作各穿 潤飾。因此，本發明之保護範圍當視後附之申， 專利乾圍所界定者為準。The firmware update can be performed on several USB peripheral devices at the same time, and the updated firmware data is verified to be correct or not. When a large number of USB peripheral devices need to be updated, the object updating method of the embodiment of the present invention can greatly save the required update time. The invention has been described above with reference to a preferred embodiment, and is not intended to limit the invention. Those skilled in the art to which the invention pertains are not limited to the spirit and scope of the present invention. Therefore, the scope of protection of the present invention is defined by the appended claims, which are defined by the patent.
200841245TW3367PA • 【圖式簡單說明】 第1圖繪示本發明實施例之韌體更新方法之流程圖 第2圖繪示本發明另一實施例之韌體更新方法之流 程圖。 【主要元件符號說明】 無200841245TW3367PA • BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a flow chart showing a method for updating a firmware according to an embodiment of the present invention. FIG. 2 is a flow chart showing a method for updating a firmware according to another embodiment of the present invention. [Main component symbol description] None
1111