JP2018136608A - Firmware execution device, driver execution device, driver management device, firmware management device, computer apparatus, method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To avoid a malfunction caused by update of a firmware or a driver.SOLUTION: A firmware execution device comprises: a combination information storage unit 101 which stores a combination information including dependence relationship information representing a dependence relationship between versions of a function module and a driver of a firmware; a driver version storage unit 102 which stores a version of a current driver; a firmware storage unit 103 which stores function modules each usable for each version of the driver; a dependence relationship determination unit 104 which determines whether or not there is a mismatch of the dependence relationship between the versions of the current firmware and the current driver at the time of starting, and whether or not the mismatch is solved by update of the firmware; and a firmware update unit 105 and a function module selection unit 106, one of which functions according to the determination result.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a technique for updating firmware.

  In recent years, firmware for controlling the hardware of a computer device has been required to have higher functions, reliability, and completeness. The reason for this is that control programs incorporated in firmware have become more sophisticated and complex in order to improve operability and reliability. Another reason is that attacks using security vulnerabilities at the firmware level have come to be seen. Under such circumstances, the firmware is frequently updated for function enhancement, security improvement, or defect correction.

  In general, unlike the update of the upper software, the firmware has a high possibility that the computer apparatus will not start if the update fails. For this reason, measures such as duplicating firmware, operation by skilled maintenance personnel, and returning to the factory for repair have been made. However, these measures are costly. In recent years, as computer systems become clouded, server devices and the like have been integrated into data centers. In this case, even when there is a problem in the firmware update of the server device in the data center, it is difficult to obtain an opportunity for maintenance. Against this background, there is a need for a technique for inexpensively and safely updating firmware.

  Here, the firmware version may have a dependency relationship with the version of the device driver. The device driver is a program that controls a hardware device connected to the inside or outside of the computer apparatus. The firmware runs on power up before the operating system starts, while the device driver runs on the operating system. Hereinafter, the device driver is also simply referred to as a driver. In this case, if the correct version combination of the firmware and driver is not updated in the correct order, a problem may occur in the operation.

  In order to cope with such a problem, it is conceivable to control the update order of firmware and drivers by an update tool operating on the operating system. However, the firmware can be updated by other methods without using such an update tool. For example, the firmware can be updated to firmware acquired from a portable storage medium or an out-of-band management network during POST (Power On Self Test). As described above, in consideration of the possibility of selecting an update method other than the update tool in maintenance work or the like, it is difficult to ensure that the update order of the driver and the firmware is appropriately performed appropriately.

  If the driver and firmware are updated in an inappropriate combination of versions or in an inappropriate order, a user operation solution or firmware downgrade is required. However, downgrading firmware that has been updated once is often difficult from a security standpoint and cannot be easily recovered.

  A technique related to such a problem is described in Patent Document 1. The related technology described in Patent Document 1 stores, in a printer, the version of the printer driver that created the print data together with the print data to be accumulated. In this related technology, when the firmware is upgraded, the version of the printer driver that creates print data that can correctly print the new version of the firmware is acquired. This related technology saves the old version of the firmware corresponding to the print data when there is a print driver version that has been created and the new version of the firmware cannot be printed correctly. .

JP 2006-107251 A

  However, the related technique described in Patent Document 1 has the following problems. In this related technique, it is necessary to save an old version of firmware in order to avoid a malfunction due to an inappropriate combination of versions accompanying firmware or driver updates. As a result, resources are needed to store all the necessary old versions of firmware.

  The present invention has been made to solve the above-described problems. In other words, an object of the present invention is to provide a technique for more reliably avoiding problems caused by firmware or driver updates while suppressing an increase in the amount of necessary resources.

  The firmware execution apparatus according to the present invention is a combination of a version of a function module included in each version of firmware installed in a computer apparatus and a version of a driver that controls a hardware device connected to the inside or outside of the computer apparatus. A combination information storage means for storing combination information including dependency relation information representing dependency relations between versions, and a driver version storage means for storing information indicating the version of the current driver currently installed in the computer device In addition to the function module of the version originally included in the current firmware version currently installed in the computer device, each bar of the driver for the function module having a dependency relationship with the version of the driver There is a mismatch in dependency between the firmware storage means for storing the functional module of the version usable by the application and the current firmware version and the current driver version when the computer apparatus is started up Whether or not, and if there is a mismatch, whether or not the mismatch is resolved by updating the firmware by referring to the combination information, and the dependency determination If it is determined by the means that the inconsistency is resolved by updating the firmware, a version of firmware that eliminates the inconsistency is acquired, the firmware storage means is updated, and then the computer apparatus is restarted The firmware update unit and the dependency relationship determination unit When it is determined that there is no inconsistency, the function module of the version originally included in the current firmware is selected and executed, and when it is determined that the inconsistency is not resolved by the firmware update, Function module selection means for selecting and executing a function module of a version that can be used depending on the version of the driver.

  The driver execution device of the present invention registers error information in the combination information storage unit of the firmware execution device when an operation error is detected when the driver is executed in the computer device including the firmware execution device described above. Error information registration means is provided.

In addition, the driver management apparatus of the present invention includes a driver update unit that updates the driver mounted on the computer device including the firmware execution device described above,
Information updating means for updating the information representing the version of the current driver stored in the driver version storage means in the firmware execution device to information representing the version updated by the driver updating means.

  The firmware management apparatus according to the present invention further includes combination information update means for updating the combination information stored in the combination information storage means in the firmware execution apparatus described above.

  The computer device of the present invention includes the above-described firmware execution device, and the firmware executed by the firmware execution device is mounted thereon.

  The method of the present invention also includes a driver for controlling a version of a functional module included in each version of firmware installed in the computer apparatus and a hardware device connected to the inside or outside of the computer apparatus. Combination information storage means for storing combination information including dependency relationship information representing dependency relationships between versions, and information indicating the version of the current driver currently installed in the computer device. In addition to the function module of the version originally included in the version of the current firmware currently installed in the computer apparatus and the driver version storage means, the driver module stores the driver module for the function module having a dependency relationship with the version of the driver. Firmware storage means for storing functional modules of a version usable by each version of the driver, and a dependency relationship between the current firmware version and the current driver version when the computer device is started Whether or not there is an inconsistency and whether or not the inconsistency is resolved by updating the firmware when there is an inconsistency, by referring to the combination information, and updating the firmware If it is determined that the inconsistency is resolved, after obtaining the version of firmware that resolves the inconsistency and updating the firmware storage means, the computer apparatus is restarted and it is determined that there is no inconsistency The function module of the version originally included in the current firmware. Select Yuru running, when the inconsistency update of the firmware is determined not to be eliminated, selects and executes the function module of the available versions depending on the version of the current driver.

  Further, the program of the present invention is a combination of a version of a function module included in each version of firmware installed in a computer device and a version of a driver that controls a hardware device connected to the inside or outside of the computer device. A combination information storage means for storing combination information including dependency relation information representing dependency relations between versions, and a driver version storage means for storing information indicating the version of the current driver currently installed in the computer device In addition to the function module of the version originally included in the current firmware version currently installed in the computer apparatus, each version of the driver for the function module having a dependency relationship with the version of the driver Thus, using the firmware storage means for storing the available version of the functional module, there is a mismatch in dependency between the current firmware version and the current driver version when the computer apparatus is started. A dependency relationship determining step of determining whether there is a mismatch and whether the mismatch is eliminated by updating the firmware when there is a mismatch, and the dependency relationship; If it is determined by the determination step that the inconsistency is resolved by updating the firmware, the version of firmware that eliminates the inconsistency is acquired and the firmware storage unit is updated, and then the computer apparatus is restarted Firmware updating step and the dependency determination step If it is determined that there is no inconsistency, the function module of the version originally included in the current firmware is selected and executed, and it is determined that the inconsistency is not eliminated by updating the firmware. A function module selection step of selecting and executing a function module of an available version according to the version of the current driver.

  The present invention can provide a technique for more reliably avoiding problems caused by firmware or driver updates while suppressing an increase in the amount of necessary resources.

It is a figure which shows the functional block structure of the firmware execution apparatus as the 1st Embodiment of this invention. It is a figure which shows an example of the hardware constitutions of the firmware execution apparatus as the 1st Embodiment of this invention. It is a figure which shows typically the functional module memorize | stored in the firmware memory | storage part in the 1st Embodiment of this invention. It is a flowchart explaining operation | movement of the firmware execution apparatus as the 1st Embodiment of this invention. It is a figure which shows the functional block structure of the firmware execution apparatus as the 2nd Embodiment of this invention. It is a flowchart explaining operation | movement of the firmware execution apparatus as the 2nd Embodiment of this invention. It is a figure which shows the combination information in the specific example of the 2nd Embodiment of this invention. It is a figure which shows the combination information in the other specific example of the 2nd Embodiment of this invention. It is a figure which shows the functional block structure of the firmware execution apparatus as the 3rd Embodiment of this invention. It is a flowchart explaining operation | movement of the firmware execution apparatus as the 3rd Embodiment of this invention. It is a figure which shows the functional block structure of the firmware execution apparatus as the 4th Embodiment of this invention. It is a figure which shows typically the functional module memorize | stored in the firmware memory | storage part in the 4th Embodiment of this invention. It is a flowchart explaining operation | movement of the firmware execution apparatus as the 4th Embodiment of this invention. It is a figure which shows the functional block structure of the firmware management apparatus as the 5th Embodiment of this invention. It is a flowchart explaining the operation | movement of the firmware management apparatus as the 5th Embodiment of this invention. It is a flowchart explaining the specific example of operation | movement of the firmware management apparatus as the 5th Embodiment of this invention. It is a figure which shows the functional block structure of the driver execution apparatus as the 6th Embodiment of this invention. It is a flowchart explaining operation | movement of the driver execution apparatus as the 6th Embodiment of this invention. It is a figure which shows the functional block structure of the driver management apparatus as the 7th Embodiment of this invention. It is a flowchart explaining operation | movement of the driver management apparatus as the 7th Embodiment of this invention. It is a figure which shows the functional block structure of the driver management apparatus as the 8th Embodiment of this invention. It is a flowchart explaining the operation | movement of the driver management apparatus as the 8th Embodiment of this invention. It is a figure which shows the functional block structure of the computer apparatus as the 9th Embodiment of this invention.

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

