KR20180023575A - Firmware auto updating method and computer readable recording medium writing firmware auto updating method - Google Patents

Abstract

The present invention relate to a method for automatically updating a firmware, capable of completing a firmware update by performing a corresponding update once by a user by automating a complicated firmware update procedure and including all necessary resources in an updater, in order to solve the problems of a conventional firmware updater, and a computer-readable recording medium recording the same. The method for automatically updating a firmware includes the steps of: extracting binary files using meta-information; and performing an update operation with the binary files.

Description

TECHNICAL FIELD [0001] The present invention relates to a firmware update method and a computer readable recording medium on which a method of automatically updating a firmware is recorded.

The present invention relates to an automatic firmware updating method and a computer readable recording medium on which the method is recorded. More particularly, the present invention relates to an automatic updating method for completing a complicated firmware updating procedure including a plurality of steps, And a computer readable recording medium on which the method is recorded.

Most people think of PCs (Peraonal Computers) such as desktops and laptops. However, it can be defined as a computer, if it has a processor (CPU) in a broad sense, and it can input information from outside and process it according to a defined rule and generate an electronic result. If you look like this, you can say that mobile phones, MP3 players, PMPs, video game machines, portable electronic calculators, etc. all belong to the computer system.

The hardware that receives the information transmitted through the software outputs the result of the desired form via the internal logic circuit. The output referred to here means the output of the calculation result or the operation of a specific device. However, since the range of application of computer system is widened and the information transmitted by software is also enormous, it is difficult to cope with various situations by only a limited type of logic circuit in hardware.

Of course, every time new software comes along, you can create new hardware with logic circuitry that works, but doing so can be costly and time consuming. So computer designers have created a storage area in the control part of the hardware, where they can add a program that can reinforce or replace the logic circuit. This is 'Firmware'.

The firmware has the ability to control the basic operation of the hardware prior to other software. For example, when you turn on the PC, you can see a list of hardware information such as the name of the PC manufacturer, CPU, memory, and hard disk capacity on the black desktop just before the start of the operating system (Windows, etc.) . It is called BIOS (Basic Input / Output System), and it is a kind of firmware that performs basic input / output functions of PC. If the hard disk mounted on the PC is damaged and the operating system fails to boot, the BIOS will operate normally and an error message will be displayed indicating that the necessary data for operating the operating system can not be found.

Also, in the case of a digital camera or a video game machine, even if a medium such as a memory card or a CD is not inserted, the initial screen is displayed when the power is turned on, and the computer is ready to receive the storage medium. This is also a typical case showing the role and type of firmware.

The firmware of the old devices was stored in ROM (Read Only Memory) inside the hardware. Since the ROM is a memory that can not be modified, it is difficult to change the contents once the firmware is loaded. However, the EPROM or flash memory, which does not erase the contents of the stored data even after the power is turned off, can be modified and the contents of the firmware can be corrected relatively easily.

The chip containing the firmware may be detachable so that it can be replaced.

In addition, recently released smart phones can update firmware to improve performance or functionality.

Thanks to the recent releases of PCs, smart phones, cell phones, and PMPs, manufacturers often provide new firmware with improved performance and / or improved functionality on a regular basis (called firmware upgrades or updates) .

There have been various problems in the conventional firmware update.

In order to update the firmware of a processor (for example, an MCU: Main Controller Unit), several update procedures must be performed, and the update sequence is complicated depending on the situation.

Depending on each procedure, related binary files exist separately and are cumbersome to manage.

These problems are likely to cause mistakes in the firmware update process. Also, depending on the version of Windows on which the firmware is to be installed, there is a problem in manually updating the firmware because the related driver is deleted in a different manner.

If the device is turned off or the firmware of another device is accidentally overwritten during the firmware update, the device may malfunction or become inoperable.

1 is a flowchart of a conventional firmware update.

The flowchart illustrated in FIG. 1 is based on the assumption that the firmware memory structure of the MCU logically includes three block structures: (1) Boot Loader Block, (2) Data Block, and (3) Main Code Block. The firmware memory structure may have more than three block structures. (1) Boot Loader Block is the part that drives MCU peripherals when powered on. (2) The data block is a block referenced in the operation of the main code block. (3) The main code block is the code block in which the tasks of the Boot Loader Block are completed and executed.

