JP2019049814A - Electronic device - Google Patents

Abstract

To reduce a consumption amount of a main storage device area required for starting up an electronic device as compared to the case where all program modules constituting firmware stored in storage means are read into a main storage device upon starting up the electronic device.SOLUTION: A selection part 14 selects one version of a function unit file of a plurality of versions stored in a second storage part on the basis of contents of a path setting file stored in a third storage part. An execution module stored in a first storage part 11 loads the function unit file of the version selected by the selection part 14 onto a main storage device.SELECTED DRAWING: Figure 3

Description

  The present invention relates to an electronic device.

  Patent Document 1 describes a version management method for a module group in an information processing apparatus, and when a module (module 1) is updated, a module (module 2 and others) affected by the update of the module 1 is also updated. If so, a version management information database that associates the updated module name with the latest version number of the module, manages these modules (modules 1, 2, etc.) as a unit, and other modules for each module An inter-module correspondence table for managing dependency information, and when the module name and the version number of the module are designated, the module is included with reference to the version management information database and the inter-module correspondence table. For modules other than those in the group of modules that are Version management method of modules, characterized in that collecting the correct version module, is disclosed.

Japanese Patent Laid-Open No. 07-302194

  According to the present invention, the main storage device area required for starting the electronic device is compared with the case where all the program modules constituting the firmware stored in the storage means are read into the main storage device when the electronic device is started. The purpose is to reduce consumption.

[Electronic device]
The present invention according to claim 1 is storage means for storing firmware filed in function units, and storing means for storing a plurality of different versions for each function unit file constituting the firmware;
A selection means for selecting a version of the functional unit file to be read into the main storage device at startup from a plurality of versions stored in the storage means;
Is an electronic device.

  According to a second aspect of the present invention, there is provided the electronic device according to the first aspect, wherein a file that is not an execution format among the functional unit files stored in the storage unit is not deleted from the storage unit during a firmware update process. Device.

  According to a third aspect of the present invention, in the firmware update process, when the functional unit file constituting the firmware to be installed is not the same as any of the functional unit files stored in the storage unit, The electronic device according to claim 2, further stored in a storage unit.

  According to the fourth aspect of the present invention, when the firmware update process, the functional unit file constituting the firmware to be installed is the same as one of the functional unit files stored in the storage unit The electronic device according to claim 2, wherein the electronic device is not additionally stored in the storage unit.

  According to a fifth aspect of the present invention, in the electronic device according to any one of the first to fourth aspects, the selecting unit selects a functional unit file version to be read into the main storage device at the time of activation in accordance with an instruction from the outside.

  The present invention according to claim 6 is the electronic device according to claim 5, wherein the selecting means selects a version of the functional unit file to be read into the main storage device upon activation in accordance with an instruction from a user.

The present invention according to claim 7 further comprises accepting means for accepting an instruction from the user as to which version of the functional unit file is to be read into the main storage device at startup,
The electronic device according to claim 6, wherein the selection unit selects a functional unit file version to be read into the main storage device at the time of activation in accordance with an instruction received by the reception unit.

  The present invention according to claim 8 is the electronic device according to claim 5, wherein the selection means selects a version of a functional unit file to be read into the main storage device upon activation in accordance with an instruction from another device.

The present invention according to claim 9 further comprises receiving means for receiving data transmitted from another device,
The electronic device according to claim 8, wherein the selection unit selects a version of a functional unit file that is read into a main storage device at the time of activation in accordance with data received by the reception unit.

  According to a tenth aspect of the present invention, the selecting means is a functional unit that is read into the main storage device at startup based on whether a history of events that have occurred in the electronic device meets a predetermined condition. 5. The electronic device according to claim 1, wherein a file version is selected.

  According to the eleventh aspect of the present invention, the selecting means is a function unit file version to be read into the main storage device at the time of activation based on whether or not an error history relating to a specific function meets a predetermined condition. The electronic device according to claim 10, wherein the electronic device is selected.

  In the present invention according to claim 12, when the error relating to a specific function occurs more than a predetermined frequency, the selection unit creates a debug log for the function unit file related to the specific function. The electronic device according to claim 11, wherein a plate having a function is selected as a plate to be read into the main storage device at startup.

  In the present invention according to claim 13, the selecting means creates a debug log for the function unit file related to the specific function when the error related to the specific function does not occur more than a predetermined frequency. The electronic device according to claim 11, wherein a version that does not have a function to be selected is selected as a version to be read into the main storage device at startup.

