TWI854882B - Method of performing full firmware update procedure on embedded electronic device - Google Patents

Abstract

When performing a full firmware update procedure on an electronic device, a full firmware update file is first divided into a first sub update file and a second sub update file, a header file associated the sizes of each sub update file is created, and the header file, the first sub update file and the second sub update file are merged into a full FOTA file before being uploaded to the electronic device. The electronic device accesses each sub update file based on the header file, stores the accessed first sub update file into a first storage unit of the electronic device, and stores the accessed second sub update file into a second storage unit of a sub-system in the electronic device. After performing the firmware update steps associated with the first sub update file, the second sub update file stored in the second storage unit is copied to the first storage unit before performing the firmware update steps associated with the second sub update file.

Description

Method for performing a complete firmware update procedure on an embedded electronic device

The present invention relates to a method for executing a complete firmware update procedure on an embedded electronic device, and in particular to a method for executing a complete firmware update procedure on an embedded electronic device with limited built-in memory space through FOTA technology.

Embedded electronic devices usually include hardware, software and firmware. Hardware refers to all physical components required for the system to function, such as motherboards, graphics cards, central processing units, ventilation fans, network cameras and power supplies, which can be connected to each other through circuit boards. Software refers to non-physical products created with programming languages, such as applications (APPs), web pages and various operating systems, which are used to enable hardware to provide users with various convenient services. Firmware refers to software embedded in hardware devices that can control hardware through programming languages. Common firmware is found in basic input/output system chips on motherboards, optical drives, burners, Internet protocol gateways/routers, wireless access points (WAPs), modems and other information products. Users can remotely control and operate the settings and functions in the firmware through a designated interface, query the current operating status of the hardware, and perform hardware settings, upgrades and adjustments.

Firmware can be considered as a package containing all official special software, which is usually stored in the flash memory of embedded electronic devices. Users can perform firmware update procedures through specific devices and methods. The main purpose of firmware updates includes correcting errors in the code, adding or improving execution functions, adjusting system security, and improving firmware efficiency.

The first known firmware update method is to connect the embedded electronic device to the host computer via the universal serial bus (USB) port, and then use the FlashTool flash software to download the latest version of the official FTF format firmware file, and then update it offline. This technology can transfer large amounts of firmware files for complete firmware updates, but in certain application scenarios, the above wired data transmission is not feasible or extremely inconvenient.

The second learned firmware update method is to use firmware over-the-air (FOTA) technology to automatically update the operating system of embedded electronic devices. After the embedded electronic device establishes a connection with the server, it can download and update the firmware without connecting to the computer host. However, if the root file system (rootfs) or modem of the embedded electronic device has an error, the firmware update will not be possible via the network. In addition, the storage space of the built-in flash memory of mobile electronic devices is usually insufficient to cope with the file size required for full firmware updates using FOTA technology. Therefore, electronic devices with limited built-in memory space can only use the first learned firmware update method mentioned above to perform full firmware updates, which is inconvenient for users.

Therefore, a method is needed to perform a complete firmware update on electronic devices with limited built-in memory space through FOTA technology.

The present invention provides a method for executing a complete firmware update program on an embedded electronic device, which includes cutting a complete firmware update file into a plurality of update data; dividing the plurality of update data into a first sub-update file and a second sub-update file; making a header file related to the file size of each sub-update file; sequentially combining the header file, the first sub-update file and the second sub-update file into a complete FOTA file; uploading the complete FOTA file to the embedded electronic device; extracting the content of the first sub-update file from the complete FOTA file according to the header file, and storing the extracted first sub-update file in one of the embedded electronic device. The invention relates to a method for performing a firmware update on the first storage unit; clearing the memory space of a second storage unit in a subsystem module of the embedded electronic device; extracting the content of the relevant second sub-update file from the complete FOTA file according to the header file, and storing the extracted second sub-update file in the second storage unit; executing a firmware update step on the first sub-update file stored in the first storage unit at a first time point; copying the second sub-update file stored in the second storage unit to the first storage unit at a second time point after the first time point; and executing a firmware update step on the second sub-update file stored in the first storage unit at a third time point after the second time point. During the operation of the embedded electronic device, the first storage unit provides a first available memory space, and the second storage unit provides a second available memory space, wherein the file size of the complete firmware update file exceeds the first available memory space, but does not exceed the sum of the first available memory space and the second available memory space.

