The Top DSM Community on the Web

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. Log in to remove most ads.

Please Support Rix Racing
Please Support STM Tuned

Can't Read/Write in EcuFlash *Evo 8 ECU swap*

This site may earn a commission from merchant
affiliate links, including eBay, Amazon, and others.

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

PFC_CiarlilloM

10+ Year Contributor
234
0
May 22, 2011
Euclid, Ohio
Okay So I am doing the Evo 8 ECU swap in my 2G 96 Eclipse. Pin swaps went fairly easy after I got the hang of removing them. I plugged in my Tactrix 2.0 cable, and reflash adapter.

I started up EcuFlash, and went to read the ROM -failed. Then I attempted to flash over a ROM, and received this;

[20:47:11.788] EcuFlash Version 1.42.2595 [20:47:11.788] OS Version Windows Vista
[20:47:11.788] Qt Version 4.5.0
[20:47:11.818] 56 memory models read.
[20:47:11.828] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[20:47:13.790] 344 ROM metadata models scanned.
[20:47:13.790] checksum module "subarudbw" loaded.
[20:47:13.790] checksum module "mitsucan" loaded.
[20:47:13.790] flashing tool "wrx02" loaded.
[20:47:13.790] flashing tool "wrx04" loaded.
[20:47:13.790] flashing tool "sti04" loaded.
[20:47:13.790] flashing tool "sti05" loaded.
[20:47:13.790] flashing tool "mitsukernel" loaded.
[20:47:13.790] flashing tool "mitsukernelocp" loaded.
[20:47:13.790] flashing tool "mitsubootloader" loaded.
[20:47:13.790] flashing tool "shbootmode" loaded.
[20:47:13.810] flashing tool "shaudmode" loaded.
[20:47:13.810] flashing tool "subarucan" loaded.
[20:47:13.810] flashing tool "mitsucan" loaded.
[20:47:28.138] J2534 API Version: 04.04
[20:47:28.138] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[20:47:28.138] Device Firmware Version: 1.11.3298
[20:50:36.648] sending init sequence 1 (0001)
[20:50:39.891] sending init sequence 1 (0003)
[20:50:43.116] sending init sequence 1 (FFFF)
[20:50:45.829] no response to any known code
[20:50:45.829] interface close
[20:51:45.961] J2534 API Version: 04.04
[20:51:45.961] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[20:51:45.961] Device Firmware Version: 1.11.3298
[20:51:57.479] sending init sequence 1 (0001)
[20:52:00.699] sending init sequence 1 (0003)
[20:52:03.919] sending init sequence 1 (FFFF)
[20:52:06.632] no response to any known code
[20:52:06.632] interface close
[20:52:15.769] 96530006 (157 tables) inheriting evo7base (73 tables)
[20:52:15.789] 262144 byte image read.
[20:52:20.629] J2534 API Version: 04.04
[20:52:20.629] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[20:52:20.629] Device Firmware Version: 1.11.3298
[20:53:04.821] J2534 error [ERR_TIMEOUT].
[20:53:05.321] sending init sequence 1 (0001)
[20:53:05.521] J2534 error [ERR_TIMEOUT].
[20:53:06.041] J2534 error [ERR_TIMEOUT].
[20:53:06.041] interface close

I am assuming it couldn't read because a combination of either/both, A. Computer wasn't set to "High Performance" or B. My flash pin isn't correctly installed.

Flash pin might not be making contact because I had to remove the pin that it came with and swapped it with a smaller pin from one of my OEM wires. I should have checked the front of the plastic harness housing to ensure that it was fully seated. I heard the "click" and couldn't pull it out, but it might not have went in far enough.

Anyways, the not reading isn't my issue. My issue now is that EcuFlash won't let me do anything. It's responsive, but won't let me "Read" <Didnt try "Write"> and if I exit, I get;

"EcuFlash is in the processes of reflashing your ECU. Exiting now would cause your ECU to be rendered permanently unresponsive."


So I am assuming that'd "brick" my ECU correct?

I am not sure why I attempted to "Write" if "Read" didn't work.... stupid me.

The Tactrix 2.0 cable is still lighting up solid blue with flashing white, green, and red colors to the right.



What do I do from here?
 
Last edited:
I'm taking a stab in the dark here but, considering the error occured after the J2534 DLL check, did you install the J2534 drivers externally?

http://www.tactrix.com/index.php?option=com_content&view=category&layout=blog&id=38&Itemid=61 said:
This is an Openport 2.0 driver and J2534 DLL-only install for users who only intend to use non-EcuFlash software with their Openport 2.0. This install also contains a few J2534 coding examples for developers in C. If you plan to use EcuFlash, do not download these files - go to the EcuFlash download page instead, as the driver and J2534 DLL installation are built into the EcuFlash install.
 