(First embodiment)
First, the firmware execution device 100 according to the first embodiment of the present invention will be described. The firmware execution device 100 is a device that executes firmware installed in a computer device. A functional block configuration of the firmware execution apparatus 100 is shown in FIG. In FIG. 1, a firmware execution apparatus 100 includes a combination information storage unit 101, a driver version storage unit 102, a firmware storage unit 103, a dependency relationship determination unit 104, a firmware update unit 105, and a functional module selection unit 106. Prepare.

  An example of the hardware configuration of the firmware execution apparatus 100 is shown in FIG. The firmware execution device 100 is configured by a computer device including a CPU (Central Processing Unit) 1001, a memory 1002, a network interface 1003, a management processor 1004, and a management network interface 1005. Further, the computer device constituting the firmware execution device 100 includes an output device 1006 and an input device 1007. In addition, the computer apparatus constituting the firmware execution apparatus 100 includes a hardware device 1008. Alternatively, the hardware device 1008 may be connected to the outside of the computer apparatus that constitutes the firmware execution apparatus 100.

  The memory 1002 includes a RAM (Random Access Memory), a ROM (Read Only Memory), an auxiliary storage device (such as a hard disk), and the like. The memory 1002 stores firmware that causes the computer apparatus to operate as the firmware execution apparatus 100. In addition, the memory 1002 stores programs such as an operating system and device drivers.

  The CPU 1001 reads and executes a program stored in the memory 1002 and controls other units.

  The network interface 1003 is an interface connected to the network.

  The management network interface 1005 is an interface connected to a network for out-of-band management.

  The management processor 1004 communicates with an external management server or the like via the management network interface 1005 and controls other units.

  In this case, the combination information storage unit 101, the driver version storage unit 102, and the firmware storage unit 103 are configured by the memory 1002. The dependency relationship determination unit 104 and the functional module selection unit 106 are configured by a CPU 1001 that reads and executes a program stored in the memory 1002. The firmware update unit 105 includes a CPU 1001 that executes a program stored in the memory 1002, a management processor 1004, and a management network interface 1005.

  Note that the hardware configuration of the firmware execution apparatus 100 and its functional blocks is not limited to the above-described configuration.

  Next, details of each functional block of the firmware execution apparatus 100 will be described.

  The combination information storage unit 101 stores combination information. The combination information includes dependency information.

  The dependency relationship information is information representing a dependency relationship between versions in a combination of a function module version and a driver version included in each firmware version. The firmware referred to here is firmware installed in a computer device, and is also called BIOS (Basic Input Output System). The driver here is software that operates on the operating system of the computer apparatus and controls the hardware device 1008 connected to the inside or outside of the computer apparatus. Specifically, the dependency relationship information represents the version of a driver that can use the function module of the version with respect to the version of the function module included in each version of the firmware.

  The driver version storage unit 102 stores information indicating the version of the current driver currently installed in the computer device.

  The firmware storage unit 103 stores the version of the functional module originally included in the current firmware currently installed in the computer apparatus. In addition, the firmware storage unit 103 stores function modules that can be used by each version of the driver for the function modules having a dependency relationship with the driver version. In other words, in addition to the function module of the version originally included in the current firmware, the function module usable by each version of the driver older than the driver that can use the function module of the version is stored in the firmware storage unit 103. The

  For example, an example of information stored in the firmware storage unit 103 is shown in FIG. In the example of FIG. 3, the firmware includes functional modules A, B, and C. Further, it is assumed that the functional modules A and B have a dependency relationship with the driver version. Further, it is assumed that the functional module C has no dependency relationship with the driver version. Each version of the functional module “X” is represented as a functional module Xn (n is a character string representing a numerical value). Further, the function module Xn represents that the larger the n, the newer the version.

  In this case, in FIG. 3, the firmware storage unit 103 stores functional modules A3, B2, and C1 as functional modules originally included in the current version of firmware. For the function module A, a function module A2 and a function module A1 that can be used by drivers of versions older than the driver that can use the function module A3 are stored. Similarly, for the function module B, the function module B1 that can be used by each version of the driver older than the driver that can use the function module B2 is stored.

  The dependency relationship determination unit 104 determines whether or not there is a dependency mismatch between the current firmware version and the current driver version by referring to the combination information when the computer apparatus is started. . In addition, when there is a mismatch in the dependency relationship between the current firmware version and the current driver version, the dependency relationship determination unit 104 determines whether or not the mismatch is resolved by the firmware update. This is determined by referring to the information storage unit 101.

  Specifically, in the combination information, it is assumed that the version of the driver that can use the function module version originally included in the current firmware does not match the version of the current driver. In this case, there is a mismatch in the dependency between the current firmware version and the current driver version.

  In this case, it is further assumed that the function module version available according to the current driver version is newer than the function module version originally included in the current firmware. That is, the driver is updated before the firmware. In this case, the inconsistency of the dependency relationship is resolved by updating the firmware.

  On the other hand, it is assumed that the version of the function module originally included in the current firmware is newer than the version of firmware that can be used depending on the version of the current driver. That is, the firmware is updated before the driver. In this case, even if the firmware is updated, the inconsistency of the dependency relationship is not resolved.

  When the dependency determination unit 104 determines that the inconsistency is resolved by updating the firmware, the firmware update unit 105 acquires a version of firmware that eliminates the inconsistency. For example, the firmware update unit 105 may acquire a version of firmware that eliminates inconsistencies from a management server connected via a management network. Alternatively, the firmware update unit 105 may acquire the storage position of the version firmware that eliminates the inconsistency via the input device 1007, and may acquire the corresponding firmware from the location indicated by the storage position.

  Here, it is assumed that the firmware acquired by the firmware update unit 105 includes a function module of a version that can be used by each version of the driver as described above, in addition to the function module originally included in the version of the corresponding firmware.

  That is, the acquired firmware includes a plurality of functional modules with respect to the functional modules having a dependency relationship between the versions of the driver.

  Also, the firmware update unit 105 updates the current firmware by writing the functional module included in the firmware of the version that eliminates such inconsistency into the firmware storage unit 103.

  Also, the firmware update unit 105 restarts the computer apparatus after updating the firmware storage unit 103.

  When the dependency determination unit 104 determines that there is no dependency mismatch, the function module selection unit 106 selects and executes the function module of the version originally included in the current firmware from the firmware storage unit 103. To do. Also, the function module selection unit 106 selects a function module of a version that can be used according to the current driver version from the firmware storage unit 103 when it is determined that the inconsistency of the dependency relationship is not eliminated by the firmware update. And execute.

  The operation of the firmware execution apparatus 100 configured as described above will be described with reference to FIG. The following operation is started when the computer apparatus is activated.

  First, the dependency relationship determination unit 104 reads combination information from the combination information storage unit 101 (step S101).

  Next, the dependency relationship determination unit 104 reads information representing the current driver version from the driver version storage unit 102 (step S102).

  Next, the dependency relationship determination unit 104 acquires information representing the version based on the current firmware stored in the firmware storage unit 103 (step S103).

  Next, the dependency relationship determination unit 104 determines whether or not there is a dependency mismatch between the current firmware version and the current device driver version by referring to the combination information (Step S1). S104).

  If it is determined that there is no inconsistency (No in step S104), the functional module selection unit 106 selects a version of the functional module originally included in the current firmware (step S105).

  On the other hand, when it is determined that there is inconsistency (Yes in step S104), the dependency relationship determination unit 104 determines whether the inconsistency is resolved by updating the firmware (step S106).

  If it is determined that the inconsistency is resolved by updating the firmware (Yes in step S106), the firmware update unit 105 acquires a version of firmware that eliminates the inconsistency (step S107).

  As described above, the acquired firmware includes a function module of a version that can be used by each older version of the driver in addition to the function module of the version originally included in the firmware of that version.

  Next, the firmware update unit 105 updates the firmware by writing the functional module included in the acquired firmware into the firmware storage unit 103 (step S108).

  Then, the firmware update unit 105 restarts the computer device (step S109). Thereby, the operation of the firmware execution apparatus 100 is repeated from step S101 after the restart. Then, since the firmware is updated and the inconsistency of the dependency relationship is resolved, No is obtained in step S104. Thereafter, step S105 is executed, and the function module of the version originally included in the current firmware is selected.

  On the other hand, if it is determined that the inconsistency is not eliminated by the firmware update (No in step S106), the functional module selection unit 106 selects a functional module of a usable version according to the current driver version (step S110). .

  Thereafter, the firmware execution apparatus 100 executes the functional module selected in step S105 or step S110.

  Next, effects of the first exemplary embodiment of the present invention will be described.

  The firmware execution device according to the first exemplary embodiment of the present invention can more reliably avoid problems due to firmware or driver updates while suppressing an increase in the amount of necessary resources.

  The reason will be described. In the present embodiment, the combination information storage unit stores combination information including dependency relationship information. The dependency relationship information is information representing a dependency relationship between versions of a combination of a function module version and a driver version included in each firmware version. The driver version storage unit stores information representing the current driver version. Also, the firmware storage unit stores functional modules that can be used by each version of the driver for functional modules having a dependency relationship with the driver version, in addition to the functional modules originally included in the current firmware. .

  Then, at the time of starting the computer device, the dependency determination unit determines whether there is a dependency mismatch between the current firmware version and the current driver version, and if there is a mismatch, updates the firmware. Determine whether the inconsistency is resolved. If the inconsistency is resolved by the firmware update, the firmware update unit updates the current firmware and restarts the computer apparatus. When there is no dependency mismatch between versions, the function module selection unit selects and executes the function module of the version originally included in the current firmware. In addition, when the inconsistency is not resolved by updating the firmware, the function module selection unit selects and executes a function module of a version that can be used according to the current driver version.

  In other words, in the present embodiment, when the inconsistency in the dependency relationship between versions is resolved by updating the firmware, the inconsistency is resolved by updating the firmware and restarting. In addition, even if the inconsistency in the dependency relationship between versions is not resolved by updating the firmware, this embodiment does not downgrade the entire firmware, but downgrades only a part of the functional modules, thereby causing inconsistency. Is solved.

  In this way, this embodiment eliminates inconsistencies by updating the firmware itself or downgrading only some functional modules, regardless of which firmware or driver is updated first. To do. As a result, according to the present embodiment, the operating system is not operated in a state where a problem occurs when updating the firmware or the driver.

  Furthermore, the related technology described in Patent Document 1 described in the background art downgrades the entire firmware in order to eliminate the inconsistency of the dependency relationship with the driver version. For this reason, the related technique described in Patent Document 1 requires a sufficient resource for storing the entire firmware of the previous version. On the other hand, in this embodiment, it is not necessary to save all of the necessary old version firmware, and it is only necessary to save the old version in units of necessary function modules. An increase in capacity required as a part can be suppressed.

