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

Return to the regular view of this page.

Coding

Coding

Component Documentation

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


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


























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)Yes
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 - CodingClassic_IntegrationManual

3 - CodingClassic_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
Page 12
Page 13
Page 14
Page 15
Page 16
Page 17
Page 18
Page 19
Page 20
Page 21
Page 22
Page 23

4 - CodingClassic_IntegrationManuals


Coding Classic Integration Manual
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.2.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
Description
5.2.1
2017-12-14
Version Update
5.2.0
2017-11-09
Version Update
5.1.0
2017-10-12
Version Update
5.0.1
2017-09-14
Version Update
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
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 1 of 23

Table of Contents
1 Introduction
4
1.1
General
4
1.2
Functional overview
4
2 Related documentation
5
3 Limitations
6
4 Software Architecture
7
4.1
Dependencies on AUTOSAR modules
7
4.1.1
NvM
7
4.1.2
Dem
7
4.1.3
Dcm
7
4.1.4
Com
7
4.1.5
Det
7
4.1.6
RTE
7
4.1.7
BswM
7
4.2
Dependencies to other modules
8
4.2.1
Dlog
8
4.2.2
Vin
8
4.2.3
Other SWC
8
5 Integration
9
5.1
Configuration of other Modules
9
5.1.1
NvM
9
5.1.2
Dem
9
5.1.3
Dcm
10
5.1.3.1
DiagnosticSession
10
5.1.3.2
DiagnosticSessionControl
10
5.1.3.3
RoutineControl
11
5.1.3.4
ReadDataByIdentifier
12
5.1.3.5
DiagnosticSessionControl
14
5.1.3.6
Service Request Manufacturer Notification
15
5.1.4
Com
15
5.1.5
Det
15
5.1.6
BswM
15
5.2
Configuration of generic part
16
5.2.1
CodingCrypto
16
5.2.1.1
CryptoLib
16
5.2.1.2
Csm
16
5.2.2
CodingGeneral
16
5.2.2.1
CodingDevErrorDetect
16
5.2.2.2
CodingSignatureSize
17
5.2.2.3
CodingCryptoEnable
17
5.2.2.4
CodingProdErrorCEUDDetection
17
5.2.2.5
CodingConditionCheck
17
5.2.2.6
CodingReceiveBufferSize
17
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 2 of 23

5.2.2.7
CodingSendBufferSize
18
5.2.3
CodingArea
18
5.2.3.1
CodingAreaDefVal
18
5.3
Configuration of adapter part
20
5.3.1
CodingClassicGeneral
20
5.3.1.1
CodingCycleTime
20
5.3.1.2
Other Application SWC
20
5.3.2
Event Mapping
21
5.3.3
Data Mapping
21
5.3.4
Exclusive Areas
21
5.4
Software Integration
22
5.4.1
Startup/Initialization
22
5.4.2
Normal Operation
22
5.4.3
Shutdown/Deactivation
22
5.4.4
SWCD
22
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 3 of 23

1
Introduction
The Coding system consists of a Coding module that is part of the ECU application and the Coder.
Almost in the same manner as the Bootloader programs the ROM of an ECU, the Coding module codes
the NV memory of an ECU with vehicle specific data derived from the vehicle description document e.g.
type key, extra equipment, country specifics, year of model/construction stage, additional comments or
service upgrade options.
General
For a general introduction to the BAC4/aBAC Modules please refer to [1].
This document only describes topics related to the Coding BAC4/aBAC Module.
This Integration Manual describes the basis functionality, API and the configuration of the BMW system
function Coding.
Functional overview
The Coding module implements the coding process that is part of the vehicle programming process. It
provides functions to the application to read coded data stored in the NV memory. If the NV memory
contains no valid data default values are provided. The coded data in NV memory can only be changed via
a diagnostic coding session.
The Coding module provides the following functionalities:
Manages coding data stored in NV memory
Provides read/write access via a special UDS diagnostics Session to the Coder
Provides read only access via API to the ECU application
Informs the ECU application about its current status
Performs signature checks over the Coding data
Restores safe default values in case of errors
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 4 of 23

2
Related documentation
References
[1] BAC4 General Concept for the Module Integration
BAC4_General_Concepts_for_the_Module_Integration.pdf
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 5 of 23

3
Limitations
The Coding module supports only one asymmetric key to calculate the signature for all Coding areas.
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 6 of 23

4
Software Architecture
Dependencies on AUTOSAR modules
The current version of the Module Coding depends on the following BSW modules:
NvM
The Coding module uses the NVM to read Coding data from NV memory and to write it back.
Dem
The Coding module uses the DEM API to report critical events and write error memory entries.
Dcm
The Coding module uses the DCM to communicate with the Coder by sending and receiving diagnostic
UDS messages via CAN, FlexRay, etc.
Com
The Coding module use signals from COM to get the Vehicle Speed.
Det
The Coding module optionally reports development errors to the Det.
RTE
As a software component, the Coding module uses Rte client/server and sender/receiver communication
to communicate with other SWCs and BSW modules.
BswM
The Coding receives and requests mode switches from the BswM to switch the current Coding
operational mode. It further receives a mode switch from the BswM when the active diagnostic session
has changed and when the bus communication status has changed.
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 7 of 23

Dependencies to other modules
Dlog
The Dlog module is used to obtain the information during startup if the control unit has been coded after
flash programming.
Vin
The Vin module is used to obtain the current bus VIN.
Other SWC
The Coding optionally calls another Application Software Component to perform a plausibility check of
the net coding data received during the coding data transaction if implausible net coding data can lead to
safety-critical states of the control unit.
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 8 of 23

