Integrate Generated Code for Multi-Instance Software Components

For models containing multi-instance software components, you can configure the default packaging of internal data in the generated code as C-typed per-instance memory (PIM) or AUTOSAR-typed PIM.

If you build an AUTOSAR software component model that is configured for multiple instantiation that uses C-typed PIM:

• The generated ARXML describes internal data such as BlockIO and DWork as C-typed PIM.

• The generated model header file model.h contains type definitions for the PIMs.

If you use C-typed PIM, when you integrate the generated ARXML files and code into the AUTOSAR run-time environment (RTE), the RTE generator does not automatically generate the PIM type definitions. To make the type definitions available for component instances, the RTE must include the generated model header file.

The method for including the model header file varies according to the integration tooling. For example:

• In Vector tooling, file Rte.h includes an optional user types file, Rte_UserTypes.h. Update Rte_UserTypes.h to include model.h.

• In ETAS^® tooling, Rte_UserCfg.h is an optional user configuration file. Update Rte_UserCfg.h to include model.h.

If you use AUTOSAR-typed PIM, when you integrate the generated ARXML files and code into the AUTOSAR RTE, the RTE generator automatically generates the PIM type definitions. No additional model header files need to be included.

Related Topics

• Map Calibration Data for Submodels Referenced from AUTOSAR Component Models
• Configure Subcomponent Data for AUTOSAR Calibration and Measurement
• Configure AUTOSAR Shared or Per-Instance Parameters
• Configure AUTOSAR Per-Instance Memory
• Multi-Instance Components