ECU Flash

Developer topics relating to software that reflashes or modifes ECU code and data

Moderator: Freon

ECU Flash

Postby zigzagzok » Wed Oct 11, 2006 1:56 am

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
zigzagzok
 
Posts: 71
Joined: Fri Jul 14, 2006 5:03 pm

Postby m3n0ch3 » Wed Oct 11, 2006 5:55 am

that's what it is supposed to do ;)

the green connector is for test mode, cycling de fans, lights, etc etc.

ecuflash needs the ecu to be in test mode to read and write ;)
m3n0ch3
 
Posts: 49
Joined: Fri Aug 11, 2006 11:46 am

Postby zigzagzok » Thu Oct 12, 2006 6:42 pm

m3n0ch3 wrote:that's what it is supposed to do ;)

the green connector is for test mode, cycling de fans, lights, etc etc.

ecuflash needs the ecu to be in test mode to read and write ;)


thks! :) will try out this weekend
zigzagzok
 
Posts: 71
Joined: Fri Jul 14, 2006 5:03 pm

Postby zigzagzok » Sun Oct 22, 2006 8:18 am

hi
need help again :=(
am unable to pull the rom from the car yet ...

having connected the green connectors i still the error msg in the screenshot below

Image

taking cue from the thread below, i decided to open up the compartment at the driver's side (ie my car is RHD)

http://forums.openecu.org/viewtopic.php ... c&start=15

lo-and-behold i found a white connector not hooked up

Image

after joining up the green connector at the ecu and white connector at the driver's foot
am still getting the same error msg :( frustrating...
whether i use the DBW 04 or the DBW 06 options in ECUflash

cld someone help? thks!

[00:06:15.740] Version 1.29.906
[00:06:15.740] 8 memory models read.
[00:06:18.644] 140 ROM metadata models read.
[00:06:18.644] checksum module "subarudbw" loaded.
[00:06:18.654] flashing tool "wrx02" loaded.
[00:06:18.654] flashing tool "wrx04" loaded.
[00:06:18.654] flashing tool "sti04" loaded.
[00:06:18.654] flashing tool "sti05" loaded.
[00:06:18.654] flashing tool "mitsukernel" loaded.
[00:06:18.654] flashing tool "mitsukernelocp" loaded.
[00:06:18.654] flashing tool "mitsubootloader" loaded.
[00:07:02.377] ssm2_init
[00:07:02.607] ssm2_init
[00:07:02.617] ssm2_init
[00:07:02.627] ssm2_init
[00:07:02.647] ssm2_init
[00:07:02.657] ssm2_init
[00:07:02.667] ssm2_init
[00:07:02.677] ssm2_init
[00:07:02.687] ssm2_init
[00:07:02.717] ssm2_init
[00:07:02.898] kernel get version
[00:07:03.218] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:07:37.007] ssm2_init
[00:07:37.237] ssm2_init
[00:07:37.247] ssm2_init
[00:07:37.257] ssm2_init
[00:07:37.277] ssm2_init
[00:07:37.287] ssm2_init
[00:07:37.297] ssm2_init
[00:07:37.307] ssm2_init
[00:07:37.317] ssm2_init
[00:07:37.347] ssm2_init
[00:07:37.527] kernel get version
[00:07:37.848] validating denso kernel ram area addr: FFFF6000 len: 0008
[00:08:12.197] ssm2_init
[00:08:12.428] ssm2_init
[00:08:12.438] ssm2_init
[00:08:12.458] ssm2_init
[00:08:12.478] ssm2_init
[00:08:12.488] ssm2_init
[00:08:12.498] ssm2_init
[00:08:12.508] ssm2_init
[00:08:12.528] ssm2_init
[00:08:12.538] ssm2_init
[00:08:12.718] kernel get version
[00:08:13.249] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:08:42.851] ssm2_init
[00:08:43.072] ssm2_init
[00:08:43.082] ssm2_init
[00:08:43.092] ssm2_init
[00:08:43.102] ssm2_init
[00:08:43.132] ssm2_init
[00:08:43.142] ssm2_init
[00:08:43.152] ssm2_init
[00:08:43.182] ssm2_init
[00:08:43.192] ssm2_init
[00:08:43.372] kernel get version
[00:08:43.893] validating denso kernel ram area addr: FFFF6000 len: 0008
zigzagzok
 
Posts: 71
Joined: Fri Jul 14, 2006 5:03 pm

Postby evo400 » Mon Oct 23, 2006 5:04 am

Is your ECu stock or it was reflashed for example with ECU(fuck)TEK ?
evo400
 
Posts: 62
Joined: Thu Jun 29, 2006 1:45 pm

Postby zigzagzok » Thu Oct 26, 2006 2:39 am

evo400 wrote:Is your ECu stock or it was reflashed for example with ECU(fuck)TEK ?


stock - bone stock :)
zigzagzok
 
Posts: 71
Joined: Fri Jul 14, 2006 5:03 pm

Postby Jon [in CT] » Thu Oct 26, 2006 6:28 am

