TWI480799B - Method and equipment for upadating firmware of embedded system - Google Patents

Description

Firmware update method and device for embedded system

The invention relates to a firmware updating method and device, and in particular to a firmware updating method and device for an embedded system.

The Embedded System is a dedicated computer system designed for a specific application, which includes all computers except general computers for general purpose purposes. Embedded system applications can be seen from the mobile music player to the real-time control subsystem of the space shuttle. Unlike a typical PC system that can handle a variety of tasks, an embedded system can only perform tasks for specific purposes. In addition, embedded systems have some basic features that must be met, such as security and availability. In addition, other features may require lower or no requirements, simplifying the hardware of the embedded system to reduce costs. For embedded systems that are mass-produced, reducing costs is often the primary consideration in design. Therefore, embedded systems often need to simplify the removal of unwanted features to reduce costs.

The core of an embedded system consists of one or several microprocessors or microcontrollers that are pre-programmed to perform a few tasks. And the general personal computer can execute various software installed by the user, and the software on the embedded system is usually temporarily unchanged, and thus is called firmware.

In terms of firmware, the manufacturer will provide firmware to download updates for customers. However, in the firmware update phase, the current processing method is to update the firmware content to the memory at one time. Therefore, when updating the firmware, it is necessary to interrupt the operation of the current device in order to use the new function. Such an operation It is inconvenient for the user, and it takes a long time to reboot the system when updating the firmware.

In view of the problems caused by the prior art, the present invention provides a firmware updating method and system for an embedded system to overcome the problems caused by the prior art.

One aspect of the present invention is to provide a firmware update method for an embedded system.

According to an embodiment of the present invention, a firmware update method for an embedded system includes: executing a plurality of functional modules of the embedded system, wherein the functional modules are executed according to corresponding firmware stored in the original data storage block. A module update table is provided for recording the current firmware version data of each function module. A firmware update file with updated version data is received from the server, wherein the firmware update file is used to update at least one target module in the function module to the updated firmware version data. The firmware version data is input into the module update table, so that at least one target module has both the current firmware version data and the updated firmware version data in the module update table. The firmware update file overwrites the firmware of the corresponding at least one target module in the original data storage block and determines whether the firmware is completely overwritten. When the firmware update file completely overwrites the firmware of the at least one target module in the original data storage block, at least one firmware is re-initiated according to the firmware of the at least one target module after the original data storage block is overwritten. a target module and a functional module responsive to at least one target module, wherein when at least one target module and a functional module responsive to at least one target module are reinitiated, other functional modules of the embedded system It continues to execute.

Another aspect of the present invention is to provide a firmware update device for an embedded system.

According to another embodiment of the present invention, a firmware update device for an embedded system includes a storage device and a processor. The storage device has fixed access memory and random access memory. The fixed access memory has a module update table. The processor is electrically connected to the storage device, and includes: a function module execution unit, an update receiving unit, a login unit, an overwriting unit, and an initial unit. The function module execution unit is used to execute several functional modules of the embedded system. The update receiving unit is configured to receive the firmware update file with the updated version data from the server and store the firmware update file in the storage device. The login unit is used to log the updated firmware version data into the module update table. The overwrite unit is configured to overwrite the firmware update file with the firmware of the corresponding target module in the original data storage block and determine whether the firmware is completely overwritten. When the firmware update file completely overwrites the firmware of the corresponding target module in the original data storage block, the initial unit is used to re-initialize the target model according to the firmware of the target module after the original data storage block is overwritten. Groups and functional modules that are dependent on the target module.

The application of the present invention has the following advantages. When the firmware is updated, the embedded system of the present invention can separately update the function modules that need to be updated, and then only need to initialize the function modules that receive the update and the function modules that are dependent on them. Therefore, the embedded system does not need to restart the entire system after the firmware update is completed. Other functional modules that do not have firmware updates can continue to function.

