JPH0447425A - System software generating device - Google Patents

Abstract

PURPOSE:To eliminate the need of a change of a ROM chip, to effectively utilize a hardware and to reduce the cost by collecting the information related to an input/output apparatus connected to an electronic apparatus at the time of actuating a system, and generating automatically a task for controlling the input/output apparatus in accordance with its information. CONSTITUTION:At the time of actuating the system, information related to input/output apparatuses DSj, KBK, and PRl connected to an electronic apparatus to which the device concerned is applied is collected by an information collecting means 10. A task generating means 11 generates automatically a task required for controlling the input/output apparatuses in accordance with this collected information. Accordingly, a change of a program size related to the input/output apparatus control is not generated without being accompanied with a logic change of a software (program) related to the control of the input/output apparatuses loaded in advance. Accordingly, the input/output device can be sued easily and normally without changing program logic and data.

Description

[Detailed Description of the Invention] [Industrial Field of Application] The present invention relates to a system software generation device, and in particular, to a system software generation device that can handle changes in connected input/output devices without changing the logic of installed software (program). The present invention relates to a system software generation device that generates system software.

[Prior Art] Conventionally, there are electronic devices that employ software systems to control the driving of connected hardware.

This electronic device generally has a modular configuration.

This modular configuration makes it possible to create programs and devices independently, minimizing the need to rewrite programs even if the device is changed or expanded. It is composed of a number of modules in which commands and data are systematically assembled so that they can be applied to programs.

In an electronic device that employs a modular configuration, conceptually describing the software system structure, the software system consists of system (basic) software built around the hardware as the core, and then an upper layer of the system software. A hierarchical structure is adopted in which application software is constructed.

The system software consists of a collection of basic software mainly consisting of a so-called O8 (operating system), and the application software consists of a collection of application programs created by a user. Therefore, the operation of the hardware functions desired by the user is realized by the processing of the application software that is controlled by the system software. In other words, the performance and reliability of application software created by users are highly dependent on the hardware and system software.

Furthermore, system software is generated from multiple modules that are organized collections of instructions and data. Among these multiple modules, there are some that are required, some that are optional, and some that are optional. Conventionally, when generating a system to generate system software applied to an electronic device, multiple modules are selected from a group of modules provided in advance to match the processing capacity of the main storage device, input/output device, etc. connected to the electronic device. The modules were arbitrarily selected to generate system software that was optimal, that is, matched to the processing format and hardware capabilities of the electronic device.

[Problem to be solved by the invention] However, in the system generation method described above,
The system software configuration is determined according to predetermined connection hardware configuration information, and necessary modules are selected accordingly.

Therefore, in electronic equipment where the configuration of connected hardware is changed or frequently changed, it has been impossible to uniquely determine the system software configuration to be adopted.

In other words, according to the system generation method described above, each time there is a change in the configuration of the hardware to be controlled, the modules that make up the system software are replaced, and with this replacement, the system generation process is performed again. It was being executed. However, this module replacement requires only the ROM (Read
OnlyMeory) replacement, that is, changing the program (logic, data, etc.). Therefore, every time there is a change in the hardware configuration, it is necessary to replace the ROM installed in the electronic device, and the ROM
There was a problem in that the replacement and associated system testing work required a great deal of cost and time.

Therefore, an object of the present invention is to create system software that can accommodate changes in connected input/output devices without changing the logic of installed system software in electronic equipment that employs a modular configuration. The purpose is to provide a generating device.

[Means for Solving the Problems] A system software generation device according to the present invention provides system software that individually generates tasks for controlling each input/output device in an electronic device including a plurality of input/output devices. The generation device includes, in detail, information collection means for collecting information regarding input/output devices connected to the electronic device at the time of system startup; and task generation means for generating a task to control.

According to another aspect, the system software generation device according to the present invention has the above-described configuration, and further detects the model of an input/output device used in processing an application program registered in the electronic device. a model detecting means for detecting a model, a discriminating means for discriminating that the model detected by the model detecting means is included in the information collected by the information collecting means, and a process according to a discrimination result of the discriminating means. and means for executing the same.

