Electronic control device, reproduction method, and reproduction program

Abstract

To appropriately transmit a processing request to an electronic control device to be reproduced that conforms to the classical platform, to appropriately implement the reproduction.SOLUTION: An electronic control device 1 is provided with a UCM master 8 that transmits device identification information capable of identifying an electronic control device to be reproduced, a detailed information holding unit 13 that holds detailed information of a connection destination necessary for transmitting a processing request to the electronic control device to be reproduced that is specified by the device identification information, and a flushing adapter 9 that refers to the detailed information held by the detailed information holding unit and transmits the processing request to the electronic control device conforming to a predetermined platform via a programming IF based on the detailed information when receiving the device identification information capable of identifying the electronic control device conforming to the predetermined platform as the one to be reproduced from the UCM master.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an electronic control device, a reproducibility method, and a reproducibility program. [Background technology]

[0002] For example, in an in-vehicle electronic control unit (hereinafter referred to as an ECU (Electronic Control Unit)), it is possible to reprogram an update program for the purpose of improving functionality, repairing defects, etc. In this case, a master ECU that functions as an update master that manages the implementation of reprogramming performs reprogramming by sending a processing request to a reprogramming target ECU that functions as a reprogramming target (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2020-027629 Summary of the Invention [Problem to be solved by the invention]

[0004] The master ECU includes a UCM (Update and Configuration Management) master, a flashing adapter, and a programming interface. According to the AUTOSAR Adaptive Platform (AP) specifications, the flashing adapter has an interface equivalent to that of the UCM. If the ECU to be reprogrammed is an ECU that conforms to the Classic Platform (CP), the flashing adapter receives an ECU ID from the UCM master that can identify the CP-compliant ECU and receives a processing request from the UCM master. However, because detailed information about the connection destination is insufficient, the flashing adapter cannot send the received processing request via the programming interface to the CP-compliant ECU to be reprogrammed, and therefore cannot perform the reprogramming.

[0005] The present invention has been made in consideration of the above-mentioned circumstances, and its purpose is to provide an electronic control device, a reproducibility implementation method, and a reproducibility implementation program that can properly perform reproducibility by properly sending a processing request to an electronic control device to be reproducible that conforms to the classic platform. [Means for solving the problem]

[0006] According to the invention described in claim 1, the UCM master (8) transmits device identification information capable of identifying the electronic control unit to be re-programmed. The detailed information storage unit (13) stores detailed connection information required for transmitting a processing request to the electronic control unit to be re-programmed, which is specified by the device identification information. When the flashing adapter (9) receives device identification information capable of identifying the electronic control unit conforming to a predetermined platform as the re-programmed target from the UCM master, it refers to the detailed information stored in the detailed information storage unit and transmits the processing request. and More Information of Programming IF The programming IF(10) sends the processing request based on the detailed information. Transmit to an electronic control device that conforms to a predetermined platform.

[0007] It holds detailed connection information required to send a processing request to the electronic control unit to be re-programmed, and receives device identification information from the UCM master that can identify the electronic control unit that conforms to the specified platform as the re-programming target. , processing management requirements and More Information of Programming IF and submit the processing request based on the details. The request is sent to an electronic control unit that conforms to a specified platform. As a result, if the electronic control unit that conforms to the specified platform and is the target of reprogramming is an electronic control unit that conforms to the Autozer Classic platform, the processing request can be sent appropriately to the electronic control unit that conforms to the Classic platform and is the target of reprogramming, thereby enabling the reprogramming to be performed appropriately.

[0008] In addition to the inventions set forth in the claims, the present disclosure includes the following inventions. [1] A UCM master (8) that transmits device identification information that can identify the electronic control device to be reproduced; a detailed information storage unit (13) for storing detailed information of a connection destination required to transmit a processing request to an electronic control device to be reproduced, the electronic control device being identified by the device identification information; and a flashing adapter (9) that, upon receiving device identification information from the UCM master that can identify an electronic control device that conforms to a specified platform as a target for reprogramming, references the detailed information stored in the detailed information storage unit and transmits the processing request to the electronic control device that conforms to the specified platform via a programming IF based on the detailed information.

[0009] [2] The electronic control device according to [1], wherein the UCM master transmits a processing request for obtaining version information of the software stored in the electronic control device to be reproduced as the processing request.

[0010] [3] The electronic control device according to [1] or [2], wherein the UCM master transmits a processing request regarding the installation of an update program as the processing request.

[0011] [4] The electronic control device according to any one of [1] to [3], wherein the UCM master transmits a processing request for activating an update program as the processing request.

[0012] [5] The electronic control device according to any one of [1] to [4], wherein the detailed information storage unit stores information including an IP address, a CAN ID, and a port as the detailed information.

[0013] [6] The electronic control device according to any one of claims [1] to [5], wherein the electronic control device conforming to the specified platform is an electronic control device conforming to the Autozer Classic platform. [Brief explanation of the drawings]

[0014] [Figure 1] Functional block diagram illustrating one embodiment. [Figure 2] A diagram showing the internal configuration of the control unit [Figure 3] Diagram showing the UCMID lookup table [Figure 4] Diagram showing the connection reference table [Figure 5] Diagram showing the detailed information reference table [Figure 6] Flowchart showing the connection process of the flashing adapter [Figure 7] Flowchart showing the programming IF connection process [Figure 8] Flowchart showing the process of acquiring version information of the UCM master [Figure 9] Flowchart showing version information acquisition process for flashing adapter [Figure 10] Flowchart showing the version information acquisition process of the programming interface [Figure 11] A diagram showing the process flow when acquiring version information [Figure 12] Flowchart showing the UCM master installation process [Figure 13] Flowchart showing the installation process of the flashing adapter [Figure 14] Flowchart showing the installation process of the programming interface [Figure 15] A diagram showing the installation process [Figure 16] Flowchart showing the UCM Master activation process [Figure 17] Flowchart showing activation process of flashing adapter [Figure 18] Flowchart showing the activation process of a programming IF [Figure 19] A diagram showing the process flow during activation [Figure 20] Flowchart showing the UCM master table update process [Figure 21] Flowchart showing table update processing of a flushing adapter DETAILED DESCRIPTION OF THE INVENTION

[0015] An embodiment will be described below with reference to the drawings. As shown in FIG. 1 , a master ECU 1 mounted on a vehicle functions as an update master that manages reprogramming for purposes such as function improvement and defect repair. The master ECU 1 is connected to multiple ECUs via an in-vehicle network 2 so as to enable data communication, and performs integrated management of the multiple ECUs by issuing operational instructions to the multiple ECUs and acquiring operational status information from the multiple ECUs. The in-vehicle network 2 may be, for example, a Controller Area Network (CAN) (registered trademark), Ethernet (registered trademark), LIN, Clock Extension Peripheral Interface (CXPI) (registered trademark), FLEXRAY (registered trademark), or Media Oriented Systems Transport (MOST) (registered trademark). The master ECU 1 identifies a reprogramming target ECU 3 that functions as a reprogramming target from among the multiple ECUs, and performs reprogramming by instructing the reprogramming target ECU 3 to write an update program.

[0016] The master ECU 1 is connected to a DCM (Data Communication Module) 4 that functions as a data communication device. The DCM 4 is wirelessly connected to an OTA center via a communication network, enabling it to receive distribution packages transmitted from the OTA center. When the DCM 4 receives a distribution package transmitted from the OTA center, it transfers the received distribution package to the master ECU 1. When the distribution package is transferred from the DCM 4, the master ECU 1 extracts an update program from the transferred distribution package and performs reprogramming by instructing the reprogramming target ECU 3 to write the extracted update program.

[0017] Furthermore, the master ECU 1 can transfer a distribution package from a reprogramming tool (not shown) by connecting it to the master ECU 1 via a wired connection. When the distribution package is transferred from the reprogramming tool, the master ECU 1 extracts an update program from the transferred distribution package and instructs the reprogramming target ECU 3 to write the extracted update program, thereby performing reprogramming.

[0018] The master ECU 1 includes a control unit 5 and a storage 6. The control unit 5 is configured by a microcomputer having a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), and I / O (Input / Output). The control unit 5 executes a control program stored in a non-transitory physical storage medium to perform processing corresponding to the control program, thereby controlling the overall operation of the master ECU 1. The control program executed by the control unit 5 includes a reproduction execution program.

