BMW Forum - BimmerFest BMW Forums banner

Flash all ECU's with E-Sys

1 reading
190K views 354 replies 53 participants last post by  shawnsheridan  
#1 ·
Just wanted to share some experiences with flashing all the ECU's in my car (F11 from 2010), hopefully others can benefit from this.

Order of flashing modules:
When you flash KOMBI before ZGM and SZL some functions will fail: most notable Cruise Control and Speed Limiter can no longer be activated. It makes sense to flash ZGM and SZL first.

After flashing IHKA airconditioning didn't work (hot air instead of cold), this went away after flashing CAS.

Flashing ZGM:
Attemps to flash ZGM failed initially with the following error:
Code:
MCDDiagService id=240900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgMode , service=RC_GAC - RoutineControl GetActualConfig, description=error: timeout, link=Physical request to ECU with address 0x10>
I found a few other threads mentioning possible solutions which are
  • Use direct connection via gateway url instead of via vin to tcp://ip address of your car:6801 eg tcp://169.254.30.100:6801
  • In Tal Processing | Parameters uncheck "Switch gateway(s) to programming mode"

In my case both options did not work with E-Sys 3.23.4, I then tried E-Sys 3.24.3 and was able to flash ZGM at the first attempt.

ACSM module:
After programming operations (flash) on ACSM module the airbag will be disabled, this is by design. KOMBI and iDrive will report disable airbag, seatbelts and abs to the driver.

If you read fault memory with Rheingold you'll see the following error on ACSM:
Code:
Fault description 
A fault occurred during transmission of the coding data. The coding data in the control unit are incomplete or faulty.
 
Condition for fault identification Supply voltage between 9 and 18.5 volts.

Terminal 15 on

 
Condition for fault memory entry 
 
Action in service Check whether message faults are stored in the vehicle. If necessary, run the system analysis test module. Ensure that the latest version of the program including the current software update is used for programming. Repeat programming/encoding. If the fault occurs again, use a different vehicle interface (a different ICOM) and repeat programming/encoding. If the fault still reoccurs, contact Technical Support.
 
Fault effect and breakdown warning 

 
Driver information Check Control message (97): Faulty airbag function

The airbag indicator light illuminates as soon as the fault is set in the fault memory, until the fault is deleted. The switched-on period of the airbag indicator light is at least 4 s.
 
Service instruction
I followed the Server Plan | Test plan procedure in Rheingold on the ACSM which allowed me to enable the airbag again:
Image


Finally I cleared fault memory and all appears to be well:
Image
 

Attachments

#3 ·
After flashing ACSM, the Airbag needs to be locked. If one does not have ISTA/D (Rheingold), it can be done with E-Sys or Tool32:

E-Sys Transmitter:

1) Click "External Applications" in the left menu.
2) Click "External Application"
3) Double-click "Transmitter"
4) Double-click "ACSM verriegelung_schreiben"

Tool32:

1) Launch C:\EDIABAS\Bin\TOOL32.EXE
2) Hit F3
3) Load C:\EDIABAS\Ecu\ACSM4.prg
4) In the "Select Job: F01" window, select steuern_verriegelung_schreiben
5) Hit F5
6) "Results" window should show "JOB_STATUS = OKAY"
 
#11 ·
After flashing ACSM, the Airbag needs to be locked. If one does not have ISTA/D (Rheingold), it can be done with E-Sys or Tool32:

E-Sys Transmitter:

1) Click "External Applications" in the left menu.
2) Click "External Application"
3) Double-click "Transmitter"
4) Double-click "ACSM verriegelung_schreiben"

Hi, I'm writing from Barcelona, ***8203;***8203;I updated my F01 ACSM with E-Sys and I get error failure Retention, Driver and Passenger. You have to enable ACSM to Transmitier?
 
#12 ·
I do not understand what you ask. You have to do just as I wrote above to Lock ACSM using E-Sys Transmitter.
 
#14 ·
Try Tool32 then:

Tool32 => ACSM4.prg => steuern_verriegelung_schreiben = control_lock_write
  1. Launch C:\EDIABAS\Bin\TOOL32.EXE
  2. Hit F3
  3. Load C:\EDIABAS\Ecu\ACSM4.prg
  4. In the "Select Job: F01" window, select steuern_verriegelung_schreiben
  5. Hit F5
  6. "Results" window should show "JOB_STATUS = OKAY"
 
  • Like
Reactions: dncomputech
#15 ·
Hello

Is there anything to take care of flashing the ecu except of ACSM???
I already flashed NBT, KOMBI and TRSVC ecu seperatly. Was never a problem.

But what about the other modules? Is there really a special order to flash them?
If I flash them, I will flash them seperatly too. Not all at the same time.
 
#18 ·
Open TAL IN TAL Editor, and it will show you under ECU (TalLine_ID) if it has any PreRequisite ECU (TalLine_ID's).

As you can see here, TalLine_ID=13 (Kombi) has a PreRequisite of TalLine_ID=11 (HU_CHAMP):

 
#20 ·
No. It all depends on the specific ECU firmware being flashed whether it has dependencies, and can vary from one firmware version to the next. Just because you flash NBT today with 54.0 and it has dependencies does not mean later if you flash it with 54.1 it will also have dependencies.
 
#24 · (Edited)
I'll let him clarify, as he specifically wrote he "I have ACSM4.prg..."

In your SVT, what is the exact name of vour ACSM module?