(Second Embodiment)
Next, a firmware device according to a second embodiment of the present invention will be described in detail with reference to the drawings. In the present embodiment, in the same way as in the first embodiment of the present invention, inconsistencies between firmware and driver versions are resolved, and further, problems caused by setting changes accompanying firmware or driver updates are eliminated. The firmware device to be eliminated will be described.

  Here, a problem caused by a setting change accompanying firmware or driver update will be described. When the firmware or its driver is updated, the firmware parameters may be changed by the user for the purpose of eliminating problems and improving performance. In this case, even if the firmware and the driver are updated in consideration of the combination of versions and the update order, a new problem may occur due to the firmware parameters changed in the user environment.

  For example, it is assumed that a DAC (Disk Array Controller) connected to a computer device by PCI (Peripheral Component Interconnect) does not operate normally unless the PCI link speed is limited on the firmware side due to a driver malfunction. In this case, it is necessary to change the DAC driver to a value that maximizes the performance of the PCI link speed setting on the firmware side at the same time that the driver is updated to a version that does not have a defect that matches the firmware version. At this time, even if the update is performed in consideration of the combination of firmware and driver versions and the update order, a new problem may occur due to the setting of the PCI link speed.

  In the present embodiment, a function that is added in order to solve a problem caused by a setting change associated with firmware or driver update will be described.

  First, FIG. 5 shows a functional block configuration of a firmware execution apparatus 120 as a second embodiment of the present invention. In FIG. 5, the firmware execution device 120 is different from the firmware execution device 100 according to the first exemplary embodiment of the present invention in that it includes a combination information storage unit 121 instead of the combination information storage unit 101. Further, the difference is that a firmware storage unit 123 is provided instead of the firmware storage unit 103. Furthermore, the point provided with the parameter setting part 127 differs.

  Here, the firmware execution device 120 and each functional block thereof can be configured by hardware elements similar to those of the first embodiment of the present invention described with reference to FIG. In this case, the parameter setting unit 127 is configured by the CPU 1001 that reads and executes a program stored in the memory 1002. However, the hardware configuration of the firmware execution device 120 and each functional block thereof is not limited to the above-described configuration.

  Next, among the functional blocks of the firmware execution device 120, the details of each functional block different from the first embodiment of the present invention will be described.

  The combination information storage unit 121 stores setting value information, error information, and priority information, in addition to the dependency information similar to that in the first embodiment of the present invention, for the combination of the function module version and the driver version. The included combination information is stored.

  The set value information represents each set value set that can be set in one or more parameters of the firmware in the combination.

  The error information represents the presence or absence of an operation error in the computer device when the set value information is applied in the combination.

  The priority information represents the priority of the set value information in the combination.

  Such combination information may be provided in advance by a driver or firmware vendor, for example. Specifically, it is assumed that a problem occurs in a combination of a certain driver version and a functional module version, and a parameter setting value that can avoid such a problem may be provided in advance by the vendor. For example, it is assumed that there is a dependency between the function module version included in the firmware and the driver version for the function of software RAID (Redundant Arrays of Inexpensive Disks). At this time, the problem may be avoided by changing the link speed of the PCI connecting the storage to be controlled, changing the hardware interrupt interval, or invalidating the power saving control function of the storage. In such a case, for a combination of a functional module version and a driver version that may cause a failure, a set of setting values such as PCI link speed, hardware interrupt interval, storage power saving control function, etc. Or a vendor. When one or more sets of setting value information are provided for the same combination, priority information indicating the priority of each setting value may be further provided. Further, when the presence / absence of an operation error has been verified for each set value information, error information may be provided.

  The firmware storage unit 123 stores firmware parameter setting values in addition to the same information as the firmware storage unit 103 according to the first embodiment of the present invention.

  Based on the combination information, the parameter setting unit 127 sets, as a firmware parameter, a setting value with no operation error in the combination of the function module version selected by the function module selection unit 106 and the current driver version. That is, the parameter setting unit 127 updates the setting value stored in the firmware storage unit 123 using such a setting value. If there is one or more sets of setting value information indicating a setting value with no operation error in the corresponding combination, the parameter setting unit 127 sets the setting value selected based on the priority as a firmware parameter.

  Note that the setting value without (or having) an operation error refers to the setting value indicated by the setting value information associated with error information indicating that there is no (or having) an operation error in the combination information regarding a certain combination. To do. Further, the setting value selected based on the priority may be, for example, a setting value indicated by setting value information associated with priority information indicating that the priority is the highest in the combination information regarding a certain combination.

  Note that there may be a case where the set value information is not included in the combination information regarding the corresponding combination. In this case, the parameter setting unit 127 may omit the process of setting the setting value. Alternatively, in this case, the parameter setting unit 127 may set an arbitrary setting value as a parameter. For example, such an arbitrary set value may be a value input via the input device 1007.

  In addition, there may be a case where the set value information is included in the combination information regarding the corresponding combination, but the error information is not associated. In this case, the parameter setting unit 127 may regard the setting value information not associated with error information as a candidate for selection by regarding that there is no operation error.

  Further, a case is considered in which error information indicating that there is an operation error is registered in the combination information regarding the corresponding combination, but error information indicating that there is no operation error is not registered. In this case, the parameter setting unit 127 may set an arbitrary setting value other than the setting value having an operation error as the parameter. For example, such an arbitrary setting value may be another setting value input via the input device 1007 by indicating a setting value having an operation error with respect to the output device 1006.

  Further, although one or more sets of setting value information with no operation error are registered in the combination information related to the corresponding combination, there may be a case where priority information is not registered. In this case, the parameter setting unit 127 may select any one of such setting value information and set it as a parameter.

  The operation of the firmware execution apparatus 120 configured as described above will be described with reference to FIG.

  In FIG. 6, the firmware execution device 120 operates in the same manner as in the first embodiment of the present invention from step S101 to S110. As a result, when there is no inconsistency in the dependency relationship between the current firmware and the current driver version, the firmware execution apparatus 120 selects the function module of the version originally included in the current firmware. Also, the firmware execution device 120 has a dependency mismatch between the current firmware and the current driver version. If the mismatch is resolved by the firmware update, the firmware execution device 120 updates the firmware and restarts the computer device. to start. After the restart, the firmware execution device 120 determines that there is no dependency mismatch between the updated current firmware and the current driver version. Therefore, the firmware execution device 120 selects the function module of the version originally included in the updated current firmware. Also, if the inconsistency is not resolved by updating the firmware, the firmware execution device 120 selects a function module of a usable version according to the current driver version.

  Next, the parameter setting unit 127 determines whether or not error information indicating that there is an operation error is registered for the combination of the selected function module version and the current driver version (step S121).

  Here, a case where error information indicating that there is an operation error is not registered (No in step S121) will be described. In this case, the parameter setting unit 127 sets the setting value selected based on the priority as a parameter (step S122).

  On the other hand, a case where error information indicating that there is an operation error is registered (Yes in step S121) will be described. In this case, the parameter setting unit 127 sets, as a parameter, a setting value selected based on the priority from the setting values with no operation error (step S123).

  As described above, the parameter setting unit 127 regards setting value information not associated with error information as indicating a setting value without an operation error. Further, when there is no set value with no operation error, the parameter setting unit 127 may apply a set value or the like input from the input device 1007.

  Thereafter, the firmware execution device 120 executes the functional module selected in step S105 or step S110, and operates using the parameters set in step S122 or S123.

  Next, the operation of the firmware execution apparatus 120 will be described using three specific examples. In these specific examples, the firmware version is represented by a or b, and b is newer than a. Further, it is assumed that the firmware includes a functional module A having a dependency relationship with the driver version. The version of the function module A is assumed to be A2 newer than A1. The driver version is 1.0 or 2.0, and 2.0 is newer than 1.0. In addition, the priority is represented by an integer such as 1, 2, and the smaller the value, the higher the priority.

