openecu.org

Ok, we do a read to be sure everthing is working correctly. Everything looks fine. Go to flash it, everything looks fine. Success... not. Fuel pump primes for a split second everytime you key on, but will never start. Disconnect the battery, try again. Software never connects again and the car will not go into test mode. We have never had this problem with a WRX ecu, on the STi, twice. Someday ebay WILL run out of 04 ecus. What is wrong? Can the ecus be saved? When we try to connect after the flash fails, we get the error where it tries to validate ram address bla bla bla and fails.

[05:20:18.915] Version 1.28.716
[05:20:18.925] 8 memory models read.
[05:20:19.175] 73 ROM metadata models read.
[05:20:19.175] checksum module "subarudbw" loaded.
[05:20:19.175] flashing tool "wrx02" loaded.
[05:20:19.175] flashing tool "wrx04" loaded.
[05:20:19.175] flashing tool "sti04" loaded.
[05:20:19.175] flashing tool "sti05" loaded.
[05:20:19.175] flashing tool "mitsukernel" loaded.
[05:20:19.175] flashing tool "mitsukernelocp" loaded.
[05:20:19.175] flashing tool "mitsubootloader" loaded.
[05:20:19.175] error loading FTD2XX.DLL
[05:21:05.782] ssm2_init
[05:21:06.013] ssm2_init
[05:21:06.253] ssm2_init
[05:21:06.473] ssm2_init
[05:21:06.694] ssm2_init
[05:21:06.924] ssm2_init
[05:21:07.144] ssm2_init
[05:21:07.365] ssm2_init
[05:21:07.595] ssm2_init
[05:21:07.835] ssm2_init
[05:21:08.236] kernel get version
[05:21:08.777] validating denso kernel ram area addr: FFFF6000 len: 0008

Wow, not sure what to say. I've been plugging away on mine for months.

I'd be extra careful before you turn the key off. Double check the log before you turn the key back from ignition on, because that's the "point of no return" so to speak. If you have any sort of flashing problem you can reboot your laptop completely, disconnect the cable, etc. and retry as long as you haven't touched the key.

Unfortunately I think the most useful tool would be the log from the last time you flashed the ECU, but you're not going to think to save it every time.

Where both on the same car? Different cars? Same exact model ECU? (AJ242, AJ243, etc)?

Both times it said all was cool. Both times the car didn't start and never went into test mode again. Is there a way to hard dump to the rom?

What was the ROM version you read from the ECU? What did you flash back in its place? If the flash was successful (which requires CRC32 checks on all of the blocks), you can be pretty sure EcuFlash flashed exactly what you gave it to flash. The issue then comes down to did you flash a ROM image that did not come from this car, or was otherwise modified in a way that would cause the ECU to hang?

[quote[05:20:19.175] error loading FTD2XX.DLL
[/quote]

From your log it doesnt seem like it flashed.

clear this error first by copying FTD2XX.DLL to the /windows/system32 dir

Then do a read. if that is good do a test flash.

always keep a copy of the origial rom.

Hobbes

perhaps we could hack the JTAG function on the sh7055 to do a hard flash?
I just checked the datasheet, its got all of the necessary pins.....

anyone know anything about this?

I guess I should try it since I'm a EE and I think this just happened to my 2004 USDM WRX's ECU.

I guess I should try it since I'm a EE and I think this just happened to my 2004 USDM WRX's ECU.

I'm concerned that you got the FTD2XX.DLL error.. That doesn't seem right, if your getting anywhere at all I'm actually surprised.

On the EVO you can recover a smoked ECU by flashing it again, if it doesnt respond we use a universal init code to bypass the flashed rom and bootloader..

On the Subaru its a little more complicated, but using a JTAG will recover it, if you know the layout of the pads, you can buy a JTAG tool that can mount on the pads temporarily. Unfortunately I have no idea how you would get further than that since I have no experience with your ECU.

Oh and this may sound trivial..

But does the 04 and Later STi have Immobilizers? If they do, its possible your unable to start the car because the code has been lost. I have also heard of locked ECUs from ECUTek with later Subarus that don't respond to inits similar to what your experiencing.

The bad news is I have absolutely no information other than a best guess for you.

04 does not have the immobilizer.

Is there information on which chips are which on the forum somewhere?

technical information forum, there are links to datasheets for all of the microcontrollers ecuflash supports and then some!

it would be a great thing to fall back on.

WOTboy, are you registered on enginuity?
I started a JTAG information compiliation thread there:
http://www.enginuity.org/viewtopic.php?p=6768#6768

Same problem today on my 05 LGT. ER HC on the speedo and Get Kernel Error. Everything flashed OK and I clicked on Compare to ECU to double check. All CRC's were ok. Turned the car off. It won't start now.

What version of cable are you using? 1.2 or 1.3? I have 1.3. Flashed many times before with 1.2 and worked every time. I tried the 1.3 maybe 4 times and now this??

Is it normal for the black connector to separate into 2 pieces when removing it from the OBD plug? Does it need more glue?

I emailed Colby. I'm hope he can provide some support.