AUTOSAR Software Components

Configure component properties, map Simulink elements to AUTOSAR elements, configure element packages, apply modeling checks

An AUTOSAR application is modeled by interconnected software components. Each software component encapsulates a functional implementation of automotive behavior, with well-defined connection points to the outside world.

To develop an AUTOSAR software component in Simulink^®, you create an initial representation of an AUTOSAR component, as described in Component Creation. The resulting representation includes:

Simulink blocks, connections, and data that model AUTOSAR elements such as ports, runnables, inter-runnable variables, and parameters.
Stored properties, defined in the AUTOSAR standard, for AUTOSAR elements in the software component.
A mapping of Simulink elements to AUTOSAR elements.

Use the Code Mappings editor and the AUTOSAR Dictionary to begin refining and developing the component. The Code Mappings editor provides a Simulink perspective of the component, in which you selectively map Simulink elements to AUTOSAR elements. The AUTOSAR Dictionary provides an AUTOSAR perspective of the component, in which you configure AUTOSAR elements and their properties. To get started, see AUTOSAR Component Configuration.

Tools

Code Mappings Editor

Map AUTOSAR elements for code generation

Functions

expand all

Simulink to AUTOSAR Mapping

`autosar.api.getSimulinkMapping`	Map Simulink elements to AUTOSAR elements
`addSignal`	Add Simulink block signal to AUTOSAR mapping
`getDataStore`	Get AUTOSAR mapping information for Simulink data store
`getDataTransfer`	Get AUTOSAR mapping information for Simulink data transfer
`getFunction`	Get AUTOSAR mapping information for Simulink entry-point function
`getFunctionCaller`	Get AUTOSAR mapping information for Simulink function-caller block
`getInport`	Get AUTOSAR mapping information for Simulink inport
`getInternalDataPackaging`	Get default internal data packaging for AUTOSAR component model
`getOutport`	Get AUTOSAR mapping information for Simulink outport
`getParameter`	Get AUTOSAR mapping information for Simulink model workspace parameter
`getSignal`	Get AUTOSAR mapping information for Simulink block signal
`getState`	Get AUTOSAR mapping information for Simulink block state
`mapDataStore`	Map Simulink data store to AUTOSAR variable
`mapDataTransfer`	Map Simulink data transfer to AUTOSAR inter-runnable variable
`mapFunction`	Map Simulink entry-point function to AUTOSAR runnable and software address methods
`mapFunctionCaller`	Map Simulink function-caller block to AUTOSAR client port and operation
`mapInport`	Map Simulink inport to AUTOSAR port
`mapOutport`	Map Simulink outport to AUTOSAR port
`mapParameter`	Map Simulink model workspace parameter to AUTOSAR component parameter
`mapSignal`	Map Simulink block signal to AUTOSAR variable
`mapState`	Map Simulink block state to AUTOSAR variable
`removeSignal`	Remove Simulink block signal from AUTOSAR mapping
`setInternalDataPackaging`	Set default internal data packaging for AUTOSAR component model

AUTOSAR Properties

`autosar.api.getAUTOSARProperties`	Configure AUTOSAR software component elements and properties
`add`	Add property to AUTOSAR element
`addPackageableElement`	Add element to AUTOSAR package in model
`createEnumeration`	Create Simulink enumeration data type definition to work with imported AUTOSAR element
`createNumericType`	Create Simulink numeric data type definition to work with imported AUTOSAR element
`delete`	Delete AUTOSAR element
`deleteUnmappedComponents`	Delete unmapped AUTOSAR components from model
`find`	Find AUTOSAR elements
`get`	Get property of AUTOSAR element
`set`	Set property of AUTOSAR element

AUTOSAR Component Configuration

`autosar.api.create`	Create or update mapped AUTOSAR component model
`autosar.api.delete`	Delete AUTOSAR properties and mapping for Simulink model
`autosar.api.syncModel`	Update Simulink to AUTOSAR mapping of model with Simulink modifications
`autosar.api.validateModel`	Validate AUTOSAR properties and mapping of Simulink model
`autosar_ui_launch`	Open AUTOSAR Dictionary dialog box
`autosar_ui_close`	Close AUTOSAR Dictionary dialog box
`updateAUTOSARProperties`	Update model with ARXML definitions of AUTOSAR elements
`updateModel`	Update AUTOSAR model with ARXML changes

Topics

AUTOSAR Component Configuration

Configure AUTOSAR software component properties and mapping between Simulink and AUTOSAR elements.

Map AUTOSAR Elements for Code Generation

Use Code Mappings editor to view and map AUTOSAR software component from Simulink perspective.

Map Calibration Data for Submodels Referenced from AUTOSAR Component Models

Use Code Mappings editor to view and map internal data for submodels referenced from AUTOSAR components.

Configure AUTOSAR Elements and Properties

Use AUTOSAR Dictionary to view and configure AUTOSAR software component elements and properties.

Incrementally Update AUTOSAR Mapping After Model Changes

Incrementally auto-configure and map new Simulink elements in AUTOSAR model.

Design and Simulate AUTOSAR Components and Generate Code

Develop AUTOSAR components by implementing behavior algorithms, simulating components and compositions, and generating component code.

Configure AUTOSAR Packages

Import or define element packages within hierarchical AUTOSAR package structure.

Configure AUTOSAR Package for Component, Interface, CompuMethod, or SwAddrMethod

Enter package path in component, interface, CompuMethod, or SwAddrMethod view in AUTOSAR Dictionary.

AUTOSAR Blockset Checks

Describes Model Advisor checks for AUTOSAR Blockset.

Limitations and Tips

Limitations that apply to AUTOSAR component development.