JP2008152793A - Image forming apparatus, and program update method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image forming apparatus and a method for acquiring a storage area avoiding that the type of image data cannot be converted as a memory cannot be acquired. <P>SOLUTION: This image forming apparatus includes one or more processing units which perform processes concerning image formation, a control unit which performs communications with the processing units directly or via the other processing units, and a program which operates the processing units and the control unit. The apparatus has an update program acquiring unit that acquires an update program for updating programs and a program update unit that updates the program of one of the processing units to the update program in the order of the number of the processing units through which the one of the processing units and the control unit communicate with each other. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to updating one or more programs, and more particularly to an image forming apparatus that updates a program and a program updating method thereof.

  In recent years, there has been known an image forming apparatus (hereinafter referred to as a multifunction peripheral) in which functions of apparatuses such as a facsimile machine, a printer, a copy machine, and a scanner are housed in a single casing. In this multi-function apparatus, a display unit, a printing unit, an imaging unit, and the like are provided in one casing, and four types of applications corresponding to a facsimile, a printer, a copy, and a scanner are provided. Operates as a printer, copy and scanner.

  As described above, since the multi-function apparatus is operated by various applications and modules that execute processing based on the program, a new function is added by updating the program written in the NV-RAM or the like. be able to.

  This program update processing may be performed by connecting to a server storing the update program via a network such as the Internet and acquiring the update program (hereinafter referred to as download).

  The downloaded update program includes a plurality of programs, such as a program for updating a printer program and a program for updating a program for controlling printing paper, and these are continuous and form one data. .

  For example, as shown in FIG. 37, the data structure of this update program has an update program header that is the header of the entire update program at the head, and then an individual update program header that is the header of each update program and the update program body However, the data structure is continuous by the number of update programs.

  The total length of the update program header represents the entire data length excluding the update program header, and the total number of programs indicates the number of all update programs included in the update program. The program type of the individual update program header represents the type of program such as a printer program, the version represents the version of the update program, and the length represents the data length of the update program body.

  If the continuous update program is updated in the order of the data structure shown in FIG. 37, there is a possibility that the program cannot be updated.

  In the case of a program update that is performed via a network without a serviceman directly operating the image forming apparatus, the screen of the image forming apparatus that has updated the program displays that the program has been updated. Sometimes.

  If such a screen is displayed on the image forming apparatus, it may cause confusion when used by an operator. In addition, the operator must turn the power on again by updating the program.

  In this way, in the case of a program update that is performed via a network without a service person directly operating the image forming apparatus, the operator is able to update the program automatically at night, etc. It was difficult to know that the program was updated and the update result.

  SUMMARY An advantage of some aspects of the invention is that it provides a program update method suitable for an image forming apparatus that updates a program via a network, and an image forming apparatus equipped with the program update method.

  In order to solve the above-described problems, the present invention provides one or more processing units that perform processing relating to image formation, a control unit that communicates with the processing unit directly or via another processing unit, and the processing unit. In an image forming apparatus having a program for operating the control unit, an update program acquisition unit that acquires an update program for updating the program, the program of one processing unit, the one processing unit, and the control unit And a program update unit that causes the update program to update the program in an order determined according to the number of processing units that pass through for communication.

  In order to solve the above problem, the present invention is characterized in that the program update unit generates update order information for determining the order based on the update program acquired by the update program acquisition unit.

  In order to solve the above problem, the present invention is characterized in that the update order information includes information in which the order is associated with a type of a program updated by the acquired update program.

  In order to solve the above problem, the present invention is characterized in that the update order information includes information indicating an update status of a program updated by the acquired update program.

  In order to solve the above problem, according to the present invention, the control unit includes one or more applications that execute processing relating to image forming processing, and the program update unit individually stores a program of each application. It is possible to update.

  In order to solve the above-described problem, the present invention provides the program update unit that updates the program of a processing unit that performs processing for displaying information related to the image forming apparatus to an operator who operates the image forming apparatus. It is characterized in that the order to be performed is the last order.

  Moreover, in order to solve the said subject, this invention further has a communication part for connecting with a network, The said update program acquisition part acquires the said update program by the said communication part, It is characterized by the above-mentioned.

  In order to solve the above problem, the present invention is characterized in that the control unit restarts the processing units in the order of the processing units for which the update of the program has been completed.

  In order to solve the above problem, the present invention is characterized in that the control unit restarts the processing unit that updated the program after all the processing units that update the program have finished updating. To do.

  In order to solve the above problem, the present invention provides an update program stored in another storage area different from the storage area in which the control section stores the program when the control section updates its own program. It is characterized by operating in.

  In order to solve the above problem, the present invention is characterized in that the update program is stored in an area of a volatile storage unit.

  In order to solve the above problem, the present invention is characterized in that the size of the update program is smaller than the size of the program of the control unit.

  In order to solve the above problem, the present invention is characterized in that, when the control unit updates a program of the processing unit, the control unit restricts execution of the processing.

  In order to solve the above problem, the present invention is characterized in that the control unit restarts itself when communication with the processing unit that updated the program is disconnected.

  In order to solve the above-mentioned problem, the present invention restarts itself after a predetermined time has elapsed since the last restart of the processing unit among the processing units to be restarted. It is characterized by doing.

  Further, in order to solve the above-described problem, according to the present invention, when the control unit restarts itself, the control unit stores the apparatus state relating to the image forming apparatus in the nonvolatile storage unit, and after the control unit is restarted The state of the image forming apparatus is transitioned to the stored apparatus state.

  In order to solve the above-described problem, the present invention is characterized in that the apparatus state is a power saving state in which power consumption of the image forming apparatus is reduced.

  In order to solve the above-described problem, the present invention includes a display unit that displays information about the image forming apparatus, and the apparatus state is a state of information displayed on the display unit. And

  In order to solve the above problem, the present invention is characterized in that the display unit displays a progress of update of the program.

  In order to solve the above-described problem, the present invention is characterized in that the display unit does not display the progress status of the program update if the display unit is in a state of reducing power consumption of the image forming apparatus.

  In order to solve the above problem, the present invention is characterized in that the program update unit generates an update management table including information on the acquired update program.

  In order to solve the above problem, the present invention is characterized in that the update management table includes a module ID for specifying the acquired update program.

  In order to solve the above problem, the present invention provides the processing unit, wherein the control unit directly restarts the control unit, and the control unit makes a restart request to the processing unit. There are two types of processing units that can be restarted.

  In order to solve the above problems, the present invention provides an update result information generation unit that generates update result information indicating a result of updating the program, and an update result output that outputs an update result based on the update result information. And a portion.

  In order to solve the above-described problem, the present invention provides the update result output unit that prints the update result, transmits the result by e-mail, or displays it on a display unit that displays information about the image forming apparatus. It is characterized by.

  In order to solve the above problem, the present invention provides that the update result information is any one of a program version before update, a program version after update, a date and time of update, and a success or failure of update. It is characterized by including two or more.

  In order to solve the above problem, the present invention is characterized in that the update result information generating unit stores the update result information in a nonvolatile storage unit.

  In order to solve the above-mentioned problem, the present invention is characterized in that the update result information generation unit adds the generated update result information to update history information based on update result information in a past update. And

  Further, in order to solve the above-described problem, the present invention provides the control unit that restarts the image forming apparatus after the update result information generation unit stores the update result information in a nonvolatile storage unit, and The update result output unit outputs the update result after restarting.

  In order to solve the above-described problems, the present invention provides one or more processing units that perform processing relating to image formation, a control unit that communicates with the processing unit directly or via another processing unit, and the processing A program update method for an image forming apparatus having an operation unit and a program for operating the control unit, an update program acquisition step for acquiring an update program for updating the program, and the program of one processing unit, And a program update stage in which the update program is updated in an order determined according to the number of processing units that are passed through for communication between one processing unit and the control unit.

  In order to solve the above problems, the present invention provides hardware resources used in image forming processing, one or more processing units that perform processing relating to image formation, a program that operates the processing units, A program update method for an image forming apparatus having a communication unit, wherein an update program acquisition step for acquiring an update program for updating the program by the communication unit, and a program update step for updating the program by the update program And a restarting step of restarting the processing unit that has updated the program.

  In order to solve the above problem, the present invention is characterized in that the restarting step restarts in the order of the processing units that have updated the program.

  In order to solve the above-described problem, the present invention provides a program update method for an image forming apparatus including hardware resources used in image forming processing, a program for performing processing related to image formation, and a communication unit. An update program acquisition stage for acquiring an update program for updating the program by the communication unit, a program update stage for updating the program with the update program, and an update for generating update result information indicating a result of updating the program It has a result information generation step and an update result output step for outputting an update result based on the update result information.

  In order to solve the above problems, the present invention is characterized in that, in the update result output stage, the update result is printed, transmitted by e-mail, or displayed on a display unit of the image forming apparatus. And

  In order to solve the above problem, the present invention provides that the update result information is any one of a program version before update, a program version after update, a date and time of update, and a success or failure of update. It is characterized by including two or more.

  In order to solve the above problem, the present invention is characterized in that, in the update result information generation stage, the generated update result information is added to update history information based on update result information of updates performed in the past. To do.

  In order to solve the above-described problem, the present invention further includes a restarting step in which the image forming apparatus is restarted after the update result information generating step.

  In order to solve the above problem, according to the present invention, in the update result information generation step, the update result information is stored in a nonvolatile storage unit included in the image forming apparatus before the image forming apparatus is restarted. It is memorized.

  As described above, according to the present invention, it is possible to obtain a program update method suitable for an image forming apparatus that updates a program via a network, and an image forming apparatus equipped with the program update method.

  Embodiments of the present invention will be described below with reference to the drawings. In this embodiment, downloading an update program means acquiring the update program and storing the update program in a predetermined storage area such as a memory. The update program is a new program that replaces the currently operated program, and the update program is a program that executes processing for updating the operated program to the update program.

  FIG. 1 shows a block diagram of an embodiment of a compound machine according to the present invention. The multi-function apparatus 1 is configured to include a software group 2, a multi-function apparatus activation unit 3, and hardware resources 4.

  The compound machine starting unit 3 is executed first when the power of the compound machine 1 is turned on, and activates the application layer 5 and the platform layer 6. For example, the multi-function apparatus activation unit 3 reads the programs of the application layer 5 and the platform layer 6 from a hard disk device (hereinafter referred to as HDD) and transfers each read program to a memory area and activates it. The hardware resource 4 includes a scanner 25, a plotter 26, and a hardware resource 24 such as an ADF (Auto Document Feeder).

  The software group 2 includes an application layer 5 and a platform layer 6 activated on an operating system (hereinafter referred to as OS) such as UNIX (registered trademark). The application layer 5 includes programs that perform processing unique to user services related to image formation such as printers, copies, faxes, and scanners.

  The application layer 5 includes a printer application 9 that is a printer application, a copy application 10 that is a copy application, a fax application 11 that is a fax application, and a scanner application 12 that is a scanner application.

  The platform layer 6 interprets a processing request from the application layer 5 and generates a hardware resource 4 acquisition request, and manages one or more hardware resources 4 to control the control service layer. 7 includes a system resource manager (hereinafter referred to as “SRM”) 21 that arbitrates acquisition requests from 7 and a handler layer 8 that manages hardware resources 4 in response to acquisition requests from the SRM 21.

  The control service layer 7 includes a network control service (hereinafter referred to as NCS) 13, a remote service (hereinafter referred to as RS) 14, an operation panel control service (hereinafter referred to as OCS) 15, a fax control service (hereinafter referred to as FCS) 16, One or more of: an engine control service (hereinafter referred to as ECS) 17, a memory control service (hereinafter referred to as MCS) 18, an on-demand update service (hereinafter referred to as OUS) 19, a system control service (hereinafter referred to as SCS) 20 It is configured to include service modules.

  The platform layer 6 is configured to have an API 28 that can receive a processing request from the application layer 5 using a predefined function. The OS executes the software of the application layer 5 and the platform layer 6 in parallel as processes.

  The process of the NCS 13 corresponding to the communication unit provides a service that can be commonly used for applications that require network I / O, and distributes data received from the network side according to each protocol to each application, Mediates when sending data from each application to the network side.

  For example, the NCS 13 controls data communication with a network device connected via a network by HTTP (HyperText Transfer Protocol Daemon) by HTTP (HyperText Transfer Protocol).

  The process of RS14 provides a service using a network such as the Internet. The process of the OCS 33 controls an operation panel serving as information transmission means between the operator and the main body control. The FCS16 process provides APIs for sending and receiving faxes from the application layer 5 using the PSTN or ISDN network, registering / quoting various fax data managed in the backup memory, reading faxes, receiving faxes, etc. To do.

  The process of the ECS 17 controls the engine unit such as the scanner 25, the plotter 26, and other hardware resources 24. The process of the MCS 18 performs memory control such as acquisition and release of memory and use of the HDD. The OUS 19 corresponding to the update program acquisition unit downloads the program and stores it in the memory upon notification from the network.

  The processes of the SCS 20 corresponding to the program update unit, update result information generation unit, update result output unit, and restart unit include application management, operation unit control, system screen display, LED display, hardware resource management, interrupt application control, etc. Process.

  The process of the SRM 21 controls the system and manages the hardware resources 4 together with the SCS 20. For example, the process of the SRM 21 performs arbitration according to an acquisition request from an upper layer that uses the hardware resources 4 such as the scanner 25 and the plotter 26, and performs execution control.

  Specifically, the process of the SRM 21 determines whether or not the requested hardware resource 4 is available (whether it is not used by another acquisition request). The higher layer is notified that the resource 4 is available. Further, the process of the SRM 21 performs scheduling for using the hardware resource 4 in response to an acquisition request from an upper layer, and the request contents (for example, paper conveyance and image forming operation by the printer engine, memory allocation, file generation, etc.) Has been implemented directly.

  The handler layer 8 includes a fax control unit handler (hereinafter referred to as FCUH) 22 for managing a fax control unit (hereinafter referred to as FCU), which will be described later, and an image for allocating memory to the process and managing the memory allocated to the process. A memory handler (hereinafter referred to as IMH) 23 is included. The SRM 39 and the FCUH 22 make a processing request for the hardware resource 4 by using an engine I / F 27 that enables transmission of a processing request for the hardware resource 4 by a predefined function.

  The multi-function apparatus 1 can process the processing commonly required for each application by the platform layer 6 in an integrated manner. Next, a hardware configuration of the multifunction machine 1 will be described.

  FIG. 2 shows a hardware configuration diagram of an embodiment of the compound machine 1. The multi-function machine 1 includes a controller board 50, an operation panel 39, an FCU 40, and an engine 43. The FCU 40 includes a G3 standard compatible unit 103 and a G4 standard compatible unit 104.

  The controller board 50 includes a CPU 31, an ASIC 36, an HDD 38, a system memory (MEM-P) 32, a local memory (MEM-C) 37, a north bridge (hereinafter referred to as NB) 33, and a south bridge. (Hereinafter referred to as SB) 34, NIC 101 (Network Interface Card), USB device 41, IEEE 1394 device 42, Centronics device 102, and MLB 45.

  The operation panel 39 is connected to the ASIC 36 of the controller board 50. In addition, the SB 34, the NIC 101, the USB device 41, the IEEE 1394 device 42, the Centronics device 102, and the NB 33 are connected by a PCI bus.

  The MLB 45 is a board that is connected to the multi-function apparatus 1 via the PCI bus. The MLB 45 converts the image data input from the MFP 1 and outputs the converted image data or encoded image data to the MFP 1.

  The FCU 40 and the engine 43 are connected to the ASIC 36 of the controller board 50 via a PCI bus.

  In the controller board 50, the local memory 37, the HDD 38, and the like are connected to the ASIC 36, and the CPU 31 and the ASIC 36 are connected via the NB 33 of the CPU chip set. In this way, if the CPU 31 and the ASIC 36 are connected via the NB 33, it is possible to cope with a case where the interface of the CPU 31 is not disclosed.

  Further, the ASIC 36 and the NB 33 are not connected via a PCI bus, but are connected via an AGP (Accelerated Graphics Port) 67. In this way, in order to control the execution of one or more processes forming the application layer 5 and the platform layer 6 in FIG. 2, the ASIC 36 and the NB 33 are connected via the AGP 35 instead of the low-speed PCI bus, thereby reducing the performance. It is preventing.

  The CPU 31 performs overall control of the compound machine 1. The CPU 31 starts and executes NCS13, RS14, OCS15, FCS16, ECS17, MCS18, OUS19, SCS20, SRM21, FCUH22, IMH23, and MEU44 as processes on the OS, and also forms a printer application 9 that forms the application layer 5. The copy application 10, the fax application 11, and the scanner application 12 are activated and executed.

  The NB 33 is a bridge for connecting the CPU 31, the system memory 32, the SB 34 and the ASIC 36. The system memory 32 is a memory used as a drawing memory or the like of the multifunction machine 1. The SB 34 is a bridge for connecting the NB 33 to the PCI bus and peripheral devices. The local memory 37 is a memory used as a copy image buffer and a code buffer.

  The ASIC 36 is an IC for use in image processing having hardware elements for image processing. The HDD 38 is a storage for storing images, programs, font data, forms, and the like. The operation panel 39 is an operation unit that accepts an input operation from the user and performs display for the user.

  Next, with reference to FIG. 3, the positioning of each processing unit and program in the multifunction machine 1 will be described. FIG. 3 is a diagram illustrating the positioning of each processing unit and firmware as a program. FIG. 3 shows a controller board 50 that is a control unit, and an operation panel board 55, an FCU board 51, an engine board 52, a finisher 53, and an ADF 54 that are processing units. Also, the software group 2 that is the firmware of the control unit, the operation panel firmware 61 that is the firmware of the operation panel board 55, the FCU firmware 56 that is the firmware of the FCU board 51, and the plotter firmware 57 that is the firmware of the engine board 52 A scanner firmware 58, a finisher firmware 59 that is the firmware of the finisher 53, and an ADF firmware 60 that is the firmware of the ADF 54 are shown.

  First, the controller board 50 will be described. The controller board 50 is a board on which the software group 2 shown in FIG. A board described below is connected from the controller board 50.

  The operation panel board 55 is a board that controls the operation panel 39, and performs processing for displaying information related to the multifunction machine 1 to an operator who operates the multifunction machine 1. The operation panel board 55 and the controller board 50 are connected via a synchronous serial line 64 for communication.

  Next, the FCU board 51 will be described. This board is the fax control unit described above. Further, the FCU board 51 and the controller board 50 are connected by a PCI bus 62 for communication.

  Next, the engine board 52 will be described. The engine board 52 is mounted with a farm of an engine unit such as a plotter furr 57 and a scanner farm 58. The engine board 52 is also connected by a PCI bus 62 in order to communicate with the controller board 50.

  The operation panel board 55, the FCU board 51, and the engine board 52 described above are boards that directly communicate with the controller board 50, respectively.

  A finisher 53 and ADF described below are boards that communicate with the controller board 50 via the engine board 52 by communicating with the engine board 52 via a serial line.

  The finisher 53 is a device for binding printing paper with a stapler, and is operated by a finisher farm 59. The ADF 54 is a device that automatically sends a document, and operates by the ADF farm 60.

  The operation panel board 55, the FCU board 51, the engine board 52, the finisher 53, and the ADF 54 described above each have a CPU.

  As described above, the MFP 1 operates one or more processing units that perform processing relating to image formation, a control unit that communicates with the processing unit directly or through another processing unit, and the processing unit and the control unit. Program.

  Next, processing at the time of starting up each board will be described with reference to FIG. FIG. 4 shows a sequence diagram among the controller board 50, the engine board 52, the FCUH 22, and the OCS 19. The FCUH 22 manages the startup of the FCU board 62, and the OCS 19 manages the startup of the operation panel board 55.

  First, in step S1 and step S2, it is confirmed that the controller board 50 and the engine board 52 can communicate with each other. In step S3, the controller board 50 notifies the engine board 52 that it has been connected to the controller. Similarly, the engine board 52 notifies the controller board that the engine is connected in step S3. At this time, the engine board 52 also transmits information about the installed program at the same time.

  When the FCUH 22 confirms that the FCU board 51 has been activated in step S <b> 5, the FCUH 22 transmits to the controller board 50 information about the activation of the FCU board 51 and the program installed on the FCU board 51. Similarly, when the operation panel board 55 is activated, the OCS 19 transmits information about the activation of the OCS and the program installed on the operation panel board 55.

  Next, processing when updating a program will be described.

  The program of the processing unit is updated according to an instruction from the SCS 20 of the controller board 50. First, update of a program mounted on the controller board 50 including the SCS 20 will be described.

  The programs of the applications 9, 10, 11, and 12 mounted on the controller board 50 and the program of the controller 6 (see FIG. 1) can be updated individually.

  Further, each program of the controller 6 operates by a program written in the NV-RAM 47 when performing normal processing. Therefore, when updating the program, the program on the NV-RAM 47 cannot be rewritten. Therefore, the program being executed is expanded in the RAM such as the local memory 37 or the system memory 32, and processing is performed using the expanded program. To run.

  However, since the RAM does not have much capacity, the controller board 50 prepares an update program for updating the program separately from the program for executing the normal operation, and the update program Is expanded in the RAM and the program is updated. FIG. 5 is a diagram showing the development of the update program from the NV-RAM to the RAM. As shown in FIG. 5, the update program 201 written in the NV-RAM is expanded as an update program 202 in the RAM.

  The difference between this update program and a program for executing a normal operation will be described.

  The program of the controller 6 includes a program for performing communication in order to communicate with many processing units and control the multi-function apparatus 1. FIG. 6 shows a state in which the controller program 203 and the peripheral software program 204 can communicate with each other. The peripheral software program in FIG. 6 may be software that performs direct communication such as the FCU firmware 56 shown in FIG. 3 or may be a firmware that is mounted on the engine board 52.

  Thus, since the controller board 50 controls other processing units, the program for executing the contents to be transmitted / received is a program having a large size.

  The update program is a program obtained by adding an update process to a program that has become a small program by excluding the above-described communication program, so it is compared with a program for executing a normal process. Is a small program.

