JP7517188B2 - Engine Control Unit - Google Patents

Description

This disclosure relates to an engine control device.

One example of an engine control device is a control device for an internal combustion engine disclosed in Patent Document 1. This control device predicts fluctuations in crankshaft rotation speed based on the average value of the time required for a given CA (Crank Angle) in each cylinder. The control device then controls the fuel injection timing by predicting the time required for the next cycle based on the predicted fluctuations in the crankshaft rotation speed.

JP 2005-133669 A

In the control device described above, the analog signal input from the sensor to the microcomputer is converted to digital data via an ADC (Analog Digital Converter). Then, in the control device, this data is transferred from the ADC to RAM by a DMAC (Direct Memory Access Controller) and stored in the RAM. In addition, in the control device, the CPU core starts calculations in synchronization with an angle interrupt and reads the data stored in the RAM.

However, in engine control devices, the more sophisticated engine control is leading to an increase in the number of sensors and a higher sampling rate, which makes data processing more complicated and increases the amount of data. As a result, in engine control devices, the latency required for the core to read data stored in the RAM increases. For this reason, the engine control device may not be able to complete processing synchronized with the previous angle interrupt by the time of the angle interrupt.

One disclosed objective is to provide an engine control device that makes it easier to complete processing before the next processing timing.

The engine control device disclosed herein comprises:
An engine control device that performs processing in synchronization with an angle of an engine crankshaft,
An acquisition unit (31) that acquires an angle signal according to an angle;
A storage device (3) for storing at least one piece of data to be used in processing;
A processing device (1) having at least one calculation unit (11, 12) that executes processing in synchronization with an angle signal, and at least one memory unit (13, 13a, 13b) that can be accessed in a shorter time than when the calculation unit accesses a memory device;
a transfer unit (4, 5) for transferring use data, which is data used by the calculation unit for a process to be executed, from the storage device to the storage unit in advance of a timing when the use data is required for the process to be executed ;
The transfer section is
A prediction unit (412) for predicting a predicted period in which an angle signal is input;
a timing acquisition unit (42a) for acquiring a transfer timing for starting transfer of the usage data based on the predicted period;
The timing acquisition unit acquires the transfer timing by subtracting a predetermined transfer specified time, which corresponds to the transfer time of the usage data from the storage device to the storage unit, from the predicted period .

As a result, the calculation unit reads the usage data from the storage unit when performing processing in synchronization with the angle. Therefore, the calculation unit can read the usage data in a shorter time than when reading the usage data from the storage device. Therefore, the engine control device can easily end the processing by the calculation unit by the next processing timing in synchronization with the angle.
Further, the engine control device disclosed herein comprises:
An engine control device that performs processing in synchronization with an angle of an engine crankshaft,
An acquisition unit (31) that acquires an angle signal according to an angle;
A storage device (3) for storing at least one piece of data to be used in processing;
A processing device (1) having at least one calculation unit (11, 12) that executes processing in synchronization with an angle signal, and at least one memory unit (13, 13a, 13b) that can be accessed in a shorter time than when the calculation unit accesses a memory device;
a transfer unit (4, 5) for transferring use data, which is data used by the calculation unit for a process to be executed, from the storage device to the storage unit in advance of a timing when the use data is required for the process to be executed;
The transfer section is
A prediction unit (412) for predicting a predicted period in which an angle signal is input;
a timing acquisition unit (42a) for acquiring a transfer timing for starting transfer of the usage data based on the predicted period;
The timing acquisition unit multiplies a predetermined basic transfer time of data by the number of processes scheduled to be executed to calculate the total transfer time required to transfer the usage data from the storage device to the storage unit, and acquires the transfer timing by subtracting the total transfer time from the predicted period .
Further, the engine control device disclosed herein comprises:
An engine control device that performs processing in synchronization with an angle of an engine crankshaft,
An acquisition unit (31) that acquires an angle signal according to an angle;
A storage device (3) for storing at least one piece of data to be used in processing;
A processing device (1) having at least one calculation unit (11, 12) that executes processing in synchronization with an angle signal, and at least one memory unit (13, 13a, 13b) that can be accessed in a shorter time than when the calculation unit accesses a memory device;
a transfer unit (4, 5) for transferring use data, which is data used by the calculation unit for a process to be executed, from the storage device to the storage unit in advance of a timing when the use data is required for the process to be executed;
The transfer section is
A prediction unit (412) for predicting a predicted period in which an angle signal is input;
a timing acquisition unit (42a) for acquiring a transfer timing for starting transfer of the usage data based on the predicted period;
The timing acquisition unit multiplies a predetermined basic transfer time for data by transfer time information specific to the usage data used in the processing to be executed, to calculate the total transfer time required to transfer the usage data from the storage device to the storage unit, and acquires the transfer timing by subtracting the total transfer time from the predicted period.

The various aspects disclosed in this specification employ different technical means to achieve their respective objectives. The claims and the reference characters in parentheses in this section are illustrative of the corresponding relationships with the embodiments described below, and are not intended to limit the technical scope. The objectives, features, and advantages disclosed in this specification will become clearer with reference to the detailed description that follows and the accompanying drawings.

FIG. 2 is a block diagram showing a schematic configuration of an ECU according to the first embodiment. FIG. 2 is a block diagram showing a schematic configuration of a timer module according to the first embodiment. FIG. 2 is a block diagram showing a schematic configuration of a timing calculation unit in the first embodiment. 4 is a block diagram showing a schematic configuration of a transfer start instruction unit in the first embodiment. 5 is a flowchart showing a timing calculation process in the first embodiment. 5 is a time chart showing a processing operation during a timing calculation process in the first embodiment. 10 is a flowchart showing a transfer start process according to the first embodiment. 5 is a time chart showing a processing operation at the time of transfer start processing in the first embodiment. FIG. 11 is a block diagram showing a schematic configuration of a timing calculation unit in a second embodiment. 13 is a flowchart showing a timing calculation process in the second embodiment. 10 is a time chart showing a processing operation during a timing calculation process in the second embodiment. FIG. 13 is a block diagram showing a schematic configuration of a timing calculation unit in a third embodiment. 13 is a flowchart showing a timing calculation process in the third embodiment. 13 is a time chart showing a processing operation during timing calculation processing in the third embodiment. FIG. 13 is a block diagram showing a schematic configuration of a timing calculation unit in a fourth embodiment. FIG. 13 is a block diagram showing a schematic configuration of a transfer start instruction unit in the fourth embodiment. 13 is a flowchart showing a timing calculation process in the fourth embodiment. 13 is a flowchart showing a transfer start process according to the fourth embodiment. FIG. 13 is a block diagram showing a schematic configuration of a transfer start instruction unit in the fifth embodiment. 13 is a flowchart showing a transfer start process according to the fifth embodiment. 13 is a time chart showing a processing operation at the time of a transfer start process in the fifth embodiment. FIG. 13 is a block diagram showing a schematic configuration of an ECU in a sixth embodiment.

Below, several embodiments for implementing the present disclosure will be described with reference to the drawings. In each embodiment, parts corresponding to matters described in the preceding embodiment may be given the same reference numerals, and duplicated descriptions may be omitted. In each embodiment, when only a part of the configuration is described, the other parts of the configuration may be applied by referring to the other embodiment described previously.

First Embodiment
An ECU (Electronic Control Unit) 100 will be described with reference to Figures 1 to 8. In this embodiment, an example is adopted in which an engine control device is applied to the ECU 100. Therefore, the ECU 100 is configured so as to be mountable on a vehicle provided with an engine.

