instruction
stringlengths 29
35k
| input
stringclasses 1
value | output
stringlengths 29
35k
|
|---|---|---|
C1+ CV01 - Open phase faults during vehicle integration D2 -- Problem Description (R: PRE):
During Vehicle integration, open phase faults have been observed
Requirement which is violated (R: Originator):
Expected behavior (R: Originator):
Operating Environment (R: Originator):
Test case identification (R: Originator):
D3 -- Established Interim Containment Action (R: PRE):
n/a
D4a -- Verified Root Cause (R: PRE):
Open phase faults: Current control tune parameters incorrect (no EPP current control tuning performed)
D4b -- Verified Escape Point (R: PRE):
Logged Data (DTC Readout/CAN Log/PAR File)(R: Originator):
PCA:
Current control tune to be performed after Dyno4 is operational in BVP
D7 -- Lessons Learned (R: PRE): The solution was proposed in the attachment and consists in the current controller gain increase, as they were incorrect. The current controller parameters have been updated in the .par file at the end of July. So far, the issue has not been seen again.
The following parameters have been updated:
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisIntglGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisPropGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisIntglGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisPropGainMap
More details in the attached message. | C1+ CV01 - Open phase faults during vehicle integration D2 -- Problem Description (R: PRE):
During Vehicle integration, open phase faults have been observed
Requirement which is violated (R: Originator):
Expected behavior (R: Originator):
Operating Environment (R: Originator):
Test case identification (R: Originator):
D3 -- Established Interim Containment Action (R: PRE):
n/a
D4a -- Verified Root Cause (R: PRE):
Open phase faults: Current control tune parameters incorrect (no EPP current control tuning performed)
D4b -- Verified Escape Point (R: PRE):
Logged Data (DTC Readout/CAN Log/PAR File)(R: Originator):
PCA:
Current control tune to be performed after Dyno4 is operational in BVP
D7 -- Lessons Learned (R: PRE): The solution was proposed in the attachment and consists in the current controller gain increase, as they were incorrect. The current controller parameters have been updated in the .par file at the end of July. So far, the issue has not been seen again.
The following parameters have been updated:
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisIntglGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisPropGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisIntglGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisPropGainMap
More details in the attached message. |
|
[Opel K0][Requirement] - Drop and replace SSM_PB related modules SWPM - SKO (21.07.21 - 13:47)
--------------------------------------------------------------------------------
Brief investigation comment:
After latest branch from VW it is identified that some of SSM_PB related modules need to be updated as shown below:
Drop and replace the yellow highlighted modules?
Instead the following modules shall be shared from BrkSW – POOL into the PSA k0
1.3 of
And
-------------------------------------------------------------------------------- Brief analysis summary:
-----------------------
Need to drop the sub components Ssm_Pbi and SsmPbWrp from Opel K0 - EPBi Folder and share it from BrkSW Pool.
------------------------------------------------------------------------------
TASK
------------------------------------------------------------------------------
Drop the Ssm_Pbi and SsmPbWrp components from the below Repository location path
/SCS#Customer/PSA/K0/05_Software/VIEW_Mainline/MMC_APPL/MMC_APPL_SW/Application/EPBi/project.pj
Share Ssm_Pbi & SsmPbWrp from BrkSW repository location
/BrkSw/SwDevelopmentPool/Software/Components/Ssm_Pbi/project.pj- Checkpoint 1.9.2.1
/BrkSw/SwDevelopmentPool/Software/Components/SsmPbWrp/project.pj- Checkpoint 1.3
Acceptance criteria:
-----------------------------
After sharing the new sub components verify the compilation check.
Owner: Sravan Kumar Akoju
Reviewer: Mehta Jay
Estimated design effort/h: 1hr
Estimated implementation effort/h: 3hr
Estimated unit testing effort/h: 0 | [Opel K0][Requirement] - Drop and replace SSM_PB related modules SWPM - SKO (21.07.21 - 13:47)
--------------------------------------------------------------------------------
Brief investigation comment:
After latest branch from VW it is identified that some of SSM_PB related modules need to be updated as shown below:
Drop and replace the yellow highlighted modules?
Instead the following modules shall be shared from BrkSW – POOL into the PSA k0
1.3 of
And
-------------------------------------------------------------------------------- Brief analysis summary:
-----------------------
Need to drop the sub components Ssm_Pbi and SsmPbWrp from Opel K0 - EPBi Folder and share it from BrkSW Pool.
------------------------------------------------------------------------------
TASK
------------------------------------------------------------------------------
Drop the Ssm_Pbi and SsmPbWrp components from the below Repository location path
/SCS#Customer/PSA/K0/05_Software/VIEW_Mainline/MMC_APPL/MMC_APPL_SW/Application/EPBi/project.pj
Share Ssm_Pbi & SsmPbWrp from BrkSW repository location
/BrkSw/SwDevelopmentPool/Software/Components/Ssm_Pbi/project.pj- Checkpoint 1.9.2.1
/BrkSw/SwDevelopmentPool/Software/Components/SsmPbWrp/project.pj- Checkpoint 1.3
Acceptance criteria:
-----------------------------
After sharing the new sub components verify the compilation check.
Owner: Sravan Kumar Akoju
Reviewer: Mehta Jay
Estimated design effort/h: 1hr
Estimated implementation effort/h: 3hr
Estimated unit testing effort/h: 0 |
|
[0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- Conclusion taken over from spawned CR with first change regarding this topic: [31.08.2021], E. Webert:
- Soll dieses Änderung noch für den MEB Classic erfolgen? Ja, sonst sind Kundenbeanstandungen zu erwarten (Pedalrückwirkungen)
- Für welche SW? Geplant für X523 => Wann ist die X523?
- Frage aus dem CCB mit VW: Tritt es auch bei anderen Boost-Funktionen oder der HVV (Hinterachsvollverzögerung) auf? Sollte man auch bei weiteren Funktionen Pedalkraftkompensation abschalten?
- HVV heißt bei uns RAxB (vgl. Mail im Anhang AW_ OP 5532680 - _0521__CASE__VW_MEB41x_SCS_MCP oscillations cause HBA exit and HBA triggering_CBecker.msg)
- Wir gucken auf den ARB-Mode BRK_CTRL_ARB_BRAKE_ASSIST und dieser Mode deckt nicht nur HBA ab, sondern alle HBX-Funktionen (HBA, HBB, DBK, RAxB, RAB [Prefill])
- Heißt wir brauchen keine weiteren Ausnahmen.
[13.09.2021], E. Webert:
- es muss eine weitere Ausnahme erfolgen
- vgl. dazu CR 5703695 - RB: Pedalflattern im Stillstand (HBA und PFC im Stillstand)
- die Logik wird mit der 2. Task eingecheckt => Task 5705543
[04.10.2021], E. Webert:
- Unklar, ob die Änderung das Problem löst
- laut weiteren Analysen kommt es zu einem nicht gewünschten Verhalten aufgrund einer Logik im ARB (MAX-Bildung bei SSM?)
- Man sollte versuchen es vorher im ARB zu lösen, dann kann dieses CR rejectet werden
- auf Feedback warten
[04.11.2021], E. Webert:
- vg. Mail im Anhang: AW_ noch offene OP-Bewertung für die anstehende CAT5.msg
- laut CASE soll für MEB Classic erstmal keine Lösung erfolgen
- für UN ECE soll es neue bewertet werden => teilweise gibt es Lösungsvorschläge für einen Fix im ARB => Mail im Anhang: WG Analyse Anregungen nach HBB.msg
- Punkt wird rejectet | [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- Conclusion taken over from spawned CR with first change regarding this topic: [31.08.2021], E. Webert:
- Soll dieses Änderung noch für den MEB Classic erfolgen? Ja, sonst sind Kundenbeanstandungen zu erwarten (Pedalrückwirkungen)
- Für welche SW? Geplant für X523 => Wann ist die X523?
- Frage aus dem CCB mit VW: Tritt es auch bei anderen Boost-Funktionen oder der HVV (Hinterachsvollverzögerung) auf? Sollte man auch bei weiteren Funktionen Pedalkraftkompensation abschalten?
- HVV heißt bei uns RAxB (vgl. Mail im Anhang AW_ OP 5532680 - _0521__CASE__VW_MEB41x_SCS_MCP oscillations cause HBA exit and HBA triggering_CBecker.msg)
- Wir gucken auf den ARB-Mode BRK_CTRL_ARB_BRAKE_ASSIST und dieser Mode deckt nicht nur HBA ab, sondern alle HBX-Funktionen (HBA, HBB, DBK, RAxB, RAB [Prefill])
- Heißt wir brauchen keine weiteren Ausnahmen.
[13.09.2021], E. Webert:
- es muss eine weitere Ausnahme erfolgen
- vgl. dazu CR 5703695 - RB: Pedalflattern im Stillstand (HBA und PFC im Stillstand)
- die Logik wird mit der 2. Task eingecheckt => Task 5705543
[04.10.2021], E. Webert:
- Unklar, ob die Änderung das Problem löst
- laut weiteren Analysen kommt es zu einem nicht gewünschten Verhalten aufgrund einer Logik im ARB (MAX-Bildung bei SSM?)
- Man sollte versuchen es vorher im ARB zu lösen, dann kann dieses CR rejectet werden
- auf Feedback warten
[04.11.2021], E. Webert:
- vg. Mail im Anhang: AW_ noch offene OP-Bewertung für die anstehende CAT5.msg
- laut CASE soll für MEB Classic erstmal keine Lösung erfolgen
- für UN ECE soll es neue bewertet werden => teilweise gibt es Lösungsvorschläge für einen Fix im ARB => Mail im Anhang: WG Analyse Anregungen nach HBB.msg
- Punkt wird rejectet |
|
[0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- [31.08.2021], E. Webert:
- Soll dieses Änderung noch für den MEB Classic erfolgen? Ja, sonst sind Kundenbeanstandungen zu erwarten (Pedalrückwirkungen)
- Für welche SW? Geplant für X523 => Wann ist die X523?
- Frage aus dem CCB mit VW: Tritt es auch bei anderen Boost-Funktionen oder der HVV (Hinterachsvollverzögerung) auf? Sollte man auch bei weiteren Funktionen Pedalkraftkompensation abschalten?
- HVV heißt bei uns RAxB (vgl. Mail im Anhang AW_ OP 5532680 - _0521__CASE__VW_MEB41x_SCS_MCP oscillations cause HBA exit and HBA triggering_CBecker.msg)
- Wir gucken auf den ARB-Mode BRK_CTRL_ARB_BRAKE_ASSIST und dieser Mode deckt nicht nur HBA ab, sondern alle HBX-Funktionen (HBA, HBB, DBK, RAxB, RAB [Prefill])
- Heißt wir brauchen keine weiteren Ausnahmen.
[13.09.2021], E. Webert:
- es muss eine weitere Ausnahme erfolgen
- vgl. dazu CR 5703695 - RB: Pedalflattern im Stillstand (HBA und PFC im Stillstand)
- die Logik wird nach erfolgreichem Test mit einem weiteren CR eingecheckt: 5732889 | [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- [31.08.2021], E. Webert:
- Soll dieses Änderung noch für den MEB Classic erfolgen? Ja, sonst sind Kundenbeanstandungen zu erwarten (Pedalrückwirkungen)
- Für welche SW? Geplant für X523 => Wann ist die X523?
- Frage aus dem CCB mit VW: Tritt es auch bei anderen Boost-Funktionen oder der HVV (Hinterachsvollverzögerung) auf? Sollte man auch bei weiteren Funktionen Pedalkraftkompensation abschalten?
- HVV heißt bei uns RAxB (vgl. Mail im Anhang AW_ OP 5532680 - _0521__CASE__VW_MEB41x_SCS_MCP oscillations cause HBA exit and HBA triggering_CBecker.msg)
- Wir gucken auf den ARB-Mode BRK_CTRL_ARB_BRAKE_ASSIST und dieser Mode deckt nicht nur HBA ab, sondern alle HBX-Funktionen (HBA, HBB, DBK, RAxB, RAB [Prefill])
- Heißt wir brauchen keine weiteren Ausnahmen.
[13.09.2021], E. Webert:
- es muss eine weitere Ausnahme erfolgen
- vgl. dazu CR 5703695 - RB: Pedalflattern im Stillstand (HBA und PFC im Stillstand)
- die Logik wird nach erfolgreichem Test mit einem weiteren CR eingecheckt: 5732889 |
|
[0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- Test can be done by CASE | [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- Test can be done by CASE |
|
HKMC_SK PE | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code Activity Description:
With the outcome from W130j as Impact Analysis results on SWE1 per one clustered change from this release and one build, the change impacted features and behaviors identified and determined, SW Requriement Project Manager arrange Feature manager or Funciton Developers to Generate SW Requriements by following below Task scope and ZF procedures and steps:
(Notes: Due to specific change may derives tailored activities from Impact Analysis on below full activity scope, therefore the actual activities tailor status of the Task to be described by Task Responsible in this Task Notes area, per Review activity description, it need performed in connected review Task Conclusion area due to the main Task Notes area can't be updated while in Reivew phase)
Task Scope:
Feature:
Behavior:
Process following:
1. Develop Behaviour Requirements (C_066_2_SSE_002_EN_SoftwareRequirementsAnalysis defines general)
1.1 Write SW Requirements with bleow sub steps which follows C_066_3_SSE_025_EN Write SW Requirements Work Instruction:
3.1. Processing Collected Software Requirements
3.2. Manage Requirements and Traceability
3.3. Software Requirements Style
3.4. Handling of software requirement sources
3.5. Handling of Signals and Parameters for software requirements
3.6. Handling of Attributes for software requirements
Attributes shall be set according to the work instruction C_066_3_SSE_026_EN_SW_Attributes
1.2 ?Assign SW Releases for SW Requirements with below sub steps which follows C_066_3_SSE_020_EN Assign SW Releases for SW Requirements Work Instruction:
3.1. Add SW release to a requirement
3.2. Removing a SW release from a requirement
3.3. Maintaining requirements assigned to multiple SW releases – functional change
3.4. Maintaining requirements assigned to multiple SW releases – no functional change
3.5. Maintaining requirements assigned to multiple SW releases – bug fix
2. Review Software Requirements (C_066_2_SSE_002_EN_SoftwareRequirementsAnalysis defines general)
Organise a Software Requirements Review performed with below sub steps and follows C_066_3_SSE_029_EN Organise a Software Requirements Review Work Instruction:
3.1. Organize a formal software requirements review
3.1.1. Prepare the review of software requirements
3.1.2. Perform technical and formal review
3.1.3. Organize Review by stakeholder
3.1.4. Stakeholder Review
3.1.5. Finalize SW Requirements review
3.2. Organize an informal software requirements review
4. Review invitation
Input for this WP are:
?
1. SW Release Plan
2. System Requirement & Architecture (Compliance Analyzed)
3. ECU HW design spec (Compliance Analyzed)
4. Customer Requirement (Compliance Analyzed)
5. Impact Analysis
6. SW engineering traceability matrix
?
Output of this WP:
1. SW Requirement
2. SW Requirement Baseline
3. FSF Manual (Updates)
Responsible: SW Feature Manager, SW FM Developer
Support: SW Requirement Porject Manager, SWPM, SW Safety Engineer, SW Test Enineer ? Change to Analysed | HKMC_SK PE | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code Activity Description:
With the outcome from W130j as Impact Analysis results on SWE1 per one clustered change from this release and one build, the change impacted features and behaviors identified and determined, SW Requriement Project Manager arrange Feature manager or Funciton Developers to Generate SW Requriements by following below Task scope and ZF procedures and steps:
(Notes: Due to specific change may derives tailored activities from Impact Analysis on below full activity scope, therefore the actual activities tailor status of the Task to be described by Task Responsible in this Task Notes area, per Review activity description, it need performed in connected review Task Conclusion area due to the main Task Notes area can't be updated while in Reivew phase)
Task Scope:
Feature:
Behavior:
Process following:
1. Develop Behaviour Requirements (C_066_2_SSE_002_EN_SoftwareRequirementsAnalysis defines general)
1.1 Write SW Requirements with bleow sub steps which follows C_066_3_SSE_025_EN Write SW Requirements Work Instruction:
3.1. Processing Collected Software Requirements
3.2. Manage Requirements and Traceability
3.3. Software Requirements Style
3.4. Handling of software requirement sources
3.5. Handling of Signals and Parameters for software requirements
3.6. Handling of Attributes for software requirements
Attributes shall be set according to the work instruction C_066_3_SSE_026_EN_SW_Attributes
1.2 ?Assign SW Releases for SW Requirements with below sub steps which follows C_066_3_SSE_020_EN Assign SW Releases for SW Requirements Work Instruction:
3.1. Add SW release to a requirement
3.2. Removing a SW release from a requirement
3.3. Maintaining requirements assigned to multiple SW releases – functional change
3.4. Maintaining requirements assigned to multiple SW releases – no functional change
3.5. Maintaining requirements assigned to multiple SW releases – bug fix
2. Review Software Requirements (C_066_2_SSE_002_EN_SoftwareRequirementsAnalysis defines general)
Organise a Software Requirements Review performed with below sub steps and follows C_066_3_SSE_029_EN Organise a Software Requirements Review Work Instruction:
3.1. Organize a formal software requirements review
3.1.1. Prepare the review of software requirements
3.1.2. Perform technical and formal review
3.1.3. Organize Review by stakeholder
3.1.4. Stakeholder Review
3.1.5. Finalize SW Requirements review
3.2. Organize an informal software requirements review
4. Review invitation
Input for this WP are:
?
1. SW Release Plan
2. System Requirement & Architecture (Compliance Analyzed)
3. ECU HW design spec (Compliance Analyzed)
4. Customer Requirement (Compliance Analyzed)
5. Impact Analysis
6. SW engineering traceability matrix
?
Output of this WP:
1. SW Requirement
2. SW Requirement Baseline
3. FSF Manual (Updates)
Responsible: SW Feature Manager, SW FM Developer
Support: SW Requirement Porject Manager, SWPM, SW Safety Engineer, SW Test Enineer ? Change to Analysed |
|
[Issue] of PBC_040 - SIL Test - Actuator change to Unknown at RAR and HostAvailability NONE/APPLY/RELEASE, before RAR or Parkapply Preconditions:Init with Fully released actuators. Close to Parkapplied, Set PbcIn.HostavailabilityRl/Rr/Both = None OR Relase OR Apply.
Action:Set Wheespeed to 3 km/h or perform a parkapply
Expected Behaviour: Good side perform a RAR.Bad side MotorCommad not move to any state.
Actual behaviour: Good side perform a RAR. bad side set PbcOut.MotorCommad = Apply(Stop/None one for cycle, and set PbcOut.ActuatorState to ePbcActuatorStateUnknown
11/1/21: Analzed by Lubbers with changes made to Design Document.
Further Information: Same behaviour with undervoltage and parkapply. Only left side try to start an actuation. This behaviour seems to be strange.
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps. | [Issue] of PBC_040 - SIL Test - Actuator change to Unknown at RAR and HostAvailability NONE/APPLY/RELEASE, before RAR or Parkapply Preconditions:Init with Fully released actuators. Close to Parkapplied, Set PbcIn.HostavailabilityRl/Rr/Both = None OR Relase OR Apply.
Action:Set Wheespeed to 3 km/h or perform a parkapply
Expected Behaviour: Good side perform a RAR.Bad side MotorCommad not move to any state.
Actual behaviour: Good side perform a RAR. bad side set PbcOut.MotorCommad = Apply(Stop/None one for cycle, and set PbcOut.ActuatorState to ePbcActuatorStateUnknown
11/1/21: Analzed by Lubbers with changes made to Design Document.
Further Information: Same behaviour with undervoltage and parkapply. Only left side try to start an actuation. This behaviour seems to be strange.
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps. |
|
[Issue] of PBC_040 - SIL Test - Actuation stops even if actuation is possible due to change of Hostavailablity Preconditions: Init with Fully released actuators.
Action: Apply or Release, Set PbcInHostavailability to apply if acatuation is in apply direction or release if actuation is in release direction.
Expected Behaviour: Actuation is finished
Actual behaviour: Actuation stops and affected actuator is unknown
Further Information/Requirements: If actuation is possible shall not stop..
Please see attachment
1/11/21: Analyzed by Mark Lubbers. Changes made to Design Document. EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps. | [Issue] of PBC_040 - SIL Test - Actuation stops even if actuation is possible due to change of Hostavailablity Preconditions: Init with Fully released actuators.
Action: Apply or Release, Set PbcInHostavailability to apply if acatuation is in apply direction or release if actuation is in release direction.
Expected Behaviour: Actuation is finished
Actual behaviour: Actuation stops and affected actuator is unknown
Further Information/Requirements: If actuation is possible shall not stop..
Please see attachment
1/11/21: Analyzed by Mark Lubbers. Changes made to Design Document. EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps. |
|
[Issue] of PBC_040 - SIL Test - RAR perform with speed >= 15 km/h Preconditions:Precondition for RAR
Action:Set all speeds >= 15 km/h
Expected Behaviour: No RAR perfomed
Actual behaviour: RAR is performed
Further Information/Requirements: This threshold of 15km/h is the limit of RAR,because of HSB Vehicle safety speed. Maybe the HSB from Host will not enable the applyline and this will lead an internal fault. See VDA Chapter 3.1.2 HOST Safety Barrier
Investigate possible difference between host and PBC ref speed calculation.
SIL Test -130-304-PBC_RAR_BY_WHEEL_SPEED_15_KMH
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.
12/02/21: Change Implemented per associated task. | [Issue] of PBC_040 - SIL Test - RAR perform with speed >= 15 km/h Preconditions:Precondition for RAR
Action:Set all speeds >= 15 km/h
Expected Behaviour: No RAR perfomed
Actual behaviour: RAR is performed
Further Information/Requirements: This threshold of 15km/h is the limit of RAR,because of HSB Vehicle safety speed. Maybe the HSB from Host will not enable the applyline and this will lead an internal fault. See VDA Chapter 3.1.2 HOST Safety Barrier
Investigate possible difference between host and PBC ref speed calculation.
SIL Test -130-304-PBC_RAR_BY_WHEEL_SPEED_15_KMH
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.
12/02/21: Change Implemented per associated task. |
|
[Issue] of PBC_040 - SIL Test - PowerLatchRequest = ePbcPowerLatchNotRequested too early Preconditions: Init with Fully released actuators.
Action:Apply Release under several condition.
Expected Behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested two cycles after last PbcOut.MotorComamd = ePbcMotorCommandNone
Actual behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested after last Pbcout.Actuatorstae = ePbcActuatorStateParkApplied ORePbcActuatorStateReleased
Further Information/Requirements: This can lead to a lock of software. In the past we made the experience that the Host system calls PBC.Cyclic as long as PbcOut.EcuPowerLatchRequest = ePbcPowerLatchRequested and if this signal depends on the actuatorstate it can happen that the PbcMotoCommands stays at ePbcMotorCommandStop.
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.
11/9/21: mrb Per Design Board review, this requirement is NOT necessary. (ML) | [Issue] of PBC_040 - SIL Test - PowerLatchRequest = ePbcPowerLatchNotRequested too early Preconditions: Init with Fully released actuators.
Action:Apply Release under several condition.
Expected Behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested two cycles after last PbcOut.MotorComamd = ePbcMotorCommandNone
Actual behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested after last Pbcout.Actuatorstae = ePbcActuatorStateParkApplied ORePbcActuatorStateReleased
Further Information/Requirements: This can lead to a lock of software. In the past we made the experience that the Host system calls PBC.Cyclic as long as PbcOut.EcuPowerLatchRequest = ePbcPowerLatchRequested and if this signal depends on the actuatorstate it can happen that the PbcMotoCommands stays at ePbcMotorCommandStop.
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.
11/9/21: mrb Per Design Board review, this requirement is NOT necessary. (ML) |
|
[Daimler_MMA_IBC] VX1000 connection setting in A2l shall be corrected When trying o connect CANApe with generated
DA31_P05_M10_S02_VT2_200_010_000_RTP.A2L, following error is occured.
Please analys and implment necessary Changes in A2l [26.08.2021, ScafesA]--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The issue appear for the A2L generated in the SW version X200. In the X200 it was a issue and the information in the A2Ls have been incomplete and wrong and could cause errors with the VX1000 connection.
That Issue is confirmed that have been solved starting with SW version X250 with CR 5528764.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):Alexandru Scafes
Proposal of next steps (incl. effort/h and verification): Retest if the VX 1000 connection is corrected and if the errors is still present on SW version X250 or newer.
-------------------------------------------------------------------------------- | [Daimler_MMA_IBC] VX1000 connection setting in A2l shall be corrected When trying o connect CANApe with generated
DA31_P05_M10_S02_VT2_200_010_000_RTP.A2L, following error is occured.
Please analys and implment necessary Changes in A2l [26.08.2021, ScafesA]--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The issue appear for the A2L generated in the SW version X200. In the X200 it was a issue and the information in the A2Ls have been incomplete and wrong and could cause errors with the VX1000 connection.
That Issue is confirmed that have been solved starting with SW version X250 with CR 5528764.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):Alexandru Scafes
Proposal of next steps (incl. effort/h and verification): Retest if the VX 1000 connection is corrected and if the errors is still present on SW version X250 or newer.
-------------------------------------------------------------------------------- |
|
[VW KPM] [SV][BL][CAN] F1AB nach CheckMemory [Error Description]: VW80126.Gutfall (80126/VW80126.Gutfall):
FLASH_TEST_Gutfall
Kommentar Prüfer:
Es hat sich trotz CheckMemory keiner der Software Block Versionen aktualisiert.
[A: 80126-A119]
[A: 80126-A694]
Fehler-Beschreibung DANTE:
00000 (DIAG): Diagnose - RequestPDU (3): 22 F1 AB
Response (39): 62 F1 AB 58 33 32 35 58 33 32 33 41 30 30 32 44 45 4D 4F 49 58 30 35 41 30 30 36 41 30 30 31 42 30 30 31 42 30 30 31
00000 (TEST): Block 1 Typ: Writable [DATA]. Die Software Block Version hat sich vor dem CheckMemory aktualisiert. --> n.i.O.
00000 (TEST): Typ: Writable [DATA]. Es hat sich trotz CheckMemory keiner der Software Block Versionen aktualisiert oder es wurde bereits vor dem CheckMemory gemacht. --> n.i.O.
zugehörige Dateien:
Gutfall_2021-06-21_15-16-27_CAN_Diagnose.asc
[Fault Type]: 0
[Creator Contact Person]: Koch, Sven
[Creator Email]: extern.nils.krueger@volkswagen.de
[Creator Phone]:
*********************
Developer comment:
In SW Module apnv.c - ApplFblNvWriteBlockStates the invalidation of the block is not taking place. Needs to be corrected. Title: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory - Block Invalidation not Implemented
Description:
· Add NVRAM Block state write to invalidation of logical block
Proposed Tests:
· Check if block is invalid after erasing
Estimated design effort/h: 1
Estimated implementation effort/h: 1
Estimated unit testing effort/h: 1
Total effort/h: 3
[Optional] Planned completion date: | [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory [Error Description]: VW80126.Gutfall (80126/VW80126.Gutfall):
FLASH_TEST_Gutfall
Kommentar Prüfer:
Es hat sich trotz CheckMemory keiner der Software Block Versionen aktualisiert.
[A: 80126-A119]
[A: 80126-A694]
Fehler-Beschreibung DANTE:
00000 (DIAG): Diagnose - RequestPDU (3): 22 F1 AB
Response (39): 62 F1 AB 58 33 32 35 58 33 32 33 41 30 30 32 44 45 4D 4F 49 58 30 35 41 30 30 36 41 30 30 31 42 30 30 31 42 30 30 31
00000 (TEST): Block 1 Typ: Writable [DATA]. Die Software Block Version hat sich vor dem CheckMemory aktualisiert. --> n.i.O.
00000 (TEST): Typ: Writable [DATA]. Es hat sich trotz CheckMemory keiner der Software Block Versionen aktualisiert oder es wurde bereits vor dem CheckMemory gemacht. --> n.i.O.
zugehörige Dateien:
Gutfall_2021-06-21_15-16-27_CAN_Diagnose.asc
[Fault Type]: 0
[Creator Contact Person]: Koch, Sven
[Creator Email]: extern.nils.krueger@volkswagen.de
[Creator Phone]:
*********************
Developer comment:
In SW Module apnv.c - ApplFblNvWriteBlockStates the invalidation of the block is not taking place. Needs to be corrected. Title: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory - Block Invalidation not Implemented
Description:
· Add NVRAM Block state write to invalidation of logical block
Proposed Tests:
· Check if block is invalid after erasing
Estimated design effort/h: 1
Estimated implementation effort/h: 1
Estimated unit testing effort/h: 1
Total effort/h: 3
[Optional] Planned completion date: |
|
[VW KPM] [SV][PMode][CAN] PMode Parameter FF FF FF Perform an analysis for the issue below and suggest the next steps.
---------------------------------------------------------------------------------------------------------------------------
[Error Description]: Kontaktdaten:
E-Mail: VWAG R: WOB, EESN Sys-VQ
Beanstandung vom Sys-VQ-Prüfplatz
PMode.00.01.0.040.010 (PMode/PMode_ab_V8.1/physikalisch):
Aktivierung aller Produktionsmodes in erlaubter Session
Kommentar Prüfer:
Der P-Mode wird durch die Parameter 0xFF FF FF nicht aktiviert. Gemäß der Spezifikation muss der P-Mode aktiviert werden, da mit Parameter 0xFF FF FF alle Bits gesetzt sind.
[A: Q-LAH_PMode-9]
Fehler-Beschreibung DANTE:
00000 (DIAG): Diagnose - RequestPDU (3): 22 04 FE
Response (6): 62 04 FE 00 00 00
00000 (TEST): Der Identifier 04 FE wurde mit 0x62 04 FE 00 00 00 beantwortet.
Erwartet: != 00 00 00. --> n.i.O.
zugehörige Dateien:
TC_PMode_00_01_0_040_010_2021-06-21_15-04-28_CAN_Diagnose.asc
[Fault Type]: 0
[Creator Contact Person]: Koch, Sven
[Creator Email]: extern.nils.krueger@volkswagen.de
[Creator Phone]: 05.08.2021 BoianD: This topic is related to Base Software (Diag / Chasinf). OBD / SiSo has nothing to do with the triggering of the production mode. | [VW KPM] [SV][PMode][CAN] PMode Parameter FF FF FF Perform an analysis for the issue below and suggest the next steps.
---------------------------------------------------------------------------------------------------------------------------
[Error Description]: Kontaktdaten:
E-Mail: VWAG R: WOB, EESN Sys-VQ
Beanstandung vom Sys-VQ-Prüfplatz
PMode.00.01.0.040.010 (PMode/PMode_ab_V8.1/physikalisch):
Aktivierung aller Produktionsmodes in erlaubter Session
Kommentar Prüfer:
Der P-Mode wird durch die Parameter 0xFF FF FF nicht aktiviert. Gemäß der Spezifikation muss der P-Mode aktiviert werden, da mit Parameter 0xFF FF FF alle Bits gesetzt sind.
[A: Q-LAH_PMode-9]
Fehler-Beschreibung DANTE:
00000 (DIAG): Diagnose - RequestPDU (3): 22 04 FE
Response (6): 62 04 FE 00 00 00
00000 (TEST): Der Identifier 04 FE wurde mit 0x62 04 FE 00 00 00 beantwortet.
Erwartet: != 00 00 00. --> n.i.O.
zugehörige Dateien:
TC_PMode_00_01_0_040_010_2021-06-21_15-04-28_CAN_Diagnose.asc
[Fault Type]: 0
[Creator Contact Person]: Koch, Sven
[Creator Email]: extern.nils.krueger@volkswagen.de
[Creator Phone]: 05.08.2021 BoianD: This topic is related to Base Software (Diag / Chasinf). OBD / SiSo has nothing to do with the triggering of the production mode. |
|
[Defect]: [Diag] ESP178: Session Handling-OTX - Check reprogramming precondition Not Implemented This CR shall be used to implement the following diagnostic jobs:
1. Check Reprogramming Preconditions - StartRoutine: $31 01 02 03 zz
2. PreCheckProgrammingDependencies - StartRoutine: $31 01 02 07 zz
Information:
- The behavior of the routines is specified in the CDD but it must be checked whether further relevant customer requirements are specified in other specifications + DOORS modules.
- The CR shall cover SWE1, SWE2, SWE3 and SWE4.
- The CR has not be derived from BROP and/or DCRP but has been requested by the customer to be implemented for B1.1 (= X0150). Please, refer to the attached Excel Sheet "MMA_Diag_EffortEstimation_basedOn_v2.5_PlanningStatus_2021-04-08.xlsx" that is exchanged with the customer.
To Diag CCB:
- Please, add owner from Diag team.
- Please, add analysers from Diag team and SwAD team. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
19.05.2021 WeyandC:
Routine 0x0203 "Check Reprogramming Preconditions" is not specified in DOORS module "EBS_Diagnostic_Requirements_Specification". But the routines is specified by the CDD and by specification "DDS R01-01".
It is no longer requested by the customer that routine 0x0207 "PreCheckProgrammingDependencies" is supported by the application. This is why follow-up ALM_Change Request 5198683 has been or will be rejected.
Purpose of the CR:
1. Implement sub function $01 "StartRoutine" for routine 0x0203 "Check Reprogramming Preconditions":
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified and have been discussed with the customer:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future.
Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
2. As this is the first routine that is implemented for MMA, the CR must also be used to adapt the Diag framework to support routines under the project-specific conditions.
- Adaptations are required to support sub function $01 "StartRoutine" for service $31 "RoutineControl" with additional response bytes.
- Therefore, the generic start routine handling shall be adapted.
- The following SW pool components are affected: DiagArAdapter, DiagTestMgmtUnit
DIAG part:
1. Adapt SWC Diag
- Add service port for the new routine to SWC Diag and configure direction to server:
- Add runnable for the new routine.
=> Export updated Diag_AUTOSAR_Diag.arxml.
2. implementation of routine 0x0203 "Check Reprogramming Preconditions":
=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469
3. Diag framework adaptations:
=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the new routine 0x0203 "Check Reprogramming Preconditions"
- Map the new runnable to OS task Task_DiagEvents_D_C0_1. The slot is not relevant.
=> Generate RTE and OS.
NOTE:
1. SWC-Diag will call the following Autosar interfaces:
- (void)Rte_Read_R_BrakeActive_BrakeControlArbitratorActive(&brake_ctrl_active);
- (void)Rte_Read_R_ArbDriveTorque_DriveControlArbitratorActive(&drive_ctrl_active);
The ports are still connected from Geely / VW (= baseline for the MMA project). No actions are required.
The Autosar interfaces can be used from SwAD / Autosar point of view. Please, refer to the attached email "AW_ ALM_Change Request 5136349_ _MMA__X0150__Diag_ Implement _Programming Check_ routines.msg" for details.
2. Diag Design:
- It was decided for this routine that Dcm configuration is not manually adapted in DaVinci Configurator. The multiple in and out parameters are NOT replaced with a single in- and a single out-parameter. Hence, the DiagArAdapter routine runnable must copy data from the multiple in-parameters to the single generic Diag in-parameter and vice versa from the single Diag generic out-parameter to the multiple out-parameters.
- It was also decided that stack variables (= function variables) will be used as the additional stack consumption is negligible.
- For the future, it will be check whether the Dcm configuration will be manually adapted in DaVinci Configurator for new routines or whether shared Diag RAM variables shall be used to copy data between parameters defined by Autosar and generic Diag parameters.
=> Both decision will not affect the implementation of routine 0x0203 that is provided with this CR.
--------------------------------------------------------------------------------
Risk (low/medium/high):medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeyandC, SwAD part confirmed by C. Klukowski, Autosar task proposal confirmed by S. Basavaraju via Teams
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK 1/5
------------------------------------------------------
Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for routine 0x0203
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the new routine: 0x0203 "Check Reprogramming Preconditions"
- Map the new runnable for the routine to OS task Task_DiagEvents_D_C0_1. The slot is not relevant.
=> Generate RTE, and OS.
Owner: Hemanth Ambarukhana
Reviewer: Sireesha Basavaraju, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date: 26.05.2021 (set by task owner)
------------------------------------------------------
TASK 2/5
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
The following DIDs routine be implemented with this CR:
Routine 0x0203 "Check Reprogramming Preconditions" with sub function $01 "StartRoutine" is specified by the CDD and by specification "DDS R01-01".
Functionality:
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified by now or require clarification:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future. Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
Refer to the attached emails for further details.
Please, use this CR to define SW requirements for this routine.
Owner: J. Hornung
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 26.05.2021
------------------------------------------------------
TASK 3/5
------------------------------------------------------
Title: [MMA][Diag][SWE2][X0200] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement routine 0x0203 "Check Reprogramming Preconditions".
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: A. Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 28.05.2021
------------------------------------------------------
TASK 4/5
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Implement routine 0x0203 "Check Reprogramming Preconditions" and adapt RoutineControl framework
Description:
Purpose of the task:
1. Implement sub function $01 "StartRoutine" for routine 0x0203 "Check Reprogramming Preconditions":
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified by now or require clarification:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future.
Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
2. As this is the first routine that is implemented for MMA, the task must also be used to adapt the Diag framework to support routines under the project-specific conditions.
- Adaptations are required to support sub function $01 "StartRoutine" for service $31 "RoutineControl" with additional response bytes.
- Therefore, the generic start routine handling shall be adapted.
- The following SW pool components are affected: DiagArAdapter, DiagTestMgmtUnit
General:
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
Details:
1. Adapt SWC Diag:
- Add service port for the new routine to SWC Diag and configure direction to server:
- Add runnable for the new routine.
=> Export updated Diag_AUTOSAR_Diag.arxml
2. Framework adaptations:
DiagArAdapter:
- Adapt the interface GenericStartRoutineInterface:
- new parameter list: const U16 test_id, const U8 *input_parameters, U8 *const output_parameters, const U8 param_length, U16 * const out_param_length, Dcm_NegativeResponseCodeType *ErrorCode
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
- Adapt the interface GenericStopRoutineInterface
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
- Adapt the interface GenericASyncShortTermAdjustmentInterface
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
TestGroup:
- Adapt the interface CommandTest:
- new parameter list: const U16 comms_id, const U8 test_type, const BOOLEAN command, const U8* const parameters, U8* const output_data, const U16 length, U16* const out_length
- add a new block after the "Execute Command" block and before the "Update Group Status block":
- check if "status" is TST_STATUS_OK and "out_length" is not NULL; if so call interface "ExecuteGetCommandDataInterface" and store the return value via "out_length" pointer
- Add new type definition in the global header file for function pointer to retrieve the response parameters for start routine service request: typedef U16 (*GET_COMMAND_TEST_DATA_TYPE)(U8* results)
TestSpecification:
- Add new function U16 ExecuteGetCommandDataInterface(const U32 test_id, U8 results_buffer[]) with subsystem scope
- the function shall check whether "GetCommandTestDataInterface" is not NULL for the given "test_id"
- if so, it shall return the length returned by the respective "GetCommandTestDataInterface" interface.
- otherwise, it shall return 0 as length.
- Adapt definition of data type TEST_SPEC_DATA_TYPE:
- add new paramter "GET_COMMAND_TEST_DATA_TYPE GetCommandTestDataInterface" behind the "Get_Result_Data_Inteface" parameter
InputOutputControlById.c:
- non functional adaptation to make the SW compile:
- adapt the calls of function "CommandTest" in function "IoControlByIdentifier" to make the SW compile
- pass NULL for the new parameters of "CommandTest"
3. Implementation of routine 0x0203:
DiagArAdapter_cfg:
- Implement the new runnable "RoutineServices_Check_Reprogramming_Preconditions_Start":
- define stack variables:
- for 2nd parameter of CommandTest: const U8 start_routine_in_signals = 0u
- for 3rd parameter of CommandTest (=> it is expected that a size of 8 bytes will be sufficient => currently a size of 2 bytes would be ok): U8 start_routine_out_signals[DIAG_PRGR_PRECND_MAX_DYN_LENGTH]
- for 5th parameter of CommandTest: U16 data_length_out = 0u
- OpStatus == DCM_initial:
- call CommandTest with the listed parameters and with 1st parameter = PROG_PRECOND_CHECK_TEST_ID, with 4th parameter = 0 and with ErrorCode as 6th parameter
- if returned data_length_out is less than minimal response length (= 2) or greater than minimal response legnth + size of array "start_routine_out_signals":
- call UpdateTestManagementActive(FALSE)
- return E_NOT_OK with ErrorCode DCM_E_GENERALREJECT
- otherwise:
- copy data from "start_routine_out_signals" to actual out parameters "routineInfo_Out", "Number_of_Unfulfilled_Preconditions_Out", "List_of_Preconditions_Out" and set "DataLength" to the correct value
- return E_OK
- OpStatus == DCM_CANCEL:
- call UpdateTestManagementActive(FALSE)
- return E_OK
- OpStatus has another value:
- return E_NOT_OK with ErrorCode DCM_E_GENERALREJECT
TestSpecification_Cfg:
- Adapt ROM table Test_Spec_Data: replace dummy entry with entry for routine 0x0203:
{
&CommandChkPrgrPrecnd,
&UpdateChkPrgrPrecnd,
NULL,
NULL,
&ReportChkPrgrPrecndCommandData,
PROG_PRECOND_CHECK_TEST_ID,
ROUTINE_BY_ID_TEST,
EXCLUSIVE_TEST_GROUP,
SECURITY_ACCESS_NOT_REQUIRED,
PARAM_LENGTH_ZERO,
(U8)IOC_NO_CHECK_REQUIRED
}
RoutineControl_Cfg:
1. Implement Command_Interface with subsystem scope: CommandChkPrgrPrecnd
- Check all programming preconditions by calling the following functions and store the check results in LOCAL variable:
- CheckNonDefaultSessionSpeed()
=> returns FALSE if speed is to high and programming session cannot be entered
- (void)Rte_Read_R_BrakeActive_BrakeControlArbitratorActive(&BOOLEAN x) and (void)Rte_Read_R_ArbDriveTorque_DriveControlArbitratorActive(&BOOLEAN y)
=> at least one function returns TRUE if a control intervention is active and programming session cannot be entered
- IsEcuResetAllowedByPb()
=> returns FALSE if EPB actuation is active and programming session cannot be entered
2. Implement Update_Interface with subsystem scope: UpdateChkPrgrPrecnd
- just return FALSE
3. Implement GetCommandTestDataInterface with subsystem scope: ReportChkPrgrPrecndCommandData
- set first response byte (DIAG_ROUTINE_STATUS_BYTE_INDEX) to 0x00 (DIAG_DAI_RID_SUCCESS_COMPLETED)
- set second byte to the number of Programming PreConditions that are not fulfilled and prevent the system from entering the programming session => note: the number must be calculated in this function
- if speed condition is unfulfilled, set next free response byte to 0x05 (DIAG_VEHICLE_SPEED_COND)
- if control intervention or EPB actuation is in progress, set next free response byte to 0x06 (DIAG_CONTROLLER_ACTIVE_COND)
- return the number of additional response bytes (= all bytes without pos. response byte + subfunction byte and RID bytes)
Note:
Please, find an untested(!) implementation proposal "Untested_Diag_ImplementatioProposal.zipx" attached to the task.
Note that this implementation might not work correctly, and may cause QAC and polyspace warnings that needs to be fixed or handled.
The proposal is based on SW checkpoint 1.3.3.142 with DiagArAdapter checkpoint 1.9.1.16 and DiagTestMgmtUnit checkpoint 1.8.2.7.
Owner: Ashwini Digajerla
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 18h
[Optional] Planned completion date: 25.05.2021 (set by task owner)
------------------------------------------------------
TASK 5/5
------------------------------------------------------
Title: [MMA][X0200][SWAD] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
Please import and map requirements for stub implementation of the following routine:
0x0203 "Check Reprogramming Preconditions"
Map new runnable to OS task Task_DiagEvents_D_C0_1.
Owner: C. Klukowski
Reviewer: C. Bayer, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8h
[Optional] Planned completion date: 27.05.2021 (set by task owner)
------------------------------------------------------ | [Defect]: [Diag] ESP178: Session Handling-OTX - Check reprogramming precondition Not Implemented This CR shall be used to implement the following diagnostic jobs:
1. Check Reprogramming Preconditions - StartRoutine: $31 01 02 03 zz
2. PreCheckProgrammingDependencies - StartRoutine: $31 01 02 07 zz
Information:
- The behavior of the routines is specified in the CDD but it must be checked whether further relevant customer requirements are specified in other specifications + DOORS modules.
- The CR shall cover SWE1, SWE2, SWE3 and SWE4.
- The CR has not be derived from BROP and/or DCRP but has been requested by the customer to be implemented for B1.1 (= X0150). Please, refer to the attached Excel Sheet "MMA_Diag_EffortEstimation_basedOn_v2.5_PlanningStatus_2021-04-08.xlsx" that is exchanged with the customer.
To Diag CCB:
- Please, add owner from Diag team.
- Please, add analysers from Diag team and SwAD team. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
19.05.2021 WeyandC:
Routine 0x0203 "Check Reprogramming Preconditions" is not specified in DOORS module "EBS_Diagnostic_Requirements_Specification". But the routines is specified by the CDD and by specification "DDS R01-01".
It is no longer requested by the customer that routine 0x0207 "PreCheckProgrammingDependencies" is supported by the application. This is why follow-up ALM_Change Request 5198683 has been or will be rejected.
Purpose of the CR:
1. Implement sub function $01 "StartRoutine" for routine 0x0203 "Check Reprogramming Preconditions":
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified and have been discussed with the customer:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future.
Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
2. As this is the first routine that is implemented for MMA, the CR must also be used to adapt the Diag framework to support routines under the project-specific conditions.
- Adaptations are required to support sub function $01 "StartRoutine" for service $31 "RoutineControl" with additional response bytes.
- Therefore, the generic start routine handling shall be adapted.
- The following SW pool components are affected: DiagArAdapter, DiagTestMgmtUnit
DIAG part:
1. Adapt SWC Diag
- Add service port for the new routine to SWC Diag and configure direction to server:
- Add runnable for the new routine.
=> Export updated Diag_AUTOSAR_Diag.arxml.
2. implementation of routine 0x0203 "Check Reprogramming Preconditions":
=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469
3. Diag framework adaptations:
=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the new routine 0x0203 "Check Reprogramming Preconditions"
- Map the new runnable to OS task Task_DiagEvents_D_C0_1. The slot is not relevant.
=> Generate RTE and OS.
NOTE:
1. SWC-Diag will call the following Autosar interfaces:
- (void)Rte_Read_R_BrakeActive_BrakeControlArbitratorActive(&brake_ctrl_active);
- (void)Rte_Read_R_ArbDriveTorque_DriveControlArbitratorActive(&drive_ctrl_active);
The ports are still connected from Geely / VW (= baseline for the MMA project). No actions are required.
The Autosar interfaces can be used from SwAD / Autosar point of view. Please, refer to the attached email "AW_ ALM_Change Request 5136349_ _MMA__X0150__Diag_ Implement _Programming Check_ routines.msg" for details.
2. Diag Design:
- It was decided for this routine that Dcm configuration is not manually adapted in DaVinci Configurator. The multiple in and out parameters are NOT replaced with a single in- and a single out-parameter. Hence, the DiagArAdapter routine runnable must copy data from the multiple in-parameters to the single generic Diag in-parameter and vice versa from the single Diag generic out-parameter to the multiple out-parameters.
- It was also decided that stack variables (= function variables) will be used as the additional stack consumption is negligible.
- For the future, it will be check whether the Dcm configuration will be manually adapted in DaVinci Configurator for new routines or whether shared Diag RAM variables shall be used to copy data between parameters defined by Autosar and generic Diag parameters.
=> Both decision will not affect the implementation of routine 0x0203 that is provided with this CR.
--------------------------------------------------------------------------------
Risk (low/medium/high):medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeyandC, SwAD part confirmed by C. Klukowski, Autosar task proposal confirmed by S. Basavaraju via Teams
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK 1/5
------------------------------------------------------
Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for routine 0x0203
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the new routine: 0x0203 "Check Reprogramming Preconditions"
- Map the new runnable for the routine to OS task Task_DiagEvents_D_C0_1. The slot is not relevant.
=> Generate RTE, and OS.
Owner: Hemanth Ambarukhana
Reviewer: Sireesha Basavaraju, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date: 26.05.2021 (set by task owner)
------------------------------------------------------
TASK 2/5
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
The following DIDs routine be implemented with this CR:
Routine 0x0203 "Check Reprogramming Preconditions" with sub function $01 "StartRoutine" is specified by the CDD and by specification "DDS R01-01".
Functionality:
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified by now or require clarification:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future. Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
Refer to the attached emails for further details.
Please, use this CR to define SW requirements for this routine.
Owner: J. Hornung
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 26.05.2021
------------------------------------------------------
TASK 3/5
------------------------------------------------------
Title: [MMA][Diag][SWE2][X0200] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement routine 0x0203 "Check Reprogramming Preconditions".
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: A. Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 28.05.2021
------------------------------------------------------
TASK 4/5
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Implement routine 0x0203 "Check Reprogramming Preconditions" and adapt RoutineControl framework
Description:
Purpose of the task:
1. Implement sub function $01 "StartRoutine" for routine 0x0203 "Check Reprogramming Preconditions":
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified by now or require clarification:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future.
Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
2. As this is the first routine that is implemented for MMA, the task must also be used to adapt the Diag framework to support routines under the project-specific conditions.
- Adaptations are required to support sub function $01 "StartRoutine" for service $31 "RoutineControl" with additional response bytes.
- Therefore, the generic start routine handling shall be adapted.
- The following SW pool components are affected: DiagArAdapter, DiagTestMgmtUnit
General:
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
Details:
1. Adapt SWC Diag:
- Add service port for the new routine to SWC Diag and configure direction to server:
- Add runnable for the new routine.
=> Export updated Diag_AUTOSAR_Diag.arxml
2. Framework adaptations:
DiagArAdapter:
- Adapt the interface GenericStartRoutineInterface:
- new parameter list: const U16 test_id, const U8 *input_parameters, U8 *const output_parameters, const U8 param_length, U16 * const out_param_length, Dcm_NegativeResponseCodeType *ErrorCode
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
- Adapt the interface GenericStopRoutineInterface
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
- Adapt the interface GenericASyncShortTermAdjustmentInterface
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
TestGroup:
- Adapt the interface CommandTest:
- new parameter list: const U16 comms_id, const U8 test_type, const BOOLEAN command, const U8* const parameters, U8* const output_data, const U16 length, U16* const out_length
- add a new block after the "Execute Command" block and before the "Update Group Status block":
- check if "status" is TST_STATUS_OK and "out_length" is not NULL; if so call interface "ExecuteGetCommandDataInterface" and store the return value via "out_length" pointer
- Add new type definition in the global header file for function pointer to retrieve the response parameters for start routine service request: typedef U16 (*GET_COMMAND_TEST_DATA_TYPE)(U8* results)
TestSpecification:
- Add new function U16 ExecuteGetCommandDataInterface(const U32 test_id, U8 results_buffer[]) with subsystem scope
- the function shall check whether "GetCommandTestDataInterface" is not NULL for the given "test_id"
- if so, it shall return the length returned by the respective "GetCommandTestDataInterface" interface.
- otherwise, it shall return 0 as length.
- Adapt definition of data type TEST_SPEC_DATA_TYPE:
- add new paramter "GET_COMMAND_TEST_DATA_TYPE GetCommandTestDataInterface" behind the "Get_Result_Data_Inteface" parameter
InputOutputControlById.c:
- non functional adaptation to make the SW compile:
- adapt the calls of function "CommandTest" in function "IoControlByIdentifier" to make the SW compile
- pass NULL for the new parameters of "CommandTest"
3. Implementation of routine 0x0203:
DiagArAdapter_cfg:
- Implement the new runnable "RoutineServices_Check_Reprogramming_Preconditions_Start":
- define stack variables:
- for 2nd parameter of CommandTest: const U8 start_routine_in_signals = 0u
- for 3rd parameter of CommandTest (=> it is expected that a size of 8 bytes will be sufficient => currently a size of 2 bytes would be ok): U8 start_routine_out_signals[DIAG_PRGR_PRECND_MAX_DYN_LENGTH]
- for 5th parameter of CommandTest: U16 data_length_out = 0u
- OpStatus == DCM_initial:
- call CommandTest with the listed parameters and with 1st parameter = PROG_PRECOND_CHECK_TEST_ID, with 4th parameter = 0 and with ErrorCode as 6th parameter
- if returned data_length_out is less than minimal response length (= 2) or greater than minimal response legnth + size of array "start_routine_out_signals":
- call UpdateTestManagementActive(FALSE)
- return E_NOT_OK with ErrorCode DCM_E_GENERALREJECT
- otherwise:
- copy data from "start_routine_out_signals" to actual out parameters "routineInfo_Out", "Number_of_Unfulfilled_Preconditions_Out", "List_of_Preconditions_Out" and set "DataLength" to the correct value
- return E_OK
- OpStatus == DCM_CANCEL:
- call UpdateTestManagementActive(FALSE)
- return E_OK
- OpStatus has another value:
- return E_NOT_OK with ErrorCode DCM_E_GENERALREJECT
TestSpecification_Cfg:
- Adapt ROM table Test_Spec_Data: replace dummy entry with entry for routine 0x0203:
{
&CommandChkPrgrPrecnd,
&UpdateChkPrgrPrecnd,
NULL,
NULL,
&ReportChkPrgrPrecndCommandData,
PROG_PRECOND_CHECK_TEST_ID,
ROUTINE_BY_ID_TEST,
EXCLUSIVE_TEST_GROUP,
SECURITY_ACCESS_NOT_REQUIRED,
PARAM_LENGTH_ZERO,
(U8)IOC_NO_CHECK_REQUIRED
}
RoutineControl_Cfg:
1. Implement Command_Interface with subsystem scope: CommandChkPrgrPrecnd
- Check all programming preconditions by calling the following functions and store the check results in LOCAL variable:
- CheckNonDefaultSessionSpeed()
=> returns FALSE if speed is to high and programming session cannot be entered
- (void)Rte_Read_R_BrakeActive_BrakeControlArbitratorActive(&BOOLEAN x) and (void)Rte_Read_R_ArbDriveTorque_DriveControlArbitratorActive(&BOOLEAN y)
=> at least one function returns TRUE if a control intervention is active and programming session cannot be entered
- IsEcuResetAllowedByPb()
=> returns FALSE if EPB actuation is active and programming session cannot be entered
2. Implement Update_Interface with subsystem scope: UpdateChkPrgrPrecnd
- just return FALSE
3. Implement GetCommandTestDataInterface with subsystem scope: ReportChkPrgrPrecndCommandData
- set first response byte (DIAG_ROUTINE_STATUS_BYTE_INDEX) to 0x00 (DIAG_DAI_RID_SUCCESS_COMPLETED)
- set second byte to the number of Programming PreConditions that are not fulfilled and prevent the system from entering the programming session => note: the number must be calculated in this function
- if speed condition is unfulfilled, set next free response byte to 0x05 (DIAG_VEHICLE_SPEED_COND)
- if control intervention or EPB actuation is in progress, set next free response byte to 0x06 (DIAG_CONTROLLER_ACTIVE_COND)
- return the number of additional response bytes (= all bytes without pos. response byte + subfunction byte and RID bytes)
Note:
Please, find an untested(!) implementation proposal "Untested_Diag_ImplementatioProposal.zipx" attached to the task.
Note that this implementation might not work correctly, and may cause QAC and polyspace warnings that needs to be fixed or handled.
The proposal is based on SW checkpoint 1.3.3.142 with DiagArAdapter checkpoint 1.9.1.16 and DiagTestMgmtUnit checkpoint 1.8.2.7.
Owner: Ashwini Digajerla
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 18h
[Optional] Planned completion date: 25.05.2021 (set by task owner)
------------------------------------------------------
TASK 5/5
------------------------------------------------------
Title: [MMA][X0200][SWAD] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
Please import and map requirements for stub implementation of the following routine:
0x0203 "Check Reprogramming Preconditions"
Map new runnable to OS task Task_DiagEvents_D_C0_1.
Owner: C. Klukowski
Reviewer: C. Bayer, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8h
[Optional] Planned completion date: 27.05.2021 (set by task owner)
------------------------------------------------------ |
|
[Defect]: [Diag] ESP178: ID-Data services not implemented Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B1
As part of 'Work step: Perform Preliminary Impact Analysis' in stages https://cdc-stages.emea.zf-world.com:8443/pkit/go/pelement.do?id=469319&type=Subprocess following teams are identified, which are impacted by the customer requirements.
Diag, Comms, Security, Memo
Please assign as 'Owners'; Diag
Please assign as 'Analysers'; Diag, Memo, SwAD.
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Doing by SwD:
(SWE1)Please derive requirements from the 'Source' (for 'Source' refer below) and map the behavior to the derived requirements
(SWE2)Please update SwAD model according to derived requirements.
(SWE3)Please develop a sw design (RPY model) and implement the behaviors according to the derived requirements.
(SWE4)Please develop sw unit tests according to the derived requirements.
Doing by SwAD:
(SwAD)Import the derived requirements into SwAD model.
Input Work Products (Link or other reference): Source (customer requirements): refer attached excel sheet 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' ,please filter column 'N' 'Diag Cluster ID' for the value of 16
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
The attachment 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' is an export of the customer DOORS module 'EBS Diagnostic Requirements Specification', current 29.1, which contains additional columns:
'F' (Provider of information),
'G' (Behavior),
'H' (Involved team).
Description of the additional columns based on an example:
'C': DIAG_2119;
'E': 'The service Read DTC Information (SID $19) shall be supported, with all in this requirement specification defined "DTC Information'
'F': This column contains the teams or the behavior which support the implementation of this requirement by the behavior in column 'G', e.g. to provide information/interface to fulfill the requirement. In this case Fm has to provide an interface.
'G': Behavior: This column contains the behavior(s) which have to implement the customer requirement. In this case the customer requirement shall be implemented by the in column 'G' mentioned behavior(s).
'H': This column contains the teams which are impacted by this requirement, team might be in supporting role (refer column 'F') and other in 'responsible role' to implement the behavior (refer column'H').
--------------------------------------------------------------------------------
Output Work Products:
Refer stages
--------------------------------------------------------------------------------
Acceptance Criteria:
--------------------------------------------------------------------------------
The requirements are derived.
SwAD model updated according to derived requirements.
Sw design (RPY model) and implementation of the behaviors according to the derived requirements is done.
sw unit tests according to the derived requirements are developed.
Derived requirements are mapped to behaviors and imported to Domain Architecture.
In case of gaps/incompleteness/incorrectness which shall not be resolved with particular Task (where the review has failed), only 'ONE' follow up CR shall be created which covers all findings of all Tasks of that CR (purpose: reduction of CRs).
This must be agreed with the SwPM and the CR must be planned by SwPM.
This CR must be spawned by the parent CR of the failed Task.
Responsibility to provide the findings which shall be solved with another CR into the another CR belongs to the Owner of this Task. The reviewer should complete/close the Task only if the findings are documented in the follow up CR.
Example how the follow-up CR might look:
Summary: [FollowUp] <Summary_Of_CR_spawnedBy>
Description:
'This CR is a follow-up CR of <ID_of_CR_spawnedBy>.
With this CR the findings shall be resolved, which were identified during the review of the Task(s) attached to the CR <ID_of_CR_spawnedBy>.
It is agreed with SwPM to shift the correction of the findings to another build.
Task: <ID of Task with Findings>
Refer attachment 'ReviewFindingsOfTask_<ID of Task with Findings>'.' --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
22.04.2021
Ashwini Digajerla
Dig team:
As per cluster ID 16 below DIDs has to be implemented.
-Read ECU Name(c)
-Read Supported configuration mechanisms(0xF131)
-Read DID for Snapshot-Date: Vehicle Odometer in LowResolution(0x010A)
-Read DID for Snapshot-Date: Current Operating Time(0x0133)
Due to non availbility of the required interfaces for DID 0x010A and 0x0133 from Coms and FM subsytems ,seperate Spawn CR is created for implementing this 2 DIDs.
Req Reference:Cdd file from D:\Daimbler\VariantSB\DiagMain\Cfg\Model
Davini Configarator changes:
->Although all diagnostic jobs are already configured in the Dcm configuration, a Dcm configuration update will be required with this CR 4861342 .
This is because:
1. “Dsp Data Use Port” shall be changed to “USE_DATA_SYNCH_CLIENT_SERVER” As the callout will never return “pending”.
->Task mapping for the RTE calls shall be done.
Davini Developer changes:
->Create new runnables for 0xF101 and 0xF103 DIDs and generated DCM and RTE.
Diag Application changes:
Code Changes:
-> Implement Read functions in DiagArAdapter_Cfg.c file
->Add Read functions for 2 DIDs in the file \ReadDataByIdentifier_Cfg_Priv.h .
-> In ReadDataByIdentifier_Cfg.c file add the call back functions in lookup table and implement functions to read the data.
-> Add required macros to the corresponding ReadDataByIdentifier_Cfg.h. and ReadDataByIdentifier_Cfg_sub.h files.
->only ROM data will be read with the 2 DIDs
->Attached code changes.
-> No actions required by MeMo,FM and coms team for this CR.
26.04.2021 WeyandC: Ooi Siang Tan has been removed from the list of analysers as MeMo team is not involved in this CR. Please, refer to the attached email "AW_ _DCRP 46_1_ _IBC__SW-D_ SF 8_8 System Diagnostic Function -Read ID-Data_ Remaining jobs_ Cluster ID 16.msg".
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Ashwini Digajerla .
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE1/4][Diag] SF 8.8 System Diagnostic Function -- Read ID-Data: Remaining jobs, Cluster ID 16
Description:
(SWE1) Please, provide Sw requirements for the customer requirements that specify diagnostic service: 0xF104,0xF131
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
Owner: Joachim Hornung
Reviewer: Christian Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE2/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement diagnsotic service :0xF104,0xF131
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: Christian Weyand
Reviewer: Ahmed Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date: 30.04.2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE3/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
Implement Diag application part to support DIDs 0xF104 and 0xF131 .
The task shall be used:
1. to update the design model
2. to implement the requested functionality including QAC, polyspace and log file analysis
3. and to update / add VCast tests, execute them and link them to the design model.
Details for point 2:
The implementation in diagnostic application needs to be adapted with below new DIDs.
-Read ECU Name(0xF104)
-Read Supported configuration mechanisms(0xF131)
Davini Configarator changes:
->Although all diagnostic jobs are already configured in the Dcm configuration, a Dcm configuration update will be required with this CR 4861342 .
This is because:
1. “Dsp Data Use Port” shall be changed to “USE_DATA_SYNCH_CLIENT_SERVER” As the callout will never return “pending”.
->Task mapping for the RTE calls shall be done.
Davini Developer changes:
->Create new runnables for 0xF101 and 0xF103 DIDs and generated DCM and RTE.
Diag Application changes:
Code Changes:
-> Implement Read functions in DiagArAdapter_Cfg.c file
->Add Read functions for 2 DIDs in the file \ReadDataByIdentifier_Cfg_Priv.h .
-> In ReadDataByIdentifier_Cfg.c file add the call back functions in lookup table and implement functions to read the data.
-> Add required macros to the corresponding ReadDataByIdentifier_Cfg.h. and ReadDataByIdentifier_Cfg_sub.h files.
->only ROM data will be read with the 2 DIDs
->Attached code changes.
-> No actions required by MeMo,FM and coms team for this CR.
Owner: Irannavar Satish Pundalik EXT HDR Tata Elxsi
Reviewer: Ashwini Digajerla
Estimated design effort/h:6
Estimated implementation effort/h:6
Estimated unit testing effort/h:18
------------------------------------------------------
Total effort/h: 30h
[Optional] Planned completion date: 30.04.2021
------------------------------------------------------
Task SwAD:
------------------------------------------------------
Title:(SWE4/4)SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description: Please import and map requirements.
Owner:Caesar Klukowski
Reviewer: Christoph Bayer, Christian Weyand
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 4.5.2021
------------------------------------------------------
Task AUTOSAR:
------------------------------------------------------
Title:SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
->With new Arxml provided by Diag task ,create new service ports and runnables for 0xF101 and 0xF103 DIDs .
->Do task mapping for the new runnables in configarator . .
->Generated DCM and RTE and checkin the changes.
Owner: Sireesha Basavaraju
Reviewer: Hemanth Ambarukhana Krishna
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 30.4.2021
------------------------------------------------------ | [Defect]: [Diag] ESP178: ID-Data services not implemented Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B1
As part of 'Work step: Perform Preliminary Impact Analysis' in stages https://cdc-stages.emea.zf-world.com:8443/pkit/go/pelement.do?id=469319&type=Subprocess following teams are identified, which are impacted by the customer requirements.
Diag, Comms, Security, Memo
Please assign as 'Owners'; Diag
Please assign as 'Analysers'; Diag, Memo, SwAD.
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Doing by SwD:
(SWE1)Please derive requirements from the 'Source' (for 'Source' refer below) and map the behavior to the derived requirements
(SWE2)Please update SwAD model according to derived requirements.
(SWE3)Please develop a sw design (RPY model) and implement the behaviors according to the derived requirements.
(SWE4)Please develop sw unit tests according to the derived requirements.
Doing by SwAD:
(SwAD)Import the derived requirements into SwAD model.
Input Work Products (Link or other reference): Source (customer requirements): refer attached excel sheet 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' ,please filter column 'N' 'Diag Cluster ID' for the value of 16
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
The attachment 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' is an export of the customer DOORS module 'EBS Diagnostic Requirements Specification', current 29.1, which contains additional columns:
'F' (Provider of information),
'G' (Behavior),
'H' (Involved team).
Description of the additional columns based on an example:
'C': DIAG_2119;
'E': 'The service Read DTC Information (SID $19) shall be supported, with all in this requirement specification defined "DTC Information'
'F': This column contains the teams or the behavior which support the implementation of this requirement by the behavior in column 'G', e.g. to provide information/interface to fulfill the requirement. In this case Fm has to provide an interface.
'G': Behavior: This column contains the behavior(s) which have to implement the customer requirement. In this case the customer requirement shall be implemented by the in column 'G' mentioned behavior(s).
'H': This column contains the teams which are impacted by this requirement, team might be in supporting role (refer column 'F') and other in 'responsible role' to implement the behavior (refer column'H').
--------------------------------------------------------------------------------
Output Work Products:
Refer stages
--------------------------------------------------------------------------------
Acceptance Criteria:
--------------------------------------------------------------------------------
The requirements are derived.
SwAD model updated according to derived requirements.
Sw design (RPY model) and implementation of the behaviors according to the derived requirements is done.
sw unit tests according to the derived requirements are developed.
Derived requirements are mapped to behaviors and imported to Domain Architecture.
In case of gaps/incompleteness/incorrectness which shall not be resolved with particular Task (where the review has failed), only 'ONE' follow up CR shall be created which covers all findings of all Tasks of that CR (purpose: reduction of CRs).
This must be agreed with the SwPM and the CR must be planned by SwPM.
This CR must be spawned by the parent CR of the failed Task.
Responsibility to provide the findings which shall be solved with another CR into the another CR belongs to the Owner of this Task. The reviewer should complete/close the Task only if the findings are documented in the follow up CR.
Example how the follow-up CR might look:
Summary: [FollowUp] <Summary_Of_CR_spawnedBy>
Description:
'This CR is a follow-up CR of <ID_of_CR_spawnedBy>.
With this CR the findings shall be resolved, which were identified during the review of the Task(s) attached to the CR <ID_of_CR_spawnedBy>.
It is agreed with SwPM to shift the correction of the findings to another build.
Task: <ID of Task with Findings>
Refer attachment 'ReviewFindingsOfTask_<ID of Task with Findings>'.' --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
22.04.2021
Ashwini Digajerla
Dig team:
As per cluster ID 16 below DIDs has to be implemented.
-Read ECU Name(c)
-Read Supported configuration mechanisms(0xF131)
-Read DID for Snapshot-Date: Vehicle Odometer in LowResolution(0x010A)
-Read DID for Snapshot-Date: Current Operating Time(0x0133)
Due to non availbility of the required interfaces for DID 0x010A and 0x0133 from Coms and FM subsytems ,seperate Spawn CR is created for implementing this 2 DIDs.
Req Reference:Cdd file from D:\Daimbler\VariantSB\DiagMain\Cfg\Model
Davini Configarator changes:
->Although all diagnostic jobs are already configured in the Dcm configuration, a Dcm configuration update will be required with this CR 4861342 .
This is because:
1. “Dsp Data Use Port” shall be changed to “USE_DATA_SYNCH_CLIENT_SERVER” As the callout will never return “pending”.
->Task mapping for the RTE calls shall be done.
Davini Developer changes:
->Create new runnables for 0xF101 and 0xF103 DIDs and generated DCM and RTE.
Diag Application changes:
Code Changes:
-> Implement Read functions in DiagArAdapter_Cfg.c file
->Add Read functions for 2 DIDs in the file \ReadDataByIdentifier_Cfg_Priv.h .
-> In ReadDataByIdentifier_Cfg.c file add the call back functions in lookup table and implement functions to read the data.
-> Add required macros to the corresponding ReadDataByIdentifier_Cfg.h. and ReadDataByIdentifier_Cfg_sub.h files.
->only ROM data will be read with the 2 DIDs
->Attached code changes.
-> No actions required by MeMo,FM and coms team for this CR.
26.04.2021 WeyandC: Ooi Siang Tan has been removed from the list of analysers as MeMo team is not involved in this CR. Please, refer to the attached email "AW_ _DCRP 46_1_ _IBC__SW-D_ SF 8_8 System Diagnostic Function -Read ID-Data_ Remaining jobs_ Cluster ID 16.msg".
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Ashwini Digajerla .
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE1/4][Diag] SF 8.8 System Diagnostic Function -- Read ID-Data: Remaining jobs, Cluster ID 16
Description:
(SWE1) Please, provide Sw requirements for the customer requirements that specify diagnostic service: 0xF104,0xF131
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
Owner: Joachim Hornung
Reviewer: Christian Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE2/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement diagnsotic service :0xF104,0xF131
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: Christian Weyand
Reviewer: Ahmed Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date: 30.04.2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE3/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
Implement Diag application part to support DIDs 0xF104 and 0xF131 .
The task shall be used:
1. to update the design model
2. to implement the requested functionality including QAC, polyspace and log file analysis
3. and to update / add VCast tests, execute them and link them to the design model.
Details for point 2:
The implementation in diagnostic application needs to be adapted with below new DIDs.
-Read ECU Name(0xF104)
-Read Supported configuration mechanisms(0xF131)
Davini Configarator changes:
->Although all diagnostic jobs are already configured in the Dcm configuration, a Dcm configuration update will be required with this CR 4861342 .
This is because:
1. “Dsp Data Use Port” shall be changed to “USE_DATA_SYNCH_CLIENT_SERVER” As the callout will never return “pending”.
->Task mapping for the RTE calls shall be done.
Davini Developer changes:
->Create new runnables for 0xF101 and 0xF103 DIDs and generated DCM and RTE.
Diag Application changes:
Code Changes:
-> Implement Read functions in DiagArAdapter_Cfg.c file
->Add Read functions for 2 DIDs in the file \ReadDataByIdentifier_Cfg_Priv.h .
-> In ReadDataByIdentifier_Cfg.c file add the call back functions in lookup table and implement functions to read the data.
-> Add required macros to the corresponding ReadDataByIdentifier_Cfg.h. and ReadDataByIdentifier_Cfg_sub.h files.
->only ROM data will be read with the 2 DIDs
->Attached code changes.
-> No actions required by MeMo,FM and coms team for this CR.
Owner: Irannavar Satish Pundalik EXT HDR Tata Elxsi
Reviewer: Ashwini Digajerla
Estimated design effort/h:6
Estimated implementation effort/h:6
Estimated unit testing effort/h:18
------------------------------------------------------
Total effort/h: 30h
[Optional] Planned completion date: 30.04.2021
------------------------------------------------------
Task SwAD:
------------------------------------------------------
Title:(SWE4/4)SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description: Please import and map requirements.
Owner:Caesar Klukowski
Reviewer: Christoph Bayer, Christian Weyand
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 4.5.2021
------------------------------------------------------
Task AUTOSAR:
------------------------------------------------------
Title:SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
->With new Arxml provided by Diag task ,create new service ports and runnables for 0xF101 and 0xF103 DIDs .
->Do task mapping for the new runnables in configarator . .
->Generated DCM and RTE and checkin the changes.
Owner: Sireesha Basavaraju
Reviewer: Hemanth Ambarukhana Krishna
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 30.4.2021
------------------------------------------------------ |
|
[Defect]: [Diag] ESP178: ID-Data services not implemented Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read Version Data, Cluster ID 9
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B1
As part of 'Work step: Perform Preliminary Impact Analysis' in stages https://cdc-stages.emea.zf-world.com:8443/pkit/go/pelement.do?id=469319&type=Subprocess following teams are identified, which are impacted by the customer requirements.
Diag, Comms, Security, Memo
Please assign as 'Owners'; Diag
Please assign as 'Analysers'; Diag, Comms, Memo, SwAD.
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Doing by SwD:
(SWE1)Please derive requirements from the 'Source' (for 'Source' refer below) and map the behavior to the derived requirements
(SWE2)Please update SwAD model according to derived requirements.
(SWE3)Please develop a sw design (RPY model) and implement the behaviors according to the derived requirements.
(SWE4)Please develop sw unit tests according to the derived requirements.
Doing by SwAD:
(SwAD)Import the derived requirements into SwAD model.
Input Work Products (Link or other reference): Source (customer requirements): refer attached excel sheet 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' ,please filter column 'N' 'Diag Cluster ID' for the value of 9
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
The attachment 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' is an export of the customer DOORS module 'EBS Diagnostic Requirements Specification', current 29.1, which contains additional columns:
'G' (Behavior),
'H' (Involved team).
--------------------------------------------------------------------------------
Output Work Products:
Refer stages
--------------------------------------------------------------------------------
Acceptance Criteria:
--------------------------------------------------------------------------------
The requirements are derived.
SwAD model updated according to derived requirements.
Sw design (RPY model) and implementation of the behaviors according to the derived requirements is done.
sw unit tests according to the derived requirements are developed.
Derived requirements are mapped to behaviors and imported to Domain Architecture.
In case of gaps/incompleteness/incorrectness which shall not be resolved with particular Task (where the review has failed), only 'ONE' follow up CR shall be created which covers all findings of all Tasks of that CR (purpose: reduction of CRs).
This must be agreed with the SwPM and the CR must be planned by SwPM.
This CR must be spawned by the parent CR of the failed Task.
Responsibility to provide the findings which shall be solved with another CR into the another CR belongs to the Owner of this Task. The reviewer should complete/close the Task only if the findings are documented in the follow up CR.
Example how the follow-up CR might look:
Summary: [FollowUp] <Summary_Of_CR_spawnedBy>
Description:
'This CR is a follow-up CR of <ID_of_CR_spawnedBy>.
With this CR the findings shall be resolved, which were identified during the review of the Task(s) attached to the CR <ID_of_CR_spawnedBy>.
It is agreed with SwPM to shift the correction of the findings to another build.
Task: <ID of Task with Findings>
Refer attachment 'ReviewFindingsOfTask_<ID of Task with Findings>'.' 2021-06-02 WeyandC: Analysis update after meeting with J. Wagner (Autosar) und M. Schlien (Comms).
2021-05-26 C. Klukowski: Refer meeting minutes '2021-05-26_CR 4861296 - MMA X0200 Clarification regarding interfaces for version information for diagnostics.txt'.
Note:
1. The customer has confirmed that DID 0xEF02 "Read Standard Reprogramming SW Package information" is no longer requested to be supported by the application SW. Please, refer to the attached email "AW_ Read DIDs zum Auslesen der Versionsinformationen (X0200).msg".
2. Security colleague has confirmed that DID 0xEF04 "Read SSA Version Information" has already been implemented with ALM_Change Request 4970113 and that its implementation is no longer in the scope of this CR. Please, refer to the attached email "RE_ DAI MMA X0200 - Read SSA VErsion Information.msg".
3. The CR will be used to provide a fix implementation in Diag. A follow-up CR has been spawned to ALM_Change Request 5358720 investigate with Vector how the toolchain can be used to bring the data automatically into the SW and to replace the initial fix implementation.
4. Bootloader colleague C. Henkel was informed about the "µC Identification" that is read with DID 0xEF03 and which should be identical to the one that is read with 0xEF02 in the bootloader.
Purpose of the CR:
Provide implemenation for the following read jobs / read DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
DIAG part:
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for all the listed DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for all the listed DIDs to SWC Diag and configure direction to server:
- support operations ConditionCheckRead, and ReadData
- Add runnables for these DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementation in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for all the listed DIDs.
4. Implement callouts in ReadDataByIdentifier_Cfg to fill response buffer with requested data:
4.1. General:
- Extend configuration table "Read_Data_Id_Access".
- Implement a read callout in ReadDataByIdentifier_Cfg for the DID.
- The response data should provided by Diag itself. Use defines or const variables with file scope.
4.2. Regarding DID 0xEF00 "ECU Extract Version"
Response Format - data type : fix values:
- ECU Extract Major Version - BCD (1Byte) : 21
- ECU Extract Minor Version - BCD (1Byte) : 05
- ECU Extract Patch Version - BCD (1Byte) : 00
- Identification Type Module - Identifications EF00 : 0
- XDIS Version - ASCII (10Byte) : "20.4.1" + filled with space characters
- Export Date - ASCII (10Byte) : "2021-02-05" + filled with space characters
- ECU Name - ASCII (30Byte) : "ESP" + filled with space characters
- Checksum - HexField (200 Byte) : HEX: F9 12 B3 76 E0 05 21 B0 E2 EC 30 D5 B6 74 7F E8 3D 07 6B 22 + filled with 0x00
4.3. Regarding DID 0xEF01 "Diagnostic Extract Version"
Response Format - data type : fix values:
- Diagnostic Extract Major Version - BCD (1Byte): 02
- Diagnostic Extract Minor Version - BCD (1Byte): 00
- Diagnostic Extract Patch Version - BCD (1Byte): 02
- CANdela Version - ASCII (10Byte): “12.0.100” + filled with space characters
- DDM Version - ASCII (10Byte): “V16.0.0” + filled with space characters
- Exported Diagnostic - Variant ASCII (30Byte): "Diag_005002" + filled with space characters
4.4. Regarding DID 0xEF03 "Standard Application SW Package information"
Response Format - data type : fix values:
- Standard Application SW Package Major Version BCD (1Byte) : 11
- Standard Application SW Package Minor Version BCD (1Byte) : 26
- Standard Application SW Package Patch Level BCD (1Byte) : 03
- Standard Application SW Package Build Version BCD (1Byte) : 00
- µC Identification µC ID : "TC387TP" + filled with space characters
- Supplier Identification SupplierList : 0x26
4.5. Regarding DID 0xF10D "Read DDS Package Release"
- Implement a new check function void CheckDdsPackageReleaseInfo(void) in ReadDataByIdentifier_Cfg with subsystem scope.
+ The new function shall be called from function InitDataAccessUnitApplication() after the call of function CheckActiveDiagInfo().
+ The function shall read Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID and store the content of the function in an U8 array with a size of 4 that is declared within the scope of the function
+ The following content is expected:
- array[0]: year of DDS package release of the application
- array[1]: month of DDS package release of the application
- array[2]: year of DDS package release of the bootloader
- array[3]: month of DDS package release of the bootloader
+ The DDS package release of the application is 20 dec (year), 1 dec (month) => introduce defines in ReadDataByIdentifier_Cfg with private scope
+ Check if this data is stored for the application. If so, do nothing. Otherwise, update the content of the array and write Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID with the updated array.
+ Note: No need to check the checksum of the Nvram block. If the checksum is invalid, the Nvram handler will return value 0xFF for all bytes of the block. The DDS package release will be considered as invalid, and the block will be updated.
- Implementation of the DID:
+ first read content of Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID. Then copy the content byte wise into the the Nvram buffer
+ Note: No need to check the checksum of the Nvram block. If the checksum was incorrect, it was corrected in the init phase with function CheckDdsPackageReleaseInfo().
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for these DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
- Map the new runnables only for the DIDs that are implemented by SWC Diag to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE and OS.
17.05.2021 WeyandC:
- Analysis have been started.
- Please, refer to the attached email "ALM_Change Request 4861296_ _DCRP 46_1_ _IBC__SW-D_ SF 8_8 System Diagnostic Function Read Version Data_ Cluster ID 9 .msg" and the attached txt file "CR4861296_VersionData_Notes.txt".
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): C. Weyand, discussed with J. Wagner (Autosar), M. Schlien (Comms), and C. Klukoswki (SwAD). Security team and Integration team are not affected.
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK 1/5
------------------------------------------------------
Title: [DCRP 46.1] [IBC][SW-D] SF 8.8 System Diagnostic Function Read Version Data, Cluster ID
Description:
Please import and map requirements for stub implementation of the following diagnostic read DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
Map runanbles to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_2. The slots are not relevant from functional point of view..
Owner: C. Klukowski
Reviewer: C. Bayer, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8h
[Optional] Planned completion date:
------------------------------------------------------
TASK 2/5
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Implement the following read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
The following DIDs shall be implemented:
- $22 EF 00: Read ECU Extract Version: is specified by section 1.13.1.20 "ECU Extract Version" in the customer DOORS module and by the CDD.
- $22 EF 01: Read Diagnostic Extract Version: is specified by the CDD.
- $22 EF 03: Read Standard Application SW Package information: is specified by section 1.13.1.22 "Standard Application SW Package information" in the customer DOORS module and by the CDD.
- $22 F1 0D: Read DDS Package Release: is specified by section 1.13.1.3 "DDS Package Release" in the customer DOORS module and by the CDD.
Customer DOORS module:
"EBS Diagnostic Requirements Specification": http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00?doors.view=00000003
Owner: C. Weyand
Reviewer: F. Mukkat
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK 3/5
------------------------------------------------------
Title: [MMA][Diag][SWE2][X0200] Implement the following read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement stubs for diagnostic read jobs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: F. Mukkat
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK 4/5
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
+ $22 EF 00: Read ECU Extract Version - $22 EF 01: Read Diagnostic Extract Version
+ $22 EF 03: Read Standard Application SW Package information
+ $22 F1 0D: Read DDS Package Release
- Map the new runnables only for the DIDs that are implemented by SWC Diag to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_2. The slots are not relevant.
=> Generate Dcm, RTE, and OS.
Owner: J. Wagner
Reviewer: H. Ambarukhana, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date:
------------------------------------------------------
TASK 5/5
------------------------------------------------------
Title:
Description:
Note: CR analysis is not yet completed and task description might be adapted.
The following read jobs / read DIDs shall be implemented with this task: - $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for all the listed DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for all the listed DIDs to SWC Diag and configure direction to server:
- support operations ConditionCheckRead, and ReadData
- Add runnables for these DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementation in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for all the listed DIDs.
4. Implement callouts in ReadDataByIdentifier_Cfg to fill response buffer with requested data:
4.1. General:
- Extend configuration table "Read_Data_Id_Access".
- Implement a read callout in ReadDataByIdentifier_Cfg for the DID.
- The response data should provided by Diag itself. Use defines or const variables with file scope.
4.2. Regarding DID 0xEF00 "ECU Extract Version"
Response Format - data type : fix values:
- ECU Extract Major Version - BCD (1Byte) : 21
- ECU Extract Minor Version - BCD (1Byte) : 05
- ECU Extract Patch Version - BCD (1Byte) : 00
- Identification Type Module - Identifications EF00 : 0
- XDIS Version - ASCII (10Byte) : "20.4.1" + filled with space characters
- Export Date - ASCII (10Byte) : "2021-02-05" + filled with space characters
- ECU Name - ASCII (30Byte) : "ESP" + filled with space characters
- Checksum - HexField (200 Byte) : HEX: F9 12 B3 76 E0 05 21 B0 E2 EC 30 D5 B6 74 7F E8 3D 07 6B 22 + filled with 0x00
4.3. Regarding DID 0xEF01 "Diagnostic Extract Version"
Response Format - data type : fix values:
- Diagnostic Extract Major Version - BCD (1Byte): 02
- Diagnostic Extract Minor Version - BCD (1Byte): 00
- Diagnostic Extract Patch Version - BCD (1Byte): 02
- CANdela Version - ASCII (10Byte): “12.0.100” + filled with space characters
- DDM Version - ASCII (10Byte): “V16.0.0” + filled with space characters
- Exported Diagnostic - Variant ASCII (30Byte): "Diag_005002" + filled with space characters
4.4. Regarding DID 0xEF03 "Standard Application SW Package information"
Response Format - data type : fix values:
- Standard Application SW Package Major Version BCD (1Byte) : 11
- Standard Application SW Package Minor Version BCD (1Byte) : 26
- Standard Application SW Package Patch Level BCD (1Byte) : 03
- Standard Application SW Package Build Version BCD (1Byte) : 00
- µC Identification µC ID : "TC387TP" + filled with space characters
- Supplier Identification SupplierList : 0x0026
4.5. Regarding DID 0xF10D "Read DDS Package Release"
- Implement a new check function void CheckDdsPackageReleaseInfo(void) in ReadDataByIdentifier_Cfg with subsystem scope.
+ The new function shall be called from function InitDataAccessUnitApplication() after the call of function CheckActiveDiagInfo().
+ The function shall read Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID and store the content of the function in an U8 array with a size of 4 that is declared within the scope of the function
+ The following content is expected:
- array[0]: year of DDS package release of the application
- array[1]: month of DDS package release of the application
- array[2]: year of DDS package release of the bootloader
- array[3]: month of DDS package release of the bootloader
+ The DDS package release of the application is 20 dec (year), 1 dec (month) => introduce defines in ReadDataByIdentifier_Cfg with private scope
+ Check if this data is stored for the application. If so, do nothing. Otherwise, update the content of the array and write Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID with the updated array.
+ Note: No need to check the checksum of the Nvram block. If the checksum is invalid, the Nvram handler will return value 0xFF for all bytes of the block. The DDS package release will be considered as invalid, and the block will be updated.
- Implementation of the DID:
+ first read content of Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID. Then copy the content byte wise into the the Nvram buffer
+ Note: No need to check the checksum of the Nvram block. If the checksum was incorrect, it was corrected in the init phase with function CheckDdsPackageReleaseInfo().
Note:
- The values for DIDs 0xEF00, 0xEF01, 0xEF03 are also defined in the attached text file.
Owner: S. Irannavar
Reviewer: A. Digajerla
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 18h
[Optional] Planned completion date:
------------------------------------------------------ | [Defect]: [Diag] ESP178: ID-Data services not implemented Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read Version Data, Cluster ID 9
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B1
As part of 'Work step: Perform Preliminary Impact Analysis' in stages https://cdc-stages.emea.zf-world.com:8443/pkit/go/pelement.do?id=469319&type=Subprocess following teams are identified, which are impacted by the customer requirements.
Diag, Comms, Security, Memo
Please assign as 'Owners'; Diag
Please assign as 'Analysers'; Diag, Comms, Memo, SwAD.
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Doing by SwD:
(SWE1)Please derive requirements from the 'Source' (for 'Source' refer below) and map the behavior to the derived requirements
(SWE2)Please update SwAD model according to derived requirements.
(SWE3)Please develop a sw design (RPY model) and implement the behaviors according to the derived requirements.
(SWE4)Please develop sw unit tests according to the derived requirements.
Doing by SwAD:
(SwAD)Import the derived requirements into SwAD model.
Input Work Products (Link or other reference): Source (customer requirements): refer attached excel sheet 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' ,please filter column 'N' 'Diag Cluster ID' for the value of 9
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
The attachment 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' is an export of the customer DOORS module 'EBS Diagnostic Requirements Specification', current 29.1, which contains additional columns:
'G' (Behavior),
'H' (Involved team).
--------------------------------------------------------------------------------
Output Work Products:
Refer stages
--------------------------------------------------------------------------------
Acceptance Criteria:
--------------------------------------------------------------------------------
The requirements are derived.
SwAD model updated according to derived requirements.
Sw design (RPY model) and implementation of the behaviors according to the derived requirements is done.
sw unit tests according to the derived requirements are developed.
Derived requirements are mapped to behaviors and imported to Domain Architecture.
In case of gaps/incompleteness/incorrectness which shall not be resolved with particular Task (where the review has failed), only 'ONE' follow up CR shall be created which covers all findings of all Tasks of that CR (purpose: reduction of CRs).
This must be agreed with the SwPM and the CR must be planned by SwPM.
This CR must be spawned by the parent CR of the failed Task.
Responsibility to provide the findings which shall be solved with another CR into the another CR belongs to the Owner of this Task. The reviewer should complete/close the Task only if the findings are documented in the follow up CR.
Example how the follow-up CR might look:
Summary: [FollowUp] <Summary_Of_CR_spawnedBy>
Description:
'This CR is a follow-up CR of <ID_of_CR_spawnedBy>.
With this CR the findings shall be resolved, which were identified during the review of the Task(s) attached to the CR <ID_of_CR_spawnedBy>.
It is agreed with SwPM to shift the correction of the findings to another build.
Task: <ID of Task with Findings>
Refer attachment 'ReviewFindingsOfTask_<ID of Task with Findings>'.' 2021-06-02 WeyandC: Analysis update after meeting with J. Wagner (Autosar) und M. Schlien (Comms).
2021-05-26 C. Klukowski: Refer meeting minutes '2021-05-26_CR 4861296 - MMA X0200 Clarification regarding interfaces for version information for diagnostics.txt'.
Note:
1. The customer has confirmed that DID 0xEF02 "Read Standard Reprogramming SW Package information" is no longer requested to be supported by the application SW. Please, refer to the attached email "AW_ Read DIDs zum Auslesen der Versionsinformationen (X0200).msg".
2. Security colleague has confirmed that DID 0xEF04 "Read SSA Version Information" has already been implemented with ALM_Change Request 4970113 and that its implementation is no longer in the scope of this CR. Please, refer to the attached email "RE_ DAI MMA X0200 - Read SSA VErsion Information.msg".
3. The CR will be used to provide a fix implementation in Diag. A follow-up CR has been spawned to ALM_Change Request 5358720 investigate with Vector how the toolchain can be used to bring the data automatically into the SW and to replace the initial fix implementation.
4. Bootloader colleague C. Henkel was informed about the "µC Identification" that is read with DID 0xEF03 and which should be identical to the one that is read with 0xEF02 in the bootloader.
Purpose of the CR:
Provide implemenation for the following read jobs / read DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
DIAG part:
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for all the listed DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for all the listed DIDs to SWC Diag and configure direction to server:
- support operations ConditionCheckRead, and ReadData
- Add runnables for these DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementation in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for all the listed DIDs.
4. Implement callouts in ReadDataByIdentifier_Cfg to fill response buffer with requested data:
4.1. General:
- Extend configuration table "Read_Data_Id_Access".
- Implement a read callout in ReadDataByIdentifier_Cfg for the DID.
- The response data should provided by Diag itself. Use defines or const variables with file scope.
4.2. Regarding DID 0xEF00 "ECU Extract Version"
Response Format - data type : fix values:
- ECU Extract Major Version - BCD (1Byte) : 21
- ECU Extract Minor Version - BCD (1Byte) : 05
- ECU Extract Patch Version - BCD (1Byte) : 00
- Identification Type Module - Identifications EF00 : 0
- XDIS Version - ASCII (10Byte) : "20.4.1" + filled with space characters
- Export Date - ASCII (10Byte) : "2021-02-05" + filled with space characters
- ECU Name - ASCII (30Byte) : "ESP" + filled with space characters
- Checksum - HexField (200 Byte) : HEX: F9 12 B3 76 E0 05 21 B0 E2 EC 30 D5 B6 74 7F E8 3D 07 6B 22 + filled with 0x00
4.3. Regarding DID 0xEF01 "Diagnostic Extract Version"
Response Format - data type : fix values:
- Diagnostic Extract Major Version - BCD (1Byte): 02
- Diagnostic Extract Minor Version - BCD (1Byte): 00
- Diagnostic Extract Patch Version - BCD (1Byte): 02
- CANdela Version - ASCII (10Byte): “12.0.100” + filled with space characters
- DDM Version - ASCII (10Byte): “V16.0.0” + filled with space characters
- Exported Diagnostic - Variant ASCII (30Byte): "Diag_005002" + filled with space characters
4.4. Regarding DID 0xEF03 "Standard Application SW Package information"
Response Format - data type : fix values:
- Standard Application SW Package Major Version BCD (1Byte) : 11
- Standard Application SW Package Minor Version BCD (1Byte) : 26
- Standard Application SW Package Patch Level BCD (1Byte) : 03
- Standard Application SW Package Build Version BCD (1Byte) : 00
- µC Identification µC ID : "TC387TP" + filled with space characters
- Supplier Identification SupplierList : 0x26
4.5. Regarding DID 0xF10D "Read DDS Package Release"
- Implement a new check function void CheckDdsPackageReleaseInfo(void) in ReadDataByIdentifier_Cfg with subsystem scope.
+ The new function shall be called from function InitDataAccessUnitApplication() after the call of function CheckActiveDiagInfo().
+ The function shall read Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID and store the content of the function in an U8 array with a size of 4 that is declared within the scope of the function
+ The following content is expected:
- array[0]: year of DDS package release of the application
- array[1]: month of DDS package release of the application
- array[2]: year of DDS package release of the bootloader
- array[3]: month of DDS package release of the bootloader
+ The DDS package release of the application is 20 dec (year), 1 dec (month) => introduce defines in ReadDataByIdentifier_Cfg with private scope
+ Check if this data is stored for the application. If so, do nothing. Otherwise, update the content of the array and write Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID with the updated array.
+ Note: No need to check the checksum of the Nvram block. If the checksum is invalid, the Nvram handler will return value 0xFF for all bytes of the block. The DDS package release will be considered as invalid, and the block will be updated.
- Implementation of the DID:
+ first read content of Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID. Then copy the content byte wise into the the Nvram buffer
+ Note: No need to check the checksum of the Nvram block. If the checksum was incorrect, it was corrected in the init phase with function CheckDdsPackageReleaseInfo().
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for these DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
- Map the new runnables only for the DIDs that are implemented by SWC Diag to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE and OS.
17.05.2021 WeyandC:
- Analysis have been started.
- Please, refer to the attached email "ALM_Change Request 4861296_ _DCRP 46_1_ _IBC__SW-D_ SF 8_8 System Diagnostic Function Read Version Data_ Cluster ID 9 .msg" and the attached txt file "CR4861296_VersionData_Notes.txt".
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): C. Weyand, discussed with J. Wagner (Autosar), M. Schlien (Comms), and C. Klukoswki (SwAD). Security team and Integration team are not affected.
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK 1/5
------------------------------------------------------
Title: [DCRP 46.1] [IBC][SW-D] SF 8.8 System Diagnostic Function Read Version Data, Cluster ID
Description:
Please import and map requirements for stub implementation of the following diagnostic read DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
Map runanbles to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_2. The slots are not relevant from functional point of view..
Owner: C. Klukowski
Reviewer: C. Bayer, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8h
[Optional] Planned completion date:
------------------------------------------------------
TASK 2/5
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Implement the following read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
The following DIDs shall be implemented:
- $22 EF 00: Read ECU Extract Version: is specified by section 1.13.1.20 "ECU Extract Version" in the customer DOORS module and by the CDD.
- $22 EF 01: Read Diagnostic Extract Version: is specified by the CDD.
- $22 EF 03: Read Standard Application SW Package information: is specified by section 1.13.1.22 "Standard Application SW Package information" in the customer DOORS module and by the CDD.
- $22 F1 0D: Read DDS Package Release: is specified by section 1.13.1.3 "DDS Package Release" in the customer DOORS module and by the CDD.
Customer DOORS module:
"EBS Diagnostic Requirements Specification": http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00?doors.view=00000003
Owner: C. Weyand
Reviewer: F. Mukkat
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK 3/5
------------------------------------------------------
Title: [MMA][Diag][SWE2][X0200] Implement the following read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement stubs for diagnostic read jobs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: F. Mukkat
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK 4/5
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
+ $22 EF 00: Read ECU Extract Version - $22 EF 01: Read Diagnostic Extract Version
+ $22 EF 03: Read Standard Application SW Package information
+ $22 F1 0D: Read DDS Package Release
- Map the new runnables only for the DIDs that are implemented by SWC Diag to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_2. The slots are not relevant.
=> Generate Dcm, RTE, and OS.
Owner: J. Wagner
Reviewer: H. Ambarukhana, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date:
------------------------------------------------------
TASK 5/5
------------------------------------------------------
Title:
Description:
Note: CR analysis is not yet completed and task description might be adapted.
The following read jobs / read DIDs shall be implemented with this task: - $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for all the listed DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for all the listed DIDs to SWC Diag and configure direction to server:
- support operations ConditionCheckRead, and ReadData
- Add runnables for these DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementation in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for all the listed DIDs.
4. Implement callouts in ReadDataByIdentifier_Cfg to fill response buffer with requested data:
4.1. General:
- Extend configuration table "Read_Data_Id_Access".
- Implement a read callout in ReadDataByIdentifier_Cfg for the DID.
- The response data should provided by Diag itself. Use defines or const variables with file scope.
4.2. Regarding DID 0xEF00 "ECU Extract Version"
Response Format - data type : fix values:
- ECU Extract Major Version - BCD (1Byte) : 21
- ECU Extract Minor Version - BCD (1Byte) : 05
- ECU Extract Patch Version - BCD (1Byte) : 00
- Identification Type Module - Identifications EF00 : 0
- XDIS Version - ASCII (10Byte) : "20.4.1" + filled with space characters
- Export Date - ASCII (10Byte) : "2021-02-05" + filled with space characters
- ECU Name - ASCII (30Byte) : "ESP" + filled with space characters
- Checksum - HexField (200 Byte) : HEX: F9 12 B3 76 E0 05 21 B0 E2 EC 30 D5 B6 74 7F E8 3D 07 6B 22 + filled with 0x00
4.3. Regarding DID 0xEF01 "Diagnostic Extract Version"
Response Format - data type : fix values:
- Diagnostic Extract Major Version - BCD (1Byte): 02
- Diagnostic Extract Minor Version - BCD (1Byte): 00
- Diagnostic Extract Patch Version - BCD (1Byte): 02
- CANdela Version - ASCII (10Byte): “12.0.100” + filled with space characters
- DDM Version - ASCII (10Byte): “V16.0.0” + filled with space characters
- Exported Diagnostic - Variant ASCII (30Byte): "Diag_005002" + filled with space characters
4.4. Regarding DID 0xEF03 "Standard Application SW Package information"
Response Format - data type : fix values:
- Standard Application SW Package Major Version BCD (1Byte) : 11
- Standard Application SW Package Minor Version BCD (1Byte) : 26
- Standard Application SW Package Patch Level BCD (1Byte) : 03
- Standard Application SW Package Build Version BCD (1Byte) : 00
- µC Identification µC ID : "TC387TP" + filled with space characters
- Supplier Identification SupplierList : 0x0026
4.5. Regarding DID 0xF10D "Read DDS Package Release"
- Implement a new check function void CheckDdsPackageReleaseInfo(void) in ReadDataByIdentifier_Cfg with subsystem scope.
+ The new function shall be called from function InitDataAccessUnitApplication() after the call of function CheckActiveDiagInfo().
+ The function shall read Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID and store the content of the function in an U8 array with a size of 4 that is declared within the scope of the function
+ The following content is expected:
- array[0]: year of DDS package release of the application
- array[1]: month of DDS package release of the application
- array[2]: year of DDS package release of the bootloader
- array[3]: month of DDS package release of the bootloader
+ The DDS package release of the application is 20 dec (year), 1 dec (month) => introduce defines in ReadDataByIdentifier_Cfg with private scope
+ Check if this data is stored for the application. If so, do nothing. Otherwise, update the content of the array and write Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID with the updated array.
+ Note: No need to check the checksum of the Nvram block. If the checksum is invalid, the Nvram handler will return value 0xFF for all bytes of the block. The DDS package release will be considered as invalid, and the block will be updated.
- Implementation of the DID:
+ first read content of Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID. Then copy the content byte wise into the the Nvram buffer
+ Note: No need to check the checksum of the Nvram block. If the checksum was incorrect, it was corrected in the init phase with function CheckDdsPackageReleaseInfo().
Note:
- The values for DIDs 0xEF00, 0xEF01, 0xEF03 are also defined in the attached text file.
Owner: S. Irannavar
Reviewer: A. Digajerla
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 18h
[Optional] Planned completion date:
------------------------------------------------------ |
|
[Defect]: [Diag] ESP178: ID-Data services not implemented This CR scope:
Integration of Crypto Stack + SSA for the functionally route of the SecOC jobs to Crypto SW
here the SecOC key generation has to be done using the default Car specific secret during the development phase (SSA-928)
Provision of initial (standard) key material:
Car-specific secret: 0x5577654d617274696e4a756c69616e416e64726561734d61726b757332303136, Data-ID: 4660 (0x1234)
Resulting SHA-512-Hash: 0x2be0d3774362c7df21f2a696d9915889b54163460a41d1d8c8c1104b
ba4da96a27bd88b5829667075caf4319559d35bbcac333c4c57ffc417e3d11f826472300
Resulting symmetric key: 0x2be0d3774362c7df21f2a696d9915889, resulting checksum for symmetric key: 0x26472300 Hari Krishna E 07/04/2021:
this CR is the first feature integration (Secure Comms) item of B1.1, due to that the CR shall be used for the SSA integration in general plus the SecOC interactions
Accordingly, the analysis has been performed to identify the interaction points of SecOC and SSA along with the important aspects to be considered for integration
1. SSA scheduling
2. SecOC key setup using the Standard Secret via KeyM
3. SecOC BroadCast PDU reception (BcTp)
4. SecOC Interactions withCSM (Crypto SwLib)
5. SSA key storage blocks in NvM
6. SecOC Interactions with FvM(SSA)
a presentation file (SecOC_Integ_Concept.pptx) has been prepared to cover the above listed topics out of customer spec & vector integration docs (refer attachments)
@CCB:
to realize the integration points, following tasks are necessary
#Task: Functional Integ of SSA + SecOC @ Security team (point 2 to 6)
#spawn CR: Scheduling of SSA @ SwAD team (point 1 - slides 3 & 4)
Note: dependencies related to NvM & Dem shall be addressed to CRs (4990180 & 5116760) | [Defect]: [Diag] ESP178: ID-Data services not implemented This CR scope:
Integration of Crypto Stack + SSA for the functionally route of the SecOC jobs to Crypto SW
here the SecOC key generation has to be done using the default Car specific secret during the development phase (SSA-928)
Provision of initial (standard) key material:
Car-specific secret: 0x5577654d617274696e4a756c69616e416e64726561734d61726b757332303136, Data-ID: 4660 (0x1234)
Resulting SHA-512-Hash: 0x2be0d3774362c7df21f2a696d9915889b54163460a41d1d8c8c1104b
ba4da96a27bd88b5829667075caf4319559d35bbcac333c4c57ffc417e3d11f826472300
Resulting symmetric key: 0x2be0d3774362c7df21f2a696d9915889, resulting checksum for symmetric key: 0x26472300 Hari Krishna E 07/04/2021:
this CR is the first feature integration (Secure Comms) item of B1.1, due to that the CR shall be used for the SSA integration in general plus the SecOC interactions
Accordingly, the analysis has been performed to identify the interaction points of SecOC and SSA along with the important aspects to be considered for integration
1. SSA scheduling
2. SecOC key setup using the Standard Secret via KeyM
3. SecOC BroadCast PDU reception (BcTp)
4. SecOC Interactions withCSM (Crypto SwLib)
5. SSA key storage blocks in NvM
6. SecOC Interactions with FvM(SSA)
a presentation file (SecOC_Integ_Concept.pptx) has been prepared to cover the above listed topics out of customer spec & vector integration docs (refer attachments)
@CCB:
to realize the integration points, following tasks are necessary
#Task: Functional Integ of SSA + SecOC @ Security team (point 2 to 6)
#spawn CR: Scheduling of SSA @ SwAD team (point 1 - slides 3 & 4)
Note: dependencies related to NvM & Dem shall be addressed to CRs (4990180 & 5116760) |
|
[Defect]: [Diag] ESP178: ID-Data services not implemented The customer was informed that a functional implementation for the following read DIDs cannot be provided for SW B2 / X0200:
- 0xF18C „ECU SerialNumber"
- 0x010C „Vehicle Odometer“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information“
Hence, the customer has requested at least a stub implementation for these DIDs:
- F18C „ECU SerialNumber“: 178X0200000001 (ASCII)
- 010C „Vehicle Odometer“: 0x00000A
- 0133 „Current Operating Time“: 0x0000000000
- F103 „Vedoc relevant information“: 178X0200000001 (ASCII)
=> Please, refer to the attached email "Fehlende Diagnosedienste zum B2.msg" for details.
This CR shall be used to provide the requested stub implementation for X0200.
Functional implementation will be provided with the following CRs at a later point of time:
- 0xF18C „ECU SerialNumber": ALM_Change Request 4861309
- 0x010C „Vehicle Odometer“: ALM_Change Request 5190898
- 0x0133 „Current Operating Time“: ALM_Change Request 5190898
- 0xF103 „Vedoc relevant information“: ALM_Change Request 4861309 --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
18.05.2021 WeyandC:
0. General note:
- The customer mixed up the following DIDs: 0x010A „Vehicle Odometer in Low Resolution“ and 0x010C "Vehicle Odometer“ in the attached email "Fehlende Diagnosedienste zum B2.msg".
- Other than stated in the CR description, a stub for DID 0x010A "Vehicle Odometer in Low Resolution" shall be provided with this CR - not for DID 0x010C.
- The customer has also confirmed that same string shall be returned for DID 0xF103 as for 0xF18C.
- Please, refer to the Excel Sheet "MMA_Diag_EffortEstimation_2021-05-18_Daimler.xlsx" that was updated today together with the customer (F. Tetzlaff).
Purpose of the CR:
Provide stub implemenation for the following read jobs / read DIDs:
- F18C „ECU SerialNumber“: return fix string 178X0200000001 (ASCII)
- 010A „Vehicle Odometer in Low Resolution“: return fix value 0x000A
- 0133 „Current Operating Time“: return fix value 0x0000000000
- F103 „Vedoc relevant information“: return fix string 178X0200000001 (ASCII)
DIAG part:
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for the 4 DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for the 4 DIDs to SWC Diag and configure direction to server:
- 0xF18C: support operations ConditionCheckRead, ReadData and ReadDataLength
- 0x010A: support operations ConditionCheckRead, and ReadData
- 0x0133: support operations ConditionCheckRead, and ReadData
- 0xF103: support operations ConditionCheckRead, ReadData and ReadDataLength
- Add runnables for the DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementatiton in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for the 4 DIDs.
4. Implement configuration and implementation in ReadDataByIdentifier_Cfg.
- add entries for the 4 DIDs to ROM table Read_Data_Id_Access and update the size of the table
- implement read functions for the new 4 DIDs:
a. read function for DID 0xF18C "ECU SerialNumber"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
b. read function for DID 0x010A "Vehicle Odometer in Low Resolution"
- shall fill the buffer with hex value 0x000A
- shall copy data of (a) define(s) to the response buffer
- response length: 2 byte
c. read function for DID 0x0133 "Current Operating Time"
- shall fill the buffer with hex value 0x0000000000
- shall copy data of (a) define(s) to the response buffer
- response length: 5 byte
d. read function for DID 0xF103 "Vedoc relevant information"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
- 0xF18C „ECU SerialNumber"
- 0x010A „Vehicle Odometer in Low Resolution“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information“
- Map the 10 new runnables for the DIDs to OS task Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE and OS.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeyandC, accepted by S. Basavaraju, C. Klukowski
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK: Autosar
------------------------------------------------------
Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
- 0xF18C "ECU SerialNumber"
- 0x010A "Vehicle Odometer in Low Resolution"
- 0x0133 "Current Operating Time"
- 0xF103 "Vedoc relevant information"
- Map the 10 new runnables for the DIDs to OS task Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE, and OS.
Owner: Hemanth Ambarukhana
Reviewer: Sireesha Basavarju, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7
[Optional] Planned completion date:
------------------------------------------------------
TASK: DIAG SWE1
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
The following DIDs shall be implemented:
- DID 0xF18C "ECUSerialNumberDataIdentifier" is specified by section 1.13.1.12 "ECU Serial Number" in the customer DOORS module and by the CDD.
- DID 0xF103 "Vedoc Relevant Information" is specified by section 1.13.1.25 "Vedoc Relevant Information" in the customer DOORS module and by the CDD.
- DID 0x010A "Vehicle Odometer in Low Resolution" is specified by the CDD.
- DID 0x0133 "Current Operating Time" is specified by the CDD.
Customer DOORS module:
"EBS Diagnostic Requirements Specification": http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00?doors.view=00000003
Please, use this task to specify SW requirements for the stub implementation of the 4 read DIDs:
- F18C „ECU SerialNumber“: return fix string 178X0200000001 (ASCII)
- 010A „Vehicle Odometer in Low Resolution“: return fix value 0x000A
- 0133 „Current Operating Time“: return fix value 0x0000000000
- F103 „Vedoc relevant information“: return fix string 178X0200000001 (ASCII)
Owner: J. Hornung
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4
[Optional] Planned completion date: 26.06.2021
------------------------------------------------------
TASK: DIAG SWE3/4
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for the 4 DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for the 4 DIDs to SWC Diag and configure direction to server:
- 0xF18C: support operations ConditionCheckRead, ReadData and ReadDataLength
- 0x010A: support operations ConditionCheckRead, and ReadData
- 0x0133: support operations ConditionCheckRead, and ReadData
- 0xF103: support operations ConditionCheckRead, ReadData and ReadDataLength
- Add runnables for the DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementatiton in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for the 4 DIDs.
4. Implement configuration and implementation in ReadDataByIdentifier_Cfg.
- add entries for the 4 DIDs to ROM table Read_Data_Id_Access and update the size of the table
- implement read functions for the new 4 DIDs:
a. read function for DID 0xF18C "ECU SerialNumber"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
b. read function for DID 0x010A "Vehicle Odometer in Low Resolution"
- shall fill the buffer with hex value 0x000A
- shall copy data of (a) define(s) to the response buffer
- response length: 2 byte
c. read function for DID 0x0133 "Current Operating Time"
- shall fill the buffer with hex value 0x0000000000
- shall copy data of (a) define(s) to the response buffer
- response length: 5 byte
d. read function for DID 0xF103 "Vedoc relevant information"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
Owner: Satishpundalik Irannavar
Reviewer: Ashwini Digajerla
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 14h
[Optional] Planned completion date:
------------------------------------------------------
TASK: DIAG SWE2
------------------------------------------------------
Title: [MMA][Diag][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
(SWE2) Please update SwAD model according to derived requirements.
The CR is used to implement stubs for diagnostic read jobs:
- 0xF18C „ECU SerialNumber"
- 0x010A „Vehicle Odometer in Low Resolution“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information"
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: A. Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 28.05.2021
------------------------------------------------------
TASK SwAD
------------------------------------------------------
Title: [MMA] [X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103 - Import requirements and map the runnables
Description:
Import and map the requirements.
Map the runnables (10) to OS task Task_DiagEvents_D_C0_1.
For details refer CR or Tasks at CR.
Owner:Caesar Klukowski
Reviewer:Christian Weyand, Jens Auer
------------------------------------------------------
Total effort/h: 8
------------------------------------------------------ | [Defect]: [Diag] ESP178: ID-Data services not implemented The customer was informed that a functional implementation for the following read DIDs cannot be provided for SW B2 / X0200:
- 0xF18C „ECU SerialNumber"
- 0x010C „Vehicle Odometer“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information“
Hence, the customer has requested at least a stub implementation for these DIDs:
- F18C „ECU SerialNumber“: 178X0200000001 (ASCII)
- 010C „Vehicle Odometer“: 0x00000A
- 0133 „Current Operating Time“: 0x0000000000
- F103 „Vedoc relevant information“: 178X0200000001 (ASCII)
=> Please, refer to the attached email "Fehlende Diagnosedienste zum B2.msg" for details.
This CR shall be used to provide the requested stub implementation for X0200.
Functional implementation will be provided with the following CRs at a later point of time:
- 0xF18C „ECU SerialNumber": ALM_Change Request 4861309
- 0x010C „Vehicle Odometer“: ALM_Change Request 5190898
- 0x0133 „Current Operating Time“: ALM_Change Request 5190898
- 0xF103 „Vedoc relevant information“: ALM_Change Request 4861309 --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
18.05.2021 WeyandC:
0. General note:
- The customer mixed up the following DIDs: 0x010A „Vehicle Odometer in Low Resolution“ and 0x010C "Vehicle Odometer“ in the attached email "Fehlende Diagnosedienste zum B2.msg".
- Other than stated in the CR description, a stub for DID 0x010A "Vehicle Odometer in Low Resolution" shall be provided with this CR - not for DID 0x010C.
- The customer has also confirmed that same string shall be returned for DID 0xF103 as for 0xF18C.
- Please, refer to the Excel Sheet "MMA_Diag_EffortEstimation_2021-05-18_Daimler.xlsx" that was updated today together with the customer (F. Tetzlaff).
Purpose of the CR:
Provide stub implemenation for the following read jobs / read DIDs:
- F18C „ECU SerialNumber“: return fix string 178X0200000001 (ASCII)
- 010A „Vehicle Odometer in Low Resolution“: return fix value 0x000A
- 0133 „Current Operating Time“: return fix value 0x0000000000
- F103 „Vedoc relevant information“: return fix string 178X0200000001 (ASCII)
DIAG part:
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for the 4 DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for the 4 DIDs to SWC Diag and configure direction to server:
- 0xF18C: support operations ConditionCheckRead, ReadData and ReadDataLength
- 0x010A: support operations ConditionCheckRead, and ReadData
- 0x0133: support operations ConditionCheckRead, and ReadData
- 0xF103: support operations ConditionCheckRead, ReadData and ReadDataLength
- Add runnables for the DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementatiton in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for the 4 DIDs.
4. Implement configuration and implementation in ReadDataByIdentifier_Cfg.
- add entries for the 4 DIDs to ROM table Read_Data_Id_Access and update the size of the table
- implement read functions for the new 4 DIDs:
a. read function for DID 0xF18C "ECU SerialNumber"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
b. read function for DID 0x010A "Vehicle Odometer in Low Resolution"
- shall fill the buffer with hex value 0x000A
- shall copy data of (a) define(s) to the response buffer
- response length: 2 byte
c. read function for DID 0x0133 "Current Operating Time"
- shall fill the buffer with hex value 0x0000000000
- shall copy data of (a) define(s) to the response buffer
- response length: 5 byte
d. read function for DID 0xF103 "Vedoc relevant information"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
- 0xF18C „ECU SerialNumber"
- 0x010A „Vehicle Odometer in Low Resolution“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information“
- Map the 10 new runnables for the DIDs to OS task Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE and OS.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeyandC, accepted by S. Basavaraju, C. Klukowski
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK: Autosar
------------------------------------------------------
Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
- 0xF18C "ECU SerialNumber"
- 0x010A "Vehicle Odometer in Low Resolution"
- 0x0133 "Current Operating Time"
- 0xF103 "Vedoc relevant information"
- Map the 10 new runnables for the DIDs to OS task Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE, and OS.
Owner: Hemanth Ambarukhana
Reviewer: Sireesha Basavarju, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7
[Optional] Planned completion date:
------------------------------------------------------
TASK: DIAG SWE1
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
The following DIDs shall be implemented:
- DID 0xF18C "ECUSerialNumberDataIdentifier" is specified by section 1.13.1.12 "ECU Serial Number" in the customer DOORS module and by the CDD.
- DID 0xF103 "Vedoc Relevant Information" is specified by section 1.13.1.25 "Vedoc Relevant Information" in the customer DOORS module and by the CDD.
- DID 0x010A "Vehicle Odometer in Low Resolution" is specified by the CDD.
- DID 0x0133 "Current Operating Time" is specified by the CDD.
Customer DOORS module:
"EBS Diagnostic Requirements Specification": http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00?doors.view=00000003
Please, use this task to specify SW requirements for the stub implementation of the 4 read DIDs:
- F18C „ECU SerialNumber“: return fix string 178X0200000001 (ASCII)
- 010A „Vehicle Odometer in Low Resolution“: return fix value 0x000A
- 0133 „Current Operating Time“: return fix value 0x0000000000
- F103 „Vedoc relevant information“: return fix string 178X0200000001 (ASCII)
Owner: J. Hornung
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4
[Optional] Planned completion date: 26.06.2021
------------------------------------------------------
TASK: DIAG SWE3/4
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for the 4 DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for the 4 DIDs to SWC Diag and configure direction to server:
- 0xF18C: support operations ConditionCheckRead, ReadData and ReadDataLength
- 0x010A: support operations ConditionCheckRead, and ReadData
- 0x0133: support operations ConditionCheckRead, and ReadData
- 0xF103: support operations ConditionCheckRead, ReadData and ReadDataLength
- Add runnables for the DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementatiton in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for the 4 DIDs.
4. Implement configuration and implementation in ReadDataByIdentifier_Cfg.
- add entries for the 4 DIDs to ROM table Read_Data_Id_Access and update the size of the table
- implement read functions for the new 4 DIDs:
a. read function for DID 0xF18C "ECU SerialNumber"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
b. read function for DID 0x010A "Vehicle Odometer in Low Resolution"
- shall fill the buffer with hex value 0x000A
- shall copy data of (a) define(s) to the response buffer
- response length: 2 byte
c. read function for DID 0x0133 "Current Operating Time"
- shall fill the buffer with hex value 0x0000000000
- shall copy data of (a) define(s) to the response buffer
- response length: 5 byte
d. read function for DID 0xF103 "Vedoc relevant information"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
Owner: Satishpundalik Irannavar
Reviewer: Ashwini Digajerla
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 14h
[Optional] Planned completion date:
------------------------------------------------------
TASK: DIAG SWE2
------------------------------------------------------
Title: [MMA][Diag][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
(SWE2) Please update SwAD model according to derived requirements.
The CR is used to implement stubs for diagnostic read jobs:
- 0xF18C „ECU SerialNumber"
- 0x010A „Vehicle Odometer in Low Resolution“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information"
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: A. Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 28.05.2021
------------------------------------------------------
TASK SwAD
------------------------------------------------------
Title: [MMA] [X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103 - Import requirements and map the runnables
Description:
Import and map the requirements.
Map the runnables (10) to OS task Task_DiagEvents_D_C0_1.
For details refer CR or Tasks at CR.
Owner:Caesar Klukowski
Reviewer:Christian Weyand, Jens Auer
------------------------------------------------------
Total effort/h: 8
------------------------------------------------------ |
|
[VW][MQB48W][ESC][X0401-010_X330] ESP_StartStopp_Info = Systemfehler Due to incorrect size of the ICC array "IccTxBuf_C1_C0.IsChassinfFunctionEnable_boolean" and the "for loop" shown below, Start/Stop function is always considered to be disabled by Chassinf (IsChassinfFunctionEnable(CHASSINF_SSA) always returns FALSE) even if the ECU is coded for Start/Stop and therefore, 'Systemfehler' is sent on the signal "ESP_StartStopp_Info" by the Start/Stop Handler.
The issue is reported for X0401 SW as ICC is still used. In the later SW versions, ICC is replaced with RTE and this issue would not occur . The above fix therefore, is only required for X0401 SW. Brief analysis summary:
--------------------------------------------------------------------------------
This CR should be used for Regeneration of ICC to provide updated inter core communication wrapper for the rest of the software.
Regeneration is required to resolve the issues due to incorrect size of ICC array 'IccTxBuf_C1_C0.IsChassinfFunctionEnable_boolean '
Correct array size is 152.
Latest x401 CP : 1.633.1.215.2.68 should be used.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification): Implement proposed task | [VW][MQB48W][ESC][X0401-010_X330] ESP_StartStopp_Info = Systemfehler Due to incorrect size of the ICC array "IccTxBuf_C1_C0.IsChassinfFunctionEnable_boolean" and the "for loop" shown below, Start/Stop function is always considered to be disabled by Chassinf (IsChassinfFunctionEnable(CHASSINF_SSA) always returns FALSE) even if the ECU is coded for Start/Stop and therefore, 'Systemfehler' is sent on the signal "ESP_StartStopp_Info" by the Start/Stop Handler.
The issue is reported for X0401 SW as ICC is still used. In the later SW versions, ICC is replaced with RTE and this issue would not occur . The above fix therefore, is only required for X0401 SW. Brief analysis summary:
--------------------------------------------------------------------------------
This CR should be used for Regeneration of ICC to provide updated inter core communication wrapper for the rest of the software.
Regeneration is required to resolve the issues due to incorrect size of ICC array 'IccTxBuf_C1_C0.IsChassinfFunctionEnable_boolean '
Correct array size is 152.
Latest x401 CP : 1.633.1.215.2.68 should be used.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification): Implement proposed task |
|
Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC" Realization of Customer request: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC"
target is to provide the recent Parameterset (series software S011) in a new format for new Software S012:
CRs shall be created for following tasks
F&C:
*. update minor Revision of recent Parameter set “PARAMPBL_Audi_CBEV_039_056_000.c” 0G à 0H à new Parameter set
(Integration:
*. creating of new ODX file with the name: “DB_0003_7101_4KE_A00H_AU516PBCA00H_M3PBCVAR001ECE18HA.odx”
*. using new ODX create (v2.50): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22ODXCreate%5fV250%5fLizenz%5f20221205.7z%22
*. with new FDS2309: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22config%5fFDSProject%5f2309%5fE.7z%22
*. and possibly (depending on answer of Conti): new SA2 code (to be provided by Continental)
*. Preparation of Zip file using Audi Tool: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/PPE/01%5fFrom%5fCustomer/03%5fTools/ODX/project.pj&selection=%22dsdg22sys42%5fwithout%5fprefix.zip%22 )
This Change Request shall be used to for PBC Function & Control Team - change in parameter set P. Billig (23.07.21 - 14:10):
--------------------------------------------------------------------------------
Brief investigation comment:
This CR is for adapting some revision numbers and generating the new PARAMPBL_*.c file only (F&C part, see above).
To do so:
- Adapt minor revision of parameter file as usual. Do NOT generate parameter files yet.
- In file PBC_PARA\03_Integration\Build_Param\Config\DB_0003_7101_4KE_A001_AU5160000000_AU5164KESW0001DSA001.ocnf adapt values
<DataRecordVersion>A00G</DataRecordVersion>
<ModulVariant>AU516PBCA00G</ModulVariant>
to
<DataRecordVersion>A00H</DataRecordVersion>
<ModulVariant>AU516PBCA00H</ModulVariant>
- Update PBC_PARA\03_Integration\Build_Param\Build module to checkpoint 1.14.1.9.1.3
- Now generate new parameter files.
- If not present, check in generated PARAMPBL_*.c file
- If an older PARAMPBL_*.c is present at the same folder with a different name, remove it.
- Check in other parameter file generation artifacts, as usual.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for TCI: <Title> Audi CBEV - Adapt some parameter file revision numbers and generate new parameter files / Verifier: E. Harder (8 h)
Is a change in the ParameterFile required? (Do we need a PARA build?)
--------------------------------------------------------------------------------
Yes [x] or No []
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 22.07.21 - 13:40:
Please investigate this point and advise the next steps. | Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC" Realization of Customer request: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC"
target is to provide the recent Parameterset (series software S011) in a new format for new Software S012:
CRs shall be created for following tasks
F&C:
*. update minor Revision of recent Parameter set “PARAMPBL_Audi_CBEV_039_056_000.c” 0G à 0H à new Parameter set
(Integration:
*. creating of new ODX file with the name: “DB_0003_7101_4KE_A00H_AU516PBCA00H_M3PBCVAR001ECE18HA.odx”
*. using new ODX create (v2.50): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22ODXCreate%5fV250%5fLizenz%5f20221205.7z%22
*. with new FDS2309: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22config%5fFDSProject%5f2309%5fE.7z%22
*. and possibly (depending on answer of Conti): new SA2 code (to be provided by Continental)
*. Preparation of Zip file using Audi Tool: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/PPE/01%5fFrom%5fCustomer/03%5fTools/ODX/project.pj&selection=%22dsdg22sys42%5fwithout%5fprefix.zip%22 )
This Change Request shall be used to for PBC Function & Control Team - change in parameter set P. Billig (23.07.21 - 14:10):
--------------------------------------------------------------------------------
Brief investigation comment:
This CR is for adapting some revision numbers and generating the new PARAMPBL_*.c file only (F&C part, see above).
To do so:
- Adapt minor revision of parameter file as usual. Do NOT generate parameter files yet.
- In file PBC_PARA\03_Integration\Build_Param\Config\DB_0003_7101_4KE_A001_AU5160000000_AU5164KESW0001DSA001.ocnf adapt values
<DataRecordVersion>A00G</DataRecordVersion>
<ModulVariant>AU516PBCA00G</ModulVariant>
to
<DataRecordVersion>A00H</DataRecordVersion>
<ModulVariant>AU516PBCA00H</ModulVariant>
- Update PBC_PARA\03_Integration\Build_Param\Build module to checkpoint 1.14.1.9.1.3
- Now generate new parameter files.
- If not present, check in generated PARAMPBL_*.c file
- If an older PARAMPBL_*.c is present at the same folder with a different name, remove it.
- Check in other parameter file generation artifacts, as usual.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for TCI: <Title> Audi CBEV - Adapt some parameter file revision numbers and generate new parameter files / Verifier: E. Harder (8 h)
Is a change in the ParameterFile required? (Do we need a PARA build?)
--------------------------------------------------------------------------------
Yes [x] or No []
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 22.07.21 - 13:40:
Please investigate this point and advise the next steps. |
|
Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC" Realization of Customer request: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC"
target is to provide the recent Parameterset in a new format:
CRs shall be created for following tasks
F&C:
*. update minor Revision of recent Parameter set “PARAMPBL_Audi_CBEV_039_056_000.c” 0G à 0H à new Parameter set
*. will be implemented with CR 5533486
Integration:
*. creating of new ODX file with the name: “DB_0003_7101_4KE_A00H_AU516PBCA00H_M3PBCVAR001ECE18HA.odx”
*. using new ODX create (v2.50): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22ODXCreate%5fV250%5fLizenz%5f20221205.7z%22
*. with new FDS2309: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22config%5fFDSProject%5f2309%5fE.7z%22
*. and possibly (depending on answer of Conti): new SA2 code (to be provided by Continental)
*. Preparation of Zip file using Audi Tool: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/PPE/01%5fFrom%5fCustomer/03%5fTools/ODX/project.pj&selection=%22dsdg22sys42%5fwithout%5fprefix.zip%22
Please use this CR to introduce the odx file format Since this involves changes only to the Binaries of PARA and the necessary Tools update, this CR can be canceled and the changes will be implemented using the Integration Task. | Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC" Realization of Customer request: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC"
target is to provide the recent Parameterset in a new format:
CRs shall be created for following tasks
F&C:
*. update minor Revision of recent Parameter set “PARAMPBL_Audi_CBEV_039_056_000.c” 0G à 0H à new Parameter set
*. will be implemented with CR 5533486
Integration:
*. creating of new ODX file with the name: “DB_0003_7101_4KE_A00H_AU516PBCA00H_M3PBCVAR001ECE18HA.odx”
*. using new ODX create (v2.50): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22ODXCreate%5fV250%5fLizenz%5f20221205.7z%22
*. with new FDS2309: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22config%5fFDSProject%5f2309%5fE.7z%22
*. and possibly (depending on answer of Conti): new SA2 code (to be provided by Continental)
*. Preparation of Zip file using Audi Tool: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/PPE/01%5fFrom%5fCustomer/03%5fTools/ODX/project.pj&selection=%22dsdg22sys42%5fwithout%5fprefix.zip%22
Please use this CR to introduce the odx file format Since this involves changes only to the Binaries of PARA and the necessary Tools update, this CR can be canceled and the changes will be implemented using the Integration Task. |
|
[QRCM] GM T1XX - Motor Position Sensor (MPS) Failure to Learn "systematic root-cause" should be documented in 3x5 Why, and an improvement idea should be proposed.
This CR is to track the implementation of the systematic improvement Reject this CR for Preventive Action. SW can handle any specified range of error adjustment. 2% was specificed by Systems group. | [QRCM] GM T1XX - Motor Position Sensor (MPS) Failure to Learn "systematic root-cause" should be documented in 3x5 Why, and an improvement idea should be proposed.
This CR is to track the implementation of the systematic improvement Reject this CR for Preventive Action. SW can handle any specified range of error adjustment. 2% was specificed by Systems group. |
|
[QA][PA2116][SYS.4][GP.2.1.2][GP.2.1.3][GP.2.1.4][SYS.5][GP.2.1.2][GP.2.1.3]Only Duration estimation mentioned in the MS project plan but not the effort (person days) Update MS Project information according to mentioned points. Update MS project information according to the weekness that ASPICE mentioned. | [QA][PA2116][SYS.4][GP.2.1.2][GP.2.1.3][GP.2.1.4][SYS.5][GP.2.1.2][GP.2.1.3]Only Duration estimation mentioned in the MS project plan but not the effort (person days) Update MS Project information according to mentioned points. Update MS project information according to the weekness that ASPICE mentioned. |
|
Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs. Andrew Berg 07-21-21
Proposed_Changes_v2.zip attached.
QAC Report v2.zip attached.
Test Report v2.docx attached.
Andrew Berg 07-14-21
Proposed_Changes_v1.zip attached.
QAC Report v1.zip attached. | Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs. Andrew Berg 07-21-21
Proposed_Changes_v2.zip attached.
QAC Report v2.zip attached.
Test Report v2.docx attached.
Andrew Berg 07-14-21
Proposed_Changes_v1.zip attached.
QAC Report v1.zip attached. |
|
Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults Below Fault IDs need to be removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED See description | Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults Below Fault IDs need to be removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED See description |
|
Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults The goal of this CR to remove the following fault from the following programs:
A100 PBM, A100 SBM, 31XX:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED
The current plan for release is:
- September 7th for 31XX V05.0 Integ 2
- September 9th for A100 PBM V18.0 Integ 1
- September 16th for A100 SBM V18.0 Integ 1 Duplicate of CR 5449398 | Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults The goal of this CR to remove the following fault from the following programs:
A100 PBM, A100 SBM, 31XX:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED
The current plan for release is:
- September 7th for 31XX V05.0 Integ 2
- September 9th for A100 PBM V18.0 Integ 1
- September 16th for A100 SBM V18.0 Integ 1 Duplicate of CR 5449398 |
|
Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs. Andrew Berg 07-21-21
Proposed_Changes_v2.zip attached.
QAC Report v2.zip attached.
Test Report v2.docx attached.
Andrew Berg 07-14-21
Proposed_Changes_v1.zip attached.
QAC Report v1.zip attached. | Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs. Andrew Berg 07-21-21
Proposed_Changes_v2.zip attached.
QAC Report v2.zip attached.
Test Report v2.docx attached.
Andrew Berg 07-14-21
Proposed_Changes_v1.zip attached.
QAC Report v1.zip attached. |
|
Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults Below Fault IDs need to be removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED following faults are removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED | Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults Below Fault IDs need to be removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED following faults are removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED |
|
[OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected SW-Resets due to exceptions in Opel-K0 project and below change was introduced with “ALM_Task 5202634: [OPEL K0] [PSW] Proivde interfaces for Tx signals” where the dataset are not aligned to group ID ordering of CAL sub groups. But addition of new Calibration set for AAW does not match to the group ordering, The group ordering for the AAW calibration set must be changed | [OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected SW-Resets due to exceptions in Opel-K0 project and below change was introduced with “ALM_Task 5202634: [OPEL K0] [PSW] Proivde interfaces for Tx signals” where the dataset are not aligned to group ID ordering of CAL sub groups. But addition of new Calibration set for AAW does not match to the group ordering, The group ordering for the AAW calibration set must be changed |
|
[OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected 1) In X300_173 testing within Dry-HIL, UNEXPECTED_EXCEPTION failure was seen directly after switching the gearbox from D to P.
In further investigation it was found that it is caused due to alignment issue within Calibration Data as shown in below snap
It is identified that there is no alignment set for 'Calibration_Flash_text', 'Calibration_Flash_const_text_0', 'Calibration_Flash_const_text_3', 'Calibration_Flash_data', 'Calibration_Ram'. Hence need to update Calibration linker scripts to have the alignment proper.
2) Seen that SSM_PB_PARAM_CALIBRATION_PTR address is wrongly pointing to 0x805C8198 and this need to be corrected to 0x805BC08C.
3) Also it looks PBC_PARAM_CALIBRATION_PTR is not being used within the App and so it can be cleanedup if possible.
Attached are the correct files. Please check and update the Linker contents. (Took 1.199 opel sandbox as base line for changes) [Saritha Tatipally (Z666542), 24-06-2021]--------------------------------------------------------------------------------
Brief analysis summary: [OPEL K0] Need to have alignment fixed within Calibration Data
--------------------------------------------------------------------------------
It was observed while testing on Dry HIL, UnExpected Exception - ALN error at DEAD Address 0x805C002D which is a odd address of calibration.
So alignment of calibration is needed
Risk (low/medium/high): Low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):Saritha Tatipally
Proposal of next steps (incl. effort/h and verification): Please create TASK 1
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title: [OPEL K0] Update calibration Linker with alignment
Description :
It is identified that there is no alignment set for 'Calibration_Flash_text', 'Calibration_Flash_const_text_0', 'Calibration_Flash_const_text_3', 'Calibration_Flash_data', 'Calibration_Ram'. Hence need to update Calibration linker scripts to have the alignment proper.
2) Seen that SSM_PB_PARAM_CALIBRATION_PTR address is wrongly pointing to 0x805C8198 and this need to be corrected to 0x805BC08C.
3) Also it looks PBC_PARAM_CALIBRATION_PTR is not being used within the App and so it can be cleanedup if possible
Owner: Saritha Tatipally
Reviewer: Dileep
Estimated design effort/h:
Estimated implementation effort/h:4
Estimated unit testing effort/h:2
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date: 05-07-2021
------------------------------------------------------ | [OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected 1) In X300_173 testing within Dry-HIL, UNEXPECTED_EXCEPTION failure was seen directly after switching the gearbox from D to P.
In further investigation it was found that it is caused due to alignment issue within Calibration Data as shown in below snap
It is identified that there is no alignment set for 'Calibration_Flash_text', 'Calibration_Flash_const_text_0', 'Calibration_Flash_const_text_3', 'Calibration_Flash_data', 'Calibration_Ram'. Hence need to update Calibration linker scripts to have the alignment proper.
2) Seen that SSM_PB_PARAM_CALIBRATION_PTR address is wrongly pointing to 0x805C8198 and this need to be corrected to 0x805BC08C.
3) Also it looks PBC_PARAM_CALIBRATION_PTR is not being used within the App and so it can be cleanedup if possible.
Attached are the correct files. Please check and update the Linker contents. (Took 1.199 opel sandbox as base line for changes) [Saritha Tatipally (Z666542), 24-06-2021]--------------------------------------------------------------------------------
Brief analysis summary: [OPEL K0] Need to have alignment fixed within Calibration Data
--------------------------------------------------------------------------------
It was observed while testing on Dry HIL, UnExpected Exception - ALN error at DEAD Address 0x805C002D which is a odd address of calibration.
So alignment of calibration is needed
Risk (low/medium/high): Low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):Saritha Tatipally
Proposal of next steps (incl. effort/h and verification): Please create TASK 1
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title: [OPEL K0] Update calibration Linker with alignment
Description :
It is identified that there is no alignment set for 'Calibration_Flash_text', 'Calibration_Flash_const_text_0', 'Calibration_Flash_const_text_3', 'Calibration_Flash_data', 'Calibration_Ram'. Hence need to update Calibration linker scripts to have the alignment proper.
2) Seen that SSM_PB_PARAM_CALIBRATION_PTR address is wrongly pointing to 0x805C8198 and this need to be corrected to 0x805BC08C.
3) Also it looks PBC_PARAM_CALIBRATION_PTR is not being used within the App and so it can be cleanedup if possible
Owner: Saritha Tatipally
Reviewer: Dileep
Estimated design effort/h:
Estimated implementation effort/h:4
Estimated unit testing effort/h:2
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date: 05-07-2021
------------------------------------------------------ |
End of preview. Expand
in Dataset Viewer.
README.md exists but content is empty.
Use the Edit dataset card button to edit it.
- Downloads last month
- 37