In addition, the user can determine the firmware version data of the current function module via the module update table. Therefore, the user can know the development status of the function module from the firmware version data, and then determine whether the firmware of the function module needs to be advanced. Line updates. Therefore, the present invention can determine whether the function module in the embedded system needs to be firmware updated according to the needs of the user.

The spirit and scope of the present invention will be described in the following detailed description of the preferred embodiments of the present invention, which can be modified and modified by the teachings of the present invention. The spirit and scope of the present invention.

Please refer to FIG. 1 , which is a flow chart of steps of a firmware update method 100 for an embedded system according to an embodiment of the invention. As shown in FIG. 1, the firmware update method 100 of the embedded system includes the following steps:

In step 110, a plurality of functional modules of the embedded system are executed. The function module is executed according to the corresponding firmware stored in the original data storage block. For example, an embedded system can be divided into a graphical user interface (GUI) class, a processing system class, and a driver class according to functional attributes. Further, the embedded system may be subdivided into several functional modules according to different functional attributes within the user interface class, the processing system class, and the driver device class. Each functional module has a corresponding firmware in the original data storage block, and the function of the functional module is performed by the associated firmware. In this implementation, the original data storage block is located in a fixed access memory. For example, the fixed access memory can be a flash memory, a non-Volatile Random Access Memory (NVRAM), or other storage element that can be accessed. In addition, the execution of the embedded system includes a microprocessor or microcontroller pre-programmed to perform a few tasks to execute the embedded system. Each function module.

In step 120, a module update table is provided to record the current firmware version data of each function module. The firmware version data includes the firmware version of the firmware of each function module in the original data storage block, and the firmware version data may include the version number of the firmware information. Therefore, each function module and its corresponding current firmware version data can be displayed in the module update table for the user to understand the firmware update status of the function module.

In step 130, a firmware update file with updated version data is received from the server. In this embodiment, the target module in the function module can be updated by using the firmware update file, and the target module is updated to an updated firmware version data by using the firmware update file. However, in some embodiments, the firmware update file may simultaneously update a plurality of target modules in the function module, so that several target modules in the function module are simultaneously updated to an identical updated firmware version data. The updated firmware version data may include the version number of the updated firmware information.

In step 140, the updated firmware version data is registered in the module update table. In this embodiment, each target module in the function module can have both the current firmware version data and the updated firmware version data in the module update table. However, the module update table can display the current firmware version data and the updated firmware version data of the target module (the target module is a functional module that can receive the firmware update file update), and the user can update the table via the module. The version number of the current firmware information of the target module that can receive the firmware update file update and the version number of the firmware update information of the firmware update file are known. Therefore, the user can compare the two versions of the data to determine whether to update the target module.

However, when the target module is plural, the user can pick up a plurality of target modules that can be firmware updated by using the information provided in step 140. Select and select at least one target module for firmware update.

In step 160, the firmware update file is overwritten with the firmware of the corresponding target module in the original data storage block. In this embodiment, the target module has the current firmware version data and the updated firmware version data in the module update table. When the firmware version data and the updated firmware version data are the same, the firmware is not updated. The file overwrites the firmware of the corresponding target module in the original data storage block, and indicates that the firmware update of the embedded system is not performed.

In addition, in step 170, it is determined whether the firmware update file completely overwrites the firmware of the corresponding target module in the original data storage block.

In step 180, when the firmware update file completely overwrites the firmware of the update module, the target module and the target module are re-initiated according to the firmware of the target module after the original data storage block is overwritten. Dependent function module. Several functional modules are functionally dependent, so when re-initializing one of the functional modules, several other functional modules that are initially dependent are required. Therefore, after the firmware of the target module is overwritten by the firmware update file, the target module and other functional modules that are dependent on the target module are initialized, so that the target module after the firmware update can be Interoperate normally with other dependent function modules.

Therefore, when the firmware update file completely overwrites the firmware of the update module, other functional modules that have not been initialized can still perform their functional operations. The embedded system described in this embodiment does not completely complete the process of updating the firmware of the module due to the firmware update file, so that the entire system is completely stopped.

