JP2010244185A - Device for recording and management of log data - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To automate log data acquisition when any failure occurs without compressing the capacity of a recording medium. <P>SOLUTION: A log data recording management device includes a first processor (main CPU 11) to which a log data recording device (recording medium 19) is connected and one or more second processor (sub CPU 12 to 14) communicatively connected to the first processor. The first or one or more second processors include a means for collecting log data related with a set value to hardware installed in each of them in executing a program, and for temporarily storing the log data in storage devices (memory 15 and memories 16 to 18) each of which can be referred to. The second processors are respectively configured to stop the collection of the log data when the occurrence of the failure is detected, and to transfer the log data stored in the storage devices (memories 16 to 18) by inter-processor communication to a first processor, and for storing a log data in the log data recording device. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a log data recording management apparatus suitable for use in, for example, an assembly inspection process of an in-vehicle information device, in which a product is constructed by a plurality of processing devices (CPUs).

  In the on-site production line, product inspection is performed in a state in which software is installed and operable after hardware is assembled. By the way, when a problem occurs at a site where the operation is possible only after the software is installed, log data that can be acquired by the product may be required for analysis.

  At present, log data can be obtained by human operation, but there is no choice but to obtain log data after confirming the reproduction of the product in which the problem has occurred. The number of man-hours for handling etc. increases. In addition, since the inspection is performed semi-automatically, forgetting to acquire log data, or even if it can be acquired, necessary information is often deleted, and in this case, time may be spent unnecessarily.

  On the other hand, Patent Document 1 discloses a technique in which another CPU mounted on a product substitutes program debugging by inter-processor communication in order to capture the state at the moment when a malfunction of a CPU having no program debugging function occurs. It is disclosed.

JP 2007-141138 A

  Patent Document 1 discloses means for recording information at the moment when the above-described failure occurs, but it is difficult to specify the circumstances and factors leading to the occurrence of the failure only by recording the result. There is also. In addition, it is possible to save log data at all times, but at this time, even data that is not related to a failure is saved, which may adversely affect the compression and inspection of the capacity of the recording medium.

  The present invention has been made to solve the above-described problems, and automating the acquisition of log data at the time of failure without reducing the capacity of the recording medium to reduce the burden on the operator at the time of product inspection. It is an object to provide a log data recording management device.

  In order to solve the above-described problems, a log data recording management device according to the present invention includes a first processing device to which a log data recording device is connected and one or more first processing devices that are communicably connected to the first processing device. Log data recording management device including two processing devices, wherein each of the first and second processing devices collects log data related to a set value to each hardware at the time of program execution, and each of the log data is referred to Log data stored in the storage device, wherein the second processing device stops collecting the log data when detecting that a malfunction has occurred in the operation, Is transferred to the first processing device by inter-processor communication and stored in the log data recording device.

  According to the log data recording management apparatus of the present invention, it is possible to reduce the burden on the operator at the time of product inspection by automating the acquisition of log data when a failure occurs without reducing the capacity of the recording medium.

It is a block diagram which shows the structure of the log data recording management apparatus which concerns on Embodiment 1 of this invention. It is the figure which showed typically about the log data storage method to the memory | storage device which the log data recording management apparatus which concerns on Embodiment 1 of this invention has. It is the block diagram which expanded the function and showed the structure of the program which the 1st processing apparatus of the log data recording management apparatus concerning Embodiment 1 of this invention performs. It is the block diagram which expanded the function and showed the structure of the program which the 2nd processing apparatus of the log data recording management apparatus concerning Embodiment 1 of this invention performs. It is a flowchart which shows operation | movement of the 1st processing apparatus of the log data recording management apparatus which concerns on Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the 2nd processing apparatus of the log data recording management apparatus which concerns on Embodiment 1 of this invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
Embodiment 1 FIG.
FIG. 1 is a block diagram showing a configuration of a log data recording management apparatus according to Embodiment 1 of the present invention. Here, an example is shown in which the log data recording management device according to Embodiment 1 of the present invention is applied to a log data recording management device.

  As shown in FIG. 1, the log data recording management apparatus can communicate with a first processing apparatus (hereinafter referred to as a main CPU 11) to which a recording medium 19 is connected, and the main CPU 11 via a bus. It includes sub CPUs 12 to 14 as one or more second processing devices to be connected. The recording medium 19 is assumed to be constituted by a large-capacity hard disk or the like used as a log data recording device, and is not directly connected to the sub CPUs 12 to 14.

  Here, it is assumed that, for example, the main CPU 11 is mounted on the main body of the log data recording management device, and the sub CPUs 12 to 14 are mounted to control peripheral devices such as a navigation device, a tuner device, and a communication device. To explain.

