Information processing apparatus, control method for information processing apparatus, and program
The information processing apparatus addresses the issue of firmware size exceeding RAM capacity post-upgrade by using sub-firmware copying and irreversible data erasure with backup and restore processes, ensuring device restart and reuse.
Patent Information
- Application Number
- JP2023073443
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-27
- Publication Date
- 2024-11-08
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
In image forming apparatuses, firmware upgrades can increase its size beyond the capacity of RAM, preventing the device from restarting after an irreversible information erasure function is executed, making it difficult to reuse.
An information processing apparatus with a non-volatile storage unit and a volatile storage unit, where firmware is divided into sub-firmware smaller than the volatile storage capacity, allowing comparison and copying to volatile storage if space is sufficient, and using a Sanitize command for irreversible data erasure with firmware backup and restore processes.
Enables the device to restart after irreversible data erasure by temporarily saving firmware, ensuring the device can be reused despite increased firmware size post-upgrade.
Smart Images

Figure 2024158325000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing device, a control method for an information processing device, and a program. [Background technology]
[0002] In an image forming apparatus capable of forming an image, information stored in the apparatus may be erased, for example, when the apparatus is disposed of or relocated. This can prevent information leakage. Some image forming apparatuses have a batch erase function that erases all information at once. The batch erase function initializes the settings of the image forming apparatus and erases information (data) that has been appropriately saved by a user's operation while the image forming apparatus is in use, and can return the image forming apparatus to the factory default state. For example, an SSD (Solid State Drive) may use a dedicated command when completely erasing information stored in a FLASH memory (non-volatile storage unit), that is, irrecoverably. This dedicated command conforms to a generally popular standard, and the specifications are set as a command that erases all information stored in the SSD at once. In addition, some image forming apparatuses have a dedicated SSD that appropriately saves information while the image forming apparatus is in use. In this case, the dedicated command can also be used to erase information.
[0003] In addition, some image forming devices have a single SSD that can store information appropriately by user operation while the image forming device is in use, and firmware for starting the image forming device is stored in advance. In such an image forming device, when information is erased using a dedicated command, the firmware is also erased in addition to the information stored in the SSD. An image forming device from which the firmware has been erased cannot be started, and as a result, it becomes difficult to reuse the device. Therefore, in order to leave specific information such as firmware, a technique is known in which the specific information is saved in RAM before the information is erased. This makes it possible to write the specific information saved in RAM back to the storage device after the information is erased. For example, Patent Document 1 discloses that when formatting a FLASH memory in a digital camera, a specific file stored in the FLASH memory is temporarily saved in RAM. This makes it possible to leave the specific file even after the contents of the FLASH memory are erased. In addition, as for the firmware of the image forming device, if the size of the firmware is sufficiently smaller than the size of the free space in the RAM, the firmware can be left by using a technique similar to that of Patent Document 1. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2005-149135 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, in recent digital devices such as image forming devices, when firmware is upgraded, functions may be added to the firmware. In this case, the size of the firmware may become larger than before the upgrade. Depending on the size of the firmware after the upgrade, it may become impossible to temporarily save the firmware in RAM. As a result, there is a problem that the digital device cannot be started up, making it difficult to reuse it.
[0006] The present invention has been made in view of the above problems, and has an object to provide an information processing device that can be restarted even if an information erasure function that erases information so that it cannot be restored is executed, and a control method and program for the information processing device. [Means for solving the problem]
[0007] In order to achieve the above-mentioned object, the information processing device of the present invention is an information processing device comprising: a non-volatile memory unit having a memory area for storing information and capable of executing an information erasure function for erasing the information stored in the memory area so that it cannot be restored; and a volatile memory unit, wherein the memory area stores firmware used to start up the information processing device as the information, and the firmware includes a sub-firmware whose size is smaller than the capacity of the volatile memory unit, and the information processing device is characterized in that it comprises a comparison means for comparing the size of the free space of the volatile memory unit with the size of the firmware prior to executing the information erasure function when executing the information erasure function, and a duplication means for copying the firmware to the volatile memory unit if the size of the free space is larger than the size of the firmware as a result of the comparison by the comparison means, and copying at least the sub-firmware of the firmware to the volatile memory unit if the size of the free space is smaller than the size of the firmware. Effect of the Invention
[0008] According to the present invention, even if an information erasure function that erases information so that it cannot be restored is executed, the device can be restarted. [Brief description of the drawings]
[0009] [Figure 1] 1 is a block diagram showing a hardware configuration of an image forming apparatus and its peripheral devices; [Diagram 2] FIG. 2 is a schematic diagram showing the contents stored in a non-volatile storage unit (SSD). [Diagram 3] 5A and 5B are schematic diagrams showing a state in which a volatile memory unit is used; [Figure 4] 13 is a flowchart showing a process for instructing execution of a batch erasure function. [Diagram 5] 5 is a flowchart showing a process performed at the time of start-up of the image forming apparatus. [Figure 6] 6 is a flowchart showing the process (normal startup process) in step S521 (subroutine) of the flowchart shown in FIG. 5. [Figure 7A] 6 is a flowchart showing the process (data erasure process) in step S510 (subroutine) of the flowchart shown in FIG. 5. [Figure 7B] 7B is a flowchart showing the process (firmware backup process) in step S705 (subroutine) of the flowchart in FIG. 7A. [Figure 7C] 7B is a flowchart showing the process (firmware restore process) in step S710 (subroutine) of the flowchart in FIG. 7A. [Figure 8] 6 is a flowchart showing the process (firmware download process) in step S517 (subroutine) of the flowchart shown in FIG. 5. [Figure 9A] FIG. 7B is a diagram showing an example of a message screen displayed in step S703 of the flowchart in FIG. 7A. [Figure 9B] FIG. 7B is a diagram showing an example of a message screen displayed in step S706 of the flowchart in FIG. 7A. [Figure 9C]FIG. 7D is a diagram showing an example of a message screen displayed in step S753 of the flowchart in FIG. 7C. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. However, the configurations described in the following embodiments are merely examples, and the scope of the present invention is not limited by the configurations described in the embodiments. For example, each part constituting the present invention can be replaced with any configuration that can perform the same function. In addition, any configuration may be added. FIG. 1 is a block diagram showing the hardware configuration of an image forming apparatus and its peripheral devices. The image forming apparatus 1 shown in FIG. 1 is an apparatus to which an information processing apparatus that processes various information is applied. In this embodiment, the image forming apparatus 1 is an MFP (Multi-Function Peripheral) and has a controller 100, a scanner device 106, a printer device 107, an operation unit 109, and an SSD 121. The scanner device 106 is a device that optically reads an image from a document and converts it into a digital image. The printer device 107 is a device that outputs a digital image on, for example, a paper medium. The operation unit 109 is an operation device for operating the image forming apparatus 1. The SSD 121 is a storage device that stores various firmware, digital images, and the like. The controller 100 is a computer that is communicatively connected to the scanner device 106, the printer device 107, the operation unit 109, and the SSD 121, and controls each device (module). The image forming device 1 can input and output digital images to and from a computer (not shown), which is one of external devices, via a network 108, issue jobs, and remotely manage the external device (not shown). The image forming device 1 is also communicatively connected to a server (external device) 105 via the network 108. The image forming device 1 has an update function that updates the firmware to a new version downloaded from the server 105. The server 105 stores a plurality of versions of firmware for the image forming device 1, from old versions to new versions. The image forming device 1 can also download a specific version of firmware other than the latest firmware.
[0011] The controller 100 is a general-purpose computer system. The controller 100 has a CPU (first CPU) 101, a boot ROM 102, a RAM 103, a PCI_Express_I / F (interface) 111, a sub CPU (second CPU) 112, a RAM 113, and an image processor 114. The controller 100 also has a scanner I / F (interface) 115, a printer I / F (interface) 116, and a reset circuit 122. The controller 100 also has a LAN_I / F (interface) 118, a USB_I / F (interface) 119, an operation unit I / F (interface) 124, and a bus bridge 125. The CPU 101, boot ROM 102, RAM 103, PCI_Express_I / F 111, LAN_I / F 118, USB_I / F 119, reset circuit 122, and operation unit I / F 124 are connected to each other so as to be able to communicate with each other via an internal bus (first bus) 104. The sub CPU 112, RAM 113, and image processor 114 are connected to each other so as to be able to communicate with each other via an internal bus (second bus) 117 that is different from the internal bus 104. In addition, the internal bus 104 and the internal bus 117 are connected to each other via a bus bridge 125.
[0012] The CPU 101 is a processor that performs overall control of the image forming apparatus 1. The boot ROM 102 stores an initial program called BIOS. The RAM 103 is a volatile storage unit that the CPU 101 uses as a main memory, and is composed of a volatile storage unit such as a DRAM. The sub-CPU 112 is a processor that performs partial control of the image forming apparatus 1. In this embodiment, the sub-CPU 112 controls the scanner device 106 and the printer device 107 when the image forming apparatus 1 executes a job. By having the sub-CPU 11 independent of the CPU 101, it is possible to realize real-time control of the scanner device 106 and the printer device 107. The RAM 113 is a volatile storage unit that the sub-CPU 112 uses as a main memory. The image processing processor 114 is an ASIC (Application Specific Integrated Circuit) for performing real-time digital image processing. The scanner device 106 is connected via a scanner I / F 115. The printer device 107 is connected via a printer I / F 116. The PCI_Express_I / F 111 is a bus interface for connecting various hardware devices that comply with the PCI Express standard. The SSD 121 is connected via the PCI_Express_I / F 111. The SSD 121 is a large-capacity, high-speed readable and writable non-volatile storage unit that complies with the industry standard NVMExpress standard. The SSD 121 is mainly used to store programs executed by the CPU 101 and image data when a job is executed. The programs include, for example, programs for causing the controller 100 to execute each unit and each means of the image forming apparatus 1 (a control method for an information processing apparatus).
[0013] The reset circuit 122 is a circuit that resets the operation of each hardware on the controller 100 and restarts the image forming apparatus 1. The CPU 101 can restart the image forming apparatus 1 by controlling the reset circuit 122. The reset signal 123 generated from the reset circuit 122 is a signal for resetting the sub CPU 112 and inhibiting the operation of the sub CPU 112. The sub CPU 112 does not start operating while the reset signal 123 is input. The reset signal 123 is automatically input to the sub CPU 112 when the power supply of the image forming apparatus 1 is turned on or when the image forming apparatus 1 is restarted by the reset circuit 122. The reset signal 123 is stopped by the control of the CPU 101. This stop allows the sub CPU 112 to start operating. A USB memory (auxiliary storage device) 120 conforming to the USB storage class standard is detachably connected to the controller 100 via a USB_I / F 119 that is a connection unit. Moreover, an operation unit 109 is connected to the controller 100 via an operation unit I / F 124. The operation unit 109 has an LCD panel 110 for displaying various information to a user who uses the image forming apparatus 1. The LCD panel 110 has a function as a touch panel. This allows the LCD panel 110 to receive operation instructions from the user. Moreover, the controller 100 is connected to a network 108 via a LAN_I / F (communication unit) 118.
[0014] FIG. 2 is a schematic diagram showing the contents stored in the non-volatile storage unit (SSD). As shown in FIG. 2(a), the SSD 121 has a storage area for storing various information. The storage areas include an area for storing a boot loader 201, a normal mode firmware area 202, a safe mode firmware area 203, a setting value area 204, a Java application installation area 205, and a data area 206. The boot loader 201 is a program for performing a process of loading an OS into a main memory (RAM 103) when the image forming apparatus 1 is started. The normal mode firmware area 202 is a storage area for storing (memorizing) firmware executed by the CPU 101 when the image forming apparatus 1 normally operates. The firmware is used to start the image forming apparatus 1. When the image forming apparatus 1 is started, the image forming apparatus 1 loads a program from the normal mode firmware area 202 into the RAM 103 and executes it with the CPU 101. This realizes various functions of the image forming apparatus 1.
[0015] The safe mode firmware area 203 is a storage area for storing firmware executed by the CPU 101 when the image forming apparatus 1 uses the update function. When the image forming apparatus 1 of the present embodiment uses the update function, the image forming apparatus 1 loads firmware different from that during normal operation from the safe mode firmware area 203 into the RAM 103 at startup and executes it with the CPU 101. This is a measure against the storage contents of the normal mode firmware area 202 becoming abnormal when, for example, an unexpected power outage occurs during firmware update. This makes it possible to prevent the storage contents of the safe mode firmware area 203, which is a storage area different from the normal mode firmware area 202, from being affected even if the storage contents of the normal mode firmware area 202 become abnormal. In addition, the image forming apparatus 1 can be restored by starting the image forming apparatus 1 using the firmware stored in the safe mode firmware area 203 and executing the update function again. In this embodiment, the boot loader 201, the program stored in the normal mode firmware area 202, and the program stored in the safe mode firmware area 203 are collectively referred to as "firmware." Moreover, the boot loader 201 and the programs stored in the safe mode firmware area 203 are collectively referred to as "sub-firmware (subset firmware)." Therefore, the firmware includes the sub-firmware.
[0016] The setting value area 204 is a storage area for storing the operation settings of the image forming apparatus 1. For example, the setting value area 204 stores setting values set by the user, internal operation flag information, and the like. The Java application installation area 205 is a storage area for storing applications (software) that add or expand functions executable by the image forming apparatus 1. Note that the sub-firmware is software different from the applications stored in the Java application installation area 205. In the image forming apparatus 1 of this embodiment, the user can install applications as necessary. This makes it possible to add functions to the image forming apparatus 1 or expand functions that the image forming apparatus 1 already has. In this embodiment, it is possible to install applications created in Java (registered trademark). The installed Java application is stored in the Java application installation area 205. The data area 206 is a storage area used for storing image data. For example, a document scanned by the scanner device 106 can be stored as image data in the data area 206. In addition, the data area 206 can also temporarily store a copy image when a copy job is executed.
[0017] As shown in FIG. 2B, the firmware stored in the normal mode firmware area 202 is composed of a plurality of executable programs such as an OS and application programs. In this embodiment, the firmware includes an OS 211, a boot control application 212, a sub-CPU firmware 213, an MFP application 214, and a batch erasure program 215. The OS 211 is an operating system for controlling each piece of hardware of the controller 100 by the CPU 101. For example, a general-purpose operating system such as Linux (registered trademark) is used as the OS 211. The boot control application 212 is an application program that is executed on the OS 211 and controls the boot process of the image forming apparatus 1. The boot control application 212 is first started after the boot of the OS 211 is completed. For example, the boot control application 212 corresponds to an init program of Linux. The sub-CPU firmware 213 is a program executed by the sub-CPU 112, and is loaded into the RAM 113 and executed when the image forming apparatus 1 is started. In the image forming apparatus 1, the scanner device 106 and the printer device 107 are controlled by the sub-CPU firmware 213, and thus the image forming apparatus 1 can execute jobs. The MFP application 214 is an application program for implementing various functions of the image forming apparatus 1, such as copying, printing, and saving scanned documents. The CPU 101 executes the MFP application 214, thereby executing various jobs in the image forming apparatus 1. Note that, in this embodiment, the MFP application 214 is configured as one program, but is not limited thereto, and may be configured as a plurality of programs, for example. The MFP application 214 may also include various data other than the programs, such as font data and display language translation data, for example.
[0018] The all-at-once erasure program 215 is an application program capable of executing a all-at-once erasure function (information erasure function) for erasing all information stored in the storage area of the SSD 121 in an unrecoverable manner, and is executed on the OS 211. By executing the all-at-once erasure program 215, it is possible to erase all image data and setting values stored by a user in the image forming apparatus 1, and to return the image forming apparatus 1 to a state equivalent to that at the time of shipment from the factory. The all-at-once erasure program 215 is configured as a program smaller than the MFP application 214, and is configured so as to require less memory (capacity) for execution. Note that the total size of these executable programs is smaller than the area size of the normal mode firmware area 202, but the size of the programs may increase or decrease when the version is upgraded by the update function.
[0019] 2(c), the safe mode firmware area 203 stores an OS 221, a boot control application 222, and an updater application 223. The OS 221 is an operating system for controlling each piece of hardware of the controller 100 by the CPU 101, and is a similar program to the OS 211. The boot control application 222 is also a similar program to the boot control application 212. The updater application 223 is an application program that is executed on the OS 221 to realize an update function. The updater application 223 is executed by the CPU 101 to realize a version upgrade of the firmware of the image forming apparatus 1.
[0020] As shown in FIG. 2(d), the set value area 204 stores a batch erase flag 231, a download flag 232, and firmware version information 233. The batch erase flag 231 is flag information for holding information on whether or not the execution of the batch erase function is requested by the user. The download flag 232 is flag information for holding information on whether or not the update function is executed and firmware is downloaded from the server 105. The firmware version information 233 holds the version of the firmware to be acquired from the server 105 when the update function is executed. Note that, in this embodiment, the information stored in the set value area 204 is the batch erase flag 231, the download flag 232, and the firmware version information 233, but is not limited to these. For example, information such as a set value for which copy, color copy or monochrome copy, is to be set as the initial setting may be stored in the set value area 204.
[0021] FIG. 3 is a schematic diagram showing the usage state of the volatile storage unit. In this embodiment, the volatile storage unit includes a RAM 103 and a RAM 113. The volatile storage unit is not limited to being composed of two RAMs, the RAM 103 and the RAM 113, and may be composed of, for example, three or more RAMs. The state shown in FIG. 3(a) is the usage state of the RAM 103 and the RAM 113 when the image forming apparatus 1 is operating normally. As described above, the CPU 101 and the RAM 103 (one of the RAMs) are connected to each other via the internal bus 104 so as to be able to communicate with each other. As shown in FIG. 3(a), the RAM 103, which is the main memory of the CPU 101, is used for an OS execution area 301 and an application execution area 302. The OS execution area 301 is a memory area for executing an operating system. This OS execution area 301 is used as an area for loading an OS program and is also used as a work memory required for the operation of the OS. The application execution area 302 is used as an area for loading an application program that runs on the OS and is also used as a work memory for the application program. Further, the sub CPU 112 and RAM 113 (the other RAM) are connected to each other so as to be able to communicate with each other via an internal bus 117. The RAM 113, which is the main memory of the sub CPU 112, is used for a sub CPU firmware execution area 303 and an image area 304. The sub CPU firmware execution area 303 is used as an area for loading the sub CPU firmware 213, and is also used as a work memory for the sub CPU firmware 213. The image area 304 is used for storing image data scanned by the scanner device 106 during job execution, image data to be printed by the printer device 107, etc.
[0022] The state shown in FIG. 3(b) is the usage state of the RAM 103 and the RAM 113 when the all-at-once erasure function is executed. As shown in FIG. 3(b), the application execution area 302 is a smaller area than the state shown in FIG. 3(a). The image forming apparatus 1 of the present embodiment is configured to execute the all-at-once erasure function in the application execution area 302 without executing the MFP application 214. The all-at-once erasure program 215 is a program that can operate with as little memory as possible. This allows the application execution area 302 to be set small. By reducing the application execution area 302, the save area 305a can be formed in the RAM 103 as an unused area (free area). In addition, the entire RAM 113 can be set as the save area 305b. The save area 305a and the save area 305b configure the save area 305 in which the firmware in the SSD 121 is temporarily saved when the all-at-once erasure function is executed. The image forming apparatus 1 of the present embodiment does not accept jobs while the all-at-once erasure function is being executed. This allows the entire RAM 113 to be allocated to the save area 305a. In this manner, in the image forming apparatus 1, the free space of the RAM 113 can be allocated to be larger than the free space of the RAM 103 when executing the batch erasing function.
[0023] FIG. 4 is a flowchart showing a process of instructing execution of the all-at-once erasure function. After the start-up of the image forming apparatus 1 is completed, the CPU 101 executes the MFP application 214. As a result, the image forming apparatus 1 waits for an execution instruction of the all-at-once erasure function from the user. As shown in FIG. 4, in step S401, the CPU 101 judges whether or not the user has instructed execution of the all-at-once erasure function. This judgment is made based on whether or not a predetermined execution start instruction has been input via the operation unit 109. Then, if it is judged as a result of the judgment in step S401 that an execution instruction has been given, the process proceeds to step S402. On the other hand, if it is judged as a result of the judgment in step S401 that an execution instruction has not been given, the process waits in step S401.
[0024] In step S 402 , the CPU 101 sets the batch erase flag 231 in the setting value area 204 .
[0025] In step S403, CPU 101 controls reset circuit 122 to restart image forming apparatus 1. The actual data erasure process is executed while image forming apparatus 1 is being restarted. This is because it is difficult to execute a job and a data erasure process simultaneously. Restarting also ensures that no job has been input. Then, after step S403 is executed, the process ends.
[0026] 5 is a flowchart showing the process at the time of start-up of the image forming apparatus. When the image forming apparatus 1 is started, it is the CPU 101 that starts operating first. In the initial state of the image forming apparatus 1, the sub CPU 112 is in a state in which the reset signal 123 is input. The start of operation of the sub CPU 112 is restricted until the CPU 101 controls the reset signal 123. As shown in FIG. 5, in step S501, the CPU 101 starts executing the BIOS, which is an initial program stored in the boot ROM 102.
[0027] In step S 502 , the CPU 101 loads the boot loader 201 from the SSD 121 into the RAM 103 , and starts execution of the boot loader 201 on the RAM 103 .
[0028] In step S503, CPU 101 determines whether download flag 232 is set in set value area 204. As described above, image forming apparatus 1 is configured to execute firmware different from that during normal operation by CPU 101 at startup when the update function is operated. Therefore, in step S503, firmware to be used for startup is determined based on download flag 232. Then, if it is determined that download flag 232 is set (set) as a result of the determination in step S503, the process proceeds to step S512. On the other hand, if it is determined that download flag 232 is not set as a result of the determination in step S503, the process proceeds to step S504.
[0029] In step S504, the CPU 101 selects the normal mode firmware area 202 as the storage area to be used for startup.
[0030] In step S 505 , the CPU 101 loads the OS 211 from the normal mode firmware area 202 into the RAM 103 , and starts execution of the OS 211 on the RAM 103 .
[0031] In step S 506 , the CPU 101 loads the launch control application 212 into the RAM 103 , and starts execution of the launch control application 212 on the RAM 103 .
[0032] In step S507, CPU 101 determines whether or not all-at-once erasure flag 231 is set, that is, whether or not execution of the all-at-once erasure function has been instructed. If it is determined in step S507 that all-at-once erasure flag 231 is set, the process proceeds to step S508. On the other hand, if it is determined in step S507 that all-at-once erasure flag 231 is not set, the process proceeds to step S520.
[0033] In step S508, CPU 101 selects the allocation of RAM 103 and RAM 113 to the allocation shown in Fig. 3(b), that is, the allocation in which save area 305 is formed. As described above, the allocation state during normal operation shown in Fig. 3(a) and the allocation state during execution of the all-at-once erase function shown in Fig. 3(b) differ from each other, particularly in the usage state of RAM 113. Therefore, it is preferable to determine whether the allocation method for RAM 103 and RAM 113 should be the state shown in Fig. 3(a) or the state shown in Fig. 3(b) before sub-CPU 112 starts operating when image forming apparatus 1 is started.
[0034] In step S 509 , the CPU 101 loads the all-at-once erasure program 215 into the RAM 103 , and starts the execution of the all-at-once erasure program 215 on the RAM 103 .
[0035] In step S510, CPU 101 executes a data erasure process, the details of which will be described later (see FIG. 7A).
[0036] In step S511, CPU 101 controls reset circuit 122 to restart image forming apparatus 1. After step S511 is executed, the process returns to step S501, and the subsequent steps are executed in sequence.
[0037] Furthermore, in step S512 after executing step S503, the CPU 101 selects the safe mode firmware area 203 as the storage area to be used for startup.
[0038] In step S513, the CPU 101 loads the OS 221 from the safe mode firmware area 203 into the RAM 103, and starts execution of the OS 221 on the RAM 103.
[0039] In step S 514 , the CPU 101 loads the launch control application 222 into the RAM 103 , and starts execution of the launch control application 222 on the RAM 103 .
[0040] In step S515, CPU 101 selects the allocation of RAM 103 and RAM 113 to the allocation state shown in FIG.
[0041] In step S 516 , the CPU 101 loads the update application 223 into the RAM 103 , and starts the execution of the update application 223 on the RAM 103 .
[0042] In step S517, the CPU 101 executes firmware download processing using the updater application 223. Details of this firmware download processing will be described later (see FIG. 8).
[0043] In step S518, the CPU 101 clears (drops) the download flag 232 in the setting value area 204.
[0044] In step S519, CPU 101 controls reset circuit 122 to restart image forming apparatus 1. After step S519 is executed, the process returns to step S501, and the subsequent steps are executed in sequence.
[0045] Furthermore, in step S520 after executing step S507, CPU 101 selects the allocation of RAM 103 and RAM 113 to the allocation state shown in FIG.
[0046] In step S521, CPU 101 executes a normal startup process, which will be described in detail later (see FIG. 6).
[0047] In step S522, CPU 101 starts accepting a job, and then the process ends.
[0048] Fig. 6 is a flowchart showing the process (normal startup process) in step S521 (subroutine) of the flowchart shown in Fig. 5. As shown in Fig. 6, in step S601, the CPU 101 loads the sub CPU firmware 213 from the SSD 121 to the RAM 113.
[0049] In step S602, the CPU 101 controls the reset signal 123 to start the operation of the sub CPU 112. This enables the sub CPU 112 to start the execution of the sub CPU firmware 213 on the RAM 113.
[0050] In step S 603 , the CPU 101 loads the MFP application 214 into the RAM 103 , and starts execution of the MFP application 214 on the RAM 103 .
[0051] In step S604, CPU 101 loads the Java application stored in Java application install area 205 into RAM 103, starts execution of the Java application, and then the process ends.
[0052] Fig. 7A is a flowchart showing the process (data erasure process) in step S510 (subroutine) in the flowchart shown in Fig. 5. As shown in Fig. 7A, in step S700, CPU 101 sets the allocation of RAM 103 and RAM 113 to the allocation in the state shown in Fig. 3(b), that is, the allocation in which save area 305 is formed (RAM save area formation process).
[0053] In step S701, the CPU 101 (comparison means) compares the size of the free space of the RAM 103 and the RAM 113, that is, the size of the save area 305, with the total size of the firmware stored in the SSD 121 (comparison step). The size of the save area 305 is calculated by subtracting the size of the OS execution area 301 and the size of the application execution area 302 from the size of the RAM 103, and adding the size of the RAM 113 to the result. In addition, for the size of the OS execution area 301 and the size of the application execution area 302, if the actual memory usage during the data erasure process can be measured, a measured value may be used, or a value based on a previously estimated value may be used. The total size of the firmware is calculated by adding up the actual sizes of the executable programs stored in each area of the boot loader 201, the normal mode firmware area 202, the safe mode firmware area 203, and the Java application installation area 205.
[0054] In step S702, CPU 101 determines whether the size of save area 305 is sufficiently large with respect to the total size of firmware. The size of save area 305 needs to be at least as large as the sum of the total size of firmware and the size of firmware version information 233. This is because save area 305 stores the value of firmware version information 233 in addition to firmware. Therefore, the size of save area 305 is determined to be sufficient when such a size relationship is satisfied. Then, if it is determined in step S702 that the size of save area 305 is sufficiently large, the process proceeds to step S705. On the other hand, if it is determined in step S702 that the size of save area 305 is not sufficiently large, the process proceeds to step S703.
[0055] In step S703, the CPU 101 controls the LCD panel 110 of the operation unit 109 to display a message prompting the connection of the USB memory 120 to the USB_I / F 119. The image forming apparatus 1 of the present embodiment is configured to be able to execute the batch erase function even when the size of the save area 305 is not large enough. In this configuration, the USB memory 120 needs to be connected to the USB_I / F 119. This allows the USB memory 120 to be used as a means for supplementing the insufficient storage capacity of the save area 305. Even when the USB memory 120 is not connected, it can be substituted by downloading firmware from the server 105 via the network 108. However, the process can be completed with fewer restarts when the USB memory 120 is connected. Therefore, the connection of the USB memory 120 is preferable for executing the batch erase function when the size of the save area 305 is not large enough. FIG. 9A is a diagram showing an example of a message screen displayed in step S703 of the flowchart in FIG. 7A. The message screen 900A shown in FIG. 9A includes a button 901 and a message 902. A message 902 is a message that prompts the user to connect the USB memory 120 to the USB_I / F 119. The user can instruct the data erasure process to continue by operating the button 901. The button 901 may be operated after the USB memory 120 is connected, or may be operated without the USB memory 120 being connected.
[0056] In step S704, CPU 101 determines whether or not button 901 on message screen 900A has been operated (pressed). If it is determined in step S704 that button 901 has been operated, the process proceeds to step S705. On the other hand, if it is determined in step S704 that button 901 has not been operated, the process remains in standby at step S704.
[0057] In step S705, the CPU 101 (copying means) executes firmware backup processing (copying step) for copying the firmware in the SSD 121 to the save area 305. Details of the firmware backup processing will be described later (see FIG. 7B).
[0058] In step S706, CPU 101 controls LCD panel 110 of operation unit 109 to display a message indicating that data is being erased. Fig. 9B is a diagram showing an example of a message screen displayed in step S706 of the flowchart in Fig. 7A. Message screen 900B shown in Fig. 9B includes message 903. Message 903 is a message indicating that data is being erased.
[0059] In step S707, CPU 101 transmits a data erasure command to SSD 121 to erase data stored in SSD 121. Specifically, CPU 101 transmits a "Sanitize command" defined in the NVMe standard to SSD 121. This Sanitize command erases all data stored in SSD 121 in an unrecoverable manner, that is, securely. This makes it possible to prevent information leakage, etc. Note that in step S707, since all storage contents of SSD 121 are erased, firmware of image forming apparatus 1 stored in SSD 121, setting values stored in setting value area 204, operational flag information, etc. are also erased.
[0060] In step S708, the CPU 101 determines whether the data erasure process of the SSD 121 has been completed. If it is determined in step S708 that the data erasure process has been completed, the process proceeds to step S709. On the other hand, if it is determined in step S708 that the data erasure process has not been completed, the process waits in step S708. Note that data erasure using the Sanitize command takes time, so it is preferable to wait for the completion of the data erasure process.
[0061] In step S709, the CPU 101 executes a disk formatting process on the SSD 121. When data is erased using the Sanitize command, all contents including management information of the file system are erased from the SSD 121. For this reason, in order to reuse the SSD 121, it is preferable to execute a disk formatting process.
[0062] In step S710, CPU 101 (restoration means) executes firmware restore processing to restore the firmware (at least the sub-firmware) copied to save area 305 in step S705 to SSD 121 (storage area). As described above, the firmware stored in SSD 121 has also been erased by erasing data from SSD 121. Therefore, image forming apparatus 1 cannot be used as it is. Therefore, by executing firmware restore processing, image forming apparatus 1 can be restored to a usable state. Details of firmware restore processing will be described later (see FIG. 7C).
[0063] With the above-mentioned configuration, in the image forming apparatus 1, when executing a batch deletion function for irretrievably deleting all data (information) including firmware stored in the SSD 121, the firmware can be temporarily saved prior to the execution of the function. This saving can be performed regardless of the size of the firmware. Then, by restoring the saved firmware, the image forming apparatus 1 can be restarted. This allows the image forming apparatus 1 to continue to be used. In addition, the RAM 113, which is the main memory of the sub-CPU 112, is also used as a saving area for the firmware. This allows the firmware to be sufficiently saved regardless of the size of the firmware.
[0064] Fig. 7B is a flowchart showing the process (firmware backup process) in step S705 (subroutine) of the flowchart in Fig. 7A. In the firmware backup process, CPU 101 temporarily saves the firmware stored in SSD 121 to save area 305. Note that since the size of the firmware may vary depending on the firmware version upgrade, it is not always possible to save the entire firmware to save area 305. Therefore, in image forming apparatus 1, a priority is assigned within the firmware and the firmware is saved to save area 305. Table 1 below lists the storage areas in SSD 121 in descending order of priority for saving to save area 305.
[0065] [Table 1]
[0066] As shown in Table 1, the Java application stored in the Java application install area 205 is set to have the lowest priority. The Java application is an additional application that the user installs as necessary, so it can be set to have the lowest priority. On the other hand, the boot loader 201 and the group of programs in the safe mode firmware area 203, that is, the sub-firmware, are set to have the highest priority. This is because the sub-firmware has a function for downloading firmware from the server 105, that is, for reinstalling firmware. Even if the firmware cannot be saved to the save area 305, the firmware downloaded from the server 105 can be reinstalled and the state before the deletion to the SSD 121 can be restored. Therefore, the sub-firmware is set to have a high priority. In addition, in the image forming apparatus 1, even if the storage capacity of the save area 305 is insufficient, if the USB memory 120 is connected, the USB memory 120 can be used as an additional save area.
[0067] As shown in FIG. 7B, in step S721, the CPU 101 saves the boot loader 201 in the save area 305.
[0068] In step S722, CPU 101 saves the group of programs (contents) in safe mode firmware area 203 to save area 305. Boot loader 201 and the group of programs stored in safe mode firmware area 203, i.e., sub-firmware, have limited functions, i.e., not many functions, and therefore their size is sufficiently smaller than the capacity of save area 305. This makes it possible to easily save the sub-firmware to save area 305.
[0069] In step S723, CPU 101 stores, in save area 305, version information of the firmware of image forming apparatus 1 at the time before data erasure from SSD 121 was performed, that is, currently stored in SSD 121. This version information is used when it is necessary to download firmware from server 105 (see FIG. 8). Note that the version information is stored, for example, in firmware version information 233 in setting value area 204.
[0070] In step S724, CPU 101 determines whether the programs (contents) of normal mode firmware area 202 can be stored in save area 305. This determination is made by comparing the remaining memory capacity of save area 305 with the size of the programs in normal mode firmware area 202. If the remaining memory capacity of save area 305 is larger than the size of the programs in normal mode firmware area 202, it is determined that the programs can be stored in save area 305. Then, if it is determined in step S724 that the programs can be stored in save area 305, the process proceeds to step S725. On the other hand, if it is determined in step S724 that the programs cannot be stored in save area 305, the process proceeds to step S726.
[0071] In step S725, CPU 101 saves the programs in normal mode firmware area 202 to save area 305, and the process proceeds to step S728.
[0072] In step S726, CPU 101 determines whether or not USB memory 120 is connected. If it is determined in step S726 that USB memory 120 is connected, the process proceeds to step S727. On the other hand, if it is determined in step S726 that USB memory 120 is not connected, the process proceeds to step S728.
[0073] In step S727, CPU 101 saves the programs in normal mode firmware area 202 to USB memory 120, and the process proceeds to step S728.
[0074] In step S728, CPU 101 determines whether the application (contents) in Java application install area 205 can be stored in save area 305. This determination is made by comparing the remaining storage capacity of save area 305 with the size of the application in Java application install area 205. If the remaining storage capacity of save area 305 is larger than the size of the application in Java application install area 205, it is determined that the application can be stored in save area 305. If the determination in step S728 indicates that the application can be stored in save area 305, the process proceeds to step S729. On the other hand, if the determination in step S728 indicates that the application cannot be stored in save area 305, the process proceeds to step S730.
[0075] In step S729, CPU 101 saves the application in Java application install area 205 to save area 305, and the process ends.
[0076] In step S730, CPU 101 determines whether or not USB memory 120 is connected. If it is determined in step S730 that USB memory 120 is connected, the process proceeds to step S731. On the other hand, if it is determined in step S730 that USB memory 120 is not connected, the process ends.
[0077] In step S731, the CPU 101 saves the application in the Java application install area 205 to the USB memory 120.
[0078] As described above, in the image forming apparatus 1, when the size of the save area 305 is sufficiently large compared to the total size of the firmware, a firmware backup process is executed to copy the firmware to the save area 305. Also, when the size of the save area 305 is smaller than the total size of the firmware and larger than the size of the sub-firmware, at least the sub-firmware of the firmware can be copied to the save area 305. Then, when the sub-firmware is copied to the save area 305, the part of the firmware excluding the sub-firmware, that is, the program group of the normal mode firmware area 202 can be copied to the USB memory 120. As a result, the entire firmware is copied, and the firmware can be quickly restored thereafter. Also, whether or not to save the sub-firmware of the firmware can be automatically selected according to the size of the firmware, the size of the RAM capacity, and whether or not the USB memory 120 is attached or detached. This makes it easy to perform a user operation when executing the batch erasure function.
[0079] Fig. 7C is a flowchart showing the process (firmware restore process) in step S710 (subroutine) in the flowchart of Fig. 7A. As shown in Fig. 7C, in step S741, the CPU 101 restores the boot loader 201 in the SSD 121. This restoration is performed by writing the boot loader 201 saved in the save area 305 back to the SSD 121.
[0080] In step S742, the CPU 101 restores the safe mode firmware area 203 in the SSD 121. This restoration is performed by writing back to the SSD 121 the group of programs in the safe mode firmware area 203 that have been saved in the save area 305.
[0081] In step S743, CPU 101 determines whether or not the programs in normal mode firmware area 202 have been saved to save area 305. If it is determined in step S743 that the programs have been saved to save area 305, processing proceeds to step S744. On the other hand, if it is determined in step S743 that the programs have not been saved to save area 305, processing proceeds to step S745.
[0082] In step S744, the CPU 101 restores the programs in the normal mode firmware area 202 that have been saved in the save area 305 to the SSD 121, and proceeds to process step S749.
[0083] In step S745, CPU 101 determines whether or not the programs in the normal mode firmware area 202 have been saved to the USB memory 120. If the USB memory 120 is not connected in step S745, CPU 101 determines that the programs in the normal mode firmware area 202 have not been saved to the USB memory 120. If it is determined in step S745 that the programs have been saved to the USB memory 120, the process proceeds to step S746. On the other hand, if it is determined in step S745 that the programs have not been saved to the USB memory 120, the process proceeds to step S747.
[0084] In step S746, the CPU 101 restores the programs in the normal mode firmware area 202 that have been saved in the USB memory 120 to the SSD 121, and the process proceeds to step S749.
[0085] In step S 747 , the CPU 101 writes the firmware version information stored in the save area 305 to the firmware version information 233 in the setting value area 204 .
[0086] In step S748, CPU 101 sets download flag 232, and the process proceeds to step S749. The process in step S748 is a process for downloading firmware from server 105 and restoring the programs in normal mode firmware area 202 in a process subsequent to this process.
[0087] In step S749, CPU 101 determines whether or not the application in Java application install area 205 has been saved to save area 305. If it is determined in step S749 that the application has been saved to save area 305, the process proceeds to step S750. On the other hand, if it is determined in step S749 that the application has not been saved to save area 305, the process proceeds to step S751.
[0088] In step S750, the CPU 101 restores the application in the Java application install area 205 that has been saved in the save area 305 to the SSD 121, and the process ends.
[0089] In step S751, CPU 101 determines whether or not the application in Java application install area 205 has been saved to USB memory 120. If USB memory 120 is not connected in step S751, CPU 101 determines that the application in Java application install area 205 has not been saved to USB memory 120. If it is determined in step S751 that the application has been saved to USB memory 120, processing proceeds to step S752. On the other hand, if it is determined in step S751 that the application has not been saved to USB memory 120, processing proceeds to step S753.
[0090] In step S752, the CPU 101 restores the application in the Java application install area 205 that has been saved in the USB memory 120 to the SSD 121, and the process ends.
[0091] In step S753, the CPU 101 controls the LCD panel 110 of the operation unit 109 to display a message prompting the user to reinstall the Java application. After step S753 is executed, the process ends. FIG. 9C is a diagram showing an example of a message screen displayed in step S753 of the flowchart in FIG. 7C. The message screen 900C shown in FIG. 9C includes a message 904. The message 904 is a message prompting the user to reinstall the Java application. The Java application is installed by the user as necessary. For example, a third-party Java application may be installed. In this case, the Java application is not limited to being automatically reinstalled via the network 108. For example, if the application in the Java application installation area 205 has not been saved to either the save area 305 or the USB memory 120, it is preferable to display a message prompting the user to manually reinstall the Java application.
[0092] FIG. 8 is a flowchart showing the process (firmware download process) in step S517 (subroutine) of the flowchart shown in FIG. 5. As shown in FIG. 8, in step S801, the CPU 101 checks the contents of the firmware version information 233 in the set value area 204. The updater application 223 is a program that realizes an update function for updating the firmware of the image forming apparatus 1 to a new version, and also performs part of the operation of the firmware restoration function when executing the batch deletion function. In this embodiment, firmware version information is stored in the firmware version information 233. In this case, the updater application 223 operates as a firmware restoration function. Note that, when firmware version information is not stored in the firmware version information 233, the updater application 223 is configured to operate as an update function.
[0093] In step S802, CPU 101 determines whether firmware version information is stored in firmware version information 233. If it is determined in step S802 that version information is stored, the process proceeds to step S804. On the other hand, if it is determined in step S802 that version information is not stored, the process proceeds to step S803.
[0094] As described above, server 105 stores in advance a plurality of versions of firmware for image forming apparatus 1, from old to new. Then, in step S803, CPU 101 downloads the latest version of firmware from server 105 via network 108, and the process proceeds to step S805.
[0095] In step S804, the CPU 101 downloads from the server 105 the firmware corresponding to the version stored in the firmware version information 233, and the process proceeds to step S805.
[0096] In step S805, the CPU 101 writes the firmware downloaded in step S803 or step S804 to the normal mode firmware area 202 in the SSD 121.
[0097] In step S806, CPU 101 clears the contents of firmware version information 233, and the process ends. With the above-described configuration, firmware can be reinstalled.
[0098] The disclosure of this embodiment includes the following configuration, method, and program. (Configuration 1) An information processing device including: a non-volatile storage unit having a storage area for storing information and capable of executing an information erasure function for irretrievably erasing the information stored in the storage area; and a volatile storage unit, firmware used to start up the information processing device is stored in the storage area as the information; the firmware includes a sub-firmware having a size smaller than a capacity of the volatile storage unit; The information processing device includes: a comparison means for comparing a size of a free space in the volatile storage unit with a size of the firmware prior to the execution of the information erasing function when the information erasing function is executed; and a copying means for copying the firmware to the volatile storage unit when the size of the free space is larger than the size of the firmware as a result of the comparison by the comparison means, and for copying at least the sub-firmware of the firmware to the volatile storage unit when the size of the free space is smaller than the size of the firmware. (Configuration 2) The information processing device described in configuration 1, characterized in that the copying means copies the sub-firmware to the volatile memory unit when the size of the free space is smaller than the size of the firmware and larger than the size of the sub-firmware. (Configuration 3) An information processing device according to configuration 1 or 2, further comprising a restoration means for restoring at least the sub-firmware copied in the volatile memory unit to the memory area after the information erasure function is executed. (Configuration 4) The information processing device according to configuration 3, wherein the sub-firmware has a function for reinstalling the firmware after restoration to the storage area. (Configuration 5) A communication unit that is communicably connected to an external device that stores the firmware in advance, 5. The information processing apparatus according to configuration 4, wherein the sub-firmware acquires the firmware from the external device via the communication unit and performs the reinstallation. (Configuration 6) The non-volatile storage unit is capable of storing software that adds or expands functions that can be executed by the information processing device, 6. The information processing device according to any one of configurations 1 to 5, wherein the sub-firmware is different from the software. (Configuration 7) The information processing device according to any one of configurations 1 to 6, wherein the volatile storage unit is composed of at least two RAMs. (Configuration 8) A first CPU that performs overall control of the information processing device, and a second CPU that performs partial control of the information processing device, The information processing device according to configuration 7, wherein one of the two RAMs is communicatively connected to the first CPU via a first bus, and the other RAM is communicatively connected to the second CPU via a second bus different from the first bus. (Configuration 9) The information processing apparatus according to configuration 8, wherein when the information erasing function is executed, the copying means allocates a larger free space to the other RAM than to the one RAM. (Configuration 10) A connection unit to which an auxiliary storage device is detachably connected, The information processing device described in any one of configurations 1 to 9, characterized in that, when the size of the free space is smaller than the size of the firmware, the copying means copies the sub-firmware to the volatile storage unit, and copies the portion of the firmware excluding the sub-firmware to the auxiliary storage device connected to the connection unit. (Method 1) A method for controlling an information processing device including a non-volatile storage unit having a storage area for storing information and capable of executing an information erasure function for irretrievably erasing the information stored in the storage area, and a volatile storage unit, comprising: firmware used to start up the information processing device is stored in the storage area as the information; the firmware includes a sub-firmware having a size smaller than a capacity of the volatile storage unit; The method for controlling the information processing device includes: a comparison step of comparing a size of a free space in the volatile storage unit with a size of the firmware prior to executing the information erasing function when the information erasing function is executed; a copying process for copying the firmware to the volatile storage unit when the size of the free space is larger than the size of the firmware as a result of the comparison in the comparison process, and copying at least the sub-firmware of the firmware to the volatile storage unit when the size of the free space is smaller than the size of the firmware. (Program 1) A program for causing a computer to execute each of the means of the information processing device according to any one of configurations 1 to 10.
[0099] Although the preferred embodiment of the present invention has been described above, the present invention is not limited to the above-mentioned embodiment, and various modifications and changes are possible within the scope of the gist. The present invention can also be realized by a process in which a program that realizes one or more functions of the above-mentioned embodiment is supplied to a system or device via a network or a storage medium, and one or more processors of a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (for example, ASIC) that realizes one or more functions. In addition, as an application example of the information processing device, although the image forming device was used in the above-mentioned embodiment, it is not limited to this, and may be, for example, a personal computer, a tablet terminal, a smartphone, etc. In addition, in the above-mentioned embodiment, the CPU 101 has a function as a comparison means that compares the size of the save area 305 with the size of the firmware, and a copy means that copies the firmware in the SSD 121 to the save area 305, but is not limited thereto. For example, a part that functions as a comparison means and a part that functions as a copy means may be provided. In addition, in the present embodiment, an SSD based on the NVMe standard is used, but this is not limited thereto. For example, an SSD or a hard disk device that complies with the SATA (Serial AT Attachment) standard may be used. In the present embodiment, the Sanitize command is used as a method for erasing data stored in the SSD, but the method is not limited to this. [Explanation of symbols]
[0100] 1. Image forming device 101 CPU (1st CPU) 103 RAM 112 Sub CPU (2nd CPU) 113 RAM 121 SSD 201 Bootloader 202 Normal mode firmware area 203 Safe Mode Firmware Area 305 Evacuation area
Claims
1. An information processing device including: a non-volatile storage unit having a storage area for storing information, the non-volatile storage unit being capable of executing an information erasure function for irretrievably erasing the information stored in the storage area; and a volatile storage unit, firmware used to start up the information processing device is stored in the storage area as the information; the firmware includes a sub-firmware having a size smaller than a capacity of the volatile storage unit; The information processing device includes: a comparison means for comparing a size of a free space in the volatile storage unit with a size of the firmware prior to the execution of the information erasing function when the information erasing function is executed; and a copying means for copying the firmware to the volatile storage unit when the size of the free space is larger than the size of the firmware as a result of the comparison by the comparison means, and for copying at least the sub-firmware of the firmware to the volatile storage unit when the size of the free space is smaller than the size of the firmware.
2. 2. The information processing apparatus according to claim 1, wherein said copying means copies the sub-firmware to said volatile storage unit when the size of said free space is smaller than the size of said firmware and is larger than the size of said sub-firmware.
3. 2. The information processing apparatus according to claim 1, further comprising a restoration unit that restores at least the sub-firmware copied in the volatile storage unit to the storage area after the information erasing function is executed.
4. 4. The information processing apparatus according to claim 3, wherein the sub-firmware has a function for reinstalling the firmware after restoration to the storage area.
5. a communication unit communicably connected to an external device that has the firmware pre-stored therein; 5. The information processing apparatus according to claim 4, wherein the sub-firmware acquires the firmware from the external device via the communication unit and performs the reinstallation.
6. the non-volatile storage unit is capable of storing software that adds or expands functions that can be executed by the information processing device; 2. The information processing apparatus according to claim 1, wherein the sub-firmware is different from the software.
7. 2. The information processing apparatus according to claim 1, wherein the volatile storage unit is composed of at least two RAMs.
8. a first CPU that performs overall control of the information processing device, and a second CPU that performs partial control of the information processing device; 8. An information processing device according to claim 7, wherein one of the two RAMs is communicatively connected to the first CPU via a first bus, and the other RAM is communicatively connected to the second CPU via a second bus different from the first bus.
9. 9. The information processing apparatus according to claim 8, wherein, when the information erasing function is executed, the copying means allocates a larger free space to the other RAM than to the one RAM.
10. a connection section to which an auxiliary storage device is detachably connected, The information processing device according to claim 1, characterized in that, when the size of the free space is smaller than the size of the firmware, the copying means copies the sub-firmware to the volatile storage unit, and copies the portion of the firmware excluding the sub-firmware to the auxiliary storage device connected to the connection unit.
11. A method for controlling an information processing device including a non-volatile storage unit having a storage area for storing information and capable of executing an information erasure function for irretrievably erasing the information stored in the storage area, and a volatile storage unit, comprising: firmware used to start up the information processing device is stored in the storage area as the information; the firmware includes a sub-firmware having a size smaller than a capacity of the volatile storage unit; The method for controlling the information processing device includes: a comparison step of comparing a size of a free space in the volatile storage unit with a size of the firmware prior to executing the information erasing function when the information erasing function is executed; a copying process for copying the firmware to the volatile storage unit when the size of the free space is larger than the size of the firmware as a result of the comparison in the comparison process, and copying at least the sub-firmware of the firmware to the volatile storage unit when the size of the free space is smaller than the size of the firmware.
12. 2. A program for causing a computer to execute each of the means of the information processing apparatus according to claim 1.
Citation Information
Patent Citations
Electronic apparatus, program and method for initialization
JP2005149135A
