JPH0561656A - Confirmity check system between hardware and firmware - Google Patents

Abstract

PURPOSE:To prevent the occurrence of malfunction in a device or damage due to the malfunction or the like by comparing the contents of a firmware version number storing means with that of a hardware version number setting means and judging whether the device is to be started or not. CONSTITUTION:A version number comparing means 20 reads out the number of firmware versions and the number of hardware versions respectively from the firmware version number storing means 21 and the hardware setting means 22, checks the numbers of versions and outputs a coincidence signal and a discrepancy signal respectively to a start executing means 23 and a stopping means 24. The means 23 executes hardware starting operation at the time of inputting the coincidence signal, and at the time of inputting the discrepancy signal, the means 24 outputs an alarm signal and stops hardware. When a limited execution means is included instead of the means 24, a discrepancy signal is outputted and the limited execution means stores a version with a smaller version number out of two versions, outputs a start execution signal to the means 23 to start the device and executes processing based upon the stored number of versions.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a compatibility check system between hardware equipped with firmware and firmware.

[0002]

2. Description of the Related Art Conventionally, there are various devices in which a microprocessor is mounted on a control board and program control is performed by firmware, and a printer is one of them.

FIG. 7 is a block diagram showing a printer control unit of a conventional example, and FIG. 8 is a detailed ROM mounting diagram of FIG.
The control board 6 (hereinafter referred to as the board 6) has a microprocessor 1 (hereinafter referred to as the CPU 1) and a read-only memory 2 (hereinafter referred to as RO) in which programs and fixed data are stored.
M2), a random access memory 3 (hereinafter referred to as RAM3) for temporarily storing received data from the outside, and C
Input / output driver 4 driven by a command from PU1
(Hereinafter referred to as I / O driver 4) is installed,
It is connected by a bus line 5 printed and wired. or,
The I / O driver 4 is connected to an interface circuit 7 with an external device (not shown), a print head 8, a line feed motor 9, and a spacing motor 10 for moving the print head 8 in the print direction.

In the circuit thus constructed, the CPU 1 is
The program stored in the OM2 receives print data (character data) and control data (normally called a control code for a character pitch command, a line feed command, etc.) from an external device (not shown). When the print data for one line is received, the printer starts the print operation.

By the way, since the programs and fixed data stored in the ROM 2 may be changed, R
It is rare that the OM2 is directly soldered to the substrate 6. The IC socket 11 shown in FIG. 8 is used so that the ROM 2 can be easily attached. IC socket 11 is substrate 6
It is soldered to. Then, the ROM 2 is attached to the IC socket 11. Therefore, the ROM 2 can be attached to or detached from the substrate 6. Therefore, the ROM 2 mounted on the IC socket 11 can be removed and replaced with the ROM 2 whose stored contents are changed when the stored program or fixed data is changed.

A component including the ROM 2 mounted on the substrate 6 or the substrate 6 is provided with a version number. The hardware version number of the ROM 2 and the hardware version number of the substrate 6 are checked by comparing the version numbers provided for each.

[0007]

However, the conventional hardware / firmware compatibility check method compares and verifies the hardware version number provided in the ROM and the firmware version number provided on the board. At the time of assembling, the version number is mistaken or wrong and the ROM is mounted on the board, the device is started up with the wrong combination, and as a result, malfunction occurs or in the worst case, the device is damaged. There was the problem of letting it go. In addition, when there are new and old models, the ROM and the board must be produced and managed in correspondence with the new and old models, respectively, so that there is a problem that it can be complicated.

The present invention does not cause malfunction or damage even when the apparatus is started up without matching the hardware version number and the firmware version number, and complicated production management etc. when there are old and new models. The purpose is to provide a compatibility check method between hardware and firmware.

[0009]

In order to achieve the above object, according to the compatibility check method of the hardware and the firmware of the present invention, an alarm display means and a firmware version number storage means for storing the firmware version number. When,
A hardware version number setting means for setting the hardware version number, a version number comparison means for comparing the contents of the firmware version number storage means and the hardware version number setting means, and a match signal from the version number comparison means are input. Equipped with start-up executing means for executing the start-up operation of hardware and stop means for inputting a mismatch signal from the version number comparing means to output an alarm signal to the alarm display means and for stopping the hardware Is.

