JPH076114A - Computer system - Google Patents

Abstract

PURPOSE:To simplify initializing work at the time of connecting an extended card in a computer system capable of connecting the extended card. CONSTITUTION:A driver program memory 17 capable of storing a driver program for driving its own extended card 15 is added to the extended card 15 itself and a driver program reading means for reading out the driver program of the card 15 through a system bus 11 and a writing means for writing each read driver program in an OS program are added to a CPU 12. Identifier for specifying itself is stored in each extended card 15 and the main CPU 12 reads out the identifier of each extended card and recognizes the sort of the extended card connected to the system bus 11 at present.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a computer system in which a plurality of expansion cards can be connected to a system bus for expanding functions.

[0002]

2. Description of the Related Art In a small computer system, a main CP that executes various kinds of information processing on a system bus.
A U (central processing unit), an HDD (hard disk device) and an FDD (floppy disk device) that store various kinds of information are connected. Generally, these electronic components
In order to deal with inspection maintenance and flexible function development, it is formed in a board shape (card shape) and is detachably attached to the system bus.

In such a computer system, in order to add an additional function, a plurality of expansion cards can be connected to the system bus later. This expansion card can execute various types of information processing based on a business program (firmware) stored inside like the main CPU.

A computer system to which an expansion card having such a function can be connected is constructed, for example, as shown in FIG. Main CPU 2 and H on system bus 1
DD3 and FDD4 are connected. Further, a plurality of expansion cards 5 are connected to the system bus 1.

In such a computer system, in general, in order for the main CPU 2 to operate the HDD 3, FDD 4 and expansion card 5, each electronic component 3-5 is used.
It is necessary to incorporate each driver program for each into the OS program in advance.

Therefore, in order to newly install the expansion card 5 in this computer system so that the main CPU 2 activates the expansion card 5, the expansion card 5 is required.
It is necessary to newly incorporate the above driver program into the OS program.

Conventionally, as a procedure for setting the driver program in the OS program, for example, an FD (floppy disk) in which the driver program of the expansion card 5 is written is attached to the FDD 4, and the FDD 4 to the HDD 3
The program is written in the OS program stored inside. Therefore, the main CPU 2 can operate the newly connected expansion card 5 by using the new OS program rebuilt in the HDD 3.

[0008]

However, as shown in FIG. 3, each time the expansion card 5 is newly connected to the system bus 1, the driver program of the expansion card 5 is set in the FDD 4 and the FDD 4 Even in a computer system in which the OS program of the HDD 3 is written, there are still the following problems to be solved.

That is, it is necessary for the operator to perform all the above-mentioned operations artificially. Therefore, the initial setting work when installing a new expansion card becomes complicated,
Work efficiency decreases. In particular, when the expansion card 5 needs to be replaced frequently, there is a concern that the processing efficiency of the entire system will decrease.

When a plurality of expansion cards are incorporated, even if the expansion cards perform the same type of processing work, the combination conditions and consistency between the firmware and the OS program are different. Since it is necessary, it is necessary to prepare a driver program suitable for each.

Further, even if the driver programs are of the same type, the specifications may be changed for improvement and the version may be changed. Therefore, unless the above-mentioned FD mounting work for the FDD 4 and the write operation for the HDD 3 are performed with the utmost care, the expansion card 5 may not operate at all, or only some functions may be satisfied. is there.

For example, if an old version of the driver program is used, it will operate normally, so the operator will judge that the initial setting work has been correctly executed, but the new function will not be executed, or the old version will not work. There is a concern that the problem that has occurred but the problem that was solved in the new version may occur again. Since these problems do not occur immediately when the expansion card is installed, there is a concern that they may be overlooked.

Further, since the expansion card 5 and the FD storing the driver program for driving the expansion card 5 are separately supplied, there is a concern that the operator may set the combination in the computer system in an incorrect combination.

The present invention has been made in view of the above circumstances, and by incorporating a driver program for driving the expansion card into the expansion card itself, it is possible to automatically mount the expansion card on the system bus. The optimum driver program is written in the OS program,
It is an object of the present invention to provide a computer system capable of preventing erroneous settings when an expansion card is installed and greatly improving the efficiency of initial setting work.

[0015]

SUMMARY OF THE INVENTION In order to solve the above problems, the present invention provides a system bus to which a main CPU is connected, in which a plurality of expansion cards are detachably mounted, and a main C
The PU is applied to a computer system that drives each expansion card using an OS program in which a driver program for driving each expansion card connected to the system bus is incorporated.

