Notes on updating ECUs

To flash with same software (e.g. force flash):

Edit SVT_ist (in SVT-Editor > StandardSVK, and for
applicable ECU(s) to be flashed, change Main, Sub, and Patch
versions to 000, e.g.:

id 00000792 <- don’t change, just example ID

mainVersion 000
subVersion 000
patchVersion 000

Do NOT change HWEL. Zero out BTLD, SWFL, and CAFD.

Leave HWEL and HWAP alone. Then calculate SVT_soll,
TAL, and then flash.

Checking for available updates:

Red blue ECU’s mean update available, all black means none.
HWEL always should be black. NBT map and evernote are
updated separately, so ignore their colors for the most part.

Connection:
Use VIN and not gateway maybe? Guide says gateway,
shawn says vin, dunno. VIN connection might be intended for
broken cars/ECU’s. I used VIN, in the end.

Use Read (ECU) not Read VCM (step 7)? Not sure, since the
buttons were renamed between 3.27 and 3.33. Should be
VCM in theory, but I used Read (ECU) and it was fine. It
queries the system busses to determine ECU list. Read SVT is
a stored ECU List.

VO codings:
Add 710 remove 255 (M steering)
Change DCC_Sports_SLD to DCC_Sports
 OR

Change DCC_Sports to DCC_Sports_SLD

Add 715 (M aero)

Add 337 (M sport)
Add 455
Check for 430 (auto dip inside and outside)
Add 453 and 455 and 456 (climate + active + comfort seat with memory)
Add 4U1 (ceramic)

From shawn:
“Just use Read (ECU).

I use Connect via VIN.

Flash Single ECU or all ECU or any number in between.

Any E-Sys version >= 3.30.1 should be fine.”

Some random info from a poster:

“I was talking about flashing a car with retrofitted module(s). The basic idea is to calculate two
or more different svt_soll and tal files, first pair with original i-step shipment and then an extra
pair for every retrofitted module. Original module part is basics, it is not talked here. For
retrofitted modules, you must adjust I-step shipment before svt_soll calculation. You must
change it until you get the same HWEL-number for that module on both svt_soll and svt_ist.
When the numbers match, there will be only one HWEL number which is shown in black color.
Then you use this svt_soll and TAL to flash only this one module. You don't have to try every
single i-step shipment, AFAIK electrical system can get changes only when zeitkriterium
changes (i-step shipment month changes). After every flash with one svt_soll and TAL, you
must read SVT by using read ecu and then vo-code one module with update msm & vcm
turned on. This will fix svt target in vcm, it gets messed up when you do a flashing of this kind
(svt_soll has false information on some of the modules, opposite of what you are flashing).”

Flashing retrofitted/non-original modules:

So, make flash, but after you calculate SVT Target (SVT_soll), check the box that says "HW-IDs
from SVTactual" and then Save it. If HWEL is Black only, no Red / Blue HWEL, then you can
proceed to flash it.

Lock airbags using ISTA after flashing

If you get HTTP errors, kill HTTP (either TAL edit (see below) or Settings > Connections) and
use UDS. Extremely slow but reliable. 9+ hours to flash NBT, 100% need a power supply.

Changing to UDS:
E-Sys > Editors & Viewers > TAL-Editor > Load prepared TAL from disk > In the tree, expand
TalLine_ID entries > Expand *Deploy tree (e.g. IBADeploy) >Expand *Deploy_* file tansfer
entry (e.g. IBADeploy_IBAD_00001234_123_456_789 > Right-click on PreferredProtocol, Edit
> Change to UDS. Repeat for all items.

Current istep: F010-21-03-520

Apparently 3.27 works better for NBT flashing. Calculate everything with 3.33, but then use
3.27 for the actual flash