Image processing apparatus and firmware update method

Abstract

To prevent a failure in updating firmware.SOLUTION: Firmware is applied with management numbers (core number, non-core number) according to a partition configuration, and a region of the firmware affecting the start-up of an image processing apparatus is applied with the core number, and a region not affecting the start-up is applied with the non-core number. When updating firmware FW1 to the latest firmware FW2, the control unit 111 compares the respective core numbers first, and when the core numbers are different from each other, does not perform the update. When the respective non-core numbers match each other or the firmware FW1 is custom firmware, the control unit 111 asks a user whether to update the firmware.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an image processing apparatus and a firmware updating method. [Background technology]

[0002] Image forming devices such as multifunction peripherals equipped with scanner, printer, copy, and fax functions store firmware that controls the hardware that realizes each function in read-only memory (ROM). The firmware stored in the ROM is updated to the latest firmware as needed.

[0003] Patent Document 1 describes a method for updating firmware without losing the setting information of an image processing device, while Patent Document 2 describes a method for updating only necessary firmware while taking into consideration the avoidance of controller board failures, etc. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-164902 [Patent Document 2] Japanese Patent Application Laid-Open No. 2018-124749 Summary of the Invention [Problem to be solved by the invention]

[0005] The ROM that stores firmware is divided into multiple partitions for data storage. The partition configuration may change depending on the firmware version, and if the partition configuration of firmware that affects the device's startup is changed, there may be problems such as the device not starting up correctly.

[0006] In other words, when updating firmware, it is necessary to take into consideration the partition structure of the firmware stored in the ROM, but Patent Documents 1 and 2 do not mention this point.

[0007] The present invention has been made in view of the above circumstances, and has as its object to prevent firmware update failures. [Means for solving the problem]

[0008] The image processing device of the present invention has a plurality of partitions and is equipped with a memory unit that stores firmware, a control unit that performs firmware updates, and a data acquisition unit that acquires firmware for updates, and the firmware has a core number that is a management number based on the configuration of the partitions and corresponds to the partition involved in startup, and the control unit compares the core number of the firmware for updates with the core number of the firmware stored in the memory unit, and, on the condition that these two core numbers match, performs a process of overwriting the firmware for updates in the firmware area stored in the memory unit.

[0009] The firmware update method of the present invention is a firmware update method for updating firmware stored in a memory unit having a plurality of partitions with update firmware, wherein the firmware has a management number corresponding to a partition involved in startup as a core number, as a management number based on the configuration of the partition, and further includes a comparison step for comparing the core number of the update firmware with the core number of the firmware stored in the memory unit, and an overwrite step for overwriting the update firmware in the firmware area stored in the memory unit if it is determined in the comparison step that the core number held by the update firmware matches the core number of the firmware stored in the memory unit. [Effects of the Invention]

[0010] According to the present invention, when updating firmware to the latest firmware, the core numbers assigned based on the partition configuration are compared, and if the core numbers are different, the update is not performed, thereby preventing firmware update failures. This makes it possible to avoid firmware updates that are not intended by the user. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 2 is a diagram illustrating an electrical configuration of the image processing device. [Figure 2] FIG. 2 is a diagram for explaining a partition configuration of firmware. [Figure 3] FIG. 2 is a diagram for explaining a partition configuration of firmware. [Figure 4] FIG. 2 is a diagram for explaining a partition configuration of firmware. [Figure 5] FIG. 2 is a diagram for explaining a partition configuration of firmware. [Figure 6] FIG. 2 is a diagram for explaining a partition configuration of firmware. [Figure 7] 10 is a flowchart showing the flow of firmware update processing. [Figure 8] FIG. 2 is a diagram for explaining a partition configuration of firmware. [Figure 9] FIG. 2 is a diagram showing a display example of a display unit. DETAILED DESCRIPTION OF THE INVENTION

[0012] An image processing device and a firmware update method according to an embodiment of the present invention will be described below with reference to the drawings. The image processing device according to this embodiment is an image forming device such as a printer or a copier, or a multifunction device equipped with multiple functions such as a facsimile or a scanner. In this embodiment, an image forming device will be described as an example.

[0013] 1 is a diagram showing the electrical configuration of an image forming apparatus 1 according to one embodiment of the present invention. The image forming apparatus 1 includes a control unit 11, an input receiving unit 12, an image reading unit 13, an image forming unit 14, a storage device 15, a communication unit 16, and an external storage device connection unit 17 (data acquisition unit).

[0014] The input reception unit 12 includes hard keys such as a decision key for confirming various operations and settings, a start key, and the like, and a display unit 121. The input reception unit 12 receives various instructions in response to the operation of the above keys by the user. The display unit 121 includes, for example, an LCD, and displays an operation screen, messages, and the like. The display unit 121 may also include a touch panel.