100:Embedded electronic devices

110: Processing unit

120: Subsystem module

131: First storage unit

132: Second storage unit

140: User Interface

200-320: Steps

Figure 1 is a functional block diagram of an embedded electronic device in an embodiment of the present invention.

Figure 2 is a flow chart of a method for executing a complete firmware update procedure on an embedded electronic device using FOTA technology in an embodiment of the present invention.

Figure 3 is a schematic diagram of the relevant data of the embedded electronic device after the file cutting of the complete firmware update program is executed in the embodiment of the present invention.

Figure 4 is a schematic diagram of the complete FOTA file generated when the embedded electronic device of the embodiment of the present invention executes the complete firmware update procedure.

Figures 5 to 9 are schematic diagrams of data at various stages when the embedded electronic device of the embodiment of the present invention executes a complete firmware update procedure through FOTA technology.

Figure 10 is a schematic diagram of the data after the embedded electronic device of the embodiment of the present invention executes a complete firmware update procedure.

Figure 1 is a functional block diagram of an embedded electronic device 100 in an embodiment of the present invention. The embedded electronic device 100 at least includes a processing unit 110, a subsystem module 120, a first storage unit 131, and a user interface 140.

In the embodiment of the present invention, the embedded electronic device 100 may be an Internet of Things (IoT) device, a mobile Internet device (MID) or a smart phone designed for different applications such as industry, medical, communication, storage or automobile, but is not limited thereto.

In the embodiment of the present invention, the subsystem module 120 includes at least a second storage unit 132, which stores subsystem firmware to provide the functions required for the application of the embedded electronic device 100. For example, when the embedded electronic device 100 is an Internet Service Provider (ISP) device, the subsystem module 120 can be a modem module. However, the types of the embedded electronic device 100 and the subsystem module 120 therein do not limit the scope of the present invention.

In the embodiment of the present invention, the first storage unit 131 is a built-in memory of the embedded electronic device 100, such as an embedded multimedia card (eMMC), a universal flash storage (UFS), or a fast non-volatile memory (NVMe), but is not limited thereto.

In the embodiment of the present invention, the second storage unit 132 is a built-in memory of the subsystem module 120, and may include one or more memory devices, such as flash memory, random access memory (RAM), and/or read-only memory (ROM), etc., but is not limited thereto.

In the embodiment of the present invention, the embedded electronic device 100 is a product that has a high requirement for thinness and lightness, so its built-in first storage unit 131 can only provide limited available memory space. More specifically, during the operation of the embedded electronic device 100, the available memory space provided by the first storage unit 131 cannot cope with the memory space required to execute a complete firmware update procedure.

In the embodiment of the present invention, when the embedded electronic device 100 is in operation, the available memory space provided by the first storage unit 131 is less than the memory space required to execute the complete firmware update procedure, but the total available memory space provided by the first storage unit 131 and the second storage unit 132 is greater than the memory space required to execute the complete firmware update procedure. Therefore, when the embedded electronic device 100 is executing the complete firmware update procedure, the present invention will use the additional available memory space provided by the second storage unit 132 in the subsystem module 120 to support the memory space required to execute the complete firmware update procedure.

Figure 2 is a flow chart of a method for executing a complete firmware update procedure on an embedded electronic device 100 using FOTA technology in an embodiment of the present invention, which includes the following steps:

Step 200: Split a complete firmware update file into multiple update data.

Step 210: Divide the plurality of update data into a first sub-update file and a second sub-update file.

Step 220: Create a header file containing the firmware version, verification code, and size of each sub-update file.

Step 230: Sequentially combine the header file, the first sub-update file, and the second sub-update file into a complete FOTA file.

Step 240: Upload the complete FOTA file to the embedded electronic device 100.

Step 250: Determine whether the complete FOTA file can pass the correctness verification; if so, execute step 260; if not, execute step 320.

