GB5401 2014 10 27 Ethernet Software Implementation Specification PDF

Document Name:
Ethernet Software Implementation Specification

Approved By:
File
Reg no
Info Class
N/A
GB5401_2014_10_27_Ethernet_Software_Impleme
ntation_Specification.docx
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
1 (148)
II
General Motors Company

GB5401
Release: V1.7
Release Date: 10/27/2014
GM Confidential
2014 General Motors LLC. All Rights Reserved
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
2 (148)
II
Table Of Contents
1 Introduction ......................................................................................................................................... 8
1.1 Document Updates and Revision History ....................................................................................... 8
1.2 Issue History .................................................................................................................................. 8
1.2.1 Revision Log ............................................................................................................................ 8
1.3 Team Membership....................................................................................................................... 10
1.3.1 Serial Data............................................................................................................................. 10
1.3.2 Contracted Experts................................................................................................................ 11
1.4 Document Scope .......................................................................................................................... 11
1.5 Requirement Wording Conventions ............................................................................................. 11
2 Applicable Documents ........................................................................................................................ 12
2.1 Precedence Order ........................................................................................................................ 12
2.2 Government Regulations and Documents .................................................................................... 13
2.3 General Motors Documents ......................................................................................................... 13
2.4 Industry Documents ..................................................................................................................... 13
2.4.1 AUTOSAR Consortium Documents......................................................................................... 13
2.4.2 OSEK Documents................................................................................................................... 14
2.4.3 ISO Documents ..................................................................................................................... 14
2.5 Other Documents ........................................................................................................................ 15
2.6 AUTOSAR version......................................................................................................................... 15
2.7 Modifications to AUTOSAR........................................................................................................... 16
2.8 BSW modules required for Global B Ethernet ............................................................................... 16
2.9 RTE (required) .............................................................................................................................. 18
2.10 Services Layer ............................................................................................................................ 18
2.11 System Services ......................................................................................................................... 18
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
3 (148)
II
2.12 OS (capable)............................................................................................................................... 18
2.13 EcuM Flexible (required) ............................................................................................................ 20
2.14 ComM (required) ....................................................................................................................... 22
2.15 Dem (not required) .................................................................................................................... 23
2.16 FIM (not required) ..................................................................................................................... 24
2.17 Det (not required) ...................................................................................................................... 24
2.18 DLT (not required)...................................................................................................................... 24
2.19 StbM (not required) ................................................................................................................... 24
2.20 Watchdog Manager (not required)............................................................................................. 25
2.21 BswM (required) ........................................................................................................................ 25
2.22 Memory Services ....................................................................................................................... 27
2.23 NVRAM Manager (capable) ........................................................................................................ 27
2.24 Communication Services ............................................................................................................ 28
2.25 COM (Not required) ................................................................................................................... 29
2.26 Dcm (not required) .................................................................................................................... 31
2.27 Debugging (not required) ........................................................................................................... 31
2.28 XCP (not required) ..................................................................................................................... 31
2.29 PduR (required) ......................................................................................................................... 31
2.30 IpduM (not required) ................................................................................................................. 32
2.31 NmIf (not required) .................................................................................................................... 32
2.32 Ethernet SM (required) .............................................................................................................. 33
2.33 UDP Nm (not required) .............................................................................................................. 33
2.34 Socket Adapter (required) .......................................................................................................... 34
2.35 DoIP (required) .......................................................................................................................... 35
2.36 Internet Protocol Stack (required) .............................................................................................. 35
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
4 (148)
II
2.36.1 UDP (required) .................................................................................................................... 36

2.36.2 TCP (required) ..................................................................................................................... 36
2.36.3 DHCP (required)) ................................................................................................................. 36
2.36.4 ARP (required)..................................................................................................................... 37
2.36.5 IP (required) ........................................................................................................................ 37
2.36.6 ICMP (required)................................................................................................................... 37
2.36.7 NDP (required) .................................................................................................................... 38
2.37 ECU Abstraction Layer ................................................................................................................ 38
2.37.1 Onboard Device Abstraction................................................................................................ 38
2.37.1.1 External Watchdog driver (not required) ...................................................................... 38
2.37.1.2 Watchdog Interface (not required) ............................................................................... 38
2.37.2 Memory Hardware Abstraction ........................................................................................... 38
2.37.2.1 External EEPROM driver (not required) ......................................................................... 39
2.37.2.2 External Flash driver (not required) .............................................................................. 39
2.37.2.3 EEPROM Abstraction (capable) ..................................................................................... 39
2.37.2.4 Flash EEPROM Emulation (capable) .............................................................................. 40
2.37.2.5 Memory Abstraction Interface (capable) ...................................................................... 40
2.37.3 Communication Hardware Abstraction................................................................................ 41
2.37.3.1 Ethernet Transceiver driver (required).......................................................................... 41
2.37.3.2 Ethernet Interface (required)........................................................................................ 42
2.37.3.3 Driver for ext. xx ASIC (not required) ............................................................................ 42
2.37.3.4 Driver for ext CC (not required) .................................................................................... 43
2.37.4 I/O Hardware Abstraction ................................................................................................... 43
2.37.4.1 Driver for ext. ADC ASIC (not required) ......................................................................... 43
2.37.4.2 Driver for ext. I/O ASIC (not required)........................................................................... 43
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
5 (148)
II
2.37.4.3 I/O signal interface (not required) ................................................................................ 44

2.37.5 Complex Drivers (not required) ........................................................................................... 44
2.38 Microcontroller Abstraction Layer .............................................................................................. 44
2.38.1 Microcontroller Drivers ....................................................................................................... 44
2.38.1.1 GPT driver (not required).............................................................................................. 44
2.38.1.2 Watchdog driver (not required) .................................................................................... 44
2.38.1.3 MCU driver (capable).................................................................................................... 45
2.38.1.4 Core Test (not required) ............................................................................................... 46
2.38.2 Memory Drivers .................................................................................................................. 46
2.38.2.1 Flash Test (not required)............................................................................................... 46
2.38.2.2 RAM Test (not required) ............................................................................................... 47
2.38.2.3 Internal Flash driver (capable) ...................................................................................... 47
2.38.2.4 Internal EEPROM driver (capable) ................................................................................. 48
2.38.3 Communication Drivers ....................................................................................................... 48
2.38.3.1 SPI Handler driver (capable) ......................................................................................... 48
2.38.3.2 Ethernet driver (capable) .............................................................................................. 49
2.38.4 I/O Drivers........................................................................................................................... 50
2.38.4.1 ICU driver (not required) .............................................................................................. 50
2.38.4.2 PWM driver (not required) ........................................................................................... 50
2.38.4.3 ADC driver (not required) ............................................................................................. 50
2.38.4.4 DIO driver (capable) ..................................................................................................... 51
2.38.4.5 Port driver (capable) ..................................................................................................... 52
2.39 Configurations for BSW modules required for Ethernet.............................................................. 53
2.39.1 [REQ] Eth ............................................................................................................................ 53
2.39.1.1 [REQ] EthConfigSet ....................................................................................................... 53
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
6 (148)
II
2.39.1.2 [REQ] EthGeneral ......................................................................................................... 59

2.39.2 [REQ] EthIf .......................................................................................................................... 62
2.39.2.1 [REQ] EthIfConfigSet..................................................................................................... 62
2.39.2.2 [REQ] EthIfGeneral ....................................................................................................... 68
2.39.3 [REQ] EthSm ........................................................................................................................ 73
2.39.3.1 [REQ] EthSmGeneral ..................................................................................................... 73
2.39.3.2 [REQ] EthSmNetwork ................................................................................................... 75
2.39.4 [REQ] EthTrcv ...................................................................................................................... 78
2.39.5 [REQ] SoAd .......................................................................................................................... 88
2.39.5.1 [REQ] SoAdDemEventParameterRefs ............................................................................ 88
2.39.5.2 [REQ] SoAdDoIpConfig.................................................................................................. 90
2.39.5.3 [REQ] SoAdGeneral....................................................................................................... 98
2.39.5.4 [REQ] SoAdPduRoute .................................................................................................. 105
2.39.5.5 [REQ] SoAdDemEventConnectionParameterRefs ........................................................ 116
2.39.6 [REQ] UdpNm.................................................................................................................... 125
2.39.6.1 [REQ] UdpNmGlobalConfig ......................................................................................... 126
2.40 Additional software components required for Global B Ethernet ............................................. 132
2.40.1 START/STOP Ethernet Communication .............................................................................. 132
2.40.1.1 START Ethernet Communication ................................................................................. 133
2.40.1.2 STOP Ethernet Communication................................................................................... 134
2.40.2 Application Callback .......................................................................................................... 135
2.40.2.1 Vehicle Identification (VIN) Application Callback ......................................................... 135
2.40.2.2 Entity Identification (EID) Information ........................................................................ 137
2.40.2.3 Group Identification (GID) Application Callback .......................................................... 139
2.40.2.4 Diagnostics Power Mode Application Callback ............................................................ 140
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
7 (148)
II
2.40.2.5 Routing Activation Authentification Application Callback ............................................ 142

2.40.2.6 Routing Activation Confirmation Application Callback................................................. 143
2.41 VLAN........................................................................................................................................ 145
3 Notes................................................................................................................................................ 145
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
8 (148)
II
Introduction
1.1 Document Updates and Revision History
This document can be revised and appear in several versions. The document will be classified in order to
allow identification of updates and versions.
1.2 Issue History

Each issue is given a number and date. A history shall be kept over all issues.
1.2.1 Revision Log

Revision
Date
Chapter
Description
0.22
April 19, 2012
All Chapters
First issue
Release 1.0
Sep 07, 2012
2.38
Configuration parameters
corrected
2.39
2.40
Release 1.1
Oct 12, 2012
Added SW-C requirements

Added Rationale to all sections
2.11
Modified OS from "Required"

module to "Capable"
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
9 (148)
II
rationale corrected
2.38
Added section for Vehicle

Identification application
callback details
2.39.2.1
Release 1.3
Dec 28,2012
2.32
2.38
Release 1.4
March 15,2013
July 26, 2013
rationale modified
Document name changed to
GB5401
2.38
Release 1.5
UDPNM modified from

Required to Not required
2.39.1.1
2.39.1.2
2.39.2.3
2.39.2.5
rationale modified (Clarified
the buffer length for
EthCtrlRxBufLenByte, added
description for
EthIfTrcvLinkStateChgFunction
IPV6 and IPV4)
sections added on SW-C
handling of Start, Stop,GID,
VIN, EID callbacks, Routing
activation authentification and
Routing activation
confirmation callbacks.
2.39.2.6
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
10 (148)
Release 1.6
Aug 09,2013
Release 1.7
May 19, 2014
Reg no
Info Class
II
1.2
Added revision history
2.7
Added Section 2.7 on

applicable RFCs
2.31
NMIF changed to not required
2.37.2, 2.38.2
Memory modules changed to

capable
2.38.4.4
Activation Line handling

through ICU is changed to DIO
2.39
Configuration parameter
changes as part of review
1.3 Team Membership

The following people are responsible for GM Global B serial data requirements for AUTOSAR Ethernet:
1.3.1 Serial Data

Name
Organization
Protocol
Mark Hu
GMNA
Ethernet
Rajesh Thazhemadathil
GMTCI
Ethernet
Resmy Francis
GMTCI
Ethernet
Sinu Isac
GMTCI
Ethernet
Harald Eisele
GME
GME Serial Data Architecture
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
11 (148)
Ken Orlando
GMNA
Reg no
Info Class
II
GMNA Serial Data Architecture
1.3.2 Contracted Experts
1.4 Document Scope

This specification identifies which AUTOSAR modules are required to perform Ethernet serial data
communications for Global B diagnostics over IP (DOIP), provides a description and rationale for each of
the required modules, and specifies a default value for AUTOSAR module configurations classified as GM
mandatory.
Ethenet Software Strategy specification captures HOW the requirements of the Ethenet Communication
Strategy can be implemented. The Ethenet Software Strategy require the entire set of features within
the implementation or will identify which portions of the implementation are relevant to General
Motors (eg. data access interfaces, activation/deactivation interfaces, notification interfaces).
Configurable parameters (eg. feature enable flags, timer values, payload values) are analyzed and where
possible, a standard value is specified in the Ethenet Software Strategy.
1.5 Requirement Wording Conventions

Within this document the following conventions are applied:
Shall a binding requirement of the component or subsystem within the scope of this
specification.
Must a requirement of a components or subsystem outside of the scope of this specification.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
12 (148)
II
Will a result of an immutable law of physics.
Withstand all functions of a component perform as specified during and after exposure to the
defined condition without inadvertent actuation of its outputs.
Should denotes a preference or desired conformance
G-Req identifies a general requirement. The text in this paragraph is considered as a formal
requirement. General requirements are applicable to all implementations, i.e. all car lines, platforms
etc.
I-Req identifies an Implementation requirement. The text in this paragraph is considered as a
formal requirement. Implementation requirements may be applicable to a specific implementation,
e.g. car line, platform etc. Implementation requirements may be moved to an implementation
specification at a later time
Rationale: - describes the rationale behind a requirement. Ultimately the rationale is described in
such a way that a reader of the document can understand the motivation for a specific requirement,
even if the reader was not part of the discussion or creation of the requirement.
Applicable Documents
2.1 Precedence Order
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
13 (148)
II
In case of conflict between the text of this specification and the documents cited herein, the text of this
specification takes precedence. Nothing in this specification, however, supersedes applicable laws and
regulations unless a specific exemption has been obtained.
2.2 Government Regulations and Documents

N/A
2.3 General Motors Documents

Document
Number
Document
Reference
Document Title
Document
Version
GB5400
Ethernet Communication System Communication

Strategy Specification
Release 1.21
GB8004
GM AUTOSAR Specification Addendum:Required

RFC List
V1.0 Rev 2
Table 2: General Motors Documents
2.4 Industry Documents

2.4.1 AUTOSAR Consortium Documents
Document Document Document Title
Number
Reference
Document
Version
Autosar R4.0.3 Specifications
GM Confidential
R4.0.3
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
14 (148)
II
Table 3: AUTOSAR Consortium Documents
2.4.2 OSEK Documents

Document Document Document Title
Number
Reference
Document
Version
Table 5: OSEK Documents
2.4.3 ISO Documents

Document Document
Number
Reference
Document Title
Document
Version
13400-1
W402 ISO_FDIS_13400-1__E__DoIP_rev_on.pdf
Draft
13400-2
Draft
13400-3
Draft
Table 6: ISO Documents
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
15 (148)
II
2.5 Other Documents

Document
Number
Document
Reference
Document Title
Document
Version
RFC768
User Datagram Protocol
RFC791
Internet Protocol
RFC 792
Internet Control Message Protocol
RFC793
Transmission Control Protocol
RFC3315
Dynamic Host Configuration Protocol for IPv6

(DHCPv6)
RFC4443
Internet Control Message Protocol (ICMPv6) for the

Internet Protocol Version 6 (IPv6) Specification
RFC826
Address Resolution Protocol
RFC4861
Neighbor Discovery for IP version 6 (IPv6)
RFC2460
Internet Protocol Version 6 (IPv6) Specification
RFC2461
Neighbor Discovery for IP Version 6 (IPv6)
Table 7: Other Documents
2.6 AUTOSAR version

