JP4725557B2 - Configuration code generation device and program for configuration code generation device - Google Patents

Description

  The present invention relates to a configuration code generation device and a program for a configuration code generation device.

  Conventionally, in development of an ECU that is mounted on a vehicle and performs data communication with other ECUs in the vehicle, a program that is executed by a CPU mounted on the ECU is divided into a software platform (hereinafter referred to as software PF) and an application. A creation method is employed (see, for example, Patent Document 1).

  The software PF is a program group for directly driving the hardware of the ECU on which the CPU is mounted. Therefore, the configuration of the software PF strongly depends on the hardware configuration of the ECU. Examples of the software PF include an OS (for example, OSEK-OS (registered trademark)) and a device driver.

  The application is a program group that drives the hardware of the ECU on which the CPU is mounted by using the function provided by the software PF. As an application, for example, if the ECU is an engine ECU, various amounts (accelerator opening, engine rotation speed, etc.) necessary for calculating the engine ignition timing are transferred to another ECU (or another CPU in the same ECU). ), The ignition timing is calculated from the received information, and there is a program for realizing the process of controlling the injector so that the calculated ignition timing is realized.

  The use of the function provided by the software PF is, for example, the operation of the software PF using hardware (for example, output of a control signal to an actuator, acquisition of a detection signal from a sensor, communication with another ECU) This is realized by providing an application interface (hereinafter referred to as API) for executing signal transmission / reception, and calling the API as required by the application.

  Software PF installed in different ECUs often provides a common API to applications. Therefore, it is not necessary to code the application in consideration of the hardware configuration of the ECU in creating the application.

  Further, as shown in the software hierarchy diagram of FIG. 2, a method of further developing the configuration code 2 is employed as a part of the software PF1 or different from the software PF1 and the configuration code 2.

  The configuration code includes detailed information of communication data handled by the application. Communication data handled by an application refers to data that the application passes to and from another application executed by another CPU. When the communication partner application is executed by another CPU in the same ECU, the communication data is data for inter-CPU communication. When the communication partner application is executed by a CPU in another ECU, the communication data is communication data between ECUs.

  The configuration code includes a program for realizing transmission or reception of the communication data using the software PF. Specifically, the program for realizing transmission or reception of communication data using the software PF is a function program for data transmission / reception (hereinafter referred to as communication data function). These communication data functions use an API provided by the software PF. The application is described so as to realize data transmission / reception by calling communication data functions for data transmission / reception.

  A configuration code in a certain CPU is usually configured to have one data transmission / reception function for each type of communication data handled by all applications executed by the CPU.

As shown in FIG. 3, an execution image (ie, object code) of a program for a CPU is created by compiling and linking the software PF, configuration code, and application for the CPU.
JP 2000-330775 A “Specification of RTE Software”, [online], May 5, 1996, AUTOSAR GbR, Internet <URL: http://www.autosar.org/download/R2.0/AUTOSAR SWS_RTE.pdf>

  FIG. 4 schematically shows a proposal of a configuration code generation method. The configuration code 8 is created by executing the configuration tool 7 which is a program executed in a normal computer 50.

  FIG. 5 is a flowchart showing an outline of a procedure for creating a configuration code using the configuration tool 7. As shown in this figure, the user creates an application design information table based on the application specification 4 and inputs it to the configuration tool 7 (step 110), creates a system design information table based on the system specification 5 and configures it. Input to the tool 7 (step 120), create a communication resource design information table based on the communication specification 6 and input to the configuration tool 7 (step 130). Then, when the user issues a predetermined execution command to the configuration tool 7, the configuration tool 7 generates a configuration code from these design information tables (step 140).

  The application design information table is data indicating a correspondence relationship between a transmission application that is a transmission source of the communication data of the type and a reception application that is a destination of the communication data of the type for each of a plurality of types of communication data transmitted and received by the application. is there.

  In the system design information table, for each of a plurality of CPUs in a plurality of ECUs mounted in the vehicle, the correspondence relationship between the ECU mounting the CPU, the communication bus connected to the CPU, and the application executed by the CPU It is data which shows.

  One communication resource design information table is created for each CPU. Each communication resource design information table has summary data, relevance determination data, detailed data, and resource mapping data. The summary data is data indicating a correspondence relationship between a transmission CPU that is a transmission source of the communication data of the type and a reception CPU that is a destination of the communication data of the type for each of a plurality of types of communication data. The relevance determination data is data indicating whether the CPU is involved in transmission / reception of the communication data. The detailed data is data indicating details (for example, transmission cycle) of the communication data. The resource mapping data is data indicating a correspondence relationship between a name when the communication data is referred from the platform side and a name when the communication data is referred from the application side.

  In steps 110, 120, and 130, the user manually inputs various information to the configuration tool 7, thereby completing the creation of the application design information table and the system design information table. FIG. 13 shows the work procedure of step 130 in more detail. As shown in this figure, in step 130, the user first sets the outline data in the communication resource design information table (step 410), and then sets the resource mapping data manually (step 420). Subsequently, the user sets the relevance determination data manually (step 420). Finally, the user sets the detailed data manually (step 430). In the manual input in steps 410 to 440, the user refers to the data of communication specification 6.

