DE10235610A1 - Function checking method for testing a function implemented in software e.g. for motor vehicle, involves integrating a function into a control device program as a bypass program to execute it through an invocation - Google Patents

Abstract

A control device program (CDP) is stored, in which a function is integrated as a bypass program (BP) into the CDP and executed through an invocation. The BP is integrated into the CDP by a copying routine. Activated by a software switch via an applications system, a BP service routine invokes the BP via an address contained in a bypass pointer table. Independent claims are also included for the following: (a) A memory device for a control device with a memory segment for a bypass program; (b) and for a control device with an arithmetic unit and a memory device; (c) and for a computer program with program code device; (d) and for a computer program product with program code devices.

Description

The invention relates to a method to check one Function implemented in software for a control unit and a control unit to carry out of the method as well as a computer program and a computer program product.

State of the art

For controlling different functional areas Control units are used in motor vehicles today. In the area of the motor management systems (Motronic), for example, by hardware and assigned control unit software the different operating modes of an engine, for example an Otto engine, regulated or controlled. The control unit and control unit software unit takes over the control of units in many areas of the vehicle dependent on of input quantities.

Each of these tasks by the ECU software must be processed is in a control unit function described. A large number of control unit functions form here and the operating system the so-called program status for the engine control system. additionally control unit data are provided, those in the form of constants, applicable fixed values, characteristic curves and / or maps in the control unit concerned are and form the data status. The program status and the associated data form the software version for the engine control system.

In the software version is by specification the control unit functions and the data the behavior of the control unit in different operating modes of the motor defined or specified. It is possible to use a suitable application control unit and the associated application system by changing data in restricted Form to set the functioning of control unit functions.

Usually when a new one ECU functionality achieved a control unit bypass is to be used at this point, which enables a check, without a new program status must be generated.

For example, the so-called external control unit bypass used, which is used in function development.

The development environment continues from an application control unit with an emulation probe, one Application system, external hardware and a PC with software for code generation together. The bypass function is modeled with the PC software and subsequently implemented in code. The bypass code generated in the process is changed to a external hardware loaded and executed there, using a software switch concept can be activated or deactivated.

In this way a new functionality is brought about while at the same time the existing function code is bypassed. The calculated here Bypass values are over a Interface using a transmission protocol in the ECU software written back.

With the procedure with external control unit bypass the bypass values are calculated outside the control unit system, where the calculation is typically carried out in float arithmetic. It can too only individual control unit sizes with the bypass are processed. In addition, the timing, i.e. reading and writing back of control unit sizes, fixed to a transmission protocol bound. It should also be noted that there is a free cut in the control unit function and also parallel management of documentation and software development the control unit functions with and without bypass clearance are required.

A disadvantage of the process with external bypass is that it in the simulation of complex control loops for calculation grid losses that can distort the result of the bypass instrumentation and can even make it unusable. Moreover is in the control unit a different arithmetic (integer) than in the external hardware (float) used. Further disadvantages are the limited computing time, the increased Time spent on the preparation of a bypass cut and the high administrative effort of control unit functions with and without bypass clearance. Another disadvantage is that only individual control unit sizes with the bypass can be processed.

Advantages of invention

In contrast, the method according to the invention provides to check one Function implemented in software for a control unit before that the new Function as a bypass program in the control unit range integrated and executed by a call.

With the method according to the invention can the disadvantages mentioned above are eliminated and the costs and development time in software development can be reduced.

The inventive method with an internal control unit bypass is a method in which a newly created software function is integrated into an existing control unit program and can be executed via a mechanism without changing the existing software structure. It is therefore possible to test the bypass functions in the target system already during the development phase and to check their software suitability in terms of runtime, physical behavior, etc. Of course, it is possible to integrate several bypass programs, each of which can be called up separately or in combination with other bypass programs.

In an embodiment of the invention the bypass program by copying it into the control unit program integrated.

In this process, the content of memory segments from the bypass software into the control units or Project Software inserted.

A bypass service routine is preferred provided that about an address contained in a bypass pointer table the bypass program calls.

