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

Return to the regular view of this page.

SysTime

SysTime

Component Documentation

1 - SysTime Peer Review Checklists

Overview

Summary Sheet
Synergy Project
3rd Party Files

Sheet 1: Summary Sheet























Rev 1.019-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 SysTime
Revision / Baseline:


Windows User: Intended Use: Identify the implementation baseline name intended to be used for the changed component when changes are approved. SysTime_Bac_Ar4.3.0_05.00.03_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#21734


























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_D04_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 :

03/15/18
































Lead Peer Reviewer:


Kevin Smith


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Rijvi Ahmed





































































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 packageYes
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 packageYes
Comments:




































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




































Component "include" and "src" folder contains exact component files from 3rd party delivery packageYes
Comments:




































Component "make" folder contains any makefiles included from 3rd party delivery packageYes
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 settingsYes
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 projectYes
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 contentsYes
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 :

03/15/18

































Lead Peer Reviewer:


Kevin Smith


Approved by Reviewer(s):



Yes
































Other Reviewer(s):


Rijvi Ahmed







































































2 - SysTimeClassic_IntegrationManual

3 - SysTimeClassic_IntegrationManual_ind

Outline
Page 1
Page 2
Page 3
Page 4
Page 5
Page 6
Page 7
Page 8
Page 9
Page 10
Page 11

4 - SysTimeClassic_IntegrationManuals


SysTime Classic Integration Manual
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.0.3
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
Description
5.0.3
2017-12-14
Version Update
5.0.2
2017-10-12
Version Update
5.0.1
2017-08-10
Version update, no change of content.
5.0.0
2017-06-08
Initial version for SP2021
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
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 1 of 11

Table of Contents
1 Introduction
3
1.1
Functional overview
3
2 Related documentation
4
3 Limitations
5
4 Software Architecture
6
4.1
Dependencies on AUTOSAR modules
6
4.1.1
RTE
6
4.1.2
Det
6
4.1.3
Dcm
6
4.1.4
Dem
6
4.1.5
Com
6
4.1.6
BswM
6
4.2
Dependencies to other modules
6
5 Integration
7
5.1
Configuration of other Modules
7
5.1.1
Dcm
7
5.1.2
Com
7
5.1.3
Dem
7
5.1.4
BswM
8
5.1.5
Det
8
5.2
Configuration of generic part
8
5.2.1
SysTimeGeneral
8
5.2.1.1
SysTimeDevErrorDetect
8
5.2.1.2
SysTimeMainTaskCycle
9
5.2.1.3
SysTimeInitialTimeout
9
5.3
Configuration of adapter part
9
5.3.1
SysTimeGeneral
9
5.3.1.1
SysTimeEnableServiceInterface
9
5.4
Configuration of the RTE
9
5.4.1
Assembly Software Connectors
9
5.4.1.1
Dcm
10
5.4.1.2
Dem
10
5.4.1.3
Det
10
5.4.1.4
BswM
10
5.4.1.5
Other Application SWC
10
5.4.2
Event Mapping
10
5.4.3
Data Mapping
10
5.4.4
Exclusive Areas
11
5.5
Software Integration
11
5.5.1
Startup/Initialization
11
5.5.2
Normal Operation
11
5.5.3
Shutdown/Deactivation
11
5.5.4
SWCD
11
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 2 of 11

1
Introduction
This Integration Manual describes the basic functionality of the BMW system function "System Time
Client", the configuration of the SysTime module and of dependant modules, and the integration of the
SysTime module into the BAC4.
[IM_SysTime_0001] dThe SysTime module shall be integrated in every diagnosable ECU.
c(DMA_PA_9033)
Functional overview
The system time represents the time, which has passed since the initialization of the System Time
Master. The main objective of the System Time Client functionality is to maintain the current system time
for the local ECU. This means:
Receiving the system time from the System Time Master
Interpolation of the system time if no system time signal was received from the System Time Master
Providing the system time to the Dem and to other software components
Providing the system time for diagnostic requests
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 3 of 11

