InitFunction documentation. InitFunction documentation. Specifies the modules DefRef path. E.g.: /AUTOSAR/EcucDefs/Msn ConfigPtr documentation. Specify the name of the Function. If InitFunctionCall is not set, this name is used as C function to call during initialization. Specify additional code which can be referenced from the initialization callouts of EcuM and BswM. E.g.: Mcu_InitClock() If it is necessary to call a function with a module pointer from the global postbuild-loadable configuration, the placeholder %CONFIGPTR% can be used: E.g.: Mcu_Init(%CONFIGPTR%) Specify the header file which declares the function and necessary types. Specify the phase in which this init function shall be called. Specify InitFunctionData for each relevant Configuration Variant. If no InitFunctionData is specified, the InitFunction will never have a config pointer. If a config pointer is necessary in some variants, each variant can be assigned to a config pointer via the InitFunctionData. Also a combination of several ConfigVariants is possible. ConfigPtr documentation. Mark if this InitFunctionData is valid for variant configurations. If this parameter is not available, this InitFunctionData will be valid for variant and invariant usecases. Specify the ConfigVariants in which this InitFunctionData is relevant. If no ConfigVariant is specified, this InitFunctionData is relevant for each ConfigVariant. If the InitFunction needs a Config Pointer in the current variant, this has to be specified here. ConfigPtr documentation. Multiple ConfigPtrNames are only possible in the case of variance. To support dynamic Conifg Pointer Names, wildcards can be used. Possible wildcards are: -%VARNAME% -%VARNAME_PRE_UNDERSCORE% -%VARNUMBER% -%VARNUMBER_PRE_UNDERSCORE% -%MULTICONFIGNAME% Memory class of this Config Pointer. Type of this Config Pointer. DefRef Path to the MultipleConfigContainer.