01552_14_01306_8.0_EPS_CMP_SW_VC2_Notebook.doc

Software Requirement Notebook
DAE CMP : SW VC2
DATE REFERENCE IND PROJET PAGE
30/06/2017 01552_14_01306 8.0 CMP 1/34
CE DOCUMENT EST LA PROPRIETE DU GROUPE PSA PEUGEOT CITROEN ET NE PEUT ETRE REPRODUIT OU COMMUNIQUE SANS SON AUTORISATION
Reference:
01552_14_01306 Ind 8.0
DIRECTION RECHERCHE ET DEVELOPPEMENT
DRD/DSEE/MCDV/E2TC/SDTC
SOFTWARE REQUIREMENTS NOTEBOOK
EPS CMP
01552_14_01306 ind 8.0
SOFTWARE REQUIREMENT NOTEBOOK
DAE CMP
SW VC2
REFERENCE IND DATE
CONFIDENT
IALITE
01552_14_01306 8.0 30/06/2017
USAGE
INTERNE
PROJET(S) SITE Découpage PSA PAGE
EPS CMP E47 1/34
Written by Checked by Approved by
Nom : Alain YAGOUBI Nom : Malik Chaffi Nom : Philippe CARTIER
Entité :
DSEE/MCDV/E2TC/SDTC
Entité :
DSEE/MCDV/E2TC/SDTC
Entité :
DSEE/MCDV/E2TC/SDTC
Date :
30/06/2017
Signature : Date:
30/06/2017
Signature : Date : Signature :

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 2/34
REVISION / REVISION
Ce cahier des charges est issu du modèle CSEE_CLCO06_0132/
This document has been written according to CCEE_CLCO06_0132
Version Date Description
1.0 2014/02 Creation for EPS BVH1v5 RFQ
2.0 2014/09 Update:
- List of specification update
- Variant coding definition transfer to application note [708]
3.0 2014/12 Update:
4.0 2015/July Update for SW VF-2:
- Addition of chapter EE identification with VF-2 release
5.0 2015/09/01 Update for SW VF-1:
- Deliveries date
- EE identification with VF-1 release
- Addition of chapter Altis Corrected
6.0 2015/09/01 Update for SW VF:
- Deliveries date
- EE identification with VF release
- Addition of chapter Altis Corrected
6.1 24/05/2016 § 1.1 DEVELOPMENT CONTEXT
§ 4.1.1 Specifications list
§ 4.5.4.3 EE identification
7.0 26/09/2016 Update for SW VC1:
- Deliveries date
- EE identification with VC1 release
- Application Key
7.1 03/10/2016 § 4.1.3 Altis to correct
§ 4.1.1 Specifications list:
8.0 30/06/2017 §1.1 Development Context
§4.1.1 Specifications list
§ 4.1.3 Altis to correct
§ 4.5.4.4 Identification Zone
§ 4.5.4.7 Authentication zone
§ 4.5.4.8 Définition du contenu de l’étiquette CEM

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 3/34
SOMMAIRE / TABLE OF CONTENTS
REVISION / REVISION.................................................................................................................................................... 2
SOMMAIRE / TABLE OF CONTENTS.......................................................................................................................... 3
1 SCOPE OF APPLICATION .................................................................................................................................... 5
1.1 DEVELOPMENT CONTEXT ............................................................................................................................... 5
1.2 GENERAL SYSTEM DESCRIPTION .................................................................................................................. 5
2 MENTIONED DOCUMENTS................................................................................................................................. 5
2.1 REFERENCE DOCUMENTS................................................................................................................................ 5
2.2 APPLICABLE DOCUMENTS .............................................................................................................................. 6
2.3 REQUIREMENTS DOCUMENTS ORGANISATION......................................................................................... 7
3 TERMINOLOGY ..................................................................................................................................................... 8
3.1 GLOSSARY........................................................................................................................................................... 8
3.2 ACRONYMS ....................................................................................................................................................... 10
3.3 DOCUMENT RULE ............................................................................................................................................ 13
4 REQUIREMENTS.................................................................................................................................................. 14
4.1 FUNCTIONAL REQUIREMENTS..................................................................................................................... 14
4.1.1 Specifications list:....................................................................................................................................... 14
4.1.2 Doors Format Exchange............................................................................................................................. 15
4.1.3 Altis to correct ............................................................................................................................................ 15
4.1.4 Exception sheets list.................................................................................................................................... 16
4.1.5 Software components list from PSA: NON APPLICABLE......................................................................... 16
4.2 PERFORMANCE REQUIREMENTS................................................................................................................. 16
4.2.1 CPU load .................................................................................................................................................... 16
4.2.2 Memories occupancy .................................................................................................................................. 17
4.2.3 Stack management ...................................................................................................................................... 19
4.3 INTERFACES REQUIREMENTS ...................................................................................................................... 19
4.3.1 Context Diagram......................................................................................................................................... 19
4.3.2 CAN network(s)........................................................................................................................................... 20
4.3.3 Serial links .................................................................................................................................................. 21
4.3.4 Wired inputs/outputs ................................................................................................................................... 21
4.4 OPERATIONAL REQUIREMENTS................................................................................................................... 22
4.4.1 Software life cycle....................................................................................................................................... 22
4.4.2 Life time ...................................................................................................................................................... 22
4.4.3 Ergonomics................................................................................................................................................. 22
4.4.4 Safety........................................................................................................................................................... 23
4.4.5 Product quality ........................................................................................................................................... 23
4.4.6 Intrusion protection .................................................................................................................................... 23
4.4.7 System resources......................................................................................................................................... 23
4.5 CONSTRAINT REQUIREMENTS ..................................................................................................................... 23
4.5.1 Rules and consumerism: ............................................................................................................................. 23
4.5.2 Weight and Physical characteristics........................................................................................................... 23
4.5.3 Design and manufacturing.......................................................................................................................... 24
4.5.4 Product identification ................................................................................................................................. 28
4.5.5 Traceability and configuration management .............................................................................................. 31
4.5.6 Transport, storage and conditioning........................................................................................................... 32
4.5.7 Flexibility and extension............................................................................................................................. 32
4.5.8 End of life.................................................................................................................................................... 33
4.5.9 Environment conditions .............................................................................................................................. 33
4.5.10 Planning................................................................................................................................................. 33
4.6 INTEGRATION AND VALIDATION REQUIREMENTS................................................................................. 33

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 4/34
4.6.1 Tests and Validation ................................................................................................................................... 33

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 5/34
PURPOSE
The purpose of this document is to specify the requirements related to the software
development of the part “EPS CMP” and the associated test benches.
This document belongs to the contractual documentation of consultation.
1 SCOPE OF APPLICATION
1.1 DEVELOPMENT CONTEXT
The EPS Software is expected to be used for multiple vehicles on the CMP plate-form.
The SW VC2 will be used for:
- EL1 D34
Deliveries Date:
- SW Level 3: 19/02/2017
- SW Injection Fault 19/04/2017
1.2 GENERAL SYSTEM DESCRIPTION
The general architecture of the system is described in [001].
The present document lists the requirements concerning the software
2 MENTIONED DOCUMENTS
2.1 REFERENCE DOCUMENTS
The documents listed below helped elaborating the present one. They are not communicated
systematically.
Lien Title Reference Date Diffusion
[001] Ensemble de pilotage <réf> <date> Interne PSA
[100] DFCC <réf> <date> Interne PSA
[101] Norme A10 0310 ind C <réf>
[102] Referential MDL CSEE_CLCO06_0582 <date> Interne PSA
[103] Dossier de justification du modèle de ce document CSEE_CLCO06_0512 <date> Interne PSA
[104] Dossier de justification de ce document 01552_12_10540 <date> Interne PSA
[105] Recueil des exigences relatives à l’implémentation d’une
solution de bypass logiciel dans un calculateur de
développement fournisseur
CSEO_APPT07_0171
6.0
<date> Interne PSA
[106] Exigences fonctionnelles IGMP pour consultations
fournisseurs de calculateurs dédiés aux organes
CSMT_IMOT06_0092
3.0
NA Interne PSA
[107] Model SW Notebook CSEE_CLCO06_0132 6.0 Interne PSA
[200] Pratique de l’ingénierie des exigences DPTA_QMGT06_0144 <date> Interne PSA

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 6/34
1.0
[201] model de CPPR 01552_11_06465 1.0 Interne PSA
2.2 APPLICABLE DOCUMENTS
The following documents, as well as the present one are part of a consistent set. They can be
provided on request.
Lien Title Reference Date Diffusion
[003] CDC SDF 01452_13_00052 <date> Diffusable
[005] CDC HW
01552_14_01888
<date> Diffusable
[007] MRF DA_AQF07_0001_EX <date> Diffusable
[008] CPPR SW 01552_12_10720 <date> Diffusable
[009] CPPR SYSTEM
01598_14_01050
<date> Diffusable
[010]
Rapid prototyping requirements Software Bypass
CSEO_APPT07_0171 <date> Diffusable

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 7/34
2.3 REQUIREMENTS DOCUMENTS ORGANISATION
The present document is the document [006].
[006]
[004]
[007]
[008]
[005]
CDC CALCULATEUR
PROGRAMME
PROGRAMMED ECU
Exigences applicables à l’ensemble
du calculateur
CDC HW
HW SPECIFICATION SHEET
Contraintes HW
Tenue environnement
Contraintes dimensionnement
Définition des E/S du système
Profils de mission
Contraintes mécaniques
Diagnostique HW
CDC SW
SW SPECIFICATION SHEET
Contraintes temps réél
Fonctions de service
Téléchargement
Diagnostique fonctionnel
Diagnostique SW
CPPR Projet
Special Clauses and Results Schedule
Exigences Pilotage projet et
processus de développement
Exigences Livrables HW
Exigences Livrables SW
Exigences livrables SDF
Exigences livrables CSMT
DOCUMENTS
APPLICABLES
APPLICABLE
DOCUMENTS
CDC SDF
SAFETY SPECIFICATION SHEET
Exigences de sûreté de
fonctionnement
[003]
DOCUMENTS
APPLICABLES
APPLICABLE
DOCUMENTS
DOCUMENTS
APPLICABLES
APPLICABLE
DOCUMENTS

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 8/34
3 TERMINOLOGY
3.1 GLOSSARY
The following terms are used throughout the documents.
Technical term Description
Autodiagnostic
The ECUs own an auto diagnostic function. It means that the monitoring of
the sensors, actuators, the CAN bus and the ECU itself is done by the
software. The purpose of the function is:
- To detect the failures or functional anomalies
- Ensure the safety of the passengers using emergency strategies
- Avoid the failure propagation by using degraded modes which gives the
possibility to reach a garage.
- Record and raise the failures in order to make the reparation more
efficient and alert the driver if necessary
Functional bypass The purpose of the functional bypass is to bypass all the outputs of a
function clearly delimited in the ECU functional architecture. Example:
speed regulation/limitation.
Software bypass The purpose of the software bypass is to bypass different variables of the
ECU software, which are not necessarily related to a specific function.
Example : the order of the EGR position, in degrees
Bypass in “standalone”
mode
The software bypass is automatically activated at the ECU and RPU power
on, without any intervention of the user.
Specification sheet
Document gathering all the requirements of the system or a part of the
system.
It results from the design file of the upper-level system.
The specification sheet is the technical component of the RfQ file.
Bypassable ECU Development ECU equipped with a bypass interface and programmed with
software implementing bypass variables.
Calibration Set of parameter values
CAN IS
Inter-system CAN network dedicated to driving functions(engine, gearbox,
braking system, suspension, …)
Software component
Source code in C ANSI and detailed specification of the API supplied by
PSA.
Third party software
component
Software component used by the supplier but developed by a third party
Reference document
Document (standard, specification, architecture and internal design
document) used to write the technical specification.
Document applicable
Document containing a specifying part, which can be a part of the technical
specificaiton and the document called by the technical specification.
A2L file The description file ASAP, or A2L file, is used to describe the ECU internal
memory configuaration. It includes information about the different memory
structures and allocations, the conversion procedures for the representation
physical units, the descriptions of the measurement and characteristics
channels and the description of the means to access to the ECU by the CAN
bus.
Core functions Functions shared between the software development partners
Specific functions In the context of partnership between car manufacturers, functions specific

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 9/34
to the software development partners
Software
Set of programs, process, rules and documentation related to a data
processing system. The software includes in particular the applicative
software and the calibration.
Applicative software
Executable software, when associated to the calibration executes the ECU
functions.
Generic software
Software used for tuning and development. It cannot be industrialised. It is
applicative software with a development calibration.
Master software
Binary file in the download format used by the PSA plants or after-sales
(.ulp or .cal). It contains particularly the software identification data in the
ECU environment. This software is specific to a vehicle application and it
can be industrialised.
Part partnership Partnership for the development of an automotive part.
Stack
The stack is a data structure based on the concept “Last In, First Out”
(LIFO). Here, the stack is actually the call stack which contains whole or
part of the call arguments of functions and procedures, as well as return
addresses. It contains also a dedicated area for local variables. The stack is
then composed of stack frames which contain, for each imbricated
procedure in execution, the arguments, the local variables and the return
point. The system stack saves the context (registry values, return point, …)
when exceptions and interruptions occur. In order to be read and written,
the stack is located in RAM.
Bypass point = bypass
variable
Software variable prepared to be modifiable in real time by an external
bypass ECU.
Prototypes
Product compliant with the specifications which has been realized on non-
serial production means.
Vehicle partnership Partnership for a vehicle development.
Technical specification
Document gathering all the coherent requirements of the specified system.
The technical specification describes what the system shall do. It does not
describe how it shall do it. The technical specification is the final result of
the specification process
It refers to interface specifications.
The technical specification is the technical component of the contract
Download
Operation performing upgrades of the applicative software and/or
calibrations in the ECU.
Télécodage
Operation associating a given vehicle-specific configuration to the TCU.
The set of parameters related to this configuration is selected.
Tests
4 types of tests are identified:
 Unit tests
 Integration tests
 Functional tests
 Non-regression tests