[Operation] Since the system software generation device according to the present invention is configured as described above, when the system is started, the information collection means collects information regarding input/output devices connected to the electronic equipment to which the device is applied, The task generation means automatically generates tasks necessary to control the input/output device according to the collected information. Therefore, changes in the input/output device configuration can be handled without changing the logic of software (programs) for controlling the input/output devices installed in advance, so that the program size for controlling the input/output devices does not change at this time.

Further, using a determining means, determining that the model detected by the model detecting means is included in the information regarding the input/output device collected by the information collecting means,
Since processing is executed according to the determination result, if it is determined that the detected model is not included in the collected information, the model that is not installed in the electronic device is specified as the data input/output cutting edge. A warning can be given to users who have registered application program processing.

[Embodiment] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a schematic diagram showing the functional configuration of an electronic device to which a system software generation device according to an embodiment of the present invention is applied.

The illustrated electronic equipment mainly includes a control unit 10 that controls various input/output devices connected to the lower level, and a plurality of units that perform data input/output operations with the outside of the electronic equipment while inputting and outputting data with the control unit 10. Display device DSj (hereinafter, j=1.2.3, . . . , h
), multiple input devices KBk (hereinafter k=1.2.3
,...,m) and multiple printers PRt (hereinafter referred to as
t=1.2.3,...,n). The control unit 10 includes a main CPU (abbreviation for central processing unit) 11 that controls and monitors the operation of the electronic device itself.
, a memory ROMI2 and a RAM (Random Access Memo) for storing various data including programs required for processing operations of the electronic device.
ry (abbreviation) 13, input/output processor and sub CPU1
A serial I/F (abbreviation for interface) controller 14 comprising a serial I/F (abbreviation for interface) 41, a connector 151 (hereinafter referred to as , i=1.2.3, ..., g).

Further, each of the display device DSj, input device KBk, and printer PRt is equipped with a CPU, and all of these devices are connected to the upper control unit 10 by a serial line.

In addition, each of these input/output devices stores its own type (model) in advance in the internal memory of its CPU, and responds to its own type (model) from the host serial I/F controller 14. It has a function of reading the stored own type (model) from the internal memory and responding.

Further, the processing of the electronic device can be broadly divided into processing related to arithmetic control and processing related to input/output control. The main CPU II of the control unit 10 mainly performs calculation control. One input/output control is separated and independent from this arithmetic control, and the function for this input/output control is concentrated in the sub CPU 141 of the serial I/F controller 14. Therefore, the main CPU
Since main CPU 1 is freed from processing for input/output control, the load on main CPU 1 is reduced, making it possible to speed up arithmetic processing.

Further, the model of each input/output device shown in the figure is not specified, and it is also possible to connect two or more of the same model at the same time.

FIG. 2 is a schematic diagram showing the configuration of tasks generated for controlling the input/output device of the electronic device shown in FIG. 1 and the mutual relationships among the tasks.

As shown in the figure, a plurality of tasks generated on the control unit 10 side are executed by the serial I/F controller 14.
A display device DS j connected to the input/output device side via
This task is to cause input device KBk and printer PRE to perform input/output operations.

Note that hereinafter, a task is a unit of work processed by the main CPU II, and is executed in a predetermined storage area of the ROMI 2 in FIG. 1 under the control of the main CPU II.

As shown in the figure, when the main CPU 1 on the control unit 10 side is in operation, the required application task group TO1 input device control task group Tl
k, display device control task group T2j1, printer control task group T3t, and serial I/F control task T4
has been generated and loaded onto a predetermined storage area of the memory ROM 12. Each of these tasks is
When PU1l is allocated, it is in a state where it can immediately transition to an executable state, that is, it is in an activated state.