In addition, in this embodiment, before the firmware update file is overwritten with the firmware of the corresponding target module in the original data storage block (step 160), The firmware of the target module in the original data storage block is further stored to the temporary data storage block (step 150). Therefore, when the firmware update file does not completely overwrite the firmware of the target module, the firmware of the target module stored in the temporary data storage block is rewritten back into the original data storage block (step 190). The temporary storage data storage block in the embodiment is located in the random access memory. However, in some embodiments, after the firmware update file does not completely overwrite the firmware of the corresponding target module in the original data storage block, update failure information may be sent (step 192) to inform the user that the firmware update failed. . After the firmware update file completely overwrites the firmware of the corresponding target module in the original data storage block, the update completion information is sent (step 182) to inform the user that the firmware update is successful.

Please refer to FIG. 2, which is a flow chart showing the steps of step 150a in the firmware update method of the embedded system according to FIG. 1. As shown in FIG. 2, when the target module is plural, after the firmware of the target module in the original data storage block is stored in the temporary data storage block (step 150), the selected target mode is determined. Whether the group is performing an operation in the embedded system (step 152). When the selected target module is a target module that is not in operation, the firmware update file overwrites the firmware of the corresponding selected target module in the original data storage block (step 160), and then performs the first step. The flow of steps described in the figure.

In addition, when the selected target module is performing the operation, the execution of the selected target module and the function module corresponding to the selected target module is stopped (step 154), and the firmware update file is overwritten. The firmware of the selected target module in the original data storage block is written (step 160), and the step flow as described in FIG. 1 is performed.

Please refer to FIG. 3, which is a functional block diagram of a firmware update device 200 of an embedded system according to still another embodiment of the present invention. The firmware update device 200 of the embedded system includes a storage device 220 and a processor 210.

The storage device 220 has a fixed access memory 222 and a random access memory 224 (Random Access Memory, RAM), wherein the fixed access memory 222 stores a module update table. For example, after the graphical user interface (GUI) class, the processing system class, and the driver class in the embedded system, each class is further classified into several function modules according to different functional attributes. However, each functional module has a corresponding firmware and stores the firmware in the fixed access memory 222. In addition, the firmware may include a corresponding function module name, version data, and firmware code. The firmware update table can be used to record the firmware version data of several functional modules of an embedded system. In addition, in some embodiments, the fixed access memory 222 can be a flash memory, a non-Volatile Random Access Memory (NVRAM), or other storage elements that can be accessed. In other embodiments, the random access memory 224 can also be replaced by other memory used as the primary memory of the embedded system.

The processor 210 stores the firmware update file from the server 300 through the output input interface 400 to receive the firmware update file and is electrically connected to the storage device 220 to store the firmware update file in the storage device 220. The output input interface 400 can include a network interface, a Universal Serial Bus Interface (USB) interface, a mass storage device interface, and other output input device interfaces.

The processor 210 has a plurality of configurations to execute the program Module device. In this embodiment, the processor 210 includes: a function module execution unit 211, an update receiving unit 212, a login unit 213, an overwriting unit 214, and an initial unit 215.

The function module execution unit 211 is configured to register the firmware version data of the plurality of function modules of the embedded system into the module update table.

The update receiving unit 212 is configured to receive the firmware update file with the updated version data from the server 300 and store the firmware update file in the storage device 220, where the firmware update file is used to update the target module in the function module. Update the firmware version information. In this embodiment, the firmware update file includes the name, version data, and firmware code of the corresponding function module.

The overwrite unit 214 is configured to overwrite the firmware update file with the firmware of the corresponding target module in the original data storage block and determine whether the firmware is completely overwritten. Therefore, the overwrite unit 214 can select a function module from the module update table as the update module to accept a firmware update file for firmware update.

