JP2007310695A - Embedded equipment and method for writing firmware to embedded equipment - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily take countermeasures against trouble of firmware of embedded equipment. <P>SOLUTION: When firmware is written to a digital multifunction machine 10, an execution file of firmware is transferred to the digital multifunction machine 10 to rewrite an execution file of firmware written in a flash memory 121 (step S101). Next, it is determined whether source codes should be preserved in the digital multifunction machine 10 or not, and source codes for forming the execution file transferred to the digital multifunction machine 10 in the step S101 are preserved when the source codes should be preserved ("YES" in step S102). A shared folder on a network is designated (step S103), and source codes in the designated shared folder are transferred to the digital multifunction machine 10, so that the source codes are copied to a CF card 60 mounted on a CF interface 130 (step S104). <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an embedded device and a method for writing firmware to the embedded device.

  Conventionally, countermeasures for malfunctions in firmware of embedded devices have been performed by finding and debugging the source code of the firmware with a defect, generating a new execution file from the source code after debugging, and writing it in the embedded device.

  Patent Document 1 is a prior art document related to the present invention, and relates to a technique for accurately accepting a program upgrade instruction.

JP 2004-310231 A

  However, the conventional technique has a problem in that it is difficult to take measures against a malfunction of the firmware when the source code of the firmware is lost. Such a problem may occur when it is necessary to take measures against a malfunction of firmware written in an old embedded device. In addition, with the conventional technology, there is a problem that it is difficult to take measures against firmware defects even when the correspondence between the source code and the executable file becomes unclear as a result of repeated firmware upgrades. .

  The present invention has been made to solve these problems, and it is an object of the present invention to facilitate countermeasures against malfunctions in firmware of embedded devices.

  In order to solve the above-mentioned problem, according to the first aspect of the present invention, a firmware execution file that defines the operation of an embedded device is stored in the first storage means of the embedded device so as to be executable by a computer built in the embedded device. A method of writing firmware to the embedded device, comprising: a first storage step of storing the source code that is the basis for generating the execution file in a second storage unit of the embedded device. .

  The invention of claim 2 is the method of writing firmware to the embedded device according to claim 1, wherein the source code stored in the second storing step is encrypted.

  According to a third aspect of the present invention, the source code stored in the second storage step is specified based on information on correspondence between firmware and source code. This is a firmware writing method.

  According to a fourth aspect of the present invention, there is provided a first storage means for storing an execution file of firmware defining the operation so as to be executable by a built-in computer, and a second storage for storing a source code as a basis for generating the execution file. And an embedded device.

  The invention of claim 5 is the embedded device according to claim 4, wherein the second storage means is a recording medium removable from the embedded device.

  The invention of claim 6 is the embedded device according to claim 4, wherein the second storage means is accessible from outside the embedded device.

  According to the first to sixth aspects of the present invention, since the source code that is the basis for generating the firmware execution file can be obtained from the second storage means of the embedded device, it is easy to take measures against the firmware malfunction.

  According to the invention of claim 2, the source code can be kept secret.

  According to the invention of claim 3, it becomes easy to store an appropriate source code in the second storage means.

  According to the invention of claim 5 or claim 6, it becomes easy to refer to the source code.

<1 Firmware development system configuration>
FIG. 1 is a block diagram illustrating a desirable configuration of a firmware development system 1A that defines the operation of the digital multifunction peripheral 10.

  As shown in FIG. 1, the development system 1A includes a digital multifunction peripheral 10 to which the developed firmware is applied, a development personal computer (hereinafter referred to as “development PC”) 20 on which the firmware is developed, and a digital complex. And a network 30 that connects the machine 10 and the development PC 20 so that they can communicate with each other.

  The digital multifunction device 10 operates as an embedded device having a copy function, a fax function, a scanner function, a printer function, and the like by the microcomputer 110 executing the firmware written in the flash memory 121 and performing overall control of each configuration. . The digital multi-function peripheral 10 includes a compact flash (registered trademark) interface (hereinafter referred to as “CF interface”) 130 to which a compact flash (registered trademark) card (hereinafter referred to as “CF card”) 60 can be attached and detached. The digital multi-function peripheral 10 can access the CF card 60 attached to the CF interface 130.

  The development PC 20 is used to edit the source code, an editor 201, a compiler 202 used to compile the source code and generate an object code, and link the object code to generate an execution file. An FTP program 204 and the like used for transferring files via the linkage editor 203 and the network 30 are installed in a general personal computer. Further, the development PC 20 also includes a CF interface 211 to which the CF card 60 can be attached and detached. The development PC 20 can access the CF card 60 attached to the CF interface 211.

  The developer of the firmware of the digital multi-function peripheral 10 edits the firmware source code with the editor 201 on the development PC 20, compiles the edited source code with the compiler 202, generates an object file, and generates the generated object file. Are linked by the linkage editor 203 to obtain a firmware execution file. Note that the firmware source code is stored in a shared folder (not shown) on the network 30 for each group that is the basis for generating one executable file.