The application design information table, the system design information table, and the communication resource design information table are created by the procedure as described above, and the configuration code is automatically generated based on these tables . The standard specification of the configuration code (RTE) is described in Non-Patent Document 1, for example.

  However, since the creation of the application design information table, system design information table, and communication resource design information table is not automated, the burden on the user is large. The present invention has been made in view of the above points, and has an object to reduce input work by a user of information necessary for creating a configuration code in the development of a configuration code for a CPU mounted on an in-vehicle ECU.

  The inventor paid attention to the fact that the information for determining the contents of the relevance determination data is prepared when the contents of the application design information table and the communication resource design information table are determined.

A feature of the present invention for achieving the above object is that one of a plurality of CPUs mounted on any of a plurality of ECUs mounted on a vehicle and performing data communication with each other via a plurality of communication buses, the single CPU CPU (hereinafter, first referred 1CPU) process for generating object code to implement the operation of the first 1CPU by compiling and linking the software platform and the first 1CPU application, used in, a configuration codes for the first 1CPU, configuration code, including a program for the first 1CPU realize the transmission or reception of the communication data by using the software platform together including information of the communication data to be relayed The raw The present invention relates to a configuration code generation device to be configured.

  The configuration code generation device includes a storage medium and an arithmetic circuit. The arithmetic circuit includes a first recording unit that receives an input of the application design information table and records it on the storage medium, and a second recording unit that receives an input of the system design information table and records it on the storage medium. Yes.

  Here, the application design information table is a correspondence relationship between the transmission application of the transmission source and the reception application of the destination for each of a plurality of types of communication data transmitted by the plurality of applications respectively executed by any of the plurality of CPUs. It is data which shows.

  In addition, the system design information table indicates which of the plurality of ECUs each of the plurality of CPUs is mounted on, and which of the plurality of communication buses each of the plurality of CPUs is connected to. And data indicating a correspondence relationship between each of the plurality of CPUs and which of the plurality of applications is executed.

The arithmetic circuit has a relevance recording unit that creates relevance determination data for the first CPU based on information recorded by the first and second recording units and records the relevance determination data in the storage medium. Yes. The relevance determination data specifies communication data related to communication by the target first CPU .

  Further, the arithmetic circuit has configuration code generation / recording means for generating the configuration code based on the information recorded by the first and second recording means and the relationship recording means and recording the configuration code on the storage medium. ing.

  As described above, the configuration code generation apparatus automatically generates and records relevance determination data necessary for generating the configuration code. As specific means for the generation, the relevance recording means has the following first to third specifying means.

  The first specifying means, based on the application design information table, is a source transmission application and destination address for each of a plurality of types of communication data transmitted by a plurality of applications respectively executed by any of the plurality of CPUs. Identify the receiving application.

  The second specifying means further applies the specifying result of the first specifying means to the system design information table, so that a plurality of types of communication data transmitted by a plurality of applications respectively executed in any of the plurality of CPUs. To which of a plurality of predetermined route patterns is specified.