ID : ETHSW-247
[REQ] Global B serial data requirements for AUTOSAR Ethernet shall be based on AUTOSAR version
4.0.3.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
16 (148)
II
2.7 Modifications to AUTOSAR

As part of GM's AUTOSAR Strategy a subset of open issues not resolved in AUTOSAR Rel 4.0.3
specification and addressed by AUTOSAR Consortium in later releases have been identified. The
complete
list of RfCs relevant for GM's strategy identified relative to AUTOSAR Release 4.0.3 is aggregated in
"GB8004-GM AUTOSAR Specification Addendum:Required Rfc List". Applicability of the RfCs to a specific
ECU will be based on the ECU's Deployment characteristics (eg: AUTOSAR Type definition,
Communication Channel/BSW Modules used etc).
2.8 BSW modules required for Global
Ethernet
[NOTE] The following figure summarizes which AUTOSAR BSW modules are required to perform Global
B Ethernet serial data communication.
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
17 (148)
GM Confidential
Reg no
Info Class
II
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
18 (148)
II
[NOTE] The following sections provide a description and rationale of each of the AUTOSAR BSW
modules requried to perform Global B Ethernet serial data communication.
2.9 RTE (required)

ID : ETHSW-256
[REQ] RTE shall be required to perform Global B Ethernet serial data communication.
[RATIONALE] RTE is required to implement activation line and DCM services. Application retains
abstraction from BSW by using the standard RTE interface to either START or STOP the Ethernet
communications based on activation line conditions. If the application is able to perform a requested
diagnostic task, application retains abstraction from BSW by using the standard RTE function calls and
inform BSW about the progress of the requested diagnostic task.
2.10 Services Layer

2.11 System Services
2.12 OS (capable)
ID : ETHSW-262
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
19 (148)
II
[REQ] The software stack shall provide the capability of the OS but implementing as defined in AUTOSAR
is not required.
ID : ETHSW-4684
[REQ] The software stack shall implement the OS standard interfaces as defined in AUTOSAR
ID : ETHSW-4685
[REQ] The software stack shall process inputs and provide outputs in order to fulfill the needs of the OS
standard interfaces to the GM required BSW modules.
[NOTE] To classify the AUTOSAR OS, here are the basic features: the OS
is configured and scaled statically

is amenable to reasoning of real-time performance
provides a priority-based scheduling policy
provides protective functions (memory, timing etc.) at run-time
is host able on low-end controllers and without external resources
Interaction with the RTE
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
20 (148)
II
The configuration of an AUTOSAR system maps the runnables of a software component to

(one or more) tasks that are scheduled by the operating system
A software component is therefore implemented as runnables executing within the body of a task,
or set of tasks, only.
The RTE provides the runtime interface between runnables and the basic software modules.
The basic software modules also comprise a number of tasks and ISRs that are scheduled by the
operating system.
[RATIONALE] The runnables of Ethernet software components are scheduled by the operating system.
DOIP over Ethernet required interrupt mode at Ethernet datalink layer. So Ethernet transmit, receive,
and error interrupts at Ethernet datalink layer are scheduled by the operating system. In addition to
that, DOIP over Ethernet required polling mode at TCP layer and the Mainfunction time base for polling
mode at TCP layer is also scheduled by the operating system. The stack for Ethernet application software
components are allocated by the OS.
2.13 EcuM Flexible (required)

ID : ETHSW-275
[REQ] ECU State Manager shall be required to perform Global B Ethernet serial data communication.
[NOTE] The ECU Manager module is a basic software module that manages common aspects of ECU
states. Specifically, the ECU Manager module
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
21 (148)
II
Initializes and de-initializes the OS, the SchM and the BswM as well as all basic software driver
modules.
Configures the ECU for SLEEP and SHUTDOWN when requested.
manages all wakeup events on the ECU

The ECU Manager module provides the wakeup validation protocol to distinguish real wakeup events
from erratic ones.
Thus with Flexible ECU Management, most ECU states are no longer implemented in the ECU Manager
module itself. In general, the ECU Manager module is only active when the generic mode management
facilities are unavailable in:
Early STARTUP phases,

Late SHUTDOWN phases,
SLEEP phases where the facilities are locked out by the scheduler
Communication allowed and shutdown of ECU) is handled by EcuM-Flex together with BswM
[RATIONALE] The EcuM initializes and de-initializes all the Ethernet specific BSW modules. The Ethernet
wakeup source is configured in the EcuM. The ECU State Manager validates the real wakeup events
from erratic ones.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
22 (148)
II
2.14 ComM (required)

ID : ETHSW-287
[REQ] Communication Manager shall be required to perform Global B Ethernet serial data
communication.
[NOTE] The Communication Manager Module (COM Manager, ComM) is a component of the Basic
Software (BSW).
It is a Resource Manager, which encapsulates the control of the underlying communication services. The
ComM module controls basic software modules relating to communication and not software
components or runnable entities. The ComM module collects the bus communication access requests
from communication requestors
The purpose of the ComM module is:
1. Simplifying the usage of the bus communication stack for the user. This includes a simplified
network management handling.
2. Coordinating the availability of the bus communication stack (allow sending and receiving of
signals) of multiple independent software components on one ECU.
3. Offer an API to disable sending of signals to prevent the ECU from (actively) waking up the
communication bus.
Comment: In DoIP over ethernet activation line is the wakeup source.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
23 (148)
II
4. Controlling of more than one communication bus channel of an ECU by implementing a channel
state machine for every channel.
Comment: The ComM module requests a Communication Mode from the corresponding Bus State
Manager module. The actual bus states are controlled by the corresponding Bus State Manager
module.
5. Offering the possibility to force an ECU that keeps the bus awake to the No Communication
mode
6. Simplifying the resource management by allocating all resources necessary for the requested
Communication Mode.
Comment: E.g. check if communication is allowed when a user requests Full Communication mode,
and prevent the ECU from shutdown during communication.
[RATIONALE] The full communication and no communication states of each Ethernet channel are
handled by ComM based on the request from the Application. Application evaluates the activation line
conditions and issues either full communication or no communication commands to the ComM
through the standard RTE interface. A ComM user should be defined for each Ethernet channel which is
designated to request or release the communication mode.
2.15 Dem (not required)

ID : ETHSW-301
[REQ] Diagnostic Event Manager shall not be required to perform Global B Ethernet serial data
communication.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
24 (148)
II
2.16 FIM (not required)

ID : ETHSW-303
[REQ] Function Inhibition Manager shall not be required to perform Global B Ethernet serial data
communication.
2.17 Det (not required)

ID : ETHSW-305
[REQ] Development Error Tracer shall not be required to perform Global B Ethernet serial data
communication.
2.18 DLT (not required)

ID : ETHSW-307
[REQ] Diagnostic Log & Trace shall not be required to perform Global B Ethernet serial data
communication.
2.19 StbM (not required)

ID : ETHSW-309
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
25 (148)
II
[REQ] Synchronized Timebase Manager shall not be required to perform Global B Ethernet serial data
communication.
2.20 Watchdog Manager (not required)

ID : ETHSW-311
[REQ] Watchdog Manager shall not be required to perform Global B Ethernet serial data
communication.
2.21 BswM (required)

ID : ETHSW-313
[REQ] Basic Software Mode Manager shall be required to perform Global B Ethernet serial data
communication.
[NOTE] The BSW Mode Manager is the module that implements the part of the Vehicle Mode
Management and Application Mode Management concept that resides in the BSW. Its responsibility is
to arbitrate mode requests from application layer SW-Cs or other BSW modules based on simple rules,
and perform actions based on the arbitration result.
The BswM receives mode requests from the SW-Cs via the RTE. Mode Switch Notifications are also
propagated to the SW-Cs via the RTE.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
26 (148)
II
Has the reference to the Communication ManagerPNC handle of the Partial Network Cluster that the
request corresponds to
The BswM realizes two functionalities Mode Arbitration and Mode Control to allow the application
of an Application Mode Management and a Vehicle Mode Management
The BswM propagates user requests to the ComM module, if configured in the action lists of BswM
to be able to request ComM modes via BswM.
The BswM controls the PDU Groups in the AUTOSAR Communication Module (COM), if the call of
Com_IpduGroupControl is configured in the action list
Starting and Stopping of I-PDU groups in COM are handled in BSWM

The handling of I-PDU Groups in COM is performed by the BswM. As a part of I-PDU group
start/stop it is possible to have the included signal values reset to their corresponding initialization
values.
BswM handles enable and disable of deadline monitoring of signals in COM.
BswM can also trigger transmission of an I-PDU
Mode Switch Indications originating from the ComM go through the BswM for further propagation
to the SW-Cs
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
27 (148)
II
[RATIONALE] Mode Switch Indications originating from the EthSm goes to the BswM. BswM notifies the
mode switch indications to the application SW-Cs in the upper layer based on the confirmation from the
lower layer.
2.22 Memory Services

2.23 NVRAM Manager (capable)
ID : ETHSW-329
[REQ] The software stack shall provide the capability of the NVRAM Manager but implementing as
defined in AUTOSAR is not required.
ID : ETHSW-4686
[REQ] The software stack shall implement the NVRAM Manager standard interfaces as defined in
AUTOSAR
ID : ETHSW-4687
[REQ] The software stack shall process inputs and provide outputs in order to fulfill the needs of the
NVRAM Manager standard interfaces to the GM required BSW modules.
[NOTE] The NvM module provide services to ensure the data storage and maintenance of NV (non
volatile) data according to their individual requirements in an automotive environment. The NvM
module shall be able to administrate the NV data of an EEPROM and/or a FLASH EEPROM emulation
device.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
28 (148)
II
The NvM module provide the required synchronous/asynchronous services for the management and the
maintenance of NV data (init/read/write/control).
The ComM module uses the NVRAM Manager to store and read non-volatile data.
The NVRAM Manager must be initialized after a power up or reset of the ECU.
It must be initialized before ComM, as when ComM is initialized, ComM assumes that NVRAM is
ready to be used, and that it can read back non-volatile configuration data. When ComM is deinitialized, it writes non-volatile data to NVRAM.
The NvM module reports the state of its blocks to the BswM via integration code registered as
NvM callbacks.
BswM have actions causing the NvM to read and write all blocks during startup and shutdown.
[RATIONALE] Application SWC of Ethernet Gateway ECU uses NVRAM Manager module for retrieving
the Vehicle Identification Number (VIN), Entity Identification Number (EID) and Group Identification
Number (GID) from Non-Volatile memory. Application SWC retrieves these data, whenever it wants to
send the Vehicle Announcement message (0x0004). In addition to that application SWC retrieves these
data, whenever it gets Vehicle Identification Request (0x0001) / Vehicle Identification Request with EID
(0x0002) / Vehicle Identification Request with VIN (0x0003) from the offboard or onboard testers.
2.24 Communication Services
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
29 (148)
II
2.25 COM (Not required)

ID : ETHSW-338
[REQ] COM shall not be required to perform Global B Ethernet serial data communication.
[NOTE] Within the AUTOSAR Layered Architecture the AUTOSAR COM module is placed between RTE
and the PDU Router
The RTE uses the capabilities of the AUTOSAR COM module to send and receive signals.
Main Features:
Provision of signal oriented data interface for the RTE

Packing of AUTOSAR signals to I-PDUs to be transmitted
Unpacking of received I-PDUs and provision of received signals to RTE
Routing of signals from received I-PDUs into I-PDUs to become transmitted
Routing of signal groups from received I-PDUs into I-PDUs to become transmitted
Communication transmission control (start/ stop of I-PDU groups)
GM Confidential
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
30 (148)
II
Replications of send requests

Guarantee of minimum distances between transmit I-PDUs
Identify the use and importance of obligation and expenditure plans.
Filter mechanisms for incoming signals
Different notification mechanisms
Provision of init values and update indications
Byte order conversion
Sign extension
Support of two different transmission modes per I-PDU
Signal based gateway

Support of large and dynamic length data types
Support of I-PDU counters and I-PDU replication
GM Confidential
Info Class
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
31 (148)
II
2.26 Dcm (not required)

ID : ETHSW-361
[REQ] Diagnostic Communication Manager shall not be required to perform Global B Ethernet serial
data communication.
2.27 Debugging (not required)

ID : ETHSW-363
[REQ] Debugging shall not be required to perform Global B Ethernet serial data communication.
2.28 XCP (not required)

ID : ETHSW-365
[REQ] XCP shall not be required to perform Global B Ethernet serial data communication.
2.29 PduR (required)

ID : ETHSW-367
[REQ] PDU Router shall be required to perform Global B Ethernet serial data communication.
[NOTE] The PDU Router module provides services for routing of I-PDUs (Interaction Layer Protocol Data
Units) using the following module types:
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
32 (148)
II
Communication interface modules (e.g. Com, LinIf, CanIf, CanNm, FrIf and FrNm)
Transport Protocol modules (e.g. J1939, LinTp [part of LinIf], CanTp, FrTp)
The routing of I-PDUs are made statically by the I-PDU identifier, no I-PDUs are routed dynamically in
run-time or dependent on contents.
[RATIONALE] PduR routes the Ethernet specific PDU from DCM in the upper layer to SoAd in the lower
layer and notify the transmission confirmation / receive indication of PDU based on the
confirmation/indication from SoAd in the lower layer. PduR performs TP gateway, so that data can be
routed between Ethernet to CAN/FR or vice versa.
2.30 IpduM (not required)

ID : ETHSW-374
[REQ] IPDU Multiplexer shall not be required to perform Global B Ethernet serial data communication.
2.31 NmIf (not required)

ID : ETHSW-376
[REQ] NM Interface shall not be required to perform Global B Ethernet serial data communication.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
33 (148)
II
2.32 Ethernet SM (required)

ID : ETHSW-390
[REQ] Ethernet State Manager shall be required to perform Global B Ethernet serial data
communication.
[RATIONALE] The main task of the Ethernet State Manager can be summarized as follows:
The Ethernet State Manager provide an abstract interface to the AUTOSAR Communication
Manager to startup or shutdown the communication on an Ethernet cluster.
The Ethernet State Manager does not directly access the Ethernet hardware (Ethernet
Communication Controller and Ethernet Transceiver), but by means of the Ethernet Interface. The
Ethernet Interface redirects the request to the appropriate driver module.
The Ethernet State Manager controls the actual states of the Ethernet bus that correspond to a
Communication Mode of the ComM module. The ComM module requests a Communication Mode from
the Ethernet State Manager and the Ethernet State Manager maps the Communication Mode to a bus
state.
2.33 UDP Nm (not required)

ID : ETHSW-396
[REQ] UdpNm shall not be required to perform Global B Ethernet serial data communication.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
34 (148)
II
The UDP Network Management (UdpNm) function provides an adaptation between Network
Management Interface (Nm) and a TCP/IP Stack (TCP/IP)
2.34 Socket Adapter (required)

