JP6558264B2 - Vehicle data communication system - Google Patents

Description

  The present invention relates to a vehicle data communication system.

  Conventionally, an electronic control device functioning as a gateway (hereinafter referred to as G / WECU), a rewrite target ECU that rewrites a program by writing rewrite data received from the rewrite tool via the G / WECU (ie, reprograms) There is provided a vehicular data communication system (see, for example, Patent Document 1).

Japanese Patent No. 5363192

  The rewriting target ECU receives and specifies a request message (for example, a message defined in ISO14229) defined in the rewriting service function specification from the rewriting tool via the G / WECU. Then, the rewrite target ECU rewrites the program by writing the rewrite data received from the rewrite tool via the G / WECU. Therefore, in the rewriting target ECU, as rewriting software stored in the ROM, a rewriting service function (that is, a reprogram service function) for executing requests for various service functions, and a rewriting function for rewriting a program (that is, a reprogram function); Need to be stored.

  However, in the configuration in which the rewriting service function and the rewriting function are stored in the rewriting software of the ECU to be rewritten, when the ECU is newly installed in the vehicle, the rewriting service function and the rewriting function are also included in the rewriting software of the ECU. And need to be stored. For this reason, there are problems that man-hours and costs required for development of the rewriting software increase, and that the area that can be used by the application software is restricted due to the increase of the area occupied by the rewriting software in the ROM area.

  The present invention has been made in view of the above circumstances, and its purpose is to reduce the man-hours and costs required for development of rewriting software for the rewriting target ECU and to be used in application software in the ROM area of the rewriting target ECU. It is an object of the present invention to provide a vehicular data communication system capable of reducing restrictions on possible areas.

According to the first aspect of the present invention, the gateway electronic control unit (2) includes a rewriting service function (251a) for executing various service function requests and a rewriting function (253a, 253b) for rewriting a program. And a rewrite function transfer function (251e) and a rewrite request transfer function (251f). When the gateway electronic control unit receives a rewrite request from the rewrite tool (6), it transmits the rewrite request to the rewrite target electronic control unit (3, 4) using the rewrite request transfer function, and the rewrite function is transferred to the rewrite function. It is transmitted to the electronic control device to be rewritten using the function. The rewrite target electronic control device uses the rewrite function received from the gateway electronic control device and rewrites the program by writing the rewrite data received from the rewrite tool via the gateway electronic control device.

  The rewriting service function and the rewriting function are integrated into the gateway electronic control device, and these functions are omitted from the rewriting target electronic control device, and those functions are not stored in the rewriting software of the rewriting target electronic control device. Thereby, even when it is going to mount ECU newly in a vehicle, it becomes unnecessary to store the rewriting service function and the rewriting function in the rewriting software of the ECU. As a result, it is possible to reduce the man-hours and costs required for developing rewriting software for the rewriting target electronic control device, and it is possible to reduce restrictions on the area that can be used by the application software in the ROM area of the rewriting target electronic control device.

Functional block diagram showing a first embodiment of the present invention The figure which shows the structure of ROM and RAM Sequence Diagram Sequence Diagram The figure which shows the structure of ROM and RAM Diagram showing the configuration of the rewrite function Sequence Diagram Sequence Diagram The flowchart which shows the main process of G / WECU The flowchart which shows the CAN reception control processing of G / WECU The flowchart which shows the CAN transmission control processing of G / WECU Flow chart showing G / WECU rewrite service processing (application software) Flowchart showing G / WECU rewrite service process (rewrite software) The flowchart which shows the acknowledgment process of G / WECU The flowchart which shows the negative response process of G / WECU The flowchart which shows the rewrite request processing of G / WECU The flowchart which shows the rewriting function transfer process of G / WECU Flowchart showing G / WECU security unlocking preparation request processing Flow chart showing security unlock request processing of G / WECU Flowchart showing G / WECU program erasure request processing Flowchart showing download request processing of G / WECU Flowchart showing data transfer request processing of G / WECU The flowchart which shows the data transfer completion request processing of G / WECU Flow chart showing program validity request processing of G / WECU The flowchart which shows ECU reset request processing of G / WECU The flowchart which shows the rewrite request transfer process of G / WECU The flowchart which shows the main process of rewriting object ECU The flowchart which shows the CAN reception control processing of ECU for rewriting The flowchart which shows CAN transmission control processing of ECU for rewriting Flow chart showing data storage processing of ECU to be rewritten The flowchart which shows the affirmative response process of ECU for rewriting The flowchart which shows the negative response process of ECU for rewriting Flowchart showing rewrite function processing of ECU to be rewritten Flowchart showing the rewriting process of the ECU to be rewritten Flowchart showing program erasure process of ECU to be rewritten Flowchart showing download processing of ECU to be rewritten Flow chart showing the writing process of the ECU to be rewritten The flowchart which shows the write completion process of ECU for rewriting Flowchart showing program validity confirmation processing of ECU to be rewritten Flowchart showing reset process of ECU to be rewritten Diagram showing how the rewrite function is sent The figure which shows the aspect by which the rewriting function of the 2nd Embodiment of this invention is transmitted.