When the firmware update file completely overwrites the firmware of the corresponding target module in the original data storage block, the initial unit 215 is used to re-initialize the target according to the firmware of the target module after the original data storage block is overwritten. The module and the functional module that is dependent on the target module. Therefore, in addition to the target module with the firmware update file and the functional module with its dependencies, the other functional modules in the embedded system can continue to operate without interruption due to firmware update of other update modules.

In addition, the processor 210 may further include a backup unit 216 and a write back unit 217. The backup unit 216 is configured to store the firmware update file in the random access memory 224 and store the firmware backup of the target module in the random access memory 224. When the firmware update file is overwritten with the selected target module and In the corresponding firmware, the backup unit 216 first stores the firmware backup of the selected target module before the overwrite in the random access memory 224. When the firmware update file does not completely overwrite the firmware of the target module, the write back unit 217 is configured to rewrite the firmware of the target module stored in the random access memory 224 back to the fixed access memory 222.

In this embodiment, the processor 210 further includes a sending unit 218, configured to send update success information or update failure information. For example, after the firmware update file does not completely overwrite the firmware of the update module, the sending unit 218 may send an update failure message to notify the user to update the failed message. After the firmware update file completely overwrites the firmware of the update module, the sending unit 218 may send an update completion message to notify the user that the firmware update is successful.

In addition, in some embodiments, the processor 220 further includes a suspending unit 219 for stopping the selected target module and the function of the selected target module when the selected target module is performing the operation. The module is executed to initialize the subsequent target module and the dependent function module.

It will be apparent from the above-described embodiments of the present invention that the application of the present invention has the following advantages. When the firmware is updated, the embedded system of the present invention can separately update the function modules that need to be updated, and then only need to initialize the function modules that receive the update and the function modules that are dependent on them. Therefore, the embedded system does not need to restart the entire system after the firmware update is completed. Other functional modules that do not have firmware updates can continue to function.

In addition, the user can determine the firmware version data of the current function module via the module update table. Therefore, the user can know the development status of the function module from the firmware version data, and then determine whether the firmware of the function module needs to be advanced. Line updates. Therefore, the present invention can determine whether the function module in the embedded system needs to be firmware updated according to the needs of the user.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention, and the present invention can be modified and modified without departing from the spirit and scope of the present invention. The scope is subject to the definition of the scope of the patent application attached.

100‧‧‧ Firmware update method for embedded systems

110~192‧‧‧Steps

200‧‧‧ Firmware update device for embedded systems

210‧‧‧ processor

215‧‧‧ initial unit

216‧‧‧Backup unit

217‧‧‧ writeback unit

218‧‧‧Send unit

219‧‧‧ Suspension unit

220‧‧‧Storage device

211‧‧‧Function Module Execution Unit

212‧‧‧Update receiving unit

213‧‧‧ Login unit

214‧‧‧Overwrite unit

222‧‧‧Fixed access memory

224‧‧‧ Random access memory

300‧‧‧Server

400‧‧‧Input and output interface

The above and other objects, features, advantages and embodiments of the present invention will become more apparent and understood.

1 is a flow chart showing the steps of a firmware update method for an embedded system according to an embodiment of the invention.

2 is a flow chart showing the steps of step 150a in the firmware update method of the embedded system of FIG. 1.

FIG. 3 is a functional block diagram of a firmware update device of an embedded system according to still another embodiment of the present invention.

100‧‧‧ Firmware update method for embedded systems

110~192‧‧‧Steps

Claims (11)

