06' EDM Forester turbo

06' EDM Forester turbo

Postby ecuflasher » Wed Jul 25, 2007 10:30 am

Hi guys,

I'm trying to read the ROM off my 06' EDM Forester turbo carefully following the instructions given within this forum but I still can't connect to the ECU.

I connected the green diagnostic connectors on the driver side and the fans cycled on and off when the ignition is turned on. I take this to indicate successful test mode. I checked to see if there's another set of green diagnostic connectors on the passenger side but couldn't see any. I reckon the driver side shld be the correct set for my car since I can enter test mode so I proceeded to the next step.

I then used Ecuflash 1.30 and selected "2005-2006 Subaru DBW models", click on 'Read' and then turned on the ignition key immediately after clicking the prompt. I then got the following error :

"
[00:39:35.656] SSM2 init
[00:39:35.916] [FF] A2 10 11 4E 42 50 40 07 F3 FA C9 8C 2B 83 FE AC
00 00 00 66 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 F5
C9 86 00 00 00 01 2D F1 80 00 81 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
[00:39:35.916] SSM2 ECU ID is 4E 42 50 40 07
[00:39:35.916] SSM2 cmd_0x81
"

I tried all other options but all gave me the same error message. I tried using 1.29a and got a different error message :

"
[00:40:34.490] ssm2_init
[00:40:34.720] ssm2_init
[00:40:34.730] ssm2_init
[00:40:34.761] ssm2_init
[00:40:34.781] ssm2_init
[00:40:34.801] ssm2_init
[00:40:34.811] ssm2_init
[00:40:34.831] ssm2_init
[00:40:34.841] ssm2_init
[00:40:34.871] ssm2_init
[00:40:35.061] kernel get version
[00:40:35.381] validating denso kernel ram area addr: FFFF0000 len: 0008 "

What did I miss?
ecuflasher
 
Posts: 13
Joined: Wed Jul 25, 2007 2:36 am

Postby Freon » Wed Jul 25, 2007 1:54 pm

Did you connect the white connectors? It seems some users have reported a white set on both sides of the car with some non-US models. The white connectors are generally just a single white connector, and the pins need to be connected across. You can look at the tactrix site for hints as to how the wires need to be connected if there is a 4-conductor cable. Obviously if it is just a two conductor, just connect them. You can use paperclips initially, though if one looks like it will fit I suggest buying a flash connector from tactrix.com .
Freon
 
Posts: 700
Joined: Thu Nov 17, 2005 5:50 pm
Location: Indianapolis, IN

Postby ecuflasher » Thu Sep 20, 2007 12:34 am

I checked for the white connectors but there isn't any. I tried using version 1.32 but it cannot access the ROM too. Error message as follows :

[16:34:04.148] Version 1.32.1399
[16:34:04.148] 11 memory models read.
[16:34:04.148] scanning for metadata models in E:/CarTuning/Tuning/EF09/rommetadata
[16:34:04.179] 83 ROM metadata models scanned.
[16:34:04.179] checksum module "subarudbw" loaded.
[16:34:04.179] flashing tool "wrx02" loaded.
[16:34:04.179] flashing tool "wrx04" loaded.
[16:34:04.179] flashing tool "sti04" loaded.
[16:34:04.179] flashing tool "sti05" loaded.
[16:34:04.179] flashing tool "mitsukernel" loaded.
[16:34:04.179] flashing tool "mitsukernelocp" loaded.
[16:34:04.179] flashing tool "shbootmode" loaded.
[16:34:08.925] SSM2 init
[16:34:09.376] SSM2 init
[16:34:09.646] SSM2 ECU ID is 4E 42 50 40 07