According to the invention of claim 1, a driver program memory for storing a driver program for driving its own expansion card is added to each expansion card, and each main CPU is provided with a driver program memory at the time of startup. A driver program reading unit for reading the driver program of the expansion card via the system bus and a unit for writing each read driver program in the OS program are added.

According to the second aspect of the present invention, an identifier memory for storing an identifier for identifying itself is added to each expansion card, and the expansion CPU connected to the system bus at startup is added to the main CPU. Read each identifier,
A means for recognizing the card type of each expansion card currently connected to the system bus is added.

According to the third aspect of the invention, the driver program memory is formed on the shared memory of the expansion card and the main CPU. Further, in the invention of claim 4, for each expansion card, a driver program memory for storing a driver program for driving its own expansion card and a driver program operating condition for operating the driver program are stored. A driver program operating condition memory is added. Further, to the main CPU, a driver program operating condition reading means for reading the driver program operating condition of each expansion card via the system bus at the time of startup, and a driver program for reading the driver program of each expansion card via the system bus at startup. A reading means and a means for writing a driver program that matches all the read driver program operating conditions among the read driver programs into the OS program are added.

According to the invention of claim 5, a hardware version is adopted as a driver program operating condition,
In the invention of claim 6, the firmware version is adopted as the driver program operating condition.

According to the invention of claim 7, a driver program memory for storing a driver program for driving its own expansion card and a driver program stored in this driver program memory are provided for each expansion card. OS of OS program to operate
An OS program version memory for storing the program version is added. Then, for the main CPU, an OS program version reading means for reading the OS program version of each expansion card via the system bus at startup, and a driver program reading means for reading the driver program of each expansion card at startup on the system bus. Of the read driver programs, a means for writing a driver program in which the OS program common to all the read OS program versions can operate is added.

According to the eighth aspect of the present invention, when there is no driver program capable of operating the OS program common to all the read OS program versions with respect to the main CPU of the seventh aspect, the external storage A means for writing a driver program for operating the minimum function of each expansion card stored in the device into the OS program is added.

[0022]

In the computer system configured as described above, the expansion card itself stores a driver program for driving the expansion card. Then, when this expansion card is connected to the system bus and the computer system is started, the main CPU, before starting the actual information processing business according to the application program,
The driver program connected to the system bus is read and written in its own OS program. Then, in the actual process of executing the information processing business, it becomes possible to drive the required expansion card correctly according to the OS program reconstructed using this driver program.

Further, in the invention of claim 2, in addition to the driver program, each expansion card stores an identifier for specifying the expansion card. Therefore, the main CPU can specify the card type of the installed expansion card by reading the identifier of each expansion card when the power is turned on.

Further, in the invention of claim 3, the driver program is formed on a shared memory between the expansion card and the main CPU. That is, depending on the type of expansion card, different processing may be performed using the same data as the main CPU. In such a case, it is possible to execute the processing task more efficiently by having the data to be processed individually in the shared memory.

Therefore, in a computer system using such a shared memory, if the above-mentioned driver program is written in this shared memory, the main CPU
Can read the driver program more easily.

Further, in claim 4, in addition to the driver program, each expansion card stores a driver program operating condition for operating the driver program.

In this case, each driver program is read by the main CPU, and each driver program operating condition is also read at the same time. Then, among the read driver programs, the driver programs that match all the driver program operating conditions are written in the OS program.

That is, even if a large number of expansion cards having similar functions are connected to the system bus, if the expansion deadlines of the expansion cards are different, the expansion cards may be installed in the system for improvement. When connecting to the bus, there are cases where the hardware type such as matching of the types of signals transmitted and received between the connecting terminals and matching of the designated address area are changed. Therefore, in such a case, it is necessary to match the operating conditions in the hardware version. Similarly, it is necessary to match the operating conditions in the firmware version.

Therefore, each expansion card stores a driver program corresponding to the above hardware version and firmware version. Therefore, when the main CPU drives each expansion card according to the OS program, it is necessary to set a driver program capable of driving all expansion cards in the OS program.

Therefore, the driver program is written in the OS program according to the procedure described above. In general, since the new version function often includes the old version function, it is desirable to write the driver program corresponding to the latest version in the OS program when the difference between the versions is unknown.