Step 260: Extract the content of the relevant first sub-update file based on the header file of the complete FOTA file, and store the extracted first sub-update file in the first storage unit 131.

Step 270: Clear the memory space in the second storage unit 132 of the subsystem module 120.

Step 280: Extract the content of the relevant second sub-update file based on the header file of the complete FOTA file, and store the extracted second sub-update file in the second storage unit 132.

Step 290: Determine whether the first sub-update file and the second sub-update file are complete; if so, execute step 300; if not, execute step 320.

Step 300: Restart the system, and then execute the firmware update step of the first sub-update file in the memory of the first storage unit 131.

Step 310: Restart the system, copy the second sub-update file in the second storage unit 132 to the first storage unit 131, and then execute the firmware update step related to the second sub-update file in the first storage unit 131.

Step 320: The system will prompt that the firmware update has failed and exit the firmware update program.

In step 200, the present invention will cut a complete firmware update file into multiple update data, each of which can be update data for the kernel, root file system (rootfs), original equipment manufacturer (OEM) package, and subsystem firmware. In one embodiment, step 200 can be completed using any relevant file cutting tool or file cutting software.

In step 210, the present invention divides the plurality of update data into a first sub-update file and a second sub-update file. Assuming that the complete firmware update file is divided into (M+N) update data in step 200, and the content of each update data is different, the first sub-update file may include M update data, and the second sub-update file may include N update data, where M and N are positive integers. As mentioned above, when executing the complete firmware update procedure, the file size of the complete firmware update file will exceed the available memory space that the first storage unit 131 can provide, but will not exceed the total available memory space that the first storage unit 131 and the second storage unit 132 can provide. In one embodiment, the present invention can determine the size of the first sub-update file and the second sub-update file based on the ratio of available memory space that can be provided by the first storage unit 131 and the second storage unit 132.

In the embodiment of the present invention, the second sub-update file will include the sub-system firmware update data in the complete firmware update file, and the time point of executing the update steps of the relevant first sub-update file will be earlier than executing the relevant second sub-update. The time point of the file update step.

FIG. 3 is a schematic diagram of the relevant data of the embedded electronic device 100 after executing step 210 of the complete firmware update procedure according to the embodiment of the present invention. For the purpose of illustration, it is assumed that the complete firmware update file is divided into four update data: rootfs update data, OEM package update data, kernel update data, and subsystem firmware update data, and the total file size is about 144MB. Assuming that the available memory space provided by the first storage unit 131 and the second storage unit 132 is similar, after executing step 210, the first sub-update file may include two update data, namely, rootfs update data and OEM package update data (file size is about 73MB), and the second sub-update file may include two update data, namely, kernel update data and subsystem firmware update data (file size is about 71MB), as shown in FIG. 3.

In the embodiment of the present invention, each update data in the first sub-update file is different from each update data in the second sub-update file, and the second sub-update file at least includes subsystem firmware update data.

In step 220, the present invention will create a header file with the firmware version, verification code, and size of each sub-update file. In step 230, the present invention will sequentially combine the header file, the first sub-update file, and the second sub-update file into a complete FOTA file.

FIG. 4 is a schematic diagram of a complete FOTA file generated when the embedded electronic device 100 of the present invention executes a complete firmware update procedure. In one embodiment, the verification code may be a cyclic redundancy check (CRC) to verify errors that may occur after data transmission or storage. In other embodiments, the verification code may be any hash function of a fixed-bit verification code generated based on data such as network data packets or computer files. In one embodiment, Size 1 represents the file size of the first sub-update file, and its value may be the number of bits of the length of the relevant first sub-update file; Size 2 represents the file size of the second sub-update file, and its value may be the number of bits of the length of the relevant second sub-update file. However, the format of the header file and the type of verification code do not limit the scope of the present invention.