[0015] The image reading unit 13 includes a scanner or the like and reads an image of a document to obtain image data. The image forming unit 14 is, for example, an electrophotographic image forming mechanism and forms on paper an image or the like indicated by the image data obtained by the image reading unit 13 or the image data received by the communication unit 16 from an external device or the like.

[0016] The storage device 15 is, for example, an HDD, and is a large-capacity storage device that stores image data, various programs, data tables, etc. The storage device 15 may be configured as an SSD (Solid State Drive) or the like in addition to an HDD. The communication unit 16 is configured as a communication module or the like, and transmits and receives various data to and from external devices such as servers via a network.

[0017] The external storage device connector 17 is a socket (for example, a slot or USB port interface) to which the external storage device 3 is connected. The external storage device 3 is a storage capable of saving large amounts of data, such as an SD (Secure Digital) card or a USB (Universal Serial Bus) memory. The external storage device 3 is used by being attached to the external storage device connector 17. A control unit 111 (described later) reads various data from the external storage device 3 connected to the external storage device connector 17 and stores the various data in the storage device 15.

[0018] The control unit 11 is composed of a processor, RAM (Random Access Memory), ROM, etc. The processor is a CPU (Central Processing Unit), MPU (Micro Processing Unit), ASIC (Application Specific Integrated Circuit), etc. The control unit 11 functions as a control unit 111 when the processor executes a control program stored in the ROM, etc. The control unit 111 controls the overall operation of the image forming apparatus 1.

[0019] The control unit 11 further includes a nonvolatile memory 112 (storage unit). The nonvolatile memory 112 is divided into multiple partitions and stores firmware for each function of the image forming apparatus 1, such as printing and scanning, in addition to startup firmware for the image forming apparatus 1.

[0020] 2 is a diagram illustrating the partition configuration of firmware. Firmware FW1 stored in nonvolatile memory 112 of image forming apparatus 1 is startup firmware that is read and executed by control unit 111 when image forming apparatus 1 starts up.

[0021] Firmware FW2 is also startup firmware for the image forming apparatus 1 and is the latest version (update firmware) of firmware FW1. Firmware FW2 is stored in the external storage device 3, and when this external storage device 3 is attached to the external storage device connector 17, the control unit 111 reads out firmware FW2 from the external storage device 3 and performs update processing. In this case, the external storage device connector 17 is an example of a data acquisition unit in the claims.

[0022] The firmware for update may be acquired by the communication unit 16 downloading it from a server or the like via a network under the control of the control unit 111. In this case, the communication unit 16 is an example of a data acquisition unit in the claims.

[0023] In the firmware FW1 and FW2, it is assumed that partitions 1 to 3 store firmware that directly affects the startup of the image forming apparatus 1, and partitions 4 and 5 store firmware that does not affect the startup.

[0024] The partition configuration of the area in which firmware FW1 and firmware FW2 that affect startup are stored is different. Therefore, if firmware FW2 is overwritten in the area in nonvolatile memory 112 where firmware FW1 is stored during an update, image forming apparatus 1 may not start up correctly.

[0025] Therefore, when firmware is created, a management number is assigned according to the partition configuration of the firmware. Figure 3 shows the partition configuration of firmware FW1. In the case of a partition configuration such as that shown in Figure 3, the management number "Core 001" is assigned to the area of ​​firmware that affects startup, and the management number "Non-Core 001" is assigned to the area of ​​firmware that does not affect startup. Each of these management numbers is owned by firmware FW1.

[0026] Figure 4 shows the partition configuration of firmware FW2. The partition configuration of the area that affects startup in firmware FW2 is different from the partition configuration of the area that affects startup in firmware FW1 shown in Figure 3. Therefore, the area of ​​firmware that affects startup in firmware FW2 is assigned a management number "Core 002" that is different from that of firmware FW1. Each of these management numbers is assigned to firmware FW2.

[0027] On the other hand, the partition configuration of the area that does not affect the start of firmware FW2 is the same as that of firmware FW1, and therefore the same management number "non-core 001" is assigned.

[0028] Figure 5 shows the partition configuration of firmware FW3. The partition configuration of the area that affects startup in firmware FW3 is the same as the partition configuration of the area that affects startup in firmware FW1 shown in Figure 3, so the same management number "core 001" is assigned. On the other hand, the partition configuration of the area that does not affect startup in firmware FW3 is different from that of firmware FW1, so the management number "non-core 002" is assigned to the area that does not affect startup of firmware FW3. Each of these management numbers is owned by firmware FW3.

[0029] Figure 6 shows the partition configuration of firmware FW4. The partition configuration of the area that affects startup in firmware FW4 is different from the partition configuration of firmware FW1 to FW3, so it is assigned the management number "core 003." The partition configuration of the area that does not affect startup in firmware FW4 is also different from the partition configuration of firmware FW1 to FW3, so it is assigned the management number "non-core 003." Each of these management numbers is assigned to firmware FW4.

