CarTechnoloGY
Flashing NBT and KOMBI with ICOM Original - 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: Flashing NBT and KOMBI with ICOM Original (/showthread.php?tid=76971)



Flashing NBT and KOMBI with ICOM Original - TIGHTFIN - 27-03-2023

Greetings to all. Need help, an error appears when programming NBT and KOMBI using E-Sys 3.35.3 (PSdZData FULL 4.37.42) ,connect ICOM original:


<[] Activate programming mode was not successful for: ECUId:HU_NBT_0x63 [WARN]>

<[] ECUId:HU_NBT_0x63 not accessible cause could not be switched to parallel programming mode [WARN]>

<[HU_NBT - 63] ECUId:HU_NBT_0x63 not accessible cause could not be switched to parallel programming mode [THROWABLE]>

<[KOMBI - 60] ECUId:KOMBI_0x60 not accessible cause could not be switched to parallel programming mode [THROWABLE]>

<[] ECUId:HU_NBT_0x63 not accessible cause could not be switched to parallel programming mode [WARN]>

It was necessary to flash (update the software version) KOMBI BMW F30. I looked at the Dependencies with the KOMBI firmware, It depends on HU_NBT, FEM_GW. I put all these blocks in TAL and when flashing errors.

I know that there are some features of setting up ICOM for NBT and KOMBI programming, I once heard somewhere. There's something with setting up IP in Windows and configuring via DHCP. Help, please


full LOG:

Read SVT before TAL execution started.
TAL execution started.
<ExecutionID=2023/03/26-21:23:33.764>
<[] prepareTALExecution started [PROGRESS]>
<[] prepareTALExecution finished [PROGRESS]>
<[] prepareVehicleForFlash started [PROGRESS]>
<[] prepareVehicleForFlash finished [PROGRESS]>
<MCDDiagService<id=240900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgModeCascade, service=RC_GAC - RoutineControl GetActualConfig, description=error: timeout, link=HU_NBT_63_ETHERNET_63> [DIAGSERVICE]>
<MCDDiagService<id=240900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgModeCascade, service=RC_GAC - RoutineControl GetActualConfig, description=error: timeout, link=HU_NBT_63_ETHERNET_63> [DIAGSERVICE]>
<MCDDiagService<id=240900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgModeCascade, service=RC_GAC - RoutineControl GetActualConfig, description=error: timeout, link=HU_NBT_63_ETHERNET_63> [DIAGSERVICE]>
<MCDDiagService<id=242900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgModeCascade, service=RC_SDB - RoutineControl SetDefaultBus, description=error: timeout, link=HU_NBT_63_ETHERNET_63> [DIAGSERVICE]>
<MCDDiagService<id=84900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgModeCascade, service=RDBI_FTP - ReadDataByIdentifier FlashTimingParameter, description=error: timeout, link=HU_NBT_63_ETHERNET_63> [DIAGSERVICE]>
<MCDDiagService<id=238900, job=com.bmw.psdz.jobs.common.MCD3_ActivateProgModeCascade, service=RC_AAM - RoutineControl ActivateApplicationMode, description=error: timeout, link=HU_NBT_63_ETHERNET_63> [DIAGSERVICE]>
<[] Activate programming mode was not successful for: ECUId:HU_NBT_0x63 [WARN]>
<[] ECUId:HU_NBT_0x63 not accessible cause could not be switched to parallel programming mode [WARN]>
<[HU_NBT - 63] ECUId:HU_NBT_0x63 not accessible cause could not be switched to parallel programming mode [THROWABLE]>
<[KOMBI - 60] ECUId:KOMBI_0x60 not accessible cause could not be switched to parallel programming mode [THROWABLE]>
<[] ECUId:HU_NBT_0x63 not accessible cause could not be switched to parallel programming mode [WARN]>
<[] 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".
TAL execution finished. Duration: "3min 12s".
<>
Read SVT after TAL execution started.
Read SVT after TAL execution finished.


RE: Flashing NBT and KOMBI with ICOM Original - laquangksxd - 27-03-2023

With icom you need to create dhcp server to be able to flash kombi/nbt


RE: Flashing NBT and KOMBI with ICOM Original - zero9 - 27-03-2023

Use simple enet cable for these modules.


RE: Flashing NBT and KOMBI with ICOM Original - Siki78 - 27-03-2023

(27-03-2023, 12:13 PM)zero9 Wrote:  Use simple enet cable for these modules.

Yes and use esys3.27.1


RE: Flashing NBT and KOMBI with ICOM Original - TIGHTFIN - 27-03-2023

(27-03-2023, 12:01 PM)laquangksxd Wrote:  With icom you need to create dhcp server to be able to flash kombi/nbt

Can you please tell me how to set up a DHCP server? Which program to use and which IP to register in Windows and which in DHCP. Thanks.