[0019] The storage 6 is a non-volatile memory mainly made of, for example, a NOR flash memory or a NAND flash memory, and is shared by multiple applications executed by the control unit 5. That is, the multiple applications each access the storage 6 to write and read data. In this embodiment, a configuration in which the storage 6 is built into the master ECU 1 is exemplified, but the present invention can also be applied to a configuration in which the storage 6 is disposed outside the master ECU 1. Furthermore, while a configuration in which the storage 6 is shared by multiple applications executed by the control unit 5 is exemplified, the storage 6 may also be shared by applications executed by a control unit of another ECU connected to the master ECU 1 so as to be able to communicate data with the master ECU 1.

[0020] As shown in Fig. 2, the control unit 5 includes an OTA client 7, a UCM master 8, a flashing adapter 9, a programming IF 10, and a UCM 11. The UCM master 8 includes a first table storage unit 12. The first table storage unit 12 stores a UCMID reference table shown in Fig. 3 and a connection destination reference table shown in Fig. 4. The UCMID reference table is a table in which an ECUID (ECU identification information) that can identify an ECU to be reproduced is associated with a UCMID that can identify a UCM. The connection destination reference table is a table in which a UCMID is associated with a connection destination.

[0021] When the UCM master 8 acquires the ECU ID of the ECU to be reproduced, it references the UCM ID reference table to acquire the UCM ID corresponding to the acquired ECU ID, and then references the connection destination reference table to acquire the connection destination corresponding to the acquired UCM ID. For example, when the UCM master 8 acquires "ECU01" as the ECU ID, it references the UCM ID reference table to acquire "UCM01" as the UCM ID, and then references the connection destination reference table to acquire the flashing adapter 9 as the connection destination. For example, when the UCM master 8 acquires "ECU04" as the ECU ID, it references the UCM ID reference table to acquire "UCM02" as the UCM ID, and then references the connection destination reference table to acquire UCM as the connection destination.