(First embodiment)
Hereinafter, a first embodiment of the present invention will be described with reference to FIGS. The vehicle data communication system 1 includes an electronic control unit (hereinafter referred to as G / WECU) 2 that functions as a gateway, and rewrite target ECUs 3 and 4 that receive rewrite data from the G / WECU 2 and rewrite a program. In the present embodiment, a configuration having two rewrite target ECUs, ie, a first rewrite target ECU 3 and a second rewrite target ECU 4 is illustrated as the rewrite target ECU. However, the rewrite target ECU includes three or more rewrite target ECUs. It may be configured. The G / WECU 2 and the rewrite target ECUs 3 and 4 are connected via a local CAN bus 5. The G / WECU 2 can be connected to a rewriting tool 6 operated by an operator who performs a program rewriting operation. The G / WECU 2 and the rewriting tool 6 are connected via a global CAN bus 7.

  The G / WECU 2 includes an MCU 21 including a microcomputer and a CAN transceiver 22. The MCU 21 has a CAN communication function 23, a flash function 24, a ROM 25, and a RAM 26, and controls the operation of the G / WECU 2. The CAN transceiver 22 controls data communication between the local CAN bus 5 and the global CAN bus 7 by a communication protocol defined by CAN. The function means a module that executes a specific program and performs a specific process.

  The first rewrite target ECU 3 includes a first MCU 31 including a microcomputer and a CAN transceiver 32. The first MCU 31 includes a CAN communication function 33, a flash function 34, a ROM 35, and a RAM 36, and controls the operation of the first rewriting target ECU 3. The CAN transceiver 32 controls data communication with the local CAN bus 5 according to a communication protocol defined by CAN. The second rewrite target ECU 4 has a configuration equivalent to that of the first rewrite target ECU 3, and includes a second MCU 41 including a microcomputer and a CAN transceiver 42. The second MCU 41 has a CAN communication function 43, a flash function 44, a ROM 45, and a RAM 46. The CAN transceiver 42, the CAN communication function 43, the flash function 44, the ROM 45, and the RAM 46 are the same as the CAN transceiver 32, the CAN communication function 33, the flash function 34, the ROM 35, and the RAM 36, respectively.

  Hereinafter, an aspect of storing a rewriting service function and a rewriting function, which are functions necessary for rewriting a program, will be described. The function means a module that executes a specific program and performs a specific process. In the following, a case where the program of the rewriting target ECU 3 is rewritten will be described, but the same applies to the case where the program of the rewriting target ECU 4 is rewritten. FIG. 2 shows a configuration in which a rewriting service function and a rewriting function are stored in the rewriting software of the rewriting target ECU 3.

  In the G / WECU 2, rewriting software 251 and application software 252 are stored in the ROM 25 of the MCU 21. The rewriting software 251 stores a rewriting service function 251a, a data storage function 251b, a CAN communication control function 251c, and a rewriting function 251d. The application software 252 stores a message transfer function 252a, a CAN communication control function 252b, and a rewrite service function 252c.

  In the rewriting target ECU 3, rewriting software 351 and application software 352 are stored in the ROM 35 of the MCU 31. The rewriting software 351 stores a rewriting service function 351a, a data storage function 351b, a CAN communication control function 351c, and a rewriting function 351d. The application software 352 stores a CAN communication control function 352a and a rewrite service function 352b. The RAM 36 stores a rewrite function 351d of the ROM 35 by a data storage function 351b. In such a configuration, the program of the rewrite target ECU 3 is rewritten according to the sequence shown in FIGS. 3 and 4.

  When the rewriting tool 6 receives a program rewriting operation from an operator while being connected to the G / WECU 2 via the global CAN bus 7, the rewriting tool 6 prepares for enabling the rewriting gateway function. Start with. When the rewriting tool 6 completes the preparation normally, the rewriting tool 6 transmits a rewriting request to the G / WECU 2 with the SID as “10”, for example. When the G / WECU 2 receives the rewrite request from the rewrite tool 6, the G / WECU 2 transmits the received rewrite request to the rewrite target ECU 3. When the rewrite target ECU 3 receives the rewrite request from the G / WECU 2, the rewrite function 351 d is stored in the RAM 36 using the data storage function 351 b and an affirmative response is transmitted to the G / WECU 2. When the G / WECU 2 receives a positive response from the rewrite target ECU 3, the G / WECU 2 transmits the received positive response to the rewrite tool 6.

  Next, the rewriting tool 6 transmits a security unlocking preparation request to the G / WECU 2 with the SID “27”, for example. When the G / WECU 2 receives the security unlocking preparation request from the rewriting tool 6, the G / WECU 2 transmits the received security unlocking preparation request to the rewriting target ECU 3. When the rewrite target ECU 3 receives the security unlocking preparation request from the G / WECU 2, the rewrite target ECU 3 generates a seed and transmits an affirmative response including the generated seed to the G / WECU 2. When the G / WECU 2 receives a positive response from the rewrite target ECU 3, the G / WECU 2 transmits the received positive response to the rewrite tool 6.