The content of the pointer or pointer table is determined by the bypass development environment. In the The table shows the assignment of the addresses of control unit functions or control unit sizes for the bypass functions to be called Are defined.

The bypass service routine is expediently through a software switch activated an application system.

One possibility is that with a so-called function bypass manipulates a function of the control device becomes. With a single size bypass can manipulate an ECU size become.

Usually takes place via References a data transfer between the control unit program and the bypass program.

The method according to the invention enables one Rapid prototyping in the target system, since the function developer is responsible for his ECU functions Develop directly in the target system and have no effect on software development can test. The bypass code is running in real time in the control unit.

The problem of grid loss occurs during internal control unit bypass not due to the bypass instrumentation fixed to the timing or the scheduling of the control unit function oriented. In contrast to the external control unit bypass, control unit functions can with the function bypass and individual control unit sizes with the single size bypass getting tested. Eliminating the need for expensive external hardware a reduction in costs. Furthermore, the method according to the invention enables a reduction in the administrative burden of ECU functions with and without bypass clearance.

The development environment in the method according to the invention consists of an application control unit with, for example, one Emulation unit, an application system and a PC with software for Code generation together.

The storage device according to the invention for a control device in which a control unit program filed, includes a number of memory segments. At least one of the Memory segments for a bypass program intended.

This preferably points to the bypass program provided memory segment a first area for bypass data, a second area for a bypass code and a third area for a bypass pointer table on.

The control device according to the invention has a computing unit and a storage device in which the ECU program is filed. The memory device comprises a number of memory segments, at least one for a bypass program is provided.

The computer program according to the invention comprises program code means to run of the steps of the method described above and is based on a computer or a corresponding computing unit.

The computer program product according to the invention is stored on a computer-readable data medium. As suitable disk come EEPROMS and flash memories, but also CD-ROMs, floppy disks and hard drives for use.

Further advantages and configurations the invention will become apparent from the description and the accompanying Drawing.

It is understood that the above not only mentioned and the features to be explained below in the specified combination, but also in others Combinations or alone can be used without the frame to leave the present invention.

drawing

The invention is based on exemplary embodiments shown in the drawing and will be referred to below on the drawing in detail described.

1 shows a preferred embodiment of the control device according to the invention in a schematic Presentation.

2 shows a software development process for an internal control unit bypass.

3 shows the structure of a preferred embodiment of the memory device according to the invention.

4 shows in a schematic diagram a merging of bypass and control unit software.

5 shows a structure of a bypass pointer table.

6 shows a sequence of a search function in the bypass service routine.

7 shows a preferred embodiment of the method according to the invention.

8th shows a further preferred embodiment of the method according to the invention.

9 shows a bypass free cut for the functional bypass.

10 shows a bypass free cut for the single size bypass.

In 1 is a preferred embodiment of the control device according to the invention, overall with the reference number 10 designated, shown.

The control unit 10 has an electronic computing unit 12 , namely a CPU 12 , and a storage device 14 on that over a data line 16 are interconnected. The storage device 14 comprises a number of memory segments 18 , In the storage device 14 a control program is stored, at least one of the memory segments 18 for storing a bypass program and thus for integrating it into the project software.

In 2 the development of the bypass software is illustrated parallel to the development of the project software.

In a first field 20 is the development process for the project software and in a second field 22 reproduced the creation of the bypass software.

From the development process of the project software there are 24 interface files in one step, in one Step 26 a linker file, in a step 28 project application data and in a step 30 the project software.

When creating the bypass software in a step 32 a simulation model of the bypass function created and encoded in a step 34 with a code generator. The interface files determined in step 24 are in a step 36 as Pass references to project sizes.

Below is one step 38 the bypass source code is created and compiled in a step 40. The linker file created in step 26 becomes in a step 42 transferred as a bypass linker file. The data is then generated using a linker in a step 44 connected. In a step 46, the bypass software and The bypass application data is obtained in a step 48.

