JP2006164030A - Firmware update method of multi-function device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To return a multi-function device to a state before update without adding a memory for backup when the update of firmware fails. <P>SOLUTION: When the firmware of the multi-function device itself is transmitted to a server on a network, and the own firmware is updated to the other firmware via the network and a local interface, the firmware having been stored in the server device is read and is written as firmware if the writing processing of the other firmware does not complete. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to updating firmware that operates in a multifunction system or the like.

  Conventionally, when updating firmware of a multifunction device or the like, a flash ROM storing the firmware is replaced with another flash ROM storing new firmware, a serial interface such as RS232C, or a parallel interface such as IEEE 1284 Alternatively, it is common to use a method such as transferring new firmware via an interface of a device such as USB or IEEE 1394, and writing the transferred new firmware to the flash ROM.

Also, when adopting a mechanism to write new firmware via various interfaces, prepare a flash ROM with about twice the capacity of the firmware and write new firmware. The old firmware is saved in another area of the flash ROM, and then new firmware is written (written in the area currently used). The firmware was updated by writing new firmware to an area other than the area of the firmware being used via various interfaces and then copying it to the area currently being used (for example, (See Patent Document 1).
JP 2001-117780 A

  However, in the above-described conventional technology, when updating the firmware by transferring new firmware from outside the apparatus via various interfaces. If data transfer from the outside (firmware for new update) fails, or even if the transfer is successful, it fails when actually writing new firmware to the desired location (for example, the flash ROM firmware execution area) Old firmware (firmware currently in use) that has been backed up in another area inside the device, such as flash ROM, is written again to the desired location. In this case, the memory for backup of the firmware currently in use ( Since a flash ROM, a RAM, etc.) are always required, there is a problem that the memory that must be mounted by the device cannot be reduced.

  In order to solve the above-described problem, the present invention transfers the firmware (= old firmware) that is currently operating to an appropriate location such as a hard disk of a server on the network before executing the firmware update. Store and save. Of course, the address of the server that saved the old firmware, the directory information of the stored hard disk, etc. are stored.

  In this state, transfer the new firmware from various interfaces and update the firmware. However, the firmware update fails, for example, if the transfer of the new firmware fails or the writing to the desired location fails even if the transfer is successful. When this happens, the old firmware transferred (saved) to the hard disk or the like of the server on the network is read, written to a desired location, and reused.

  Or remember the address of a specific Web server where the new firmware is stored (for example, the Web server of the manufacturer of the device where the firmware is running), the directory or URL where the new firmware is stored, etc. If the firmware update fails, go to the web server and search for the new firmware that you need (or the same version of the firmware that is currently running), and download the desired firmware if it exists. And a means for writing to a desired location (starting up as new firmware).

  Even when new firmware is transferred via various interfaces according to the present invention and the firmware is updated, a storage area (such as a flash ROM for saving the current operating firmware or storing new firmware) There is no need to secure memory), so there is no need to secure memory just for firmware update, so it is possible to save extra memory (flash ROM, etc.) for storing firmware .

