[HU_man]

Confirmed BTLD flashed over UDS not HTTP like remain parts.

[danyro]

And then the question remains - why sometimes the speed is 21kB/s and sometimes is running at full speed like the swfl parts eg 70Mbps...what makes this difference?

[BimmerSLO]

Proven solution with ENET cable

1. Connect to car via ENET and TFTPD64 HTTP server. IP under connect via VIN in ESYS should be like 192.168.x.x
2. Prepare SVT_ist, SVT_soll and TAL in newer ESYS with latest psdzdata
3. Close new ESYS and open ESYS 3.27.1, open TAL and SVT_soll in TAL execution, read FA.
4. Enable Parallel programing under Parameters and check Activate programming mode for switchable ECUs (leave address field blank)
5. Check blFlash, swDeploy, cdDeploy and ibaDeploy
6. Execute TAL >>Start<<

blFlash always uses UDS protocol. swDeploy and ibaDeploy use HTTP protocol, but ESYS 3.27.1 has a software bug,
where in Log file it will state that it is flashing swDeploy with UDS, but actually it is doing it with HTTP.
If TTS is taking 15min to flash, you know you are running HTTP.

cdDeploy might fail and car could get stuck in Transport mode. You need to then deactivate Transport mode with ISTA and afterwards disconnect and reconnect the battery.
Maybe clear transport mode once again. After that, do Detect CAF with newer ESYS on NBT.