At the end of the development process receives the user in a step 50 the project software and in one Step 52 the project application file including bypass application data.

The development of the bypass software is therefore independent from the development of the project software. From the development process of the project software interface files are transferred to the bypass development process, the for access to project software data is required.

In 3 is the structure of a storage device according to the invention 60 clarified. A first area 62 is a bypass RAM area for the global bypass sizes, a second area 64 as a bypass code area for the bypass program code, a third area 66 for pointer tables for the function bypass, a fourth area 68 for pointer tables for single size bypass and a fifth area 70 provided as a data area for the bypass application data.

For the procedure of the internal control unit bypass becomes memory areas for the Bypass instrumentation required in the ECU software. This are filled with data through the bypass development environment. there the memory segments prevent an address shift due to postprocessing. For this reason, the existing control unit software largely remains in its Original state.

So there is in the project software for global Bypass RAM sizes Bypass RAM area. For control unit data, such as fixed values, characteristic curves or maps that are in the bypass function defined as application data is the bypass data area intended. The actual bypass program code is in the memory segment Bypass code.

The areas still continue for the Bypass pointer tables needed.

In 4 the merging of bypass and control unit or project software is shown in principle. A RAM area is shown 80 in which the project software is stored. arrow 82 illustrates that the RAM cells specified in the bypass function in the project software occupy the bypass RAM area.

Another area 84 represents the bypass code area 84 The bypass code is in the bypass code area 84 copied. An area 86 serves to include the pointer table for the function bypass and yet another area 88 the inclusion of the pointer table for the single size bypass. Finally are in one area 90 the bypass data. In this area 90 it contains the application data defined in the bypass function.

The bypass software is created using the bypass development environment. The structure and structure of the memory segments correspond to those of the project software. One with arrows 92 marked copying process (delta flashing), the contents of the memory segments from the bypass software are inserted into the project software and thus integrated into this.

In 5 is a possible structure of a bypass pointer table 100 shown. In a first column 102 a table index is included. In a second column 104 are the addresses of the control unit functions or control unit sizes. In the case of the single size bypass, the data type of the control unit size to be manipulated determines the data structure of the table. In a third column 106 the function pointer addresses of the bypass functions to be called are contained.

The bypass pointer table 100 is used by the bypass service routine. The content of table 100 is determined by the bypass development environment. The assignment of the addresses of control unit functions or control unit sizes is defined in table 100.

It should be noted that there are basically two types of pointer tables 100 there, namely one for the function bypass and another for the single size bypass. The charts 100 each have a fixed length and data structure.

The following is an example of the implementation of a bypass pointer table for the function bypass:

In 6 a sequence of a search function is shown in the bypass service routine. The search routine is started in one step. A parameter i is then set to zero in a step 112. A check is then made in step 114 as to whether a table value is equal to the value of the parameter. If this is the case, the corresponding bypass function code is called in a step 116.

If it is determined in step 114 that the Table value is not equal to the value of the parameter, is in one Step 118 checks whether the Table value is zero. If this is not the case, the Parameter i increased by 1 in a step 120. Then will in a step 122 checks whether i is equal to n. If this is not the case, there is a jump to step 114th

If i is equal to n or if in step 118 it is found that the Table value is zero, an error message appears in step 124, since no bypass function is specified. End with step 126 the search routine.

The bypass service routine that the Interface between control unit function and bypass function is part of the operating system. As a transfer parameter In the function bypass, this becomes the address of the control unit function called and single size bypass transfer the address of the control unit size to be manipulated.

The bypass service routine includes one Search algorithm, which in the corresponding pointer table after the Value of the transfer parameter examined. If this is found, the operational bypass function is called via the Function pointer. There are service routines for the function bypass and for the single size bypass. These differ in the processing of the pointer tables, in the data structure and in the handling of the return values.

The following is an example of a bypass service routine for the function bypass:

The following is an example of a bypass service routine for single size bypass:

