openecu.org

I am using the blue jumper connector and the OBD2 USB cable with the green jumpers plugged together and when I try to read the stock ROM it always says that there is an error. using ECU flash the latest version.

I have read on the forum here that I should try the older ecu flash version and that did the same thing. I also tried using ECU explorer and had similar results.

Any Help?

[16:34:17.046] Version 1.40.2178
[16:34:17.062] 19 memory models read.
[16:34:17.062] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[16:34:17.187] 319 ROM metadata models scanned.
[16:34:17.187] checksum module "subarudbw" loaded.
[16:34:17.187] flashing tool "wrx02" loaded.
[16:34:17.187] flashing tool "wrx04" loaded.
[16:34:17.187] flashing tool "sti04" loaded.
[16:34:17.187] flashing tool "sti05" loaded.
[16:34:17.187] flashing tool "mitsukernel" loaded.
[16:34:17.187] flashing tool "mitsukernelocp" loaded.
[16:34:17.187] flashing tool "shbootmode" loaded.
[16:34:17.187] flashing tool "shaudmode" loaded.
[16:34:17.187] flashing tool "subarucan" loaded.
[16:36:59.718] Using interface OpenPort 1.3 Universal TX28SxNZ658974d5515c1130615c84cc77adf96267fb59d3
[16:37:03.983] denso02_bootloader_cmd_start
[16:37:05.311] denso02_bootloader_cmd_start
[16:37:06.577] denso02_bootloader_cmd_start
[16:37:07.811] denso02_bootloader_cmd_start
[16:37:09.046] denso02_bootloader_cmd_start
[16:37:09.499] kernel get version
[16:37:09.827] interface close
[16:37:09.827] interface close


Any Help?

Check there's not a second set of green test connectors around. If it's working properly, when you first turn the key on the fans will cycle. If not, reflashing won't work.

Where would the second set of green jumpers be? driver or passenger side?

Try behind carpet near ECU (passenger footwell), or even behind driver's side kick panel.

Found the green plug in passenger footwell. It was already connected and tried it with it unplugged. Still same result.

I need to get this thing inspected this week!!! or I will be fined!!!

Please Help!!

Before you continue make sure the car goes into test mode, i.e., the fans cycle. Is that happening? Don't bother proceeding unless it is.
When you know that's right, turn the key on (and enter immobilzer code if applicable) and immediately after (within a few seconds) click 'Ok' to initiate the connection with ECUFlash.
I presume you're using the correct hookup method?

When I turn on the ignition, the fans start cylclig within a few seconds. and I ahve been able to use Rom raider Logger on this car so I think I am able to communicate with the car fine.

Is the "imobilizer code" the one that pops up on a list of makes and models when I click on read eCU?

Also how can I make sure that i am on the corrcet hookup method?

Using the same software and OBD2 cable i am able to talk and reflash to my 2005 WRX with the different jumper plug. Also there is a second 8-pin plug on the 2002 under the dash that is not hooked up to anything, but the OBD kit I bought has nothing that will fit that plug.

sub hu man wrote:When I turn on the ignition, the fans start cylclig within a few seconds. and I ahve been able to use Rom raider Logger on this car so I think I am able to communicate with the car fine.

So far so good.

Is the "imobilizer code" the one that pops up on a list of makes and models when I click on read eCU?

No. On cars with immobilizers, when you turn the key on, you need to enter the code on the keypad first before the car powers up.

Also how can I make sure that i am on the corrcet hookup method?

For 2l models (non-DBW), use either of the 01-05 WRX non-USDM, or the 02-03 USDM, or 04-05 USDM methods. It'll be one of these.

I tried all 3 hookup methods and still got the same result. I also tried pressong the OK button right at the same time as turning on the ignition. Same result.

Any other suggestions?

Is the ECU locked? EcuTeK or Cobb? If so you'll have problems.

This ECU to my knowledge has never been flashed before. I have had it completely out before while running a plug and platy unit.

I am past the point of getting it inspected but I would like to figure out what I am doing wrong so that next year I won't have to go through this again.

I read somewhere else that someone had to use ecu explorer to talk to his 2002. I'm not sure where to get this software.

I finally was able to talk to this ECU. It turns out that something was wrong with the ECU itself. I got my hands on another one, plugged it in, and was immediately able to talk to it. Strangely, the car ran fine the whole time only throwing code thta I knew about involving the emmisions and O2 sensors. Thanks for all of the help everyone. I will now be working on my 2005 2.0L.