<Specific example 1>
Here, a specific example in the case where there is no dependency relationship between the firmware version and the driver version in any combination will be described.

  First, it is assumed that the current firmware is version a.

  Further, it is assumed that the driver version storage unit 102 stores “2.0” as the current driver version. That is, the current driver is version 2.0.

  Further, it is assumed that the combination information storage unit 121 stores combination information as shown in FIG. In FIG. 7, numbers are described in the column of the item “No” for explanation. Hereinafter, the combination information of the row in which the number “x” is described is also referred to as “No. x combination information”. No. shown in FIG. 1-No. The combination information 2 indicates that there is no dependency between versions in any combination of any version of the functional module included in the firmware version and any version of the driver.

  No. The combination information 1 indicates that “Disabled” can be set as the parameter X and “Enabled” can be set as the parameter Y. No. The combination information 1 indicates that priority 1 is set for these setting values. No. The combination information 1 indicates that error information is not registered for these setting values.

  No. The combination information 2 represents that “Disabled” can be set as the parameter X and “Disabled” can be set as the parameter Y. No. The combination information 2 indicates that priority 2 is set for these setting values. No. The combination information 2 indicates that error information indicating the presence or absence of an operation error is not registered for these setting values.

  In this case, first, in the firmware execution apparatus 120, at the time of activation, the dependency relationship determination unit 104 reads the combination information of FIG. 7 from the combination information storage unit 121 (step S101).

  Next, the dependency relationship determination unit 104 determines that there is no dependency mismatch between the current firmware version a and the current driver version 2.0 (No in steps S102 to S103 and S104). ).

  Therefore, the functional module selection unit 106 selects a functional module whose version is originally included in the current firmware (step S105).

  Next, the parameter setting unit 127 determines that error information indicating that there is an error is not registered for the combination of the selected functional module version and the current driver version (No in step S121). .

  Therefore, the parameter setting unit 127 sets the No. 1 in which “1” having the highest priority is set. Based on the combination information of 1, the parameter X is set to “Disabled” and the parameter Y is set to “Enabled” (step S122).

  Then, the firmware execution device 120 executes the selected functional module and operates with the set parameters.

<Specific example 2>
Here, a specific example in which the computer apparatus is activated in a situation where the driver is updated prior to the firmware will be described.

  First, it is assumed that the current firmware is version a.

  Further, it is assumed that the driver version storage unit 102 stores “2.0” as the current driver version. That is, the current driver is version 2.0.

  Further, it is assumed that the combination information storage unit 121 stores combination information as shown in FIG.

  For example, in FIG. , The dependency relationship information included in the combination information of version 1 is the version 1. This indicates that the driver x is necessary. Here, x is an arbitrary numerical value. Further, the dependency relationship information is based on the function module A1 originally included in the firmware version a, and the version 1. It also shows that x drivers are required. No. 1 includes the function module A1 and the driver version 1. In the combination of x, “Disabled” can be set as the parameter X and “Enabled” can be set as the parameter Y. No. The error information included in the combination information 1 indicates that there is no operation error for the corresponding set value. No. The priority information included in the combination information 1 indicates that priority 1 is set for the corresponding setting value.

  In addition, in FIG. 2-No. The combination information 5 indicates that the version A1 and A2 of the function module A are included in the firmware version b. It is assumed that the version of the functional module A originally included in the firmware version b is A2. In addition, No. 2-No. The dependency relationship information, the set value information, the error information, and the priority information included in each combination information of No. 5 are as illustrated, and detailed description thereof is omitted.

  In this case, first, in the firmware execution apparatus 120, at the time of activation, the dependency relationship determination unit 104 reads the combination information of FIG. 8 from the combination information storage unit 121 (step S101).

  Here, no. 1, the version of the driver that can use the current firmware version a is the version of the driver that can use the function module A1 that is originally included. x. However, the current driver is version 2.0.

  Therefore, the dependency relationship determination unit 104 determines that there is a dependency mismatch between the current firmware version a and the current driver version 2.0 (Yes in steps S102 to S103 and S104). .

  Furthermore, no. 4-No. Referring to the combination information of 5, the firmware that originally includes the functional module A2 having no dependency mismatch with the current driver version 2.0 is version b. The firmware version b is newer than the current version a.

  Therefore, the dependency relationship determination unit 104 determines that the inconsistency is resolved by updating the firmware (Yes in step S106).

  Therefore, the firmware update unit 105 acquires version b firmware that resolves the inconsistency (step S107), and updates the firmware (step S108). That is, the firmware update unit 105 writes the functional modules A1 and A2 included in the acquired firmware in the firmware storage unit 123. Then, the firmware update unit 105 restarts the computer device (step S109).

  In the restarted computer apparatus, the dependency relationship determination unit 104 determines that there is no dependency mismatch between the current firmware version b and the current driver version 2.0 based on the combination information. (No in steps S101 to S103 and S104).

  Therefore, the functional module selection unit 106 selects the functional module A2 originally included in the current firmware version b (step S105).

  Next, the parameter setting unit 127 determines that error information indicating that there is an error is not registered for the combination of the selected functional module A2 and the current driver version 2.0 (in step S121). No).

  Therefore, the parameter setting unit 127 sets the No. 1 in which “1” having the highest priority is set. Based on the combination information 4, “Enabled” is set as the parameter X and “Enabled” is set as the parameter Y.

  Then, the firmware execution device 120 executes the selected functional module A2 and operates with the set parameters.

<Specific example 3>
Here, a specific example in which the computer apparatus is activated in a situation where the firmware is updated before the driver will be described.

  First, assume that the current firmware is version b.

  Further, it is assumed that the driver version storage unit 102 stores “1.0” as the current driver version. That is, the current driver is version 1.0.

  Further, it is assumed that the combination information storage unit 121 stores the combination information illustrated in FIG.

  In this case, first, in the firmware execution apparatus 120, at the time of activation, the dependency relationship determination unit 104 reads the combination information of FIG. 8 from the combination information storage unit 121 (step S101).

  Here, no. 4-No. 5, the version of the driver that can use the current firmware version b is the version of the driver that can use the originally included function module A2. x. However, the current driver is version 1.0.

  Therefore, the dependency relationship determination unit 104 determines that there is a dependency mismatch between the current firmware version b and the current driver version 1.0 (Yes in step S104).

  No. Referring to the combination information of 1, the firmware that originally includes the functional module of the version having no inconsistency of dependency with the current driver version 1.0 is version a. The firmware version a is older than the current version b.

  Therefore, the dependency relationship determination unit 104 determines that the inconsistency is not eliminated even if the firmware is updated (No in step S106).

  Therefore, the functional module selection unit 106 selects a functional module A1 that can be used according to the current driver version 1.0 among a plurality of functional modules A included in the current firmware version b (step S110). .

  Next, the parameter setting unit 127 determines that error information indicating that there is an operation error is registered for the combination of the selected functional module A1 and the current driver version 1.0 (step S121). Yes).

  Therefore, the parameter setting unit 127 sets the No. 2 in which “2” having the highest priority is set among the setting values having no operation error. Based on the combination information of 3, “Disabled” is set as the parameter X and “Disabled” is set as the parameter Y (step S123).

  Then, the firmware execution device 120 executes the selected functional module A1 and operates with the set parameters.

  This is the end of the description of the specific example.

  Next, the effect of the second exemplary embodiment of the present invention will be described.

  The firmware execution device according to the second exemplary embodiment of the present invention more reliably avoids problems caused by parameter setting changes accompanying firmware or driver updates while suppressing an increase in the amount of necessary resources. Can do.

  The reason will be described. The second embodiment of the present invention has the following configuration in addition to the same configuration as the first embodiment of the present invention. That is, the combination information storage unit stores combination information including dependency relationship information, setting value information, error information, and priority information for each combination of functional module version and driver version. This is because the parameter setting unit sets, as a parameter, the setting value selected based on the priority among the setting values with no operation error in the combination of the selected functional module version and the current driver version. .

  As described above, according to the present embodiment, in the combination of the function module version and the current driver version selected so that there is no inconsistency in the dependency relationship, a setting value with no operation error is selected based on the priority and the parameter is selected. Set as. Therefore, this embodiment not only greatly reduces the possibility of causing problems due to parameter setting changes when updating firmware or drivers, but also sets more appropriate setting values as firmware parameters. Performance can be improved.

  In the specific example of the present embodiment, examples of combination information stored in the combination information storage unit are shown in FIGS. However, the structure and format of the combination information are not limited to those illustrated.

