RTA Knowledge Base

Table of Content

Introduction

Scope

This application note describes how to create and configure a new RTA-CAR project and how to create and configure your System Template.

Definitions and Abbreviations

BSW: AUTOSAR Basic Software, Hardware independent service layer

RTE: AUTOSAR Real Time Environment

OS: AUTOSAR Operating System

SWC: Software Component

Toolchain

It is assumed you are using the RTA-CAR 6.0.1 toolchain:

RTA-CAR 6.0.1 toolchain

ISOLAR-AB6.0.1
RTA-RTE6.8
RTA-BSW5.0
RTA-OS5.6.4

Prerequisites

In order to successfully follow this guide, you must have the RTA-CAR toolchain installed and you must be familiar with the AUTOSAR specifications, terminology and methodology.

Moreover, you need to have your ASW already created and configured inside the RTA-CAR project (see other guides).

Workflow

Import input non-AR files

When creating a new project, it is recommended you use the importer functionality in ISOLAR-AB, rather than configuring the system manually using the GUI. These importers translate input files, for example DBC (CAN system description) files, into an AUTOSAR configuration.

You can find the importer icons in the ISOLAR-AB toolbar. For more information on how to use these importers and on which features are supported, please consult the ISOLAR-AB documentation.

In this guide a DBC file will be imported and the Communication Stack will be configured for the CAN communication. The steps are similar if you need to configure a different type of Network.

Import a DBC file

Before importing a DBC file, the system configuration (SWCs, Interfaces, Ports etc.) should already exist. The DBC file describes the CAN communication between the ECUs in this system.

Open the DBC importer with the DBC importer button shown below.

In the pop-up window "Import DBC" choose the DBC file and press Next.

If desired, change the arxml file name and package in the window shown below.


Select the ECU for this project and press Next.



Select all the desired messages for the ECU and press Finish.


The result of the DBC import is the creation of an ECU Instance and all the PDUs, System Signals, BSW module configuration etc. needed for the CAN communication.

Create the System description

With a System Configuration and DBC import, all the elements needed to describe a system exist. The next step is to create the System Description.

According to AUTOSAR, the description of the System can be created with an System Element of category SYSTEM_DESCRIPTION. It contains all the information about the whole system and for all the ECUs of the system.

From the System Description, the ECU Extract can be created. The ECU Extract is the description of a single ECU of your system.

What do I do if I receive an ECU Extract or a System Description arxml file?

An ECU Extract is just another arxml file that contains the description of a single ECU, as mentioned before.

An alternative of the workflow presented in this document, is to import an ECU Extract instead of importing input files such as DBC or LDF. This means that when you will import the arxmls files which contain the ECU Description in the project, the result will be the same as the one obtained following the steps of creating the system and the Ecu extract as explained in this and in the following guides.

Create a new system

To create a System right click on "System" and select Create System info --> Elements | System.

Place the System in a new ARPackage in the existing DBC_SysDesc.arxml file.



Right click on the System and select Open with --> Generic Editor. Set the property Category to SYSTEM_DESCRIPTION.

Now you must configure the System to reference the Root Software Composition. To do so, right click on the System and select New Child --> Root Software Composition | Root Sw Composition prototype.

Double click on the RootSwComponent to open it, change its name and add the reference to the Composition previously created.

Now you can map the SWC in the composition on the ECU Instance in the System. In this case only the SWCs referring to EcuA will be mapped while the SWCs referring to EcuB will be left unmapped. Open the System with the SWC to ECU Mapping Editor.

Click the Create SystemMapping button as shown below.



Expand the Composition to see the available SWC prototypes, then drag the SWC referring to EcuA to the ECU Instance in the table on the right.

Now you must map the System Data; open the System with the "System Data Mapping Editor" by right clicking on the System.

Double click on the empty boxes in the table to select the correct System Signal to be associated to the Data Element.

Conclusions

Following the steps presented in this guide, you should be able to create your own System Description. The next steps will be to extract the information about the ECU you want to configure (creating the ECU Extract). After the creation of the ECU Extract, you can add configuration to it such as RTE, OS and BSW configurations. For further details please consult the other guides.