KR100676462B1 - Diagnosis among multi-processors and error logging system and method - Google Patents

Abstract

The present invention provides a multi-processor diagnosis for detecting an error when a system checks a running state of each module in a hierarchical structure such as DSP / FW / Device Driver / Service / DLL / AP. The present invention relates to an error logging system and a method thereof. According to the present invention, when an error occurs in a module of a lower layer of a multiprocessor, a module of the lower layer in which the error occurs is detected and rebooted, and a reboot message is generated. An error detection module for transmitting to the module, and the alarm information generating module for generating an alarm information message after clearing the error occurrence channel when receiving a reboot message from the error detection module.

PC, Server, Multiprocessor, Error Logging, Debugging

Description

DIAGNOSIS AMONG MULTI-PROCESSORS AND ERROR LOGGING SYSTEM AND METHOD}

1 is a diagram showing the configuration of a multi-processor diagnostic and error logging system according to the present invention.

2 is a diagram illustrating an example of a diagnostic and error logging flow between multi-processors according to the present invention.

3 is a diagram illustrating another example of a diagnostic and error logging flow between multi-processors according to the present invention.

Explanation of symbols on the main parts of the drawings

10: HW module 20: FW module

30: device driver module 40: service module

50: DLL module 60: AP module

70: AP monitoring module 80: alarm sound module

The present invention relates to a multi-processor diagnostic and error logging system and method thereof, and more particularly, a system in which a system is running in a hierarchical structure such as DSP / FW / Device Driver / Service / DLL / AP. The present invention relates to a multi-processor diagnostic and error logging system and method for detecting an error when there is an error.

In general, when an error occurs in one of the running modules in a hierarchical system such as DSP / FW / Device Driver / Service / DLL / AP, the entire system is down.

If the DSP (Digital Signal Processor) is dead, if the upper layer module FW (Firmware) does not check and proceeds to the processor, it causes a functional error and a bus error, causing the entire system to fail. Down.

Therefore, the module of the upper layer periodically checks the running state of the lower layer, and the module of the lower layer sends the periodic diagnostic message to the module of the upper layer to check the running state. There is a need for a stable system.

An object of the present invention for solving the above problems is, when an error occurs in one of the modules (Running) in a hierarchical system such as DSP / FW / Device Driver / Service / DLL / AP, the entire system is down The present invention provides a multi-processor diagnostic and error logging system and a method for preventing a down phenomenon and allowing debugging by leaving error logging when necessary.

According to an aspect of the multi-processor diagnostic and error logging system according to the present invention for achieving the above object, when an error occurs in the module of the lower layer of the multi-processor, the module of the lower layer in which the error occurs By rebooting, and the error detection module for transmitting the reboot message to the module of the upper layer, and when receiving the reboot message from the error detection module, generating alarm information message after clearing the error occurrence channel (clear) Contains modules

The error detecting module diagnoses an error generating module when the count value incremented from the lower layer module does not change for a predetermined time.

If the error detection module does not receive an Alive message transmitted from the lower layer module for a predetermined time, the error detection module resets the lower layer module according to a command of the upper layer module and then resets the reset message. Transmit to the higher layer module.

The error detection module stores error logging information about an error generated from a module of each layer of the multiprocessor.

The system may further include a system monitoring module which re-executes the alarm information generating module and generates an alarm information message when the operating state of the alarm information generating module is down in real time.

When receiving the alarm information generated from the alarm information generation module or the system monitoring module, further comprises an alarm sound module for generating an alarm (Alarm).

On the other hand, according to an aspect of the multi-processor diagnostic and error logging method according to the present invention for achieving the above object, when an error occurs in the module of the lower layer of the multi-processor, the module of the lower layer in which the error occurs A first process of detecting and rebooting a second process, a second process of clearing error-producing channels of the lower layer module, a third process of transmitting a reboot message of the lower layer module to a higher layer module, and In the case where the reboot message is received, a fourth process of generating an alarm information message after clearing the error occurrence channel is cleared.

In the first step, if the count value incremented from the lower layer module does not change for a predetermined time, the module generates an error.

In the first process, if an Alive message is not transmitted from the lower layer module of the multi-processor for a predetermined time, the error generation module is diagnosed.

The method may further include generating an alarm by receiving the alarm information message generated in the fourth process.

In addition, according to an aspect of the multi-processor diagnostic and error logging method according to the present invention for achieving the above object, when the Alive message (Alive Message) is not transmitted for a predetermined time from the lower layer module of the multi-processor, A first process of resetting the lower layer module, a second process of clearing error-producing channels of the lower layer module, a third process of transmitting a reset message of the lower layer module to a higher layer module, and And a fourth process of generating an alarm information message after clearing an error occurrence channel when receiving a reset message of the lower layer module.

In the first process, if an Alive message is not transmitted from the lower layer module of the multi-processor for a predetermined time, the error generation module is diagnosed.