(Third embodiment)
Next, a firmware execution device 130 as a third exemplary embodiment of the present invention will be described in detail with reference to the drawings.

  First, the functional block configuration of the firmware execution apparatus 130 is shown in FIG. In FIG. 9, the firmware execution device 130 includes a combination information acquisition unit 138 in addition to the same configuration as that of the firmware execution device 120 according to the second embodiment of the present invention.

  Next, an example of the hardware configuration of the firmware execution device 130 will be described. The firmware execution device 130 can be configured by hardware elements similar to those of the first embodiment of the present invention described with reference to FIG. In this case, the combination information acquisition unit 138 includes a CPU 1001 that executes a program stored in the memory 1002, a management processor 1004, and a management network interface 1005. However, the hardware configuration of the firmware execution device 130 and each functional block thereof is not limited to the above-described configuration.

  Next, details of the functional blocks of the firmware execution apparatus 130 that are different from those of the second embodiment of the present invention will be described.

  The combination information acquisition unit 138 acquires combination information via the management network and writes the combination information in the combination information storage unit 121 when the computer apparatus is activated. The management network is available during the activation of the firmware in the computer device including the firmware execution device 130. For example, the combination information acquisition unit 138 may acquire combination information from a management server that operates on the management network.

  The operation of the firmware execution apparatus 130 configured as described above will be described with reference to FIG.

  In FIG. 10, first, the combination information acquisition unit 138 acquires combination information via the management network at the time of activation (step S131).

  Next, the combination information acquisition unit 138 writes the acquired combination information in the combination information storage unit 121 (step S132).

  At this time, the combination information acquisition unit 138 may overwrite the information stored in the combination information storage unit 121 using the acquired combination information. Alternatively, the combination information acquisition unit 138 may additionally write the acquired combination information.

  Thereafter, the firmware execution device 130 operates in the same manner as in the first and second embodiments of the present invention from step S101 to S110. Accordingly, the firmware is updated and restarted or a functional module is selected according to the determination result of the dependency relationship determination unit 104 regarding the dependency relationship between the firmware and the driver version.

  Then, the firmware execution apparatus 130 operates in the same manner as in the second embodiment of the present invention from step S121 to S123. Thus, parameters are set based on the error information and the priority information according to the combination of firmware and driver versions.

  Above, description of operation | movement of the firmware execution apparatus 130 is complete | finished.

  Next, effects of the third exemplary embodiment of the present invention will be described.

  The firmware execution apparatus according to the third embodiment of the present invention can more reliably avoid problems caused by updating the firmware or driver to an unknown version.

  The reason will be described. In the third embodiment of the present invention, in addition to the same configuration as that of the second embodiment of the present invention, the combination information acquisition unit acquires the combination information via the management network when the computer apparatus is started. To the combination information storage unit. Therefore, the latest combination information that can be acquired is stored in the combination information storage unit every time the computer apparatus is activated. In other words, the present embodiment operates based on the latest combination information, and the firmware or driver is not updated to an unknown version. As a result, the present embodiment can avoid the occurrence of dependency mismatch between unknown versions.

(Fourth embodiment)
Next, a firmware execution device 140 as a fourth exemplary embodiment of the present invention will be described in detail with reference to the drawings.

  First, the functional block configuration of the firmware execution apparatus 140 is shown in FIG. In FIG. 11, the firmware execution device 140 includes a functional module acquisition unit 149 in addition to the same configuration as the firmware execution device 130 according to the third embodiment of the present invention.

  In the present embodiment, the information included in the firmware acquired by the firmware update unit 105 is slightly different from the first to third embodiments of the present invention. In the first to third embodiments of the present invention, it has been described that the obtained firmware includes functional modules for each version of the driver in addition to the functional modules of the version originally included in the corresponding firmware version. . In the present embodiment, the acquired firmware only needs to include the function module of the originally included version.

  Here, the firmware execution device 140 and each functional block thereof can be configured by hardware elements similar to those of the first embodiment of the present invention described with reference to FIG. In this case, the functional module acquisition unit 149 includes a CPU 1001 that executes a program stored in the memory 1002, a management processor 1004, and a management network interface 1005. However, the hardware configuration of the firmware execution device 140 and each functional block thereof is not limited to the above-described configuration.

  Next, details of the functional blocks of the firmware execution device 140 that are different from those of the second embodiment of the present invention will be described.

  The functional module acquisition unit 149 functions when the dependency determination unit 104 determines that the inconsistency is not eliminated by the firmware update. That is, in this case, the functional module acquisition unit 149 acquires, from the management network, a functional module having a version having no dependency mismatch with the current driver version as a backup module.

  Also, the functional module acquisition unit 149 stores the acquired backup module in the firmware storage unit 123. Here, the firmware storage unit 123 stores the version of the functional module originally included in the current firmware by the firmware update unit 105. The version of the functional module that is originally included is hereinafter also referred to as a main module. That is, when the functional module acquisition unit 149 functions, the firmware storage unit 123 stores the main module and the backup module for functional modules having a dependency relationship with the driver version.

  An example of functional modules stored in the firmware storage unit 123 in this embodiment is shown in FIG. In FIG. 12, it is assumed that the function module A and the function module B have a dependency relationship with the driver version. Therefore, a main module and a backup module are stored for these functional modules. In this example, the functional module A represents a main module, and the functional module A ′ represents a backup module for the functional module A. The function module B represents a main module, and the function module B ′ represents a backup module for the function module B. In this example, it is assumed that the functional module C has no dependency relationship with the driver version. Therefore, the functional module C is stored as the main module, and the backup module for the functional module C is not stored.

  The operation of the firmware execution apparatus 140 configured as described above will be described with reference to FIG.

  In FIG. 13, the firmware execution device 140 operates in substantially the same manner as in the third embodiment of the present invention described with reference to FIG. However, the operation in the case where it is determined that the inconsistency in the dependency relationship is not eliminated by the firmware update (No in step S106) is slightly different.

  In this case, in the third embodiment of the present invention, the function module selection unit 106 selects a function module of a version that can be used according to the current driver version from the function modules stored in the firmware storage unit 123. (Step S110).

  On the other hand, in this embodiment, the firmware execution apparatus 140 is different in that it executes the following steps S141 to S143 instead of step S110.

  That is, in this case, the functional module acquisition unit 149 acquires, from the management network, a functional module having a version having no dependency mismatch with the current driver version as a backup module (step S141).

  Next, the functional module acquisition unit 149 stores the acquired backup module in the firmware storage unit 123 (step S142).

  Thereafter, the functional module selection unit 106 selects a backup module (step S143).

  Thereafter, the firmware execution apparatus 140 sets parameters by executing steps S121 to S123 as in the third embodiment of the present invention.

  Above, description of operation | movement of the firmware execution apparatus 140 is complete | finished.

  Next, effects of the fourth exemplary embodiment of the present invention will be described.

  The firmware execution device according to the fourth exemplary embodiment of the present invention can further suppress an increase in the amount of required resources while more reliably avoiding problems caused by firmware or driver updates.

  The reason will be described. In the fourth embodiment of the present invention, in addition to the configuration similar to that of the fourth embodiment of the present invention, the backup module acquisition unit determines that the inconsistency is not resolved by the firmware update by the dependency relationship determination unit. It works when it is done. That is, in this case, the backup module acquisition unit acquires, from the management network, a function module having a version having no dependency mismatch with the current driver version as a backup module. Then, the backup module acquisition unit stores the acquired backup module in the firmware storage unit. This is because the functional module selection unit selects the backup module.

  In other words, in the present embodiment, even if a function module has a dependency relationship with the driver version, it is not necessary to store the function modules that can be used by all versions of the driver in the firmware storage unit. In the present embodiment, for such a functional module, a version of the main module that is originally included in the current firmware and a backup module that can be used depending on the version of the current driver may be stored in the firmware storage unit. Therefore, this embodiment can reduce the amount of resources required as a firmware storage unit.

  In the present embodiment, the firmware acquired by the firmware storage unit does not need to include functional modules for different versions. Therefore, this embodiment can apply firmware having a general data structure as firmware to be updated.

(Fifth embodiment)
Next, a fifth embodiment of the present invention will be described in detail with reference to the drawings. In the present embodiment, an embodiment of a firmware management apparatus corresponding to the firmware execution apparatus of the present invention will be described.

  First, a firmware management apparatus 200 as a fifth embodiment of the present invention will be described. The firmware management apparatus 200 is an apparatus that manages firmware executed by the firmware execution apparatus 120 according to the second embodiment of the present invention. A functional block configuration of the firmware management apparatus 200 is shown in FIG. In FIG. 14, the firmware management apparatus 200 includes a combination information update unit 201.

  Here, an example of a hardware configuration of the firmware management apparatus 200 will be described. The firmware management apparatus 200 is configured by a computer apparatus that constitutes the firmware execution apparatus 120 as the second embodiment of the present invention as shown in FIG. In this case, the combination information update unit 201 is configured by the CPU 1001 that executes a program stored in the memory 1002. Note that the hardware configuration of the firmware management apparatus 200 and its functional blocks is not limited to the above-described configuration.

  Next, details of functional blocks of the firmware management apparatus 200 will be described.

  The combination information update unit 201 updates the combination information stored in the combination information storage unit 121 in the firmware execution device 120.

  The operation of the firmware management apparatus 200 configured as described above is shown in FIG.

  In FIG. 15, first, the combination information update unit 201 acquires combination information to be updated, and stores the acquired combination information in the combination information storage unit 121 of the firmware execution apparatus 120 (step S201). For example, the combination information update unit 201 may acquire the combination information to be updated from the storage location input by the input device 1007 or a predetermined storage location on the network.

  At this time, the combination information update unit 201 may overwrite the information stored in the combination information storage unit 121 using the acquired combination information. Alternatively, the combination information update unit 201 may add and write the acquired combination information.

  Thus, the firmware management apparatus 200 ends the operation.

  The combination information update unit 201 may update the combination information in response to an instruction from the input device 1007. Alternatively, when the firmware management apparatus 200 has a firmware update function, the combination information update unit 201 may update the combination information when updating the firmware.

  The operation of the firmware management apparatus 200 at this time is shown in FIG.

  In FIG. 16, first, the firmware management apparatus 200 determines whether or not a firmware update is requested (step S211). The update request is made, for example, via the input device 1007 or the management network.

  If firmware update is not requested, the firmware management apparatus 200 ends the operation.

  On the other hand, when the firmware update is requested, the firmware management apparatus 200 acquires the firmware for update and updates the firmware (step S212).

  Note that the firmware for update refers to a newer version of firmware for updating from the current firmware.

  Next, the combination information update unit 201 updates the combination information by executing step S201 described above (step S201).

  Next, the firmware management apparatus 200 restarts the computer apparatus (step S213).

  This is the end of the description of the operation of the firmware management apparatus 200 when the combination information is updated when the firmware is updated.

  Next, the operation of the firmware management apparatus 200 will be described using a specific example. Here, it is assumed that the combination information is updated when the firmware is updated.