Furthermore, there is a real-time monitor RM as a program that comprehensively manages each of these tasks, and this is provided as a standard function of the operating system installed in the electronic device. Therefore, requests to use (occupy) each input/output device generated by tasks generated on the control unit 10 side are processed by the real-time monitor RM.
Serial 1. /F will be passed to the sub CPU 141 of the controller 14 and processed.

In order to simplify the explanation, a detailed explanation of the application task group TO will be omitted, and here the input device control task group Tlk and the display device control task group T2 will be omitted.
A detailed explanation will be given regarding j and printer control task group T3L.

First, the task management function included in the real-time monitor RM will be briefly explained.

Real-time monitor RM manages tasks.

For this purpose, task management such as timer monitoring, memory monitoring, and overlay monitoring is performed while referring to data stored in a TCB (task control block) area provided corresponding to each task. A predetermined storage area of the ROM 12 is allocated to this TCB, and it stores information such as the activation state of each task (execution state, ready state, waiting state, etc.), the priority order for each task to occupy the main CPU 11, register contents, etc. Information is stored. Therefore, main C
Even if a new task is generated in the process of arithmetic processing of PUI 1, if a TCB area for storing information regarding this generated task is provided in advance and information regarding the generated task is not stored there, The newly created task is never moved to the activated state. Therefore, this task is never executed.

As described above, the real-time monitor RM collectively manages all tasks generated in the electronic device.

Here, the generation of the task mentioned above will be explained in detail.

Task creation does not mean creating a program, but rather registering the above-mentioned TCB in the management area of the real-time monitor RM. Activation of a task performed after task generation means registering the generated task in any of the above-described task execution states, ready states, and waiting states.

By the way, the input/output device control task groups TlkST2j and Ta2 shown in FIG. 2 are tasks that utilize reentrant programs, respectively.

This reentrant program is a program in which an unchanging part (mainly procedures) and a variable part (mainly data and work area) are separated into one program. Therefore, by having a large number of variable parts, it is possible to easily adopt a program configuration that can simultaneously accept processing requests for a plurality of programs using a single endrunt program.

Note that the work area of the variable portion is a storage area for temporarily storing intermediate data that is an intermediate calculation result during execution of the reentrant program.

In addition, due to its purpose of use, reentrant programs are read-only (Re-entrant programs) so that data will not be accidentally written by another program during execution and the procedure contents will not be changed.
ad 0nly) program in a management area such as the real-time monitor RM. therefore,
Once the reentrant program is loaded into a main storage area such as the ROM 12, the reentrant program can be freely loaded and used from any task at any time. In other words, for example, in the input/output device control task group TlkST2j and Ta2 shown in FIG.
1 is assigned and this task is running using a reentrant program. After that, based on interrupt management processing such as real-time monitor RM,
CP to another task before the execution of this task is finished.
If U1l is assigned, the real-time monitor RM hands over control of CPUI 1 to this other task, puts this other task into the running state, and puts the previously running task into the waiting or ready state. and manage this other task so that it can take advantage of the reentrant program. After that, real-time monitor R
When the execution of this other task is finished and CPU 1 becomes free, M again moves the previously executed task from the waiting state or ready state to the running state according to the priority order, and returns the task to the point where it was interrupted last time. Resume execution from. In other words, the real-time monitor RM stores the intermediate data of the task whose execution was interrupted in the aforementioned work area (work area, stack area, etc.) so that the execution of the task whose execution was interrupted in this way can be resumed from the point where it was interrupted. By saving it to , it is possible to resume the next execution.

Note that this work area stores address values, stack pointer values, etc. for restarting execution.

As described above, when using a reentrant program, it is possible to execute multiple tasks even if the main storage area of the ROM 12 is relatively small, and there is no need to spend time reloading the program (allocating it to the main storage area). It has the following characteristics.

Therefore, the task group Tlk is for controlling input/output devices.