[0022] The flashing adapter 9 has a second table storage unit 13 as a detailed information storage unit. The second table storage unit 13 stores the detailed information reference table shown in Fig. 5. The detailed information reference table is a table in which ECU IDs, IP addresses, CAN IDs, and ports are associated with each other.

[0023] When the flashing adapter 9 acquires the ECU ID of the ECU to be reprogrammed, it references the detailed information reference table and acquires the IP address, CAN ID, and port number as detailed information for the corresponding ECU to be reprogrammed based on the acquired ECU ID. For example, the flashing adapter 9 acquires "ECU01" as the ECU ID. If the ECU with the assigned ECU ID is connected via Ethernet, it acquires "192.168.xx" as the IP address and "5000" as the port number. For example, the flashing adapter 9 acquires "ECU02" as the ECU ID. If the ECU with the assigned ECU ID is connected via CAN, it acquires "192.168.xx" as the IP address, "YYY" as the CAN ID, and "5001" as the port number. The flashing adapter 9 acquires the ECU ID from the UCM master 8 and uses the detailed information reference table to supplement the information necessary to instruct the programming IF 10.

[0024] The programming IF 10 is a programming interface for accessing a vehicle communication interface that complies with a predetermined standard, such as ISO 22900-2. The UCM 11 executes reprogramming of AP-compliant ECUs.

[0025] Autozer defines standard specifications for automotive software platforms. Autozer defines the Autozer Classic Platform, which uses a static operating system, and the Autozer Adaptive Platform, which uses a dynamic operating system. Therefore, ECUs installed in vehicles include ECUs that comply with the Adaptive Platform (also called AP-compliant ECUs) and ECUs that comply with the Classic Platform (also called CP-compliant ECUs). Note that ECUs installed in vehicles may also include ECUs based on other platforms.

