JP2008097356A - Digital multifunction machine, control method therefor, program, and storage medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem in a multi-CPU system wherein when a symmetrical OS compatible with multi-CPU is not used, or when CPUs different in architecture are used, it is required to allocate tasks for various processing to either one of the CPUs depending on purposes and required to clearly specify transmission across CPUs in a transmission API to transmit a message or an event across the CPUs. <P>SOLUTION: All the tasks required for the system are managed as a table, and a task name, a task number and the CPU to be operated are described as members. A plurality of tables may be provided separately, for example, the table when using multiple A CPUs, and the table when using only one CPU. The tables are switched by detecting the number of the CPUs. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a file system of an image forming apparatus.

  Conventionally, it has been difficult to operate a semaphore or message queue by installing an OS that does not support multiple CPUs on a multiple CPU system.

As a conventional example, Patent Document 1 discloses a method of using a shared buffer in a multi CPU as a message buffer.
JP-A-7-73151

  In a multi-CPU system, the operating systems on multiple CPUs are different, or are not compatible with multiple CPUs, or even if they are the same OS, the CPU architecture is different and the OS cannot be used symmetrically. Tasks for performing various processes are allocated and operated on one of the CPUs according to usage. At this time, when message transmission, event transmission, and semaphore acquisition and release are performed across CPUs, it is necessary to explicitly specify transmission across CPUs in an API for message transmission.

  All semaphore IDs managed on multiple CPUs are collected and managed as a table. Have this table on every CPU. The same processing is also performed for the task ID, message queue ID, and the like.

  By referring to this table, you can see which semaphore is created and managed on which CPU OS.

  If the setting is made so that only one CPU of the multi-CPU system is not used, the multi-CPU system is not a multi-CPU system but a single CPU system. However, for example, when using multiple CPUs, only one CPU is used. You can have multiple tables separately from the table when you do not. These tables detect and switch the number of CPUs. Each CPU transmits a message to one of the CPUs via the message transmission API when transmitting a message to the task. At that time, the CPU refers to the table to determine which CPU should be transmitted. By doing this, it is possible to cope with a case where the systems are different, such as changing the number of CPUs, and it is possible to make use of the performance of the multi-CPU even when the system is not a symmetric system.

  In a non-symmetric OS using a plurality of CPUs, resources can be exchanged between the CPUs. In addition, even when the number of CPUs is changed, it is possible to cope without changing the source or the like.

  Conventionally, it has been difficult to operate a semaphore or message queue by installing an OS that does not support multiple CPUs on a multiple CPU system.

  In a multi-CPU system, the operating systems on multiple CPUs are different, or are not compatible with multiple CPUs, or even if they are the same OS, the CPU architecture is different and the OS cannot be used symmetrically. Tasks for performing various processes are allocated and operated on one of the CPUs according to usage. At this time, when message transmission, event transmission, and semaphore acquisition and release are performed across CPUs, it is necessary to explicitly specify transmission across CPUs in an API for message transmission.

  All semaphore IDs managed on multiple CPUs are collected and managed as a table. Have this table on every CPU. The same processing is also performed for the task ID, message queue ID, and the like.

  By referring to this table, you can see which semaphore is created and managed on which CPU OS.

  If the setting is made so that only one CPU of the multi-CPU system is not used, the multi-CPU system is not a multi-CPU system but a single CPU system. However, for example, when using multiple CPUs, only one CPU is used. You can have multiple tables separately from the table when you do not. These tables detect and switch the number of CPUs. Each CPU transmits a message to one of the CPUs via the message transmission API when transmitting a message to the task. At that time, the CPU refers to the table to determine which CPU should be transmitted. By doing this, it is possible to cope with a case where the systems are different, such as changing the number of CPUs, and it is possible to make use of the performance of the multi-CPU even when the system is not a symmetric system.

  In a non-symmetric OS using a plurality of CPUs, resources can be exchanged between the CPUs. In addition, even when the number of CPUs is changed, it is possible to cope without changing the source or the like.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a block diagram showing an embodiment of an image input / output device (data processing device) on which a controller unit as an electronic component according to the present invention is mounted. A local area network (600) is connected to a host computer (in this embodiment, a first host computer 601 and a second host computer 602).

  The image input / output system 100 includes a reader device (reader unit) 200 that performs image data reading processing, a printer device (printer unit) 300 that performs image data output processing, a keyboard that performs image data input / output operations, In addition, an operation unit 150 having a liquid crystal panel for displaying / setting image data and various functions, image data read by controlling the reader device 200, and code data received from the host computers 601 and 602 via the LAN 600 An image storage unit 160 that can store / save image data generated from the computer is mounted, and is configured by a control device (controller unit) 110 formed of a single electronic component that is connected to these components and controls the components. ing.

  The reader device 200 includes a document feeding unit 250 that transports document paper, and a scanner unit 210 that optically reads a document image and converts it into image data as an electric signal. A paper feed unit 310 having a plurality of paper feed cassettes to be accommodated, a marking unit (part) 320 for transferring / fixing image data onto recording paper, and a sort process and a stapling process on the printed recording paper, And a paper discharge unit (part) 330 for discharging the paper.

  The control device 110 controls the reader unit 200 to read image data of a document, and controls the printer unit 300 to output the image data to a recording sheet to provide a copy function. The scanner function converts image data read from the reader unit 200 into code data and transmits the code data to the host computers 601 and 602 via the network 600. Code data received from the host computer via the network 600 is converted into image data. It has a printer function for conversion and output to the printer unit 300, and other functional blocks.

  FIG. 2 is a cross-sectional view showing details of the reader unit 200 and the printer unit 300.

  In the reader unit 200, the original sheets stacked on the original feeding unit 250 are sequentially fed onto the platen glass 211 one by one from the top in accordance with the stacking order, and after a predetermined reading operation is completed by the scanner unit 210, As for the read original paper, the original on the platen glass 211 is discharged to the discharge tray 219. When the original paper is conveyed onto the platen glass 211, the lamp 212 is turned on, then the movement of the optical unit 213 is started, and the original paper is irradiated and scanned from below. The reflected light from the original paper is guided to a CCD image sensor (hereinafter referred to as “CCD”) 218 via a plurality of mirrors 214, 215, 216 and a lens 217, and the scanned original image is read by the CCD 218. Read. The image data read by the CCD 218 is transferred to the controller unit 110 after predetermined processing.

  When the document feeding unit 250 has a document feeding reading function, the document sheets stacked on the document feeding unit 250 pass through the document feeding reading position 240 at a constant speed. In this case, the optical unit 213 moves to the document flow reading position 240, irradiates the document conveyed at a constant speed by the lamp 212, reads the image by the CCD 218 as needed, generates image data, and transfers the image data to the controller unit 110.

  Next, in the printer unit 300, a laser beam corresponding to the image data output from the controller unit 110 is issued from a laser issuing unit 322 driven by a laser driver 321, and the photosensitive drum 323 is electrostatically charged according to the laser beam. A latent image is formed, and a developer is attached to a portion of the electrostatic latent image by the developing device 324.

  On the other hand, recording paper is fed from any of the cassette 311, the cassette 312, the cassette 313, the cassette 314, and the manual paper feed stage 315 at the timing synchronized with the start of laser light irradiation, and is conveyed to the transfer unit 325 by the conveyance path 331. Then, the developer adhering to the photosensitive drum 323 is transferred to the recording paper. The recording sheet on which the image data is transferred is conveyed to the fixing unit 327 by the conveying belt 326, and the image data is fixed on the recording sheet by the heating / pressurizing process in the fixing unit 327. The recording paper that has passed through the fixing unit 327 passes through the transport path 335 and the transport path 334 and is discharged to the paper discharge bin 328. When the print surface is reversed and discharged to the paper discharge bin 328, the recording paper is guided to the transport path 336 and the transport path 338, from which the recording paper is transported in the reverse direction, passes through the transport path 337 and the transport path 334, and is discharged. It is discharged to a paper bottle 328. Although not shown in the figure, it is possible to mount a paper discharge unit instead of the paper discharge bin. The paper discharge unit bundles the discharged recording paper, sorts the recording paper, and staples the sorted recording paper. And so on.

  When image data is recorded on both sides of a recording sheet, after passing through the fixing unit 327, the recording sheet is guided from the conveying path 336 to the conveying path 333 by the flapper 329, and then the recording sheet is conveyed in the reverse direction. The flapper 329 is guided to the conveyance path 338 and the refeed conveyance path 332. The recording sheet guided to the refeed conveyance path 332 passes through the conveyance path 331 and is fed to the transfer unit 325 in the same manner as described above.

  FIG. 3 is a block diagram showing details of the control device (controller unit) 110.

  That is, the main controller 111 includes a CPU 112, a bus controller 113, and functional blocks including various controller circuits described later, and is connected to the ROM 114 via the ROM I / F 115, and to the DRAM 116 via the DRAM I / F 117. Connected, connected to the codec 119 via the codec I / F 118, connected to the network controller 121 via the network I / F 123, and performs a predetermined control operation with the LAN 600 via the connector 122.

  In the ROM 114, various control programs executed by the CPU 112 of the main controller 111 and calculation data are confirmed. The DRAM 116 is used as a work area for the CPU 112 to operate and an area for storing image data. The codec 119 compresses the raster image data stored in the DRAM 116 by a known compression method such as MH / MR / MMR / JBIG, and decompresses the compressed data into a raster image. An SRAM 120 is connected to the codec 119, and the SRAM 120 is used as a temporary work area for the codec 119.

  The main controller 111 is connected to the scanner I / F 140 via the scanner bus 141, connected to the printer I / F 145 via the printer bus 146, and further connected to an expansion board via a general-purpose high-speed bus 125 such as a PCI bus. It is connected to an expansion connector 124 and an input / output control unit (I / O control unit) 126 for connection.

  The I / O control unit 126 is equipped with two channels of an asynchronous serial communication controller 127 for transmitting and receiving control commands to and from the reader unit 200 and the printer unit 300. The serial communication controller 127 is an I / O controller. It is connected to the scanner I / F 140 and the printer I / F 145 via the bus 128.

  The scanner I / F 140 is connected to the scanner connector 142 via the first asynchronous serial I / F 143 and the first video I / F 144, and the scanner connector 142 is further connected to the scanner unit 210 of the reader unit 200. Yes. The scanner I / F 140 performs desired binarization processing and scaling processing in the main scanning direction and / or sub-scanning direction on the image data received from the scanner unit 210, and is sent from the scanner unit 210. A control signal is generated based on the video signal, and the image data is transferred to the main controller 111 via the scanner bus 141.

  The printer I / F 145 is connected to the printer connector 147 via the second asynchronous serial I / F 148 and the second video I / F 149, and the printer connector 147 is further connected to the marking unit 320 of the printer unit 300. Has been. Then, the printer I / F 145 performs smoothing processing on the image data output from the main controller 111 and outputs the image data to the marking unit 320. Further, the printer I / F 145 is generated based on the video signal sent from the marking unit 320. A control signal is output to the printer bus 146.

  The CPU 112 operates based on a control program read from the ROM 114 via the ROM I / F 115, and interprets, for example, PDL (page description language) data received from the first and second host computers 601 and 602. The raster image data is expanded.

  The bus controller 113 controls data transfer input / output from / to an external device connected to the scanner I / F 140, printer I / F 145, and other expansion connectors 124, and the like. Controls DMA data transfer. That is, for example, the above-described data transfer between the DRAM 116 and the codec 119, the data transfer from the scanner unit 210 to the DRAM 116, the data transfer from the DRAM 116 to the marking unit 320, and the like are controlled by the bus controller 113 and transferred by DMA. The

  The I / O control unit 126 is connected to the panel I / F 132 via the LCD controller 131 and the key input I / F 130, and the panel I / F 132 is connected to the operation unit 150. The I / O control unit 126 is connected to an EEPROM 135 as a nonvolatile memory, is connected to a hard disk drive (HDD) 162 capable of writing / reading image data via an E-IDE connector 161, and It is connected to a real time clock module 133 that updates / stores the date and time managed in the device. The real time clock module 133 is connected to the backup battery 134 and backed up by the backup battery 134.

  FIG. 4 is a block diagram showing the internal details of the main controller 111.

  The processor core 401 is connected to a system bus bridge (SBB) 402 via a 64-bit processor bus (SC bus). The SBB 402 is a 4 × 4 64-bit crossbar switch, and is connected to a memory controller 403 that controls an SDRAM or ROM including a cache memory in addition to the processor core 401 via a dedicated local bus (MC bus). The G bus 404, which is a graphic bus, and the B bus 405, which is an IO bus, are connected to a total of four buses. The SBB 402 is designed to ensure simultaneous parallel connection between these four modules as much as possible. A data compression / decompression unit (CODEC) 418 is also connected via a CODEC I / F.

  The G bus 404 is cooperatively controlled by a G bus arbiter (GBA) 406 and is connected to a scanner / printer controller (SPC) 408 for connecting to a scanner or a printer. The B bus 405 is cooperatively controlled by a B bus arbiter (BBA) 407. In addition to the SPC 408, a power management unit (PMU) 409, an interrupt controller (IC) 410, and a serial interface controller (SIC) 411 using UART. USB controller 412, parallel interface controller (PIC) 413 using IEEE1284, LAN controller (LANC) 414, general-purpose input / output controller (MISC) 415, and PCI bus interface (PCIC) 416.

  The B bus arbiter 407 is an arbitration for cooperatively controlling the B bus 405. The B bus 405 receives a bus use request for the B bus 405, and after arbitration, is given to one master selected for use permission. Is prohibited from performing bus access. The arbitration method has three levels of priority, and a plurality of masters are assigned to each priority.

  The interrupt controller 410 accumulates interrupts from the functional blocks and the controller unit 110 described above, and redistributes them to the controllers 408, 411-416 and non-maskable interrupts (NMI) supported by the CPU 401.

  The power management unit 409 manages the power for each functional block, and monitors the power consumption of the controller unit 110 as an electronic component composed of one chip. That is, the controller unit 110 is composed of a large-scale ASIC (application-specific IC) with a built-in CPU 401. For this reason, when all the functional blocks operate simultaneously, a large amount of heat is generated, and the controller unit 110 itself is There is a risk of being destroyed.

  Therefore, in order to prevent such a situation, the power consumption is managed for each functional block, and the power consumption amount of each functional block is integrated in the power management unit 409 as a power management level. Then, the power management unit 409 adds up the power consumption amounts of the functional blocks, and collectively monitors the power consumption amounts of the functional blocks so that the power consumption amount does not exceed the limit power consumption.

  The G bus arbiter 406 controls the G bus 404 in a coordinated manner by a central arbitration method, and has a dedicated request signal and a permission signal for each bus master. In addition, as a method of giving priority to the bus master, all bus masters have the same priority, a fair arbitration mode in which the bus right is granted fairly, and a priority arbitration mode in which the bus is preferentially used by any one bus master Either of these can be specified.

  FIG. 5 is a diagram illustrating an example of the operation unit 150.

  A user interface 500 can set various copy modes (for example, duplex setting, group, sort, staple output, etc.). These copy mode setting means may be hard keys or soft keys displayed on the touch panel. Reference numeral 501 denotes a start button, which is started when the button is pressed.

  FIG. 6 shows a document reading setting screen displayed on the user interface 500 when the “continuous reading mode” for repeatedly reading and storing the document is selected as the copy mode after the copy process is started by pressing the start button 501. This is an example of 502. The original reading setting screen 502 is provided with a “confirm” button 503 for entering a mode in which images read up to that time are displayed and an “end reading” button 504 for collectively outputting images read so far. Yes.

  FIG. 7 shows a read image confirmation screen that is displayed when the “Confirm” button 503 is pressed on the original reading setting screen 502. The area 505 displays the total number of pages of images accumulated so far and the currently displayed page. The page number is displayed. Reference numerals 506 and 507 denote “page move” buttons for moving the pages of the accumulated images. When the user presses 506, the user moves to the previous page, and when the user presses 507, the user moves to the next page. Reference numerals 508 and 509 denote “enlarge / reduce” buttons for enlarging / reducing the confirmation image. When the user presses 508, the confirmation image is reduced, and when the user presses 509, the confirmation image is enlarged. Reference numeral 510 denotes an accumulated image confirmation screen on which the contents of the page displayed in 505 are displayed. Reference numeral 511 denotes a “reread” button. When the “reread” button 511 is pressed, the page displayed at that time is stored, and the image confirmation screen is closed. When the image confirmation screen is closed, the screen returns to the original reading setting screen 502 so that the original can be read. At this time, the document reading is executed in the reread mode. Reference numeral 512 denotes a “close” button. When the “close” button 512 is pressed, the image confirmation screen is closed. When the original confirmation screen is closed, the original reading setting screen 502 is displayed again, and the original can be read. At this time, the document reading is executed in the continuous reading mode.

  Note that the above-described continuous reading mode refers to storing and storing image data again from the end (final image) in which the read image data is stored and stored, and storing all image data stored and stored during processing as a set. This means that the data is handled as image data, and the re-read mode means that specific image data stored and stored is replaced with newly read image data. In either case, the document reading instruction is performed by pressing the start button 501.

  FIG. 8 is a flowchart of the continuous read copy process in the present invention.

  In step S1001, it is determined whether or not a start instruction has been given due to the start button 501 being pressed. If the start button 501 is not pressed, the determination is repeated until the start button 501 is pressed. If the start button 501 is pressed, the process advances to step S1002 to check whether “continuous reading mode” is selected. If the “continuous reading mode” is not set in S1002, the process proceeds to S1012 and a normal copy process is performed and the process is terminated. If the “read image confirmation mode” is set, the process advances to step S1003 to execute a document reading process of reading a bundle of documents set on the automatic paper feeder (DF) or reading a document placed on a pressure plate. To do. When the process ends, an instruction from the operation unit 150 becomes possible. In step S1004, it is determined whether an instruction for image confirmation processing (preview processing) stored in the image storage unit 160 has been issued. If execution of the image confirmation process is instructed, the process proceeds to S1005, where the image confirmation process (preview process) is performed, and then the process proceeds to S1006. If there is no instruction to execute image confirmation processing, the process advances to step S1006. In S1006, it is determined whether or not “re-read” is instructed. The re-reading instruction is performed in the preview process of S1005. When the re-reading instruction is given, the image storage location of the page to be re-read is stored. If re-reading is instructed, the process proceeds to S1007. If re-reading is not instructed, the process proceeds to S1008. In step S1007, image data discarding (deleting) processing of the page stored when the re-reading instruction is issued is executed. Thereafter, the process returns to S1003 to execute the original reading process, and replace the image data of the reread target page. The original reading process S1003 includes a reading process for all originals set on the automatic paper feeder (DF), a reading process for originals placed on the pressure plate, and a specified number of sheets from the original set on the automatic paper feeder. Can be performed, and at the time of re-reading, it is specified that the number of read pages is one page. In step S1008, an instruction to stop the continuous reading process is determined. If there is an instruction to cancel in S1008, the process proceeds to S1009, and after executing the read image discarding process S1009 for discarding all the image data read and accumulated so far, the copy process is terminated. If there is no cancel instruction in S1008, the process proceeds to S1010. In step S1010, a read end instruction is determined. If the end of reading is instructed in step S1010, the process advances to step S1011 to execute a read image printing process for printing all the image data read up to that point, and then the copy process ends. If the reading end is not supported in S1010, the process proceeds to S1013 to determine the reading instruction. If there is an instruction to read in S1013, the process returns to S1003 to execute the original reading process. If there is no read instruction in S1013, the process returns to S1004. That is, when there is no instruction from the operation unit 160, the instruction waits for any of image confirmation, re-reading, cancellation, reading end, and reading.

  FIG. 9 is a flowchart of the document reading process.

  In S2001, the state of the automatic paper feeder (DF) is determined. When the DF is open, the process proceeds to S2006, the original reading process from the pressure plate is performed, and the process is terminated. When the DF is closed, the process proceeds to S2002, and it is determined whether or not a document is set on the DF. If no document is set in the DF, the process proceeds to S2006, where the document reading process from the pressure plate is performed, and the process ends. If a document is set in the DF, the process proceeds to S2003, and it is determined whether or not a re-read process is instructed. If it is determined in S2003 that re-reading is instructed, the process proceeds to S2004, and the image reading process for one page from the document set in the DF is terminated. If it is determined in S2003 that re-reading is not instructed, the process proceeds to S2005, where all pages of the document set in the DF are read, and the process ends.

  FIG. 10 is a flowchart of accumulated image confirmation (preview) processing.

  In step S3001, it is determined whether an image storage destination for checking the stored image has been specified. The image data read repeatedly in the continuous reading copy process is managed under the job management unit 902 of the document management unit 900 that is the image storage destination used by the continuous reading copy process being executed. The job management unit 902 Is specified so that it is possible to trace from the first page to the last page of the image data read and accumulated so far. If there is no designation in S3001, the process is terminated. That is, the preview process is not executed. If specified in step S3001, the process advances to step S3002 to specify the first page of the stored image. In S3003, image data to be displayed on the accumulated image confirmation screen 510 is generated from the accumulated image data. In this embodiment, image data is generated immediately before being displayed on the accumulated image confirmation screen 510. However, image data for displaying the accumulated image confirmation screen is generated at the time of reading and accumulating the document, and is associated with the original image and stored externally. It may be stored in the unit 160. In S3004, the image data generated in S3003 is displayed on the accumulated image confirmation screen 510. In step S3005, an input instruction is waited, and the input instruction is looped and waited. In step S3006, it is determined whether an instruction to display the next page has been issued. If an instruction to display the next page has been issued, the process advances to step S3007. In S3007, it is determined whether the stored image data is at the end, and if it is at the end, the process returns to S3005 and waits for an input instruction again. If it is determined in S3007 that it is not the tail end, the process proceeds to S3003 to generate image data for displaying the stored image confirmation screen of the specified page, and the process is repeated. In step S3008, it is determined whether an instruction to display the previous page has been issued. If an instruction to display the previous page is given, the process advances to step S3009 to determine whether the stored image data is the head. If it is determined that the head, the process returns to S3005 and waits for an input instruction again. If it is determined that it is not the head, the process advances to S3003 to generate image data for displaying the stored image confirmation screen of the specified page, and the process is repeated. In step S3010, it is determined whether an instruction to reduce the image displayed on the stored image confirmation screen 510 has been issued. If it is determined that reduction display has been instructed, the process advances to S3003 to generate image data for displaying the stored image confirmation screen of the specified page, and the process is repeated. If there is no reduction display instruction, the process advances to step S3011 to determine whether an enlargement display instruction has been issued. If it is determined in S3011 that an enlargement display instruction has been issued, if specified, the process proceeds to S3003 to generate image data for displaying the accumulated image confirmation screen of the specified page, and the process is repeated. If there is no instruction for enlarged display, the process advances to step S3012 to determine whether an instruction for rereading an image has been given. If an instruction to re-read an image is issued in S3012, the process advances to S3013 to store (hold) identification information for specifying where the currently displayed page is managed in the document management unit 900, and the process ends. The information held here is transmitted to the above-described image reading process, and the re-reading process is executed. If there is no re-reading instruction in S3012, the process returns to S3005 and waits for an input instruction.

  FIG. 11 is a diagram illustrating an internal software structure of the control device 110. Reference numeral 700 denotes controller software, which includes a protocol interpretation unit 701, a job control unit 702, and a device unit 703. The protocol interpretation unit 701 interprets commands (protocols) sent from the host computer 601 and the operation unit 150 via each interface (411-414), and requests the job control unit 702 to execute a job. . The job control unit 702 executes various jobs based on requests from the protocol interpretation unit. The device unit 703 includes driver software that controls each unit constituting the image input / output system 100, and is used when the job control unit 702 executes a job.

  FIG. 12 is a diagram illustrating the structure of the job control unit 702.

  In the figure, 700 is controller software, 701 is a protocol interpretation unit, 702 is a job control unit, and 703 is a device unit. The job control unit 702 includes a job generation unit 800, a job processing unit 810, a document processing unit 820, a page processing unit 830, a band processing unit 840, and a device allocation unit 850. The job processing unit 810 includes a job management unit 811, a binder management unit 812, and a document management unit 813. The device unit 703 can include a plurality of devices such as a first device 851, a second device 852, and a third device 853.

  A series of operation requests sent from the host computers 601 and 602 and the operation unit 150 are sent via the interfaces (411 to 414) in the form of commands (protocols). The sent command is interpreted by the protocol interpretation unit 701 and then sent to the job control unit 702. At this point, the command is converted into a form that can be understood by the job control unit 702.

  The job generation unit 800 generates a job 814. The job 814 includes various jobs such as a copy job, a print job, a scan job, and a fax job. The protocol interpreted by the protocol interpreter 701 includes, for example, various setting information such as the name of the document to be printed, the number of copies to be printed, and the designation of the output destination paper discharge tray, and the print data itself (PDL data). Etc. are included. The job 814 is sent to the job processing unit 810 for processing. The job processing unit 810 has settings related to the entire binder, such as a job management unit 811 that performs settings related to the entire job, such as the output order of a plurality of binders that constitute a job, and an output order of a plurality of documents that constitute the binder. A binder management unit 812 and a document management unit 813 for making settings related to the entire document such as the output order of a plurality of pages constituting the document, and settings and processing related to the entire job 814 are performed.

  Further, the job processing unit 810 divides the job 814 other than the settings and processing related to the entire job 814 into the binder 815 that is a smaller work unit constituting the job 814, and the binder 815 other than the settings and processing related to the entire binder 815. Is divided into documents 816, which are units of smaller work that constitutes. The document 816 is associated with the input document 821 on a one-to-one basis, and the input document 821 is converted into an output document 822 by the document processing unit 820. For example, when considering a scan job in which a bundle of documents is read by a scanner and converted into a plurality of image data, an input document 821 describes settings and operation procedures related to the bundle of documents, and a plurality of image data. An output document 822 contains the setting and operation procedures. A document processing unit 820 has a role of converting a bundle of paper into a plurality of image data.

  The document processing unit 820 performs conversion processing from the input document 821 in units of documents to the output document 822, and divides the input page 831 that is a unit of smaller work except for setting and processing related to the entire document, and the page processing unit 830. Request processing. This is exactly the same as when the job processing unit 815 is devoted to processing in units of jobs and generates the binder 815 and the document 816 for more detailed work. Specifically, the setting and operation in units of documents relate to page order such as page rearrangement, designation of double-sided printing, addition of a cover, and OHP insertion.

  The page processing unit 830 performs conversion processing from the input page 831 to the output page 832 in page units. For example, in the case of the scan job described above, the input page 831 describes various settings such as the reading resolution and reading direction (landscape / portrait) and the procedure, and the output page 832 stores the image data storage location. Etc. Settings and procedures are written.

  Up to this point, we have explained that the job unit is gradually reduced so that it can be handled in page units. If an expensive system can have a page memory for one page, the job may be subdivided and processed in units of pages. However, in reality, there is a system that processes the job 814 with a memory (band memory) for several lines when the page memory for one page cannot be provided due to a problem such as memory cost. In such a case, the conversion process is performed by dividing the page into bands, which are finer units. The input band 841, the band processing unit 840, and the output band 842 are the same as those in the page.

  The job processing unit 810, the document processing unit 820, the page processing unit 830, and the band processing unit 840 all use various physical devices that make up the image input / output system 100 when processing proceeds. Naturally, device conflict occurs when a plurality of processing units work simultaneously, and the device allocation unit 850 mediates the competition. The first to third devices 851 to 853 shown in the figure as examples are logical devices assigned to the respective processing units by the device assigning unit 850. For example, a page memory, a band memory, a document feeding unit 250, A marking unit 320 engine, a scanner unit 210, and the like are conceivable.

  FIG. 13 is a diagram illustrating a management structure of the document management unit 900 that manages image data stored in the image storage unit 160.

  The document management unit 900 includes a folder management unit 901, a job management unit 902, a binder management unit 903, a document management unit 904, and a page management unit 905, each having management information (attribute value). The document management unit 900 includes one or a plurality of folder management units 901, and management information of the folder management unit 901 is stored. The folder management unit 901 includes one or a plurality of job management units 902, and stores management information of the job management unit 902. The job management unit 902 includes one or a plurality of binder management units 903, and management information of the binder management unit 902 is stored. Further, the job management unit 902 can store / save attribute values stored in the job management unit 811 with information necessary for the operation of the job 814 processed by the job control unit 702. The binder management unit 903 includes one or a plurality of document management units 904 and stores management information of the document management unit 904. Further, the binder management unit 903 can store / save attribute values stored in the binder management unit 812 with information necessary for the operation of the binder 815 processed in the job control unit 702. The document management unit 904 includes one or a plurality of page management units 905 and stores management information of the page management unit 905. Further, the document management unit 904 can store / save the attribute value stored in the document management unit 813 processed by the job control unit 702 and the attribute value of the output document 822 processed by the document processing unit 820. it can. A page 905 includes one page of image data read by the scanner, one page of image data developed from the PDL transmitted from the host computer, and one page of data received by FAX. It is associated with image data. Further, the page management unit 905 can store / save the attribute value of the output page 832 processed by the page processing unit 830 of the job control unit 702. That is, it is possible to reproduce the job 814 submitted at the time of image accumulation from the information stored in the document management unit 900 and the image data stored in the image storage unit 160. It is also possible to perform operations different from the job at the time of submission by resetting the stored information.

  FIG. 14 is an explanatory diagram of a multi-CPU system that can access a main storage device (shared memory that can be shared and accessed by CPU-A and CPU-B). Here, two CPUs are temporarily installed. Although the system will be described, the present invention also applies to the case where a CPU other than CPU-A and CPU-B in FIG. 14 is used. In FIG. 14, 1001 is CPU-A, 1002 is CPU-B, 1003 is a shared memory, 1004 is a system bus bridge, 1005 is a memory controller, 1006 is a hard disk controller, and 1007 is a hard disk. Reference numerals 1004 and 1005 are the same as those described in FIG. 4, and a description of the data access method between the CPU and the memory is omitted here. CPU-A and CPU-B can read and write data to the 1003 shared memory via a system bus bridge and a memory controller, respectively. Similar to the memory controller, the 1006 hard disk controller is a controller that controls reading and writing to the hard disk, and is connected to the hard disk via an E-IDE connector as shown in FIG. A hard disk 1007 is an E-IDE standard hard disk and has a very large capacity with respect to the main storage device (shared memory). It is possible to access from CPU-A and CPU-B via the hard disk controller.

  FIG. 15 is an explanatory diagram regarding a semaphore. 7601 is task 1, 7602 is task 2, 7603 is a semaphore, and 7604 is processing to be performed by the task. Normally, in a multitasking OS in which multiple tasks (processes and programs) are executed simultaneously, a semaphore is used to prevent content destruction and inconsistency by accessing multiple resources simultaneously to one resource. .

  Suppose that there are now two or more tasks that you want to perform a specific process. In order to perform processing, it is necessary to acquire a semaphore (P operation). When one semaphore gets one task, the other task has to wait for acquisition. In this example, task 2 first acquired a semaphore. While task 2 has acquired a semaphore, task 1 enters a semaphore wait state. Task 1 releases the semaphore when processing is completed (V operation). Since the semaphore has been released, task 1 can acquire the semaphore that has been waiting, and can then perform processing. A semaphore makes it possible to exclude one resource or process. A detailed explanation of semaphores beyond this is omitted because it is already known. Please refer to the OS books for message queues and events.

  FIG. 16 is an explanatory diagram of this embodiment. 7001 is CPU-A in a multi-CPU system, 7002 is CPU-B, 7003 is CPU-A firmware expanded on a storage device, 7004 is CPU-B firmware, 7005 is semaphore 1, 7006 is semaphore 2, 7007 is message queue 1, 7008 is semaphore 3, 7009 is semaphore 4, 7010 is message queue 2, 7011 is task 1, and 7012 is task 2. Semaphore 1 and semaphore 2 are generated by the OS on CPU-A, and the OS on CPU-A also performs management. The message queue 1 is generated by the OS on the CPU-A, and the OS on the CPU-A also performs management. Semaphore 3 and semaphore 4 are generated by the OS on CPU-B, and the OS on CPU-B also performs management. The message queue 2 is generated by the OS on CPU-B, and the OS on CPU-B also performs management. Task 1 is a task operating on CPU-A, and task 2 is a task operating on CPU-B.

  FIG. 17 is an explanatory diagram of this embodiment. 7101 is the CPU-A in the multi-CPU system, 7102 is the CPU-B, 7103 is the CPU-A firmware developed on the storage device, 7104 is the CPU-B firmware, and 7105 is the program in the CPU-A firmware. Perform P action of semaphore with. Reference numeral 7106 denotes a program for performing the V operation of the semaphore, and reference numeral 7107 denotes a program for transmitting a message to the message queue. Reference numeral 7108 denotes a program in the firmware of the CPU-B, which performs a semaphore P operation. Reference numeral 7109 denotes a program for performing the V operation of the semaphore. Reference numeral 7110 denotes a program for transmitting a message to the message queue. 7111 is semaphore 1, 7112 is semaphore 2, 7113 is message queue 1, 7114 is semaphore 3, 7115 is semaphore 4, 7116 is message queue 2, 7117 is task 1, and 7118 is task 2. Taking the case of two CPUs as an example, when both CPU-A and CPU-B are operating, task 1 and task 2 are distributed so that they are executed by different CPUs. Semaphore 1 and semaphore 2 are mainly used by task 1, but task 2 is also used occasionally. Semaphore 3 and semaphore 4 are used by task 2, but task 1 is also used occasionally. Therefore, the OS of CPU-A manages semaphore 1 and semaphore 2, and the OS of CPU-B manages semaphore 3 and semaphore 4. The same is true for message queues.

  FIG. 22 is an explanatory diagram of this embodiment, but shows a case where CPU-B is stopped. 7701 is the CPU-A in the multi-CPU system, 7702 is the CPU-B, 7703 is the CPU-A firmware developed on the storage device, and 7705 is the program in the CPU-A firmware, and performs the P operation of the semaphore. Reference numeral 7706 denotes a program for performing the V operation of the semaphore, and reference numeral 7707 denotes a program for transmitting a message to the message queue. 7710 is semaphore 1, 7711 is semaphore 2, 7713 is semaphore 3, 7714 is semaphore 4, 7116 is message queue 1, 7717 is message queue 2, 7708 is task 1, and 7709 is task 2. Taking the case of two CPUs as an example, when CPU-B is stopped among CPU-A and CPU-B, task 1 and task 2 are executed on CPU-A. In this case, all semaphores and message queues are created and managed on the OS of CPU-A.

  FIG. 18 is an example in which task 1 on CPU-A acquires semaphore 1 on CPU-A. Reference numeral 7201 denotes a CPU-A in the multi-CPU system, 7202 denotes a CPU-B, and 7203 denotes a program on the firmware of the CPU-A developed on the storage device, which is a program for performing the P operation of the semaphore.

  7204 is a program on the firmware of the CPU-B developed on the storage device, and is a program for performing the P operation of the semaphore. 7205 is semaphore 1, 7206 is semaphore 3, 7211 is task 1, and 7212 is task 2. When task 1 acquires semaphore 1, a program for performing a semaphore P operation is executed. A program for performing the semaphore P operation refers to a table to be described later, and since the semaphore 1 is a semaphore on its own CPU, the semaphore is acquired as it is. The same applies to semaphore release and message transmission. This is the case when only one CPU in FIG. 22 is operating.

  FIG. 19 is an example in which task 1 on CPU-A acquires semaphore 1 on CPU-A. 7301 is CPU-A in the multi-CPU system, 7302 is CPU-B, 7303 is a program on the firmware of CPU-A developed on the storage device, and is a program for performing the P operation of the semaphore.

  7304 is a program on the firmware of the CPU-B developed on the storage device, and is a program for performing the P operation of the semaphore. 7305 is semaphore 1, 7306 is semaphore 3, 7311 is task 1, and 7312 is task 2. When task 1 acquires semaphore 3, first, a program that performs a semaphore P operation on its own CPU is executed. A program that performs a semaphore P operation refers to a table that will be described later, and since semaphore 3 is a semaphore on CPU-B, it issues an instruction to CPU-B to acquire semaphore 3. Thereafter, CPU-B executes a program for performing a semaphore P operation on CPU-B, and acquires semaphore 3. The same applies to semaphore release and message transmission. If two CPUs in FIG. 17 are operating, this state may occur.

  FIG. 20 is a diagram of a semaphore management table in this embodiment. 7401 is CPU-A, and 7402 is a routine for determining on which CPU the semaphore in the semaphore P operation is managed. 7403 is semaphore 1, 7404 is semaphore 2, 7405 is semaphore 3, and 7406 is semaphore 4. 7407 is a semaphore management table for multiple CPUs, and 7408 is a semaphore management table for single CPUs. In these management tables, when a system has two CPUs, a table 7407 when two CPUs are operating and a table 7408 when only one CPU is operating are arranged on all the CPUs. An ID is assigned to the semaphore used in the system. For example, if the semaphore ID is less than 0x10000000, the semaphore is managed by CPU-A, and if the semaphore ID is greater than 0x10000000, it is managed by CPU-B. Set to be a semaphore. When two CPUs are operating, each semaphore ID has a value like 7407 table, and when only one CPU is operating, each semaphore ID has a value like 7408 table. Switch tables through routines that detect how some CPUs are doing. A routine for determining on which CPU the semaphore is managed checks a table corresponding to the operation of the CPU and obtains a semaphore ID. Based on the value of the semaphore ID, it is determined whether it is a semaphore of its own CPU or a semaphore of another CPU.

  FIG. 21 is a flowchart of this embodiment. The same applies to semaphore release and message queue transmission, which will be described using an example in which task 1 operating on CPU-A acquires a semaphore. 7501 is a Start point. In step 7502, a semaphore P operation program for semaphore acquisition is executed. In 7503, the semaphore P program refers to the semaphore management table described above to obtain a semaphore ID. 7504 is a determination sentence indicating that the semaphore ID is managed on the own CPU. If the semaphore is managed by its own CPU (for example, semaphore 1, ID = 0x00000001), in 7505, the operation for actually acquiring semaphore 1 is performed and the process is terminated. If the semaphore ID is managed on another CPU in 7504 (semaphore 3, ID = 0x10000001), in 7507, CPU-A issues a request to CPU-B. This request may be made in any way. In 7508, CPU-B executes a semaphore P operation program, which is a program on CPU-B, for semaphore 3 after receiving a request from CPU-A. 7509 is a determination statement that the semaphore ID is managed on the own CPU. In this case, since semaphore 3 is a semaphore managed on CPU-B and ID = 0x10000001, it is determined that the semaphore is managed by its own CPU (CPU-B). Therefore, the semaphore P operation program for acquiring the semaphore 3 managed by the CPU-B itself is executed in 7510, and the process is terminated. The same process can be performed when task 2 on CPU-B acquires semaphore 3 and semaphore 1 respectively.