The main CPU 11 is connected to a memory 15 made up of randomly accessible elements, and the sub CPUs 12 to 14 are connected to memories 16 to 18 made up of similarly accessible random elements.
For example, as shown in FIG. 2, a log data storage area (H / W setting data storage area) is assigned to a predetermined area in the memories 16 to 18, as in the memory 15. When log data has been written up to address n + n, it is used as a ring buffer that returns to the first address n. Although not shown in the drawing, a communication buffer is also assigned to a partial area of the memories 15 and 16 to 18 so that communication between processors is realized. Unlike the log data described above, the area to which the communication buffer is allocated is used as a normal RAM.

Reference numeral 20 denotes an operation key switch. When the sub CPUs 12 to 14 manually transfer log data collected by inter-processor communication to the main CPU 11, specific information (recording key code to be described later) is input. It is also used as an operation input device.
Reference numerals 30a to 30c indicate externally connected devices such as various sensors and motors connected to the peripheral devices described above.

FIG. 3 is a functional block diagram showing the structure of a program executed by the first processing device (main CPU 11) of the log data recording management device according to the first embodiment of the present invention.
As shown in FIG. 3, if the program executed by the main CPU 11 is roughly classified for each function, the main control unit 110, the log data collection unit 112, the operation state determination unit 111, the inter-processor communication unit 113, Log data acquisition unit 114.

The main control unit 110 performs an original function as the main CPU 11 and performs sequence control among a log data collection unit 112, an operation state determination unit 111, an inter-processor communication unit 113, and a log data acquisition unit 114, which will be described later. .
The log data collection unit 112 collects a history of values set in hardware (not shown) such as a register built in the CPU from when the program is started until the log data collection is instructed. It has a function of saving in the memory 15.

  The operation state determination unit 111 has a function of detecting occurrence of a malfunction by the main CPU 11 and controlling the log data collection unit 112 and the log data acquisition unit 114. The operation state determination unit 111 may be replaced with a DTC (failure diagnosis) detection program as will be described later.

The inter-processor communication unit 113 has a function of allocating a communication buffer to the memory 15 under the control of the main control unit 110 and exchanging information with the sub CPUs 12 to 14 using the communication buffer. Here, the exchanged information includes a recording key code to be described later in addition to the log data.
The log data acquisition unit 114 has a function of performing data transfer for acquiring log data of the sub CPUs 12 to 14 transmitted via the inter-processor communication unit 113 and storing it in the recording medium 19.

FIG. 4 is a functional block diagram showing the structure of a program executed by the second processing device (sub CPU 12) of the log data recording management device according to the first embodiment of the present invention.
As shown in FIG. 4, the programs executed by the sub CPU 12 can be broadly classified into functions. The main control unit 120, the log data collection unit 122, the operation state determination unit 121, the inter-processor communication unit 123, A specific information notification unit 124.

The main control unit 120 executes, for example, an original function as the sub CPU 12 for controlling the tuner, a log data collection unit 122, an operation state determination unit 121, an inter-processor communication unit 123, and a specific information notification unit which will be described later. 124 sequence control is performed.
The log data collection unit 122 collects a history of values set in hardware (not shown) such as a register in the CPU until the log data collection stop is instructed after the program is started and stored in the memory 16. It has the function to do. The operation state determination unit 121 has a function of controlling the log data collection unit 122 and the specific information notification unit 124 by detecting the occurrence of a malfunction by the sub CPU 12.

The inter-processor communication unit 123 has a function of allocating a communication buffer to the memory 16 under the control of the main control unit 120 and exchanging information with the main CPU 11 using the communication buffer. The information exchanged here includes a recording key code to be described later in addition to the log data.
When the collected log data is transferred to the main CPU 11 by inter-processor communication, the specific information notifying unit 124 transmits inter-processor communication with specific information (recording key code) input from the operation key switch 20 as a trigger. A function of notifying the main CPU 11 via the unit 123.

  The sub CPUs 13 and 14 have the same configuration as the sub CPU 12 described above, and are not described in the sense of avoiding duplication.

5 and 6 are flowcharts showing the operation of the log data recording management apparatus according to the first embodiment of the present invention. The operation of the main CPU 11 (FIG. 5) and the operation of the sub CPU 12 (13, 14) (FIG. 6). ).
Hereinafter, the log data recording operation of the main CPU 11 and the sub CPU 12 (13, 14) shown in FIGS. 3 and 4 will be described in detail with reference to the flowcharts of FIGS.

  First, in FIG. 5, the main CPU 11 starts collection of log data as the program process proceeds (step ST502) when the program is started (step ST501 “YES”). Here, the log data is a history of setting values in a register built in the main CPU 11, and the log data collection unit 112 secures the values in the memory 15 by the main control unit 110 every time the setting values are changed. To the hardware setting data area. Here, when the log data write reaches the final address of the secured area, it returns to the start address of the secured area and overwrites the old log data as described above.