Next, the rewriting tool 6 transmits a security unlocking request to the G / WECU 2 with the SID “27”, for example. When the G / WECU 2 receives the security unlock request from the rewrite tool 6, the G / WECU 2 transmits the received security unlock request to the rewrite target ECU 3. When the rewrite target ECU 3 receives the security unlock request from the G / WECU 2, the rewrite target ECU 3 transmits an affirmative response including the received key matching result to the G / WECU 2. When the G / WECU 2 receives a positive response from the rewrite target ECU 3, the G / WECU 2 transmits the received positive response to the rewrite tool 6.

  Next, the rewriting tool 6 transmits a program erasure request to the G / WECU 2 with the SID “31”, for example. When the G / WECU 2 receives the program erasure request from the rewrite tool 6, the G / WECU 2 transmits the received program erasure request to the rewrite target ECU 3. When receiving the program erasure request from the G / WECU 2, the rewrite target ECU 3 erases the ROM area to be rewritten using the rewrite function 351 d and transmits an affirmative response to the G / WECU 2. When the G / WECU 2 receives a positive response from the rewrite target ECU 3, the G / WECU 2 transmits the received positive response to the rewrite tool 6.

  Next, the rewriting tool 6 transmits a download request to the G / WECU 2 with the SID, for example, “34”. When the G / WECU 2 receives a download request from the rewriting tool 6, the G / WECU 2 transmits the received download request to the rewriting target ECU 3. When the rewrite target ECU 3 receives a download request from the G / WECU 2, the rewrite target ECU 3 acquires the rewrite target area (address and size) and transmits an affirmative response to the G / WECU 2. When the G / WECU 2 receives a positive response from the rewrite target ECU 3, the G / WECU 2 transmits the received positive response to the rewrite tool 6.

  Next, the rewriting tool 6 transmits a data transfer request including rewritten data to the G / WECU 2 with the SID “36”, for example. When the G / WECU 2 receives the data transfer request from the rewriting tool 6, the G / WECU 2 transmits the received data transfer request to the rewriting target ECU 3. When the data transfer request is received from the G / WECU 2, the rewrite target ECU 3 writes the rewrite data included in the data transfer request in the ROM area using the rewrite function 351 d and transmits an affirmative response to the G / WECU 2. When the G / WECU 2 receives a positive response from the rewrite target ECU 3, the G / WECU 2 transmits the received positive response to the rewrite tool 6.

  Next, when the rewrite tool 6 completes the transmission of all the rewrite data, the rewrite tool 6 transmits a data transfer completion request to the G / WECU 2 with the SID “37”, for example. When the G / WECU 2 receives the data transfer completion request from the rewriting tool 6, the G / WECU 2 transmits the received data transfer completion request to the rewriting target ECU 3. When the rewrite target ECU 3 receives the data transfer completion request from the G / WECU 2, the rewrite target ECU 3 completes the writing of the rewrite data and transmits an affirmative response to the G / WECU 2. When the G / WECU 2 receives a positive response from the rewrite target ECU 3, the G / WECU 2 transmits the received positive response to the rewrite tool 6.

  Next, the rewriting tool 6 transmits a program validity request to the G / WECU 2 with the SID “31”, for example. When the G / WECU 2 receives the program validity request from the rewriting tool 6, the G / WECU 2 transmits the received program validity request to the rewriting target ECU 3. When the rewrite target ECU 3 receives the program validity request from the G / WECU 2, the rewrite target ECU 3 transmits an affirmative response including the validity of the write result such as a checksum or CRC to the G / WECU 2. When the G / WECU 2 receives a positive response from the rewrite target ECU 3, the G / WECU 2 transmits the received positive response to the rewrite tool 6.

  Next, the rewriting tool 6 transmits an ECU reset request to the G / WECU 2 with the SID as “11”, for example. When the G / WECU 2 receives the ECU reset request from the rewriting tool 6, the G / WECU 2 transmits the received ECU reset request to the rewriting target ECU 3. When the ECU 3 to be rewritten receives an ECU reset request from the G / WECU 2, it sends an affirmative response to the G / WECU 2 to perform the reset. When the G / WECU 2 receives a positive response from the rewrite target ECU 3, the G / WECU 2 transmits the received positive response to the rewrite tool 6.

  In such a configuration in which the rewriting service function 351a and the rewriting function 351d are stored in the rewriting software 351 of the rewriting target ECU 3, the rewriting service function 351a and the rewriting function 351d are used to rewrite the program. For this reason, as described in [Problems to be Solved by the Invention], the man-hour and cost required for development of the rewriting software 351 increase, and the area occupied by the rewriting software 351 in the area of the ROM 35 increases. There is a problem that the area that can be used by the application software 352 is restricted. In order to solve such a problem, the present invention consolidates the rewriting service function and the rewriting function in the G / WECU 2. FIG. 5 shows a configuration in which the rewriting service function and the rewriting function are collected and stored in the G / WECU 2.

  In the G / WECU 2, transfer data 253 is stored in the ROM 25 of the MCU 21 in addition to the above-described rewrite software 251 and application software 252. The rewrite software 251 stores a rewrite function transfer function 251e and a rewrite request transfer function 251f in addition to the rewrite service function 251a, the data storage function 251b, the CAN communication control function 251c, and the rewrite function 251d. ing. The transfer data 253 stores a first MCU rewrite function 253a and a second MCU rewrite function 253b. The RAM 26 stores the rewrite function 251d of the ROM 25 by the data storage function 251b.

  The first MCU rewriting function 253a and the second MCU rewriting function 253b are rewriting functions for rewriting a program, and each include header information and a program as shown in FIG. The header information is information that can identify the rewrite target ECU of the program transfer destination, and is a CANID that indicates an address on the local CAN bus 5.

  In the rewriting target ECU 3, rewriting software 351 and application software 352 are stored in the ROM 35 of the MCU 31. In the rewriting software 351, the above-described rewriting service function 351a and rewriting function 351d are omitted, and a data storage function 351b and a CAN communication control function 351c are stored. The application software 352 omits the above-described rewrite service function 352b, and stores a CAN communication control function 352a and a data storage function 352c. In the RAM 36, the first MCU rewriting function 253a of the ROM 25 of the G / WECU 2 is stored by the data storage function 351b.

  When the software configuration shown in FIG. 2 is compared with the software configuration shown in FIG. 5, in FIG. 5, functions corresponding to the rewrite service functions 351a and 352b stored in the rewrite target ECU 3 shown in FIG. G / WECU 2 stores the rewrite service function 251a in an aggregated manner. The rewriting service function is basically a function developed in accordance with a request from the vehicle manufacturer, and the rewriting service functions 351a and 352b of the rewriting target ECU 3 are changed to the G / WECU 2 due to the fact that it is a specification common to the rewriting target ECUs 3 and 4. The rewrite service functions 251a can be stored together. In such a configuration, the program of the rewrite target ECU 3 is rewritten according to the sequence shown in FIGS.

  When the rewriting tool 6 receives a program rewriting operation from an operator while being connected to the G / WECU 2 via the global CAN bus 7, the rewriting tool 6 prepares for enabling the rewriting gateway function. Start with. When the rewriting tool 6 completes the preparation normally, the rewriting tool 6 transmits a rewriting request to the G / WECU 2 with the SID as “10”, for example. When the G / WECU 2 receives the rewrite request from the rewrite tool 6, the G / WECU 2 transmits the first MCU rewrite function 253a to the rewrite target ECU 3 using the rewrite function transfer function 251e. When receiving the first MCU rewriting function 253a from the G / WECU 2, the rewriting target ECU 3 stores the received first MCU rewriting function 253a in the RAM 36 and transmits an affirmative response to the G / WECU 2. When the G / WECU 2 receives a positive response from the rewrite target ECU 3, the G / WECU 2 transmits the received positive response to the rewrite tool 6.

  Next, the rewriting tool 6 transmits a security unlocking preparation request to the G / WECU 2 with the SID “27”, for example. When the G / WECU 2 receives the security unlocking preparation request from the rewriting tool 6, the G / WECU 2 generates a seed and transmits an acknowledgment including the generated seed to the rewriting tool 6. The G / WECU 2 responds the generated seed to the rewriting tool 6 by transmitting an affirmative response to the rewriting tool 6 to the G / WECU 2. Next, the rewriting tool 6 transmits a security unlocking request to the G / WECU 2 with the SID “27”, for example. When the G / WECU 2 receives the security unlock request from the rewriting tool 6, the G / WECU 2 transmits an acknowledgment including the received key matching result to the rewriting tool 6. In other words, the G / WECU 2 does not transmit the security unlocking preparation request and the security unlocking request to the rewriting target ECU 3, unlike the sequence described in FIG. 3 described above, and includes the generated seed and the matching result of the received key. The response is transmitted to the rewriting tool 6.

  Thereafter, the rewriting tool 6 sends a program erase request, a download request, a data transfer request, a data transfer completion request, a program validity request, and an ECU reset request in the same manner as in the sequence described with reference to FIGS. / Sequentially transmitted to WECU2. In the above-described series of sequences, the G / WECU 2 does not transmit information that does not require transmission to the rewrite target ECU 3, that is, security unlock preparation request and security unlock request request messages to the rewrite target ECU 3. The generated seed and the matching result of the received key are returned to the rewriting tool 6. On the other hand, the G / WECU 2 transmits information that needs to be transmitted to the rewrite target ECU 3, that is, a request message after the program erasure request, to the rewrite target ECU 3 using the rewrite request transfer function 251f. The received response is transmitted to the rewriting tool 6.

  The G / WECU 2 may transmit the request message received from the rewriting tool 6 to the rewriting target ECU 3 as it is when transmitting a request message after the program erasure request to the rewriting target ECU 3. The received request message may be changed, and a request message by a dedicated command using a unique communication protocol may be transmitted to the rewriting target ECU 3. When the request message defined in the rewrite service specification is used, it is necessary to change the rewrite function program every time the rewrite service specification is changed. On the other hand, by using a request message by a dedicated command, it is not necessary to change the program of the rewrite function even if the rewrite service specification is changed, and an appropriate response can be made to the change of the rewrite service specification. It becomes possible.

  Next, the operation of the above configuration will be described with reference to FIGS. Here, the process performed by the G / WECU 2 is shown in FIGS. 9 to 25, and the process performed by the rewrite target ECU 3 is shown in FIGS. Hereinafter, each process which G / WECU2 and rewriting object ECU3 perform is demonstrated.