When transferring data from project to Bypass software should be noted that the bypass function data information from the project software. Access to project sizes can only over References to these sizes are made. So it can only be about address information and not about symbolic names of the RAM cells, on parameters or library functions be accessed because the merging of project software and Bypass software does not have the zinc process takes place.

In 7 A preferred embodiment of the method according to the invention for explaining the functional bypass is shown. The illustration illustrates the functionality of the call of a bypass function from a control unit function for the function bypass.

A first area 130 shows the processes in the control unit function, a second area 132 the processes in the bypass service routine and a third area 134 those in the bypass function for the function bypass.

With a step 136 the Begin. Subsequently it is checked in a step 138 whether the Switch for bypass activation is set. If so, it is done in a step 140 the start of the bypass service routine. Otherwise, the control unit code is executed in a step 142 and the process ends in a step 144.

After starting the bypass service routine Step 140 checks in a further step 146 whether the Address of the control unit function exists in the pointer table. If so, it is done in a step 148 the start for the function bypass and in a step 150 it becomes the bypass function code executed. The execution of the bypass function code ends in a step 152. Subsequently The execution of the bypass service routine likewise ends in a step 154.

It is determined in step 146 that the address of the ECU function is in the pointer table If the bypass service routine is ended, step 154 ends.

After the bypass service routine has ended in step 154 it is checked in a step 156 whether the bypass execution is plausible is. If this is the case, a jump is made to step 144. Otherwise there is a jump to step 142.

In the figure is a first field 158 a bypass free cut for the functional bypass and with a second field 160 the search algorithm is labeled.

As the illustration shows, is in the control unit function the bypass free cut. The bypass service routine is controlled by a software switch Application system activated. This becomes the address as a parameter transfer the called control unit function. Then a search algorithm is used in the bypass pointer table the handed over Parameter value searched. For the case that none comparable address can be found or that the table is empty, no bypass function is called. Is located a suitable address in the table is given via the assigned function pointer the bypass function is activated. Then comes in the bypass function the new control unit functionality. After successful completion of this action, the service routine delivers an "OK" to the control unit function back and the actual control unit code is bypassed. In the event of an error, however, this is carried out.

8th illustrates the principle of single size bypass. A first area 170 shows the processes in the control unit function, a second area 172 the processes in the bypass service routine for the single size bypass and a third, area those in the bypass function for the single size bypass.

The process begins at step 176. Subsequently it is checked in a step 178 whether the Switch for the bypass activation is set. If so, start in a step 180 the bypass service routine. This is not the case the control unit size remains unchanged (step 182). Then in a step 184 the control unit function code accomplished and in step 186 the action ends.

After starting the bypass service routine in step 180 it is checked in step 188 whether the address of the control unit size in the Pointer table exists. If the size is in the table, execution begins in step 190 the bypass function for the single size bypass. The bypass function code is then executed in step 192. In step 194, the return value transfer the calculated bypass value and in step 196 the execution of the bypass function ends. The return value is equal to the return value the bypass function (Step 198). The execution of the then ends in step 200 Bypass service routine.

If it is determined in step 188 that the Control unit size address not exists in the pointer table, the parameter value is transferred as the return value (step 202) and then execution with step 200 the bypass service routine ends.

After the bypass service routine has ended in step 200, in step 204, the control unit size becomes the return value the bypass service routine is set and proceeded to step 184.

In addition, are shown with a field 206 the bypass free cut for single size bypass and with one field 208 the search algorithm is labeled.

As the figure shows, it works the single size bypass basically similar like the functional bypass. One is in a control unit function Bypass breakpoint. The bypass service routine is controlled by a software switch Application system activated. This becomes the address as a parameter the control unit size to be manipulated. Then by a search algorithm in the bypass pointer table after the given Parameter value searched. If no comparable address is found or if the table is empty, no bypass function is called. If there is a suitable address in the table, use the assigned function pointer activated the bypass function. In the new control unit functionality is then used for the bypass function.

After successful completion of this Action, the bypass function delivers a return value to the service routine. The return value is to the control unit function passed. The corresponding RAM cell is then used with this described. In the event of an error, the return value is the service routine the passed parameter value, which is why the value of the control unit size does not change.

