Technical information

Modules (BCMs) do not require labels.
FLASH REPROGRAMMING SEQUENCE OF EVENTS
The process of flash reprogramming is similar to flashing the BIOS on a Personal
Computer. Interruptions, voltage problems, and a variety of other outside interactions can
potentially interfere with the process. This document seeks to provide information to
minimize problems associated with vehicle control module flash reprogramming. The
description that follows is for most PCMs and some TCMs. Other modules use different
initiation procedures.
The process starts by selecting an update from the TechCONNECT Client or ISIS and
then "loading" that update into the DRBIII®. Once the flash reprogramming update is
loaded into the DRBIII®, and before the flash reprogramming begins, the DRBIII® verifies
that the update loaded from the TechCONNECT Client or ISIS is the proper update for the
module. This is done using part number supersedence. This verification occurs only if an
update is required, available (on the TechCONNECT Client or ISIS) and has been selected
for programming.
• The module is then placed into "Boot Strap" programming mode by the DRBIII®.
This module mode gives the DRBIII® permission and the ability to proceed with the
flash reprogramming session.
• Next, the current part number, which resides in the module's flash memory, is stored
in a "Safe Memory" location within the module. This memory location is not affected
by flash memory erasure and reprogramming, which are to follow.
• Once the part number is safely stored, the flash memory in the control module is
erased. From this point forward any interruption in the flash process, will result in a
Non-Responsive module (NR). A NR module is a module that is either partially
erased or partially programmed.
• After erasure, the actual reprogramming procedure starts, and the update software
is programmed into the flash memory within the module.
• When reprogramming is completed, the flash memory is verified through an internal
process in the DRBIII® using a "Check Sum". This value is compared against
another value that represents what should be in memory and when matched, verifies
successful reprogramming.
• Next, a DRBIII® prompt is displayed instructing that the ignition switch be turned
OFF. The module exits the "Boot Strap" mode when the switch is turned off.
• After a slight pause, the DRBIII® will prompt for the ignition switch to be turned ON.
The DRBIII® then reads the new part number in flash memory (along with a new
computer program the new part number is placed into the module's memory). If the
new part number matches the expected part number, the flash reprogramming
session has completed successfully.
SOFTWARE VERSIONS MUST BE CURRENT
Before attempting a flash reprogramming session using the TechCONNECT Client, make
sure you have the most current DRBIII® software installed.
To verify whether your DRBIII® software is current, check the upper right-hand corner of
the TechCONNECT Client screen for DRBIII® Available Version, DRBIII® Current Version.
Often, because of multiple DRBIII®s in the shop, not all will get updated on a timely
manner. The installed DRBIII® software version can generally be found at the bottom
center of most screens. Alternately the version can be checked by pressing 6, 2, 5 from
the DRBIII® Main Menu and comparing it to what is available from a current
TechCONNECT Client as described above.
-3- 18-037-05