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

Use Case: Migration from AUTOSAR 3 to AUTOSAR 4

Elements of a potential AUTOSAR tool chain that have to be considered during migration.

The AUTOSAR standard stands for safety, and the exchange and reuse of software components. dSPACE offers comprehensive support for migrating from AUTOSAR 3 to AUTOSAR 4.

dSPACE Support

  • Migrating existing architectures and elements
  • Integrating AUTOSAR tools into the development process
  • Comprehensive AUTOSAR support for R3 and R4
  • Project-specific automation via scripts

Migrating the Component Code

For migrating individual software components, TargetLink®, dSPACE's production code generator is more than just suitable. In TargetLink, when generating production code from the individual functions, the user can define which AUTOSAR version the code will be based on. Because the algorithms for open and closed loop controls are independent of AUTOSAR versions, they only have to be connected to version-specific data. This means that only this connected data has to be adjusted for AUTOSAR 4. TargetLink stores the data in a version-independent Data Dictionary, so AUTOSAR 4-compliant code can be generated just by changing one global property.

Migrating the Architecture

Due to the large and complex differences between the two AUTOSAR versions, complete system architectures and larger AUTOSAR system extracts cannot be migrated at the click of a button. Some processes can be automated via scripts, but these scripts have to be adjusted to each individual case.

A converter makes it possible to automatically convert all AUTOSAR 3 elements that are part of the AUTOSAR software component template. This ensures that no information is lost. However, the converter does not create new elements that were added with AUTOSAR 4. dSPACE confers with the customer to see what the architecture should look like with AUTOSAR 4. With this information, dSPACE Engineering Services creates customized scripts that generate the desired architecture via the SystemDesk automation interface.

Conversion takes place either at dSPACE or at the customer. dSPACE offers various engineering services for the migration.

Adjusting the Tool Chain

For a successful migration, developers not only have to keep the AUTOSAR files in mind, but also the entire underlying tool chain. When files are migrated from AUTOSAR 3 to AUTOSAR 4, it might be necessary to also update the AUTOSAR tools that are being used so that the new AUTOSAR 4 files can be edited later (figure 1). Here, dSPACE offers a mature tool chain as well as individual advice and support, letting users benefit from dSPACE's long-standing project experience. In close cooperation with the customer, dSPACE checks which data needs to be migrated, what type of data exists, and whether a single software component or a complete software architecture needs to be migrated. The solution for the migration is then tailored to the individual project needs.

dSPACE also offers trainings on AUTOSAR 4 to make customers familiar with the changes in the new version.

Further Information Product Information Success Stories