Flash pin might not be making contact because I had to remove the pin that it came with and swapped it with a smaller pin from one of my OEM wires. I should have checked the front of the plastic harness housing to ensure that it was fully seated. I heard the "click" and couldn't pull it out, but it might not have went in far enough.

What do you mean you had to change the pin to a smaller one??? The Mitsubishi flash connector you got with the 2.0 (assuming you got the mistu flash connector when you bought the 2.0) should have had the correct connector in it from the get go. Are you 100% sure you connected the reflash connector to the proper pin @ the ECU?

"EcuFlash is in the processes of reflashing your ECU. Exiting now would cause your ECU to be rendered permanently unresponsive."

As for whether or not your ECU is bricked... I don’t think so. From the ECUflash log you posted there was never a connection made to the ECU. I suppose it is possible that you picked up a bricked ECU from the start. As for ECUflash still running, Like I said it never made a connection to the ECU so you should be good to close ECUflash.

Slightly off topic… Any particular reason you went with the OP 2.0 over the 1.3???
 
The pin that was in the clear harness from the Tactrix 2.0 Mitsubishi Flash adapter was too big. I tried putting it into Pin 79, but it wouldn't fit in the yellow OEM plastic harness. So I took the pin from 58, and swapped it. Then I put it in 79 without an issue.

I believe I put it in pin 79, but I will recheck. I am completely new to all of this, and wasn't sure if EcuFlash was actually connected/"talking" to the ECU. So if it's not then it wouldn't brick the ECU if I closed it obviously, but I didn't want to take any chances.

I got the ECU off of EvoM forums, so maybe it's bricked -anyway to verify?

Just verified that the flash connector is in pin 79

and as for the 2.0 over 1.3, I couldn't find a good price on the 1.3, and I received a military discount from Tactrix basically making it equal to the cheapest price I could find a 1.3 cable.

I believe I found my problem. As I was pulling on the flash adapter, I pulled out the wire without the pin attached. I am assuming I wasn't getting a proper connection to pin 79m but now I can't get the pin out of the harness.
 
The pin that was in the clear harness from the Tactrix 2.0 Mitsubishi Flash adapter was too big. I tried putting it into Pin 79, but it wouldn't fit in the yellow OEM plastic harness. So I took the pin from 58, and swapped it. Then I put it in 79 without an issue.

I believe I put it in pin 79, but I will recheck. I am completely new to all of this, and wasn't sure if EcuFlash was actually connected/"talking" to the ECU. So if it's not then it wouldn't brick the ECU if I closed it obviously, but I didn't want to take any chances.

I got the ECU off of EvoM forums, so maybe it's bricked -anyway to verify?

OK. So you pulled the pin from the connector that came with the 2.0, swapped it and went straight to the ECU with it... So you have a wire that comes straight from the ECU to the OP 2.0 for flashing. Makes sense now. Yea check that pin, make sure it is in the right one... Should be on the very top connector third from the end right above the 2 white wires.

http://www.dsmtuners.com/forums/attachment.php?attachmentid=105305&d=1263753927

I receive that error log you posted all the time when I forget to connect the reflash connecter on my EVO8 ecu (I have it wired to a switch for convenience). But I have never received the ECUflash is still running message before.
 
I took off the pin on the wire that was going in #58, put it on the flash adapter, and then plugged the flash adapter wire into the yellow harness in the pin #79 spot. The other end plugs directly into the Tactrix 2.0 cable.

Ill try and get a pic up for reference.

Is pin 79 needed to read, flash, or both?

and if I can audible hear the ecu as I try to read it, does that mean its not bricked?
 
Can you use evo scan or a universal OBD II scan tool to read monitor status or check if you can see the TPS change when you sweep the throttle? After my cable failed halfway through a flash and bricked my ECU it would not do either of those but it did before.
 
The noise I was referring to was the relay click, but thanks for the info regarding pin 79.

So I cant read the evo 8 map in EcuFlash but I am getting something in EvoScan;

Info: OpenPort Firmware v1.11.329
Info: Battery 11.633V
Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Timer: 2122.4069ms
Info: Initialization Complete...
Info: Waiting for INIT Response...
Info: ECU ID: E4BD
Info: Connection successful...


Should I attempt to "Write" a base map in EcuFlash?

I just tried to "Test write to ECU" in EcuFlash, and this failed as well. Is this still related to pin 79, or now a driver error because I am atleast getting a reading in EvoScan?
 
I wouldn't try writing to the ECU until you know you have a good connection with ECUflash. Download it first... If you can download the ROM then you should be able to upload the rom without any issues...