ID : ETHSW-401
[REQ] SoAd shall be required to perform Global B Ethernet serial data communication.
[RATIONALE] SoAd is the module between the PDU Router and a TCP/IP protocol stack. The main
purpose of the SoAd module is
To create an interface between the PDU Router and a socket based TCP/IP stack.
It will map I-PDU IDs to socket connections and vice versa. SoAd is not a TP, as it does not provide
segmentation or flow control, all of these functionalities are expected to be implemented by the
TCP/IP stack.
However, some segmentation of TCP stream data in the receive direction will be required.
SoAd will detect and handle errors resulting from TCP/IP stack operations
The SoAd is expected to have protocol parser extensions using its interfaces towards the TCP/IP stack
and towards the PDU Router.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
35 (148)
II
2.35 DoIP (required)

ID : ETHSW-409
[REQ] DoIP shall be required to perform Global B Ethernet serial data communication.
[RATIONALE] DoIP is somewhat different from the AUTOSAR Signal Transmission use-case described
above as these connections cannot be fully pre-configured and are not active at all times of normal
operation, but only during service. This requires a more dynamic approach to socket handling as
described above. This is why the SoAd and DoIP share the same interfaces to the TCP/IP stack and other
AUTOSAR modules, but handles their socket connections separately.
Use Cases
Autosar Signal Transmission

Diagnostics over IP (DoIP)
UDP Network Management (UdpNm)
XCP on Ethernet
2.36 Internet Protocol Stack (required)

ID : ETHSW-4660
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
36 (148)
II
[REQ] Internet Protocol Stack shall be required to perform Global B Ethernet serial data communication
using Adapted COTS TCP/IP stack.
[RATIONALE] Internet Protocol Stack is placed the heart of Ethernet stack. All the Ethernet diagnostic
communication are performed using the Internet Protocol Stack.
2.36.1 UDP (required)

ID : ETHSW-418
[REQ] UDP shall be required to perform Global B Ethernet serial data communication using Adapted
COTS TCP/IP stack. UDP shall be implemented as specified in IETF RFC 768
2.36.2 TCP (required)

ID : ETHSW-420
[REQ] TCP shall be required to perform Global B Ethernet serial data communication using Adapted
COTS TCP/IP stack. TCP shall be implemented as specified in IETF RFC 793.
2.36.3 DHCP (required))

ID : ETHSW-422
[REQ] DHCP shall be required to perform Global B Ethernet serial data communication. It is required to
support the remote diagnostics by connecting to service and maintenance center via plug-in Ethernet
access point on a remote location. DHCP shall be implemented using Adapted COTS TCP/IP stack
compliant to RFC 3315, RFC 2131.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
37 (148)
II
2.36.4 ARP (required)

ID : ETHSW-424
[REQ] ARP shall be required to perform Global B Ethernet serial data communication using Adapted
COTS TCP/IP stack. ARP shall be implemented as specified in RFC826.
2.36.5 IP (required)
ID : ETHSW-426
[REQ] IP shall be required to perform Global B Ethernet serial data communication using Adapted COTS
TCP/IP stack
ID : ETHSW-4699
[REQ] The IP layer should support dual IP (IPv4 & IPv6) capability as specified in IETF RFC4213
2.36.6 ICMP (required)

ID : ETHSW-428
[REQ] ICMP shall be required to perform Global B Ethernet serial data communication using Adapted
COTS TCP/IP stack. ICMP shall be implemented as specified in RFC 792.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
38 (148)
II
2.36.7 NDP (required)

ID : ETHSW-430
[REQ] NDP shall be required to perform Global B Ethernet serial data communication to support DualIP
stack using Adapted COTS TCP/IP stack. NDP shall be implemented as specified in RFC 4861.
2.37 ECU Abstraction Layer

2.37.1 Onboard Device Abstraction
2.37.1.1 External Watchdog driver (not required)
ID : ETHSW-434
[REQ] External Watchdog driver shall not be required to perform Global B Ethernet serial data
communication.
2.37.1.2 Watchdog Interface (not required)

ID : ETHSW-436
[REQ] Watchdog Interfaces shall not be required to perform Global B Ethernet serial data
communication.
2.37.2 Memory Hardware Abstraction
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
39 (148)
II
2.37.2.1 External EEPROM driver (not required)

ID : ETHSW-439
[REQ] External EEPROM drivers shall not be required to perform Global B Ethernet serial data
communication.
2.37.2.2 External Flash driver (not required)

ID : ETHSW-441
[REQ] External Flash drivers shall not be required to perform Global B Ethernet serial data
communication.
2.37.2.3 EEPROM Abstraction (capable)

ID : ETHSW-443
[REQ] The software stack shall provide the capability of the EEPROM Abstraction but implementing as
defined in AUTOSAR is not required
ID : ETHSW-5003
[REQ] The EEPROM Abstraction (EA) abstracts from the device specific addressing scheme and
segmentation and provides the upper layers with a virtual addressing scheme and segmentation as well
as a virtually unlimited number of erase cycles.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
40 (148)
II
Number (GID) from Non-Volatile memory. The FEE maps the virtual address space assigned by NVM to
the physical address space.
2.37.2.4 Flash EEPROM Emulation (capable)

ID : ETHSW-445
[REQ] The software stack shall provide the capability of the Flash EEPROM Emulation but implementing
as defined in AUTOSAR is not required
ID : ETHSW-5004
[REQ] The Flash EEPROM Emulation (FEE) abstracts from the device specific addressing scheme and
segmentation and provide the upper layers with a virtual addressing scheme and segmentation as well
as a virtually unlimited number of erase cycles.
Number (GID) from Non-Volatile memory. The FEE maps the virtual address space assigned by NVM to
the physical address space.
2.37.2.5 Memory Abstraction Interface (capable)

ID : ETHSW-447
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
41 (148)
II
[REQ] The software stack shall provide the capability of the Memory Abstraction Interface but
implementing as defined in AUTOSAR is not required
Number (GID) from Non-Volatile memory. This module allows the NVRAM manager to access several
memory abstraction modules (FEE or EA modules).
2.37.3 Communication Hardware Abstraction

2.37.3.1 Ethernet Transceiver driver (required)
ID : ETHSW-450
[REQ] Ethernet Transceiver driver shall be required to perform Global B Ethernet serial data
communication.
[RATIONALE] Provide to the upper layer (Ethernet Interface) a hardware independent interface
comprising multiple equal transceivers. This interface is uniform for all transceivers. Thus, the upper
layer (Ethernet Interface) may access the underlying bus system in a uniform manner. The configuration
of the Ethernet Transceiver Driver however is bus specific, since it takes into account the specific
features of the communication transceiver.
The Ethernet Interface module doesnt take care of configuring Ethernet Transceiver Driver but requires
its preceding initialization and configuration
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
42 (148)
II
2.37.3.2 Ethernet Interface (required)

ID : ETHSW-454
[REQ] Ethernet Interface shall be required to perform Global B Ethernet serial data communication.
[RATIONALE] The main task of the Ethernet Interface
Provide to upper layers a hardware independent interface to the Ethernet Communication System
comprising multiple different Ethernet controllers and transceivers.
This interface is uniform for all Ethernet controllers and transceivers.
Thus, the upper layers (Internet Protocol, Address Resolution Protocol) may access the underlying
bus system in a uniform manner.
The Ethernet Interface does not directly access the Ethernet hardware (Ethernet Communication
Controller and Ethernet Transceiver) but by means of one or more hardware-specific driver
modules.
The EthSM uses the API of the EthIf to initialize the Ethernet Communication Hardware and to control
the operating modes of the Ethernet Controllers and Ethernet Transceivers assigned to the Ethernet
Networks.
2.37.3.3 Driver for ext. xx ASIC (not required)

ID : ETHSW-462
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
43 (148)
II
[REQ] Driver for ext. xx ASIC shall not be required to perform Global B Ethernet serial data
communication.
2.37.3.4 Driver for ext CC (not required)

ID : ETHSW-464
[REQ] Driver for ext CC shall not be required to perform Global B Ethernet serial data communication.
2.37.4 I/O Hardware Abstraction

2.37.4.1 Driver for ext. ADC ASIC (not required)
ID : ETHSW-467
[REQ] Driver for ext. ADC ASIC shall not be required to perform Global B Ethernet serial data
communication.
2.37.4.2 Driver for ext. I/O ASIC (not required)

ID : ETHSW-469
[REQ] Driver for ext. I/O ASIC shall not be required to perform Global B Ethernet serial data
communication.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
44 (148)
II
2.37.4.3 I/O signal interface (not required)

ID : ETHSW-471
[REQ] I/O signal interface shall not be required to perform Global B Ethernet serial data communication.
2.37.5 Complex Drivers (not required)

ID : ETHSW-473
[REQ] Complex Drivers shall not be required to perform Global B Ethernet serial data communication.
2.38 Microcontroller Abstraction Layer

2.38.1 Microcontroller Drivers
2.38.1.1 GPT driver (not required)
ID : ETHSW-477
[REQ] GPT driver shall not be required to perform Global B Ethernet serial data communication.
2.38.1.2 Watchdog driver (not required)

ID : ETHSW-479
[REQ] Watchdog driver shall not be required to perform Global B Ethernet serial data communication.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
45 (148)
II
2.38.1.3 MCU driver (capable)

ID : ETHSW-481
[REQ] The software stack shall provide the capability of the MCU driver but implementing as defined in
AUTOSAR is not required
ID : ETHSW-4689
[REQ] The software stack shall implement the MCU driver standard interfaces as defined in AUTOSAR
ID : ETHSW-4688
MCU driver standrad interfaces to the GM required BSW modules.
[NOTE] The MCU driver provides services for basic microcontroller initialization, power down
functionality, reset and microcontroller specific functions required by other MCAL software modules
MCU driver Features:
Initialization of MCU clock, PLL, clock prescalers and MCU clock distribution
Initialization of RAM sections
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
46 (148)
II
Activation of C reduced power modes

Activation of a C reset
Provides a service to get the reset reason from hardware
[RATIONALE] The clock [kHz] that is inputting to the MAC must be configured in the MCU module to get
the proper MAC speed. The clock which is set for the MAC is used for the calculation of the baud rate
registers.
2.38.1.4 Core Test (not required)

ID : ETHSW-490
[REQ] Core Test shall not be required to perform Global B Ethernet serial data communication.
2.38.2 Memory Drivers

2.38.2.1 Flash Test (not required)
ID : ETHSW-493
[REQ] Flash Test shall not be required to perform Global B Ethernet serial data communication.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
47 (148)
II
2.38.2.2 RAM Test (not required)

ID : ETHSW-495
[REQ] RAM Test shall not be required to perform Global B Ethernet serial data communication.
2.38.2.3 Internal Flash driver (capable)

ID : ETHSW-497
[REQ] The software stack shall provide the capability of the Internal Flash Driver but implementing as
ID : ETHSW-5006
[REQ] The flash driver provides services for reading, writing and erasing flash memory and a
configuration interface for setting / resetting the write / erase protection if supported by the underlying
hardware.
ID : ETHSW-5013
[REQ] The Flash module shall map the address and length parameters for the read, write, erase and
compare functions as virtual addresses to the physical addresses according to the physical structure of
the flash memory areas.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
48 (148)
II
Number (GID) from Non-Volatile (EEPROM/ Flash) memory.
2.38.2.4 Internal EEPROM driver (capable)

ID : ETHSW-499
[REQ] The software stack shall provide the capability of the Internal EEPROM Driver but implementing as
ID : ETHSW-5008
[REQ] The EEPROM driver provides services for reading, writing, erasing to/from an EEPROM.
Number (GID) from Non-Volatile (EEPROM/ Flash) memory.
2.38.3 Communication Drivers

2.38.3.1 SPI Handler driver (capable)
ID : ETHSW-502
[REQ] The software stack shall provide the capability of the SPI Handler Driver but implementing as
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
49 (148)
II
[RATIONALE] When the Ethernet switches are integrated to the software stack, SPI driver is used to
access the switches.
2.38.3.2 Ethernet driver (capable)

ID : ETHSW-504
[REQ] The software stack shall provide the capability of the Ethernet driver but implementing as defined
in AUTOSAR is not required
ID : ETHSW-4690
[REQ] The software stack shall implement the Ethernet driver standard interfaces as defined in
AUTOSAR
ID : ETHSW-4691
Ethernet driver standrad interfaces to the GM required BSW modules
[RATIONALE] The main task of the Ethernet Driver:
Provide to the upper layer (Ethernet Interface) a hardware independent interface comprising
multiple equal controllers.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
50 (148)
II
This interface is uniform for all controllers. Thus, the upper layer (Ethernet Interface) may access
the underlying bus system in a uniform manner.
The interface provides functionality for initialization, configuration and data transmission.
The configuration of the Ethernet Driver however is bus specific, since it takes into account the
specific features of the communication controller
2.38.4 I/O Drivers
2.38.4.1 ICU driver (not required)
ID : ETHSW-4693
[REQ] ICU driver shall not be required to perform Global B Ethernet serial data communication.
2.38.4.2 PWM driver (not required)

ID : ETHSW-515
[REQ] PWM driver shall not be required to perform Global B Ethernet serial data communication.
2.38.4.3 ADC driver (not required)

ID : ETHSW-517
[REQ] ADC driver shall not be required to perform Global B Ethernet serial data communication.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
51 (148)
II
2.38.4.4 DIO driver (capable)

ID : ETHSW-519
[REQ] The software stack shall provide the capability of the DIO driver but implementing as defined in
ID : ETHSW-4694
[REQ] The software stack shall implement the DIO driver standard interfaces as defined in AUTOSAR
ID : ETHSW-4696
[REQ] The software stack shall process inputs and provide outputs in order to fulfill the needs of the DIO
driver standrad interfaces to the GM required BSW modules
[RATIONALE] DIO module is used to access Ethernet transceiver device connected via ports.
The DIO Driver provides services for reading and writing to/from
DIO Channels (Pins)

DIO Ports
DIO Channel Groups
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
52 (148)
II
DIO driver module works on pins and corresponding ports which are configured by the PORT driver.
Global B Ethernet serial data communications requires SW-C to START/STOP Ethernet communications
based on Activation line conditions. Activation line is used for the wakeup purpose, since the bus
wakeup is not allowed in the Global B Ethernet serial data communication. Activation line is connected
to the DIO pin and the application swc reads the pin status to detect wakeup from activation line which
is connected to the external tester or to the onboard tester.
2.38.4.5 Port driver (capable)

ID : ETHSW-526
[REQ] The software stack shall provide the capability of the Port driver but implementing as defined in
ID : ETHSW-4697
[REQ] The software stack shall implement the Port driver standard interfaces as defined in AUTOSAR
ID : ETHSW-4698
Port driver standrad interfaces to the GM required BSW modules
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
53 (148)
II
2.39 Configurations for BSW modules required for Ethernet

ID : ETHSW-528
[REQ] The Controller Supplier shall use the following configuration values to configure their AUTOSAR
stack. Any unspecified configuartion values shall be the responsibility of the controller supplier.
ID : ETHSW-1081
2.39.1 [REQ] Eth

Description
Configuration of the Eth (Ethernet Driver) module.. The value of this parameter shall
be defined in a project specific document.
Type
Range
Value
Rationale
ECU May implement Ethernet Module depending on requirement.
ID : ETHSW-1098
2.39.1.1 [REQ] EthConfigSet