In order to achieve the same purpose, the "firmware version number" and the "hardware version number" are input by the disagreement signal instead of the stopping means, and the "firmware version number" is input.
Alternatively, the smaller one of the "hardware version numbers" is stored, and a startup execution signal is output to the startup execution means to execute the startup operation, and the stored "firmware version" or "hardware version number" is stored. It is provided with limited execution means for performing processing based on the "version number".

[0011]

The version comparison means of the compatibility check method between the hardware and the firmware configured as described above reads the firmware version and the hardware version from the firmware version storage means and the hardware version setting means, respectively. , The version number is checked and the coincidence signal and the non-coincidence signal are output to the start-up execution means and the stop means, respectively. The start-up executing means executes a start-up operation of hardware when the coincidence signal is input. When the disagreement signal is input, the stop means outputs an alarm signal to the alarm display means and puts the hardware in a stopped state.

Further, in the case where the limiting execution means is provided in place of the stopping means, when the version number comparing means outputs a mismatch signal to the limiting execution means, the limited execution means is "firmware version number" and "hardware version". Number ", the one with the smaller version number is stored, and a startup execution signal is output to the startup execution means to execute the startup operation of the device, and the stored" firmware version number "or" hardware version "is stored. Perform processing based on the "version number".

[0013]

Embodiments of the present invention will be described with reference to the drawings. The elements common to the drawings are designated by the same reference numerals.

First Embodiment FIG. 1 is a basic configuration block diagram of the first embodiment. The version number comparison means 20 inputs the version numbers from the firmware version number storage means 21 and the hardware version number setting means 22 and compares them, and when they match, outputs a match signal to the start-up execution means 23. The startup executing means 23 executes startup of the device based on the coincidence signal. If they do not match, the stopping means 24
The mismatch signal is output to. When the stop means 24 receives the disagreement signal, it outputs an alarm display signal to the alarm display means 25 and puts the hardware in a stopped state.

FIG. 2 is a concrete configuration diagram of the first embodiment.
The CPU 30 includes a ROM 31 as the firmware version storage means 21, an I / O driver 33, and a bus line 34.
It is connected with. The CPU 30 also connects one end of a DIP switch 35, which is a hardware version number setting means 22 and is composed of three switches, and I / O ports P _{20 to} P ₂₂ to an I / O data bus composed of lines 36 a, 36 b, and 36 c. Connected by line 36. The line 36 is connected to the other ends of the resistors 37, 38, 39 whose one end is connected to + 5V and is pulled up. The other end of the dip switch 35 is grounded. The I / O driver 33 is the alarm display means 25.
It is connected with the line 41. The dip switch 35 can generate eight combinations by turning each switch on and off. That is, eight different version numbers can be set. Parts other than the alarm display means 25 are mounted on the substrate 40.

Next, the operation will be described with reference to FIG.
FIG. 3 is a flowchart of the first embodiment. Step S
_{At 1} , the CPU 30 reads the hardware version number set in the dip switch 35. CPU3 in step S ₂
0 reads the firmware version number stored in the header portion of the ROM 31. Step S ₃ in detects whether CPU30 has the version number read match, if match proceeds to step S _4, the case of conflict proceeds to step S _5. In step S ₄ CPU30 performs the initial start-up. In step S ₅ , the CPU 30 causes the alarm display means 2
An alarm is displayed on 5, and the machine enters the stopped state. Therefore, the ROM 31 is removed from the substrate 40, and the combination having the same version number is mounted on the device.

Second Embodiment FIG. 4 is a basic block diagram of the second embodiment.
The difference from the embodiment is that a limiting execution means 50 is provided instead of the stopping means. The version number comparison means 20 includes a firmware version number storage means 21 and a hardware version number setting means 22.
Enter the version number (from now on) and compare,
If they match, a match signal is output to the start-up executing means 23. If they do not match, a mismatch signal is output to the version number selecting / writing means 51. The startup executing means 23 executes startup of the device based on the coincidence signal. Version selection writing means 5
1 is the firmware version number storage means 21 or the hardware version number setting means 22 based on the mismatch signal, the younger "version number" and the version having the "version number" are "firmware" and "hardware". Is output to the version number storage means 52. When the function selection execution means 53 inputs the function specification content to be executed specified by the execution function specification means 54, it reads the stored content from the version number storage means 52 and selects and executes the specified function.

