12 09368 v1 0 DC Ti 71 Application Flash Eprom Reference A 5.0 A Dae BMPV
12 09368 v1 0 DC Ti 71 Application Flash Eprom Reference A 5.0 A Dae BMPV
12 09368 v1 0 DC Ti 71 Application Flash Eprom Reference A 5.0 A Dae BMPV
Rédacteur(s)/Author(s) :
Nom/Name : Entité/Entity : Date/Date : Signature/Signature :
MEUDEC Delphine DTI/DPMO/CSEE/APPT 07/01/2013
ROCHETTE
François
LIN Wenyuan
Verificateur(s)/Inspector(s) :
Nom/Name : Entité/Entity : Date/Date : Signature/Signature :
BILI Franck DTI/DPMO/QMS/QSEE/CEMD 07/01/2013
Approbateur(s)/ Approved By :
Nom / Name : Entité / Entity : Date/Date : Signature/Signature :
LOPEZ Thierry DTI/DPMO/CSEE/APPT 07/01/2013
SPECIFICATION
APPLICATION FLASH EPROM
DES CALCULATEURS DU DOMAINE SOUS
CAPOT/ RÉFÉRENCE IND PROJET PAGE
SPECIFICATION
FLASH EPROM APPLICATION
(for POWER TRAIN & CHASSIS control units)
02016_12_09368 1.0 DAE BMPV 1
Baseline (version) :
71
5.0 A
CE DOCUMENT EST LA PROPRIETE DE PSA ET NE PEUT ETRE REPRODUIT OU COMMUNIQUE SANS SON AUTORISATION
THIS DOCUMENT IS THE PROPERTY OF PSA AND MAY NOT BE REPRODUCED OR DISCLOSED WITHOUT ITS AUTHORIZATION
Table des mises à jour PSA/Table of Updates
Indice Date Auteur Nature de la modification
4.2 09/06/10 OLERON Jean Création d'une nouvelle Baseline :
10:30 Francois Generation du tableau d'historique
4.3 09/06/10 OLERON Jean Création d'une nouvelle Baseline :
10:39 Francois Maj attribut DXL Wexp Template
Correction du wexp bookmark
4.4 27/07/10 ROCHETTE Création d'une nouvelle Baseline :
15:21 François Baseline mineure pour revue technique.
5.0 20/08/10 ROCHETTE Création d'une nouvelle Baseline :
09:51 François Baseline majeure.
5.0 A 20/08/10 ROCHETTE Création d'une nouvelle Baseline :
15:41 François Baseline 5.0A suite à problème technique DOORS.
The purpose of this document is to define programming procedures in After Sales and in the assembly
line for electronic computer provided with Flash Eprom. This procedure does not call into question the
remote coding concept (e.g.: choice of a configuration from several on board a ECU) intended to reduce
hardware or software diversity on board the line but can provide a solution in the case of computers
which cannot take on board all the diversity in a single software package.
This specification applies for all vehicles from Peugeot and Citroen.
AUTHEUR/AUTHOR
The following people took part in the checking of this Technical Specification :
The progress of electronic technology has brought much flexibility to system implementation, by the use
of increasingly powerful digital circuits. The increasing introduction of software into equipment is
accompanied by new problems dependent on the specific nature of the software product and its
development.
The computer must contain a boot application installed in a non-volatile memory (ROM, EEPROM,
paginated Flash) in the digital core in order to allow downloading of the program.
The supplier must include the boot software in each computer prior to delivery at P.S.A. It programs the
identification field at the same time.
The boot software is enabled by the download tool, without any specific hardware presets.
The computer must have a Z.A. (Authentication Field) containing the parameters necessary to identify the
control unit.
The computer must have an Z.I. (IDENTification Field) containing the parameters necessary to identify
the software.
Tableau 1 / Table 1 :
This 16-bit information gives the signature (checksum) of the Flash Eprom after downloading the code.
This is simple information which does not represent the computing result for checking the integrity of the
data in memory.
CLEF / KEY :
Cette information sur 16 bits donne la clef d'accès au logiciel de téléchargement. Cette clef est inopérante
lorsque sa valeur est égale à $FFFF.
This 16-bit information gives the access key for the downloading application. This key is inoperative
when its value is equal to $FFFF.
FOURNISSEUR / SUPPLIER :
Cette information sur 8 bits identifie le fournisseur du calculateur du logiciel ou de la calibration
téléchargé. La définition de ce codage est donnée dans le document [7].
This 8-bit information identifies the supplier of the computer, the software or the downloaded
calibration. The definition of this coding is given in the document [7].
SYSTEME / SYSTEM :
Cette information sur 8 bits identifie la famille de calculateur (MP5.1, MP7.0, 1A, etc). Il est choisi par
le fournisseur (par ordre croissant de création des calculateurs).
Afin d'éviter les cas de collisions entre métiers, le champ SYSTEME est découpé de la manière
suivante :
This 8-bit information identifies the computer family (MP5.1, MP7.0, 1A, etc.). It is chosen by the
supplier (in ascending order of development of the computers).
In order to avoid cases of collisions between the different trades, the SYSTEM field is broken down as
follows :
This information on 3 bytes identifies the date of manufacture of the computer. The first byte indicates
the day of the month (1 to 31), the second the month of the year (1..12) and the last the year of the
century (0..99).
A computer manufactured on July 27, 2001 will have the coding:
27 d = $1B
07 d = $07
01 d = $01 Þ $1B0701
Exemple
Example
APPLICATION / APPLICATION :
Cette information sur 8 bits identifie le type d'application et est choisie par le responsable de l’organe.
Elle correspond à une variante matérielle pour un système donné. Un fichier de téléchargement est
incompatible d’une variante à l’autre.
This 8-bit information identifies the type of application and is chosen by the device manager. It
corresponds to a hardware alternative for a given system. A download file is incompatible from one
version to another.
VERSION / VERSION :
Cette information sur 8 bits caractérise la version de la calibration du logiciel qui fonctionne dans le
calculateur. Elle est choisie par le responsable de l’organe. Ce champ peut être lié à plusieurs leviers de
diversité. Il n’est pas forcément rattaché à la silhouette véhicule.
This 8-bit information characterizes the software calibration release which is running in the computer. It
is chosen by the device manager. This field can be related to several diversity levers. It is not inevitably
attached to the vehicle outline.
EDITION / EDITION :
Cette information sur 16 bits correspond à l'état de modification du logiciel ou de la calibration du
calculateur. Dans le cas d’un calculateur ne permettant que le téléchargement de la calibration, le poids
faible est associé à l’état d’évolution de la partie calibration et le poids fort est systématiquement
positionné à $FF.
SPECIFICATION RÉFÉRENCE IND PROJET PAGE
APPLICATION FLASH EPROM
DES CALCULATEURS DU DOMAINE SOUS CAPOT 02016_12_09368 1.0 DAE BMPV 13 / 71
/SPECIFICATION
FLASH EPROM APPLICATION
(for POWER TRAIN & CHASSIS control units)
CE DOCUMENT EST LA PROPRIETE DE PSA ET NE PEUT Baseline (version) : Date d'application :
ETRE REPRODUIT OU COMMUNIQUE SANS SON 5.0 A
AUTORISATION
This 16-bit information corresponds to the state of amendment of the software or the calibration of the
computer. In the case of a computer allowing only calibration downloading, the bottom weighting is
associated with the state of development of the calibration part and top weighting is always set to $FF.
This information on 3 bytes identifies the last date on which the computer software release was
reprogrammed. Coding is identical to DATE-1.
SITE / SITE :
Cette information sur 8 bits identifie le site de la première programmation d'une APPLICATION dans la
mémoire Flash.
On utilisera les valeurs suivantes :
- Programmation fournisseur -> $FE,
- Programmation Après-vente -> $FD,
- Programmation UP -> $00.
This 8-bit information identifies the site of the first programming of an APPLICATION in Flash memory.
The following values will be used:
- Supplier programming -> $FE,
- After sales programming -> $FD,
- UP programming -> $00.
SIGNATURE / SIGNATURE :
Cette information sur 3 octets identifie la signature du lieu de reprogrammation du calculateur.
This information on 3 bytes identifies the signature of the place where the computer was reprogrammed.
NOMBRE / NUMBER :
Cette information sur 8 bits identifie le nombre de programmes d'application qui ont déjà été téléchargés
dans ce calculateur.
This 8-bit information identifies the number of application programs which were already downloaded in
this computer.
This information on 3 bytes identifies the reference of the last “.ulp” (application program +
calibration) or “.cal” (calibration alone) file downloaded in the computer. The coding chosen is of the
BCD type.
The coding adopted by PSA consists of a number of the type 96 xx xx xx 80; the three bytes marked xx
are those which are stored in the computer identification field instead of a file number.
Example: the file to be downloaded in the computer has reference number 96 285 582 80:
$28 corresponds to 28d coded in BCD
$55 corresponds to 55d coded in BCD
$82 corresponds to 82d coded in BCD
Accordingly, the bytes $28 $55 $82 are placed in the identification field on the “.ulp” or “.cal”
file no. field.
4 TERMINOLOGIE / TERMINOLOGY
4.1acronymes / ACRONYMS
5 Exigences / REQUIREMENTS
5.1Exigences fonctionnelles / FUNCTIONAL REQUIREMENTS
La programmation du calculateur peut être découpée en trois phases distinctes :
The programming of the computer can be broken down in three distinct phases:
· The first of these phases corresponds to the manufacture of the computer. It is carried out by the
supplier.
· The second phase corresponds to the programming of the first application; the aforementioned
can be carried out:
- at the supplier’s (case of delivery of a completely downloaded computer),
- at P.S.A in the case of delivery of a computer not containing the complete vehicle
application. This is the case where a global (application program + calibration) or partial
(calibration alone) file is downloaded in the production line.
· Finally the third phase, reserved for the after sales services for managing software
upgrades (case of a reprogramming).
Note : PSA never programs the access code protection KEY in Flash Eprom.
Exi : 01551_09_00081_P-5 (1.0) Type : Exi amont :
Générique
Les calculateurs séries livrés doivent contenir la CLEF de verrouillage programmée par le fournisseur du
calculateur.
Production computers delivered must contain the locking KEY programmed by the computer supplier.
Tableau 2 / Table 2 :
et la CLEF située dans le segment historique / and the KEY located in the history segment
(*) For PSA, a delivered computer provided with an identification field as specified above corresponds
to a “virgin” computer. If the computer is delivered with a factory calibration (temporary calibration
which allow to perform the assembly operations), the field “ULP or CAL file number” can be filled.
Note : This state of the Z.I corresponds to that which is required for delivery in the case of computers
which must be downloaded by PSA during production line operations, whether this downloading relates
to a global (application program + calibration) file or calibration alone.
Exi : 01551_09_00081_P-7 (1.0) Type : Exi amont :
Générique
Lors des phases de développement d’un calculateur (études) le codage de la clef est « $FF / $FF »
autorisant l’accès au composant flash eprom sans utilisation des formules de cryptage.
During a computer's development phases (design) the coding of the key is ”$FF / $FF” authorizing
access to the flash eprom without using encoding formulae.
In the case of a production, or production-compliant, delivery, the key will contain the value chosen by
the supplier in agreement with the project.
The supplier will also generate a label to identify the product in accordance with paragraph 5.5.3.4.
When this second phase is carried out at the supplier’s (case of an order for a computer already
downloaded provided with its application software and associated calibration), the three bytes of the
system signature will be set to $00 $00 $00.
When this second phase is carried out at PSA, before downloading the code, the system will have to
correlate the parameters of the Z.I of the ECU with the downloading file parameters:
-SYSTEME
-APPLICATION
The SYSTEME and APPLICATION parameters of the code to be installed must be identical.
The PSA ODISSEE system uses the signature $02 $00 $00.
et la CLEF située dans le segment historique / and the KEY located in the history segment :
It is imperative that the downloading procedure changes the identification field (Z.I) only after
transmission of the data.
Before downloading the code, the system will have to correlate the Z.I parameters of the EMU with the
download file parameters:
-SYSTEME
-APPLICATION
-VERSION
-EDITION
The SYSTEME, APPLICATION and VERSION parameters of the code to be installed must be
identical. The EDITION parameter of the code to be installed must be higher than the EDITION
parameter of the Z.I
Tableau 5 / Table 5 :
On delivery, spare computers also contain the access code protection key programmed by the supplier.
Le calculateur ne possède à l'origine que l'étiquette du fournisseur, la seconde étiquette sera adjointe par
les services Après Vente lors de la programmation de ce dernier.
Initially, the computer has only the supplier's label; the second label will be added by After Sales
services when the latter is programmed.
Table 6 / Table 6 :
The electronic integration mode allows to recover the maximum bandwidth of the CAN network during
the downloading of the computer. It also removes the unexpected storages and malfunctions of the
computer while the others computers connected to the network are in configuration phase.
Exi : 01551_09_00081_P-20 (1.0) Type : Exi amont :
Générique
Le calculateur entre en mode intégration électronique sur réception de trames 092h selon le mécanisme
décrit dans le document [8].
The computer enters in electronic integration mode upon receiving 092h frames in accordance with the
mechanism described in the document [8].
Deleted.
The tester must find in his data base the “.ulp” or “.cal” file to be downloaded according to the vehicle
to be assembled.
The tester reads the first frame of this file (S0) and extracts:
- The logic reference,
- The ECU address code,
- The communications protocol times for the RD file transfer request (if downloading on the K
line),
-The management information, where relevant, for a call during commands known as “long” and
the associated time out value.
The tester reads the second frame of this file (S1) and extracts the following data :
CHECKSUM
CLEF
FOURNISSEUR
SYSTEME
APPLICATION
VERSION
EDITION
FICHIER
In KWP2000 protocol, the opening of the diagnostic session is performed with the request SCR in
accordance with the document [2] or with the ODX-file (if there is one).
In UDS protocol, the switch to the Programming Session is performed with the request DSC $02 in
accordance with the format defined in the ODX-file.
In KWP2000 protocol, the authentication of the computer is performed with the request RDBLID $80 in
accordance with the document [2] or with the ODX-file (if there is one).
In UDS protocol, the authentication of the computer is performed with the request RDBI $F080 in
accordance with the format defined in the ODX-file.
If the computer does not have a valid application in memory, the following bytes are set to $00 :
- Diagnostics upgrade number,
- Number of associated parameters.
The bytes which constitute the functional plan and functional product numbers authenticating the
computer are written once only in the computer, are never erased and are always visible at the time of
using this request.
In KWP2000 protocol, the reading of the identification field is performed with the request RDBLID
$FE. This request reads the computer's latest identification field, in accordance with the document [4] or
with the ODX-file (if there is one).
In UDS protocol, the reading of the identification field is performed with the request RDBI $F0FE. This
request reads the computer’s latest identification field, in accordance with the format defined in the ODX-
file.
From the Z.I data and file data, the tester checks initially that the parameters SYSTEM and
APPLICATION have the same values: If these values are not identical, the program is stopped, because
the file to be downloaded does not correspond to the computer.
For computers that have never been programmed, i.e. with the Identification Field variables having the
following values :
NOMBRE = $FE and SITE = $FE
There is no check between the Z.I variables and the variables of the file to be downloaded :
VERSION and EDITION
For computers that have already been programmed, i.e. with the Identification Field variables having
the following values :
NUMBRE ≠ $FE and SITE ≠ $FE
The tester must check that the Z.I and the file to be downloaded actually have the same VERSION. He
will then check that the file EDITION number is actually upper than the EDITION number of the Z.I.
IMPORTANT
SPECIFICATION RÉFÉRENCE IND PROJET PAGE
APPLICATION FLASH EPROM
DES CALCULATEURS DU DOMAINE SOUS CAPOT 02016_12_09368 1.0 DAE BMPV 42 / 71
/SPECIFICATION
FLASH EPROM APPLICATION
(for POWER TRAIN & CHASSIS control units)
CE DOCUMENT EST LA PROPRIETE DE PSA ET NE PEUT Baseline (version) : Date d'application :
ETRE REPRODUIT OU COMMUNIQUE SANS SON 5.0 A
AUTORISATION
Sous réserve de disposer d’un fichier de gestion des compatibilités (sous WinPdm, ADVITIUM ou
autres) il reste possible de s’affranchir du verrou FSAVE.
Cela sera notamment vrai dans les cas suivants non exhaustifs :
- surmonte pneumatique ayant une influence sur la calibration du logiciel,
- fusion de deux versions logicielles existantes en une seule,
- etc …
Lorsque l’on ne dispose pas de fichier de gestion des compatibilités et que les valeurs mentionnées ci-
dessus ne sont pas conformes, le programme est stoppé car le fichier à télécharger n’est pas compatible
du calculateur.
Subject to having a compatibilities management file (under WinPdm, ADVITIUM or others) it is still
possible to overcome the FSAVE lock.
This will in particular be true in the following non-exhaustive cases:
- pneumatic excess pressure affecting software calibration,
- merging two existing software versions into a single version,
- etc.
If you do not have a compatibilities management file and the values mentioned above are not
compliant, the program is stopped because the file to be downloaded is not compatible with the
computer.
In KWP2000 protocol, the tester asks the computer for a random 32-bit number (SEED1, SEED2,
SEED3, SEED4) using the SA#1 request, in accordance with the document [4] or the ODX-file (if there
is one).
In UDS protocol, the tester asks the computer for a random 32-bit number (SEED1, SEED2, SEED3,
SEED4) using the SA#1 request, in accordance with the format defined in the ODX-file.
With the file KEY and the random number given by the computer (SEED1 SEED2 SEED3 SEED4), the
tester computes the formula :
KEY1 KEY2:= (F1 (KEY), F2 (SEED1 SEED4))
KEY3 KEY4:=(F1 (SEED2 SEED3), F2 (KEY1 KEY2))
In KWP2000 protocol, the tester sends the result of his calculation to the computer using the Request
SA#2, in accordance with the document [4] or the ODX-file (if there is one).
In UDS protocol, the tester sends the result of his calculation to the computer using the Request SA#2, in
accordance with the format defined in the ODX-file.
If the result is not accepted by the computer, he must repeat phase 7, but wait a certain time before it
will accept the request.
In KWP2000 protocol, from the logic reference for the S0 frame of the “.ulp” or “.cal” file, the tester
sends the request SRBLID $81 in order to erase the Flash Eprom in accordance with the document [4]
or with the ODX-file (if there is one).
In UDS protocol, from the logic reference for the S0 frame of the “.ulp” or “.cal” file, the tester sends
the request RC $FF00 in order to erase the Flash Eprom in accordance with the format defined in the
ODX-file.
This command is optional, nevertheless it is possible to modify the file transmission speed during
a download on the K line :
- In KWP2000, with the SDS request in accordance with the document [4] or the ODX-file (if
there is one).
- In UDS, with the LC request in accordance with the ODX-file.
in KWP2000 protocol, the tester sends the RD $88 request in order to program the KEY, in accordance
with the document [4] or with the ODX-file (if there is one).
in UDS protocol, the tester sends the RD $88 request, the TD request and the RTE request in
accordance with the format defined in the ODX-file.
Remarque : cette opération est non prévue en usine de montage, la CLEF est toujours programmée chez
le fournisseur ; néanmoins pour valider les formules de protection incluses dans le logiciel du
calculateur, il est nécessaire que PSA puisse dans la phase études mettre à jour cette CLEF.
Note: this operation is not stipulated in the assembly works, as the KEY is always programmed at the
supplier’s; to validate the protection formulae included in the computer software, PSA must however be
able to update this KEY in the design phase.
in KWP2000 protocol, the tester sends RD requests in order to download the Flash Eprom in
accordance with the document [4] or the ODX-file (if there is one) and according to the S frames of his
“.ulp” or “.cal” file.
In UDS protocol, the tester sends the RD request, the TD requests and the RTE request in order to
download the Flash Eprom in accordance with the format defined in the ODX-file and according to the S
frames of his « .ulp » or « .cal » file.
In KWP2000 protocol, the tester sends the SRBLID $82 request in order to test the checksum in
accordance with the document [4] or with the ODX-file (if there is one).
In UDS protocol, in order to test the checksum, the tester sends the RC $FF04 request in order to test
the checksum in accordance with the format defined in the ODX-file.
In KWP2000 protocol, in order to update the Z.I, the tester sends the RD $83 request in accordance with
the document [4] or with the ODX-file (if there is one).e
In UDS protocol, in order to update the Z.I, the tester send the RD $83 request, the TD request and the
RTE request in accordance with the format defined in the ODX-file.
Schema 1
In KWP2000 protocol, the tester sends the end of communication request SPR in order to end the
downloading procedure, in accordance with the document [4] or the ODX-file (if there is one).
In UDS protocol, the tester sends the request to switch to the default session DSC $01 in order to end
the downloading procedure, in accordance with the format defined in the ODX-file.
The Flash Eprom programming voltage will be drawn from the computer power supply, delivered either
by the vehicle battery during a reprogramming, or by an external power supply when programming in
the assembly line.
Le cœur numérique aura les protections nécessaires afin d'éviter toutes programmations parasites :
The digital core will have the protections necessary to avoid any interfering programmings :
Exi : 01551_09_00081_P-57 (1.0) Type : Exi amont :
Générique
SPECIFICATION RÉFÉRENCE IND PROJET PAGE
APPLICATION FLASH EPROM
DES CALCULATEURS DU DOMAINE SOUS CAPOT 02016_12_09368 1.0 DAE BMPV 51 / 71
/SPECIFICATION
FLASH EPROM APPLICATION
(for POWER TRAIN & CHASSIS control units)
CE DOCUMENT EST LA PROPRIETE DE PSA ET NE PEUT Baseline (version) : Date d'application :
ETRE REPRODUIT OU COMMUNIQUE SANS SON 5.0 A
AUTORISATION
Pour les calculateurs qui disposent d'un moyen de mesure de la tension batterie, celui-ci vérifiera la
tension batterie en permanence lors de la procédure de téléchargement.
For computers which have a means of measuring battery voltage, this will check the battery voltage
constantly during the download.
If the computer observes a battery voltage out of range during the procedure, it will generate a fault
code on the communication line and will stop its writing into Flash procedure.
This battery voltage checking procedure will be done automatically by the computer during the
command (in KWP2000 : RD, in UDS : TD) to write a code frame into Flash.
5.3.1.2 Communication
La communication entre le calculateur et l'outil de programmation s'effectue soit par les lignes L et K
pour les systèmes ISO 8 soit par la ligne K pour les systèmes ISO5, soit par le réseau CAN. La sélection
du support peut se faire automatiquement en fonction de la valeur du paramètre (YY) de la trame S0 du
fichier à télécharger.
The communication between the computer and the programming system is implemented either by the L
and K lines for ISO 8 systems or by the K line for ISO 5 systems, or by the CAN system. The medium can
be selected automatically according to the value of the parameter (YY) of the S0 frame of the file to be
downloaded.
Exi : 01551_09_00081_P-60 (1.0) Type : Exi amont :
Générique
Lors d’une utilisation ligne K, la transmission se fera sur véhicule à la vitesse de 10400 bauds dans le
réseau après-vente et en ligne de montage. Si des vitesses supérieures sont disponibles, elles peuvent être
utilisées dans le cas de téléchargement réalisées sur des calculateurs hors véhicule (par exemple en
étude).
When using the K line, the transmission will be done on the vehicle at a speed of 10400 bauds in the
after sales network and on the assembly line. If higher speeds are available, they can be used in case of
computers downloaded out of the vehicle (for example during development phase).
The protocol must comply with the instructions in the various specifications quoted.
For programming in the assembly line, the hardware used will be:
- An ODISSEE download tool containing the interface and the software,
- A label printing system (1),
- A 12V power supply (2),
- A downloading cable (2),
-The file to be downloaded.
For after-sales programming, the operator will have the following hardware:
- A garage system (electronic diagnostics) provided with the downloading procedure and the
cable for connection to the vehicle,
- The file to be downloaded.
In order first to standardize data file naming and second to facilitate the downloading process :
Exi : 01551_09_00081_P-62 (2.0) Type : Exi amont :
Générique
Le fournisseur devra fournir des fichiers ASCII ayant la définition suivante :
Un fichier <nom_de_fichier>.ULP contenant le code applicatif + une calibration et un fichier
<nom_de_fichier>.CAL contenant la calibration seule si nécessaire, tous deux au format MOTOROLA
S1/S9, S2/S8 ou S3/S7 avec une zone d'identification et le code à télécharger. Ils seront directement
utilisables par l'outil de programme.
The supplier must provide ASCII files having the following definition :
A file <file_name>.ULP containing the application code + a calibration and a file <file_name>.CAL
containing the calibration alone if necessary, both in MOTOROLA S1/S9, S2/S8 or S3/S7 format with an
identification field and the code to be downloaded. They will be directly usable by the programming
system.
A file will have as its name the 10 digits of its reference (e.g.: N° 96.123.456.80 ).
S0 0C 0000 XX YY AA BB CC DD EE FF GG cc
Toutes les valeurs sont exprimées en hexadécimales / All values are expressed as hexadecimal numbers
(1) Obligatoire mais non utilisé dans le cas d’une communication sur le réseau CAN. La préconisation
PSA est de conserver les mêmes valeurs que dans le cadre d’une communication sur la ligne K (pas de
diversité supplémentaire dans le cas de calculateurs développés sur les deux supports en fonction de
l’application véhicule).
(1) Compulsory but not used for a call over the CAN system. The PSA recommendation is to keep the
same values as for a call over the K line (no additional diversity in the case of computers developed on
the two media according to the vehicle application).
(2) Dans le cas de calculateurs ne gérant pas la communication pendant l'exécution de commandes
longues, le dépassement du time out aura comme conséquence de faire arrêter (reset du calculateur) la
SPECIFICATION RÉFÉRENCE IND PROJET PAGE
APPLICATION FLASH EPROM
DES CALCULATEURS DU DOMAINE SOUS CAPOT 02016_12_09368 1.0 DAE BMPV 55 / 71
/SPECIFICATION
FLASH EPROM APPLICATION
(for POWER TRAIN & CHASSIS control units)
CE DOCUMENT EST LA PROPRIETE DE PSA ET NE PEUT Baseline (version) : Date d'application :
ETRE REPRODUIT OU COMMUNIQUE SANS SON 5.0 A
AUTORISATION
procédure en cours. Le testeur devra recommencer toute la procédure de téléchargement. Il est donc
impératif pour le fournisseur du fichier à télécharger de s’assurer que la valeur du time out (paramètre
GG) de la trame d’entête S0 est correctement positionnée.
Note : In the case of computers that cannot handle communication while running long commands,
exceeding the time out will result in the procedure in progress being stopped (computer reset). The tester
will have to restart the entire download procedure. The supplier of the file to be downloaded must
therefore ensure that the time out value (GG parameter) of the S0 header frame is set correctly.
Exi : 01551_09_00081_P-66 (1.0) Type : Exi amont :
Générique
La trame d’entête S1 doit être conforme à la définition suivante : / The S1 header frame must be
compliant with the following definition :
In order to optimize download times in both the design and production phases, when constituting the
“.ulp” and “.cal” files, the supplier is required to withdraw Sx frames not containing usable code. In
other words, memory areas containing only default values.
5.3.4.1 Fichier global et calibration seule / Total file and calibration only
Pour PSA, il existe deux types de fichiers :
- Un fichier global contenant un logiciel applicatif et une calibration.
- Un fichier de calibration seule.
Un fichier global lorsqu’il existe (cas où l’on peut télécharger son applicatif) est toujours livré au
montage et en APV respectivement :
- Pour le plateau retouche lors de reprises de parc.
- Pour le réseau lors d’évolutions du logiciel.
Un fichier de calibration seule est livré :
- Au montage dans le cas d’un calculateur téléchargeable dans sa globalité mais ne permettant
que le téléchargement de la calibration pendant le temps alloué à cette opération dans le flux
véhicule.
Case of a computer (e.g.: engine computer) fully downloadable (application and calibration) in the
vehicle flow :
- Only the “.ULP” format delivered to assembly and the after sales network is produced and
managed.
Case of a computer where only the calibration part can be downloaded to assembly and the
whole (application and calibration) to the after sales network :
- The total file is produced in “.ULP” format and the file containing the calibration alone in “.CAL”
format.
For assembly: - In the vehicle flow, the file in the “.CAL” format is used.
- On the rework bench, the file in “.ULP” format is used.
In After Sales: Only the “.ULP” format is managed.
Case of a computer (e.g.: steering computer) where only the calibration part can be
downloaded :
- The “.CAL” format delivered to assembly and the after sales network is produced and
managed.
SPECIFICATION RÉFÉRENCE IND PROJET PAGE
APPLICATION FLASH EPROM
DES CALCULATEURS DU DOMAINE SOUS CAPOT 02016_12_09368 1.0 DAE BMPV 58 / 71
/SPECIFICATION
FLASH EPROM APPLICATION
(for POWER TRAIN & CHASSIS control units)
CE DOCUMENT EST LA PROPRIETE DE PSA ET NE PEUT Baseline (version) : Date d'application :
ETRE REPRODUIT OU COMMUNIQUE SANS SON 5.0 A
AUTORISATION
5.3.4.3 Désignation des fichiers / File naming
Cas d’un calculateur avec le téléchargement de la calibration effectué au montage et le
téléchargement global en APV :
On officialise sous une même référence PSA (ex : N° 96.123.456.80) le fichier global et le jeu de
calibration.
Le nom du fichier global (applicatif + calibration1) stocké dans la base BORNEO et sur CDROM est
identifié par la référence PSA munie de l’extension « .ULP ».
- Le nom du fichier stocké porte la référence 12345680.ULP.
Le nom du fichier de calibration (calibration1) stocké dans la base BORNEO et sur CDROM est
identifié par la référence PSA munie de l’extension « .CAL ».
- Le nom du fichier stocké porte la référence 12345680.CAL.
Case of a computer with calibration downloaded to assembly and the total downloaded to After Sales:
The total file and calibration set are managed under a single PSA number (e.g.: (N° 96.123.456.80).
The name of the total file (application + calibration1) stored in the BORNEO data base and on CDROM
is identified by the PSA number with the extension “.ULP”.
- The stored file is named 12345680.ULP.
The name of the calibration file (calibration1) stored in the BORNEO database and on CDROM
is identified by the PSA number with the extension “.CAL”.
- The stored file is named 12345680.CAL.
A computer will never be delivered provided with an application file alone (this file is neither produced
nor managed by PSA).
The locks set up for downloading the calibration alone are exactly the same as those for downloading a
total file (application + calibration).
The software identification number in memory represents the application and the calibration; it is the
number stored in the identification field at the time of the last update.
Downloading the calibration alone to assembly for a computer downloadable as a whole should be
considered purely as an interim step imposed only if the time to download the complete file is excessive
in view of the time allocated to the operation.
The computer must protect the 12 volts power supply against interfering overvoltages which could
damage the flash memory.
In order to avoid an erasure or interfering programming, the computer must have a certain number of
locks authorizing programming by a command software suite for the digital core.
A computing formula, applied both by the computer and by the download tool, starting from a random
number (uuuu) and a KEY, will authorize unlocking of the computer.
IMPORTANT :
Pendant toute la phase de développement des calculateurs jusqu’au stade des pré-séries en ligne
(tant que les véhicules ne sont pas destinés à la vente), il reste possible de se faire livrer des
calculateurs munis d’une CLEF_APPLI = $FFFF autorisant la mise à jour du logiciel depuis un
outil ne disposant pas des formules de cryptage.
The formula is confidential, and available at P.S.A from the department :
-DTI/DPMO/CSEE/APPT at LG from Mr. Thierry Lopez.
The general instructions are those from the specification [9], the paragraphs from which given below
are supplemented as follows.
The name or logo of the supplier, the mould and its prints as well as the reference of the date of
manufacture in conformity with technical standard [10], must be recorded legibly and indelibly on the
computer.
During computer manufacture, the supplier will place a first label including at least the following
information :
- The name or initials of the supplier.
- The Supplier's Hardware reference (Systeme, Application)
- The date of manufacture
During the first programming of the computer at the supplier’s or in the assembly line, a second label
will be affixed to identify the version number associated with the build. It will contain at least the
following information:
- The P.S.A number (96 xxx xxx xx), this information is that which is available in the computer's
electronic label under the functional product number description (also called the complementary
number). (1)
- The supplier's reference.
- The new approval number.
(1) This information will be in the form of a barcode and also in characters 5 mm in height.
The frames of a MOTOROLA S file have a structure broken down into 5 fields.
Remarque : Dans les explications et les exemples qui suivent, des espaces ont été ajoutés afin
d'améliorer la compréhension du format Motorola.
Note: In the explanations and examples which follow, spaces have been added in order to improve
understanding of the Motorola format.
S1 frames correspond to addresses expressed as 16 bits. The structure of these frames is as follows :
The S2 frame identifies the start of data frames corresponding to addresses expressed as 24 bits. The
structure of these frames is as follows :
The S3 frame identifies the start of data frames corresponding to addresses expressed as 32 bits. The
structure of these frames is as follows :
Remarque : Dans le cas d’un fichier constitué de trames de type S3, le poids fort de l’adresse 32 bits
(premier octet) n’est pas transmis par l’outil de téléchargement.
Note: In the case of a file made up of S3 type frames, the top weighting of the 32-bit address (first byte)
is not transmitted by the download tool.
The S5 frame contains the number of S1 or S2 or S3 frames in a data block. The S5 frame is always
placed (if it exists) at the end of a data block. This frame is optional. The structure of these frames is as
follows
1)S5 03 010D EE
2)S5 05 00008000 F2
The S7 frame identifies the end of an S3 data block. The structure of these frames is as follows :
The S8 frame identifies the end of an S2 data block. The structure of these frames is as follows :
The S9 frame identifies the end of an S1 data block. The structure of these frames is as follows :