In the conventional firmware update, as shown in FIG. 1, the Boot Loader Block, the Data Block, and the Main Code Block are updated using the MemoryWriter (S110).

Then, it is verified whether the blocks are normally updated using the MemoryChecker (S120).

Also, if the HID description is changed and the HID driver is required to be deleted, the HID driver is deleted by executing devcon.exe with RunAsSystem.exe (S130).

A binary file for updating each of the above three memory blocks is required for firmware update. That is, (1) a binary file for updating a Boot Loader Block, (2) a binary file for updating a data block, and (3) a binary file for updating a main code block.

(4) MemoryWriter to write each binary file to each memory block, and (5) MemoryChecker to check whether each binary file is normally updated in memory.

Communication between the MCU and the updater for firmware update uses Human Interface Device (HID). However, if the HID description connected to the HID is changed, the HID driver must be removed after the firmware update is completed. To remove the HID driver, you can use an external tool such as devcon.exe provided by Microsoft® or a delete executable. In addition, operations such as uninstalling the HID driver must have administrator privileges. You can use an external tool such as RunAsSystem.exe or a delete executable to allow a program to run with administrative privileges.

Therefore, for the firmware update, HID driver eliminator (devcon.exe) for each operating system version and system type (32 bit / 64 bit) of Windows (6) System administrator rights acquirer (RunAsSystem.exe) (There are 10 files needed for each kind of file from Windows XP to Windows 10).

In order to update the conventional firmware, when the binary file is changed for each block, the user must repeat the procedure shown in FIG. 1 every time and require more than fifteen files for firmware update.

Therefore, there is a need for streamlining and automating the firmware update procedure.

In order to solve the problems of the conventional firmware updater, the present invention provides a firmware update method that automates a complicated firmware update procedure and includes a necessary resource in an updater to allow a user to execute the updater once to complete firmware update And an object of the present invention is to provide an automatic updating method and a computer readable recording medium recording the method.

According to an aspect of the firmware auto update method of the present invention,

A method for automatically updating a firmware,

Wherein the updater for performing the firmware automatic update includes at least one or more binary files for meta information and update,

Extracting the binary files using the meta information; And

And performing the update with the binary files.

Preferably,

The updater includes an update executable executable by a computer processor.

Preferably,

The updater further includes an identification code for distinguishing the update executable file area from the area where the binary files are stored.

Preferably,

And deleting a HID (Human Interface Device) driver for communication between the updater and an MCU (Main Controller Unit).

Preferably,

The updater further includes an HID driver deletion executable file necessary for deleting the HID driver.

Preferably,

The HID driver deletion executable file is different depending on the version of the window.

Preferably,

The identification code is used to verify the status of the update executable file.

Preferably,

The meta information includes information on whether the boot loader block of the firmware memory is an updater, information on whether the HID driver is deleted after updating the firmware, and whether the system restarts after updating the firmware. .

Preferably,

The meta information may further include a path of the binary files, a file name of the binary files, a file size and creation date of the binary files, a file cyclic redundancy check (CRC), and a file version.

Preferably,

The binary files include an update file of a boot loader block, a data block update file, and a main code block update file.

According to an aspect of the computer readable recording medium recording the firmware automatic update method of the present invention,

A computer-readable recording medium including an updater for performing firmware automatic updating,

The updater includes at least one or more binary files and meta information including a file path, a file size, and a file name of the binary files.

Preferably,

The updater includes an update executable executable by a computer processor.

Preferably,

The updater further includes an identification code for distinguishing the update executable file area from the area where the binary files are stored.

Preferably,

The updater further includes an HID driver deletion executable file necessary for deleting a HID (Human Interface Device) driver for communication between the updater and an MCU (Main Controller Unit).

Preferably,

The HID driver deletion executable file is different depending on the version of the window.

Preferably,

The identification code is used to verify the status of the update executable file.

Preferably,

The meta information includes at least one of a file creation date and time of the binary files, a file cyclic redundancy check (CRC), a file version, information on whether the boot loader block of the firmware memory is an updater, whether the HID driver is deleted after the firmware is updated And information on whether to restart the system after the firmware update.

