, that determines whether scope-limiting definitions are generated for BSW APIs within the Module Interlink Header file. Generation is not required for AUTOSAR compliance. If this option is not specified scope limiting definitions are generated in the same form as used for application header files. This option is supported by the OutputC plug-in ‘To use enable generation of scope-limiting definitions, use: --bsw-scope-Limit-defns=on Command-line options 27RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.9 --bsw-xml-namespace Description: Set the XML namespace URI used in generated BSW configuration file. Name: --bsw-xml--namespace Parameter: This option takes a single parameter, , that specifies the namespace URI to be used within the generated BSW configuration file, If this option is not specified the default namespace is used. This option is supported by the RTA-BSW plug-in. To use http: //namespace as the namespace URI when generating the BSW configuration file, use: -bsw-xml-namespace=http: //namespace 28 Command-line options3.10 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --calibration-disable Description: Disable RTE calibration supported for specified SWC type. calibration-disable Parameter: — This option takes a single parameter, , which must be an ab- solute reference to the SWC type for which calibration should be disabled. Default: NA Note: This option has no effect if the selected global calibration method is ‘none’. Calibration can also be disabled for individual SWC types using the ECU Configuration description. Example: To disable calibration for SWC /pkg/swcA use the following com- mand: --calibration-disable=/pkg/swcA Command-line options 29RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.11 --calibration-instantiation Description: Determines whether RTA-RTE allocates memory (RAM) for calibration instances or imports labels. Name: --calibration-instantiation Parameter: This option takes a single parameter, that specifies whether to import (import) or allocate memory (‘allocate’) for calibration instances. allocate. None The command-line option: -calibration-instantiation=allocate Causes RTA-RTE to allocate RAM buffers for each calibration group. ‘These buffers should be initialized by the application before the RTE is started. (See section 27.) Alternatively, the command-line option: --calibration-instantiation=import Causes RTA-RTE only to import labels using the extern keyword These labels can be set to buffers which are initialized externally to the generated RTE code. 30 Command-line options3.12 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --calibration-method Description: Parameter: Default: Example: Select the global calibration method. calibration-method This option takes a single parameter that specifies the selected cal- ibration method. Supported values are: none, singlePointered doublePointered, initializedRam, and singlePointered2 none The selected calibration method affects the data structures and gen- erated functions created to support calibration, The API presented to SW-Cs within the application header is not affected. For RTE generation phase, this option can be set both in the ECUC file and on the command-line. If specified in both places then RTA-RTE will use the command-line value. To select single-pointered method: calibration-method=singlePointered Command-line options 31RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.13 --client-server-global-optimization Description: Select whether or not non-AUTOSAR optimizations of inter partition client-server communication should be performed. Name: --Client-server-global-optimization Parameter: — This option takes a single parameter which enables (“on" or “1") or disables (“off” or “0") use of non-AUTOSAR optimizations for inter partition client-server communication. Disabled (“off”) for AUTOSAR compliance. None To enable the use of non-AUTOSAR optimizations for inter-partition client-server communication: -client-server-global -optimization=on 32 Command-line options3.14 RTA-RTE V6.2.0 Reference Manual --com-symbolic-sigs Description: Use C symbols for COM signal handles, com-symbolic-sigs Parameter: _ None. ETAS Default: By default, RTA-RTE generates an RTE that uses a COM signal’s nu- merical handle ID when invoking COM AP! functions. When this option is specified the generated RTE uses the symbolic name of the signal instead of the handle ID. This option must be specified when RTA-RTE is used with an AUTOSAR v1.0 compliant CoM. Example: —_To enable use of symbolic signal names: --com-symbolic-sigs Command-line options 33RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.15 --com-version Description: Modify the generated code to be appropriate for the given version of AUTOSAR COM. Name: --com-version Parameter: The parameter specifies the required version. Supported and default COM versions are dependent on the selected RTA-RTE back- end processor. Dependent on selected backend processor. None To specify use of AUTOSAR COM v1.0: -com-version=1. 34 Command-line optionsRTA-RTE V6.2.0 ETAS Reference Manual VG EMBEDDED EXCELLENCE 3.16 --contract Description: Execute contract phase for a specific software module. Name: contract Parameter: — This option takes a single parameter that must be an absolute refer- ence to the ApplicationSoftwareComponentType type or Bswimple- mentation for which contract-phase headers should be generated. Default: NA Note: Use - -contract to support the AUTOSAR RTE Contract Phase or Ba- sic Software Scheduler Contract Phase. RTA-RTE will generate an application header file for the specified application software compo- nent type or BSW implementation. To generate headers for multiple software modules, the --contract option can be repeated on the command line. You cannot mix contract phase and generation phase in the same run of RTA-RTE. To generate the contract phase headers for two hypothetical Soft- ware Component Types swc and swcB: --contract=/myPackage/ Applicat ionSwComponentTypes/componentA --contra Command-line options 35RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.17 --deviate-allow-unmapped-swci-config Description: Enable SWC instances within the RTE module configuration to be mapped to a different ECU instance. Name: --deviate-al low-unmapped-swci-config Parameter: — This option permits ("1") or forbids ("0") SWC instances within the RTE module configuration to be mapped to a different ECU instance. When permitted a warning will be issued for each unmapped stance but generation will continue. Defaul Forbid ("0") Notes: None. Example: To allow unmapped SWC instances: -deviate-allow-unmapped-swei -config=1 36 © Command-line optionsRTA-RTE V6.2.0 ETAS Reference Manual 3.18 --deviate-appl-imp1-compu-method Description: Name: Parameter: Default: Note: Example: This option suppresses the error that would be generated by having a CompuMethod on both an Application Data Type and its mapped Implementation Data Type. --deviate-appl -impl-compu-method This option enables ("1") or disables ("0") the deviation. Enabled ("1"). Standard AUTOSAR behavior specifies that when the CompuMethod is in both an Implementation Data Type and its mapped Application Data Type that this is an error. To make RTA-RTE raise a configuration error when the CompuMethod is on both the Application Data Type and its mapped Implementation Data Type (which is standard AUTOSAR behavior): --deviate-appl-impl-compu-method=of f Command-line options 37RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.19 --deviate-appl-impl-display- format Description: This option suppresses the error that would be generated by having a DisplayFormat on both an Application Data Type and its mapped Implementation Data Type. Name: -deviate-appl-impl-display-format Parameter: This option enables (“on" or “1") or disables (“off" or “O") the deviation, Enabled ("on"), Standard AUTOSAR behavior specifies that when the DisplayFormat is in both an Implementation Data Type and its mapped Application Data Type that this is an error. To make RTA-RTE raise a configuration error when the DisplayFormat is on both the Application Data Type and its mapped Implementation Data Type (which standard AUTOSAR behavior) -deviate-appl-impl-display-format=off 38 Command-line options3.20 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --deviate-bsw-any-partition Description: Parameter: Default: Note: Example: Enable mapping of BSW to any OS partition. deviate-bsw-any-partition This option enables (“1”) or disables (“0") an RTA-RTE deviation from the AUTOSAR RTE specification. When enabled BSW may be mapped to any OS partition. Disabled ("0"). None. To enable mapping of BSW to any partition: --deviate-bsw-any-partition=1 A This option has received limited testing in this release of RTA-RTE. If mapping to any partition is enabled the gen- erated RTE must be thoroughly tested before use. Command-line options 39RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.21 --deviate-allow-supportsmulti-sharedmemorys Description: Allow supportsMultipleinstantiation to be set on a SWCT with staticMemorys Name: --deviate-allow-supportsmulti-sharedmemorys Parameter: — This option enables ("1") or disables ("0") an RTA-RTE deviation from the AUTOSAR RTE specification. According to the specification, it is an error to set supportsMultipleinstantiation on an InternalBehavior that contains staticMemorys. When this option is enabled, the error is reduced to a warning, and an error is only raised if the input model actually contains multiple instances of the related SWCT. Default Disabled (“0”). None. -deviate-allow-supportsmulti-sharedmemorys=1 40 Command-line options3.22 RTA-RTE V6.2.0 ETAS Reference Manual --deviate-enum-cast Description: Parameter: Default: Explicitly cast literals used in enumerations (AUTOSAR TEXTTABLES). deviate-enum-cast This option takes a single parameter, , that specifies whether the option is enabled (‘1’) or disabled ('0') Disabled (AUTOSAR compliant). RTA-RTE writes preprocessor define directives for the symbolic val- ues in TEXTTABLEs according to AUTOSAR (rte_sws 3810). In addition to this, if the --deviate-enum-cast option is enabled, RTA-RTE also emits an explicit cast to the underlying Implementa- tionDataType. Regardless of this option, RTA-RTE writes a ‘U’ suffix to the numeric literal if the underlying SwBaseType is unsigned or missing #define E1_VALUEL 34U with --deviate-enum-cast=1 becomes #define £1 VALUE1 (myUnsignedEnumType) 34U Command-line options = 41RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.23 --deviate-group-calibration-none Description: Control grouping of calibration parameters. Name: -deviate-group-calibration-none Parameter: — This option takes a single parameter, , that specifies whether to enable ('1') or disable (‘0") the grouping of calibration parameters for ‘none’ calibration method. Default Disable grouping (AUTOSAR compliant). Note: RTA-RTE instantiates calibration parameters. For the single- and double-pointered calibration methods all parameters are grouped according to the assigned SwAddrMethod. This option enables grouping to also be applied when the ‘none’ calibration method is selected. RTA-RTE will apply grouping when no flatmap instance descriptor is available since the descriptor is required to assign a name to the parameter instance. To cause RTA-RTE to group calibration parameters when using the ‘none’ method -deviate-group-calibration-none= 42 Command-line options3.24 RTA-RTE V6.2.0 ETAS Reference Manual --deviate-ignore-datatype- semantics Description: Parameter: Default: Note: Example: Control semantic checks when checking type correctness. deviate-ignore-datatype-semantics This option takes a single parameter,