1 is a block configuration diagram showing an embodiment of a digital multi-function peripheral as a data processing apparatus according to the present invention. 1 is an internal configuration diagram of a digital multi-function peripheral. It is a block block diagram which shows the detail of the controller part as an electronic component concerning this invention. It is a block block diagram which shows the detail of a main controller. 3 is a diagram illustrating an example of an operation unit 150. FIG. FIG. 10 is a diagram illustrating an example of a document reading setting screen in “continuous reading mode”. It is a figure which shows the example of a reading image confirmation screen. It is a flowchart of a continuous reading copy process. It is a flowchart of a document reading process. It is a flowchart of a stored image confirmation (preview) process. It is a figure which shows the software structure inside a control apparatus. It is a figure which shows the structure of a job control part. It is a figure which shows the management structure of a document management part. FIG. 3 is a diagram of a multi CPU sharing a main storage device (memory). It is explanatory drawing regarding a semaphore. It is a figure of the system configuration | structure in a present Example. It is a figure of the system configuration | structure in a present Example. It is a figure of the system configuration | structure in a present Example. It is a figure of the system configuration | structure in a present Example. It is a figure of the system configuration | structure in a present Example. It is a figure of the system configuration | structure in a present Example. It is a figure of the system configuration | structure in a present Example.

Claims (7)

  An image forming apparatus with multiple CPUs, and the operating systems on multiple CPUs are different, or are not compatible with multiple CPUs. When OS cannot be used, OS resources are managed by ID, all resources of all OSs in a multi-CPU system are managed by one table or any different ID, and the table or ID is all CPUs A system characterized by possession of the above OS.   The system according to claim 1, wherein a program for using the resource refers to the table or ID.   A system having the program of claim 2 in an OS on all CPUs.   When the user uses the resource, the user uses the program, and the program refers to the table or the ID to determine which CPU the resource is on. A system characterized in that if it is a resource of its own CPU, it uses a program in the OS of its own CPU and uses the resource.   When the user uses the resource, the user uses the program, and the program refers to the table or the ID to determine which CPU the resource is on. A system characterized in that if it is a resource of another CPU, it negotiates with the other CPU, and the other CPU uses a program in the OS of the other CPU and instructs to use the resource.   The system according to claim 1, wherein the table has a plurality of tables in consideration of a case of a multi CPU and a case of a single CPU.   7. A system comprising: the number of operating CPUs is detected, and the plurality of tables possessed are switched.

Images