Production Code Node

Note
These options are only available when ASCET‑SE is installed, and a respective target is selected in the Build node.

Generate Data Structures

Determines whether data structures are generated.

Use Component Settings

Default setting.

Data structure generation is determined by the setting in the selected implementation of each included component.

Yes for All Components

Data structures are generated for all components in the project. Overrides component settings.

No for All Components

No data structures are generated for any component in the project. Overrides component settings.

Generate OS Configuration

Switches the generation of the conf.c file on (activated; default) or off (deactivated). This file contains the entire code for the OS configuration.

When the option is deactivated, no operating system configuration is generated; neither in the conf.c file nor in the project file. When you start an offline or online experiment while the option is deactivated, the following error message is displayed.

Conf.c generation must be active for experiment. Please switch 'generate OS configuration' to 'yes' in the code generation options.

Generate Map File

Note
If an AUTOSAR operating system is selected in the Build node, this option is always active and set to read-only.

Can be deactivated to suppress the automatic generation of a special map file, the virtual address table, after the code has been generated. This map file is required for the ASAM-MCD-2MC generation.

Generate VAT File

Note
This option is editable only if an AUTOSAR operating system is selected in the Build node.

Specifies whether a VAT virtual address table is generated as required by map file generation. If this option is activated, ASCET generates VATs as additional data structures that are allocated to VATROM and should not be located to physical memory on the micro controller.

This option does not change the functional behavior of the model.

Add Implementation Definitions

Can be activated to include comments with additional information regarding implementations in the generated code.

Generate Access Methods for dT (Alternative: use OS dT directly)

Specifies how the global variable dT provided by the operating system is to be used. If this option is deactivated, dT is taken directly from the operating system. The implementation of dT then cannot be modified. If this option is activated, dT is evaluated through a method invocation.

This allows using a customized implementation for dT in the model. In any case, for the respective task one of the options monitoring or dT only must be set in the pre/post-hooks menu of the OS editor, if dT is to be used in the model.

Use OID for Generation of Component Names

Specifies whether the component OID (activated) or the model name (deactivated) is used as component name in the generated code.

If the option is activated, the target optionsClass, Module, Project, or Record Type (ASCET options, <target>/Name Templates/ANSI-C node) are ignored and _%^COMPONENT.OR.IMPL.ID^% is used instead. This leads to the same type names that the Use OID * option in the Experiment Code node will generate for experiment targets. Name clashes between components with identical names, but different locations in the ASCET database/workspace are avoided.

Note
If the option is deactivated, you are responsible for avoiding name clashes. With this setting, you cannot use components with identical names, but different locations in the ASCET database/workspace in the same project.

Note

If the option is deactivated, you are responsible for avoiding name clashes.

With this setting, you cannot use components with identical names, but different locations in the ASCET database/workspace in the same project.