JP2006099393A - Firmware management device, firmware management program, electronic device, recording medium, and firmware management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable an electronic device having rewritable firmware to update the firmware into a new one and then use an appropriate version of firmware selected from other versions of firmware recorded. <P>SOLUTION: The number of system errors with the current firmware within a certain period of time is calculated after that period of time has elapsed (step S2). The numbers of system errors with the firmware of previous versions are read from a storage device 14 (step S3). The number of system errors with the current version of firmware is compared with those with a plurality of previous versions of firmware (step S4). A determination is made as to whether there is a version of firmware having a smaller number of system errors than the current version (step S5); the current firmware is changed to the corresponding version only if there is such a version (step S6). Then the device is rebooted (step S7). <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a firmware management apparatus, a firmware management program, an electronic device, a recording medium, and a firmware management method.

  Conventionally, devices such as multifunction peripherals, printers, communication management devices, computers, etc., have their processing programs, that is, firmware rewritable ROM (Read Only Memory) in the device, etc., in order to expand their functions and resolve device problems. Is stored in a rewritable manner. In a computer, an OS (Operating System) and a BIOS (Basic Input / Output System) correspond to this processing program, and are recorded in a nonvolatile memory such as a flash memory mounted on a motherboard. Some firmware that does not need to be updated is recorded in a mask ROM or the like in a non-rewritable manner. However, recent information processing technology has been rapidly developed, and flash memory and EEPROM (Electrically Erasable and Many programs are recorded in a rewritable manner (Programmable ROM).

  Conventionally, as a technique for updating firmware of various electronic devices, a computer peripheral device and a program update control method thereof that perform update control in a state where a startup program in a ROM can be reliably and reconstructed have been proposed (for example, see Patent Document 1). reference). In the technique described in Patent Document 1, the address map is changed, the activation program for controlling the peripheral device is stored in a rewritable ROM, and when the activation program is rewritten, it is already written in the ROM on the work memory. The boot program stored in the memory is saved in the work memory, and the ROM update or the ROM restoration is controlled based on the execution state of the downloaded new boot program.

  In addition, since the technique described in Patent Document 1 requires a change in the address map, various problems such as complicated hardware arise. A firmware update system for solving such a problem has also been proposed. (For example, refer to Patent Document 2).

When updating the old firmware stored in the flash ROM to the new firmware, the system described in Patent Document 2 uses the address storage unit to store the address information indicating the address of the flexible disk device initialization unit in the nonvolatile RAM. Stored in the initialization means address storage area. If an error occurs after updating to the firmware, the error information is stored in the error information storage area, the flexible disk device initialization means is copied to the special area, further expanded in the memory expansion area, executed, and updated to the old firmware. return.
JP-A-7-146837 Japanese Patent Laid-Open No. 2000-3276

  As described above, when a problem occurs after updating the firmware, it is usually performed to return to the previous firmware.

  However, although the previous firmware itself functions, there may be a fatal defect, or a non-fatal but frequent error may occur. Even in the prior art related to firmware update including Patent Documents 1 and 2 described above, for writing errors when writing new firmware to a writable ROM, and errors when executing new firmware once, Although it is possible to deal with returning to the previous firmware, it is not possible to deal with any problems with the previous firmware itself.

  Therefore, the firmware updater usually maintains the state when the new firmware can be installed, and adopts the new firmware if it is not, or if there are too many errors during execution. Instead, the previous firmware is returned to the state in which the firmware is mounted on the electronic device. Actually, even if the error caused by starting up the new firmware itself is much larger than the error caused by starting up the previous firmware, the error should be made unless it is a service person familiar with the electronic device. Therefore, the user uses the electronic device with the new firmware executable.

  The present invention has been made in view of the above-described circumstances. For electronic devices equipped with rewritable firmware, the firmware is updated to new firmware, and then recorded from other recorded firmware versions. Firmware management apparatus, firmware management program, electronic device equipped with the firmware management apparatus or firmware management program, computer-readable recording medium recording the firmware management program, and firmware capable of using appropriate firmware Its purpose is to provide a management method.