5
Integration
Configuration of other Modules
The following modules shall be configured, before this module can be generated, compiled and linked.
NvM
The NVRAM Manager shall be configured to hold one NVRAM block. The following parameters have to
be configured:
a container "`NvMBlockDescriptor"' with
NvmNvBlockLength: "`see CODING_DATA_SIZE in generated Coding_Cfg.h"'
NvmBlockCRCType: e.g. NVM_CRC16
NvMBlockUseCrc: true
NvMCalcRamBlockCrc: false
NvmBlockManagementType: NVM_BLOCK_NATIVE
NvmRamBlockDataAddress: &Coding_CodingData
NvmRomBlockDataAddress: &Coding_CodingDataDefault
NvmSelectBlockForReadAll: true
NvmSelectBlockForWriteAll: false
This NVRAM block needs
Port and Port Interface for service ports
Port and Port Interface for single block job end notifications
This NVRAM block will be used to store Coding data and will be written on Coding process.
Dem
The Coding module reports different errors to the DEM. The DEM shall be configured to provide the
following Errors (aging/healing is disabled for all DTCs):
CODING_EVENT_NOT_CODED
Description: No valid Coding data is available and default values are used.
Annotation: A Clear Event Allowed port shall be configured via Rte
DTC Class
∗ DemUdsDtc: 0x20000 + 0x100 * ECU_Address + 0x08
∗ DemDTCSeverity: DEM_DTC_SEV_NO_SEVERITY
Event
∗ DemEventKind: DEM_EVENT_KIND_SWC
∗ DemEventDestination: DEM_DTC_ORIGIN_PRIMARY_MEMORY
CODING_EVENT_WRONG_VEHICLE
Description: CPS and VIN do not match.
DTC Class
∗ DemUdsDtc: 0x20000 + 0x100 * ECU_Address + 0x09
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 9 of 23

∗ DemDTCSeverity: DEM_DTC_SEV_NO_SEVERITY
Event
∗ DemEventKind: DEM_EVENT_KIND_SWC
∗ DemEventDestination: DEM_DTC_ORIGIN_PRIMARY_MEMORY
CODING_EVENT_UNQUALIFIED_DATA
Description: CPS-VIN comparison has not been done.
Annotation: Error entry depends on configuration parameter "`CodingProdErrorCEUDDetection"'
DTC Class
∗ DemUdsDtc: 0x20000 + 0x100 * ECU_Address + 0x0A
∗ DemDTCSeverity: DEM_DTC_SEV_NO_SEVERITY
Event
∗ DemEventKind: DEM_EVENT_KIND_SWC
∗ DemEventDestination: DEM_DTC_ORIGIN_PRIMARY_MEMORY
Dcm
DiagnosticSession
The writing of net coding data into a control unit must only be possible, if the control unit is in the
CodingSession.
The following parameters have to be configured:
a container "`DcmDspSessionRow"' with
DcmDspSessionForBoot: DCM_NO_BOOT
DcmDspSessionLevel: 65 (0x41)
DcmDspSessionP2ServerMax: [IM_CodingClassic_001] dc(DK_T3_266)
DcmDspSessionP2StarServerMax: 5.0
DiagnosticSessionControl
[IM_CodingClassic_002] dThe Diagnostic Session Control service is used for changing codable control
units into the Extended Diagnostic Session, the Coding Session and the Default Session. c(COD_268)
[IM_CodingClassic_003] dThe following parameters have to be configured: c(COD_269, COD_272,
COD_276, COD_280)
a container "`DcmDsdService"' with
DcmDsdSidTabServiceId: 0x10
∗ a container "`DcmDsdSubService"' with
· DcmDsdSubServiceId: 0x01
· DcmDsdSubServiceSessionLevelRef: DEFAULT_SESSION
· DcmDsdSubServiceSessionLevelRef: EXTENDED_SESSION
· DcmDsdSubServiceSessionLevelRef: CODING_SESSION
· DcmDsdSubServiceId: 0x03
· DcmDsdSubServiceSessionLevelRef: DEFAULT_SESSION
· DcmDsdSubServiceSessionLevelRef: EXTENDED_SESSION
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 10 of 23

· DcmDsdSubServiceId: 0x41
· DcmDsdSubServiceSessionLevelRef: EXTENDED_SESSION
· DcmDsdSubServiceSessionLevelRef: CODING_SESSION
RoutineControl
[IM_CodingClassic_004] dThe Routine Control service is used for reading, writing and verifying net
coding data. c(COD_289)
Reading of net coding data from control unit (0x31 0x01 0x37 0xFC)
[IM_CodingClassic_005] dThis request has a variable response length. The following parameters have
to be configured: c(COD_292, COD_294)
a container "`DcmDspRoutine"' with
DcmDspRoutineIdentifier: 0x37FC
DcmDspRoutineUsePort: TRUE
a container "`DcmDspRoutineInfo"' and "`DcmDspStartRoutineIn"' with
a "`StartRoutineInSignal"' with
∗ DcmDspRoutineSignalLength: 48 bits
∗ DcmDspRoutineSignalPos: 0
∗ DcmDspRoutineSignalType: UINT8
a "`StartRoutineOutSignal"' with
∗ DcmDspRoutineSignalLength: max. diagnostic buffer size (e.g. 8192 bits)
∗ DcmDspRoutineSignalPos: 0
∗ DcmDspRoutineSignalType: VARIABLE_LENGTH
Writing of net coding data from control unit (0x31 0x01 0x37 0xFD)
[IM_CodingClassic_006] dThis request has a variable request length. The following parameters have
to be configured: c(COD_297, COD_299)
a container "`DcmDspRoutine"' with
DcmDspRoutineIdentifier: 0x37FD
DcmDspRoutineUsePort: TRUE
a container "`DcmDspRoutineInfo"' and "`DcmDspStartRoutineIn"' with
a "`StartRoutineInSignal"' with
∗ DcmDspRoutineSignalLength: max. diagnostic buffer size (e.g. 8192 bits)
∗ DcmDspRoutineSignalPos: 0
∗ DcmDspRoutineSignalType: VARIABLE_LENGTH
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 11 of 23