<Configuration>
The configuration of the ECU 100 will be described with reference to Figures 1 to 4. As shown in Figure 1, the ECU 100 is electrically connected to a battery 200. The ECU 100 is supplied with operating power from the battery 200. The ECU 100 is electrically connected to, as control targets, an igniter 210 and an injector 220, for example, provided in an engine. The ECU 100 outputs an ignition signal to the igniter 210 to drive the igniter 210. The ECU 100 also outputs a fuel injection signal to the injector 220 to drive the injector 220.

Furthermore, ECU 100 is electrically connected to sensors such as a cam sensor 230 and a crank sensor 240. Cam sensor 230 is disposed opposite cam rotor 232. Cam rotor 232 is fixed to camshaft 231. Cam rotor 232 rotates with the rotation of camshaft 231. Cam sensor 230 outputs a pulsed cam signal corresponding to the rotation of cam rotor 232. The cam signal is a signal that is output at a cycle of 720 CA. The cam signal is used in combination with the crank signal to detect the reference angle of the crank angle.

The crank sensor 240 is disposed opposite the crank rotor 242. The crank rotor 242 is fixed to the crankshaft 241. The crank rotor 242 rotates with the rotation of the crankshaft 241. The crank sensor 240 outputs a pulse-shaped crank signal corresponding to the rotation of the crank rotor 242. In other words, it can be said that the crank sensor 240 outputs a crank signal according to the angle of the crankshaft 241.

The crankshaft 241 corresponds to the crank shaft. The crank signal corresponds to the angle signal. The crank signal can also be called a crank angle signal.

The ECU 100 includes a microcomputer 10, a power supply circuit 20, an input circuit 31, an output circuit 32, and the like. First, the power supply circuit 20 is electrically connected to a battery 200. The power supply circuit 20 converts the voltage of the battery 200 and supplies it to the microcomputer 10, the input circuit 31, and the output circuit 32.

The input circuit 31 is electrically connected to the cam sensor 230 and the crank sensor 240. The input circuit 31 receives a cam signal and a crank signal. The input circuit 31 may also be electrically connected to other sensors, switches, and the like. In this case, the input circuit 31 receives sensor signals from other sensors and switch signals from switches. In this way, the input circuit 31 receives the crank signal and the like, and thereby acquires the crank signal and the like. The input circuit 31 corresponds to an acquisition unit. The input circuit 31 outputs the various input signals to the microcontroller 10.

The output circuit 32 is electrically connected to the igniter 210 and the injector 220. The output circuit 32 outputs an ignition signal to the igniter 210. The output circuit 32 also outputs a fuel injection signal to the injector 220. The output circuit 32 may be connected to another ECU. In this case, the output circuit 32 outputs an output signal to the other ECU. The output circuit 32 outputs a signal in response to an instruction from the microcomputer 10.

The microcontroller 10 includes a CPU 1, a ROM 2, a RAM 3, a timer module 4, a DMAC 5, an ADC 6, an I/O 7, and the like. These are electrically connected via an internal bus. The microcontroller 10 is electrically connected to a power supply circuit 20, an input circuit 31, and an output circuit 32.

The microcomputer 10 starts engine control processes such as ignition timing control, knock control, and fuel injection control in synchronization with the estimated crank angle. As a result of the engine control processes, the microcomputer 10 outputs a fuel injection signal and an ignition signal. The ECU 100 drives the igniter 210 by outputting an ignition signal via the output circuit 32. Similarly, the ECU 100 drives the injector 220 by outputting a fuel injection signal via the output circuit 32.

The CPU 1 includes a first core 11, a second core 12, a local RAM 13, etc. The CPU 1 corresponds to a calculation processing device.

The cores 11 and 12 execute processing according to a program stored in the ROM 2 or the like. The cores 11 and 12 also execute processing in synchronization with the crank signal. In other words, the cores 11 and 12 execute processing at a timing synchronized with the angle of the crankshaft 241. It can also be said that the cores 11 and 12 execute processing every time an angle interrupt occurs that is synchronized with the angle of the crankshaft 241.

The processes executed by the cores 11 and 12 are part of the engine control process. The processes executed by the cores 11 and 12 can also be considered as processes for engine control. The cores 11 and 12 execute multiple processes for engine control. Furthermore, the cores 11 and 12 can also be considered as executing processes (control processes) for controlling the igniter 210 and the injector 220.

Cores 11 and 12 use at least one data item when executing a process. When executing a process, cores 11 and 12 read data stored in local RAM 13. Then, cores 11 and 12 execute the process using the read data. The data stored in local RAM 13 has been transferred from RAM 3. This point will be explained in more detail later.

In the following, as an example, a situation in which the first core 11 executes processing is used. The data used by the first core 11 in the processing to be executed can also be considered usage data. Note that the timer module 4 and DMAC 5, which will be described later, operate in the same manner even when the second core 12 executes processing.

Cores 11 and 12 correspond to the calculation unit. Local RAM 13 corresponds to the storage unit. Local RAM 13 is provided in CPU 1 together with cores 11 and 12. Therefore, local RAM 13 is configured to be accessible in a shorter time than when cores 11 and 12 access RAM 3.

In this embodiment, an example is used in which two cores 11, 12 and one local RAM 13 are provided. However, the present disclosure is not limited to this, and it is sufficient that at least one core and at least one local RAM are provided.

ROM2 stores programs that can be executed by CPU1. RAM3 temporarily stores at least one piece of data that is used when either one of cores 11 or 12 executes a process. RAM3 corresponds to a storage device.

To distinguish it from the local RAM 13, the RAM 3 can also be considered an external storage device provided outside the CPU 1. On the other hand, the local RAM 13 can also be considered an internal storage device provided inside the CPU 1.

The timer module 4 outputs a request signal to the DMAC 5, which indicates a request to transfer the data in use. The timer module 4 will be described in detail later. In response to the request signal, the DMAC 5 transfers the data stored in the RAM 3 to the local RAM 13. In the following, when the word "transfer" is used, it refers to the transfer of data from the RAM 3 to the local RAM 13.

The timer module 4 and DMAC 5 transfer the usage data from the RAM 3 to the local RAM 13 in advance before the timing when the usage data is required when the first core 11 executes a process. More specifically, the first core 11 requires the usage data when executing a process. Therefore, the timer module 4 and DMAC 5 transfer the usage data from the RAM 3 to the local RAM 13 in advance before the timing when the usage data is required, and store the usage data in the local RAM 13. The timer module 4 and DMAC 5 correspond to a transfer unit.

ADC 6 is an AD converter that converts analog signals into digital signals. ADC 6 converts, for example, a signal input to I/O 7 into data used for processing by cores 11 and 12. I/O 7 outputs, for example, a signal input to input circuit 31 to the internal bus, and outputs a signal output to the internal bus to output circuit 32. The signals here include not only ignition signals, fuel injection signals, crank signals, and cam signals, but also signals indicating data used for processing by cores 11 and 12.

The timer module 4 will now be described with reference to Figures 2, 3, and 4. The timer module 4 includes a first timer 41, a timing calculation unit 42a, and a second timer 43. The crank signal is input to the timer module 4 via the input circuit 31 and the I/O 7.