<Specific Example 4>
Here, it is assumed that the current firmware is version a.

  Further, it is assumed that the driver version storage unit 102 stores “1.0” as the current driver version. That is, the current driver is version 1.0.

  Moreover, it is assumed that the combination information storage unit 121 stores the combination information illustrated in FIG. 8 as in the second specific example and the third specific example of the second embodiment of the present invention.

  In this case, first, the firmware management apparatus 200 updates the firmware a to the firmware b (Yes in step S211, S212). For example, the update firmware b may be acquired from a portable storage medium. Alternatively, the update firmware b may be received via a management network for out-of-band management.

  Next, the combination information update unit 201 writes the combination information for update in the combination information storage unit 121 (step S201). For example, the combination information for update may be acquired from a portable storage medium. Alternatively, the combination information for update may be received via a management network for out-of-band management. Note that the combination information for updating refers to newer combination information for updating the current combination information.

  Next, the combination information update unit 201 restarts the computer device (step S213). As a result, the current firmware becomes version b. At this time, the driver version storage unit 102 stores “1.0” as the current driver version. Therefore, after that, the firmware execution device 120 operates in the same manner as the specific example 3 in the second embodiment of the present invention.

  This is the end of the description of the operation of the specific example.

  Next, effects of the fifth exemplary embodiment of the present invention will be described.

  The firmware management apparatus according to the fifth embodiment of the present invention can more reliably avoid the occurrence of problems due to firmware or driver updates.

  The reason will be described. This is because the combination information update unit updates the combination information in the present embodiment. As a result, the present embodiment can update the combination information referred to by the firmware execution apparatus to the latest information at an arbitrary timing in order to avoid the occurrence of problems due to firmware or driver updates. .

(Sixth embodiment)
Next, a sixth embodiment of the present invention will be described in detail with reference to the drawings. In the present embodiment, an embodiment of a driver execution device corresponding to the firmware execution device of the present invention will be described.

  First, a driver execution device 300 as a sixth exemplary embodiment of the present invention will be described. The driver execution device 300 is a device that executes a driver installed in a computer device including the firmware execution device 120 according to the second embodiment of the present invention. A functional block configuration of the driver execution device 300 is shown in FIG. In FIG. 17, the driver execution device 300 includes an error information registration unit 301.

  Here, an example of a hardware configuration of the driver execution device 300 will be described. The driver execution device 300 is configured by a computer device that constitutes the firmware execution device 120 as the second embodiment of the present invention as shown in FIG. In this case, the error information registration unit 301 is configured by a CPU 1001 that executes a program stored in the memory 1002. Note that the hardware configuration of the driver execution device 300 and its functional blocks is not limited to the above-described configuration.

  Next, details of functional blocks of the driver execution device 300 will be described.

  When the error information registration unit 301 detects an operation error in the control of the hardware device 1008, the error information registration unit 301 registers the error information in the combination information storage unit 121 of the firmware execution device 120. Specifically, the error information registration unit 301 uses the combination information storage unit 121 to display the current setting value information of the parameter for the combination of the firmware functional module version related to the operation error and the current driver version. Search for entries that contain it. Then, the error information registration unit 301 may register error information indicating that there is an operation error in the searched entry.

  The operation of the driver execution device 300 configured as described above is shown in FIG.

  In FIG. 18, the error information registration unit 301 determines whether an operation error has been detected in the control of the hardware device 1008 (step S301).

  If no operation error is detected (No in step S301), the error information registration unit 301 repeats the operation in step S301.

  On the other hand, when an operation error is detected (Yes in step S301), the error information registration unit 301 registers the error information in the combination information storage unit 121 of the firmware execution apparatus 120 (step S302).

  Then, the error information registration unit 301 repeats the operation from step S301.

  Above, description of operation | movement of the driver execution apparatus 300 is complete | finished.

  Next, effects of the sixth exemplary embodiment of the present invention will be described.

  The driver execution device according to the sixth exemplary embodiment of the present invention can more reliably avoid problems caused by firmware or driver updates.

  The reason will be described. In the present embodiment, when the error information registration unit detects an operation error in the control of the hardware device, the error information is registered in the combination information storage unit of the firmware execution apparatus according to the second embodiment of the present invention. Because it does.

  Here, the present embodiment assumes a case where such an operation error has occurred due to firmware or driver updates. In this embodiment, the error information registered in this way is referred to the firmware execution apparatus as the second embodiment of the present invention that operates when the computer apparatus is restarted. Accordingly, when the computer apparatus is restarted after an operation error occurs, the corresponding set value is not set as a parameter. Therefore, the present embodiment can contribute to avoiding problems caused by firmware or driver updates.

  In the present embodiment, when the original combination information stored in the combination information storage unit of the firmware execution apparatus is provided by the vendor, the provided combination information may not include error information. . Even in this case, the driver execution device according to the present embodiment registers error information in response to detection of an operation error. Thereby, the error information is accumulated based on the operation results.

(Seventh embodiment)
Next, a seventh embodiment of the present invention will be described in detail with reference to the drawings. In the present embodiment, an embodiment of a driver management apparatus corresponding to the firmware execution apparatus of the present invention will be described.

  First, a driver management apparatus 400 as a seventh embodiment of the present invention will be described. The driver management apparatus 400 is an apparatus that manages drivers installed in a computer apparatus including the firmware execution apparatus 100 as the first embodiment of the present invention. A functional block configuration of the driver management apparatus 400 is shown in FIG. In FIG. 19, the driver management apparatus 400 includes a driver update unit 401 and an information update unit 402.

  Here, an example of a hardware configuration of the driver management apparatus 400 will be described. The driver management apparatus 400 is configured by a computer apparatus that constitutes the firmware execution apparatus 100 as the first embodiment of the present invention as shown in FIG. In this case, the driver update unit 401 and the information update unit 402 are configured by a CPU 1001 that executes a program stored in the memory 1002. Note that the hardware configuration of the driver management device 400 and each functional block thereof is not limited to the above-described configuration.

  Next, details of each functional block of the driver management apparatus 400 will be described.

  The driver update unit 401 updates the driver installed in the computer device. For example, the driver update unit 401 may update the driver based on information representing an update instruction input via the input device 1007. The driver update unit 401 may acquire a driver having a version newer than the current version from a storage location based on information indicating an update instruction. Examples of such storage locations include, but are not limited to, the memory 1002, a portable storage medium, or a management server on a network.

  The information update unit 402 updates the information indicating the current driver version stored in the driver version storage unit 102 in the firmware execution apparatus 100 to information indicating the version updated by the driver update unit 401.

  Note that the information update unit 402 may be further configured to be able to update information stored in the combination information storage unit 101 in the firmware execution device 100 at the timing when the driver is updated. In this case, the driver update unit 401 may acquire update combination information in addition to information indicating an update driver based on information indicating an update instruction.

  Next, the operation of the driver management apparatus 400 is shown in FIG.

  In FIG. 20, first, the driver update unit 401 acquires information representing a driver for update, and updates the current driver using the information representing the acquired driver (step S401).

  Next, the information update unit 402 updates the information stored in the firmware execution device 100 (step S402).

  Specifically, the information update unit 402 updates the information indicating the current driver version stored in the driver version storage unit 102 to information indicating the updated driver version. Furthermore, as described above, the information update unit 402 may update the information stored in the combination information storage unit 101. In this case, it is assumed that the combination information for update is acquired together with the information indicating the driver for update in step S401.

  Next, the driver update unit 401 restarts the computer device (step S403).

  At this time, it is assumed that the driver is updated prior to the firmware by the update operation in step S402. Also, for this reason, it is assumed that inconsistency in dependency relationship has occurred between versions. Even in that case, after the restart in step S403, each functional block of the firmware execution apparatus 100 operates in the same manner as in the first embodiment of the present invention. At this time, the current driver version information updated by the information updating unit 402 of the driver management apparatus 400 is referred to. Thus, the dependency relationship determination unit 104 determines that there is a dependency mismatch between the current firmware version and the updated driver version, and that the mismatch is resolved by the firmware update. As a result, the firmware update unit 105 updates the firmware, and the inconsistency is resolved.

  Next, effects of the seventh exemplary embodiment of the present invention will be described.

  The driver management apparatus according to the seventh embodiment of the present invention can more reliably avoid problems caused by firmware or driver updates.

  The reason will be described. In the present embodiment, the driver update unit updates the driver of the computer apparatus including the firmware execution apparatus as the first embodiment of the present invention. This is because the information updating unit updates the information stored in the driver version storage unit of the firmware execution apparatus to information indicating the updated driver version.

  Thus, in this embodiment, the updated driver version is referred to by the firmware execution apparatus as the first embodiment of the present invention that operates when the computer apparatus is restarted. Accordingly, in the firmware execution apparatus, inconsistency in dependency between the current firmware and the updated driver version is correctly determined. Therefore, the present embodiment can contribute to avoiding problems caused by firmware or driver updates.

  Furthermore, in the present embodiment, when the information update unit is configured to update the combination information at the time of driver update, such combination information ensures that the information about the updated driver version is included. Expected to include. Therefore, in the firmware execution apparatus after the restart, the combination information including the information related to the updated driver version is referred to. As a result, according to the present embodiment, it is possible to more reliably avoid the occurrence of problems due to inconsistencies in dependency relationships between versions.