A firmware updating method for an embedded system, comprising: (a) executing a plurality of functional modules of an embedded system, wherein the functional modules are executed according to corresponding firmware stored in a raw data storage block; (b) providing a module update table for recording a current firmware version of each of the function modules; (c) receiving a firmware update file with updated version data from a server, wherein The firmware update file is used to update at least one target module of the function modules to an updated firmware version data; (d) registering the updated firmware version data in the module update table; Transmitting the firmware update file to the firmware of the at least one target module in the original data storage block and determining whether the firmware is completely overwritten; and (f) when the firmware update file completely overwrites the original data storage Retrieving the at least one target module and the at least one of the target modules according to the firmware of the at least one target module after the original data storage block is overwritten in the block corresponding to the firmware of the target module The target module has dependencies on the functional modules, wherein The new initial target module and at least one of these functional modules and the at least one target module with dependencies, other functional modules of the embedded systems continued to perform. The method for updating the firmware of the embedded system according to claim 1, further comprising: before the firmware update file overwrites the firmware of the at least one target module in the original data storage block, the original At least in the data storage block The firmware of the target module is stored in a temporary storage data storage block; when the firmware update file does not completely overwrite the firmware of the at least one target module, the temporary storage data storage block stores the firmware The firmware of at least one target module is rewritten back into the original data storage block. The firmware update method of the embedded system of claim 1, wherein the step (e) comprises: determining whether the target modules perform operations when the at least one target module is plural; and selecting the unexecuted operation The at least one target module overwrites the firmware of the selected target module in the original data storage block and determines whether the firmware is completely overwritten. The firmware update method of the embedded system of claim 1, wherein the step (e) comprises: determining whether the target modules perform operations when the at least one target module is plural; and when selecting When the at least one target module is performing the operation, stopping execution of the selected at least one target module and the function modules that are dependent on the selected at least one target module, and the firmware is The update file overwrites the firmware of the selected at least one target module in the original data storage block and determines whether the firmware is completely overwritten. The firmware update method of the embedded system according to claim 1, further comprising: Sending an update failure message after the firmware update file does not completely overwrite the firmware corresponding to the at least one target module in the original data storage block; and when the firmware update file completely overwrites the original data storage After the block corresponds to at least one firmware of the target module, an update completion message is sent. The firmware update method of the embedded system of claim 1, wherein the at least one target module has both the current firmware version data and the updated firmware version data in the module update table, when the current firmware is When the volume version data is the same as the updated firmware version data, the firmware update file is not overwritten with the firmware corresponding to at least one target module in the original data storage block. An embedded system firmware update device includes: a storage device comprising a fixed access memory and a random access memory, wherein the fixed access memory stores a module update table for storing an embedded The firmware version of the plurality of functional modules of the system; and a processor electrically coupled to the storage device, comprising: a functional module execution unit for executing the functional modules of the embedded system An update receiving unit, configured to receive a firmware update file with updated version data from a server and store the firmware update file in the storage device, wherein the firmware update file is used to modify the function At least one target module in the group is updated to an updated firmware version data; a login unit is configured to log the updated firmware version data to In the module update table, an overwrite unit is configured to overwrite the firmware update block with the firmware of the at least one target module in the original data storage block and determine whether the firmware is completely overwritten; and an initial unit When the firmware update file completely overwrites the firmware of the at least one target module in the original data storage block, the at least one target module is overwritten according to the original data storage block. The firmware re-initializes the at least one target module and the functional modules that are dependent on the at least one target module. The firmware update device of the embedded system of claim 7, wherein the processor further comprises a backup unit for storing the firmware update file in a random access memory and the at least one target mode The firmware backup of the group is stored in the random access memory. The firmware update device of the embedded system of claim 8, wherein the processor further comprises a writeback unit, when the firmware update file does not completely overwrite the firmware of the at least one target module, The firmware of the at least one target module stored in the random access memory is rewritten back into the fixed access memory. The firmware update device of the embedded system of claim 9, wherein the processor further comprises a sending unit, configured to: when the firmware update file does not completely overwrite the corresponding one of the original data storage blocks After the firmware of the target module, send an update failure message; or when the firmware is updated After the file completely overwrites the firmware corresponding to at least one target module in the original data storage block, an update completion message is sent. The firmware updating device of the embedded system of claim 7, wherein the processor further comprises a suspending unit for stopping the selected at least one when the selected at least one target module is performing an operation. The target module and the execution of the functional modules that are dependent on the selected at least one target module.