JPH04326423A - Version-up control system - Google Patents

Abstract

PURPOSE:To prevent the malfunction of a device and at the same time to improve the reliability of the device by detecting and displaying quickly the adaptability between the versions of the hardware and the software and therefore reducing both the time and the cost required for investigation in an inadaptable state of versions. CONSTITUTION:A hard version reading means 3 is provided to read the version of the hardware together with a soft version reading means 7 which reads an allowable range of the version of the software adaptive to the hardware stored in a memory 5, a comparator means 9 which compares the allowable range of the software version read by the means 7 with the hardware version read by the means 3, and a display control means 11 which displays the inadaptability of the hardware when the means 9 decides that the hardware version exceeds the allowable range of the software version.

Description

[Detailed description of the invention]

[Object of the invention]

0002

[Industrial Application Field] The present invention relates to an version upgrade management system that is equipped with a microprocessor and manages hardware versions and software versions. The present invention relates to a version upgrade management system that quickly detects and displays errors.

0003

2. Description of the Related Art In a system equipped with a microprocessor (hereinafter referred to as CPU), the CPU operates according to a program stored in a ROM and learns the hardware version by reading a hardware version port. Further, the CPU can know the software version by reading version data written in advance at a predetermined address in the ROM. Furthermore, C.P.
When U receives an external request, for example, an operator requests to display the hardware version and software version, U displays the software version shown in FIG. Display the version as "V2.32". Traditional version upgrades are used to add system functions.
A software version upgrade is performed when a software change is required due to a hardware version upgrade, for example, a change to a new model of LS1 or a slight change in I/0 or memory address. Compatibility of software and hardware versions was not easy to detect.

0004

[Problems to be Solved by the Invention] However, in the conventional version upgrade management system, when a work error occurs during a hardware version upgrade or software version upgrade, for example, a mismatch due to a misplaced ROM occurs. Measures to detect the nonconformity were not considered. Therefore, the difference in the ROM can be detected only after the ROM is installed and a malfunction occurs. After a problem occurs, investigate the problem and
Since a difference in the OM is detected, it takes time and money to investigate the problem, and there is also a problem that malfunction of the device may occur due to a malfunction in the operation, resulting in a decrease in the reliability of the device.

[0005] The present invention has been made to solve such conventional problems, and its purpose is to quickly detect and display the compatibility between the hardware version and the software version. Therefore, it is an object of the present invention to provide a version upgrade management system that saves time and costs required for investigating nonconformities, prevents equipment malfunctions, and improves reliability.

[Configuration of the invention]

[0007]

[Means for Solving the Problems] In order to achieve the above object, the present invention provides a hardware version reading means 3 for reading the version of the installed hardware, as shown in FIG.
a memory 5 for storing a permissible range of software versions compatible with the installed hardware; and a software version reading means for reading the permissible range of software versions stored in the memory 5 that is compatible with the installed hardware. 7, comparison means 9 for comparing the allowable range of the software version read by the software version reading means 7 and the version of the installed hardware read by the hardware version reading means 3; The present invention further comprises a display control means 11 for displaying a non-conformance of the installed hardware when the installed hardware version exceeds the allowable range of the software version.

[0008]

[Operation] With the configuration as described above, first, the version of the installed hardware is read. Next, the allowable range of the software version that is compatible with the installed hardware is read from the memory that stores the allowable range of the software version that is compatible with the installed hardware. The allowable range of the read software version is compared with the read version of the installed hardware. If the installed hardware version exceeds the allowable range of the software version by comparison, the installed hardware is determined to be compatible and the non-compliance is displayed, so the compatibility of the hardware and software versions can be checked. Can be detected quickly.

[0009]

DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing control of an embodiment of the version upgrade management system of the present invention.

[0011] The above version upgrade management system is configured to update the version of the hardware installed in the hardware version port 1, for example, the new model LS1 (not shown), from RO to
If the version of the software stored at a predetermined address of the M13 that is compatible with the hardware exceeds the allowable range, the incompatibility of the hardware is immediately displayed.

The version upgrade management system has a hard version port 1, a ROM 13, a CPU 15, and a system bus 17.

[0013] The above-mentioned hardware version 1 includes hardware implemented for upgrading the hardware,
For example, when a printed circuit board (hereinafter referred to as PC version) on which a new model LS1 (not shown) is attached is revised or modified, the CPU 15 reads the version number data and modification number data of the PC version from the pattern cut. It will be done.

The ROM 13 stores, at a predetermined address, a value indicating the allowable range of software versions that are compatible with the hardware to be upgraded.