, that specifies whether to ignore ('1') or enable ('0') the semantic checking of connected data types Enable check (‘0"). AUTOSAR specifies compatibility rules for connected DataPrototypes involving the referenced AutosarDataType and any CompuMeth- ods, Units, or PhysicalDimensions involved. Additionally, for R4.x projects, the AUTOSAR specification states that when VariableDat- aPrototypes are not compatible it is still permitted to connect them if they conform to further rules about whether automatic data con- version is possible. In some configurations, it may be necessary to allow connection of DataPrototypes that do not fully conform to the AUTOSAR compati- bility rules. With this option specified, the compatibility and convertibility checks are very much relaxed, with the CompuMethod, Unit, and Physi- calDimension being completely ignored In addition, RTA-RTE normally checks that any CompuMethod refer- enced by an ImplementationDataType is permitted according to con- str_1158, raising an error if the check fails. If this option is specified, then the error is downgraded to a warning, allowing the generation to continue. To ignore semantic checks: --deviate-ignore-datatype-semantics=1 Command-line options 43RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.25 --deviate-implicit-cat2-mdd Description: Enable mode disabling dependency for category 2 runnables. Name: -deviate-implicit-cat2-mdd Parameter: — This option permits ("1") or forbids (“0”) mode disabling dependency for implicitly category 2 runnables. Forbid ("0" Note: Prior to AUTOSAR R4.0, a runnable is implicitly category 2 if it cludes a synchronous call point. This option permits such runnables to have mode disabling dependencies. To enable mode disabling dependencies for category 2 runnables: -deviate-implicit-cat2-mdd=1 44 Command-line options3.26 RTA-RTE V6.2.0 Reference Manual --deviate-imp' TAS m Licit-modi fy-for-Loopbacks Description: Name: Parameter: Default: Note: Example: Enable “data modify" semantics for implicit access to data items where there is a loopback assembly connector. --deviate-impLicit-modify-for-Loopbacks This option enables (“on” or “1") or disables (“off” or “0”) “data mod- ify” semantics for implicit access to data items where a loopback assembly connector exists. Disabled (“off”). Without this option, RTA-RTE implements AUTOSAR rules for the visi- bility and propagation of implicit data, and creates uninitialized Write Buffers for implicit writers to support that. One consequence of this is that Runnables using Rte_IWriteRef to write parts of a complex type will result in undefined values being propagated on the other members of the type. When this option is enabled, if you connect the PPort back to an RPort characterized by the same interface in the same swe proto- type, then RTA-RTE initializes the implicit writeback buffers from the definitive, global buffer before the Runnable enters. This enables the use of partial writes of complex data by multiple runnables without the propagation of undefined variables. It is permitted, but not necessary, to configure a DataReadAccess in the Runnable for the configured RPort. In applications using split To enable “data modify” semantics for implicit access to data items: --deviate-implicit-modi fy-for-loopbacks=on Command-line options 45RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.27. --deviate-memmap-decls Description: Select whether or not memory allocation sequences should be used for declarations as well as definitions. Name: --deviate-menmap-decls Parameter: — This option takes a single parameter which enables (“on” or “1") or disables (“of f” or “0") use of MemMap for declarations. Defaul Enabled (“on”). Note: None. Example: To disable generation of MemMap decorations: -deviate-memmap-decls=off 46 Command-line optionsRTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS 3.28 --deviate-omit-implicit-cds Description: Parameter: Default: Example: Enable optimization of CDS for implicit S/R and IRVs. deviate-omit -implicit-cds This option enables (“1”) or disables (“0") optimization of the com- ponent data structure (CDS) for implicit access to S/R and IRVs. Forbid (“0”). Optimization of the CDS removes the data handles that are not re- quired. Optimization is possible when the SWC is: 1. Singly instantiable, 2. Delivered as source code, 3. RTE generator is in vendor mode, 4, This option is enabled. To enable optimization of the CDS for implicit S/R and IRVs: --deviate-omit-implicit-cds=1 Command-line options 473.29 RTA-RTE V6.2.0 ETAS Reference Manual --deviate-physical-dimension-compatibility Description: Parameter: Note: Example: Specify physical dimension compatibility rules. -deviate-physical-dimension-compatibility This option enables ("1") or disables ("0") an RTA-RTE deviation from the AUTOSAR RTE specification. Disabled (“0”). This option modifies how the RTE generator validates compatibility of physical dimensions. 8y default RTA-RTE validates according to AUTOSAR rules and thus the physical dimensions must have the same short-name and attributes. However when this option is en- abled RTA-RTE only checks the attributes, e.g. length exponent, match and permits the short-names to differ. This enables different elements that represent the same physical dimensions to be con- nected but should be used with care since physical dimensions with matching attributes can still represent different physical quantities. See the AUTOSAR documentation for further details. To enable non-AUTOSAR compatibility rules for physical dimension comaptibility: -deviate-physical-dimension-compatibility=1 48 Command-line options3.30 RTA-RTE V6.2.0 Reference Manual --deviate-pre' rvncomoocune | ETAS fer-no-empty-executions Description: Name: Parameter: Default: Notes: Example: Enable (Yon” or “1") or disable (“off or “") optimizations to runnable entity scheduling that avoid empty executions of tasks containing only runnables (or schedulable entities) triggered by the same source, at the expense of loss of the guarantee that the runnables will execute after being activated during the execution of the task, --deviate-prefer-no-empty-executions This option enables (“on” or “1") or disables (“off” or “0”) optimiza- tions to the scheduling of runnables that reduce execution overhead but cause the behavior to deviate from the AUTOSAR specification and may cause activations occurring during runnable execution to be delayed or lost. Disabled (“off”). When enabled, activation flags are elided for tasks containing only runnables that are activated by the same trigger source and such tasks are required to be configured with an activation limit of one. This avoids empty task executions in the case of bursts of runnable activations but activations occurring while the task executes are de- layed or lost, deviating from the AUTOSAR requirement that activa- tions of a runnable during its execution be honored. --deviate-prefer-no-empty-executions=on Command-line options 493.31 RTA-RTE V6.2.0 Reference Manual ucemmeroauna | ETAS --deviate-split-swci-support Description: Parameter: Default Note: Split Sw-Cs across OsApplications -deviate-spLit-swci-support This option enables (“on” or “1") or disables (“off” or “0") splitting AppLicationSofwareComponents across protection boundaries, i.e. by mapping the Runnables to OsTasks in different OsApplications. Disabled (“off”) When enabled, this option allows RteEvents from a SWCT to be mapped to OsTasks in different OsApplications, in violation of AU- TOSAR 4.0.3 [rte sws_ 7347]. When this option is enabled, InterrunnableVariables might need to cross protection boundaries. RTA-RTE will silently augment the input model with port communication to handle this case, causing the IoC to be invoked where needed, ‘To map runnables from the same SWCinstance to OsTasks in ent OsApplications, --deviate-spLit-swci-support=on 50 Command-line optionsRTA-RTE V6.2.0 ETAS Reference Manual VG EMBEDDED EXCELLENCE 3 3.32 --deviate-task-sections Description: Modify the section names used by RTA-RTE to locate task bodies. When enabled, each task body is contained within a section named after the task; e.g. "RTE_START_SEC_TASKBODY_", Name: --deviate-task-sections Parameter: — This option takes a single parameter to switch the option on or off. Supported values are “on” and “off”. Default: Standard AUTOSAR naming convention (“off”) Rte _MenMap..h must be modified to support the new section names. To place task bodies into their own memory sections: --deviate-task-sections=on Command-line options 51RTA-RTE V6.2.0 Reference Manual ucemmeroauna | ETAS 3.33. --deviate-trace-implicit-api Description: Enable generation of VFB trace hooks for implicit API. Name: -deviate-trace-implicit-api Parameter: — This option enables ("1") or disables ("0") an RTA-RTE deviation from the AUTOSAR RTE specification. When set VFB trace hook calls are added for implicit API functions / macros. Defaul Disabled ("0"). None. Example: To enable VFB trace hook generation for the implicit API -deviate-trace-implicit -api=1 52 Command-line options3.34 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --deviate-unconnected-pmode-behavior Description: Parameter: Default: Notes: Example: Control behavior of unconnected mode PPorts. deviate-unconnected-pmode-behavior This option controls whether a mode manager Rte. Switch API stores the current mode (“on”) or discards the input parameters (“off”). When enabled the behavior of the API is an RTA-RTE deviation from the AUTOSAR RTE specification since AUTOSAR requires an uncon- nected mode manager to discard the inputs. Disabled ("off"). None. To enable storing of the current mode by an unconnected mode man- ager: --deviate-unconnected-pmode-behavior=on Command-line options 53RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.35 --diagnostic Description: Display RTE generator diagnostic information Name: -diagnostic Parameter: None Default N/A Note: Create an HTML diagnostic report including RTE generator and plug- in versions, OS version and environment variables. The diagnostic report is written to diagnostic.htm. The output lo- cation, but not the filename, of the report can be modified using the --output opti Example: To enable generation of the diagnostic report: -diagnostic 54 Command-line options3.36 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --disable-warning Description: Disable display of specified warning. disable-warning Parameter: The option takes a single parameter. , that specifies the iden- tifier of the warning or informational message to be disabled. The option can be specified multiple times to disable multiple warnings, Default: #pragma message Note: This option can disable the display of both warming and informa- tional messages. When disabled RTA-RTE does not show the mes- sage and does not count the warning or information in the totals. A This option can be disabled within the INI file by setting the flag DisableWarningOption to “disable” within the section Options. Example: —_To disable information message 153-7701: --disable-warning=153-7701 Command-line options 553.37 RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE --error-as-warning A This option is deprecated and will be removed ina future version of RTA-RTE. It should not be used in new projects. Existing projects should be updated to no longer use this option. Description: Demote specific error to warning. Name: --error-as-warning Parameter: — The option takes a single parameter , that specifies the iden- tifier of the error message to be demoted to a warning. The option can be specified multiple times to demote multiple errors. Default: NIA Notes: This option produces undefined behavior and should not be used. This option should be disabled in production projects by adding ErrorAsWarningOption=disable to the [Options] section of RTEGen.ini. This option demotes the severity of a message from “E” (error) to “W" (warning). As a result, RTA-RTE does not stop processing and will continue to attempt to generate code. Because an error has occurred, behavior in subsequent steps is un- defined. The option might be used during debugging to gather knowledge about generator bugs or problems with the input configuration. Example: To demote error message E53-1234 to W53-1234 -error-as-warning=E53-1234 56 Command-line optionsRTA-RTE V6.2.0 ETAS Reference Manual VG EMBEDDED EXCELLENCE 3.38 --error-report Description: Select the message output method error-report Parameter: This option takes a single parameter, , that specifies the destination and format of the Information, Warning, and Error mes- sages. Supported values are * console format messages and write to the standard error stream, © file create file Rte.err. Format the messages as for console and write them to this file along with a summary. © xml create file RteErr.xml. Format the errors and summary in XML and write to the file. “console” ‘To send all generated errors to a file use the following option: --error-report=file Command-line options 57RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.39 --exclusive-area- optimization Description: Set optimization policy of RTE exlusive area APIs. Name: -exclusive-area-optimization Parameter: This option takes a single parameter,

, that specifies whether to “enable” or disable “disable” optimization “enable” Note: When exclusive area optimization is disabled © For explicitly accessed exclusive areas the generated Rte Enter/Rte Exit APIs are not mapped “null” implementa- tions even when all accessors are already in mutual exclusion (e.g. mapped to same task). '* For implicitly accessed exclusive areas, RTA-RTE will perform no optimization to “null” implementation of enter/exit locks created within the highest priority task. To disable optimization of exclusive area access: --exclusive-area-optimization=disable 58 Command-line options3.40 RTA-RTE V6.2.0 ETAS Reference Manual --fast-init Description: Enable fast activation for mode switch events Name: fast-init Parameter: This option takes a single parameter, , that specifies either an atomic SWC type or a ModeSwitchEvent. Default: The default activation policy is AUTOSAR compliant activation there- fore this option needs to be specified for each event that is to be activated by the non-AUTOSAR compliant mechanism. Enables ModeSwitchEvents to be activated by a non-AUTOSAR com- pliant mechanism (for example, a function call from the body of a task started outside the control of the RTE). ModeSwitchEvents may be specified either individually by name or as a group by naming the ‘SWC type to which they belong. This avoids the complexity inherent in AUTOSAR-compliant activation for mode switch activations and is especially useful for “init” runnables that are activated only once. To enable fast activation for RTE Event ev] within an internal behav ior 18: --fast-init=/pkg/1B/ev1 Command-line options 593.41 RTA-RTE V6.2.0 Reference Manual --file ucemmeroauna | ETAS Description: Parameter: Default Note: Example: Read options from command file. -file The file from which commands are read N/A Read command-line options from the specified file in addition to any read from the command line. The option can be used recursively; a file read using -- file can include other files The ‘@’ character can be used as a synonym for the -file option. The space separating ‘@’ and into separate command-line arguments is optional. Command line parameters included with this must observe the same rules as if they were specified directly on the command line with the exception that options can be split across multiple lines. Comments can be included in a command file. A comment starts with semicolon character (';’) either at the start of the line or after some whitespace. Text up to the end of the line is ignored. The file should be a plain ASCII text file, No special file extension is required. The following examples both read options from the file project. rte: ~-file=project.rte @project.rte 60 Command-line optionsRTA-RTE V6.2.0 ETAS Reference Manual VG EMBEDDED EXCELLENCE 3.42 --force-basic-tasks Description: Force basic tasks. Name: force-basic- tasks Parameter: — This option takes no parameters. If omitted, then the task’s forced- basic semantics are taken from the ECU Configuration file (see Sec- tion 4.19.2). Default: NA When specified RTA-RTE uses forced-basic semantics (see RTA-RTE User Guide) for all tasks in the ECU instance for which the RTE is being generated. This option overrides any settings in the ECU Con- figuration file To enable force-basic semantics for all tasks: --force-basic- tasks Command-line options 61RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.43 --have-64bit-int-types Description: Enable support for 64-bit platform types for use within generated data-transformation, Name: --have-64bit-int-types Parameter: — This option takes a single parameter,

