Problem with 2007 STi (read me) Warnings!

[merchgod]

Here's some Enginuity definitions to test for this rom. It is pretty close to being final for the next def release, but I still have to check a few things.

To add to Enginuity, open up the Ecu Definition Manager in the Edit menu and add it to the list. If you don't usually use Enginuity, be sure you up your user level to 4 or 5 to view all the tables.

This is a very interesting rom. More tables than I've seen before (597 2d tables and 180 3d tables). There are 6 boost maps, 6 fuel maps, 5 base timing maps, 4 ign correction maps, among others.

[evoX]

have Tactrix Open Port 1.3 and EcuFlash 1.29a, I cannot read the ROM and I have tried reading using all the subaru models but the same error.

[02:13:10.720] Version 1.29.906
[02:13:10.740] 8 memory models read.
[02:13:12.402] 141 ROM metadata models read.
[02:13:12.402] checksum module "subarudbw" loaded.
[02:13:12.402] flashing tool "wrx02" loaded.
[02:13:12.402] flashing tool "wrx04" loaded.
[02:13:12.402] flashing tool "sti04" loaded.
[02:13:12.402] flashing tool "sti05" loaded.
[02:13:12.402] flashing tool "mitsukernel" loaded.
[02:13:12.402] flashing tool "mitsukernelocp" loaded.
[02:13:12.402] flashing tool "mitsubootloader" loaded.
[02:13:18.811] ssm2_init
[02:13:19.031] ssm2_init
[02:13:19.262] ssm2_init
[02:13:19.482] ssm2_init
[02:13:19.702] ssm2_init
[02:13:19.933] ssm2_init
[02:13:20.153] ssm2_init
[02:13:20.373] ssm2_init
[02:13:20.604] ssm2_init
[02:13:20.824] ssm2_init
[02:13:21.225] kernel get version
[02:13:21.765] validating denso kernel ram area addr: FFFF0000 len: 0008


EcuExplorer can enter the diagnostic mode and read the engine parameters, but it also cannot read the rom.

How can I read the rom on the EU 2007 STi 2.5 Turbo Limited Edition ?

[dsm02c]

have Tactrix Open Port 1.3 and EcuFlash 1.29a, I cannot read the ROM and I have tried reading using all the subaru models but the same error.


EcuExplorer can enter the diagnostic mode and read the engine parameters, but it also cannot read the rom.

How can I read the rom on the EU 2007 STi 2.5 Turbo Limited Edition ?

And there you have the million dollar question... at least for me that is....

[Jon [in CT]]

If EcuExplorer works but EcuFlash cannot get a response to the ssm2_init command it issues, then you have a FTDI device driver mismatch problem.

The ssm2_init should provoke a response even if the test connectors aren't connected together and the response should appear on the next line of the log and will look like this:
ECU ID is XX XX XX XX XX
where each X is an hexadecimal digit, 0-F.

When EcuFlash gets no response to the ssm2_init, it retries the command 9 more times. When you see this sequence in a log, you know that EcuFlash can't communicate with the ECU and that it's not a problem with the test connectors.

The FTDI device driver mismatch problem is most likely when you had installed any previous version of EcuFlash prior to installing 1.29.

[evoX]

I have installed version 1.29 the first time.
On Subaru Forester the ECU ID did appear and I was able to read the ROM memory using the WRX settings, but on the 2007 STi Limited, I always get the above results.

The green test connectors where connected, I also tried to connect the 4 pin connector.

I also have tried version 1.28 of EcuFlash and the same problem.

[evoX]

If EcuExplorer works but EcuFlash cannot get a response to the ssm2_init command it issues, then you have a FTDI device driver mismatch problem.

The FTDI device driver mismatch problem is most likely when you had installed any previous version of EcuFlash prior to installing 1.29.

If I was able to read the ROM memory from a Subaru Forester, then I think it is not a driver problem...

[mociornitza]

I can confirm the same problem with an STI 2007. Same sequence of events that evoX experienced.
Can't read the ECU with EcuFlash1.29a but some engine parameters are displayed by EcuExplorer and no ECU id appear.
All drivers are installed and working (tested on other cars).

BTW how can put a 3.0 Tribeca in diagnostic mode? can't find green connectors.
Thanks

[toofast555]

I can confirm the same problem with an STI 2007. Same sequence of events that evoX experienced.
Can't read the ECU with EcuFlash1.29a but some engine parameters are displayed by EcuExplorer and no ECU id appear.
All drivers are installed and working (tested on other cars).

Same problem

[evoX]

I was able to read & write to Subaru STi 2006 without problem using the same computer which does not work with the STi 2007, and connected just the green connector.
So the driver conflict posibility is eliminated, the only problem I think of, is the EcuFlash software needs an update or there is another trick with the connectors.

[Jon [in CT]]

For the case when you're trying to read a ROM and find 10 ssm2init commands in a row in the log without and ECUID reported, I've notice one case where the user had a background application running (Palm hotsync) which was monopolizing his USB port and prevented EcuFlash communication with the ECU.

As for the 2007 Impreza, I've read there's a pair of connectors tucked high up into the interior fuse box which must be connected, in addition to the green test connectors.

[evoX]

I also have connected that connector, it's a 4 pin connector, I have a jumper which came with Tactrix OpenPort interface, even with that connected + the green connectors the same thing happens...

[Jon [in CT]]

I also have connected that connector, it's a 4 pin connector, I have a jumper which came with Tactrix OpenPort interface, even with that connected + the green connectors the same thing happens...

That's not right. I'd remove the Tactrix jumper and if that connector came with a cap, I'd put the cap back on.

You're looking for two connectors which can connect to each other. They're probably taped together to other wiring, so you might have to remove the lower driver's side dash to locate them.

[evoX]

except the two green connectors there are another two connectors? which needs to be connected together?
I have seen two connectors tapped, and I have connected them but I think that when I have tried to connect the 4pin jumper from the fusebox was also connected.

[evoX]

I found a blue wire terminal and a red terminal tapped together under the dash, but they don't have a connector. I have connected the red terminal with the blue, and then tried all the possible combinations with the green wires connected and also with the fuse box connector jumper and the same thing happens, it does not work

[dsm02c]

I have stopped trying.