Vehicle control device

The vehicle control device with a multi-core CPU and shared data memory ensures continuous communication by allowing parallel processing of communication parameters, addressing communication interruptions during reset release.

JP7588213B2Active Publication Date: 2024-11-21ASTEMO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2023508440
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-03-22
Filing Date
2021-09-27
Publication Date
2024-11-21
Estimated Expiration
2041-09-27

AI Technical Summary

Technical Problem

Existing vehicle control devices with multi-core CPUs face communication interruptions during reset release to OS initialization, leading to communication breakdown and abnormality detection by other ECUs.

Method used

A vehicle control device with a multi-core CPU, shared data memory, and a monitoring circuit that allows a second core to access and check communication parameters during OS initialization, enabling parallel communication without waiting for completion.

Benefits of technology

Prevents communication interruptions and abnormality detection by maintaining continuous communication from reset release to OS initialization completion.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007588213000001
    Figure 0007588213000001
  • Figure 0007588213000002
    Figure 0007588213000002
  • Figure 0007588213000003
    Figure 0007588213000003
Patent Text Reader

Abstract

A vehicle control device 10 comprising a multicore CPU 11 having at least a first core 111-1 and a second core 111-2, a shared data memory 115 configured to be accessible by each core and storing at least a communication parameter, and a monitoring IC 12 that monitors operation of the multicore CPU 11 and outputs a reset signal to the multicore CPU 11. The second core 111-2 accesses the shared data memory 115 to check the communication parameter and communicates with the outside on the basis of the communication parameter stored in the shared data memory 115 within a period from cancellation of resetting until completion of OS initialization by the first core 111-1.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a vehicle control device, and more particularly to a vehicle control device equipped with a multi-core CPU. This application claims priority based on Japanese Patent Application No. 2021-046953, filed on March 22, 2021, the contents of which are incorporated herein by reference. [Background technology]

[0002] In recent years, vehicles such as automobiles are equipped with a plurality of ECUs (Electronic Control Units, i.e., vehicle control devices) for engine control, brake control, transmission control, door control, air conditioning control, etc. These ECUs communicate with each other and cooperate with each other via an in-vehicle network to ensure safe driving of the vehicle.

[0003] An ECU may have a multi-core CPU with multiple cores. In a multi-core CPU, if an abnormality occurs in any of the cores, the entire multi-core CPU is generally reset to recover from the abnormal state. However, when the entire multi-core CPU is reset, there is a problem that communication is interrupted between the release of the reset and the completion of OS initialization. In addition, the interruption of communication may cause other ECUs to determine that there is an abnormality.

[0004] In order to solve such problems, a technique is being considered that shortens the time from release of reset to completion of OS initialization by using a field programmable gate array (FPGA), as described in, for example, Patent Document 1 below. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2013-246495 A Summary of the Invention [Problem to be solved by the invention]

[0006] However, although the technology described in Patent Document 1 can shorten the time from release of reset to completion of OS initialization, there is still room for improvement.

[0007] The present invention has been made to solve such technical problems, and has an object to provide a vehicle control device that can prevent communication interruption from occurring between reset release and completion of OS initialization. [Means for solving the problem]

[0008] The vehicle control device of the present invention comprises a multi-core CPU having at least a first core and a second core, a shared data memory configured to be accessible by each core and storing at least communication parameters, and a monitoring circuit that monitors the operation of the multi-core CPU and outputs a reset signal to the multi-core CPU, wherein the second core accesses the shared data memory to check the communication parameters between the time when the reset is released and the time when OS initialization is completed by the first core, and communicates with the outside based on the communication parameters stored in the shared data memory.

[0009] In the vehicle control device according to the present invention, the second core accesses the shared data memory to check the communication parameters and communicates with the outside based on the communication parameters stored in the shared data memory during the period from reset release to completion of OS initialization by the first core, so that communication is possible without waiting for completion of OS initialization. As a result, communication interruption during the period from reset release to completion of OS initialization can be prevented. Effect of the Invention

[0010] According to the present invention, it is possible to prevent communication from being interrupted during the period from release of reset to completion of OS initialization. [Brief description of the drawings]