In step 240, the present invention can upload the complete FOTA file to the embedded electronic device 100 through the user interface 140. Then in step 250, the embedded electronic device 100 determines whether the complete FOTA file can pass the correctness verification. In one embodiment, the processing unit 110 of the embedded electronic device 100 can check the header file content in the complete FOTA file and confirm the correctness of the verification code. When it is determined that the complete FOTA file cannot pass the correctness verification, it means that data loss or damage may occur in the process of uploading the complete FOTA file to the embedded electronic device 100. At this time, the present invention will execute step 320 to prompt the firmware update failure and exit the firmware update program.

When it is determined in step 250 that the complete FOTA file can pass the correctness verification, the content of the relevant first sub-update file and the content of the relevant second sub-update file are extracted respectively according to the header file of the complete FOTA file in steps 260 and 280. Taking the embodiment shown in FIG. 4 as an example, the processing unit 110 of the embedded electronic device 100 can obtain the file size Size 1 of the first sub-update file and the file size Size 2 of the second sub-update file according to the header file of the complete FOTA file, and then extract the corresponding data according to the file size Size 1 of the first sub-update file and the file size Size 2 of the second sub-update file. For example, when the value of file size Size 1 is m and the value of file size Size 2 is n (m and n are positive integers), the processing unit 110 can extract the data of the 1st to mth bits after the header file in the complete FOTA file as the first sub-update file, and extract the data of the (m+1)th to (m+n)th bits after the header file in the complete FOTA file as the second sub-update file.

Figures 5 to 9 are schematic diagrams of data at various stages when the embedded electronic device 100 of the present invention executes a complete firmware update procedure through FOTA technology. Before executing the firmware update procedure, the embedded electronic device 100 stores existing kernel files, existing rootfs files, existing OEM files, and existing subsystem firmware, etc.

In step 260, the present invention will store the first sub-update file extracted from the complete FOTA file into the first storage unit 131 of the embedded electronic device 100, as shown in Figure 5.

In step 270, the present invention clears the memory space in the second storage unit 132 in the subsystem module 120. Then in step 280, the present invention stores the second sub-update file extracted from the complete FOTA file in the second storage unit 132 in the subsystem module 120, as shown in Figure 6.

In step 290, the processing unit 110 determines whether the first sub-update file and the second sub-update file are complete based on the header file in the complete FOTA file. When it is determined that the first sub-update file in the first storage unit 131 and/or the second sub-update file in the second storage unit 132 are not complete, it means that data loss or damage may have occurred in the process of extracting data and/or storing data. At this time, the present invention will execute step 320 to prompt the firmware update failure and exit the firmware update program.

After confirming the integrity of the first sub-update file in the memory of the first storage unit 131 and the second sub-update file in the memory of the second storage unit 132, the embedded electronic device 100 will restart the system in step 300, and then execute the firmware update step related to the first sub-update file in the memory of the first storage unit 131. More specifically, after the system is restarted in step 300, the existing rootfs file and the existing OEM file will be updated respectively according to the rootfs update data and the OEM update data in the first sub-update file in the memory of the first storage unit 131, as shown in Figure 7.

After completing the update procedure of the relevant first sub-update file, the embedded electronic device 100 will restart the system again in step 310. After the restart is completed, the second sub-update file in the memory of the second storage unit 132 will be copied to the first storage unit 131, as shown in Figure 8.

Next, the embedded electronic device 100 executes the firmware update step of the second sub-update file stored in the first storage unit 131. More specifically, after the second sub-update file is copied to the first storage unit 131 in step 310, the existing kernel file and subsystem module 120 are updated respectively according to the kernel update data and subsystem firmware update data in the second sub-update file stored in the first storage unit 131, as shown in FIG. 9.

In one embodiment, when the embedded electronic device 100 is restarted in steps 300 and 310, the Original Equipment Manufacturer Secondary Boot Loader (OEMSBL) is executed to execute the update steps of the related first sub-update file and the second sub-update file. However, the way in which the embedded electronic device 100 executes the firmware update step does not limit the scope of the present invention.

FIG. 10 is a schematic diagram of data after the embedded electronic device 100 of the embodiment of the present invention executes a complete firmware update procedure. After executing the complete firmware update procedure, the embedded electronic device 100 stores an updated kernel file, an updated rootfs file, an updated OEM file, and an updated subsystem firmware.

