This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Srv

1: IntegrationManual_Srv
2: IntegrationManual_Srv_ind
3: IntegrationManual_Srvs
4: ReleaseNotes_Srv
5: ReleaseNotes_Srv_ind
6: ReleaseNotes_Srvs
7: Srv Peer Review Checklists

Srv

Component Documentation

1 - IntegrationManual_Srv

2 - IntegrationManual_Srv_ind

Outline
Page 1
Page 2
Page 3
Page 4
Page 5
Page 6
Page 7
Page 8

3 - IntegrationManual_Srvs

Integration Manual Srv
Project
BMW AUTOSAR Core 4 Rel. 2
Author
BMW AG
Release Date
2015-12-11
Version
3.1.0
Status
Release
Hotline
+49 89 382 - 32233
Contact
bac@bmw.de
https://asc.bmw.com/jira/browse/BSUP (extern)
https://asc.bmwgroup.net/jira/browse/BSUP (intern)
Revision History
Version Date
Changed by
Description
3.1.0
2015-12-
Björn
No changes - only version update
11
Sachsenberg
3.0.1
2015-03-
Björn
No changes - only version update
13
Sachsenberg
3.0.0
2014-10-
Björn
Initial version (taken over from BAC4 1.2.x)
29
Sachsenberg
Company
Bayerische
Motoren Werke
Aktiengesellschaft
Postal address
BMW AG
80788 München
Office address
Forschungs- und
Innovationszentrum
(FIZ)
Hufelandstr. 1
80937 München
Telephone
Switchboard
+49 89 382-0
Internet
www.bmwgroup.com
IntegrationManual_Srv, Version 3.1.0, Platform Software
Page 1 of 8

Table of Contents
1 Introduction
3
1.1
General
3
1.2
Functional overview
3
2 Acronyms and Abbreviations
3
3 Related documentation
4
3.1
BMW Specifications
4
3.2
AUTOSAR Specifications
4
4 Limitations
5
5 Software Architecture
6
5.1
Dependencies on AUTOSAR modules
6
5.2
Dependencies on BMW modules
6
6 Integration
7
6.1
Configuration of other Modules
7
6.2
Configuration
7
6.2.1
General
7
6.2.1.1
HandleEccRam
7
6.2.1.2
HandleEccRom
7
6.2.1.3
MultiCpuEnable
7
6.2.1.4
FeatureSet
7
6.3
Configuration of the RTE
8
6.4
Software Integration
8
6.4.1
Startup/Initialisation
8
6.4.2
Normal Operation
8
6.4.3
Shutdown/Deactivation
8
IntegrationManual_Srv, Version 3.1.0, Platform Software
Page 2 of 8

1
Introduction
1.1 General
For a general introduction to the BAC4 Platform Modules please refer to [1].
This document only describes topics related to the SWT BAC4 Module.
This Integration Manual describes the basis functionality, API and the configuration of the BMW
system function Srv.
1.2 Functional overview
The Srv (Service) module contains some general purpose functions commonly used by other
modules like Dlog, Prog and Bm. It is used in Application, Bootloader and Bootmanager.
2
Acronyms and Abbreviations
Abbreviation/AcronymDescription
AUTOSAR
Automotive Open System Architecture
BAC
BMW AUTOSAR Core
ECU
Electronic Control Unit
IntegrationManual_Srv, Version 3.1.0, Platform Software
Page 3 of 8

3
Related documentation
3.1 BMW Specifications
[1] BAC4 General Concept for the Module Integration
BAC4_General_Concepts_for_the_Module_Integration.pdf
3.2 AUTOSAR Specifications
[2] Specification of Diagnostic Communication Manager
AUTOSAR_SWS_DiagnosticCommunicationManager
IntegrationManual_Srv, Version 3.1.0, Platform Software
Page 4 of 8

4
Limitations
No limitations known.
IntegrationManual_Srv, Version 3.1.0, Platform Software
Page 5 of 8

5
Software Architecture
5.1 Dependencies on AUTOSAR modules
Dcm
The module Dcm [2] is needed for the type definition Dcm_ProgConditionsType.
5.2 Dependencies on BMW modules
IntegrationManual_Srv, Version 3.1.0, Platform Software
Page 6 of 8