Verification of net coding data from control unit (0x31 0x01 0x37 0xFE)
[IM_CodingClassic_007] dThe following parameters have to be configured: c(COD_302, COD_304)
a container "`DcmDspRoutine"' with
DcmDspRoutineIdentifier: 0x37FE
DcmDspRoutineUsePort: TRUE
a container "`DcmDspRoutineInfo"' and "`DcmDspStartRoutineIn"' with
a "`StartRoutineInSignal"' with
∗ DcmDspRoutineSignalLength: 144 bits
∗ DcmDspRoutineSignalPos: 0
∗ DcmDspRoutineSignalType: UINT8
a "`StartRoutineOutSignal"' with
∗ DcmDspRoutineSignalLength: 8 bits
∗ DcmDspRoutineSignalPos: 0
∗ DcmDspRoutineSignalType: UINT8
ReadDataByIdentifier
[IM_CodingClassic_008] dThe Read Data By Identifier service is used in conjunction with coding for
the following request to the control unit:
Determining the value of the coding proof stamp (CPS)
Determining the current session status (reading ActiveSessionState)
Determining the current session
Determining the protocol data (transport buffer sizes, coding area count and lengths)
c(COD_289)
Read coding proof stamp (CPS) (0x22 0x37 0xFE)
Reading out the coding proof stamp (CPS) from the control unit.
[IM_CodingClassic_009] dThe following parameters have to be configured: c(COD_314, COD_316)
a container "`DcmDspDataInfo"' with
DcmDspDataFixedLength: TRUE
a container "`DcmDspData"' with
DcmDspDataConditionCheckReadFncUsed: TRUE
DcmDspDataInfoRef: reference to the "`DcmDspDataInfo"' container configured before.
DcmDspDataSize: 144 bits
DcmDspDataType: UINT8_N
DcmDspDataUsePort: USE_DATA_SYNCH_CLIENT_SERVER
a container "`DcmDspDidInfo"' with
only read-access
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 12 of 23

DcmDspDidReadSessionRef: CODING_SESSION, EXTENDED_SESSION, DEFAULT_SESSION
a container "`DcmDspDid"' with
DcmDspDidIdentifier: 0x37FE
one DID Signal "`DcmDspDidSignal"' with Data Position = 0 and a Data Reference to the
"`DcmDspData"' container configured before.
Read status of the active Session (0x22 0xF1 0x00)
Reading out the status of the ActiveSessionState from the control unit.
[IM_CodingClassic_010] dThe following parameters have to be configured: c(COD_319, COD_321)
a container "`DcmDspDataInfo"' with
DcmDspDataFixedLength: TRUE
a container "`DcmDspData"' with
DcmDspDataConditionCheckReadFncUsed: TRUE
DcmDspDataInfoRef: reference to the "`DcmDspDataInfo"' container configured before.
DcmDspDataSize: 32 bits
DcmDspDataType: UINT8_N
DcmDspDataUsePort: USE_DATA_SYNCH_CLIENT_SERVER
a container "`DcmDspDidInfo"' with
only read-access
DcmDspDidReadSessionRef: CODING_SESSION, EXTENDED_SESSION, DEFAULT_SESSION
a container "`DcmDspDid"' with
DcmDspDidIdentifier: 0xF100
one DID Signal "`DcmDspDidSignal"' with Data Position = 0 and a Data Reference to the
"`DcmDspData"' container configured before.
Read active session (0x22 0xF1 0x86)
Reading out of the ActiveSession from the control unit.
[IM_CodingClassic_011] dThe following parameters have to be configured: c(COD_324, COD_326)
a container "`DcmDspDataInfo"' with
DcmDspDataFixedLength: TRUE
a container "`DcmDspData"' with
DcmDspDataConditionCheckReadFncUsed: TRUE
DcmDspDataInfoRef: reference to the "`DcmDspDataInfo"' container configured before.
DcmDspDataSize: 8 bits
DcmDspDataType: UINT8_N
DcmDspDataUsePort: USE_DATA_SYNCH_FNC
a container "`DcmDspDidInfo"' with
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 13 of 23

only read-access
DcmDspDidReadSessionRef: CODING_SESSION, EXTENDED_SESSION, DEFAULT_SESSION
a container "`DcmDspDid"' with
DcmDspDidIdentifier: 0xF186
one DID Signal "`DcmDspDidSignal"' with Data Position = 0 and a Data Reference to the
"`DcmDspData"' container configured before.
Read protocol data (0x22 0x37 0xFF)
Reading of the protocol data from the control unit.
[IM_CodingClassic_012] dThe following parameters have to be configured: c(COD_329, COD_331)
a container "`DcmDspDataInfo"' with
DcmDspDataFixedLength: TRUE
a container "`DcmDspData"' with
DcmDspDataConditionCheckReadFncUsed: TRUE
DcmDspDataInfoRef: reference to the "`DcmDspDataInfo"' container configured before.
DcmDspDataSize: 72 bits
DcmDspDataType: UINT8_N
DcmDspDataUsePort: USE_DATA_SYNCH_CLIENT_SERVER
a container "`DcmDspDidInfo"' with
only read-access
DcmDspDidReadSessionRef: CODING_SESSION, EXTENDED_SESSION, DEFAULT_SESSION
a container "`DcmDspDid"' with
DcmDspDidIdentifier: 0x37FF
one DID Signal "`DcmDspDidSignal"' with Data Position = 0 and a Data Reference to the
"`DcmDspData"' container configured before.
DiagnosticSessionControl
[IM_CodingClassic_013] dThe ECUReset service is used in order to prompt a control unit to exit the
CodingSession following successfully completed coding. c(COD_338)
[IM_CodingClassic_014] dThe following parameters have to be configured: c(COD_341, COD_343)
a container "`DcmDsdService"' with
DcmDsdSidTabServiceId: 0x11
∗ a container "`DcmDsdSubService"' with
· DcmDsdSubServiceId: 0x01
· DcmDsdSubServiceSessionLevelRef: DEFAULT_SESSION
· DcmDsdSubServiceSessionLevelRef: EXTENDED_SESSION
· DcmDsdSubServiceSessionLevelRef: CODING_SESSION
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 14 of 23

Service Request Manufacturer Notification
A Coding Service Request Manufacturer Notification shall be configured in the container
"DcmDslServiceRequestManufacturerNotification". The Mapping to the Coding module is done by
connecting the corresponding ports.
Com
The communication stack has to be configured for the reception and sending of bus messages. The
following PDUs/Signals are expected to be present in the Com stack after import of the BMW BNE export
(CodingSample):
Speed Signal (Rx) - CAN
Shortname: V_VEH
Length: 5 Bytes
Signal: V_VEH_COG
Signal Size: 16 Bits
Startbit Position: 16
Speed Signal (Rx) - Ethernet
Service Interface ID: 0x7533
Service: SpeedAcceleration
Ereignis/Field: VehicleSpeedAndDrivingCondition
Parameter/Strukturelement: speedVehicleCentreOfGravity
Important Note: For integration of the CodingSample module in an ECU, which is connected to Ethernet
as "`System Bus"' there is an adaption to make (S/R-interface and code). A new implementation data type
has to be created e.g. "`CodingSample_VehicleSpeedAndDrivingRecordType"' and the existing
S/R-interface "`Coding_VehicleSpeedInterface"' must refer this new data implementation type.
Furthermore the provided function "`CodingSample_VehicleSpeedReceiveHandler()"' must be modified
to access the desired parameter of the new structure.
Det
The DET shall be configured to provide development Errors. These errors are application programmer
specific.
BswM
The BswM has to provide:
BswMModeRequestPort "`LifeCycle"' to receive mode switch notifications of the
ModeDeclarationGroup "`Coding_LifeCycle"' from Coding
BswMRteModeRequestPort "`LifeCycleRequest"' to request modes of the ModeDeclarationGroup
"`Coding_LifeCycle"'
BswMRules to request the Coding life cycle mode
BswMRules to switch the Coding BusCom-Mode
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 15 of 23