The first timer 41 includes a period measurement unit 411 and a period prediction unit 412. The period measurement unit 411 detects edges of the crank signal and counts the number of pulses of the crank signal. The number of pulses can be referred to as a count value PC or an edge number. The period measurement unit 411 also detects edges of the crank signal and measures the crank signal period Tam. This crank signal period Tam is the time between edges in the crank signal. Hereinafter, the crank signal period Tam will also be simply referred to as period Tam. Furthermore, the first timer 41 estimates the crank angle based on the count value PC and period Tam of the crank signal.

The period measurement unit 411 has, for example, an edge detection circuit that detects the rising edge of the crank signal and a counter that counts the detected edges. The edge detection circuit may also detect the falling edge.

The cycle prediction unit 412 detects a rough crank angle θ, for example, every 10 CA or 6 CA, based on the count value PC. The CA here is not limited to the above. The cycle prediction unit 412 predicts the next and subsequent crank signal cycles based on the detected crank angle and the cycle Tam measured by the cycle measurement unit 411. Hereinafter, the predicted crank signal cycle is also referred to as the predicted cycle Tpd. The cycle prediction unit 412 corresponds to a prediction unit, and predicts the predicted cycle Tpd at which the crank signal is input. Please refer to JP 2013-108478 A for a method of predicting the predicted cycle Tpd.

The cycle prediction unit 412 may also generate a multiplied angle clock as an operating clock for the cores 11 and 12. The cycle prediction unit 412 generates a multiplied angle clock having a frequency that is a predetermined multiple of the crank signal cycle that is more precise (e.g., in units of 1 CA) than the rough crank angle θ, based on the predicted cycle Tpd. The cores 11 and 12 may perform processing in synchronization with the multiplied angle clock, thereby performing processing in synchronization with the angle of the crankshaft 241. The ECU 100 performs processing based on the multiplied angle clock, enabling high-resolution, high-precision engine control.

As shown in Figures 2 and 3, the timing calculation unit 42a is electrically connected to the first timer 41. The timing calculation unit 42a can be realized by hardware processing in the first timer 41 or by software implementation. The timing calculation unit 42a includes, for example, an arithmetic processing unit such as a CPU and a storage device such as a ROM.

The timing calculation unit 42a has a transfer process calculation unit 421a and a total transfer time calculation unit 422a as functional blocks of the arithmetic processing device. The timing calculation unit 42a also has a timing output unit 424a as an arithmetic logic unit in the arithmetic processing device. More specifically, the timing output unit 424a is a subtractor. Furthermore, the timing calculation unit 42a has a processing table 423a stored in the storage device.

The timing calculation unit 42a acquires the transfer timing Tst for starting the transfer of the usage data based on the predicted period Tpd. The timing calculation unit 42a corresponds to the timing acquisition unit.

The transfer process calculation unit 421a calculates the number of transfer processes N to be transferred from RAM 3 to local RAM 13. In other words, the transfer process calculation unit 421a calculates the number of processes that require the transfer of usage data when transferring usage data at the next angle interrupt. The number of processes that require the transfer of usage data is referred to as the transfer process number N. The transfer process calculation unit 421a calculates the transfer process number N using the acquired count value PC and the process table 423a.

The total transfer time calculation unit 422a calculates the total transfer time Ttr required to transfer the usage data from RAM 3 to the local RAM 13. The usage data here is the usage data used in the process that was the target when the transfer process calculation unit 421a calculated the number of transfer processes N. The total transfer time calculation unit 422a calculates the total transfer time Ttr from a predetermined basic transfer time Tba and the number of transfer processes N. The number of transfer processes N corresponds to the number of processes scheduled to be executed.

The basic transfer time Tba is the base time required to transfer data from RAM 3 to local RAM 13. In other words, the basic transfer time Tba is the time required to transfer a predetermined amount of data (e.g., the number of bytes). The basic transfer time Tba is a statically determined value. The basic transfer time Tba is obtained from design values, latency, etc. The basic transfer time Tba is also stored in the storage device of the timing calculation unit 42a.

The process table 423a includes a process number indicating the number of a statically determined process, and a process-specific execution angle array indicating at what angle an angle interruption is executed in synchronization with which each process associated with the process number is executed. The process table 423a also includes a transfer process item AR for each count value. The transfer process item AR is then associated with the count value. The usage data used in each process is determined in advance.

A transfer process item AR is provided for each angle interrupt (count value). The transfer process item AR indicates the process that requires the transfer of usage data. The transfer process item AR can also be said to be information indicating which process requires the transfer of data used in which process. Therefore, the process table 423a can be said to include a transfer process item AR that indicates which process requires the transfer of usage data in each angle interrupt. Note that a process item is an item of a process, and can also be simply referred to as a process.

The transfer process item AR is represented by 8 bits when the number of possible process items is 8. In this case, the transfer process item AR contains information indicating whether or not the usage data used by the 8 process items is transferred.

In the example of Figure 6, 00101001b, for example, is used as the transfer process item AR. The transfer process item AR is configured with bits corresponding to the process numbers arranged from the left in ascending order of process numbers. Furthermore, the transfer process item AR indicates that a transfer is requested with a 1, and that a transfer is not requested with a 0. Therefore, this transfer process item AR indicates that the processes with the third, fifth, and eighth process numbers will be executed. In other words, the transfer process item AR indicates that the transfer of usage data to be used in the processes with the third, fifth, and eighth process numbers will be requested.

In this way, the transfer process item AR is formed by setting a bit corresponding to the process number that requests the transfer of usage data. Note that if there are 32 possible process items, the transfer process item AR is represented by 32 bits.

The timing output unit 424a receives the predicted period Tpd and the total transfer time Ttr. The timing output unit 424a calculates the transfer timing Tst from the predicted period Tpd and the total transfer time Ttr.

The transfer timing Tst is the timing at which the transfer of the usage data starts. In other words, the transfer timing Tst is the timing indicating the start of the transfer of the usage data from RAM 3 to the local RAM 13. The transfer timing Tst can also be said to be the transfer timing required for the first core 11 to execute processing using the usage data at the angle interrupt after the next one. Therefore, the transfer timing Tst can also be said to be the transfer timing or the start timing.

As shown in Figures 2 and 4, the second timer 43 includes a transfer start instruction unit 43a. The transfer start instruction unit 43a is electrically connected to the timing calculation unit 42a. The transfer start instruction unit 43a includes an arithmetic processing unit such as a CPU, a counter, and a storage device such as a register.

The transfer start instruction unit 43a has a transfer process item register 431a and a transfer timing register 432a as storage devices. The transfer process item register 431a temporarily stores the transfer process item AR acquired from the transfer process calculation unit 421a. The transfer process item register 431a updates the stored transfer process item AR every time a transfer process item AR is input. The transfer timing register 432a temporarily stores the transfer timing Tst acquired from the timing output unit 424a. The transfer timing register 432a updates the stored transfer timing Tst every time a transfer timing Tst is input.

The transfer start instruction unit 43a has a transfer timing counter 433a as a counter. A crank signal, a clock, and a counter stop signal are input to the transfer timing counter 433a. When the transfer timing counter 433a detects an edge of the crank signal, it starts counting the clock. In addition, when the counter stop signal is input, the transfer timing counter 433a stops counting the clock.

The transfer start instruction unit 43a has a timing comparison unit 434a and a request output unit 435a as an arithmetic logic unit in the arithmetic processing device. The count value of the transfer timing counter 433a and the transfer timing Tst are input to the timing comparison unit 434a. When the count value of the transfer timing counter 433a matches the transfer timing Tst, the timing comparison unit 434a outputs a transfer start signal and a counter stop signal.