2
Related documentation
References
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 4 of 11

3
Limitations
No limitations are known.
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 5 of 11

4
Software Architecture
Dependencies on AUTOSAR modules
The current version of the Module SysTime depends on the following BSW modules:
RTE
As a software component, the SysTime module uses Rte client/server communication as well as
sender/receiver communication to communicate with other SWCs and BSW modules. Additionally the
scheduling is done by the Rte.
Det
The System Time Client optionally reports development errors to the Det.
Dcm
The System Time Client implements a ReadDataByIdentifier service. Dcm shall be configured in a way,
that it dispatches the job 0x22 0x17 0x01 to the SysTime SWC.
Dem
The System Time Client provides a port interface for the Dem to get the current system time, which will
be attached to an event as event related data.
Com
The System Time Client receives the signal containing the current system time from the Com module.
BswM
The System Time Client receives and requests mode switches from the BswM.
Dependencies to other modules
SysTime does not have dependencies to other modules.
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 6 of 11

5
Integration
Configuration of other Modules
The following modules shall be configured, before this module can be generated, compiled and linked.
Dcm
[IM_SysTimeClassic_0003] dThe ReadDataByIdentifier request 0x22 0x17 0x01 shall be configured
in the Dcm module with the following settings:
a container "DcmDspData" with
a "DcmDspDataSize" of 32 bit (4 bytes)
"DcmDspDataType" =
UINT8N”DcmDspDataUseP ort” = USE_DAT A_SY NCH_CLIENT _SERV ER
"DcmDspDataConditionCheckReadFncUsed" = FALSE
a container "DcmDspDid" with
"DcmDspDidIdentifier" = 0x1701
only read-access, without session or security restrictions
one DID Signal "DcmDspDidSignal" with Data Position = 0 and a Data Reference to the
"DcmDspData" container configured before.
c(DMA_PA_8550, DMA_PA_8551, DMA_PA_8552)
Com
In the Com module, a signal has to be configured, that receives the message containing the 32-bit
system time from the bus.
Note: In a Can or FlexRay environment, the system time is received within the signal named
T_SEC_COU_REL. In an Ethernet environment, the system time is received within the Parameter
"timeSecondCounterRelative" of the Event "RelativeTimeBN2020".
Dem
[IM_SysTimeClassic_0006] dTo attach the system time to a freeze frame of a Dem entry, the
following has to be configured in the Dem module:
a Data Element Class "DemDataElementClass"
of type "DemExternalCSDataElementClass"
with a size "DemDataElementDataSize" of 4 byte
with port usage "DemDataElementUsePort" = TRUE
a Data Id "DemDidClass" with reference to the Data Element Class mentioned above
with reference to the Data Element Class mentioned above
with "DemDidIdentifier" = 0x1701
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 7 of 11

a Freeze Frame Class "DemFreezeFrameClass" with reference to the Data Id above
This DemFreezeFrameClass has to be referenced in the "DemDTCAttributes" of every DTC.
c(DK_T3_1374, DK_T3_452, DK_T3_453)
BswM
The BswM has to provide one BswMModeRequestPort to receive mode switches of the
ModeDeclarationGroup "SysTime_LifeCycle" from the SysTime module, and one RteModeRequestPort
to request modes of the ModeDeclarationGroup "SysTime_LifeCycle".
To initialize the SysTime module the BswM has to provide a rule, that results in an action that requests
the mode "SYSTIME_INITIALIZED"of the mode declaration group "SysTime_LifeCycle".
To set the SysTime module to normal operation mode the BswM has to provide a rule, that results in an
action that requests the mode "SYSTIME_RUNNING" of the mode declaration group
"SysTime_LifeCycle". This rule shall be triggered, if the mode has been switched to
"SYSTIME_INITIALIZED" by the SysTime module itself, AND it is technically possible to receive the
system time on the bus. When the SysTime module is in normal operation mode, the SysTime module
switches the mode to "SYSTIME_RUNNING".
To deactivate the SysTime module the BswM has to provide a rule, that results in an action that requests
the mode "SYSTIME_STOPPED" of the mode declaration group "SysTime_LifeCycle".
For details on how to initialize / deactivate the SysTime module, please refer to chapter 6.4.
Det
A SysTime entry shall be added to the Software Component List from Det. This is only necessary, if the
parameter "SysTimeDevErrorDetect" is set to "true" (see chapter 6.2).
Configuration of generic part
SysTimeGeneral
This container contains the configuration parameters of the generic part of the SysTime module
SysTimeDevErrorDetect
This parameter activates/deactivates the Development Error Detection and Notification.
If set to true: Development Error Detection and Notification is activated. If set to false: Development Error
Detection and Notification is deactivated.
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 8 of 11

