Menü Schließen

Model-Based Development for AUTOSAR-Compliant ECUs

Purpose

Enable engineers to design, simulate, and generate production-quality AUTOSAR software components directly
within Simulink. As a MathWorks® AUTOSAR™ Premium Member, the Blockset offers round-trip integration
between Simulink models and AUTOSAR ARXML descriptions, bridging high-level design and embedded implementation.

AUTOSAR Blockset Overview

Key Features

  • Development Support Apps & Blocks
    • AUTOSAR Component Designer for mapping Simulink subsystems to SW-Components
    • Import existing ARXML to generate Simulink models, or start from Blockset templates
  • BSW Service Modeling
    • Prebuilt blocks for NVRAM, Diagnostics, and other Basic Software services
    • Simulate BSW interactions alongside application logic in Simulink
  • Architecture Modeling
    • Create compositions, components, ports, data types, and stereotypes via System Composer integration
    • Support for both Classic and Adaptive platforms with round-trip ARXML export/import
  • Production Code Generation
    • Embedded Coder exports ARXML descriptions plus C/C++ code
    • ISO 26262 IEC Certification Kit qualification for safety-critical workflows

Core Blockset Components

  • AUTOSAR Component Block: Encapsulates SW-Component logic and data.
  • Runnable Entities: Map discrete tasks to timing events or OS schedules.
  • Sender/Receiver Ports: Standardized data exchange between components.
  • Client/Server Interfaces: Service-oriented communication patterns.
  • Software Compositions: Hierarchical grouping of multiple SW-Components.

Typical Workflow

  1. Requirement Analysis
    • Define functional, timing, and safety requirements.
  2. Model Development
    • Build control algorithms and diagnostics in Simulink using AUTOSAR-specific blocks.
  3. AUTOSAR Mapping
    • Assign model inputs/outputs to sender/receiver ports, runnables, and service interfaces.
  4. Simulation & Validation
    • Run compositions in Simulink to verify behavior, including BSW services.
  5. Code & ARXML Export
    • Use Embedded Coder to generate ARXML files and MISRA-compliant C/C++ code.
  6. Round-Trip Updates
    • Re-import updated ARXML into Simulink or other AUTOSAR tools for iterative refinement.

Typical Output Artifacts

  • Model Files: ARXML for software components, interfaces, and data types.
  • Code Files
    • my_autosar_swc.c / .h for component entry points and data structures
    • ARXML deployment descriptors: .arxml packages for RTE integration

System Composer vs. AUTOSAR Blockset

Aspect System Composer AUTOSAR Blockset
Purpose High-level architecture modeling AUTOSAR-compliant component development
Focus Multi-standard system views (SysML, UML) Classic & Adaptive platform SW-Component implementation
Integration Simulink simulation RTE and ECU workflows
Outputs Architecture diagrams, simulation models ARXML files, AUTOSAR-compliant C code

Key Benefits

  • Standards Compliance: Automated adherence to AUTOSAR and ISO 26262 rules.
  • Rapid Iteration: Model-based prototyping with immediate simulation feedback.
  • Modularity & Reuse: Encapsulated SW-Components and compositions simplify system scaling.
  • Seamless Toolchain: Round-trip ARXML import/export ensures consistency across AUTOSAR toolsets.
  • Improved Collaboration: Shared models and ARXML artifacts bridge architects, developers, and integrators.

By leveraging the Simulink AUTOSAR Blockset, teams can accelerate the path from requirements
to production, ensuring robust, maintainable, and standards-compliant ECU software.