openecu.org

I posted in the Legacy subforum, but it's probably not the best place.
http://forums.openecu.org/viewtopic.php?t=1511

I know there are changes for 07s, particularly the legacy (now CAN/OBD-2, unlike the 07 Imprezas). However, I'm not convinced my problem is because I'm reading my 2007 Legacy Spec B - I think there's a good possibility I'm just doing something wrong.

With either EcuFlash 1.28 or 1.29a, I'm unable to read my ROM. And the error I get is the same even if I select a com port that isn't plugged into anything. So either there's something just fundamentally different about my ECU, or (more likely at this point) I'm just doing something wrong.

The only test-mode connector I can find in my car is in the passenger side footwell. Connecting it makes the radiator fans cycle, so hopefully that's all I need.

When I try to read my ROM, I get a popup that an error occured, and the last lines in the log are:
[00:03:21.359] ssm2_init
[00:03:21.539] kernel get version
[00:03:22.070] validating denso kernel ram area addr: FFFF0000 len: 0008

Any tips for this newb?

serendipity wrote:I posted in the Legacy subforum, but it's probably not the best place.
http://forums.openecu.org/viewtopic.php?t=1511

I know there are changes for 07s, particularly the legacy (now CAN/OBD-2, unlike the 07 Imprezas). However, I'm not convinced my problem is because I'm reading my 2007 Legacy Spec B - I think there's a good possibility I'm just doing something wrong.

With either EcuFlash 1.28 or 1.29a, I'm unable to read my ROM. And the error I get is the same even if I select a com port that isn't plugged into anything. So either there's something just fundamentally different about my ECU, or (more likely at this point) I'm just doing something wrong.

The only test-mode connector I can find in my car is in the passenger side footwell. Connecting it makes the radiator fans cycle, so hopefully that's all I need.

When I try to read my ROM, I get a popup that an error occured, and the last lines in the log are:
[00:03:21.359] ssm2_init
[00:03:21.539] kernel get version
[00:03:22.070] validating denso kernel ram area addr: FFFF0000 len: 0008

Any tips for this newb?

am suffering from the same problem as well :=P

So is there anything else I can try here?

Is there a debug build of EcuFlash available with more debugging info so I can see where it's failing?

I've tried two laptops, version 1.28 and 1.29a on each, and I'm getting nothing useful.

I'm going to try the cable on some other cars to make sure it's not a cable issue (the cable is brand new though).

If there is indeed a difference in how we need to communicate with the 07 ECUs, how could I contribute to the effort to figure it out?

What are you selecting to download the image '2005-2006 DBW'?

Mine is a MY07 Forester, but will only download as a '2004 DBW'.

Hope that helps,

Mark

marky9074 wrote:What are you selecting to download the image '2005-2006 DBW'?

Mine is a MY07 Forester, but will only download as a '2004 DBW'.

Hope that helps,

Mark

cant work
niether 1.28 nor 1.29 will work
think it is because of the network differences - or pin differences :=P .. very frustrating

have tried ver 1.30 now
still cant get the rom downloaded
these are the error msgs
i have removed all the drivers before reinstalling ecuflash 1.3
am driving JDM MY07 2.0LGT 6MT with SI Drive

[00:03:06.057] Version 1.30.1095
[00:03:06.057] 8 memory models read.
[00:03:07.479] 145 ROM metadata models read.
[00:03:07.479] checksum module "subarudbw" loaded.
[00:03:07.479] flashing tool "wrx02" loaded.
[00:03:07.479] flashing tool "wrx04" loaded.
[00:03:07.479] flashing tool "sti04" loaded.
[00:03:07.479] flashing tool "sti05" loaded.
[00:03:07.479] flashing tool "mitsukernel" loaded.
[00:03:07.479] flashing tool "mitsukernelocp" loaded.
[00:03:07.479] flashing tool "mitsubootloader" loaded.
[00:03:23.041] SSM2 init
[00:03:23.322] [FF] A2 10 0F 4B 04 78 50 07 F3 FA C9 8C 0B 83 FE AC
00 00 00 66 CE 54 FD B0 60 00 0F 20 00 00 00 00
00 DC 00 00 5D 1F 30 80 F0 E6 00 FC 40 FB 00 F5
C1 86 00 00 00 01 ED 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:03:23.332] SSM2 ECU ID is 4B 04 78 50 07
[00:03:23.332] SSM2 cmd_0x81

[00:04:11.561] SSM2 init
[00:04:11.832] [FF] A2 10 0F 4B 04 78 50 07 F3 FA C9 8C 0B 83 FE AC
00 00 00 66 CE 54 FD B0 60 00 0F 20 00 00 00 00
00 DC 00 00 5D 1F 30 80 F0 E6 00 FC 40 FB 00 F5
C1 86 00 00 00 01 ED 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:04:11.832] SSM2 ECU ID is 4B 04 78 50 07
[00:04:11.832] SSM2 cmd_0x81

[00:04:33.963] SSM2 init
[00:04:34.224] [FF] A2 10 0F 4B 04 78 50 07 F3 FA C9 8C 0B 83 FE AC
00 00 00 66 CE 54 FD B0 60 00 0F 20 00 00 00 00
00 DC 00 00 5D 1F 30 80 F0 E6 00 FC 40 FB 00 F5
C1 86 00 00 00 01 ED 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:04:34.254] SSM2 ECU ID is 4B 04 78 50 07
[00:04:34.254] SSM2 cmd_0x81

bump
any one
any ideas
any suggestions?

zigzagzok wrote:bump
any one
any ideas
any suggestions?

so means that for subarus on CANBUS we are outta luck huh

zigzagzok wrote:so means that for subarus on CANBUS we are outta luck huh

Actually the MY04 already has 2 CanBus, but not exposed on the OBD2 connector. The vacation pix do show it. The high speed CAN connects ECU and TCU, the low speed CAN connects ECU and BIU.

Maybe your problem is due to newer CPU used in the MY07 ECU....just a guess.