Страница 1 мировой engineering стандарты общая спецификация

Note: 
The $34 pseudo code assumes that the ECU is unlocked when operating out of the boot software.
9.3.2.4.7 Service $36 - TransferData. 
This service is used to transfer programming routines as well as
software and calibration data to the ECU during a programming event. This service shall be fully implemented
as described in paragraph 8.13.
9.3.2.4.8 Service $3B - WriteDataByIdentifier. 
This service is required to be supported in boot if it is
necessary to write information (e.g., option content) into an ECU before the software reset at the end of the
programming event. If implemented in the boot software, then the boot implementation shall be as described in
paragraph 8.14.
9.3.2.4.9 Service $3E - TesterPresent. 
The ECU shall support the receipt of the $3E message in order to
maintain the programming event. No positive or negative responses are required.
During a programming event, an ECU executing out of RAM while erasing or writing to type 3 memory, shall
reset and suspend its P3
C 
timer if it is not able to process incoming TesterPresent requests during the
erase/write process. Upon completion of the erase/write process, the P3
C 
timer shall be enabled and
synchronized with the other ECUs upon receipt of a TesterPresent request.
Note: 
Reference the Application Timing Parameters Definition section of this specification for detailed
requirements regarding the P3
C 
timer.
9.3.2.4.9.1 Pseudo Code 
(Refer to the data dictionary of the application implementation of this service for
variable definitions.)
BEGINFUNCTION Boot_3E_Msg_Recvd()
TesterPresent_Timer ←
0 /*Reset the tester present timer*/
ENDFUNCTION
The following logic is used to implement the TesterPresent_Timer in the node’s main processing loop:
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---