By the way, the operation state determination unit 111 can detect a defect in the externally connected devices 30a to 30c by executing a DTC (fault diagnosis) detection program.
According to the DTC detection program used here, an ID is provided for each problem that has occurred. For example, the ID when the outside temperature sensor as the external connection device 30a is short-circuited with GND is 1-2-1, the ID when the differential of the driver side damper motor is too long is 3-2-1, etc. is there. By referring to this ID, the operation state determination unit 111 can identify whether the defect is inside the product or the external connection devices 30a to 30c.

  When the DTC detection process determination by the operation state determination unit 111 described above is performed (step ST503), when it is determined that the problem is in the product, that is, the main CPU 11 (step ST504 “YES”), the operation state determination unit 111. Controls the log data collection unit 112 under the control of the main control unit 110, stops log data collection, and stops writing log data to the memory 15 (step ST505). By this process, setting information from before the occurrence of the failure can be secured.

  Next, main controller 110 activates inter-processor communication by inter-processor communication unit 113, and transmits a recording key code to each of the sub CPUs 12 to 14 (step ST506). Here, the “recording key code” refers to specific information that prompts the sub CPUs 12 to 14 to record log data. Subsequently, the inter-processor communication unit 113 receives the log data sequentially transmitted from the sub CPUs 12 to 14 (step ST511), and the log data acquisition unit 114 stores the acquired log data in the recording medium 19 after the log data reception is completed. (Step ST512).

On the other hand, when it is determined in step ST504 that the failure is not in the externally connected devices 30a to 30c (step ST504 "NO"), the main control unit 110 refers to the communication buffer allocated to the memory 15 for inter-processor communication. (Step ST507), it is determined whether or not the key code for recording is in the communication buffer (Step ST508).
The recording key code referred to here is the same as that manually generated by the sub CPUs 12 to 14 as will be described later.

If it is determined in step ST508 that there is a recording key code (“YES” in step ST508), the main control unit 110 controls the log data collection unit 112 because log data is continuously transmitted from the sub CPUs 12 to 14. Then, log data collection is stopped, log data writing to the memory 15 is stopped (step ST509), and a recording key code is transmitted to each of the sub CPUs 12 to 14 using inter-processor communication by the inter-processor communication unit 113. (Sup ST510)
As a result, the main CPU 11 is ready for reception, and the inter-processor communication unit 113 receives log data sequentially transmitted from the sub CPUs 12 to 14 (step ST511). The log data acquisition unit 114 stores the acquired log data in the recording medium 19 after completion of the log data reception, and stores the log data transmitted from the sub CPUs 12 to 14 together with its own log data in the memory 15 ( Step ST512).

  Through the above-described processing, the main CPU 11 can automatically save its own log data and log data transmitted from the sub CPUs 12 to 14 in the recording medium 19 without imposing a burden on the operator.

  Next, the log data recording operation of the sub CPUs 12 to 14 will be described with reference to FIG. In FIG. 6, first, the sub CPUs 12 to 14 start collection of log data as the program process proceeds (step ST602) when the program starts (step ST601 “YES”). ).

As described above, the operation state determination unit 121 can detect a failure of the externally connected devices 30a to 30c by executing a DTC (fault diagnosis) detection program.
After the DTC detection process determination by the operation state determination unit 121 (step ST603), when it is determined that the problem is inside the product, that is, the problem of the sub CPUs 12 to 14 (step ST604 "YES"), the main control unit 120 Under control, the log data collection unit 122 stops collecting log data and stops writing log data to the memories 16 to 18 (step ST605). By this process, setting information from before the occurrence of the failure can be secured.

By the way, since the sub CPUs 12 to 14 do not have a direct read / write control function to the recording medium 19 for storing log data, the sub CPUs 12 to 14 transmit a recording key code to the main CPU 11 as a trigger when transferring the log data. There is a need.
Here, the recording key code is the same as that generated by manual input by the operation key switch 20, and is generated, for example, as a trigger for recording log data by simultaneously pressing a certain key switch. The specific information notification unit 124 acquires this recording key code and transmits it to the main CPU 11 by the inter-processor communication unit 123 (step ST606). Subsequently, the inter-processor communication unit 123 transmits the log data temporarily stored in the memories 16 to 18 to the main CPU 11 (step ST607).