[0030] In this way, control numbers are assigned according to the partition configuration of the areas of firmware that affect the startup of image forming apparatus 1 and the partition configuration of the areas that do not, and when updating the firmware currently stored in non-volatile memory 112 to the latest firmware, the control numbers held by each are compared. If the control numbers are the same, this indicates that the partition configuration is the same, so updating to the latest firmware will not cause any problems with the startup of image forming apparatus 1.

[0031] On the other hand, if the control number is different, the firmware partition configuration will be different, and updating to the latest firmware may cause the image forming device 1 to not start up properly. Therefore, in this case, by not performing the update, it is possible to avoid updating to content that the user does not intend.

[0032] 7 is a flowchart showing the flow of update processing in this embodiment. When the image forming apparatus 1 is powered on (S11), the control unit 111 checks the startup mode of the image forming apparatus 1 (S12). Normally, the startup mode is set to normal mode (a mode in which the image forming apparatus 1 starts up normally). If the startup mode is normal mode (S12; normal mode), the control unit 111 reads and executes firmware FW1 from the nonvolatile memory 112 (S13).

[0033] Furthermore, the control unit 111 checks whether the external storage device 3 is inserted into the external storage device connector 17 (S14). If the external storage device 3 is inserted (S14; YES), the control unit 111 checks whether the external storage device 3 stores update firmware (S15).

[0034] If the external storage device 3 stores the update firmware (S15; YES), the control unit 111 copies the firmware FW1 in the nonvolatile memory 112 to the backup area of ​​the nonvolatile memory 112 (S16).

[0035] 8 is a diagram showing the data configuration of the nonvolatile memory 112. When updating firmware FW1, the control unit 111 first copies the contents that will affect startup to a backup area. Before updating firmware FW1, the control unit 111 backs up the contents that will affect startup in case the update is not performed properly due to an unforeseen event, such as the image forming apparatus 1 suddenly being powered off during the update of firmware FW1.

[0036] Then, the control unit 111 changes the startup mode to the update mode (S17), restarts the image forming apparatus 1, and proceeds to step S11. The update mode is a mode for updating firmware.

[0037] In addition, if the external storage device 3 is not inserted into the external storage device connection unit 17 (S14; NO), or if the external storage device 3 does not store update firmware (S15; NO), the control unit 111 executes the firmware for each function (copying, etc.) and starts up the image forming device 1 into a state where it can operate normally.

[0038] In process S12, the control unit 111 performs a mode check and, if it determines that the mode is update mode (S12; update mode), the control unit 111 reads and executes firmware FW1 stored in the backup area of ​​the nonvolatile memory 112 (S18).

[0039] Furthermore, the control unit 111 checks whether the external storage device 3 is inserted into the external storage device connector 17 (S19). If the external storage device 3 is inserted (S19; YES), the control unit 111 checks whether the external storage device 3 stores update firmware (S20).

[0040] If the external storage device 3 stores update firmware (S20; YES), the control unit 111 compares the version of the update firmware with that of the firmware FW1 stored in the nonvolatile memory 112 (S21). If the versions are different (S21; YES), the control unit 111 compares the management number (core number) of the area that affects the startup of the update firmware with that of the firmware FW1 stored in the nonvolatile memory 112 (S22).

[0041] For example, if the firmware to be updated is firmware FW2 shown in Figure 4, the core number is different from that of firmware FW1 (S22; NO). In this case, the control unit 111 does not update firmware FW1, but changes to normal mode (S26). After this, the process proceeds to S11.

[0042] 5, the core number is the same as firmware FW1 (S22; YES), so the control unit 111 compares the management numbers (non-core numbers) of areas that do not affect startup (S23). If the non-core numbers are different, such as with firmware FW1 and firmware FW3, executing the update as is may result in the loss of data in areas that do not affect startup.

[0043] Therefore, to confirm with the user whether or not to perform the update, if the control unit 111 determines that the non-core numbers are different, such as between firmware FW1 and firmware FW3 (S23; NO), the control unit 111 causes the display unit 121 to display a selection screen prompting the user to perform the update. FIG. 9 shows an example of the display screen on the display unit 121 at this time. If the input reception unit 12 operates the "Yes" button 81 to input an instruction to perform the update to the input reception unit 12 via the touch panel (S27; YES), the control unit 111 determines that the update should be performed and overwrites the area of ​​the non-volatile memory 112 where firmware FW1 is stored with firmware FW3 (S25). The control unit 111 then changes the mode to normal mode (S26). After this, the process returns to S11.

