Evo not detected on esys

[claw]

Hi everyone!

I have here one EVO that someone converted from id4 to id6. Unit was mounted and working on other car, going to be retrofited on a different car.
I have it now on bench, but is not detected on esys, tool32 etc. Besisdes that, it is fully functional: everything works, including navigation.
I can ping unit, ssh is open.
Any idea why and how to repair it?

Thanks

 

[samsonx]

I am just starting working on EVO on the bench and when I connect to HU directly from esys its through tcp://169.254.199.99:6801 as the setup doesnt have a ZGW. I have not been able to get tool32 to connect with this config.. do you have a ZGW on the bench as well? How are you trying to connect from esys, from tool32?

 

[claw]

I do have a ZGW and ignition emulator (can).
I can't access EVO, not even with gateway/directly ip to HU.
I only have ssh access. I think that whoever converted from id4 to id5 has clear v850 and ssh was kept open.

 

[samsonx]

Did you happen to check ista to see if it reports errors for the hu? Honestly not sure what he is needed to check ista on bench, so maybe would require reinstalling in vehicle to check.. from what I've read the only way to reset the hu is via vo coding or I-level update which seems that you would be blocked from performing w/o esys

 

[claw]

Did you happen to check ista to see if it reports errors for the hu? Honestly not sure what he is needed to check ista on bench, so maybe would require reinstalling in vehicle to check.. from what I've read the only way to reset the hu is via vo coding or I-level update which seems that you would be blocked from performing w/o esys

The problem is not the bench or the Evo on bench.
I have done dozens of HU on this same bench before. Flashing, coding, whatever.

This HU has damaged bootloader somehow. It needs to be repaired.