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.
|Signal Invalidation||Control AUTOSAR root outport data element invalidation|
|Get AUTOSAR mapping information for Simulink entry-point function|
|Get AUTOSAR mapping information for Simulink function-caller block|
|Get AUTOSAR mapping information for Simulink inport|
|Get AUTOSAR mapping information for Simulink outport|
|Map Simulink entry-point function to AUTOSAR runnable and software address methods|
|Map Simulink function-caller block to AUTOSAR client port and operation|
|Map Simulink inport to AUTOSAR port|
|Map Simulink outport to AUTOSAR port|
|Determine when a message queue overflows|
Read and write AUTOSAR data by using port-based sender-receiver communication.
Read and write queued AUTOSAR data by using port-based sender-receiver communication.
Model AUTOSAR ports by using Simulink In Bus Element and Out Bus Element blocks.
Implement AUTOSAR client and server runnables with Simulink Function and Function Caller blocks.
Define AUTOSAR modes and mode elements to activate runnables in response to system mode changes.
Read and write AUTOSAR nonvolatile (NV) data by using port-based NV data communication.
Configure AUTOSAR parameter receiver component for port-based access to parameter data.
Define trigger interface that activates AUTOSAR runnables in response to external trigger events.