If this endrunt program is adopted for the program routine used by T2j and Ta2, it becomes possible to use one endrunt program between multiple tasks, and furthermore, it is possible to repeat one endrunt program within one task. It is also possible to use At this time, by simply preparing a work area for saving intermediate data for resuming execution for each task in advance as described above, the program can be run as if multiple tasks were running simultaneously in the main memory area, even though the program is a single program. It can be treated as if it were in the running state. Therefore, by executing a plurality of tasks using the same program, the storage area for storing programs can be reduced.

FIG. 3 is a schematic process flow diagram for generating system software for controlling input/output devices by the system software generation device applied to the electronic device shown in FIG. 1 above.

As shown, this processing flow diagram is divided into processing on the main CPU I side of the control unit 10 and on the sub CPU 141 side of the serial I/F controller 14, and each processing flow is stored in advance as a program in the memory ROM 12. It is executed under the control of the main CPU II or the sub CPU 141.

Figures 4 (a, ) and (b) show an example of the connected device table and processing type table referenced by the main CPU during the execution of the process for generating input/output device control system software shown in Figure 3 above. FIG.

FIG. 4(a) is a schematic diagram of the connected device table DTH in which the types of all the input/output devices shown in FIG. 1 are written.

Further, FIG. 4(b) shows the processing type ST of the user program indicating the type of user-created application program (totalization, settlement, etc.) executed in the control unit 10 shown in FIG. FIG. 3 is a schematic configuration diagram of a processing type table ITB written in such a manner that the used device UD indicating the model of the input/output device used during execution corresponds to the processing type table ITB.

Here, each illustrated table will be briefly explained.

As shown in the figure, the connected device table DTB in FIG. 4(a) has a 5-word structure of a first word W1 to a fifth word W5, each having a fixed word length of 8 bits, consisting of bits bO to b7, for example. shall be. The breakdown is that the 17th word W1 and the second word W2 are areas where the connection information of the input device KBk shown in FIG. This is an area where information is written, and the fifth word W
5 is an area in which connection information of the printer PRL is written. This connection information is information that specifies the type of input/output device connected to the control unit 10 based on the values of bits bo to b7 of the first to fifth words W1 to W5.

Specifically, for example, bit b5 of the third word W3 has a value “
If “1” is written, bit b5 of third word W3
It can be seen that the display device of the model specified by is connected. Conversely, if the value “0” is written, the third
It can be seen that the display device of the model specified by bit b5 of word W3 is not connected.

Note that a detailed explanation of the process related to creation and access of this connected device table DTB will be given later.

The processing type table ITB shown in FIG. 4(b) has a structure of an arbitrary number of words having an arbitrary fixed word length, as shown. As for the details, for example, the lower half word WL of each word is an area in which the processing type ST of the user-created program described above is written and stored. Furthermore, as described above, the lower half word WU of each word is written with the device used UD indicating the model of the input/output device used when executing the user program of processing type ST stored in the lower half word WL of the same word. This is the area where the data is stored. Therefore, processing type table I
The number of words constituting the TB corresponds to at least the number of user programs or the number of processes configured by the user programs.

Next, with reference to FIGS. 1 to 3 and FIGS. 4(a) and (b), the processing operation of generating system software for controlling input/output devices by the system software generating device according to an embodiment of the present invention will be described. Explain in detail.

Note that the glue end runt program for controlling each input/output device is stored in advance in a predetermined storage area of ROMI2,
It is assumed that it is registered in the management information of the real-time monitor RM.

First, when power (not shown) is turned on to the control unit 10 of FIG. 1, the main CPU
1 starts the processing from step 510 (abbreviated as SIO in the figure) in FIG.

First, in step SIO, the main CPU 11 outputs an instruction signal to the sub CPU 141 of the serial I/F controller 14 to check the connection status of the input/output devices currently connected to the control unit 10. In response to receiving this instruction signal, the sub CPU 141 performs steps S20 to S50.
Execute the process to check the connection status.

First, in the process of step S20, the sub CPU 141 transmits a command to adjust its own model to the CPU of each input/output device connected via each serial I/F connector 15i.

