JPH01189735A - Microprogram diagnosing system - Google Patents

Abstract

PURPOSE:To diagnose a microprogram in an on-line operation by checking the microprogram divided into blocks before performing a program processing. CONSTITUTION:A CPU 13 executes an initialization process after starting the microprogram from a ROM 11, and the sum check of the block is applied before performing the processing of block of the microprogram divided into blocks. And a block microprogram is diagnosed by comparing with a sum check value attached on a block microprogram, and when noncoincidence is obtained, abnormality information via an I/O port 14 is latched at a latch mechanism 16, and is displayed on a display mechanism 15. By performing diagnosis on every divided block microprogram, the diagnosis of the microprogram in the on-line operation can be performed.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a microprogram diagnostic method for checking a microprogram when a computer system is online and detecting abnormalities.

[Conventional technology]

Figure 2 is a flowchart showing a conventional microprogram diagnosis method. Each process of the program. FIG. 3 is a diagram showing the peripheral structure of a conventional microprogram. In the figure, 11 is a ROM in which a microprogram is recorded, and 12 is an RA.
M, 13 is a microprocessor, 14 is a human output port,
15 is a display mechanism that displays an error when it occurs.

Next, the operation will be explained. Figure 2 shows 17 After the microprogram starts, the parity check or CRC check of the microprogram is performed in the program check of check program 1, and if there is an abnormality, it is shown in Figure 3. A message to that effect is outputted via the I10 port 4, and a display indicating that an abnormality has been detected is displayed on the display mechanism 5. After the microprogram stops processing and performs HALT or performs error processing, it executes the initialization process 2 shown in FIG. 2 and enters each process 3 and 4 of the main program. No particular microprogram check is performed during each process.

[Problem to be solved by the invention]

In conventional diagnostic methods, microprograms are checked only at startup, such as when the power is turned on, and checks are not performed while the system is in operation (online), so microprogram abnormalities cannot be detected during operation. As a result, the reliability of microprogram data during system operation (online) is low, and when an abnormality occurs, there is a problem in that it is impossible to know where in the program the abnormality occurred.

This invention was made to solve the above-mentioned problems. It is possible to check the microprogram during system operation, and when an error occurs, it is possible to display in which area of the microprogram the error occurred. The purpose is to obtain a method for diagnosing microprograms during online operation.

[Means to solve the problem]

The diagnosis method for the microprogram 1 according to the present invention is to divide the microprogram into each block 31°41.42, and before entering the divided blocks 31°41.42, perform a check using the program check routine 5. Compare the sum value of block 3.1, 41.42 to be correct, and if it is correct, return to the beginning of block 31, 41.42 and process block 31, 41.42, and if it is correct, block 31, 41.42 This feature is characterized in that it outputs the status of and displays an abnormality.

[Effect]

The program check routine 5 according to the present invention checks each block of the divided microprogram 1 each time it enters, and compares it with the sum value of the block to be checked to see if it is correct.

If it is correct, it returns to the beginning and processes the block; if it is incorrect, it outputs the status of the block and indicates an error.

[Embodiments of the invention]

Embodiments of the present invention will be described below with reference to the drawings. 1st
The figure is a flowchart showing one embodiment of the present invention, and in the figure, the same reference numerals as in FIG. 2 indicate the same or corresponding parts. In the figure, numerals 31, 41, and 42 are the seven blocks obtained by dividing the microprogram, and 5 is a program check routine that checks each block 31, 4, 1, and 42. Each block 3L4. At the beginning of L42, there is a jump instruction or call instruction for jumping to the program check routine 5, and at the end of the block, there is a checksum value for that block. In this case, block 31 is made up of one process, but blocks 4.1.42 are made up of one process further divided. If one process is long like this, it is divided into multiple parts depending on the length and each is checked individually. FIG. 4 is a peripheral block diagram for latching and displaying an abnormal area when a program abnormality occurs. 11 is a microprogrammer --
12 is R'AM, 13 is a microprocessor, 14 is an I10 board, 15 is a display mechanism that displays error information, etc., and 16 is a launch mechanism that latches display data. be.

Next, the operation of the flowchart shown in FIG. 1 will be explained.

After starting the microprogram, initialization process 2 is performed, and block 3, which is the microprogram process, is performed.
1, but before entering the processing of this block 31, it jumps to the program check routine 5, performs a sum check of block 31, compares it with the value of Chesokusa J added at the end of block 31, and if it is correct, blocks 31 The process returns to the beginning of block diagram 31 and starts processing. block 41
The same is true when one large process such as 42 is divided, and a check is performed each time it is divided. If the sum values do not match in the program check routine 5, the status of the process is output to port 110 1-4 shown in FIG. 4 to indicate an abnormality. This is because the data is latched by the launch mechanism 6, so even if the process jumps to another process and starts processing after the previous error handling, it can be known later by the display mechanism 5.

This method is suitable for microprograms such as control devices for industrial computer systems that require continuous operation for long periods of time and require high reliability. In the above embodiment, a jump instruction or a call instruction to the first program check routine of each process is used, or a hardware interrupt using TIMER17 is used to jump to the program check routine as shown in the block diagram of FIG. You can.

[Effects of the Invention] As described above, according to the present invention, a microprogram is divided into blocks, and each divided block is checked by a program check routine every time it is executed. The data of the microprogram is highly reliable, and it is also possible to know where in the microprogram an abnormality has occurred.

[Brief explanation of the drawing]

FIG. 1 is a flowchart showing an embodiment of the present invention, FIG. 2 is a flowchart showing a conventional microprogram diagnosis method, and FIG.
The figure is a configuration diagram of hardware when executing the conventional diagnosis method, FIG. 4 is a configuration diagram showing an example of hardware when executing the diagnosis method of the present invention, and FIG. It is a block diagram which shows another example of the hardware in the case of execution. Engineering...Check program, 2...Initial setting process, 3, 4...Process, 5...Program check routine, 31.41.42...Block, 11.
...ROM, 12...RAM, 13...CPU, 1
4...-110 port 15... display mechanism, 16...
Latch mechanism, 17... T I MERo agent Masuo Oiwa (2 people) Figure 5

Claims (1)

[Claims] A microprogram diagnostic method for checking a microprogram when a computer system is online and detecting abnormalities, which divides the microprogram into blocks and includes a program check routine before processing the divided blocks. A microprogram characterized in that it performs a check, compares it with the sum value of the block to be checked, and if it is correct, returns to the beginning of the block and processes the block, and if it is incorrect, it outputs the test status of the block and displays an abnormality. diagnostic method.