SysTimeMainTaskCycle
This parameter describes the cycle rate, in which the function "SysTime_MainFunction" is called. This
value has to be configured according to the cycle time of the task, which the Timing Event "TimingEvent"
is mapped to (see chapter 6.3.1). Allowed values are 0.01s (10ms) to 0.10s (100ms).
The function "SysTime_MainFunction" is mapped to the Runnable Entity "MainFunction", which is
triggered by the Timing Event "TimingEvent".
SysTimeInitialTimeout
[IM_SysTime_0002] dThis parameter describes the initial timeout value for the system time signal. The
System Time Client will set the system time to 0xFFFFFFFF, if no valid system time has been received
until this timeout has expired. If the system time signal is received via Can, FlexRay or Ethernet, this
parameter has to be set to 5.0 seconds. c(DMA_PA_8471)
Configuration of adapter part
SysTimeGeneral
This container contains the configuration parameters of the classic adapter of the SysTime module.
SysTimeEnableServiceInterface
This parameter describes whether the system time is received via Service Interface or via a plain signal.
On Ethernet the system time is transmitted via Parameter "timeSecondCounterRelative" of Event
"RelativeTimeBN2020" of Service Interface "VehicleInformation". On Can and Flexray the system time is
transmitted via Signal T_SEC_COU_REL.
true: system time is received via Service Interface (needed for Ethernet communication)
false: System time is received via plain signal (needed for Can and Flexray communication)
Configuration of the RTE
After performing the steps indicated in chapter 6.1 and 6.2, the RTE configuration can be started. In other
way, the RTE will report an interface incompatibility error.
Assembly Software Connectors
The ports of the SysTime module have to be connected with ports of other modules as follows:
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 9 of 11

Dcm
[IM_SysTimeClassic_0002] dSystemTime <-> DataServices_<Data> where <Data> is the name of
the corresponding container "DcmDspData" configured in the Dcm module. c(DMA_PA_8552)
Dem
[IM_SysTimeClassic_0007] dSystemTime <-> CBReadData_<SyncDataElement> where
<SyncDataElement> is the name of the corresponding container "DemDataElementClass" configured in
the Dem module. c(DK_T3_1374)
Det
SysTimeReportError <-> DS<xxx> where <xxx> is an identifier of the module id of the SysTime
configured in the Det module.
BswM
LifeCycle <-> BswMModeRequestPort_xxx where BswMModeRequestPort_xxx means the R-Port of the
BswM that receives a mode switch from the SysTime module. LifeCycleRequest <->
RteModeRequestPort_xxx where RteModeRequestPort_xxx means the P-Port of the BswM that provides
a mode request to the SysTime module.
Other Application SWC
SysTime <-> ApplicationPort where ApplicationPort means the R-Port of an Application SWC that wants
to read the current system time from the SysTime module.
Event Mapping
The timing event "TimingEvent" of the SysTime module has to be mapped to a cyclic task with a cycle
time according to parameter "SysTimeMainTaskCycle" in chapter 6.2. The data received event
"SysTimeRx" has to be mapped to an os-task.
Data Mapping
[IM_SysTimeClassic_0001] dIf the system time is received via Can or FlexRay, the data element
"timeSignal" of the sender-receiver-interface "SysTimeRx" has to be mapped to the signal in the Com
configuration mentioned in chapter 6.1. In the BNE export this signal is named T_SEC_COU_REL.
c(DMA_PA_8471)
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 10 of 11