[0011] [Figure 1] 1 is a configuration diagram showing a vehicle control system including a vehicle control device according to a first embodiment. [Diagram 2] FIG. 4 is a sequence diagram showing control after reset release of the vehicle control device according to the first embodiment. [Diagram 3] FIG. 11 is a sequence diagram showing control before and after a reset of the vehicle control device according to the second embodiment. [Figure 4] FIG. 11 is a sequence diagram showing control before and after a reset of the vehicle control device according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an embodiment of a vehicle control device according to the present invention will be described with reference to the drawings.

[0013] [First embodiment] 1 is a configuration diagram showing a vehicle control system including a vehicle control device according to a first embodiment. A vehicle control device 10 of this embodiment is configured by an ECU, and forms a vehicle control system together with a plurality of other ECUs (ECU 20, ECU 30). Here, for example, the vehicle control device 10 is responsible for engine control, the ECU 20 is responsible for brake control, and the ECU 30 is responsible for transmission control. The vehicle control device 10, ECU 20, and ECU 30 are connected by an in-vehicle network 15 such as a CAN (Controller Area Network), and communicate and cooperate via the in-vehicle network 15 to realize safe vehicle driving, etc.

[0014] As shown in FIG. 1, the vehicle control device 10 mainly includes a multi-core CPU 11 and a monitoring IC (Integrated Circuit) 12 that monitors the operation of the multi-core CPU 11.

[0015] The multi-core CPU 11 has a plurality of cores (first core 111-1, second core 111-2, ... n-th core 111-n), and program memories (program memory 112-1, program memory 112-2, ... program memory 112-n) and data memories (data memory 113-1, data memory 113-2, ... data memory 113-n) that are provided in a one-to-one correspondence with the plurality of cores. Each program memory and data memory stores a program and data for performing the function of the corresponding core. Here, n is a natural number of 2 or more.

[0016] In this embodiment, the program memory 112-1 corresponding to the first core 111-1 stores an initialization program for initializing an OS (Operating System) to be executed after reset release, and application software (hereinafter simply referred to as "application") for performing processing assigned to the first core 111-1. The program memory 112-2 corresponding to the second core 111-2 stores a communication program for communication processing to be executed after reset release, and an application for performing processing assigned to the second core 111-2.

[0017] The monitoring IC 12 corresponds to a "monitoring unit" as recited in the claims, and monitors whether the multi-core CPU 11 is operating normally based on a signal 13 output from the multi-core CPU 11. If the signal 13 is interrupted, the monitoring IC 12 determines that an abnormality has occurred in the multi-core CPU 11 and outputs a reset signal 14 to the multi-core CPU 11 to reset the multi-core CPU 11. Furthermore, immediately after power-on (in other words, power ON), the power supply voltage is low, so the monitoring IC 12 outputs the reset signal 14 to the multi-core CPU 11 to reset the multi-core CPU 11. After the power supply voltage has stabilized, the monitoring IC 12 stops outputting the reset signal 14. This releases the reset of the multi-core CPU 11, and the multi-core CPU 11 starts operating.

[0018] The multi-core CPU 11 further includes a shared data memory 115 that each core can access, and a communication device 114 connected to each core. Each core is connected to the communication device 114 and the shared data memory 115 via a bus 116. The shared data memory 115 stores data such as communication parameters shared between the cores. Examples of the communication parameters include a communication speed, a data size, and a transmission cycle.

[0019] The multi-core CPU 11 may be configured with one IC or multiple ICs. Also, the monitoring IC 12 does not necessarily need to be provided separately from the multi-core CPU 11, and a monitoring function equivalent to the monitoring IC 12 may be incorporated into the multi-core CPU 11.

[0020] The vehicle control device 10 configured in this manner is equipped with an OS, and programs related to each control process run under the management of the OS. If the multi-core CPU 11 is reset due to an abnormality or other reason, the OS performs initialization processing after the reset is released. In the OS initialization processing, the OS initializes devices and applications, and further executes the applications.

[0021] In the multi-core CPU 11 having multiple cores, the initialization is performed by one core in order to maintain the consistency of the initialization. As described above, the program memory 112-1 corresponding to the first core 111-1 stores the initialization program for the OS to be executed after the reset is released, and therefore the first core 111-1 performs the OS initialization process after the reset is released.

