AUTOSAR Blockset User's Guide

Overview of AUTOSAR Support
	AUTOSAR Blockset Product Description
	AUTOSAR Standard
	Comparison of AUTOSAR Classic and Adaptive Platforms
		Classic Platform
		Adaptive Platform
	AUTOSAR Software Components and Compositions
	Workflows for AUTOSAR
		Simulink Originated (Bottom-Up) Workflow
		Round-Trip Workflow
	AUTOSAR Workflow Samples
	Develop AUTOSAR Software Component Model
		Prerequisites
		Example Model
		What You Will Learn
	Create Algorithmic Model Content That Represents AUTOSAR Software Component Behavior
	Configure Elements of AUTOSAR Software Component for Simulink Modeling Environment
		Set Up Initial Component Configuration
		Customize Component Configuration
		Configure AUTOSAR Software Component Elements from AUTOSAR Standard Perspective
	Simulate AUTOSAR Software Component
	Optional: Generate AUTOSAR Software Component Code (Requires Embedded Coder)
	Develop AUTOSAR Adaptive Software Component Model
		Prerequisites
		Example Model
		What You Will Learn
	Create Algorithmic Model Content That Represents AUTOSAR Adaptive Software Component Behavior
	Configure Elements of AUTOSAR Adaptive Software Component for Simulink Modeling Environment
		Set Up an Initial Component Configuration
		Customize Component Configuration
		Configure AUTOSAR Adaptive Software Component Elements from AUTOSAR Standard Perspective
	Simulate AUTOSAR Adaptive Software Component
	Optional: Generate AUTOSAR Adaptive Software Component Code (Requires Embedded Coder)
	Develop AUTOSAR Software Architecture Model
		Prerequisites
		Example Model
		What You Will Learn
	Create AUTOSAR Software Architecture Model
	Add AUTOSAR Compositions and Components and Link Component Implementations
		Add Compositions and Components to Architecture Canvas
		Define Component Behavior by Linking Implementation Models
		Complete Architecture Model Top Level
	Simulate Components in AUTOSAR Architecture
	Optional: Generate and Package Composition ARXML and Component Code (Requires Embedded Coder)
Modeling Patterns for AUTOSAR Components
	Simulink Modeling Patterns for AUTOSAR
	Model AUTOSAR Software Components
		About AUTOSAR Software Components
		Implementation Considerations
		Rate-Based Components
		Function-Call Based Components
		Multi-Instance Components
		Startup, Reset, and Shutdown
	Modeling Patterns for AUTOSAR Runnables
	Model AUTOSAR Runnables Using Exported Functions
	Model AUTOSAR Communication
		About AUTOSAR Communication
		Sender-Receiver Interface
		Queued Sender-Receiver Interface
		Client-Server Interface
		Mode-Switch Interface
		Nonvolatile Data Interface
		Parameter Interface
		Trigger Interface
	Model AUTOSAR Component Behavior
		AUTOSAR Elements for Modeling Component Behavior
		Runnables
		Inter-Runnable Variables
		Included Data Type Sets
		System Constants
		Per-Instance Memory
		Static and Constant Memory
		Shared and Per-Instance Parameters
		Port Parameters
	Model AUTOSAR Variants
		Variants for Ports and Runnables
		Variants for Runnable Implementations
		Variants for Array Sizes
		Predefined Variants and System Constant Value Sets
	Model AUTOSAR Nonvolatile Memory
		Implicit Access to AUTOSAR Nonvolatile Memory
		Explicit Access to AUTOSAR Nonvolatile Memory
	Model AUTOSAR Data Types
		About AUTOSAR Data Types
		Enumerated Data Types
		Structure Parameters
		Data Types
		CompuMethod Categories for Data Types
	Model AUTOSAR Calibration Parameters and Lookup Tables
		AUTOSAR Calibration Parameters
		Calibration Parameters for STD_AXIS, FIX_AXIS, and COM_AXIS Lookup Tables