[0026] In reprogramming, the UCM master 8 issues instructions to the UCM 11 if the ECU to be reprogrammed is an AP-compliant ECU, and to the flashing adapter 9 if it is a CP-compliant ECU. The UCM master 8 does not change the format of the instructions depending on whether the instruction is addressed to the UCM 11 or the flashing adapter 9, but sends the instructions in the same format. The flashing adapter 9 has an interface equivalent to that of the UCM 11.

[0027] Next, the operation of the above-described configuration will be described with reference to Figures 6 to 21. Here, connection processing, version information acquisition processing, installation processing, activation processing, and table update processing will be described.

[0028] (1) Connection process (see Figures 6 and 7) (1-1) Connection of the flushing adapter 9 (see Figure 6) When the flashing adapter 9 starts the connection process, it sends the ECU ID of the ECU to be reproduced to the programming IF 10 (B1) and waits to receive a connection ID from the programming IF 10 (B2). When the flashing adapter 9 determines that it has received the connection ID sent from the programming IF 10 (B2: YES), it saves the received connection ID (B3) and terminates the connection process. The detailed information includes, for example, the ECU ID, IP address, and port number, and in the case of a CAN connection, it also includes the CAN ID. Note that in the following embodiments, when the flashing adapter 9 sends the ECU ID to the programming IF 10, the IP address and port number are sent in addition to the ECU ID, and in the case of a CAN connection, the CAN ID is also sent.

[0029] (1-2) Programming IF10 connection process (see Figure 7) When the programming IF10 starts the connection process, it waits to receive the ECU ID of the reprogramming target ECU from the flashing adapter 9 (C1). When the programming IF10 determines that it has received the ECU ID of the reprogramming target ECU sent from the flashing adapter 9 (C1: YES), it identifies the reprogramming target ECU to connect to based on the received ECU ID of the reprogramming target ECU, and connects to the identified reprogramming target ECU (C2). The programming IF10 sends the connection ID to the flashing adapter 9 (C3) and ends the connection process.

[0030] (2) Version information acquisition process (see Figures 8 to 11) (2-1) UCM Master 8 version information acquisition process (see Figure 8) When the UCM master 8 starts the version information acquisition process, it waits to receive a version information acquisition request from the OTA client 7 (A11). When the UCM master 8 determines that it has received the version information acquisition request transmitted from the OTA client 7 (A11: YES), it transmits the version information acquisition request to the flashing adapter 9 (A12) and waits to receive the version information from the flashing adapter 9 (A13). When the UCM master 8 determines that it has received the version information transmitted from the flashing adapter 9 (A13: YES), it transmits the received version information to the OTA client 7 (A14) and ends the version information acquisition process. Note that while only CP-compliant ECUs will be described in this embodiment, if an AP-compliant ECU is present, the UCM master 8 transmits an equivalent version information acquisition request to the UCM 11 and receives version information from the UCM 11.

[0031] (2-2) Acquiring version information of the flashing adapter 9 (see Figure 9) When the flashing adapter 9 starts the version information acquisition process, it waits (B11) to receive a version information acquisition request from the UCM master 8. When the flashing adapter 9 determines that it has received the version information acquisition request sent from the UCM master 8 (B11: YES), it references the detailed information reference table based on the ECU ID of the ECU to be reprogrammed, and acquires detailed information about the ECU to be reprogrammed (B12, which corresponds to the detailed information reference step).

[0032] When the flashing adapter 9 acquires the detailed information of the ECU to be reprogrammed, it performs the connection process described above. That is, the flashing adapter 9 transmits the ECU ID of the ECU to be reprogrammed to the programming IF 10 (B13), and waits to receive a connection ID from the programming IF 10 (B14). When the flashing adapter 9 determines that it has received the connection ID transmitted from the programming IF 10 (B14: YES, corresponding to the device identification information receiving procedure), it saves the received connection ID (B15).