Description
All included containers and parameters that may be part of a multiple configuration
set.
Type
Range
Value
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
54 (148)
Rationale
Reg no
Info Class
II
This container is AUTOSAR mandatory container if the Ethernet is enabled. But ECU
may have multiple configuration set.
ID : ETHSW-1115
2.39.1.1.1 [REQ] EthCtrlConfig

Description
Configuration of the individual controller.
Type
Range
Value
Rationale
This container is AUTOSAR mandatory container if the Ethernet is enabled. But ECU
may have multiple configuration set.
ID : ETHSW-1132
2.39.1.1.1.1 [REQ] EthCtrlEnableMii

Description
Enables / Disables Media Independent Interface (MII) for transceiver access. The
value of this parameter shall be 1 for GM.
Type
BOOL
Range
Value
Rationale
Must be enabled for Transciever usage (Read and Write).
ID : ETHSW-1149
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
55 (148)
II
2.39.1.1.1.2 [REQ] EthCtrlEnableRxInterrupt

Description
Enables / Disables receive interrupt. The value of this parameter shall be 1 for GM.
Type
BOOL
Range
Value
Rationale
Must be enabled and equal for all Ethernet based controllers, based on timing
experiments
ID : ETHSW-1166
2.39.1.1.1.3 [REQ] EthCtrlEnableTxInterrupt

Description
Enables / Disables transmit interrupt. The value of this parameter shall be 1 for GM.
Type
BOOL
Range
Value
Rationale
Must be enabled and equal for all Ethernet based controllers, based on timing
experiments
ID : ETHSW-1183
2.39.1.1.1.4 [REQ] EthCtrlIdx

Description
Specifies the instance ID of the configured controller.
Type
INT
Range
0 - 255
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
56 (148)
II
Value
Rationale
Let T1 to decide the instance ID The value of this parameter is not controlled by GM
and is left to the discretion of the supplier.
ID : ETHSW-1200
2.39.1.1.1.5 [REQ] EthCtrlRxBufLenByte

Description
Limits the maximum receive buffer length (frame length) in bytes. The value of this
parameter is recommended as 1522 (Tag based VLAN) or 1518 (Port based) including
header information for GM.
Type
INT
Range
0 - 1522
Value
1522 (Tag based VLAN) or 1518 (Port based) including header information
Rationale
This parameter includes 1500 bytes of payload for 802.3 hardware as well as the full
Ethernet Header. AUTOSAR calculates full Ethernet Header inclusive of 4 bytes of
VLAN tag.
ID : ETHSW-1217
2.39.1.1.1.6 [REQ] EthCtrlTxBufLenByte

Description
Limits the maximum transmit buffer length (frame length) in bytes. The value of this
parameter is recommended as 1522 (Tag based VLAN) or 1518 (Port based) including
header information for GM.
Type
INT
Range
0 - 1522
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
57 (148)
II
Value
1522 (Tag based VLAN) or 1518 (Port based) including header information
Rationale
This parameter includes 1500 bytes of payload for 802.3 hardware as well as the full
Ethernet Header. AUTOSAR calculates full Ethernet Header inclusive of 4 bytes of
VLAN tag.
ID : ETHSW-1234
2.39.1.1.1.7 [REQ] EthRxBufTotal

Description
Configures the number of receive buffers.
Type
INT
Range
0 - 255
Value
Rationale
For the receive path, temporarily GM recommends to use double buffer structure
that makes more than 2 buffers unnecessary. The value of this parameter is not
controlled by GM and is left to the discretion of the supplier.
ID : ETHSW-1251
2.39.1.1.1.8 [REQ] EthTxBufTotal

Description
Configures the number of transmit buffers..
Type
INT
Range
0 - 255
Value
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
58 (148)
Rationale
Reg no
Info Class
II
For the transmit path, temporarily GM recommends to use the transmit buffers
based on the user demands. The value of this parameter is not controlled by GM and
is left to the discretion of the supplier.
ID : ETHSW-1269
2.39.1.1.1.9 [REQ] EthDemEventParameterRefs

Description
Container for the references to DemEventParameter elements which shall be invoked
using the API Dem_ReportErrorStatus in case the corresponding error occurs. The
EventId is taken from the referenced DemEventParameter's DemEventId value. The
standardized errors are provided in the container and can be extended by vendor
specific error references.
Type
Range
Value
Rationale
GM needs to provide DEM event if implemented by Tier 1. The value of this

parameter is not controlled by GM and is left to the discretion of the supplier.
ID : ETHSW-1286
2.39.1.1.1.10 [REQ] ETH_E_ACCESS

Description
Reference to the DemEventParameter which shall be issued when the error
"Controller access failed" has occured.
Type
SN-REF
Range
Value
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
59 (148)
Rationale
Reg no
Info Class
II

ID : ETHSW-1303
2.39.1.2 [REQ] EthGeneral

Description
General configuration of Ethernet Driver module.
Type
Range
Value
Rationale
This container is AUTOSAR mandatory container if the Ethernet is enabled.
ID : ETHSW-1321
2.39.1.2.1.1 [REQ] EthDevErrorDetect

Description
Enables / Disables development error detection. The value of this parameter shall be
FALSE for GM.
Type
BOOL
Range
Value
FALSE
Rationale
If ECU is in development phase, DevErrorDetect shall be set to TRUE. If ECU is in

production phase, DevErrorDetect shall be set to FALSE.
Rationale: To support software debug.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
60 (148)
II
ID : ETHSW-1338
2.39.1.2.1.2 [REQ] EthIndex

Description
Specifies the InstanceId of this module instance. If only one instance is present it shall
have the Id 0..
Type
INT
Range
0 - 255
Value
Rationale
The value of this parameter is not controlled by GM and is left to the discretion of the
supplier.
ID : ETHSW-1355
2.39.1.2.1.3 [REQ] EthMaxCtrlsSupported

Description
Limits the total number of supported controllers. The value of this parameter is
defined in the project specific document.
Type
INT
Range
1 - 255
Value
Rationale
As per 4.0.3 ASR spec, "4.1 Limitations The Ethernet Interface module is only
able to handle a single thread of execution. The execution must not be preempted by itself.
The Ethernet Interface is conceptually able to access one or more Ethernet driver
and one or more Ethernet Transceiver driver. Currently, the Ethernet Interface
module is limited to one Ethernet driver and one Ethernet Transciever driver. To
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
61 (148)
II
support multiple lower layer drivers the configuration would have to be extended.
ID : ETHSW-1372
2.39.1.2.1.4 [REQ] EthVersionInfoApi

Description
Enables / Disables version info API. The value of this parameter shall be True for GM.
Type
BOOL
Range
Value
TRUE
Rationale
Rationale: Diagnostic information of module
ID : ETHSW-1389
2.39.1.2.1.5 [REQ] EthVersionInfoApiMacro
Description
Enables / Disables version info API macro implementation. The value of this
parameter shall be True for GM.
Type
BOOL
Range
Value
TRUE
Rationale
ID : ETHSW-1406
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
62 (148)
II
2.39.2 [REQ] EthIf

Description
Configuration of the EthIf (Ethernet Interface) module.. The value of this parameter
is defined in a project specific document.
Type
Range
Value
Rationale
This module shall be optional because, Ethernet may not be implemented in all ECU's.
ID : ETHSW-1423
2.39.2.1 [REQ] EthIfConfigSet

Description
Collecting container for all parameters with post-build configuration classes.
Type
Range
Value
Rationale
Mandatory container if the EthIf module is enabled.
ID : ETHSW-1440
2.39.2.1.1 [REQ] EthIfConnection2EthCtrlMapping

Description
Maps a particular connection in the Ethernet Interface to the physical Ethernet
Controller.
Type
Range
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
63 (148)
II
Value
Rationale
This depends on the number of ethernet controllers availability in the ECU. The value
of this parameter is not controlled by GM and is left to the discretion of the supplier.
ID : ETHSW-1457
2.39.2.1.1.1 [REQ] EthIfEthCtrlRef

Description
Reference to the controller in Ethernet Driver on which this connection will be
transmitted / received. Connections are specified in the Socket Adapter.
Type
SN-REF
Range
Value
Rationale
This parameter shall be configured by the Tier1 based on the number of ethernet
controllers availability in the ECU. The value of this parameter is not controlled by GM
ID : ETHSW-1474
2.39.2.1.1.2 [REQ] EthIfSoAdConnectionRef

Description
Reference to the controller in Ethernet Driver on which this connection will be
transmitted / received. Connections are specified in the Socket Adapter.
Type
SN-REF
Range
Value
Rationale
This parameter shall be configured by the Tier1 based on the number of socket
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
64 (148)
II
connections required and configured in the in the Socket Adapter. The value of this
2.39.2.1.2 EthIfFrameOwnerConfig
Description
Configuration of Ethernet frame owner.
Type
Range
Value
Rationale
ID : ETHSW-1508
2.39.2.1.2.1 [REQ] EthIfFrameType

Description
Selects the Ethernet frame type. The value of this parameter is defined in a project
specific document.
Type
INT
Range
0 - 65535
Value
IPv4 = 0x0800
IPv6 = 0x86DD
ARP = 0x0806
Rationale
GM recommended to use IPv4, IPv6 & ARP as its upper layer protocol
ID : ETHSW-1525
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
65 (148)
II
2.39.2.1.2.2 [REQ] EthIfOwner

Description
Selects the owner of an Ethernet frame type. The owner is a zero based index into the
callback function configuration 'EthIfRxIndicationConfig'. I.e. an Ethernet frame of
type IPv4 (0x800) at index 0 will call the first callback function configured in
'EthIfRxIndicationConfig'
Type
INT
Range
0 - 255
Value
Rationale
Tier 1 to configure the appropriate frame owner based on the type of the frame. The
value of this parameter is not controlled by GM and is left to the discretion of the
supplier.
ID : ETHSW-1542
2.39.2.1.3 [REQ] EthIfRxIndicationConfig

Description
Configuration of receive callback functions..
Type
Range
Value
Rationale
ID : ETHSW-1559
2.39.2.1.3.1 [REQ] EthIfRxIndicationFunction
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
66 (148)
II
Description
Specifies receive indication callback function. The value of this parameter

recommended as Ip_RxIndication or Arp_RxIndication (function name for IPv6 not
mentioned) for GM.
Type
FNC-N
Range
Value
Rationale
Callback function shall be implemented to notify frame reception (For eg.

Ip_RxIndication or Arp_RxIndication depending on the frame type). Tier 1 to
configure the appropriate frame RX indication function. The value of this parameter is
not controlled by GM and is left to the discretion of the supplier.
ID : ETHSW-1576
2.39.2.1.4 [REQ] EthIfTrcvLinkStateChgConfig

Description
Specifies link state change callback function.
Type
Range
Value
Rationale
ID : ETHSW-1593
2.39.2.1.4.1 [REQ] EthIfTrcvLinkStateChgFunction

Description
Specifies link state change callback function. The value of this parameter
recommended as IpV4_Ip_Cbk_TrcvLinkStateChg or IpV4_Arp_TxConfirmation
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
67 (148)
II
(function name for IPv6 not mentioned) for GM.

Type
FNC-N
Range
Value
Rationale
Callback function shall be implemented to nofity the link state change (For eg.
Ip_Cbk_TrcvLinkStateChg).
The 'EthIfTrcvLinkStateChgMainReload' option defines the frequency of polling as
follows: 'Freq = MainFunctionStatePeriod * EthIfTrcvLinkStateChgMainReload'.
Tier 1 to configure the appropriate Link State Change function. The value of this
ID : ETHSW-1610
2.39.2.1.5 [REQ] EthIfTxConfirmationConfig

Description
Configuration of transmit indication callback functions.
Type
Range
Value
Rationale
ID : ETHSW-1627
2.39.2.1.5.1 [REQ] EthIfTxConfirmationFunction

Description
Specifies transmit indication callback function. The value of this parameter
recommended as Ip_TxConfirmation or Arp_TxConfirmation (function name for IPv6
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
68 (148)
II
not mentioned) for GM.

Type
FNC-N
Range
Value
Rationale
Callback function shall be implemented to nofiy Confirmation on the transmission

(For eg. Ip_TxConfirmation or Arp_TxConfirmation based on the frame type). Tier 1 to
configure the appropriate frame TX confirmation function. The value of this
ID : ETHSW-1644
2.39.2.2 [REQ] EthIfGeneral

Description
This container contains the general configuration parameters of the Ethernet
Interface..
Type
Range
Value
Rationale
ID : ETHSW-1661
2.39.2.2.1 [REQ] EthIfDevErrorDetect

Description
FALSE for GM.
Type
BOOL
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
69 (148)
II
Range
Value
FALSE
Rationale

production phase, DevErrorDetect shall be set to FALSE.
Rationale: To support software debug.
ID : ETHSW-1678
2.39.2.2.2 [REQ] EthIfEnableRxInterrupt

Description
Enables / Disables receive interrupt. The value of this parameter shall be TRUE for
GM.
Type
BOOL
Range
Value
TRUE
Rationale
GM recommended to enable the receive interrupt so that performance of the ECU

will become improved.
ID : ETHSW-1695
2.39.2.2.3 [REQ] EthIfEnableTxInterrupt

Description
Enables / Disables the transmit interrupt. The value of this parameter shall be TRUE
for GM.
Type
BOOL
Range
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
70 (148)
II
Value
TRUE
Rationale
GM recommended to enable the transmit interrupt so that performance of the ECU

will become improved.
ID : ETHSW-1712
2.39.2.2.4 [REQ] EthIfMainFunctionPeriod

Description
Specifies the period of main function EthIf_MainFunctionRx and
EthIf_MainFunctionTx in seconds. Ethernet Interface does not require this
information but the BSW scheduler.
Type
FLOAT
Range
0 - Inf
Value
Rationale
Tier 1 shall set this parameter to minimize latency and to enable the software stack to
transmit and receive process all messages it has been assigned regardless of network
bandwidth loading.
ID : ETHSW-1729
2.39.2.2.5 [REQ] EthIfMaxTrcvsTotal
Description
Limits the total number of transceivers. The value of this parameter is defined in a
project specific document.
Type
INT
Range
1 - 255
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
71 (148)
II
Value
Rationale
Asr 4.0.3 limits the number of controllers to 1.
ID : ETHSW-1746
2.39.2.2.6 [REQ] EthIfMaxTxBufsTotal

Description
Limits the total number of transmit buffers.
Type
INT
Range
1 - 255
Value
Rationale
Based on the Hardware support. The value of this parameter is not controlled by GM
ID : ETHSW-1763
2.39.2.2.7 [REQ] EthIfPublicCddHeaderFile

Description
Defines header files for callback functions which shall be included in case of CDDs.
Range of characters is 1.. 32.
Type
STRG
Range
Value
Rationale
The COTS TCP/IP stack fits in CDD. The value of this parameter is not controlled by
GM and is left to the discretion of the supplier.
ID : ETHSW-1780
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
72 (148)
II
2.39.2.2.8 [REQ] EthIfTrcvLinkStateChgMainReload

Description
Specifies the frequency of transceiver link state change checks in each. The value of
this parameter is defined in a project specific document.
Type
INT
Range
1 - 255
Value
Rationale
Please refer to the parameter "EthIfMainFunctionPeriod". The