The request output unit 435a receives the transfer process item AR and a transfer start signal. The request output unit 435a outputs a request signal based on the transfer process item AR and the transfer start signal.

<Processing Operation>
The processing operation of the ECU 100 will be described with reference to FIGS.

First, the processing operation of the timing calculation unit 42a will be described using Figures 5 and 6. The timing calculation unit 42a starts the flowchart in Figure 5 every time a crank signal is input. Note that Figure 6 describes the case where the count value is 003h. Also, in Figure 6, when the count value is 003h, the relevant parts are hatched.

In step S10, the count value PC is read. The transfer process calculation unit 421a reads the count value PC counted by the first timer 41.

In step S11, the incremental count value NPC is calculated. The transfer process calculation unit 421a calculates the incremental count value NPC by incrementing the count value PC read in step S10 by 2. In other words, the incremental count value NPC = count value PC + 2.

The current count value PC corresponds to the current angle interrupt. Therefore, the incremental count value NPC corresponds to the angle interrupt after the next one. In other words, the transfer process calculation unit 421a calculates the incremental count value NPC to recognize the process to be executed at the angle interrupt after the next one.

In step S12, the processing table 423a is read. The transfer processing calculation unit 421a refers to the processing table 423a.

In step S13, the transfer process item AR and the transfer process number N are obtained based on the process table 423a and the incremental count value NPC. The transfer process calculation unit 421a obtains the transfer process item AR linked to the incremental count value NPC from the process table 423a.

The transfer process calculation unit 421a calculates the number of transfer processes N from the acquired transfer process item AR. In the transfer process item AR in the above example, there are three processes that require the transfer of usage data in the next angle interrupt. Therefore, the transfer process calculation unit 421a calculates the number of transfer processes N as 3. The transfer process calculation unit 421a acquires the number of transfer processes N by calculating the number of transfer processes N in this way. The transfer process calculation unit 421a outputs the acquired number of transfer processes N and the transfer process item AR.

In step S14, the basic transfer time Tba is read. The total transfer time calculation unit 422a reads the basic transfer time Tba. This is to calculate the total transfer time Ttr.

In step S15, the total transfer time Ttr is calculated. The total transfer time calculation unit 422a calculates the total transfer time Ttr using the number of transfer processes N calculated in step S13 and the basic transfer time Tba read in step S14. The total transfer time calculation unit 422a multiplies the basic transfer time Tba by the number of transfer processes N to calculate the total transfer time Ttr. Total transfer time Ttr = Tba x N.

For example, in the example of FIG. 6, the processing table 423a is read, and the number of transfer processes N at the count value PC003h is 003h. The basic transfer time Tba is 010h (=016d). The total transfer time Ttr is expressed as the basic transfer time Tba x the number of transfer processes N, so it is 030h (=048d).

In step S16, the predicted period Tpd is read. The timing output unit 424a reads the predicted period Tpd predicted by the period prediction unit 412.

In step S17, the transfer timing Tst is calculated. The timing output unit 424a calculates the transfer timing Tst by subtracting the total transfer time Ttr from the predicted period Tpd. The transfer timing Tst=Tpd- Ttr . The timing output unit 424a outputs the calculated transfer timing Tst. In the example of FIG. 6, the transfer timing Tst is output as 0D5h (=213d=00111101b), which is obtained by subtracting the total transfer time Ttr 030h (=048d) from the predicted period Tpd 0105h (=261d).

Note that all of the specific numerical values, such as the value of the forwarding process item AR, are merely examples. This disclosure is not limited to these.

Next, the processing operation of the transfer start instruction unit 43a will be described with reference to Figures 7 and 8. The transfer start instruction unit 43a starts the flowchart in Figure 7 every time a crank signal is input. Note that in Figure 8, the areas that are the subject of this embodiment are hatched.

In step S20, the rising edge of the crank signal is read. The transfer start instruction unit 43a reads the rising edge of the input crank signal. In other words, the transfer start instruction unit 43a detects the rising edge of the input crank signal. Note that the transfer start instruction unit 43a may also read the falling edge of the crank signal.

In step S21, the transfer timing is read and the transfer timing register is updated. The transfer start instruction unit 43a updates the transfer timing Tst stored in the transfer timing register 432a to the transfer timing Tst input this time. In the example of FIG. 8, 00111101b is stored in the transfer timing register 432a. Note that 00101001b is stored in the transfer processing item register 431a.

In step S22, the transfer timing counter is initialized to 0 and starts counting. The transfer timing counter 433a initializes its own count value to 0. The transfer timing counter 433a then starts counting the clock. This is to compare the count value of the transfer timing counter 433a with the transfer timing Tst to determine whether the transfer timing Tst has arrived.

In step S23, it is determined whether the timing count value and the register value match. The timing comparison unit 434a determines whether the count value of the transfer timing counter 433a and the register value of the transfer timing register 432a match. The register value is the transfer timing Tst stored in the transfer timing register 432a in step S21.

If the timing comparison unit 434a determines that the count value and the register value match, the process proceeds to step S24. If the timing comparison unit 434a does not determine that the count value and the register value match, the process returns to step S23.

In step S24, a request signal is transmitted. As shown in FIG. 8, if the timing comparison unit 434a determines that the count value and the register value match, it outputs a transfer start signal. The transfer start signal is a signal indicating that the counter value and the register value match and that the transfer timing Tst has been reached.

Furthermore, when a transfer start signal is input, the request output unit 435a transmits a request signal to the DMAC5. By transmitting the request signal, the request output unit 435a requests the DMAC5 to transfer usage data. It can be said that the request output unit 435a requests the DMAC5 to transfer usage data corresponding to the transfer process item AR. In other words, the request output unit 435a requests that data used in the process of the process number whose bit is set in the transfer process item AR be transferred as usage data. In this case, the request output unit 435a may transmit a request signal that includes the transfer process item AR. In this way, the request output unit 435a can also be said to be a selector that chooses whether or not to issue a request signal.

The timing comparison unit 434a outputs a counter stop signal together with the request signal. This is to stop the counting by the transfer timing counter 433a. The counter stop signal can be a signal obtained by renaming the transfer start signal, or the like.

In the example of FIG. 8, the transfer timing register 432a stores 00111101b as the register value. Meanwhile, the transfer processing item register 431a stores 00101001b as the transfer processing item AR. Therefore, the timing comparison unit 434a outputs a transfer start signal when the count value of the transfer timing counter 433a becomes 00111101b. Then, the request output unit 435a requests the transfer of the third, fifth, and eighth data based on the transfer processing item AR of 00101001b.

＜Effects＞
As described above, the timer module 4 and the DMAC 5 transfer data to be used in the processing to be executed by the cores 11 and 12 from the RAM 3 to the local RAM 13 in advance of the timing when the data is required for the processing. When executing the processing in synchronization with the crank signal, the cores 11 and 12 read the data stored in the local RAM 13. This local RAM 13 is configured to be accessible in a shorter time than when the cores 11 and 12 access the RAM 3.

As a result, the cores 11 and 12 can read the usage data in a shorter time than when reading the usage data from the RAM 3. This makes it easier for the ECU 100 to complete the processing by the next processing timing when the cores 11 and 12 are synchronized with the angle.

In addition, cores 11 and 12 can reduce the time required to read usage data. This allows cores 11 and 12 to allocate that time to processing. As a result, cores 11 and 12 can execute processes that involve complex calculations or processes that use a large amount of usage data.

