Main Content

AUTOSAR Component Behavior

Configure runnable entities, events, and inter-runnable variables

The internal behavior of an AUTOSAR software component is implemented by a set of runnable entities (runnables). A runnable is a sequence of operations provided by the component that can be started by the AUTOSAR run-time environment. The component configures an event to activate each runnable – for example, a timing event, data received, a client request, a mode change, component startup or shutdown, or a trigger. Runnables can be interconnected using AUTOSAR inter-runnable variables (IRVs).

To configure an AUTOSAR runnable, create or identify a root-level Simulink® subsystem or function that implements a sequence of operations. The subsystem or function must generate an entry-point function in C code. Then create an AUTOSAR runnable, and map the Simulink entry-point function to the AUTOSAR runnable. Use the AUTOSAR Dictionary and the Code Mappings editor or equivalent AUTOSAR property and map functions.

The steps to create an event that activates a runnable depend on the type of event. If the event relies on a communication interface, such as data received (sender-receiver) or client request (client-server), you must first configure the communication interface before configuring the event.

Functions

addSignalAdd Simulink block signal to AUTOSAR mapping
getDataStoreGet AUTOSAR mapping information for Simulink data store
getDataTransferGet AUTOSAR mapping information for Simulink data transfer
getFunctionGet AUTOSAR mapping information for Simulink entry-point function
getFunctionCallerGet AUTOSAR mapping information for Simulink function-caller block
getParameterGet AUTOSAR mapping information for Simulink model workspace parameter
getSignalGet AUTOSAR mapping information for Simulink block signal
getStateGet AUTOSAR mapping information for Simulink block state
mapDataStoreMap Simulink data store to AUTOSAR variable
mapDataTransferMap Simulink data transfer to AUTOSAR inter-runnable variable
mapFunctionMap Simulink entry-point function to AUTOSAR runnable and software address methods
mapFunctionCallerMap Simulink function-caller block to AUTOSAR client port and operation
mapParameterMap Simulink model workspace parameter to AUTOSAR component parameter
mapSignalMap Simulink block signal to AUTOSAR variable
mapStateMap Simulink block state to AUTOSAR variable
removeSignalRemove Simulink block signal from AUTOSAR mapping

Topics

Configure AUTOSAR Runnables and Events

Configure AUTOSAR runnable entities and their activation events.

Configure AUTOSAR Runnable Execution Order

Use the Schedule Editor to schedule and specify the execution order of AUTOSAR runnables.

Configure AUTOSAR Initialize, Reset, or Terminate Runnables

Configure AUTOSAR system startup, reset, and shutdown sequences.

Add Top-Level Asynchronous Trigger to Periodic Rate-Based System

Combine asynchronous and periodic AUTOSAR runnables (JMAAB type beta compliant).

Configure AUTOSAR Initialization Runnable (R4.1)

Use AUTOSAR initialization event (InitEvent) for lightweight activation of an initialization runnable.

Configure Disabled Mode for AUTOSAR Runnable Event

Modify DisabledMode property to disable AUTOSAR event for specific modes.

Configure Internal Data Types for AUTOSAR IncludedDataTypeSets

Export component model internal data types in AUTOSAR included data type sets (IncludedDataTypeSets), which other software components can import.

Configure AUTOSAR Per-Instance Memory

Configure AUTOSAR per-instance memory (PIM) by using block signals, discrete states, or data store memory.

Configure AUTOSAR Static Memory

Configure AUTOSAR static memory by using block signals, discrete states, or data store memory.

Configure AUTOSAR Constant Memory

Configure AUTOSAR constant memory by using model workspace parameters.

Configure AUTOSAR Shared or Per-Instance Parameters

Configure AUTOSAR shared or per-instance parameters by using model workspace parameters.

Configure AUTOSAR Port Parameters for Communication with Parameter Component

Configure AUTOSAR parameter receiver component for port-based access to parameter data.