The bypass function for the functional bypass is like a conventional one Control unit function built up. Project sizes are typically accessed via references on the control unit sizes to be read or manipulated. Furthermore the bypass function is designed, library functions such as control technology transmission elements and interpolation routines, or application data from the project software to use. Project sizes can only made accessible to the bypass by their addresses, but not by the label become.

A bypass function for the function bypass is shown below as an example:

The bypass function for single size bypass is similar built up. The only difference is that the function is a typed one return value Has. Furthermore, the return value written back to the corresponding control unit size.

The following is an example Bypass function for the single size bypass listed:

9 shows a basic view of a bypass cutout for the functional bypass.

The process begins in step 210. In step 212 it is checked whether bit 1 and bit 3 of the code word are set. If this is the case, the bypass service routine is executed in step 214. It is then checked in a step 216 whether the return value of the service routine is less than 2. If this is the case, the action ends in a step 218.

It is determined in step 212 that bit 1 and bit 3 are not set, or if it is determined in step 216 that the return value of the service routine is not less than 2, the control unit function code is executed in step 220.

With the bypass free cut for the functional bypass is in a control unit function a bypass free cut. This free cut is a switch framework made up of parameters that are available via the Application system changed can be. This will make the code sequence for activated the bypass. The service routine supplies the status as a value the bypass version, the is checked for plausibility in free cutting.

The following is an example of a control unit function with bypass clearance for the functional bypass: void zwstt l0ms (void)

In 10 a bypass free cut for the single size bypass is shown. The action begins with a step 230. In a step 232 it is checked whether bit 0 of the code word is set. If this is the case, the bypass service routine is executed in a step 234. At step 236, the controller size is set equal to the return value of the bypass service routine. The execution of the control unit function code is then continued in one step until the end of the process in a step 240.

If it is determined in step 232 that bit 0 is not set, the control unit size remains unchanged (step 242) and a jump is made to step 238.

The structure of the free cut at Single size bypass is similar the one with the function bypass. The only difference is that the service routine the value from the bypass function to the corresponding control unit size in the Control unit function writes.

An example of a control unit function with bypass free cut for single size bypass is listed below:

Claims (12)

Method for checking a function implemented in software for a control unit ( 10 ), in which a control unit program is stored, in which the function is integrated as a bypass program in the control unit program and executed by a call. The method of claim 1, wherein the bypass program by a copy process is integrated into the control unit program. Method according to Claim 1 or 2, in which a bypass service routine is provided which is carried out via a bypass pointer table ( 100 ) contained address calls the bypass program. The method of claim 3, wherein the bypass service routine is performed by a software switch an application system is activated. Method according to one of claims 1 to 4, in which a control device function is manipulated. Method according to one of Claims 1 to 4, in which a control unit size is manipulated becomes. Method according to one of claims 1 to 6, in which via references a data transfer between the control unit program and the bypass program becomes. Storage device for a control unit ( 10 ) with a number of memory segments ( 18 ), in which a control unit program is stored, at least one of the memory segments ( 18 ) is intended for a bypass program. Storage device according to Claim 8, in which the at least one storage segment (for the bypass program) 18 ) a first area for bypass data, a second area for a bypass code and a third area for a bypass pointer table ( 100 ) having. Control unit with a computing unit ( 12 ) and a storage device ( 14 ), which is a number of memory segments ( 18 ) and in which a control unit program is stored, at least one of the memory segments being provided for a bypass program. Computer program with program code means to carry out all steps of a method according to one of claims 1 to 7, if the computer program on a computer or a corresponding computing unit ( 12 ), especially an electronic computing unit ( 12 ) in a control unit ( 10 ) according to claim 10. Computer program product with program code means which are stored on a computer-readable data carrier in order to carry out a method according to one of claims 1 to 7, if the computer program on a computer or a corresponding computing unit ( 12 ), especially an electronic computing unit ( 12 ) in a control unit ( 10 ) according to claim 10.