Vehicle control device

Information

  • Patent Grant
  • 10394675
  • Patent Number
    10,394,675
  • Date Filed
    Tuesday, January 12, 2016
    8 years ago
  • Date Issued
    Tuesday, August 27, 2019
    5 years ago
Abstract
The present invention provides a vehicle control device with which, even when an abnormality is detected in a core in a multi-core processor, it is possible to reduce the time needed until the core in which the abnormality is detected restarts and re-executes application software. The present invention is characterized by being provided with: a diagnostic means for carrying out a diagnostic process when starting a processor core, the diagnostic process including hardware diagnosis performed by hardware and software diagnosis performed using software after the hardware diagnosis; and a diagnostic process information change processing means for changing the method for executing the diagnostic process when all of the processor cores are started and when one of the processor cores is restarted.
Description
TECHNICAL FIELD

The present invention relates to a vehicle control device that controls a system with a multi-core processor, the system including necessary functions over a wide range and being a large-scale system including a plurality of pieces of hardware and a plurality of pieces of software combined, in transport machinery, such as a motor vehicle, a railway, or an elevator.


BACKGROUND ART

A built-in control device that controls an object to be controlled with so-called built-in software, is used in a motor vehicle, an elevator, or construction machinery. The built-in software is advantageously capable of achieving flexible and advanced control in comparison to a conventional method with a mechanical mechanism or an electric circuit.


Electronic control unit (ECU) integration including functions that have been conventionally, individually mounted on different ECUs, aggregated on one ECU, has been progressively developed in order to reduce an in-vehicle space and manufacturing costs for such a built-in control device, for example, a vehicle control device. During the progress of the ECU integration, a multi-core processor has been already applied to the vehicle control device because of the plurality of functions required to be processed on the same ECU.


The multi-core processor is capable of performing different pieces of processing in parallel with a plurality of cores and additionally is, when a partial core fails, capable of performing alternative processing to application software allocated to the partial core, with another core. Accordingly, it has been known that redundancy of the system can be achieved, and for example, PTL 1 describes the redundancy.


When the failure of the partial core in the multi-core processor is detected, only the core including the failure detected, restarts so that the failed core can be restored with the function of the entire system not being suspended. As a technique of achieving the above, a technique of dynamically changing operation and non-operation for each core in the multi-core processor, has been known, and, for example, PTL 2 describes the technique.


However, the throughput of the entire multi-core processor has an upper limit so that all initial application software is difficult to execute during the restart of the partial core. Accordingly, the core including the failure detected restarts as soon as possible and the allocated application software is executed, preferably.


CITATION LIST
Patent Literature

PTL 1: JP 2007-154050 A


PTL 2: JP 2006-260568 A


SUMMARY OF INVENTION
Technical Problem


FIG. 2 illustrates an example of an in-vehicle function allocated to each core in a multi-core microcomputer. A core 1 performs an advanced driver assistance systems (ADAS) function, and a core 2 and a core n perform an electric brake system and a communication function, respectively, in FIG. 2. In this manner, integration of ECUs is performed with the multi-core processor so that the functions that have been conventionally processed by the individual ECUs, can be processed by one ECU.



FIGS. 3(a) to 3(c) illustrate a procedure until the core restarts in a case where a failure of the core 1 has been detected in the multi-core microcomputer. FIG. 3(a) is a block diagram of the core 1 including an abnormality detected. FIG. 3(b) is a block diagram of alternative processing being performed to the ADAS function that has been performed by the core 1, by the core 2, based on PTL 1. FIG. 3(c) is a block diagram of only the core 1 restarting, based on PTL 2.


In this manner, even when the abnormality is detected in the partial core, using the multi-core processor can continue an operation with the function of the entire system not being suspended, and can restore the original state.


In FIGS. 3(a), 3(b), and 3(c), the core 2 performs the ADAS function of the core 1 so that the throughput of the core 2 considerably increases. Accordingly, when the abnormality is detected in the core, the core 1 preferably restarts at high speed as much as possible so as to be restored in the original state. However, restart processing of the core has not been considered in the conventional techniques.


As described above, an object of the present invention is to provide a vehicle control device capable of, when an abnormality is detected in a partial core on a multi-core processor, shortening time necessary until application software is re-executed since a restart of the core including the abnormality detected.


Solution to Problem