If the corresponding route pattern is a route pattern relayed by the CPU of the gateway based on the result of the specification of the second specifying device, the third specifying unit is the first CPU serving as a gateway in the communication route. Depending on whether or not, the first CPU specifies whether or not to relay the communication data , and the identification result is recorded in the storage medium as the plurality of relevance determination data.

  As described above, for each communication data, the communication data path is specified from the transmission application-reception application relationship in the application design information table and the system configuration in the system design information table, and the path pattern is specified. Information relating to which CPU is involved in communication data delivery, that is, relevance determination data can be automatically specified by a method associated with a route pattern.

  In addition, since the content of the relevance determination data is reflected in the configuration code for each CPU created in this way, the CPU does not transmit or receive, and the gateway (that is, the relay role) also Communication data that does not become necessary, that is, data that the CPU does not participate in delivery is generated so as not to include detailed information of the data, and is generated so as not to include a communication data function that handles the data. Therefore, the size of the generated execution image is reduced, and as a result, the ROM capacity of the ECU can be used more efficiently.

  In addition, the feature of the configuration code generation device of the present invention can be understood as a program.

  Hereinafter, an embodiment of the present invention will be described. FIG. 1 shows an example of a state in which a plurality of ECUs (ECU-E01, ECU-E02, ECU-E03) are connected to one or both of communication buses B1 and B2 in the vehicle in the communication system 60. Show. The present embodiment relates to a procedure for creating a program to be executed by a CPU (CPU-C01, CPU-C02, CPU-C03, CPU-C04) mounted on each of the plurality of ECUs and an apparatus used in the creation procedure. explain.

  FIG. 2 shows a software hierarchical structure of a program group executed in each of CPU-C01, CPU-C02, CPU-C03, and CPU-C04. A program executed by each CPU is divided into a software platform (hereinafter referred to as software PF) 1, a configuration code (referred to as a configuration code in the drawing) 2, and an application 3. The configuration code 2 may be regarded as a part of the software PF1, or may be regarded as a separate one from the software PF1.

  The software PF is a program group for directly driving the hardware of the ECU on which the CPU is mounted. Therefore, the configuration of the software PF strongly depends on the hardware configuration of the ECU. Examples of the software PF include an OS (for example, OSEK-OS (registered trademark)) and a device driver.

  The application is a program group that drives the hardware of the ECU on which the CPU is mounted by using the function provided by the software PF. As an application, for example, if the ECU is an engine ECU, various amounts (accelerator opening, engine rotation speed, etc.) necessary for calculating the engine ignition timing are transferred to another ECU (or another CPU in the same ECU). ), The ignition timing is calculated from the received information, and there is a program for realizing the process of controlling the injector so that the calculated ignition timing is realized.

  The use of the function provided by the software PF is, for example, the operation of the software PF using hardware (for example, output of a control signal to an actuator, acquisition of a detection signal from a sensor, communication with another ECU) This is realized by providing an application interface (hereinafter referred to as API) for executing signal transmission / reception, and calling the API as required by the application.

  Software PF installed in different ECUs often provides a common API to applications. Therefore, it is not necessary to code the application in consideration of the hardware configuration of the ECU in creating the application.

  The configuration code includes detailed information (for example, transmission / reception cycle, initial value, fail value) of communication data handled by the application. Communication data handled by an application refers to data that is transferred to and from another application executed by another CPU. When the communication partner application is executed by another CPU in the same ECU, the data is data for inter-CPU communication. When the communication partner application is executed by a CPU in another ECU, the communication data is communication data between ECUs. The configuration code includes a program for realizing transmission or reception of the communication data using the software PF. Specifically, the program for realizing transmission or reception of communication data using the software PF is a function program for transmitting and receiving communication data (hereinafter referred to as communication data function). These communication data functions use an API provided by the software PF. The application is described so as to realize data transmission / reception by calling communication data functions for data transmission / reception.

  A configuration code in a certain CPU has one data transmission / reception function for each type of communication data handled by all applications executed by the CPU.

  As shown in FIG. 3, an execution image (that is, object code) of a program for a CPU is compiled by linking software PF, configuration code, and application for the CPU (in this specification, it is a static link). ) To create.

  FIG. 4 schematically shows a configuration code generation method. The configuration code 8 is created by processing of the configuration tool 7 which is a program executed in a normal computer (corresponding to an example of a configuration code generation device) 50.

  The computer 50 includes an arithmetic circuit (not shown), a RAM, a ROM, a hard disk drive (corresponding to an example of a storage medium), and an operation device (a keyboard, a mouse, etc.). The arithmetic circuit reads and executes the configuration tool 7 stored in the RAM or the hard disk drive. When the arithmetic circuit is executing the configuration tool 7, the user who is the creator of the configuration code 8 creates the configuration code by referring to the information such as the application specification 4, the system specification 5, and the communication specification 6. Necessary information is configured, and the configured information is input to the arithmetic circuit by operating the operating device. The arithmetic circuit generates the configuration code 8 based on the input information and records it in the hard disk drive. The compiling, linking, and execution image generation processing shown in FIG. 3 may be performed by an arithmetic circuit of the computer 50, or may be performed by a device other than the computer 50. Good.

  FIG. 5 is a flowchart showing an outline of a procedure for creating a configuration code using the configuration tool 7. As shown in this figure, the user creates an application design information table as illustrated in FIG. 6 based on the application specification 4 and inputs it to the configuration tool 7 (step 110). A system design information table as illustrated in FIG. 8 is created and input to the configuration tool 7 (step 120), and a communication resource design information table as illustrated in FIG. Input (step 130). Then, when the user issues a predetermined execution command to the configuration tool 7, the configuration tool 7 generates a configuration code from these design information tables (step 140).

  As shown in FIG. 6, the application design information table is composed of records for each type of communication data handled by the application. Each record refers to the application name of the target data type (that is, the communication data is referred to from the application). Name), the name of the sending application that is the source of the communication data of the type, the name of the receiving application that is the destination of the type of communication data, and details of the communication data of the type (initial value, fail value, etc.) including. Therefore, by referring to the application design information table, for each of a plurality of types of communication data, the correspondence relationship between the transmission application that is the transmission source of the communication data of the type and the reception application that is the destination of the communication data of the type can be understood. . Note that one application design information table is created for a plurality of applications executed in the communication system 60.

  As shown in FIG. 7, the system design information table has a record for each communication bus used in the communication system 60. The record includes the name of the target communication bus, the protocol name used in the communication bus, and the A CPU list connected to the communication bus is recorded. In addition, in the CPU list, for each CPU connected to the communication bus, an application executed on the CPU and information on an ECU on which the CPU is mounted are recorded. Therefore, by referring to the communication resource design information table, the ECU on which the CPU is mounted, the communication bus connected to the CPU, and the application executed by the CPU are known for each of the plurality of CPUs.

  In the communication system 60 shown in FIG. 1, as shown in FIG. 7, the CPU-C01 executes the application A01 and is mounted on the ECU-E01, and the CPU-C02 executes the application A02 and the ECU The CPU-C03 executes the application A03 and is mounted on the ECU-E02. The CPU-C04 executes the applications A04 and A05 and is mounted on the ECU-E03.

  Further, CPU-C01 and CPU-C03 are connected to the bus B1, and CPU-C02 and CPU-C04 are connected to the bus B2. In order for CPUs not connected to the same bus to communicate with each other, it is necessary to use other CPUs as relay points (hereinafter referred to as gateways). For example, in order for the CPU-C03 and the CPU-C04 to communicate, the communication data must be transferred via the path C03 → C01 → C02 → C04 or vice versa. In this case, communication between C01 and C02 is inter-CPU communication.

  One communication resource design information table is created for each CPU. As shown in FIG. 8, each communication resource design information table has summary data, relevance determination data, detailed data, and resource mapping data for each communication data exchanged in the communication system 60.

  The summary data includes the network name of the target communication data (that is, the name when the communication data is referenced from the software PF (for example, a device driver)), the name of the data frame carrying the communication data, and the communication data It includes information on the transmission CPU that is the transmission source and the reception CPU that is the destination of the communication data.

  The relevance determination data includes information on whether or not the own CPU (that is, a CPU that is a target of the communication resource design information table) is involved in the delivery of the communication data (hereinafter referred to as own CPU related information), and Information on whether or not the CPU is a gateway for the communication data (hereinafter referred to as GW information) is included. Whether or not the communication data is related to the CPU means whether or not the CPU is included in the communication path of the communication data.

  The detailed data is data indicating details (for example, transmission cycle) of the communication data. The resource mapping data is data indicating which of the communication data described in the application design information table corresponds to the communication data. That is, it is data that associates an application name and a network name of the communication data.

  In this embodiment, the user completes the creation of the application design information table and the system design information table by manually inputting various information to the config tool 7 in steps 110 and 120.

  However, in step 130, the computer 50 automatically creates a part of the communication resource design information table. FIG. 9 shows the work procedure of step 130 in more detail. As shown in this figure, in step 130, the user first sets the summary data in the communication resource design information table manually (step 132), and then the resource mapping data is manually set by the user (step 134). Subsequently, the computer 50 automatically generates relevance determination data (step 136). Finally, the user manually inputs detailed data regarding the communication data whose own CPU related information is “related”. Set (step 138). In the manual input in steps 132, 134, and 138, the user refers to the data of communication specification 6. Then, the arithmetic circuit records the data input manually or the like in its own hard disk drive.

  Here, FIG. 10 shows a flowchart of processing executed by the arithmetic circuit of the computer 50 when the relevance determination data is generated in step 136. The arithmetic circuit starts this process by performing a predetermined operation instructing the user to generate relevance determination data on the operation device (not shown) of the computer 50 while the configuration tool 7 is being executed.

  In this process, first, in step 310, the arithmetic circuit initializes the values of all the CPU related information and GW information in the relevance determination data of each system design information table to “none”.

  Subsequently, steps 320 and 330 are performed for all communication data in the application design information table (in the example of FIG. 6, communication data referred to by application data name D1, application data name D2, application data name D3, etc.), respectively. 340 is executed once. That is, the loop of steps 320 to 340 is repeated by the number of application communication data.

  Hereinafter, communication data that is targeted at a certain time of the loop is referred to as target data. In a certain loop, in step 320, the arithmetic circuit refers to the application design information table to identify the transmission application that is the transmission source of the target data and the reception application that is the destination of the target data. For example, when the target data is data D1, the transmission application is application A02, and the reception applications are applications A01 and A03.

  Subsequently, in step 330, the route pattern of the target data is specified using the transmission application and reception application specified in step 320 and the system design information table. The route pattern is a pattern regarding how the target data reaches from the transmission application to the reception application in the communication system 60.

  FIG. 11 schematically shows six route patterns, and FIG. 12 shows a connection form between virtual CPUs for explaining the pattern of FIG. A type 1 route pattern is a pattern in which target data is delivered from a source CPU to a destination CPU by inter-CPU communication (indicated by a zigzag line arrow). In FIG. 12, the path of CPU-A → CPU line X → CPU-B corresponds to an example of this type 1.

  A type 2 route pattern is a pattern in which target data is delivered from a source CPU to a destination CPU by communication (indicated by a solid straight arrow) between ECUs. In FIG. 12, the path of CPU-A → node N 1 → node N 2 → node N 3 → node N 4 → CPU-B corresponds to an example of this type 2.

  In the type 3 route pattern, target data is delivered from a source CPU to a destination CPU via a CPU serving as a gateway. Inter-CPU communication is used from the source CPU to the gateway CPU, and from the gateway CPU to the destination CPU. Is a pattern in which communication via a communication bus between ECUs is used. In FIG. 12, the route of CPU-A → CPU line X → CPU-B → node N5 → node N6 → node N7 → node N8 → CPU-E corresponds to an example of this type 3.

  In the type 4 route pattern, the target data is delivered from the source CPU to the destination CPU through the CPU serving as a gateway, and communication via the communication bus between the ECUs is used from the source CPU to the gateway CPU. The gateway CPU to the destination CPU is a pattern in which inter-CPU communication is used. In FIG. 12, the route of CPU-D → node N9 → node N10 → node N11 → node N12 → CPU-A → CPU line X → CPU-B corresponds to an example of this type 4.

  In the type 5 route pattern, target data is delivered from a source CPU to a destination CPU via a CPU serving as a gateway, and communication via a communication bus between ECUs is used from the source CPU to the gateway CPU. From the gateway CPU to the destination CPU is a pattern in which communication via another communication bus between ECUs is used. In FIG. 12, the route of CPU-D → node N9 → node N10 → node N11 → node N12 → node N1 → node N2 → node N13 → node N14 → CPU-E corresponds to an example of this type 5. Note that the movement of data from the node N12 to the node N1 is realized by dedicated ECU hardware (ECU-HW in the figure) for performing communication control, not by processing by CPU-A software execution. Yes.

  In the type 6 route pattern, target data is delivered from the source CPU to the destination CPU via two gateway CPUs, and from the source CPU to the first gateway CPU via a communication bus between the ECUs. Communication between CPUs is used from the first gateway CPU to the second gateway CPU, and communication via another communication bus between ECUs is performed from the second gateway CPU to the destination CPU. The pattern used. In FIG. 12, CPU-D → node N9 → node N10 → node N11 → node N12 → CPU-A → inter-CPU line X → CPU-B → node N4 → node N3 → node N13 → node N14 → CPU-E. The route corresponds to an example of this type 6.

  Here, specific processing contents in step 330 of the arithmetic circuit will be described by taking communication data D1 in FIG. 6 as an example.

  First, for the target data D1, the arithmetic circuit specifies from the application design information table (see FIG. 6) in the hard disk drive that the source application is the application A02 and the destination applications are the applications A01 and 03.

  Subsequently, the arithmetic circuit specifies that the path from the application A02 to the application A01 is the path from the CPU-C02 to the CPU-C01 based on the system design information table (see FIG. 7) in the hard disk drive.

  Further, the arithmetic circuit specifies that the path from the application A02 to the application A03 is the path from the CPU-C02 to the CPU-C03 based on the system design information table.

  Further, the arithmetic circuit specifies that the CPU-C02 and the CPU-C01 are mounted on the same ECU-E01 based on the system design information table, so that the path from the CPU-C02 to the CPU-C01 is It is specified that the route is based on inter-CPU communication, and further, based on the result of this specification, the route from the application A02 to the application A01 is specified as corresponding to the type 1 route pattern.

  Subsequently, the arithmetic circuit specifies that CPU-C02 and CPU-C03 are not connected to the same communication bus, and based on the specification result, another CPU connected to the same communication bus as CPU-C03. Are identified from the system design information table, and CPUs that can communicate with the CPU-C02 are identified. In this case, the CPU that can communicate with the CPU-C02 is a CPU that is connected to both the two buses B1 and B2, and an ECU that can communicate with the CPU-C02 (i.e., in the same ECU as the CPU-C02). CPU).

  In this example, the CPU connected to the bus B1 and capable of directly communicating with the CPU-C02 is the CPU-C01. Therefore, the arithmetic circuit specifies the route of CPU-C02 → CPU communication → CPU-C01 → bus B1 → CPU-C03 as the route from CPU-C02 to CPU-C03, and further, in this specification result Based on this, since the route from the application A02 to the application A03 includes type 1, type 2, and type 3 route patterns, it is specified that the route corresponds to the type 1, type 2, and type 3 route patterns.

  Subsequently, in step 340, the arithmetic circuit selects a network name (S1 in this example) corresponding to the application name (D1 in this example) of the target data based on the resource mapping data of each system design information table in the hard disk drive. The relevance determination data in all records corresponding to the specified name is determined by the determination method assigned in advance to the type of route pattern specified in the immediately preceding step 340.

  Specifically, the determination method pre-assigned to the route pattern type is as follows. When the route pattern type identified in the immediately preceding step 340 is type 1 or type 2 and the CPU corresponding to the system design information table including the target record corresponds to the source or destination of the route, The CPU related data in the target record is rewritten to “present”.

  In addition, the CPU corresponding to the system design information table in which the type of the route pattern identified in the immediately preceding step 340 corresponds to at least one of types 3, 4, and 6 and includes the target record is If it is the gateway of the route, the GW information in the target record is rewritten to “present”.

  In addition, when the route pattern type identified in the immediately preceding step 340 corresponds to type 5 and the CPU corresponding to the system design information table including the target record is the gateway of the route (that is, When the target data is transmitted from one communication bus to another communication bus using the ECU hardware of the CPU), the GW information in the target record is rewritten to “present”.

  The arithmetic circuit repeats steps 320 to 340 as described above for each communication data, thereby determining relevance determination data in a plurality of communication resource design information tables. As described above, the computer 50 automatically calculates the relevance determination data necessary for creating the configuration code based on the contents of the application design information table, system design information table, overview data, and resource mapping data input by the user. Can be created.

  That is, for each communication data, the communication data path is specified from the transmission application-reception application relationship in the application design information table and the system configuration in the system design information table, and the path pattern is specified. The information associated with which CPU is involved in the distribution of communication data, that is, the relevance determination data can be automatically specified by the method associated with.

  Here, the generation of the configuration code in step 140 of FIG. 5 will be described. In step 140, the arithmetic circuit refers to the application design information table and the system design information table for the CPU in order to create a configuration code for the CPU, so that the CPU is involved in the transfer. The application name of the communication data application being identified is specified, a communication data function for referring to the application name is created and included in the configuration code, and the communication data for which the CPU is not involved Do not create communication data functions. Here, the specific contents of the communication data function are determined in advance.

  In step 140, the arithmetic circuit refers to the application design information table and the system design information table for the CPU in order to create a configuration code for the CPU. The detailed information of the communication data involved is specified, the detailed information is included in the configuration code, and the detailed information about the communication data not related to the CPU is not included in the configuration code.

  In this way, the configuration code for each CPU created in the configuration tool 7 reflects the contents of the relevance determination data in the communication resource design information table. Therefore, communication data that is neither transmitted nor received by the CPU nor a gateway (that is, communication data for which the CPU is not involved in communication) should not include detailed information on the data, and The configuration code is generated so as not to include a communication data function that handles data. As a result, the size of the generated execution image is reduced, and as a result, the ROM capacity of the ECU can be used more efficiently.

  In addition, since the configuration code for each CPU created in the configuration tool 7 in this way reflects the contents of the relevance determination data in the communication resource design information table, the CPU is associated with any data gateway. If this is not the case, the fact can be understood from the configuration code. In this case, the arithmetic circuit can exclude the part related to the realization of the gateway of the software PF from the link target at the time of linking. Therefore, the size of the generated execution image is reduced, and as a result, the ROM capacity of the ECU can be used more efficiently.