, that specifies whether to enable (‘1’) or disable (‘0") the use of 64-bit types. Default Disabled (‘0") Note: This option enables use of 64-bit types within generated data- transformation functions. Since these types are not standardized by AUTOSAR the option is disabled by default. If enabled the types must be defined when the generated RTE is compiled. To indicate to RTA-RTE that 64-bit types are available: --have-64bit-int-types=1 62 Command-line optionsRTA-RTE V6.2.0 ETAS Reference Manual VG EMBEDDED EXCELLENCE 3.44 --help Description: Display RTE generator help. help Parameter: None Default: NA Note: Print the usage information on the standard output. Brief usage in- formation is presented when using -?/-h and more detailed informa- tion with --help Example: To display the help text: --help Command-line options 633.45 RTA-RTE V6.2.0 Reference Manual --implicit-at ucemmeroauna | ETAS Location-method Description: Name: Parameter: Default Note: Select the allocation method used by RTA-RTE for creating implicit communication buffers. Supported methods are ‘overlay’ and ‘task’ --impLicit-allocation-method This option takes a single parameter which is the method to use. Supported values are “task” and “overlay”. “overlay” Method “task” causes a separate structure to be created and instantiated by RTA-RTE for each task’s implicit buffers. The structure instance is allocated to its own memory section called SEC VAR IMPLICITSR where is the task name in up- percase. Method “overlay” creates a single structure where tasks that cannot preempt (e.g. those at the same priority) have overlayed implicit buffers. To enable separate structures for each task’s implicit buffers: --implicit-allocation-method=task 64 Command-line optionsRTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS 3.46 --implicit-read-return-const Description: Parameter: Default: Notes: Control whether or nor the CONST or VAR compiler abstraction macros are used to cast the return value from Rte_TRead. --implicit-read-return-const This option takes a single integer parameter which defines cast used. © Use of CONST cast disabled; the API mapping uses a VAR cast. 1 Use of CONST cast enabled. 1 (CONST cast). None. To enable use of a VAR cast: --implicit-read-return-const=0 Command-line options 653.47 RTA-RTE V6.2.0 Reference Manual --implicit-us m > u e-global-buffers Description: Parameter: Default Enable or disable use of global receive buffers in place of task- specific buffers for implicit communications. This optimization is de- pendent on task preemption but when possible can save RAM since no additional copies of the global data are required. -implicit-use-global-buffers This option takes a abled optimizations. gle integer parameter which defines the en- © Optimization disabled; all implicit communication uses AUTOSAR compliant task-specific buffers. 1 Optimization of implicit communication to use global buffers is en- abled. The possible optimization depends on the relative pri- orities of tasks containing readers and writers: for best results either map to tasks at the same priority or map to the same task. 2 As ‘7’ plus all ‘fast-init’ tasks use global buffer access for implicit communication. For ‘fast-init’ tasks the optimization occurs ir respective of the task mapping of readers and writers since it is assumed that execution of the ‘fast-init” tasks is complete before periodic runnables (and hence normal RTE tasks) start. © (optimization disabled and AUTOSAR compliant task-specific buffers used). Notes: None. Example: To enable use by the generated RTE of global receive buffers: -implicit-use-global -buffers=1 66 Command-line options3.48 RTA-RTE V6.2.0 ETAS Reference Manual --incremental-build Description: Parameter: Default: Note: Incremental Build incremental-build This option takes a single parameter that enables (‘1’) or disables (‘0’) incremental output of generated files. If not specified incre- mental output is disabled. Build all files (incremental build disabled). When enabled, RTA-RTE generates files to a temporary folder and only overwrites files in the destination folder if the contents have changed. This option turns on the - -notimestamps option. To enable incremental build --incremental-build=1 Command-line options 673.49 RTA-RTE V6.2.0 Reference Manual --initial-val ucemmeroauna | ETAS ue- rounding Description: Name: Parameter: Notes: Example: Select the rounding behavior for the calculation of initial values for integer data from physical values. --initial-value-rounding This option takes a single parameter which specifies the required rounding behavior for the calculation of initial values for integer data types from physical values. The supported rounding behaviors are ‘truncate’ meaning truncation towards zero and ‘nearest’ meaning rounding to nearest, with half values rounding away from zero. truncate When a physical value is given with an ApplicationValueSpecifica- tion the computation of the corresponding internal value may result in a fractional value that must be rounded in the case that the des- tination data type is an integer. This option allows that rounding behavior to be selected The ‘truncate’ behavior means to truncate towards zero, so for ex- ample 2.3 and 2.8 both become 2 and —1.2 and —1.9 both become =1 The ‘nearest’ behavior means to round to nearest, with half values rounding away from zero, so for example 2.4 becomes 2, 2.8 and 2.5 both become 3, 1.2 becomes ~1 and —1.7 and ~1.5 both become To select rounding to nearest behavior: --initial-value-rounding=nearest 68 Comma nd-line options3.50 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --ioc-header Description: Set the IOC header file used. ioc-header Parameter: This option takes a single parameter, , that specifies the name of the IOC header file to use within generated code. Default: None. Note: This option is valid in vendor mode only. Example: To use IOC header ioc. h: --ioc-header=ioc.h Command-line options 69RTA-RTE V6.2.0 Reference Manual ucemmeroauna | ETAS 3.51 --ioc-xml-namespace Description: Set the XML namespace URI used in generated IOC configuration file. Name: -ioc-xml-namespace Parameter: This option takes a single parameter, , that specifies the namespace URI to be used within the generated 10C configuration file, Default If this option is not specified the default namespace URI is the R4.0 default namespace. This option is supported by the RTA-IOC OS plug-in. To use http: //namespace as the namespace URI when generating the IOC configuration file, use: ~ioc-xml -namespac ttp://namespace 70 Command-line optionsRTA-RTE V6.2.0 ETAS Reference Manual VG EMBEDDED EXCELLENCE 3 3.52 --local-mesd Description: Report “local McSupportData” for a specific software module. Name: local -mesd Parameter: — This option takes a single parameter that must be an absolute refer- ence to the ApplicationSoftwareComponentType type whose internal data are to be reported in McSupportData Default: NA Note: This is a non-AUTOSAR generation phase that generates McSupport- Data for specific software modules. RTA-RTE will generate an Mc- SupportData report containing the staticMemorys, constantMemo- rys and perinstanceParameters of the given modules. To include multiple modules in the McSupportData, specify the --local-mcsd option multiple times on the command line. You cannot mix “local MCSD phase” with any other phase in the same run of RTA-RTE To generate McSupportData for two hypothetical Software Compo- nent Types swcA and swcB: --local-mcsd=/MyPackage/AppLicationSwComponentTypes/swcA --Llocal-mcsd Command-line options = 71RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.53 --makedep Description: Output dependency information for generated files. Name: -makedep Parameter: The option takes one parameter, , which is the file to which dependency information is to be written. N/A None. Example: To enable generation of dependency information and output it to file rte.dep use: --makedep=rte.dep 72 Command-line options3.54 RTA-RTE V6.2.0 ETAS Reference Manual --mcore-spinlocks-always Description: Parameter: Default: Enable spiniocks in multicore mode handling, mcore-spinlocks-always This option enables ("1") or disables ("0") spinlocks in multicore mode handling. Disabled ("0"). When enabled, RTA-RTE emits spinlocks for concurrency protection in Mode APIs. At the time of writing, RTA-RTE does not optimize spin- locks, so specifying this option will cause all Mode Machine Instances to use spinlocks even if there is no inter-core communication to pro- tect against. For this reason, the option should not be used if the input model contains no inter-core mode handling. Enable inter-core mode handling: - -mcore-spinlocks-always=1 Command-line options 733.55 RTA-RTE V6.2.0 ETAS Reference Manual --mesd- policy Description: Specify options pertaining to the output of Measurement and Call- Name: bration Support Data (MCSD). --mesd-policy Parameter: — This option takes a single parameter: a comma-separated list of op- Default Notes: tions which modify the MCSD as follows: emit-memorys emits NcDataInstance containers for any BSW or ASW Static or Constant Memory. phys-constrs-always RTA-RTE shall always write PhysConstrs re- lated to every McDatalnstance. If necessary, the PhysConstr will be taken from The ApplicationDataType, Implementation- Datatype, CompuMethod (for enumerated types) or SwBase- Type (for Category NONE, 2C or BOOLEAN). If no PhysConstr can be found or calculated, an error is raised. mcfunction-from-shortname For all McDatainstances where RTA- RTE sees a relevant DataPrototype. that DataPrototype’s short- Name is copied to the McDatainstance’s McFunction. This pol- icy is deprecated; it was implemented as a workaround for use before RTA-RTE exported McFunction correctly. struct-element-symbols For McDatainstances that are structure elements, the C names for the elements are emitted as their symbols. These are not global linker symbols but they do al- low the full C expressions to access the elements to be con- structed, N/A NIA -mesd-policy=emit-menorys 74 Command-line options3.56 RTA-RTE V6.2.0 ETAS Reference Manual --measurement Description: Globally enable (or disable) support for measurement. Name: measurement Parameter: The option takes a single parameter, , that specifies whether measurement is enabled (“1", “2” and “3”) or disabled ("0") Default: Enabled ("1") With parameter “ inter-runnable vai separately. , each data element, client-server argument and ble that is to be measured must be configured With parameter “2”, measurement is enabled for all data elements and inter-runnable variable irrespective of the configuration within the XML input. This setting therefore enables items to be measured in 3rd party components (for which source is available) without mod- ifying the source XML. Parameter “3” extends “2” to also measure all client-server argu- ments. For RTE generation phase, this option can be set both in the ECUC file and on the command-line. If specified in both places then RTA- RTE will use the commang-line value — this enables simple override of the “fixed” configuration value. To enable measurement for all data elements (including inter runnable variables) irrespective of the settings in the input config- uration use the following option: --measurement= Command-line options = 75RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.57 --memory-sections Description: Specify location of the Memory Section Description File Name: -memory-sections Parameter: — specifies the folder containing the memory section de- scription file. The specification can be an absolute or relative path. A relative path is interpreted relative to the folder containing the current folder. File “nemsect .xml" within the folder containing the application exe- cutable. If the file is specified both in the INI configuration file and on the command-line the latter takes precedence. Notes: See RTA-RTE Toolchain integration Guide for further details on using the Memory Section Description File to adapt the AUTOSAR compiler abstraction usage within generated code. ‘To use memory section description file mymemsect .xml: -memory-sections=nymemsect . xml 76 Command-line options3.58 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --notimestamps Description: Disable timestamps in generated files. Name: notimestamps Parameter: None Default: Include timestamps. Note: Example: Output fixed-text banner (omit date and time of generation in gen- erated files). This option is useful when the generated output will be programmatically compared, e.g. by a source control system. To disable timestamp generation: --notimestamps Command-line options 77RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.59 --operating-system Description: Select which OS support to use. Name: -operating-system Parameter: The option takes a single parameter, <0S> that is the name of the 05 to use, for example autosari0. Dependent on selected backend. Note: The selected OS determines both the OS API used within the gener ated RTE and also the form of the generated OS configuration file (if any). To select the autosara0 OS support: -operating-system=autosar4e 78 Command-line options3.60 RTA-RTE V6.2.0 ETAS Reference Manual --optimize Description: Set the optimization strategy for the generated RTE Name: optimize Parameter: This option takes a single parameter, that specifies the opti- mization type. Supported values are “Runtime” (optimize for speed) and “Memory” (optimize for code size). Default: “Runtime” (speed) Note: When optimized for “Memory” (size) RTA-RTE invokes the COM API Example: directly to access non-queued signals rather than allocating buffers for storage. The optimization strategy can also be set using the RTE Generation parameters within the ECU Configuration description. A setting on the command-line overrides a setting in the ECU Configu- ration description. The short-form of this option is an uppercase letter “O" For RTE generation phase, this option can be set both in the ECUC file and on the command-line. If specified in both places then RTA-RTE will use the command-line value — this enables a simple override of the “fixed” configuration value, To enable optimization for “memory” usage: --optimize=-Memory Command-line options 79RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.61 --os-define-osenv Description: Define OSENV within Rte Const.h. Name: -os-define-osenv Parameter: — This option takes a single parameter which is the OSENV to define. If this option is not specified, then OSENV._ must be defined when the RTE is compiled. Note: Usually the OSENV_ should be defined when the RTE is com- piled. If it is not practical to change compiler flags for your project, for example the RTE is generated and compiled at different sites, then this option allows you to set the symbol when generating the RTE. To define RTA-OSEK as the OS environment: 80 Command-line options3.62 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --0s-fp Description: Set whether or not user code invoked by RTE generated tasks uses floating-point operations/arithmetic support. Name: --0s-fp Parameter: This option takes a single parameter that specifies whether floating point usage is disabled (“of f” or “0") or enabled (“on” or “1"). Default: Enabled (“on”). Note: This option only affects the OIL configuration file created by AU- TOSAR R1.0 OS plug-in. Its usage enables the additional optimiza- tions included in RTA-OSEK 5.0 for when tasks do not use floating point. To disable FP usage: --0s-fp=of f Command-line options 81RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.63 --os-header Description: Set the OS header file used. Name: -os-header Parameter: This option takes a single parameter, , that specifies the fname of the OS header file to use within generated code. The default OS header files used are suitable for the primary target 5 of the selected OS plug-in. However this option permits a differ- ent value to be set. This option is supported by the VFB Tracing and the OS configuration plug-ins. Example: To select 0S2.h as the OS header: -05-header=0S2.h 82 Command-line options3.64 RTA-RTE V6.2.0 Reference Manual ~-05-output-pi rvncomoocune | ETAS aram Description: Name: Parameter: Default: Example: Output all OS task parameters and references OR output only those that have changed. +-0s-output-param This option takes a single parameter,