In order to achieve the object, the present invention includes a method of performing individual pieces of diagnostic processing when all processor cores start and when a partial core in all the processor cores restarts, and performs a partial-processor-core-restart diagnostic processing method when only the partial processor core restarts, so as to shorten time necessary for restarting the partial processor core. Particularly, in the diagnostic processing when the partial processor core restarts, another processor core performs software diagnosis before the processor core that restarts performs the software diagnosis, so that the time necessary for the restart shortens.


Advantageous Effects of Invention

According to the present invention, when only the partial core in the multi-core processor restarts, the time necessary until the application software is executed since the restart of the core, can shorten.





BRIEF DESCRIPTION OF DRAWINGS


FIG. 1 is a block diagram of a system configuration of a vehicle control device according to one embodiment of the present invention.



FIG. 2 is a block diagram of specific exemplary parallel processing of functions with a multi-core microcomputer.



FIGS. 3(a) to 3(c) are block diagrams illustrating a flow of specific processing until a core restarts since an abnormality has been detected in the multi-core microcomputer in a case where a conventional technique has been used.



FIG. 4 is a flow chart of a typical example until application software is executed since a start of the microcomputer.



FIG. 5 is a flow chart of a specific example until the application is executed since a start of processor cores, in a proposed technique.



FIG. 6 is a block diagram of a specific example of software diagnosis when a partial core restarts, in the proposed technique.



FIG. 7 is a block diagram of a specific example of software diagnosis progress in a storage area in the proposed technique.



FIG. 8 is a block diagram of a specific example of software diagnosis progress in a storage area when a plurality of cores cooperates with each other in the proposed technique.





DESCRIPTION OF EMBODIMENTS

One embodiment of the present invention will be described below with reference to the drawings.



FIG. 1 is a block diagram of a system configuration of a vehicle control device according to the one embodiment of the present invention. The vehicle control device 1 includes a diagnostic technique 101, a diagnostic process method change unit 102, a power source IC 103, a multi-core processor 104, a storage area 105, and a diagnostic process log 106.


Here, the multi-core processor 104 includes a plurality of cores 10401, 10402, and 10403.


Here, the diagnostic technique 101 includes an all-core-start diagnostic technique 10101 being a diagnostic technique used in starting all the cores and a partial-core-restart diagnostic technique 10102 being a diagnostic technique used in restarting a partial core. In starting the processor cores, the diagnostic process method change unit 102 selects the all-core-start diagnostic technique 10101 when all the cores start and selects the partial-core-restart diagnostic technique 10102 when the partial core restarts. Accordingly, time necessary until application software is executed since the restart of the partial core, shortens.



FIG. 4 is a flow chart of a typical example until the application is executed since a start of the microcomputer. Processing starts at step S1020101. The microcomputer starts at step S1020102. A built-in self-test (BIST) is performed at step S1020103. Diagnosis with software is performed at step S1020104. The application is executed at step S1020105 and then the processing finishes at step S1020106.


As illustrated in FIG. 4, typically when the microcomputer starts, the BIST built in a circuit (hardware) is performed and then the diagnosis with the software is performed.


Here, the software diagnosis described at step S1020104 corresponds to, for example, RAM diagnosis on the storage area 105 using the software. More specifically, the diagnosis writes a fixed value into the storage area 105, and determines whether a result read after the writing is equivalent to the initial fixed value. Accordingly, the diagnosis of whether the storage area 105 normally operates, can be performed. In addition, examples of the software diagnosis include ROM diagnosis using a checksum and diagnosis on an error check and correct (ECC) function by fault injection.



FIG. 5 is a flow chart of a specific example until the application is executed since a start of the processor cores in the proposed technique, and processing starts at step S1020201. The core starts at step S1020202. It is determined whether only a partial processor core has started, at step S1020203. When Yes is acquired, namely, only the partial processor core has started, the processing proceeds to step S1020204 and then the partial-core-restart diagnostic technique 10101 is performed. A partial-core-start BIST is performed at step S1020204. Partial-core-restart software diagnosis is performed at step S1020205. The application software is executed at step S1020206 and the processing finishes at step S1020207. Meanwhile, when No is acquired at step S1020203, namely, all the processor cores have started, the processing proceeds to step S1020208 and the all-core-start diagnostic technique 10102 is performed. An all-core-start BIST is performed at step S1020208. All-core-start software diagnosis is performed at step S1020209. The application software is executed at step S1020206, and the processing finishes at step S1020207.



