JP2001265601A - Electronic control device and memory rewriting method - Google Patents

Abstract

(57) [Summary] [PROBLEMS] To achieve both compatibility of a mask ROM and diversification of a program rewriting function. After being manufactured by an ECU manufacturer, an ECU (10) is delivered to a specific engine manufacturer (delivery destination), and then delivered to a plurality of vehicle manufacturers (OEM destinations) that are OEM destinations. The ECU 10 includes a CPU 1
1, a mask ROM 12, a flash ROM 13, and the like. The mask ROM 12 stores a first-stage boot program corresponding to the delivery destination tool 21 and a rewriting program started in response to a request from the delivery destination tool 21. The flash ROM 13 also has a second-stage boot program corresponding to the OEM destination tools 22 and 23, a rewriting program for each OEM destination that is started according to a request for each OEM destination, and various engine controls. A normal application program is stored for each block.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an electronic control unit and a memory rewriting method used for vehicle control and the like, and more particularly, to an electronic control unit having a mask ROM and a nonvolatile memory, which can meet the demands of a plurality of different tools. And an improved technique for suitably rewriting data in a nonvolatile memory.

[0002]

2. Description of the Related Art For example, an on-vehicle electronic control device (on-vehicle E
CU) generally includes a nonvolatile memory such as a flash ROM. When power is turned on, a boot program in the mask ROM is first executed to perform engine control operation, or when rewriting the flash ROM. It is determined whether there is. For example, JP-A-10-974
In Japanese Patent Publication No. 19, the E shown in the flowchart of FIG.
It is described that mode determination is performed at the time of power-on in CU-side processing (S300 in FIG. 4 of the same publication). In addition,
The boot program is stored in the mask ROM. The reason is that if the boot program is stored in the flash ROM, it may not be possible to rewrite the flash ROM if it is erased. It is.

FIG. 4 is a system configuration diagram of a vehicle-mounted ECU. 4, the on-vehicle ECU 30 includes a CPU 31.
, A mask ROM 32, a flash ROM 33, and an input / output interface (I / F) 34. The delivery destination tool 35 is connected to the CPU 31 via the I / F 34.

[0004] As shown in FIG.
2 stores a boot program and a rewrite program (reprogramming program) started in response to a request from the tool 35. As shown in FIG. 5B, the flash ROM 33 stores ordinary application programs for performing various engine controls and the like.

In the on-vehicle ECU 30 having the above-described structure, after the power is turned on, the CPU 31 first executes a boot program in the mask ROM 32, and determines whether or not to rewrite the flash ROM 33 according to a request from the tool 35 in the boot program. When rewriting is performed, the process proceeds to the corresponding rewriting program in the mask ROM 32 (circled numeral 1 in FIG. 5). If rewriting is not to be performed, the process proceeds to a normal application program in the flash ROM 33 (circled number 2 in FIG. 5).

Meanwhile, in recent years, so-called OEM supply, which supplies various industrial products under the brand of the other party, is becoming popular. In the automobile manufacturing industry, engines manufactured by engine manufacturers are supplied to a plurality of delivery destinations. Supplied to the OEM. FIG. 6 shows an ECU for engine control.
FIG. 3 is a schematic diagram showing a form of distribution in a vehicle manufacturing process, taking an (engine ECU) as an example. As shown in FIG.
The engine ECU manufactured by the U manufacturer M1 is delivered to the engine manufacturer M2.
A set of CUs is delivered to a plurality of vehicle manufacturers M3.

In such a case, in consideration of the configuration shown in FIGS. 4 and 5, in the ECU 30, a boot program having a rewriting function specific to each delivery destination (for each engine manufacturer M2) is arranged in the mask ROM 32. . Thus, the application program in the flash ROM 33 can be rewritten by the delivery-specific tool 35.

[0008]

Generally, flash R
An external tool for rewriting data in OM33 is
Different tools are used for each of the engine maker M2 and the individual vehicle maker M3, and tools unique to each are used. Therefore,
The boot program executed when the ECU is started is different for each manufacturer. JP-A-10-9741 described above
In the device disclosed in Japanese Patent Application Publication No. 9-93, the processes in S300 to S340 in FIG.