(Eighth embodiment)
Next, an eighth embodiment of the present invention will be described in detail with reference to the drawings. In the present embodiment, another embodiment of the driver management apparatus corresponding to the firmware execution apparatus of the present invention will be described.

  First, the driver management apparatus 480 as the 8th Embodiment of this invention is demonstrated. The driver management apparatus 480 is an apparatus that updates a driver installed in a computer apparatus including the firmware execution apparatus 100 according to the first embodiment of the present invention. A functional block configuration of the driver management apparatus 480 is shown in FIG. In FIG. 21, the driver management device 480 is different from the driver management device 400 according to the seventh embodiment of the present invention in that a driver update unit 481 is provided instead of the driver update unit 401.

  Next, among the functional blocks of the driver management apparatus 480, details of functional blocks different from those of the seventh embodiment of the present invention will be described.

  The driver update unit 481 refers to the combination information stored in the combination information storage unit 101 in the firmware execution apparatus 100 before updating the driver. Then, the driver update unit 481 refers to the combination information to determine whether or not there is a dependency mismatch between the current firmware version and the updated version when the driver is updated. . If there is a mismatch in the dependency relationship with the updated version, the driver update unit 481 does not update the current driver. If there is no dependency mismatch with the updated version, the driver update unit 481 updates the current driver.

  Next, the operation of the driver management apparatus 480 is shown in FIG.

  In FIG. 22, first, the driver update unit 481 acquires the version of the driver for update (step S421).

  Next, the driver update unit 481 acquires the current firmware version (step S422).

  Next, the driver update unit 481 reads combination information from the combination information storage unit 101 of the firmware execution apparatus 100 (step S423).

  Next, the driver update unit 481 determines whether or not there is a mismatch in dependency between the version of the driver for update and the version of the current firmware with reference to the combination information (step S424).

  If it is determined that there is a dependency mismatch (Yes in step S424), the driver update unit 481 ends the operation without updating the driver.

  On the other hand, if it is determined that there is no dependency mismatch (No in step S424), the driver management apparatus 480 performs steps S401 to S403 in the same manner as the driver management apparatus 400 according to the seventh embodiment of the present invention. Operate. As a result, the driver is updated, the information in the firmware execution apparatus 100 is updated, and the computer apparatus is restarted.

  Thus, the driver management device 480 ends the operation.

  Next, effects of the eighth exemplary embodiment of the present invention will be described.

  The driver management apparatus according to the eighth embodiment of the present invention can more reliably avoid problems caused by firmware or driver updates.

  The reason will be described. This is because, in the present embodiment, the driver update unit operates as follows before updating the driver of the computer apparatus including the firmware execution apparatus as the first embodiment of the present invention. In other words, the driver update unit refers to the combination information storage unit of the firmware execution device to determine whether or not there is a dependency mismatch between the current firmware version and the version of the driver for update to be updated. Judgment by. When there is no dependency mismatch, the driver update unit operates in the same manner as the driver update unit according to the seventh embodiment of the present invention to update the driver. This is because the information update unit updates the driver version storage unit and the like of the firmware execution device.

  As described above, according to the present embodiment, it is possible to avoid the occurrence of inconsistency in the dependency relationship due to the driver being updated before the firmware.

(Ninth embodiment)
Next, a ninth embodiment of the present invention will be described in detail with reference to the drawings. In the present embodiment, an embodiment of a computer apparatus including the firmware execution apparatus of the present invention will be described. Note that, in each drawing referred to in the description of the present embodiment, the same reference numerals are given to the same configuration and steps that operate in the same manner as in the first embodiment of the present invention, and the detailed description in the present embodiment. Description is omitted.

  First, FIG. 23 shows a functional block configuration of a computer apparatus 1 as the ninth embodiment of the present invention. In FIG. 23, the computer apparatus 1 includes a firmware execution apparatus 100 as the first embodiment of the present invention. Firmware implemented in the computer apparatus 1 is executed by the firmware execution apparatus 100. Here, the computer apparatus 1 can be configured by the hardware elements described with reference to FIG. However, the hardware configuration of the computer apparatus 1 is not limited to the above-described configuration.

  The functional block configuration and operation of the firmware execution apparatus 100 included in the computer apparatus 1 are as described in the first embodiment of the present invention.

  Next, effects of the ninth exemplary embodiment of the present invention will be described.

  The computer apparatus according to the ninth embodiment of the present invention can more reliably avoid problems caused by firmware or driver updates.

  The reason will be described.

  The computer apparatus according to the present embodiment includes a firmware execution apparatus as the first embodiment of the present invention. This is because the present embodiment eliminates inconsistencies in dependency relations between versions both when the driver is updated before the firmware and when the firmware is updated before the driver.

  That is, the computer apparatus according to the present embodiment eliminates the inconsistency in the dependency relationship even when the firmware or driver is updated without considering the dependency relationship between the versions and the update order. Thereby, the computer apparatus of this Embodiment can avoid the malfunction by the update of a firmware or a driver more reliably.

  In the present embodiment, the computer apparatus uses a firmware execution apparatus as one of the second to fourth embodiments of the present invention instead of the firmware execution apparatus as the first embodiment of the present invention. May be included.

  In the present embodiment, the computer apparatus may include a firmware management apparatus as the fifth embodiment of the present invention in addition to the firmware execution apparatus.

  In the present embodiment, the computer device may include a driver execution device as a sixth embodiment of the present invention in addition to the firmware execution device.

  In the present embodiment, the computer device may include a driver management device according to the seventh or eighth embodiment of the present invention in addition to the firmware execution device.

  Further, in each of the above-described embodiments of the present invention, the example in which each functional block of each apparatus is realized by a CPU that executes a computer program stored in a memory has been described. Not only this but each functional block or those arbitrary combinations may be implement | achieved by the hardware for exclusive use.

  In each embodiment of the present invention described above, the operation of each device described with reference to each flowchart is stored in a storage device (storage medium) of the computer device as a computer program of the present invention. Then, the computer program may be read and executed by the CPU. In such a case, the present invention is constituted by the code of the computer program or a storage medium.

  Moreover, each embodiment mentioned above can be implemented in combination as appropriate.

  The present invention is not limited to the above-described embodiments, and can be implemented in various modes.

A part or all of each of the above-described embodiments can be described as in the following supplementary notes, but is not limited thereto.
(Appendix 1)
Regarding the combination of the version of the function module included in each version of the firmware installed in the computer apparatus and the version of the driver controlling the hardware device connected to the inside or outside of the computer apparatus, the dependency relationship between the versions is determined. Combination information storage means for storing combination information including dependency relationship information to represent;
Driver version storage means for storing information representing the version of the current driver currently installed in the computer device;
In addition to the function module of the version originally included in the current firmware version currently implemented in the computer device, the function module having a dependency relationship with the version of the driver can be used by each version of the driver Firmware storage means for storing various versions of functional modules;
Upon startup of the computing device, whether there is a dependency mismatch between the current firmware version and the current driver version, and if there is a mismatch, updating the firmware Dependency determination means for determining whether or not the inconsistency is resolved by referring to the combination information;
When it is determined by the dependency relationship determining means that the inconsistency is resolved by updating the firmware, the computer apparatus is obtained after obtaining the version of firmware that eliminates the inconsistency and updating the firmware storage means. Firmware update means for restarting,
When the dependency determination means determines that the inconsistency does not exist, the function module of the version originally included in the current firmware is selected and executed, and the inconsistency is not resolved by the firmware update. Function module selection means for selecting and executing a function module of a version that can be used according to the version of the current driver, if determined;
A firmware execution device comprising:
(Appendix 2)
The combination information storage means includes setting value information representing a setting value that can be set as a parameter of the firmware, in addition to the dependency information, for the combination of the version of the functional module and the version of the driver, and the setting Storing the combination information further including error information indicating the presence or absence of an operation error when the value is applied;
It further comprises parameter setting means for setting, as the parameter, a setting value without an operation error in the combination of the function module selected by the function module selecting means and the current driver version by referring to the combination information. The firmware execution apparatus according to appendix 1, wherein
(Appendix 3)
The combination information storage means, for the combination of the version of the functional module and the version of the driver, in addition to the dependency relationship information, the setting value information, and the error information, priority information indicating the priority of the setting value And further storing the combination information,
The parameter setting means refers to the combination information, and selects based on the priority among the setting values without operation error in the combination of the function module selected by the function module selection means and the current driver version. The firmware execution apparatus according to attachment 2, wherein the set value is set as the parameter.
(Appendix 4)
Any one of appendix 1 to appendix 3, further comprising: a combination information acquisition unit that acquires the combination information via a management network and stores the combination information in the combination information storage unit when the computer apparatus is activated. Firmware execution device described in one.
(Appendix 5)
When the dependency determination unit determines that the inconsistency is not eliminated by the firmware update, a function module having a version having no dependency mismatch with the current driver version is obtained from the management network. The firmware execution apparatus according to any one of appendix 1 to appendix 4, further comprising a functional module obtaining unit that obtains and stores the module in the firmware storage unit.
(Appendix 6)
The combination of the firmware execution devices when an operation error is detected when the driver is executed in the computer device including the firmware execution device according to any one of the supplementary notes 2 and the supplementary notes 3 to 5 subordinate to the supplementary note 2. A driver execution apparatus comprising error information registration means for registering the error information in an information storage means.
(Appendix 7)
Driver update means for updating the driver mounted on a computer device including the firmware execution device according to any one of appendix 1 to appendix 5;
Information updating means for updating the information representing the version of the current driver stored in the driver version storage means in the firmware execution device to information representing the version updated by the driver updating means;
A driver management device comprising:
(Appendix 8)
The driver update means refers to the combination information stored in the combination information storage means in the firmware execution device, thereby updating the current firmware version and the updated version when the current driver is updated. The driver management apparatus according to appendix 7, wherein the current driver is not updated if there is a dependency mismatch between the first and second drivers.
(Appendix 9)
9. The driver management apparatus according to appendix 7 or appendix 8, wherein the information update unit further updates the combination information stored in the combination information storage unit in the firmware execution apparatus.
(Appendix 10)
A firmware management apparatus comprising combination information update means for updating combination information stored in the combination information storage means in the firmware execution apparatus according to any one of appendix 1 to appendix 5.
(Appendix 11)
A computer device including the firmware execution device according to any one of appendix 1 to appendix 5 and having the firmware executed by the firmware execution device mounted thereon.
(Appendix 12)
When the computer device includes the firmware execution device according to any one of Supplementary Note 2 and Supplementary Note 3 and Supplementary Note 4 subordinate to Supplementary Note 2,
further,
12. The computer device according to appendix 11, including the driver execution device according to appendix 6.
(Appendix 13)
further,
13. The computer apparatus according to appendix 11 or appendix 12, including the driver management apparatus according to any one of appendix 7 to appendix 9.
(Appendix 14)
further,
14. The computer apparatus according to any one of appendix 11 to appendix 13, including the firmware management apparatus according to appendix 10.
(Appendix 15)
Computer equipment
Dependency relationship between versions of a combination of a version of a function module included in each version of firmware installed in the computer apparatus and a version of a driver that controls a hardware device connected to the inside or outside of the computer apparatus Combination information storage means for storing combination information including dependency relationship information representing
Driver version storage means for storing information representing the version of the current driver currently installed in the computer device;
In addition to the function module of the version originally included in the current firmware version currently implemented in the computer device, the function module having a dependency relationship with the version of the driver can be used by each version of the driver Firmware storage means for storing functional modules of various versions,
Upon startup of the computing device, whether there is a dependency mismatch between the current firmware version and the current driver version, and if there is a mismatch, updating the firmware Determine whether or not the inconsistency is resolved by referring to the combination information,
When it is determined that the inconsistency is resolved by the firmware update, after obtaining the version of firmware that resolves the inconsistency and updating the firmware storage unit, the computer apparatus is restarted,
If it is determined that there is no inconsistency, the function module of the version originally included in the current firmware is selected and executed,
A method of selecting and executing a function module of a version that can be used according to the version of the current driver when it is determined that the inconsistency is not resolved by updating the firmware.
(Appendix 16)
Regarding the combination of the version of the function module included in each version of the firmware installed in the computer apparatus and the version of the driver controlling the hardware device connected to the inside or outside of the computer apparatus, the dependency relationship between the versions is determined. Combination information storage means for storing combination information including dependency relationship information to represent;
Driver version storage means for storing information representing the version of the current driver currently installed in the computer device;
In addition to the function module of the version originally included in the current firmware version currently implemented in the computer device, the function module having a dependency relationship with the version of the driver can be used by each version of the driver Firmware storage means for storing functional modules of various versions,
Upon startup of the computing device, whether there is a dependency mismatch between the current firmware version and the current driver version, and if there is a mismatch, updating the firmware A dependency determination step of determining whether or not the inconsistency is resolved by referring to the combination information;
When it is determined by the dependency determination step that the inconsistency is resolved by updating the firmware, a version of firmware that eliminates the inconsistency is acquired and the firmware storage unit is updated, and then the computer apparatus A firmware update step to restart
If the inconsistency determination step determines that the inconsistency does not exist, the function module of the version originally included in the current firmware is selected and executed, and the inconsistency is not resolved by the firmware update. A function module selection step of selecting and executing a function module of an available version according to the version of the current driver, if determined;
For causing the computer apparatus to execute the program.