'EthIfTrcvLinkStateChgMainReload' option defines the frequency of polling as follows:
'Freq = MainFunctionStatePeriod * EthIfTrcvLinkStateChgMainReload'.
ID : ETHSW-1797
2.39.2.2.9 [REQ] EthIfVersionInfoApi

Description
Enables / Disables version info API.
Type
BOOL
Range
Value
TRUE
Rationale
ID : ETHSW-1814
2.39.2.2.10 [REQ] EthIfVersionInfoApiMacro

Description
Enables / Disables version info API macro implementation.
GM Confidential
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
73 (148)
Type
BOOL
Range
Value
TRUE
Rationale
Info Class
II
ID : ETHSW-1831
2.39.3 [REQ] EthSm

Description
Configuration of the Ethernet State Manager. The value of this parameter is defined
in a project specific document.
Type
Range
Value
Rationale
ID : ETHSW-1848
2.39.3.1 [REQ] EthSmGeneral

Description
This container contains the global parameter of the Ethernet State Manager..
Type
Range
Value
Rationale
There is only 1 EthSM suppored and defined in AUTOSAR
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
74 (148)
II
ID : ETHSW-1865
2.39.3.1.1 [REQ] EthSmDevErrorDetect

Description
Enables/ Disables the development error detection and notification mechanism..
The value of this parameter shall be FALSE for GM.
Type
BOOL
Range
Value
FALSE
Rationale

production phase, DevErrorDetect shall be set to FALSE. Rationale: To support
software debug.
ID : ETHSW-1882
2.39.3.1.2 [REQ] EthSmDummyMode

Description
Disables the API to the EthIf. The API to the ComM is available but the functionality is
deactivated. The function calls from the ComM will be answered with the return
value E_OK.. The value of this parameter shall be FALSE for GM.
Type
BOOL
Range
Value
FALSE
Rationale
Disable Dummymode since Ethernet does exist . Only required in case of Variant 1 .
GM uses the Autosar Ethernet driver and interface
ID : ETHSW-1899
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
75 (148)
II
2.39.3.1.3 [REQ] EthSmMainFunctionPeriod
Description
Specifies the period in seconds that the MainFunction has to be triggered with.
Type
FLOAT
Range
0.005 - 1
Value
Rationale
Controller Supplier shall set this parameter to minimize latency and to enable the
software stack to transmit and receive process all messages it has been assigned
regardless of network bandwidth loading.
ID : ETHSW-1916
2.39.3.1.4 [REQ] EthSmVersionInfoApi

Description
Enables and disables the version info API.
Type
BOOL
Range
Value
TRUE
Rationale
ID : ETHSW-1933
2.39.3.2 [REQ] EthSmNetwork

Description
This container contains the Ethernet network-specific parameters of each Ethernet
network. It also contains the controller and transceiver IDs assigned to a Ethernet
network. The value of this parameter shall be defined in Project Specific document
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
76 (148)
II
Type
Range
Value
Rationale
As per 4.0.3 ASR spec, "4.1 Limitations The Ethernet Interface module is only
able to handle a single thread of execution. The execution must not be preempted by itself.
The Ethernet Interface is conceptually able to access one or more Ethernet driver
and one or more Ethernet Transceiver driver. Currently, the Ethernet Interface
module is limited to one Ethernet driver and one Ethernet Transciever driver. To
support multiple lower layer drivers the configuration would have to be extended.
ID : ETHSW-1950
2.39.3.2.1 [REQ] EthSmConfirmationTimeout

Description
Timeout in seconds for the calls to EthIf. Tier1 shall come up with appropriate value
of this parameter.
Type
FLOAT
Range
0 - Inf
Value
0-5
Rationale
supplier.
ID : ETHSW-1967
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
77 (148)
II
2.39.3.2.2 [REQ] EthSMComMNetworkHandleRef

Description
Unique handle to identify one certain Ethernet network. Reference to one of the
network handles configured for the ComM.
Type
SN-REF
Range
Value
Rationale
Tier1 to choose one communication channel identifier for this parameter since it only
support one Ethernet Controller. The value of this parameter is not controlled by GM
ID : ETHSW-1984
2.39.3.2.3 [REQ] EthSmControllerId

Description
ID of the Ethernet controller assigned to the configured network handle. Reference to
one of the controllers of Eth configuration.
Type
SN-REF
Range
Value
Rationale
support one Ethernet Controller. The value of this parameter is not controlled by GM
ID : ETHSW-2001
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
78 (148)
II
2.39.3.2.4 [REQ] EthSmTransceiverId

Description
ID of the ethernet transceiver assigned to the configured network handle. Reference
to one of the transceivers of EthTrcv configuration..
Type
SN-REF
Range
Value
Rationale
support one Ethernet Trasceiver The value of this parameter is not controlled by GM
ID : ETHSW-2018
2.39.4 [REQ] EthTrcv

Description
Configuration of Ethernet Transceiver Driver module. The value of this parameter is
defined in a project specific document.
Type
Range
Value
Rationale
ID : ETHSW-2039
GM Confidential
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
79 (148)
II
2.39.4.1.1.1.1.1 [REQ] EthTrcvConfigSet
Description
All underlying parameters may be part of a multiple configuration set..
Type
Range
Value
Rationale
Mandatory container if the EthTrcv module is enabled.
ID : ETHSW-2056
2.39.4.1.1.1.1.2 [REQ] EthTrcvConfig
Description
Configuration of the individual transceiver.
Type
Range
Value
Rationale
ID : ETHSW-2073
2.39.4.1.2 [REQ] EthTrcvCtrlIdx

Description
Specifies the controller used for MII access to the transceiver.
Type
INT
GM Confidential
Info Class
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
80 (148)
Range
Reg no
Info Class
II
0 - 255
Value
Rationale
supplier.
ID : ETHSW-2090
2.39.4.1.3 [REQ] EthTrcvIdx

Description
Specifies the instance ID of the configured transceiver..
Type
INT
Range
0 - 255
Value
Rationale
supplier.
ID : ETHSW-2107
2.39.4.1.4 [REQ] EthTrcvMiiIdx

Description
Specifies the transceiver index used for MII access to the transceiver.
Type
INT
Range
0 - 255
Value
Rationale
supplier.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
81 (148)
II
ID : ETHSW-2126
2.39.4.1.4.1.1.1 [REQ] EthTrcvDemEventParameterRefs
Description

using the API Dem_ReportErrorStatus API in case the corresponding error occurs. The
specific error rererences.
Type
Range
Value
Rationale

ID : ETHSW-2143
2.39.4.1.5 [REQ] ETHTRCV_E_ACCESS

Description
"Transceiver access failed" has occured..
Type
SN-REF
Range
Value
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
82 (148)
Rationale
Reg no
Info Class
II

ID : ETHSW-2162
2.39.4.1.5.1.1.1 [REQ] EthTrcvGeneral
Description
General configuration of Ethernet Transceiver Driver module.
Type
Range
Value
Rationale
ID : ETHSW-2179
2.39.4.1.6 [REQ] EthTrcvDevErrorDetect
Description
FALSE for GM.
Type
BOOL
Range
Value
FALSE
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
83 (148)
Rationale
Reg no
Info Class
II

software debug.
ID : ETHSW-2196
2.39.4.1.7 [REQ] EthTrcvGetBaudRateApi

Description
Enables / Disables EthTrcv_GetBaudRate API. The value of this parameter shall be
TRUE for GM.
Type
BOOL
Range
Value
TRUE
Rationale
GM strategy intend to support 100Mb as well as 10Mb ethernet connection.
ID : ETHSW-2213
2.39.4.1.8 [REQ] EthTrcvGetDuplexModeApi

Description
Enables / Disables EthTrcv_GetDuplexMode API. The value of this parameter shall be
TRUE for GM.
Type
BOOL
Range
Value
TRUE
Rationale
GM intends to enable this parameter since GetDuplexModeApi is required to get the

current transceiver duplex mode.
Full duplex mode is intended for use on point-to-point links between switches or end
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
84 (148)
II
node to switch. Half duplex mode is used in connections between an end node and a
repeater or between repeaters. GM intended to use Full Duplex mode.
ID : ETHSW-2230
2.39.4.1.9 [REQ] EthTrcvGetLinkStateApi

Description
Enables / Disables EthTrcv_GetLinkState API. The value of this parameter shall be
TRUE for GM.
Type
BOOL
Range
Value
TRUE
Rationale
GM intends to enable this parameter since Link state API required to get the current
transceiver link state changes to the IP layer.
ID : ETHSW-2247
2.39.4.1.10 [REQ] EthTrcvGetTransceiverModeApi

Description
Enables / Disables EthTrcv_GetTransceiverMode API. The value of this parameter
shall be TRUE for GM.
Type
BOOL
Range
Value
TRUE
Rationale
GM intends to enable this parameter since Get Transceiver Mode API required to get
the current mode of the transceiver.
ID : ETHSW-2264
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
85 (148)
II
2.39.4.1.11 [REQ] EthTrcvIndex

Description
have the Id 0..
Type
INT
Range
0 - 255
Value
Rationale
supplier.
ID : ETHSW-2281
2.39.4.1.12 [REQ] EthTrcvMaxTrcvsSupported

Description
have the Id 0..
Type
INT
Range
0 - 255
Value
Rationale
supplier.
ID : ETHSW-2298
2.39.4.1.13 [REQ] EthTrcvSetTransceiverModeApi

Description
Enables / Disables EthTrcv_SetTransceiverMode API. The value of this parameter
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
86 (148)
II

Type
BOOL
Range
Value
TRUE
Rationale
GM intends to enable this parameter to set the current transceiver status either as
Enabled or Disabled.
ID : ETHSW-2315
2.39.4.1.14 [REQ] EthTrcvStartAutoNegotiationApi

Description
Enables / Disables EthTrcv_StartAutoNegotiation API. The value of this parameter
Type
BOOL
Range
Value
TRUE
Rationale
GM intends to enable this parameter since GM strategy intend to support 100Mb as

well as 10Mb ethernet connection.
ID : ETHSW-2332
2.39.4.1.15 [REQ] EthTrcvVersionInfoApi

Description
Enables / Disables version info API. The value of this parameter shall be True for GM.
Type
BOOL
Range
GM Confidential
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
87 (148)
Value
TRUE
Rationale
Info Class
II
ID : ETHSW-2349
2.39.4.1.16 [REQ] EthTrcvVersionInfoApiMacro
Description
Enables / Disables version info API macro implementation. The value of this
parameter shall be True for GM.
Type
BOOL
Range
Value
TRUE
Rationale
ID : ETHSW-2366
2.39.4.1.17 [REQ] EthTrcvWaitCount

Description
Wait count for transceiver state changes..
Type
INT
Range
0 - 4294967295
Value
Rationale
supplier.
ID : ETHSW-2383
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
88 (148)
II
2.39.5 [REQ] SoAd

Description
Configuration of the SoAd (Socket Adaptor) module. The value of this parameter is
Type
Range
Value
Rationale
ID : ETHSW-2400
2.39.5.1 [REQ] SoAdDemEventParameterRefs

Description
Type
Range
Value
Rationale

ID : ETHSW-2417
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
89 (148)
II
2.39.5.1.1 [REQ] SOAD_E_INTR

Description
"Interrupted system call" has occured..
Type
SN-REF
Range
Value
Rationale

ID : ETHSW-2434
2.39.5.1.2 [REQ] SOAD_E_IO

Description
"Input/output error" has occured..
Type
SN-REF
Range
Value
Rationale

ID : ETHSW-2451
2.39.5.1.3 [REQ] SOAD_E_UPPERBUFF

Description
Reference to the DemEventParameter which shall be issued when the error "No
buffer available in upper layer" has occured..
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
90 (148)
Type
SN-REF
Range
Reg no
Info Class
II
Value
Rationale

ID : ETHSW-2468
2.39.5.2 [REQ] SoAdDoIpConfig

Description
This container contains all global configuration parameters of the DoIP plug-in..
Type
Range
Value
Rationale
Mandatory container if the SoAd DOIP module is enabled.
ID : ETHSW-2485
2.39.5.2.1 [REQ] SoAdDoIpAliveCheckResponseTime

Description
This parameter specifies the maximum time that a DoIP entity shall wait for an Alive
Check Response after sending an Alive Check Request. The value of this parameter is
recommended as Timeout: 500 ms for GM.
Type
FLOAT
Range
0 - Inf
Value
Timeout: 500 ms
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
91 (148)
Rationale
Reg no
Info Class
II
The value of this parameter shall be set as per ISO13400-2 parameter

T_TCP_Alive_Check.
ID : ETHSW-2502
2.39.5.2.2 [REQ] SoAdDoIpControlTimeout

Description
This parameter specifies the maximum time that the test equipment waits for a
response to a previously sent control command. The value of this parameter is
recommended as Timeout: 2 s for GM.
Type
FLOAT
Range
0 - Inf
Value
Timeout: 2 s
Rationale
The value of this parameter shall be set as per ISO13400-2 parameter A_DoIP_Ctrl.
ID : ETHSW-2519
2.39.5.2.3 [REQ] SoAdDoIpGenericInactiveTime
Description
This parameter specifies the maximum time of inactivity on a TCP_DATA socket

before it is closed. The value of this parameter is recommended as Timeout: 5min for
GM.
Type
FLOAT
Range
0 - Inf
Value
Timeout: 5min
Rationale
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
92 (148)
II
T_TCP_Generic_Inactivity is set
ID : ETHSW-2536
2.39.5.2.4 [REQ] SoAdDoIpHostNameOpt

Description
Defines the <manufacturer specific> part of the "host name option". The value of this
parameter is recommended as "DoIP-OEM Specific part" for GM.
Type
STRG
Range
Value
"DoIP-OEM Specific part"
Rationale
The value of this parameter shall be set as per ISO13400-2 example.
ID : ETHSW-2553
2.39.5.2.5 [REQ] SoAdDoIpInitialInactiveTime

Description
This parameter specifies the maximum time of inactivity directly after a TCP_DATA
socket was established. After the specified time without Routing Activation the
TCP_DATA socket is closed. The value of this parameter is recommended as 2s for
GM.
Type
FLOAT
Range
0 - Inf
Value
2s
Rationale

T_TCP_Initial_Inactivity
ID : ETHSW-2570
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
93 (148)
II
2.39.5.2.6 [REQ] SoAdDoIpResponseTimeout

Description
This parameter specifies the maximum time after which a DoIP information request
must have been processed and the corresponding response must have been sent by
the DoIP entity otherwise the request or the response must be considered lost. The
value of this parameter is recommended as 2s for GM.
Type
FLOAT
Range
0 - Inf
Value
2s
Rationale

A_DoIP_Diagnostic_Message. This parameter is not usually used, since this time is
managed by testers.
ID : ETHSW-2587
2.39.5.2.7 [REQ] SoAdDoIpVidAnnounceInterval

Description
This timing parameter specifies the time between the Vehicle Announcement
Messages that are sent by DoIP entities after a valid IP address was configured. The
value of this parameter is recommended as 500ms for GM.
Type
FLOAT
Range
0 - Inf
Value
500ms
Rationale

A_DoIP_Announce_Interval
ID : ETHSW-2604
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
94 (148)
II
2.39.5.2.8 [REQ] SoAdDoIpVidAnnounceMaxWait