FIG. 6 illustrates a specific example of the software diagnosis in restarting the partial core when the proposed technique has been used. FIG. 6 illustrates a state where an abnormality has been detected in the core 1 and the partial-core-restart diagnostic technique 10101 has been performed. In the proposed technique, the core n previously performs the software diagnosis and a core 1 storage area being a range to be diagnosed is diagnosed during the core 1 including the abnormality detected, being performed with the BIST, so that time until the core 1 executes the application software can shorten.



FIG. 7 illustrates progress management when the software diagnosis is performed to a storage area 10502. As illustrated in FIG. 7, as a method of managing the progress of the software diagnosis, storing and managing an address value in a range including the diagnosis finished, can resume the software diagnosis from the initial position even when work is changed during the diagnosis.



FIG. 8 illustrates software diagnosis progress of a storage area 10503 when the plurality of cores cooperates with each other. As illustrated in FIG. 8, when diagnosis is performed with two cores, one core starts the diagnosis from a lower address value and the other core starts the diagnosis from a higher address value so that time necessary for the diagnosis can further shorten.


REFERENCE SIGNS LIST




  • 1 vehicle control device


  • 101 diagnostic means


  • 10101 all-core-start diagnostic means


  • 10102 partial-core-restart diagnostic means


  • 102 diagnostic process method change unit


  • 103 power source IC


  • 104 multi-core processor


  • 10401, 10402, 10403 processor core


  • 105, 10501, 10502, 10503 storage area


  • 106 diagnostic process log


Claims
  • 1. A vehicle control device comprising: a plurality of processing cores that include a first processing core and a second processing core, wherein each processing core is assigned one or more in in-vehicle functions so that the first processing core is assigned a first in-vehicle function and the second processing core is assigned a second in-vehicle function; anda storage area that is communicatively coupled to the plurality of processing cores, wherein the storage area includes a plurality of portions that are each assigned to a respective processing core;wherein each respective processing core from the plurality of processing cores is configured to: detect a fault by performing a hardware diagnosis by the respective processing core when the respective processing core is started, andperform a software diagnosis on the portion of the storage area assigned to the respective processing core after the hardware diagnosis is completed; andwherein, on a condition that the fault is detected in the first processing core, the vehicle control device is configured to: reassign the first in-vehicle function from the first processing core to the second processing core, wherein the second processing core executes both the first in-vehicle function and the second in-vehicle function,perform the software diagnosis on the portion of the storage area assigned to the first processing core using a third processing core, andrestart the first processing core.
  • 2. The vehicle control device according to claim 1, wherein an access right to the portion of the storage area that is allocated to the first processing core is changed in performing the software diagnostic of the storage area.
  • 3. The vehicle control device according to claim 1, further comprising: a dedicated processor core configured to detect faults in the plurality of processing cores.
  • 4. The vehicle control device according to claim 1, wherein a diagnostic result of the software diagnosis is output as a log.
Priority Claims (1)
Number Date Country Kind
2015-009051 Jan 2015 JP national
PCT Information
Filing Document Filing Date Country Kind
PCT/JP2016/050604 1/12/2016 WO 00
Publishing Document Publishing Date Country Kind
WO2016/117402 7/28/2016 WO A
US Referenced Citations (4)
Number Name Date Kind
6854081 Suzuki Feb 2005 B1
20050050387 Mariani et al. Mar 2005 A1
20100138693 Ohkawa Jun 2010 A1
20160378103 Malinowski Dec 2016 A1
Foreign Referenced Citations (7)
Number Date Country
2000-040069 Feb 2000 JP
2006-260568 Sep 2006 JP
2007-154050 Jun 2007 JP
2008-123031 May 2008 JP
2010-170355 Aug 2010 JP
2012-074057 Apr 2012 JP
2014-191389 Oct 2014 JP
Non-Patent Literature Citations (3)
Entry
International Search Report for WO 2016/117402 A1, dated Apr. 26, 2016.
Extended European Search Report dated Aug. 23, 2018 for the European Patent Application No. 16740009.2.
Communication Pursuant to Article 94(3) EPC dated Jun. 14, 2019 for European Patent Application No. 16740009.2.
Related Publications (1)
Number Date Country
20170357560 A1 Dec 2017 US