Quote:
Originally Posted by dave-
General question here about bad flash a while back.
Basically went to flash like normal and it failed, don't recall the error and can't find the full log but I left the ignition on and only hit write again. It worked but I got the following error on the second write attempt. I assume it is because the first failed write erased everything?
Code:
[11:46:29.509] reading vehicle info...
[11:46:31.514] OBDII communications failed - trying OEM bootloader...
[11:46:31.515] connected to OEM bootloader!
[11:46:31.515] preparing to write area 00008000-0013FEFF...
[11:46:31.517] erasing area 00008000-0013FEFF...
[11:46:37.110] writing area 00008000-0013FEFF...
[11:48:15.121] interface close
Did I avoid a brick by leaving the ignition on and just doing another write? Or is ecuflash smart enough that it would just been able to write the ROM again regardless of what I did with the ignition? |
You will probably never know.
but always safer to try writing again before turning ignition off as you can always try again after turning ignition off.
The ECU is still in program mode from previous write attempt, till ignition is turned off.
Their are three ROM area in the ECU
1. SH Boot area (very low level boot area) need serial communication to access ie soldering wires to ECU
2. USER BOOT Area can be accessed via OBD port
3. USER ROM area - the area flashing devices read/erase/write/talk to.
Appears all flashing devices only write to the third area USER ROM area.
So you connect your flashing device, it initially tries to communicate with the software code in the USER ROM area via OBD communication method. If no response the Tactrix and other system can try communicating with the USER BOOT area code. This is your get out of jail free card if flash fails part way through.
Main causes of failed flash are bad connection to obd port, low or flat car battery or laptop issues.
As I understand it Tactrix tries to communicate with the ECU via the OBD communication method first . I believe this is communicating via the software thats contained in the rom you flash. You only get one go at this method as USER ROM area is ERASED before write takes place.
I suspect what happened was
1. Initial flash failed part way through for unknown reason.
2. USER ROM area now erased or partial write
3. Second time tectrix tries to talk to ecu via code in USER ROM area which is trashed it fails
4. Tectrix tries comms via USER BOOT code, comms established , USER ROM area erased and written successfully.
The big problem occurs when you write complete rubbish code, or for some reason the partially written rom cause the ecu to loop or go into some other weird state where you have no communication via the OBD port.
Check your obd connection by either READING ROM or LOGGING and wiggle connection if it drops out during READ or you get heaps of short log files you have connection issues.