AUTOSAR Blockset
Design and simulate AUTOSAR software
AUTOSAR Blockset provides apps and blocks for developing AUTOSAR Classic and Adaptive software using Simulink® models. You can design and map Simulink models to software components using the AUTOSAR Component Designer app. Alternatively, the blockset lets you generate new Simulink models for AUTOSAR by importing software component and composition descriptions from AUTOSAR XML (ARXML) files.
AUTOSAR Blockset provides blocks and constructs for AUTOSAR library routines and Basic Software (BSW) services, including NVRAM and Diagnostics. By simulating the BSW services together with your application software model, you can verify your AUTOSAR ECU software without leaving Simulink.
AUTOSAR Blockset lets you create AUTOSAR architecture models in Simulink (requires System Composer™). In the AUTOSAR architecture model, you can author software compositions, components, and interfaces. You can add simulation behavior including Basic Software service components. Alternatively, you can round-trip (import and export) software descriptions via ARXML files.
AUTOSAR Blockset supports C and C++ production code generation (with Embedded Coder®). It is qualified for use with the ISO 26262 standard (with IEC Certification Kit).
Get Started:
Model AUTOSAR Classic Software Components
Automatically create an AUTOSAR Classic software component with default AUTOSAR ports, interfaces, and other configurations in Simulink.
Model AUTOSAR Classic software components.
Model AUTOSAR Adaptive Software Components
For AUTOSAR Adaptive platform, use AUTOSAR Blockset to automatically generate software components with default AUTOSAR ports, service interfaces, and other configurations in Simulink.
Model AUTOSAR Adaptive software components.
Configure Advanced AUTOSAR Properties
Edit and map the advanced AUTOSAR properties for both AUTOSAR Classic and Adaptive models using the AUTOSAR editor and dictionary.
Explore gallery (2 images)
Scaling from Software Components to Compositions
Create AUTOSAR software compositions from software components using model references. Visualize the behavior of the compositions with Dashboard blocks.
Simulation of compositions including input controls and Dashboard blocks.
Blocks for Simulating AUTOSAR BSW Services
Use blocks and constructs for BSW services, including NVRAM Manager and Diagnostics Event Manager, to simulate BSW services together with your application software model. Verify your AUTOSAR ECU software directly in Simulink.
Simulate and Test Software Compositions
Model and simulate the behavior of compositions within Simulink. Optionally perform back-to-back testing workflows for AUTOSAR composition models with Simulink Test™.
Testing AUTOSAR compositions.
Create an AUTOSAR Architecture Model
AUTOSAR architecture models allow you to author software compositions, components, and interfaces in Simulink and link them to requirements (requires Simulink Requirements™). You can also specify behavior for the components in the architecture model by creating a new Simulink component model, linking to an existing component model, or importing one from ARXML.
Configure Scheduling and Simulation
You can add Basic Software (BSW) blocks, including Diagnostic Service Component and NVRAM Service Component blocks, to the architecture model to simulate calls to BSW services. Additionally, you can schedule and specify the execution order of component runnables for simulation using Schedule Editor. This allows you to verify your AUTOSAR ECU software without leaving Simulink.
Using Schedule Editor to configure AUTOSAR runnable execution order.
Generate and Package Composition ARXML Descriptions and Component Code
You can export composition and component ARXML descriptions, generate component code, and package build artifacts for integration with an AUTOSAR run-time environment.
Generating composition ARXML and component code.
Starting with the Simulink Model
Use an existing or newly created Simulink model and configure it for AUTOSAR using the AUTOSAR Component Designer app. Then use Embedded Coder to generate ARXML files (a bottom-up AUTOSAR workflow).
Using the AUTOSAR Component Quick Start tool to configure AUTOSAR properties.
Starting with the AUTOSAR Architecture
Import ARXML files from an AUTOSAR authoring tool as Simulink components and composition models. Then model the detailed design in Simulink. Update the model when updated ARXML files become available (a top-down AUTOSAR workflow).
Iterating Between the Simulink Models and Your AUTOSAR Architecture
Update Simulink model configured for AUTOSAR, export updated ARXML files, and merge into the AUTOSAR authoring tool; export updated ARMXL files from the authoring tool, then import ARXML files to merge architectural changes in the Simulink model (a round-trip AUTOSAR workflow).
Iterating between the Simulink model and AUTOSAR Architecture.
AUTOSAR Production Code Generation
With Embedded Coder, generate C/C++ code and AUTOSAR XML files. Perform SIL and PIL tests with the code for verification.
Explore gallery (2 images)
Blocks and Code Replacements for AUTOSAR Library Routines
Use preconfigured AUTOSAR blocks and code replacements to generate optimized library routines for AUTOSAR Classic applications.
Explore gallery (2 images)
ISO26262 Qualification and MISRA-C Compliance
Qualify Embedded Coder generated code for ISO 26262 with IEC Certification Kit. Verify your generated AUTOSAR code for MISRA-C compliance, check for run-time errors, and look for mismatches between the code and AUTOSAR ARXML descriptions using Polyspace Code Prover™.
Polyspace Bug Finder can detect violations of the AUTOSAR C++14 coding standard.