Example 1
The first embodiment will be described below with reference to the drawings.

  FIG. 1 shows the overall configuration of a multifunction device 100 in which the present invention is adopted.

  Reference numeral 101 denotes transmission / reception means for transmitting / receiving data to / from various interfaces such as USB and Ethernet (registered trademark) (various interfaces such as Ethernet are not shown). A system bus 102 connects various components of the multifunction device 100 such as a CPU, RAM, and ROM, which will be described later. A CPU 103 controls the operation of the multi-function device 100. Reference numeral 104 denotes a RAM for temporarily storing data and the like in processing executed by the multi-function device 100.

  Reference numeral 105 denotes nonvolatile storage means such as a ROM (or flash ROM) for storing programs (= firmware) necessary for the multi-function device 100 and various data. An image conversion unit 106 converts print data received from the transmission / reception unit 101 or image data read from the scanner 108 that can read an image into data in a format printable by the print engine 107. Reference numeral 109 denotes an operation panel including a display for displaying various information (internal information of the multifunction device, etc.) to a user who uses the multifunction device 100, a button for inputting setting values set by the user, a keyboard, and the like. .

  FIG. 3 is a diagram showing a state in which the multi-function device 100 adopting the present invention is connected to a network 301 such as a LAN via the transmission / reception means 101. Servers such as 302 and 303 and other PCs are also connected to a network such as a LAN. The network 301 is also connected to the Internet 305 via a gateway 304 (a device such as a router can connect the network 301 to another network). Further, another network 309 is connected to the Internet 305 via a gateway 306 similar to 305. Web servers and PCs as shown in 307 and 308 are also connected to another network 309.

  Although not shown here, it goes without saying that various networks other than another network 309 are connected to the Internet.

  Next, the operation of the first embodiment of the present invention will be described with reference to the flowcharts of FIGS.

  When updating the firmware, first, a place (hard disk or memory) for saving the currently operating firmware (= old firmware stored in the ROM 105) on the network 301 to which the multifunction device 100 is connected. Or other storage means) is searched (S201).

  If a place to save the old firmware is found, the process proceeds to S203. If no place is found, there is no place to save the old firmware to another server (307, 308) via the Internet. (S202). If there is no place to save the old firmware in either of the search results, the process proceeds to S215 via (4) (this process will be described later).

  If there is a place (server or the like) in which the old firmware is saved, the old firmware is read out from the ROM 105 and stored in that place (S203). It is checked whether the transfer of the old firmware to the server or the like is successful (S204). If the transfer is not successful, the process proceeds to S215 via (4) as in the case where the server is not found.

  If the old firmware has been successfully saved, various information is stored in the ROM 105 or RAM 104 so that the old firmware can be read later, such as the address of the saved server, the directory or URL of the disk storing the old firmware (S205). ).

  Next, the new firmware to be updated (usually upgraded firmware) is transferred (overwritten) to the ROM 105 via the transmission / reception means 101 (S206). There is no problem even if the transmission source is anywhere such as a PC on the network 301. At this time, among the old firmware stored in the ROM 105, the firmware area necessary for executing the minimum processing required at the time of update, such as access to the network, transmission / reception of data, and writing to the ROM, is stored on the ROM 105. The data is saved and saved in another area (or the new firmware is not overwritten even when new firmware is written in the ROM 105).

  In step S207, it is confirmed whether all the new firmware has been transferred and written in the ROM 105. If the transfer to the ROM 105 fails due to a transfer failure or the like, the process advances to step S209 via (2). If the transfer and writing to the ROM 105 are also successful, the checksum of the new firmware written in S208 is confirmed, and it is also checked whether there is any data omission or data corruption during transfer. If the new firmware is not correct as a result of the inspection, the process proceeds to S209 via (2) as in the case where the transfer fails.

  If it is confirmed that the new firmware is correctly written in the ROM 105 as a result of the inspection (via (5)), the process proceeds to S214, and the multi-function device 100 is restarted using the new firmware. Needless to say, it is possible to let the user choose whether to restart immediately.

  In addition, since the firmware was restarted with the new firmware, the firmware part necessary for executing the minimum processing required at the time of update, such as access to the network and transmission / reception of data and writing to the ROM, among the old firmware described above ( The portion which has not been overwritten) is no longer necessary, so this portion on the ROM 105 can also be used for another purpose.

  When transfer of new firmware or writing to the ROM 105 has failed (transition from S207, 208), in S209, the old firmware stored in S205 is stored from the location (such as the server 302 of the network 301). The firmware is transferred to the ROM 105. Also in the transfer of the old firmware, it is confirmed whether or not the transfer is successful (S210). If the transfer fails, the process proceeds to S213 via (3). If the old firmware has been successfully transferred, the checksum and the like are further confirmed in S211 to check whether the data is correct. If the data is not correct, the process proceeds to S213 as described above.

  If the old firmware has been correctly transferred to the ROM 105, the multifunction device 100 is restarted using the firmware (S212).

  If transfer of old firmware or storage in the ROM 105 fails, an error warning for the user is displayed (displayed on the operation panel 109 or the like) in S213 to notify that the firmware update has failed.

  In the process when the transfer of the old firmware fails in S202 and S204 described above (S215), a warning indicating that (transfer of the old firmware has failed) is displayed on the operation panel 109 or the like, and the user remains as it is. Whether to continue the firmware update is selected (S216). If the user selects to continue updating the firmware, the process proceeds to S217, and new firmware is transferred (transfer from the transfer source to the ROM 105). Also in this case, it is confirmed whether the transfer is successful (S218), data such as a checksum after the transfer is also checked (S219), and if transfer of new firmware fails, the process proceeds to S213 and an error is displayed. .