Description
Describes the maximum time a DoIP entity shall wait before sending an Vehicle
Identification Response. The value of this parameter is recommended as 0-500ms for
GM.
Type
FLOAT
Range
0 - Inf
Value
0-500ms
Rationale

A_DoIP_Announce_Wait
ID : ETHSW-2621
2.39.5.2.9 [REQ] SoAdDoIpVidAnnounceMinWait

Description
Describes the minimum time a DoIP entity shall wait before sending an Vehicle
Identification Response. The value of this parameter is recommended as 0-500ms for
GM.
Type
FLOAT
Range
0 - Inf
Value
0-500ms
Rationale

A_DoIP_Announce_Wait
ID : ETHSW-2638
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
95 (148)
II
2.39.5.2.10 [REQ] SoAdDoIpVidAnnounceNum

Description
Specifies the number of Vehicle Announcement messages which the DoIP entity
sends after a valid IP address has been configured.. The value of this parameter shall
be 3 for GM.
Type
INT
Range
0 - 255
Value
Rationale

A_DoIP_Announce_Num
ID : ETHSW-2655
2.39.5.2.11 [REQ] SoAdDoIpEid

Description
A unique 6-byte DoIp Entity Identification (EID). The value of this parameter is
Type
Range
Value
Rationale
At present recommend to set EID as the MAC address
ID : ETHSW-2672
2.39.5.2.11.1 [REQ] SoAdDoIpEidByte

Description
One byte of the DoIp Entity Identification (EID). The value of this parameter is defined
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
96 (148)
II
Type
Range
Value
Rationale
ID : ETHSW-2689
2.39.5.2.11.2 [REQ] SoAdDoIpEidByteIndex
Description
Index of the Eid byte array. The value of this parameter is defined in a project specific
document.
Type
INT
Range
0-5
Value
Rationale
ID : ETHSW-2706
2.39.5.2.11.3 [REQ] SoAdDoIpEidByteValue

Description
Byte Value at the SoAdDoIpEidByteIndex position in the Eid byte array. The value of
this parameter is defined in a project specific document.
Type
INT
Range
0 - 255
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
97 (148)
II
Value
Rationale
ID : ETHSW-2723
2.39.5.2.12 [REQ] SoAdDoIpRoute

Description
A SoAd_DoIP_Route allocates a PDU ID to a combination of a DoIP source and a DoIP
target address..
Type
Range
Value
Rationale
This configuration is recommended to be used for DOIP. (Not the SoAd Pdu route and
SoAd Socket Route)
ID : ETHSW-2740
2.39.5.2.12.1 [REQ] SoAdDoIpSourceAddress

Description
The logical DoIP address of the source entitiy. The value of this parameter shall be
range as per ISO13400-2 for GM.
Type
INT
Range
0 - 65535
Value
range as per ISO13400-2
Rationale
Valid range specified in ISO spec. GM recommended value will be given in the
diagnostics specification.
ID : ETHSW-2757
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
98 (148)
II
2.39.5.2.12.2 [REQ] SoAdDoIpTargetAddress

Description
The logical DoIP address of the target entity.. The value of this parameter shall be
range as per ISO13400-2 for GM.
Type
INT
Range
0 - 65535
Value
range as per ISO13400-2
Rationale
Valid range specified in ISO spec. GM recommended value will be given in the
diagnostics specification
ID : ETHSW-2774
2.39.5.2.13 [REQ] SoAdDoIpSocketConnectionRef

Description
Reference to the used socket connection.
Type
REF
Range
Value
Rationale
supplier.
ID : ETHSW-2791
2.39.5.3 [REQ] SoAdGeneral

Description
This container contains all global configuration parameters of SoAd configured from
the Pdu Router Module perspective.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
99 (148)
II
Type
Range
Value
Rationale
Mandatory container if the SoAd module is enabled.
ID : ETHSW-2808
2.39.5.3.1 [REQ] SoAdBufferMemorySize

Description
Memory size reserved for SoAd buffers.
Type
INT
Range
0 - 65535
Value
Rationale
This parameter is required only for BSD Socket. GM would go for Autosar Sockets.
supplier.
ID : ETHSW-2825
2.39.5.3.2 [REQ] SoAdCallbackApi

Description
True if the TCP/IP stack supports the AUTOSAR Call-back API in addition to the
Berkeley Socket API. The value of this parameter shall be TRUE for GM.
Type
BOOL
Range
Value
TRUE
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
100 (148)
Rationale
Reg no
Info Class
II
GM intended to set this parameter as True, since TCP/IP stack supports the AUTOSAR
Call-back API in addition to the Berkeley Socket API only if this parameter is TRUE.
ID : ETHSW-2842
2.39.5.3.3 [REQ] SoAdDevErrorDetect

Description
Pre-processor switch for enabling development error detection support. The value of
this parameter shall be FALSE for GM.
Type
BOOL
Range
Value
FALSE
Rationale

software debug.
ID : ETHSW-2859
2.39.5.3.4 [REQ] SoAdDoIpActive
Description
True if a DoIP protocol plug-in is available. The value of this parameter shall be TRUE
for GM.
Type
BOOL
Range
Value
TRUE
Rationale
DOIP is a required module
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
101 (148)
II
ID : ETHSW-2876
2.39.5.3.5 [REQ] SoAdDoIpVersionInfoApi

Description
Switches the DoIP_GetVersionInfo() API ON or OFF.
Type
BOOL
Range
Value
TRUE
Rationale
ID : ETHSW-2893
2.39.5.3.6 [REQ] SoAdIPv6AddressEnabled

Description
Allows for increased memory allocation to store IPv6 addresses. The value of this
parameter shall be TRUE for GM.
Type
BOOL
Range
Value
TRUE
Rationale
GM would require IPV6 support
ID : ETHSW-2910
2.39.5.3.7 [REQ] SoAdMainFunctionPeriod

Description
Determines the frequency at which the SoAd_MainFunction() is called in [s].
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
102 (148)
Type
FLOAT
Range
0 - Inf
Reg no
Info Class
II
Value
Rationale
ID : ETHSW-2927
2.39.5.3.8 [REQ] SoAdMaxOpenSockets

Description
Specifies the number of sockets that will be open at any one time. The value of this
parameter is defined in a project specific document.
Type
INT
Range
0 - 65535
Value
Rationale
3 for external tester, 1 for onboard tester,1 reserved,1 as onboard DUT.
ID : ETHSW-2944
2.39.5.3.9 [REQ] SoAdPollingInterval

Description
Specifies the interval at which the SoAd shall poll the TCP/IP stack for new
information in [s]. The value of this parameter shall be ZERO for GM.
Type
FLOAT
Range
0 - Inf
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
103 (148)
II
Value
Rationale
This parameter is required only for polling mode, not required in interrupt mode. The
value of this parameter shall be ZERO since GM intend to not use polling mode.
ID : ETHSW-2961
2.39.5.3.10 [REQ] SoAdSocketCount

Description
Number of entries in the Socket connection table. The value of this parameter is
Type
INT
Range
1 - 255
Value
Rationale
1UDP,1DHCP,1 reserved TCP socket for request rejection, multiple external testers,
etc. Based on the number of external testers at a given point of program this can be
decided
ID : ETHSW-2978
2.39.5.3.11 [REQ] SoAdTcpIpMainFunctionPeriod

Description
Determines the frequency at which the TcpIp_MainFunctionCyclic() is called in [s].
Type
FLOAT
Range
0 - Inf
Value
Rationale
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
104 (148)
II

ID : ETHSW-2995
2.39.5.3.12 [REQ] SoAdTcpIpVersionInfoApi

Description
Activates the TCPIP_GetVersionInfo API. The value of this parameter shall be TRUE for
GM.
Type
BOOL
Range
Value
TRUE
Rationale
Diagnostic information of Module.
ID : ETHSW-3012
2.39.5.3.13 [REQ] SoAdUdpNmApiEnabled

Description
Activates the configurable interfaces to be used by UdpNm. The value of this
parameter shall be FALSE for GM.
Type
BOOL
Range
Value
FALSE
Rationale
UDP Nm Api Not required since there are no wakeup and sleep based on bus activity.
It is based on activation line
ID : ETHSW-3029
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
105 (148)
II
2.39.5.3.14 [REQ] SoAdVersionInfoApi
Description
Activates the SoAd_GetVersionInfo() API.
Type
BOOL
Range
Value
TRUE
Rationale
ID : ETHSW-3046
2.39.5.3.15 [REQ] SoAdXcpApiEnabled

Description
Activates the configurable interfaces to be used by Xcp. The value of this parameter is
Type
BOOL
Range
Value
FALSE
Rationale
Current implementation doesn't require XCP over ethernet. May be required in

Future.
ID : ETHSW-3063
2.39.5.4 [REQ] SoAdPduRoute

Description
Describes the path of a PDU from the PDU Router to the socket in the TCP/IP stack for
transmission. This container is not used for GM and left to the discretion of the
supplier
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
106 (148)
II
Type
Range
Value
Rationale
Pdu header option not used.
ID : ETHSW-3080
2.39.5.4.1 [REQ] SoAdDestinationId

Description
ID to be sent on the TCP/IP connection if the PDU header option is enabled.
Type
INT
Range
0 - 4294967296
Value
Rationale
Pdu header option not used. The value of this parameter is not controlled by GM and
ID : ETHSW-3097
2.39.5.4.2 [REQ] SoAdSourcePduId

Description
PDU ID of the PDU coming from the PDU Router.
Type
INT
Range
0 - 65535
Value
Rationale
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
107 (148)
II

ID : ETHSW-3114
2.39.5.4.3 [REQ] SoAdSourceSduLength

Description
Length in bytes of the SDU to be sent over the TCP/IP stack.
Type
INT
Range
0 - 65535
Value
Rationale
ID : ETHSW-3131
2.39.5.4.4 [REQ] SoAdTxConfirmationUL

Description
This optional parameter defines the name of the <User_TxConfirmation> in case that
SoAdUserTxConfirmationUL is configured to Cdd. If SoAdUserTxConfirmationUL
equals PduR Xcp or UdpNm the name of the <User_TxConfirmation> is fixed and this
parameter is skipped. If SoAdUserTxConfirmationUL equals Cdd the name of the
<User_TxConfirmation> is selectable.
Type
FNC-N
Range
Value
Rationale
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
108 (148)
II
ID : ETHSW-3148
2.39.5.4.5 [REQ] SoAdUserTxConfirmationUL

Description
This parameter defines the upper layer (UL) module to which the confirmation of the
successfully transmitted SoAdSourcePduId has to be routed via the
<User_SoAdTxConfirmation>. The value of this parameter is defined in a project
specific document.
Type
ENUM
Range
Value
PDUR
Rationale
ID : ETHSW-3165
2.39.5.4.6 [REQ] SoAdDestinationSocketRef

Description
Connection on which the PDU is to be sent on references the appropriate entry in the
Socket Connection Table.
Type
REF
Range
Value
Rationale
ID : ETHSW-3182
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
109 (148)
II
2.39.5.4.7 [REQ] SoAdSourcePduRef

Description
Reference to the global PDU structure.
Type
REF
Range
Value
Rationale
ID : ETHSW-3199
2.39.5.4.8 [REQ] SoAdSocketConnection
Description
Information required to receive and transmit data via the TCP/IP stack on a particular
connection..
Type
Range
Value
Rationale
Mandatory container if the SoAd module is enabled.
ID : ETHSW-3216
2.39.5.4.9 [REQ] SoAdAutosarConnector

Description
Connection point within the AUTOSAR stack for this socket connection. The value of
this parameter shall be DOIP for GM.
GM Confidential
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
110 (148)
Type
ENUM
Range
Value
DOIP
Rationale
EnDG uses DOIP as the only user for SoAd
Info Class
II
ID : ETHSW-3233
2.39.5.4.10 [REQ] SoAdPduHeaderEnable

Description
Enables the transmission of the PDU header (ID length) on this TCP/IP connection.
Type
BOOL
Range
Value
Rationale
GM intends to use the TP style API currently. May be required in future to support IF
style API also. Left to the discretion of the supplier.
ID : ETHSW-3250
2.39.5.4.11 [REQ] SoAdPduProvideBufferEnable

Description
Enables the use of TP style API towards the PDU Router for this PDU. Will trigger the
calls to ProvideRxBuffer and ProvideTxBuffer respectively.
Type
BOOL
Range
Value
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
111 (148)
Rationale
Reg no
Info Class
II
GM intends to use the TP style API currently. May be required in future to support IF
style API also. Left to the discretion of the supplier.
ID : ETHSW-3267
2.39.5.4.12 [REQ] SoAdResourceManagementEnable

Description
Enables the resource management option for this socket.
Type
BOOL
Range
Value
Rationale
GM does not use dynamic socket management currently. May be required in future.
Left to the discretion of the supplier.
ID : ETHSW-3284
2.39.5.4.13 [REQ] SoAdSocketAutosarApi

Description
Enables the use of the AUTOSAR call-back API for this connection. The value of this
parameter shall be TRUE for GM.
Type
BOOL
Range
Value
TRUE
Rationale
GM intended to set this parameter as True, since TCP/IP stack supports AUTOSAR
Call-back API in addition to the Berkeley Socket API only if this parameter is TRUE.
ID : ETHSW-3301
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
112 (148)
II
2.39.5.4.14 [REQ] SoAdSocketId

Description
The Socket ID is used as a reference to a particular connection when transferring data
to and from the PDU Router..
Type
INT
Range
0 - 65535
Value
Rationale
supplier.
ID : ETHSW-3318
2.39.5.4.15 [REQ] SoAdSocketLocalIpAddress

Description
Local IP address used for this connection.
Type
STRG
Range
Value
Rationale
GM does not use this parameter currently. Left to the discretion of the supplier.
ID : ETHSW-3335
2.39.5.4.16 [REQ] SoAdSocketLocalPort

Description
Local UDP or TCP port used for this connection. The value of this parameter shall be
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
113 (148)
II
13400 for GM.

Type
INT
Range
0 - 65535
Value
13400
Rationale
The value of this parameter shall be set as per ISO-13400-2 specification.
ID : ETHSW-3352
2.39.5.4.17 [REQ] SoAdSocketProtocol

Description
Specifies the transport protocol (UDP or TCP).. The value of this parameter is defined
Type
ENUM
Range
Value
Rationale
Number of TCP socket connection shall be (No. of testers+1) and number of UDP
socket connection shall be 1. The transport protocol for TCP socket connection shall
be TCP and transport protocol for UDP socket connection shall be UDP.
ID : ETHSW-3369
2.39.5.4.18 [REQ] SoAdSocketRemoteIpAddress
Description
IP address where NM packets are being sent to.
Type
STRG
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
114 (148)
Range
Reg no
Info Class
II
Value
Rationale
GM does not use the Network Management for IP and left to the discretion of the
supplier
ID : ETHSW-3386
2.39.5.4.19 [REQ] SoAdSocketRemotePort

Description
Remote UDP or TCP port used for this connection.. The value of this parameter is
Type
INT
Range
0 - 65535
Value
Rationale
As per ISO 13400-2 spec, test equipment shall transmit UDP control messages to the
DoIP entity with the UDP source port UDP_TEST_EQUIPMENT_REQUEST dynamically
assigned within the dynamic port range (49 15265 535). The value of this parameter
is defined in a project specific document as per dynamic port range in ISO 13400-2
spec.
ID : ETHSW-3403
2.39.5.4.20 [REQ] SoAdSocketTcpInitiate