[0022] Meanwhile, since the program memory 112-2 corresponding to the second core 111-2 stores a communication program related to the communication processing to be executed after the reset is released, the second core 111-2 performs the communication processing after the reset is released. At that time, the second core 111-2 accesses the shared data memory 115 and checks the communication parameters by the communication program to be executed after the reset is released, and further communicates with the outside based on the communication parameters stored in the shared data memory 115. The communication processing of the second core 111-2 is executed in parallel with the OS initialization processing by the first core 111-1.

[0023] Then, when the OS initialization process by the first core 111-1 is completed and an application in the first core 111-1 is started, communication is switched. That is, the communication program of the second core 111-2 is stopped, and the communication process led by the first core 111-1 is started.

[0024] Hereinafter, control after reset release in the vehicle control device 10 will be described with reference to Fig. 2. Here, an example of a series of processes from reset release by powering on to OS initialization, communication, and application execution will be described. Note that in Fig. 2, steps S211 to S214 are processes performed by the first core 111-1, and steps S221 to S225 are processes performed by the second core 111-2.

[0025] 2, after the reset is released by turning on the power, the first core 111-1 first starts the OS (step S211), and then performs an initialization process for the OS (step S212). At this time, the second core 111-2 performs each process in parallel with the process of the first core 111-1.

[0026] Specifically, the second core 111-2 first accesses the shared data memory 115 and checks the communication parameters (step S221). The check of the communication parameters in this step is to check whether or not the normal communication parameters are set in the shared data memory 115. Immediately after the power is turned on (in other words, immediately after the reset is released), the values ​​in the shared data memory 115 are indefinite, and therefore normal communication parameters are not set. For this reason, the second core 111-2 performs a process of initializing the communication parameters (step S222). Next, the second core 111-2 starts communication with an external device (e.g., ECU 20 or ECU 30) via the communication device 114 based on the initialized communication parameters (step S223).

[0027] Then, when the first core 111-1 completes the OS initialization process, the first core 111-1 starts an application related to communication and the like (step S213). At this time, the second core 111-2 performs communication switching process (step S224). Specifically, the communication program of the second core 111-2 is stopped, and the communication process led by the first core 111-1 is performed. Next, the first core 111-1 and the second core 111-2 execute their respective applications (steps S214 and S225).

[0028] According to the vehicle control device 10 of this embodiment, the second core 111-2 accesses the shared data memory 115 to check the communication parameters and performs an initialization process of the communication parameters and then communicates with an external device based on the initialized communication parameters during the period from when the reset is released by turning the power on until the OS initialization is completed by the first core 111-1. This enables communication without waiting for the completion of the OS initialization. As a result, it is possible to prevent communication from being interrupted during the period from when the reset is released until the OS initialization is completed. Furthermore, this makes it possible to avoid abnormality determinations from other ECUs due to communication interruptions.

[0029] [Second embodiment] The vehicle control device 10 according to the second embodiment has a similar structure to that of the first embodiment, but differs from the first embodiment in the control content of the vehicle control device 10. Only the differences will be described below.

[0030] Conventionally, separate ECUs were installed to control different functions, such as engine control and motor control. In recent years, ECUs with different functions have been integrated to make devices more compact and reduce costs. In integrated ECUs, there is a demand for one function to continue operating even if an abnormality occurs in the other function.

[0031] When an abnormality occurs, there is a method of initializing the function in which the abnormality occurs by software, but there is also a method of resetting the entire multi-core CPU by hardware to eliminate the abnormality. In this embodiment, a method of resetting the entire multi-core CPU by hardware to eliminate the abnormality is adopted. Then, prior to resetting the entire multi-core CPU 11, the currently used communication parameters are stored in the shared data memory 115, and after the reset is released, communication is performed based on the currently used communication parameters stored above, thereby maintaining the continuity of communication before and after the reset. Note that the abnormality referred to in this embodiment is an abnormality that can be detected via a sensor or the like attached to the vehicle. Therefore, a reset caused by such an abnormality is an intentional reset.

[0032] Hereinafter, the control before and after reset of the vehicle control device according to this embodiment will be described with reference to Fig. 3. In Fig. 3, steps S311 to S315 are processes performed by the first core 111-1, and steps S321 to S325 are processes performed by the second core 111-2.

