NBT EVO b140 Flashing fails with CheckMemoryhttp error

NBT EVO b140 Flashing fails with CheckMemoryhttp error - 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: NBT EVO b140 Flashing fails with CheckMemoryhttp error (/showthread.php?tid=27106)

Pages: 1 2 3 4 5 6 7

NBT EVO b140 Flashing fails with CheckMemoryhttp error - Mwahab - 24-08-2017

I have 2 B140 units, both of them fails during the BIGGEST SWFL 0000271a

This is the message we get when flashing fails

service routinecontrol CheckMemoryHttp returned unexpected result: debugiInformation_02_FF: ECU: HU_NBT2_63_ETHERNET_63 severity: FATAL ERROR

One unit was patched, and i needed to patch with a new VIN so the provider advised me to to reflash it in order to load the new sets.

The other unit came to me like that, SOFT BIRCKED!

We tried several stuff and all of them failed.

Dowgraded from Btld 5 to 00
Pszdata 60 - 61 - 61.2 - 62 - 59.x
Flashed it with ID4 TAL
Flashed it with the old patched VIN
Flashed over CAN
Flashed over DHCP server
ENET was used during the whole process
Flashed in CAR then in BENCH
Excluded this SWFL from TAL, other were flashed successfully.
Flashed W/O btld
W/O Parallel programming
Esys 3.27 - 3.28
Windows 10
Hard drive can not be accessed via tool32
installed java x64
dissembled the unit, and i didnt found any loose connection.

This the second unit i have like this, and its getting so annoying.

I hope somebody may help, who had ever saw such issue and solved it.
Your help is much appreciated

Several respected brains in Cartech remooted in, ended up with the same eror, they told me to " REFLASH AGAIN AND AGAIN"
others admits it's Soft bricked

Notes: During 271a SWFL, the Flashing takes variable times, from slow to being so fast, the screen sometimes stays at 1%, other times 18% till 30% but the outcome is the same.
A reboot sound is heard during flashing this SWFL, is that normal?

I just thought about flashing it with an ICOM.

These ppl were in during the whole process remotely
@Loliceman
@Bagzbanny

stuff you may need is included as logs, Istep etc
[Image: Fqw9riK.jpg]

Quote:MCDDiagService<id=36900, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUFlash, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x63>
[HU_NBT2 - 63 - swfl_0000271a-001_052_004] Transaction type: swDeploy; Message: 2% progress on ECUId:HU_NBT2_0x63 [3% of swfl_0000271a-001_052_004]
[HU_NBT2 - 63 - swfl_0000271a-001_052_004] Transaction type: swDeploy; Message: TA finished
[HU_NBT2 - 63] -MessageID is used multiple times, so MessageText may be ambiguous-job failed with negative response error:
code: repeat job
description: transfer data repetition counter exceeded; ECU: HU_NBT2_63_ETHERNET
severity: ERROR

[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] job failed with negative response error:
code: repeat job
description: transfer data repetition counter exceeded; ECU: HU_NBT2_63_ETHERNET
severity: ERROR

[HU_NBT2 - 63] prepareECUforFlash started
MCDDiagService<id=352900, job=com.bmw.psdz.jobs.uds.hu.MCD3_PrepareECUforFlash, service=RC_DEACTIVATE_HDD_SAFE_MODE - RoutineControl DeactivateHddSafeMode, description=error: timeout, link=Physical request to ECU with address 0x63>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.uds.hu.MCD3_PrepareECUforFlash, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x63>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.uds.hu.MCD3_PrepareECUforFlash, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x63>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.uds.hu.MCD3_PrepareECUforFlash, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x63>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.uds.hu.MCD3_PrepareECUforFlash, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x63>
[HU_NBT2 - 63] prepareECUforFlash error
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files.
[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] negative response error:
code: the result contains an error
description: Service RDBI_ADS has error in result: [Severity=2051][ErrorCode=53311][ErrorCodeDescription=Module offline][VendorCode=20039][VendorCodeDescription=link is no longer active]; ECU: HU_NBT2_63_ETHERNET
severity: ERROR

[HU_NBT2 - 63] There was an error during TAL execution, please check the log files.
[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] negative response error:
code: the result contains an error
description: Service RDBI_ADS has error in result: [Severity=2051][ErrorCode=53311][ErrorCodeDescription=Module offline][VendorCode=20039][VendorCodeDescription=link is no longer active]; ECU: HU_NBT2_63_ETHERNET
severity: ERROR

[HU_NBT2 - 63] finalizeECUFlash started
[HU_NBT2 - 63] finalizeECUFlash finished
[] There was an error, please check the log files.
[] - [Exception - HU_NBT2 - 63] negative response error:
code: the result contains an error
description: Service RDBI_ADS has error in result: [Severity=2051][ErrorCode=53311][ErrorCodeDescription=Module offline][VendorCode=20039][VendorCodeDescription=link is no longer active]; ECU: HU_NBT2_63_ETHERNET
severity: ERROR

[] finalizeVehicleFlash started
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0xdf>
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0x10>
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0x10>
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0x63>
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0x63>
MCDDiagService<id=66900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=RC_DAFM_DFM - RoutineControl DeactivateFlashMode, description=error: timeout, link=Physical request to ECU with address 0xdf>
MCDDiagService<id=66900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=RC_DAFM_DFM - RoutineControl DeactivateFlashMode, description=error: timeout, link=Physical request to ECU with address 0xdf>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0xdf>
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0xdf>
[] finalizeVehicleFlash finished
[] finalizeTALExecution started
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeTALExecution, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0xdf>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeTALExecution, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0xdf>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeTALExecution, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0xdf>
MCDDiagService<id=464900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeTALExecution, service=RC_TAS_ROUTING - Routine Control for TAS, description=error: timeout, link=Physical request to ECU with address 0xf0>
MCDDiagService<id=464900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeTALExecution, service=RC_TAS_ROUTING - Routine Control for TAS, description=error: timeout, link=Physical request to ECU with address 0xf0>
[] finalizeTALExecution finished
TAL execution finished
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "29min 9s". [C206]