BswMRules to switch the Coding Session-Mode
Configuration of generic part
CodingCrypto
This container contains the configuration (parameters) of the crypto part of the Coding module.
CryptoLib
Choose this container to use the BMW crypto library for crypto operations.
Csm
Choose this container to use the AUTOSAR Csm for crypto operations.
CodingHashSize
This parameter defines the size of the hash depending on the Hash Method.
The Coding module supports the following hash algorithm
SHA-256 - length 32 bytes
SHA-384 - length 43 bytes
SHA-512 - length 64 bytes
CodingGeneral
This container contains the configuration parameters of the generic part of the Coding module.
CodingDevErrorDetect
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.
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 16 of 23

CodingSignatureSize
[IM_Coding_001] dThis parameter defines the size of the net Coding Data Signature depending on the
Signature Method. c(COD_147, COD_148)
The Coding module supports the following asymmetric keys
RSA key length 2048 bit
RSA key length 3072 bit
RSA key length 4096 bit
ECC key length 256 bit
ECC key length 384 bit
ECC key length 521 bit
CodingCryptoEnable
This parameter activates/deactivates the Service to check net Coding Data Signature.
If set to true: Service to check net Coding Data Signature is activated.
If set to false: Service to check net Coding Data Signature is deactivated.
CodingProdErrorCEUDDetection
[IM_Coding_002] dThis parameter activates/deactivates the Production Error "`Coding Event
Unqualified Data"' (CEUD) Detection and Reporting. c(COD_114, COD_138)
If set to true: Production Error CEUD Detection and Report is activated.
If set to false: Production Error CEUD Detection and Report is deactivated.
CodingConditionCheck
[IM_Coding_003] dThis parameter activates/deactivates the Coding Ability due to Operating Conditions
Detection e.g. car is being driven or engine is running. c(COD_060)
If set to true: Operating Conditions Detection is activated.
If set to false: Operating Conditions Detection is deactivated.
CodingReceiveBufferSize
[IM_Coding_004] dThis parameter defines the size of the Coding Receive Buffer (Rx) of Control Unit in
Bytes. c(COD_171)
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 17 of 23

CodingSendBufferSize
[IM_Coding_005] dThis parameter defines the size of the Coding Send Buffer (Tx) of Control Unit in
Bytes. c(COD_171)
CodingArea
[IM_Coding_006] dThis container contains the default value for unused bits and all user configurable
functions of this Coding area. c(COD_097)
CodingAreaDefVal
This parameter defines the Default Value for Unused Bits in the Coding Area.
The Coding module supports the following default values
AllBitsZero (0x00)
AllBitsOne (0xFF)
CodingFunction
This container contains one or more Coding Functions.
CodingFunctionStartByte
This parameter contains the Startbyte of the Coding Function Value within the User Configurable Data.
CodingFunctionEndByte
This parameter contains the Endbyte of the Coding Function Value within the User Configurable Data.
CodingFunctionMask
This parameter contains the Mask of the Coding Function Value within the User Configurable Data.
CodingFunctionApplType
This parameter defines the Function Type of the Coding Function Value towards the Application.
The Coding module supports the following types
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 18 of 23

boolean
bytearray
uint8
uint16
uint32
uint64
sint8
sint16
sint32
sint64
float32
float64
CodingFunctionDataCheck
[IM_Coding_007] dThis parameter activates/deactivates the Coding Function Value Check. Control
Units must perform a Plausibility Check of the Net Coding Data received during the Coding Data
Transaction if implausible Net Coding Data can lead to safety-critical states of the Control Unit.
c(COD_227)
If set to true: Coding Function Value Check is activated.
If set to false: Coding Function Value Check is deactivated.
CodingFunctionTransformationRule
This parameter defines the Transformation Rule for the Coding Function Value from Non Volatile Memory
to the User Interface (Application). This Rule shall be configured as a Simple C Operation e.g. "`+10"' or
"`*2"'.
CodingFunctionLowerLimit
This parameter defines the Lower Limit for the Coding Function Value passed to the User Interface
(Application).
CodingFunctionUpperLimit
This parameter defines the Upper Limit for the Coding Function Value passed to the User Interface
(Application).
CodingFunctionNvramType
This container defines the Function Type of the Coding Function Value in Non Volatile Memory.
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 19 of 23

The Coding module supports the following types
boolean
bytearray
uint8
uint16
uint32
uint64
sint8
sint16
sint32
sint64
float32
float64
Choose the desired container to defines the Function Type of the Coding Function Value in Non Volatile
Memory
CodingFunctionDefaultValue
This parameter contains the Default Value of the Coding Function within the User Configurable Data.
Configuration of adapter part
CodingClassicGeneral
This container contains the configuration parameters of the classic adapter of the Coding module.
CodingCycleTime
This parameter defines the Call Cycle of the Coding Timer Function in Seconds.
Other Application SWC
Application Connectors
CheckCodingFunction_<x>: Shall be connected with its corresponding CodingSample ports.
ConditionMode: Shall be connected with its corresponding CodingSample port.
Data: Shall be connected with its corresponding CodingSample and CodingTestClient port.
DataMode: Shall be connected with its corresponding CodingSample and CodingTestClient port.
LifeCycle: Shall be connected with its corresponding BswM and CodingTestClient port.
ProgId: Shall be connected with its corresponding Dlog port.
SVK: Shall be connected with its corresponding Dlog port.
Vin: Shall be connected with its corresponding Vin port.
Service Connectors
BusCom: Shall be connected with its corresponding BswM port.
CBClrEvt_EventNotCoded: Shall be connected with its corresponding Dem port.
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 20 of 23