One thing I haven't asked yet... What version of Windows are you using, XP or 7? If memory serves correctly there are some issues with using OP2.0 and Win7.

Edit... Never mind i found it in your ECUFlash log... you are running Vista. I cant remember if there were any issues with Vista.

Could be either, is it safe to assume you verified you have the reflash wire on the correct pin of the ECU?
 
Last edited by a moderator:
I actually have Windows 7 and not Vista but I verified it. Everything checks out okay. I even soldered the connection, and actually get something in EvoScan now because of it. One of the things that I read states that it's hard to read/flash if there's anything less then 12v, and according to EvoScan, I am around 11.63 ish.

and by download/upload ROM what do you mean? Read/Write, or actually download it from the internet? Totally new to this, sorry.
 
Maybe a 2.0 thing. Try starting the car and letting it run while you read the ECU. I know a lot of people actually let their car run while they flash to the ECU. I don’t know if it is any better or not but I have not had any issues with leaving my car off during the reflash... but then again I am running the 1.3 cable, not the 2.0 adaptor.

You could maybe try this if you are still having issues with reading the ECU. Could be a driver issue. It recommends ecuflash 1.43 beta for Win7 users.

EvoXForums.com - Mitsubishi Lancer Evolution X Forums - View Single Post - Ecuflash stopped working....HELP!!!!

Sorry about that... Download=Read from ECU... Upload=Write to ECU. I suppose I should be using "read" and "write" instead of "upload" and "download"
 
Thanks for all the help, Ill check that out

I am confused on this ROM part now because I am putting this Evo 8 Ecu (P/N:1860a118) in my 2G. Do I just use this revised/edited base map ROM that a member on here sent me for my lightly modded 96 eclipse or do I have to get the ROM that's written on the ECU from the previous evom member to be able to "read/write" successfully.
 
Depends What ROM did you receive from the other member and who did you get the ROM from here on tuners??? Honestly you don’t need to Read the ROM from the ECU to be able to flash to it, there are three possibilities of ROMS you could use. 94170015, 96530006, and 90550011. But the only one you really want to mess with is 96530006 or a variant there of. the 9055 ROMS work but Support for all the good fun add-ons stopped with Tephra V5.1, and the 9417 ROMs have a couple of other issues that will give you a headache. Almost everyone here has converted to the 9653 variant.
 
I didn't receive a ROM from the guy I bought it off on EvoM but "GSXDNA" on here sent me a base map/rom of his bolt on lightly modded/stock GSX similiar to mine just to get me up and running. The ROM's name is "96530006"

I just don't get why EvoScan atleast gets some data, but EcuFlash still fails... even with the updated beta.
 
That 9653 ROM you got from GSXDNA should be fine... I am kind of at a loss as to why it isn’t reading...

It has been a couple of days since I have flashed my ECU so do me a favor and refresh my memory. When you try reading the ECU is when it asks you what process to use correct??? I.E. you click on the Read ECU button then it brings up a window that you have to select what ECU you are reading, then it tells you to turn the ignition on and click "OK"... Correct? Or does it ask you that before you write to the ECU??? One of those small details I can’t ever remember... If it asks before you read, what ECU option are you selecting?
 
It changed a little during the beta, but when i click "read" a tab comes up for me to select the ecu type, and I select "Mitsubishi- 3rd Gen- 7/8" basically then I get a warning

"Connect the OpenPort interface to the OBDII port,
plug in the OpenPort initialization connector,
turn your ignition to the 'ON' position,
and then press the OK button to continue"

by that time, I already have everything plugged in, and the car turned "ON" and then I get the failed message

[03:13:16.989] EcuFlash Version 1.43.3150
[03:13:16.989] OS Version Windows 7
[03:13:16.989] Qt Version 4.6.2
[03:13:17.009] 62 memory models read.
[03:13:17.009] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[03:13:17.689] 357 ROM metadata models scanned.
[03:13:17.689] checksum module "subarudbw" loaded.
[03:13:17.689] checksum module "mitsucan" loaded.
[03:13:17.689] checksum module "mitsuh8" loaded.
[03:13:17.689] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[03:13:17.689] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[03:13:17.689] flashing tool "wrx02" loaded.
[03:13:17.699] flashing tool "wrx04" loaded.
[03:13:17.699] flashing tool "sti04" loaded.
[03:13:17.699] flashing tool "sti05" loaded.
[03:13:17.699] flashing tool "mitsukernel" loaded.
[03:13:17.699] flashing tool "mitsukernelocp" loaded.
[03:13:17.699] flashing tool "mitsubootloader" loaded.
[03:13:17.699] flashing tool "shbootmode" loaded.
[03:13:17.699] flashing tool "shaudmode" loaded.
[03:13:17.699] flashing tool "subarucan" loaded.
[03:13:17.699] flashing tool "mitsucan" loaded.
[03:14:13.421] J2534 API Version: 04.04
[03:14:13.421] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[03:14:13.421] Device Firmware Version: 1.11.3298
[03:14:13.421] Device Serial Number: TAXaZU2w
[03:16:36.998] sending init sequence 1 (0001)
[03:16:40.498] sending init sequence 1 (0003)
[03:16:43.818] sending init sequence 1 (FFFF)