AUTOSAR Component Creation
	Create AUTOSAR Software Component in Simulink
		Create Mapped AUTOSAR Component with Quick Start
		Create Mapped AUTOSAR Component with Simulink Start Page
	Create and Configure AUTOSAR Software Component
	Import AUTOSAR XML Descriptions Into Simulink
		Create ARXML Importer Object
		Import Software Component and Create Model
		Import Software Composition and Create Models
		Import Component or Composition External Updates Into Model
		Import Shared Element Packages into Component Model
	Import AUTOSAR Software Component with Multiple Runnables
	Import AUTOSAR Component to Simulink
	Import AUTOSAR Software Composition with Atomic Software Components (Classic Platform)
	Import AUTOSAR Software Component Updates
		Update Model with AUTOSAR Software Component Changes
		AUTOSAR Update Report Section Examples
	Import and Reference Shared AUTOSAR Element Definitions
	Import AUTOSAR Package into Component Model
	AUTOSAR ARXML Importer
	Round-Trip Preservation of AUTOSAR XML File Structure and Element Information
	Limitations and Tips
		Cannot Save Importer Objects in MAT-Files
		ApplicationRecordDataType and ImplementationDataType Element Names Must Match
AUTOSAR Component Development
	AUTOSAR Component Configuration
	Configure AUTOSAR Elements and Properties
		AUTOSAR Elements Configuration Workflow
		Configure AUTOSAR Atomic Software Components
		Configure AUTOSAR Ports
		Configure AUTOSAR Runnables
		Configure AUTOSAR Inter-Runnable Variables
		Configure AUTOSAR Parameters
		Configure AUTOSAR Communication Interfaces
		Configure AUTOSAR Computation Methods
		Configure AUTOSAR SwAddrMethods
		Configure AUTOSAR XML Options
	Map AUTOSAR Elements for Code Generation
		Simulink to AUTOSAR Mapping Workflow
		Map Entry-Point Functions to AUTOSAR Runnables
		Map Inports and Outports to AUTOSAR Sender-Receiver Ports and Data Elements
		Map Model Workspace Parameters to AUTOSAR Component Parameters
		Map Data Stores to AUTOSAR Variables
		Map Block Signals and States to AUTOSAR Variables
		Map Data Transfers to AUTOSAR Inter-Runnable Variables
		Map Function Callers to AUTOSAR Client-Server Ports and Operations
		Specify C Type Qualifiers for AUTOSAR Static and Constant Memory
		Specify Default Data Packaging for AUTOSAR Internal Variables
	Map Calibration Data for Submodels Referenced from AUTOSAR Component Models
		Submodel Data Mapping Workflow
		Map Submodel Parameters to AUTOSAR Component Parameters
		Map Submodel Data Stores to AUTOSAR Variables
		Map Submodel Signals and States to AUTOSAR Variables
		Generate Submodel Data Macros for Verification and Deployment
	Incrementally Update AUTOSAR Mapping After Model Changes
	Design and Simulate AUTOSAR Components and Generate Code
	Configure AUTOSAR Packages
		AR-PACKAGE Structure
		Configure AUTOSAR Packages and Paths
		Control AUTOSAR Elements Affected by Package Path Modifications
		Export AUTOSAR Packages
		AR-PACKAGE Location in Exported ARXML Files
	Configure AUTOSAR Package for Component, Interface, CompuMethod, or SwAddrMethod
	Configure AUTOSAR Sender-Receiver Communication
		Configure AUTOSAR Sender-Receiver Interface
		Configure AUTOSAR Provide-Require Port
		Configure AUTOSAR Receiver Port for IsUpdated Service
		Configure AUTOSAR Sender-Receiver Data Invalidation
		Configure AUTOSAR S-R Interface Port for End-To-End Protection
		Configure AUTOSAR Receiver Port for DataReceiveErrorEvent
		Configure AUTOSAR Sender-Receiver Port ComSpecs
	Configure AUTOSAR Queued Sender-Receiver Communication
		Simulink Workflow for Modeling AUTOSAR Queued Send and Receive
		Configure AUTOSAR Sender and Receiver Components for Queued Communication
		Implement AUTOSAR Queued Send and Receive Messaging
		Configure Simulation of AUTOSAR Queued Sender-Receiver Communication
		Simulate N-to-1 AUTOSAR Queued Sender-Receiver Communication
		Simulate Event-Driven AUTOSAR Queued Sender-Receiver Communication
		Implement AUTOSAR Queued Send and Receive By Using Stateflow Messaging
	Configure AUTOSAR Ports By Using Simulink Bus Ports
		Model AUTOSAR Ports By Configuring Simulink Bus Ports
		Model AUTOSAR Interfaces By Typing Bus Ports with Bus Objects
	Configure AUTOSAR Client-Server Communication
		Configure AUTOSAR Server
		Configure AUTOSAR Client
		Configure AUTOSAR Client-Server Error Handling
		Concurrency Constraints for AUTOSAR Server Runnables
		Configure and Map AUTOSAR Server and Client Programmatically
	Configure AUTOSAR Mode-Switch Communication
		Configure Mode Receiver Port and Mode-Switch Event for Mode User
		Configure Mode Sender Port and Mode Switch Point for Application Mode Manager
	Configure AUTOSAR Nonvolatile Data Communication
	Configure AUTOSAR Port Parameters for Communication with Parameter Component
	Configure Receiver for AUTOSAR External Trigger Event Communication
	Configure AUTOSAR Runnables and Events
	Configure AUTOSAR Runnable Execution Order
	Configure AUTOSAR Initialize, Reset, or Terminate Runnables
	Add Top-Level Asynchronous Trigger to Periodic Rate-Based System
	Configure AUTOSAR Initialization Runnable (R4.1)
	Configure Disabled Mode for AUTOSAR Runnable Event
	Configure Internal Data Types for AUTOSAR IncludedDataTypeSets
	Configure AUTOSAR Per-Instance Memory
		Configure Block Signals and States as AUTOSAR Typed Per-Instance Memory
		Configure Data Stores as AUTOSAR Typed Per-Instance Memory
		Configure Data Stores to Preserve State Information at Startup and Shutdown
	Configure AUTOSAR Static Memory
		Configure Block Signals and States as AUTOSAR Static Memory
		Configure Data Stores as AUTOSAR Static Memory
	Configure AUTOSAR Constant Memory
	Configure AUTOSAR Shared or Per-Instance Parameters
		Configure Model Workspace Parameters as AUTOSAR Shared Parameters
		Configure Model Workspace Parameters as AUTOSAR Per-Instance Parameters
	Configure Variants for AUTOSAR Ports and Runnables
	Configure Variants for AUTOSAR Runnable Implementations
	Export Variation Points for AUTOSAR Calibration Data
	Configure Dimension Variants for AUTOSAR Array Sizes
	Control AUTOSAR Variants with Predefined Value Combinations
	Configure Postbuild Variant Conditions for AUTOSAR Software Components
	Configure Variant Parameter Values for AUTOSAR Elements
		Specify Variant Parameters at Precompile Time
		Specify Variant Parameters at Postbuild Time
	Configure AUTOSAR CompuMethods
		Configure AUTOSAR CompuMethod Properties
		Create AUTOSAR CompuMethods
		Configure CompuMethod Direction for Linear Functions
		Export CompuMethod Unit References
		Modify Linear Scaling for SCALE_LINEAR_AND_TEXTTABLE CompuMethod
		Configure Rational Function CompuMethod for Dual-Scaled Parameter
	Configure AUTOSAR Data Types Export
		Control Application Data Type Generation
		Configure DataTypeMappingSet Package and Name
		Initialize Data with ApplicationValueSpecification
		Configure AUTOSAR Internal Data Constraints Export
	Automatic AUTOSAR Data Type Generation
	Configure Parameters and Signals for AUTOSAR Calibration and Measurement
	Configure Subcomponent Data for AUTOSAR Calibration and Measurement
	Configure AUTOSAR Data for Calibration and Measurement
		About Software Data Definition Properties (SwDataDefProps)
		Configure SwCalibrationAccess
		Configure DisplayFormat
		Configure SwAddrMethod
		Configure SwAlignment
		Export SwImplPolicy
		Export SwRecordLayout for Lookup Table Data
	Configure Lookup Tables for AUTOSAR Calibration and Measurement
		Configure STD_AXIS Lookup Tables by Using Lookup Table Objects
		Configure COM_AXIS Lookup Tables by Using Lookup Table and Breakpoint Objects
		Configure FIX_AXIS Lookup Tables by Using Simulink Parameter Objects
		Configure Array Layout for Multidimensional Lookup Tables
		Parameterizing Instances of Reusable Referenced Model Lookup Tables and Breakpoints
		Exporting Lookup Table Constants as Record Value Specification
		Exporting AdminData Record Layout Annotations
	Configure and Map AUTOSAR Component Programmatically
		AUTOSAR Property and Map Functions
		Tree View of AUTOSAR Configuration
		Properties of AUTOSAR Elements
		Specify AUTOSAR Element Location
	AUTOSAR Property and Map Function Examples
		Configure AUTOSAR Software Component
		Configure AUTOSAR Interfaces
		Configure AUTOSAR XML Export
	Limitations and Tips
		AUTOSAR Client Block in Referenced Model