The ECU 100 acquires the transfer timing Tst using the predicted period Tpd. Therefore, the ECU 100 can acquire the transfer timing Tst more accurately than a configuration that acquires the transfer timing Tst without using the predicted period Tpd.

The ECU 100 calculates the total transfer time Ttr using the number of transfer processes N to obtain the transfer timing Tst. Therefore, the ECU 100 can obtain the transfer timing Tst more accurately than a configuration that obtains the transfer timing Tst without using the number of transfer processes N.

(Modification)
The timing calculation unit 42a may obtain the transfer timing without using the number of transfer processes N. The timing calculation unit 42a obtains the transfer timing, for example, by subtracting the specified transfer time from the predicted period Tpd. The specified transfer time is a predetermined time that corresponds to the transfer time of the usage data from the RAM 3 to the local RAM 13. The specified transfer time is, for example, stored in advance in a storage unit of the timing calculation unit 42a.

As a result, the timing calculation unit 42a does not need to calculate the total transfer time. Therefore, in this modified example, the processing load on the timing calculation unit 42a can be reduced.

Preferred embodiments of the present disclosure have been described above. However, the present disclosure is not limited to the above-described embodiments, and various modifications are possible without departing from the spirit of the present disclosure. Below, the second to sixth embodiments will be described as other aspects of the present disclosure. The above-described embodiments and the second to sixth embodiments can each be implemented alone, but can also be implemented in appropriate combinations. The present disclosure is not limited to the combinations shown in the embodiments, and can be implemented in various combinations.

Second Embodiment
An ECU according to the second embodiment will be described with reference to Figures 9, 10 and 11. In this embodiment, differences from the above-mentioned embodiment will be described. The ECU according to the second embodiment differs from the above-mentioned embodiment in the configuration and processing operation of a timing calculation unit 42b.

<Configuration>
9, the timer module 4 includes a timing calculation unit 42b instead of the timing calculation unit 42a. The timing calculation unit 42b includes a transfer process calculation unit 421b, a total transfer time calculation unit 422b, a process table 423b, and a timing output unit 424b. The timing calculation unit 42b corresponds to a timing acquisition unit.

The timing calculation unit 42b multiplies the basic transfer time Tba by a transfer time coefficient α[x] specific to the data used in each process to calculate the total transfer time Ttr of the data used from the RAM 3 to the local RAM 13. The timing calculation unit 42b obtains the transfer timing Tst by subtracting this total transfer time Ttr from the predicted period Tpd.

Cores 11 and 12 have different amounts of data used for each process. In addition, the data capacity of each piece of data used varies. Therefore, the time required to transfer the data used varies depending on the process. The transfer time coefficient α is a coefficient that correlates with the time required to transfer the data used for each process. The transfer time coefficient α is linked to each process number.

For example, let us take the case where the data capacity for defining the basic transfer time Tba is 10, and the basic transfer time Tba is 10. In process A, it is assumed that used data with a data capacity of 20 is used. In this case, the transfer time coefficient α associated with process A is 2. Similarly, it is assumed that used data with a data capacity of 5 is used. In this case, the transfer time coefficient α associated with process B is 0.5.

The transfer process calculation unit 421b, like the transfer process calculation unit 421a, obtains the transfer process item AR from the process table 423b. Then, the transfer process calculation unit 421b outputs the obtained transfer process item AR to the total transfer time calculation unit 422b.

The total transfer time calculation unit 422b calculates the total transfer time Ttr in the same way as the total transfer time calculation unit 422a. However, the method of calculating the total transfer time Ttr differs from that of the total transfer time calculation unit 422a.

The total transfer time calculation unit 422b calculates the total transfer time Ttr using the basic transfer time Tba and the transfer time coefficient α. The total transfer time calculation unit 422b obtains the transfer time coefficient α from the input transfer process item AR and the process table 423b. In other words, the total transfer time calculation unit 422b obtains the process number of the process that requires the transfer of usage data at the next angle interrupt from the transfer process item AR. Then, the total transfer time calculation unit 422b obtains the transfer time coefficient α linked to the obtained process number from the process table 423b.

The total transfer time calculation unit 422b calculates the total transfer time Ttr by multiplying the basic transfer time Tba by the sum of the transfer time coefficients α. The total transfer time Ttr may differ depending on the value of the transfer time coefficient α even if the number of transfer processes N is the same. The sum of the transfer time coefficients α is referred to as the total transfer time coefficient Σα.

The transfer process calculation unit 421b may also obtain, from the process table 423b, the process number of the process that requires the transfer of usage data in the next angle interruption, along with the transfer process item AR. In this case, the transfer process calculation unit 421b may output the obtained process number to the total transfer time calculation unit 422b.

The processing table 423b includes a transfer time coefficient α linked to each processing number in addition to the processing number and the execution angle array for each processing. The transfer time coefficient α corresponds to the transfer time information. Note that the processing table 423b includes a transfer processing item AR, similar to the processing table 423a. The timing output unit 424b is similar to the timing output unit 424a.

<Processing Operation>
The processing operation of the timing calculation unit 42b will be described with reference to Figures 10 and 11. The timing calculation unit 42b starts the flowchart of Figure 10 every time a crank signal is input. In Figure 10, the same steps as in Figure 5 are given the same step numbers. Note that Figure 11 will be described assuming that the count value is 003h. Also, in Figure 11, when the count value is 003h, the relevant parts are hatched.

In step S13a, the transfer process item AR is obtained. The transfer process calculation unit 421b obtains the transfer process item AR from the process table 423b, similar to the transfer process calculation unit 421a. The transfer process calculation unit 421b then outputs the obtained transfer process item AR to the total transfer time calculation unit 422b.

In step S13b, the total transfer time coefficient Σα of the transfer time coefficient α is calculated. The total transfer time calculation unit 422b acquires the process number of the process that requires the transfer of usage data from the transfer process item AR acquired in step S13a. The total transfer time calculation unit 422b also acquires the transfer time coefficient α linked to the acquired process number from the process table 423b. The total transfer time calculation unit 422b then adds up all the acquired transfer time coefficients α to calculate the total transfer time coefficient Σα, which is the sum of the transfer time coefficients α.

In step S15a, the total transfer time Ttr is calculated. The total transfer time calculation unit 422b calculates the total transfer time Ttr using the total transfer time coefficient Σα calculated in step S13 and the basic transfer time Tba read in step S14. The total transfer time calculation unit 422b multiplies the basic transfer time Tba by the total transfer time coefficient Σα to calculate the total transfer time Ttr. Total transfer time Ttr = Tba × Σα (x).

In the example of FIG. 11, the final total transfer time coefficient Σα at the count value 003h is 11b (=03d). Also, the basic transfer time is 010h = (016h). In this case, the total transfer time Ttr is calculated as 010h (16d) x 11b (=03d) = 030h (=048d).

The transfer timing Tst is the value obtained by subtracting the total transfer time Ttr from the predicted period Tpd. Therefore, 0D5h (=213d), which is obtained by subtracting the total transfer time Ttr 030h (=048d) from the predicted period Tpd 0105h (=261d), is output as the transfer timing Tst. In addition, the transfer process item AR at the count value 003h in the process table 423b is read, and 01010001b is output as the transfer process item AR.

＜Effects＞
The ECU of the second embodiment can achieve the same effects as the ECU 100. Furthermore, the ECU of the second embodiment can calculate the time required for the transfer of each piece of usage data individually, rather than uniformly, by using the above-described configuration. Therefore, the ECU of the second embodiment can calculate the time required for the transfer with higher accuracy than the ECU 100.

