[danyro]

Guys,

I did not manage to find a clear answer to the question:
How to connect in E-sys in order to flash/update to the latest ilevel a factory fitted NBT EVO?

I am asking because for an unknown reason, tried to go to the latest ilevel and the update started via UDS using ENET cable. For the previous ones, I used ICOM A2 clone and went ok.

I used dhcp, so zgw and other modules got ip.
In e-sys i chose "Connection via gw(tcp://IP:6801)" and then started the flash process with default settings(parallel programming etc). The flash goes into UDS mode for no reason. I've waited to finish the bootloader(90minutes) and then i've interrupted the process. Now the screen blue is present, which is logic.
I can fix it via ISTA+ as the ECU is in programming mode but i want to make it via E-sys.

Therefore, i have 2 scenarios:
1. in esys, use "Connection via gw URL and insert the ip of NBT(e.g: 169.254.199.99:6801) and then uncheck JUST parallel programming. Leave checked "Activate programming mode for switchable ECUs"
2. E-sys, use "Connection via VIN" and also, uncheck JUST parallel programing. Leave checked "Activate programming mode for switchable ECUs"

Which is the right way for flashing via ENET cable?

This is what I got into logs:
===============================================
TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2018/03/19-00:11:18.739
[] prepareTALExecution started [PROGRESS]
[] prepareTALExecution finished [PROGRESS]
[] prepareVehicleForFlash started [PROGRESS]
MCDDiagService<id=20600, job=com.bmw.psdz.jobs.common.MCD3_PrepareVehicleForFlash, service=CC, description=error: negative response : conditionsNotCorrect, link=#RtGen_MultipleEcuJob_LogicalLink> [DIAGSERVICE]
MCDDiagService<id=38000, job=com.bmw.psdz.jobs.common.MCD3_PrepareVehicleForFlash, service=RC_CPPC, description=ECU signaled that any ProgrammingPreCondition not fullfilled, but no further details provided from ECU!, link=HU_NBT2_63_ETHERNET> [DIAGSERVICE]
[] prepareVehicleForFlash finished [PROGRESS]
[HU_NBT2 - 63] prepareECUforFlash started [PROGRESS]
[HU_NBT2 - 63] prepareECUforFlash finished [PROGRESS]
[HU_NBT2 - 63] authenticateECUforFlash started [PROGRESS]
[HU_NBT2 - 63] authenticateECUforFlash finished [PROGRESS]
[HU_NBT2 - 63 - swfl_0000271a-006_016_002] Transaction type: swDeploy; Message: TA started [TRANSACTION]
[HU_NBT2 - 63] performEcuFlash started with protocol UDS [PROGRESS]
[HU_NBT2 - 63 - swfl_0000271a-006_016_002] Transaction type: swDeploy; Message: 0% progress on ECUId:HU_NBT2_0x63 [0% of swfl_0000271a-006_016_002] [TRANSACTION]
==============================================

any info/sugestions would be appreciated.
thanks!

[hero3838]

Guys,

I did not manage to find a clear answer to the question:
How to connect in E-sys in order to flash/update to the latest ilevel a factory fitted NBT EVO?

I am asking because for an unknown reason, tried to go to the latest ilevel and the update started via UDS using ENET cable. For the previous ones, I used ICOM A2 clone and went ok.

I used dhcp, so zgw and other modules got ip.
In e-sys i chose "Connection via gw(tcp://IP:6801)" and then started the flash process with default settings(parallel programming etc). The flash goes into UDS mode for no reason. I've waited to finish the bootloader(90minutes) and then i've interrupted the process. Now the screen blue is present, which is logic.
I can fix it via ISTA+ as the ECU is in programming mode but i want to make it via E-sys.

Therefore, i have 2 scenarios:
1. in esys, use "Connection via gw URL and insert the ip of NBT(e.g: 169.254.199.99:6801) and then uncheck JUST parallel programming. Leave checked "Activate programming mode for switchable ECUs"
2. E-sys, use "Connection via VIN" and also, uncheck JUST parallel programing. Leave checked "Activate programming mode for switchable ECUs"

Which is the right way for flashing via ENET cable?

This is what I got into logs:
===============================================
TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2018/03/19-00:11:18.739
[] prepareTALExecution started [PROGRESS]
[] prepareTALExecution finished [PROGRESS]
[] prepareVehicleForFlash started [PROGRESS]
MCDDiagService<id=20600, job=com.bmw.psdz.jobs.common.MCD3_PrepareVehicleForFlash, service=CC, description=error: negative response : conditionsNotCorrect, link=#RtGen_MultipleEcuJob_LogicalLink> [DIAGSERVICE]
MCDDiagService<id=38000, job=com.bmw.psdz.jobs.common.MCD3_PrepareVehicleForFlash, service=RC_CPPC, description=ECU signaled that any ProgrammingPreCondition not fullfilled, but no further details provided from ECU!, link=HU_NBT2_63_ETHERNET> [DIAGSERVICE]
[] prepareVehicleForFlash finished [PROGRESS]
[HU_NBT2 - 63] prepareECUforFlash started [PROGRESS]
[HU_NBT2 - 63] prepareECUforFlash finished [PROGRESS]
[HU_NBT2 - 63] authenticateECUforFlash started [PROGRESS]
[HU_NBT2 - 63] authenticateECUforFlash finished [PROGRESS]
[HU_NBT2 - 63 - swfl_0000271a-006_016_002] Transaction type: swDeploy; Message: TA started [TRANSACTION]
[HU_NBT2 - 63] performEcuFlash started with protocol UDS [PROGRESS]
[HU_NBT2 - 63 - swfl_0000271a-006_016_002] Transaction type: swDeploy; Message: 0% progress on ECUId:HU_NBT2_0x63 [0% of swfl_0000271a-006_016_002] [TRANSACTION]
==============================================

any info/sugestions would be appreciated.
thanks!

Did you find solution?