The present invention is constituted by the following technical means in order to solve the above-described problems.
A first technical means is a firmware management apparatus that manages firmware of an electronic device stored in a rewritable nonvolatile storage means in which current firmware that is currently used firmware is rewritable, Counting means for counting the number of errors that occurred when the current firmware is executed on the electronic device, the number of errors of the current firmware counted by the counting means, and executing the firmware version used in the past on the electronic device A comparison unit that compares the number of errors that occurred at the time, and a version of firmware that is more suitable for use than the current firmware among the versions of firmware that were used in the past, based on the comparison result of the comparison unit The specifying means for specifying and the current firmware by the specifying means And changing means for changing the constant version of firmware is obtained by comprising the.

  The second technical means further comprises an average number calculating means for calculating an average number of errors from the time of updating the current firmware to a lapse of a predetermined period for the current firmware in the first technical means, wherein the comparing means Instead of the number of errors, the average number of errors of the current firmware calculated by the average number calculation means is compared with the average number of errors that occurred when the version of firmware used in the past was executed on the electronic device. It is characterized by that.

  According to a third technical means, in the second technical means, when the specifying means has a version of firmware having an average number of errors smaller than the average number of errors of the current firmware based on a comparison result by the comparing means The corresponding version of firmware is specified as a version suitable for the use.

  According to a fourth technical means, in the second technical means, the specifying means determines the average of the current firmware with respect to the average number of errors of the firmware of the version used in the past as a comparison target, based on the comparison result by the comparison means. When the ratio of the number of errors is equal to or greater than a predetermined ratio, the corresponding version of firmware is identified as a version suitable for the use.

  According to a fifth technical means, in any one of the first to fourth technical means, the error is a system error.

  According to a sixth technical means, in the second technical means, the error corresponds to a system error and a normal error which is another error, and the counting means includes a system error number and a normal error number as error numbers, respectively. Means for counting, the average number calculating means includes means for calculating an average system error number and an average normal error number as an average error number, respectively, and the comparing means includes an average system error number and an average error number. A means for performing a comparison based on each of the average number of normal errors, and the specifying means, based on a comparison result by the comparison means, the current system value for the average number of system errors of firmware used in the past as a comparison target. When the ratio of the average number of system errors in the firmware is equal to or higher than the first predetermined ratio, and the comparison When the ratio of the average normal error number of the current firmware to the average normal error number of the firmware of the version used in the past is equal to or less than the second predetermined ratio, the corresponding version of firmware is suitable for the use. It is characterized by specifying as a version.

  According to a seventh technical means, in any one of the first to sixth technical means, the comparing means excludes firmware versions whose used period is shorter than a predetermined period from comparison targets. Is.

  The eighth technical means is any one of the first to seventh technical means, further comprising means for designating a version to be specified by the specifying means.

  A ninth technical means is a firmware management program for managing the firmware of the electronic device stored in the rewritable nonvolatile storage means, the current firmware being the currently used firmware, Counting the number of errors that occurred when the current firmware was executed by the electronic device, storing and storing in the storage means of the electronic device, the number of errors of the current firmware counted in the counting step, and past A comparison step for reading out and comparing the number of errors that occurred when the version of firmware used in the electronic device is executed by the electronic device, and a comparison result in the comparison step, which has been used in the past A new version of the firmware that is more suitable for use than the current firmware. A specifying step of specifying the firmware of the version, and a changing step of changing the current firmware stored in the nonvolatile storage means to the version of the firmware specified in the specifying step. It is what.

  A tenth technical means further includes an average number calculating step of calculating an average number of errors from the time of updating the current firmware to a lapse of a predetermined period for the current firmware in the ninth technical means, wherein the comparing step Instead of the number of errors, the average number of errors of the current firmware calculated in the average number calculation step is compared with the average number of errors that occurred when the version of firmware used in the past was executed on the electronic device. It is characterized by that.

  According to an eleventh technical means, in the tenth technical means, there is a version of firmware having an average error number smaller than the average error number of the current firmware based on the comparison result in the comparison step in the specific step. In this case, the corresponding version of firmware is identified as a version suitable for the use.

  According to a twelfth technical means, in the tenth technical means, the specifying step is based on the comparison result in the comparison step, and the current firmware is compared with the average number of errors of the firmware of the version used in the past as a comparison target. When the ratio of the average number of errors is equal to or greater than a predetermined ratio, the corresponding version of firmware is specified as a version suitable for the use.

  A thirteenth technical means is characterized in that, in any of the ninth to twelfth technical means, the error is a system error.

  A fourteenth technical means according to the tenth technical means, wherein the error corresponds to a system error and a normal error which is another error, and the counting step includes a step of counting the number of system errors as the number of errors, Counting the number of normal errors as the number of errors, and the step of calculating the average number includes the step of calculating the average number of system errors as the number of average errors and the step of calculating the number of normal errors as the average number of errors. And the comparison step includes a step of performing a comparison based on an average number of system errors as an average number of errors, and a step of performing a comparison based on an average number of normal errors as an average number of errors. Based on the comparison result in the step, the firmware version of the past used for comparison The ratio of the average system error number of the current firmware to the average number of system errors is equal to or higher than the first predetermined ratio, and the current normal error number to the average normal error number of the firmware used in the past that is the comparison target. When the ratio of the average number of normal errors of the firmware is equal to or less than the second predetermined ratio, the corresponding version of the firmware is specified as the version suitable for the use.

  According to a fifteenth technical means, in any one of the ninth to fourteenth technical means, the comparison step excludes firmware versions whose used period is shorter than a predetermined period from comparison targets. Is.

  The sixteenth technical means according to any one of the ninth to fifteenth technical means, further comprises a step of predesignating a version to be specified in the specifying step.

  The seventeenth technical means is any one of the ninth to sixteenth technical means, wherein the firmware management program is included as a part of the firmware.

  An eighteenth technical means is an electronic apparatus comprising the firmware management apparatus according to any one of the first to eighth technical means.

  A nineteenth technical means is an electronic apparatus characterized in that the firmware management program according to any of the ninth to seventeenth technical means is stored in an executable manner.

  A twentieth technical means is a computer-readable recording medium recording the firmware management program according to any of the ninth to seventeenth technical means.

  A twenty-first technical means is a firmware management method for managing firmware of an electronic device stored in rewritable non-volatile storage means, which is current firmware that is currently being used. Counting the number of errors that occurred when the current firmware was executed by the electronic device, storing and storing in the storage means of the electronic device, the number of errors of the current firmware counted in the counting step, and past A comparison step for reading out and comparing the number of errors that occurred when the version of firmware used in the electronic device is executed by the electronic device, and a comparison result in the comparison step, which has been used in the past Versions that are more suitable for use than the current firmware. And a change step of changing the current firmware stored in the non-volatile storage means to a version of the firmware specified in the specification step. Is.

  According to the present invention, for an electronic device having rewritable firmware, it is possible to use appropriate firmware from other recorded versions of firmware after updating the firmware to new firmware. . Therefore, by applying the present invention, even if the firmware is updated and then changed to an older version of the firmware, the optimal version of all the provided versions is not necessary. Since the firmware is used, it is possible to achieve a state in which defects are eliminated to the maximum in all versions.

  The present invention relates to management of firmware of electronic devices. The present invention may also be implemented as a firmware management apparatus, a firmware management program, an electronic device, a recording medium storing the program, or a firmware management method for changing firmware in accordance with a processing procedure in the firmware management apparatus or firmware management program. is there. Here, firmware currently used in the electronic device (hereinafter referred to as current firmware) is stored in rewritable nonvolatile storage means so that the version can be upgraded or degraded. .

  Further, the firmware management apparatus according to the present invention is an apparatus in which the firmware management program is incorporated so as to be executable, or means corresponding thereto (counting means, comparison means, specifying means, changing means, average number calculating means, etc. described later) Can be configured as a device equipped with hardware. Firmware that reduces errors during execution by mounting such a firmware management device as hardware in an electronic device, or by mounting such a firmware management program as a part of firmware in an electronic device The firmware is managed so that is selected. As an example of installing a firmware management program in electronic equipment as part of firmware, firmware management that manages itself in a rewritable nonvolatile semiconductor memory (PROM such as EEPROM such as flash memory (flash ROM)) of the electronic equipment The firmware including the program is stored in an executable manner, or only the firmware management program is stored as a firmware in a non-rewritable memory such as a mask ROM (of course, a rewritable memory may be used) as will be described later with reference to FIG. For example, the firmware is stored in a rewritable nonvolatile semiconductor memory.

  As described above, the electronic device according to the present invention can be realized as an electronic device including the firmware management apparatus described here, or an electronic device that stores the firmware management program in an executable manner. Here, electronic devices include copiers, facsimile machines, scanners, their multifunction devices, terminal adapters and routers, security devices incorporating firewalls and virus check functions, communication devices such as network adapters, and PCs. Examples include various devices such as network adapters in (personal computers), various boards such as video encoders, household electrical appliances such as television receivers and video recorders, automobiles, and components thereof.

  Hereinafter, the present invention will be described with a focus on a firmware management apparatus. Further, the firmware management apparatus is an apparatus in which the current firmware including the firmware management program is incorporated so as to be executable, and the past has been used in the past. The following description is mainly based on the premise that the firmware management program is also included in each version of firmware. Then, a description will be mainly given of a form in which the current firmware including the firmware management program according to the present invention is incorporated into the main controller of the multifunction machine as an example of an electronic device. Accordingly, here, the firmware management apparatus is composed of an arithmetic device, various storage devices, and a firmware management program in the main controller. The program, electronic device, recording medium, and method according to the present invention are not limited to these assumptions, and needless to say, the following description can be used.

  FIG. 1 is a diagram illustrating a configuration example of a firmware management apparatus according to an embodiment of the present invention, and is a diagram illustrating an example of a firmware management apparatus incorporated in a main controller of a multifunction peripheral. In the figure, 1 is a main controller (hereinafter simply referred to as a controller), 2 is an image printing unit (printer unit), 3 is an image reading unit (scanner unit), 4 is an external I / F (interface), 11 is RAM, A flash ROM (hereinafter referred to as a flash memory), 13 is a CPU, and 14 is a storage device.

  The MFP illustrated here has an image printing unit 2 that prints an image, an image reading unit 3 that reads an image of an original, and an external I / F such as a LAN (Local Area Network) adapter connected to the bus. It is controlled by the controller 1.

  The controller 1 includes a RAM (Random Access Memory) 11 for storing processing data, a flash memory 12 for storing execution programs, a CPU (Central Processing Unit) 13, and a storage device for storing past firmware error history. ing. The current firmware including the firmware management program according to the present invention is stored in the flash memory 12, and is read and executed on the RAM 11 by the CPU 13 at the time of execution. The controller 1 functions by this execution, and image printing is performed. The unit 2, the image reading unit 3, the external I / F 4 and the like are intensively controlled. Note that a sub-controller may be incorporated in each of the units 2 to 4. Further, the firmware version used in the past corresponding to the current firmware is stored in the storage device 14.

  The firmware management apparatus according to this embodiment includes the following counting means, comparing means, specifying means, and changing means. The counting means counts the number of errors that occur when the current firmware is executed by the controller 1. Actually, for example, the CPU 13 increments the error history count for the version in the storage device such as the storage device 14 every time an error occurs, so that the count result is stored as an error history. This counting process is also performed on the firmware of the previous version (generation) that has become the current firmware, and the counting result is stored in the storage device 14 as an error history.

  The comparison unit compares the number of errors of the current firmware counted by the counting unit with the number of errors that occurred when the controller 1 executed one or more versions of firmware used in the past. For example, the CPU 13 may read the error history from the storage device 14 onto the RAM 11 and execute the comparison process.

  The specifying unit specifies a version of firmware that is more suitable for use than the current firmware from the versions of firmware used in the past based on the comparison result of the comparison unit. Here, when there is no version suitable for use compared with the current firmware, it is not necessary to specify. This specifying process may be executed by the CPU 13 based on the comparison process result, for example. The changing means changes the current firmware stored in the rewritable nonvolatile storage means such as the flash memory 12 to the version of firmware specified by the specifying means. Although this change process will be described later, when the current firmware is the latest firmware in the controller 1, it is degraded. Firmware changes are explained on the assumption that firmware upgrades (upgrades) are performed by rewriting the firmware itself. However, even when upgrading with a patch, when upgrading, it is necessary to In this case, you can delete the patch part.

  In FIG. 1, each of the above-described units is configured by a program (firmware management program according to the present embodiment) whose processing contents are procedures, and an arithmetic device such as a CPU 13 for executing the program. . Therefore, this program includes a counting step, a comparing step, a specifying step, and a changing step. Also, the firmware management method according to the present embodiment includes these steps.

  FIG. 2 is a flowchart for explaining a processing example in the firmware management apparatus of FIG. 1, and is also a flowchart for explaining a processing procedure by the firmware management program and method according to the embodiment of the present invention.

  Here, an example will be described in which only a system error, which is an error that cannot be recovered by the MFP user, is considered as an error, but it can be handled only for other errors (including communication errors and jams). Alternatively, both may be handled together, or both may be handled individually as in other embodiments described below. The system error refers to a fatal error that causes the system to stop, and includes an error that can be recovered by restarting the power supply and restarting, and an error that can be recovered by starting from another system.

  First, it is determined whether or not a certain period has elapsed (step S1), and the processes after step S2 are executed when the certain period has elapsed. The fixed period may be determined as appropriate, such as 1 month, 10 days, or 1 day, or may be determined based on the operating time of the electronic device or its controller 1. In addition, here, it is assumed that the processing after step S2 is performed after a certain period of time has elapsed from when the new firmware is updated as the current firmware, but the firmware is different from this firmware (firmware that is not a different version but a different target) It may be considered that an error starts to occur due to the compatibility with the introduction of, and the processing after step S2 may be executed at regular intervals.

  In step S2, the number of system errors within the period of the current firmware is calculated (step S2). The number of system errors of the past version is read from the storage device 14 (step S3). The number of system errors between the current version and past versions of firmware is compared (step S4). Then, it is determined whether or not there is a version of firmware that has a smaller number of system errors than the current one (step S5). On the other hand, if it is determined in step S5 that it exists, the current firmware is changed to the corresponding version (step S6) and restarted (step S7). After the restart, the controller 1 is driven by a firmware version suitable for use as compared with the above-described current firmware (already converted to firmware that has been used previously). Even if the version of the firmware is older than the firmware used before the change, the current firmware becomes the current firmware.

  FIG. 3 is a flowchart for explaining the firmware change process executed in the firmware management process of FIG.

  The firmware change process in steps S6 and S7 described above will be supplementarily described. Before the change, the current version of firmware (current firmware) is stored in the flash memory 12, transferred to the RAM 11, and being executed. First, the corresponding version of firmware is read from the storage device 14 and overwritten in the flash memory 12 (step S11). At this time, the current firmware is erased by overwriting, but is temporarily stored in the RAM 11 as described above, and there is no problem in executing the current firmware. In step S11, the current firmware may be moved to the storage device 14 without being overwritten. In this case, this current firmware is also stored as one version of the past firmware.

  After step S11, the number of system errors is reset (step S12) and restarted (step S13). After this, normal post-startup processing is performed. At this point, the changed version (update version) firmware is already stored in the flash memory 12, and therefore the CPU 13 of the controller 1 stores the changed version firmware in the RAM 11. Transfer and execute (step S14). From the process of step S14, the controller 1 performs control based on the changed version of firmware.

  As described above, in the present embodiment, when an error occurs in the current firmware, the generation for which the firmware is to be degraded (may be upgraded) is identified from the comparison with the error occurrence status in the past multiple generations of firmware. Therefore, in the conventional technology, the process of degrading from the error occurrence frequency in a plurality of generations used in the past could not be performed, but according to the present embodiment, when a system error or the like frequently occurs after upgrading the firmware. It is possible to suppress the occurrence of system errors and the like by returning to firmware with few errors from a plurality of past generations in an emergency evacuation. As described above, according to the present embodiment, for an electronic device equipped with rewritable firmware, after updating the firmware to the new firmware, an appropriate firmware is recorded from one or more recorded versions of firmware. Can be selected and used even if it is old firmware and degraded.

  FIG. 4 is a flowchart for explaining a processing example in a firmware management apparatus according to another embodiment of the present invention represented by the firmware management apparatus in FIG. 1, and a firmware management program according to another embodiment of the present invention. It is also a flowchart for explaining the processing procedure by the method.

  As another embodiment according to the present invention, in the above-described embodiment, the firmware management apparatus is provided with the following average number calculation means, and the error numbers are not simply compared, but compared with the average. preferable.

  The average number calculating means calculates the average number of errors from the time of updating the current firmware to the lapse of a predetermined period for the current firmware, for example, by dividing the count value (number of error occurrences) by the counting means by the predetermined period. Means. Here, it is possible to calculate an average of not only the time of update but also a predetermined period thereafter. The predetermined period may be, for example, the period as described above (1 day, 10 days, etc.), or the average number of errors may be calculated in consideration of the time during activation. Then, instead of the number of errors, the comparison unit calculates the average number of errors of the current firmware calculated by the average number calculation unit, and the average number of errors that occurred when the version of firmware used in the past was executed on the electronic device. Compare The firmware management program according to the present embodiment includes steps corresponding to these means.

  And in this embodiment, it is preferable to provide the following specific means. If there is a version of firmware having an average error number smaller than the average error number of the current firmware based on the comparison result, the specifying unit specifies the corresponding version of firmware as a version suitable for use. The firmware management program according to the present embodiment includes steps corresponding to the specifying means.

  In the firmware change process in the present embodiment, first, the same process (step S21) as step S1 described in FIG. 2 is executed, and the process after step S22 is executed when a certain period of time has passed. Here, the case where only a system error is considered as an error is also illustrated here.

  In step S22, the average number of system errors per day for the current firmware is calculated (step S22). The number of system errors in the past version is read from the storage device 14 (step S23), and the average number of system errors per day for each past version is calculated (step S24). Then, the average number of system errors between the current version and past versions of firmware is compared (step S25). Then, it is determined whether or not there is a version of firmware that has a smaller average system error number than the present one (step S26). On the other hand, if it is determined in step S26 that the current firmware is present, the current firmware is changed to the corresponding version (step S27) and restarted (step S28). Thereafter, as described above, the controller 1 is driven by a firmware version suitable for use.

  As described above, according to the present embodiment, in addition to the effects of the embodiment described with reference to FIGS. 1 to 3, the degradation is not performed by changing the average number of errors, but the degradation is not changed from the sudden number of errors. Etc., so it is not necessary to switch the version quickly.

  FIG. 5 is a flowchart for explaining a processing example in a firmware management apparatus according to another embodiment of the present invention represented by the firmware management apparatus in FIG. 1, and a firmware management program according to another embodiment of the present invention. It is also a flowchart for explaining the processing procedure by the method.

  As another embodiment of the present invention, in the embodiment provided with the above average number calculation means, when specifying the version suitable for use in the specifying means, the specification based on the ratio of the average error number of the current firmware may be performed. preferable. That is, according to the comparison means by the comparison means, the identification means in the present embodiment has a ratio of the average error number of the current firmware to the average error number of the firmware of the version used in the past that is the comparison target is not less than a predetermined ratio. If this happens, the corresponding version of firmware is identified as a version suitable for use. The firmware management program according to the present embodiment includes steps corresponding to the specifying means.

  The firmware update process according to the present embodiment performs the same process as steps S21 to S26 described in FIG. 4 (steps S31 to S36), and then ends the process as it is when it is determined that it does not exist in step S36. If it is determined that it exists, the process proceeds to step S37. Here, the case where only a system error is considered as an error is also illustrated here.

  In step S37, it is determined whether or not the average system error number of the current version is equal to or greater than a certain ratio a from the corresponding version. Only when the ratio is equal to or greater than the predetermined ratio a, the current firmware is changed to the corresponding version (step S38) and restarted (step S39). Thereafter, as described above, the controller 1 is driven by a firmware version suitable for use.

  As described above, according to the present embodiment, in addition to the effects of the embodiment described with reference to FIG. 4, even if the current firmware has more errors than the past firmware, it is not degraded in the case of a small difference. The possibility of causing other problems is eliminated.

  FIG. 6 is a flowchart for explaining an example of processing in a firmware management apparatus according to another embodiment of the present invention represented by the firmware management apparatus in FIG. 1, and a firmware management program according to another embodiment of the present invention. It is also a flowchart for explaining the processing procedure by the method.

  As another embodiment of the present invention, in the embodiment provided with the above average number calculating means, each of a system error and a normal error (communication error or jam occurrence), which is another error, before the specific process is performed. It is preferable to perform the treatment separately. Therefore, in the present embodiment, the counting means has both means for counting the number of system errors and means for counting the number of normal errors, and the average number calculating means is means for calculating the average number of system errors; The means for calculating the average number of normal errors has both, and the comparison means has both means for comparing based on the average number of system errors and means for comparing based on the average number of normal errors. Furthermore, the specifying means in the present embodiment is configured such that the ratio of the average system error number of the current firmware to the average system error number of the firmware of the version used in the past that is the comparison target is based on the comparison result by the comparison means. When the ratio is equal to or greater than the predetermined ratio and the ratio of the average normal error number of the current firmware to the average normal error number of the firmware of the version used in the past that is the comparison target is equal to or less than the second predetermined ratio The corresponding version of firmware is identified as a version suitable for use. The firmware management program according to the present embodiment includes steps corresponding to these means.

  In the firmware change process according to the present embodiment, first, the same processes (steps S41 to S47) as steps S31 to S37 described in FIG. 5 are performed. However, the processing in steps S42 to S44 is performed not only on the number of system errors but also on the number of normal errors.

  In the present embodiment, the determination in steps S46 and S47 is a case where there is a version V firmware having a smaller average system error number than the current firmware, and the average system error number of the current firmware is constant from the version V. Even if the ratio is equal to or greater than A, the firmware change is not uniformly executed. In other words, in the case of YES in step S47, it is determined whether or not the firmware needs to be changed (whether or not it is appropriate to change) based on the average value of the average number of normal errors.

  Specifically, first, based on the average number of normal errors for the current firmware calculated in steps S42 to S44 and other versions of firmware that have been used, the average normal of the current version and multiple versions of firmware used in the past The number of errors is compared (step S48). The average number of normal errors may be calculated before the comparison process in step S48. As a result of the comparison in step S48, it is determined whether or not the average number of normal errors of the current version is equal to or less than a certain ratio B from version V (step S49). If the ratio is larger than the ratio B, the process is terminated. Only when the ratio is equal to or less than the ratio B, the current firmware is changed to the corresponding version V (step S50) and restarted (step S51). Thereafter, as described above, the controller 1 is controlled by a firmware version suitable for use.

  Here, the values of the ratios A and B are basically design matters. For example, if A = 1.4 (140%) and B = 0.5 (50%), the current firmware is version V. Even if the average number of system errors is 40% or more higher than the firmware, if the average number of normal errors is 50% or less, the current firmware is not changed to version V. Conversely, if the current firmware is 40% or more higher than the version V in the average number of system errors and is larger than 50% in the average number of normal errors, the current firmware is changed to the version V. In view of the normal use state, the current firmware is often the latest version accumulated, and this change corresponds to a degradation.

  As described above, according to the present embodiment, in addition to the effects of the embodiment described with reference to FIG. 4, even if the system error of the current firmware increases, the normal error is reduced enough to compensate for it. If it is, changes such as degradation are prohibited, so the actual trouble can be kept small.

  FIG. 7 is a flowchart for explaining a processing example in a firmware management apparatus according to another embodiment of the present invention represented by the firmware management apparatus in FIG. 1, and a firmware management program according to another embodiment of the present invention. It is also a flowchart for explaining the processing procedure by the method.

  As another embodiment of the present invention, in the embodiment described with reference to FIG. 6, it is preferable that the change process is executed when there are too many system errors even if there are few normal errors. The firmware management apparatus according to the present embodiment includes means for executing such change processing, and the firmware management program according to the present embodiment includes steps corresponding to the means.

  In the firmware change process according to the present embodiment, first, the same processes (steps S61 to S66) as steps S41 to S46 described in FIG. 6 are performed. The processing in steps S62 to S64 is not only performed for the number of system errors but also for the number of normal errors. In step S66, the process proceeds to step S67 and subsequent steps only when there is a version V with a small average system error number. In the present embodiment, two threshold values are provided in the comparison based on the average system error number, and one threshold value is provided in the comparison based on the average normal error number, and the threshold processing is performed after step S67.

  In step S67, it is determined whether or not the average system error number of the current version is equal to or greater than a certain ratio C from version V. If the result of this determination is that the ratio is equal to or greater than C, the current firmware is changed to the corresponding version V (step S71) and restarted (step S72). Thereafter, as described above, the controller 1 is controlled by a firmware version suitable for use.

  On the other hand, when it is determined in step S67 that the ratio is not equal to or greater than C, the process proceeds to step S68. In step S68, it is determined whether or not the average number of system errors of the current firmware is greater than or equal to a certain ratio D from version V. If the result of this determination is not greater than or equal to the ratio D, the processing is terminated, and if it is greater than or equal to the ratio D, the process proceeds to step S69. In step S69, the average number of normal errors between the current firmware and a plurality of versions of firmware used in the past is compared. The average number of normal errors may be calculated up to the comparison process in step S70, and in this example, it is calculated in steps S62 to S64. As a result of the comparison in step S69, it is determined whether or not the average number of normal errors of the current firmware is equal to or less than a certain ratio B from version V (step S70). If the ratio is larger than the ratio B, the process is terminated. Only when the ratio is equal to or less than the ratio B, the current firmware is changed to the corresponding version V (step S71) and restarted (step S72). Thereafter, as described above, the controller 1 is controlled by a firmware version suitable for use.

  Here, the values of the ratios C, D, and B are basically design matters, and C> D may be satisfied. For example, C = 1.5 (150%), D = 1.1 (110%) , B = 0.5 (50%), even if the current firmware does not increase by more than 50% in the average system error number than the version V firmware, it will increase by more than 10% and in the average normal error number by more than 50% If it is larger, the current firmware is changed to version V. In view of the normal use state, the current firmware is often the latest version accumulated, and this change corresponds to a degradation. On the other hand, even if the current firmware increases by 10% or more and less than 50% in the average number of system errors from version V, if the average number of normal errors is 50% or less, the current firmware is not changed to version V. In this way, in the present invention, it is preferable to add a process that eliminates the need to change the version as much as possible.

  As described above, according to the present embodiment, in addition to the effects of the embodiment described with reference to FIG. 6, the change process is executed when there are too many system errors even if there are few normal errors. It is possible to set an allowable limit and perform the change process appropriately.

  FIG. 8 is a flowchart for explaining a processing example in the firmware management apparatus according to another embodiment of the present invention represented by the firmware management apparatus in FIG. 1, and a firmware management program according to another embodiment of the present invention. It is also a flowchart for explaining the processing procedure by the method.

  As another embodiment of the present invention, in the comparison process in each of the above-described embodiments, it is preferable to exclude firmware versions whose used period is shorter than a predetermined period from comparison targets. The firmware is released at a certain interval, but if there is a version with a short calculation period, it is possible that the number of errors is small or biased, and other problems may occur, so the comparison target Is preferably excluded. The firmware management apparatus according to the present embodiment includes means for executing such exclusion processing, and the firmware management program according to the present embodiment includes steps corresponding to the means. Hereinafter, for simplification of description, the present embodiment will be described with reference to FIG. 8 only for an example of performing this exclusion on the embodiment described with reference to FIG. This description can be applied to the form.

  In the firmware change process according to the present embodiment, first, the same processes (steps S81 to S83) as steps S1 to S3 described in FIG. 2 are performed. Here, the case where only a system error is considered as an error is also illustrated here.

  After step S83, a change candidate list (also referred to as an update candidate list) is created by removing a version with a short usage period from the versions used in the past (step S84). Then, the number of system errors of the firmware is compared with the current version and a plurality of versions used in the past in the change candidate list (step S85). Then, it is determined whether or not a version of firmware having a smaller system error number than the current one exists in the change candidate list (step S86). On the other hand, if it is determined in step S86 that the current firmware is present, the current firmware is changed to the corresponding version (step S87) and restarted (step S88). After the restart, the controller 1 is controlled by the firmware version suitable for use as described above.

  As described above, according to the present embodiment, in addition to the effects of the above-described embodiments, since a change (degrade or upgrade) to firmware that is used only in a too short period is excluded from the comparison target, Other errors that are only used for the first time will not be changed to the expected version of firmware.

  FIG. 9 is a flowchart for explaining a processing example in a firmware management apparatus according to another embodiment of the present invention represented by the firmware management apparatus in FIG. 1, and a firmware management program according to another embodiment of the present invention. It is also a flowchart for explaining the processing procedure by the method.

  As another embodiment of the present invention, it is preferable that a version to be specified is specified in advance in the specifying process in each of the above-described embodiments. That is, in this embodiment, the firmware management apparatus is provided with means for specifying a version to be specified by the specifying means, and such specification is performed in advance. Of course, a version that is not a specific target may be specified.

  The firmware management program according to the present embodiment includes steps corresponding to this means. In the form that the firmware management program is included in the current firmware or the past firmware as shown in the example, information such as what version is traced back to the firmware or compatibility is described up to this version is described. And processing based on the information is performed. Thus, for example, it is possible to specify that the degradation target is limited to the current firmware to the past N generations. In addition, when describing the grades that can be used in the firmware, it is also possible to specify more than this version so that subsequent upgrades are possible, or upgrade by performing a change process every predetermined period Instead of making it impossible, it is better to basically perform the change process only once. Hereinafter, for simplification of description, this embodiment will be described with reference to FIG. 9 only for an example of performing this exclusion on the embodiment described with reference to FIG. This description can be applied to the form.

  In the firmware change process according to the present embodiment, first, the same processes (steps S91 to S93) as steps S1 to S3 described in FIG. 2 are performed. Here, the case where only a system error is considered as an error is also illustrated here.

  After step S93, a change candidate list (also referred to as an update candidate list) consisting only of versions limited to the current version is created from the versions used in the past (step S94). Then, the number of system errors of the firmware is compared with the current version and a plurality of versions used in the past in the change candidate list (step S95). Then, it is determined whether or not a version of firmware having a smaller number of system errors than the current one exists in the change candidate list (step S96). On the other hand, if it is determined in step S96 that the current firmware is present, the current firmware is changed to the corresponding version (step S97) and restarted (step S98). After the restart, the controller 1 is controlled by the firmware version suitable for use as described above.

  As described above, according to the present embodiment, in addition to the effects of the above-described embodiments, since it is excluded from the comparison target so as to prohibit degrading retroactively to a version that is too old, other versions that are expected to have other problems It will not be changed to firmware. For example, even when the firmware upgrade is accompanied by a change in the standard of the network system connected to the electronic device, it is possible to prevent the firmware from being degraded too far back.

  FIG. 10 is a diagram showing a configuration example of a firmware management apparatus according to another embodiment of the present invention. In FIG. 10, reference numeral 5 denotes a firmware management unit, and other components are the same as those in FIG. Detailed description is omitted.

  In FIG. 10, unlike the firmware management apparatus of FIG. 1, a firmware management unit 5 is provided separately from the controller 1 as a firmware management apparatus. The firmware management unit 5 is, for example, a sub-controller connected to the controller 1, and the firmware management program according to the present invention is stored in the sub-controller as a firmware in a storage means such as a mask ROM or a flash memory. ing. In this example, the sub controller is actually activated first.

  As described above, the firmware management program as one of the firmware of the electronic device (or other electronic device for controlling the electronic device; however, it is necessary to start from the other electronic device) is compatible with the current firmware and the corresponding firmware. It may be configured to be incorporated separately from previous versions of firmware.

  Finally, an embodiment of a recording medium storing a firmware management program and data for realizing a firmware management function according to the present invention will be briefly described. Specifically, a CD-ROM, a magneto-optical disk, a DVD-ROM, an FD, a flash memory, and other various ROMs and RAMs can be assumed as the recording medium. The firmware management program according to each embodiment of the present invention described above Can be recorded and distributed on these recording media to facilitate the realization of this function. Then, the information processing apparatus such as a computer is loaded with the recording medium as described above, and the program is read by the information processing apparatus, or the program is stored in the recording medium included in the information processing apparatus, By reading in response, the firmware management function according to the present invention can be executed.