If the system time is received via Ethernet, the data element "RelativeTimeBN2020" of the
sender-receiver-interface "SysTimeEventRx" has to be mapped to the signal group in the Com
configuration, which represents the Event "RelativeTimeBN2020".
Exclusive Areas
The exclusive area "SysTimeGetTimeArea" has to be configured in the RTE.
Software Integration
Startup/Initialization
Before initialization of the SysTime module, the Det module and the RTE have to be initialized.
[IM_SysTimeClassic_0004] dTo initialize the SysTime module, the BswM shall request the mode
"SYSTIME_INITIALIZED" of the mode declaration group "SysTime_LifeCycle". This shall be done before
any monitoring function is active which could lead to error memory entries. c(DMA_PA_8300)
When initialization of the SysTime has been finished successfully, the SysTime module switches the
mode to "SYSTIME_INITIALIZED".
Normal Operation
When the SysTime module switches the mode to "SYSTIME_INITIALIZED", AND it is technically
possible to receive the system time on the bus, the BswM shall request the mode
"SYSTIME_RUNNING". When the SysTime module switches the mode to "SYSTIME_RUNNING", the
module is in normal operation mode.
Shutdown/Deactivation
[IM_SysTimeClassic_0005] dTo deactivate the SysTime module, the BswM has to request the mode
"SYSTIME_STOPPED". When the SysTime module switches the mode to "SYSTIME_STOPPED", the
module is deactivated. This shall not be done as long as any monitoring function is active which could
lead to error memory entries. c(DMA_PA_8300)
SWCD
If the modules Dem and Dcm are configured correctly, there should be no changes necessary in the file
SysTime_ext_interfaces.arxml. If the RTE importer complains about incompatible interfaces, please
check the Dem and Dcm configuration, or adapt the interfaces in SysTime_ext_interfaces.arxml according
to the generated Software Component Description files of Dcm and Dem.
SysTimeClassic_IntegrationManual.pdf, Version 5.0.3, Software Platforms
Page 11 of 11

Document Outline

5 - SysTimeClassic_ReleaseNotes

6 - SysTimeClassic_ReleaseNotes_ind

Outline
Page 1
Page 2
Page 3
Page 4

7 - SysTimeClassic_ReleaseNotess


Release Notes SysTimeClassic
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.0.3
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
5.0.3
2017-12-14
BAC-6695
5.0.2
2017-10-12
BAC-5176, BAC-6230, BAC-6433
5.0.1
2017-08-10
BAC-6204, BAC-6200
5.0.0
2017-06-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_SysTimeClassic, Version 5.0.3, Software Platforms
Page 1 of 4

1
Module Description
This package contains the adapter for a classic AUTOSAR platform for the SysTimeGeneric package. The
System Time Client is modeled as an AUTOSAR software component (SWC) residing above the RTE.
2
Revisions and Modifications
Revision 5.0.3 [Released]
Item
Description
CR ID:
BAC-6695
CR Headline:
Fix MISRA violations
Description of Issues:
SysTime has MISRA violations.
Description of Changes:
Fixed MISRA violations where reasonable.
Changed Files:
src/SysTime_ConcAdapter.c
src/SysTimeClassic.c
src/SysTime_TimerAdapter.c
include/SysTime_AssertAdapter.h
Compatibility:
Revision 5.0.2 [Released]
Item
Description
CR ID:
BAC-5176
CR Headline:
BAC modules paramdef violate TPS_ECUC_06004
Description of Issues:
According to AUTOSAR_TPS_ECUConfiguration
TPS_ECUC_06004 an AdminData field is required at the
beginning of every ECU Configuration Parameter Definition XML
file.
Description of Changes:
Added AdminData field containing module version and release
date.
Changed Files:
cfgdesc/SysTimeClassic_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6230
CR Headline:
Usage of IMPLEMENTATION-CONFIG-CLASSES in BMW
modules is invalid according to ASR4.2.2
Description of Issues:
Elements IMPLEMENTATION-CONFIG-CLASSES containing
ECUC-IMPLEMENTATION-CONFIGURATION-CLASS are
deprecated.They shall be replaced by VALUE-CONFIG-
CLASSES/ECUC-VALUE-CONFIGURATION-CLASS and/or
MULTIPLICITY-CONFIG-CLASSES/ECUC-MULTIPLICITY-
CONFIGURATION-CLASS
ReleaseNotes_SysTimeClassic, Version 5.0.3, Software Platforms
Page 2 of 4

