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

Return to the regular view of this page.

DlogShared

DlogShared

Component Documentation

1 - DlogShared 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 DlogShared
Revision / Baseline:


Windows User: Intended Use: Identify the implementation baseline name intended to be used for the changed component when changes are approved. DlogShared_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#21728


























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 packageN/A
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 packageN/A
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 settingsN/A
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 contentsN/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







































































2 - DlogSharedGeneric_ReleaseNotes

3 - DlogSharedGeneric_ReleaseNotes_ind

Outline
Page 1
Page 2
Page 3
Page 4

4 - DlogSharedGeneric_ReleaseNotess


Release Notes DlogSharedGeneric
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-6711, BAC-6728, BAC-6702
5.0.2
2017-11-09
BAC-6368, BAC-6362, BAC-6422
5.0.1
2017-09-14
BAC-6223, BAC-5169
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_DlogSharedGeneric, Version 5.0.3, Software Platforms
Page 1 of 4

1
Module Description
Part of the configuration of the Dlog module that is shared between Bootloader, Bootmanager and
Application.
2
Revisions and Modifications
Revision 5.0.3 [Released]
Item
Description
CR ID:
BAC-6711
CR Headline:
missing MIN-MAX limits for parameter definitions
Description of Issues:
Many integer parameters used for sizes and address values in Blu
and DlogShared do not have a MIN-MAX limit specified
Description of Changes:
add missing min and max values in DlogShared_paramdef.arxml
Changed Files:
cfgdesc/DlogShared_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6728
CR Headline:
Fix limits of Flash Timing Parameters
Description of Issues:
Fix limits of Flash Timing Parameters
Description of Changes:
Fix limits of Flash Timing Parameters
Changed Files:
cfgdesc/DlogShared_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6702
CR Headline:
Dlog: SVK Backup MAX Limit wrong in autosar def file?
Description of Issues:
According to BMW 61 places alltogether are supposed to be kept
clear for the logistics of SVK Backups. In the AutoSAR definition of
Dlog_Shared (DlogShared_paramdef.arxml) a maximum of 31
places is stated.
Description of Changes:
increase max number of SVK backup from 31 to 61
Changed Files:
cfgdesc/DlogShared_paramdef.arxml
Compatibility:
Revision 5.0.2 [Released]
Item
Description
CR ID:
BAC-6368
CR Headline:
Remove obsolete configs for AuthCounter and MirrorSwe
Description of Issues:
Remove obsolete configs for AuthCounter and MirrorSwe
Description of Changes:
Remove obsolete configs for AuthCounter and MirrorSwe
ReleaseNotes_DlogSharedGeneric, Version 5.0.3, Software Platforms
Page 2 of 4

Changed Files:
cfgdesc/DlogShared_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6362
CR Headline:
Adapt to new postbuild variant handling
Description of Issues:
adapt to new postbuild variant handling
Description of Changes:
adapt to new postbuild variant handling
Changed Files:
cfgdesc/DlogShared_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6422
CR Headline:
Bs, Dlog, Pia: Schema of paramdefs, paramconfs and SWCDen
should be AUTOSAR_4-3-0_STRICT_COMPACT.xsd
Description of Issues:
Schema of paramdefs, paramconfs and SWCDen should be
AUTOSAR_4-3-0_STRICT_COMPACT.xsd
Description of Changes:
change arxml schema to
AUTOSAR_4-3-0_STRICT_COMPACT.xsd
Changed Files:
cfgdesc/DlogShared_paramdef.arxml
Compatibility:
Revision 5.0.1 [Released]
Item
Description
CR ID:
BAC-6223
CR Headline:
Usage of IMPLEMENTATION-CONFIG-CLASSES is deprecated
and shall be replaced by VALUE-CONFIG-CLASSES according to
ASR4.2.2
Description of Issues:
TPS_ECUC_06051 is removed from spec. In schema
AUTOSAR_4-2-2.xsd IMPLEMENTATION-CONFIG-CLASSES is
marked as deprecated. That means: IMPLEMENTATION-
CONFIG-CLASSES/IMPLEMENTATION-CONFIG-CLASS has to
be replaed by
VALUE-CONFIG-CLASSES/VALUE-CONFIG-CLASS entirely
within paramdefs!
Description of Changes:
fix config classes in paramdef.arxml file
Changed Files:
cfgdesc/DlogShared_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-5169
CR Headline:
Some (most?) BAC modules paramdef violate TPS_ECUC_06004
ReleaseNotes_DlogSharedGeneric, Version 5.0.3, Software Platforms
Page 3 of 4

Description of Issues:
According to AUTOSAR TPS_ECUConfiguration there is the
following requirement:
[TPS_ECUC_06004] AdminData field in ECU Configuration
Parameter Definition XML file d An AdminData field is required at
the beginning of every ECU Configuration Parameter Definition
XML file (regardless whether it is the StMD or the VSMD file) to
allow the setting of AdminData for the whole XML File. c()
Most of our modules fail to define the AdminData Element (just
saw it in Darh - and here the element contains mixed info to be
fixed). It is somehow weired as we then will define version info
within CommonPublishedInformation AND AdminData - but as it is
formally required, we have to follow it.
Description of Changes:
add AdminData to paramdef file
Changed Files:
cfgdesc/DlogShared_paramdef.arxml
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_DlogSharedGeneric, Version 5.0.3, Software Platforms
Page 4 of 4

Document Outline