It is a figure which shows the example of 1 structure of the firmware management apparatus which concerns on one Embodiment of this invention. It is a flowchart for demonstrating the process example in the firmware management apparatus of FIG. FIG. 3 is a flowchart for explaining firmware change processing executed in the firmware management processing of FIG. 2. It is a flowchart for demonstrating the process example in the firmware management apparatus which concerns on other embodiment of this invention represented by the firmware management apparatus of FIG. It is a flowchart for demonstrating the process example in the firmware management apparatus which concerns on other embodiment of this invention represented by the firmware management apparatus of FIG. It is a flowchart for demonstrating the process example in the firmware management apparatus which concerns on other embodiment of this invention represented by the firmware management apparatus of FIG. It is a flowchart for demonstrating the process example in the firmware management apparatus which concerns on other embodiment of this invention represented by the firmware management apparatus of FIG. It is a flowchart for demonstrating the process example in the firmware management apparatus which concerns on other embodiment of this invention represented by the firmware management apparatus of FIG. It is a flowchart for demonstrating the process example in the firmware management apparatus which concerns on other embodiment of this invention represented by the firmware management apparatus of FIG. It is a figure which shows the example of 1 structure of the firmware management apparatus which concerns on other embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Main controller (controller), 2 ... Image printing part, 3 ... Image reading part, 4 ... External I / F, 5 ... Firmware management part, 11 ... RAM, 12 ... Flash ROM (flash memory), 13 ... CPU, 14: Storage device.