In order to realize the program rewriting (reprogramming) at each manufacturer in considering the distribution form of FIG. 6, a mask ROM 32 is provided for each OEM destination (vehicle manufacturer M3), and each mask R is
A boot program must be created for each OM32. In this case, the delivery destination (engine manufacturer M2)
OEM destination (vehicle manufacturer M3)
It also needs to be equipped with a rewrite function using a unique tool.
That is, when there are a plurality of OEM destinations, it is not allowed to mount the rewriting function of another OEM destination on the same mask ROM. Therefore, a plurality of mask ROMs are set, and a boot program and a rewriting program are stored in each mask ROM. . Therefore, the number of man-hours for production management is increased due to an increase in the number of product numbers and the like, which causes a problem in cost.

On the other hand, in order to share the mask ROM 32, it is conceivable to store all programs corresponding to tools of all OEM destinations (vehicle manufacturer M3) in the mask ROM 32 in advance. Therefore, it is not easy to cope with an increase in OEM destinations. After the vehicle is shipped, the vehicle manufacturer M3 flashes the flash ROM 32.
There has been a request to rewrite the data in the above, but a configuration in which all the programs are stored in the mask ROM 32 cannot meet this request.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and has as its object to realize an electronic device capable of achieving both the common use of a mask ROM and the wide variety of program rewriting functions. It is to provide a control device.

[0012]

According to the electronic control device of the present invention, one of boot programs corresponding to a plurality of tools is stored in a mask ROM, and the other boot program is stored in a nonvolatile memory. Stored. In this case, the boot program corresponding to the common tool of the electronic control device is stored in the mask ROM, so that the mask ROM
Can be realized. Further, by storing the other boot programs in the nonvolatile memory, it is possible to individually set the boot programs for the tools different from the common tool, even if the types are unspecified and many for each electronic control device. Can be. As a result, it is possible to achieve both a common mask ROM and a wide variety of program rewriting functions.

In the electronic control device according to the second aspect, the first boot program corresponding to the tool used at the specific first delivery destination is stored in the mask ROM, and the second boot program is stored in the mask ROM.
The second boot program corresponding to the tool used at the customer's delivery destination was stored in the non-volatile memory. According to this configuration, the first boot program is called by the tool at the specific first delivery destination, and the second boot program is called by the tool at the second delivery destination to be delivered thereafter.

In this case, by storing the first boot program in the mask ROM, it is possible to share the mask ROM for each of the same first delivery destinations. In addition, by storing the second boot program in the nonvolatile memory, a program rewriting function for each second delivery destination can be realized in the same electronic control device.

[0015] In particular, when there are a plurality of second delivery destinations, a boot program corresponding to each delivery destination tool is stored in a non-volatile memory, so that the second delivery destination is stored. Even when a plurality of boot programs are required for each destination, the second destination-specific program rewriting function can be realized. Therefore, it is possible to easily cope with an increase in the number of second delivery destinations, and to provide an electronic control device excellent in practicality.

In the electronic control unit according to the fourth aspect, the second boot program and the first boot program are stored in the nonvolatile memory.
And an application program that can be rewritten by at least one of the delivery-destination tools is stored in different blocks. In this case, since the second boot program and the application program in the non-volatile memory are separately stored, only one of the programs can be rewritten, and the versatility of the device is improved. I do.

According to a fourth aspect of the present invention, as described in the fifth aspect, the first boot program determines whether to rewrite a program stored in the nonvolatile memory including the second boot program, In the second boot program, it is preferable to determine whether to rewrite only the application program in the nonvolatile memory. That is, in the first delivery destination, the rewriting of data in the nonvolatile memory is not restricted, whereas in the second delivery destination, the rewriting of data in the nonvolatile memory is restricted to only the application program. In this case, at the first delivery destination, in addition to the rewriting of the application program, a boot program corresponding to the second delivery destination can be arbitrarily set for each second delivery destination. A rewriting function can be supported.

According to the present invention, the first delivery destination is a manufacturer of the engine or the vehicle-mounted device, and the second delivery destination is a vehicle manufacturer of the vehicle to which the engine or the vehicle-mounted device is supplied. In the electronic control device delivered to the vehicle manufacturer via the engine or vehicle-mounted device manufacturer, it is possible to achieve both the common use of the mask ROM and the wide variety of program rewriting functions.