The method may further include generating an alarm by receiving the alarm information message generated in the fourth process.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, detailed descriptions of preferred embodiments of the present invention will be described with reference to the accompanying drawings. It should be noted that reference numerals and like elements among the drawings are denoted by the same reference numerals and symbols as much as possible even though they are shown in different drawings. In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

1 is a view showing the configuration of a multi-processor diagnostic and error logging system according to the present invention.

As shown in FIG. 1, the system of the present invention includes a hardware module (HardWare module, hereinafter referred to as "HW module") 10, a firmware module (hereinafter referred to as "FW module") 20, , A device driver module 30, a service module 40, a dynamic link library (DLL) module 50, an application module (hereinafter referred to as an "AP module"). ), An application monitoring module (70) and an alarm sound module (80).

The HW module 10 is a hardware device installed in a PC or a server, and may include a board that performs various functions.

The FW module 20 is a module for controlling hardware devices installed in the PC or the server. The FW module 20 not only communicates with the HW module 10 but also has an upper layer Device Driver module 30. Communicate.

In particular, the FW module 20 includes a digital signal processor (DSP) 21.

The device driver module 30 is a module that allows the service module 40 to recognize devices mounted in the PC or the server, and communicates with the lower layer FW module 20. In addition to performing the communication with the service module (Service module) 40 of the upper layer.

The service module 40 is a module in which service programs installed in the PC or server are stored. As a service program, for example, Windows, Linux, Unix, or Solaris OS programs such as Solaris) belong to this category.

The service module 40 also communicates with the device driver module 30 of the lower layer and also communicates with the DLL (Dynamic Llink Library) module 50 of the upper layer.

In particular, such a service module 40 stores error logging information on errors generated from modules of each layer.

The DLL (Dynamic Llink Library) module 50 is a set of small programs, and is called when needed by a large program running in a PC or a server to perform a specific function.

As such, the DLL (Dynamic Llink Library) module 50 also communicates with the service module 40 of the lower layer and also communicates with the AP module 60 of the upper layer.

The AP module 60 is an application program that is called and used by a user, and various applications belong to this, and communicate with the DLL (Dynamic Llink Library) module 50 of the lower layer.

Application monitoring module (70) is a module for monitoring the state of the AP module 60, AP module 60 due to an error as a result of monitoring the running (Running) state of the AP module 60. ) Is down, the AP module 60 is rebooted and then re-executed.

The alarm sound module 80 generates an alarm sound when alarm information is transmitted from the AP monitoring module 70.

Accordingly, the system administrator can listen to the alarm sound generated from the alarm sound module 80 and perform error tracking in the multiprocessor module.

FIG. 2 is a diagram illustrating a diagnosis and error logging flow between multi-processors according to the present invention. In particular, FIG. 2 illustrates a diagnosis and error logging method between an FW module and a DSP when an error occurs from a DSP module. Let's explain.

As shown in FIG. 2, first, the DSP periodically increments a count in a status register S10.

Accordingly, the FW module checks whether the count changes for a predetermined time (S20).

As a result of the check, the FW module may reboot the DSP by rebooting (S30) if the count does not change for a certain time, for example, for 1 second.

Subsequently, the FW module clears the corresponding CHs (16CH per DSP) (S40) and transmits a DSP Reboot message to the device driver module (S50).

Accordingly, when the device driver module receives the DSP Reboot message from the FW module, the device driver module clears the corresponding CHs (16CH per DSP) (S60), and transmits the DSP Reboot message to the service module (S70). Done.

Accordingly, when the service module also receives the DSP Reboot Message from the driver module, the corresponding CHs (16CH per DSP) are cleared (S80), and the DSP Reboot Message is transmitted to the DLL module (S90). .

Subsequently, when receiving the DSP Reboot Message from the service module, the DLL module clears the corresponding CHs (16CH per DSP) (S100) and transmits the DSP Reboot Message to the AP module (S110).

Subsequently, when the AP module receives the DSP Reboot message from the DLL module, the AP module clears the corresponding CHs (16CH per DSP) (S120), and then transmits alarm information to the alarm sound module. S130).

3 is a diagram illustrating a diagnostic and error logging flow between multi-processors according to the present invention. In particular, FIG. 3 is a diagram illustrating a diagnostic and error logging method between an FW module and a driver module when an error occurs from an FW module. This will be explained.

As shown in FIG. 3, first, the FW module periodically increases the count in the Status Register (S10), and transmits an Alive message to the upper layer driver module every 20 seconds. do.

Accordingly, the driver module checks whether the count changes for a predetermined time (S20).

As a result of the check, the driver module resets the FW module (S30) if the count does not change for a predetermined time, for example, 30 seconds, and then clears the corresponding CHs (the corresponding board) (Clear) (S40). Then, the FW Reset Message is transmitted to the service module of the higher layer (S50).

Accordingly, when receiving the FW Reset Message from the driver module, the service module clears the corresponding CHs (the corresponding boards) (S60), and transmits the FW Reset message to the DLL module of the upper layer (S70). .