[0033] The flashing adapter 9 transmits a connection ID and a version information acquisition request to the programming IF 10 (B16, corresponding to the processing request transmission procedure) and waits to receive version information from the programming IF 10 (B17). If the flashing adapter 9 determines that it has received the version information transmitted from the programming IF 10 (B17: YES), it transmits the received version information to the UCM master 8 (B18) and terminates the version information acquisition process. Note that if the flashing adapter 9 has completed connection processing with the programming IF 10 and holds a connection ID, steps B12 to B15 may be skipped. Furthermore, if the flashing adapter 9 requests version information from multiple ECUs, it transmits the version information to the UCM master 8 after receiving version information from all ECUs. In this case, a single response is sent to the UCM master 8.

[0034] (2-3) Programming IF10 version information acquisition process (see Figure 10) When the programming IF10 starts the version information acquisition process, it performs the connection process described above. That is, the programming IF10 waits to receive the ECU ID of the reprogramming target ECU from the flashing adapter 9 (C11). When the programming IF10 determines that it has received the ECU ID of the reprogramming target ECU transmitted from the flashing adapter 9 (C11: YES), it identifies the reprogramming target ECU to connect to based on the received ECU ID of the reprogramming target ECU, and connects to the identified reprogramming target ECU (C12).

[0035] The programming IF10 transmits the connection ID to the flashing adapter 9 (C13) and waits to receive the connection ID and a version information acquisition request from the flashing adapter 9 (C14). If the programming IF10 determines that it has received the connection ID and version information acquisition request transmitted from the flashing adapter 9 (C14: YES), it transmits a version information acquisition request to the ECU to be copied based on the ECU ID corresponding to the received connection ID (C15) and waits to receive version information from the ECU to be copied (C16).

[0036] In this case, when the reproducibility target ECU receives the version information acquisition request sent from the programming IF 10, it transmits the version information to the programming IF 10. When the programming IF 10 determines that it has received the version information sent from the reproducibility target ECU (C16: YES), it transmits the received version information to the flashing adapter 9 (C17) and ends the version information acquisition process. As described above, the control unit 5 executes the process flow shown in FIG. 11 when acquiring version information.

[0037] (3) Installation process (see Figures 12 to 15) (3-1) UCM Master 8 installation process (see Figure 12) When the UCM master 8 starts the installation process, it waits to receive update information from the OTA client 7 (A21). When the UCM master 8 determines that it has received the update information sent from the OTA client 7 (A21: YES), it references the UCM ID reference table and the connection destination reference table to obtain mapping information indicating the correspondence between the ECU ID of the ECU to be reproduced and the connection destination (A22), and waits to receive the ECU ID of the ECU to be reproduced and the update program from the OTA client 7 (A23).

[0038] When the UCM master 8 determines that it has received the ECU ID of the ECU to be reproduced and the update program sent from the OTA client 7 (A23: YES), it waits to receive an installation request from the OTA client 7 (A24). When the UCM master 8 determines that it has received an installation request sent from the OTA client 7 (A24: YES), it identifies the installation request destination based on the mapping information (A25).

[0039] The UCM master 8 sends the ECU ID of the ECU to be reprogrammed and the update program to the flashing adapter 9 (A26), sends an installation request to the flashing adapter 9 (A27), and waits to receive an installation completion notification from the flashing adapter 9 (A28). When the UCM master 8 determines that it has received the installation completion notification sent from the flashing adapter 9 (A28: YES), it terminates the installation process. Note that if the ECUs to be reprogrammed include an AP-compliant ECU, the UCM master 8 also sends the ECU ID of the ECU to be reprogrammed and the update program to the UCM 11 in step A26, and also sends an installation request to the UCM 11 in step A27.

[0040] (3-2) Installation process of the flushing adapter 9 (see Figure 13) When the flashing adapter 9 starts the installation process, it waits to receive the ECU ID of the ECU to be reproduced and the update program from the UCM master 8 (B21). When the flashing adapter 9 determines that it has received the ECU ID of the ECU to be reproduced and the update program sent from the UCM master 8 (B21: YES), it waits to receive an installation request from the UCM master 8 (B22). When the flashing adapter 9 determines that it has received the installation request sent from the UCM master 8 (B22: YES), it references the detailed information reference table based on the ECU ID of the ECU to be reproduced, and acquires detailed information about the ECU to be reproduced (B23, corresponding to the detailed information reference step).

