Contents

Introduction

Scope

This document describes how to configure the System Description for SOME/IP module. Based on the Extended Starter Kit, this application notes describes the few steps required to transition the actual Sd configuration from BSW to System Description. ConfGen is used to import that configuration back into Sd module.

Few steps not covered by ConfGen are detailed as well.

Assumptions

The following ETAS tools were used for this Application Note.

ISOLAR-AB 9.2.1
RTA-BSW 6.1.3
RTA-RTE 7.5.3
ETAS Starter Kit project RTA-SK_VRTA_GCC_Extended_9.2.1_R1

Limitations

RTA-BSW does not support importing of Ethernet frames. Therefore this AN will not cover this part of a full AUTOSAR configuration.

This AN is based on RTA-SK_VRTA_GCC_Extended_9.2.1_R1, which already includes Pdus, Signals and Transformer configuration for SOME/IP services.

Therefore the steps of creating those objects are skipped here and focus his on configuring the SOME/IP-SD.

Acronyms and abbreviations

SOME/IP-SD configuration

SOME/IP uses Service Discovery module to offer and find services.

Services are then configured

SocketConnectionBundle configuration

Network End Point

A NetworkEndPoint is configured to define the Unicast address of the target. The parameters can be checked by double clicking Ethernet in the AR Explorer to open in the Generic Editor

The ApplicationECU Unicast configuration is found under NetworkEndpoints

A NetworkEndPoint can be configured to define the Multicast address of the network. This configuration is also found under NetworkEndpoints

Service Discovery control

For this step, the configuration is found in the same Generic Editor window, this time under So AD Config. First to access the properties tab, the Socket connection bundle should be selected in the AR Explorer

Next, the Socket Address SdTxControl configuration referenced should be checked in the Generic editor window

Note that to specify the multicast address, the socket address referenced by the SocketConnectionBundle that defines the Multicast socket connection should configure a MulticastConnector

Routing groups don't require EventGroupControlType configuration for the control path

The PDUs referenced by the SocketConnectionBundles for Control Path have Category set to SD, and SocketConnectionIpuIdentifier HeaderId are set to 0xFFFF8100 for the 3 PDUs of the Control Path

The PDU category configuration is found by selecting the relvant PDU in the AR Explorer and can then be found under the Properties tab

This will configure the control path of Service Discovery control path. This can be found in the ECU Navigator, under BSW Modules, the Com Stack and Ethernet Modules. 

Double click the Sd module to open with the BSW Editor

ApplicationEndPoint Services instance

Provided and consumed services are described in the system description by aggregation under ApplicationEndPoint.

Provided services

Provided services are aggregated under associated ApplicationEndPoint. In the open ETHERNET Generic Editor, navigate to SocketAddress under So Ad Config 

A new ProvidedServiceInstance should be created as shown, under the relevant SocketAddress. This should be configured as shown

A new Event Handler should be created under the new ProvidedServiceInstance_12. This should be configured as shown

ApplicationEndPoint defined the network port associated with the service

SdServerTimer configuration are defined by the SdServerConfig parameters. This is created under the EventHandler_2 just configured and should have the parameters shown

A RequestResponseDelay and InitialSdDelayConfig can then be created under the New Sd Server Config, and configured as shown

InitialSdDelayConfig configuration:

RequestResponseDelay configuration:

Consumed services

Consumed services are aggregated under associated ApplicationEndPoint. In the Generic editor, navigate to the relevant SocketAddress

Create a new Consumed Service Instance under the Application Endpoint. This new Instance should be configured as shown

Under the new Consumed Service Instance, create a new ConsumedEventGroup and configure as shown

Under the ConsumedEventGroup_0 just created, create and configure a new Sd Client Config This should be configured with the parameters shown

Under the Sd Client Config, create and configure as shown a RequestResponseDelay and an InitialSdDelayConfig

SdClientTimer configuration in SD module are defined by the SdServerConfig parameters

Routing Groups

Configuration of the routine group's EventGroupControlType will affect the configuration of the SdEventHandlers and determine if the SdEventHandlerMulticast should be configured. This is done through the AR explorer and the properties tab

algo.properties

The file algo.properties can be modified to change the default values for few parameters in SdGeneral and also SdConsumedEventGroupAutoRequire and SdClientServiceAutoRequire. This file can be located using the Filesystem Navigator

Limitations

Methods references are not configured automatically

SD SdConsumedMethods and SdProvidedMethods should be configured manually

AUTOSAR 4.4.0 requires that "a Client Server Operation in a Client Server Interface is used for the description of the Method" (see AUTOSAR_TPS_SystemTemplate, AR release 4.4.0, page 323 of 1794)

AUTOSAR suppose that the Client Server to Signal Mapping defines the service provided or consumed. This information is used to populate the SD SdConsumedMethods and SdProvidedMethods configuration

Unsupported feature: 

Unsupported feature: 

Current version of AUTOSAR toolchain does not support the CS connection and requires Methods to use Send Receiver to Signal Mapping . So, user cannot reference the Service Instance from the non existent Client Server to Signal Mapping.

SdGeneral configuration

Few parameters not covered by algo.properties are set manually. Open the Sd module from the ECU navigator by double-clicking

Changes