A test procedure gathers all the tests that must be performed to validate a
software function, as well as the expected results.
Supplier functional tests
Functional tests run by the supplier to ensure that the software respects the
design choices done by the supplier.
PSA functional tests
Functional tests run by the supplier to ensure that the software respects the
PSA requirements

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 10/34
Validation
Activities to perform in order to determine if the object (software function)
is conform to the expectations.
3.2 ACRONYMS
Abréviation Signification
ACCP Advanced Common Rail Combustion Process
AD A Définir
ADC Anti Démarrage Codé
APC APrès Contact
API Application Programm Interface
APV APrès-Vente
MCD
ASAM-MCD 1MC ou
ASAP 1
ASAM-MCD 2MC ou
ASAP 2
ASAM-MCD 3MC ou
ASAP 3
pour Measurement, Calibration and Diagnostics
- ASAP 1 relève du protocole
- ASAP 2 relève du format de description des données. ex : fichier A2L
- ASAP 3 relève d’une interface logicielle.
AQMPP Assurance Qualité par la Maîtrise du Produit et du Processus
BSI Boîtier de Servitude Intelligent
CAN Controller Area Network
CCP Can Calibration Protocol : protocole de calibration utilisant le bus CAN
comme vecteur de transmission
CDC Cahier Des Charges
CMM Contrôle Moteur Multifonction
CPPR Clauses Particulières et Planning de Résultat
CRCPP Can Rapid Control Prototyping Protocol. Protocole de communication basé
sur le CCP pour bypass développé par Ford.
CPU Central Processing Unit
CRQ Change Request (demande d’évolution)
DMS DéMarrage Série
E/S Entrées / Sorties
ECCS Extreme Conventional Combustion System
ECU Electronic Control Unit
EOBD European On Board Diagnostic
ETK Emulator TastKopf (ETAS) : interface de mesure/calibration et prototypage
rapide de la société ETAS.
FNR FourNisseuR

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 11/34
Abréviation Signification
FRIC Fonction de Refroidissement Intégré au Calculateur
GAP Gestion d'Alternateur Piloté
HW HardWare
ISA Ingénierie Système Automobile
IT InTerruption
LDA Logiciel D’Application
LDB Logiciel De Base
LVV Limiteur Vitesse Véhicule
MIL Malfunction Indicator Lamp
MPO Mulet Porte Organe
MRF Document Management Relation Fournisseur
NVRAM Mémoire non volatile
PMH Point Mort Haut
POD / GSI Plug On Device / Generic Serial Interface (dSPACE): interface de
mesure/calibration et prototypage rapide de la société dSPACE.
PRSEL PRototype Série En Ligne
PRSHL PRototype Série Hors Ligne
RCD Réveil Commandé à Distance
RTE Run Time Environment
RPU Rapid Prototyping Unit : calculateur de prototypage rapide
RVV Régulateur Vitesse Véhicule
SDF Sûreté De Fonctionnement
SOP Start Of Production
SRU Stade Représentatif Unique
SW SoftWare
TBD To Be Defined
TI Temps d'Injection
UCE Unité de Commande Electronique
UP Usine de Production
WCET Worst Case Execution Time
XCP X Calibration Protocol : protocole de calibration remplaçant et standardisant
le CCP. utilise plusieurs vecteurs de transmission possibles : USB, CAN,
Ethernet. CCP et XCP on CAN sont standardisés par ASAM MCD 1a
ZA Zone d’Authentification
ZI Zone d’Identification
The abbreviations that are used throughout the document are listed in the table below:

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 12/34
Abbreviation Meaning
ADC Immobilizer
API Application Program Interface
AQMPP PSA quality assurance methodology in the development phase (Assurance
Qualité par la Maîtrise du Produit et du Processus)
CAN Controller Area Network
CDC Specification notebook (Cahier Des Charges)
CMM Engine Control Unit (Contrôle Moteur Multifonction)
CMQ Quality Management Clauses
CPU Central Processing Unit
CRQ Change Request
DMS SOP (DéMarrage Série)
I/O Input/Output
ECU Electronic Control Unit
GAP Smart Alternator management (Gestion d'Alternateur Piloté)
HW HardWare
MPO Mule vehicle (Mulet Porte Organe)
PRSEL PRototype Série En Ligne
PRSHL PRototype Série Hors Ligne
SOP Start Of Production
SRU First functionally representative prototype (Stade Représentatif Unique)
TBD To Be Defined
AZ Authentication Zone
IZ Identification Zone

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 13/34
3.3 DOCUMENT RULE
Throughout the document, the requirements are identified by the following format:
[Numéro] Libellé de l’exigence. /[Number] Requirement text

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 14/34
4 REQUIREMENTS
PSA requirements are described in this chapter and are applicable for the software
development.
4.1 FUNCTIONAL REQUIREMENTS
PSA software requirements that described the applicative functions (in nominal mode and
degraded mode) and services functions are listed in this chapter.
The applicable specifications list that is communicated in this chapter is contractual. Each
applicable document must be seen as a requirement.
4.1.1 Specifications list:
See “Lotissement sheet” for complete specification list:
http://docinfogroupe.inetpsa.com/ead/doc/ref.20655_15_00269/v.vc/fiche
DOCUMENT TITLE
DOCUMENT REFERENCE
(DOCINFO)
VC2
EPS BMPV Software Requirement Notebook - CDC SW 01552_14_01306 7.0
Safety dependability and durability requirements generic 01452_13_00052 3.0
Condition Démarrage/Arret Assistance 01452_12_00155 7.0
STT Phase 2 - STTd 01452_09_00092 7.3
IASV_COFS08_1406_SpecificationTechnique CityPark Additif
DAE
00998_12_00471 4.0
STO EPS LxA Function 01140_14_00283 9.0
ST Multimode Direction assistée 01552_13_01129 4.0
Note Technique AVA 01554_10_04507 2.0
Technical Note Diversity Management - Multi-Tuning 01552_14_06649 2.0
TS Produce RCA with estimated and memorized offset CAV3 virtual
EPS
01552_15_07461 3.0
ST diag et DTC EPS GENERIC 01452_12_00134 3.0
Matrice applicative diagnostique DAE générique 01452_13_00094 5.0
DAE 1v5 : DC_TI_20_Mécanismes du JDD AEE2010 02016_14_00911 1.0
DAE 1v5 : DC_TI_701_TS Application Layer for Diagnostic 02016_14_00904 1.0
DAE 1v5 : DC_TI_702_TS UDS generic mechanisms 02016_14_00905 1.0
DAE 1v5 : DC_TI_703_TS UDS Configuration 02016_14_00906 1.0

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 15/34
NA - DCTI72 intégration des services de communication 01552_14_01924 3.0
DAE_BCUV_CMP_UDS2_V2 (ODX) 0000003319 00 1.0
DAE 1v5 : DC_TI_705_TS Reprogrammation ECU 02016_14_00907 1.0
DAE 1v5 : DC_TI_706_TS Flash Eprom Application 02016_14_00908 1.0
DAE 1v5 : DC_TI_707_TS Electronic Integration and putting ECUs
into operation
02016_14_00909 1.0
Fonction de cryptage partie 1 (confidentiel) 96 298 009 9A A
Fonction de cryptage partie 2 (confidentiel) 96 298 108 9A A
Fiabilisation_de_l’endormissement_des_organes_DIRA.pdf 01554_10_05004 6.0
CAN_Messaging_and_FH__EPS_BVH1v5 01552_14_04469 4.0
Annex_CAN_Messaging_and_FH_EPS_BVH1v5_01552_14_04469 01552_14_04557 3.1
STE Sécurisation Trames par Checksum et Compteur de Processus
(IndH) - 96.598.426.99
01554_10_00970 H
Specification Technique d’Interfaces Reseaux - Regles de
Communication reseaux CAN
00948_10_01988 1.0
NB: confidential documents can be transmitted with a confidentiality engagement
4.1.2 Doors Format Exchange
In order to have a common attribute for Doors exchange, the following documents shall be shared
agreed for the program Init:
[800] Doors_Attributs_Module_type_EPS_1V5 01552_14_06688 1.0
[801] RIF_Supplier_View
4.1.3 Altis to correct
TE TITLE GRAVITY
6584049 FONC : Assistance Start Up on IGKey OFF C
6947521 Download : bad answer with the RTE request C
6971255 The Diagnostic Session Control failed C
6976949 2701 request Sub-Function not supported in extented session but accepted by EC C
7182189 "Start up and shut down" function : A1 condition : only 2 frames to stop Assistance instead of 3 frames C
7531346 Several DTC appears after a wake up if the frames are not send during IGN OFF B
7531408 [STTd] : Stop quel que soit l'angle au volant au 1er démarrage (convergence angle volant Nexteer trop long) B
7711775 CityPark: CPK status is "unavailable" instead of "invalid" if engine state is invalid C
7722265 UDS : Powerlatch flag state DID is not available in Default Session (0x01) C
7722317 UDS : The wrong NACK code is obtained on several DID in RDBI (0x22) service C
7722354
UDS : Negative response is obtained instead of positive expected on several DID in RDBI (0x22) service in
Functional Addressing
C
7722373 UDS : ECU does not respond on CDTCS (0x85) instead of positive response expected in Functional Addressing C

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 16/34
7725262
FH-CAN : in 2004 architecture : the DTC U1218-81 never appears when 552h frame for Year, Day or Seconds
are out of range
C
7734110 UDS : ECU respond positively on CDTCS (0x85) instead of negative response expected in safety condition 2 C
7818337 Variant Coding : If no variant coding was don default value of CAVPR is not AVA as expected C
7851406 The warning lamp of EPS switches on constantly after a rehabilitation of power supply low. B
7851406 The warning lamp of EPS switches on constantly after a rehabilitation of power supply low. B
8047148
[LXA_v2.3_P0] : EPS_STATE_LKA : The obtained value 4 is different than expected 0 when we create a
undervoltage or overvoltage
B
8048258
[LXA_v2.3_P0] : when driver applies the torques, when he stops to apply torque, STEERWHL_HOLD_DRV
switches to 0 after 1.1sec instead of 0.2 sec (DELAY_STEER_WL_HOLD_DETECTION)
B
8051825
[LXA_V2.3_P0] : Detection of driver activity by LXA inhibition is not handled when EPS_STATE_LKA is
unauthorized
A
8343039 CANHS: [FNR]# Bad DTC. C
8343121 CANHS: [FNR]# Error C_BusOff C
8352427
CANHS: [FNR]# Requirement unavoidable concerning the Network Communication management are untested
DAE NEXTEER CMP EMP1V5
B
8514327
[LXA_V2.3_P0] : Inhibition time after driver's activity is not handle from the end of the activity but from the
beginning
8520813 Multimode: If vehicle speed > 0 km/h the switch between two modes is not allowed.
4.1.4 Exception sheets list
EPS_1V5_SW-ORG_CDC_5.1_30 (1.0)
Any exception from previous program isn’t accepted.
Any exception must be presented to PSA for approval.
/EPS_1V5_SW-ORG_CDC_5.1_30
4.1.5 Software components list from PSA: NON APPLICABLE
4.2 PERFORMANCE REQUIREMENTS
The performance requirements are integrated in the functional specifications listed in §5.1 and
in the operational & constraints requirements.
The software shall be designed to have the possibility to add new functionalities or to tune its
parameters before & after the first DMS.
4.2.1 CPU load
GEN_SW-ORG_CDC_5.2_10 (1.1)
The supplier shall implement in its software a way to measure in real time the consumed
CPU load.
/GEN_SW-ORG_CDC_5.2_10

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 17/34
PSA diagnostic tools should be able to read the CPU load rate computed over 1 second
CPU load reading access shall be inhibited on commercialized software (master software
after the PRSEL2 milestone).
For the functional content described in §5.1, the first SOP software shall not use more than
70 % CPU load.
For any product phase (development, serial production, maintenance), the maximum CPU
load used by any software delivered to PSA shall not be above 90 %.
4.2.2 Memories occupancy
GEN_SW-ORG_CDC_5.2_110 (2.1)
Removed
GEN_SW-ORG_CDC_5.2_112 (2.2)
For the first SOP and for the functional content that is described in §5.1, the software shall
not use more than 70 % of the RAM memory.

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 18/34
GEN_SW-ORG_CDC_5.2_113 (2.2)
The software shall never use more than 95% of ECU RAM in any phase of the product life
(development, production, maintenance).
GEN_SW-ORG_CDC_5.2_114 (2.1)
The software shall not use more than 70% of ECU NVM at first DMS, for the overall
functional content described in §5.1.
GEN_SW-ORG_CDC_5.2_115 (2.2)
The software shall never use more than 95% of ECU NVM in any phase of the product life
GEN_SW-ORG_CDC_5.2_116 (2.1)
The software shall not use more than 70% of ECU ROM at first DMS, for the overall
functional content described in §5.1.
GEN_SW-ORG_CDC_5.2_117 (2.2)
The software shall never use more than 95% of ECU ROM in any phase of the product life

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 19/34
4.2.3 Stack management
GEN_SW-ORG_CDC_5.2_230 (2.1)
Removed
/GEN_SWORG_CDC_5.2_230
4.3 INTERFACES REQUIREMENTS
4.3.1 Context Diagram
4.3.1.1 Purpose of the control unit
The EPS ECU must allow the control of an electrical motor which will assist the driver in its
operations with the wheel.
The EPS must also ensure some vehicle functions allocated on several calculators.
For the function communication, the ECU will use the CAN IS Network.
4.3.1.2 Global overview
The schematic below is an overview of the different elements that interact with <EPS
EPS_1V5>, engine control unit
Overview without Angle Sensor (AVA function) or with CAV Virtual (Optional):
Boitiers électroniquess
Logiciel
DAE +
Fichier de calibration
AVA
BSI
Modules
logiciels PSA
DAE
Pilotage du
moteur DAE
Liaisons filaires
Réseau CAN intersystème
ESP
Echange de données
CMM
Logiciels
DIAG

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 20/34
Overview with deported angle sensor (CAV Class 3):
Boitiers électroniquess
Logiciel
DAE +
Fichier de calibration
BSI
Modules
logiciels PSA
DAE
CAV
Pilotage du
moteur DAE
Liaisons filaires
Réseau CAN intersystème
ESP
Echange de données
CPK
CMM
Logiciels
DIAG
4.3.2 CAN network(s)
The ECU is connected to end of line and after sales tools and also to other vehicle control units
via CAN.
4.3.2.1 Protocols
The requirements related to communication are expressed in the list of functional
specifications available in §5.1.
4.3.2.2 Data description
The requirements concerning CAN transmitted data are described in the functional
specifications (see §5.1).

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 21/34
4.3.3 Serial links
4.3.3.1 LIN/BSS link
Removed
4.3.3.2 K line
Removed
Removed
4.3.3.3 Protocols
The requirements concerning communication protocols are described in the functional
specifications (see §5.1).
4.3.3.4 Data description
The requirements concerning Data are described in the functional specifications (see §5.1).
4.3.3.5 Bypass links:
Not applicable.
4.3.4 Wired inputs/outputs
4.3.4.1 Wired inputs/outputs signal processing
The requirements are specified in the document “wired signals diagnosis” in §5.1.2
4.3.4.2 Electrical diagnosis of wired signals
The requirements are specified in the document “wired signals diagnosis” in §5.1.2

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 22/34
4.4 OPERATIONAL REQUIREMENTS
4.4.1 Software life cycle
Software environment is defined by the 4 following states:
 Development phase during which software is integrated into development ECUs and
representative ECUs to industrialized products. The software can also be downloaded
by PSA with development tools.
EPS_1V5_SW-ORG_CDC_5.4_10 (1.0)
The PSA download procedure should be used from the beginning of the program.
If not, the supplier must provide the downloading procedure (scenario, tool, Guideline,).
The procedure must be approved by PSA.
/EPS_1V5_SW-ORG_CDC _5.4_10
 For Pre-series and series phases, 3 scenarios exist:
o The application software and the calibration file are downloaded by the
supplier.
o The application software is downloaded by the supplier and the calibration file
is downloaded by the car maker in end of line.
o The application software and the calibration file are downloaded by the car
maker in end of line.
EPS_1V5_SW-ORG_CDC_5.4_20 (1.0)
In its offer, the supplier will suggest its scenario. The scenario must be approved by PSA.
/EPS_1V5_SW-ORG_CDC _5.4_20
The “customer use” phase, where the software is used within vehicles by Peugeot or Citroën
customers.
 The after-sales phase, where the software is diagnosed and updated.
The software phases (boot, wake-up, download, diagnostics…) are described in § 5.1.
4.4.2 Life time
Software lifetime starts by the first delivery to PSA until end of maintenance of the associated
ECU. (See document [005])
4.4.3 Ergonomics
Sans objet / Not applicable

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 23/34
4.4.4 Safety
Transferred to CPPR...
Transferred to CPPR...
4.4.5 Product quality
Apart from the safety aspects defined in chapter 5.4.4, the software quality requirements are
specified into the documents [007] and [008].
4.4.6 Intrusion protection
In order to avoid software hacking, PSA requests that the supplier implements a function to
secure the access to programmable memory. This function is described in two confidential
documents that are not transmitted on electronic support. They are transmitted upon
request during the “request for quotation” phase
4.4.7 System resources
The resources requirements are included in the Hardware specification.
4.5 CONSTRAINT REQUIREMENTS
4.5.1 Rules and consumerism:
4.5.2 Weight and Physical characteristics
Cf. CDC HW (réf.)

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 24/34
4.5.3 Design and manufacturing
4.5.3.1 Design process
Removed. /
4.5.3.2 Software components
Not applicable
4.5.3.3 Software architecture
EPS_1V5_ORG_CDC_5.5_20 (1.0)
The Supplier must communicate its Autosar ICC level conformity, if used for its software
architecture.
EPS_1V5_SW-ORG_CDC_5.5_30 (1.0)
The supplier must deliver unique software compatible with all the program applications.
EPS_1V5_SW-ORG_CDC_5.5_40 (1.0)
The supplier will present its strategy for the software diversity to be compatible with all the
applications. (Compilation, End of Line configuration, calibration, Variant coding, others.).
EPS_1V5_SW-ORG_CDC_5.5_50 (1.0)
The supplier must identify all the HW-SW interactions impacted by the diversity.
EPS_1V5_SW-ORG_CDC_5.5_60 (1.0)
The supplier delivers an exhaustive document with the functional decomposition of its
software and the management of the associated diversity

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 25/34
EPS_1V5_SW-ORG_CDC_5.5_70 (1.0)
For each function, the supplier delivers the modular decomposition (Invariant and variant
parts).
Invariant part: Not impacted by the vehicle diversity.
Variant part: Parameters/strategies to adapt the software for the Vehicle applications.
EPS_1V5_SW-ORG_CDC_5.5_80 (1.0)
For each function, the supplier indicates its maturity.
EPS_1V5_SW-ORG_CDC_5.5_90 (1.0)
The supplier should privilege the parameters calibration by variant coding and/or
downloading to support the applications diversity.
EPS_1V5_SW-ORG_CDC_5.5_100 (1.0)
The supplier delivers the list of all the function calibration parameters. The list must be
approved by PSA for each function. (Refer also to [007])
4.5.3.4 Coding tools and language
GEN_SW-ORG_CDC_5.5_180 (1.1)
To generate the software release, the supplier shall only use the coding tools and languages
described in the development plan.

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 26/34
4.5.3.5 Calibration methods and tools:
GEN_SW-ORG_CDC_5.5_340 (1.1)
Each calibration parameter has to be set in priority:
- either to a specific value communicated by PSA project team,
- or to a failure value indicated in PSA specifications, if no specific value has been
indicated.
GEN_SW-ORG_CDC_5.5_370 (1.1)
NA
GEN_SW-ORG_CDC_5.5_380 (1.1)
With each software version, the supplier has to deliver generic software with a calibration
that allows testing the new implemented functions.
EPS_1V5_SW-ORG_CDC_5.5_310 (1.0)
During development phase, all the tuning parameters shall be tunable.
The tuning parameters are indicated within specifications.
EPS_1V5_SW-ORG_CDC_5.5_320 (1.0)
The Software/Calibration parameters mapping must be approved by PSA at each software
freeze review.
The list of all calibration parameters must be shared at each freeze review and must respect
the requirement GEN-SWORG-CPPR.701 (1.0) in CPPR [007].

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 27/34
EPS_1V5_SW-ORG_CDC_5.5_330 (1.0)
During development phase, all the Safety barrier parameters should be tunable.
The freeze of the values must be presented and approved by PSA.
EPS_1V5_SW-ORG_CDC_5.5_340 (1.0)
The Tuning methods and tools are suggested by the supplier and must be approved by PSA.
The Tuning method shouldn’t change during all the project life. Any modification must be
approved by PSA.
EPS_1V5_SW-ORG_CDC_5.5_350 (1.0)
The Tuning methods and tools must permit to memorize the tuned values in the ECU
memory and to generate a parameter file readable by PSA tools.
PSA should be able to memorize the value following a tool request or by an action on APC
signal.
EPS_1V5_SW-ORG_CDC_5.5_360 (1.0)
The supplier shall deliver the calibration methods for the functions under its responsibility
in order to identify the constraints on PSA (planning, Deliverable, Impact on PSA functions
and parameters
EPS_1V5_SW-ORG_CDC_5.5_370 (1.0)
During the tuning phase, PSA should be able to read the PSA data values in the EPS
memory using the Tuning tool.

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 28/34
4.5.4 Product identification
4.5.4.1 Generic software identification
GEN_SW-ORG_CDC_5.5_400 (1.1)
The Generic software shall be identified by the supplier with a unique reference.
GEN_SW-ORG_CDC_5.5_410 (1.1)
The unique reference of the generic software shall appear on/with the delivery.
4.5.4.2 Master software identification
GEN_SW-ORG_CDC_5.5_450 (1.1)
Master software and calibration has to be identified using the reference communicated to
the supplier via an officialisation sheet.
GEN_SW-ORG_CDC_5.5_460 (1.1)
The unique reference of the master software shall appear on/with the delivery.

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 29/34
4.5.4.3 EE identification:
The definition of the following zones is described in DC_TI_XX UDS specification.
4.5.4.4 Identification Zone
Description Format Conversion
Value at
supplier delivery
Signature de la flash (*) $xx $xx Hexa $00 00
Réservé $xx $xx Hexa $00 00
Code fournisseur $xx Hexa $13
Système $xx Hexa $6A
Date de fabrication (DATE-1)
Ex : 27 July 2001
27 d = $1B
07 d = $07
01 d = $01
$1B0701
$xx $xx $xx Hexa To fill by Supplier
Application $xx Hexa $B1 for Super Low 1 (PSA Boot)
$B2 for Low 1 (PSA Boot)
$B3 for Medium 1 (PSA Boot)
$B4 for Medium 3 (PSA Boot)
$B5 for High 3 (PSA Boot)
$4B for Medium 3 (DFM Boot)
$5B for High 3 (DFM Boot)
Version du logiciel * $xx Hexa $00
Edition du logiciel: octet de poids fort * $xx Hexa $FF
Edition du logiciel: octet de poids faible * $xx Hexa $00
Date de téléchargement (DATE-2) * $xx $xx $xx Hexa To fill by Supplier
Lieu du téléchargement $xx Hexa $FE
Signature de l’outil de téléchargement $xx $xx $xx Hexa $00 00 00
Nombre de téléchargement
Livré Téléchargé = 01
Livré Télé mais op à réaliser = FE
$xx Hexa $FE
N° du fichier « .cal » in BCD 96 $xx $xx $xx 80 Hexa $92 $91 $48
See DC_TI_xx for the associated requirement
4.5.4.5 Application Key:
Description Format Conversion Valeur à la livraison .ULP/CAL
CLE_APPLI $xx $xx Hexa $21 $05
See DC_TI_xx for the associated requirement

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 30/34
4.5.4.6 Code UCE
GEN_SW-ORG_CDC_5.5_440 (1.1)
Code UCE to use in the S0 frame of the .ULP/CAL files.
DESCRIPTION FORMAT CONVERSION VALEUR A LA LIVRAISON .ULP
CODE UCE $xx Hexa $E9
4.5.4.7 Authentication zone
N° d’octet Description Format Conversion Code
#3 #4 #5 #06 #7
Part number
(= equipment ref. number
including HW+Boot)
$xx$xx$xx$xx$xx B.C.D Part number
#8 #9 Code fournisseur $xx $xx HEXA $00 $13
#10 #11 #12 #13
#14
HW number
(HW+Boot)
$xx$xx$xx$xx$xx B.C.D
$98 $28 $30 $95 $80
(MPPV1 with TC)
$98 $28 $30 $96 $80
(MPPV3 with TC)
$98 $28 $40 $49 $80
(MPPV1 Without TC)
#15 #16 Indice d’évolution du logiciel $xx $xx HEXA $F5 0x
#17 #18 Indice d’évolution des calibrations $xx $xx HEXA
$XX XX
(CAL Nexteer TBD)

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 31/34
#19 Indice d’évolution du calculateur
(écrit en fin de ligne Nexteer pour
indiquer la version HW Theta)
$xx HEXA $XX
#20 Nombre des paramètres associés
(il n’a pas de lien avec les
variables de contextes associés)
$xx HEXA $01
#21 #22 #23 #24 Type application $xx $xx $xx $cc HEXA $FF $FF $FF $FF
4.5.4.8 Définition du contenu de l’étiquette CEM
N° octet Nom des paramètres Conversion Codes
#3 Fournisseur Hexa $13
#4 à #8 Initiales de l’organe ASCII ‘DAE ’ : $44 41 45 20 20
#9 à #24 Champ libre ASCII
TBC
CMP ' :
$43 4d 50 20 20 20 20 20 20 20 20 20
#25 Indice CEM Hexa 00
4.5.4.9 Serial Number Traceability:
DESCRIPTION SIZE FORMAT VALUE
ECU Serial Number Data Identifier $XX $Hex 13
Serial Number $XX … $XX ASCII Serial Number
4.5.4.10 Variant Coding Definition:
See Application Note “Technical Note Diversity Management - Multi-Tuning”
4.5.5 Traceability and configuration management
GEN_SW-ORG_CDC_5.5_570 (1.1)
Each software module (file) shall be identified by a unique reference and a version number
and a date.

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 32/34
GEN_SW-ORG_CDC_5.5_580 (1.1)
Each specification of a software module shall be identified by a unique reference and a
version number or a date.
GEN_SW-ORG_CDC_5.5_590 (1.1)
Each requirement of each supplier specification shall be identified by a unique reference.
4.5.6 Transport, storage and conditioning
GEN_SW-ORG_CDC_5.5_720 (1.1)
The supplier shall ensure the software will not be damaged by the storage, the transports or
the conditioning
GEN_SW-ORG_CDC_5.5_730 (1.1)
If the software is delivered via email, it is mandatory to deliver it also on a physical
support, to be defined together with the supplier and PSA project during RFQ phase.
4.5.7 Flexibility and extension
GEN_SW-ORG_CDC_5.5_740 (1.1)
The software shall be compatible with two consecutive hardware versions. (Especially
between B sample and C sample) Should there be derogation to this requirement, it has to
be discussed no later than during the software content freeze review
GEN_SW-ORG_CDC_5.5_750 (1.1)
Removed

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 33/34
EPS_1V5_SW-ORG_CDC_5.5.750 (1.1)
The calibration “.Cal” (defined in document [301] and [302]) is downloaded in PSA plant
and after-sales using PSA tools.
/EPS_1V5_SW-ORG_CDC_5.5.750
EPS_1V5_SW-ORG_CDC_5.5.760 (1.1)
The generic and Master software file must have the “.ULP” format (defined in [301] [302])
It must be possible to download the “.ULP” by using the PSA plant and After-sale tools.
/EPS_1V5_SW-ORG_CDC_5.5.760
4.5.8 End of life
4.5.9 Environment conditions
4.5.10 Planning
4.5.10.1 Global software development planning
GEN_SW-ORG_CDC_5.5_810 (1.1)
The software development shall be consistent with the overall project schedule, which major
milestones are given in the document “Special Clauses and Results Schedule”.
4.5.10.2 Software development planning
Please refer to Project Planning:
https://docinfogroupe.psa-peugeot-citroen.com/ead/doc/ref.20655_16_00108/v.vc/fiche
4.6 INTEGRATION AND VALIDATION REQUIREMENTS
4.6.1 Tests and Validation
The validation process and associated human and technical resources shall be described in the
development plan (see requirement [SW5.5_30]).

DAE CMP : SW VC2
30/06/2017 01552_14_01306 8.0 CMP 34/34
The supplier shall perform tests that guarantee no regression between two software
versions.

01552_14_01306_8.0_EPS_CMP_SW_VC2_Notebook.doc

Recommended

Recommended

More Related Content

Similar to 01552_14_01306_8.0_EPS_CMP_SW_VC2_Notebook.doc

Similar to 01552_14_01306_8.0_EPS_CMP_SW_VC2_Notebook.doc (15)

More from monutilisation0

More from monutilisation0 (8)

Recently uploaded

Recently uploaded (20)

01552_14_01306_8.0_EPS_CMP_SW_VC2_Notebook.doc