Description of Changes:
Replaced IMPLEMENTATION-CONFIG-CLASSES by
VALUE-CONFIG-CLASSES, added
MULTIPLICITY-CONFIG-CLASSES where necessary.
Changed Files:
cfgdesc/SysTimeClassic_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6433
CR Headline:
Schema of paramdefs, paramconfs and SWCDen should be
AUTOSAR_4-3-0_STRICT_COMPACT.xsd
Description of Issues:
Schema of parameter definition files and SWCDs should be
conform to AUTOSAR_4-3-0_STRICT_COMPACT.xsd
Description of Changes:
Adapted parameter definition files and SWCDs to schema
AUTOSAR_4-3-0_STRICT_COMPACT.
Changed Files:
cfgdesc/SysTimeClassic_paramdef.arxml
generate/meta/SysTime_ext_interfaces.arxml.pgen
generate/meta/SysTime_internal.arxml.pgen
generate/meta/SysTime_interfaces.arxml.pgen
Compatibility:
Revision 5.0.1 [Released]
Item
Description
CR ID:
BAC-6204
CR Headline:
SysTime: Wrong cross version check for classic adapter
Description of Issues:
SysTimeClassic_Version.h uses wrong cross version check of
generic part.
Description of Changes:
Correct cross version check in classic adapter.
Changed Files:
generate/include/SysTimeClassic_Version.h.pgen
Compatibility:
Item
Description
CR ID:
BAC-6200
CR Headline:
Improve Requirements Traceability
Description of Issues:
Add requirements from IntegrationManual to RequirementsTable.
Description of Changes:
Added requirements from IntegrationManual to
RequirementsTable.
Changed Files:
Compatibility:
Revision 5.0.0 [Released]
Item
Description
CR ID:
CR Headline:
Initial Release for SP2021
Description of Issues:
Initial Release for SP2021
ReleaseNotes_SysTimeClassic, Version 5.0.3, Software Platforms
Page 3 of 4

Description of Changes:
Initial Release for SP2021
Changed Files:
Compatibility:
ReleaseNotes_SysTimeClassic, Version 5.0.3, Software Platforms
Page 4 of 4

Document Outline

8 - SysTimeClassic_RequirementsTable

9 - SysTimeClassic_RequirementsTable_ind

Outline
Page 1
Page 2
Page 3
Page 4

10 - SysTimeClassic_RequirementsTables


SysTime Classic Requirements Table
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.0.3
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
5.0.3
2017-12-14
JC-42
Version Update
5.0.2
2017-10-12
JC-42
Version Update
5.0.1
2017-08-10
JC-42
BAC-6200: Add integration requirements.
5.0.0
2017-06-29
JC-42
Initial version for SP2021.
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
SysTimeClassic_RequirementsTable.pdf, Version 5.0.3, Software Platforms
Page 1 of 4

Table of Contents
1 Related documentation
3
2 Requirements Table
4
SysTimeClassic_RequirementsTable.pdf, Version 5.0.3, Software Platforms
Page 2 of 4

1
Related documentation
References
[1] LH Diagnosemaster Systembeschreibung
SAP: 10000504-000-13
[2] Diagnose - Systembeschreibung
SAP: 10000784-000-12
SysTimeClassic_RequirementsTable.pdf, Version 5.0.3, Software Platforms
Page 3 of 4

