JP2004192628A - Image forming apparatus, and method and program for activating program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image forming apparatus and method for activating programs reducing overlapped portions of respective programs and efficiently activating programs relating to a hardware resource. <P>SOLUTION: This image forming apparatus has the hardware resource used for image forming process and the program executing processes relating to image formation. This image forming apparatus has an examining unit for checking the hardware resource, a configuration means for configuring relation between the examining unit and the programs, and activating unit 52 activating the programs related to the examining unit according to check result by the examining unit. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

  The present invention relates to an image forming apparatus, a program starting method, and a program starting program, and more particularly, to a program starting method for starting a program according to a predetermined setting file, an image forming apparatus using the program starting method, and a program starting program.

  2. Description of the Related Art In recent years, an image forming apparatus (hereinafter, referred to as a multifunction peripheral) in which functions of respective apparatuses such as a printer, a copier, a facsimile, and a scanner are housed in one housing has become known. This multifunction machine includes a display unit, a printing unit, an imaging unit, and the like in one housing, and four types of software corresponding to a printer, a copier, a facsimile, and a scanner, respectively. It operates as a copy, facsimile and scanner. For example, Patent Literature 1 discloses an example of a fusion machine.

  In such a multifunction machine, a BIOS (Basic Input / Output System) and a boot loader (Boot Loader) are activated after the power is turned on. The boot loader expands a kernel (Kernel) and a root file system on a RAM (Random Access Memory) to activate the kernel. Then the kernel mounts the root file system. Here, mounting means starting the file system, peripheral devices, and the like in an accessible state.