, that specifies whether task parameters and/or referenced should be copied from the in- put to the generated OS configuration file. Supported values are “changed” and “all”. “changed” When set to (“all”) this option causes RTA-RTE to output all OS task parameters (priority, activation limit and schedule) and OS task references (OS resources) regardless of whether they have been changed. When set to (“changed”) this option causes RTA-RTE to output only those OS task parameters and OS task references (OS resources) that it has modified. This option can be used with both the AUTOSAR3O and AUTOSAR4O OS support. See the RTA-RTE Toolchain Integration Guide for further details on working with RTA-RTE and the osparam option. To output all OS parameters in the generated OS configuration --0s-output -param=all Command-line options 833.65 RTA-RTE V6.2.0 Reference Manual --05-permit-e: Description: Parameter: m - sic eioaoesncrueue TAS xtended- tasks Configure whether the RTE generator is permitted to create ex. tended tasks. --0s-permit-extended-tasks This option takes a single parameter,

, that specifies whether generation of extended tasks by RTA-RTE is permitted (“1") or for- bidden (“0”). Enabled ("1") If extended tasks are disabled (option parameter “0") then certain runnable-entity mappings that require extended tasks are invalid; most notably the mixing of runnables triggered by TimingEvents with runnables triggered by other RTE Events. To disable support for extended tasks: -08-permit-extended-tasks=0 84 Command-line options3.66 RTA-RTE V6.2.0 ETAS Reference Manual --08-task-as-function Description: Name: Parameter: Default: Example: Determine if generated tasks are created using the AUTOSAR OS macro TASK or as function definitions. --0s-task-as- function This option takes a single parameter,

