[gvitkis]

Hi friends,

I have a bench for FLASH EVO, fully functional.
My bench consists of ZGW2-8SK, with direct connection from the small ZGW connector to OABR, for 4 PIN ETH, plus ETH power supply connected to pin 29 of the Quadlook.
I have done FLASH many EVO, never any problems. I always run FLASH EVO with ENET
In the last 3 EVO a very strange thing happens to me.
All 3 FLASH EVO communicate only with UDS protocol, both for BL, SW, IBA, CD.
Before this strange problem, FLASH always started with the HTTP protocol, for BL, SW, IBA, CD. or it happened that only the BL was done in UDS, but although it was very fast, then everything else was done in HTTP.
I tried to modify the TAL, several times to force it in manual by inserting the KWP2000 or HTTP protocol to the BL, the same as all the SW, but it doesn't work, it always goes to UDS
I checked the integrity of the connections and the various PING, everything works perfectly.
I also tried with various versions of ESYS.
I don't understand why it only works in UDS
I am also attaching photos and XML FA-SOLL-TAL
Infinitely thank you very much..

[jb2005]

There isn't any problem. Bootloader should be flashed on UDS. Afterwards there are more mechanisms available to allow HTTP flashing. I don't understand why it's bothering you. It's not slow as you said.

[uprockin]

I have a similar issue. I actually didn't change any parameter, but bootloader started to flash in slow mode and takes approximately 1.5 hours (only for BL). Normally it was taking about 3-4 mins.
Your help is greatly appreciated.

[gvitkis]

I have a similar issue. I actually didn't change any parameter, but bootloader started to flash in slow mode and takes approximately 1.5 hours (only for BL). Normally it was taking about 3-4 mins.
Your help is greatly appreciated.

as it happens to me, but I don't understand why, do you have all the correct links and OABR?