Page 1 of 2

Pulling the ROM on JDM LGT 2.0 SpecB 6MT

PostPosted: Wed Oct 11, 2006 2:03 am
by zigzagzok
I understd that we would have to use ECUFLash to download the ROM;
To download a copy of the ROM i wld connect the greeen connector
Image
but when i short the connectors, my radiator fans start cycling and the relays click click click;
on hearing this i disconnected the plugs

am driving a JDM LGT 2.0 SpecB 6MT -with SI Drive
the ecu is below

Image

would appreciate any advice

PostPosted: Wed Oct 11, 2006 2:31 am
by west_minist
Do you have a green connector under the steering column?

When you connect it, you will hear that.

Start the ecufash and prepare it for down load.

push in the clutch and turn the key on. As soon as you do that, press ok.

PostPosted: Wed Oct 11, 2006 5:15 pm
by LGT+WRX
^ +1.

For the USDM 2.5GT (turbocharged, BL/BP) models, the fan-cycling/relay-clicking after the green connectors have been shorted is normal, and will cease eventually (when the ECU is connected).

I am unable to confirm, however, if the same holds true for JDM vehicles.

PostPosted: Wed Oct 11, 2006 10:38 pm
by radsdau
west_minist wrote:push in the clutch and turn the key on. As soon as you do that, press ok.

What does pushing in the clutch do? (other than the obvious mechanical stuff... 8) )

PostPosted: Thu Oct 12, 2006 12:00 am
by Freon
The green connector is the "test" or "diagnostics mode" connector. That's why your fans start to cycle. The system is doing some sort of self test.

The trick is clicking "ok" on Ecuflash moments after you turn the key. This is just how it works.

I don't think you need to press the clutch. ??? Not that it would hurt.

PostPosted: Thu Oct 12, 2006 6:45 pm
by zigzagzok
radsdau wrote:
west_minist wrote:push in the clutch and turn the key on. As soon as you do that, press ok.

What does pushing in the clutch do? (other than the obvious mechanical stuff... 8) )


hi all thks for the info ! :) will try out this weekend
need to push in the clutch to start the car - think there is another switch..

PostPosted: Sun Oct 15, 2006 12:05 am
by zigzagzok
Freon wrote:The green connector is the "test" or "diagnostics mode" connector. That's why your fans start to cycle. The system is doing some sort of self test.

The trick is clicking "ok" on Ecuflash moments after you turn the key. This is just how it works.

I don't think you need to press the clutch. ??? Not that it would hurt.


hi all need ur help again :(

the software ECUFLASH - with the latest version downloaded 2/10/06 it started fine - detected the Openport 1.3 Mitsubishi cable - shown on the right corner of the window

then i followed the procedure below to try to pull the rom
http://forums.openecu.org/viewtopic.php?t=904

twice with the clutch in
twice with the clutch out
keep getting this error msg - any idea?
much thanks!!

[00:08:46.757] Version 1.29.906
[00:08:46.767] 8 memory models read.
[00:08:49.661] 140 ROM metadata models read.
[00:08:49.661] checksum module "subarudbw" loaded.
[00:08:49.661] flashing tool "wrx02" loaded.
[00:08:49.661] flashing tool "wrx04" loaded.
[00:08:49.661] flashing tool "sti04" loaded.
[00:08:49.661] flashing tool "sti05" loaded.
[00:08:49.661] flashing tool "mitsukernel" loaded.
[00:08:49.661] flashing tool "mitsukernelocp" loaded.
[00:08:49.661] flashing tool "mitsubootloader" loaded.
[00:10:52.658] ssm2_init
[00:10:52.898] ssm2_init
[00:10:52.908] ssm2_init
[00:10:52.928] ssm2_init
[00:10:52.948] ssm2_init
[00:10:52.958] ssm2_init
[00:10:52.978] ssm2_init
[00:10:52.998] ssm2_init
[00:10:53.008] ssm2_init
[00:10:53.029] ssm2_init
[00:10:53.219] kernel get version
[00:10:53.539] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:12:23.328] ssm2_init
[00:12:23.559] ssm2_init
[00:12:23.569] ssm2_init
[00:12:23.589] ssm2_init
[00:12:23.609] ssm2_init
[00:12:23.629] ssm2_init
[00:12:23.639] ssm2_init
[00:12:23.659] ssm2_init
[00:12:23.679] ssm2_init
[00:12:23.699] ssm2_init
[00:12:23.879] kernel get version
[00:12:24.410] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:13:24.807] ssm2_init
[00:13:25.037] ssm2_init
[00:13:25.047] ssm2_init
[00:13:25.067] ssm2_init
[00:13:25.087] ssm2_init
[00:13:25.097] ssm2_init
[00:13:25.117] ssm2_init
[00:13:25.137] ssm2_init
[00:13:25.147] ssm2_init
[00:13:25.177] ssm2_init
[00:13:25.368] kernel get version
[00:13:25.688] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:15:29.035] ssm2_init
[00:15:29.266] ssm2_init
[00:15:29.266] ssm2_init
[00:15:29.286] ssm2_init
[00:15:29.306] ssm2_init
[00:15:29.316] ssm2_init
[00:15:29.336] ssm2_init
[00:15:29.346] ssm2_init
[00:15:29.366] ssm2_init
[00:15:29.386] ssm2_init
[00:15:29.566] kernel get version
[00:15:30.097] validating denso kernel ram area addr: FFFF0000 len: 0008