6
Integration
6.1 Configuration of other Modules
Nothing to be done here.
6.2 Configuration
The Srv configuration contains the following containers:
Srv General
6.2.1 General
This container contains the configuration (parameters) of the Srv module. Note that these
configuration parameters also affect the configuration of other modules such as Dlog, Prog, etc.
6.2.1.1 HandleEccRam
This should be enabled if the hardware handles ECC errors in RAM.
6.2.1.2 HandleEccRom
This should be enabled if the hardware handles ECC errors in ROM.
6.2.1.3 MultiCpuEnable
This should be enabled if a multi CPU ECU is used. Note that communication to the slave CPUs
is done via integrator/user defined functions. Please consult the corresponding modules'
integration manuals for details about those functions.
6.2.1.4 FeatureSet
Defines the feature set that will be provided. For SRV_FS_BOOTMANAGER and SRV_FS_BLU
it is reduced to save space in Bootmanager and Blu, respectively. Should be SRV_FS_FULL in
Bootloader and Application.
IntegrationManual_Srv, Version 3.1.0, Platform Software
Page 7 of 8

6.3 Configuration of the RTE
No RTE needed.
6.4 Software Integration
6.4.1 Startup/Initialisation
Nothing to be done here.
6.4.2 Normal Operation
Nothing to be done here.
6.4.3 Shutdown/Deactivation
Nothing to be done here.
IntegrationManual_Srv, Version 3.1.0, Platform Software
Page 8 of 8

Document Outline

4 - ReleaseNotes_Srv

5 - ReleaseNotes_Srv_ind

Outline
Page 1
Page 2
Page 3

6 - ReleaseNotes_Srvs

Release Notes Srv
Project
BMW AUTOSAR Core 4 Rel. 2
Author
BMW AG
Release Date
2015-12-11
Version
3.1.0
Status
Release
Hotline
+49 89 382 - 32233
Contact
bac@bmw.de
https://asc.bmw.com/jira/browse/BSUP (extern)
https://asc.bmwgroup.net/jira/browse/BSUP (intern)
Revision History
Version
Date
Issues
3.1.0
2015-12-11
BAC-4692
3.0.1
2015-03-13
BAC-3938, BAC-3651
3.0.0
2014-10-29
Company
Bayerische
Motoren Werke
Aktiengesellschaft
Postal address
BMW AG
80788 München
Office address
Forschungs- und
Innovationszentrum
(FIZ)
Hufelandstr. 1
80937 München
Telephone
Switchboard
+49 89 382-0
Internet
www.bmwgroup.com
ReleaseNotes_Srv, Version 3.1.0, Platform Software
Page 1 of 3