2
Requirements Table
The Requirements are taken from [1] and [2].
Requirement
Description
Satisfied by
[DK_T3_1374]
No description
[IM_SysTimeClassic_0006]
[IM_SysTimeClassic_0007]
[DK_T3_452]
No description
[IM_SysTimeClassic_0006]
[DK_T3_453]
No description
[IM_SysTimeClassic_0006]
[DMA_PA_8300]
No description
[IM_SysTimeClassic_0004]
[IM_SysTimeClassic_0005]
[DMA_PA_8471]
No description
[IM_SysTimeClassic_0001]
[DMA_PA_8550]
No description
[IM_SysTimeClassic_0003]
[DMA_PA_8551]
No description
[IM_SysTimeClassic_0003]
[DMA_PA_8552]
No description
[IM_SysTimeClassic_0002]
[IM_SysTimeClassic_0003]
SysTimeClassic_RequirementsTable.pdf, Version 5.0.3, Software Platforms
Page 4 of 4

Document Outline

11 - SysTimeGeneric_ReleaseNotes

12 - SysTimeGeneric_ReleaseNotes_ind

Outline
Page 1
Page 2
Page 3

13 - SysTimeGeneric_ReleaseNotess


Release Notes SysTimeGeneric
Project
BMW AUTOSAR Core 4 Rel. 3 and adaptive BMW AUTOSAR Core Rel. 1
Author
BMW AG
Release Date
2017-12-14
Version
5.0.3
Status
Release
Hotline
+49 89 382 - 32233 (classic) / +49 89 382 - 22522 (adaptive)
Contact
bac@bmw.de (classic) / abac@bmw.de (adaptive)
https://asc.bmw.com/jira/browse/BSUP (extern)
https://asc.bmwgroup.net/jira/browse/BSUP (intern)
Revision History
Version
Date
Issues
5.0.3
2017-12-14
BAC-6695
5.0.2
2017-10-12
BAC-5176, BAC-6230, BAC-6433
5.0.1
2017-08-10
BAC-6200
5.0.0
2017-06-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_SysTimeGeneric, Version 5.0.3, Software Platforms
Page 1 of 3

1
Module Description
The system time represents the time, which has passed since the initialization of the System Time
Master. The main objective of the System Time Client functionality is to maintain the current system time
for the local ECU. This means: - Receiving the system time from the System Time Master - Interpolation
of the system time if no system time signal was received from the System Time Master - Providing the
system time to the Dem and to other software components - Providing the system time for diagnostic
requests
2
Revisions and Modifications
Revision 5.0.3 [Released]
Item
Description
CR ID:
BAC-6695
CR Headline:
Fix MISRA violations
Description of Issues:
SysTime has MISRA violations.
Description of Changes:
Fixed MISRA violations where reasonable.
Changed Files:
src/SysTime.c
Compatibility:
Revision 5.0.2 [Released]
Item
Description
CR ID:
BAC-5176
CR Headline:
BAC modules paramdef violate TPS_ECUC_06004
Description of Issues:
According to AUTOSAR_TPS_ECUConfiguration
TPS_ECUC_06004 an AdminData field is required at the
beginning of every ECU Configuration Parameter Definition XML
file.
Description of Changes:
Added AdminData field containing module version and release
date.
Changed Files:
cfgdesc/SysTime_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6230
CR Headline:
Usage of IMPLEMENTATION-CONFIG-CLASSES in BMW
modules is invalid according to ASR4.2.2
Description of Issues:
Elements IMPLEMENTATION-CONFIG-CLASSES containing
ECUC-IMPLEMENTATION-CONFIGURATION-CLASS are
deprecated.They shall be replaced by VALUE-CONFIG-
CLASSES/ECUC-VALUE-CONFIGURATION-CLASS and/or
MULTIPLICITY-CONFIG-CLASSES/ECUC-MULTIPLICITY-
CONFIGURATION-CLASS
ReleaseNotes_SysTimeGeneric, Version 5.0.3, Software Platforms
Page 2 of 3