The invention of claim 7 relates to a memory rewriting method. First, it is determined whether or not a rewriting request from a specific tool is made by a first-stage boot program stored in a mask ROM. Executes the request, and when there is no request, 2 stored in the flash ROM
The boot program at the stage determines whether there is a rewrite request from another tool different from the specific tool, and if there is a request, executes the request. According to the present invention, the boot program is executed in multiple stages, so that the rewriting function required each time can be correctly realized.

[0020]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings. In the present embodiment,
As an example, an engine ECU (electronic control device for engine control) distributed in the form shown in FIG. 6 has a function of rewriting various programs in a flash ROM. That is, an engine ECU manufactured by an ECU manufacturer
Are delivered to a specific engine maker (first delivery destination), and then OEM-received to a plurality of vehicle manufacturers (second delivery destination).
At this time, various programs in the flash ROM are arbitrarily rewritten by an engine manufacturer or a vehicle manufacturer. The details will be described below. In the following description, for convenience, one specific engine manufacturer is referred to as a “delivery destination” and a plurality of vehicle manufacturers are referred to as “O”.
EM destination ".

FIG. 1 is a block diagram showing the configuration of the ECU 10. In FIG. 1, an ECU 10 includes a CPU 11
, A mask ROM 12, a flash ROM 13, and input / output interfaces (I / Fs) 14, 15, and 16. The ECU 10 can be connected to a plurality of types of external tools, and the I / Fs 14 to 16 are provided according to the number and types of the external tools. For example, the delivery destination tool 21 used at the delivery destination (engine manufacturer)
An OEM destination tool 22, which is connected to the CPU 11 via the I / F 14 and used by the OEM destination (vehicle manufacturer).
Reference numeral 23 denotes the CPU 11 via I / Fs 15 and 16, respectively.
Connected to.

Here, the mask ROM 12 and the flash R
The storage contents of the OM 13 will be described with reference to FIG. As shown in FIG. 2A, the mask ROM 12 has
A first-stage boot program as a first boot program corresponding to the delivery destination tool 21 and a rewriting program started by the first-stage boot program in response to a request from the delivery destination tool 21 are stored. FIG.
As shown in (b), the OE is stored in the flash ROM 13.
A second-stage boot program as a second boot program corresponding to the M-destination tools 22 and 23, and an O booted by the second-stage boot program according to a request for each OEM destination
A rewrite program for each EM destination and a normal application program for performing various engine controls are stored for each block.

In such a configuration, the flash ROM 1
3 are all programs to be rewritten in the delivery destination tool 21, and
When a rewrite request is made by the program No. 1, the rewrite is appropriately performed by executing the delivery destination rewriting program in the mask ROM 12.

The normal application program in the flash ROM 13 is stored in the delivery destination tool 2 as described above.
1 and can be appropriately rewritten in accordance with the request of the delivery destination tool 21,
23 is a program to be rewritten, and is appropriately rewritten by executing an OEM destination rewriting program in the flash ROM 13.

FIG. 2 is different from the conventional configuration shown in FIG. 5 in that the boot program is multi-staged. In the first-stage boot program, it is determined whether or not to execute the rewrite program for the delivery destination. The first boot program determines whether to execute an OEM destination rewrite program. In this configuration, the first-stage boot program and the rewrite program corresponding to the specific delivery destination tool 21 cannot be rewritten. On the other hand, the second stage boot program and the rewriting program corresponding to the OEM destination tools 22 and 23 can be flexibly rewritten, and the setting can be arbitrarily changed.

Next, the flow of processing of the CPU 11 when the ECU is started will be described with reference to the flowchart of FIG. 3, first, in step 101, a boot program (first-stage boot program in FIG. 2) corresponding to the delivery destination tool 21 is called, and it is determined whether or not there is a rewrite request from the delivery destination tool 21. For example, when a predetermined rewrite switch on the delivery tool 21 side is turned on and a rewrite request is issued, a signal line connecting the ECU 10 and the delivery tool 21 changes from a logic high level to a low level, thereby causing the CPU 11 Judge that there is a rewrite request.