According to a fourteenth aspect of the present invention, there is provided verification means for verifying an electronic signature given to a functional unit file stored in the storage means,
Control means for controlling the startup processing of the electronic device according to the verification result by the verification means;
The electronic device according to claim 1, further comprising:

  According to a fifteenth aspect of the present invention, the control unit stops the activation process of the electronic device when the electronic signature given to the functional unit file of the version selected by the selection unit is not a valid signature. 15. The electronic device according to claim 14, wherein the electronic device is controlled.

  According to a sixteenth aspect of the present invention, the control unit does not stop the activation process of the electronic device when the electronic signature given to the functional unit file of the version selected by the selection unit is a valid signature. 15. The electronic device according to claim 14, wherein the electronic device is controlled as follows.

  According to a seventeenth aspect of the present invention, the control unit is configured such that the function of the version selected by the selection unit when the digital signature given to the functional unit file of the version selected by the selection unit is not a valid signature. The electronic device according to claim 14, wherein, as an alternative to the unit file, control is performed so that a functional unit file of a version different from the version selected by the selection unit is read into a main storage device during a startup process of the electronic device. is there.

  The present invention according to claim 18 is directed to the control unit, wherein when the electronic signature given to the functional unit file of the version selected by the selection unit is a valid signature, the control unit selects the version selected by the selection unit. The electronic device according to claim 14, wherein the functional unit file is controlled to be read into a main storage device during a startup process of the electronic device.

  According to the first aspect of the present invention, compared to the case where all of the program modules constituting the firmware stored in the storage means are read into the main storage device when the electronic device is activated, the electronic device is activated. It is possible to reduce the consumption of the necessary main storage area.

  According to the second aspect of the present invention, in addition to the effect of the present invention according to the first aspect, a plurality of functional unit file versions stored in the storage means can be provided by updating the firmware.

  According to the third aspect of the present invention, in addition to the effect of the present invention according to the second aspect, the capacity of the storage means required for storing the functional unit files of different versions is the same as the function of the same content. Compared to the case where unit files are stored in a plurality of storage means, the number of unit files can be reduced.

  According to the fourth aspect of the present invention, in addition to the effect of the present invention according to the second aspect, the capacity of the storage means required for storing the functional unit files of different versions is the same as the function of the same content. Compared to the case where unit files are stored in a plurality of storage means, the number of unit files can be reduced.

  According to the present invention of claim 5, in addition to the effect of the present invention of any one of claims 1 to 4, the version of the functional unit file that is read into the main storage device at the time of startup can be designated from the outside. .

  According to the present invention of claim 6, in addition to the effect of the present invention of claim 5, the version of the functional unit file instructed by the user is read into the main storage device at the time of activation.

  According to the present invention of claim 7, in addition to the effect of the present invention of claim 6, the user can specify the version of the functional unit file that is read into the main storage device at the time of activation.

  According to the present invention of claim 8, in addition to the effect of the present invention of claim 5, the version of the functional unit file instructed by another device is read into the main storage device at the time of activation.

  According to the present invention of claim 9, in addition to the effect of the present invention of claim 8, the version of the functional unit file that is read into the main storage device at the time of activation can be designated via another device. .

  According to the tenth aspect of the present invention, in addition to the effect of the present invention according to any one of the first to fourth aspects, the electronic device autonomously selects a functional unit file version to be read into the main storage device at the time of activation. become able to.

  According to the eleventh aspect of the present invention, in addition to the effect of the tenth aspect of the present invention, the function unit file version to be read into the main storage device at the time of activation is selected based on the error history related to the specific function. Become so.

  According to the twelfth aspect of the present invention, in addition to the effect of the present invention of the eleventh aspect, when an error relating to a specific function occurs more than a predetermined frequency, A version having a function for creating a log for debugging is read into the main memory at the time of activation.

  According to the thirteenth aspect of the present invention, in addition to the effect of the present invention of the eleventh aspect, when an error relating to a specific function does not occur more than a predetermined frequency, a functional unit file relating to the function As for, a version that does not have a function of creating a debug log is read into the main storage device at the time of startup.

  According to the present invention of claim 14, in addition to the effects of the present invention of any one of claims 1 to 13, when the functional unit file may be falsified, it is normal for the startup process of the electronic device. Can be controlled differently.

  According to the fifteenth aspect of the present invention, in addition to the effect of the present invention of the fourteenth aspect, even if a functional unit file that may have been falsified is selected by the selection means, the falsified possibility It is possible to prevent the electronic device from being activated in a state in which a functional unit file having a characteristic is loaded on the main storage device.

  According to the sixteenth aspect of the present invention, in addition to the effect of the fourteenth aspect of the present invention, the electronic device is activated in a state where a functional unit file having a low possibility of being tampered is loaded on the main storage device. It becomes possible.

  According to the present invention of claim 17, in addition to the effect of the present invention of claim 14, even if a functional unit file that may have been altered has been selected by the selection means, the possibility that the alteration has occurred It is possible to prevent the electronic device from being activated in a state in which a functional unit file having a characteristic is loaded on the main storage device.

  According to the present invention of claim 18, in addition to the effect of the present invention of claim 14, the electronic device is activated in a state where a functional unit file with a low possibility of being tampered is loaded on the main storage device. It becomes possible.