[03:16:46.609] no response to any known code
[03:16:46.609] interface close

*Bold section is when I hear an audible "click" noise 3x

Here's a few screenshots

That audible clicking sound appears to be coming from under the hood in the engine bay somewhere
 

Attachments

  • Capture.jpg
    Capture.jpg
    36.3 KB · Views: 397
  • Capture2.jpg
    Capture2.jpg
    50.2 KB · Views: 282
OK. So Recap...

EVOScan and ECUflash both installed w/no issues.

With OP2.0 connected to OBD2 port + ignition on = EVOscan connects to ECU and Logs data (you verified it is reading data correctly by checking TPS changes in EVOscan when you press the gas pedal). This should indicate an ECU that is not bricked...

With OP2.0 connected to OBD2 Port + re-flash wire ran from ECU to OP2.0 connector + Mitsu Gen 3 Evo 7/8 selected as Read option = failed to connect

With OP2.0 connected to OBD2 Port + re-flash wire ran from ECU to OP2.0 connector + Test write to ECU= failed to connect.

Hate to say it but I am kind of stumped.... you re-installed drivers, you updated to the Beta Version you are getting a connection with EVOscan... Might be something up with your 2.0 adapter. Maybe someone here or on EvoM in your area has a 1.3 or even a 2.0 you can use just to see if it your hardware. I have to head home, but I will check something on my car when I hit the parking lot and will check back when I get home.

Sorry I couldn’t be more help.
 
I didnt try the tps sweep in evoscan but I will in just a second, and let you know, but everything you said describes my situation perfectly. I put something up on EvoM, and no one has gotten back yet.

Well TPS changes when I touch the gas!
 
I tried flashing on another computer with no luck. I also attempted reinstalling everything a handful of times including deleting all the drivers. I have no idea how it can log advance timing/tps/etc but not flash. i bought the cable new from tactrix.
 
Might be defective hardware then. Again sorry I couldn't be more help. Maybe one if the DSM ECU Flash guys will chime in tomorrow with an idea.

Well I gotta hit the sack. Good luck, and hope you get it figured out.
 
Well funny thing is I got my car to start. I found a couple missed pins after checking the visual guide on here because I was using another forums because it was geared more towards an automatic. The interesting thing is that it wouldnt allow me to read/write. It started on whatever map was on the car.

and even better is that my car ran 100 times smoother/better the whole trip back 45 miles (40hwy/5city) I have the log and I'll post it after I get off work today. Along with a detailed description.

Here's the log, I have had a really long day so I will describe it after work. I'm not sure what's going on with the time, but this was roughly from 5:50-6:30am this morning.

<Knock Sum address was "26" at the time>
Changed "Knock Sum" adress to "3E"

Apparently it's not letting me upload <3.1MB> and isn't giving me an exact reason why it failed. Any suggestions?
 
Well funny thing is I got my car to start. I found a couple missed pins after checking the visual guide on here because I was using another forums because it was geared more towards an automatic. The interesting thing is that it wouldnt allow me to read/write. It started on whatever map was on the car.

and even better is that my car ran 100 times smoother/better the whole trip back 45 miles (40hwy/5city) I have the log and I'll post it after I get off work today. Along with a detailed description.

Here's the log, I have had a really long day so I will describe it after work. I'm not sure what's going on with the time, but this was roughly from 5:50-6:30am this morning.

<Knock Sum address was "26" at the time>
Changed "Knock Sum" adress to "3E"

Apparently it's not letting me upload <3.1MB> and isn't giving me an exact reason why it failed. Any suggestions?

Glad to here you got the ECUflash part figured out.

You cant upload the Log to Tuners? Probably because it is to big Tuners limits post attachments uploads to 500k in size. Try uploading to Google docs and share it that way.
 
Support Vendors who Support the DSM Community
Boosted Fabrication ECM Tuning ExtremePSI Fuel Injector Clinic Innovation Products Jacks Transmissions JNZ Tuning Kiggly Racing Morrison Fabrications MyMitsubishiStore.com RixRacing RockAuto RTM Racing STM Tuned

Latest posts

Build Thread Updates

Vendor Updates

Latest Classifieds

Back
Top