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


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


























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 - BUtilClassic_IntegrationManual

3 - BUtilClassic_IntegrationManual_ind

Outline
Page 1
Page 2
Page 3
Page 4

4 - BUtilClassic_IntegrationManuals


BUtil Classic Integration Manual
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.1.1
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.1.1
2017-12-14
JC-42
Version Update
5.1.0
2017-09-14
JC-42
Version Update
5.0.1
2017-08-10
JC-42
Version Update.
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
BUtilClassic_IntegrationManual, Version 5.1.1, Software Platforms
Page 1 of 4


Table of Contents
1 Introduction
3
1.1
Functional overview
3
2 Related documentation
4
BUtilClassic_IntegrationManual, Version 5.1.1, Software Platforms
Page 2 of 4


1
Introduction
This Integration Manual describes the basis functionality, API and the configuration of the BMW system
function BUtil.
Functional overview
The BUtil library contains some general purpose functions commonly used by other modules like Dlog,
Prog and Bm. It is used in Application, Bootloader and Bootmanager.
BUtilClassic_IntegrationManual, Version 5.1.1, Software Platforms
Page 3 of 4


2
Related documentation
References
BUtilClassic_IntegrationManual, Version 5.1.1, Software Platforms
Page 4 of 4

Document Outline


5 - BUtilClassic_ReleaseNotes

6 - BUtilClassic_ReleaseNotes_ind

Outline
Page 1
Page 2
Page 3

7 - BUtilClassic_ReleaseNotess


Release Notes BUtilClassic
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.1.1
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.1.1
2017-12-14
BAC-6676
5.1.0
2017-09-14
BAC-6290, BAC-6288
5.0.1
2017-08-10
BAC-6174
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_BUtilClassic, Version 5.1.1, Software Platforms
Page 1 of 3


1
Module Description
2
Revisions and Modifications
Revision 5.1.1 [Released]
Item
Description
CR ID:
BAC-6676
CR Headline:
BUtil: Version cross check between generic and adapter part
missing
Description of Issues:
Version check and version cross check between generic and
adapter part is missing.
Description of Changes:
add missing version checks
Changed Files:
include/BUtil_UDSAdapterHelper.h
include/BUtilClassic_Version.h
src/BUtil_UDSAdapterHelper.c
Compatibility:
Revision 5.1.0 [Released]
Item
Description
CR ID:
BAC-6290
CR Headline:
fix compiler warnings
Description of Issues:
fix compiler warnings
Description of Changes:
fix compiler warnings
Changed Files:
src/BUtil_UDSAdapterHelper.c
Compatibility:
Item
Description
CR ID:
BAC-6288
CR Headline:
add UDS prefix to generated ReadData and WriteData functions
Description of Issues:
add UDS prefix to generated ReadData and WriteData functions
Description of Changes:
add UDS prefix to generated ReadData and WriteData functions
Changed Files:
generate/pageinclude/BUtil_UDSAdapterHelper.pgen
Compatibility:
Revision 5.0.1 [Released]
Item
Description
CR ID:
BAC-6174
CR Headline:
#include "Dcm_Types.h" conflicts with Rte*.h
Description of Issues:
#include "Dcm_Types.h" conflicts with Rte*.h
Description of Changes:
include Dcm_Typs.h only in case no Rte header is included
Changed Files:
include/BUtil_UDSAdapterHelper.h
Compatibility:
ReleaseNotes_BUtilClassic, Version 5.1.1, Software Platforms
Page 2 of 3


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_BUtilClassic, Version 5.1.1, Software Platforms
Page 3 of 3

Document Outline


8 - BUtilClassic_UserManual

9 - BUtilClassic_UserManual_ind

Outline
Page 1
Page 2
Page 3
Page 4

10 - BUtilClassic_UserManuals


BUtil Classic User Manual
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.1.1
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.1.1
2017-12-14
JC-42
Version Update
5.1.0
2017-09-14
JC-42
Version Update
5.0.1
2017-08-10
JC-42
Version Update.
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
BUtilClassic_UserManual.pdf, Version 5.1.1, Software Platforms
Page 1 of 4


Table of Contents
1 Overview
3
1.1
Purpose
3
2 Related documentation
4
BUtilClassic_UserManual.pdf, Version 5.1.1, Software Platforms
Page 2 of 4


1
Overview
BUtil is an internal used library within the BMW Platform Software Modules (BAC and aBAC). External
software shall not use the library directly. The interfaces or features may be removed from one to the next
release.
Purpose
The BUtil library contains some general purpose functions commonly used by other modules like Dlog,
Prog and Bm. It is used in Application, Bootloader and Bootmanager.
The Goal of this library is not to provide a general propose solution for external software, but only for the
BMW Platform Sofware (BAC and aBAC). You shall not directly use this library.
BUtilClassic_UserManual.pdf, Version 5.1.1, Software Platforms
Page 3 of 4


2
Related documentation
References
BUtilClassic_UserManual.pdf, Version 5.1.1, Software Platforms
Page 4 of 4

Document Outline


11 - BUtilGeneric_ReleaseNotes

12 - BUtilGeneric_ReleaseNotes_ind

Outline
Page 1
Page 2
Page 3

13 - BUtilGeneric_ReleaseNotess


Release Notes BUtilGeneric
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-6676, BAC-6573
5.0.2
2017-10-12
BAC-6382, BAC-6343
5.0.1
2017-09-14
BAC-6299
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_BUtilGeneric, Version 5.0.3, Software Platforms
Page 1 of 3


1
Module Description
2
Revisions and Modifications
Revision 5.0.3 [Released]
Item
Description
CR ID:
BAC-6676
CR Headline:
BUtil: Version cross check between generic and adapter part
missing
Description of Issues:
Version check and version cross check between generic and
adapter part is missing.
Description of Changes:
add missing version checks
Changed Files:
include/BUtil/TimerTypes.h
include/BUtil/GenericNvMTypes.h
include/BUtil/GenericErrMemTypes.h
include/BUtil_Algorithm.h
include/BUtil/GenericUDSTypes.h
Compatibility:
Item
Description
CR ID:
BAC-6573
CR Headline:
nrc wrongBlockSequenceCounter missing in GenericUDSTypes.h
Description of Issues:
nrc wrongBlockSequenceCounter missing in GenericUDSTypes.h
Description of Changes:
add missing
UDS_DIAG_E_WRONGBLOCKSEQUENCECOUNTER
Changed Files:
include/BUtil/GenericUDSTypes.h
Compatibility:
Revision 5.0.2 [Released]
Item
Description
CR ID:
BAC-6382
CR Headline:
Fix file headers
Description of Issues:
fix file headers
Description of Changes:
fix file headers
Changed Files:
include/BUtil_Assert.h
include/BUtil_Version.h
include/BUtil_BitArray.h
Compatibility:
Item
Description
CR ID:
BAC-6343
CR Headline:
Add missing Get64Bit Macros
Description of Issues:
Add missing Get64Bit Macros (follow-up to BAC-6299)
ReleaseNotes_BUtilGeneric, Version 5.0.3, Software Platforms
Page 2 of 3


Description of Changes:
add 64 bit put and get macros
Changed Files:
include/BUtil_ByteMask.h
Compatibility:
Revision 5.0.1 [Released]
Item
Description
CR ID:
BAC-6299
CR Headline:
Add missing macros for 64 bit support
Description of Issues:
64 bit support is missing.
Description of Changes:
Add 64 bit macros.
Changed Files:
include/BUtil_ByteMask.h
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_BUtilGeneric, Version 5.0.3, Software Platforms
Page 3 of 3

Document Outline