1 shows a hardware configuration of an electronic device 100 according to an embodiment of the present invention. It is a conceptual diagram of a structure of the example of the firmware which concerns on embodiment of this invention. 2 shows a functional configuration of the electronic device 100. 2 shows an example of a flow of firmware update processing in the electronic apparatus 100. An example of a flow in which a version of an entity module is selected based on an instruction from the outside is shown. An example of a screen that accepts designation from the user for the version of the entity module to be used is shown below. An example of the state of the version of the entity module stored in the storage unit 12 is shown. An example of information included in a file for designating the version of an actual module to be used, transmitted from another server device will be shown. An example of information included in a file for designating the version of an actual module to be used, transmitted from another server device will be shown. An example of a flow in which a version of an entity module is selected without an external instruction is shown. An example of an error history and an error totaling result is shown. Here is an example where the security module supports different algorithm types depending on the version.

  FIG. 1 shows a hardware configuration of the electronic device 100. The electronic device 100 communicates with the CPU 1, the memory 2, the auxiliary storage device 3 such as a magnetic storage device or an optical disk (including a drive for reading), and data transmission and reception with an external device or the like via a network. An interface (IF) 4 is provided, and these components are connected to each other via a control bus 5.

  The CPU 1 controls the operation of the electronic device 100 (particularly in terms of hardware) by executing firmware stored in the ROM area of the memory 2 as the main storage device or the auxiliary storage device 3. The firmware refers to a software program for controlling the hardware of the computer system, and is read into the RAM area of the memory 2 at the time of activation (hereinafter also referred to as “loaded” or the like) and executed.

  Here, a configuration of firmware of the electronic device 100 according to the present embodiment will be described.

  Firmware that is a software program for controlling the hardware of an electronic device in order to cause the electronic device in which the computer system is incorporated to perform a desired movement is generally divided into functional units (functional module units). The firmware according to the present embodiment is divided into program files in units of functional modules (hereinafter referred to as “program files”) that are created and implemented as one execution format program file including one execution module and a plurality of entity modules. As conceptually shown in FIG. 2, the firmware 21 includes one execution file 22 (corresponding to a “main module”) and an execution file, which are executable program files. It comprises a library 23 for providing functions. The library is a set of a plurality of entity files 24 (corresponding to “entity modules”). 2 shows an example of firmware when the electronic apparatus 100 is an image forming apparatus having a facsimile function and a copying function. A file is a unit when data is input / output on a storage device in a computer system, and data is input / output using a file as a minimum unit.

  In this way, a plurality of functional modules, which are program files for each functional unit, are combined to form one conceptual firmware, but each called by the main module (and loaded into the RAM area of the memory 2). There is no difference from general firmware in that the entity module provides a predetermined function to the main module.

  In addition, the main module of the firmware according to the present embodiment refers to a file (hereinafter also referred to as a “path setting file”) for storing the path of each functional module (the route to the directory where the file exists) in advance ( If the path setting file does not exist, the main module calls each entity module, which is a separate file, by referring to the path setting file when the electronic apparatus 100 is activated. In addition, when the path setting file is created, a predetermined initial value is set as a path of each functional module (hereinafter also referred to as “path setting value”).

  FIG. 3 shows a functional configuration of the electronic device 100. The electronic device 100 includes a first storage unit 11, a second storage unit 12, a third storage unit 13, and a selection unit 14.

  The first storage unit 11 stores an execution module in the firmware. In the present embodiment, the first storage unit 11 is realized by the ROM area of the memory 2.

  The second storage unit 12 stores a library, that is, a real module (group) in the firmware. In the present embodiment, the second storage unit 12 is realized by the auxiliary storage device 3.

  The second storage unit 12 is configured to store a plurality of different versions (hereinafter, also referred to as “versions”) for each entity module constituting the firmware library. Specifically, for example, for the same functional unit entity module, different versions have different file names, or even if the file names are the same, the stored directory is different, so Different versions of the entity module are stored.

  In the electronic device 100 according to the present embodiment, the entity module stored in the second storage unit 12 is not deleted during the firmware update process. Then, if the entity module constituting the firmware to be installed is not the same as any of the entity modules already stored in the second storage unit 12, it is added to the second storage unit 12 and stored in the second storage unit 12. If it is the same as one of the already stored entity modules, it is not added to the second storage unit 12. Note that installation refers to a process or action for adding software (here, firmware) to an electronic apparatus in which a computer system is incorporated so that it can be used.

  FIG. 4 illustrates a flow of firmware update processing.

  Step S1: The main module (execution file) stored in the first storage unit 11 is overwritten and updated with the main module constituting the firmware to be installed (hereinafter also referred to as “additional firmware”).

  Step S2: For each entity module (for each functional unit), the version of the entity module constituting the additional firmware (referred to as “additional module”) and the version of the entity module already stored in the second storage unit 12 (“existing” Module ”) and a determination is made as to whether an existing module has the same version as the additional module.

  Step S3: If the version of the entity module of the additional firmware does not match any of the versions of the entity modules already stored in the second storage unit 12 (NO in step S2), the module ( Entity file) is added to the second storage unit 12.

  Step S4: If the version of the entity module of the additional firmware is the same as any of the versions of the entity module already stored in the second storage unit 12 (YES in step S2), the module of the additional firmware The (substance file) is not added to the second storage unit 12.

  In the above description, an example has been described in which the additional firmware is assumed to be a conceptual (single) version of firmware. However, the firmware according to the present embodiment is filed in units of actual modules. Therefore, the update process may be performed in file units (corresponding to a part of firmware). For example, when installing what is provided without including the main module, the above step S1 is naturally unnecessary.

  In a general electronic device, firmware update means rewriting firmware (including deletion of an old version) as a single file, and a specific entity module included in previously installed firmware If the user wants to use the module, the version of the firmware containing the module is installed again, that is, the firmware needs to be updated. On the other hand, in the electronic apparatus 100 according to the present embodiment, since the old version of the entity module is not deleted along with the firmware update, the firmware update operation is unnecessary even in such a case.

  The third storage unit 13 stores a path setting file. The third storage unit 13 is realized by the auxiliary storage device 3, for example.

  The selection unit 14 expands (loads) on the memory when starting up the electronic device 100 from among the plurality of different stored versions, for each functional module in which the plurality of different versions are stored in the second storage unit 12. Select the version to be played. Specifically, when the selection unit 14 changes the value of the path setting value of the path setting file stored in the third storage unit 14, that is, the value of the path of each entity module, A version to be expanded on the memory is selected.

  There are two major methods for changing the path setting value in the path setting file: a method based on a direct instruction from the outside (for example, a user or another device), and an autonomous operation without an external instruction. (For example, based on the history of events that occurred in the electronic device 100).

  As an example of the case where the path setting value is changed based on an instruction from the outside, for example, a reception unit that receives an instruction from the user regarding which version of the functional unit file is to be read into the memory at the time of activation is further provided. In this way, it is possible to receive an instruction from the user, or to further include a receiving unit for receiving data transmitted from another device so as to accept an instruction from another server device or the like. good. Hereinafter, a flow for selecting the version of the entity module used by the electronic apparatus 100 according to the present embodiment will be described with reference to FIG.

  Step S101: Accepting designation of the version of the functional module to be used from outside.

  If the designation is made by the user, for example, when the two storage units "compatibility-oriented version" and "vulnerability-compatible version" are stored in the second storage unit 12, the input screen as shown in FIG. To accept an input for designating which version of the module, “Compatibility-oriented version” or “Vulnerability version” is to be used.

  If the designation is made from another device, for example, when the version of each entity module is stored in the second storage unit 12 as shown in FIG. The specification of the version of each entity module is received by receiving data including information such as the type of the entity module and its version number as illustrated in FIG.

  Step S102: The selection unit 14 changes the path setting value for each entity module in the path setting file to the path value of the directory where the version specified in step S101 exists.

  Step S103: The electronic device 100 is restarted at an arbitrary timing, and at startup, the main module calls each function module based on the path setting value set in the path setting file for each entity module. The specified version of the entity module is loaded onto the memory 2 (RAM area).

  Note that in the electronic device 100 in which the version of each entity module is stored in the second storage unit 12 as shown in FIG. 7, when the data illustrated in FIG. Security module: Version 2.0, Authentication module: Version 3.0, Scan module: Version 1.0, Print module: Version 3.0

  Here, when the firmware is subsequently updated and the security module: version 3.0 is added to the second storage unit 12, the actual module selected at the time of activation is the security module: version 3.0, the authentication module: Version 3.0, scan module: version 1.0, and print module: version 3.0. In this way, the version of the selected entity module is changed even if the external instruction content is not changed. In the above example, the latest version of the security module is selected even if the content of instructions from the outside is not changed. However, the security module is provided so that the newer version of the security module increases the security strength. If so, the electronic device 100 is automatically selected so as to increase the security strength.

  Next, an example in which the version of the entity module is selected based on whether the history of events (various events such as errors and notifications) occurring in the electronic device 100 meets predetermined conditions will be described. To do.

  First, an example in which the version of the entity module is selected based on whether or not the error history meets a predetermined condition will be described with reference to the flowchart of FIG. Here, for each entity module, a “debug version” having a function of creating a log for debugging (a history of processing contents in the electronic device is recorded in order to find defects and problems in the program) And two versions of “normally used version” that are not included are stored in the second storage unit 12 in advance, and an error exceeding a predetermined frequency (here, seven times a week) occurs. In this example, the debug version is selected for the actual module, and the normal use version is selected for the actual module.

  Step S201: The error history is referred to, and the number of error occurrences for each functional module is counted. This is performed periodically (here, every week), and the number of error occurrences is reset each time. FIG. 11 conceptually shows an example of an error history and the total number of errors.

  Step S202: The selection unit 14 sets a path setting value for each functional module in the path setting file according to the number of error occurrences counted in step S201. Specifically, for the function module whose number counted in step S201 is 7 times or more, the path setting value is set to be the path of the debug version directory, and the function module that is not (less than 6 times). Is set so that the path setting value is the path of the normal use version directory.

  Step S203: The electronic device 100 is restarted at an arbitrary timing, and at the time of startup, the main module calls each function module based on the path setting value set in the path setting file for each function module. It is loaded onto the RAM area of the memory 2.

  As described above, when the error history of FIG. 11 is taken as an example, the debug version is selected for the security module, and the normal use version is selected for other function modules without direct instructions from the outside. It will be.

  Further, as in the example shown below, the version of the entity module may be selected based on the usage history regarding a specific function.

  For example, in the security module that manages the security-related functions of the electronic device 100, the encryption algorithm used for plaintext encryption and decryption of the ciphertext and the hash function algorithm used for detecting data alteration are available (available). When the algorithm function is built in, the algorithm that was supported by the old version of the security module is not supported by the new version of the module, so the new module has fewer types of supported algorithms. (Illustrated in FIG. 12).

  This is because both algorithms generally become obsolete over time, so it is preferable not to use (or cannot) use older algorithms to ensure communication security (confidentiality, integrity, etc.). Based on thinking.

  On the other hand, since the algorithm corresponding to each communication partner device is naturally different, there is a view that it is preferable to use as many algorithms as possible from the viewpoint of convenience. However, the more modules that can use more algorithms, the more memory is consumed.

  Therefore, for example, referring to the history used for the cryptographic algorithm and the hash function algorithm, the version of the security module that includes all the used algorithms and minimizes the type of the corresponding algorithm is selected. You may make it do. As a result, the amount of memory consumed for the security module is minimized.

  In addition, since the firmware is provided via the Internet or the installed firmware may be falsified, in this embodiment, in order to ensure authenticity, each functional module is provided with each function module. The timing of loading on the memory so as to include a verification unit that verifies the attached electronic signature (that is, in units of files) and a control unit that controls the activation processing of the electronic device 100 according to the verification result by the verification unit The authenticity may be confirmed by.

  Explaining an example in which a public key cryptosystem private key is used as an electronic signature, each functional module is provided and installed in a state encrypted in advance with the firmware creator's private key. The signature is verified by the verification unit when the electronic device 100 is activated, and a module (hereinafter also referred to as “pirated module”) whose electronic signature is not a valid signature (cannot be confirmed by the firmware creator) is selected by the selection unit 14. If it is selected, the startup process of the electronic device 100 is stopped, or another version that is not a pirated module (confirmed to have been created by the firmware creator) as an alternative to the selected module These modules may be loaded into the memory.

  In the above-described embodiment, an example in which only the execution file that is the main module of the firmware is stored in the ROM area of the memory 2 and the library is stored in the auxiliary storage device 3 has been described. The present invention can also be implemented in a form stored in the area.

  In the aspect in which the library is stored in the ROM area, the risk of falsification of each file (substance module) in the library is reduced as compared with the aspect in which the library is stored in the auxiliary storage device 3.

  In the case where the library is stored in the auxiliary storage device 3, there is no restriction on the file capacity of each entity module and the number of stored versions due to the ROM capacity.

100 Electronic device 1 CPU
2 memory 3 auxiliary storage device 4 communication interface 5 control bus 11 first storage unit 12 second storage unit 13 third storage unit 14 selection unit 21 firmware 22 execution file 23 library 24 entity file

Claims (18)

Storage means for storing firmware filed in functional units, each of the functional unit files constituting the firmware, storing means for storing a plurality of different versions;
A selection means for selecting a version of the functional unit file to be read into the main storage device at startup from a plurality of versions stored in the storage means;
An electronic device with   The electronic device according to claim 1, wherein a file that is not an execution format among the functional unit files stored in the storage unit is not deleted from the storage unit during a firmware update process.   The function unit file constituting the firmware to be installed is additionally stored in the storage unit when the firmware update process is not the same as any of the function unit files stored in the storage unit. Item 3. The electronic device according to Item 2.   When the firmware update process, if the functional unit file constituting the firmware to be installed is the same as one of the functional unit files stored in the storage unit, it is not additionally stored in the storage unit. The electronic device according to claim 2.   5. The electronic device according to claim 1, wherein the selection unit selects a version of the functional unit file that is read into the main storage device at the time of activation in accordance with an instruction from the outside.   The electronic device according to claim 5, wherein the selection unit selects a functional unit file version to be read into the main storage device at the time of activation in accordance with an instruction from a user. A receiving means for receiving an instruction from the user as to which version of the functional unit file is to be read into the main storage device at the time of activation;
The electronic device according to claim 6, wherein the selection unit selects a functional unit file version to be read into the main storage device at the time of activation in accordance with an instruction received by the reception unit.   The electronic device according to claim 5, wherein the selection unit selects a version of the functional unit file that is read into the main storage device at startup in accordance with an instruction from another device. Further comprising receiving means for receiving data transmitted from another device,
The electronic device according to claim 8, wherein the selection unit selects a functional unit file version to be read into a main storage device at the time of activation in accordance with data received by the reception unit.   The selection unit selects a version of a functional unit file to be read into a main storage device at startup based on whether or not a history of events occurring in the electronic device meets a predetermined condition. The electronic device according to any one of 1 to 4.   11. The function unit file according to claim 10, wherein the selection unit selects a version of the function unit file to be read into the main storage device at the time of activation based on whether or not an error history relating to a specific function satisfies a predetermined condition. Electronic equipment.   When an error relating to a specific function occurs more than a predetermined frequency, the selection means stores a version having a function of creating a log for debugging with respect to a function unit file relating to the specific function at the time of starting. 12. The electronic device according to claim 11, wherein the electronic device is selected as a plate to be read by the device.   When the error relating to a specific function does not occur more frequently than the predetermined frequency, the selection unit activates a version that does not have a function of creating a debug log for the function unit file related to the specific function. 12. The electronic device of claim 11, wherein the electronic device is selected as a plate that is sometimes read into the main memory. Verification means for verifying an electronic signature assigned to the functional unit file stored in the storage means;
Control means for controlling the startup processing of the electronic device according to the verification result by the verification means;
The electronic device according to claim 1, further comprising:   15. The electronic device according to claim 14, wherein the control unit performs control so as to stop activation processing of the electronic device when an electronic signature given to the functional unit file of the version selected by the selection unit is not a valid signature. apparatus.   15. The control unit according to claim 14, wherein when the electronic signature given to the functional unit file of the version selected by the selection unit is a valid signature, the control unit is controlled not to stop the activation process of the electronic device. Electronic equipment.   When the electronic signature given to the functional unit file of the version selected by the selecting unit is not a valid signature, the control unit replaces the functional unit file of the version selected by the selecting unit with the selecting unit. 15. The electronic device according to claim 14, wherein the electronic device controls so that a functional unit file of a version different from the version selected by the step is read into a main storage device during a startup process of the electronic device.   When the electronic signature given to the functional unit file of the version selected by the selecting unit is a valid signature, the functional unit file of the version selected by the selecting unit activates the electronic device. The electronic device according to claim 14, wherein the electronic device is controlled to be read into a main storage device during processing.

Images