CheckNCD: Shall be connected with its corresponding Dcm port.
DETService: Shall be connected with its corresponding Det port.
EventNotCoded: Shall be connected with its corresponding Dem port.
EventUnqualifiedData: Shall be connected with its corresponding Dem port.
EventWrongVehicle: Shall be connected with its corresponding Dem port.
LifeCycleRequest: Shall be connected with its corresponding BswM and CodingTestClient port.
Notification: Shall be connected with its corresponding Dcm port.
NvMNotifyJobFinished: Shall be connected with its corresponding NvM port.
NvMService: Shall be connected with its corresponding NvM port.
ReadCPS: Shall be connected with its corresponding Dcm port.
ReadNCD: Shall be connected with its corresponding Dcm port.
ReadProtocolData: Shall be connected with its corresponding Dcm port.
SessionChangeIndication: Shall be connected with its corresponding BswM port.
WriteNCD: Shall be connected with its corresponding Dcm port.
Event Mapping
Coding_DemClearEventAllowedNotCoded: Operation Invoked Event
Coding_TimerMain: Timing Event
DCMConfirmation: Operation Invoked Event
DCMIndication: Operation Invoked Event
GetCafIds: Operation Invoked Event
LifeCycleHandler: Data Receive Event
R_CheckNCD: Operation Invoked Event
R_ConditionCheckReadCPS: Operation Invoked Event
R_ConditionCheckReadProtocolData: Operation Invoked Event
R_GetCodingFunction_<x>: Operation Invoked Event
R_ReadCPS: Operation Invoked Event
R_ReadNCD: Operation Invoked Event
R_ReadProtocolData: Operation Invoked Event
R_WriteNCD: Operation Invoked Event
SessionChange: Mode Switch Event
VinReceiveHandler: Data Receive Event
WriteDataBlockNotification: Operation Invoked Event
Data Mapping
No Data Mapping necessary for the Coding module.
Exclusive Areas
The exlusive areas CodingData and CodingState shall be configured.
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 21 of 23

Software Integration
Startup/Initialization
Before the Coding operation mode CODING_INITIALIZED is requested, the following preconditions shall
be satisfied:
The Coding module is in STOPPED-Mode
The NVRAM Manager is initialized
The NVRAM Manager has finished the job Nvm_ReadAll(). This implies that the NV block containing
the Coding data has also been loaded. If the block is corrupted, the NVRAM Manager automatically
loads the default ROM block containing the default values.
The Dlog is in RUNNING-Mode
The integrator has to assure, that the Coding operation mode CODING_INITIALIZED is requested, after
NvM_ReadAll() is finished and Dlog module switched to RUNNING-Mode.
Normal Operation
Before the Coding operation mode CODING_RUNNING is requested, the following preconditions shall be
satisfied:
The Coding module is in INITIALIZED-Mode
The Coding_TimerMain() will be scheduled cyclically via RTE (a good value for this is a 100ms cycle ).
After the Coding BusCom-Mode is set to CODING_BUSCOMON the Coding_TimerMain() may request
the Vin module to get the onboard electrical system VIN to validate net Coding data if no VIN has been
received until now. This qualification process is repeated 3 times at 1000 ms intervals, if a VIN has still not
been received from the onboard electrical system. After this, qualification of the net coding data is not
performed in this wake cycle, even if an onboard electrical system VIN is received at a later point.
Shutdown/Deactivation
Before the Coding operation mode CODING_STOPPED is requested, the following preconditions shall
be satisfied:
The Coding module is either in INITIALIZED- or RUNNING-Mode
Shutdown/Deactivation is requested
The integrator has to assure, that the Coding operation mode CODING_STOPPED is requested, after a
shutdown/deactivation request was received.
SWCD
The Coding module provides the following Mode:
ModeDeclarationGroup Coding_ConditionMode
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 22 of 23

{
{
CODING_ALLOWED
CODING_NOT_ALLLOWED
}
initialMode = CODING_ALLOWED
}
This mode is used to enable or disable the start of a Coding process. An implementation how to change
this Mode is done in CodingSample_VehicleSpeedReceiveHandler(). The user can add additional rules.
The Coding module provides the following Mode:
ModeDeclarationGroup Coding_BusComMode
{
{
CODING_BUSCOMOFF,
CODING_BUSCOMON
}
initialMode = CODING_BUSCOMOFF
}
The integrator has to assure, that this Mode is set to CODING_BUSCOMON, after the bus
communication has started. The Coding module requests the VIN from the Vin module after this Mode is
set to CODING_BUSCOMON.
No special callback functions have to be introduced by the application programmer for using the Coding
module. The following application callback functions are already implemented in CodingSample.c and can
be adapted by the application programmer:
CodingSample_VehicleSpeedReceiveHandler()
CodingSample_CheckCodingFunction_<x>()
CodingClassic_IntegrationManual, Version 5.2.1, Software Platforms
Page 23 of 23

Document Outline

5 - CodingClassic_ReleaseNotes

6 - CodingClassic_ReleaseNotes_ind

Outline
Page 1
Page 2
Page 3
Page 4
Page 5

7 - CodingClassic_ReleaseNotess


Release Notes CodingClassic
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.2.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.2.1
2017-12-14
BAC-6660, BAC-6704, BAC-6561, BAC-6585
5.2.0
2017-11-09
BAC-6434, BAC-6350
5.1.0
2017-10-12
BAC-6402
5.0.1
2017-09-14
BAC-6250, BAC-6239, BAC-6224, BAC-5170
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_CodingClassic, Version 5.2.1, Software Platforms
Page 1 of 5

