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

GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 160 of 336
TransferData_Allowed ←
YES
if applicable, make permanent diagnostic CAN Identifiers available to the boot
prior to transferring program operation to the boot software.
if applicable, Transfer program operation to the boot.
ENDIF
ENDIF
ENDFUNCTION
Note: 
The pseudo code above shows the final response to the $34 service taking place prior to transferring
control to the boot software. An ECU may choose to transfer program control to the boot and then send the
final response. If the final response is sent before transferring control to the boot, then the utility file should
contain a delay op-code to ensure that the programming tool does not attempt to send the next message
before the boot software begins executing.
8.12.7 Node Verification Procedure. 
The procedures below have been written for nodes which support
security. Make the appropriate adjustments for nodes which do not support security access.
Procedure 1:
1. Perform security sequence. Send a DisableNormalCommunication request message and verify the
positive response. Begin periodic TesterPresent messages. Enable programming mode with the $A5
service (requires two messages). Send RequestDownload message with a valid dataFormatIdentifier and
unCompressedMemorySize parameter value. Execute this step when no memory fault exists which would
result in a negative response with response code $99. Verify positive response ($74).
2. If the ECU supports the negative response code 99, use development instrumentation to set a memory
DTC, Then repeat step one of this procedure and verify the proper negative response ($7F $34 $99,
ReadyForDownload-DTCStored).
3. Perform steps 1 and 2 of this procedure a 2
nd 
time with the programming mode enabled in high speed
operation (applicable only to devices on Single Wire CAN link).