1
Package Enumeration Scheme
Every package carries a 3-digit version number. The following table explains how compatibility between
versions can be determined from the version number:
Changed Version
Example
Compatibility
Patch Version
1.0.0 → 1.0.1
A defect has been fixed. Versions are fully
compatible.
Minor Version
1.0.0 → 1.1.0
API of package changed or a new feature was
added. Versions may not be compatible. If the new
package is used, other packages may be changed
as well.
Major Version
1.0.0 → 2.0.0
Indicates the BAC4 Release, in which the module
is delivered. Major Version 2 of a module refers to
BAC4 Rel. 1. Major Version 3 of a module refers to
BAC4 Rel. 2.
2
Package Description
The Srv (Service) module contains some general purpose functions commonly used by other modules
like Dlog, Prog and Bm. It is used in Application, Bootloader and Bootmanager.
This package is maintained by BMW AUTOSAR Core 4 Support, via ASCENT Jira
(https://asc.bmwgroup.net/jira/browse/BSUP or https://asc.bmw.com/jira/browse/BSUP) or telephone
hotline (+49-89-382-32233).
3
Revisions and Modifications
3.1 Revision 3.1.0 [Released]
Item
Description
CR ID:
BAC-4692
CR Headline:
Srv: Adapt ECUC and SWCD schema to 4.2.2
Description of Issues:
Adapt ECUC schema to 4.2.2
Description of Changes:
Adapt ECUC schema to 4.2.2
Changed Files:
autosar/Asr40/Srv_paramdef.arxml
Compatibility:
3.2 Revision 3.0.1 [Released]
Item
Description
CR ID:
BAC-3938
CR Headline:
Srv: Set Parameters' ConfigClass from container
CommonPublishedInformation to PUBLISHED-INFORMATION
ReleaseNotes_Srv, Version 3.1.0, Platform Software
Page 2 of 3

Description of Issues:
Although the module's version is checked during pre-compile
there's no need to have this parameter configurable to the user.
Therefore, all modules should have the ConfigClass from the
parameters SwMajorVersion, SwMinorVersion and
SwPatchVersion set to PUBLISHED-INFORMATION.
Description of Changes:
set config class of CommonPublishedInformation to
PUBLISHED-INFORMATION
Changed Files:
autosar/Asr40/Srv_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-3651
CR Headline:
Srv: Adapt makefiles to EA requirements
Description of Issues:
Adapt makefiles to EA requirements
Description of Changes:
Adapt makefiles to EA requirements
Changed Files:
generate/verify/Srv.autoverify.tt
make/Srv_defs.mak
Compatibility:
3.3 Revision 3.0.0 [Released]
Item
Description
CR ID:
CR Headline:
Initial Release for SP2018
Description of Issues:
Initial Release for SP2018
Description of Changes:
Initial Release for SP2018
Changed Files:
Compatibility:
ReleaseNotes_Srv, Version 3.1.0, Platform Software
Page 3 of 3

Document Outline

7 - Srv Peer Review Checklists

Overview

Summary Sheet
Synergy Project
3rd Party Files

Sheet 1: Summary Sheet

Rev 1.0

19-Apr-17

Peer Review Summary Sheet

Synergy Project Name:

Windows User: Intended Use: Identify which component is being reviewed. This should match the component short name and the middle part of the Synergy project name Srv

Revision / Baseline:

Windows User: Intended Use: Identify the implementation baseline name intended to be used for the changed component when changes are approved. Srv_Bac_Ar4.2.2_03.01.00_Bmw_0

Change Owner:

Windows User: Intended Use: Identify the developer who made the change(s) being reviewed Akilan Rathakrishnan

Work CR ID:

Windows User: Intended Use: Identify the Implementation Work CR whose work is being reviewed (may be more than one) EA4#4713

3rd party delivery package identifier:

Intended Use: This is a reference to the identifier of the 3rd party delivery package(s) that the component was extracted/created from. Rationale: This will allow easier tracing back to 3rd party deliveries. CBD1700369_D02_Rh850

Windows User: Identifiy which type of 3rd party component this is so as to provide appropriate review checklist sheets Component Type:

Windows User: General section for summarizing review comments or review notes. Review Checklist Summary:

Comments:

Sheet 2: Synergy Project

Peer Review Meeting Log (Component Synergy Project Review)

Quality Check Items:

Rationale is required for all answers of No

New baseline version name from Summary Sheet follows

Yes

Comments:

naming convention for 3rd Party Software Components

Project contains necessary subprojects

N/A

Comments:

Project contains the correct version of subprojects

N/A

Comments:

General Notes / Comments:

LN: Intended Use: Identify who were the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. KMC: Group Review Level removed in Rev 4.0 since the design review is not checked in until approved, so it would always be DR4. Review Board:

Change Owner:

Akilan Rathakrishnan

Review Date :

09/28/17

Lead Peer Reviewer:

Kevin Smith

Approved by Reviewer(s):

Yes

Other Reviewer(s):

Sheet 3: 3rd Party Files

Peer Review Meeting Log (3rd Party File Review)

Quality Check Items:

Rationale is required for all answers of No

(e.g. component_bswmd.arxml) Component "autosar" folder contains autosar module description file from 3rd party delivery package

Yes

Comments:

(e.g. component_preo.arxml) Component "autosar" folder contains any relevant preconfiguration files from 3rd party delivery package(s)

N/A

Comments:

If needed as in the case with Renesas MCAL (e.g. MCALcomponent_bswmd_rec.arxml taken from Vector delivery) Component "autosar" folder contains any needed supplemental autosar module description file(s)

N/A

Comments:

Component "doc" folder contains all documentation related to this component from 3rd party delivery package

Yes

Comments:

Modifications from delivery to be reviewed (e.g. path changes) Component "generate" folder contains all external generation files from 3rd party delivery package

Yes

Comments:

Component "include" and "src" folder contains exact component files from 3rd party delivery package

Yes

Comments:

Component "make" folder contains any makefiles included from 3rd party delivery package

Yes

Comments:

1) All source and headers of component should be referenced in .gpj 2) Compiler settings may need to be tailored to source component (e.g. Renesas MCAL vs Vector BSWs) Component "tools" folder contains GHS project file with appropriate files referenced with appropriate compiler settings

Yes

Comments:

Should delete old existing files/directories from integration project and copy new ones into integration project May also contain logic for integrator user interaction if required. (e.g. selection of micro variant on MCAL) Component "tools" folder contains Integrate.bat with appropriate logic in it for integration into project

Yes

Comments:

For external generation and internal behavior definition for use with Vector Davinci tools. Typically only desired/needed for non-Vector developed components. This file should be copied as part of Integrate.bat. Components optionally contains settings xml file with appropriate contents

Yes

Comments:

General Notes / Comments:

LN: Intended Use: Identify who were the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. KMC: Group Review Level removed in Rev 4.0 since the design review is not checked in until approved, so it would always be DR4. Review Board:

Change Owner:

Akilan Rathakrishnan

Review Date :

09/28/17

Lead Peer Reviewer:

Kevin Smith

Approved by Reviewer(s):

Yes

Other Reviewer(s):