If there is the rewrite request, the process proceeds to step 102, and various programs in the flash ROM 13 are rewritten appropriately by the rewrite programs in the mask ROM 12. At this time, the CPU 11 receives a newly written control program or the like from the delivery destination tool 21 and writes the control program or the like at the corresponding address.

If there is no rewrite request from the delivery destination tool 21, in step 103, the boot program (2 in FIG. 2) corresponding to the OEM destination tools 22, 23, etc.
(Step S boot program) to determine whether there is a rewrite request from the OEM destination tools 22 and 23 and the like.
This determination is also performed in the same manner as in step 101. For example, when a predetermined rewrite switch on the delivery destination tool 21 is turned on and a rewrite request is issued, the signal line connecting the ECU 10 and the delivery destination tool 21 becomes logical. The level changes from the high level to the low level, whereby the CPU 11 determines that there is a rewrite request.

If there is the rewrite request, the process proceeds to step 104, and the application program in the flash ROM 13 is appropriately rewritten by the rewrite program in the flash ROM 13. At this time, the CPU 11 transmits the newly written control program and the like to the OEM destination tool 2.
2, 23, etc. and write to the corresponding address.

Delivery tool 21, OEM tool 22,
Step 1 if there is no rewrite request from any of 23 and the like
In step 05, the normal application program in the flash ROM 13 is executed. That is, normal engine control such as fuel injection control and ignition control is performed. Incidentally, in FIG. 3, steps 103 to 105 surrounded by a dashed line.
Is a process that is appropriately changed according to the design concept of the delivery destination or the OEM destination.

The flow of the program by the processing of FIG. 3 will be described again with reference to FIG. That is, Delivery Tool 2
In the case of rewriting at step 1, as indicated by the circled number 1 in FIG. 2, the program shifts to the delivery destination rewriting program after the execution of the first-stage boot program. The action after execution of the delivery destination rewriting program may be in accordance with the design concept of the delivery destination. After executing the delivery destination rewriting program, once turn off the power
Nothing may be done until F, or a reset or a second-stage boot program or a transition to a normal application program may be made.

When rewriting is performed by the OEM destination tools 22, 23, etc., as shown by a circle number 2 in FIG. 2, after executing the second-stage boot program, the process proceeds to the OEM destination rewriting program. The treatment after the execution of the OEM destination rewriting program may be in accordance with the design concept of the OEM destination.
After executing the OEM-specific rewriting program, once turn off the power
Nothing may be done until F, or a reset or transition to a normal application program may be made.

When no rewriting is performed, in FIG.
As shown by the circled number 3, the first stage boot program and the second stage boot program
After the stage boot program, the process is shifted to a normal application program.

According to the embodiment described above, the following effects can be obtained. (A) Among the boot programs respectively corresponding to the plurality of tools 21 to 23, the boot program corresponding to one specific delivery tool 21 is stored in the mask ROM 12, so that the same delivery destination (for each engine manufacturer) is stored. The mask ROM 12 can be shared. Further, since other boot programs corresponding to the OEM destination tools 22 and 23 are stored in the flash ROM 13, the same ECU 10 can realize a program rewriting function (reprogramming function) for each OEM destination (for each vehicle manufacturer). In this case, the manufacturing part numbers of the ECUs supplied and supplied to different OEM destinations do not increase, and the increase in cost can be suppressed.

(B) In the flash ROM 13, 2
Since the stage boot program and the application program are stored in different blocks, the programs can be rewritten separately, and the versatility of the device is improved.

(C) In the first stage boot program, it is determined whether or not all the programs in the flash ROM 13 are to be rewritten.
Since it is determined whether to rewrite only the application program in the flash ROM 13,
At the delivery destination (engine manufacturer), in addition to the rewrite setting of the application program, a boot program corresponding to each OEM destination (each vehicle manufacturer) can be arbitrarily set, and the rewrite function can be supported for each OEM destination. Can be. In this case, a boot program suitable for the OEM destination can be set not only at the time of manufacturing the ECU but also at the delivery destination.

(D) As a memory rewriting method, a multi-stage boot program is executed to determine the presence or absence of a rewriting request from each of the tools 21 to 23, so that the required program rewriting function can be correctly realized each time. .