1
Module Description
The Coding system consists of a Coding module that is part of the ECU application and the Coder.
Almost in the same manner as the Bootloader programs the ROM of an ECU, the Coding module codes
the NV memory of an ECU with vehicle specific data derived from the vehicle description document e.g.
type key, extra equipment, country specifics, year of model/construction stage, additional comments or
service upgrade options.
2
Revisions and Modifications
Revision 5.2.1 [Released]
Item
Description
CR ID:
BAC-6660
CR Headline:
Correct Misra- and Metric-violations
Description of Issues:
Correct Misra- and Metric-violations and compiler warnings.
Description of Changes:
Correct Misra- and Metric-violations and compiler warnings.
Changed Files:
src/Coding_UDSAdapter.c
src/Coding_TimerAdapter.c
generate/include/CodingClassic_Cfg.h.pgen
template/include/Coding_MemMap.h.sample
generate/meta/Coding_internal.arxml.pgen
include/Coding_Assert.h
generate/meta/Coding_ext_interfaces.arxml.pgen
src/Coding_ErrMemAdapter.c
src/Coding_CryptoAdapter.c
doc/CodingClassic_RequirementsTable.pdf
generate/include/CodingClassic_Version.h.pgen
doc/CodingClassic_IntegrationManual.pdf
generate/meta/Coding_interfaces.arxml.pgen
doc/CodingClassic_UserManual.pdf
Compatibility:
Item
Description
CR ID:
BAC-6704
CR Headline:
Activation of signature verification (RSA)
Description of Issues:
Changed Coding adapter to fit to the provided Crypto-Lib (RSA).
Description of Changes:
Changed Coding adapter to fit to the provided Crypto-Lib (RSA).
Changed Files:
src/Coding_CryptoAdapter.c
Compatibility:
Item
Description
CR ID:
BAC-6561
ReleaseNotes_CodingClassic, Version 5.2.1, Software Platforms
Page 2 of 5

CR Headline:
Wrong description of event mapping "Coding_TimerMain" in
IntegrationManual
Description of Issues:
Fix description of event mapping "Coding_TimerMain" in
Integration Manual.
Description of Changes:
Changed description from "Mode Switch Event" to "Timing Event".
Changed Files:
doc/CodingClassic_IntegrationManual.pdf
Compatibility:
Item
Description
CR ID:
BAC-6585
CR Headline:
Rework Coding_paramdef.arxml
Description of Issues:
Add missing configuration parameters, provide human readable
Coding function value input field and support tool based
implementation type range check.
Description of Changes:
Added missing configuration parameters 'lowerlimit' and
'upperlimit'. Use choice container for supported implementation
data types. Updated PAGe include files to convert human readable
Coding function values to Coding internal machine code.
Changed Files:
doc/CodingClassic_IntegrationManual.pdf
Compatibility:
Revision 5.2.0 [Released]
Item
Description
CR ID:
BAC-6434
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/CodingClassic_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6350
CR Headline:
RoutineSignal Arrays must be configured with
VARIABLE_LENGTH
Description of Issues:
Routine signal arrays must be configured with
VARIABLE_LENGTH.
Description of Changes:
Coding generic has to support an additional function parameter
'dataLength' and Coding adapter has to support configuration with
VARIABLE_LENGTH.
Changed Files:
src/Coding_UDSAdapter.c
CMakeLists.txt
generate/meta/Coding_ext_interfaces.arxml.pgen
ReleaseNotes_CodingClassic, Version 5.2.1, Software Platforms
Page 3 of 5

Compatibility:
Revision 5.1.0 [Released]
Item
Description
CR ID:
BAC-6402
CR Headline:
Activation of signature verification
Description of Issues:
Customize the function calls according to specification. Support
the provided Crypto-Lib.
Description of Changes:
Removed unnecessary function call from Coding module.
Changed Coding adapter to fit to the provided Crypto-Lib on one
side and to fullfill the specification requirements on the other side.
Changed Files:
generate/meta/Coding_ext_interfaces.arxml.pgen
generate/meta/Coding_internal.arxml.pgen
src/Coding_CryptoAdapter.c
Compatibility:
Revision 5.0.1 [Released]
Item
Description
CR ID:
BAC-6250
CR Headline:
CodingClassic_MemMap.h.sample should be
Coding_MemMap.h.sample
Description of Issues:
Sample file has wrong file name.
Description of Changes:
Corrected file name.
Changed Files:
template/include/Coding_MemMap.h.sample
Compatibility:
Item
Description
CR ID:
BAC-6239
CR Headline:
Improve requirements traceability
Description of Issues:
Improve generation of documents.
Description of Changes:
Replace special character and add reference information.
Changed Files:
doc/Coding_RequirementsTable.pdf
Compatibility:
Item
Description
CR ID:
BAC-6224
CR Headline:
PublishedInformation of BMW modules is not modeled according
to ASR4.2.2
Description of Issues:
Removed depricated ImplementationConfigClass from
PublishedInformation and added ValueConfigClass instead.
Description of Changes:
File content was updated.
Changed Files:
cfgdesc/CodingClassic_paramdef.arxml
Compatibility:
ReleaseNotes_CodingClassic, Version 5.2.1, Software Platforms
Page 4 of 5

Item
Description
CR ID:
BAC-5170
CR Headline:
Modules paramdef violates TPS_ECUC_06004
Description of Issues:
AdminData filed in ECU configuration parameter definition is
required.
Description of Changes:
Added missing AdminData field.
Changed Files:
cfgdesc/CodingClassic_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_CodingClassic, Version 5.2.1, Software Platforms
Page 5 of 5

Document Outline

8 - CodingClassic_RequirementsTable

9 - CodingClassic_RequirementsTable_ind

Outline
Page 1
Page 2
Page 3
Page 4

10 - CodingClassic_RequirementsTables


Coding Classic Requirements Table
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.2.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.2.1
2017-12-14
JC-42
Version Update
5.2.0
2017-11-09
JC-42
Version Update
5.1.0
2017-10-12
JC-42
Version Update
5.0.1
2017-09-14
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
CodingClassic_RequirementsTable, Version 5.2.1, Software Platforms
Page 1 of 4

Table of Contents
1 Related documentation
3
2 Requirements Table
4
CodingClassic_RequirementsTable, Version 5.2.1, Software Platforms
Page 2 of 4

1
Related documentation
References
[1] LH Codierung
SAP: 10728424 000 02
[2] Diagnose - Systembeschreibung
SAP: 10000784-000-12
CodingClassic_RequirementsTable, Version 5.2.1, Software Platforms
Page 3 of 4

