BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a schematic diagram showing a configuration of the control equipment.
FIG. 2 is a schematic diagram showing a configuration of a communication unit of a device driver.
FIG. 3 is a communication timing chart without an interrupt-not-required mode.
FIG. 4 is a communication timing chart for switching between an interrupt-not-required mode and an interrupt mode.
FIGS. 5A, 5B and 5C are SPI driver configuration tables.
FIGS. 6A and 6B are job function correspondence tables.
FIGS. 7A and 7B are transmission tables.
FIG. 8 is a processing flow in an SPI job registration.
FIG. 9 is a processing flow for starting an interrupt-not-required mode.
FIG. 10 is a processing flow for a data set table.
FIG. 11 is a processing flow for a data set.
FIG. 12 is a processing flow for a data read.
FIG. 13 is a processing flow for a command set.
FIG. 14 is a processing flow for a data read table.
FIG. 15 is a processing flow for starting an interrupt mode transmission.
FIG. 16 is a processing flow for an interrupt.
FIG. 17 is a processing flow for the next queue.
FIGS. 18A and 18B illustrate a processing flow for a Send microcomputer B and a processing flow for an Rx Microcomputer B.
FIGS. 19A and 19B illustrate a processing flow for a Send Diagnostic 1 and a processing flow for an Rx Diagnostic 1.
FIGS. 20A and 20B illustrate a processing flow for a Send Diagnostic 2 and a processing flow for an Rx Diagnostic 2.
DESCRIPTION OF THE EMBODIMENTS
A control equipment with a built-in communication function that can reduce the load of communication processing without changing the hardware configuration by making improvements on software is realized.
Embodiment 1
FIG. 1 shows a configuration of the control equipment. The control equipment 1 is connected with a sensor 2 and an actuator 3 and also connected through a network 4 to other control equipment 5. Two or more sets of sensor 2, actuator 3, network 4 and other control equipment 5 may be provided. The control equipment 1 includes a microcomputer-A 11, a microcomputer-B 6, IC_A 7, IC_B 8, IC_C 9 and IC_D 10. Further, although ports are shown to connect to a virtual_A 71 and a virtual_B 72, the virtual_A 71 and virtual_B 72 do not physically exist. The microcomputer-A 11 has a memory 111, a CPU 112 and a peripheral module 113. Through the peripheral module 113 the microcomputer-A 11 is connected to the network 4, sensor 2, actuator 3, microcomputer-B 6, IC_A 7, IC_B 8, IC_C 9 and IC_D 10. The memory 111 has an application program 1111, a device driver 1112 and an OS 1113. For the SPI communication, the device driver 1112 has a mode switching process 11121, an interrupt-not-required mode process 11122 and an interrupt mode process 11123.
FIG. 2 is a functional diagram associated with an SPI communication software unit of the device driver 1112 of the microcomputer-A 11. The device driver comprises communication software and an SPI driver. An application program hands a request to the communication software. The communication software, according to the request given, identifies the device to communicate with, from among the microcomputer-B, IC_A 7, IC_B 8, IC_C 9 and IC_D 10, and then communicates with the identified device. The peripheral module SPI_A 11131 is connected to the microcomputer-B 6, the peripheral module SPI_B 11132 is connected to the IC_A 7, IC_B 8 and virtual_A 71, and the peripheral module SPI_C 11133 is connected to the IC_C 9, IC_D 10 and virtual_B 72. The virtual_A 71 and virtual_B 72 do not exist physically.
FIG. 3 shows a flow of processing for transmission to the microcomputer-B 6. When the application program issues a request in the form of an event 201 using a transmission start function, the communication software registers the request with a job queue. The job registered with the job queue is processed by the SPI driver to start the transmission process corresponding to the job name. FIGS. 6A and 6B show a job-function correspondence table 111213. A transmission function corresponding to the job MiB 1112137 is Send Microcomputer-B, which sets data C0-C7 and a transmission destination and then starts transmission. When the transmission is complete, a transmission completion interrupt starts an SPI driver interrupt handler, which in turn starts an Rx Microcomputer-B that executes a reception operation for the job MiB. At event 202 the similar processing to that of event 201 is executed, with C8 to C15 set as the transmission data. In the figure, “McrB” represents the microcomputer-B.
FIG. 4 shows a flow of communication that requires switching between the interrupt-not-required mode and the interrupt mode. An initial state is an interrupt mode. At event 203 a transmission buffer is set with d0 to d3 as transmission data and with virtual_A, IC_A and IC_B as destinations. At event 204, an interrupt-not-required mode start function causes indices 0 to 3 of the transmission buffer to be transmitted repetitively. At event 205 there is a request to set the value of signal SigA to 1. A data setting function sets data d4 using the SigA value of 1. At event 206, when there is a request for diagnostic, Job Diagnostic 1 is set in the job queue. An SPI job registration function switches the mode from the interrupt-not-required mode to the interrupt mode and starts Send Diagnostic 1, the transmission function for the registered Job Diagnostic 1. The Send Diagnostic 1 sets transmission data e0-e30 with virtual_A, IC_A and IC_B as destinations, as shown in Table 2 in FIG. 7B. IC_A and IC_B are required to have their communications separated more than a predetermined delay time apart. In this embodiment, the delay time is assumed to be able to be created by using two transmission durations. Here, the first two transmissions are set with virtual_A as the destination and the third transmission is set with a destination of IC_A. The reason that two transmissions in which IC_A does not receive are provided is that if the previous communication has ended with the transmission to IC_A and if a new transmission is immediately initiated to the same IC_A, the required delay time fails to be secured.
Although at event 208 there is an entry of a separate Job Diagnostic 2, since Job Diagnostic 1 is currently being transmitted, the transmission of Job Diagnostic 2 is not initiated at this timing. After the reception operation of Job Diagnostic 1 is finished, Job Diagnostic 1 is taken out of the job queue and the next Job Diagnostic 2 is processed. At this time, the transmission operation for Job Diagnostic 2 is started to set and transmit data e32-e37. At the end of the transmission, the SPI driver starts the reception operation for Job Diagnostic 2. With Job Diagnostic 2 completed, the mode changes to the interrupt-not-required mode as there are no requested jobs. In this mode, the indices 0-3 of the transmission buffer are repetitively transmitted as described before. At event 207, there is a request to set the value of signal SigB to 1, so data d5 that causes the signal SigB value to become 1 is set. At event 211 there is a request to set the value of SigA to 0, so data d6 that causes the SigA value to become 0 is set.
As described above, in the interrupt-not-required mode since a completion interrupt is prevented by hardware repetitively transmitting data, unnecessary reception operation is not started. Further, a delay can be generated by hardware transmitting the data to a virtual device, thus reducing the load of software. Also, when it is desired to change the transmission data, it can be done simply by changing the transmission data in the transmission buffer. When it is desired to cancel the transmission to IC_A, this can be done by changing the destination from IC_A to a virtual device. The transmission buffer used in the interrupt mode avoids a buffer area used by the interrupt-not-required mode. This allows the data, which is to be transmitted in the interrupt-not-required mode, to be updated irrespective of the mode, even during the interrupt mode, as with event 207 and event 211. In the figure, V_A represents Virtual_A; I_A represents IC_A; and I_B represents IC_B.
FIGS. 5A and 5B show functions and data provided by the SPI driver. The mode switching process 11121 comprises an interrupt-not-required mode start 111211, an SPI job registration 111212, a job function correspondence table 111213, and a job queue 111214. The interrupt-not-required mode process 11122 comprises a data set 111221, a data read 111222, and a command set 111223. The interrupt mode process 11123 comprises a data set table 111231, a data read table 111232, an interrupt mode transmission start 111233, and an interrupt operation 111234.
FIGS. 6A and 6B show the job function correspondence table 111213 for SPI_1 and SPI_2.
FIGS. 7A and 7B show tables to update the transmission buffer. Table 1 (FIG. 7A) represents the content of a table used by event 203 of FIG. 4. Table 2 (FIG. 7B) represents the content of a table used by event 206. Looking at the transmission destination of IC_A, it is seen that a delay of two transmissions or more is provided between the destinations by sending data to other devices. The same also applies to IC_B.
FIG. 8 shows a processing flow of the SPI job registration. If the job queue is empty, a job is registered with the job queue and the transmission operation is started. At this time, if the interrupt-not-required mode is active, the mode is switched to the interrupt mode. If the jog queue is not empty, the job is registered with the job queue and the processing is ended.
FIG. 9 shows a processing flow of the interrupt-not-required mode start. If the specified len is 0, the interrupt-not-required mode operation is ended without performing anything. If len is not 0, the register is so set as to cause the length from start to len to be transmitted repetitively. Then, the communication is started. The start and len thus set are stored.
FIG. 10 shows a processing flow of the data set table. The specified table content from start address to len is copied to the transmission buffer beginning with a start address.
FIG. 11 shows a processing flow of the data set. Data is updated to the data of the transmission buffer at an index address.
FIG. 12 shows a processing flow of the data read. Data of the reception buffer at an index address is reported.
FIG. 13 shows a processing flow of the command set. Data of the transmission buffer for the destination at an index address is updated.
FIG. 14 shows a processing flow of the data read table. Data of the reception buffer from the start address to len is copied to rx_data_ptr address.
FIG. 15 shows a processing flow of the interrupt mode transmission start. First, the communication is stopped. Next, the register is so set that the communication will be restarted from the start address of the transmission buffer and that, after the len of data is transmitted, a completion interrupt will come in. Then, the communication is started.
FIG. 16 shows a processing flow of the interrupt operation. The interrupt operation is prepared for each of the modules SPI_1, SPI_2 and SPI_3. First, an interrupt bit is cleared and the reception operation corresponding to the current job is started from the job queue. Then, the next queue operation is started.
FIG. 17 shows a processing flow of the next queue operation. The current job is picked up from the job queue. Next, if the job queue is empty, the interrupt-not-required mode start is executed. At this time, the start and len are given the previously stored values. When the interrupt-not-required mode is not used, as in FIG. 3, an initial value is specified. That is, len=0 and the mode is not switched to the interrupt mode. If the job queue is not empty, the transmission operation for the next job is started.
FIGS. 18A and 18B illustrate processing flows of Send Microcomputer-B 1112138, which is the transmission operation for the Job Microcomputer-B, and of Rx Microcomputer-B 1112139, which is the reception operation for the Job Microcomputer-B. The Send Microcomputer-B 1112138 uses a data set table function to set 8-byte data and a transmission destination. The Rx Microcomputer-B 1112139 uses a data read table function to copy the data of the reception buffer to table_miB_rx.
FIGS. 19A and 19B illustrate processing flows of Send Diagnostic 1, which is the transmission operation for the Job Diagnostic 1, and of Rx Diagnostic 1, which is the reception operation for the Job Diagnostic 1. The Send Diagnostic 1 uses the data set table function to set data and a transmission destination and then starts the transmission. The Rx Diagnostic 1 uses the data read table function to copy the data of the reception buffer and performs diagnostic analysis on the data.
FIGS. 20A and 20B illustrate processing flows of Send Diagnostic 2, which is the transmission operation for the Job Diagnostic 2, and of Rx Diagnostic 2, which is the reception operation for the Job Diagnostic 2. The Send Diagnostic 2 uses the data set table function to set data and a transmission destination and then starts the transmission. The Rx Diagnostic 2 uses the data read table function to copy the data of the reception buffer and performs diagnostic analysis on the data.
The present invention is applicable to control equipment with a built-in communication apparatus, including automotive control equipment.
It should be further understood by those skilled in the art that although the foregoing description has been made on embodiments of the invention, the invention is not limited thereto and various changes and modifications may be made without departing from the spirit of the invention and the scope of the appended claims.
Patent Application
20080016257