Read SVT after TAL execution started.
MCDDiagService<id=46900, job=com.bmw.psdz.jobs.common.MCD3_GenerateConfigFromVehicle, service=RDBI_SVK - ReadDataByIdentifier SVK, description=error: timeout, link=Physical request to ECU with address 0xdf>
Read SVT after TAL execution finished.

ESYS LOGS.txt
File Type:
Downloaded:	31 times
Size:	22 bytes

RE: NBT EVO b140 Flashing fails with CheckMemoryhttp error - Almaretto - 24-08-2017

Why are you flashing with Launcher enabled? It is not needed.

RE: NBT EVO b140 Flashing fails with CheckMemoryhttp error - IZGOY - 24-08-2017

All in place in the block ????
All correctly connected?
Hard drive, DVD drive?

NBT EVO b140 Flashing fails with CheckMemoryhttp error - bmwdd - 24-08-2017

Were you able to flash other swfl files or was this the first swfl file it flashed and it failed as soon as it starts?

Sent from my iPhone using Tapatalk Pro

RE: NBT EVO b140 Flashing fails with CheckMemoryhttp error - ruben_17non - 24-08-2017

Try, 3.30 without launcher and psdzdata V59 or V60, check if you obtain same error.
is extrange i never have this error...

check RAM and HDD of your laptop, need free space, for "unpack" Swfl´s

RE: NBT EVO b140 Flashing fails with CheckMemoryhttp error - Mwahab - 24-08-2017

(24-08-2017, 05:01 AM)Almaretto Wrote: Why are you flashing with Launcher enabled? It is not needed.

I personally tried with the Launcher and without the Launcher.

(24-08-2017, 07:16 AM)IZGOY Wrote: All in place in the block ????
All correctly connected?
Hard drive, DVD drive?

Yes all in place, the unit was working fine before flashing with an Emulator attached, it read the USB, and i selected the hdd to be flashed also.
There wasn't any Music collection saved on the HDD.

(24-08-2017, 08:58 AM)bmwdd Wrote: Were you able to flash other swfl files or was this the first swfl file it flashed and it failed as soon as it starts?

Sent from my iPhone using Tapatalk Pro

Yes i were able to Flash other SWFL when i exclude 271a from TAL

(24-08-2017, 10:40 AM)ruben_17non Wrote: Try, 3.30 without launcher and psdzdata V59 or V60, check if you obtain same error.
is extrange i never have this error...

check RAM and HDD of your laptop, need free space, for "unpack" Swfl´s

I tried with my PC, yes there wasn't enough good space just around 20GB in Drive with 'Data' Folder, then tried with @Gabrolla PC, i will check with him if is there was enough space or not.

NBT EVO b140 Flashing fails with CheckMemoryhttp error - bmwdd - 24-08-2017

Make sure your do not have any antivirus monitoring running

Sent from my iPhone using Tapatalk Pro

RE: NBT EVO b140 Flashing fails with CheckMemoryhttp error - Mwahab - 24-08-2017

(24-08-2017, 13:27 PM)bmwdd Wrote: Make sure your do not have any antivirus monitoring running

Sent from my iPhone using Tapatalk Pro

I have no antivirus in Programming PC, Firewall is disabled too.
It's like i am reeady for any attack biggrin

Have you faced such issue before?

Someone one in Russian forum is telling me

Quote:Looks like your EVOs have been opened and not properly reassembled. HDD or DVD drive is not properly connected. Make sure to unscrew the adapter board before inserting it into DVD, then screw it back together when DVD is already attached to a connector. Check the drive status in Tool32. If your HDD or DVD is not found, you would not be able to flash 271a - it tries to update the drive firmware and fails when no drive is found. It took me a while to figure this one out. DVD connector is a PITA to connect properly. Must be an easter egg from BMW.

Anybody can share link for V58.0 - 59.0 - 60.0 ? any of them.

RE: NBT EVO b140 Flashing fails with CheckMemoryhttp error - ivannw - 24-08-2017

(24-08-2017, 13:33 PM)Mwahab Wrote:
(24-08-2017, 13:27 PM)bmwdd Wrote: Make sure your do not have any antivirus monitoring running

Sent from my iPhone using Tapatalk Pro

I have no antivirus in Programming PC, Firewall is disabled too.
It's like i am reeady for any attack

Have you faced such issue before?

Someone one in Russian forum is telling me

Quote:Looks like your EVOs have been opened and not properly reassembled. HDD or DVD drive is not properly connected. Make sure to unscrew the adapter board before inserting it into DVD, then screw it back together when DVD is already attached to a connector. Check the drive status in Tool32. If your HDD or DVD is not found, you would not be able to flash 271a - it tries to update the drive firmware and fails when no drive is found. It took me a while to figure this one out. DVD connector is a PITA to connect properly. Must be an easter egg from BMW.

Anybody can share link for V58.0 - 59.0 - 60.0 ? any of them.

Rule 3: Do not Post Links on the Board! External links must be attached in a notepad file.

Thanks, Admin

Like this under

59.5

Enviado de meu SM-G955F usando Tapatalk

NBT EVO b140 Flashing fails with CheckMemoryhttp error - bmwdd - 24-08-2017

You can easily tell if your evo was opened before or not

Sent from my iPhone using Tapatalk Pro