Subsequently, when receiving the FW Reset Message from the service module, the DLL module clears the corresponding CHs (the corresponding boards) (S80) and transmits the FW Reset Message to the upper layer AP module (S90).

Subsequently, when the AP module receives the FW Reset Message from the DLL module, after clearing the corresponding CHs (the corresponding boards) (S100), the AP module transmits alarm information to the alarm sound module (S110). Done.

On the other hand, in step S20 of checking whether the count has been changed, if the count is normally changed, the service module checks whether or not to receive an Alive message transmitted from the FW module (S120).

As a result of the check, the service module transmits an FW Reset CMD command to the driver module (S130) if it fails to receive an Alive Message from the driver module for a certain time, for example, for one minute.

Accordingly, when the driver module receives the FW Reset CMD command from the service module, the driver module resets the FW module and transmits the FW Reset message to the service module again.

Subsequently, when the FW Reset Message is received from the driver module, the service module clears the corresponding CHs (the corresponding boards) (S60) and transmits the FW Reset Message to the upper level DLL module (S70).

Subsequently, when receiving the FW Reset Message from the service module, the DLL module clears the corresponding CHs (the corresponding boards) (S80) and transmits the FW Reset Message to the upper layer AP module (S90).

Subsequently, when the AP module receives the FW Reset Message from the DLL module, after clearing the corresponding CHs (the corresponding boards) (S100), the AP module transmits alarm information to the alarm sound module (S110). Done.

Accordingly, the alarm sound module generates an alarm when alarm information is transmitted from the AP module, and the system manager listens to the generated alarm sound and diagnoses the error in the multiprocessor module. Error logging is enabled.

In the above, specific preferred embodiments of the present invention have been illustrated and described. However, the present invention is not limited to the above-described embodiment, and various modifications can be made by any person having ordinary skill in the art without departing from the gist of the present invention attached to the claims. will be.

According to the present invention, when an abnormality occurs in a specific module through monitoring of each module of a multiprocessor module, the system falls into an error state by resetting only the corresponding module and transmitting reset information to a higher level. The following services can be normally executed without.

Claims (13)

In the multi-processor diagnostic and error logging system, If an error occurs in the module of the lower layer of the multi-processor, the error detection module for detecting and rebooting the module of the lower layer that the error occurs, and sends a reboot message to the module of the upper layer; When receiving the reboot message from the error detection module, the multi-processor diagnostic and error logging system comprising an alarm information generating module for generating an alarm information message after clearing (error) the error occurrence channel. The method of claim 1, The error detection module, The multi-processor diagnostic and error logging system, characterized in that the diagnosis by the error generating module, if the count value incremented from the module of the lower layer does not change for a predetermined time. The method of claim 1, The error detection module, If the Alive message transmitted from the lower layer module is not received for a predetermined time, the module of the lower layer is reset according to the command of the higher layer module, and then the reset message is sent to the higher layer module. Multiprocessor diagnostic and error logging system, characterized in that for transmitting. The method of claim 1, The error detection module, Error logging information (Error Logging information) for the error generated from the module of each of the multi-processor layer. The method of claim 1, In the case of the down state by checking the operation state of the alarm information generation module in real time, the multi-processor diagnosis and error, characterized in that it further comprises a system monitoring module for re-executing the alarm information generation module to generate an alarm information message. Logging system. The method of claim 5, When receiving the alarm information generated from the alarm information generation module or the system monitoring module, the multi-processor diagnostic and error logging system further comprises an alarm sound module for generating an alarm (Alarm). In the multi-processor diagnostic and error logging method, A first step of detecting and rebooting a module of a lower layer in which the error occurs when an error occurs in a module of a lower layer of a multiprocessor; A second process of clearing faulty channels of the lower layer module; Transmitting a reboot message of the lower layer module to a module of an upper layer; And a fourth step of generating an alarm information message after clearing an error occurrence channel when the reboot message is received. The method of claim 7, wherein In the first step, The multi-processor diagnosis and error logging method, characterized in that the diagnosis by the error generating module, if the count value incremented from the module of the lower layer does not change for a predetermined time. The method of claim 7, wherein In the first step, If an Alive message is not transmitted for a predetermined time from the lower layer module of the multi-processor, the diagnosis between the multi-processor and error logging method characterized in that the diagnostic module. The method of claim 7, wherein And receiving an alarm information message generated in the fourth process to generate an alarm. 10. In the multi-processor diagnostic and error logging method, A first process of resetting the lower layer module when an Alive message is not transmitted from the lower layer module of the multiprocessor for a predetermined time; A second process of clearing faulty channels of the lower layer module; Transmitting a reset message of the lower layer module to a module of an upper layer; And receiving a reset message of the lower layer module, and generating an alarm information message after clearing an error occurrence channel. The method of claim 11, In the first step, If an Alive message is not transmitted for a predetermined time from the lower layer module of the multi-processor, the diagnosis between the multi-processor and error logging method characterized in that the diagnostic module. The method of claim 11, And receiving an alarm information message generated in the fourth process to generate an alarm. 10.

Images