The microprocessor (hereinafter referred to as CPU) 15 reads from the hardware version port 1 the version number data, modification number data, etc. of the PC version of the hardware installed for version upgrade. Also, CPU
15 compares the version number data etc. read from the hardware version port 1 with a value stored at a predetermined address in the ROM 15 indicating the allowable range of the version of the software compatible with the hardware. By comparison, CPU15 is
If the version number data etc. read from the hardware version port 1 exceed the allowable range of the software version in the ROM 13, a non-conformance of the installed hardware is displayed on a display section 23, etc., which will be described later.

The system bus 17 is connected to the CPU 15, the hard version port 1, etc., and transmits data.

[0017]Furthermore, the version upgrade management system
It has drivers 19a and 19b, a display section 21, a printing section 23, and various circuits 25.

The driver 19a is an amplifier circuit for shaping the signal transmitted to the display section 21 via the system bus 17, and the driver 19b shapes the signal transmitted to the printing section 23 via the system bus 17. This is an amplifier circuit for

The display section 21 is made up of, for example, a CRT and displays non-conformity of the software installed in the hardware version port 1 by the CPU 15.

[0020]Here, to explain the above display example using FIG.
ard! ! ” displays non-conformities.

[0021] The printing unit 23 is, for example, a printer or the like, and prints information such as non-compliance of the hardware installed in the hardware version port 1 detected by the CPU 15.

Various circuits 25 are necessary for the operation of the system of this embodiment.

Next, the operation of this embodiment will be explained using the flowchart of FIG.

First, after the system is started, when the PC version is installed by the operator, the CPU 15 reads a value stored at a predetermined address in the ROM 13 that indicates the allowable range of software versions compatible with the installed hardware. . Further, the CPU 15 reads version number data and modification number data of a PC version mounted with, for example, a new model LSI (not shown) from the hard version port 1 (steps 100 to 110).

[0025] The CPU 15 is a hard version port 1.
The version number data etc. read from the ROM 13 are compared with the value indicating the allowable range of the software version read from the ROM 13. Based on the comparison, the CPU 15 continues processing when the version number data etc. are within the allowable range of the software version (
Steps 120-130).

On the other hand, if the version number data etc. exceed the allowable range of the software version, the CPU 15 displays a signal via the system bus 17 indicating an error such as incorrect installation of the LSI installed in the mounted PC version. Part 21
Output to. The output signal is shaped by the driver 19a and input to the display unit 21. The display section 21 displays "Unmatch So" shown in FIG. 2 from the input signal.
ft to Hard! ! '' is displayed to inform the operator of a problem with the LSI installed on the PC version. The operator checks the PC version based on the display on the display unit 21 to detect an LSI installation error.

[0027] As a result, the suitability or non-compliance of the installed hardware can be quickly determined and displayed, thereby saving time and cost for investigating non-compliance.

Next, as another embodiment, in addition to version data, by providing model data together with hardware and software, it is possible to detect non-conformity when the software is installed by mistake with the software of another CPU-equipped device. can.

Further, in this embodiment, hardware nonconformity is displayed on the display section 21 to indicate the nonconformity to the operator. There is also a method of notifying the operator.

[0030]

[Effects of the Invention] As explained above, the present invention quickly detects and displays the compatibility between the hardware version and the software version, thereby reducing the time and cost required to investigate the case of non-compliance. save money, and
Malfunctions of the device can be prevented and reliability can be improved.

[Brief explanation of drawings]

FIG. 1 is a complaint correspondence diagram of the version upgrade management system of the present invention.

FIG. 2 is a block diagram showing control of an embodiment of the version upgrade management system of the present invention.

FIG. 3 is a diagram showing a display example of the present invention.

FIG. 4 is a flowchart showing the operation of the present invention.

FIG. 5 is a diagram showing a conventional display example.

[Explanation of symbols]

1 Version port 3 Hard version reading means 5. Memory 7 Software version reading means 9. Comparison means 11 Display control means 13 ROM 15 CPU 23 Display section 25 Printing section

Claims (1)

[Claims] 1. Hardware version reading means for reading the version of the installed hardware; a memory for storing an allowable range of software versions compatible with the installed hardware; and a hardware version reading means for reading the version of the installed hardware; a software version reading means for reading an allowable range of software versions compatible with the hardware; the allowable range of software versions read by the software version reading means; and the version of the installed hardware read by the hardware version reading means. and display control means for displaying non-conformance of the installed hardware when the version of the installed hardware exceeds the allowable range of the software version. Featured version update management system.