After the kernel is started, an application / service layer starting program for starting an application (hereinafter referred to as an application) and various services is started. The application / service layer start-up program is a process that is first started in the MFP, mounts a file system in accordance with a predetermined setting file, and executes the service layer and application layer processes required for operation of the MFP in accordance with the predetermined setting file. It is running. In the conventional multifunction peripheral, the processes of the service layer and the application layer that have been started check hardware resources such as a display unit, a printing unit, and an imaging unit in the processing of each process. For example, Patent Literature 2 describes an example of a program that starts an application in accordance with predefined operation definition information.
JP-A-2002-84383 JP 2000-20203 A

  However, in the conventional multifunction peripheral, hardware resources are commonly used by a plurality of processes, and if hardware resources are checked in the processing of each process, there is a problem that the overlapping portion of each process increases. Was. In addition, in the conventional multifunction machine, hardware resources are checked during the processing of each process. Therefore, unless each process is started, it is not possible to check the presence / absence of hardware resources and performance.

  Therefore, in the conventional multifunction machine, even if a process is not used because there is no hardware resource or the performance of the hardware resource is low, the process must be started in vain to check the hardware resource. There was a problem. Note that Patent Document 2 does not check hardware resources, and cannot solve the above problem.

  The present invention has been made in view of the above points, and an image forming apparatus, a program starting method, and a program that can reduce overlapping portions of programs and can efficiently start programs related to hardware resources It is intended to provide a program starting program.

  Therefore, in order to solve the above-described problem, the present invention is an image forming apparatus having hardware resources used in image forming processing and a program for performing processing related to image formation, wherein a check on the hardware resources is performed. Checking means for performing, setting means for setting a relation between the checking means and the program, and starting means for starting the program related to the checking means in accordance with a result of the check by the checking means. And

  Further, the present invention is a program starting method for an image forming apparatus having hardware resources used in image forming processing and a program for performing processing related to image forming, wherein the starting unit includes the program and the hardware. An analyzing step of analyzing setting means that has set a relation with a checking means for checking resources; a starting means of the checking means for starting the checking means in accordance with a result of the analysis; And a program activating step of activating the program related to the checking means in accordance with a result of the check by the checking means.

  The present invention also provides a computer having a hardware resource used in image forming processing and a program for performing processing related to image formation, a check unit for checking the hardware resource, the check unit, and the program. And a program starting program for functioning as starting means for starting the program related to the checking means in accordance with the result of the check by the checking means.

  According to the present invention, since the check regarding the hardware resource is performed by the check unit, it is not necessary to perform the check regarding the hardware resource in the processing of each program, and the overlapping part of each program can be reduced.

  Further, according to the present invention, since the program is started in accordance with the result of the check on the hardware resources, it is not necessary to start an unused program, and the program can be started efficiently.

  As described above, according to the present invention, an image forming apparatus, a program starting method, and a program starting program capable of reducing the overlapping portion of each program and efficiently starting a program related to hardware resources are provided. Can be provided.

  Next, the best mode for carrying out the present invention will be described based on the following embodiments with reference to the drawings.

  FIG. 1 is a configuration diagram of one embodiment for describing a software configuration of a multifunction peripheral according to the present invention. The multifunction device 1 is configured to include a software group 2, a multifunction device activation unit 3, and hardware resources 4.

  The hardware resources 4 include a plotter 11, a scanner 12, and other hardware resources 13 such as a facsimile. The software group 2 includes an application layer 5 and a platform 6 running on an operating system (hereinafter referred to as OS) such as UNIX (registered trademark).

  The application layer 5 includes programs for performing processes specific to user services related to image formation such as a printer, a copy, a facsimile, and a scanner. The application layer 5 in FIG. 1 includes a printer application 21, a copy application 22, a fax application 23, a scanner application 24, and a net file application 25. The network file application 25 is a network file application, and manages data communication with a network device connected to the multifunction peripheral 1 via a network.

  The platform 6 interprets the processing request from the application layer 5 to generate a request for acquiring the hardware resource 4, and manages one or more hardware resources 4 to control the one or more hardware resources 4. It includes a system resource manager (hereinafter, referred to as SRM) 39 that arbitrates an acquisition request, and a handler layer 10 that manages the hardware resources 4 in response to the acquisition request from the SRM 39.

  The control service layer 9 includes one or more service modules such as NCS 31, DCS 32, OCS 33, FCS 34, ECS 35, MCS 36, UCS 37, and SCS 38. The platform 6 is configured to have an API 53 that receives a processing request from the application layer 5 using a function defined in advance. The OS executes each software of the application layer 5 and the platform 6 as a process in parallel.

  The process of the NCS (Network Control Service) 31 mediates when distributing data received from the network by each protocol to each application, or mediates when transmitting data from each application to the network. For example, the NCS 31 controls data communication with a network device connected to the MFP via a network.

  The process of the DCS (delivery control service) 32 controls the delivery of the document data stored in the MFP. The process of the OCS (operation panel control service) 33 controls an operation panel described later.

  The process of the FCS (Fax Control Service) 34 is to send and receive faxes from the application layer 5 using the PSTN or ISDN network, register or quote various fax data managed in a backup memory, read faxes, and receive faxes. Provides an API for printing and the like.

  A process of an ECS (engine control service) 35 controls engine units such as the plotter 11, the scanner 12, and the hardware resources 13. The process of the MCS (memory control service) 36 controls acquisition and release of memory, use of HDD, compression and decompression of image data, and the like. The process of the UCS (User Information Control Service) 37 manages user information.

  The process of the SCS (system control service) 38 performs processes such as control of an operation unit, display of a system screen, display of LEDs, management of hardware resources, management of applications, control of interrupt applications, and the like.

  The process of the SRM 39 controls the system and manages the hardware resources 4 together with the SCS 38. For example, the process of the SRM 39 performs arbitration in accordance with an acquisition request from an upper layer using the hardware resources 4 such as the plotter 11 and the scanner 12, and controls execution of the hardware resources 4.

  Specifically, the process of the SRM 39 determines whether the acquisition-requested hardware resource 4 is available (whether the acquisition-requested hardware resource 4 is not used by another acquisition request). 4 is notified to the upper layer that it is available. The process of the SRM 39 performs scheduling for using the hardware resource 4 in response to the acquisition request from the upper layer, and directly sends the request contents (paper conveyance and image forming operation by the printer engine, memory reservation, file generation, etc.). We are implementing.

  The handler layer 10 includes an FCUH (fax control unit handler) 40 for managing an FCU (fax control unit) described later, and an IMH (image memory handler) 41 for allocating memory to a process and managing the memory allocated to the process. And The SRM 39 and the FCUH 40 make a processing request to the hardware resource 4 using the engine I / F 54 that transmits a processing request to the hardware resource 4 by a function defined in advance.

  With the configuration of FIG. 1, the multifunction peripheral 1 can unify processing required for each application by the platform 6. Next, the hardware configuration of the MFP 1 will be described.

  FIG. 2 is a configuration diagram of one embodiment for describing a hardware configuration of the multifunction peripheral according to the present invention. 2 includes a controller 60, an operation panel 80, an FCU 81, and an engine unit 82.

  The controller 60 includes a CPU 61, a system memory 62, an NB 63, an SB 64, an ASIC 66, a local memory 67, an HDD 68, an NIC 69, an SD card slot 70, a USB I / F 71, an IEEE 1394 I / F 72, and a Centronics I / F 73.

  The operation panel 80 is connected to the ASIC 66 of the controller 60. The FCU 81 and the engine unit 82 are connected to the ASIC 66 of the controller 60 via a PCI bus 83.

  In the controller 60, the local memory 67, the HDD 68, and the like are connected to the ASIC 66, and the CPU 61 and the ASIC 66 are connected via the NB 63 of the CPU chip set. The ASIC 66 and the NB 63 are connected via an AGP (Accelerated Graphics Port) 65.

  The CPU 61 performs overall control of the multifunction peripheral 1. In the MFP 1 of FIG. 1, the CPU 61 activates one or more service modules forming the control service layer 9, the SRM 39, and the FCUH 40 and IMH 41 forming the handler layer 10 on the OS. The printer application 21, the copy application 22, the fax application 23, the scanner application 24, and the net file application 25 that form the application are activated and executed.

  The NB (North Bridge) 63 is a bridge for connecting the CPU 61, the system memory 62, the SB 64, the ASIC 66, the NIC 69, the SD card slot 70, the USB I / F 71, the IEEE 1394 I / F 72, and the Centronics I / F 73. The NB 63 is connected to the SB 64, the NIC 69, the SD card slot 70, the USB I / F 71, the IEEE 1394 I / F 72, and the Centronics I / F 73 via the PCI bus 74. The SB (south bridge) 64 is a bridge for connecting the PCI bus 74 to a ROM, peripheral devices, and the like.

  The system memory 62 is a memory used as a drawing memory or the like. The local memory 67 is a memory used as a copy image buffer, a code buffer, and the like. The ASIC 66 is an IC for image processing having hardware components for image processing. The HDD 68 is an example of a storage (auxiliary storage device) that stores image data, document data, programs, font data, forms, and the like.

  The NIC (network interface card) 69 is an interface device that connects the MFP 1 to a network such as the Internet or a LAN. The SD card slot 70 is capable of inserting and removing an SD card, and performs an interrupt to the device driver according to insertion or removal of the SD card.

  The USB I / F 70, the IEEE 1394 I / F 71, and the Centronics I / F 72 are interfaces conforming to respective standards. The operation panel 80 is an operation unit that receives an input operation from the operator and performs a display for the operator. The FCU 81 has a backup memory. The memory of the FCU 81 is used, for example, to temporarily store facsimile data received when the power of the MFP 1 is OFF.

  FIG. 3 is a configuration diagram of an example of the multifunction peripheral starting unit. The MFP starter 3 in FIG. 1 is executed first when the MFP 1 is powered on, and starts the application layer 5 and the platform 6. The multifunction peripheral starting unit 3 includes a ROM monitor 51 and a program starting unit 52. The process of the multifunction peripheral starting unit 3 will be described with reference to the flowchart of FIG.

  FIG. 4 is a flowchart of an example of a process of the multifunction peripheral starting unit. In step S1, when the power of the MFP 1 is turned on, the BIOS and the ROM monitor 51 as a boot loader are executed. The ROM monitor 51 performs initialization of hardware, diagnosis of the controller 60, initialization of software, and the like. Proceeding to step S2 following step S1, the ROM monitor 51 expands the OS and the root file system on the system memory 62 and starts the OS. Then, the OS mounts the root file system.

  Proceeding to step S3 following step S2, the OS acquires device information (for example, the clock frequency of the CPU 61, the memory sizes of the system memory 62 and the local memory 57, the board type of the controller 60, and the like) of the device connected at the time of startup. .

  Proceeding to step S4 following step S3, the OS activates the program activation unit 52 as an application / service activation program. The program starting unit 52 secures a memory area on the system memory 62 and the local memory 67. The program starting unit 52 is a process that is started first in the multifunction peripheral 1. Proceeding to step S5 following step S4, the program starting unit 52 mounts the file system according to the setting file.

  Further, the program activating unit 52 activates a check program as checking means for hardware resources according to the setting file. The program activating unit 52 determines whether to activate a program of the application layer 5 and the platform 6 (hereinafter, referred to as a main program) described in the setting file based on whether or not the check program ends normally.

  If it is determined that the main program is to be started, the program starting unit 52 reads the main program from a ROM or the like in accordance with the setting file, expands the read main program into a memory area secured on the system memory 62 and the local memory 67, The processes of the application layer 5 and the platform 6 are started. Hereinafter, the process of step S5 performed by the program activation unit 52 will be described in detail.

  FIG. 5 is a flowchart of an example of a process of the program starting unit. First, in step S10, the program starting unit 52 analyzes the setting file. Proceeding to step S11 following step S10, the program starting unit 52 mounts the file system according to the setting file.

  Proceeding to step S12 following step S11, the program starting unit 52 reads one exec command described in the setting file and determines whether or not the exec command has the “-c” option. For example, in the case of a setting file as shown in FIG. 6, the program starting unit 52 determines that the "-c" option is included in the exec command on the first line. If it is determined that the exec command has the “-c” option (YES in S12), the program starting unit 52 proceeds to step S13, and starts the check program specified by the exec command. For example, in the case of the setting file as shown in FIG. 6, the program starting unit 52 starts the check program “fccheck” specified by the exec command on the first line.

  The activated check program performs a check on hardware resources (for example, a check on the presence / absence of hardware resources, performance, etc.), and notifies the program start unit 52 of the check result, as described later.

  Proceeding to step S14 following step S13, the program starting unit 52 determines whether the check program has been completed normally or abnormally based on the check result notified from the check program. If it is determined that the check program has been completed normally (YES in S14), the program starting unit 14 proceeds to step S15. In step S15, the program activation unit 52 activates the main program specified by the exec command. For example, in the case of the setting file as shown in FIG. 6, the program starting unit 52 starts the main program “/ fax / bin / fax” specified by the exec command on the first line. Thereafter, the program starting unit 14 ends the check program.

  Proceeding to step S16 following step S15, the program starting unit 52 determines whether or not the main program to be started, in other words, the unread exec command still exists in the setting file. If it is determined that an exec command that has not been read yet exists in the setting file (YES in S16), the program activation unit 52 returns to step S12, reads the exec command that has not been read from the setting file, and performs the processing from step S12.

  On the other hand, when it is determined that the exec command that has not been read yet exists in the setting file (NO in S16), the program activation unit 52 ends the processing. If it is determined in step S12 that the "-c" option is not included in the exec command (NO in S12), the program starting unit 52 proceeds to step S15 and starts the main program specified by the exec command. If the "-c" option is not included in the exec command, the program starting unit 52 always starts the main program specified by the exec command.

  If it is determined in step S14 that the check program has not been completed normally (NO in S14), the program starting unit 52 proceeds to step S16. When the check program ends abnormally, the program starting unit 52 does not start the main program specified by the exec command.

  By the processing of the flowchart in FIG. 5, the program starting unit 52 starts the program specified by the exec command when the check program ends normally, and starts the program specified by the exec command when the check program ends abnormally. Therefore, the operation of the MFP 1 can be suppressed.

  Although the exec command has been described as an example of the command in the flowchart of FIG. 5, the command may be a mount command. In this case, the program starting unit 52 performs the mount specified by the mount command when the check processing ends normally, and does not perform the mount specified by the mount command when the check processing ends abnormally, so that the MFP 1 Mounting operation can be suppressed.

  Next, the processing of a plurality of check programs will be described using the setting file of FIG. In the setting file of FIG. 6, since the "exec" command on the first line includes the "-c" option, the check program "fccheck" is started. The check program “fcheckcheck” activated by the program activation unit 52 performs, for example, processing as shown in FIG.

  FIG. 7 is a flowchart of an example of the processing of the check program “fcheck”. In step S20, the check program performs a process for opening the device driver of the FCU 81. Proceeding to step S21 following step S20, the check program determines whether the opening of the device driver in step S20 was successful.

  If it is determined that the opening of the device driver is successful (YES in S21), the check program proceeds to step S23, assuming that the FCU 81 is connected to the MFP 1, and sets a value “0” indicating a normal end to the program starting unit. Notify 52. On the other hand, if it is determined that the opening of the device driver has failed (NO in S21), the check program proceeds to step S22, and determines whether the FCU 81 has already been opened and is in a busy state. Whether or not the FCU 81 is busy can be confirmed by, for example, whether or not “EBUSY” is included in “errno”.

  If it is determined that the FCU 81 is already open and busy (YES in S22), the check program proceeds to step S24, assuming that the FCU 81 is connected to the multi-function peripheral 1, and sets a value “0” indicating a normal end. The program activating unit 52 is notified. On the other hand, if it is not determined that the FCU 81 has already been opened and is in the busy state (NO in S22), the check program proceeds to step S25, assuming that the FCU 81 is not connected to the multifunction device 1, and indicates an abnormal end. The value “1” is notified to the program starting unit 52.

  According to the processing of the flowchart in FIG. 7, the check program notifies the program start unit 52 of the normal end when the FCU 81 is connected to the multifunction machine 1 and the abnormal end when the FCU 81 is not connected to the multifunction machine 1. The start unit 52 can be notified. Note that the program activation unit 52 activates the application “fax” when notified of normal termination from the check program, and does not activate the application “fax” when notified of abnormal termination from the check program.

  Therefore, the program activation unit 52 activates the application “fax” when the FCU 81 is connected to the multifunction device 1 by using the normal end or abnormal end notified from the check program, and executes the application “fax” when the FCU 81 is not connected. The application “fax” can be prevented from being activated. That is, the program activation unit 52 can suppress the activation of the application “fax” by the connection state of the FCU 81. In the flowchart of FIG. 7, the FCU 81 is described as an example of a device, but any device may be used. That is, according to the flowchart of FIG. 7, the activation of the application can be suppressed depending on the connection state of the device such as the option board.

  In the setting file of FIG. 6, when the processing of the exec command on the first line is completed, the processing of the exec command on the second line is performed. In the setting file of FIG. 6, since the "-c" option is included in the exec command on the second line, the check program "cpcheck1" is started. For example, the check program “cpucheck1” activated by the program activation unit 52 performs a process as shown in FIG.

  FIG. 8 is a flowchart of an example of the processing of the check program “cpucheck1”. In step S30, the check program calls the system call "getINFO (CPU)" and acquires the clock frequency of the CPU 61 included in the device information from the OS.

  Proceeding to step S31 following step S30, the check program determines whether or not the clock frequency of the CPU 61 obtained in step S30 is 500 MHz or less. If it is determined that the clock frequency of the CPU 61 is equal to or lower than 500 MHz (YES in S31), the check program proceeds to step S32, and notifies the program starting unit 52 of a value “0” indicating a normal end. On the other hand, when determining that the clock frequency of the CPU 61 is not lower than 500 MHz (NO in S31), the check program proceeds to step S33, and notifies the program starting unit 52 of a value “1” indicating abnormal termination.

  According to the process of the flowchart of FIG. 8, the check program notifies the program start unit 52 of the normal end when the clock frequency of the CPU 61 is 500 MHz or less, and notifies the program start unit 52 of the abnormal end when the clock frequency of the CPU 61 is not 500 MHz or less. Can be notified. The program activation unit 52 activates the application “setfont_bitmap” when notified of a normal end from the check program, and does not activate the application “setfont_bitmap” when notified of an abnormal end from the check program.

  Therefore, the program starting unit 52 sets the default font used by the printer to the bitmap format by using the normal end or the abnormal end notified from the check program. That is, even if the clock frequency of the CPU 61 is equal to or lower than 500 MHz, the program starting unit 52 can change the default font so that printing can be performed within a predetermined time, thereby giving priority to high-speed printing.

  In the setting file of FIG. 6, when the processing of the exec command on the second line ends, the processing of the exec command on the third line is performed. In the setting file of FIG. 6, since the “-c” option is included in the exec command on the third line, the check program “cpucheck2” is started. For example, the check program “cpucheck2” activated by the program activation unit 52 performs a process as shown in FIG.

  FIG. 9 is a flowchart of an example of the processing of the check program “cpucheck2”. In step S40, the check program calls the system call “getINFO (CPU)” and acquires the clock frequency of the CPU 61 included in the device information from the OS.

  Proceeding to step S41 following step S40, the check program determines whether or not the clock frequency of the CPU 61 acquired in step S40 is equal to or higher than 501 MHz. If it is determined that the clock frequency of the CPU 61 is equal to or higher than 501 MHz (YES in S41), the check program proceeds to step S42, and notifies the program starting unit 52 of a value “0” indicating a normal end. On the other hand, when determining that the clock frequency of the CPU 61 is not equal to or higher than 501 MHz (NO in S41), the check program proceeds to step S43, and notifies the program activation unit 52 of a value “1” indicating abnormal termination.

  According to the process of the flowchart of FIG. 9, the check program notifies the program start unit 52 of the normal end when the clock frequency of the CPU 61 is equal to or higher than 501 MHz, and notifies the program start unit 52 of the abnormal end when the clock frequency of the CPU 61 is not equal to or higher than 501 MHz. Can be notified. The program activation unit 52 activates the application “setfont_vector” when notified of a normal end from the check program, and does not activate the application “setfont_vector” when notified of an abnormal end from the check program.

  Therefore, the program starting unit 52 sets the default font used by the printer to the vector image by using the normal end or the abnormal end notified from the check program. That is, when the clock frequency of the CPU 61 is equal to or higher than 501 MHz, the program starting unit 52 changes the default font to a fine default font, so that the print quality can be improved.

  According to the processing of the flowcharts of FIGS. 8 and 9, the multifunction peripheral 1 of the present invention changes the default font used according to the performance of the CPU 61 so that printing can be performed within a fixed time, thereby giving priority to high-speed printing. Can be.

  In the setting file of FIG. 6, when the processing of the exec command on the third line is completed, the processing of the exec command on the fourth line is performed. In the setting file of FIG. 6, since the "-c" option is included in the exec command on the fourth line, the check program "memcheck1" is started. For example, the check program “memcheck1” activated by the program activation unit 52 performs a process as shown in FIG.

  FIG. 10 is a flowchart of an example of the processing of the check program “memcheck1”. In step S50, the check program calls the system call “getINFO (mem)” and acquires the memory sizes of the system memory 62 and the local memory 67 included in the device information from the OS. Proceeding to step S51 following step S50, the check program determines whether the memory size acquired in step S50 is not less than 64 MB and not more than 128 MB.

  If it is determined that the memory size is 64 MB or more and 128 MB or less (YES in S51), the check program proceeds to step S52, and notifies the program starting unit 52 of a value “0” indicating a normal end. On the other hand, if the check program determines that the memory size is not more than 64 MB and not more than 128 MB (NO in S51), the check program proceeds to step S53, and notifies the program starting unit 52 of a value “1” indicating abnormal end.

  According to the process of the flowchart of FIG. 10, the check program notifies the program start unit 52 of the normal end when the memory size is 64 MB or more and 128 MB or less, and notifies the program start unit 52 of the abnormal end when the memory size is not 64 MB or more and 128 MB or less. Can be notified. Note that the program starting unit 52 starts five http daemons (hereinafter referred to as httpd) when notified of a normal end from the check program, and does not start httpd when notified of an abnormal end from the check program.

  Therefore, the program starting unit 52 uses the normal end or the abnormal end notified from the check program to reduce the number of httpd to be started even if the memory sizes of the system memory 62 and the local memory 67 are small. Thus, it is possible to prevent an increase in processing time for one request.

  In the setting file of FIG. 6, when the processing of the exec command on the fourth line ends, the processing of the exec command on the fifth line is performed. In the setting file of FIG. 6, since the "-c" option is included in the exec command on the fifth line, the check program "memcheck2" is started. For example, the check program “memcheck2” activated by the program activation unit 52 performs a process as shown in FIG.

  FIG. 11 is a flowchart of an example of processing of the check program “memcheck2”. In step S60, the check program calls the system call “getINFO (mem)”, and acquires the memory sizes of the system memory 62 and the local memory 67 included in the device information from the OS. Proceeding to step S61 following step S60, the check program determines whether the memory size acquired in step S60 is 128 MB or more.

  If it is determined that the memory size is 128 MB or more (YES in S61), the check program proceeds to step S62, and notifies the program start unit 52 of a value “0” indicating a normal end. On the other hand, if it is determined that the memory size is not more than 128 MB (NO in S61), the check program proceeds to step S63, and notifies the program starting unit 52 of a value “1” indicating abnormal termination.

  According to the processing of the flowchart in FIG. 11, the check program can notify the program start unit 52 of the normal end when the memory size is 128 MB or more, and notify the program start unit 52 of the abnormal end when the memory size is not 128 MB or more. The program activating unit 52 activates ten httpd when notified of normal termination from the check program, and does not activate httpd when notified of abnormal termination from the check program.

  Therefore, by using the normal termination or abnormal termination notified from the check program, the program activation unit 52 increases the number of httpd to be activated when the memory sizes of the system memory 62 and the local memory 67 are large, and Can respond immediately to requests from

  10 and 11, the MFP 1 of the present invention can appropriately change the number of httpd to be started according to the memory sizes of the system memory 62 and the local memory 67.

  Next, the processing of the check program will be described using the setting file of FIG. In the setting file of FIG. 12, since the "-c" option is included in the "mount" command, the check program "hddnoneexist" is started. The check program “hdnonexist” activated by the program activation unit 52 performs, for example, processing as shown in FIG.

  FIG. 13 is a flowchart of an example of the process of the check program “hdnonexist”. In step S70, the check program calls the system call “getINFO (hdd)”, and acquires from the OS the HDD connection presence / absence information included in the device information.

  Proceeding to step S71 following step S70, the check program determines whether or not the HDD is connected to the MFP 1 according to the HDD connection presence / absence information acquired in step S70. If it is determined that the HDD is not connected to the MFP 1 (NO in S71), the check program proceeds to step S72, and notifies the program starting unit 52 of a value “0” indicating a normal end. On the other hand, if it is determined that the HDD is connected to the MFP 1 (YES in S71), the check program proceeds to step S73, and notifies the program starting unit 52 of a value “1” indicating abnormal termination.

  According to the process of the flowchart of FIG. 13, the check program notifies the program start unit 52 of the normal end when the HDD is not connected to the multifunction machine 1 and the abnormal end when the HDD is connected to the multifunction machine 1. The start unit 52 can be notified. The program activating unit 52 mounts the ramdisk when notified of a normal end from the check program. Specifically, “/ dev / md0c” is mounted on the mount point “/ ramdisk”. Further, the program starting unit 52 does not mount the ramdisk when notified of an abnormal end from the check program.

  Therefore, the program starting unit 52 mounts the ramdisk when the HDD is not connected to the MFP 1 by using the normal end or the abnormal end notified from the check program. That is, the program starting unit 52 can use the ramdisk as the local storage device for the PDL storage even when the HDD is not connected to the multifunction device 1. When the HDD is connected to the MFP 1, the program starting unit 52 can use the HDD as a local storage device for PDL storage.

  Next, the processing of the check program will be described using the setting file of FIG. The setting file of FIG. 14 is stored in the SD card as shown in FIG. In the case of the SD card shown in FIG. 15, “xxx.cnf” represents a setting file, and “module / xxx.mod” represents a module file to be mounted and executed.

  In the setting file of FIG. 14, since the "-c" option is included in the mount command, the check program "sdcommand" is started. The check program “sdcommand” activated by the program activation unit 52 performs, for example, processing as shown in FIG.

  FIG. 16 is a flowchart of an example of the processing of the check program “sdcommand”. In step S80, the check program analyzes a setting file as shown in FIG. 14 in the SD card. Proceeding to step S81 following step S80, the check program determines whether an SD command exists in the setting file based on the analysis result of step S80. If it is determined that an SD command exists (YES in S81), the check program proceeds to step S82. On the other hand, if it is determined that there is no SD command (NO in S81), the check program proceeds to step S83.

  In step S82, the check program determines whether the slot specified by the SD command matches the slot in which the SD card is inserted. For example, in the case of the setting file as shown in FIG. 14, since the slot specified by the SD command is “2”, when the slot in which the SD card is inserted is “2”, the check program uses the SD command. It is determined that the specified slot matches the slot in which the SD card is inserted.

  If it is determined that the slot specified by the SD command matches the slot in which the SD card is inserted (YES in S82), the check program proceeds to step S83, and sets a value “0” indicating normal end to the program. Notify the activation unit 52. On the other hand, if it is determined that the slot specified by the SD command does not match the slot in which the SD card is inserted (NO in S82), the check program proceeds to step S84, where the value “1” representing abnormal end is set. To the program starting unit 52.

  According to the processing of the flowchart in FIG. 16, the check program notifies the program start unit 52 of the normal termination when the slot specified by the SD command and the slot in which the SD card is inserted match, and If the specified slot does not match the slot in which the SD card is inserted, abnormal termination can be notified to the program starting unit 52.

  Note that when notified of a normal end from the check program, the program starting unit 52 mounts the gzip-compressed ROMFS format module file “xxx.mod” to the mount point “/ mnt” and executes the module file. Further, the program starting unit 52 does not mount and execute the module file when notified of the abnormal end from the check program.

  Therefore, the program starting unit 52 mounts and executes the module file in the SD card inserted in the slot different from the slot designated by the SD command by using the normal end or the abnormal end notified from the check program. Can be suppressed.

  In the case of the setting file of FIG. 6, the relationship among the main program, the check program, the program starting unit 52, the OS, and the hardware resources is as shown in FIG. 17, for example. FIG. 17 is a diagram showing an example of the relationship among the main program, the check program, the program starting unit 52, the OS, and the hardware.

  The program activation unit 52 activates the check programs in order, and when the check program ends normally, activates a main body program corresponding to the check program. In FIG. 17, the main program located above each check program is the main program corresponding to the check program.

  FIG. 17 shows an example in which the check program and the main body program are in one-to-one correspondence, but the check program and the main body program may be in one-to-n correspondence as shown in FIG.

  FIG. 18 is a diagram for explaining an example in which a check program and a main body program correspond to 1: n. In the example of FIG. 18, the check program a corresponds to the main body programs a and b. The program starting unit 52 starts the check program a, and when the check program a ends normally, starts the main body programs a and b corresponding to the check program a. When the check program a corresponds to the main body programs a and b as shown in FIG. 18, the setting file is configured as shown in FIG. FIG. 19 is a configuration diagram of another example of the setting file. The processing of the program starting unit 52 is the same as that of FIG.

  Further, in a case where a plurality of main programs under a directory are activated based on the result of the check by the same check program, it is efficient to suppress the mounting of the directory based on the result of the check.

  FIG. 20 is a configuration diagram of an example of a setting file for suppressing mounting. In the case of the setting file as shown in FIG. 20, the program starting unit 52 starts the check program “memcheck3” specified by the mount command on the first line. For example, it is assumed that the check program “memcheck3” in FIG. 20 ends normally when the memory size of the system memory 62 and the local memory 67 is 64 MB or more.

  The program starting unit 52 mounts “web.romfs” specified by the mount command on the directory “/ web” when the check program ends normally, but does not mount it when the check program ends abnormally. For example, if there is a description as shown in FIG. 6 below the description of the setting file in FIG. 20, the program “/ web / bin / httpd” under the directory “/ web” will not be started. Therefore, the program starting unit 52 can avoid wasting memory according to the memory size of the system memory 62 and the local memory 67.

  The mounting process using the setting file in FIG. 20 is a process performed in step S11 in FIG. Further, the setting file in FIG. 20 shows an example in which the mounting of the directory is suppressed according to the memory size. However, the mounting of the directory may be suppressed according to the presence or absence of hardware resources, the CPU performance, and the like. .

  FIG. 18 shows an example in which the check program and the main program correspond to each other on a one-to-n basis. However, as shown in FIG. 21, the check program and the main program may correspond to each other on an n-to-one basis.

  FIG. 21 is a diagram for describing an example in which the check program and the main body program correspond to n: 1. In the example of FIG. 21, the check programs a and b correspond to the main program a. The program starting unit 52 starts the check programs a and b, and when the check programs a and b end normally, starts the main program a corresponding to the check programs a and b. When the check programs a and b correspond to the main program a as shown in FIG. 21, the setting file is configured as shown in FIG. FIG. 22 is a configuration diagram of another example of the setting file.

  In the setting file of FIG. 22, two check programs “check program a” and “check program b” each having the “−c” option in one exec command are set. Therefore, the program starting unit 52 starts the check programs a and b in step S13 in FIG. Then, in step S14, the program activating unit 52 determines whether or not both of the check programs a and b have been completed normally. When it is determined that both have been normally completed, the program activating unit 52 activates the main program a specified by the exec command. . The processing other than steps S13 and S14 of the program starting unit 52 is the same as that in FIG.

  In the MFP 1, the same check program may be started according to the setting file. Therefore, when reactivating a previously activated check program, it is desirable to use the result of the check of the check program from the viewpoint of shortening the processing time. Therefore, the MFP 1 of the present invention performs the processing as shown in FIGS. 23 and 24 so that the result of the check by the check program that has been started before can be used.

  FIGS. 23 and 24 are flowcharts of an example of processing performed by the program activation unit and the check program. Note that the processing in steps S90 to S93 is the same as the processing in steps S10 to S13 in FIG. 5, and a description thereof will be omitted.

  In step S94, it is determined whether or not the check program started in step S93 has already been checked based on whether or not a check result is stored in a predetermined memory area. For example, as a predetermined memory area for storing a check result, an area on a memory that can be directly accessed by a check program process without using an OS can be used. If it is determined that the check has been completed (YES in S94), the check program proceeds to step S95, reads the result of the check from a predetermined memory area, notifies the program starting unit 52, and then proceeds to step S98. On the other hand, if it is determined that the check has not been completed (NO in S94), the check program proceeds to step S96, and performs a check on hardware resources as described above.

  Proceeding to step S97 following step S96, the check program writes the result of the check to a predetermined memory area, and notifies the program starting unit 52 of the result of the check, and then proceeds to step S98. Note that the processing of steps S98 to S100 is the same as the processing of steps S14 to S16 in FIG. 5, and a description thereof will be omitted. According to the flowcharts of FIG. 23 and FIG. 24, the result of the check of the check program started before can be used.

  Furthermore, the MFP 1 may start all the check programs at the time of start-up, and write the results of the checks by all the check programs in a predetermined memory area in advance. In this case, after performing the check by the check program immediately after startup, the MFP 1 can use the result of the check written in the predetermined memory area, so that the processing time can be reduced.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

