High-Performance Classic and Adaptive AUTOSAR Support

Classic AUTOSAR Support

The TargetLink Classic AUTOSAR block library.

The optional TargetLink AUTOSAR Module makes the modeling, simulation, and code generation features of TargetLink available for designing Classic AUTOSAR software components. TargetLink supports the vast majority of Classic AUTOSAR communication mechanisms and generates genuine RTE AUTOSAR macros.  

Designing Classic AUTOSAR Software Components

Modeling Classic AUTOSAR SWCs.

The TargetLink Classic AUTOSAR Block Library provides Classic AUTOSAR structure elements, for example, runnables, ports, and communication interfaces, at the model level. To define a Classic AUTOSAR runnable, a Function block specified as a Classic AUTOSAR runnable is used in a subsystem, similar to regular TargetLink functions. 

AUTOSAR page in a TargetLink block dialog.

The TargetLink InPort and OutPort blocks are used to define the data exchange between the runnables of one or more software components. Developers can specify properties on the block level and via the TargetLink Data Dictionary.  

Generating Classic AUTOSAR-Compliant Code

The generated C code with RTE macro calls.

TargetLink generates production code for Classic AUTOSAR software components. Moreover, TargetLink provides special options allowing for Classic AUTOSAR optimizations. Runnables are implemented as C functions, and Classic AUTOSAR communication mechanisms are implemented as run-time environment macros according to the Classic AUTOSAR standard. The same model can be used to generate Classic AUTOSAR-compliant code and standard TargetLink code. 

Simulating and Testing Classic AUTOSAR Software Components and SWC Compositions

TargetLink simulates Classic AUTOSAR software components in all simulation modes. Multiple software components can be simulated in one simulation run. The communication between software components is simulated to the extent supported by the Simulink design environment. For testing purposes in SIL and PIL, TargetLink generates a stub RTE that maps the RTE macro function calls in the application with SWC code to global variables and generates access functions to global variables.

Helpful Features and Utilities (Examples)

Feature/Utility Description Benefit
Importing and exporting software component descriptions.
  • Based on TargetLink AUTOSAR models, ARXML files can be exported directly from TargetLink.
  • Importing and merging existing software component descriptions from the TargetLink Data Dictionary.
Seamless Classic AUTOSAR development process with a tool such as SystemDesk and dSPACE AUTOSAR Compare.

Generating a Classic AUTOSAR frame model.

  • Generating a frame model containing the relevant ports and runnables.
  • Inserting the control algorithm into the model frame to obtain a complete Classic AUTOSAR software component.
  • Generating SWC compositions as frames.
Easy and convenient transfer of AUTOSAR specifications into the TargetLink model
Migrating standard TargetLink models to Classic AUTOSAR.
  • TargetLink AUTOSAR Migration Tool for automatically converting individual subsystems to Classic AUTOSAR runnables.
  • Supporting the flexible specification of Classic AUTOSAR properties.
Highest flexibility when reusing existing software parts.
Modeling Guide for Classic AUTOSAR Explains how to model and generate code for Classic AUTOSAR software components. Support while developing Classic AUTOSAR software components with the model-based development approach of TargetLink.

TargetLink in a Classic AUTOSAR Tool Chain

For Classic AUTOSAR software development, TargetLink is typically combined with an AUTOSAR architecture tool such as SystemDesk. A software architecture with multiple components is specified in the architecture tool, while TargetLink is used to design and implement the individual software components. The two tools exchange data via Classic AUTOSAR XML files. Both a top-down approach (starting with the software architecture) or a bottom-up approach (starting with a TargetLink function model) can be used for Classic AUTOSAR round trips. This AUTOSAR round trip can be simplified and automated by using dSPACE AUTOSAR Compare, which lets you compare and manually or automatically merge your AUTOSAR artifacts.

Adaptive AUTOSAR Support

The TargetLink Adaptive AUTOSAR block library.

The optional TargetLink Adaptive AUTOSAR Module makes the modeling, simulation, and code generation features of TargetLink available for designing Adaptive AUTOSAR applications. TargetLink supports selected features of Adaptive AUTOSAR, for example:

  • Importing and exporting Adaptive AUTOSAR ARXMLs with elements defined by ara::com.
  • Importing Adaptive AUTOSAR ARXMLs with elements defined by ara::per.
  • Modeling select parts of service-based communication as described by ara::com.
  • Modeling select parts of accessing persistent memory as described by ara::per.
  • Modeling and simulating error handling as described by ara::com and ara::per. 

Designing Adaptive AUTOSAR Applications

Modeling Adaptive AUTOSAR event communication with TargetLink.

TargetLink supports the model-based development of functional parts of adaptive applications. It provides different model elements for you to model the functionalities.

The following uses cases are supported to model communication according to ara::com:

  • Accessing fields as a service consumer or service provider.
  • Sending or receiving events.
  • Calling or implementing a method.

In addition, TargetLink supports the modeling of persistent data access, i.e., reading and writing key-value pairs from key-value storage, according to ara::per. 

Generating Code for Adaptive Applications

TargetLink generates Adaptive AUTOSAR functions from Method Behavior subsystems and Adaptive AUTOSAR subsystems. The Adaptive AUTOSAR function is a C++ function representing a partial functionality of an adaptive application. This function can be called in the C++ code of an adaptive application.

Simulating and Testing Adaptive AUTOSAR Models

TargetLink simulates Adaptive AUTOSAR models in MIL and SIL simulation mode. While building the simulation application for SIL simulation, TargetLink uses preprocessor macros and conditional compilation. This allows the simulation of the Adaptive AUTOSAR functions directly in TargetLink without the need of an Adaptive AUTOSAR middleware. For testing purposes, TargetLink supports modeling and simulating error handling as specified by Adaptive AUTOSAR.

Feature/Utility Description Benefit
MIL and SIL simulation Directly simulate the Adaptive AUTOSAR function in TargetLink without Adaptive AUTOSAR middleware. Easily simulate and validate your Adaptive AUTOSAR functionality in the development environment. TargetLink allows for comfortable and straight-forward testing without setting up, configuring, and maintaining a build chain for Adaptive AUTOSAR.
Modeling of select Adaptive AUTOSAR clusters Model persistent data access as defined by ara::per by reading and writing key-value pairs from a key-value storage. Model communication as defined by ara::com:
  • Accessing fields as a service consumer or service provider.
  • Sending or receiving events.
  • Calling or implementing a method.
Convenient and well-known modeling similar to Classic AUTOSAR modeling in TargetLink.
Modeling Guide for Adaptive AUTOSAR Explains how to model and generate code according to Adaptive AUTOSAR for the integration into adaptive applications. Support while developing functional parts of adaptive applications with the model-based development approach of TargetLink.

  • AUTOSAR Technology dSPACE supports the development of ECU software according to the AUTOSAR Adaptive Platform and the AUTOSAR Classic Platform.
  • Product Information

    Subscribe newsletter

    Subscribe to our newsletters, or manage or delete your subscriptions