The present invention can be embodied in the following forms other than the above. In the above embodiment, a delivery destination (engine manufacturer) is used as an external tool connected to the ECU 10.
Although the delivery destination tool 21 used in the above and the OEM destination tools 22 and 23 used in the OEM (vehicle manufacturer) have been exemplified, these will be changed as follows. For example, it is made to correspond to a plurality of tools of the same manufacturer. That is, for example, when a high-function tool and a low-function tool are used in the same maker, the high-function tool is stored as a standard tool in the mask ROM, and the boot program corresponding to the low-function tool is stored in the mask ROM. It is stored in a flash ROM (non-volatile memory). In this case, the EC where the high-performance tools are shared
The mask ROM can be shared for each U, and it is possible to easily cope with various low-function tools.

The present invention is not limited to the above-described engine ECU, but can be applied to other applications. In other words, various in-vehicle equipment ECUs that are actively supplied with OEMs in the automobile manufacturing industry
In addition, the present invention can be applied to an electronic control device used for a purpose other than an automobile. In short, the present invention can be suitably implemented in an electronic control device having a distribution form in which the delivery is made to a specific first delivery destination and then delivered to a second delivery destination.

[Brief description of the drawings]

FIG. 1 is a configuration diagram showing an outline of an engine ECU according to an embodiment of the invention.

FIG. 2 is a schematic diagram showing storage contents of a memory.

FIG. 3 is a flowchart showing the flow of processing on the ECU side.

FIG. 4 is a configuration diagram showing an outline of an ECU in a conventional technique.

FIG. 5 is a schematic diagram showing storage contents of a memory.

FIG. 6 is a schematic diagram showing a form of distribution of the engine ECU.

[Explanation of symbols]

10 ECU, 11 CPU, 12 mask ROM, 1
3. Flash ROM (non-volatile memory), 21 to 23
…tool.

 ──────────────────────────────────────────────────続 き Continuing from the front page (72) Inventor Toshio Tsuji 1-1-1 Showa-cho, Kariya-shi, Aichi F-Term in Denso Co., Ltd. (reference) 3G084 BA13 BA15 BA17 EB02 EB07 5B076 BB17 BB18 EB01 5H215 AA10 BB05 BB09 CC09 CX04 GG04 HH03 9A001 BB01 BB03 HH34 KK29 KK31

Claims (7)

[Claims] An electronic control device comprising a mask ROM in which data cannot be written and erased and a nonvolatile memory in which data can be written and erased, wherein a boot program corresponding to each of a plurality of tools is provided.
An electronic control device wherein one is stored in a mask ROM and another boot program is stored in a nonvolatile memory. 2. After being delivered to a specific first delivery destination, a second delivery
An electronic control unit to be delivered to a delivery destination of a first delivery destination, wherein a first boot program corresponding to a tool used at the first delivery destination is stored in a mask ROM and used at the second delivery destination. The electronic control device according to claim 1, wherein a second boot program corresponding to the tool is stored in a nonvolatile memory. 3. The electronic control device according to claim 2, wherein there are a plurality of said second delivery destinations, and a boot program corresponding to each delivery destination tool is stored in a nonvolatile memory. 4. The nonvolatile memory according to claim 1, wherein said nonvolatile memory is erasable in units of blocks, and said nonvolatile memory is rewritten by a second boot program and at least one of a delivery destination tool and a first boot program. 4. The electronic control device according to claim 2, wherein the possible application programs are stored in different blocks. 5. The electronic control device according to claim 4, wherein in the first boot program, it is determined whether or not to rewrite a storage program in the nonvolatile memory including the second boot program. In a boot program, an electronic control unit that determines whether to rewrite only an application program in a nonvolatile memory. 6. An electronic control unit for controlling a vehicle-mounted engine, wherein a first delivery destination is a manufacturer of the engine or the vehicle-mounted device, and a second delivery destination is a vehicle to which the engine or the vehicle-mounted device is supplied. The electronic control device according to any one of claims 2 to 5, which is a manufacturer. 7. A memory rewriting method applied to the electronic control device according to claim 1, wherein a first-stage boot program stored in a mask ROM determines whether there is a rewriting request from a specific tool. If there is a request, the request is executed, and if there is no request, the presence or absence of a rewrite request from another tool different from the specific tool is determined by a second stage boot program stored in the flash ROM, If there is a request, a memory rewriting method for executing the request.