<2 Digital MFP configuration>
Next, the configuration of the digital multifunction peripheral 10 will be described with reference to the block diagram of FIG.

  As shown in FIG. 2, the digital multi-function peripheral 10 includes an MPU (microprocessor unit) 111, a ROM 112, and a RAM 113. The microcomputer 110 realized by the MPU 111, the ROM 112, and the RAM 113 executes the firmware stored in the flash memory 121, thereby controlling each configuration of the digital multifunction peripheral 10 and realizing various functions of the digital multifunction peripheral 10. ing.

  The flash memory 121 of the digital multi-function peripheral 10 is a non-volatile memory in which stored contents can be rewritten, and stores various types of information that should be retained continuously. Further, the image memory 122 of the digital multi-function peripheral 10 temporarily stores an image to be processed by the digital multi-function peripheral 10 as image data.

  The digital multifunction peripheral 10 includes an image reading unit 123 and an image recording unit 124. The image reading unit 123 reads an image drawn on a document by a CCD (Charge Coupled Device) image sensor or the like, and generates image data related to the image. The image reading unit 123 can read an image drawn on a document by an ADF (Automatic Document Feeder) method or an FBS (Flat Bed Scanner) method. The image recording unit 124 forms an image related to image data on a recording medium by an electrophotographic method.

  The digital multi-function peripheral 10 is provided with an operation unit 125 that is an operation target and a display unit 126 that displays information in a visible manner as user interfaces. In the digital multi-function peripheral 10, a liquid crystal touch panel display is adopted as the display unit 126, and the display unit 126 also serves as a part of the operation unit 125.

  The network interface 127 connects the digital multi-function peripheral 10 to the network 30 by, for example, Ethernet (registered trademark).

  An NCU (Network Control Unit) 128 and a MODEM (Modem DEModulator) 129 are used for transmission / reception of fax images via the public switched telephone network 91. The NCU 128 controls connection to the public switched telephone network 91. The NCU 128 has a function of transmitting a dial signal corresponding to a telephone number of a communication destination and a function of detecting an incoming call. MODEM 129 is based on the fax transmission control procedure according to ITU (International Telecommunication Union) -T recommendation T.30. 17, V. 27ter, V.L. The transmission data is modulated and the received data is demodulated in accordance with 29 or the like. Alternatively, MODEM 129 can add V.V. 34, modulation of transmission data and demodulation of reception data are performed.

  As described above, the digital multifunction machine 10 includes the CF interface 130 to which the CF card 60 can be attached and detached. The digital multi-function peripheral 10 can access the CF card 60 attached to the CF interface 130.

  In the copy mode, the digital multi-function peripheral 10 reads an image drawn on a document using the image reading unit 123, and forms the image on a recording medium such as a recording paper using the image recording unit 124. Copy the image to the recording medium.

  In the fax mode, the digital multi-function peripheral 10 reads an image drawn on a document using the image reading unit 123 and transmits image data related to the image to another fax machine using the NCU 128 and MODEM 129 (fax transmission). . The digital multi-function peripheral 10 forms an image related to the image data transmitted from another fax machine on a recording medium using the image recording unit 124 (fax reception). The digital multi-function peripheral 10 uses the G3 method or the super G3 method for sending and receiving faxes using the public switched telephone network 91.

  In the scanner mode, the digital multi-function peripheral 10 reads an image on a document using the image reading unit 123 and stores image data related to the image in the built-in flash memory 121.

  In the printer mode, the digital multi-function peripheral 10 receives image data transmitted from the client computer via the network 30 and forms an image related to the image data on a recording medium using the image recording unit 124.