FIG. 2 is a configuration diagram of an embodiment for describing a software configuration of the multifunction peripheral according to the present invention. FIG. 2 is a configuration diagram of an embodiment for describing a hardware configuration of a multifunction peripheral according to the present invention. FIG. 3 is a configuration diagram of an example of a multifunction peripheral starting unit. 6 is a flowchart illustrating an example of a process performed by a multifunction peripheral activation unit. 9 is a flowchart illustrating an example of a process performed by a program activation unit. FIG. 4 is a configuration diagram of an example of a setting file. It is a flow chart of an example of processing of a check program “fcookcheck”. It is a flow chart of an example of processing of a check program “cpucheck1”. It is a flowchart of an example of a process of a check program "cpucheck2". It is a flow chart of an example of processing of a check program “memcheck1”. It is a flow chart of an example of processing of a check program “memcheck2”. FIG. 11 is a configuration diagram of another example of a setting file. It is a flow chart of an example of processing of a check program “hddnoneexist”. FIG. 11 is a configuration diagram of another example of a setting file. FIG. 3 is an image diagram of an example of a file stored in an SD card. It is a flowchart of an example of a process of a check program "sdcommand". FIG. 4 is a relationship diagram illustrating an example of a relationship among a main body program, a check program, a program starting unit 52, an OS, and hardware. FIG. 9 is a diagram for describing an example in which a check program and a main body program correspond to one-to-n. FIG. 11 is a configuration diagram of another example of a setting file. FIG. 6 is a configuration diagram of an example of a setting file for suppressing mounting. FIG. 9 is a diagram for describing an example in which a check program and a main body program correspond to n: 1. FIG. 11 is a configuration diagram of another example of a setting file. It is a flowchart (1/2) of an example of the process which a program starting part and a check program perform. It is a flowchart of an example of the process which a program starting part and a check program perform (2/2).

