AUTOSAR Communication

Configure communication ports and interfaces

The communication interface of an AUTOSAR software-component consists of well-defined ports. An AUTOSAR component communicates through its ports with other AUTOSAR software components or Basic Software (BSW) services. A port provides information to, or requires information from, its communication partners. Each port owned by the component maps to a communication interface, based on the component functional requirements, for example:

Sender-receiver (S-R) interface, for message passing
Client-server (C-S) interface, for function invocation
Mode-switch (M-S) interface, for managing mode-based execution
Nonvolatile (NV) data interface, for port-based access to NV data
Parameter interface, for port-based access to parameter data
Trigger interface, for managing trigger-based execution

To configure AUTOSAR communication for a component port, you create an AUTOSAR interface, map the port to the interface, and map Simulink^® elements, such as a root inport or outport, to the AUTOSAR port, as required by the type of interface. Use the AUTOSAR Dictionary and the Code Mappings editor or equivalent AUTOSAR property and map functions.

Blocks

Signal Invalidation

Control AUTOSAR root outport data element invalidation

Functions

`getDataDefaults`	Get default end-to-end (E2E) protection method for AUTOSAR component model
`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
`getOutport`	Get AUTOSAR mapping information for Simulink outport
`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
`overflowed`	Determine when a message queue overflows
`setDataDefaults`	Set default end-to-end (E2E) protection method for AUTOSAR component model

Topics

Configure AUTOSAR Sender-Receiver Communication
Read and write AUTOSAR data by using port-based sender-receiver communication.
Configure AUTOSAR Queued Sender-Receiver Communication
Read and write queued AUTOSAR data by using port-based sender-receiver communication.
Configure AUTOSAR Ports By Using Simulink Bus Ports
Model AUTOSAR ports by using Simulink In Bus Element and Out Bus Element blocks.
Configure AUTOSAR Client-Server Communication
Implement AUTOSAR client and server runnables with Simulink Function and Function Caller blocks.
Configure AUTOSAR Mode-Switch Communication
Define AUTOSAR modes and mode elements to activate runnables in response to system mode changes.
Configure AUTOSAR Nonvolatile Data Communication
Read and write AUTOSAR nonvolatile (NV) data by using port-based NV data communication.
Configure AUTOSAR Port Parameters for Communication with Parameter Component
Configure AUTOSAR parameter receiver component for port-based access to parameter data.
Configure Receiver for AUTOSAR External Trigger Event Communication
Define trigger interface that activates AUTOSAR runnables in response to external trigger events.