Generating A2L Files

Manual generation

You can generate A2L files from CANape at any time with the information from the Linker Map file. To define communication-specific data in the A2L, you just need to create a suitable new driver in CANape (XCP-on-FlexRay, CCP-on-CAN, etc.) and save the settings.

The measurement and calibration parameters from the ECU can be selected from the Linker Map file using object names. You can use the editor to conveniently input and manage all other settings, such as entry of minimum and maximum values, groupings, definition of conversion rules and storage schemes.

Automatic generation by C Code Parser

Special comments in C code are parsed with the A2L Creator, which is supplied as a component of the ASAP2 Tool-Set. Software developers do not need to define the objects a second time in a parallel database, rather they define them in the form of comments in the C code. This minimizes the risk of inconsistencies between the code and a separate database.

The software developer makes a change to the code directly at the relevant point. That is also precisely where the comments are located; so the developer can make all changes at one point, without having to update the changes in another tool.

The parser searches the C code for the comments and generates a partial A2L from them, which represents the measurement and calibration parameters.

Automatic ASAP2 generation process with ASAP2 Creator, Updater and Merger. Comparison of ASAP2 files and specific modification results using the ASAP2 Comparer and Modifier. The ASAP2 Checker checks ASAP2 files for syntactic and semantic errors.

The communication section of the A2L, or other partial A2L files containing the complex conversion rules, can be merged into a complete A2L in another step and be updated with current address information from the Linker Map file.

Did you find this page helpful?

Please comment: