Vehicle control device, vehicle control method, and recording medium
The vehicle control system ensures reliable program updates by using a protected area for critical startup programs and a dual storage system, allowing the vehicle to start even if updates fail, with notifications for corrective action.
Patent Information
- Application Number
- JP2022137520
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2022-02-15
- Filing Date
- 2022-08-31
- Publication Date
- 2024-11-28
- Estimated Expiration
- 2042-08-31
AI Technical Summary
Existing vehicle control software is vulnerable to compromise during program updates, which can significantly affect vehicle operation, necessitating reliable methods to ensure the integrity of program updates.
A vehicle control system with a restricted rewrite area for critical startup programs and a dual storage system for program updates, including a rewrite-protected area and a rewritable area, ensures that if an update fails, the vehicle can still be started using the protected program, with notifications and signals for corrective action.
Ensures reliable vehicle operation by maintaining a protected version of the startup program, allowing the vehicle to start even if updates fail, and provides notifications for corrective action, thereby enhancing the reliability of program updates.
Smart Images

Figure 0007591538000001 
Figure 0007591538000002 
Figure 0007591538000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a vehicle control device, a vehicle control method, and a recording medium. [Background technology]
[0002] In recent years, the functions of software that controls vehicles have been enhanced with the aim of improving traffic safety and reducing CO2 emissions. A technology for updating a program executed by an ECU (Electronic Control Unit) mounted on a vehicle has been proposed. For example, Patent Document 1 discloses a configuration in which a storage unit that stores a program includes a vehicle control program storage area that stores a control program, and a second program storage area that stores an update program that is an update version of the control program. With this configuration, it is possible to store the update program in the storage unit even while the control program is being executed, and it is said that this reduces constraints on the timing of program updates. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2019-144669 A Summary of the Invention [Problem to be solved by the invention]
[0004] The software that controls a vehicle includes programs that are important for the vehicle's basic operations. If such programs are damaged, it can have a significant impact on the operation of the vehicle. For this reason, it is necessary to ensure the reliability of the program update process. The present invention has been made in view of the above background, and has an object to ensure reliability regarding updates to programs that control a vehicle. [Means for solving the problem]
[0005] One aspect for achieving the above object includes a vehicle control unit that controls a vehicle by executing a vehicle startup program for starting the vehicle, a storage unit having a rewrite restricted area in which the vehicle startup program is stored and rewrite restricted, and a rewriteable area in which the vehicle startup program is stored in a rewritable manner, a communication unit that communicates with an external device, and a program update unit that executes an update process to store a vehicle startup update program received by the communication unit and used to update the vehicle startup program in the rewritable area; a notification unit that notifies that the update process has not been completed normally, The vehicle control unit executes the vehicle startup program stored in the rewritable area, and when the update process by the program update unit is not normally completed, executes the vehicle startup program stored in the rewritable area. the storage unit includes, in the rewritable area, a first storage area for storing the vehicle startup program and the vehicle startup update program, and a second storage area for storing the vehicle startup program and the vehicle startup update program; the program update unit executes the update process to store the vehicle startup update program in at least one of the first storage area or the second storage area, and when the update process to store the vehicle startup update program in the second storage area is not completed normally, stores, in the first storage area, abnormality occurrence information indicating that the update process was not completed normally; and the vehicle control unit issues a first abnormality occurrence notification by the notification unit when executing the vehicle startup program stored in the first storage area based on the abnormality occurrence information. A vehicle control device. Effect of the Invention
[0006] According to the above configuration, even if a problem occurs in updating the program for starting the vehicle, the vehicle can be started using the program stored in the area where rewriting is restricted, thereby ensuring reliability regarding updates to the program that controls the vehicle. [Brief description of the drawings]
[0007] [Figure 1] FIG. 1 is a schematic diagram of a vehicle control system. [Diagram 2] FIG. 1 is a diagram showing a schematic configuration of a program management system. [Diagram 3] FIG. 2 is a block diagram showing the configuration of a main part of a control system according to the first embodiment. [Figure 4] FIG. 2 is a schematic diagram showing an example of the configuration of a storage unit in the first embodiment. [Diagram 5] 4 is a flowchart showing the operation of the control system in the first embodiment. [Figure 6] 4 is a flowchart showing the operation of the control system in the first embodiment. [Figure 7]FIG. 11 is a schematic diagram showing an example of the configuration of a storage unit in a second embodiment. [Figure 8] 10 is a flowchart showing the operation of a control system in a second embodiment. [Figure 9] 10 is a flowchart showing the operation of a control system in a second embodiment. [Figure 10] 10 is a flowchart showing the operation of a control system in a second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0008] FIG. 1 is a diagram showing a control system 1 for a vehicle. The control system 1 includes a central ECU 2 that performs overall control and information processing of the vehicle. Hereinafter, the vehicle in which the control system 1 is mounted is referred to as the vehicle itself. Specifically, the vehicle itself is a vehicle V, which will be described later. The central ECU 2 is connected to communication lines including communication lines 4a, 4b, and 4c. The central ECU 2 realizes a gateway function that manages the transmission and reception of communication data between these communication lines. In addition, a TCU (Telematics Control Unit) 12, which is a wireless device that complies with the communication standard of a mobile communication system, is connected to the central ECU 2. The central ECU 2 executes OTA (Over The Air) management using the TCU 12. The OTA management includes control related to a process of downloading an update program for an in-vehicle device provided in the vehicle from a server outside the vehicle and a process of applying the downloaded update program to the in-vehicle device. In addition, a DLC (Data Link Connector) 19 is connected to the central ECU 2. A diagnostic device, which will be described later, can be connected to the DLC 19.
[0009] The first zone ECU 20a, the second zone ECU 20b, and the third zone ECU 20c are connected to the communication lines 4a, 4b, and 4c, respectively. There is no limit to the number or type of ECUs connected to the first zone ECU 20a, the second zone ECU 20b, and the third zone ECU 20c, and this embodiment shows one configuration example. In this example, the first zone ECU 20a is connected to ECUs 30a, 30b, and 30c. The second zone ECU 20b is connected to ECUs 30d, 30e, 30f, 30g, 30h, 30i, 30j, and 30k. The third zone ECU 20c is connected to ECUs 30l, 30m, and 30n.
[0010] Hereinafter, the first zone ECU 20a, the second zone ECU 20b, and the third zone ECU 20c will be collectively referred to as zone ECUs 20, and the ECUs 30a to 30n will be collectively referred to as ECUs 30.
[0011] The ECU 30 may include, for example, an MPU (Map Positioning Unit), an MVC-ECU (MVC; Multi View Camera), a PKS-ECU (PKS; Parking Support), and / or an ADAS-ECU (ADAS; Advanced Driver-Assistance System), as well as other ECUs that control the operation of various devices and sensors included in the vehicle. Such devices and sensors include a driving motor that drives the vehicle, a steering device such as an accelerator and a brake, a VSA device (VSA; Vehicle Stability Assurance), and the like. s ist), a battery, lighting bodies such as headlamps, a window motor that drives a door window, an actuator that drives a door lock mechanism, a door lock sensor, a door opening / closing sensor, a temperature sensor, an exterior camera, an interior camera, etc.
[0012] Each zone ECU 20 is connected to a plurality of ECUs 30 arranged in the same section of the vehicle body space of the host vehicle, or a plurality of ECUs 30 that control the operation of devices and sensors arranged in the same section.
[0013] In addition to the zone ECU 20, other control devices and devices may be connected to the central ECU 2. Such control devices and devices may include an infotainment control box (ICB), a speaker, a microphone, a meter panel, a steering switch, a Global Navigation Satellite System (GNSS) sensor, a touch panel, and the like.
[0014] In this embodiment, the communication lines 4a, 4b, and 4c are configured by, for example, a CAN bus that performs communication in compliance with the CAN communication standard. Hereinafter, the communication lines 4a, 4b, and 4c are collectively referred to as the communication lines 4. Hereinafter, the communication lines 4 correspond to the in-vehicle network in the present disclosure. In addition, the zone ECUs 20 connected to the communication lines 4 correspond to the multiple electronic control devices in the present disclosure.
[0015] The zone ECUs 20 connected to the communication line 4 transmit data to be transmitted in one frame or as a sequence of frames according to the CAN communication standard, according to the prior art. According to the CAN communication standard, each transmitted frame contains an identification code (ID), and each zone ECU 20 that receives a frame determines whether the frame was addressed to itself or not, based on the ID contained in the frame.
[0016] FIG. 2 is a diagram showing a schematic configuration of the program management system 100. As shown in FIG. The program management system 100 is a system that enables updating of programs executed by various ECUs that constitute the control system 1. The program management system 100 includes a server 110 and a vehicle diagnosis device 120.
[0017] The server 110 is connected to the control system 1 via a communication network N. The communication network N includes, for example, a cellular communication network, a Wi-Fi (registered trademark) network, Bluetooth (registered trademark), the Internet, a Wide Area Network (WAN), a Local Area Network (LAN), a public line, a provider device, a dedicated line, a base station, etc., and a base station B is illustrated in Fig. 2. The TCU 12 included in the control system 1 executes cellular communication with the base station B, thereby executing data communication with an external device through the communication network N.
[0018] The control system 1 can download update data for updating programs executed by various ECUs of the control system 1 from the server 110 by communicating with the server 110 via the TCU 12. The means by which the control system 1 downloads update data from the server 110 and updates the programs corresponds to the above-mentioned OTA. The server 110 corresponds to an example of an external device of the control system 1. The TCU 12 corresponds to an example of a communication unit.
[0019] The vehicle diagnosis device 120 is a device installed in a dealer or a repair shop that handles the vehicle V on which the control system 1 is mounted. The vehicle diagnosis device 120 is connected by a cable to the DLC 19 of the control system 1. The control system 1 can perform updates of the programs executed by the control system 1 by communicating with the vehicle diagnosis device 120. The vehicle diagnosis device 120 can be an example of an external device, and the DLC 19 can be an example of a communication unit.
[0020] Here, updating an ECU program refers to rewriting a program executed by an ECU with a different version of the program. Updating an ECU program may include rewriting data referenced when an ECU executes a program and / or data generated or changed by execution of the program together with the program. Updating an ECU program may include rewriting a program executed by an ECU with the same version of the program.
[0021] [First embodiment] First, a first embodiment of the present disclosure will be described. Fig. 3 is a block diagram showing the main configuration of the control system 1 in the first embodiment. Fig. 3 shows a part of the configuration related to program updates in the control system 1, and does not prevent the control system 1 from being provided with configurations not shown in Fig. 3.
[0022] In the control system 1, each of the ECUs including the central ECU 2, the zone ECU 20, and the ECU 30 includes a processor and a storage unit. Un The ECU is composed of an ECU (Electronic Control Unit), an MCU (Micro Controller Unit), and an MPU (Micro Processor Unit). The storage unit stores in a non-volatile manner the programs executed by the processor and the data processed by the processor. The storage unit is, for example, a ROM (Read Only Memory). The ECU may also be equipped with a RAM (Random Access Memory) that forms a work area for temporarily storing programs and data. The ECU may be composed of an integrated circuit that integrally comprises a processor, ROM, and RAM. The ECU may also be configured to comprise each of the processor, ROM, and RAM as independent hardware.
[0023] The central ECU 2 includes an update control unit 201 as a functional unit related to updating a program. The update control unit 201 may be hardware included in the central ECU 2. Alternatively, the update control unit 201 may be a functional unit realized by cooperation between software and hardware as a result of a processor of the central ECU 2 executing a program.
[0024] The update control unit 201 includes an update data receiving unit 202 and an update data control unit 203. The update data receiving unit 202 controls the TCU 12 to receive update data for updating a program from the server 110. The update data control unit 203 uses the update data received by the update data receiving unit 202 to control a process in which various ECUs including the central ECU 2 update programs.
[0025] 3 illustrates the second zone ECU 20b as an object of control by the update control unit 201, but this is just one example. There is no limit to the number of ECUs that are objects of control by the update control unit 201. The update control unit 201 controls the update of programs executed by at least some of the ECUs included in the control system 1. The update control unit 201 may control the update of programs by all ECUs included in the control system 1 or almost all ECUs.
[0026] As an example of an ECU that updates a program under the control of the update control unit 201, the second zone ECU 20b will be described in this embodiment. The second zone ECU 20b includes a program execution unit 51, an update execution unit 52, and a memory unit 53. The memory unit 53 corresponds to the memory unit described above. The program execution unit 51 executes the program stored in the memory unit 53. It can also be said that the program execution unit 51 represents the function of the processor itself provided in the second zone ECU 20b. The program execution unit 51 corresponds to an example of a vehicle control unit. Furthermore, the control system 1 corresponds to an example of a vehicle control device. The memory unit 53 stores the program executed by the program execution unit 51 and data related to this program. The update execution unit 52 updates the program stored in the memory unit 53. The update execution unit 52 corresponds to an example of a program update unit.
[0027] In the vehicle V, the control targets of the second zone ECU 20b are the ECUs 30d to 30k shown in Fig. 1. The ECUs 30d to 30k include, for example, ECUs that control the lamps, window motors, door sensors, door lock mechanisms, and ESLs of the vehicle V. The ECUs 30d to 30k include, for example, ECUs that control the wiper motors, window washer motors, and power supply relays 41. In this embodiment, the ECU 30k will be described as an ECU that controls the power supply relay 41.
[0028] The wiper motor is a motor that operates the wipers of the vehicle V. The window washer motor is a motor that drives the window washer pump. The window washer pump is driven by the window washer motor and sprays window washer fluid onto the front window of the vehicle V.
[0029] The power supply relay 41 is a switching circuit for switching the state of power supply from a battery mounted on the vehicle V. The ECU 30k controls the power supply relay 41 based on a signal output by the second zone ECU 20b to switch between a power-on state in which power from the battery is supplied to each component of the control system 1 and a power-off state in which power supply to at least a part of the control system 1 is stopped. The power supply relay 41 is, for example, a contact relay. The power supply relay 41 may be an element called a solid-state relay or a semiconductor relay, or another switching element.
[0030] Here, the power-on state refers to a state in which the vehicle V can run by operating the drive device of the vehicle V. The drive device is, for example, a motor or an internal combustion engine that drives the vehicle. For example, the power-on state includes a state in which the vehicle V is running, a state in which the vehicle V is stopped and the drive device is operating, and a state in which the drive device can be operated. In contrast, the power-off state refers to a state in which at least the drive device of the vehicle V is stopped and a startup process is required to operate the drive device. In the power-off state, components other than the drive device may be stopped in the control system 1.
[0031] For example, if the drive device includes an internal combustion engine, the power-off state includes a state in which the internal combustion engine stops operating and a starter motor or the like that starts the internal combustion engine does not operate. Also, for example, if the drive device includes a motor, the power-off state includes a state in which power supply to the motor stops and control of the drive state of the motor stops. In the power-off state, multiple ECUs including the central ECU 2 and the second zone ECU 20b may be operating.
[0032] The operation of the control system 1 to transition from a power-off state to a power-on state is referred to as “start-up” here. In order to start the vehicle V, the second zone ECU 20b needs to control the ECU 30k to cause the power relay 41 to perform switching.
[0033] FIG. 4 is a schematic diagram showing an example of the configuration of the storage unit 53. As shown in FIG. The storage unit 53 has a non-volatile storage area. The storage unit 53 stores programs and data in a rewritable storage area. The storage unit 53 is configured, for example, by a semiconductor storage device or a magnetic recording device. As a specific example, the storage unit 53 is configured by a flash ROM or an EEPROM (Electrically Erasable Programmable ROM). In the following description, the programs and data stored in the storage unit 53 are referred to as programs. That is, the programs referred to in the following description include data that is referenced, generated, or processed when the processor executes the programs. These programs and data as a whole can be referred to as software. That is, the program management system 100 has a function of managing and updating the software of the control system 1 mounted on the vehicle V.
[0034] The storage area of the storage unit 53 is logically divided into a plurality of areas. That is, the storage unit 53 is provided with a boot area 61 and a program storage area 62. The boot area 61 and the program storage area 62 both store programs. The boot area 61 is an area in which rewriting by the update execution unit 52 is restricted or prohibited. The boot area 61 corresponds to an example of a rewrite-restricted area. Therefore, the update execution unit 52 does not perform a process of updating the program stored in the boot area 61. In contrast, the program storage area 62 is an area that can be rewritten by the update execution unit 52. The program storage area 62 corresponds to an example of a rewriteable area. The update execution unit 52 can execute a process of storing a new program in the program storage area 62 and a process of updating the program stored in the program storage area 62. In addition, the boot area 61 does not need to be completely prohibited from being rewritten, and may be an area that is set so that the update execution unit 52 does not target the process of rewriting programs and data. For example, rewriting of the boot area 61 under the control of the central ECU 2 or the vehicle diagnostic device 120 connected via the DLC 19 is not prevented.
[0035] The restriction on writing to the boot area 61 may be a restriction based on hardware or software. For example, when the boot area 61 and the program storage area 62 are provided in a storage area of the same semiconductor storage device, the restriction on the boot area 61 is realized by the specifications of the update execution unit 52 or software. Also, for example, when the boot area 61 and the program storage area 62 are storage areas of different semiconductor storage devices, the restriction on the boot area 61 may be realized by hardware.
[0036] The boot area 61 stores a boot loader 71. The boot loader 71 is a program that is executed first by the program execution unit 51 when the second zone ECU 20b starts the vehicle V. The program execution unit 51 executes the boot loader 71 to perform initialization and the like required for the processing of the program execution unit 51. Furthermore, the program execution unit 51 reads out and executes a vehicle startup program 73 stored in the program storage area 62 by the function of the boot loader 71.
[0037] The program storage area 62 stores a program executed by the program execution unit 51. The program storage area 62 stores a vehicle startup program 73. The vehicle startup program 73 includes a program for starting the vehicle V by the second zone ECU 20b controlling the ECU 30k to operate the power supply relay 41. The vehicle startup program 73 may also include a function for controlling an engine starter (not shown), etc.
[0038] The vehicle startup program 73 includes one or more programs for executing basic operations of the vehicle V. That is, the vehicle startup program 73 includes functions essential for starting, running, and stopping the vehicle V. For example, the vehicle startup program 73 includes functions related to the control of the door lock mechanism and the ESL. The functions of the vehicle startup program 73 include controls that are required by law or regulation to be executed while the vehicle V is traveling. For example, the vehicle startup program 73 includes a function related to control of the illumination of the lamps of the vehicle V, a function related to control of the wiper motor, and a function related to control of the windshield washer motor.
[0039] The function of the vehicle startup program 73 may include a function required for updating a program in the control system 1. For example, the vehicle startup program 73 may include a function required for updating a program in the control system 1. of and a function for communicating with the vehicle diagnosis device 120 via the DLC 19.
[0040] Furthermore, the vehicle startup program 73 may include a program related to a function that is not essential for driving the vehicle V. For example, the vehicle startup program 73 may include a function related to accessibility that enhances user convenience and a function related to infotainment that enhances user entertainment. Specifically, the function of the vehicle startup program 73 may include a function for opening and closing a door hands-free, a function for lighting the interior space of the vehicle V, and the like.
[0041] The boot area 61 stores a vehicle startup program 72 in addition to the boot loader 71. The vehicle startup program 72 is executed by the program execution unit 51 in the same manner as the vehicle startup program 73, and is a program for the program execution unit 51 to control each part. The vehicle startup program 72 includes one or more programs for executing basic operations of the vehicle V in the same manner as the vehicle startup program 73. Specifically, the vehicle startup program 72 includes functions essential for starting, running, and stopping the vehicle V, and controls required to be executed while the vehicle V is running by laws and regulations, etc. Therefore, by the program execution unit 51 executing the vehicle startup program 72, it is possible to at least start the vehicle V and run the vehicle V.
[0042] The vehicle startup program 72 may be a program that does not include an accessibility-related function that enhances user convenience or an infotainment-related function that enhances user entertainment, among the functions realized by the vehicle startup program 73. In this case, the storage capacity for storing the vehicle startup program 72 is smaller than that of the vehicle startup program 73, so that the storage capacity of the boot area 61 can be reduced.
[0043] The vehicle startup program 73 stored in the program storage area 62 can be updated by the function of the update execution unit 52. In contrast, the vehicle startup program 72 stored in the boot area 61 is not updated by the update execution unit 52. For example, the vehicle startup program 72 remains unchanged in the state stored in the boot area 61 when the vehicle V is shipped from the factory. Therefore, the vehicle startup program 72 is in a protected state regardless of the operation of the update execution unit 52. Even if some kind of problem occurs in the update process in which the update execution unit 52 updates the vehicle startup program 73, the control system 1 can start up the vehicle V and run the vehicle V by executing the vehicle startup program 72 with the program execution unit 51.
[0044] Figures 5 and 6 are flowcharts showing the operation of the control system 1. Figure 5 shows a process for updating the vehicle startup program 73 stored in the program storage area 62. Steps S14 to S16 in Figure 5 correspond to an example of the update process.
[0045] The update data receiving unit 202 transmits a request to the server 110 by the TCU 12 (step S11). The request in step S11 is a request for an update program for updating a program stored in the ECU, for example, a request for transmitting a vehicle control update program for updating the vehicle startup program 73.
[0046] The update data receiving unit 202 downloads from the server 110 the program transmitted by the server 110 in response to the request in step S11, and temporarily stores the program in a storage area (not shown) (step S12). Here, the update data control unit 203 waits for the power of the vehicle V to be switched off in order to start the update process. That is, the update data control unit 203 determines whether or not the vehicle V has been switched to a power-off state (step S13). While the vehicle V has not been switched to a power-off state (step S13; NO), the update data control unit 203 waits in step S13.
[0047] When it is determined that the vehicle V has been switched to the power-off state (step S13; YES), the update execution unit 52 starts the update process according to the control of the update data control unit 203 (step S14).
[0048] In the update process, the update execution unit 52 stores the vehicle control update program downloaded in step S12 in the program storage area 62 (step S15). The update execution unit 52 uses the vehicle control update program stored in the program storage area 62 to execute installation of the vehicle startup program 73 stored in the program storage area 62 (step S16). The process of step S16 corresponds to a process of updating the vehicle startup program 73 to a new version of the vehicle startup program 73.
[0049] The update execution unit 52 performs a process of confirming that the installation has been completed normally (step S17). In step S17, the update execution unit 52 confirms that the installed program is in a state in which it can be executed normally by the program execution unit 51. For example, the update execution unit 52 calculates a hash value of the updated vehicle startup program 73, The calculated hash value is The normality of the updated vehicle startup program 73 is confirmed by comparing the calculated vehicle control update program with the hash value downloaded from the server 110 .
[0050] The update execution unit 52 determines whether the installation of the vehicle startup program 73 has been completed normally based on the result of the process in step S17 (step S18). If the installation has been completed normally (step S18; YES), the update execution unit 52 executes activation of the installed program (step S19) and ends this process. The activation includes settings related to the execution of the updated program.
[0051] When it is determined that the installation of the vehicle startup program 73 has not been completed normally (step S18; NO), the update execution unit 52 writes the abnormality occurrence information 74 in the program storage area 62 (step S20).
[0052] The abnormality occurrence information 74 is information indicating that the update process of the vehicle startup program 73 has not been completed normally. The abnormality occurrence information 74 may be, for example, a flag. In this case, the update execution unit 52 writing the abnormality occurrence information 74 in step S20 corresponds to rewriting the flag of the abnormality occurrence information 74 to on. If the abnormality occurrence information 74 is stored in the program storage area 62, the program execution unit 51 does not execute the vehicle startup program 73 at startup. This makes it possible to prevent the vehicle startup program 73, which may not operate normally, from being executed.
[0053] FIG. 6 shows the operation related to the start-up of the second zone ECU 20b. The program execution unit 51 reads and executes the boot loader 71 stored in the boot area 61 (step S31). Then, the program execution unit 51 refers to the program storage area 62 (step S32) and determines whether or not the abnormality occurrence information 74 is stored (step S33). If the abnormality occurrence information 74 is not stored (step S33; NO), the program execution unit 51 executes the vehicle startup program 73 stored in the program storage area 62 (step S34). By executing the vehicle startup program 73, the program execution unit 51 causes the ECU 30k to switch the power supply relay 41 to start the vehicle V (step S35). This allows the control system 1 to be in a state capable of controlling functions required for the running of the vehicle V, and the vehicle V transitions to a power-on state.
[0054] When the abnormality occurrence information 74 is stored in the program storage area 62 (step S33; YES), the program execution unit 51 executes the vehicle startup program 72 stored in the boot area 61 (step S36). By executing the vehicle startup program 72, the program execution unit 51 causes the ECU 30k to switch the power supply relay 41, thereby starting up the vehicle V (step S37).
[0055] In this case, the update control unit 201 or the program execution unit 51 issues an abnormality occurrence notification (step S38). The abnormality occurrence notification is a notification indicating that the update process of the vehicle startup program 73 has not been completed normally.
[0056] The abnormality occurrence notification is sent to, for example, a user in the driver's seat or another seat of the vehicle V. The content of the abnormality occurrence notification may, for example, request re-execution of the update of the vehicle startup program 73, or guide the vehicle startup program 73 to be updated using the vehicle diagnosis device 120 at a dealer or repair shop of the vehicle V. In step S38, the notification is executed, for example, by displaying characters or images on a touch panel mounted on the vehicle V, or by outputting sound from a speaker mounted on the vehicle V.
[0057] After issuing the abnormality occurrence notification, the update control unit 201 or the program execution unit 51 transmits an abnormality occurrence signal to an external device (step S39). The abnormality occurrence signal is a signal indicating that the update process of the vehicle startup program 73 has not been completed normally. The abnormality occurrence notification is transmitted to the server 110 by the TCU 12, for example, or transmitted to the vehicle diagnosis device 120 via the DLC 19. Also, in step S39, the abnormality occurrence notification may be configured to be transmitted to a smartphone or a personal computer registered in advance in the control system 1.
[0058] By transmitting an abnormality signal from the control system 1 to the server 110 or other devices, it becomes possible, for example, for a dealer or repair shop of the vehicle V to provide assistance to a user driving the vehicle V with regard to repairing or redoing the update of the vehicle startup program 73.
[0059] [Second embodiment] Next, a second embodiment of the present disclosure will be described. Fig. 7 is a schematic diagram showing a configuration example of a storage unit 53A in the second embodiment. The storage unit 53A is provided in the second zone ECU 20b instead of the storage unit 53 shown in Figs. 3 and 4. The configuration and functions of the control system 1 in the second embodiment are common to those of the first embodiment, except for the difference between the storage unit 53 and the storage unit 53A and the difference in operation related thereto. In the following description, the configuration described in the first embodiment will be omitted from illustration and description by assigning the same reference numerals as in the first embodiment.
[0060] The storage unit 53A has a non-volatile storage area. The storage unit 53A stores programs and data in a rewritable storage area. Like the storage unit 53, the storage unit 53A is configured with a semiconductor storage device or a magnetic recording device, and specifically, is configured with a flash ROM or an EEPROM.
[0061] The memory area of the memory unit 53A is logically divided into a plurality of areas. That is, the memory unit 53A is provided with a boot area 61A, an A-side boot image memory area 65, a B-side boot image memory area 66, a first program memory area 67, and a second program memory area 68. Each of these areas stores a program.
[0062] The boot area 61A stores a master boot record 81 and a vehicle startup program 82. The boot area 61A is configured similarly to the boot area 61, except that the programs stored in the boot area 61A are different from those in the boot area 61.
[0063] The master boot record 81 is a program that is executed first by the program execution unit 51 when the second zone ECU 20b starts the vehicle V. The program execution unit 51 refers to the master boot record 81, which includes a program equivalent to the boot loader 71 and data specifying a program that the program execution unit 51 should execute following this program. The program execution unit 51 executes the program included in the master boot record 81 to perform initialization and the like required for the processing of the program execution unit 51. Furthermore, the program execution unit 51 reads and executes the boot program 83 or the boot program 84 using the function of the boot loader 71.
[0064] The A side boot image storage area 65 stores a boot program 83. The B side boot image storage area 66 stores a boot program 84. The boot program 83 controls the basic operation of the second zone ECU 20b. of The boot program 84 is a program for starting the execution of the vehicle startup program 85. of This is a program that is executed to start the execution of the vehicle startup program 86.
[0065] Therefore, the program execution unit 51 executes the master boot record 81, followed by the boot program 83 and the vehicle startup program 85, or the boot program 84 and the vehicle startup program 86.
[0066] The first program storage area 67 stores a vehicle startup program 85. The second program storage area 68 stores a vehicle startup program 86. The vehicle startup program 85 is a program similar to the vehicle startup program 73. The same is true for the vehicle startup program 86. The first program storage area 67 can also store abnormality occurrence information 87A and update information 88A. The second program storage area 68 can also store abnormality occurrence information 87B and update information 88B.
[0067] That is, the vehicle startup programs 85, 86 include a program for causing the second zone ECU 20b to operate the ECU 30k to switch the power supply relay 41 and start the vehicle V. In addition, the vehicle startup programs 85, 86 may include a function for controlling an engine starter (not shown), etc.
[0068] The vehicle startup programs 85, 86 include one or more programs for executing basic operations of the vehicle V. In other words, the vehicle startup programs 85, 86 include functions essential for starting, running, and stopping the vehicle V. For example, the vehicle startup programs 85, 86 include a function for controlling the door lock mechanism 33 and the ESL 34. In addition, the functions of the vehicle startup programs 85, 86 include controls that are required by law or regulation to be executed while the vehicle V is running. For example, the vehicle startup programs 85, 86 include a function for controlling the illumination of the lamps, a function for controlling the wiper motor, and a function for controlling the window washer motor.
[0069] The functions of the vehicle startup programs 85, 86 may include a function necessary for updating a program in the control system 1. For example, the vehicle startup programs 85, 86 may include a function for communicating with the server 110 via the TCU 12 and a function for communicating with the vehicle diagnosis device 120 via the DLC 19.
[0070] Furthermore, the vehicle startup programs 85, 86 may include programs related to functions that are not essential for driving the vehicle V. For example, the vehicle startup programs 85, 86 may include a function related to accessibility that enhances user convenience and a function related to infotainment that enhances user entertainment. Specifically, the functions of the vehicle startup programs 85, 86 may include a function for opening and closing doors hands-free, a function for lighting the interior space of the vehicle V, and the like.
[0071] Both the vehicle startup program 85 and the vehicle startup program 86 are programs that are compatible with the second zone ECU 20b. The vehicle startup program 85 and the vehicle startup program 86 may be the same program or may be different programs. For example, the vehicle startup program 85 and the vehicle startup program 86 are the same type of program but different versions. Assume an example in which the vehicle startup program 86 is a newer version than the vehicle startup program 85. In this example, for example, the vehicle startup program 86 is an improved version program in which functions are added to the vehicle startup program 85. Also, for example, the vehicle startup program 86 is a program in which defects and vulnerabilities of the vehicle startup program 85 are eliminated.
[0072] The boot area 61A stores a vehicle startup program 82 in addition to the master boot record 81. The vehicle startup program 82 is executed by the program execution unit 51, similar to the vehicle startup programs 85 and 86, and is a program for the program execution unit 51 to control each unit.
[0073] Like the vehicle startup programs 85 and 86, the vehicle startup program 82 includes one or more programs for executing basic operations of the vehicle V. Specifically, it includes functions essential for starting, running, and stopping the vehicle V, and controls that are required by law or regulation to be executed while the vehicle V is running. Therefore, by the program execution unit 51 executing the vehicle startup program 82, it becomes possible to at least start the vehicle V and run the vehicle V.
[0074] The vehicle startup program 82 may be a program that does not include an accessibility-related function that enhances user convenience or an infotainment-related function that enhances user entertainment among the functions realized by the vehicle startup programs 85 and 86. In this case, the storage capacity for storing the vehicle startup program 82 is smaller than those of the vehicle startup programs 85 and 86, so that the storage capacity of the boot area 61A can be reduced.
[0075] The memory area of memory unit 53A is classified into side A and side B. Side A includes side A boot image memory area 65 and first program memory area 67. Side B includes side B boot image memory area 66 and second program memory area 68. Boot area 61A does not belong to either side A or side B.
[0076] The storage area of the A side and the storage area of the B side store programs independently of each other. The program execution unit 51 realizes various functions of the second zone ECU 20b by using the programs stored in either the storage area of the A side or the B side. When the program execution unit 51 selects the A side, the program execution unit 51 executes the master boot record 81, followed by the boot program 83 and the vehicle startup program 85. In this case, the program execution unit 51 can control each unit including the power relay 41 without executing the program of the B side. In other words, the program execution unit 51 can execute the operation of the second zone ECU 20b as long as the program is normally stored in either the A side or the B side of the storage unit 53A.
[0077] When updating a program stored in the storage unit 53A, the update execution unit 52 selects either side A or side B. As an example, assume that a program newer than the vehicle startup program 85 stored in the program storage first area 67 is provided by the server 110. In this case, the update execution unit 52 updates the vehicle startup program 86 stored in a storage area different from the vehicle startup program 85. The update execution unit 52 downloads a vehicle control update program for updating the vehicle startup program 86 from the server 110, and updates the program stored in the program storage second area 68 based on this vehicle control update program. Thereafter, the update execution unit 52 changes the setting so that the program execution unit 51 executes the vehicle startup program 86, which is the new version.
[0078] The first program storage area 67 and the second program storage area 68 are areas that can be rewritten by the update execution unit 52. The first program storage area 67 and the second program storage area 68 correspond to an example of a rewritable area. Therefore, the update execution unit 52 can execute a process of storing a new program in the first program storage area 67 and the second program storage area 68, and a process of updating a program that has already been stored therein.
[0079] The boot area 61A is an area in which rewriting is restricted or prohibited, similarly to the boot area 61. The boot area 61A corresponds to an example of a rewrite-restricted area. Therefore, the update execution unit 52 does not perform a process of updating the programs stored in the boot area 61A. Specifically, the vehicle startup program 82 is not subject to the update process executed by the update execution unit 52. For example, the vehicle startup program 82 is not changed from the state stored in the boot area 61A at the time of shipment of the vehicle V from the factory. The boot area 61A does not need to be completely prohibited from being rewritten, and may be an area set so that it is not subject to the process of the update execution unit 52 rewriting programs or data. For example, rewriting of the boot area 61A is not prevented by the control of the central ECU 2 or the vehicle diagnosis device 120 connected via the DLC 19.
[0080] The A side boot image storage area 65 and the B side boot image storage area 66 are not targets for program rewriting by the update execution unit 52. For example, the A side boot image storage area 65 and the B side boot image storage area 66 may be areas in which rewriting by the update execution unit 52 is restricted, similar to the boot area 61A.
[0081] Vehicle startup program stored in the program storage area 62 85,86 can be updated by the function of the update execution unit 52. In contrast, the vehicle startup program 82 stored in the boot area 61A is not updated by the update execution unit 52. Therefore, the vehicle startup program 82 is in a protected state regardless of the operation of the update execution unit 52. Even if some kind of problem occurs in the update process in which the update execution unit 52 updates the vehicle startup program 73, the control system 1 can start up the vehicle V and run the vehicle V by executing the vehicle startup program 82 by the program execution unit 51.
[0082] Figures 8, 9 and 10 are flowcharts showing the operation of the control system 1 in the second embodiment. Figures 8 and 9 show a process for updating the vehicle startup programs 85, 86 stored in the storage unit 53A. Figure 9 is a modified example of the operation shown in Figure 8. Steps S14, and S41 to S44 in Figure 8 correspond to an example of the update process. Steps S46, and S43 to S44 in Figure 9 correspond to an example of the update process.
[0083] Steps S11 to S14 and S17 to S19 in FIG. 8 are the same as those in FIG. 5, and therefore their explanation will be omitted here.
[0084] As shown in Fig. 8, after starting the update process in step S14, the update execution unit 52 identifies either the first program storage area 67 or the second program storage area 68 as the area to be updated (step S41). The update execution unit 52 generates update information and stores it in the memory unit 53A (step S42). The update information is information indicating whether the program not to be updated is suitable for use. The update execution unit 52 generates the update information based on the reason for performing the update process.
[0085] As an example, a case will be described in which the update execution unit 52 updates the vehicle startup program 85 stored in the first program storage area 67. In this case, in step S41, the update execution unit 52 selects the first program storage area 67 as the area to be updated. The update execution unit 52 generates update information 88B for the vehicle startup program 86 stored in the second program storage area 68 that is not the area to be updated, and stores the information in the second program storage area 68. The update information 88B indicates whether the vehicle startup program 86 is suitable for use. When the reason for performing the update process corresponds to eliminating defects or vulnerabilities in the vehicle startup program 86, the update execution unit 52 generates update information 88B indicating that the vehicle startup program 86 is not suitable for use. When the reason for performing the update process does not correspond to eliminating defects or vulnerabilities in the vehicle startup program 86, the update execution unit 52 generates update information 88B indicating that the vehicle startup program 86 is suitable for use. The reason for performing the update process can be determined, for example, by additional information that the server 110 transmits to the control system 1 together with the vehicle control update program. In this case, when transmitting the vehicle control update program to the control system 1, the server 110 transmits additional information indicating the reason for performing the update process to the control system 1. Similarly, when updating the vehicle activation program 86 stored in the program storage second area 68, the update execution unit 52 generates update information 88A indicating whether the vehicle activation program 85 is suitable for use or not, and stores the information in the program storage first area 67. Moreover, the update information 88A, 88B may be a code indicating the reason for performing the update process, or the like.
[0086] The update execution unit 52 stores the vehicle control update program downloaded in step S12 in the area to be updated (step S43). The update execution unit 52 uses the vehicle control update program stored in step S43 to install the vehicle startup program stored in the area to be updated (step S44). The process of step S44 is the same as that of step S16.
[0087] In addition, when it is determined in step S18 that the installation has not been completed normally, the update execution unit 52 stores abnormality occurrence information in the area to be updated. completion If not, the update execution unit 52 stores the abnormality occurrence information 87A in the first program storage area 67, which is the area to be updated, in step S45.
[0088] 8 shows an operation in which the update data control unit 203 waits for the power supply of the vehicle V to be switched off, and executes the update process after the power supply of the vehicle V is switched off, similar to Fig. 5. Since the storage unit 53A has a storage area on side A and a storage area on side B, the update process can be executed without affecting the reliability of the program even while the power supply of the vehicle V is on. The operation in this case is shown in Fig. 9.
[0089] In FIG. 9, steps S11, S12, S17 to S19, and S43 to S45 are the same operations as those in FIG. 8, and therefore the description thereof will be omitted.
[0090] As shown in FIG. 9, after the update data receiving unit 202 downloads the program in step S12, the update executing unit 52 selects a storage area and starts the update process (step S46). In step S46, the update executing unit 52 selects the area with the older last update date and time from the storage area on the A side and the storage area on the B side of the storage unit 53A as the target of the update process. In detail, the update executing unit 52 specifies the last update date and time of the program storage first area 67 and the program storage second area 68. The last update date and time of the program storage first area 67 is the date and time when the program stored in the program storage first area 67 was last updated. The same applies to the last update date and time of the program storage second area 68. The update executing unit 52 compares the last update date and time of the program storage first area 67 and the program storage second area 68, and selects the area with the older last update date and time. In step S46, the update executing unit 52 may generate update information by the same process as in step S42, and store the update information in the storage area on the non-selected side. After step S46, the update execution section 52 proceeds to step S43.
[0091] If the update execution unit 52 determines in step S18 that the installation has been completed normally (step S18; YES), the update data control unit 203 determines whether or not an operation to turn off the power of the vehicle V has been performed (step S47). The determination in step S47 may be the same as in step S13. Alternatively, in step S47, the update data control unit 203 may determine whether or not an operation to instruct turning off the power of the vehicle V has been performed. In other words, the determination may be an operation to instruct this, rather than an actual switching off of the power of the vehicle V. An example of this type of operation is the operation of the ignition switch of the vehicle V.
[0092] The update data control unit 203 waits until the power supply of the vehicle V is switched off (step S47; NO). When it is determined that the power supply of the vehicle V is switched off (step S47; YES), the update data control unit 203 performs a process of requesting the user to approve the activation (step S48). For example, in step S48, the update data control unit 203 executes one or more of a process of displaying a message requesting approval for the update on a touch panel mounted on the vehicle V, and a process of outputting a voice message requesting approval for the update from a speaker mounted on the vehicle V. Here, in step S48, the update data control unit 203 may display an operation icon or the like on the touch panel for the user to perform an approval operation.
[0093] The update data control unit 203 determines whether or not an operation to approve the update has been performed by the user (step S49). The operation to approve the update is, for example, an operation on a touch panel. If it is determined that an operation to approve the update has not been performed (step S49; NO), the update data control unit 203 ends this process. In this case, the update data control unit 203 performs the operation of step S48 every time the power of the vehicle V is turned off thereafter.
[0094] If an operation to approve the update is performed (step S49; YES), the update execution unit 52 executes activation of the installed program (step S19) under the control of the update data control unit 203, and ends this process. In step S19, the update execution unit 52 performs setting so that the program installed in step S44 will be executed the next time the power of the vehicle V is turned on.
[0095] The update execution unit 52 and the update data control unit 203 may be configured to selectively execute either the operation in FIG. 8 or the operation in FIG. In addition, the update execution unit 52 and the update data control unit 203 may be configured to execute both the operation of FIG. 8 and the operation of FIG. 9, and to select and execute either one of them. For example, the update data control unit 203 may be configured to execute the operation of FIG. 8 when the reason for performing the update process corresponds to eliminating a defect or vulnerability of the vehicle startup program 86. In this case, the update execution unit 52 and the update data control unit 203 execute the operation of FIG. 8 or FIG. 9 when the reason for performing the update process does not correspond to eliminating a defect or vulnerability of the vehicle startup program 86. In the program update process, it is necessary to consider that the original program cannot be executed by overwriting and updating the program stored in the storage unit 53A. When both the program stored in the program storage first area 67 and the program stored in the program storage second area 68 are in a state where they can be executed by the program execution unit 51 without any problems, updating either one does not affect reliability. In such a case, the storage unit 53A stores executable programs in both the program storage first area 67 and the program storage second area 68. Therefore, the program can be updated without affecting the reliability of the program even if the power of the vehicle V is not turned off. In this case, the operation of FIG. 9 has the advantage that the update process can be performed while the power of the vehicle V is turned on.
[0096] 10 shows the operation related to the start-up of the second zone ECU 20b. The operation in FIG. 10 can be performed in either the case where the program update is performed as shown in FIG. 8 or the case where the program update is performed as shown in FIG.
[0097] The program execution unit 51 refers to the master boot record (MBR) 81, and selects and executes the boot program 83 or the boot program 84 (step S51). In step S51, the program execution unit 51 selects either the A-side boot image storage area 65 or the B-side boot image storage area 66, i.e., either the A side or the B side. For example, the program execution unit 51 compares the last update dates and times of the vehicle startup program 85 and the vehicle startup program 86 using the function of the program included in the master boot record 81. In this case, the program execution unit 51 selects the area of the A side or the B side that stores the vehicle startup program with the newer last update date and time.
[0098] In the following, as an example, a case will be described in which the program execution unit 51 selects and executes a program on side A in step S51. The operation when the program execution unit 51 selects a program on side B can be understood in a similar manner.
[0099] When the program execution unit 51 executes the boot program 83 in step S51, it refers to the first program storage area 67 (step S52) and determines whether or not the abnormality occurrence information 87A is stored (step S53).
[0100] If the abnormality occurrence information 87A is not stored (step S53; NO), the program execution unit 51 executes the vehicle startup program 85 stored in the first program storage area 67 (step S54). The program execution unit 51 executes the vehicle startup program 85, thereby causing the ECU 30k to switch the power supply relay 41 and start up the vehicle V (step S55). This enables the control system 1 to control functions necessary for the running of the vehicle V, and the vehicle V transitions to a power-on state.
[0101] If the abnormality occurrence information 87A is stored in the first program storage area 67 (step S53; YES), the program execution unit 51 refers to the update information 88B (step S55). In step S55, the program execution unit 51 refers to the memory area not referred to in step S52, i.e., the update information 88B stored in the second program storage area 68.
[0102] The program execution unit 51 determines whether or not the vehicle startup program 86 in the second program storage area 68 is available based on the update information 88B referenced in step S55 (step S57).
[0103] When it is determined that the vehicle startup program 86 is available (step S57; YES), the program execution unit 51 executes the vehicle startup program 86 (step S58). By executing the vehicle startup program 86, the program execution unit 51 causes the ECU 30k to switch the power supply relay 41, thereby starting up the vehicle V (step S59). This enables the control system 1 to control functions necessary for the running of the vehicle V, and the vehicle V transitions to a power-on state.
[0104] Thereafter, the update control unit 201 or the program execution unit 51 issues a first abnormality notification (step S60). The first abnormality notification is a notification indicating that the update process of the vehicle startup program 85 has not been completed normally, and is a notification issued when the vehicle startup program 86 is executable. The method of issuing the first abnormality notification is the same as the abnormality notification executed in step S38.
[0105] When it is determined that the vehicle startup program 86 is not available (step S57; NO), the program execution unit 51 executes the vehicle startup program 82 stored in the boot area 61A (step S61). The program execution unit 51 executes the vehicle startup program 82, thereby causing the ECU 30k to switch the power supply relay 41 and start up the vehicle V (step S62). This enables the control system 1 to control functions necessary for the running of the vehicle V, and the vehicle V transitions to a power-on state.
[0106] Thereafter, the update control unit 201 or the program execution unit 51 issues a second abnormality notification (step S60). The second abnormality notification is a notification indicating that the update process of the vehicle startup program 85 is not completed normally and that the vehicle startup program 86 is not suitable for use. The first abnormality notification is issued when one of the vehicle startup programs 85 and 86 stored in the storage unit 53A is normally usable and the update process of the other is not successful. This situation can be resolved by redoing the update process. In contrast, the second abnormality notification indicates that both of the vehicle startup programs 85 and 86 stored in the storage unit 53A are not suitable for use and that the vehicle V has been started using the vehicle startup program 82 for emergency use. The vehicle startup program 82 is a program having a function that satisfies the criteria for safely driving the vehicle V, but has fewer functions compared to the vehicle startup programs 85 and 86. For this reason, it is desirable to deal with the state in which the vehicle V has been started by the vehicle startup program 82 as soon as possible. For example, it is desirable to update or repair at least one of the vehicle startup programs 85, 86 by connecting a vehicle diagnostic device 120 to the DLC 19 at a dealer or repair shop of the vehicle V.
[0107] Therefore, the first abnormality notification, for example, is a notification that urges the user to redo the update process. In contrast, the second abnormality notification, for example, is a notification that requests the user to take action early. For this reason, it is desirable that the manner of the first abnormality notification and the manner of the second abnormality notification are different enough for the user to clearly distinguish them. The method of the second abnormality notification can be the same as that of the first abnormality notification executed in step S60.
[0108] After issuing the second abnormality occurrence notification, the update control unit 201 or the program execution unit 51 transmits an abnormality occurrence signal to the external device (step S64). The abnormality occurrence signal is the same as the signal transmitted in step S39.
[0109] The above embodiment shows a specific example to which the present invention is applied, and does not limit the form to which the invention is applied.
[0110] In the above embodiment, the operation has been described in the case where control system 1 updates vehicle startup programs 72, 85, 86 stored in storage units 53, 53A based on a vehicle control update program downloaded from server 110. The present invention is not limited to this, and for example, the operation shown in Fig. 5 or 8 may be executed when control system 1 receives a vehicle control update program from vehicle diagnosis device 120 connected to DLC 19. In other words, the operation of the above embodiment may be applied in the case where control system 1 obtains a vehicle control update program from vehicle diagnosis device 120, which is an external device, and updates the vehicle startup program.
[0111] In the above embodiment, the vehicle startup programs 72, 85, and 86 executed by the second zone ECU 20b of the control system 1 are updated. This is just one example. For example, the configurations of the storage units 53 and 53A and the operations of the program execution unit 51 and the update execution unit 52 described in the present embodiment can of course be applied to the central ECU 2 and other ECUs.
[0112] In the above embodiment, an example has been described in which the present invention is applied to an update process for updating a vehicle startup program required for starting the vehicle V. This is just one example, and the configuration and operation of the present embodiment can be applied to an update process for updating a program related to the functions of the vehicle V.
[0113] In the above embodiment, an example has been described in which an abnormality occurrence notification, a first abnormality occurrence notification, or a second abnormality occurrence notification is given when installation of the vehicle startup program is not completed normally. This is one example. For example, when the program execution unit 51 executes a vehicle startup program updated by an update process, that is, when the update process is successful, the program execution unit 51 may give a notification indicating that the update process is successful. Also, a signal indicating that the update process is successful may be sent to an external device.
[0114] Furthermore, the configuration of the control system 1 shown in the above embodiment is just an example, and the type of ECU included in the control system 1, the number of ECUs, and the configuration of the devices controlled by the ECUs can be modified in various ways.
[0115] 1 and 3 are diagrams showing the schematic configuration of the functional configuration of each device of the program management system 100, divided according to the main processing content, in order to facilitate understanding of the present invention, and are not intended to limit the configuration of the devices. Each process shown in Figures 5, 6, 8, 9, and 10 may be executed by one program or multiple programs.
[0116] Furthermore, the vehicle V is, for example, a four-wheeled vehicle, but the type of the vehicle V is not particularly limited and may be a large automobile, a commercial vehicle, a two-wheeled vehicle, a three-wheeled vehicle, etc. Furthermore, the configuration of each part in the control system 1 can be changed arbitrarily.
[0117] The above embodiment supports the following configurations.
[0118] (Configuration 1) A vehicle control device comprising: a vehicle control unit that controls a vehicle by executing a vehicle startup program for starting the vehicle; a memory unit having a rewrite restricted area in which the vehicle startup program is stored and rewrite-restricted, and a rewritable area in which the vehicle startup program is stored in a rewritable manner; a communication unit that communicates with an external device; and a program update unit that executes an update process to store a vehicle startup update program received by the communication unit and used to update the vehicle startup program in the rewritable area, wherein the vehicle control unit executes the vehicle startup program stored in the rewrite restricted area, and if the update process by the program update unit is not completed successfully, executes the vehicle startup program stored in the rewrite restricted area. According to the vehicle control device of configuration 1, even if a problem occurs in updating the vehicle startup program, the vehicle can be started using the vehicle startup program stored in the area where rewriting is restricted. The vehicle startup program stored in the area where rewriting is restricted is not subject to updating, and is therefore maintained in an executable state. This can reliably avoid a situation in which the vehicle startup program cannot be executed, and ensure the reliability of updates to the program that controls the vehicle.
[0119] (Configuration 2) The vehicle control device according to configuration 1, wherein the vehicle startup program includes a power relay control program for controlling a power relay of the vehicle. According to the vehicle control device of configuration 2, it is possible to ensure reliability regarding updates to the program that controls the power supply relay of the vehicle.
[0120] (Configuration 3) A vehicle control device as described in Configuration 1 or Configuration 2, wherein the program update unit, when the update process is not completed normally, stores abnormality occurrence information indicating that the update process was not completed normally in the memory unit. According to the vehicle control device of configuration 3, by storing information indicating that the update process was not completed normally, it is possible to reliably identify a vehicle startup program whose update process was not completed normally. For example, when the vehicle control unit starts up and executes a vehicle startup program, it is possible to prevent the vehicle startup program whose update process was not completed normally from being executed. This ensures higher reliability in updating the program that controls the vehicle.
[0121] (Configuration 4) The vehicle control device according to configuration 3, wherein the vehicle control unit executes the vehicle startup program stored in the rewrite restricted area when the abnormality occurrence information is stored in the memory unit. According to the vehicle control device of configuration 4, it is possible to distinguish vehicle startup programs whose update process has not been completed normally based on the abnormality occurrence information. As a result, the vehicle is started using the vehicle startup programs stored in the area where rewriting is restricted, without executing the vehicle startup programs that are not suitable for execution. This ensures higher reliability in updating the programs that control the vehicle.
[0122] (Configuration 5) A vehicle control device as described in any one of configurations 1 to 4, further comprising a notification unit that issues an abnormality notification indicating that the update process was not completed normally, and when the vehicle control unit executes the vehicle startup program stored in the rewrite restricted area, the notification unit issues the abnormality notification. According to the vehicle control device of configuration 5, the vehicle status can be notified to the user by notifying that the update process of the vehicle startup program has not been completed normally. This notification can, for example, prompt the user to re-execute the update process of the vehicle startup program or to repair the vehicle startup program. Therefore, even if a problem occurs in updating the program that controls the vehicle, the user can take more appropriate measures.
[0123] (Configuration 6) A vehicle control device as described in configuration 5, wherein when the notification unit executes the abnormality occurrence notification, the communication unit transmits an abnormality occurrence signal to the external device indicating that the update process was not completed normally. According to the vehicle control device of configuration 6, it is possible to notify an external device that the update process of the vehicle startup program has not been completed normally. This notification allows the external device to detect or record that the update process of the vehicle startup program has not been completed normally. This makes it possible to provide assistance to the user from the outside, for example, regarding re-executing the update process of the vehicle startup program or repairing the vehicle startup program.
[0124] (Configuration 7) The vehicle control device described in configuration 1, wherein the memory unit has a first memory area for storing the vehicle startup program and the vehicle startup update program, and a second memory area for storing the vehicle startup program and the vehicle startup update program, in the rewritable area, and the program update unit executes the update process to store the vehicle startup update program in at least one of the first memory area or the second memory area, and if the update process to store the vehicle startup update program in the second memory area is not completed normally, stores abnormality occurrence information in the first memory area, indicating that the update process was not completed normally. According to the vehicle control device of the seventh aspect, while updating the vehicle startup program, the vehicle startup program can be held in an area that is not affected by the update, so there is no need to restrict the timing of updating the program in case of a problem occurring in the program update. Therefore, the constraints on the timing of updating the program can be reduced. Then, when a problem occurs in the update process, the vehicle can be started using the vehicle startup program stored in the area where rewriting is restricted. That is, even if both the vehicle startup program for which the update was not normally completed and the vehicle startup program for which the update was not normally completed are in a state that is not suitable for execution, it is possible to start the vehicle. Furthermore, the vehicle startup program for which the update process was not normally completed can be distinguished based on the abnormality occurrence information. As a result, the vehicle can be started using the vehicle startup program stored in the area where rewriting is restricted without executing the vehicle startup program that is not suitable for execution. Therefore, the vehicle can be started reliably, and higher reliability can be ensured with respect to the update of the program that controls the vehicle.
[0125] (Configuration 8) A vehicle control device as described in Configuration 7, wherein when the vehicle startup program is stored in the first storage area and the second storage area, the vehicle control unit selects and executes the vehicle startup program stored in the first storage area or the vehicle startup program stored in the second storage area based on the abnormality occurrence information. According to the vehicle control device of configuration 8, the vehicle startup program for which the update process was not completed normally is distinguished based on the abnormality occurrence information. This allows the vehicle to be started using the vehicle startup program stored in the area where rewriting is restricted, without executing the vehicle startup program that is not suitable for execution. Therefore, the vehicle can be started reliably, and higher reliability can be ensured with respect to the update of the program that controls the vehicle.
[0126] (Configuration 9) A vehicle control device as described in configuration 7 or configuration 8, further comprising a notification unit that notifies that the update process was not completed successfully, and the vehicle control unit issues a first notification of abnormality occurrence via the notification unit when executing the vehicle startup program stored in the first memory area based on the abnormality occurrence information. According to the vehicle control device of configuration 9, the vehicle status can be notified to the user by notifying that the update process of the vehicle startup program has not been completed normally. This notification can, for example, prompt the user to re-execute the update process of the vehicle startup program. Therefore, even if a problem occurs in the update of the program that controls the vehicle, the user can take more appropriate measures.
[0127] (Configuration 10) A vehicle control device as described in configuration 9, wherein when the vehicle control unit executes the vehicle startup program stored in the rewrite restricted area, the notification unit issues a second abnormality notification different from the first abnormality notification. According to the vehicle control device of configuration 10, it is possible to notify the user that both the vehicle startup program whose update was not normally completed and the vehicle startup program whose update was not completed are in an unsuitable state for execution. The second abnormality notification is different from the first abnormality notification that prompts the user to re-execute the update process of the vehicle startup program, and therefore it is possible to notify the user that a more immediate action is required.
[0128] (Configuration 11) A vehicle control device as described in configuration 10, wherein when the notification unit executes the second abnormality notification, the communication unit transmits an abnormality occurrence signal to the external device indicating that the update process was not completed normally. According to the vehicle control device of configuration 11, it is possible to inform an external device that the update process of the vehicle startup program has not been completed normally and that the unupdated vehicle startup program is also in an unsuitable state for execution. This makes it possible to provide assistance to the user from the outside with regard to, for example, re-executing the update process of the vehicle startup program or repairing the vehicle startup program.
[0129] (Configuration 12) A vehicle control method that utilizes a vehicle control device having a communication unit that communicates with an external device outside the vehicle and a memory unit that stores a vehicle startup program for starting up the vehicle, wherein the memory unit is provided with a rewrite restricted area in which the vehicle startup program is stored and rewrite-restricted, and a rewritable area in which the vehicle startup program is stored in a rewritable manner, the vehicle control method performs an update process in which a vehicle startup update program used to update the vehicle startup program received by the communication unit is stored in the rewritable area, the vehicle is started by executing the vehicle startup program stored in the rewritable area, and if the update process is not completed normally, the vehicle startup program stored in the rewrite restricted area is executed. According to the vehicle control method of configuration 12, even if a problem occurs in updating the vehicle startup program, the vehicle can be started using the vehicle startup program stored in the area where rewriting is restricted. The vehicle startup program stored in the area where rewriting is restricted is not subject to updating, and is therefore maintained in an executable state. This can reliably avoid a situation in which the vehicle startup program cannot be executed, thereby ensuring reliability in updating the program that controls the vehicle.
[0130] (Configuration 13) A recording medium storing a program executed by a computer that controls a vehicle control device having a communication unit that communicates with an external device outside the vehicle and a memory unit that stores a vehicle startup program for starting the vehicle, wherein the memory unit is provided with a rewrite restricted area in which the vehicle startup program is stored and rewrite-restricted, and a rewritable area in which the vehicle startup program is stored in a rewritable manner, the recording medium storing a program that causes the computer to execute an update process in which a vehicle startup update program used to update the vehicle startup program received by the communication unit is stored in the rewritable area, starts the vehicle by executing the vehicle startup program stored in the rewritable area, and if the update process is not completed normally, executes the vehicle startup program stored in the rewrite restricted area. According to the program recorded on the recording medium of configuration 13, even if a problem occurs in updating the vehicle startup program, the vehicle can be started using the vehicle startup program stored in the area where rewriting is restricted. The vehicle startup program stored in the area where rewriting is restricted is not subject to updating, and is therefore maintained in an executable state. This can reliably avoid a situation in which the vehicle startup program cannot be executed, ensuring reliability in updating the program that controls the vehicle. [Explanation of symbols]
[0131] 1...control system (vehicle control device), 2...central ECU, 12...TCU (communication unit), 19...DLC (communication unit), 20...zone ECU, 20a...first zone ECU, 20b...second zone ECU, 20c...third zone ECU, 30, 30a, 30b, 30c, 30d, 30e, 30f, 30g, 30h, 30i, 30j, 30k, 30l, 30m, 30n...ECU, 41...power relay, 51...program execution unit (vehicle control unit), 52...update execution unit (program update unit), 53, 53A...storage unit, 61, 61A...boot area (rewrite restricted area), 62...program RAM memory area (rewritable area), 67...program memory first area (rewritable area), 68...program memory second area (rewritable area), 72...vehicle startup program, 73...vehicle startup program, 74...abnormality occurrence information, 81...master boot record, 82...vehicle startup program, 85, 86...vehicle startup program, 87A, 87B...abnormality occurrence information, 88A, 88B...update information, 100...program management system, 110...server, 120...vehicle diagnosis device, 201...update control unit, 202...update data receiving unit, 203...update data control unit, V...vehicle.
Claims
1. a vehicle control unit that controls the vehicle by executing a vehicle startup program for starting the vehicle; a storage unit including a rewrite restricted area in which the vehicle startup program is stored and rewrite restricted, and a rewriteable area in which the vehicle startup program is stored in a rewritable manner; A communication unit that communicates with an external device; a program update unit that executes an update process to store a vehicle startup update program, which is received by the communication unit and is used to update the vehicle startup program, in the rewritable area; a notification unit that notifies that the update process has not been completed normally, the vehicle control unit executes the vehicle startup program stored in the rewritable area, and when the update process by the program update unit is not normally completed, executes the vehicle startup program stored in the rewritable area; the storage unit includes a first storage area for storing the vehicle startup program and the vehicle startup update program, and a second storage area for storing the vehicle startup program and the vehicle startup update program, in the rewritable area; The program update unit is Executing the update process to store the vehicle startup update program in at least one of the first storage area and the second storage area; when the update process for storing the vehicle startup update program in the second storage area is not completed normally, abnormality occurrence information indicating that the update process was not completed normally is stored in the first storage area; the vehicle control unit, when executing the vehicle startup program stored in the first storage area based on the abnormality occurrence information, issues a first abnormality occurrence notification by the notification unit; Vehicle control device.
2. When the vehicle startup program is stored in the first storage area and the second storage area, the vehicle control unit selects and executes the vehicle startup program stored in the first storage area or the vehicle startup program stored in the second storage area based on the abnormality occurrence information. The vehicle control device according to claim 1.
3. when the vehicle control unit executes the vehicle startup program stored in the rewrite restricted area, the notification unit issues a second abnormality occurrence notification different from the first abnormality occurrence notification. The vehicle control device according to claim 1 or 2.
4. When the notification unit executes the second abnormality occurrence notification, the communication unit transmits, to the external device, an abnormality occurrence signal indicating that the update process has not been completed normally. The vehicle control device according to claim 3.
5. A vehicle control method executed by a vehicle control device including a communication unit that communicates with an external device located outside a vehicle, and a storage unit having a rewrite-restricted area in which a vehicle startup program for starting the vehicle is stored and in which rewrite is restricted, and a rewriteable area in which the vehicle startup program is rewritable, the rewritable area of the storage unit includes a first storage area and a second storage area for storing the vehicle startup program, a program updating step of executing an update process in which a vehicle startup update program used for updating the vehicle startup program received by the communication unit is stored in at least one of the first storage area and the second storage area of the rewritable area; a vehicle control step of starting the vehicle by executing the vehicle startup program stored in the rewritable area, and, if the update process by the program update step is not normally completed, executing the vehicle startup program stored in the rewrite restricted area; and a notification step of notifying that the update process was not completed normally. the program update step includes, when the update process for storing the vehicle startup update program in the second storage area is not completed normally, storing, in the first storage area, abnormality occurrence information indicating that the update process was not completed normally; The vehicle control step includes a step of performing a first notification of an abnormality occurrence in a case where the vehicle startup program stored in the first storage area is executed based on the abnormality occurrence information. A vehicle control method.
6. A recording medium storing a program executed by a computer constituting a vehicle control device, the recording medium including a communication unit that communicates with an external device located outside a vehicle, and a storage unit having a rewrite-restricted area in which a vehicle startup program for starting the vehicle is stored and in which rewrite is restricted, and a rewriteable area in which the vehicle startup program is rewritable, the rewritable area of the storage unit includes a first storage area and a second storage area for storing the vehicle startup program, The program stored in the recording medium causes the computer to a program update unit that executes an update process to store a vehicle startup update program used for updating the vehicle startup program received by the communication unit in at least one of the first storage area and the second storage area of the rewritable area; a vehicle control unit that starts the vehicle by executing the vehicle startup program stored in the rewritable area, and that, if the update process by the program update unit is not normally completed, executes the vehicle startup program stored in the rewritable area; a notification unit that notifies that the update process has not been completed normally; when the update process for storing the vehicle startup update program in the second storage area is not completed normally, the program update unit stores, in the first storage area, abnormality occurrence information indicating that the update process was not completed normally; the vehicle control unit, when executing the vehicle startup program stored in the first storage area based on the abnormality occurrence information, issues a first abnormality occurrence notification by the notification unit; Recording medium.
Citation Information
Patent Citations
Data recording / reproducing device
JP2001117765A
Program execution apparatus
JP2004054818A
Control device for vehicle, and device for updating vehicle control program
JP2009042850A
Information processing apparatus and program updating method
JP2010140183A
Onboard electronic control device
JP2018092241A
