WO2006061884A1 - 自動車用制御装置とそのソフトウエア作成方法及びシステム - Google Patents
自動車用制御装置とそのソフトウエア作成方法及びシステム Download PDFInfo
- Publication number
- WO2006061884A1 WO2006061884A1 PCT/JP2004/018197 JP2004018197W WO2006061884A1 WO 2006061884 A1 WO2006061884 A1 WO 2006061884A1 JP 2004018197 W JP2004018197 W JP 2004018197W WO 2006061884 A1 WO2006061884 A1 WO 2006061884A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- software
- hierarchical structure
- creating
- control device
- process description
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Program-control systems
- G05B19/02—Program-control systems electric
- G05B19/04—Program control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/042—Program control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
- G05B19/0426—Programming the control sequence
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D41/00—Electrical control of supply of combustible mixture or its constituents
- F02D41/24—Electrical control of supply of combustible mixture or its constituents characterised by the use of digital means
- F02D41/26—Electrical control of supply of combustible mixture or its constituents characterised by the use of digital means using computer, e.g. microprocessor
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/25—Pc structure of the system
- G05B2219/25389—Macro's, subroutines
Definitions
- the present invention relates to an automotive control device and a microcomputer software creation method and creation system constituting the automotive control device.
- a microcomputer (hereinafter referred to as a microcomputer) incorporating a CPU, ROM, RAM, input / output signal processing device, and the like has been used as a control device for automobile engine control and the like.
- the software installed in the microcomputer consists of application programs that perform control processing and device drivers that perform input and output so that the desired control operations can be performed.
- Device drivers that perform I / O are problematic because of the large amount of change man-hours that are easily affected when the hardware used is changed.
- Hardware changes can be broadly divided into two types: change of the sensor actuator to be controlled, and change of the microcomputer to be controlled.
- change of the hardware to be controlled such as a sensor character
- the hardware to be controlled such as a sensor character
- develop software so that the target control operation can be realized.
- it was necessary to extract the changed part determine the changed specification, change work, and verify while referring to the manual describing the specifications of the microcomputer, which required a lot of man-hours. .
- Non-Patent Document 1 As disclosed in Non-Patent Document 1, U NIX (registered trademark), an information-related general-purpose operating system (OS), is used to reduce software modification man-hours associated with hardware changes. is there.
- the interface with the hardware to be controlled is standardized into three types: block type, message channel type, and character type, and all input / output programs are via one of the above three types of virtual interfaces.
- the software has a three-layer structure of application, virtual driver, and actual driver program, and the application program can be developed without being aware of the target hardware change.
- a program change associated with a device change is locally performed by making device drivers into three layers.
- Non-Patent Document 2 a device driver is divided into a higher driver and a lower driver, and the upper driver performs processing using the interface of the lower driver. Unaffected by changes! / As a configuration! /
- Non-Patent Document 1 S. J. Leffler et al. Akira Nakamura et al. “Design and Implementation of UNIX 4.3 BSD” Maruzen Co., Ltd. (1991)
- Patent Document 1 JP 2000-97102 A
- Non-Patent Document 2 ⁇ ITRON4.0 Specification Study Group “Device Driver Design Guidelines” ⁇ I
- Patent Document 2 JP 2002-287981 A
- a commonly used preprocessor that performs macro processing such as C language is character string replacement processing by sequential processing, so it is impossible to accelerate processing composed of a plurality of hierarchies. It is. For this reason, with these conventional techniques, it is not possible to suppress the processing overhead that occurs each time the hierarchy is passed. For example, in the case of a device driver configured in three layers, it becomes a program that performs call processing in three layers in order to perform one input / output process, resulting in a delay in program execution time and an increase in size. . In order to realize real-time control suitable for control of automobiles, etc., it is necessary to perform each processing such as calculation and input / output processing at the optimum timing, and a delay of several microseconds is often not allowed.
- Embedded systems such as automobile engine control devices have strict demands on response speed due to demands for reducing ROM and RAM capacity, which have a direct impact on costs, and real-time control. It becomes a big obstacle.
- An object of the present invention is to reduce the number of software changes when changing hardware and control methods, and to reduce the execution speed of an application and the required capacity of a storage device.
- a first process description part that describes the process of each hierarchy in a macro using a label that is defined for each hierarchy, and the connection relation between the hierarchies are labeled for each hierarchy.
- a hierarchical structure description part defined as a macro an identifier expansion part that performs macro expansion based on the hierarchical structure description part, and a second processing description part that is expanded to one hierarchy by using a preprocessor and a coniler. Format software can be obtained.
- the first process description section layered into a plurality of layers is created.
- means for creating is
- a pre-set processor that creates the second process description section and a compiler that converts the second process description section into an object format file.
- a linker for creating control software for linking the object format file with the application object format file and writing it to the storage device of the automobile control device.
- FIG. 1 is a configuration diagram of a device driver, an application, and hardware when developing a device driver according to an embodiment of the present invention.
- FIG. 2 is a configuration diagram of an automobile engine control system as an object of an embodiment of the present invention.
- FIG. 3 is a detailed diagram of a specific example in the upper layer (L1) of the process description part in FIG.
- FIG. 4 is a detailed diagram of a specific example in the lower layer (L2) of the process description part in FIG.
- FIG. 5 is a detailed view of a hierarchical structure description part in the device driver of FIG.
- FIG. 6 is a detailed view of an identifier expansion unit in the device driver of FIG.
- FIG. 7 is a development procedure diagram according to one embodiment of the present invention.
- FIG. 8 is a diagram showing an example of source code having no overhead between layers according to an embodiment of the present invention.
- FIG. 9 is a development environment and development procedure diagram of a device driver creation method according to an embodiment of the present invention.
- FIG. 10 is a diagram showing an example of an input / output terminal list according to an embodiment of the present invention.
- Hierarchical structure description part 192... Identifier Expanding unit 200 Control unit 220 Sensor sensor 71 Device driver program source code 72 Build 73 Device driver object file 902 Device driver Repository, 905 ... I / O terminal list, 906 ... Hierarchical configuration generator, 911 ... Preprocessor, 913 ... Expanded process description part, 914 ... Compiler, 916 ... Device driver object format file, 917 ... Application source code 918 ⁇ 9
- FIG. 1 is a configuration diagram of a device driver, an application, and nodeware when developing a device driver according to an embodiment of the present invention.
- a device driver 120 that performs an intake air amount calculation and an intake air temperature calculation based on input / output ports 131 to 133 of the microcomputer 130 based on inputs obtained with various sensor forces is shown.
- FIG. 2 is a configuration diagram of an automobile engine control system that is an object of an embodiment of the present invention.
- the control unit 200 includes a CPU 201, an interrupt controller 202, a timer pulse controller 203, an AD converter 204, a ROM 205, and a RAM 206. These are connected by a bus 207 and accessed from the input / output port 208 to the outside. Each of these elements 202 1 208 may be built in one element or connected using another element.
- Reference numeral 210 denotes a power supply unit of the control unit 200.
- the control unit 200 is connected to a sensor / actuator 220 as a control target via an input / output port 208.
- the sensor actuator 220 includes an air flow sensor 221, an electric throttle 222, an injector 223, a spark plug 224, an air-fuel ratio sensor 225 such as a LAF sensor, a crank angle sensor 226, etc., and the control unit 200 controls these controls. Do. That is, control is performed by reading / writing data from / to a register in the input / output port 208 from components such as the CPU 201. Describe how to control The software is written in the ROM 205 and RAM 206 in the control unit 200.
- This embodiment is a software program that can easily change the software and save the memory capacity that speeds up the execution of the application even when the hardware is changed. It relates to the creation method.
- the configuration of software executed by the control unit 200 in FIG. 2 will be described with reference back to FIG.
- Software is broadly divided into three categories: application program 100, operating system (OS) 110, and device driver 120.
- the application program 100 exchanges information and processing with the OS 110 and the device driver 120 through an application program interface (API) 140.
- API application program interface
- the OS 110 and the device driver 120 control these through the hardware interface (HWI) 150 such as the input / output ports 131 to 133 of the microcomputer 130.
- HWI hardware interface
- the device driver 120 executes the intake air amount calculation 121 and the intake temperature calculation 122 based on the input obtained from the sensor through the input / output ports 131 to 133 of the microcomputer 130 is shown.
- the device driver 120 receives a request through the API 140 from the injection control 101, the ignition control 102, or the like of the application program 100.
- the control target is the CPU 130, and the target control is performed by reading and writing the analog input / output ports 131-133 through the HWI150.
- the upper layer (L1) 160 is provided with modules for obtaining input values required by the application 100, such as the intake air amount calculation 121 and the intake air temperature calculation 122.
- the lower layer (L2) 170 is provided with a module that takes input values and performs general-purpose input processing, and describes the processing contents.
- the hierarchical structure description part 191 describes a specific structure between hierarchies, which upper layer uses which lower layer. Using the identifier expansion unit 192, the hierarchical structure defined in the hierarchical structure description unit 191 is associated with 180 processing description units, and a desired output is obtained.
- FIGS. 3 and 4 are detailed diagrams of specific examples in the upper layer (L1) 160 and the lower layer (L2) 170 of the process description unit 180 of FIG. 1, and these will be described.
- FIG. 3 is a detailed view of the intake air amount calculation (IAA) 121 of the upper layer (L1) 160 in FIG.
- FIG. 3A shows an outline of the process.
- the intake air amount calculation module has an intake air amount update process for process name 1 and an intake air amount acquisition process for process name 2, and the input necessary for this calculation. It shows that there is Vcc correction analog input as processing.
- FIG. 3B is a flowchart showing the outline of the intake air amount update process
- FIG. 3C is a flowchart showing the outline of the intake air amount acquisition process.
- Figure 3 (D) is an example of program code that implements Figure 3 (A), (B), and (C).
- step 301 the input value is updated by the Vcc correction analog input (VAI) in the lower layer L2, and then in step 302, the update is performed. Get the value.
- step 303 correction is performed using a map for correcting the characteristics of the airflow sensor based on the acquired value.
- step 304 the value obtained by the correction is held in a buffer.
- the processing for acquiring the intake air amount in FIG. 3C is realized by returning the value of the buffer in step 305.
- Fig. 3 (D) is an example of a program source in which these processes are described using C language macros.
- the call to another module is described as “Ln—Proc (—Ln (ID))”, and the data reference is described as “Ls— (ID)”.
- Ln is the layer name of the module to be called
- Proc is the process name to be called
- ID is its own module name
- Ls is the layer name of its own module.
- FIG. 4 is a detailed diagram of the Vcc correction analog input (VAI) 1 72 that is an element of the lower layer (L2) 170 in FIG.
- FIG. 4 (A) shows an overview of the processing.
- the Vcc correction analog input module has processing name 1 Vcc correction analog input value update processing and processing name 2 Vcc correction analog input value acquisition processing, and is necessary for this processing. This indicates that there is an input from a microcomputer port as a valid input type.
- Fig. 4 (B) is a flowchart of the Vcc correction analog input value update process
- Fig. 4 (C) is a flowchart of the Vcc correction analog input value acquisition process.
- Figure 4 (D) is an example of a source code that implements these Figure 4 (A), (B), and (C).
- Vcc correction analog input value update process in FIG. 4B, first, Vcc is input from the microcomputer port via the hardware interface (HWI) 150 to Step 401 ! Next, in step 402, the Vcc correction coefficient is multiplied to obtain an updated value. In Step 403, the acquired update value is stored in the buffer.
- HWI hardware interface
- Vcc corrected analog input value income in FIG. 4 (C) is realized by returning the value of the above buffer to step 404! /.
- Fig. 4 (D) is an example of a program source in which these processes are described using C language macros.
- the macro description is the same as in Fig. 3 (D).
- FIG. 5 is a detailed diagram of the hierarchical structure description part 191 in the device driver 120 of FIG.
- FIG. 5 (A) shows an outline of the configuration. It shows that the label names IAT, IAA, VAI, and FAI of each processing module and the label names of the processing modules that belong to these are FAI, VAI, AN1, and AN2. That is, the lower module of the intake air temperature calculation (I AT) 122 is the primary filter analog input 171, its label is FAI, and the lower module of the intake air amount calculation (IAA) 121 is the Vcc correction analog input 172. The label is VAI. Also, the primary filter analog input 171, that is, label F AI compatible hardware power analog I / O port and label is AN2, Vcc correction analog input 172, that is, label VAI compatible hardware power Analog input / output port and label Show that is AN1! /
- FIG. 5 (B) is a source code of the hierarchical structure description unit 191 implemented based on the hierarchical structure of FIG. 5 (A). This source code is described using a macro and is in the form of “# define ID—Ln IDn” or “# define ID ADDR xxxx”. Where ID is the device driver Module identifier (label), IDn is the identifier (label) of another module related to the module, -ADDR is the identifier (label) indicating the port of the microcomputer, and XXX is the port name.
- FIG. 6 is a detailed view of the identifier expansion unit 192 in the device driver 120 of FIG.
- the identifier expansion part is of the form “# define — Ln (ly) ly # # — Ln”, “# define — ADDR (ly) ly # # _ADDR”, “# define Ln_ (ly) Ln_ # # ly” .
- Ln is the name of the upper and lower layer
- ADDR is an arbitrary identifier indicating the port of the microcomputer, and the others are the same as described above.
- FIG. 7 is a development procedure diagram using the process description part, the hierarchical structure description part, and the identifier expansion part described above.
- the device driver object source file 73 is obtained through the build 72 through the hierarchical structure description part 711, the identifier development part 712, and the process description part 713 of the device driver program source code 71 created as described above. That is, when converted into machine language code using the preprocessor 721 and the container 722, the object file 73 of the device driver is output.
- this object file 73 since the processing description part constructed in a hierarchical manner is expanded to one layer by the preprocessor 721, the overhead between the layers is removed.
- FIG. 8 is a diagram illustrating an example of a source code from which overhead between layers is removed according to an embodiment of the present invention.
- the caller source code is shown in FIG. 8A, and the code after this is expanded by the preprocessor 721 is shown in FIG. 8B.
- the call processing between the layers of steps 301 and 302 in FIG. 3 (B) and step 401 in FIG. 4 (B) is expanded in one layer. This eliminates the need to save the arguments and stack pointers associated with the call processing of other layers, and realizes high-speed processing and a reduction in code size.
- FIG. 8C shows a machine language code according to a conventional method
- FIG. 8D shows an example of reduction by one embodiment of the present invention.
- the machine language code for calling in step 301 in FIG. 3 (B) is 81 surrounded by a broken line frame in FIG. 8 (C).
- FIG. 9 is a development environment and a development procedure diagram for realizing a device driver creation method according to an embodiment of the present invention.
- step 901 an identifier expansion unit 192 and a process description unit 180, which are already created device drivers 120, are registered.
- step 903 necessary identifier expansion unit 192 and process description unit 180 are acquired from device storage repository 902 that stores them.
- step 907 is performed using hierarchical configuration generation unit 906.
- the hierarchical structure description unit 908, the identifier expansion unit 909, and the process description unit 910 obtained in this way are macro expanded by the preprocessor 911 in step 912.
- the process description unit 913 in which the hierarchical structure is expanded based on the identifier expansion unit 909 and the hierarchy configuration description unit 908 can be obtained from the process description unit 910 described using the hierarchy.
- the expanded process description part 913 obtained here does not have a hierarchical structure, but has only one hierarchy, and processing overhead between the hierarchies is reduced.
- the device driver object format file 916 is obtained in the compiling step 915 using the compiler 914.
- the driver object format file 916 is linked in step 920 using the linker 919 together with the application object format file 918 obtained by compiling the application source code 917, and the control software 921 is obtained.
- FIG. 10 is a diagram showing an example of the input / output terminal list 905.
- the input / output terminal list 905 shows correspondence between hardware devices and control unit terminals.
- the hierarchical structure generation device 906 outputs FIG. 5 (B).
- the hierarchical structure description part 908 can be automatically generated from the input / output terminal list 905, which is the hardware design result, using a computer, and productivity can be improved.
- Hierarchical configuration generation device 906, device dry repository 902, and compiler 914 use a computer equipped with input means such as a keyboard, mouse, and network, display means such as a CRT, and storage means such as a hard disk. Can be realized.
- microcomputer software creation method and creation system is applied to an electronic control unit of an automobile engine control device that requires rapid processing and high reliability, and has a high force and frequent hardware change. Therefore, the burden on developers can be greatly reduced, and high availability is expected.
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Chemical & Material Sciences (AREA)
- Mechanical Engineering (AREA)
- Combustion & Propulsion (AREA)
- Automation & Control Theory (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP04822576.7A EP1835366A4 (en) | 2004-12-07 | 2004-12-07 | AUTOMOTIVE CONTROLLER AND SOFTWARE PRODUCTION METHOD AND SYSTEM THEREFOR |
| PCT/JP2004/018197 WO2006061884A1 (ja) | 2004-12-07 | 2004-12-07 | 自動車用制御装置とそのソフトウエア作成方法及びシステム |
| US11/792,366 US20080256522A1 (en) | 2004-12-07 | 2004-12-07 | Automobile Controller, Software Generation Method and Software Generation System Thereof |
| JP2006546575A JP4921175B2 (ja) | 2004-12-07 | 2004-12-07 | 自動車用制御装置のソフトウエア作成方法 |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/JP2004/018197 WO2006061884A1 (ja) | 2004-12-07 | 2004-12-07 | 自動車用制御装置とそのソフトウエア作成方法及びシステム |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2006061884A1 true WO2006061884A1 (ja) | 2006-06-15 |
Family
ID=36577714
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/JP2004/018197 Ceased WO2006061884A1 (ja) | 2004-12-07 | 2004-12-07 | 自動車用制御装置とそのソフトウエア作成方法及びシステム |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US20080256522A1 (ja) |
| EP (1) | EP1835366A4 (ja) |
| JP (1) | JP4921175B2 (ja) |
| WO (1) | WO2006061884A1 (ja) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2009080566A (ja) * | 2007-09-25 | 2009-04-16 | Hitachi Ltd | 車両制御用プログラムおよびプログラム生成方法、プログラム生成装置、及び自動車用制御装置 |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8468332B2 (en) * | 2009-06-13 | 2013-06-18 | Kinglite Holdings Inc. | Dynamic link loading in extensible firmware interface compliant systems |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH05150960A (ja) * | 1991-11-26 | 1993-06-18 | Fujitsu Ltd | プリコンパイラ |
| JPH07277105A (ja) * | 1994-04-15 | 1995-10-24 | Hitachi Ltd | 自動車用制御装置 |
| JPH09128246A (ja) * | 1995-10-30 | 1997-05-16 | Fujitsu Ltd | コンパイラ装置 |
| JP2003171774A (ja) * | 2001-09-28 | 2003-06-20 | Suzuki Motor Corp | アルミニウム基材及びその表面処理方法 |
| JP2004026083A (ja) * | 2002-06-27 | 2004-01-29 | Fujitsu Ten Ltd | 車輌制御プログラム開発システム、車輌制御装置、及び記憶媒体 |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPS63181034A (ja) * | 1987-01-23 | 1988-07-26 | Nissan Motor Co Ltd | 制御プログラムの開発支援装置 |
| JPH03282935A (ja) * | 1990-03-30 | 1991-12-13 | Pfu Ltd | コンパイル処理装置及びコンパイル処理方式 |
| US6122634A (en) * | 1996-11-12 | 2000-09-19 | International Business Machines Corporation | Fractal nested layout for hierarchical system |
| US6550052B1 (en) * | 1999-11-09 | 2003-04-15 | Daimlerchrysler Corporation | Software development framework for constructing embedded vehicle controller software |
| US7571445B2 (en) * | 2001-11-29 | 2009-08-04 | Dell Products L.P. | System and method for dynamic device driver support in an open source operating system |
| US7996825B2 (en) * | 2003-10-31 | 2011-08-09 | Hewlett-Packard Development Company, L.P. | Cross-file inlining by using summaries and global worklist |
-
2004
- 2004-12-07 US US11/792,366 patent/US20080256522A1/en not_active Abandoned
- 2004-12-07 EP EP04822576.7A patent/EP1835366A4/en not_active Withdrawn
- 2004-12-07 JP JP2006546575A patent/JP4921175B2/ja not_active Expired - Lifetime
- 2004-12-07 WO PCT/JP2004/018197 patent/WO2006061884A1/ja not_active Ceased
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH05150960A (ja) * | 1991-11-26 | 1993-06-18 | Fujitsu Ltd | プリコンパイラ |
| JPH07277105A (ja) * | 1994-04-15 | 1995-10-24 | Hitachi Ltd | 自動車用制御装置 |
| JPH09128246A (ja) * | 1995-10-30 | 1997-05-16 | Fujitsu Ltd | コンパイラ装置 |
| JP2003171774A (ja) * | 2001-09-28 | 2003-06-20 | Suzuki Motor Corp | アルミニウム基材及びその表面処理方法 |
| JP2004026083A (ja) * | 2002-06-27 | 2004-01-29 | Fujitsu Ten Ltd | 車輌制御プログラム開発システム、車輌制御装置、及び記憶媒体 |
Non-Patent Citations (1)
| Title |
|---|
| See also references of EP1835366A4 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2009080566A (ja) * | 2007-09-25 | 2009-04-16 | Hitachi Ltd | 車両制御用プログラムおよびプログラム生成方法、プログラム生成装置、及び自動車用制御装置 |
Also Published As
| Publication number | Publication date |
|---|---|
| JPWO2006061884A1 (ja) | 2008-06-05 |
| EP1835366A1 (en) | 2007-09-19 |
| US20080256522A1 (en) | 2008-10-16 |
| JP4921175B2 (ja) | 2012-04-25 |
| EP1835366A4 (en) | 2014-08-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5179249B2 (ja) | 制御装置シミュレーション方法、システム及びプログラム | |
| JP5153465B2 (ja) | シミュレーション方法、システム及びプログラム | |
| US20140236384A1 (en) | Vehicle Control Software and Vehicle Control Apparatus | |
| JP2986042B2 (ja) | オブジェクト指向プログラミング環境を変更するための方法及び装置 | |
| JP5224957B2 (ja) | シミュレーション方法、システム及びプログラム | |
| CN115167831A (zh) | 基于autosar的软件集成方法、设备和使用方法 | |
| US8170860B2 (en) | Method and device for emulating control and/or regulating functions of a control or regulating device | |
| US7676774B2 (en) | System LSI verification system and system LSI verification method | |
| US20030110468A1 (en) | Program code generator and program | |
| CN114911582A (zh) | 用于控制自动化或自主车辆中多种驾驶功能的方法、控制单元、计算机程序及存储器介质 | |
| JP5186290B2 (ja) | シミュレーション方法、システム及びプログラム | |
| WO2006061884A1 (ja) | 自動車用制御装置とそのソフトウエア作成方法及びシステム | |
| JP2011238297A (ja) | 自動車用制御装置のソフトウエア作成方法 | |
| Köster et al. | Connecting Simulink to OSEK: Automatic code generation for real-time operating systems with Targetlink | |
| Klaus et al. | Automatic generation of scheduled SystemC models of embedded systems from extended task graphs | |
| JP5186307B2 (ja) | シミュレーション方法、システム及びプログラム | |
| Habibi et al. | On the transformation of SystemC to AsmL using abstract interpretation | |
| US20060198501A1 (en) | Method and device for constructing a voice dialog | |
| Conrad et al. | Towards a methodology for the design of hybrid systems in automotive electronics | |
| JPH09179738A (ja) | オブジェクト指向言語処理方法及び処理装置 | |
| US20030154322A1 (en) | Electronic system for developing software and a method for accessing the internal data of said software | |
| JP4919782B2 (ja) | 組込みコントローラ及び組込みコントローラ開発ツール | |
| Freund et al. | The EAST-ADL: A joint effort of the European automotive industry to structure distributed automotive embedded control software | |
| Tsuzuki et al. | [Industrial Paper] Performance Measurement and Finding Challenges in Using FMUs to Perform Scenario-Based Testing in a Cloud Environment | |
| US8769489B2 (en) | Method for encapsulating components hierarchically composed functions |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
| AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
| WWE | Wipo information: entry into national phase |
Ref document number: 2006546575 Country of ref document: JP |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2004822576 Country of ref document: EP |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| WWP | Wipo information: published in national office |
Ref document number: 2004822576 Country of ref document: EP |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 11792366 Country of ref document: US |