Problem 1:
Foxflash crashed while writing VW EDC16U31 ECU? I can’t even provide identification now.
Solution:
It is bricked.
It has to be done either in bdm or jtag very easy to do and can be done with foxflash.
Kess clone or ktag clone make this ecu easy.
Problem 2:
edc16u31 bricked while cloning with foxflash, was cloning in bench after writing intFl ecu bricked, now no connection thru jtag. i am wrong?
Solution:
You’re doing it wrong, supply power through the board to the BDM pins.
You can ktag bdm, but fox flash also does it well via bdm, only the power must be supplied to the bdm pins.
Like this
Problem 3:
Tried to read VW EDC16U31 bricked ECU, mpps or kess2 could not read ecu.
decided to read/write with Foxflash on bench. Foxflash failed to write it as well. Voltage 12.2v.
Solution:
Add voltage over 13v, the basic power ac-dc just gives 12v.
You need minimum 13.2V for that. If you don’t have power source just bring another car and connect to your car with jumper cables, and let the engine run.
These u31s are tricky on every tool.
You can read write only full data via bench. Extflash and so on only by bdm. A lot of tools brick this ecu, so:) The problem is not the tool or voltage, the problem is with protocol.
When it bricks, you need to do by bdm to recover, then write with obd, and everything will be ok.
EDC16U31/U34 need proper checksum always from fresh file. If you need additional changes in your file, you need make a scrip in Wols and applicate on fresh file then let the tool do checksum.