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 Application Software.

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:

Prerequisites

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

Workflow description

Create a new RTA-CAR Project

Open a new Workspace in ISOLAR-AB 6.0.1.

From the Menu Bar select File --> New... --> RTA-CAR Project as shown below.

In the pop-up window "New RTA-CAR Project", set "Project Name", choose the Project Location removing the "Use default location" flag, set the AUTOSAR release to AUTOSAR 4.2.2., then press Finish.

At a Filesystem level, this step will create the structure shown below:

Create an Application Data Type

The new RTA-CAR Project will open in the "AR Explorer" view. Expanding the item Software --> Data Types you can see that two subcategories of data are already present and populated: "Implementation Data Types" and "Base Types".

It is possible to create a third category of data type: "Application Data Types"; to do so, right click on Software and select Software --> Create Data Type --> Create Application Data Type --> Create Elements | Application Primitive Data Type.

The Application Data Types are the type of data used to provide more abstraction to the ASW. It is not mandatory to create new Application Data Types - Base Data Types can also be used in ASW.

New AR Element Creation Window

For each new element created in the project, a pop-up window "New AR Element Creation" will appear.

In this window you can select the name of the AR Package in which the new element will be placed, as well as the arxml describing the new element. You can use this window in order to create a new arxml file and a new package, or you can decide to use an existing arxml file and an existing package.

Create a Data Type Mapping

The new Application data type must be mapped to an Implementation Data Type or Base Data Type. To do so, you must create a Data Type Mapping set. Right click on "Software" and select Software --> Create DataType --> Create Element | Data Type Mapping Set.

You can skip this step if you are not using any Application Data Type in your project.

Place the Mapping set in the previously created ARPackage.

Add a new Data Type Mappings by open the mapping set, and in tab "Data Type Map" pressing Add. 

Configure the new Data Type Mapping by selecting the desired Application Data Type and Implementation Data Type or Base Data Type.

In the example shown in the screenshot, we mapped "MyApplicationDataType" to the "uint8" Implementation Data Type.

Create a new Port Interface

Ports connecting SWCs must reference a defined Port Interface. To create a Port interface, right click on "Software" and select Software --> Create Interface --> Create Port Interface --> Elements | Sender Receiver Interface.

Additional AUTOSAR interfaces, such as Client Server Interfaces or Mode Switch Interfaces can be created in the same way.

Create the Port Interface into a new ARPackage "Interfaces". Note: the user has the freedom to decide where to place the Package and which arxml files use/create for each element.

Double click on the Interface to open it with the "Data Dictionary Editor"; in "Sender Receiver Interface", select the interface from the table and press the Add VariableData Prototype button.

Set the Data Element name and its Type reference. The result of this step is shown in Figure below.

With this step, we are defining that the data exchanged with the new Port Interface will be of the type "MyApplicationDataType".

Create a new SWC

In this sample project you will create two SWC prototypes one for transmitting and the other one for receiving. The system is composed by two ECUs that use the same SWC prototypes.

To create the SWC right click on "Software" and select Software --> Create Component --> Elements | Application Sw Component Type and place the SWC in a new ARPackage named "SWCs".

Note: It is recommended to use an arxml file for each SWC, allowing easier reuse of SWCs in other projects.

Create a new Port

SWCs communicate with each other through ports, the transmitting SWC prototype has a PPort while the receiving one has an RPort. To create a new port, open the SWC with "Component Editor"; in "Main" Tab press the PPorts... button. In the pop-up window "Port Creation Dialog", select the Interface previously created.

After creating the port you can modify its name double clicking in the column "Short Name".

Create a new Internal Behaviour

Each SWC requires an "Internal Behaviour", for example to contain Runnable Entities. To create the container, right click on the SWC and select New Child --> Internal Behaviours | Swc Internal Behaviour.

Double click on the container to open it and set its properties, in particular set the name, the reference to the Data Type Mapping Set and, in case the SWC prototype will be used in more than one instance, set the property "SupportsMultipleInstantiation" to true. The result of this step is shown below.

Create a new runnable

Now that the Internal Behavior is created, you can create the Runnable Entities. To create a Runnable Entity, open the SWC prototype with the "Component Editor" and switch to the "Functions" Tab. Press the Runnables button and edit the runnable name and its Function name in the table.

Create a new Data Access Point

Runnable Entities only have access to SWC ports if there is Data Access. To create Data Access, in the "Functions" Tab switch to the "Data Access Points" subtab and press the Access Points... button.

This Runnable will transmit data on the PPort, so the Data Access will be a Data Send Point. In the pop-up window "Create DataAccessPoint Dialog" select the "Data Send Points".

Create a new Event

Runnables can be executed only if they are connected to an event. In this sample project both the SWCs are triggered by a timing event. To create the event switch to "Events" tab, open the drop down menu next to the green add button, and select "Timing Event".

In the "TimingEvent Creation Dialog" select the desired Runnable by double clicking on it and pressing OK.

Configure the event's properties such as the the event name and the period - the result of this step is shown below.

NB: Now repeat the same steps to create a second SWC to receive the data, in this case the port will be a required port and the event a data received event; finally the Data access point must be a Data Receive Point.

Create a Composition

Once all the desired SWC prototypes have been created, they can be aggregated into a composition. To do so, right click on "Software" and select Software --> Create Composition --> Elements | Composition Sw Component Type and place the Composition in a new ARPackage named "Composition".

Double click on the composition to open it with the "Composition Editor", open the drop down menu next to the green add button and select Component Prototype.

In the pop-up window "Create Component Prototype Dialog" select all the ASW SWCs and press OK.

Note: Adding the same SWC propotypes multiple times will create multiple instances from the SWC prototype.

You can edit the SWC names double clicking on each one of them.

The four SWCs in the Composition are not connected yet; to connect them you must create some connectors; re-open the Composition and switch to "Manual Connection Editor" Tab. Choose from the "Source Component" and "Target Component" drop-down menus the RPort and the PPort and connect them by pressing the connector button in the middle.

Now that the Composition is done, the overview can be viewed by right clicking on the Composition and selecting Open with --> Composition Overview.

Conclusions

The steps presented in this guide allows you to create your own Application SW. You can repeat the steps to further configure the system according to your needs.