AUTOSAR Code Generation
	Generate AUTOSAR C Code and XML Descriptions
	Configure AUTOSAR Code Generation
		Select AUTOSAR Classic Schema
		Specify Maximum SHORT-NAME Length
		Configure AUTOSAR Compiler Abstraction Macros
		Root-Level Matrix I/O
		Inspect AUTOSAR XML Options
		Generate AUTOSAR C and XML Files
	Code Generation with AUTOSAR Code Replacement Library
		Code Replacement Library for AUTOSAR Code Generation
		Find Supported AUTOSAR Library Routines
		Configure Code Generator to Use AUTOSAR 4.0 Code Replacement Library
		AUTOSAR 4.0 Library Host Code Verification
		Code Replacement Library Checks
		AUTOSAR Code Replacement Library Example for IFX/IFL Function Replacement
		Required Algorithm Property Settings for IFL/IFX Function and Block Mappings
	Verify AUTOSAR C Code with SIL and PIL
	Integrate Generated Code for Multi-Instance Software Components
	Import and Simulate AUTOSAR Code from Previous Releases
	Limitations and Tips
		Generate Code Only Check Box
		AUTOSAR Compiler Abstraction Macros (Classic Platform)
		Preservation of Bus Element Dimensions in Exported ARXML and Code
		C++11 Style Scoped Enum Classes Generated for AUTOSAR Adaptive Applications