(Example 2)
A second embodiment will be described with reference to FIGS.

  When updating the firmware, the user first provides the address of the Web server (for example, provided by the manufacturer of the multi-function device 100) from which the new firmware to be updated is stored from the operation panel 109 or the like of the multi-function device 100. Information necessary for reading and transferring new firmware such as Web server address), directory, or URL is input and stored in the ROM 105 or the like (S401).

  Next, the new firmware to be updated (usually upgraded firmware) is transferred (overwritten) to the ROM 105 via the transmission / reception means 101 as in the first embodiment. However, in the case of the second embodiment, it is not necessary to save old firmware.

  If the transfer of new firmware fails or the transfer is successful but the data is not correct by a subsequent data check (checksum check etc.) (S403), the new firmware stored in S401 is stored. The stored location is searched from the network or the like based on the address information where the firmware is supposed to be stored (S404). If the server is not found as a result of searching according to the address information or the like, the process proceeds to S408.

  If a storage location (server or the like) is found based on the address information that seems to store the new firmware stored in S401, the new firmware is read from the storage location and transferred to the ROM 105 (S405). . When the transfer is not successful, or the data such as the checksum is not correctly checked even if the transfer is successful (S406). The process proceeds to S408.

  If the new firmware read from the server detected based on the address information that seems to store the new firmware stored in S401 and transferred to the ROM 105 is correct, the multifunction device is started with the new firmware. (S407).

  In S401, the user inputs various types of information directly from the operation panel 109. However, even if such information is input from the outside of the multi-function device 100 via the network 301 or other interfaces, the effect of the invention is obtained. There is no change.

(Example 3)
In the second embodiment, before starting the firmware update, information necessary for reading and transferring the new firmware such as the address, directory, or URL of the Web server that is supposed to store the new firmware to be updated is stored. Although it was input, it is determined that the transfer or storage of the new firmware has failed in S403, and even if a warning is displayed to the user at that timing and the above various information is input, the effect of the invention remains unchanged. .

Example 4
In the first to third embodiments, the multifunction device 100 is targeted. However, the present invention may be a single function device having only a single function, such as a printer or a facsimile.

The block diagram which shows the outline of the controller etc. of the multifunction apparatus which employ | adopted this invention Flowchart for explaining the first embodiment of the present invention Flowchart for explaining the first embodiment of the present invention Flowchart for explaining the first embodiment of the present invention The figure which shows the outline of the network environment etc. where the multi-function apparatus which employ | adopted this invention is connected Flowchart for explaining the second embodiment of the present invention. Flowchart for explaining the second embodiment of the present invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Multifunction apparatus 101 Transmission / reception means 102 which transmits / receives with various interfaces 102 CPU and system bus which connects various components 103 CPU
104 RAM
105 Nonvolatile storage means such as a flash ROM 106 Image conversion means for converting and outputting an image to a print engine 107 Print engine for printing 108 Scanner for reading an image 109 A display for a user to check the status of the device Operation panel 301 equipped with buttons that can be operated by the user 301 Network such as a LAN to which the multifunction device 100 adopting the present invention is connected 302 to 303 301 Servers connected to the LAN of the 301, other PCs, etc. A gateway such as a router for connecting a LAN and an external network such as the Internet 305 Internet etc. 306 305 A gateway for connecting a different LAN to the Internet etc. 307 to 308 Servers and other PC or the like that is connected to another LAN

Claims (3)

In the firmware update method of the multifunction device,
Means for transferring and storing the firmware of the multi-function device itself to a first server on a network;
Storage means for storing the address and directory of the first server storing the firmware;
When updating another firmware to its own firmware via a network or a local interface, if the writing process of the other firmware is not completed, the self stored in the first server A firmware update method for a multi-function device, which reads out its own firmware and executes it as new own firmware.   Before the update is executed, the address and directory information of the second server on the network storing the other firmware to be updated are stored, and then the firmware update is started. If the update of the firmware stored in the server fails, the new firmware is read out based on the address and directory information of the second server, and the update is executed using it. The method for updating firmware of a multi-function device according to claim 1.   The address and directory information of the second server on the network that seems to store the new firmware to be updated are manually input by the user from an operation panel or the like provided in the device for updating the firmware. The method for updating firmware of a multifunction device according to claim 2.

Images