FIG. 5 is a concrete configuration diagram of the second embodiment.
The difference from the specific configuration of the first embodiment is that a RAM 55 as a version number storage means and an operation section 56 as an execution function designation means are provided.

Next, the operation will be described with reference to FIG.
FIG. 6 is a flowchart of the second embodiment. Step S
From ₁₁ to step S ₁₄ is the same as steps S ₁ of the first embodiment up to the step S _4. If the version numbers do not match in step S ₁₃ , the process proceeds to step S ₁₅ . In step S ₁₅ CPU 30 checks whether the hardware version number input from the dip switch 35 is larger than the firmware version which is stored in the header portion of the ROM 31. If it is larger, proceed to step S ₁₆ , and if not, step S _16.
Proceed to ₁₇ . In step S ₁₆ , the CPU 30 stores the “firmware” and the “version number” in the RAM 55, and the step S ₁₆
Proceed to ₁₄ (hereinafter referred to as "firmware version"). In step S ₁₇ , the CPU 30 writes “hardware” in the RAM 55.
And stores the "version number", the process proceeds to step S ₁₄ (hereafter referred to as "hardware version number"). In step S ₁₈ CPU30
Checks whether or not a function to be executed is designated from the operation unit 56. In step S ₁₉ , the CPU 30 causes the RAM 5
Contents 5 are stored in it is checked whether the "firmware version number" or "No", go to "firmware version number" If the step S _20, the process proceeds to step S ₂₂ if "not". In step S ₂₀ CPU 30 selects a program for executing the function specified based on the "firmware version". In step S ₂₁ CPU 30 executes according to the selected a specified function program. Step S
_{In 22} , the CPU 30 selects a program that executes the designated function based on the “hardware version number”, and in step S
Proceed to ₂₁ .

As compared with the first embodiment, the second embodiment executes the function if the program for executing the designated function is stored in the ROM even if the firmware version number and the hardware version number do not match. Therefore, if there is a ROM with the highest "firmware version", it can be used for all old and new models, and it has the effect of reducing the complexity of production management.

[0021]

Since the present invention is configured as described above, it has the following effects.

The firmware version number is stored in the ROM,
The hardware version number setting means for setting the version number of the control board is provided, and the version comparison means compares the contents of both to determine whether or not to start up the device. It can prevent damage.

If there is a mismatch as a result of the version number comparison, the limited execution means stores the smaller one of the "firmware version number" and the "hardware version number" and starts up the apparatus. By performing the execution process based on the stored "firmware version" or "hardware version", the malfunction of the device and damage due to malfunction can be prevented and the ROM with the highest "firmware version" If there is, it can support all old and new models, and it can be expected that production management will be easier.

[Brief description of drawings]

FIG. 1 is a basic configuration block diagram of a first embodiment.

FIG. 2 is a specific configuration diagram of the first embodiment.

FIG. 3 is a flowchart of the first embodiment.

FIG. 4 is a basic configuration block diagram of a second embodiment.

FIG. 5 is a specific configuration diagram of the second embodiment.

FIG. 6 is a flowchart of the second embodiment.

FIG. 7 is a block diagram showing a printer control unit of a conventional example.

FIG. 8 is a detailed view of the ROM installation of FIG.

[Explanation of symbols]

 2,31 ROM 6,40 Board 25 Alarm display means 35 DIP switch

Claims (2)

[Claims] 1. A method of checking compatibility between hardware equipped with firmware and firmware, comprising: an alarm display means, a firmware version number storage means for storing the firmware version number, and a hardware version for setting the hardware version number. Number setting means, a version number comparing means for comparing the contents of the firmware version number storing means and the hardware version number setting means, and a start signal for inputting a coincidence signal from the version number comparing means to execute a hardware start-up operation. Of the hardware and the firmware, which are provided with an upgrade execution means and a stop means for inputting a mismatch signal from the version number comparison means to output an alarm signal to the alarm display means and for stopping the hardware. Conformity check method. 2. The hardware / firmware compatibility check method according to claim 1, wherein the "firmware version number" and the "hardware version number" are input by a disagreement signal instead of the stopping means, and the "firmware version number" is input. Alternatively, the smaller one of the "hardware version numbers" is stored, and a startup execution signal is output to the startup execution means to execute the startup operation, and the stored "firmware version" or "hardware version number" is stored. A compatibility check method between hardware and firmware, which is provided with limited execution means for performing processing based on "version number".