For a better experience on dSPACE.com, enable JavaScript in your browser. Thank you!

High-Performance, Native AUTOSAR Support

Designing AUTOSAR Software Components (SWCs)

The TargetLink AUTOSAR Block Library

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

Modeling AUTOSAR SWCs

To define an AUTOSAR runnable, the Function/Runnable block 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 AUTOSAR communication mechanisms. 

Referencing 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 AUTOSAR-compliant code and standard TargetLink code.  

Generating AUTOSAR-Compliant Code

The generated C code for a runnable with three included RTE macro calls.

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

Simulating and Testing 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 AUTOSAR XML format
  • Importing and merging existing component descriptions from the TargetLink Data Dictionary
  • Seamless AUTOSAR development process with a tool like SystemDesk
  • AUTOSAR frame model generation
  • Generating a frame model containing the relevant AUTOSAR ports and runnables
  • The developer can insert the control algorithm into the model frame to obtain a complete AUTOSAR software component
  • Easy migration of existing models to AUTOSAR
  • Easy modeling from scratch
  • Migrating standard TargetLink models to AUTOSAR
  • TargetLink AUTOSAR Migration Tool for automatically converting individual subsystems to AUTOSAR runnables
  • Supporting the flexible specification of AUTOSAR properties
  • Highest flexibility when re-using existing software parts

TargetLink in an AUTOSAR Tool Chain

For 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 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 AUTOSAR round trips.

Further Information