Third Embodiment
The ECU of the third embodiment will be described with reference to Figures 12, 13 and 14. In this embodiment, differences from the second embodiment will be described. The ECU of the third embodiment differs from the second embodiment in the configuration and processing operation of a timing calculation unit 42c.

<Configuration>
12, the timer module 4 includes a timing calculation section 42c instead of the timing calculation section 42b. The timing calculation section 42c includes a total transfer time calculation section 422c, a processing table 423c, and a timing output section 424c.

The count value PC and the processing number are input to the total transfer time calculation unit 422c. The processing number here indicates the processing that requires transfer at the next angle interrupt. For this reason, one processing number or multiple processing numbers are input to the total transfer time calculation unit 422c. In this embodiment, as an example, an example is used in which two processing numbers, processing numbers 03 and 04, are input.

The total transfer time calculation unit 422c obtains the transfer time coefficient α associated with the input process number from the process table 423c. Then, the total transfer time calculation unit 422c calculates the total transfer time coefficient Σα in the same way as the total transfer time calculation unit 422b. The total transfer time calculation unit 422c calculates the total transfer time Ttr by multiplying the basic transfer time Tba by the total transfer time coefficient Σα.

Unlike process table 423b, process table 423c does not have a process-specific execution angle array. In addition, a process number that requests transfer at the next angle interrupt is input to process table 423c. Timing output unit 424c is the same as timing output unit 424b.

<Processing Operation>
The processing operation of the timing calculation unit 42c will be described with reference to Figures 13 and 14. The timing calculation unit 42c starts the flowchart of Figure 13 every time a crank signal is input. In Figure 13, the same steps as in Figure 10 are given the same step numbers. Note that Figure 14 will be described assuming that the count value is 003h. Also, in Figure 11, when the count value is 003h, the relevant parts are hatched.

In step S11a, the predicted period Tpd is read. The total transfer time calculation unit 422c reads the predicted period Tpd predicted by the period prediction unit 412. In step S12a, the transfer timing Tst is set to Tpd. The total transfer time calculation unit 422c sets the transfer timing Tst to the predicted period Tpd read in step S11a.

The total transfer time calculation unit 422c repeatedly executes steps S13c to S18 until all process numbers have been read. In other words, the total transfer time calculation unit 422c repeatedly executes steps S13c to S18 until the input of process numbers stops.

In step S13c, the process number is read. The total transfer time calculation unit 422c reads the input process number.

In step S13d, the transfer time coefficient α of the processing number in the processing table is read. The total transfer time calculation unit 422c reads the transfer time coefficient α associated with the processing number read in step S13c from the processing table 423c.

In step S13e, the total transfer time coefficient Σα is calculated. The total transfer time calculation unit 422c calculates the sum of the transfer time coefficients α read in step S13d. In other words, the total transfer time calculation unit 422c adds the transfer time coefficients α each time it reads them. Therefore, the timing calculation unit 42c updates the transfer timing Tst in step S17 each time a processing number is input.

In step S18, it is determined whether or not reading of all process numbers has been completed. If the total transfer time calculation unit 422c determines that reading of all process numbers has been completed, the flow chart in FIG. 13 ends. If the total transfer time calculation unit 422c does not determine that reading of all process numbers has been completed, the flow returns to step S13c.

In the example of FIG. 14, the timing calculation unit 42c performs the above processing operation when the count value is updated to 003h. Processing numbers 03 and 04 are input to the timing calculation unit 42c with a count value of 003h. The basic transfer time Tba is then set to 010h (= 16d), the transfer time coefficient for processing number 03 is set to 011b (= 03d), and the transfer time coefficient for processing number 04 is set to 10b (= 02d). The predicted period is also set to 0105h (= 261d).

Each time a process number is received, the total transfer time calculation unit 422c obtains the transfer time coefficient α associated with that process number from the process table 423c. The total transfer time calculation unit 422c then adds that transfer time coefficient to the total transfer time Ttr. The total transfer time Ttr is calculated as 030h (=048d) when process number 03 is received, and as 050h (=080d) when process number 04 is received.

The transfer timing Tst is the predicted period Tpd minus the total transfer time Ttr. Therefore, the final transfer timing Tst is output as 0B5h (=181d), which is 0105h (=261d) minus the total transfer time Ttr 050h (=080d). Furthermore, the transfer processing item AR is read from the processing table and 01010000h is output.

＜Effects＞
The ECU of the third embodiment can achieve the same effect as the second embodiment. Furthermore, even if it is not determined with which angle interruption each process is to be executed, the ECU of the third embodiment can dynamically determine whether or not to perform advance transfer of the usage data by inputting a process number before the angle interruption timing at a predetermined angle. Therefore, the ECU of the third embodiment can improve the degree of freedom in design and reduce the process of reading the process table.

Fourth Embodiment
The ECU of the fourth embodiment will be described with reference to Figures 15, 16, 17, and 18. In this embodiment, differences from the first embodiment will be described. The ECU of the fourth embodiment differs from the first embodiment in the configurations and processing operations of the timing calculation unit 42d and the transfer start instruction unit 43d. Also, unlike the first embodiment, the ECU of the fourth embodiment does not calculate the transfer timing Tst. That is, the ECU of the fourth embodiment transfers the use data before the timing required for processing, without the timing calculation unit 42d calculating the transfer timing Tst.

<Configuration>
15 and 16, the timer module 4 includes a timing calculation unit 42d instead of the timing calculation unit 42a, and a transfer start instruction unit 43d instead of the transfer start instruction unit 43a.

As shown in FIG. 15, the timing calculation unit 42d includes a transfer process calculation unit 421d and a processing table 423d. The count value PC is input to the transfer process calculation unit 421d. The transfer process calculation unit 421d acquires a transfer process item AR linked to the count value PC from the processing table 423d. The transfer process calculation unit 421d then outputs the acquired transfer process item AR. The processing table 423d includes a transfer process item AR for each count value. The transfer process item AR is then linked to the count value.

In this way, the transfer process calculation unit 421d outputs the transfer process item AR corresponding to the count value without calculating the transfer timing Tst.

As shown in FIG. 16, the transfer start instruction unit 43d includes a transfer process item register 431d and a request output unit 435d. The transfer process item register 431d is similar to the transfer process item register 431a. An end signal is input to the transfer start instruction unit 43d. The end signal is input to the request output unit 435d. It can also be said that the end signal is input to the request output unit 435d instead of the transfer start signal.

The end signal is a signal indicating that the processing executed by cores 11 and 12 in response to the occurrence of an angle interrupt has ended. As described above, in CPU 1, first core 11 executes processing in response to the occurrence of an angle interrupt. Then, when the execution of processing by cores 11 and 12 ends, CPU 1 outputs (transmits) the end signal.

<Processing Operation>
The processing operation of the timing calculation unit 42d will be described with reference to Fig. 17. The timing calculation unit 42d starts the flow chart of Fig. 17 every time a crank signal is input.

Step S30 is the same as step S10. Step S31 is the same as step S11. Step S32 is the same as step S12.

In step S33, the transfer process item AR is obtained. The transfer process calculation unit 421d obtains the transfer process item AR linked to the incremental count value NPC from the process table 423d.