, that specifies whether tasks are output as functions or TASKS. When defined as “1” gener- ated tasks are created as functions which can be invoked by legacy systems. See the RTA-RTE Toolchain integration Guide for detail. Disabled ("0"). This option is supported by the C Output and OS output plug-ins. When enabled in vendor mode no task-specific header files are ref- erenced within the generated task files. When enabled, RTA-RTE replaces the TASK() macro in generated output with a function definition. A This option is incompatible with runnables that specify a minimum start interval since the execution of such runnables must be controlled by the RTE. To enable generation as tasks, use: --os-task-as-function=1 Command-line options 853.67 RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE --05-xml-namespace A This option is deprecated and will be removed ina future version of RTA-RTE. It should not be used in new projects. Existing projects should be updated to no longer use this option. Description: Set the XML namespace URI used in generated OS configuration file. Name: --0s-xml-namespace Parameter: This option takes a single parameter, , that specifies the namespace URI to be used for the generated OS configuration file. Default If this option is not specified the default is default namespace URI is http: //autosar.org/3.0.2 Notes: This option can be used with the AUTOSAR30 OS support. Example: To use http: //namespace as the namespace URI when generating the OS configuration file, use: -0s-xml-namespace=http: //namespace 86 Command-line options3.68 RTA-RTE V6.2.0 Reference Manual --output Description: Name: Parameter: Default: Notes: Example: rvncomoocune | ETAS Direct all generated output files whose names match pattern (which can include wild cards) to folder . --output, The option takes one parameter that typically consists of the pat- tern and the folder . The specification of must be enclosed in square brackets and precedes , for example ‘output=[+.c]Source. If either or are omitted then this option is ignored ex- cept for the value “check only” which, when present, causes the RTE generator to run, display detected errors and discard all output other than the error log. Files are generated in the current folder. For further details on the use of the --output option including how multiple options are parsed see Section 2.2.1. To redirect all C files to folderA and all other files to folderB use the following two options in sequence: *.c]folderA --output=[+] folders --output To log errors to a file and discard all other output use: error-report=file --output=check only Command-line options 87RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.69 --period Description: Declare the period at which Rte MainFunction will be called Name: -period Parameter: This option takes a single parameter, that specifies the time between invocations of Rte MainFunction in seconds. 0.01 (10ms period) The value of must be chosen such that all Minimum Start Inte vals are integral multiples of . For maximum efficiency, choose Greatest Common Divisor of the Minimum Start Intervals in the ECU Extract. If no Minimum Start Intervals are used then this option is not relevant. To notify RTA-RTE that the Rte MainFunction API will be invoked every 50ms: 88 Command-line optionsRTA-RTE V6.2.0 Reference Manu: rvncomoocune | ETAS 3.70 --preferred-intra-core-protection-scheme Description: Select the preferred scheme for the implementation of intra-core concurrency protection in RTE internal code. Name: --preferred-intra-core-protection-scheme Parameter: This option takes a single parameter which names the intra-core concurrency protection strategy that is preferred for RTE inter- nal code. Supported schemes are per-core-resources, where an RTE internal OS resource for each processor core is locked, 0s-interrupt-blocking, where OS interrupts are suspended and all-interrupt -bLocking where all interrupts are suspended, Default: per-core-resources Notes: The scheme selected with this option applies to RTE internal code where the accesses being protected are all from execution contexts on the same processor core and where the choice of scheme is not limited due to there being accesses from particular execution con- texts (e.g. interrupt contexts) or due to the actions of the code being protected. This option has no effect on the APIs implementing ExclusiveAreas declared in software components. Note that at the time of writing this option only applies to a small subset of the generated code. To prefer the use of OS interrupt blocking within RTE internal code: --preferred-intra-core-protection-scheme-os -interrupt -blocking With this setting OS interrupt blocking will be used where possible but there may be some places where this is not possible. For exam- ple where there is access via a BSW interrupt entity from a category 1 interrupt, all interrupt blocking will be used. On the other hand, where the protected code calls OS APIs such as ActivateTask the locking of per-core OS resources will be used, since it is not valid to call such APIs with interrupts disabled. Command-line options 893.71 RTA-RTE V6.2.0 Reference Manual --protection- ucemmeroauna | ETAS threshold-copy-bytes Description: Name: Parameter: ‘Tune the amount of data that can be copied in a critical section when. concurrency protection is needed. --protection-threshold-copy-bytes This option takes a single parameter: an integer expressing the threshold number of bytes that can be copied in one critical section. Supported values: * 0": Batch all copy operations needing concurrency protection ina single critical section. May reduce latency. * “1": Each copy operation needing concurrency protection is placed in its own critical section. May reduce jitter. * values larger than 1: apply algorithm as per notes below. “9 For thresholds greater than 1, RTA-RTE batches copy operations re- quiring concurrency protection: © When there are copies to be made that require concurrency pro- tection, RTA-RTE enters a critical section (e.g. by GetResource). * RTA-RTE holds the critical section open, potentially across multi- ple copy operations, while there are still items to copy and the cumulative work performed (as defined below) within the critical section does not exceed the threshold. ‘« RTARTE releases the critical section. + Ifnot all the copy operations are complete, RTA-RTE repeats from item 1 until all the items are copied. Work Performed = ( Number of bytes of data copied ) + ( Estimate of equivalent work, e.g. arithmetic operations Example: To enable a separate lock around each copy action: -protection-threshold-copy-bytes=1 To set protection —threshold «= to.-««32—sébytes: -protection-threshold-copy-bytes=32 In this example, if there several data items to copy totalling 60 bytes, RTA-RTE would release the critical section (e.g. by ReleaseResource followed by GetResource) ance during the batch of copy operations. 90 Command-line optionsRTA-RTE V6.2.0 ETAS Reference Manual VG EMBEDDED EXCELLENCE 3.72 --quiet Description: Control the text output. Name: --quiet Parameter: The option takes a single parameter: an integer specifying the level of output required. Valid values are: © Verbose. 1 Normal: Suppress certain plug-in information messages (default). 2 Quiet: No output other than RTA-RTE banner during normal oper- ation 3 Silent: output at all during normal operation Default: Normal output (level 1) Notes: None, Example: To suppress all output during normal operation: --quiet=3 Command-line options 91RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.73 --report Description: Enable output of XML report. Name: “report Parameter: This option takes a single parameter that specifies the the report name and, optionally, the report template file, None. None. Example: —_To generate the RteObjects report with a template: -report=[template. xml]RteObjects To generate the same report but without a template: --report=[nuLURtedb jects 92 Command-line options3.74 RTA-RTE V6.2.0 Reference Manual --rte rvncomoocune | ETAS Description: Name: Parameter: Default: Select “RTE” generation phase to generate an RTE for the specified ECU name. sorte This option takes a single parameter, that specifies the ECU instance or the ECU configuration (ECUC value collection in R4.0) for which RTE generation should occur. The System element must be referenced from the ECU configuration. For R4.0 the parameter can be “auto” which causes the RTE generator to search for and use the single EcucValueCol lection present in the input. NA The ECU instance must be specified using an absolute in- stance reference. (See Section 4.2.4.) To enable RTE generation for /pkg/ecu: ~-rte=/pkg/ecu To enable automatic search for the ECUC value collection and pro- cessing of the ECU extract (R4.0 only): --rte=auto Command-line options 93.RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.75 --samples Description: Enable creation of SWC skeleton files. Name: -samples Parameter: The --samples option takes a single parameter that specifies the samples required. swe : Create skeleton code files consisting of empty runnable-entity bodies for each runnable in the SWC. The generated files are named Rte_.c where is the SWC name. memmap : Create skeletons of SWC-specitic memory-mapping files. The generated files are named _MenMap.h where is the SWC name. Default None Generated samples overwrite existing files with the same name. ‘The generated samples are intended to be examples only, and should be adapted for the application and target hardware before use, Example: —_To enable sample generation for SWCs: --samples=swe 94 Command-line options3.76 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --strict-config-check Description: Enable RTE validation of input OS configuration, strict-config-check Parameter: This option takes a single parameter,