(1) Processing performed by G / WECU 2 G / WECU 2 performs CAN communication control processing, rewriting service processing, response processing, rewriting request processing, rewriting function transfer processing, security unlocking preparation request processing, security unlocking request processing, and program deletion. Request processing, download request processing, data transfer request processing, data transfer completion request processing, program validity request processing, ECU reset request processing, and rewrite request transfer processing are performed. Hereinafter, each processing will be described.

(1-1) CAN Communication Control Process The G / WECU 2 performs a main process shown in FIG. 9, a CAN reception control process shown in FIG. 10, and a CAN transmission control process shown in FIG. 11 as the CAN communication control process.

  When starting the main process, the G / WECU 2 proceeds to the CAN reception control process (A1). When the G / WECU 2 starts the CAN reception control process, the G / WECU 2 determines whether or not a CAN signal has been received from the rewriting tool 6 (A11). If it determines that the CAN signal has been received (A11: YES), the G / WECU 2 performs the rewriting service process. Transition (A12). When the G / WECU 2 returns from the rewriting service process, the G / WECU 2 ends the CAN reception control process. Further, when starting the CAN transmission control process, the G / WECU 2 sets information in the transmission buffer in the CAN register (A21), transmits a CAN signal (A22), and ends the CAN transmission control process.

(1-2) Rewriting Service Process The G / WECU 2 performs a rewriting service process (application software) shown in FIG. 12 and a rewriting service process (rewriting software) shown in FIG. 13 as the rewriting service process.

  When the G / WECU 2 starts the rewriting service process (application software), the G / WECU 2 proceeds to the rewriting request process (A31). When the G / WECU 2 returns from the rewrite request process, the G / WECU 2 ends the rewrite service process (application software).

  When the G / WECU 2 starts the rewriting service process (rewriting software), the rewriting request process (A41), the security unlocking preparation request process (A42), the security unlocking request process (A43), the program deletion request process (A44), The process proceeds to a download request process (A45), a data transfer request process (A46), a data transfer completion request process (A47), a program validity request process (A48), and an ECU reset request process (A49). When the G / WECU 2 returns from the ECU reset request process, the G / WECU 2 ends the rewrite service process (rewrite software).

(1-3) Response Process The G / WECU 2 performs an affirmative response process shown in FIG. 14 and a negative response process shown in FIG. 15 as the response process. When starting the acknowledgment process, the G / WECU 2 sets the destination CANID and acknowledgment data in the transmission buffer (A51), and proceeds to the CAN transmission control process (A52). When the G / WECU 2 returns from the CAN transmission control process, the G / WECU 2 ends the acknowledgment process. Further, when the negative response process is started, the G / WECU 2 sets the destination CANID and negative response data in the transmission buffer (A61), and proceeds to the CAN transmission control process (A62). When the G / WECU 2 returns from the CAN transmission control process, the G / WECU 2 ends the negative response process.

(1-4) Rewrite Request Process When the G / WECU 2 starts the rewrite request process shown in FIG. 16, it determines whether a rewrite request has been received from the rewrite tool 6 (A71). When the G / WECU 2 determines that the rewrite request has been received (A71: YES), the G / WECU 2 transitions from the application software 252 to the rewrite software 251 (A72), and the rewrite request is a request based on a physical address or a function address. Is specified (A73), and the process proceeds to the rewrite function transfer process (A74). The request based on the physical address is a rewrite request for one rewrite target ECU, and the request based on the function address is a rewrite request for all the rewrite target ECUs.

  When the G / WECU 2 returns from the rewrite function transfer process, the G / WECU 2 waits to receive a response from the write target ECU 3 (A75). When the G / WECU 2 determines that the response from the write target ECU 3 has been received (A75: YES), it determines whether the response is an affirmative response (A76). When the G / WECU 2 determines that the response is an affirmative response (A76: YES), the G / WECU 2 transmits an affirmative response to the rewrite tool 6 (A77) and ends the rewrite request process. On the other hand, when the G / WECU 2 determines that the response is not a positive response but a negative response (A76: NO), the G / WECU 2 transmits a negative response to the rewriting tool 6 (A78), and ends the rewriting request process.