Claims (21)

A firmware management device that manages firmware of an electronic device stored in a rewritable nonvolatile storage means that is current firmware that is currently being used,
Counting means for counting the number of errors generated when the current firmware is executed by the electronic device;
Comparison means for comparing the number of errors of the current firmware counted by the counting means with the number of errors that occurred when the version of firmware used in the past was executed on the electronic device,
Based on the comparison result by the comparison means, a specification means for specifying a firmware version suitable for use compared to the current firmware from the firmware versions used in the past;
Changing means for changing the current firmware to the version of firmware specified by the specifying means;
A firmware management apparatus comprising:   For the current firmware, it further comprises an average number calculating means for calculating an average number of errors from when the current firmware is updated until a predetermined period elapses, and the comparing means is calculated by the average number calculating means instead of the number of errors. 2. The firmware management apparatus according to claim 1, wherein the average number of errors of the current firmware that has been used is compared with the average number of errors that occurred when the version of firmware used in the past was executed by the electronic device. .   Based on the comparison result by the comparison unit, the specifying unit determines that the version of the firmware having the average number of errors smaller than the average number of errors of the current firmware is a version suitable for the use. The firmware management apparatus according to claim 2, wherein the firmware management apparatus is specified.   When the ratio of the average number of errors of the current firmware to the average number of errors of the firmware of the version used in the past that is the comparison target is equal to or greater than a predetermined ratio, based on the comparison result by the comparison unit The firmware management apparatus according to claim 2, wherein a corresponding version of firmware is identified as a version suitable for the use.   The firmware management apparatus according to claim 1, wherein the error is a system error. The error corresponds to a system error and a normal error which is another error,
The counting means has means for counting the number of system errors and the number of normal errors, respectively, as the number of errors,
The average number calculating means includes means for calculating an average system error number and an average normal error number as the average error number, respectively.
The comparison means includes means for performing comparison based on each of an average system error number and an average normal error number as an average error number,
Based on the comparison result by the comparison unit, the specifying unit is configured such that a ratio of the average system error number of the current firmware to the average system error number of the firmware of the version used in the past that is a comparison target is equal to or more than a first predetermined ratio And the ratio of the average normal error number of the current firmware to the average normal error number of the firmware of the version used in the past that is the comparison target is equal to or less than the second predetermined ratio. The firmware management apparatus according to claim 2, wherein a version of firmware to be specified is specified as a version suitable for the use.   7. The firmware management apparatus according to claim 1, wherein the comparison unit excludes a version of firmware having a used period shorter than a predetermined period from comparison targets. 8.   The firmware management apparatus according to any one of claims 1 to 7, further comprising means for designating a version to be specified by the specifying means. A firmware management program for managing firmware of an electronic device stored in rewritable non-volatile storage means, which is current firmware that is currently used,
Counting the number of errors that occurred when the current firmware was executed by the electronic device, and storing and storing in the storage means of the electronic device,
A comparison step in which the number of errors of the current firmware counted in the counting step and the number of errors generated when the version of firmware used in the past is executed by the electronic device are read from the storage unit and compared;
Based on the comparison result in the comparison step, a specific step of identifying a firmware version suitable for use compared to the current firmware out of the firmware versions used in the past;
Changing the current firmware stored in the non-volatile storage means to the version of the firmware identified in the identifying step;
A firmware management program comprising:   For the current firmware, the method further includes an average number calculating step for calculating an average number of errors from when the current firmware is updated until a predetermined period elapses, and the comparing step is calculated in the average number calculating step instead of the number of errors. 10. The firmware management program according to claim 9, wherein the average number of errors of the current firmware that has been used is compared with the average number of errors that occurred when the version of firmware used in the past was executed by the electronic device. .   In the specific step, when there is a version of firmware having an average error number smaller than the average error number of the current firmware based on the comparison result in the comparison step, the version of the firmware suitable for the use is used. The firmware management program according to claim 10, characterized by:   In the specific step, the ratio of the average error number of the current firmware to the average error number of the firmware of the version used in the past that is the comparison target is greater than or equal to a predetermined ratio based on the comparison result in the comparison step. The firmware management program according to claim 10, wherein a corresponding version of firmware is identified as a version suitable for the use.   The firmware management program according to claim 9, wherein the error is a system error. The error corresponds to a system error and a normal error which is another error,
The counting step includes a step of counting the number of system errors as the number of errors, and a step of counting the number of normal errors as the number of errors,
The average number calculating step includes calculating an average system error number as an average error number, and calculating an average normal error number as an average error number,
The comparison step includes performing a comparison based on an average system error number as an average error number, and performing a comparison based on an average normal error number as an average error number,
In the specifying step, based on the comparison result in the comparison step, a ratio of the average system error number of the current firmware to the average system error number of the firmware of the version used in the past as a comparison target is a first predetermined ratio. And when the ratio of the average normal error number of the current firmware to the average normal error number of the firmware of the version used in the past that is the comparison target is equal to or less than the second predetermined ratio, The firmware management program according to claim 10, wherein a corresponding version of firmware is identified as a version suitable for the use.   15. The firmware management program according to claim 9, wherein the comparison step excludes a version of firmware having a used period shorter than a predetermined period from a comparison target.   The firmware management program according to any one of claims 9 to 15, further comprising a step of designating a version to be specified in advance in the specifying step.   The firmware management program according to claim 9, wherein the firmware management program is included as part of the firmware.   An electronic apparatus comprising the firmware management apparatus according to claim 1.   An electronic device comprising the firmware management program according to claim 9 stored in an executable manner.   The computer-readable recording medium which recorded the firmware management program of any one of Claim 9 thru | or 17. A firmware management method for managing firmware of an electronic device stored in rewritable non-volatile storage means, which is firmware currently being used,
Counting the number of errors that occurred when the current firmware was executed by the electronic device, and storing and storing in the storage means of the electronic device,
A comparison step in which the number of errors of the current firmware counted in the counting step and the number of errors generated when the version of firmware used in the past is executed by the electronic device are read from the storage unit and compared;
Based on the comparison result in the comparison step, a specific step of identifying a firmware version suitable for use compared to the current firmware out of the firmware versions used in the past;
Changing the current firmware stored in the non-volatile storage means to the version of the firmware identified in the identifying step;
A firmware management method comprising:

Images