[0033] 3, when the first core 111-1 detects an abnormality (step S311), it instructs the second core 111-2 to save the communication parameters currently in use. Based on the instruction from the first core 111-1, the second core 111-2 saves the communication parameters currently in use (step S321). At this time, the second core 111-2 stores the communication parameters currently in use in the shared data memory 115, not in the data memory 113-2 corresponding to the second core 111-2. Here, the communication parameters stored in the shared data memory 115 are referred to as communication parameters 331.

[0034] Next, the first core 111-1 transmits an instruction to generate a reset to the monitor IC 12 (step S312), and the multi-core CPU 11 is then reset.

[0035] After the reset is released, the first core 111-1 first starts up the OS (step S313), and then performs an OS initialization process (step S314). At this time, the second core 111-2 performs each process in parallel with the process of the first core 111-1.

[0036] Specifically, the second core 111-2 accesses the shared data memory 115 and checks the communication parameters 331 stored in the shared data memory 115 (step S322). The communication parameters in this step are checked to ensure that they are not indefinite values ​​in the memory immediately after power-on. Next, the second core 111-2 refers to the communication parameters 331 and performs a recovery process for the communication parameters (step S323). Next, the second core 111-2 starts communication with an external device (e.g., ECU 20 or ECU 30) via the communication device 114 based on the restored communication parameters (i.e., communication parameters 331) (step S324).

[0037] Then, when the OS initialization process by the first core 111-1 is completed, as described in the first embodiment, the first core 111-1 starts an application related to communication and the like (step S315), and the second core 111-2 performs a process of switching communication (step S325). After that, each process described in the first embodiment is performed.

[0038] According to the vehicle control device 10 of this embodiment, in addition to obtaining the same effect as the first embodiment described above, the following effect is further obtained. That is, the communication parameters currently in use are stored in the shared data memory 115 before resetting, and the second core 111-2 communicates based on the communication parameters currently in use stored in the shared data memory 115 during the period from reset release to the completion of OS initialization by the first core 111-1, so that the continuity of communication before and after resetting can be maintained. Note that, in the technology described in the above Patent Document 1, only initial communication is performed after resetting is released, so that it is considered that a problem occurs in which the continuity of communication before and after resetting cannot be maintained. According to the vehicle control device 10 of this embodiment, the problem of the technology described in the above Patent Document 1 can be solved.

[0039] In this embodiment, in order to distinguish whether the communication parameters are normal values ​​or indefinite values ​​in memory immediately after the power is turned on, known methods can be used, such as duplicating each piece of data related to the communication parameters or adding a checksum or hash.

[0040] In this embodiment, in addition to the communication parameters, a communication program may be further stored in the shared data memory 115. In this way, complex communication processing can be handled, for example, communication including variable values ​​is also possible. Furthermore, a program that interprets and executes a script may be stored in the shared data memory 115, for example, a communication program written in a script language is stored. In this way, complex communication processing can be handled.

[0041] [Third embodiment] The vehicle control device 10 according to the third embodiment has a similar structure to that of the above-described first embodiment, but differs from the above-described first embodiment in the processing contents of the vehicle control device 10. Only the differences will be described below.

[0042] Fig. 4 is a sequence diagram showing control before and after a reset of the vehicle control device according to the third embodiment. In Fig. 4, steps S411 to S414 are processes performed by the first core 111-1, and steps S421 to S424 are processes performed by the second core 111-2.

[0043] As shown in Fig. 4, the first core 111-1 first performs a process of saving the default values ​​of the communication parameters (step S411). The default values ​​of the communication parameters are communication parameter values ​​used when a reset occurs due to an unexpected abnormality, and are preset. A communication pattern indicating that the reset is due to an unexpected abnormality is built into the default values. The default values ​​are saved in the shared data memory 115 using a method for distinguishing them from the indefinite values ​​of the memory described above. Here, the default values ​​saved in the shared data memory 115 are referred to as communication parameters 431.

[0044] If an unexpected abnormality occurs in the multi-core CPU 11, the monitor IC 12 outputs a reset signal 14 to the multi-core CPU 11. As a result, the multi-core CPU 11 is reset.