<3 Writing firmware to the digital MFP>
FIG. 3 is a flowchart showing a procedure for writing firmware to the digital multi-function peripheral 10.

  As shown in FIG. 3, when writing firmware to the digital multi-function peripheral 10, first, the FTP program 204 is started and the firmware execution file is transferred to the digital multi-function peripheral 10, thereby being written into the flash memory 121. The firmware execution file is rewritten (step S101).

  Subsequently, it is determined whether or not the source code is to be stored in the digital multi-function peripheral 10, and when it is stored ("YES" in step S102), the execution file transferred to the digital multi-function peripheral 10 in step S101 is generated. A shared folder on the network in which the source code that is the basis of the file is stored is designated (step S103), and the source code in the designated shared folder is transferred to the digital multi-function peripheral 10, whereby the source code is transferred to the CF interface. Copy to the CF card 60 attached to 130 (step S104). In step S104, if the source code is encrypted and the encrypted source code is written to the CF card 60, the source code can be kept secret.

  As a result of such firmware writing, a firmware execution file is written to the flash memory 121 in the digital multi-function peripheral 10, and a source card that is the basis for generating the execution file is a CF card mounted on the CF interface 130. 60 will be written.

  In such a digital multi-function peripheral 10, when it is necessary to take measures against firmware malfunctions, the CF card 60 attached to the CF interface 130 is accessed via the network 30, or the CF card 60 is digitally By removing the CF interface 130 of the MFP 10 and attaching it to the CF interface 211 of the development PC 20 for access, the source code that is the basis for generating the firmware execution file can be obtained. Can be easily performed.

<4 Modification>
In the above description, the writing of firmware to the digital multifunction peripheral 10 has been described as an example. However, the present invention can also be applied to the writing of firmware to an embedded device other than the digital multifunction peripheral 10.

  In the above description, the source code that is the basis for generating the firmware execution file is written to the CF card 60 attached to the CF interface 130. The source code is written to the CF interface 130. It is not limited to the CF card 60. That is, a recording medium other than the CF card 60, for example, a flash memory such as an SD memory card, an xD picture card (registered trademark), a memory stick, or a USB (Universal Serial Bus) storage (particularly a USB flash memory) can be attached and detached. The interface may be provided in the digital multi-function peripheral 10 and the source code may be written on a recording medium attached to the interface. Alternatively, the source code may be written in the flash memory 121 or the like accessible from the outside via the network 30.

  In the above description, the shared folder on the network where the source code is stored is specified in step S103. Instead, the information on the correspondence between the firmware and the source code is referred to, and based on the information. By specifying the source code to be written to the CF card 60 attached to the CF interface 130, an appropriate source code can be automatically written to the CF card 60 attached to the CF interface 130.

1 is a block diagram illustrating a desirable configuration of a firmware development system 1A for a digital multifunction peripheral 10. FIG. 1 is a block diagram showing a configuration of a digital multifunction machine 10. 5 is a flowchart illustrating a procedure for writing firmware to a digital multifunction peripheral.

Explanation of symbols

1A Development System 10 Digital MFP 20 Development PC
30 network 60 CF card 110 microcomputer 121 flash memory 130 CF interface

Claims (6)

A first storage step of storing an execution file of firmware defining the operation of the embedded device in the first storage means of the embedded device so as to be executable by a computer built in the embedded device;
A second storage step of storing the source code that is the basis for generating the executable file in the second storage means of the embedded device;
A method for writing firmware to an embedded device.   The method for writing firmware to an embedded device according to claim 1, wherein the source code stored in the second storing step is encrypted.   The method for writing firmware to an embedded device according to claim 1 or 2, wherein the source code stored in the second storage step is specified based on information on correspondence between firmware and source code. First storage means for storing an executable file of firmware defining operation so as to be executable by a built-in computer;
Second storage means for storing source code that is the basis for generating the executable file;
Embedded equipment with   The embedded device according to claim 4, wherein the second storage unit is a recording medium removable from the embedded device. The embedded device according to claim 4, wherein the second storage unit is accessible from outside the embedded device.

Images