Explanation of reference numerals

DESCRIPTION OF SYMBOLS 1 Multifunction machine 2 Software group 3 Multifunction machine start part 4 Hardware resources 5 Application layer 6 Platform 9 Control service layer 10 Handler layer 11 Plotter 12 Scanner 13 Hardware resource 21 Printer application 22 Copy application 23 Fax application 24 Scanner application 25 Net file Application 31 Network Control Service (NCS)
32 Delivery Control Service (DCS)
33 Operation Panel Control Service (OCS)
34 Fax Control Service (FCS)
35 Engine Control Service (ECS)
36 Memory Control Service (MCS)
37 User Information Control Service (UCS)
38 System Control Service (SCS)
39 System Resource Manager (SRM)
40 Fax control unit handler (FCUH)
41 Image Memory Handler (IMH)
51 ROM monitor 52 program starter 53 application program interface (API)
54 Engine I / F
60 Controller 61 CPU
62 System memory 63 North Bridge (NB)
64 South Bridge (SB)
65 AGP (Accelerated Graphics Port)
66 ASIC
67 Local memory 68 Hard disk drive (HDD)
69 Network Interface Controller (NIC)
70 Slot for SD card 71 USB I / F
72 IEEE1394 I / F
73 Centronics I / F
80 Operation panel 81 Fax control unit (FCU)
82 Engine 83 PCI bus