Very frustrating :(
ecuflasher
 
Posts: 13
Joined: Wed Jul 25, 2007 2:36 am

Postby Freon » Thu Sep 20, 2007 10:21 am

There are two different 32bit DBW CPUs. 7055 (512kB) and 7058 (1MB). They're mostly the same except for flash size and memory model. They do take a different flash method. In the US market, the 7055 was only used in 2004, and all 2.5L Turbo DBW cars switched to the 1MB 7058 in 2005+. I think it is called "sti04" in the XML.

It could be in other markets they kept using the 7055 for more years. I would try using the 2004 DBW flash method.

Also, looking back I'm not sure why I suggested checking the white connector. I don't think it is required in any DBW car. You should, however, check for green connectors on both sides of the car. They require no plug, just take the two green pieces and connect them.
Freon
 
Posts: 700
Joined: Thu Nov 17, 2005 5:50 pm
Location: Indianapolis, IN

Postby radsdau » Thu Sep 20, 2007 4:16 pm

To make sure, pull your ECU out, take the lid off, and see what's written on the top of the micro (the big chip)
radsdau
 
Posts: 674
Joined: Wed Feb 08, 2006 6:56 pm

Postby ecuflasher » Tue Sep 25, 2007 12:16 am

radsdau wrote:To make sure, pull your ECU out, take the lid off, and see what's written on the top of the micro (the big chip)


I opened up the ECU and here are the numbers :

Big Chip : 64F7058F80

Which method do I use?
ecuflasher
 
Posts: 13
Joined: Wed Jul 25, 2007 2:36 am

Postby ecuflasher » Tue Sep 25, 2007 1:40 am

I tried using all the flashing methods (Subaru) and using 1.29a, 1.30 and 1.32 but still cannot access the ECU.
ecuflasher
 
Posts: 13
Joined: Wed Jul 25, 2007 2:36 am

Postby salex » Tue Sep 25, 2007 1:38 pm

Tried on an early 2007 EDM Forester turbo... Same. No luck! ECU not yet supported.
salex
 
Posts: 72
Joined: Wed Jun 21, 2006 2:30 pm
Location: Greece

Postby Freon » Tue Sep 25, 2007 2:56 pm

7058 is sti05 method.
Freon
 
Posts: 700
Joined: Thu Nov 17, 2005 5:50 pm
Location: Indianapolis, IN

Postby radsdau » Tue Sep 25, 2007 4:09 pm

I suspect the current model ECUs still use 7058 but something else is different and they won't allow connection using current known methods.
Either that or there is some other connection that needs to be made. Has anyone buzzed out the green connector wire to an ECU pin to make sure it's actually getting there? (I don't know what ECU pin it is).
If that connection is complete and it still don't work, it'll most likely be a new method. Bring on the Colby genius! (there have got to be a few more genius's (genii?) on this forum by now too that could crack this, particularly someone who has access to a Subaru tool)
radsdau
 
Posts: 674
Joined: Wed Feb 08, 2006 6:56 pm

Postby ecuflasher » Sun Sep 30, 2007 7:04 pm

Looks like this is going to take awhile :)
ecuflasher
 
Posts: 13
Joined: Wed Jul 25, 2007 2:36 am

Postby salex » Mon Oct 01, 2007 5:54 am

Anybody tried 1.33 on it yet?
salex
 
Posts: 72
Joined: Wed Jun 21, 2006 2:30 pm
Location: Greece

Postby ecuflasher » Wed Oct 03, 2007 7:31 am

salex wrote:Anybody tried 1.33 on it yet?


Just downloaded and tried using 1.33. However, the app crashed whenever I
select "Read from ECU" and select ANY flashing mode. The error msg is "AppName: ecuflash.exe AppVer: 0.0.0.0 ModName: ftd2xx.dll
ModVer: 3.1.7.1 Offset: 00004fb2"

I tried reinstalling the whole app but it still happens. It cannot work for Subarus or Mitsus.
ecuflasher
 
Posts: 13
Joined: Wed Jul 25, 2007 2:36 am

Postby ecuflasher » Wed Oct 24, 2007 7:04 pm

Bump
ecuflasher
 
Posts: 13
Joined: Wed Jul 25, 2007 2:36 am

Postby Jon [in CT] » Thu Oct 25, 2007 5:00 am

ecuflasher wrote:
salex wrote:Anybody tried 1.33 on it yet?


Just downloaded and tried using 1.33. However, the app crashed whenever I
select "Read from ECU" and select ANY flashing mode. The error msg is "AppName: ecuflash.exe AppVer: 0.0.0.0 ModName: ftd2xx.dll
ModVer: 3.1.7.1 Offset: 00004fb2"

I tried reinstalling the whole app but it still happens. It cannot work for Subarus or Mitsus.
I don't think that version 3.1.7.1 of ftd2xx.dll is the version which is packaged with version 1.33 of EcuFlash.
Jon [in CT]
 
Posts: 352
Joined: Sat Jan 01, 2005 10:23 am

Next

Return to Subaru (all models)

Who is online

Users browsing this forum: No registered users and 18 guests