In the inventions of claims 5 and 6,
By specifying the driver program operating condition as the hardware version and the firmware version, the effect becomes more remarkable.

Further, in the invention of claim 7, each expansion card stores the version of the OS program on the main CPU side in addition to the driver program. That is, like the driver program of each expansion card, the OS program on the main CPU side is changed or improved according to the type of expansion card connected. Therefore, each expansion card stores an OS program version that specifies the OS program that optimally drives its own expansion card.

When the main CPU reads the OS program version of each expansion card, the driver program capable of operating the OS program common to all the read OS program versions is written in the OS program. That is, even in this case, an operable driver program is always selected.

Finally, according to the invention of claim 8, even when the method of claim 7 is used, when there is no driver program for normal operation of all expansion cards, an external storage device connected to this main CPU. The driver program for operating the minimum functions of the respective expansion cards stored in the OS is written in the OS program. Therefore, each connected expansion card can be driven without fail.

[0035]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a schematic configuration of a computer system of the embodiment. Main CP on system bus 11
A U12, an HDD 13 that stores an OS program and the like, and an external storage device 14 including an FDD or the like are connected. Further, a plurality of expansion cards 15 can be connected to the system bus 11 as needed.

In each expansion card 15, an expansion card function 16 of the expansion card itself including, for example, an application program and a driver for externally driving the expansion card function 16 of the expansion card. A driver program memory 17 for storing programs, a driver program operating condition memory 19 for storing driver program operating conditions for efficiently operating the expansion card function 16, and expansion card information for storing attributes of the expansion card 15. A memory 19 and the like are stored.

In the expansion card information memory 19, a card unique card identifier 19a given to the expansion card 15, a card version 19b updated every time the setting contents of the expansion card 15 are changed, and the driver The driver program stored in the program memory 17 is set to the driver program version 19c that is updated each time the driver program is changed or improved.

In the driver program operating condition memory 18, the hardware version 18 is updated every time the above-mentioned hardware changes or improvements are implemented.
a, the current expansion card 15 is compatible (matched)
An OS program version 18b for specifying the OS program on the main CPU 12 side and a firmware version 18c for the expansion card function are set.

The other expansion cards 15 connected to the system bus 11 have substantially the same structure. Then, after the operator connects (mounts) the necessary expansion card 15 having such a configuration to the system bus 11 and then turns on the power of the entire computer system, the main CPU 12 causes the normal information processing based on the application program. The program is configured to execute the initial processing shown in the flowchart of FIG. 2 before starting the work.

When the flow chart starts, each expansion card 15
The card identifier 19a of the expansion card information memory 19 is read. Then, it is checked whether or not the card identifier is already registered in the internal table (P
1).

If a new card identifier exists, the expansion card 15 is newly installed, and this card identifier is registered in the table. Next, the card version 19b.b stored in the expansion card information memory 19 and the driver program operating condition memory 18 is stored. Driver program version 19c. Hardware version 18a.
The OS program version 18b and the firmware version 18c are read (P2).

Next, each driver program stored in each driver program memory 17 is read. Then, the above-mentioned versions 18a to 1 that have already been read
A driver program that can be executed (supported) for each version is selected for each of 8c, 19b, and 19c.
Further, one driver program corresponding to all version types is determined from the driver programs selected one by one for each version (P3).

When one driver program is normally determined (P4), the corresponding driver program is set in the HDD 13
Write to the OS program stored in (P5). In P4, if a driver program commonly corresponding to all the versions is not found,
The minimum operable driver program stored in the external storage unit 14 is read (P6) and written in the OS program (P5).

In the computer system configured as described above, when a new function is added to the computer system, each expansion card 15 having the corresponding function is simply attached to the system bus 11.
Among the driver programs stored in 5, the driver programs capable of operating at least all expansion cards 15 are selected and automatically set as the OS program.

Therefore, the operator carries out any operation for incorporating the driver program into the OS program without considering the various versions of the respective expansion cards 15 to be incorporated into this computer system. do not have to. Therefore, the initial setting work efficiency when the expansion card is mounted can be significantly improved.

Furthermore, since the optimum driver program is automatically written in the OS program, it is possible to prevent the human error of writing an incorrect driver program in the OS program as in the conventional system. . Therefore, the reliability of the entire computer system can be improved.

Further, when the optimum driver program for all expansion cards 15 cannot be retrieved from each expansion card 15, the minimum functions of each expansion card 15 stored in the external storage unit 14 are driven. A possible driver program is written in the OS program. Therefore, it is possible to prevent the situation where the entire computer system does not operate.