[0045] After the reset is released, the first core 111-1 first starts up the OS (step S412), and then performs an OS initialization process (step S413). At this time, the second core 111-2 performs each process in parallel with the process of the first core 111-1.

[0046] Specifically, the second core 111-2 accesses the shared data memory 115, checks the communication parameters 431 stored in the shared data memory 115, checks that the parameters are not undefined values ​​in the memory (step S421), and acquires the communication parameters 431 (step S422). As a result, the default values ​​set in step S411 are acquired.

[0047] Next, the second core 111-2 starts communication with an external device (for example, the ECU 20 or the ECU 30) via the communication device 114 based on the acquired communication parameters 431 (step S423). Since a communication pattern indicating a reset due to an unexpected abnormality is incorporated in the communication parameters 431, the other ECUs (the ECU 20 and the ECU 30) can grasp this through the vehicle control device 10.

[0048] Then, when the OS initialization process by the first core 111-1 is completed, as described in the first embodiment, the first core 111-1 starts an application related to communication and the like (step S414), and the second core 111-2 performs communication switching process (step S424). After that, each process described in the first embodiment is performed.

[0049] In the vehicle control device 10 of this embodiment, the first core 111-1 sets default values ​​of communication parameters in advance and stores them in the shared data memory 115. Then, when a reset occurs due to an unexpected abnormality, the second core 111-2 performs communication based on the default values, thereby enabling communication without waiting for completion of OS initialization. As a result, it is possible to prevent communication from being interrupted between the release of reset and the completion of OS initialization. This also makes it possible to avoid abnormality determination from other ECUs due to communication interruption.

[0050] In this embodiment, the default values ​​of the communication parameters are set by the first core 111-1 in step S411, but it is also possible to set, for example, only a flag, and in step S421, when the flag is detected, send fixed communication parameters to the second core 111-2.

[0051] In the above three embodiments, the reset pattern due to power ON (first embodiment), the intended reset pattern (second embodiment), and the reset pattern due to an unexpected abnormality (third embodiment) have been described. For example, if communication data to another ECU is sent with an identification number or the like that can identify each of the above three patterns, it is possible to clearly inform the other ECU whether the vehicle control device 10 is normal or abnormal.

[0052] Although the embodiments of the present invention have been described in detail above, the present invention is not limited to the above-described embodiments, and various design modifications can be made without departing from the spirit of the present invention as described in the claims. [Explanation of symbols]

[0053] 10 Vehicle control device 11 Multi-core CPU 12 Monitoring IC (monitoring section) 13 Signal 14 Reset Signal 15 In-vehicle network 20,30 ECU 111-1 Core 1 111-2 2nd Core 111-n nth core 112-1, 112-2, … 112-n program memory 113-1, 113-2, … 113-n Data memory 114 Communication Devices 115 Shared Data Memory 116 Bus

Claims

1. a multi-core CPU having at least a first core and a second core; a shared data memory configured to be accessible by each core and storing at least communication parameters; a monitoring unit that monitors an operation of the multi-core CPU and outputs a reset signal to the multi-core CPU; Equipped with A vehicle control device characterized in that the second core accesses the shared data memory to confirm communication parameters between the time when reset is released and the time when OS initialization by the first core is completed, and communicates with the outside based on the communication parameters stored in the shared data memory.

2. The shared data memory stores currently used communication parameters before the reset; The vehicle control device according to claim 1 , wherein the second core communicates with an external device based on currently used communication parameters stored in the shared data memory.

3. 3. The vehicle control device according to claim 1, wherein the shared data memory further stores a program for performing communication.

4. The vehicle control device according to claim 1 or 2, wherein the shared data memory further stores a program for interpreting and executing a script.

5. The shared data memory further stores default values ​​of communication parameters; The vehicle control device according to any one of claims 1 to 4, wherein when the second core is reset due to an unexpected abnormality, the second core communicates with an external device based on the default value.

Citation Information

Patent Citations

  • Multiprocessor system and control method thereof

    JP2008305317A

  • I / O controller and I / O control method

    JP2013054434A

  • Communication device

    JP2013246495A

  • Electronic equipment, reactivation method, and program

    JP2018092571A

  • Fault monitoring method and fault monitoring device

    WO2017022364A1