zigzagzok wrote:stock - bone stock :)
Are you able to log data from it using one of the free datalogging programs (Ecuedit or Ecuexplorer)?
Jon [in CT]
 
Posts: 352
Joined: Sat Jan 01, 2005 10:23 am

Postby zigzagzok » Fri Oct 27, 2006 6:14 pm

Jon [in CT] wrote:
zigzagzok wrote:stock - bone stock :)
Are you able to log data from it using one of the free datalogging programs (Ecuedit or Ecuexplorer)?


yes i am able to log data from ECUExplorer....
but strangely i am not able to see the name of the ecu.. ie if the ecu is connected supposed to display the name and a little drop box appears to show "real time data" and "trouble codes"...
am only able to see the "real time data" and the "trouble codes"
zigzagzok
 
Posts: 71
Joined: Fri Jul 14, 2006 5:03 pm

Postby zigzagzok » Sat Oct 28, 2006 11:41 pm

still no luck
have tried combinations of white plug out green plug in etc.. still the same error msg below

however as i cld use ecuexplorer to log data; i turned on the log and captured some interaction info.. wonder if it cld help?...



===========================================
[00:04:41.214] Version 1.29.906
[00:04:41.214] 8 memory models read.
[00:04:44.288] 140 ROM metadata models read.
[00:04:44.288] checksum module "subarudbw" loaded.
[00:04:44.288] flashing tool "wrx02" loaded.
[00:04:44.288] flashing tool "wrx04" loaded.
[00:04:44.288] flashing tool "sti04" loaded.
[00:04:44.288] flashing tool "sti05" loaded.
[00:04:44.288] flashing tool "mitsukernel" loaded.
[00:04:44.288] flashing tool "mitsukernelocp" loaded.
[00:04:44.288] flashing tool "mitsubootloader" loaded.
[00:05:15.053] ssm2_init
[00:05:15.293] ssm2_init
[00:05:15.303] ssm2_init
[00:05:15.323] ssm2_init
[00:05:15.343] ssm2_init
[00:05:15.353] ssm2_init
[00:05:15.373] ssm2_init
[00:05:15.383] ssm2_init
[00:05:15.403] ssm2_init
[00:05:15.423] ssm2_init
[00:05:15.603] kernel get version
[00:05:16.134] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:05:37.214] ssm2_init
[00:05:37.455] ssm2_init
[00:05:37.465] ssm2_init
[00:05:37.475] ssm2_init
[00:05:37.495] ssm2_init
[00:05:37.505] ssm2_init
[00:05:37.525] ssm2_init
[00:05:37.545] ssm2_init
[00:05:37.555] ssm2_init
[00:05:37.575] ssm2_init
[00:05:37.755] kernel get version
[00:05:38.076] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:08:19.738] ssm2_init
[00:08:19.968] ssm2_init
[00:08:19.988] ssm2_init
[00:08:19.998] ssm2_init
[00:08:20.018] ssm2_init
[00:08:20.029] ssm2_init
[00:08:20.049] ssm2_init
[00:08:20.069] ssm2_init
[00:08:20.079] ssm2_init
[00:08:20.099] ssm2_init
[00:08:20.279] kernel get version
[00:08:20.810] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:08:55.650] ssm2_init
[00:08:55.880] ssm2_init
[00:08:55.900] ssm2_init
[00:08:55.910] ssm2_init
[00:08:55.930] ssm2_init
[00:08:55.950] ssm2_init
[00:08:55.960] ssm2_init
[00:08:55.980] ssm2_init
[00:08:55.990] ssm2_init
[00:08:56.010] ssm2_init
[00:08:56.201] kernel get version
[00:08:56.721] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:10:16.636] ssm2_init
[00:10:16.867] ssm2_init
[00:10:16.877] ssm2_init
[00:10:16.887] ssm2_init
[00:10:16.897] ssm2_init
[00:10:16.907] ssm2_init
[00:10:16.927] ssm2_init
[00:10:16.927] ssm2_init
[00:10:16.937] ssm2_init
[00:10:16.957] ssm2_init
[00:10:17.137] kernel get version
[00:10:17.668] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:14:53.104] ssm2_init
[00:14:53.334] ssm2_init
[00:14:53.354] ssm2_init
[00:14:53.364] ssm2_init
[00:14:53.384] ssm2_init
[00:14:53.404] ssm2_init
[00:14:53.424] ssm2_init
[00:14:53.444] ssm2_init
[00:14:53.464] ssm2_init
[00:14:53.474] ssm2_init
[00:14:53.665] kernel get version
[00:14:54.195] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:15:58.908] ssm2_init
[00:15:59.139] ssm2_init
[00:15:59.139] ssm2_init
[00:15:59.159] ssm2_init
[00:15:59.189] ssm2_init
[00:15:59.439] ssm2_init
[00:15:59.449] ssm2_init
[00:15:59.469] ssm2_init
[00:15:59.489] ssm2_init
[00:15:59.499] ssm2_init
[00:15:59.689] kernel get version
[00:16:00.210] validating denso kernel ram area addr: FFFF0000 len: 0008
[00:16:32.386] ssm2_init
[00:16:32.617] ssm2_init
[00:16:32.617] ssm2_init
[00:16:32.627] ssm2_init
[00:16:32.647] ssm2_init
[00:16:32.647] ssm2_init
[00:16:32.667] ssm2_init
[00:16:32.677] ssm2_init
[00:16:32.697] ssm2_init
[00:16:32.707] ssm2_init
[00:16:32.887] kernel get version
[00:16:33.408] validating denso kernel ram area addr: FFFF0000 len: 0008
Attachments
ecuexplorer debug log 291006 1422.zip
(56.76 KiB) Downloaded 218 times
zigzagzok
 