, that specifies whether to enable (‘on’ or ‘weak’) or disable (‘off’) the strict configuration checks. Default: Disable check. Note: RTA-RTE supports the AUTOSAR strict configuration check: when en- abled the RTE configuration must not require any OS objects that are not already present in the input configuration. For example, all Tunnables must be mapped to existing tasks and, if necessary, use pre-declared OsEvents and ScheduleTable/alarms for triggering. RTA-RTE also supports “weak” configuration checks — this changes the reported error to a warning, allowing the build to continue. Example: To enable strict configuration checks: --strict-config-check-on Command-line options 95RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.77 --strict-initial-values-check Description: Enable RTE validation of input OS configuration, Name: -strict-initial-values-check Parameter: This option takes a single parameter,

, that specifies the behavior when an uninitialized calprm is encountered. 1. info: to output an informational message 2. war: to output a warning message 3. error: to output an error message 4. none: to disable the detection of uninitialized calprms Default Error. Notes: Example: —_To reduce the severity of an uninitialized calprm to a warning: -strict-initial-values-check=warn 96 Command-line options3.78 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --strict-unconnected-rport-check Description: Parameter: Default: Example: Permit unconnected RPorts. strict-unconnected-rport-check This option takes one argument with the value ‘off’, ‘warn’ or ‘error’, which specifies what RTA-RTE should do when it detects an unconnected R-Port. If the option is not specified, it is an error to have unconnected R- Ports This is the AUTOSAR external configuration —_switch strictUnconnectedRPortCheck. To allow RTA-RTE to accept an input model having unconnected re- quire ports: --strict-unconnected-rport-check=off To enable the check for unconnected RPorts and raise a warning when such a port is encountered --strict-unconnected- rport-check=warn Command-line options 97RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.79 --sws Description: Selection of backend processor. Name: -sws. Parameter: The parameter specifies the appropriate AUTOSAR release. Default If this option is not specified then RTA-RTE examines the input XML for an XML namespace and selects the appropriate backend proces- sor automatically. Note: The --sws option bypasses the namespace check and explicitly se- lects the backend processor. The set of valid parameter values de- pends on the installed backend processors; use the --help option for the RTA-RTE frontend to show the valid list. To explicitly select the R4.0 backend processor: 8 /\ When explicitly selecting the backend processor ensure that the input XML is conformant to the selected AU- TOSAR release. 98 Command-line options3.80 RTA-RTE V6.2.0 ETAS Reference Manual --task-recurrence Description: Parameter: Default: Notes: Example: Set the recurrence for externally activated periodic tasks. task- recurrence This option takes a single parameter that specifies the task/OsEvent name and the recurrence rate in seconds as a task .event=seconds” pair. The specification of an OsEvent name is optional: if omitted the recurrence rate applies to activations of the task. Time values are specified in seconds with a period as the decimal separator. Create OS alarms and/or schedule table entries (or use existing ones) to implement periodic RTE events. This option disables RTA-RTE’s generation of OS alarms and/or schedule table entries for periodic events. Instead RTA-RTE uses the specified task recurrences to both derive internal scaling for gener- ated code (e.g. to map an RTE event with 20ms period to a task with an explicit recurrence of 10ms) and to validate the mapping to de- tect erroneous cases (e.g. mapping an RTE event with period 10ms toa task with an explicit recurrence of 20ms).. When this option is used for any task then it must be A used to specify recurrence rates for all tasks with periodic events since it disables RTA-RTE’s support for generating OS mechanisms to activate periodic events. This option can be specified many times to provide recurrence rates for multiple tasks. Alternatively the parameter can be specified as a comma-separated list of task name/rate pairs. To specify a recurrence rate of 20ms for taskA: --task-recurrence taskA=0.02 To specify a recurrence rate of 10ms for OsEvent ev1: --task-recurrence TaskA.ev1=0.01 Command-line options 993.81 RTA-RTE V6.2.0 ETAS Reference Manual --template-path Description: Parameter: Default Note: Example: Selection location of RTE library templates. -template-path This option takes a single parameter which _ speci fies the folder containing RTE library files. A If a relative path is used, it is interpreted relative to the RTA-RTE application executable. Specified within RTE configuration INI file. if the template path is specified both in the INI configuration file and on the command-line the latter takes precedence. None To select project-specific templates located in folderA: -template-path=foldera 100 Command-line optionsRTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS 3.82 --test-license Description: Display RTE license information Name: test-License Parameter: None Default: NA Note: Perform a license check and display the result. Example: —_To test the license in use: s --test-license Command-line options 1013.83 RTA-RTE V6.2.0 Reference Manual TAS m ~-text-value-spec-policy Description: Name: Parameter: Default: Notes: Example: Adjust whether RTE writes symbols or numeric values for TextValueSpecs --text-value-spec-policy compumethod-resolution TextValueSpec.value is interpreted as a physical quantity to be looked up in a corresponding ‘TEXTTABLE or BITFIELD. TEXTTABLE CompuMethod. The numer- ical equivalent is written to the generated code. If the value cannot be found RTA-RTE rejects the configuration with an er ror. symbolic-pdav-always When used in a PortDefinedArgumentValue, TextValueSpec.value is treated as a symbol that is to be copied directly into the gener ated code. Compile-time definitions must be provided when compiling Rte. c. compumethod- resolution NIA - text -value-spec-policy=symbolic-pdav-always 102 Command-line options3.84 RTA-RTE V6.2.0 ETAS Reference Manual --toolchain-significant-len Description: Parameter: Default: Example: Specify number of significant characters in toolchain identifiers. toolchain-significant-Len This option takes a single parameter,