Claims (24)

An image forming apparatus having hardware resources used in image forming processing and a program for performing processing related to image formation,
Checking means for checking the hardware resources;
Setting means for setting an association between the check means and the program;
Activating means for activating the program related to the checking means in accordance with the result of the check by the checking means.   The image forming apparatus according to claim 1, wherein the setting unit sets the check unit and the program in a one-to-one relationship.   2. The image forming apparatus according to claim 1, wherein the setting unit sets the check unit and the program in a one-to-n relationship.   2. The image forming apparatus according to claim 1, wherein the setting unit sets the check unit and the program in an n-to-one relationship. A storage unit for storing a result of the check by the check unit,
The check unit checks the result of the check stored in the storage unit before performing the check on the hardware resource, and uses the result of the check if the result of the check to be performed is already stored. The image forming apparatus according to claim 1, wherein:   The image forming apparatus according to claim 2, wherein the activation unit activates the check unit according to the content set in the setting unit.   7. The image forming apparatus according to claim 6, wherein the activation unit terminates the checking unit after activating the program.   The checking unit checks the presence or absence of the hardware resource, outputs a normal value as a result of the check when it is determined that the hardware resource is present, and outputs an abnormal value when it is determined that the hardware resource is not present. The image forming apparatus according to claim 2, wherein the image is output as a result of the check.   The checking means performs a process for opening a device driver corresponding to the hardware resource, determines that the hardware resource is present when the opening is successful or has already been opened, and otherwise, 9. The image forming apparatus according to claim 8, wherein it is determined that the hardware resource does not exist.   The activation unit is set in the setting unit when a normal value is supplied from the check unit as a result of checking for the presence or absence of hardware resources that operate as part or all of a printer, a copy, a fax, or a scanner. 10. The image forming apparatus according to claim 8, wherein the program for executing a process of a printer, a copy, a facsimile, or a scanner is started in accordance with the contents.   The checking unit checks the presence or absence of the hardware resource, outputs a normal value as a result of the check when it is determined that there is no hardware resource, and outputs an abnormal value when it is determined that the hardware resource is present. The image forming apparatus according to claim 2, wherein the image is output as a result of the check.   The method according to claim 1, wherein the starting means mounts a RAM disk according to the contents set in the setting means when a normal value is supplied from the checking means as a result of the check of the presence or absence of the hard disk device. Item 12. The image processing device according to Item 11.   The checking unit checks a predetermined performance of the hardware resource, and outputs a normal value as a result of the check when it is determined that the hardware resource satisfies a predetermined performance. The image forming apparatus according to claim 2, wherein an abnormal value is output as a result of the check when it is determined that the performance of the image forming apparatus does not satisfy the above.   The activation unit activates the program set in the setting unit in association with the check unit when a normal value is supplied from the check unit as a result of the performance check of the central processing unit (CPU). 14. The image according to claim 13, wherein when an abnormal value is supplied from the check unit as a result of the check, the program set in the setting unit in association with the check unit is not started. Forming equipment.   The activation unit activates the program set in association with the check unit in the setting unit when a normal value is supplied from the check unit as a result of the memory performance check, and the result of the check is 14. The image forming apparatus according to claim 13, wherein when an abnormal value is supplied from the checking unit, the program set in the setting unit in association with the checking unit is not started. The setting means sets the checking means in association with a directory where the program exists or a higher directory,
The activation unit mounts a directory of the program set in association with the check unit when the result of the check is a normal value, and associates the directory with the check unit when the result of the check is an abnormal value. 16. The image forming apparatus according to claim 14, wherein a directory of the program set in advance is not mounted.   The checking unit checks a predetermined identifier stored in the hardware resource, and outputs a normal value as a check result when it is determined that the predetermined identifier satisfies a predetermined condition. 8. The image forming apparatus according to claim 2, wherein an abnormal value is output as a check result when it is determined that the identifier does not satisfy a predetermined condition.   The checking means checks an identifier stored in the SD card, and outputs a normal value as a check result when it is determined that the identifier matches the identifier of the slot in which the SD card is inserted. 18. The image forming apparatus according to claim 17, wherein when it is determined that the identifier does not match the identifier of the slot in which the SD card is inserted, an abnormal value is output as a result of the check.   The activation unit, when a normal value is supplied from the check unit as a result of the check, executes the program set in the setting unit in association with the check unit, and outputs an abnormal value as a result of the check. 19. The image forming apparatus according to claim 17, wherein, when supplied from the check unit, the program set in the setting unit in association with the check unit is not executed.   6. The image forming apparatus according to claim 5, wherein the storage unit is created in an area on a memory that can be directly accessed by the check unit.   2. The image forming apparatus according to claim 1, wherein the activation unit is activated by an operating system activated after power is turned on.   2. The program according to claim 1, wherein the program includes an application program for performing image forming processing, a control service program for managing hardware resources used in the image forming processing, and an operating system program. Image forming apparatus. A program starting method for an image forming apparatus, comprising: a hardware resource used in an image forming process; and a program for performing a process related to the image forming.
An analyzing step of analyzing a setting unit that sets an association between the program and a checking unit that performs a check on the hardware resource;
A checking means starting step, wherein the starting means starts the checking means according to a result of the analysis;
A program activating step of activating the program associated with the checking means in accordance with a result of the check by the checking means. A computer having hardware resources used in image formation processing and a program for performing processing related to image formation,
Checking means for checking the hardware resources;
Setting means for setting an association between the check means and the program;
A program starting program for functioning as starting means for starting the program related to the checking means in accordance with the result of the check by the checking means.

Images