Introduction

Scope

RTA-SUM is a solution for integrating the Standard Utility Modules (SUMs) defined by GM for the Global B platform. SUMs are software components located in the Application Layer of the standardized architecture of AUTOSAR.

The scope of this getting started guide is to explain and summarize all the steps needed for the integration and configuration of the RTA-SUM modules in a RTA-CAR project. This document is not meant to be an exhaustive guideline to cover all the integration aspects of all the RTA-SUM modules, but rather to provide a general guideline on the common steps and workflow for the RTA-SUM integration. Please be aware that the steps required for the RTA-SUM integration might vary among the different modules.

Definitions and Abbreviations

SUM: General Motors Standard Utility Module

BSW: AUTOSAR Basic Software, Hardware independent service layer

RTE: AUTOSAR Real Run Time Environment

OS: AUTOSAR Operating System

SWC: Software Component

Toolchain

It is assumed you are using the below RTA-CAR 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. You also must be familiar with the GM specification and GM-SUM modules functionalities.

Project creation/update

The first step is to create your RTA-CAR project, if you already don't have one. 

In the project creation phase, the RTA-CAR toolchain will create the basic folder structure for your project. Once you have your basic project structure created, you can proceed with the next step and install the RTA-SUMs into your project.

The following steps of this guide are assuming you already have a working RTA-CAR project with the RTA-CAR toolchain. 

Installation of the ETAS RTA-SUM modules into your project. 

Follow the RTA-SUM_Getting_Started_Guide.pdf that comes as part of the SUM packages to install the RTA-SUM plugin onto ISOLAR-AB.

SUM Common package

The following files are created in the \ecu_config\static\SUM_COMMON when you create a new RTA-CAR project that includes RTA-SUM:

1. compiler.h
2. compiler_cfg.h
3. MemMap.h
4. Platform_Types.h
5. Std_Types.h
6. AUTOSAR_MOD_PlatformBaseTypes.arxml
7. AUTOSAR_MOD_PlatformTypes.arxml

These files should be available on the path and should be removed from this location if they are already included elsewhere in the RTA-CAR project (e.g. from the RTA-BSW).

The integrator should make the decision on whether to keep or remove these files.

GM_SUM_Intefaces.arxml

This file is important for the RTE generation and should NOT be removed from the project.

Project structure

• Source code: RTA-SK\src\sum
• Static source code, API files, validation scripts: RTA-SK\ecu_config\static
• Configuration files: RTA-SK\sum_config

Configuration of the RTA-SUM modules

After importing all the needed files, you should be able to see the modules that you imported in the list of the ECU Navigator. In the example below, after doing the steps for the TCS module, you will be able to see it in the list, right clicking on the "Other Modules" item:

Clicking the item "Create Tcs" will create a new arxml that will contain the TCS configuration. This step is the same for all the RTA-SUM modules, so you can click all the modules that you want to add to your configuration

The selected module can be now configured as a standard BSW module. Configuration and integration hints can be found in the individual user guides that come as part of the SUM packages.

You can fill it out with the values that you wish to have in your configuration, for example:

RTA-SUM Generation

It is now possible to run the CodGen for the RTA-SUM modules, which will generate the SWCs and the corresponding source code for all the RTA-SUM modules you configured.

To specify the SUM modules for the code build select Open RTA Code Generator dialog... and select the SUM module to build depending on the project model year.

Output files

If the generation runs correctly, you will be able to see the generated files in your output folder.

For each module these will be:

• SUM_xxx_Cfg.c
• SUM_xxx_Cfg.h
• SUM_xxx_Cfg_SWCD.arxml

You also should have the generated SWCs for each configured RTA-SUM module in the list of the Components available in the project:

Dependencies of RTA-SUM modules

After the generation of the RTA-SUM SWCs and source code, there are still steps to be done. Every SUM module requires particular BSW configurations and interactions with the BSW modules, as well as with the other RTA-SUM modules.

Since there are dependencies among the different RTA-SUM modules, ETAS strongly suggest to integrate the modules in the following order:

• SUSD
• PNC
• SSC
• SSM
• ERRH
• DIAG
• TCS

In the example below, after generating the RTA-SUMs, we opened the SUM-TCS SWC to have a further look to what has been created.

You will see that some Port Interfaces are not available in the Main tab. This means that the SUM_TCS does not find the correct reference to the Interfaces. The reason is that the BSW configuration is not complete and these required interfaces are not yet created.

Once you configured the BSW and satisfied the dependencies of the RTA-SUM modules, you must regenerate the BSW source code. Along with the BSW source code generation, also the Service SWC descriptions of the BSW modules will be updated. Please consult the RTA Getting Started guides if you want more details on how to configure the BSW and run the generators. 

After regenerating the BSW source code, the interfaces have been created and have been included in the BSW SWCDs, therefore the RTA-SUM SWCs will be able to resolve the previously missing references, as shown in the example below:

ASW and System Integration

At this point you should have the BSW and the RTA-SUM module configurations completed. The next step is to update the ASW adding the RTA-SUM SWC prototype to the composition and creating the connections with the other SWC (ASW, BSW Service Components, other RTA-SUM modules).

For example, the RTA-SUM TCS needs to be connected to the SUSD for the PermitExecution and the ShutdownPermission signals.

Please consult the RTA-CAR Guides for more information on how to update your ASW composition and how to create connections using the RTA-CAR toolchain.

To summarize, the steps you have to follow in order to integrate the RTA-SUM modules with your ASW and your system are the following:

1. Update all the connections in the ASW composition (i.e. connect the RTA-SUM modules among them and with the ASW and BSW Service Components)
2. Update your System configuration: Add the SWC to the ECU Mapping using the "SWC To ECU Mapping Editor"
3. Regenerate the EcuExtract
4. Update the RTE Configuration mapping the new runnables to the Tasks

It is outside of the scope of this guide provide details on how to execute this steps with the tools. For further information, please consult the RTA Getting started guides.

RTE generation

After your system configuration has been updated, you can generate the RTE. The generated RTE code will contain all the function calls that allow the RTA-SUM to interact with each other and with the ASW and BSW.