1993-2011 General Motors Company, GM Customer Care & Aftersales. All Rights Reserved.
Page
102
B4 Op-Code: Block Transfer to Download Calibration File - Mode 36
Supported By:
Class 2 Interpreter 1
Description:
The B4 Op-Code is used to build a mode 36 message for downloading a calibration file (or software) to a
control module. Depending on the product being programmed this Op-Code may need to be preceded by a
mode 34 message (see Op-Code 34 ).
The exception value (AC3) will allow the B4 Op-Code to support slightly different processing without having to
create unique Op-Codes. Currently exception 0 should be used to download files to a 95 VCM-XA and
exception 1 to download a car platform control module. (See pseudo code for exception descriptions.)
The B4 Op-Code uses the global source address for all messages. If a source address other than the
current
source address needs to be used the Interpreter instructions should contain a 01 Op-Code prior to this Op-
Code.
If the GlobalHeaderLength value (OpCode $F3) is not zero then the downloading of the
module will be
separated into two parts with the “GlobalHeaderLength” number of bytes will be downloaded first, followed by
the remaining calibration data. The “default” GlobalHeaderLength value is zero.
Caution: The “message data length” value in the Utility File header can be “over-written” via the “$F5
Override
the Utility File Message Length Field” Op-Code. (See the $F5 Op-Code for specifics.)
Action Fields:
AC0:
Target Device ID
AC1:
Calibration ID
for Calibration to Download
AC2:
Value of the routine number (taken from routine section of utility file)
AC3:
Exceptions:
00 - This option downloads each packet with a transmit type of download only.
The calibration download data packet size is obtained from the utility file header.
The RAM download address is obtained from the utility file header. This option uses the same
download address for each data packet downloaded. Uses 3-byte addressing.
If the last piece of data to download
is less than the packet size, then the missing data is padded
with 0x00 data.
For examples of how this exception works see reprogramming specifications for the 1995
VCM-XA or the 1996 PCM-32U.
01 - This option downloads each packet with a transmit type of download & execute.
The Mode $36 message contains “routine data” from the routine (AC2) that precedes each
calibration packet data from the calibration file (AC1).
The calibration download data packet size is obtained from the utility file header.
The RAM download address is determined from the routine section (prolog).
The download
packet address is obtained from the utility file header and is incremented by the packet size after
each download. Uses 2-byte download packet addressing.
If the last piece of data to download is less than the packet size, then
the packet length will
adjusted to the actual number of remaining bytes to send (no padding with 0x00 data).
For examples of how this exception works see reprogramming specifications for the 1996
PCM-66U.
02 - Follows the same logic as exception 01 with the exception of:
Uses 3-byte download packet addressing.
03 - Follows the same logic as exception 00.
04 - Follows the same logic as exception 00 or 03 with the exception of:
The download address will be incremented by the packet size after each download.
If the last piece of data to download is less than the packet size, then the packet length will
adjusted to the actual number of remaining bytes to send (no padding with 0x00 data).
*Note:
A prolog and routine are both contained within the routine section of utility file; however, they are different.
The prolog is a value that precedes each
packet of information, which could be a routine that is
downloaded. With a routine, the data is downloaded to the controller only once.
A prolog would remain
constant during the downloading of a routine.
CameraLoops.com
1993-2011 General Motors Company, GM Customer Care & Aftersales. All Rights Reserved.
Page
103
Do'stlaringiz bilan baham: 