Preferably,

The binary files include an update file of a boot loader block, a data block update file, and a main code block update file.

According to the firmware automatic updating method and the computer readable recording medium recording the method according to the present invention, since the updater includes all the resources necessary for updating the firmware, the update can be performed more quickly and efficiently.

According to the firmware automatic updating method and the computer readable recording medium recording the method of the present invention, the complicated updating procedure is automatically performed by one execution of the updater, and thus there is a considerably low possibility of errors in the firmware updating process.

According to the firmware automatic updating method and the computer readable recording medium recording the method of the present invention, the updater can include a reserved space to prepare for future performance improvement.

1 is a flowchart of a conventional firmware update.
FIG. 2 is a view schematically showing a structure of a updater for performing firmware update according to the present invention.
FIG. 3 is a view showing information included in meta information of the updater according to the present invention.
4 is a flowchart illustrating an update process using the updater according to the present invention.

In order to fully understand the present invention, operational advantages of the present invention, and objects achieved by the practice of the present invention, reference should be made to the accompanying drawings and the accompanying drawings which illustrate preferred embodiments of the present invention.

Hereinafter, the present invention will be described in detail with reference to the preferred embodiments of the present invention with reference to the accompanying drawings. Like reference symbols in the drawings denote like elements.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings and embodiments.

FIG. 2 is a view schematically showing a structure of a updater for performing firmware update according to the present invention.

The updater 200 performing firmware automatic updating is stored in a computer-readable recording medium.

The updater according to the present invention includes at least one or more binary files 240 and meta information 230 including a file path, a file size and a file name of binary files.

The updater 200 for firmware update in the present invention includes an update executable file 210 readable by a machine such as a computer.

The updater 200 further includes an identification code 220 for distinguishing between the update execution file area 210 and the area 240 in which the binary files are stored.

The updater 200 includes an HID driver deletion executable file necessary for deleting a HID (Human Interface Device) driver for communication between the updater 200 and an MCU (Main Controller Unit).

The meta information 230 includes information on a file creation date and time of binary files, a file cyclic redundancy check (CRC), a file version, information on whether the boot loader block of the firmware memory is an updater (310 in FIG. 3) Information about the HID driver deletion (320 in FIG. 3), and information about the restart of the system after the firmware update (330 in FIG. 3).

The detailed contents of the meta information 230 will be described in more detail with reference to FIG.

The binary files 240 included in the updater 200 include an update file of a boot loader block, a data block update file, and a main code block update file.

The update executable file 210 executes the updater 200, extracts the binary files, and proceeds to update the firmware according to the set options.

The update executable file can merge HID driver deletion executable files (eg, devcon.exe, RunAsSystem.exe) related to HID driver deletion. The HID driver deletion executable file differs depending on the version of Windows.

The identification code 220 is used for two purposes and is composed of randomly generated characters: (1) an update executable file area 210 which constitutes an updater based on a string of identification code, and Area 240, and (2) verify whether the update executable file is a normal executable file. It is determined whether or not the identification code exists in the update executable file. If the identification code does not exist, it is determined that there is a problem.

The binary files 240 include binary files to be used for firmware update (e.g., Boot Loader block update file, Main Code block update file, Data block update file).

FIG. 3 is a view showing information included in meta information of the updater according to the present invention.

FIG. 3 shows an example of the structure of meta information 300 having a fixed length value.

The meta information 300 includes the following information:

1) Binary file information name

    - File path and filename

    - File size, creation date and time

    - File CRC

2) Various set values

    - version of binary files

    - the title and version displayed in the title of the Updater executable

    - Whether the Boot Loader Block is updated (310)

    - Whether to delete the HID driver after updating the firmware (320)

    - Whether to restart the system after updating the firmware (330)

Since the length of each value of the meta information 300 is defined in advance, the corresponding information can be obtained by reading the value by the designated length.

The reserved space 340 holds the length of the area in which the setting values are to be stored in advance, and adds a new value to the reserved space in case the new value is added due to other reasons such as performance improvement. By doing so, the effect of the structure information changed by the added value can be minimized.

