evoscan

iTrader: (-1)

Correct - the recovery mode is no longer a "mode", nor is it buried in the options. If an alternate mode of flashing exists for a given ROM / ECU, it is in the ECU menu along with the other flashing methods. In the Evo X case, look under the ECU menu, the last icon with a red arrow and red target symbol with the label "Recovery write to ECU".

evoscan

iTrader: (-1)

In the aforementioned case, it only becomes bricked when you turn the key off after a failed reflash. Are you saying that if you fail to exit programming mode in ecuflash you can brick your EvoX ecu? then why doesn't ecuflash detect this situation and self correct before its too late? and result in the ensuing pain of removing and bench flashing the EvoX ecu.

-Hamish.

MikeyPSF

No, failing to exit the programming state, which one enters just by doing a read, will not brick the ECU.

evoscan

iTrader: (-1)

when you turn the car off.. (1) fails to READ/WRITE via CAN, and (2) FAILs to start the car? in most peoples minds, that is what is called "bricked".

generally "bricked" refers to the fact that the problem has gone past the operators ability to fix it. in most cases users can not remove and bench flash their ecu. hence the term "bricked".

MikeyPSF

I'm not sure if I understand what you're trying to highlight or if you're posing a question, but I'd agree that if you need to remove the ECU from the car and wire up to it directly to recover it, that's probably appropriately called 'bricked' by most user's view. I think maybe you're also saying/asking that if a read fails and then you can't immediately start the car, the car is then bricked. That isn't the case.

To clarify my statement ("...failing to exit the programming state, which one enters just by doing a read, will not brick the ECU."), if you start a read on the Evo X, you enter the programming state. If that read is interrupted and you turn the car off after that interruption, the car won't start. That isn't because the ECU is bricked, it's just in the programming state. You can reconnect using EcuFlash and then select 'Exit Programming State' to get back to a totally normal state without any other steps. If you are in the middle of a reflash where a new ROM image has been partially written, but your USB cable pulls out half way through AND you then turn the car off, the ECU is bricked and will need to be bench recovered because even if you could reconnect and exit the programming state, you've still got a partially reprogrammed ECU with an invalid/incomplete ROM image. If the USB cable comes out, interrupting the write process, and you simply plug the cable back in and restart the process, EcuFlash will pick up where it left off, and then exit the programming state when it's done.

-Mike

evoscan

iTrader: (-1)

Thanks Mikey,

So what you are saying is what everyone already knows.

A) bricked = you're screwed, and you need to learn how to bench reflash to recover it.

B) reading a rom = no way to brick your ecu.

C) writing a rom = enter programming state -> write data -> exit programming state.

D) if you leave the vehicle key on, you can interrupt C above as many times as you like via accidental pullouts of the usb cable or laptop needs charging and restarting etc. just don't turn the key off! retry again in ecuflash and you will be fine, make sure its successful before turning the key off.

E) if you turn the key off before C above is finished = you're bricked, and need to do a bench recovery reflash.

F) if your car battery goes flat before C above is finished = you're bricked, and need to do a bench recovery reflash. (and hope like hell you aren't on the roadside somewhere)


did I get you right? we are now in 2016, does ecuflash have any improvements for E or F lately?

-Hamish.

MikeyPSF

Currently a bricking is only recoverable on the bench. It should be possible in the car but we've been unable to determine what other component in the system is causing a conflict. We had an Evo X here in the shop last year and tried to determine the offending item but not yet. If anyone has any interesting ideas, we're all ears. The physical ECU connections for the recovery in or out of the car are all the same, but something outside the ECU is causing conflict and even monitoring the car's communication network hasn't helped in isolating the issue.


Correct, but with the caveat that like your scenario C, a read of the ECU also enters the programming state so if you interrupt the read process you may have to select 'exit programming state' in EcuFlash to get the car back to normal, but no bench reflash is required.


Correct.


Correct.


Correct if you've gotten far enough in the process so that bits have been erased.


Correct. I would suggest never reflashing the ECU on the side of the road with a weak battery


We would need to get another Evo X back in the shop to try to isolate what in the car is causing the conflict. Although benching the ECU is a pain, it's been a long time since anyone has contacted us asking for assistance with the process so I get the impression that it is a rare occurrence. That might not be the case, but that's based on customers contacting us. We tend to prioritize what we get the most requests for.

-Mike
Tactrix

YaroRS

Guys, if ECU is locked on purpose, is it possible to read it on the bench ?