(1-5) Rewrite Function Transfer Process When the G / WECU 2 starts the rewrite function transfer process shown in FIG. 17, the G / WECU 2 determines whether the rewrite target of the rewrite function is one ECU or all ECUs (A81). ). When the G / WECU 2 determines that the rewriting target of the rewriting function is one ECU (A81: YES), the G / WECU 2 searches for the rewriting function to be transferred based on the CANID of the transmission destination (A82), the CANID of the transmission destination, and the transfer target The rewrite function and rewrite function transfer ID are set in the transmission buffer (A83), and the process proceeds to the CAN transmission control process (A84). When the G / WECU 2 returns from the CAN transmission control process, the G / WECU 2 ends the rewrite function transfer process.

  On the other hand, when the G / WECU 2 determines that the rewriting target of the rewriting function is all ECUs (A81: NO), the G / WECU 2 determines whether the rewriting function has been transmitted to all the rewriting target ECUs (A85). If the G / WECU 2 determines that the rewrite function has not been transmitted to all the rewrite target ECUs (A85: NO), the G / WECU 2 sets the destination CANID, the rewrite function to be transferred, and the rewrite function transfer ID in the transmission buffer (A86). The process proceeds to the CAN transmission control process (A87). When the G / WECU 2 returns from the CAN transmission control process, the G / WECU 2 returns to Step A85. If the G / WECU 2 determines that the rewrite function has been transmitted to all the rewrite target ECUs (A85: YES), the G / WECU 2 ends the rewrite function transfer process.

(1-6) Security unlocking preparation request process When the G / WECU 2 starts the security unlocking preparation request process shown in FIG. 18, it determines whether or not a security unlocking preparation request has been received from the rewriting tool 6 (A91). ). When the G / WECU 2 determines that a security unlocking preparation request has been received from the rewriting tool 6 (A91: YES), the G / WECU 2 generates a seed (A92), and transmits the generated seed to the rewriting tool 6 (A93). The unlocking preparation request process ends.

(1-7) Security Unlocking Request Process When the G / WECU 2 starts the security unlocking request process shown in FIG. 19, it determines whether a security unlocking request has been received from the rewriting tool 6 (A101). If it is determined that the security unlocking request has been received (A101: YES), the G / WECU 2 determines whether a security unlocking preparation request has been made (A102). If it is determined that the security unlocking preparation request has been made (A102: YES), the G / WECU 2 determines whether or not the received keys match (A103). When the G / WECU 2 determines that the received keys match (A103: YES), the G / WECU 2 transmits an affirmative response to the rewriting tool 6 (A104), and ends the security unlocking request process. On the other hand, if the G / WECU 2 determines that the security unlocking preparation request has not been made (A102: NO), or determines that the received keys do not match (A103: NO), it sends a negative response to the rewriting tool 6. (A105), the security unlock request processing is terminated.

(1-8) Program Erase Request Process When the G / WECU 2 starts the program erase request process shown in FIG. 20, the G / WECU 2 determines whether a program erase request has been received from the rewrite tool 6 (A111). When the G / WECU 2 determines that the program erasure request has been received (A111: YES), the G / WECU 2 proceeds to a rewrite request transfer process shown in FIG. 26 (A112). When the rewrite request transfer process is started, the G / WECU 2 determines that a program erase request has been received (A171: YES), and sets the destination CANID, erase start address, erase size, and erase ID in the transmission buffer (A172). ), The process proceeds to the CAN transmission control process (A173).

  When the G / WECU 2 returns from the CAN transmission control process, the G / WECU 2 ends the rewrite request transfer process and waits for reception of a response from the write target ECU 3 (A113). If the G / WECU 2 determines that the response from the write target ECU 3 has been received (A113: YES), it determines whether the response is an affirmative response (A114). When the G / WECU 2 determines that the response is an affirmative response (A114: YES), the G / WECU 2 transmits an affirmative response to the rewrite tool 6 (A115), and ends the program erase request process. On the other hand, when the G / WECU 2 determines that the response is not an affirmative response but a negative response (A114: NO), the G / WECU 2 transmits a negative response to the rewriting tool 6 (A116), and ends the program erase request process.

(1-9) Download Request Process When the G / WECU 2 starts the download request process shown in FIG. 21, the G / WECU 2 determines whether a download request has been received from the rewriting tool 6 (A121). If the G / WECU 2 determines that a download request has been received (A121: YES), the G / WECU 2 proceeds to a rewrite request transfer process shown in FIG. 26 (A122). When the rewrite request transfer process is started, the G / WECU 2 determines that a download request has been received (A174: YES), and sets the CANID, write start address, write size, and download ID of the transmission destination in the transmission buffer (A175). Then, the process proceeds to the CAN transmission control process (A176).

  When the G / WECU 2 returns from the CAN transmission control process, the G / WECU 2 ends the rewrite request transfer process and waits for reception of a response from the write target ECU 3 (A123). If the G / WECU 2 determines that the response from the write target ECU 3 has been received (A123: YES), it determines whether the response is an affirmative response (A124). When the G / WECU 2 determines that the response is an affirmative response (A124: YES), the G / WECU 2 transmits an affirmative response to the rewriting tool 6 (A125), and ends the download request process. On the other hand, when the G / WECU 2 determines that the response is not an affirmative response but a negative response (A124: NO), the G / WECU 2 transmits a negative response to the rewriting tool 6 (A126), and ends the download request process.