[0041] When the flashing adapter 9 acquires the detailed information of the ECU to be reprogrammed, it performs the connection process described above. That is, the flashing adapter 9 transmits the ECU ID of the ECU to be reprogrammed to the programming IF 10 (B24), and waits to receive a connection ID from the programming IF 10 (B25). When the flashing adapter 9 determines that it has received the connection ID transmitted from the programming IF 10 (B25: YES, corresponding to the device identification information receiving procedure), it saves the received connection ID (B26). Note that if the flashing adapter 9 already holds the connection ID, it may skip steps B23 to B26.

[0042] The flushing adapter 9 sends the connection ID and an installation request to the programming IF 10 (B27, corresponding to the processing request sending procedure), and waits (B28) to receive an installation completion notification from the programming IF 10. When the flushing adapter 9 determines that it has received the installation completion notification sent from the programming IF 10 (B28: YES), it sends the received installation completion notification to the UCM master 8 (B29), and ends the installation process.

[0043] (3-3) Programming IF10 installation process (see Figure 14) When the programming IF10 starts the installation process, it performs the connection process described above. That is, the programming IF10 waits to receive the ECU ID of the reprogramming target ECU from the flashing adapter 9 (C21). When the programming IF10 determines that it has received the ECU ID of the reprogramming target ECU transmitted from the flashing adapter 9 (C21: YES), it identifies the destination reprogramming target ECU based on the received ECU ID of the reprogramming target ECU, and connects to the identified destination reprogramming target ECU (C22).

[0044] The programming IF 10 transmits the connection ID to the flashing adapter 9 (C23) and waits to receive the connection ID and an installation request from the flashing adapter 9 (C24). If the programming IF 10 determines that it has received the connection ID and installation request transmitted from the flashing adapter 9 (C24: YES), it transmits an installation instruction to the ECU to be reprogrammed based on the ECU ID corresponding to the received connection ID (C25) and waits to receive an installation completion notification from the ECU to be reprogrammed (C26).

[0045] In this case, when the reprogramming target ECU receives the installation instruction sent from the programming IF 10, it installs the update program, and when installation of the update program is completed, it sends an installation completion notice to the programming IF 10. When the programming IF 10 determines that it has received the installation completion notice sent from the reprogramming target ECU (C26: YES), it sends the received installation completion notice to the flashing adapter 9 (C27) and ends the installation process. As described above, the control unit 5 executes the process flow shown in FIG. 15 during installation.

[0046] (4) Activation process (see Figures 16 to 19) (4-1) UCM Master 8 activation process (see Figure 16) When the UCM master 8 starts the activation process, it waits to receive the ECU ID of the ECU to be reproduced from the OTA client 7 (A31). When the UCM master 8 determines that it has received the ECU ID of the ECU to be reproduced sent from the OTA client 7 (A31: YES), it waits to receive an activation request from the OTA client 7 (A32). When the UCM master 8 determines that it has received the activation request sent from the OTA client 7 (A32: YES), it identifies the activation request destination based on the mapping information (A33).

[0047] The UCM master 8 sends the ECU ID of the ECU to be reprogrammed to the flashing adapter 9 (A34), sends an activation request to the flashing adapter 9 (A35), and waits to receive an activation completion notification from the flashing adapter 9 (A36). If the UCM master 8 determines that it has received the activation completion notification sent from the flashing adapter 9 (A36: YES), it ends the activation process. Note that if the ECUs to be reprogrammed include an AP-compliant ECU, the UCM master 8 also sends an activation request to the UCM 11 in step A35.