In response, the CPU of each input/output device
Since the sub CPU 41 reads its own model stored in the internal memory in advance and sends it to the sub CPU 41 via the /F connector 15i, the sub CPU 41 receives data regarding the model of each device from each input/output control device in the process of step S30. be able to. Thereafter, the process moves to step S40, and the connected device table DTB shown in FIG. 4(a) is created in a predetermined storage area of the memory RAM 13 based on this received data.

Now, when creating this connected device table DTB, the value "1" is written to the corresponding bit of the word corresponding to the model of the connected device, but the value "1" is written to all bits that do not correspond. 0'' is written to create the connected device table DTB. Thereafter, in processing step S50, this connected device table D
The TB is transferred from the memory RAM 13 to the memory ROMI 2, set in a state where the main CPU 1 can access it, and the process is returned to the main CPU II side again. Main CP
The UII executes the processing from step S60 in response to the processing being returned from the sub CPU 141.

First, in the process of step S60, the CPU II uses the connected device table DT stored in the memory ROMI2.
B is sequentially searched from the beginning to the end, and the next step S7
0 and step S80, an input device control task is generated and activated in response to the search result of step S60 indicating that the input device KBk is connected. At this time, since the connected device table DTB is sequentially searched in processing step S60, step S
The loop processing from step S60 to step S80 is repeatedly executed, and when the determination processing at step S70 is established, the generation and activation of the input device control task group T1 in FIG. 2 is completed.

When the determination process in step S70 is established, the process proceeds to step S90 and step 5100, in which the display device D
In response to the connection of Sj, a display device control task is generated and activated. At this time, since the connected device table DTB is sequentially searched in processing step 360, the loop processing from step S60 to step 5100 is continued until the determination processing of whether or not the search for display device connection information is completed in step S90 is established. This is repeatedly executed, and when the determination process in step S90 is satisfied, the generation and activation of the display device control task group T2j shown in FIG. 2 is completed.

When the determination process in step S90 is established, the process proceeds to steps 5110 and 5120 in which a printer control task is generated and activated depending on whether the printer PRE is connected. At this time, since the connected device table DTB is sequentially searched in processing step S60, the loop processing from step S60 to step 5120 is repeated until the determination process of whether or not the printer connection information search is completed in step 5110 is satisfied. is executed,
When the determination process in step 110 is established, the generation and activation of the printer control task group T3L shown in FIG. 2 is completed. and,
If the determination process in step 5110 is satisfied, the process branches to steps after step 5130, which will be described later.

Now, here, the above-mentioned processing step S80, step 5
The generation and activation of tasks in steps 100 and 5120 will be explained below.

As mentioned above, the generation of a task in this system software generation device means that information about the generated task is registered in the TCB area of ROMI2 managed by the real-time monitor RM, and also that when the task is executed, the working memory is An area is taken up on the memory RAM 13. At this time, multiple I/O controller tasks are
As mentioned above, it is stored in advance on the memory ROMI 2,
In addition, since the task is generated using a single glue-end run program registered in the management information of the real-time monitor RM, it can be seen that the program logic and data are not changed (added or deleted) in this task generation.

Further, the generated task is activated by being registered in the task execution cycle (ready state, execution state, wait state, etc.) as described above.

In other words, each task is managed by the real-time monitor RM with reference to the TCB area, and each task is sent to the main CPU according to its priority and while receiving various interrupt processing.
U11 is allocated and becomes ready to be executed.

Therefore, by knowing the input/output device connection status and updating TCH data and allocating a work area during execution accordingly, a plurality of tasks using the same reendrant program are generated and activated.

As described above, when the generation and activation of control tasks for all input/output devices connected according to the connected device table DTB are completed, the next step is step 5130.
Then, the processing type table ITB is created.