The transfer process calculation unit 421d may create a transfer process item AR. In this case, the process table 423d associates the count value PC with the process to be executed at the angle interrupt of the count value. The transfer process calculation unit 421d then obtains from the process table 423d the process to be executed at the timing when the added count value becomes NPC. The transfer process calculation unit 421d sets a bit corresponding to the obtained process to create a transfer process item AR.

The processing operation of the transfer start instruction unit 43d will be described with reference to FIG. 18. The transfer start instruction unit 43d starts the flowchart of FIG. 18 every time a crank signal is input. Step S40 is the same as step S20. Step S44 is the same as step S24.

In step S41, the transfer process item is read. The transfer start instruction unit 43d reads the transfer process item AR from the transfer process item register 431d.

In step S42, the end signal is read. The transfer start instruction unit 43d reads the end signal output from the CPU 1.

In step S43, it is determined whether output is complete. The transfer start instruction unit 43d determines whether output of the end signal by the CPU 1 is complete. If the transfer start instruction unit 43d determines that output of the end signal by the CPU 1 is complete, it proceeds to step S44, and if it does not determine that output is complete, it returns to step S42. Then, in step S44, a request signal is sent in the same way as in step S24.

In other words, the request output unit 435d transmits a request signal when the transfer process item AR and the end signal are input. At this time, the request output unit 435d transmits a request signal when the transfer process item AR is input and, for example, the rising edge of the end signal is detected.

In this way, when the end signal is output, the timer module 4 transfers the usage data to be used in the process executed in synchronization with the next angle signal from the RAM 3 to the local RAM 13. This allows the timer module 4 to transfer the usage data before the timing required for the process executed in synchronization with the next angle signal.

＜Effects＞
The ECU of the fourth embodiment can achieve the same effects as the ECU 100. Furthermore, since the ECU of the fourth embodiment does not calculate the transfer timing Tst, the processing load of the timer module 4 can be reduced compared to a configuration that calculates the transfer timing Tst.

Fifth Embodiment
The ECU of the fifth embodiment will be described with reference to Figures 19, 20, and 21. In this embodiment, differences from the first embodiment will be described. The ECU of the fifth embodiment differs from the first embodiment in the configuration and processing operation of a transfer start instruction unit 43e. That is, the transfer start instruction unit 43e differs from the transfer start instruction unit 43a in that it transmits a request signal corresponding to each data transfer to the DMAC 5.

<Configuration>
19, the transfer start instruction unit 43e includes a request update unit 436e in addition to the transfer start instruction unit 43a. Also, the transfer start instruction unit 43e includes a request output unit 435e instead of the request output unit 435a. The transfer process item register 431e is the same as the transfer process item register 431a. The transfer timing register 432e is the same as the transfer timing register 432a. The transfer timing counter 433e is the same as the transfer timing counter 433a. The timing comparison unit 434e is the same as the timing comparison unit 434a.

The request output unit 435e receives a processing number and a channel number. The request output unit 435e has multiple channels ch1 to chn for transmitting request signals. Based on the input channel number, the request output unit 435e selects a channel to use for transmitting the request signal from channels ch1 to chn. The request output unit 435e transmits the request signal corresponding to the processing number from the selected channel.

In other words, the request output unit 435e transmits a request signal for data to be used in the process indicated by the input process number from the corresponding channel ch1 to ch. Note that the request output unit 435e transmits, for example, the process number as the request signal. However, the present disclosure is not limited to this.

The request update unit 436e is a part that updates the channel that transmits the request signal. The request update unit 436e includes a next processing number register 4361e and a processing channel table 4362e. A transfer start instruction is input to the request update unit 436e. The request update unit 436e outputs the processing number and a channel number that indicates the channel to be used for transmitting the request signal. The request update unit 436e is also configured to be able to refer to the transfer processing item AR stored in the transfer processing item register 431e.

The next processing number register 4361e stores the processing number to be transferred next. The processing channel table 4362e individually links multiple statically determined processing numbers to multiple channel numbers. The channel number indicates which of the multiple channels ch1 to chn is to be used to transmit the request signal.

For example, process number 01 is linked to channel number 1h, which indicates channel ch1. In this case, the request output unit 435e transmits a request signal for the usage data to be used in the process of process number 01 from channel ch1.

The next process number register 4361e stores the process number to be transferred next based on the transfer process item AR in synchronization with the rising edge of the crank signal. The next process number register 4361e outputs the channel number corresponding to the currently stored process number, and the process number to be transferred next is updated each time a request signal is transmitted.

When the request update unit 436e sends a request signal, it refers to the transfer process item register 431e and checks each bit of the transfer process item AR in order. The request update unit 436e updates the next process number to be transferred by storing the process number for which a request signal has not been sent in the next process number register 4361e. In this way, the request update unit 436e sends a request signal for each process number for which transfer of usage data is required in the transfer process item AR. Note that the next process number register 4361e may update the next process number to be transferred each time the channel number corresponding to the currently stored process number is output.

When a transfer start signal is input, the request update unit 436e obtains from the processing channel table 4362e the channel number corresponding to the processing number stored in the next processing number register 4361e. The request update unit 436e then transmits this processing number and channel number to the request output unit 435e.

<Processing Operation>
The processing operation of the transfer start instruction unit 43e will be described with reference to Fig. 20. The transfer start instruction unit 43e starts the flowchart of Fig. 20 every time a crank signal is input. Note that step S50 is the same as step S20. Step S52 is the same as step S21. Step S53 is the same as step S22. Step S54 is the same as step S23. Step S58 is the same as step S24. Thus, like the timing comparison unit 434a, the timing comparison unit 434e outputs a transfer start signal when it is determined that the count value and the register value match.

In step S51, the transfer process item AR is read and the next process number register is updated. The request update unit 436e reads the transfer process item AR by referring to the transfer process item register 431e in synchronization with the rising edge of the crank signal. The request update unit 436e stores the next process number to be transferred from the transfer process item AR in the next process number register 4361e.

When a transfer start instruction is input, the request update unit 436e executes step S55. In step S55, the next processing number register is read. The request update unit 436e reads the next processing number register 4361e and obtains the processing number stored in the next processing number register 4361e.

In step S56, the processing channel table is read. The request update unit 436e reads the processing channel table 4362e and obtains the channel number corresponding to the processing number obtained in step S55. Steps S55 and S56 are performed to select the channel for transmitting the request signal this time.

In step S57, the processing number and the channel number are output. The request update unit 436e outputs the processing number obtained in step S55 and the channel number obtained in step S56.

In step S58, a request signal is transmitted. The request output unit 435e transmits a request signal corresponding to the processing number from a channel selected based on the input channel number.

In step S59, it is determined whether or not the transmission of all request signals has been completed. The request update unit 436e determines whether or not the transmission of all request signals has been completed. In other words, all request signals are request signals that correspond to all use data (processing numbers) that are to be transferred in the current angle interrupt. The request update unit 436e can determine whether or not the transmission of all request signals has been completed from the transfer processing item AR and the processing number corresponding to the transmitted request signal.

Then, if the request update unit 436e determines that the transmission of all request signals has been completed, it ends the flowchart in FIG. 20. On the other hand, if the request update unit 436e does not determine that the transmission of all request signals has been completed, it proceeds to step S60.

Step S60 updates the next process number register. When the request update unit 436e transmits the request signal, it updates the next process number register. The request update unit 436e refers to the transfer process item register 431e and updates the process number to be transferred next in the next process number register 4361e.

