Saturday, May 19th, 2012

From system design to production-ready AUTOSAR software

We are working in close cooperation with dSPACE in the area of producing AUTOSAR-compatible control unit software. In the AUTOSAR software architecture, our tool EB tresos Studio covers the creation and configuration of the basic software, and dSPACE’s SystemDesk the application layer and the system design. Together, our concerted tools form a tried and tested tool chain for all AUTOSAR ECU software development steps. The exchange between the two tools is based on standard AUTOSAR file formats.

The starting point for designing the AUTOSAR software architecture of ECUs is dSPACE SystemDesk. The graphical representation of components simplifies the development even of complex systems. The AUTOSAR basic software core is generated with our tool EB tresos Studio. The system information the ECU requires is imported from SystemDesk into EB tresos Studio, and the AUTOSAR basic software is correspondingly preconfigured. The completion of the configuration and subsequent generation of source code in EB tresos Studio leads to the production-ready ECU basic software core, EB tresos AutoCore. The final AUTOSAR-compliant software can then be integrated into an ECU.

Learn more about the tool chain in this application note. It describes the interaction between two AUTOSAR tools, dSPACE SystemDesk and EB tresos Studio, versions

  • SystemDesk 3.0

  • EB tresos Studio 2010.a and EB tresos Studio 10.0

In the workflows described, SystemDesk is used as a software design tool, and optionally as a system design tool. EB tresos Studio is used to configure and generate the AUTOSAR basic software, as well as for RTE configuration and generation. The application note is subdivided according to tools and to typical use cases.
The following use cases are described:

  • Creating the software architecture with dSPACE SystemDesk

    • Creating a software architecture for a single ECU

    • Creating a software architecture for an ECU network

    • Connecting with AUTOSAR service components

    • Using an AUTOSAR ECU extract


  • Configuring the basic software incl. RTE with EB tresos Studio

 

Download the PDF

dSPACE SystemDesk and EB tresos Studio – AUTOSAR development work-flow descriptions

Download the PDF (German)

dSPACE SystemDesk and EB tresos Studio – AUTOSAR development work-flow descriptions

 

<" alt="" border="0" />—[if gte mso 9]> <—[if gte mso 10]>  

SystemDesk – EB tresos Studio