(1-10) Data Transfer Request Processing When starting the data transfer request processing shown in FIG. 22, the G / WECU 2 determines whether or not a data transfer request has been received from the rewriting tool 6 (A131). When the G / WECU 2 determines that the data transfer request has been received (A131: YES), the G / WECU 2 proceeds to the rewrite request transfer process shown in FIG. 26 (A132). When the rewrite request transfer process is started, the G / WECU 2 determines that a data transfer request has been received (A177: YES), sets the CANID, rewrite data, and data transfer ID of the transmission destination in the transmission buffer (A178), and CAN. The process proceeds to the transmission control process (A179).

  When the G / WECU 2 returns from the CAN transmission control process, the G / WECU 2 ends the rewrite request transfer process and waits for reception of a response from the write target ECU 3 (A133). When the G / WECU 2 determines that the response from the write target ECU 3 has been received (A133: YES), it determines whether or not the response is an affirmative response (A134). When the G / WECU 2 determines that the response is an affirmative response (A134: YES), the G / WECU 2 transmits an affirmative response to the rewriting tool 6 (A135), and ends the data transfer request process. On the other hand, when the G / WECU 2 determines that the response is not an affirmative response but a negative response (A134: NO), the G / WECU 2 transmits a negative response to the rewriting tool 6 (A136), and ends the data transfer request process.

(1-11) Data Transfer Completion Request Process When starting the data transfer completion request process shown in FIG. 23, the G / WECU 2 determines whether or not a data transfer completion request has been received from the rewriting tool 6 (A141). When the G / WECU 2 determines that the data transfer completion request has been received (A141: YES), the G / WECU 2 proceeds to the rewrite request transfer process shown in FIG. 26 (A142). When the rewrite request transfer process is started, the G / WECU 2 determines that a data transfer completion request has been received (A180: YES), sets the CANID of the transmission destination and the data transfer completion ID in the transmission buffer (A181), and transmits CAN. The process proceeds to control processing (A182).

  When the G / WECU 2 returns from the CAN transmission control process, the G / WECU 2 ends the rewrite request transfer process and waits for reception of a response from the write target ECU 3 (A143). When the G / WECU 2 determines that the response from the writing target ECU 3 has been received (A143: YES), the G / WECU 2 determines whether the response is an affirmative response (A144). When the G / WECU 2 determines that the response is an affirmative response (A144: YES), the G / WECU 2 transmits an affirmative response to the rewriting tool 6 (A145), and ends the data transfer completion request process. On the other hand, when the G / WECU 2 determines that the response is not an affirmative response but a negative response (A144: NO), the G / WECU 2 transmits a negative response to the rewriting tool 6 (A146), and ends the data transfer completion request processing.

(1-12) Program Validity Request Process When the G / WECU 2 starts the program validity request process shown in FIG. 24, it determines whether a program validity request has been received from the rewriting tool 6 (A151). When the G / WECU 2 determines that the program validity request has been received (A151: YES), the G / WECU 2 proceeds to a rewrite request transfer process shown in FIG. 26 (A152). When the rewrite request transfer process is started, the G / WECU 2 determines that the program validity request has been received (A183: YES), and sets the destination CANID, target address, target size, and program validity ID in the transmission buffer. (A184), the process proceeds to the CAN transmission control process (A185).

  When the G / WECU 2 returns from the CAN transmission control process, the G / WECU 2 ends the rewrite request transfer process and waits for a response from the write target ECU 3 (A153). When the G / WECU 2 determines that the response from the write target ECU 3 has been received (A153: YES), the G / WECU 2 determines whether or not the response is an affirmative response (A154). When the G / WECU 2 determines that the response is an affirmative response (A154: YES), the G / WECU 2 transmits an affirmative response to the rewriting tool 6 (A155), and ends the program validity request processing. On the other hand, when the G / WECU 2 determines that the response is not an affirmative response but a negative response (A154: NO), the G / WECU 2 transmits a negative response to the rewriting tool 6 (A156), and ends the program validity request processing.

(1-13) ECU Reset Request Process When the G / WECU 2 starts the ECU reset request process shown in FIG. 25, it determines whether or not an ECU reset request has been received from the rewriting tool 6 (A161). If it is determined that the ECU reset request has been received (A161: YES), the G / WECU 2 proceeds to a rewrite request transfer process shown in FIG. 26 (A162). When the G / WECU 2 starts the rewrite request transfer process, it determines that the ECU reset request has been received (A186: YES), sets the CANID and ECU reset ID of the transmission destination in the transmission buffer (A187), and the CAN transmission control process. (A188).

  When the G / WECU 2 returns from the CAN transmission control process, the G / WECU 2 ends the rewrite request transfer process and waits for reception of a response from the write target ECU 3 (A163). When the G / WECU 2 determines that the response from the write target ECU 3 has been received (A163: YES), it determines whether or not the response is an affirmative response (A164). When the G / WECU 2 determines that the response is an affirmative response (A164: YES), the G / WECU 2 transmits an affirmative response to the rewriting tool 6 (A165), and ends the ECU reset request process. On the other hand, when the G / WECU 2 determines that the response is not an affirmative response but a negative response (A164: NO), the G / WECU 2 transmits a negative response to the rewriting tool 6 (A166), and ends the ECU reset request process.

(2) Processing performed by the write target ECU 3 The write target ECU 3 includes a CAN communication control process, a data storage process, a response process, a rewrite function process, a program erase process, a download process, a write process, a write completion process, a program validity check process, Perform reset processing. Hereinafter, each processing will be described.

(2-1) CAN Communication Control Process The write target ECU 3 performs a main process shown in FIG. 27, a CAN reception control process shown in FIG. 28, and a CAN transmission control process shown in FIG. 29 as the CAN communication control process.

  The writing target ECU 3 starts the CAN reception control process when the main process is started (B1). When the writing target ECU 3 starts the CAN reception control process, it determines whether or not the CAN signal has been received from the G / WECU 2 (B11). If it is determined that the CAN signal has been received (B11: YES), the writing target ECU 3 performs the data storage process. Transition (B12). When the writing target ECU 3 returns from the data storage process, the CAN reception control process ends. When the CAN transmission control process is started, the write target ECU 3 sets information in the transmission buffer in the CAN register (A21), transmits a CAN signal (B22), and ends the CAN transmission control process.