Since the driver program for driving each expansion card is incorporated in each expansion card, the storage of this expansion card is simplified. The present invention is not limited to the above-mentioned embodiments. In the embodiment system, the expansion card memory 19 of each expansion card 15
In addition, the driver program operating condition memory 18 is searched for a compatible driver program over all versions, but if necessary, a version having a lesser influence may be excluded from the matching conditions.

When only one expansion card 15 is connected, the driver program read from this expansion card 15 may be unconditionally written in the OS program.

Although the dry-per program memory 17 for storing the dry-per program is provided as a dedicated memory in the expansion card 15, it may be provided on a shared memory formed with the main CPU 12, for example. .

[0051]

As described above, in the computer system of the present invention, the expansion card itself incorporates the driver program for driving the expansion card. Therefore, the optimum driver program is automatically written in the OS program only by mounting the expansion card having the necessary expansion function on the system bus, and it is possible to prevent erroneous setting at the time of mounting the expansion card. The setting work efficiency can be greatly improved.

[Brief description of drawings]

FIG. 1 is a block diagram showing a schematic configuration of a computer system according to an embodiment of the present invention.

FIG. 2 is a main CP of the computer system of the embodiment.
The flowchart which shows operation | movement of U.

FIG. 3 is a block diagram showing a schematic configuration of a conventional computer system.

[Explanation of symbols]

11 ... System bus, 12 ... Machine CPU. 13 ... HD
D, 14 ... External storage device, 15 ... Expansion card, 16 ... Expansion card function, 17 ... Driver program memory, 18
... driver program operating condition memory, 19 ... expansion card information memory, 19a ... card identifier.

Claims (8)

[Claims] 1. A plurality of expansion cards are removably provided on a system bus to which a main CPU is connected, and a driver program for causing the main CPU to drive each of the expansion cards connected to the system bus. In a computer system that drives each expansion card using an embedded OS program, each expansion card has a driver program memory that stores a driver program for driving its own expansion card, and the main CPU is A computer system comprising: a driver program reading unit that reads the driver program of each expansion card at the time of startup via the system bus; and a unit that writes the read driver programs into the OS program. 2. Each expansion card has an identifier memory that stores an identifier for identifying itself, and the main CPU reads each identifier of each expansion card connected to the system bus at the time of startup, 2. The computer system according to claim 1, further comprising means for recognizing a card type of each expansion card currently connected to the system bus. 3. The computer system according to claim 1, wherein the driver program memory is formed on a shared memory between the corresponding expansion card and the main CPU. 4. A system bus to which a main CPU is connected is detachably provided with a plurality of expansion cards, and a driver program for causing the main CPU to drive each expansion card connected to the system bus. In a computer system that drives each expansion card using an embedded OS program, each expansion card operates a driver program memory that stores a driver program for driving its own expansion card, and the driver program. And a driver program operating condition memory for storing operating conditions of a driver program for the main CPU, and the main CPU reads the driver program operating condition of each expansion card via the system bus at startup, , Each of the above expansions at startup Driver program reading means for reading the driver program of the card via the system bus, and means for writing, in the OS program, driver programs that match all the read driver program operating conditions among the read driver programs. A computer system characterized by having. 5. The computer system according to claim 4, wherein the driver program operating condition is a hardware version. 6. The computer system according to claim 4, wherein the operating condition of the driver program is a firmware version. 7. A plurality of expansion cards are detachably provided on a system bus to which a main CPU is connected, and a driver program for causing the main CPU to drive each of the expansion cards connected to the system bus. In a computer system for driving each expansion card by using an embedded OS program, each expansion card stores a driver program memory for storing a driver program for driving its own expansion card, and a memory stored in the driver program memory. An OS program version memory for storing an OS program version of the OS program for operating the generated driver program, and the main CPU has an OS of each expansion card at the time of startup.
The OS program version reading means for reading the program version via the system bus, the driver program reading means for reading the driver program of each expansion card at the time of startup via the system bus, and the read driver program among the read driver programs A computer system comprising: a driver program capable of operating an OS program common to all read OS program versions. 8. The main CPU is the minimum of each expansion card stored in an external storage device when there is no driver program capable of operating an OS program common to all the read OS program versions. 8. The computer system according to claim 7, further comprising means for writing a driver program for operating the function of the above into the OS program.