High-Performance, Native AUTOSAR Support

Designing Classic AUTOSAR Software Components (SWCs)

The optional TargetLink AUTOSAR Module makes TargetLink’s modeling, simulation, and code generation features available for designing Classic AUTOSAR software components (SWCs). Developers can use the TargetLink AUTOSAR Block Library to easily specify Classic AUTOSAR structure elements, such as runnables, ports, and communication interfaces at model level.  

Modeling Classic AUTOSAR SWCs

To define a Classic AUTOSAR runnable, the Function block, which is specified as a Classic AUTOSAR Runnable, is applied to a modeled subsystem just as for normal TargetLink functions. To define how data is exchanged between the runnables of one or more SWCs, TargetLink Inports and Outports are used just as in non-AUTOSAR applications. TargetLink supports a vast majority of all Classic AUTOSAR communication mechanisms. 

Referencing Classic AUTOSAR objects specified in the Data Dictionary from dedicated block dialogs.

Property specifications are made both on block level and via the TargetLink Data Dictionary. The same model can be used to generate both Classic AUTOSAR-compliant code and standard TargetLink code.  

Generating Classic AUTOSAR-Compliant Code

TargetLink generates production code for Classic AUTOSAR software components and provides all the code generation options for optimization. Modeled runnables are implemented as C functions, and Classic AUTOSAR communication mechanisms specified in TargetLink Inports/Outports are implemented as run-time environment (RTE) macros according to the Classic AUTOSAR standard. 

Simulating and Testing Classic AUTOSAR SWCs

With TargetLink, SWCs can be simulated in all three simulation modes:

  • Model-in-the-loop (MIL)
  • Software-in-the-loop (SIL)
  • Processor-in-the-loop (PIL)

Multiple SWCs can be simulated in one simulation run. Communication between SWCs is simulated to the extent supported by the Simulink design environment.

Helpful Features and Utilities (Examples)

Feature Description Benefit
  • Importing and exporting SWC descriptions
  • Creating component descriptions and exporting them in Classic AUTOSAR XML format
  • Importing and merging existing component descriptions from the TargetLink Data Dictionary
  • Seamless Classic AUTOSAR development process with a tool like SystemDesk
  • Classic AUTOSAR frame model generation
  • Generating a frame model containing the relevant Classic AUTOSAR ports and runnables
  • The developer can insert the control algorithm into the model frame to obtain a complete Classic AUTOSAR software component
  • Easy migration of existing models to Classic AUTOSAR
  • Easy modeling from scratch
  • 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 re-using existing software parts

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 “fill“ and implement the individual SWCs. The two tools exchange data on the basis of Classic AUTOSAR XML files. A topdown approach (starting with the software architecture) and a bottom-up approach (starting with a TargetLink function model) can both be used for Classic AUTOSAR round trips. This AUTOSAR round trip can be simplified and automated by using the new, additional product dSPACE AUTOSAR Compare, which enables users to compare and manually or automatically merge their AUTOSAR artefacts.

Production Code for Adaptive AUTOSAR

With the optional TargetLink Adaptive AUTOSAR Module, TargetLink offers model-based code generation for functional parts of Adaptive AUTOSAR applications. TargetLink 5.1 supports selected features of the Adaptive AUTOSAR Release 19-11 standard. The following additional features are supported with TargetLink 5.1 compared to TargetLink 5.0:

  • Import of Adaptive AUTOSAR ARXMLs with elements defined by ara::per
  • Modeling of select parts of a service-based communication as described by ara::com:
    • Sending and receiving events as defined in Adaptive AUTOSAR release 18-10.
    • SIL simulation of Adaptive AUTOSAR components.
  • Modeling of select parts of access to persistent memory as described by ara::per:
    • Read and write access to key-value pairs with an AdaptivePlatformType from key-value storages via Data Store blocks.

A demo model that showcases the different modeling styles for Adaptive AUTOSAR communication is provided. Additionally, a new guide (Adaptive AUTOSAR modeling guide) for the user documentation is available.

More Information Product Information

Subscribe newsletter

Subscribe to our newsletters, or manage or delete your subscriptions