The processing type table ITB may be created by the user manually inputting keys from a keyboard, and then the main CPU II creates the processing type table ITB on the memory ROM 12 based on the key input data. In addition, the CPU 11 uses the processing type table IT
By executing the program prepared in advance for B creation, the processing type S is determined from information regarding the user's application program registered in advance on the memory RAMI2.
Reads data related to T and indicates the device used in the application program.Reads data related to the device used UD, and stores this data ST and UD in the processing type table ITB on the memory ROM12.
It may also be written and stored.

When the processing type table ITB is created in the memory ROM 12 as described above, the processing proceeds to the next step 5140.
to move to.

In step 5140, the connection information of the input/output device in the connected device table DTB already registered on the memory ROMI2 is compared with the data regarding the used device UD in the processing type table ITB, and the model corresponding to the used device UD is compared. Confirm that all input/output devices are registered in the connected device table DTB.

In response to this confirmation result, in the determination process of step 5150, if it is determined that all the devices of the model registered in the used device UD are registered in the connected device table DτB (corresponding bit = "1"), Shifts to the start of normal user program processing, but otherwise issues a warning process.

This warning process outputs a warning message to the effect that "the input/output device required by the user program is not connected to the electronic device" via some output device to alert the user. do.

As described above, in electronic equipment to which the system software generation device is applied, tasks for controlling input/output devices connected to the electronic equipment can be automatically generated every time the system is started up. Therefore, even if there is any change in the connection status of the input/output devices of the electronic device, these input/output devices can be easily used normally without changing the program logic or data once the system is started. becomes possible.

[Effects of the Invention] In an electronic device that employs the system software generation device according to the present invention, information regarding input/output devices connected to the electronic device is collected when the system is started, and input/output devices are configured according to the collected information. Control tasks can be automatically generated. In addition, in the collected information,
If the type of input/output device used in the processing of an application program registered in advance in the electronic device is not registered, a warning can be given to the user to prompt him or her to take action. Furthermore, since the task generation described above is performed using a reentrant program, even if the configuration of connected input/output devices changes and the generated task changes, the logic and data of the program will not change. Therefore, since the program size does not increase, the storage area can be used effectively. Along with this, if programs and data related to system software are collectively stored in a ROM chip, program changes due to changes in the configuration of connected input/output devices, that is, RO
This eliminates the need to replace the M chip, resulting in effective use of hardware and cost reduction.

[Brief explanation of the drawing]

FIG. 1 is a schematic diagram showing the functional configuration of an electronic device to which a system software generation device according to an embodiment of the present invention is applied. FIG. 2 is a schematic diagram showing the configuration of tasks generated for controlling the input/output device of the electronic device shown in FIG. 1 and the mutual relationships among the tasks. FIG. 3 is a schematic process flow diagram for generating system software for controlling input/output devices by the system software generation device applied to the electronic device of FIG. Figures 4(a) and (b)
) is a schematic diagram showing an example of a connected device table and a processing type table that are referred to by the main CPU during execution of processing for generating input/output device control system software in FIG. 3; In the figure, 10 is a control unit, 11 is a main CPU, 14 is a serial I/F controller, 141 is a sub CPU, DSj is a display device, KBk is an input device, and P
Rt is the printer, TO is the application task group, T
lk is an input device control task group, T2j is a display device control task group, T3L is a printer control task group, T4 is a serial E/F control task, RM is a real-time monitor, DT
B is a connected device table, ITB is a processing type table, ST is a processing type, and UD is a used device. In each figure, the same reference numerals indicate the same or corresponding parts. Diagram

Claims (2)

[Claims] (1) A system software generation device that individually generates tasks for controlling each input/output device in an electronic device including a plurality of input/output devices; an information collecting means for collecting information regarding input/output devices; and based on the information collected by the information collecting means,
A system software generation device, comprising: task generation means for generating a task for controlling the input/output device. (2) a model detection means for detecting a model of an input/output device used in the processing of an application program registered in the electronic device; and a model detected by the model detection means is collected by the information collection means. 2. The system software generation device according to claim 1, further comprising: a determining unit that determines whether the information is included in the information; and a unit that executes processing according to a determination result of the determining unit.