Description
Specifies the initiator for this TCP connection.. The value of this parameter shall be
FALSE for GM.
Type
BOOL
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
115 (148)
II
Range
Value
FALSE
Rationale
FALSE: This TCP connection is to be initiated in the listen mode.
ID : ETHSW-3420
2.39.5.4.21 [REQ] SoAdSocketTcpNoDelay

Description
Specifies not to use the congestion control mechanism for this connection. This
parameter is only relevant for TCP connections. It will not be defined for UDP
sockets.. The value of this parameter shall be FALSE for GM.
Type
BOOL
Range
Value
FALSE
Rationale
FALSE: This TCP connection will use congestion control.
ID : ETHSW-3437
2.39.5.4.22 [REQ] SoAdSocketUdpListenOnly

Description
Used to disable the transmit functionality on this UDP port. This parameter is only
relevant for UDP connections.. The value of this parameter shall be FALSE for GM.
Type
BOOL
Range
GM Confidential
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
116 (148)
Value
FALSE
Rationale
FALSE: This UDP port can send and receive data
Info Class
II
ID : ETHSW-3454
2.39.5.5 [REQ] SoAdDemEventConnectionParameterRefs

Description
Type
Range
Value
Rationale
supplier.
ID : ETHSW-3471
2.39.5.5.1 [REQ] SOAD_E_AGAIN

Description
"Resource temporarily unavailable" has occured..
Type
SN-REF
Range
Value
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
117 (148)
Rationale
Reg no
Info Class
II
supplier.
ID : ETHSW-3488
2.39.5.5.2 [REQ] SOAD_E_CONNABORTED

Description
"Software caused connection abort" has occured..
Type
SN-REF
Range
Value
Rationale
supplier.
ID : ETHSW-3505
2.39.5.5.3 [REQ] SOAD_E_CONNREFUSED

Description
"Connection refused" has occured..
Type
SN-REF
Range
Value
Rationale
supplier.
ID : ETHSW-3522
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
118 (148)
II
2.39.5.5.4 [REQ] SOAD_E_CONNRESET

Description
"Connection reset by peer" has occured..
Type
SN-REF
Range
Value
Rationale
supplier.
ID : ETHSW-3539
2.39.5.5.5 [REQ] SOAD_E_HOSTDOWN
Description
Reference to the DemEventParameter which shall be issued when the error "Host is
down" has occured..
Type
SN-REF
Range
Value
Rationale
supplier.
ID : ETHSW-3556
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
119 (148)
II
2.39.5.5.6 [REQ] SOAD_E_HOSTUNREACH

Description
Reference to the DemEventParameter which shall be issued when the error "Host is
down" has occured..
Type
SN-REF
Range
Value
Rationale
supplier.
ID : ETHSW-3573
2.39.5.5.7 [REQ] SOAD_E_NETDOWN

Description
Reference to the DemEventParameter which shall be issued when the error "Network
is down" has occured..
Type
SN-REF
Range
Value
Rationale
supplier.
ID : ETHSW-3590
2.39.5.5.8 [REQ] SOAD_E_NETRESET

Description
dropped connection on reset" has occured..
GM Confidential
Document Name:

Approved By:
File
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
120 (148)
Type
SN-REF
Range
Reg no
Info Class
II
Value
Rationale
supplier.
ID : ETHSW-3607
2.39.5.5.9 [REQ] SOAD_E_NETUNREACH

Description
is unreachable" has occured..
Type
SN-REF
Range
Value
Rationale
supplier.
ID : ETHSW-3624
2.39.5.5.10 [REQ] SOAD_E_NOTCONN

Description
Reference to the DemEventParameter which shall be issued when the error "Socket is
not connected" has occured..
Type
SN-REF
Range
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
121 (148)
II
Value
Rationale
supplier.
ID : ETHSW-3641
2.39.5.5.11 [REQ] SOAD_E_PIPE

Description
Reference to the DemEventParameter which shall be issued when the error "Broken
pipe" has occured..
Type
SN-REF
Range
Value
Rationale
supplier.
ID : ETHSW-3658
2.39.5.5.12 [REQ] SOAD_E_SDULENGTH

Description
Reference to the DemEventParameter which shall be issued when the error "SDU
length mismatch" has occured..
Type
SN-REF
Range
Value
Rationale
supplier.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
122 (148)
II
ID : ETHSW-3675
2.39.5.5.13 [REQ] SOAD_E_TIMEDOUT

Description
"Operation timed out" has occured..
Type
SN-REF
Range
Value
Rationale
supplier.
ID : ETHSW-3692
2.39.5.5.14 [REQ] SoAdSocketRoute

Description
Describes the path of a PDU from a socket in the TCP/IP stack to the PDU Router after
reception in the TCP/IP Stack. The value of this parameter is not controlled by GM
Type
Range
Value
Rationale
This configuration is not used currently. May be required in future
ID : ETHSW-3709
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
123 (148)
II
2.39.5.5.15 [REQ] SoAdDestinationSduLength
Description
Length in bytes of the data contained in the PDU.
Type
INT
Range
0 - 65535
Value
Rationale
supplier.
ID : ETHSW-3726
2.39.5.5.16 [REQ] SoAdRxIndicationUL

Description
This parameter defines the name of the <User_RxIndication> in case that
SoAdUserRxIndicationUL is configured to Cdd. If SoAdUserRxIndicationUL equals
PduR Xcp or UdpNm the name of the <User_RxIndication> is fixed and this parameter
is skipped. If SoAdUserRxIndicationUL equals CDD the name of the
<User_RxIndication> is selectable. The value of this parameter is not controlled by
GM and is left to the discretion of the supplier.
Type
FNC-N
Range
Value
Rationale
ID : ETHSW-3743
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
124 (148)
II
2.39.5.5.17 [REQ] SoAdSourceId

Description
ID contained in the packet received on the TCP/IP connection if the PDU header
option is enabled. The value of this parameter is not controlled by GM and is left to
the discretion of the supplier.
Type
INT
Range
0 - 4294967296
Value
Rationale
ID : ETHSW-3760
2.39.5.5.18 [REQ] SoAdUserRxIndicationUL

Description
This parameter defines the upper layer (UL) module to which the indication of the
successfully received SoAd PDU has to be routed via <User_SoAdRxIndication>. This
<User_SoAdRxIndication> has to be invoked when the RX indication is received by the
EthIf module. The value of this parameter is not controlled by GM and is left to the
discretion of the supplier.
Type
ENUM
Range
Value
Rationale
ID : ETHSW-3777
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
125 (148)
II
2.39.5.5.19 [REQ] SoAdDestinationPduRef

Description
Reference to the global PDU structure. The value of this parameter is not controlled
by GM and is left to the discretion of the supplier.
Type
REF
Range
Value
Rationale
ID : ETHSW-3794
2.39.5.5.20 [REQ] SoAdSourceSocketRef

Description
Connection on which the PDU was received. This references an entry in the Socket
Connection Table. The value of this parameter is not controlled by GM and is left to
the discretion of the supplier.
Type
REF
Range
Value
Rationale
ID : ETHSW-3811
2.39.6 [REQ] UdpNm

Description
This container contains all global configuration parameters of UDP NM configured
from the NM Module perspective.. The multiplicity of this module shall be set as
ZERO for GM.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
126 (148)
II
Type
Range
Value
Rationale
This module shall not be used in GM configuration, because GW ECU does not use
UDP NM message to wake up ONSTAR. GW ECU uses CAN NM message to wake up
ONSTAR. Offboard and Onboard testers uses Activation line to wake up GW ECU.
ID : ETHSW-3828
2.39.6.1 [REQ] UdpNmGlobalConfig

ID : ETHSW-3845
2.39.6.1.1 [REQ] UdpNmBusSynchronizationEnabled

ID : ETHSW-3862
2.39.6.1.2 [REQ] UdpNmComControl_Enabled

ID : ETHSW-3879
2.39.6.1.3 [REQ] UdpNmComUserDataSupport

ID : ETHSW-3896
2.39.6.1.4 [REQ] UdpNmCoordinatorEnabled

ID : ETHSW-3913
GM Confidential
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
127 (148)
II
2.39.6.1.5 [REQ] UdpNmCoordinatorId

ID : ETHSW-3930
2.39.6.1.6 [REQ] UdpNmCoordinatorSyncSupport
ID : ETHSW-3947
2.39.6.1.7 [REQ] UdpNmDevErrorDetect

ID : ETHSW-3964
2.39.6.1.8 [REQ] UdpNmImmediateRestartEnabled

ID : ETHSW-3981
2.39.6.1.9 [REQ] UdpNmNodeDetectionEnabled

ID : ETHSW-3998
2.39.6.1.10 [REQ] UdpNmNodeIdEnabled

ID : ETHSW-4015
2.39.6.1.11 [REQ] UdpNmNumberOfChannels

ID : ETHSW-4032
2.39.6.1.12 [REQ] UdpNmPassiveModeEnabled

ID : ETHSW-4049
GM Confidential
Info Class
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
128 (148)
II
2.39.6.1.13 [REQ] UdpNmPduRxIndicationEnabled

ID : ETHSW-4066
2.39.6.1.14 [REQ] UdpNmRemoteSleepIndEnabled

ID : ETHSW-4083
2.39.6.1.15 [REQ] UdpNmRepeatMsgIndEnabled

ID : ETHSW-4100
2.39.6.1.16 [REQ] UdpNmStateChangeIndEnabled

ID : ETHSW-4117
2.39.6.1.17 [REQ] UdpNmUserDataEnabled

ID : ETHSW-4134
2.39.6.1.18 [REQ] UdpNmVersionInfoApi

ID : ETHSW-4151
2.39.6.1.19 [REQ] UdpNmChannelConfig

ID : ETHSW-4168
2.39.6.1.19.1 [REQ] UdpNmNodeId

ID : ETHSW-4185
GM Confidential
Info Class
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
129 (148)
II
2.39.6.1.19.2 [REQ] UdpNmPduCbvPosition

ID : ETHSW-4202
2.39.6.1.19.3 [REQ] UdpNmPduLength

ID : ETHSW-4219
2.39.6.1.19.4 [REQ] UdpNmPduNidPosition

ID : ETHSW-4236
2.39.6.1.19.5 [REQ] UdpNmUserDataLength

ID : ETHSW-4253
2.39.6.1.19.6 [REQ] UpdNmMainFunctionPeriod

ID : ETHSW-4270
2.39.6.1.19.7 [REQ] UpdNmMsgCycleOffset
ID : ETHSW-4287
2.39.6.1.19.8 [REQ] UpdNmMsgCycleTime

ID : ETHSW-4304
GM Confidential
Info Class
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
130 (148)
II
2.39.6.1.19.9 [REQ] UpdNmMsgTimeoutTime

ID : ETHSW-4321
2.39.6.1.19.10 [REQ] UpdNmRemoteSleepIndTime

ID : ETHSW-4338
2.39.6.1.19.11 [REQ] UpdNmRepeatMessageTime

ID : ETHSW-4355
2.39.6.1.19.12 [REQ] UpdNmTimeoutTime

ID : ETHSW-4372
2.39.6.1.19.13 [REQ] UpdNmWaitBusSleepTime

ID : ETHSW-4389
2.39.6.1.19.14 [REQ] UdpNmComMNetworkHandleRef

ID : ETHSW-4406
2.39.6.1.19.15 [REQ] UdpNmRxPdu

ID : ETHSW-4423
2.39.6.1.19.15.1 [REQ] UdpNmRxPduId

ID : ETHSW-4440
GM Confidential
Info Class
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
131 (148)
II
2.39.6.1.19.15.2 [REQ] UdpNmRxPduRef

ID : ETHSW-4457
2.39.6.1.19.16 [REQ] UdpNmTxPdu

ID : ETHSW-4474
2.39.6.1.19.16.1 [REQ] UdpNmTxConfirmationPduId

ID : ETHSW-4491
2.39.6.1.19.16.2 [REQ] UdpNmTxPduRef

ID : ETHSW-4508
2.39.6.1.19.17 [REQ] UdpNmUserDataTxPdu

ID : ETHSW-4525
2.39.6.1.19.17.1 [REQ] UdpNmTxUserDataPduId

ID : ETHSW-4542
2.39.6.1.19.17.2 [REQ] UdpNmTxUserDataPduRef

ID : ETHSW-4559
2.39.6.1.20 [REQ] UdpNmDemEventParameterRefs

ID : ETHSW-4576
GM Confidential
Info Class
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
132 (148)
II
2.39.6.1.20.1 [REQ] UDPNM_E_INIT_FAILED

ID : ETHSW-4593
2.39.6.1.20.2 [REQ] UDPNM_E_NETWORK_TIMEOUT

ID : ETHSW-4610
2.39.6.1.20.3 [REQ] UDPNM_E_TCPIP_TRANSMIT_ERROR
2.40 Additional software components required for Global
Ethernet
ID : ETHSW-531
[REQ] The following section shall specify any additional software component required for Global B
Ethernet serial data communications.
2.40.1 START/STOP Ethernet Communication

ID : ETHSW-4631
[REQ] Global B Ethernet serial data communications requires SW-C to START/STOP Ethernet
communications based on Activation line conditions.
ID : ETHSW-4633
[REQ] The SW-C shall read the activation line condition based on ICU callback or based on DIO pin
through IO Hardware Abstraction Module (IoHwAb).
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
133 (148)
II
Rationale: Both HIGH to LOW transition and LOW to HIGH transition can not be acheived using a single
ICU pin, since ICU pin can detect only either falling edge or rising edge at a time, not together.
ID : ETHSW-4682
[REQ] The SW-C shall validate the real wakeup event from erratic ones.
2.40.1.1 START Ethernet Communication

ID : ETHSW-4634
[REQ] The SW-C shall implement a START-UP delay for activating the Ethernet communications.
ID : ETHSW-4683
[REQ] If the activation line from the Off-board tester/On-board tester becomes
ACTIVATION_LINE_ACTIVE (HIGH), SW-C shall request FULL_COMMUNICATION by invoking ComM
through standard RTE interface.
ID : ETHSW-4701
[REQ] Based on the FULL_COMMUNICATION request from SWC, the mode of Ethernet Controller and
Tranciever shall switch from MODE_DOWN to MODE_ACTIVE state.
ID : ETHSW-4702
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
134 (148)
II
[REQ] If the activation line status of the Off-board tester changes from ACTIVATION_LINE_INACTIVE
(LOW) to ACTIVEACTIVATION_LINE_ACTIVE (HIGH) and TCPIP is in STARTUP state, Dynamic IPv4 address
and Dynamic IPv6 address assignment shall be started in Ethernet Gateway ECU.
ID : ETHSW-4703
[REQ] If the activation line status of the On-board tester changes from ACTIVATION_LINE_INACTIVE
(LOW) to ACTIVEACTIVATION_LINE_ACTIVE (HIGH) and TCPIP is in STATE_STARTUP state, Static IPv4
address assignment shall be started in Ethernet Gateway ECU.
2.40.1.2 STOP Ethernet Communication

