ASAM-MCD-2MC Generation for Protected Components

IP‑protected components must be generated and compiled with virtual address table (see the ASCET‑SE User Guide for details). You must activate the Generate Map File option in the Production Code node of the Project Properties window, and the addressTable option in the codegen_ecco.ini file.

You also need to define the COMPILE_VAT macro in the project_settings.mk file. The macro is added to the PROJECT_DEFINES section, e.g.,

PROJECT_DEFINES = $(MEM_LAYOUT) $(COMPILE_UNUSED_DEF) __DCC__ __GENERATE_ISR_DUMMY COMPILE_VAT

Note

It is recommended to use these settings in all ASCET installations involved in the component exchange.

Then you can generate code with the unprotected components, protect the components and transfer them to the development partner. The partner can build the project as described before. See also IP Protection Procedure and Building/Rebuilding Executable Code.

To generate a complete *.a2l file, the partner has to read the information from the precompiled objects. This is done in the project editor, via the Tools menu, ASAM-2MC submenu, Read Hex File option. Afterwards, the *.a2l file can be written as described in Generating Application Files; it should contain the complete addresses.

See also

IP Protection

Preconditions for IP Protection

IP Protection Procedure

Project Editor – Production Code Node

Project Editor – Building/Rebuilding Executable Code

Project Editor – Generating Application Files