2
Requirements Table
The Requirements are taken from [1, 2].
Requirement
Description
Satisfied by
[COD_059]
No description
[COD_063]
No description
[COD_114]
No description
[COD_117]
No description
[COD_127]
No description
[COD_129]
No description
[COD_130]
No description
[COD_138]
No description
[COD_162]
No description
[COD_166]
No description
[COD_173]
No description
[COD_174]
No description
[COD_178]
No description
[COD_179]
No description
[COD_182]
No description
[COD_184]
No description
[COD_185]
No description
[COD_188]
No description
[COD_189]
No description
[COD_213]
No description
[COD_214]
No description
[COD_215]
No description
[COD_241]
No description
[COD_244]
No description
[COD_251]
No description
[COD_252]
No description
[COD_253]
No description
[COD_254]
No description
[COD_258]
No description
[COD_292]
No description
[COD_294]
No description
[COD_297]
No description
[COD_302]
No description
[COD_304]
No description
[COD_307]
No description
[COD_314]
No description
[COD_316]
No description
[COD_329]
No description
[COD_331]
No description
[COD_334]
No description
[COD_367]
No description
CodingClassic_RequirementsTable, Version 5.2.1, Software Platforms
Page 4 of 4

Document Outline

11 - CodingGeneric_ReleaseNotes

12 - CodingGeneric_ReleaseNotes_ind

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

13 - CodingGeneric_ReleaseNotess


Release Notes CodingGeneric
Project
BMW AUTOSAR Core 4 Rel. 3 and adaptive BMW AUTOSAR Core Rel. 1
Author
BMW AG
Release Date
2017-12-14
Version
5.2.1
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.2.1
2017-12-14
BAC-6660, BAC-6704, BAC-6585, BAC-6736, BAC-6192
5.2.0
2017-11-09
BAC-6434, BAC-6350
5.1.0
2017-10-12
BAC-6402
5.0.1
2017-09-14
BAC-6302, BAC-6239, BAC-6224, BAC-6073, BAC-6003,
BAC-5170
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_CodingGeneric, Version 5.2.1, Software Platforms
Page 1 of 6

1
Module Description
The Coding system consists of a Coding module that is part of the ECU application and the Coder.
Almost in the same manner as the Bootloader programs the ROM of an ECU, the Coding module codes
the NV memory of an ECU with vehicle specific data derived from the vehicle description document e.g.
type key, extra equipment, country specifics, year of model/construction stage, additional comments or
service upgrade options.
2
Revisions and Modifications
Revision 5.2.1 [Released]
Item
Description
CR ID:
BAC-6660
CR Headline:
Correct Misra- and Metric-violations
Description of Issues:
Correct Misra- and Metric-violations and compiler warnings.
Description of Changes:
Correct Misra- and Metric-violations and compiler warnings.
Changed Files:
generate/include/Coding_Cfg.h.pgen
doc/CodingGeneric_RequirementsTable.pdf
template/include/Coding_MemMap.h.sample
generate/src/Coding_Function.c.pgen
generate/include/Coding_Version.h.pgen
generate/include/Coding_Function.h.pgen
generate/src/Coding_Cfg.c.pgen
include/Coding_CryptoAdapter.h
generate/pageinclude/Coding_Functions.pgen
generate/pageinclude/Coding_Function_Types.pgen
src/Coding.c
include/Coding.h
Compatibility:
Item
Description
CR ID:
BAC-6704
CR Headline:
Activation of signature verification (RSA)
Description of Issues:
Changed Coding adapter to fit to the provided Crypto-Lib (RSA).
Description of Changes:
Changed Coding adapter to fit to the provided Crypto-Lib (RSA).
Changed Files:
generate/pageinclude/Coding_Functions.pgen
generate/src/Coding_Function.c.pgen
Compatibility:
Item
Description
CR ID:
BAC-6585
CR Headline:
Rework Coding_paramdef.arxml
ReleaseNotes_CodingGeneric, Version 5.2.1, Software Platforms
Page 2 of 6

Description of Issues:
Add missing configuration parameters, provide human readable
Coding function value input field and support tool based
implementation type range check.
Description of Changes:
Added missing configuration parameters 'lowerlimit' and
'upperlimit'. Use choice container for supported implementation
data types. Updated PAGe include files to convert human readable
Coding function values to Coding internal machine code.
Changed Files:
generate/pageinclude/Coding_Function_Types.pgen
cfgdesc/Coding_paramdef.arxml
generate/pageinclude/Coding_Functions.pgen
Compatibility:
Item
Description
CR ID:
BAC-6736
CR Headline:
Fix optional production error CEUD compile error
Description of Issues:
Deactivation of optional production error leads to compile error.
Description of Changes:
Add missing preprocessor directives.
Changed Files:
src/Coding.c
Compatibility:
Item
Description
CR ID:
BAC-6192
CR Headline:
Identical function names in different coding areas lead to
generation of duplicate event names
Description of Issues:
Add Coding configuration plausibility check.
Description of Changes:
Check uniqueness of all Coding function names in Coding
configuration.
Changed Files:
generate/pageinclude/Coding_Functions.pgen
Compatibility:
Revision 5.2.0 [Released]
Item
Description
CR ID:
BAC-6434
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/Coding_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6350
ReleaseNotes_CodingGeneric, Version 5.2.1, Software Platforms
Page 3 of 6

CR Headline:
RoutineSignal Arrays must be configured with
VARIABLE_LENGTH
Description of Issues:
Routine signal arrays must be configured with
VARIABLE_LENGTH.
Description of Changes:
Coding generic has to support an additional function parameter
'dataLength' and Coding adapter has to support configuration with
VARIABLE_LENGTH.
Changed Files:
src/Coding.c
include/Coding.h
Compatibility:
Revision 5.1.0 [Released]
Item
Description
CR ID:
BAC-6402
CR Headline:
Activation of signature verification
Description of Issues:
Customize the function calls according to specification. Support
the provided Crypto-Lib.
Description of Changes:
Removed unnecessary function call from Coding module.
Changed Coding adapter to fit to the provided Crypto-Lib on one
side and to fullfill the specification requirements on the other side.
Changed Files:
generate/include/Coding_Cfg.h.pgen
cfgdesc/Coding_paramdef.arxml
include/Coding_CryptoAdapter.h
generate/pageinclude/Coding_Functions.pgen
generate/pageinclude/Coding_Function_Types.pgen
src/Coding.c
Compatibility:
Revision 5.0.1 [Released]
Item
Description
CR ID:
BAC-6302
CR Headline:
Add look up table for type conversion
Description of Issues:
Provide look up table (adaptive platform and ara implementation
data types) for PAGe.
Description of Changes:
Added look up table for adaptive platform and ara implementation
data types in page include file.
Changed Files:
generate/pageinclude/Coding_Functions.pgen
Compatibility:
Item
Description
CR ID:
BAC-6239
CR Headline:
Improve requirements traceability
Description of Issues:
Improve generation of documents.
Description of Changes:
Replace special character and add reference information.
ReleaseNotes_CodingGeneric, Version 5.2.1, Software Platforms
Page 4 of 6

