openecu.org

Posted: **Fri Jan 12, 2007 8:54 am**

Hi guys,

My tuner has pulled the ROM from my new MY07 Forester STI, but as yet has had no luck flashing back....

In the interim, armed with the tactrix cable I thought I would go through the motions to connect up, just as a learning process.

I have connected the green connectors under the OBD-II connecter, and followed the instructions selecting a DBW 2005-2006, but it bombs out saying check the log.....the log doesnt really give much away. As Colby mentions in other posts, I did this with the clutch in as it's a JDM model.....

[20:13:15.843] Version 1.29.906
[20:13:15.843] 8 memory models read.
[20:13:16.968] 140 ROM metadata models read.
[20:13:16.968] checksum module "subarudbw" loaded.
[20:13:16.968] flashing tool "wrx02" loaded.
[20:13:16.968] flashing tool "wrx04" loaded.
[20:13:16.968] flashing tool "sti04" loaded.
[20:13:16.968] flashing tool "sti05" loaded.
[20:13:16.968] flashing tool "mitsukernel" loaded.
[20:13:16.968] flashing tool "mitsukernelocp" loaded.
[20:13:16.968] flashing tool "mitsubootloader" loaded.
[20:13:41.062] ssm2_init
[20:13:41.203] ECU ID is 3B 02 59 43 16
[20:13:41.203] ssm2_cmd_0x81
[20:13:41.250] ssm2_cmd_0x83
[20:13:41.296] denso challenge-response
[20:13:41.343] challenge is AB D1 8E 14
[20:13:41.359] response is 00 43 53 2D
[20:13:41.406] ssm2_cmd_0x10
[20:13:41.765] validating denso kernel ram area addr: FFFF3000 len: 0C28

Any ideas?

Mark

Posted: **Fri Jan 12, 2007 4:14 pm**

Any chance you might be able to take the case of the ECU and get some pictures of the board, including the part numbers on the chips and the frequency number of the crystal? It might be that this ECU clocks faster and need different baud rate timing for the kernel to communicate with it.

Colby

Posted: **Sat Jan 13, 2007 12:07 am**

Hi Colby, can do....I thought though that Zak, had already sent you this info?

Mark

Posted: **Sat Jan 13, 2007 10:39 am**

Posted: **Sun Jan 14, 2007 1:27 pm**

Colby, this is the ECU that Zak could not flash back to, and discussed pulling it and sending it to you....

Is this still an option? Or is there someone closer to home that can work it on the bench...??

Mark

Posted: **Mon Jan 15, 2007 1:47 am**

OK, managed to pull it as 2004 DBW even though it is a MY07.....

I am a complete noob so any help from here onwards is appreciated. As I understand it from my tuner he has pulled all the tables and made a definition, but failed to flash it back.

I would like to try and test flash it back myself before I consider pulling the ECU and sending it somewhere.....but at the moment not sure how to do that and do not want to 'play' without some experienced help...

Thanks,

Mark

Posted: **Mon Jan 15, 2007 10:10 am**

EcuEdit says ECU ID is A2WC012E.....

Edited: Naah, dont think this is right! Think this was generated by me finger clicking trying to get past the ROM ID definition so I could save the file... using (sti04base)

Posted: **Tue Jan 16, 2007 11:17 am**

Colby if you read this...

I am off on vacation on Sunday for a couple of weeks, and it would be the perfect time to pull the ECU and send it to you, if you are still OK with taking a look at it....

I would really like to try and test flash it myself, but with no definitions I am a bit stuck....

Let me know if you can help.

Thanks in advance..

Mark

Posted: **Tue Jan 16, 2007 11:28 am**

Apparantly it is A2WC012E at 0x2000.....and as the size is 512kb I guess it is a 2004 32-bit rom....

I'm slightly confused that I have a MY07 that reads as a 2004 and has a 512kb size....

Posted: **Tue Jan 16, 2007 11:46 am**

OK, using XMLWRITE I found a definition that looks similar A2WC011E, so I created a file and edited the headers.....

Will the attached file be OK to test flashing back?

Thanks,

Mark

Posted: **Wed Jan 17, 2007 4:26 am**

Did a test flash this morning after changing 'DENSO' to 'MARKY' and test flashed OK, then went for an actual flash and it failed.....

Restored with the original file and it said there were no differences when test flashing, but went ahead and flashed the original file back ok...

So I am seeing the same as my tuner! As soon as anything is modified in the file.......actual flashing fails...

Thats all I can do for now!

Help!

Mark

Posted: **Wed Jan 17, 2007 10:38 am**

Someone else with a Forester is having exactly the same problem over on the Enginuity forum....

http://www.enginuity.org/viewtopic.php?p=10010#10010

Posted: **Wed Jan 17, 2007 11:25 am**

I have the same problem...

http://forums.openecu.org/viewtopic.php?t=1192

Someone know, what is this?

Posted: **Wed Jan 17, 2007 11:52 pm**

I count four people all with the same problem, all with Foresters and A2###### ROM ID's

Posted: **Thu Jan 18, 2007 2:23 am**

Started a new thread here:

http://forums.openecu.org/viewtopic.php?t=1901