This update program makes it impossible to communicate with peripheral software, but can reduce the area occupied by the RAM. FIG. 7 shows a state of communication in a state where the update program 203 is being executed, and shows a state in which the controller board 50 and the peripheral software program 204 can no longer communicate with each other. If the program of the controller 6 is updated, communication with each processing unit cannot be performed. Therefore, in this case, the program of the controller 6 cannot update the program of another processing unit.

  This is also true for the engine board 52 that communicates with the finisher 53 or the ADF 54. Since the finisher 53 or the ADF 54 is instructed to update the program from the engine board 52, when the engine board 52 is updated, the engine board 52 communicates with the finisher 53 or the ADF 54 in the same manner as the controller board 50. The program of the finisher 53 or the ADF 54 cannot be updated.

  That is, as the number of processing units that are passed through to communicate with the controller board 50 is larger, the program must be updated first.

  Next, priority information for determining the order in which programs are updated will be described with reference to FIG. The priority information shown in FIG. 8 is a table indicating the program type and the priority of the program. The program type represents an FCU firmware, a finisher farm, a printer application, or the like.

  As for the priority, for example, the priority of the program C is 2, and the priority of the program E is 10. The order of updating is the first when the priority value is smaller. Therefore, the program A is updated before the program D. In the case of the same rank, the program may be updated from any program in that rank.

  This priority information is determined according to the number of processing units that pass through for communication between each processing unit and the controller board 50. Therefore, if the processing units are arranged as shown in FIG. 3, the priority of the finisher farm 59 and the ADF farm 60 that communicate with the controller board 50 via the engine board 52 is 1.

  Next, update order information for determining the order of update by the update program acquired in accordance with the priority information and a process of generating the update order information will be described.

  FIG. 9 is a diagram illustrating a process of generating update order information. It is assumed that the update programs are programs E, F, D, and A and are downloaded in this order.

  The controller 6 refers to the priority of the update program acquired from the priority information, and generates a priority table 70 composed of a set of the acquired update program and the priority. Then, the priority table 70 is sorted in ascending order by priority, and update order information 71 is generated. The update order information 71 includes information in which the order and the type of program updated by the acquired update program are associated with each other.

  As described above, the update order information 71 may be expanded after the update order information 71 is generated. FIG. 10 is an extension of the update order information 71 and includes a version and an execution state as shown in the figure. The execution status in FIG. 10 indicates “not executed”, “being executed”, and “executed”. “Non-executed” indicates a state in which the program is not updated. “In execution” indicates a state in which the program update is being executed, and “executed” indicates a state in which the program update has been executed. As described above, the execution state is information indicating the update status of the program updated by the update program.

  In FIG. 10, the operation panel firmware is updated later than the program update of the controller 6. The reason is that the operation panel farm draws the progress status for the operator. Therefore, the order of updating the operation panel firmware is the last. FIG. 11 shows the update program 206 developed on the RAM from the NV-RAM in which the operation panel firmware 205 is written.

  When updating the operation panel firmware after updating the program of the controller 6, the update program of the controller 6 includes processing for communicating with the operation panel board. If it is not necessary to draw the progress status, the order of updating the operation panel firmware is determined in the same manner as the program update of other processing units.

  The update order information described above is held by the SCS 20 of the controller 6. FIG. 12 is a diagram illustrating the position of the update order information in the controller 6. As shown in the figure, the update order information 207 is held by the controller 6.

  Next, program update processing in the multi-function apparatus 1 will be described with reference to the flowchart of FIG.

  In step S101 corresponding to the update program acquisition stage, the SCS 20 of the controller 6 receives a program update start request from the OUS 19 that has acquired the update program via the network. In the next step S102, the controller 6 generates update order information according to the priority information and the update program expanded in the RAM.

  Next, in step S103 corresponding to the program update stage, the controller 6 executes the update of the highest priority program among the programs in the update non-executed state indicated by the update order information. Then, the controller 6 changes the state of the update order information of the program that is executing the update in step S104 to be executed, and changes it to executed after the change is completed.

  Next, in step S105, the controller 6 determines whether or not the update of all the programs registered in the update order information has been completed. If not completed, the controller 6 executes the process of step S103 again. If completed, the controller 6 executes a reboot of the board on which the program updated in step S106 is mounted, and ends the process.

  Next, the reboot process will be described. First, the types of boards will be described. There are two types of boards: a controller that can be rebooted directly by the controller 6 and a board that reboots itself when the controller 6 issues a reboot execution request. The reboot process of these boards will be described.

  First, a board reboot process that can be directly rebooted by the controller 6 will be described with reference to FIG. When the update process for all the update target programs is completed in step S201, the controller 6 issues an operation stop request for restricting the execution of the process to the engine farm so that no trouble occurs even if the engine farm is rebooted in step S202. Notice.

  Step S203 waits for the completion of the operation stop from the engine farm in response to the operation stop request. When the operation stop completion is received in this step, the controller 6 notifies the operation panel firmware of the operation stop request in step S204. In step S205, the controller 6 again waits for the completion of the operation stop from the operation panel firmware for the operation stop request.

  When the operation stop completion is received in this step, the controller 6 executes reboot in step S206.

  Thus, when the controller 6 is a board that can be directly rebooted, the controller 6 makes an operation stop request before rebooting.

  Next, a board reboot process in which the board reboots itself when the controller 6 issues a reboot execution request will be described with reference to FIG. When the update process of all the update target programs is completed in step S301, the controller 6 notifies the engine farm of a reboot execution request in step S302. Next, in step S303, the controller 6 notifies the operation panel firmware of a reboot execution request. After the predetermined time, the controller 6 executes its own reboot in step S304. Then, after restarting, the controller 6 resumes communication with each processing unit in step S305.

  In this way, when the controller 6 makes a reboot execution request, and the board reboots itself, the controller 6 notifies the reboot execution request and reboots itself after a certain time.

  The process of the flowchart described above will be described with reference to the sequence diagram of FIG. This sequence diagram shows exchanges performed between the OUS 19, the SCS 20, the operation panel firmware 61, the system software 72, and the engine firmware 73. The system software 72 represents the program of the controller 6 and the application layer 5 shown in FIG. The engine farm 73 represents a plotter farm 57 or a scanner farm 58 mounted on the engine board.

  In step S401 corresponding to the update program acquisition stage, the OUS 19 of the controller 6 notifies the SCS 20 of the same controller 6 that the update program has been downloaded. With this notification, the SCS 20 performs module determination processing and generates an update management table to be described later. The SCS 20 that has generated the update management table transmits the update program to the engine farm 73 in step S402 corresponding to the program update stage. When the program update is completed, the engine farm 73 notifies the update result response to the SCS 20 in step S403.

  Next, in step S404, the SCS 20 notifies the system software 72 excluding the SCS 20 of a reboot preparation request in order to update the program of the controller 6. When the preparation for rebooting is completed, the system software 72 notifies the completion of rebooting preparation in step S405.

  Next, SCS20 switches to RAM execution which is a volatile memory | storage part (refer FIG. 5). The SCS 20 switched to the RAM execution performs a program update process of the system software 72 in step S406. Next, the SCS 20 transmits an update program to the operation panel farm 61 in step S407. In step S408, the operation panel firmware 61 notifies the SCS 20 of the result of updating the program.

  Since all the programs have been updated, the SCS 20 reboots the engine farm 73 and the operation panel farm 71 in step S409 in step S409 corresponding to the restart stage. Then, the SCS 20 reboots the system software 72 after t seconds.

  The generation of the update management table described above will be described with reference to FIG. The update management table includes, as items in the table, a program type, a version of the program, a module ID of received program data, and an update execution state.

  The module ID of the received program data uniquely identifies the program data. The execution state is the same as the execution state described in FIG.

  In this update execution data table, for example, the scanner engine program has a version of 1.22, a module ID of JP2CFa_escan, and the execution state is not executed.

  In order to explain the generation of the update management table, first, the table shown in FIG. 18 will be explained. The table shown in FIG. 18 shows the configuration of module IDs mounted on the multifunction machine 1.

  This table includes, as items, the program type of the program of the MFP 1, the version of the program, and the module ID. Assume that the configuration of the compound machine 1 is the configuration shown in FIG. Further, it is assumed that the downloaded update programs are a plotter engine program, a scanner engine program, a controller program, a printer application program, a FAX application program, and an operation unit program.

  At this time, the SCS 20 removes the program not included in the program configuration information of the model, and generates the update management table shown in FIG. In this case, since the FAX application program is not installed in the configuration of the MFP 1, an update management table excluding the FAX application program is generated as shown in FIG.

  Next, processing for rebooting in the order in which the SCS 2 has updated the program will be described with reference to the flowchart of FIG.

  In step S501 corresponding to the program update stage, the SCS 20 executes a program update process of the engine farm 73. In the next step S502, the SCS 20 notifies the engine farm 73 of an operation stop request.

  Step S503 waits for reception of the operation stop completion transmitted from the engine farm 73. When the SCS 20 receives the completion of the operation stop, in step S504 corresponding to the restart stage, the SCS 20 executes the reboot of the engine farm 73 and advances the process to step S512.

  The process returns to step S502. The SCS 20 that has notified the engine farm 73 of the operation stop request in step S502 executes program update processing of the system software 72 in step S505. In the next step S506, the SCS 20 notifies the system software 72 other than the SCS 20 of an operation stop request.

  Step S507 waits for the completion of the operation stop transmitted from the system software 72. When the SCS 20 receives the completion of the operation stop, the SCS 20 advances the process to step S512.

  The process returns to step S506. The SCS 20 that has notified the system software 72 of the operation stop request in step S506 executes program update processing of the operation panel firmware 61 in step S508. In the next step S509, the SCS 20 notifies the operation panel farm 61 of an operation stop request.

  Step S510 waits for reception of the operation stop completion transmitted from the operation panel farm 61. When the SCS 20 receives the completion of the operation stop, the SCS 20 executes the reboot of the operation panel firmware 61 in step S511 corresponding to the restart stage.

  If the SCS 20 determines in step S512 that the reboot of the engine farm 73 and the operation panel farm 61 has been completed, the SCS 20 reboots the system software 72 in step S513 and ends the process.

  Next, the processing described above will be described with reference to the sequence diagram of FIG. This sequence diagram shows exchanges performed between the OUS19, the SCS 20, the operation panel firmware 61, the system software 72, and the engine firmware 73, as in the previous sequence diagram.

  In step S601 corresponding to the update program acquisition stage, the OUS 19 notifies the SCS 20 that the update program has been downloaded. With this notification, the SCS 20 performs the module determination process described above and generates an update management table.

  Next, the SCS 20 transmits the update program to the engine farm 73 in step S602 corresponding to the program update stage. When the program update is completed, the engine farm 73 notifies the update result response to the SCS 20 in step S603. The SCS 20 notified of the update result response makes a reboot execution request to the engine farm 73 in step S604 corresponding to the restart stage, and the engine farm 73 executes reboot.

  Next, in step S605, the SCS 20 notifies the system software 72 excluding the SCS 20 of a reboot preparation request in order to update the program of the controller 6. When the preparation for rebooting is completed, the system software 72 notifies the completion of rebooting preparation in step S606. And SCS20 switches to RAM execution mentioned above.

  In step S607, the SCS 20 that has switched to RAM execution performs a system software program update process. Next, the SCS 20 transmits an update program to the operation panel farm 61 in step S608. In step S609, the operation panel firmware 61 notifies the SCS 20 of the result of updating the program.

  Next, the SCS 20 issues a reboot execution request to the operation panel firmware in step S610 corresponding to the restart stage, and the operation panel firmware 61 executes the reboot.

  Then, the SCS 20 reboots the system software 72 after t seconds since all the programs have been updated.

  Next, a description will be given of processing in which the SCS 20 performs its own reboot when the SCS 20 detects that the communication line with the operation panel farm 61 or the engine farm 73 has been disconnected.

  The disconnection of the communication line means that the communication partner has rebooted. Therefore, this process is a process in which the SCS 20 executes its own reboot after confirming whether the communication partner of the SCS 20 has surely executed the reboot.

  This process will be described with reference to FIG. In step S701 corresponding to the update program acquisition stage, the OUS 19 notifies the SCS 20 that the update program has been downloaded. With this notification, the SCS 20 performs module determination processing and generates the above-described update management table.

  The SCS 20 that has generated the update management table transmits the update program to the engine farm 73 in step S702 corresponding to the program update stage. When the program update is completed, the engine farm 73 notifies the update result response to the SCS 20 in step S703.

  Next, in step S704, the SCS 20 notifies the system software 72 excluding the SCS 20 of a reboot preparation request in order to update the program of the controller 6. When the preparation for reboot is completed, the system software 72 notifies the completion of reboot preparation in step S705.

  Next, the SCS 20 switches to RAM execution. The SCS 20 that has switched to RAM execution performs a program update process for the system software 72 in step S706. Next, the SCS 20 transmits an update program to the operation panel firmware 61 in step S707. In step S708, the operation panel firmware 61 notifies the SCS 20 of the result of updating the program.

  Since all the programs have been updated, the SCS 20 issues a reboot execution request to the engine farm 73 in step S709 corresponding to the restart stage. Accordingly, it is confirmed in step S710 that the communication line with the engine farm 73 has been disconnected.

  Next, the SCS 20 sends a reboot execution request to the operation panel farm 61 in step S711 corresponding to the restart stage. Accordingly, it is confirmed in step S712 that the communication line with the operation panel farm 61 has been disconnected.

  Next, since the SCS 20 has confirmed that the engine farm 73 and the operation panel 61 have been rebooted, the SCS 20 reboots the system software 72.

  As described above, two methods of rebooting have been described: a method of rebooting after all the programs have been updated, and a method of rebooting in the order in which the program updates have been completed.

  These two methods are different in the time until the compound machine 1 reboots. FIG. 23 shows the time required for rebooting after updating of the programs of all the processing units is completed.

  FIG. 23 shows that the program update is performed from the FCU firmware, and the update of the engine farm program is started at time a when the update of the program of the FCU firmware is completed. Further, it is shown that the update of the operation panel firmware starts at the time b when the update process of the engine farm program is completed. Then, it is shown that the reboot is executed at the time c when the update of the program of the operation panel firmware is finished, and the reboot is finished at the time d.

  Next, FIG. 24 shows the time required when the reboot is performed in the order in which the program update is completed.

  FIG. 24 shows that the program update is performed from the FCU firmware, and the engine firmware program update and the FCU firmware reboot process are started at time a when the program update of the FCU firmware is completed. Has been. Further, it is shown that the update of the operation panel firmware and the reboot process of the engine farm are started at the time b when the update process of the engine farm program is completed. Then, it is shown that the operation panel firmware is rebooted at time c when the update of the program of the operation panel firmware is completed, and the reboot is completed at time d.

  As described above, when the program update and the reboot are performed in parallel, the processing time can be shortened. Further, when processing is performed in parallel, the time can be shortened as the program is updated so that it takes a long time to reboot.

  Next, display processing of the operation panel 39 as a display unit will be described with reference to FIG.

  In step S801 corresponding to the update program acquisition stage, the SCS 20 is notified from the OUS 19 that the update program has been downloaded. In the next step S802, the SCS 20 generates an update management table. In step S803, the SCS 20 updates the program at the top of the table among the programs not yet updated.

  Next, in step S804, the SCS 20 determines whether the energy saving mode is set. If the energy saving mode is not set, the process proceeds to step S807. In the energy saving mode, the SCS 20 hides the panel from the operation panel farm 61. During this time, the SCS 20 determines whether or not an event for canceling the energy saving mode has occurred in step S806.

  Here, the event for canceling the energy saving mode refers to an event such as an operation panel 39 having a touch sensor being touched.

  When the energy saving mode is canceled, in step S807, the SCS 20 displays the update progress status and ends the process.

  The energy saving mode described above will be described. There are five types of energy saving modes: a standby state, a preheating state, a low power state, a silent state, and an engine off state.

  The standby state is a state where printing is possible. The preheating state and the low power state are states in which the fixing temperature is lowered, and the low power state corresponds to the energy star. The number of times the fixing temperature is lowered or not lowered depends on the model and setting. The silent state is a state in which the power supply relating to the fixing temperature is stopped, the peripheral device is silently activated and the HDD can be accessed, and corresponds to incoming faxes and data input. The engine off state is a state where the engine is stopped, for example, a state where the CPU of the engine is sleeping or is electrically disconnected.

  Next, a process for maintaining the state of the MFP 1 and shifting the fusion note 1 to the state before the update after the program update will be described with reference to FIG.

  In step S901 corresponding to the update program acquisition stage, the SCS 20 is notified from the OUS 19 that the update program has been downloaded. Next, the SCS 20 stores the current state of the MFP 1 in the NV-RAM 47 which is a nonvolatile storage unit.

  The state of the MFP 1 is, for example, the energy saving state earlier, such as a state where the screen of the operation panel 39 is darkened, a preheating state, a fixing temperature is suppressed, and the engine is stopped. .

  When the program update execution is completed in step S903, the SCS 20 executes reboot in step S904.

  Then, in step S904 after the restart, the SCS 20 shifts the MFP to the state of the MFP 1 stored in the NV-RAM 47.

  In the following, a process for notifying an operator such as a user or administrator that the program has been updated will be described. The flowchart shown in FIG. 27 shows the processing of the SCS 20 that notifies the operator by printing the update result on the printing paper after updating the program.

  This flowchart will be described. In step S1001 corresponding to the update program acquisition stage, the SCS 20 receives a program update start request from the OUS19. Next, the SCS 20 generates an update management table from the notified update program.

  In step S1003 corresponding to the program update stage, the SCS 20 that has generated the update management table executes the update of the highest program among the programs whose execution status in the update management table is not yet executed.

  In step S1004, the SCS 20 changes the execution state in the update management table of the program that has executed the update. Next, the SCS 20 writes the update flag stored in the NV-RAM 47 for each updated program in step S1005 corresponding to the update result information generation stage. This written content will be described later.

  The SCS 20 determines whether or not the update of all the programs registered in the update execution table is completed in step S1006. If not completed, the SCS 20 performs the process of step S1003 again. If completed, the process proceeds to step S1007. Proceed with the process.

  In step S1007, the SCS 20 writes the update date / time in update date / time information to be described later, and executes reboot. In step S1008, the reboot execution is completed, that is, after restarting, the SCS 20 determines whether there is updated program information in the NV-RAM 47 in step S1009.

  If there is no updated program information in the NV-RAM 47, the SCS 20 displays a normal screen on the operation panel 39 in step S1010, and ends the process.

  If there is updated program information in the NV-RAM 47, the SCS 20 prints and outputs the update result based on the update result information in step S1011 corresponding to the update result output stage. The contents of this print will be described later.

  Thus, after printing and discharging, the SCS 20 deletes the update result information stored in the NV-RAM 47 in step S1012, and ends the process.

  The contents written in the NV-RAM 47 in step S1005 in the flowchart described above will be described with reference to FIG.

  The table shown in FIG. 28 shows the data structure written in the NV-RAM 47. This data structure includes, as items, a program name, a version before update, a version after update, and an update result.

  Among these, the program name represents the name of the program, such as an engine program, and can be represented by, for example, a character code or a code assigned in advance. The version before update represents the version before the program is updated, and can be similarly expressed by a character code. The updated version represents the version after the program is updated, and can be similarly expressed by a character code. The update result indicating the success or failure of the program update is data indicating whether or not the program update is successful. This data can be expressed as long as it is 1-bit data or more.

  Note that “NULL” shown after the update of the printer application program and the update result in the drawing indicates that the data is represented by “0” and there is no content of the data. Therefore, it is indicated that the printer application program has not been updated.

  Next, update date / time information written in the NV-RAM 47 will be described with reference to FIG. As shown in FIG. 29, the update date information is written in the year, month, day, hour, and minute.

  The data shown in FIG. 28 and FIG. 29 is the update result information, but the content of the update result information may be appropriately changed according to the update result provided to the operator. For example, if only the success or failure of the program update is provided, it is sufficient to have information of 1 bit or more.

  Next, the contents printed in step S1011 will be described with reference to FIG. The printed contents are the program name 211 included in the update result information, the version 212 before update, the version 213 after update, the update result 214, the update date and time 215, and other fixed sentences 216 and 217.

  As described above, the information included in the update result information is printed in the contents to be printed, and the information necessary for the operator or the like is provided.

  Next, processing for transmitting the update result to the operator by e-mail will be described with reference to the flowchart of FIG. Note that steps S1101 to S1108 in the flowchart of FIG. 31 are the same as steps S1001 to S1008 in the flowchart of FIG. 27, and thus description thereof will be omitted, and processing after step S1109 will be described.

  After completion of the reboot execution, the SCS 20 determines whether there is updated program information in the NV-RAM 47 in step S1109.

  If there is no updated program information in the NV-RAM 47, the SCS 20 displays a normal screen on the operation panel 39 in step S1110, and ends the process.

  If there is updated program information in the NV-RAM 47, the SCS 20 determines in step S1111 whether the administrator's mail address is set. If the administrator's e-mail address is not set, the SCS 20 advances the process to step S1113.

  If the administrator's e-mail address is set, in step S1112, the SCS 20 transmits an e-mail in which the update result based on the update result information is written to the administrator. After transmitting the e-mail, the SCS 20 deletes the update result information stored in the NV-RAM 47 in step S213 and ends the process.

  The contents of the transmitted e-mail will be described with reference to FIG. As shown in FIG. 32, the program name 211 included in the update result information, the version 212 before update, the version 213 after update, the update result 214, the update date / time 215, and other fixed sentences 216 and 217 are obtained. ing. The content transmitted by e-mail is the same as the content to be printed.

  Next, processing for notifying the operator by displaying on the operation panel 39 as a display unit will be described with reference to the flowchart of FIG. Note that steps S1201 to S1208 in the flowchart of FIG. 33 are the same as steps S1001 to S1008 in the flowchart of FIG. 27, and thus description thereof will be omitted, and the processes after step S1209 will be described.

  After completion of the reboot execution, the SCS 20 determines whether there is updated program information in the NV-RAM 47 in step S1209.

  If there is no updated program information in the NV-RAM 47, the SCS 20 displays a normal screen on the operation panel 39 in step S1210, and ends the process.

  When there is updated program information in the NV-RAM 47, the SCS 20 displays an update result based on the stored update result information on the operation panel 39 in step S1211.

  In this way, after being displayed on the operation panel 39, the SCS 20 erases the update result information stored in the NV-RAM 47 in step S1212 and ends the process.

  The display contents of the operation panel 39 will be described with reference to FIG. FIG. 34 shows various keys 221, 223, 224, 225, and 226 and a display screen 222. The display screen 222 includes a program name 228 included in the update result information, a version 229 before update, a version 230 after update, an update result 231, an update date 232, other fixed phrases 233, and an OK button 227. Is displayed.

  Various keys 221, 223, 224, 225, and 226 are keys for operating the multi-function apparatus 1. The display screen 222 displays information for the operator. The OK button 227 is pressed by the operator when closing the displayed content. The contents displayed on the operation panel are the same as the contents to be printed.

  Next, the process of storing the update history in the NV-RAM 47 so that the operator can browse will be described with reference to the flowchart of FIG. Note that steps S1301 to S1308 in the flowchart of FIG. 35 are the same as steps S1001 to S1008 in the flowchart of FIG. 27, and thus description thereof will be omitted, and processing from step S1309 will be described.

  After completion of the reboot execution, the SCS 20 determines whether there is updated program information in the NV-RAM 47 in step S1309.

  If there is no updated program information in the NV-RAM 47, the SCS 20 displays a normal screen on the operation panel 39 in step S1310, and ends the process.

  If there is updated program information in the NV-RAM 47, the SCS 20 adds the stored update result information to the update history information in step S1311. After adding the update result information to the update history information, the SCS 20 deletes the update result information stored in the NV-RAM 47 in step S1312, and ends the process.

  The update history information will be described with reference to FIG. As shown in FIG. 36, the update history information includes a program name included in the update result information for each update date, a version before update, a version after update, an update result, and an update date.

  In this way, the result is stored every time it is updated. For example, the update history information in FIG. 36 includes the update history from the update performed at 4:00:00 on December 15, 2001 to the update performed at 2:00:00 on November 1, 2002. Is remembered.

  The above is the embodiment of the present invention. In this embodiment, the nonvolatile memory for storing the update program may be a flash memory that does not cost much.