(2-2) Data Storage Process When the write target ECU 3 starts the data storage process shown in FIG. 30, it determines whether or not the first MCU rewriting function 253a is received from the G / WECU 2 (B31). When the writing target ECU 3 determines that the first MCU rewriting function 253a has been received (B31: YES), it stores the received first MCU rewriting function 253a in the RAM 36 (B32), and sends an affirmative response to the G / WECU 2. It transmits (B33) and shifts to the rewrite function process (B34). When the write target ECU 3 returns from the rewrite function process, the data storage process ends.

(2-3) Response Process The write target ECU 3 performs an affirmative response process shown in FIG. 31 and a negative response process shown in FIG. 32 as the response process. When the write target ECU 3 starts the acknowledgment process, it sets the CANID and acknowledgment data of the transmission destination in the transmission buffer (B41), and proceeds to the CAN transmission control process (B42). When returning from the CAN transmission control process, the write target ECU 3 ends the acknowledgment process. Further, when starting the negative response process, the write target ECU 3 sets the CANID and negative response data of the transmission destination in the transmission buffer (B51), and proceeds to the CAN transmission control process (B52). When returning from the CAN transmission control process, the writing target ECU 3 ends the negative response process.

(2-4) Rewriting Function Process When the writing target ECU 3 starts the rewriting function process shown in FIG. 33, it determines whether or not a CAN signal has been received (B61). When the writing target ECU 3 determines that the CAN signal has been received (B61: YES), the writing target ECU 3 proceeds to the rewriting process shown in FIG. 34 (B62). When returning from the rewriting process, the writing target ECU 3 determines whether or not all the rewriting processes have been completed (B63). The writing target ECU 3 determines the condition for determining that all the rewriting processes have been completed depending on whether or not to implement a reset process (B82) in the rewriting process described later. When the reset process is performed, the writing target ECU 3 determines that the rewrite process has been completed when the reset process is normally completed. However, in that case, a reset occurs in the reset process and restarts from the beginning of the program, so the rewrite function process is not returned. On the other hand, when the reset process is not performed, the write target ECU 3 determines that all the rewrite processes have been completed when the program validity confirmation process (B80) in the rewrite process to be described later has been completed normally. When the writing target ECU 3 determines that all the rewriting processes have been completed (B63: YES), the rewriting function process is terminated.

  When the rewriting process is started, the writing target ECU 3 determines which request is the received CAN signal. When it is determined that the program erasure request has been received (B71: YES), the write target ECU 3 proceeds to the program erasure process (B72), and when it is determined that the download request has been received (B73: YES), the write target ECU 3 proceeds to the download process (B73: YES). B74). When it is determined that the data transfer request has been received (B75: YES), the write target ECU 3 proceeds to the write process (B76), and when it is determined that the data transfer completion request has been received (B77: YES), the process proceeds to the write completion process. (B78). When it is determined that the program validity request has been received (B79: YES), the writing target ECU 3 proceeds to the program validity confirmation process (B80), and when it is determined that the ECU reset request has been received (B81: YES), the reset process is performed. (B82). When the writing target ECU 3 returns from the respective processes, the rewriting process is terminated.

(2-5) Program Erase Processing When the program target ECU 3 starts the program erase processing shown in FIG. 35, the program target ECU 3 determines whether the erase target address and the erase size are appropriate (B91). If the write target ECU 3 determines that the erase target address and erase size are appropriate (B91: YES), the ROM area from the erase target address to the erase size is deleted (B92), and whether or not the program has been successfully erased. Is determined (B93). If the write target ECU 3 determines that the program has been successfully erased (B93: YES), it sends an affirmative response to the G / WECU 2 (B94), and the program erase process is terminated. On the other hand, if the write target ECU 3 determines that the program erasure has failed (B93: NO), it sends a negative response to the G / WECU 2 (B95), and ends the program erasure process. If the writing target ECU 3 determines that the erasing target address and the erasing size are not appropriate (B91: NO), in this case as well, a negative response is transmitted to the G / WECU 2 (B95), and the program erasing process is terminated.

(2-6) Download Process When the write target ECU 3 starts the download process shown in FIG. 36, the write target ECU 3 determines whether the write target address and the write size are appropriate (B101). When the write target ECU 3 determines that the write target address and the write size are appropriate (B101: YES), the write target ECU 3 stores the write target address and the write size in the RAM 36 (B102), and transmits an affirmative response to the G / WECU 2 (B103). ) The download process is terminated. On the other hand, when the write target ECU 3 determines that the write target address and the write size are not appropriate (B101: NO), it sends a negative response to the G / WECU 2 (B104) and ends the download process.

(2-7) Write Process When the write target ECU 3 starts the write process shown in FIG. 37, the rewrite data is written to the write target address (B111), and it is determined whether the rewrite data has been successfully written (B112). . If the write target ECU 3 determines that the rewrite data has been successfully written (B112: YES), the write target ECU 3 adds the current write size to the current write target address, and updates the current write target address in preparation for the next write process. (B113). The writing target ECU 3 subtracts the current writing size from the current writing size, updates the current writing size in preparation for the next writing process (B114), and sends an acknowledgment to the G / WECU 2 (B115). The process ends. On the other hand, when the writing target ECU 3 determines that the writing of the rewrite data has failed (B112: NO), the writing target ECU 3 transmits a negative response to the G / WECU 2 (B116) and ends the writing process.

(2-8) Write Completion Process When the write target ECU 3 starts the write completion process shown in FIG. 38, it determines whether or not the current write size is “0” (B121). When the writing target ECU 3 determines that the current writing size is “0” (B121: YES), the writing target ECU 3 transmits an affirmative response to the G / WECU 2 (B122), and ends the writing completion process. On the other hand, if the writing target ECU 3 determines that the current writing size is not “0” (B122: NO), it sends a negative response to the G / WECU 2 (B123), and ends the writing completion process.

