Help! ECUflash Reading error with 06" FXT ECU

User topics relating to software that reflashes or modifes ECU code and data

Moderator: Freon

Help! ECUflash Reading error with 06" FXT ECU

Postby stingerwang » Mon Jul 23, 2007 6:26 pm

Today I wanted to use ECUFlash to read My FXT ECU's Flash Memory and at the process of reading, the engine stoped running itself without interrupting, the log shows reading error, and the error LEDs of engine and cruiser flickered.

I used ECUTEK clear the DTC and try again several times, the engine stoped again and again, and the LEDs flickered again and again.

I'm from P.R.china. My Subaru Forester 2.5XT belongs 06". but I don't know which Version the ECU on it is.

Before ECU Reading, a "Jumper set" of "ECUTEK Performance" has been pluged in "Green Socket" of My FXT, but ECU's Flash has not been reflashed by ECUTEK.

If the "Jumper set" of "ECUTEK Performance" pluged affected the ECUflash' reading operation and should be removed before reading?

The goale of Using ECUflash is preserving the original contents of the ECU flash of my car.

The ODBII cable used with ECUflash is "Tactrix OpenPort Universal for Mitsubishi and Subaru" I just received yesterday, although I ordered and payed for "Tactrix OpenPort for Subaru WRX and Drive-by-wire vehicles".

The two Cable have the same function or not?.
If the "Tactrix 2003-2005 WRX Reflash Connector" needs to be pluged in "Green Socket" ?

The Label of the ECU is showed bellow and the the contents of the log file as here:

[06:35:48.500] Version 1.30.1095
[06:35:48.515] 8 memory models read.
[06:35:50.390] 145 ROM metadata models read.
[06:35:50.390] checksum module "subarudbw" loaded.
[06:35:50.390] flashing tool "wrx02" loaded.
[06:35:50.390] flashing tool "wrx04" loaded.
[06:35:50.390] flashing tool "sti04" loaded.
[06:35:50.406] flashing tool "sti05" loaded.
[06:35:50.406] flashing tool "mitsukernel" loaded.
[06:35:50.406] flashing tool "mitsukernelocp" loaded.
[06:35:50.406] flashing tool "mitsubootloader" loaded.
[06:36:22.968] SSM2 init
[06:36:23.140] [FF] A2 10 11 42 42 50 41 06 F3 FA CB 84 2B 83 FE AC
00 00 00 60 CE D4 FD B0 60 00 0F 20 00 00 00 00
00 DC 00 00 75 1F 30 80 F0 E2 00 00 43 FB 00 F1
89 02 00 00 00 00 0D F0
[06:36:23.156] SSM2 ECU ID is 42 42 50 41 06
[06:36:23.156] SSM2 cmd_0x81
[06:36:23.234] SSM2 cmd_0x83
[06:36:23.281] SSM2 challenge-response
[06:36:23.328] SSM2 challenge is DB 7E 48 82
[06:36:23.343] SSM2 response is 06 8F 10 BD
[06:36:23.406] SSM2 cmd_0x10
[06:36:23.765] SSM2 validating kernel ram area addr: FFFF3000 len: 0C98
[06:36:50.437] SSM2 init
[06:36:50.593] [FF] A2 10 11 42 42 50 41 06 F3 FA CB 84 2B 83 FE AC
00 00 00 60 CE D4 FD B0 60 00 0F 20 00 00 00 00
00 DC 00 00 75 1F 30 80 F0 E2 00 00 43 FB 00 F1
89 02 00 00 00 00 0D F0
[06:36:50.609] SSM2 ECU ID is 42 42 50 41 06
[06:36:50.609] SSM2 cmd_0x81
[06:36:50.656] SSM2 cmd_0x83
[06:36:50.718] SSM2 challenge-response
[06:36:50.781] SSM2 challenge is 55 09 E6 4E
[06:36:50.781] SSM2 response is 05 05 D0 C1
[06:36:50.843] SSM2 cmd_0x10
[06:36:51.250] SSM2 validating kernel ram area addr: FFFF3000 len: 0C98

The last line is read error ...(not saved in log file).
Attachments
ECU Version of Forester 2.5XT.JPG
The Version of My FXT's ECU, From P.R.China.
ECU Version of Forester 2.5XT.JPG (25.93 KiB) Viewed 3219 times
stingerwang
 
Posts: 3
Joined: Sun Jul 08, 2007 5:51 pm
Location: Beijing, China

Postby Jon [in CT] » Tue Jul 24, 2007 9:35 am

It seems that you have the engine running while attempting to read your ECU's flash memory. You should not start the engine. You should turn the ignition key only to the ON position when instructed by EcuFlash.
Before ECU Reading, a "Jumper set" of "ECUTEK Performance" has been pluged in "Green Socket" of My FXT, but ECU's Flash has not been reflashed by ECUTEK.

If the "Jumper set" of "ECUTEK Performance" pluged affected the ECUflash' reading operation and should be removed before reading?
I do not know what the EcuTeK "jumper set" is, but it is not needed for your 2006 Forester XT. There should be two green 'test' connectors which must be joined together only when you read or reflash your ECU. The article at http://www.scoobypedia.co.uk/pub/web/Knowledge.ConnectingToYourECU.html has some pictures.
he ODBII cable used with ECUflash is "Tactrix OpenPort Universal for Mitsubishi and Subaru" I just received yesterday, although I ordered and payed for "Tactrix OpenPort for Subaru WRX and Drive-by-wire vehicles".

The two Cable have the same function or not?.
If the "Tactrix 2003-2005 WRX Reflash Connector" needs to be pluged in "Green Socket" ?
The Tactrix cable you received will work with your car. You need to connect the larger connector to the car's OBD-II connector on the lower dashboard and the USB connector to your computer. The other smaller connector on the Tactrix cable is used only with Mitsubishi cars.

Your ECU is the same as the one used in Europe for the 2006 Forester XT automatic transmission. Its calibration ID is A8DH100P and it is supported by the Enginuity ROM editor at http://www.enginuity.org.
Jon [in CT]
 
Posts: 352
Joined: Sat Jan 01, 2005 10:23 am

Postby stingerwang » Thu Jul 26, 2007 12:14 am

Thank you a lot!
stingerwang
 
Posts: 3
Joined: Sun Jul 08, 2007 5:51 pm
Location: Beijing, China


Return to Reflashing Software

Who is online

Users browsing this forum: No registered users and 43 guests