[0048] (4-2) Activation process of the flashing adapter 9 (see Figure 17) When the flashing adapter 9 starts the activation process, it waits to receive the ECU ID of the ECU to be reproduced from the UCM master 8 (B31). When the flashing adapter 9 determines that it has received the ECU ID of the ECU to be reproduced sent from the UCM master 8 (B31: YES), it waits to receive an activation request from the UCM master 8 (B32). When the flashing adapter 9 determines that it has received the activation request sent from the UCM master 8 (B32: YES), it references the detailed information reference table based on the ECU ID of the ECU to be reproduced, and acquires detailed information about the ECU to be reproduced (B33, corresponding to the detailed information reference step).

[0049] When the flashing adapter 9 acquires the detailed information of the ECU to be reprogrammed, it performs the connection process described above. That is, the flashing adapter 9 transmits the ECU ID of the ECU to be reprogrammed to the programming IF 10 (B34), and waits to receive a connection ID from the programming IF 10 (B35). When the flashing adapter 9 determines that it has received the connection ID transmitted from the programming IF 10 (B35: YES, corresponding to the device identification information receiving procedure), it saves the received connection ID (B36). Note that if the flashing adapter 9 already holds the connection ID, it may skip steps B33 to B36.

[0050] The flushing adapter 9 sends the connection ID and an activation request to the programming IF 10 (B37, corresponding to the processing request sending procedure), and waits (B38) to receive an activation completion notification from the programming IF 10. When the flushing adapter 9 determines that it has received the activation completion notification sent from the programming IF 10 (B38: YES), it sends the received activation completion notification to the UCM master 8 (B39), and ends the activation process.

[0051] (4-3) Activation process of programming IF10 (see Figure 18) When the activation process begins, the programming IF10 performs the connection process described above. That is, the programming IF10 waits to receive the ECU ID of the reprogramming target ECU from the flashing adapter 9 (C31). When the programming IF10 determines that the ECU ID of the reprogramming target ECU transmitted from the flashing adapter 9 has been received (C31: YES), the programming IF10 identifies the destination reprogramming target ECU based on the received ECU ID of the reprogramming target ECU, and connects to the identified destination reprogramming target ECU (C32).

[0052] The programming IF10 sends the connection ID to the flashing adapter 9 (C33) and waits to receive the connection ID and an activate request from the flashing adapter 9 (C34). If the programming IF10 determines that it has received the connection ID and activate request sent from the flashing adapter 9 (C34: YES), it sends an activate instruction to the reprogramming target ECU based on the ECU ID corresponding to the received connection ID (C35) and waits to receive an activation completion notification from the reprogramming target ECU (C36).

[0053] In this case, when the reprogramming target ECU receives the activate instruction sent from the programming IF 10, it activates the update program, and when activation of the update program is completed, it sends an activation completion notification to the programming IF 10. When the programming IF 10 determines that it has received the activation completion notification sent from the reprogramming target ECU (C36: YES), it sends the received activation completion notification to the flashing adapter 9 (C37) and ends the activation process. As described above, the control unit 5 executes the process flow shown in FIG. 19 at the time of activation.

[0054] (5) Table update process (see Figures 20 and 21) (5-1) UCM Master 8 table update process (see Figure 20) When the UCM master 8 starts the table update process, it waits to receive an instruction to update the UCMID reference table (A41) and also waits to receive an instruction to update the connection destination reference table (A42). When the UCM master 8 determines that it has received an instruction to update the UCMID reference table (A41: YES), it updates the UCMID reference table (A43) and ends the table update process. When the UCM master 8 determines that it has received an instruction to update the connection destination reference table (A42: YES), it updates the connection destination reference table (A44) and ends the table update process.

[0055] (5-2) Table update process for the flushing adapter 9 (see Figure 21) When the flushing adapter 9 starts the table update process, it waits for reception of an instruction to update the detailed information reference table (B41). When the flushing adapter 9 determines that an instruction to update the detailed information reference table has been received (B41: YES), it updates the detailed information reference table (B42) and ends the table update process.

[0056] As described above, according to this embodiment, the following advantageous effects can be obtained. The master ECU 1 holds a detailed information reference table, and when it receives an ECU ID that can identify a CP-compliant ECU as a reprogramming target from the UCM master 8, it references the detailed information and sends a processing request to the CP-compliant ECU based on the detailed information via the programming IF 10. This allows the reprogramming to be carried out appropriately by appropriately sending the processing request to the CP-compliant reprogramming target ECU.

