CarTechnoloGY
G05 TAL issue, not able to flash MGU - Printable Version

+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: BMW - Mini - Rolls Royce (https://cartechnology.co.uk/forumdisplay.php?fid=61)
+---- Thread: G05 TAL issue, not able to flash MGU (/showthread.php?tid=52606)

Pages: 1 2 3


G05 TAL issue, not able to flash MGU - Thorsten - 21-06-2019

Hello together,

perhaps, somebody can help me...
I have a X5 G05 there, iStep 19-03-535 and need to flash the headunit, MGU, to iStep 19-03-560.
While generating the TAL, E Sys is showing thie issue, please have a look to the attachment.

If I ignore it and start the TAL process, E Sys is hanging.
I tried E Sys 3.27.1, 3.30 and 3.31.0


UPDATE:
G20 with factory iStep 18-11-553, I can’t flash MGU with E Sys, same error message while TAL creation process.


Thorsten


RE: G05 TAL issue, not able to flash MGU - Stromag - 21-06-2019

Which version of PSdZdata?

 Did you set the hook for VCM and MSM?


RE: G05 TAL issue, not able to flash MGU - Thorsten - 21-06-2019

HI,

E Sys 3.27.1, 3.30.0and 3.31.0.
psdzdata the latest one,, 4.17.31

VCM and MSM is disabled.


Thorsten


RE: G05 TAL issue, not able to flash MGU - Stromag - 21-06-2019

(21-06-2019, 14:56 PM)Thorsten Wrote:  HI,

E Sys 3.27.1, 3.30.0and 3.31.0.
psdzdata the latest one,, 4.17.31

VCM and MSM is disabled.


Thorsten

I'm assuming that this is an undamaged vehicle, so I'd put the hooks on VCM and MSM and try again.  I'm reminded that somebody had this problem.


RE: G05 TAL issue, not able to flash MGU - Thorsten - 21-06-2019

HI,

I tried this, but nothing - while TAL is generating, the same error came up again...


Thorsten


RE: G05 TAL issue, not able to flash MGU - Stromag - 21-06-2019

During the valley generation comes this message?

 Ps: psdzdata 4.17.3x are not I Level 19_03_560.
 It would be the 4.17.4x


RE: G05 TAL issue, not able to flash MGU - ferbmw - 21-06-2019

Same problem with my G20. 
I want to update from factory level 18-11-557 to 19-3-548. Same pop up screen with same text.
Different issue is I did not start the flash process.
Essys 3.27, psdszdata 4.17.31.


RE: G05 TAL issue, not able to flash MGU - luntik - 21-06-2019

As we talk about flashing new generation of G series I would ask about RAM ECU I have tried to flash and got this error:

Read SVT before TAL execution started.

TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2019/06/20-23:47:54.002
[] prepareTALExecution started [PROGRESS]
MCDDiagService<id=48649, job=com.bmw.psdz.jobs.uds.MCD3_CheckProgrammingCounter, service=RDBI_PC - ReadDataByIdentifier ProgrammingCounter, description=error: negative response : requestOutOfRange, link=RAM_37_ETHERNET> [DIAGSERVICE]
[] prepareTALExecution finished [PROGRESS]
[] prepareVehicleForFlash started [PROGRESS]
[] prepareVehicleForFlash finished [PROGRESS]
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgModeCascade, service=DSC - DiagnosticSessionControl, description=error: timeout, link=RAM_37_ETHERNET_37> [DIAGSERVICE]
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgModeCascade, service=DSC - DiagnosticSessionControl, description=error: timeout, link=RAM_37_ETHERNET_37> [DIAGSERVICE]
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgModeCascade, service=DSC - DiagnosticSessionControl, description=error: timeout, link=RAM_37_ETHERNET_37> [DIAGSERVICE]
MCDDiagService<id=242900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgModeCascade, service=RC_SDB - RoutineControl SetDefaultBus, description=error: timeout, link=RAM_37_ETHERNET_37> [DIAGSERVICE]
[] Activate programming mode was not successful for: ECUId:RAM_0x37 [WARN]
[] ECUId:RAM_0x37 not accessible cause could not be switched to parallel programming mode [WARN]
[RAM - 37] ECUId:RAM_0x37 not accessible cause could not be switched to parallel programming mode [THROWABLE]
[] finalizeVehicleFlash started [PROGRESS]
[] finalizeVehicleFlash finished [PROGRESS]
[] prepareVehicleForCoding started [PROGRESS]
[] prepareVehicleForCoding finished [PROGRESS]
[] finalizeVehicleCoding started [PROGRESS]
[] finalizeVehicleCoding finished [PROGRESS]
[] finalizeTALExecution started [PROGRESS]
[] finalizeTALExecution finished [PROGRESS]
TAL execution finished [TAL_EXECUTION_FINISHED]
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "1min 34s". [C206]

Read SVT after TAL execution started.
Read SVT after TAL execution finished.


RE: G05 TAL issue, not able to flash MGU - Thorsten - 22-06-2019

(21-06-2019, 16:46 PM)Stromag Wrote:  During the valley generation comes this message?

 Ps: psdzdata 4.17.3x are not I Level 19_03_560.
 It would be the 4.17.4x

You are right, 4.17.4x are the psdzdata files of ISTA - but such details like E Sys Version and which iStep I am using are written in my first post.


RE: G05 TAL issue, not able to flash MGU - Thorsten - 25-06-2019

HI,

perhaps somebody else here with same issue or idea, how to fix it?


Thorsten