Configure AUTOSAR Adaptive XML Options
R2026bTo configure AUTOSAR adaptive XML options for ARXML export, open a model for which a mapped AUTOSAR Adaptive software component has been created and open the AUTOSAR Dictionary. Select XML Options.
The XML options view in the AUTOSAR Dictionary displays configuration options for exported ARXML files. You can configure:
ARXML file packaging for AUTOSAR elements created in Simulink®
AUTOSAR package paths
Whether to allow implementation data type references
Default values for SwCalibrationAccess
Whether to export internal data constraints

Exported XML File Packaging
In the XML options view, you can specify the granularity of XML file packaging for AUTOSAR elements created in Simulink. Imported AUTOSAR XML files retain their file structure, as described in Round-Trip Preservation of AUTOSAR XML File Structure and Element Information. Select one of the following values for Exported XML file packaging.
Single file— Exports XML into a single file,.modelname.arxmlModular— Exports XML into multiple files, named according to the type of information contained.Exported File Name File Contents modelname_component.arxmlAdaptive software components, including required and provided ports.
This file is the main ARXML file exported for the Simulink model. In addition to software components, the component file contains packageable elements that the exporter does not move to data type or interface files based on AUTOSAR element category.
modelname_datatype.arxmlData types and related elements, including:
Application data types
Standard Cpp implementation data types
Constant specifications
Physical data constraints
Units and unit groups
Software record layouts
modelname_interface.arxmlAdaptive interfaces, including required and provided service interfaces with namespaces, events, and methods.
Alternatively, you can programmatically configure exported XML file packaging by
calling the AUTOSAR set function. For property
ArxmlFilePackaging, specify either
"SingleFile" or "Modular". For
example:
arProps = autosar.api.getAUTOSARProperties(hModel); set(arProps,"XmlOptions",ArxmlFilePackaging="SingleFile");
Note
The autosar.api.getAUTOSARProperties function is not
supported for AUTOSAR Adaptive models created or upgraded in R2026b. For these
models, use the AUTOSAR Dictionary to configure XML options.
For the Adaptive Platform, model builds also generate XML manifests for AUTOSAR executables and service instances. For more information, see Generate AUTOSAR Adaptive C++ and ARXML Files.
AUTOSAR Package Paths
In the XML options view, you can configure AUTOSAR packages (AR-PACKAGEs), which contain groups of AUTOSAR elements and reside in a hierarchical AR-PACKAGE structure. The AR-PACKAGE structure for a component is logically distinct from the ARXML file partitioning selected with the XML option Exported XML file packaging or imported from AUTOSAR XML files. For more information about AUTOSAR packages, see Configure AUTOSAR Packages.
Inspect and modify the AUTOSAR package paths grouped under the headings Package Paths and Additional Packages.
Alternatively, you can programmatically configure an AUTOSAR package path by
calling the AUTOSAR set function. Specify a package property
name and a package path. For example:
arProps = autosar.api.getAUTOSARProperties(hModel); set(arProps,"XmlOptions","ApplicationDataTypePackage",... '/Company/Powertrain/DataTypes/ApplDataTypes');
For more information about AUTOSAR package property names and defaults, see Configure AUTOSAR Packages and Paths.
Additional XML Options
In the XML options view, under the heading Additional Options, you can configure aspects of exported AUTOSAR XML content.

You can:
Optionally override the default behavior for generating AUTOSAR application data types in ARXML code. To force generation of an application data type for each AUTOSAR data type, change the value of ImplementationDataType Reference from
AllowedtoNotAllowed.Control the default value of the SwCalibrationAccess property of generated AUTOSAR measurement variables, calibration parameters, and signal and parameter data objects. For SwCalibrationAccess DefaultValue, select one of the following values:
ReadOnly— Read access only.ReadWrite(default) — Read and write access.NotAccessible— Not accessible with calibration and measurement tools.
Optionally override the default behavior for generating internal data constraint information for AUTOSAR implementation data types in ARXML code. To force export of internal data constraints for implementation data types, select the option Internal DataConstraints Export.
Alternatively, you can programmatically configure the additional XML options by
calling the AUTOSAR set function. Specify a property name and
value. The valid property names are ImplementationTypeReference,
SwCalibrationAccessDefault,
InternalDataConstraintExport,
IdentifyServiceInstance, and
NetworkBinding. For example:
arProps = autosar.api.getAUTOSARProperties(hModel); set(arProps,"XmlOptions","ImplementationTypeReference","NotAllowed"); set(arProps,"XmlOptions","SwCalibrationAccessDefault","ReadOnly"); set(arProps,"XmlOptions","InternalDataConstraintExport",true);
See Also
autosar.api.getAUTOSARProperties
Topics
- Model AUTOSAR Adaptive Software Components
- Create AUTOSAR Software Component in Simulink
- Configure AUTOSAR Adaptive Service Interface Properties
- Model AUTOSAR Adaptive Service Communication and Execution Behavior
- Configure AUTOSAR Adaptive Code Generation
- Comparison of AUTOSAR Classic and Adaptive Platforms