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

Page 277
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
9.4.3.2 Programming Utility File Process. 
This part contains all steps required to perform a security access
to the node to be programmed and the steps for the transfer of the data to the physical node. See Table 230.
For the physically addressed request messages contained in the utility file, the tester uses the diagnostic PTP
request CANId of the individual node(s) to be programmed (as determined via the diagnostic services $1A,
$A2 and stored in the diagnostic mapping matrix). The exceptions to this are the TesterPresent messages
transmitted automatically by the SPS communication layer and the synchronization step where the 
master
execute 
transmits a functionally addressed (AllNode) ReturnToNormalMode ($20) request.
Table 230 shows the general process incorporated within the utility file. The actual utility file instruction set may
incorporate more steps as required by the specific node, particularly regarding the actual data transfer steps.
Table 230: Steps of the Utility File Process
Step Action
22
SecurityAccess ($27)
For those nodes which are theft, emission, or safety related (or contain functionality otherwise bound
by legal requirements).
23
RequestDownload ($34)
•
Tells a node to allocate the necessary resources needed for programming (and forces the node to
begin operating out of boot software if boot exists and the node is not already executing out of the
boot).
Note: 
Steps performed by the ECU on reception of this service depend on the ECU internal structure.
•
A node which has been previously programmed shall store its permanent PTP request and USDT
diagnostic response CAN Identifiers in a way such, that the boot software can access them during
the remainder of the programming event.
24