PostPosted: Tue Oct 17, 2006 9:05 am
by bmorrisj
either you are waiting too long or your ecu is a brick.... the car still runs normally right....


when i use ecu flash...

1. connect green plugs
2. ready ecuflash for flashing
a. select map
b. click the flash button
c. now im ready with an 'OK' prompt
3. turn the key to ignition then immediately click ok
4. flash done, turn off the key

PostPosted: Wed Oct 18, 2006 7:39 pm
by zigzagzok
bmorrisj wrote:either you are waiting too long or your ecu is a brick.... the car still runs normally right....


when i use ecu flash...

1. connect green plugs
2. ready ecuflash for flashing
a. select map
b. click the flash button
c. now im ready with an 'OK' prompt
3. turn the key to ignition then immediately click ok
4. flash done, turn off the key


thats wat i do; green plugs connected
left hand turn ignition key to "on"
right hand click "ok" button.... almost simultaneously
wonder becoz the ecu is japanese - if it will make any difference?....

PostPosted: Sun Nov 19, 2006 10:54 pm
by zigzagzok
hi all
i have done the following
still no luck to pull down the rom :(
did the installation as follows below
picture of the green connector
and the openport connector

Image
Image
Image
Image
Image
Image
Image
Image
Image
Image
Image
Image

ECUFLASH log

[00:12:05.623] Version 1.29.906
[00:12:05.623] 8 memory models read.
[00:12:06.835] 140 ROM metadata models read.
[00:12:06.835] checksum module "subarudbw" loaded.
[00:12:06.835] flashing tool "wrx02" loaded.
[00:12:06.835] flashing tool "wrx04" loaded.
[00:12:06.835] flashing tool "sti04" loaded.
[00:12:06.835] flashing tool "sti05" loaded.
[00:12:06.835] flashing tool "mitsukernel" loaded.
[00:12:06.835] flashing tool "mitsukernelocp" loaded.
[00:12:06.835] flashing tool "mitsubootloader" loaded.
[00:12:22.307] ssm2_init
[00:12:22.547] ssm2_init
[00:12:22.547] ssm2_init
[00:12:22.567] ssm2_init
[00:12:22.597] ssm2_init
[00:12:22.828] ssm2_init
[00:12:22.838] ssm2_init
[00:12:22.858] ssm2_init
[00:12:22.878] ssm2_init
[00:12:22.888] ssm2_init
[00:12:23.078] kernel get version
[00:12:23.599] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:12:50.427] ssm2_init
[00:12:50.668] ssm2_init
[00:12:50.668] ssm2_init
[00:12:50.688] ssm2_init
[00:12:50.708] ssm2_init
[00:12:50.718] ssm2_init
[00:12:50.738] ssm2_init
[00:12:50.748] ssm2_init
[00:12:50.768] ssm2_init
[00:12:50.788] ssm2_init
[00:12:50.968] kernel get version
[00:12:51.499] validating denso kernel ram area addr: FFFF6000 len: 0008
[00:14:44.501] ssm2_init
[00:14:44.732] ssm2_init
[00:14:44.732] ssm2_init
[00:14:44.752] ssm2_init
[00:14:44.762] ssm2_init
[00:14:44.782] ssm2_init
[00:14:44.802] ssm2_init
[00:14:44.812] ssm2_init
[00:14:44.832] ssm2_init
[00:14:44.842] ssm2_init
[00:14:45.022] kernel get version
[00:14:45.553] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:15:49.134] ssm2_init
[00:15:49.365] ssm2_init
[00:15:49.375] ssm2_init
[00:15:49.395] ssm2_init
[00:15:49.415] ssm2_init
[00:15:49.435] ssm2_init
[00:15:49.455] ssm2_init
[00:15:49.465] ssm2_init
[00:15:49.485] ssm2_init
[00:15:49.495] ssm2_init
[00:15:49.685] kernel get version
[00:15:50.216] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:16:16.033] ssm2_init
[00:16:16.263] ssm2_init
[00:16:16.263] ssm2_init
[00:16:16.283] ssm2_init
[00:16:16.293] ssm2_init
[00:16:16.313] ssm2_init
[00:16:16.313] ssm2_init
[00:16:16.323] ssm2_init
[00:16:16.343] ssm2_init
[00:16:16.363] ssm2_init
[00:16:16.534] kernel get version
[00:16:17.074] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:16:27.469] ssm2_init
[00:16:27.700] ssm2_init
[00:16:27.720] ssm2_init
[00:16:27.730] ssm2_init
[00:16:27.750] ssm2_init
[00:16:27.770] ssm2_init
[00:16:27.790] ssm2_init
[00:16:27.800] ssm2_init
[00:16:27.820] ssm2_init
[00:16:27.840] ssm2_init
[00:16:28.030] kernel get version
[00:16:28.561] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:17:40.845] ssm2_init
[00:17:41.075] ssm2_init
[00:17:41.075] ssm2_init
[00:17:41.095] ssm2_init
[00:17:41.125] ssm2_init
[00:17:41.356] ssm2_init
[00:17:41.376] ssm2_init
[00:17:41.406] ssm2_init
[00:17:41.426] ssm2_init
[00:17:41.436] ssm2_init
[00:17:41.626] kernel get version
[00:17:41.946] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:20:00.576] ssm2_init
[00:20:00.806] ssm2_init
[00:20:00.806] ssm2_init
[00:20:00.826] ssm2_init
[00:20:00.836] ssm2_init
[00:20:00.856] ssm2_init
[00:20:00.866] ssm2_init
[00:20:00.886] ssm2_init
[00:20:00.896] ssm2_init
[00:20:00.916] ssm2_init
[00:20:01.097] kernel get version
[00:20:01.647] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:20:34.745] ssm2_init
[00:20:34.975] ssm2_init
[00:20:34.985] ssm2_init
[00:20:35.005] ssm2_init
[00:20:35.015] ssm2_init
[00:20:35.035] ssm2_init
[00:20:35.055] ssm2_init
[00:20:35.075] ssm2_init
[00:20:35.085] ssm2_init
[00:20:35.105] ssm2_init
[00:20:35.296] kernel get version
[00:20:35.817] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:21:06.991] ssm2_init
[00:21:07.212] ssm2_init
[00:21:07.232] ssm2_init
[00:21:07.242] ssm2_init
[00:21:07.262] ssm2_init
[00:21:07.282] ssm2_init
[00:21:07.292] ssm2_init
[00:21:07.312] ssm2_init
[00:21:07.322] ssm2_init
[00:21:07.332] ssm2_init
[00:21:07.522] kernel get version
[00:21:08.043] validating denso kernel ram area addr: FFFF0000 len: 0008

PostPosted: Sun Nov 26, 2006 2:22 am
by zigzagzok
took apart the ecu and snapped some pics ... if it is of interest to anyone...

Image
Image
Image
Image
Image
Image
Image
Image
Image
Image
Image
Image

PostPosted: Sun Nov 26, 2006 6:24 am
by west_minist
Most of all, a clear picture of the procressor would really help. That is the main reason for opening the ECU :)

PostPosted: Sun Nov 26, 2006 4:31 pm
by zigzagzok
west_minist wrote:Most of all, a clear picture of the procressor would really help. That is the main reason for opening the ECU :)


that was the best pic i cld take :(
subaru engineers scrapped off the serial nos and apply some reflective paint on it...
zoomed in on the pic and this is the best guess of the longest row of nos on the main chip :(

6AF7058F8U
or
BAF7U5BFBU

PostPosted: Sun Nov 26, 2006 5:27 pm
by west_minist
Yeah. I can understand your pain. A 2005 Forrester owner needs a reflash and we are unable to pull the rom.

PostPosted: Sun Jan 28, 2007 1:40 pm
by Jon [in CT]
zigzagzok, can you recall which option you selected when you reached the screen shown below?

Image