DESCRIPTION OF SYMBOLS 1 Computer apparatus 100,120,130,140 Firmware execution apparatus 101,121 Combination information storage part 102 Driver version storage part 103,123 Firmware storage part 104 Dependency judgment part 105 Firmware update part 106 Functional module selection part 127 Parameter setting part 138 Combination information acquisition unit 149 Functional module acquisition unit 200 Firmware management device 201 Combination information update unit 300 Driver execution device 301 Error information registration unit 400, 480 Driver management device 401, 481 Driver update unit 402 Information update unit 1001 CPU
1002 Memory 1003 Network interface 1004 Management processor 1005 Management network interface 1006 Output device 1007 Input device 1008 Hardware device

Claims (10)

Regarding the combination of the version of the function module included in each version of the firmware installed in the computer apparatus and the version of the driver controlling the hardware device connected to the inside or outside of the computer apparatus, the dependency relationship between the versions is determined. Combination information storage means for storing combination information including dependency relationship information to represent;
Driver version storage means for storing information representing the version of the current driver currently installed in the computer device;
In addition to the function module of the version originally included in the current firmware version currently implemented in the computer device, the function module having a dependency relationship with the version of the driver can be used by each version of the driver Firmware storage means for storing various versions of functional modules;
Upon startup of the computing device, whether there is a dependency mismatch between the current firmware version and the current driver version, and if there is a mismatch, updating the firmware Dependency determination means for determining whether or not the inconsistency is resolved by referring to the combination information;
When it is determined by the dependency relationship determining means that the inconsistency is resolved by updating the firmware, the computer apparatus is obtained after obtaining the version of firmware that eliminates the inconsistency and updating the firmware storage means. Firmware update means for restarting,
When the dependency determination means determines that the inconsistency does not exist, the function module of the version originally included in the current firmware is selected and executed, and the inconsistency is not resolved by the firmware update. Function module selection means for selecting and executing a function module of a version that can be used according to the version of the current driver, if determined;
A firmware execution device comprising: The combination information storage means includes setting value information representing a setting value that can be set as a parameter of the firmware, in addition to the dependency information, for the combination of the version of the functional module and the version of the driver, and the setting Storing the combination information further including error information indicating the presence or absence of an operation error when the value is applied;
It further comprises parameter setting means for setting, as the parameter, a setting value without an operation error in the combination of the function module selected by the function module selecting means and the current driver version by referring to the combination information. The firmware execution device according to claim 1.   3. The combination information acquisition unit according to claim 1, further comprising a combination information acquisition unit configured to acquire the combination information via a management network and store the combination information in the combination information storage unit when the computer apparatus is activated. Firmware execution device.   When the dependency determination unit determines that the inconsistency is not eliminated by the firmware update, a function module having a version having no dependency mismatch with the current driver version is obtained from the management network. The firmware execution apparatus according to any one of claims 1 to 3, further comprising functional module acquisition means for acquiring and storing the firmware in the firmware storage means.   When an operation error is detected when executing the driver in a computer apparatus including the firmware execution apparatus according to claim 2 or claim 3 dependent on claim 2, the firmware execution is performed. A driver execution device comprising error information registration means for registering the error information in the combination information storage means of the device. Driver update means for updating the driver mounted on a computer device including the firmware execution device according to any one of claims 1 to 4,
Information updating means for updating the information representing the version of the current driver stored in the driver version storage means in the firmware execution device to information representing the version updated by the driver updating means;
A driver management device comprising:   5. A firmware management apparatus comprising combination information update means for updating combination information stored in the combination information storage means in the firmware execution apparatus according to any one of claims 1 to 4.   A computer apparatus including the firmware execution apparatus according to claim 1, wherein the firmware executed by the firmware execution apparatus is mounted. Computer equipment
Dependency relationship between versions of a combination of a version of a function module included in each version of firmware installed in the computer apparatus and a version of a driver that controls a hardware device connected to the inside or outside of the computer apparatus Combination information storage means for storing combination information including dependency relationship information representing
Driver version storage means for storing information representing the version of the current driver currently installed in the computer device;
In addition to the function module of the version originally included in the current firmware version currently implemented in the computer device, the function module having a dependency relationship with the version of the driver can be used by each version of the driver Firmware storage means for storing functional modules of various versions,
Upon startup of the computing device, whether there is a dependency mismatch between the current firmware version and the current driver version, and if there is a mismatch, updating the firmware Determine whether or not the inconsistency is resolved by referring to the combination information,
When it is determined that the inconsistency is resolved by the firmware update, after obtaining the version of firmware that resolves the inconsistency and updating the firmware storage unit, the computer apparatus is restarted,
If it is determined that there is no inconsistency, the function module of the version originally included in the current firmware is selected and executed,
A method of selecting and executing a function module of a version that can be used according to the version of the current driver when it is determined that the inconsistency is not resolved by updating the firmware. Regarding the combination of the version of the function module included in each version of the firmware installed in the computer apparatus and the version of the driver controlling the hardware device connected to the inside or outside of the computer apparatus, the dependency relationship between the versions is determined. Combination information storage means for storing combination information including dependency relationship information to represent;
Driver version storage means for storing information representing the version of the current driver currently installed in the computer device;
In addition to the function module of the version originally included in the current firmware version currently implemented in the computer device, the function module having a dependency relationship with the version of the driver can be used by each version of the driver Firmware storage means for storing functional modules of various versions,
Upon startup of the computing device, whether there is a dependency mismatch between the current firmware version and the current driver version, and if there is a mismatch, updating the firmware A dependency determination step of determining whether or not the inconsistency is resolved by referring to the combination information;
When it is determined by the dependency determination step that the inconsistency is resolved by updating the firmware, a version of firmware that eliminates the inconsistency is acquired and the firmware storage unit is updated, and then the computer apparatus A firmware update step to restart
If the inconsistency determination step determines that the inconsistency does not exist, the function module of the version originally included in the current firmware is selected and executed, and the inconsistency is not resolved by the firmware update. A function module selection step of selecting and executing a function module of an available version according to the version of the current driver, if determined;
For causing the computer apparatus to execute the program.

Images