In the above embodiment, the arithmetic device functions as an example of the first recording unit by receiving the input of the application design information table in step 110 of FIG. 5, and receives the input of the system design information table in step 120. 9 functions as an example of a configuration code generation recording unit relevance recording unit by generating a configuration code in step 140, and executes step 136 in FIG. It functions as an example of a recording means, functions as an example of a first specifying means by executing step 320 in FIG. 10, functions as an example of a second specifying means by executing step 330, and executes step 340 This functions as an example of third specifying means.
(Other embodiments)
In the above-described embodiment, the arithmetic circuit is the application design information table, system design information table, communication resource design information table summary data, communication resource design information table resource mapping data, and communication resource design information table details. Data input is accepted and stored via an operating device, but by reading the data stored in a portable storage medium such as a USB memory, the input of the data can be accepted. It may be realized, or by receiving these data via a computer network, the input acceptance of the data may be realized.

It is a figure which shows the example of the state in which each of several ECU is connected to either or both of communication buses B1 and B2 in a vehicle. It is a figure which shows the hierarchical structure of the program group performed in each CPU. It is a figure which shows roughly the procedure which produces | generates the execution image of the program performed by each CPU. It is a figure which shows the method of the production | generation of a configuration code schematically. It is a flowchart which shows the outline | summary of the procedure of preparation of a configuration code. It is a chart which shows an example of an application design information table. It is a chart which shows an example of a system design information table. It is a chart which shows an example of a communication resource design information table. It is a flowchart which shows the detailed procedure of the setting of the communication resource in the procedure of preparation of a configuration code. It is a flowchart of the process which the computer 50 performs for preparation of relevance determination data. It is a figure which shows six route patterns typically. It is a figure which shows the connection form between virtual CPU for demonstrating the pattern of FIG. It is a flowchart which shows the detailed procedure of the setting of the conventional communication resource in the procedure of preparation of a configuration code.