On the other hand, when it is determined in step ST604 that the externally connected devices 30a to 30c are not defective (step ST604 "NO"), the main control unit 120 communicates with the communication buffers allocated to the memories 16 to 18 for inter-processor communication. (Step ST608), it is determined whether or not there is a recording key code in the communication buffer (step ST609).
Here, when it is determined that there is a recording key code (step ST609 “YES”), the main control unit 120 controls the log data collection unit 122 to stop the log data collection and stores the log data in the memories 16 to 18. Log data writing is stopped (step ST610). By this processing, setting information to the CPU internal register before the occurrence of the trouble is secured.

Finally, the log data temporarily stored in the memories 16 to 18 by the inter-processor communication unit 123 is transmitted to the main CPU 11 and the above-described series of processing ends.
As described above, the main CPU 11 can receive the log data sequentially transmitted from the sub CPUs 12 to 14 and store the log data in the recording medium 19 after the completion of the log data reception.

  By the above processing, the sub CPUs 12 to 14 can automatically save their own log data in the recording medium 19 without imposing a burden on the operator.

As described above, according to the log data recording management device according to the first embodiment of the present invention, for example, in FIG. 1, the first (main CPU 11) and one or more second processing devices (sub CPUs 12 to 14). Includes means for collecting log data relating to setting values to the hardware during program execution and temporarily storing them in storage devices (memory 15 and memories 16 to 18) that can be referred to, and the second processing device includes: When the occurrence of a malfunction is detected, the collection of log data is stopped, and the log data stored in the storage device (memory 16 to 18) is transferred to the first processing device by inter-processor communication, and the log data recording device (recording medium) 19), it is possible to reliably acquire log data up to the occurrence of a defect, and therefore it is not necessary to perform reproduction confirmation, and the time until analysis. Shrinkage is Hakare, burden on the operator is reduced.
For malfunction detection, if the DTC detection program is diverted, there is no need to reconstruct the log data recording management apparatus at a relatively low cost.

The functions of the first processing device (main CPU 11) or the second processing device (sub CPUs 12 to 14) shown in FIGS. 3 and 4 may be realized entirely by software, or at least a part thereof. May be realized by hardware.
For example, at the time of program execution, log data related to the setting values for each hardware is collected, and when data processing is temporarily stored in a storage device that can be referred to, or when occurrence of a malfunction is detected, log data is collected. Data processing for stopping and transferring the log data stored in the storage device to the first processing device by inter-processor communication and storing it in the log data recording device may be realized on the computer by one or more programs. In addition, at least a part of it may be realized by hardware.

  10 log data recording management device, 11 main CPU (first processing device), 12-14 sub CPU (second processing device), 15-18 memory (storage device), 19 recording medium, 20 key switch for operation ( Operation input device), 30a, 30c Externally connected device, 110, 120 Main control unit, 111, 121 Log data collection unit, 112, 122 Operation state determination unit, 113, 123 Inter-processor communication unit, 114 Log data acquisition unit, 124 Specific information notification unit.

Claims (5)

A log data recording management device including a first processing device to which a log data recording device is connected, and one or more second processing devices that are communicably connected to the first processing device,
The first and second processing devices are:
At the time of program execution, it includes means for collecting log data related to setting values to the hardware of each, and temporarily storing them in a storage device that can be referred to.
The second processing device includes:
When the occurrence of a malfunction is detected, the collection of the log data is stopped, and the log data stored in the storage device is transferred to the first processing device by inter-processor communication and stored in the log data recording device. A log data recording management device characterized by the above. It has an operation input device that inputs specific information,
The second processing device includes:
2. The log data according to claim 1, wherein when the collected log data is transferred to the first processing device by the inter-processor communication, specific information acquired from the operation input device is used as an operation trigger. Record management device. The first and second processing devices are:
3. The log data according to claim 1, wherein when it is detected that a malfunction has occurred in the operation, it is determined whether or not the malfunction has occurred by referring to information indicating the malfunction that has occurred. Record management device. The first processing device includes:
If it ’s your fault,
Stops collecting its own log data, transmits specific information for encouraging the one or more second processing devices to record log data, receives log data transmitted from the second processing device, and receives the log Save it in a data recorder,
If it ’s not your fault,
If there is the specific information in the communication buffer allocated to the storage device, the collection of the log data is stopped, and specific information that prompts the second processing device to record the log data is transmitted, and the second processing device 4. The log data recording management apparatus according to claim 3, wherein the log data recording management apparatus waits for transmission of log data from the log data and stores it in the log data recording apparatus. The second processing device includes:
If it ’s your fault,
Stop collecting its own log data and send specific information input from the operating device to the first processing device and send the collected log data;
If it ’s not your fault,
4. The log data collection is stopped and the collected log data is transmitted to the first processing device if the specific information is present in a communication buffer allocated to the storage device. Log data record management device.

Images