Posts: 71
Joined: Fri Jul 14, 2006 5:03 pm

Postby tekgnosis » Sun Oct 29, 2006 7:42 am

I had this problem for a few minutes too...

as it turns out, you can't put your car into test mode (ie: turn the ignition ON) until you've asked ecuFlash to pull the rom.

once hit 'pull ecu rom data', it'll ask you to put the car into test mode. when it says "do it"...do it. otherwise, the car gets into full test mode (cycling the fans, etc).

you'll notice that it takes a couple of seconds for teh fans to start cycling...that's the time you need to get ecuflash to initialize with the comptuer.

hope this helps!
tekgnosis
 
Posts: 15
Joined: Thu Aug 17, 2006 7:52 am

Postby zigzagzok » Mon Oct 30, 2006 10:32 pm

tekgnosis wrote:I had this problem for a few minutes too...

as it turns out, you can't put your car into test mode (ie: turn the ignition ON) until you've asked ecuFlash to pull the rom.

once hit 'pull ecu rom data', it'll ask you to put the car into test mode. when it says "do it"...do it. otherwise, the car gets into full test mode (cycling the fans, etc).

you'll notice that it takes a couple of seconds for teh fans to start cycling...that's the time you need to get ecuflash to initialize with the comptuer.

hope this helps!


yes done that... :=(
laptop - plug in usb cable - run ecuflash - verify that the cable is detected on the right bottom corner - click on read from ecu - box pops up to prompt which model to choose - click on 05-2006 DBW LGT - then click read - box pops up and say put key in ignition and turn to on - right hand turns key to "on" - left hand click on "ok" button on laptop almost simultaneously...
still cannot work.. sigh :evil:
zigzagzok
 
Posts: 71
Joined: Fri Jul 14, 2006 5:03 pm

Postby joegoi » Tue Oct 31, 2006 9:01 am

i think you have got all the step right.
But what model is your car.
for mine sti2004 edm i need to click the 02-03 wrx.
change yours maybe that will work.

the white connector your are refering to might be the steering wheel airbag. i took my off once and the airbag light up.

the white connector the rest is talking is the init one which have the 4 wires to it. i did not see any from your picture though.

try to click the connection.
at the 1st denso ON the key switch full.
Hope that could help.

FRsti taught me that.
joegoi
 
Posts: 12
Joined: Tue Aug 01, 2006 1:33 am
Location: singapore

Postby Jeramie » Thu Nov 02, 2006 4:55 am

"the white connector your are refering to might be the steering wheel airbag. i took my off once and the airbag light up"

this is not true. Apparently there are a few people with 07 model cars that are finding a two "mysterious" white connectors that need to be connected before flashing.

Unfourtonetly for me I can't seem to locate these connectors on my 07 wrx (if infact they do exsist).

From the flash logs looks like I have the same problem with my 07 WRX. :cry:

zigzagzok is your car DBW? (32bit ecu?)
Jeramie
 
Posts: 155
Joined: Thu Jun 23, 2005 12:45 pm
Location: Quakertown, PA

Postby zigzagzok » Tue Nov 07, 2006 2:56 am

Jeramie wrote:"the white connector your are refering to might be the steering wheel airbag. i took my off once and the airbag light up"

this is not true. Apparently there are a few people with 07 model cars that are finding a two "mysterious" white connectors that need to be connected before flashing.

Unfourtonetly for me I can't seem to locate these connectors on my 07 wrx (if infact they do exsist).

From the flash logs looks like I have the same problem with my 07 WRX. :cry:

zigzagzok is your car DBW? (32bit ecu?)



yes my car is DBW :(
have taken the panels off the bottom of the dash and took some pics if it will help


the white connector
Image

behind the fuse box
Image

Steering joint
Image

OBDII Connector

Image

Image

Fuse box
Image
zigzagzok
 
Posts: 71
Joined: Fri Jul 14, 2006 5:03 pm

Postby Jeramie » Tue Nov 07, 2006 6:28 am

Image

Are those green connectors in this pic the diagnostic connectors?
Jeramie
 
Posts: 155
Joined: Thu Jun 23, 2005 12:45 pm
Location: Quakertown, PA

Next

Return to Reflashing Software

Who is online

Users browsing this forum: No registered users and 1 guest