[0044] If the input acceptance unit 12 operates the button 82 indicating "No" and inputs an instruction not to execute the update to the input acceptance unit 12 via the touch panel (S27; NO), the control unit 111 determines not to execute the update and changes the mode to the normal mode (S26). After this, the process proceeds to S11.

[0045] Furthermore, some firmware may be custom firmware with special functions added. When the control unit 111 determines that the non-core numbers are the same, such as firmware FW1 and firmware FW3 (S23; YES), the control unit 111 determines whether or not the firmware FW1 in the non-volatile memory 112 is custom firmware (S24). When the control unit 111 determines that the firmware FW1 in the non-volatile memory 112 is custom firmware (S24; YES), the control unit 111 causes the display unit 121 to display a selection screen for asking whether or not to perform an update, as shown in Fig. 9. In other words, even if the core number and other information match the firmware to be updated, if firmware FW1 is custom firmware, the control unit 111 causes a confirmation screen to be displayed for the user to confirm whether or not to perform an update.

[0046] When the "Yes" button 81 of the input receiving unit 12 is operated to input an instruction to execute an update to the input receiving unit 12 via the touch panel (S27; YES), the control unit 111 determines that an update should be performed and overwrites the area of ​​the nonvolatile memory 112 where the firmware FW1 is stored with the firmware FW3 stored in the external storage device 3 (S25). The control unit 111 then changes the mode to the normal mode (S26). After this, the process proceeds to S11.

[0047] When the input acceptance unit 12 operates the button 82 indicating "No" and inputs an instruction not to execute the update to the input acceptance unit 12 via the touch panel (S27; NO), the control unit 111 determines not to execute the update and changes the mode to the normal mode (S26). After this, the process proceeds to S11.

[0048] If the external storage device 3 is not inserted in the external storage device connector 17 (S19; NO), if the update firmware is not stored in the external storage device 3 (S20; NO), or if the versions of firmware FW1 and the update firmware are the same (S21; NO), the control unit 111 does not update firmware FW1 and changes the mode to normal mode (S26). After this, the process proceeds to S11.

[0049] As explained above, according to this embodiment, when updating the firmware stored in non-volatile memory 112 to the latest firmware, the core numbers indicating the partition configuration are compared, and if the core numbers are different, the update is not performed, thereby avoiding a situation in which an update is performed with content that the user does not intend.

[0050] Furthermore, in this embodiment, if the core number of the firmware stored in non-volatile memory 112 and the latest firmware are the same (the partition configuration of the area that affects startup is the same) but the non-core number is different (the partition configuration of the area that does not affect startup is different), or if the firmware stored in non-volatile memory 112 is custom firmware, the user is asked whether or not to perform an update, thereby making it possible to avoid updating with content that the user does not intend. [Explanation of symbols]

[0051] 1. Image forming device 11 Control Unit 111 Control Unit 112 Non-volatile memory 12 Input reception section 121 Display section 13 Image reading unit 14 Image forming unit 15 Storage section 16 Communications Department 17 External storage device connector 3 External storage device

Claims

1. a storage unit having a plurality of partitions and storing firmware; a control unit that executes firmware updates; a data acquisition unit that acquires firmware for update, the firmware has, as a core number, a management number corresponding to a partition involved in booting, as a management number based on the configuration of the partition; The control unit compares the core number of the firmware to be updated with the core number of the firmware stored in the memory unit, and, on the condition that the two core numbers match, performs a process of overwriting the firmware area stored in the memory unit with the firmware to be updated.

2. further comprising an input receiving unit that receives instructions from a user; the firmware has, as non-core numbers, management numbers corresponding to partitions not involved in the startup, along with the management numbers corresponding to partitions involved in the startup; The control unit comparing the core number and non-core number of the firmware for update with the core number and non-core number of the firmware stored in the storage unit; 2. The image processing device according to claim 1, wherein when the core numbers match but the non-core numbers are different, if the input receiving unit receives input indicating that overwrite is allowed, the image processing device performs a process of overwriting the firmware for update in the firmware area stored in the memory unit.

3. The image processing device described in claim 1 or claim 2, wherein when the firmware stored in the memory unit is custom firmware, the control unit performs a process of overwriting the firmware for update in the firmware area stored in the memory unit when the input receiving unit receives input indicating overwrite permission.

4. 1. A firmware update method for updating firmware stored in a storage unit having a plurality of partitions with update firmware, comprising: the firmware has, as a core number, a management number corresponding to a partition involved in booting, as a management number based on the configuration of the partition; a comparison step of comparing a core number of the firmware for update with a core number of the firmware stored in the storage unit; The firmware update method further includes an overwrite step of overwriting the firmware area stored in the memory unit with the firmware for update if it is determined in the comparison step that the core number held by the firmware for update matches the core number of the firmware stored in the memory unit.

Images