(2-9) Program Validity Confirmation Processing The writing target ECU 3, when starting the program validity confirmation processing shown in FIG. 39, determines whether or not the validity confirmation target address and the target size are appropriate (B131). . When the write target ECU 3 determines that the validity check target address and the target size are appropriate (B131: YES), the write target ECU 3 performs the checksum calculation (B132), and the expected value of the checksum calculation stored in the rewrite data Is acquired (B133). The writing target ECU 3 collates the calculated value obtained by the checksum calculation with the expected value (B134), and when it is determined that they match (B134: YES), sends an affirmative response to the G / WECU 2 (B135). ), The program validity checking process is terminated. On the other hand, if the write target ECU 3 determines that the two do not match (B134: NO), it sends a negative response to the G / WECU 2 (B136) and ends the program validity checking process. If the write target ECU 3 determines that the validity check target address and the target size are not appropriate (B131: NO), a negative response is also sent to the G / WECU 2 in this case (B136), and the program validity check process is performed. Exit.

(2-10) Reset Process When the reset process shown in FIG. 40 is started, the write target ECU 3 determines whether the program is being erased or rewritten data is being written (B141). If the write target ECU 3 determines that the program is not being erased or rewritten data is not being written (B141: NO), it sends an affirmative response to the G / WECU 2 (B142), performs a reset (B143), and ends the reset process. To do. On the other hand, if the write target ECU 3 determines that the program is being erased or rewritten data is being written (B141: YES), a negative response is transmitted to the G / WECU 2 (B144), and the reset process is terminated.

  In the above-described configuration, the rewriting service function 251a and the MCU rewriting functions 253a and 253b are integrated in the G / WECU 2, so that the rewriting target ECU using the common MCU is the MCU held by the G / WECU 2. The rewriting functions 253a and 253b can be shared. That is, as shown in FIG. 41, the G / WECU 2 and the rewriting target ECUs 3 and 4 are connected via the local CAN bus 5 and the third rewriting target ECU 8 is connected via the local CAN bus 9 and the rewriting target. In the configuration in which the ECUs 3 and 8 use a common MCU, the MCU rewriting function 253a can be shared by the rewriting target ECUs 3 and 8.

As described above, according to the first embodiment, the following effects can be obtained.
In the vehicular data communication system 1, the rewriting service function 251 a and the MCU rewriting functions 253 a and 253 b are integrated into the G / WECU 2, and these functions are omitted from the rewriting target ECUs 3 and 4. The configuration is not stored in the rewriting software. Thereby, even when it is going to mount ECU newly in a vehicle, it becomes unnecessary to store the rewriting service function and the rewriting function in the rewriting software of the ECU. As a result, it is possible to reduce the man-hours and costs required to develop the rewriting software for the rewriting target ECUs 3 and 4, and to reduce the restrictions on the areas usable by the application software in the areas of the ROMs 35 and 45 of the rewriting target ECUs 3 and 4. .

  In addition, regarding the ECU to be rewritten using a common MCU, the MCU rewriting functions 253a and 253b held by the G / WECU 2 can be shared, and when the ECU is newly installed in the vehicle, the ECU If the MCU and the MCU of the ECU already mounted on the vehicle have the same specifications, the program can be rewritten without adding a new function. Furthermore, by using a request message by a dedicated command using a unique communication protocol as a request message after the program erasure request, it is not necessary to change the program of the rewrite function even if the rewrite service specifications are changed. Therefore, it is possible to appropriately cope with a change in the specification of the rewriting service.

(Second Embodiment)
Next, a second embodiment of the present invention will be described with reference to FIG. In addition, description is abbreviate | omitted about the same part as above-mentioned 1st Embodiment, and a different part is demonstrated. In the first embodiment, the rewriting service function 251a and the MCU rewriting functions 253a and 253b are integrated into the G / WECU 2, but in the second embodiment, the rewriting service function 251a is integrated into the G / WECU 2. The MCU rewriting functions 253a and 253b are integrated into the rewriting tool 6. In this case, the G / WECU 2 transmits the MCU rewriting functions 253 a and 253 b received from the rewriting tool 6 to the rewriting target ECUs 3 and 4. According to the second embodiment, the same effect as that of the first embodiment can be obtained. Further, by consolidating the MCU rewriting functions 253a and 253b into the rewriting tool 6, it is possible to reduce restrictions on the area that can be used by application software in the ROM 25 area of the G / WECU 2.

(Other embodiments)
The present invention is not limited to those exemplified in the above-described embodiment, and can be arbitrarily modified or expanded without departing from the scope thereof.
A configuration in which the MCU rewriting function is integrated into the G / WECU 2 and a configuration in which the MCU rewriting function is integrated into the rewriting tool 6 may be mixed. That is, in one vehicle communication system, one MCU rewriting function may be integrated into the G / WECU 2 and another MCU rewriting function may be integrated into the rewriting tool 6.

  In the drawings, 1 is a vehicle data communication system, 2 is a G / WECU (gateway electronic control device), 3 and 4 are rewrite target ECUs (rewrite target electronic control devices), 251a is a rewrite service function, and 251e is a rewrite function transfer function. 251f is a rewrite request transfer function, and 253a and 253b are MCU rewrite functions (rewrite functions).

Claims (3)

A gateway electronic control unit (2) that receives a rewrite request from the rewrite tool (6), and a rewrite target electronic control unit (3) that writes the rewrite data received from the rewrite tool via the gateway electronic control unit and rewrites the program. 4) and a vehicle data communication system (1) comprising:
The gateway electronic control unit includes a rewrite service function (251a) for executing various service function requests, a rewrite function (253a, 253b) for rewriting a program, a rewrite function transfer function (251e), and a rewrite request. When the rewrite request is received from the rewrite tool, the rewrite request is transmitted to the rewrite target electronic control device using the rewrite request transfer function, and the rewrite function is transferred to the rewrite function. Send to the electronic controller to be rewritten using the function transfer function,
The vehicular data communication system wherein the rewriting target electronic control device uses the rewriting function received from the gateway electronic control device and rewrites the program by rewriting data received from the rewriting tool via the gateway electronic control device. . The vehicle data communication system according to claim 1,
The gateway electronic control device is a vehicle data communication system in which the rewrite function is shared by a plurality of rewrite target electronic control devices. In the vehicle data communication system according to claim 1 or 2,
The gateway electronic control device is a vehicle data communication system for performing data communication including transmission of the rewrite data to the rewrite target electronic control device using a unique communication protocol .

Images