openecu.org

Posted: **Sat Jul 22, 2006 4:06 pm**

anyone else had this problem

thanks

jason

aim= fljason86

Posted: **Sat Jul 22, 2006 6:38 pm**

i can't make your thumbnail any bigger - it's hard to read!

Posted: **Sat Jul 22, 2006 11:08 pm**

[00:25:39.854] Version 1.28.716
[00:25:39.864] 8 memory models read.
[00:25:40.144] 71 ROM metadata models read.
[00:25:40.144] checksum module "subarudbw" loaded.
[00:25:40.144] flashing tool "wrx02" loaded.
[00:25:40.144] flashing tool "wrx04" loaded.
[00:25:40.144] flashing tool "sti04" loaded.
[00:25:40.144] flashing tool "sti05" loaded.
[00:25:40.144] flashing tool "mitsukernel" loaded.
[00:25:40.144] flashing tool "mitsukernelocp" loaded.
[00:25:40.144] flashing tool "mitsubootloader" loaded.
[00:25:40.144] error loading FTD2XX.DLL
[00:26:02.807] ssm2_init
[00:26:02.977] ECU ID is 2E 04 49 60 05
[00:26:02.977] ssm2_cmd_0x81
[00:26:18.038] denso02_bootloader_cmd_start
[00:26:19.250] denso02_bootloader_cmd_start
[00:26:20.462] denso02_bootloader_cmd_start
[00:26:21.674] denso02_bootloader_cmd_start
[00:26:22.885] denso02_bootloader_cmd_start
[00:26:23.296] kernel get version
[00:26:37.186] 196608 byte image read.
[00:26:43.735] denso02_bootloader_cmd_start
[00:26:44.947] denso02_bootloader_cmd_start
[00:26:46.159] denso02_bootloader_cmd_start
[00:26:47.371] denso02_bootloader_cmd_start
[00:26:48.592] denso02_bootloader_cmd_start
[00:26:49.003] kernel get version

at the kernal get version is where i get the error "an error has occured, please see the log for details'

Posted: **Sun Jul 23, 2006 8:53 pm**

looks like it cant find your cable driver to me...

Posted: **Sun Jul 23, 2006 8:56 pm**

This is the result you would get if you didn't have the test mode connector connected. Are the fans cycling when you turn the car on?

Posted: **Mon Jul 24, 2006 6:14 am**

yep fans turn on the green connectors are pluged in and the clear jumper is also plugged in

jason

Posted: **Mon Jul 24, 2006 8:03 am**

what year/model is the vehicle?

Posted: **Mon Jul 24, 2006 1:21 pm**

04 wrx it was able to flash before .. i put a map on the ecu and now i am not able to flash it anymore

Posted: **Mon Jul 24, 2006 3:57 pm**

An E**tek map ?

Posted: **Mon Jul 24, 2006 4:37 pm**

no thats what i thought it might be but its a map for a vf34

Posted: **Mon Jul 24, 2006 5:35 pm**

The ROM is A4TE002B, which appears to be an 03 JDM STI twin scroll. The only thing changed from the reference ROM I have is the injector flow scaling. Does this ROM even allow your car to run? Why did you flash this ROM into a USDM(?) 04 WRX?

Posted: **Mon Jul 24, 2006 7:57 pm**

the car runs great just runs rich idles a little high. this is what one of the members told me their map was and they had the same setup.

is there anyway to flash a new map on it with out getting the kernal error

Posted: **Tue Jul 25, 2006 9:20 am**

my concern is that you have put a 2003 JDM ROM in a 2004 USDM vehicle. the 2003 ROM may use the LE line on the OBD connector to boot into the reflash mode. the 2004 ROM / ECU / harness doesn't use that wire boot into the reflash mode (it does it over SSM solely), and may use a different ECU pin for the LE line than the JDM (i don't have the JDM schematics, so I can't be sure). if the wiring is somehow different, the code you are running now on your ECU can't "hear" EcuFlash requesting to go into the boot mode anymore.

what about the person that shared the ROM with you? what vehicle are they running it on?

colby

Posted: **Tue Jul 25, 2006 9:50 am**

so in short i messed up and now the ecu dosent realize taht im trying to talk to it... how would i go buy fixing this if i can at all

jason

Posted: **Tue Jul 25, 2006 9:56 am**

if you have a spare ECU to swap out to keep you car running, you can send your ecu to me and i can either reflash it on my bench setup, or i can reprogram it using a BDM. the ECU is definitely recoverable.

colby