ID : ETHSW-4635
[REQ] The SW-C shall implement a STOP delay for de-activating the ethernet communications.
ID : ETHSW-4713
[REQ] If the activation line from the Off-board tester/On-board tester becomes
ACTIVATION_LINE_INACTIVE (LOW) and TCPIP state is not STATE_ONLINE, SW-C shall request
NO_COMMUNICATION by invoking ComM through standard RTE interface and already assigned
Dynamic IPv4 address, Dynamic IPv6 address and Static IPv4 address shall be released from Ethernet
Gateway ECU.
ID : ETHSW-4714
[REQ] Based on the NO_COMMUNICATION request from SWC, the mode of Ethernet Controller and
Tranciever shall switch from MODE_ACTIVE to MODE_DOWN state.
ID : ETHSW-4700
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
135 (148)
II
[REQ] If the activation line status of the Off-board tester/On-board tester changes from
ACTIVATION_LINE_ACTIVE (HIGH) to ACTIVATION_LINE_INACTIVE (LOW) and TCPIP is in ONLINE state ,
SW-C shall not request NO_COMMUNICATION by invoking ComM through standard RTE interface.
2.40.2 Application Callback

ID : ETHSW-4668
[REQ] The SW-C shall implement application callbacks.
2.40.2.1 Vehicle Identification (VIN) Application Callback
ID : ETHSW-4670
[REQ] The SW-C shall implement a Vehicle Identification Application Callback for supporting the Vehicle
Identification Request Message, Vehicle Identification Request With EID Message, Vehicle Identification
Request With VIN Message and Vehicle Announcement Message.
ID : ETHSW-4675
[REQ] Whenever the offboard or onboard tester sends a Vehicle Identification Request Message or
Vehicle Identification Request With EID Message or Vehicle Identification Request With VIN Message,
SoAd module of the Ethernet Gateway ECU shall invoke the Vehicle Identification Application Callback.
ID : ETHSW-4676
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
136 (148)
II
[REQ] Whenever the Ethetnet Gateway ECU wants to send Vehicle Announcement Message, SoAd
module of the Ethetnet Gateway ECU shall invoke the Vehicle Identification Application Callback through
a standard RTE inteface.
ID : ETHSW-4673
[REQ] Vehicle Identification Application Callback shall retrieve the Vehicle Identification Number(VIN)
from the non-volatile memory.
ID : ETHSW-4674
[REQ] Vehicle Identification Application Callback shall retrieve the Vehicle Identification Number(VIN) by
invoking NVRAM manager through a standard RTE inteface.
ID : ETHSW-4724
[REQ] The signature for the Vehicle Identification Application Callback shall be as follows.
Prototype:
Std_ReturnType <SWC>_GetVinInformation (uint8* VinInformation)
Parameters (in):
None.
Parameters (out):
VinInformation ---> Pointer containing the VIN information of the Vehicle. Only valid if the return value
equals E_OK.
Parameters (in/out):
None.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
137 (148)
II
Return value:
Std_ReturnType ---> E_OK: VinInformationcontains valid information
E_NOT_OK: VinInformation contains no valid information
2.40.2.2 Entity Identification (EID) Information
[NOTE] The Entity Identification (EID) Information can be retrieved either from the SoAd Configuration
Container (SoAdDoIpEid) or using Entity Identification Application Callback.
[NOTE] GM prefers to retrieve Entity Identification (EID) Information from the SoAd Configuration
Container (SoAdDoIpEid). In case if the SoAd Configuration Container (SoAdDoIpEid) not available, GM
prefers to use Entity Identification Application Callback.
ID : ETHSW-4671
[REQ] The SW-C shall implement a Entity Identification Application Callback for supporting the Entity
Identification Request Message (payload type 0x0002).
ID : ETHSW-4677
[REQ] Whenever the offboard or onboard tester sends an Entity Identification Request Message, SoAd
module of the Ethetnet Gateway ECU shall invoke the Entity Identification Application Callback.
ID : ETHSW-4678
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
138 (148)
II
[REQ] Entity Identification Application Callback shall retrieve the Entity Identification Number(EID) from
the non-volatile memory.
ID : ETHSW-4679
[REQ] Entity Identification Application Callback shall retrieve the Entity Identification Number(EID) by
ID : ETHSW-4733
[REQ] The signature for the Entity Identification Application Callback shall be as follows.
Prototype:
Std_ReturnType <SWC>_GetEidInformation (uint8* EidInformation)
Parameters (in):
None.
Parameters (out):
EidInformation ---> Pointer containing the EID information of the DOIP node. Only valid if the return
value equals E_OK.
None.
Return value:
Std_ReturnType ---> E_OK: EidInformationcontains valid information
E_NOT_OK: EidInformation contains no valid information
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
139 (148)
II
2.40.2.3 Group Identification (GID) Application Callback

ID : ETHSW-4737
[REQ] The SW-C shall implement a Group Identification Application Callback for supporting the Vehicle
Announcement Message / Vehicle
Identification Response Message (0x0004).
ID : ETHSW-4738
[REQ] Whenever the offboard or onboard tester sends Vehicle Identification Request or Vehicle
Identification Request with EID or Vehicle Identification Request with VIN, SoAd module of the Ethernet
Gateway ECU shall invoke the Group Identification Application Callback.
ID : ETHSW-4742
[REQ] Whenever Ethernet Gateway ECU wants to send Vehicle Announcement Message, SoAd module
of the Ethernet Gateway ECU shall invoke the Group Identification Application Callback.
ID : ETHSW-4739
[REQ] Group Identification Application Callback shall retrieve the Group Identification Number(GID)
from the non-volatile memory.
ID : ETHSW-4740
[REQ] Group Identification Application Callback shall retrieve the Group Identification Number(GID) by
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
140 (148)
II
ID : ETHSW-4741
[REQ] The signature for the Group Identification Application Callback shall be as follows.
Prototype:
Std_ReturnType <SWC>_GetGidInformation (uint8* GidInformation)
Parameters (in):
None.
Parameters (out):
GidInformation ---> Pointer containing the GID information. Only valid if the return value equals E_OK.
None.
Return value:
Std_ReturnType ---> E_OK: GidInformationcontains valid information
E_NOT_OK: GidInformation contains no valid information
2.40.2.4 Diagnostics Power Mode Application Callback

ID : ETHSW-4672
[REQ] The SW-C shall implement a Diagnostics Power Mode Application Callback for supporting the
Diagnostic Power Mode Information Request Message(payload type 0x4003).
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
141 (148)
II
ID : ETHSW-4680
[REQ] Whenever the offboard or onboard tester sends a Diagnostic Power Mode Information Request
Message, SoAd module of the Ethetnet Gateway ECU shall invoke the Diagnostics Power Mode
Application Callback.
ID : ETHSW-4681
[REQ] Diagnostics Power Mode Application Callback shall return the diagnostics power mode (as of
now, return always 0x01: ready) of the vehicle.
ID : ETHSW-4723
[REQ] The signature for the Diagnostics Power Mode Application Callback shall be as follows.
Prototype:
Std_ReturnType <SWC>_GetPowerModeStatus (PowerModeType* PowerMode)
Parameters (in):
None.
Parameters (out):
PowerMode ---> Pointer containing the information of the PowerModeStatus. Only valid if the return
value equals E_OK.
None.
Return value:
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
142 (148)
II
Std_ReturnType ---> E_OK: PowerMode contains valid information

E_NOT_OK: PowerMode contains no valid information
2.40.2.5 Routing Activation Authentification Application Callback

ID : ETHSW-4719
[REQ] The SW-C shall implement a Routing Activation Authentification Application Callback for
supporting the Routing Activation Request Message(payload type 0x0005) with OEM-specific Activation
type (0xE0 [Central security] & 0xE1-0xFF [Available for additional OEM-specific use]).
ID : ETHSW-4720
[REQ] Whenever the offboard or onboard tester sends a Routing Activation Request Message with OEMspecific Activation type, SoAd module of the Ethetnet Gateway ECU shall invoke the Routing Activation
Authentification Application Callback.
ID : ETHSW-4721
[REQ] Routing Activation Authentification Application Callback shall return the authentification result (as
of now, return always TRUE means Authentification was successful) for routing activation request
Message with OEM-specific Activation type (0xE0 & 0xE1-0xFF).
ID : ETHSW-4722
[REQ] The signature for the Routing Activation Authentification Application Callback shall be as follows.
Prototype:
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
143 (148)
II
Std_ReturnType <SWC>_RoutingActivationAuthentication (boolean* Authentified, uint8*

AuthenticationReqData, uint8* AuthenticationResData)
Parameters (in):
AuthenticationReqData --> Pointer to OEM specific bytes for Routing activation request.
Parameters (out):
Authentified ---> Pointer containing the information if Authentication was successful (TRUE) or not
(FALSE). Only valid if the return value equals E_OK.
AuthenticationResData ---> Pointer to OEM specific bytes for Response on Routing activation.
None.
Return value:
Std_ReturnType ---> E_OK: Authentified and AuthenticationResData contain valid Data.
E_PENDING: Authentication still running.
E_NOT_OK: Authentified and/or AuthenticationResData do not contain valid
information.
2.40.2.6 Routing Activation Confirmation Application Callback

ID : ETHSW-4727
[REQ] The SW-C shall implement a Routing Activation Confirmation Application Callback for supporting
the Routing Activation Request Message(payload type 0x0005) with OEM-specific Activation type (0xE0
[Central security] & 0xE1-0xFF [Available for additional OEM-specific use]).
ID : ETHSW-4728
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
144 (148)
II
[REQ] Whenever the offboard or onboard tester sends a Routing Activation Request Message with OEMspecific Activation type, SoAd module of the Ethetnet Gateway ECU shall invoke the Routing Activation
Confirmation Application Callback.
ID : ETHSW-4729
[REQ] Routing Activation Confirmation Application Callback shall return the Confirmation result (as of
now, return always TRUE means Confirmation was successful) for routing activation request Message
with OEM-specific Activation type (0xE0 & 0xE1-0xFF).
ID : ETHSW-4730
[REQ] The signature for the Routing Activation Confirmation Application Callback shall be as follows.
Prototype:
Std_ReturnType <SWC>_RoutingActivationConfirmation (boolean* Confirmed, uint8*
ConfirmationReqData, uint8* ConfirmationResData)
Parameters (in):
ConfirmationReqData -->Pointer to OEM specific bytes for Routing activation request.
Parameters (out):
Confirmed ---> Pointer containing the information if Confirmation was successful (TRUE) or not (FALSE).
Only valid if the return value equals E_OK.
ConfirmationResData ---> Pointer to OEM specific bytes for Response on Routing activation. Contains
valid data if function return with E_OK.
GM Confidential
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
145 (148)
II
None.
Return value:
Std_ReturnType ---> E_OK: Confirmed and ConfirmationResData contain valid Data.
E_PENDING: Confirmation still running.
E_NOT_OK: Confirmed and/or ConfirmationResData do not contain valid information.
2.41 VLAN
VLAN shall be implemented as per Ethernet Communication Strategy.
Notes
Glossary
Acronyms, Abbreviations and Symbols

Explanation
Acronyms,
Abbreviation
s & Symbols
API
Application Interface
APPL
Application
GM Confidential
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
146 (148)
II
ASR
AUTOSAR
AUTOSAR
AUTomotive Open System Architecture
BSW
Basic Software
BswM
Basic Software Manager
CAN
Controller Area Network
CC
Communication Controller
Com
AUTOSAR Communication Service: Communication Interface
ComM
AUTOSAR System Service: Communication Manager
CRC
Cyclic Redundancy Check
CTS
Component Technical Specification
DCM
AUTOSAR Communication Service: Diagnostic Communication Manager
DD
Data Dictionary
DEM
AUTOSAR System Service: Diagnostic Event Manager
DET
AUTOSAR System Service: Development Error Tracer
Drvr
Driver
DTC
Diagnostic Trouble Code
ECU
Electronic Control Unit
EcuM
AUTOSAR System Service: ECU State Manager
EEPROM
Electrically Erasable Programmable Read Only Memory
EMC
Electromagnetic Compatibility
GM Confidential
Info Class
Document Name:

Approved By:
File
Reg no
Info Class
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
147 (148)
II
ENM
Enumerated signal type
ESD
Electrostatic Discharge
FR
FlexRay
FRDG
FlexRay Development Group
GMW
General Motors Worldwide
HW
Hardware
ID
Identifier
If
Interface
I-PDU
Interaction Layer PDU
ISO
International Organization for Standardization
ISR
Interrupt Service Routine
L-PDU
Datalink Layer PDU
LSB
Least Significant Bit/Byte
MSB
Most Significant Bit/Byte
N/A
Not Applicable
NM
Network Management
NMIf
AUTOSAR Communication Service: Network Management Interface
OS
Operating System
OSEK
German: Offene Systeme und deren Schnittstellen fr die Elektronik in Kraftfahrzeugen;

English: "Open Systems and their Interfaces for the Electronics in Motor Vehicles
GM Confidential
Document Name:

Approved By:
File
Reg no
N/A
Issued by:
Date
Issue
Page
EnDG
10/27/2014
V1.7
148 (148)
PDU
Protocol Data Unit
PduR
PDU Router
RTE
AUTOSAR Run Time Environment
Rx
Receive
SAE
Society of Automotive Engineers
SchM
AUTOSAR System Service: Schedule Manager
SM
State Manager
SSTS
Sub-System Technical Specification
TBD
To Be Defined
TP
Transport Protocol
Trcvr
Transceiver
Tx
Transmit
SW-C
Software Component
II
Table 7 Acronyms, Abbreviations and Symbols
GM Confidential
Info Class

GB5401 2014 10 27 Ethernet Software Implementation Specification PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GB5401 2014 10 27 Ethernet Software Implementation Specification PDF

Uploaded by

Copyright:

Available Formats

Document Name:

Ethernet Software Implementation Specification

General Motors Company

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

2.36.1 UDP (required) .................................................................................................................... 36

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

2.37.4.3 I/O signal interface (not required) ................................................................................ 44

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

2.39.1.2 [REQ] EthGeneral ......................................................................................................... 59

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

2.40.2.5 Routing Activation Authentification Application Callback ............................................ 142

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

1.2 Issue History

1.2.1 Revision Log

April 19, 2012

Sep 07, 2012

Oct 12, 2012

Added SW-C requirements

Modified OS from "Required"

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

Added section for Vehicle

July 26, 2013

UDPNM modified from

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

May 19, 2014

Added revision history

Added Section 2.7 on

NMIF changed to not required

Memory modules changed to

Activation Line handling

1.3 Team Membership

1.3.1 Serial Data

GME Serial Data Architecture

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

GMNA Serial Data Architecture

1.3.2 Contracted Experts

1.4 Document Scope

1.5 Requirement Wording Conventions

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

Will a result of an immutable law of physics.

2014 General Motors LLC. All Rights Reserved

Ethernet Software Implementation Specification

2.2 Government Regulations and Documents

2.3 General Motors Documents

Ethernet Communication System Communication

GM AUTOSAR Specification Addendum:Required

Table 2: General Motors Documents

2.4 Industry Documents

Autosar R4.0.3 Specifications

2014 General Motors LLC. All Rights Reserved