[0057] The master ECU1 is configured to send a request to obtain version information as a processing request. This allows software version information to be properly obtained from CP-compliant reprogramming target ECUs. The master ECU1 is configured to send a request to install an update program as a processing request. This allows the update program to be properly installed in CP-compliant reprogramming target ECUs. The master ECU1 is configured to send a request to activate the update program as a processing request. This allows the update program to be properly activated in CP-compliant reprogramming target ECUs.

[0058] Although the present disclosure has been described with reference to the embodiments, it is understood that the present disclosure is not limited to the embodiments or structures. The present disclosure also encompasses various modifications and modifications within the scope of equivalents. In addition, various combinations and forms, as well as other combinations and forms including only one element, more than one element, or less than one element, are also within the scope and spirit of the present disclosure.

[0059] The control unit and the method described herein may be implemented by a special-purpose computer configured by configuring a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the control unit and the method described herein may be implemented by a special-purpose computer configured by configuring a processor with one or more dedicated hardware logic circuits. Alternatively, the control unit and the method described herein may be implemented by one or more special-purpose computers configured by combining a processor and memory programmed to perform one or more functions with a processor configured with one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by a computer on a computer-readable non-transitory tangible storage medium. [Explanation of symbols]

[0060] In the drawing, 1 is a master ECU (electronic control unit), 3 is an ECU to be reproduced, 5 is a control unit, 8 is a UCM master, 9 is a flashing adapter, 10 is a programming IF, and 13 is a second table memory unit (detailed information storage unit).

Claims

1. A UCM master (8) that transmits device identification information that can identify an electronic control device to be reproduced; a detailed information storage unit (13) for storing detailed information of a connection destination required to transmit a processing request to an electronic control device to be reproduced, the electronic control device being identified by the device identification information; a flashing adapter (9) that, upon receiving device identification information from the UCM master that can identify an electronic control device that conforms to a predetermined platform as a repro target, refers to the detailed information stored in the detailed information storage unit and transmits the processing request and the detailed information to a programming IF; and a programming IF (10) for transmitting the processing request to an electronic control device that conforms to a predetermined platform based on the detailed information.

2. 2. The electronic control unit according to claim 1, wherein the UCM master transmits, as the processing request, a processing request for acquiring version information of software stored in the electronic control unit to be reproduced.

3. 2. The electronic control unit according to claim 1, wherein the UCM master transmits a processing request relating to installation of an update program as the processing request.

4. 2. The electronic control unit according to claim 1, wherein the UCM master transmits a processing request relating to activation of an update program as the processing request.

5. 2. The electronic control device according to claim 1, wherein the detailed information holding unit holds information including an IP address, a CANID, and a port as the detailed information.

6. The electronic control device according to any one of claims 1 to 5, wherein the electronic control device conforming to the predetermined platform is an electronic control device conforming to an Autozer Classic platform.

7. In the electronic control device (1), a device identification information receiving step for receiving device identification information capable of identifying an electronic control device that conforms to a predetermined platform as a repro target; a detailed information reference step for referencing detailed information of a connection destination required to transmit a processing request to an electronic control device to be reproduced, the detailed information being identified by the device identification information; a processing request transmission procedure for transmitting the processing request and the detailed information to a programming IF; and a procedure for transmitting the processing request to an electronic control device that conforms to a predetermined platform based on the detailed information.

8. A control unit (5) of the electronic control device (1) a device identification information receiving step for receiving device identification information capable of identifying an electronic control device that conforms to a predetermined platform as a repro target; a detailed information reference step for referencing detailed information of a connection destination required to transmit a processing request to an electronic control device to be reproduced, the detailed information being identified by the device identification information; a processing request transmission procedure for transmitting the processing request and the detailed information to a programming IF; and a reproduction execution program that executes a procedure of transmitting the processing request to an electronic control device that conforms to a predetermined platform based on the detailed information.

Images