Description of Changes:
Replaced IMPLEMENTATION-CONFIG-CLASSES by
VALUE-CONFIG-CLASSES, added
MULTIPLICITY-CONFIG-CLASSES where necessary.
Changed Files:
cfgdesc/SysTime_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6433
CR Headline:
Schema of paramdefs, paramconfs and SWCDen should be
AUTOSAR_4-3-0_STRICT_COMPACT.xsd
Description of Issues:
Schema of parameter definition files and SWCDs should be
conform to AUTOSAR_4-3-0_STRICT_COMPACT.xsd
Description of Changes:
Adapted parameter definition files and SWCDs to schema
AUTOSAR_4-3-0_STRICT_COMPACT.
Changed Files:
cfgdesc/SysTime_paramdef.arxml
Compatibility:
Revision 5.0.1 [Released]
Item
Description
CR ID:
BAC-6200
CR Headline:
Improve Requirements Traceability
Description of Issues:
Add requirements from IntegrationManual to RequirementsTable.
Description of Changes:
Added requirements from IntegrationManual to
RequirementsTable.
Changed Files:
Compatibility:
Revision 5.0.0 [Released]
Item
Description
CR ID:
CR Headline:
Initial Release for SP2021
Description of Issues:
Initial Release for SP2021
Description of Changes:
Initial Release for SP2021
Changed Files:
Compatibility:
ReleaseNotes_SysTimeGeneric, Version 5.0.3, Software Platforms
Page 3 of 3

Document Outline

14 - SysTimeGeneric_RequirementsTable

15 - SysTimeGeneric_RequirementsTable_ind

Outline
Page 1
Page 2
Page 3
Page 4

16 - SysTimeGeneric_RequirementsTables


SysTime Generic Requirements Table
Project
BMW AUTOSAR Core 4 Rel. 3 and adaptive BMW AUTOSAR Core Rel. 1
Author
BMW AG
Release Date
2017-12-14
Version
5.0.3
Status
Release
Hotline
+49 89 382 - 32233 (classic) / +49 89 382 - 22522 (adaptive)
Contact
bac@bmw.de (classic) / abac@bmw.de (adaptive)
https://asc.bmw.com/jira/browse/BSUP (extern)
https://asc.bmwgroup.net/jira/browse/BSUP (intern)
Revision History
Version
Date
Changed by
Description
5.0.3
2017-12-14
JC-42
Version Update
5.0.2
2017-10-12
JC-42
Version Update
5.0.1
2017-08-10
JC-42
BAC-6200: Add integration requirements.
5.0.0
2017-06-29
JC-42
Initial version for SP2021.
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
SysTimeGeneric_RequirementsTable.pdf, Version 5.0.3, Software Platforms
Page 1 of 4

Table of Contents
1 Related documentation
3
2 Requirements Table
4
SysTimeGeneric_RequirementsTable.pdf, Version 5.0.3, Software Platforms
Page 2 of 4

1
Related documentation
References
[1] LH Diagnosemaster Systembeschreibung
SAP: 10000504-000-13
[2] Diagnose - Systembeschreibung
SAP: 10000784-000-12
SysTimeGeneric_RequirementsTable.pdf, Version 5.0.3, Software Platforms
Page 3 of 4

2
Requirements Table
The Requirements are taken from [1] and [2].
Requirement
Description
Satisfied by
[DK_T3_452]
No description
[DK_T3_453]
No description
[DMA_PA_8451]
No description
[DMA_PA_8460]
No description
[DMA_PA_8471]
No description
[DMA_PA_8550]
No description
[DMA_PA_8551]
No description
[DMA_PA_8552]
No description
[DMA_PA_8471]
No description
[IM_SysTime_0002]
[DMA_PA_9033]
No description
[IM_SysTime_0001]
SysTimeGeneric_RequirementsTable.pdf, Version 5.0.3, Software Platforms
Page 4 of 4

Document Outline