The seven programs of ASAP2 Tool-Set
A prerequisite for use of the ASAP2 Creator is that comments must be inserted in the C-code. ASAP2-specific information such as data type, conversion rules, min-max conditions, structures, arrays, etc. is defined in these comments.
The ASAP2 Updater reads in an ASAP2 source file, updates all address and data type information based on the entries in a linker map file and generates a new ASAP2 file from this information.
The ASAP2 Merger merges several ASAP2 files to a common ASAP2 file. One of the source files must be determined as master, the other source files are slaves. From the master, all information is used for the result ASAP2 file, from the slaves only the measurement and calibration objects, conversion rules, functions, groups, and record layouts are taken into account.
The ASAP2 Comparer lets you compare two ASAP2 files quickly and conveniently. An initialization file is used to define which objects should be compared. The results are documented in a file. Different file formats may be used for this results file: text, CSV or XML.
Not every A2L file conforms to criteria of the standard. To assure high process reliability over the entire toolchain, an A2L file is checked against the standard, and deviations are pointed out. Along with syntax checking, more extensive semantic plausibility checks can also be performed.
This tool lets users modify ASAP2 files in specific ways. Some of the supported modifications are:
- Complex filtering of ASAP2 files by any desired search criteria (name, comment, address, object attribute, etc.). The search results can be taken from the ASAP2 file or be extracted to a separate file.
- Configurable optimization of the ASAP2 file (reducing file size by removing redundant information)
- Correction functions (removing invalid key words and references from the ASAP2 file, invalid characters in object names can be replaced)
The convenient ASAP2 Studio is used to create, modify and update ECU description files in ASAP2 format. The editor is optimally integrated in the development process. For example, when the ASAP2 Studio is used to create database objects, address and data type information can be taken from the linker map file or debug file. ASAP2 Studio is the “standalone” version of the database editor integrated in CANape. The graphical user interface is sorted by areas of application and permits fast, easy use with the intuitive ribbon.