It is a block diagram of one Example of the compound machine by this invention. It is a hardware block diagram of one Example of the compound machine by this invention. It is a figure which shows the positioning of each process part and a program. It is a sequence diagram which shows starting of each process part. It is a figure which shows expansion | deployment of the program for an update from NV-RAM to RAM. It is a figure which shows the mode of communication in a normal state. It is a figure which shows the mode of communication in the state under execution of the program for update. It is a figure which shows priority information. It is a figure which shows the process which produces | generates update order information. It is a figure which shows update order information. It is a figure which shows expansion | deployment of the program for an update from NV-RAM to RAM. It is a figure which shows the position of update order information. It is a flowchart which shows the update process of a program. It is a flowchart which shows the process which performs a reboot directly. It is a flowchart which shows the process which performs a reboot by making a reboot request | requirement. It is a sequence diagram which shows the process which performs a reboot after the update of all the programs. It is a figure which shows an update management table. It is a figure which shows the structure of module ID. It is a figure which shows an update management table. It is a flowchart which shows the process which performs a reboot in order of the completion of the update of a program. It is a sequence diagram which shows the process which performs a reboot in order of the update completion of a program. It is a sequence diagram which shows the process which performs a reboot after a communication line disconnection. It is a figure which shows the required time in the case of performing a reboot after the update of all the programs. It is a figure which shows the required time when performing a reboot in order of the update of a program. It is a flowchart which shows the process regarding the display of an update progress condition. It is a flowchart which shows the process which hold | maintains the state of a compound machine. It is a flowchart which shows the process which prints an update result. It is a figure which shows update result information. It is a figure which shows update result information. It is a figure which shows the printed update result. It is a flowchart which shows the process which transmits an update result with an email. It is a figure which shows the update result transmitted with the email. It is a flowchart which shows the process which displays an update result. It is a figure which shows the displayed update result. It is a flowchart which shows the process which memorize | stores update history information. It is a figure which shows update log information. It is a figure which shows the data structure of an update program.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Fusion machine 2 Software group 3 Fusion machine starting part 4 Hardware resource 5 Application layer 6 Controller 7 Control service layer 8 Handler layer 9 Printer application 10 Copy application 11 Fax application 12 Scanner application 13 Network control service (NCS)
14 Remote service (RS)
15 Operation Panel Control Service (OCS)
16 Fax Control Service (FCS)
17 Engine Control Service (ECS)
18 Memory Control Service (MCS)
19 On-demand update service (OUS)
20 System Control Service (SCS)
21 System Resource Manager (SRM)
22 Fax control unit handler (FCUH)
23 Image memory handler (IMH)
24 Other hardware resources 25 Scanner 26 Plotter 27 Engine I / F (PCI)
28 Application Program Interface (API)
31 CPU
32 System memory (MEM-P)
33 North Bridge (NB)
34 South Bridge (SB)
35 AGP (Accelerated Graphics Port)
36 ASIC
37 Local memory (MEM-C)
38 Hard Disk Drive (HD)
39 Operation Panel 40 Fax Control Unit (FCU)
41 USB device 42 IEEE1394 device 43 Engine unit 47 NV-RAM
50 Controller board 51 FCU board 52 Engine board 53 Finisher 54 ADF
55 Operation Panel Board 56 FCU Farm 57 Plotter Farm 58 Scanner Farm 59 Finisher Farm 60 ADF Farm 61 Operation Panel Farm 62 PCI Bus 63 Serial Line 64 Synchronous Serial Line 70 Priority Table 71 Update Order Information 72 System Software 73 Engine Farm 101 NIC
102 Centronics device 103 G3 standard compatible unit 104 G4 standard compatible unit 201, 202 Update program 203 Controller program 204 Peripheral software program

Claims (8)

A program update method for an image forming apparatus, comprising: hardware resources used in image forming processing; one or more processing units that perform processing relating to image formation; a program that operates the processing units; and a communication unit. And
An update program acquisition step of acquiring an update program for updating the program by the communication unit;
A program update stage for updating the program with the update program;
And a restarting step of restarting the processing unit that has updated the program.   The method according to claim 1, wherein in the restarting step, restarting is performed in the order of the processing unit that updated the program. In a program update method for an image forming apparatus having hardware resources used in image forming processing, a program for performing processing relating to image formation, and a communication unit,
An update program acquisition step of acquiring an update program for updating the program by the communication unit;
A program update stage for updating the program with the update program;
An update result information generation stage for generating update result information indicating a result of updating the program;
An update result output step of outputting an update result based on the update result information.   The program update method according to claim 3, wherein in the update result output step, the update result is printed, transmitted by e-mail, or displayed on a display unit of the image forming apparatus.   The update result information includes at least one of a version of the program before the update, a version of the program after the update, the date and time of the update, and the success or failure of the update. Program update method.   6. The program update method according to claim 5, wherein, in the update result information generation step, the generated update result information is added to update history information based on update result information of updates performed in the past.   The program update method according to claim 3, further comprising a restarting step of performing after the restarting of the image forming apparatus after the update result information generating step.   8. The program according to claim 7, wherein the update result information generation step stores the update result information in a nonvolatile storage unit included in the image forming apparatus before the image forming apparatus is restarted. Update method.

Images