4 is a flowchart illustrating an update process using the updater according to the present invention.

The firmware automatic update method is performed by an updater that performs firmware automatic update, and the updater includes at least one or more binary files for meta information and update.

As shown in FIG. 4, the automatic firmware updating method of the present invention extracts binary files using meta information (S410).

Find out where the meta information starts based on the identification code. After reading all of the meta information, extract the firmware binary file located at the following location.

Since the length of each binary file can be known from the meta information, it is read out by the corresponding length.

The update is performed with the binary files (S420).

Binary files are loaded into memory and checked for CRC to make sure they are normal. If the CRC values do not coincide with each other, the abnormal firmware may be updated and the process is terminated without further processing.

In the firmware update step, the execution of each firmware update is determined by the set value of the meta information.

(1) If the update of the boot loader block is enabled, the boot loader block is updated.

(2) Update the data block.

(3) Update the Main Code Block.

For each procedure, compare the contents of the binary file with the data in memory to see if it has been updated normally after the update.

If HID deletion is enabled, delete the HID driver using devcon.exe. Since the corresponding devcon.exe differs for each Windows version, it will determine the current version of Windows and automatically run the appropriate devcon.exe.

The firmware update method of the present invention may further include a pre-check step preceding the step S410.

In the preceding check step, various resources and meta information included in the updater are extracted and it is checked whether the MCU and HID communication operate normally. Remove the HID driver from the update executable file. The executable files devcon.exe and RunAsSystem.exe are extracted.

In addition, it may include a step of outputting to the screen whether the update is successful or unsuccessful in the last step.

Firmware update process can be saved as a log file, and the problem can be easily identified by using the log file stored in case of a problem.

It will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims. It will be clear to those who have.

Claims (18)

A method for automatically updating a firmware,
Wherein the updater for performing the firmware automatic update includes at least one or more binary files for meta information and update,
Extracting the binary files using the meta information; And
And updating the firmware with the binary files. The method according to claim 1,
Wherein the updater comprises an update executable executable by a computer processor. The method of claim 2,
Wherein the updater further comprises an identification code for distinguishing the update executable file area from the area where the binary files are stored. The method of claim 3,
Further comprising deleting a HID (Human Interface Device) driver for communication between the updater and an MCU (Main Controller Unit). The method of claim 4,
Wherein the updater further includes an HID driver deletion executable file necessary for deleting the HID driver. The method of claim 5,
Wherein the HID driver deletion executable file differs depending on the version of the window. The method of claim 5,
Wherein the identification code is used to verify the status of the update executable file. The method of claim 4,
The meta information includes information on whether the boot loader block of the firmware memory is an updater, information on whether the HID driver is deleted after updating the firmware, and whether the system restarts after updating the firmware. The method for automatically updating the firmware. The method of claim 8,
Wherein the meta information further includes a path of the binary files, a file name of the binary files, a file size and a creation date of the binary files, a file cyclic redundancy check (CRC), and a file version. The method according to claim 1,
Wherein the binary files include an update file of a boot loader block, a data block update file, and a main code block update file. A computer-readable recording medium comprising an updater for performing firmware automatic updating,
Wherein the updater includes at least one or more binary files and meta information including a file path, a file size, and a file name of the binary files. The method of claim 11,
Wherein the updater comprises an update executable file executable by a computer processor. The method of claim 12,
Wherein the updater further comprises an identification code for distinguishing between the update executable file area and the area where the binary files are stored. 14. The method of claim 13,
Wherein the updater further comprises an HID driver deletion executable file necessary for deleting a HID (Human Interface Device) driver for communication between the updater and an MCU (Main Controller Unit). 15. The method of claim 14,
Wherein the HID driver deletion executable file differs depending on the version of Windows. 16. The method of claim 15,
Wherein the identification code is used to verify the status of the update executable file. The method of claim 11,
The meta information may include at least one of a file creation date and time of the binary files, a file cyclic redundancy check (CRC), a file version, information on whether the boot loader block of the firmware memory is an updater, whether the HID driver is deleted after the firmware update And information on whether to restart the system after updating the firmware. The method of claim 11,
Wherein the binary files include an update file of a boot loader block, a data block update file, and a main code block update file.

Images