Changed Files:
doc/Coding_RequirementsTable.pdf
Compatibility:
Item
Description
CR ID:
BAC-6224
CR Headline:
PublishedInformation of BMW modules is not modeled according
to ASR4.2.2
Description of Issues:
Removed depricated ImplementationConfigClass from
PublishedInformation and added ValueConfigClass instead.
Description of Changes:
File content was updated.
Changed Files:
cfgdesc/Coding_paramdef.arxml
Compatibility:
Item
Description
CR ID:
BAC-6073
CR Headline:
Stop timeout monitoring during module shutdown
Description of Issues:
Stop timeout monitoring (Coding data qualification) during
shutdown.
Description of Changes:
Added call: Coding_Timer_CancelTimer() in Coding_Shutdown()
(sync branch) and in
Coding_NvMFinishedCallbackWriteCodingData() (async branch).
Changed Files:
src/Coding.c
Compatibility:
Item
Description
CR ID:
BAC-6003
CR Headline:
Transformation rule must respect signedness of nvRam type
Description of Issues:
The Coding transformation rule mechanism does not consider that
the Coding data are stored in an uint8 array when the user
application requests an sint8 Coding value.
Description of Changes:
Add missing type cast when Coding data are extracted from uint8
array.
Changed Files:
generate/src/Coding_Function.c.pgen
Compatibility:
Item
Description
CR ID:
BAC-5170
CR Headline:
Modules paramdef violates TPS_ECUC_06004
Description of Issues:
AdminData filed in ECU configuration parameter definition is
required.
Description of Changes:
Added missing AdminData field.
Changed Files:
cfgdesc/Coding_paramdef.arxml
Compatibility:
Revision 5.0.0 [Released]
ReleaseNotes_CodingGeneric, Version 5.2.1, Software Platforms
Page 5 of 6

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_CodingGeneric, Version 5.2.1, Software Platforms
Page 6 of 6

Document Outline

14 - CodingGeneric_RequirementsTable

15 - CodingGeneric_RequirementsTable_ind

Outline
Page 1
Page 2
Page 3
Page 4
Page 5

16 - CodingGeneric_RequirementsTables


Coding 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.2.1
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.2.1
2017-12-14
JC-42
Version Update
5.2.0
2017-11-09
JC-42
Version Update
5.1.0
2017-10-12
JC-42
Version Update
5.0.1
2017-09-14
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
CodingGeneric_RequirementsTable, Version 5.2.1, Software Platforms
Page 1 of 5

Table of Contents
1 Related documentation
3
2 Requirements Table
4
CodingGeneric_RequirementsTable, Version 5.2.1, Software Platforms
Page 2 of 5

1
Related documentation
References
[1] LH Codierung
SAP: 10728424 000 02
CodingGeneric_RequirementsTable, Version 5.2.1, Software Platforms
Page 3 of 5

2
Requirements Table
The Requirements are taken from [1].
Requirement
Description
Satisfied by
[COD_059]
No description
[COD_089]
No description
[COD_091]
No description
[COD_092]
No description
[COD_093]
No description
[COD_097]
No description
[COD_114]
No description
[COD_119]
No description
[COD_121]
No description
[COD_126]
No description
[COD_131]
No description
[COD_132]
No description
[COD_133]
No description
[COD_134]
No description
[COD_135]
No description
[COD_136]
No description
[COD_137]
No description
[COD_138]
No description
[COD_139]
No description
[COD_141]
No description
[COD_143]
No description
[COD_145]
No description
[COD_147]
No description
[COD_149]
No description
[COD_150]
No description
[COD_162]
No description
[COD_166]
No description
[COD_169]
No description
[COD_173]
No description
[COD_174]
No description
[COD_175]
No description
[COD_178]
No description
[COD_179]
No description
[COD_180]
No description
[COD_182]
No description
[COD_183]
No description
[COD_184]
No description
[COD_185]
No description
[COD_186]
No description
[COD_188]
No description
[COD_189]
No description
[COD_205]
No description
[COD_206]
No description
[COD_207]
No description
[COD_209]
No description
[COD_213]
No description
[COD_214]
No description
[COD_215]
No description
CodingGeneric_RequirementsTable, Version 5.2.1, Software Platforms
Page 4 of 5

Requirement
Description
Satisfied by
[COD_216]
No description
[COD_218]
No description
[COD_220]
No description
[COD_222]
No description
[COD_225]
No description
[COD_226]
No description
[COD_227]
No description
[COD_228]
No description
[COD_229]
No description
[COD_230]
No description
[COD_231]
No description
[COD_232]
No description
[COD_233]
No description
[COD_234]
No description
[COD_235]
No description
[COD_237]
No description
[COD_238]
No description
[COD_239]
No description
[COD_240]
No description
[COD_241]
No description
[COD_244]
No description
[COD_246]
No description
[COD_249]
No description
[COD_250]
No description
[COD_251]
No description
[COD_252]
No description
[COD_253]
No description
[COD_254]
No description
[COD_255]
No description
[COD_257]
No description
[COD_258]
No description
[COD_259]
No description
[COD_260]
No description
[COD_280]
No description
[COD_285]
No description
[COD_292]
No description
[COD_294]
No description
[COD_297]
No description
[COD_302]
No description
[COD_304]
No description
[COD_307]
No description
[COD_310]
No description
[COD_314]
No description
[COD_316]
No description
[COD_329]
No description
[COD_331]
No description
[COD_334]
No description
[COD_352]
No description
[COD_367]
No description
[COD_368]
No description
CodingGeneric_RequirementsTable, Version 5.2.1, Software Platforms
Page 5 of 5

Document Outline