In the example of FIG. 21, the value of the transfer timing Tst output from the timing calculation unit 42a is 00111101 (=61d). 00111101 (=61d) is stored in the transfer timing register 432e in synchronization with the rising edge of the crank signal. In addition, the transfer timing counter 433e starts counting in synchronization with the rising edge of the crank signal.

The request update unit 436e also updates the next processing number register 4361e based on the transfer processing item AR output from the timing calculation unit 42a. At this time, if the transfer processing item AR is 8 bits and is 01010101b, the transfer of the data to be used in the processing of the second bit from the beginning is to be performed. Therefore, 2 is stored in the next processing number register 4361e.

In addition, in the processing channel table 4362e, processing number 02 is linked to channel number 2h indicating channel ch2, and processing number 04 is linked to channel number 4h indicating channel ch4. Therefore, when 2 is stored in the next processing number register 4361e, the request update unit 436e obtains channel number 2h.

Then, as described above, the request update unit 436e receives the transfer start instruction and executes steps S54 to S58. Therefore, the request output unit 435e transmits the first request signal corresponding to process number 02 from channel ch2.

Then, the request update unit 436e executes step S59. The request update unit 436e updates the value of the next processing number register 4361e to 4. Furthermore, if 4 is stored in the next processing number register 4361e, the request update unit 436e acquires channel number 4h. Then, the request output unit 435e transmits a second request signal corresponding to processing number 04 from channel ch4.

The request update unit 436e repeatedly updates the next processing number register 4361e, obtains the channel number, outputs the processing number and channel number, and transmits the request signal until transmission of all request signals is complete. When transmission of all request signals is complete, the request update unit 436e stops counting by the transfer timing counter 433e and stops updating the next processing number register 4361e.

＜Effects＞
The ECU of the fifth embodiment can achieve the same effects as the ECU 100. Furthermore, the ECU of the fifth embodiment can perform data transfer even in a case where data transfer is to be performed from a plurality of transmission sources to a plurality of transmission destinations.

Sixth Embodiment
An ECU 110 according to the sixth embodiment will be described with reference to Fig. 22. In this embodiment, differences from the first embodiment will be described. The ECU 110 differs from the ECU 100 mainly in the configuration of the CPU 1.

CPU1 has two cores 11 and 12 and two local RAMs 13a and 13b. CPU1 also has a pair of cores and local RAMs that require the shortest access time.

Of the two local RAMs 13a and 13b, the first core 11 requires the shortest time to access the first local RAM 13a. Of the two local RAMs 13a and 13b, the second core 12 requires the shortest time to access the second local RAM 13b. Therefore, it can be said that the first core 11 is paired with the first local RAM 13a. Also, it can be said that the second core 12 is paired with the second local RAM 13b.

The CPU 1 may have three or more cores. The CPU 1 may also have three or more local RAMs.

The timer module 4 and DMAC 5 transfer the usage data to the local RAM that is paired with the core that uses the usage data. In other words, the timer module 4 and DMAC 5 transfer the usage data used by the first core 11 for processing to the first local RAM 13a. The timer module 4 and DMAC 5 also transfer the usage data used by the second core 12 for processing to the second local RAM 13b.

The ECU of the sixth embodiment can achieve the same effect as the ECU 100. The ECU of the sixth embodiment can reduce the time required for each of the cores 11 and 12 to read the usage data compared to the case where the usage data is transferred to an unpaired local RAM. Therefore, the cores 11 and 12 can execute processes involving complex calculations and processes using a large amount of usage data, similar to the first embodiment.

Although the present disclosure has been described with reference to an embodiment, it is understood that the present disclosure is not limited to the embodiment or structure. The present disclosure also encompasses various modifications and modifications within the scope of equivalents. In addition, while various combinations and forms are shown in the present disclosure, other combinations and forms including only one element, more, or less are also within the scope and concept of the present disclosure.

10...microcomputer, 1...CPU, 11...first core, 12...second core, 13...local RAM, 2...ROM, 3...RAM, 4...timer module, 41...first timer, 411...period measurement unit, 412...period prediction, 42a...timing calculation unit, 43...second timer, 43a...transfer start instruction unit, 5...DMAC, 6...ADC, 7...I/O, 20...power supply circuit, 31...input circuit, 32...output circuit, 100, 110...ECU, 200...battery, 210...igniter, 220...injector, 230...cam sensor, 231...camshaft, 232...cam rotor, 240...crank sensor, 241...crankshaft, 242...crank rotor

Claims (3)

An engine control device that performs processing in synchronization with an angle of an engine crankshaft,
an acquisition unit (31) for acquiring an angle signal according to the angle;
A storage device (3) for storing at least one piece of data to be used in the processing;
a processor (1) having at least one processor (11, 12) for executing the process in synchronization with the angle signal, and at least one memory unit (13, 13a, 13b) that can be accessed in a shorter time than when the processor accesses the memory device;
a transfer unit (4, 5) that transfers use data, which is the data used by the calculation unit for the processing to be executed, from the storage device to the storage unit in advance before the use data is required for the processing to be executed ,
The transfer unit is
A prediction unit (412) for predicting a predicted period in which the angle signal is input;
a timing acquisition unit (42a) that acquires a transfer timing for starting the transfer of the usage data based on the predicted period;
The timing acquisition unit acquires the transfer timing by subtracting a predetermined transfer specified time, which corresponds to the transfer time of the usage data from the storage device to the storage unit, from the predicted period . An engine control device that performs processing in synchronization with an angle of an engine crankshaft,
an acquisition unit (31) for acquiring an angle signal according to the angle;
A storage device (3) for storing at least one piece of data to be used in the processing;
a processor (1) having at least one processor (11, 12) for executing the process in synchronization with the angle signal, and at least one memory unit (13, 13a, 13b) that can be accessed in a shorter time than when the processor accesses the memory device;
a transfer unit (4, 5) that transfers use data, which is the data used by the calculation unit for the processing to be executed, from the storage device to the storage unit in advance before the use data is required for the processing to be executed ,
The transfer unit is
A prediction unit (412) for predicting a predicted period in which the angle signal is input;
a timing acquisition unit (42a) that acquires a transfer timing for starting the transfer of the usage data based on the predicted period;
The timing acquisition unit calculates a total transfer time required to transfer the usage data from the storage device to the storage unit by multiplying a predetermined basic transfer time of the data by the number of processes scheduled to be executed, and acquires the transfer timing by subtracting the total transfer time from the predicted period . An engine control device that performs processing in synchronization with an angle of an engine crankshaft,
an acquisition unit (31) for acquiring an angle signal according to the angle;
A storage device (3) for storing at least one piece of data to be used in the processing;
a processor (1) having at least one processor (11, 12) for executing the process in synchronization with the angle signal, and at least one memory unit (13, 13a, 13b) that can be accessed in a shorter time than when the processor accesses the memory device;
a transfer unit (4, 5) that transfers use data, which is the data used by the calculation unit for the processing to be executed, from the storage device to the storage unit in advance before the use data is required for the processing to be executed ,
The transfer unit is
A prediction unit (412) for predicting a predicted period in which the angle signal is input;
a timing acquisition unit (42a) that acquires a transfer timing for starting the transfer of the usage data based on the predicted period;
The timing acquisition unit calculates a total transfer time required to transfer the usage data from the storage device to the storage unit by multiplying a predetermined basic transfer time of the data by transfer time information specific to the usage data used in the process to be executed, and acquires the transfer timing by subtracting the total transfer time from the predicted period.

Images