Explanation of symbols

1 ... software PF, 2 ... configuration code, 3 ... application,
4 ... Application specification, 5 ... System specification, 6 ... Communication specification,
7 ... Config tool, 8 ... Configuration code, 50 ... Computer,
60 ... Communication system, B1, B2 ... Bus, E01-E03 ... ECU,
C01-C05 ... CPU, A01-A05, N01-N14 ... node.

Claims (2)

Software of one CPU (hereinafter referred to as a first CPU) for one of a plurality of CPUs mounted on any of a plurality of ECUs mounted on a vehicle and performing data communication with each other via a plurality of communication buses. process for generating object code to implement the operation of the first 1CPU by compiling and linking the platform and the first 1CPU application, used in, a configuration code for the first 1CPU, the first the configuration code using a software platform including a program for implementing the transmission or reception of the communication data, configuration code generator der for generating together including information of the communication data 1CPU relays Te,
A storage medium;
An arithmetic circuit,
The arithmetic circuit is:
Input of an application design information table indicating a correspondence relationship between a transmission application of a transmission source and a reception application of a destination for each of a plurality of types of communication data transmitted by a plurality of applications respectively executed by any of the plurality of CPUs First recording means for receiving and recording to the storage medium;
Which of the plurality of ECUs each of the plurality of CPUs is mounted on, which communication bus of each of the plurality of CPUs is connected to the plurality of communication buses, and the plurality of CPUs A second recording means for receiving and recording in the storage medium a system design information table indicating a correspondence relationship as to which of the plurality of applications is executed by each of the CPUs;
Relevance determination means for specifying communication data relayed by the first CPU based on information recorded by the first recording means and the second recording means, and relevance recording means for recording in the storage medium;
A configuration code generating / recording unit configured to generate the configuration code based on the information recorded by the first recording unit, the second recording unit, and the association recording unit and record the configuration code on the storage medium. And
The relevance recording means is a transmission application and destination of a transmission source for each of a plurality of types of communication data transmitted by a plurality of applications respectively executed by any of the plurality of CPUs based on the application design information table A first specifying means for specifying the receiving application;
By applying the identification result of the first identification unit to the system design information table, communication paths for a plurality of types of communication data transmitted by a plurality of applications respectively executed by any of the plurality of CPUs are determined in advance. A second specifying means for specifying which of the plurality of route patterns is applicable,
If the corresponding route pattern is a route pattern relayed by the CPU of the gateway based on the specification result of the second specifying means , depending on whether the first CPU is a gateway in the communication route, Configuration code comprising: third specifying means for specifying whether or not the first CPU relays the communication data and recording the specified result in the storage medium as the relevance determination data Generator. Software of one CPU (hereinafter referred to as a first CPU) for one of a plurality of CPUs mounted on any of a plurality of ECUs mounted on a vehicle and performing data communication with each other via a plurality of communication buses. A configuration code for the first CPU used in the step of generating an object code for realizing the operation of the first CPU by compiling and linking a platform and an application of the first CPU . use the configuration code generating device for generating a configuration code, including a program for utilizing the software platform to implement the transmission or reception of the communication data with including information of the communication data 1CPU relays A that program,
Input of an application design information table indicating a correspondence relationship between a transmission application of a transmission source and a reception application of a destination for each of a plurality of types of communication data transmitted by a plurality of applications respectively executed by any of a plurality of CPUs First recording means for receiving and recording on a storage medium;
Which of the plurality of ECUs each of the plurality of CPUs is mounted on, which communication bus of each of the plurality of CPUs is connected to the plurality of communication buses, and the plurality of CPUs A second recording means for receiving an input of a system design information table indicating a correspondence relationship between which of the plurality of applications is executed by each of the CPUs, and recording the received information on the storage medium;
Relevance determination means for specifying communication data relayed by the first CPU based on information recorded by the first recording means and the second recording means, and recording the relevance recording means on the storage medium; A computer as a configuration code generation and recording unit that generates the configuration code and records the configuration code on the storage medium based on the information recorded by the first recording unit, the second recording unit, and the association recording unit Make it work
The relevance recording means is a transmission application and destination of a transmission source for each of a plurality of types of communication data transmitted by a plurality of applications respectively executed by any of the plurality of CPUs based on the application design information table A first specifying means for specifying the receiving application;
By applying the identification result of the first identification unit to the system design information table, communication paths for a plurality of types of communication data transmitted by a plurality of applications respectively executed by any of the plurality of CPUs are determined in advance. A second specifying means for specifying which of the plurality of route patterns is applicable,
If the corresponding route pattern is a route pattern relayed by the CPU of the gateway based on the specification result of the second specifying means , depending on whether the first CPU is a gateway in the communication route, A program comprising: third specifying means for specifying whether or not the first CPU relays the communication data and recording the specified result as the relevance determination data in the storage medium.

Images