In summary, for embedded electronic devices with limited built-in memory space, the present invention will use multi-stage FOTA technology to perform a complete firmware update procedure for embedded electronic devices. The firmware update step for the subsystem module will be performed in the last stage, so that before updating the existing subsystem firmware, the additional available memory space provided by the built-in memory of the subsystem module can be used to support the memory space required to execute the complete firmware update procedure.

The above is only the preferred embodiment of the present invention. All equivalent changes and modifications made according to the scope of the patent application of the present invention shall fall within the scope of the present invention.

210-320: Steps

Claims (8)

A method for executing a complete firmware update program on an embedded electronic device comprises: cutting a complete firmware update file into a plurality of update data; dividing the plurality of update data into a first sub-update file and a second sub-update file; creating a header file (header) related to the file size of each sub-update file; sequentially combining the header file, the first sub-update file and the second sub-update file into a complete firmware broadcast (firmware The method comprises the steps of: extracting a first sub-update file from the complete FOTA file according to the header file, and storing the extracted first sub-update file in a first storage unit of the embedded electronic device; clearing a subsystem firmware in a second storage unit memory of a subsystem module of the embedded electronic device to clear the memory space of the second storage unit, wherein the subsystem firmware provides the functions required by the application of the embedded electronic device; extracting the content of the second sub-update file from the complete FOTA file according to the header file, and storing the extracted second sub-update file in the second storage unit; At a first time point, a firmware update step is performed in relation to the first sub-update file stored in the first storage unit; at a second time point after the first time point, the second sub-update file stored in the second storage unit is copied to the first storage unit; and at a third time point after the second time point, a firmware update step is performed in relation to the second sub-update file stored in the first storage unit, wherein: during the operation of the embedded electronic device, the first storage unit provides a first available memory space, and the second storage unit provides a second available memory space; and the file size of the complete firmware update file exceeds the first available memory space, but does not exceed the sum of the first available memory space and the second available memory space. The method as described in claim 1, wherein: the complete firmware update file is divided into (M+N) update data; the first sub-update file includes N update data; the second sub-update file includes M update data, and the M update data at least includes update data related to the subsystem firmware; N and M are positive integers; and the content of each update data in the first sub-update file is different from the content of each update data in the second sub-update file. The method as described in claim 2, wherein: the N update data include a kernel update data, a root file system (rootfs) update data, or an original equipment manufacturer (OEM) package update data; and the M update data also include the kernel update data, the root file system update data, and the update data in the OEM package update data that are not included in the N update data. The method as described in claim 1 further comprises: determining the values of M and N according to the ratio between the memory space of the first storage unit and the memory space of the second storage unit, wherein the memory space of the second storage unit is not larger than the memory space of the first storage unit. The method as described in claim 1 further comprises: creating the header file of the file size and a verification code of each sub-update file; after uploading the complete FOTA file to the embedded electronic device, judging whether the complete FOTA file can pass the correctness verification according to the verification code of the header file; and after judging that the complete FOTA file can pass the correctness verification, extracting the content of the first sub-update file and the content of the second sub-update file from the complete FOTA file according to the header file. The method as described in claim 1 further comprises: after storing the extracted first sub-update file in the first storage unit, determining whether the first sub-update file is complete; and after determining that the first sub-update file is complete, restarting the embedded electronic device at the first time point to execute a firmware update step related to the first sub-update file stored in the first storage unit. The method as described in claim 1 further comprises: after copying the second sub-update file in the second storage unit memory to the first storage unit at the second time point, determining whether the second sub-update file is complete; and after determining that the second sub-update file is complete, restarting the embedded electronic device at the third time point to execute the firmware update step related to the second sub-update file in the first storage unit memory. The method as described in any one of claim items 5-7 further comprises: when it is determined that the complete FOTA file cannot pass the correctness verification, when it is determined that the first sub-update file is incomplete after the extracted first sub-update file is stored in the first storage unit, and/or when it is determined that the second sub-update file is incomplete after the second sub-update file stored in the second storage unit is copied to the first storage unit, prompting that the firmware update fails and exiting the complete firmware update procedure.