, that specifies the number of significant characters. 31 Indicates to the RTE generator the number of significant charac- ters checked by the toolchain. The RTE generator will then issue a warning if multiple RTE generated identifiers are not distinguishable within the specified number of characters. For RTE generation phase, this option can be set both in the ECUC file and on the command-line. If specified in both places then RTA-RTE will use the command-line value. To set the number of significant characters to 60: toolchain-significant -len=60 Command-line options 103RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.85 --use-partition-sections Description: Select whether or not partition-specific default memory sections should be used for partition-local objects without a section specified exoli Name: -use-partition-sections Parameter: This option takes a single parameter which enables (“on" or “1") or disables (“off" or “O") use of partition-specific memory sections by default for objects that are local to a partition and have no memory section specified. When enabled, the name of the EcuCPartition is used as the infix for the memory section name when one is config- ured, otherwise the name of the OsApplication is used. Disabled (“off”) for AUTOSAR compliance Notes: None. To enable the use of partition-specific default memory sections: -use-partition-sections=on 104 Command-line options3.86 RTA-RTE V6.2.0 Reference Manual rvncomoocune | ETAS --variability-also-bind Description: Add a BindingTime that RTA-RTE will also try to honor. Name: variability-also-bind Parameter: If used, this option must be given the parameter PRE-COMPILE-TIME which is the only supported value at this time. Default: Only instantiate variability with BindingTime CODE GENERATION - TIME Note: NA Example: --variability-also-bind=PRE-COMPILE-TIME Command-line options 105RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.87 --version Description: Display RTE generator version. Name: -version Parameter: None Default N/A Print the RTA-RTE product and RTE generator version information on the standard output. Example: To display the RTA-RTE version: --version 106 Command-line optionsRTA-RTE V6.2.0 ETAS Reference Manual VG EMBEDDED EXCELLENCE 3 3.88 --vfb-trace Description: Globally enable (or disable) the creation of VFB trace hooks in the generated RTE. Name: --vfb-trace Parameter: This option takes a single parameter that specifies whether gener- ation of hook functions is enabled (“on” or “1") or disabled (“off” or “0"), Default: Enabled (“on”) For the RTE generation phase, this option can be set both in the ECUC file and on the command-line. If specified in both places then RTA-RTE will use the command-line value. To disable VFB trace hook generation from the command-lin --vfb-trace=off Command-line options 107RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3 3.89 --warn-directive Description: Set the name (excluding the ‘#') of the C pre-processor directive used to issue warnings. Name: --warn-directive Parameter: The option takes a single parameter, , that specifies the direc- tive name. Defaul #pragma message Note: None. Example: —_To select #warn as the warning directive used in generated RTE code: -warn-directive=warn 108 Command-line options3.90 RTA-RTE V6.2.0 ETAS Reference Manual ~-warning-as-error Description: Parameter: Default: Set whether wamings are treated as errors. warning-as-error The option takes a single parameter that specifies whether to enable (‘1’) o disable (‘0’) treatment of warnings as errors. Treat warnings as warnings ('0") When enabled RTE treats any warning as an error and raises the error level appropriately. Note that the warning message text itself is not changed and thus may still refer to the error as a “warning”, Note: If you wish to use this option along with --disable-warning then you must turn the specific message back to a waming using --error-as-warning. To treat all warnings as errors but continue suppressing warning w17-1023 ‘warning-as-error=1 --error-as-warning=E17-1023 disable-warning=W17-1023 Command-line options 109RTA-RTE V6.2.0 ETAS Reference Manual >a VING EMBEDED EXCELLENCE 3.91 --xmlentity Description: Add the specified XML schema to the XML entity resolver. Name: -xmilentity Parameter: This option takes a single parameter, [], that speci- fies the system identifier and path to the schema file. The path can be absolute or relative to the folder in which the RTE generator is run NA By default, RTA-RTE uses the XML namespace to identify the XSD used for validation of the file, To support this RTA-RTE includes XSD caching to reduce load by reusing read schemas. In some circum- stances this approach may not be desired. For example, the R4.0 schemas use identical namespaces and therefore cannot be distin- guished from each other. The --xmLentity option enables an asso- ciation to be made between a system identifier () anda path to the associated schema. When RTA-RTE encounters a schemaLocation attribute in an XML file with a system identifier it uses the set of and path associa- tions to attempt to map the identifier to a path. If this is successful, the schema is read from the specified path rather than from the file specified by the schemaLocat ion attribute. When using the - -xmlentity option it is recommended that schema caching is disabled (see the --xmlschema option below). Doing this allows schemas with the same namespace but different system iden- tifiers to be resolved to different files. Example: Consider an XML file with schemaLocat ion attribute: xsi:schemaLocation="http://autosar.org/schema/r4.® AUTOSAR 4-0-1.xsd” ‘To map AUTOSAR 4-0-1.xsd to a specific file use: -xmlentit AUTOSAR_4-0-1.xsd]c:\schemas\ar401.xsd 110 Command-line options