AUTOSAR Adaptive Software Component Modeling
	Model AUTOSAR Adaptive Software Components
	Create and Configure AUTOSAR Adaptive Software Component
	Import AUTOSAR Adaptive Software Descriptions
	Import AUTOSAR Adaptive Components to Simulink
	Import AUTOSAR Package into Adaptive Component Model
	Configure AUTOSAR Adaptive Elements and Properties
		AUTOSAR Elements Configuration Workflow
		Configure AUTOSAR Adaptive Software Components
		Configure AUTOSAR Adaptive Service Interfaces and Ports
		Configure AUTOSAR Adaptive Persistent Memory Interfaces and Ports
		Configure AUTOSAR Adaptive XML Options
	Map AUTOSAR Adaptive Elements for Code Generation
		Simulink to AUTOSAR Mapping Workflow
		Map Inports and Outports to AUTOSAR Service Ports and Events
		Map Data Stores to AUTOSAR Persistent Memory Ports and Data Elements
	Configure AUTOSAR Adaptive Software Components
	Model AUTOSAR Adaptive Service Communication
		Model Client-Server Communication
	Configure Memory Allocation for AUTOSAR Adaptive Service Data
	Configure AUTOSAR Adaptive Service Discovery Modes
	Configure AUTOSAR Adaptive Service Instance Identification
	Model AUTOSAR Adaptive Persistent Memory
	Generate AUTOSAR Adaptive C++ Code and XML Descriptions
	Configure AUTOSAR Adaptive Code Generation
		Select AUTOSAR Adaptive Schema
		Specify Maximum SHORT-NAME Length
		Specify XCP Slave Transport Layer
		Specify XCP Slave IP Address
		Specify XCP Slave Port
		Enable XCP Slave Message Verbosity
		Use Custom XCP Slave
		Inspect AUTOSAR Adaptive XML Options
		Customize Class Name and Namespace in Generated Code
		Configure Run-Time Logging Behavior
		Generate AUTOSAR Adaptive C++ and XML Files
	Configure AUTOSAR Adaptive Data for Run-Time Calibration and Measurement
		Configure XCP Communication Interface in Generated Code
	Build Library or Executable from AUTOSAR Adaptive Model
	Build Out of the Box Linux Executable from AUTOSAR Adaptive Model
	Configure Run-Time Logging for AUTOSAR Adaptive Executables
		Logging to Console
		Logging to File
		Logging to Network
AUTOSAR Composition and ECU Software Simulation
	Import AUTOSAR Composition to Simulink
	Combine and Simulate AUTOSAR Software Components
		Import AUTOSAR Composition as Model (Classic Platform)
		Create Composition Model for Simulating AUTOSAR Components
		Alternatives for AUTOSAR System-Level Simulation
	Model AUTOSAR Basic Software Service Calls
	Configure Calls to AUTOSAR Diagnostic Event Manager Service
	Configure Calls to AUTOSAR Function Inhibition Manager Service
		Model Function Inhibition
		Scope Failures to Operation Cycles
		Control Function Availability During Failure or For Testing
		Configure Service Calls for Function Inhibition
	Configure Calls to AUTOSAR NVRAM Manager Service
	Configure AUTOSAR Basic Software Service Implementations for Simulation
	Simulate AUTOSAR Basic Software Services and Run-Time Environment
	Configure and Simulate AUTOSAR Function Inhibition Service Calls
	Simulate and Verify AUTOSAR Component Behavior by Using Diagnostic Fault Injection
AUTOSAR Software Architecture Modeling
	Create AUTOSAR Architecture Models
	Add and Connect AUTOSAR Compositions and Components
		Add and Connect Component Blocks
		Add and Connect Composition Blocks
	Import AUTOSAR Composition from ARXML
		Import AUTOSAR Composition By Using AUTOSAR Importer App
		Import AUTOSAR Composition By Calling importFromARXML
	Create Profiles Stereotypes and Views for AUTOSAR Architecture Analysis
		Create Profiles and Stereotypes
		View Component or Composition Dependencies
		Create Custom Views for Analysis
	Link AUTOSAR Components to Simulink Requirements
	Define AUTOSAR Component Behavior by Creating or Linking Models
		Create Model Based on Block Interface
		Link to Implementation Model
		Create Model from ARXML Component Description
	Configure AUTOSAR Scheduling and Simulation
		Simulate Basic Software Service Calls
		Connect a Test Harness
		Schedule Component Runnables
	Generate and Package AUTOSAR Composition XML Descriptions and Component Code
		Configure Composition XML Options
		Export Composition XML and Component Code
		Export Composition ECU Extract
	Author AUTOSAR Compositions and Components in Architecture Model
	Import AUTOSAR Composition into Architecture Model
	Configure AUTOSAR Architecture Model Programmatically
	Manage Shared Interfaces and Data Types for AUTOSAR Architecture Models
		Create Interface Dictionary
		Design Data Types and Interfaces by Using Interface Dictionary
		Link Interface Dictionary to Architecture Model
		Apply Interfaces to Architecture Model in Simulink Environment
		Deploy Interface Dictionary
		Limitations