The Central Hub for DSM Community and Information

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. This is where the DSM platform history is documented and archived. Log in to help us in our mission, and to remove most ads from the browsing experience.

ECUflash First Flashed DSM ECU! (98/99 Flashing FAQ)

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

Congrats, I don't know that your the first. I've heard of people doing this on the 98/99 ecu's for a while now.

EDIT: I also don't realize why everyone was so gun ho about the evo8 ecu when you can flash the plastic 98/99 ecus.

The evo ecu is well supported, the H8 ecus needed new hardware (openport 2.0) to be easily flashable and that has only happened recently.
 
So the 6/98-4/99 build dates are the only ones that work? :confused:

Now I'm really confused. I just found this old listing on eBay that shows MD346676 being a black plastic ECU.

Does that H2 stand for an H2 processor? If there is such a thing?

6/98-4/99 are 99s and are Flashable.
7/97-5/98 are 98s and are Flashable.

7/96-5/97 are 97s, which are plastic case but can't be flashed.

I have no idea what H2 is, mine says H4.
 
6/98-4/99 are 99s and are Flashable.
7/97-5/98 are 98s and are Flashable.

7/96-5/97 are 97s, which are plastic case but can't be flashed.

I have no idea what H2 is, mine says H4.

Hmmm... I found a deal on one for $85 that's MD346675.
So that means it's from a FWD 7/97-5/98. Maybe I should pick it up.
 
so 140ish and I can reflash the 2gb ECU? Which kinda sucks because I have the 95 EPROM ha... But my parts car is a 98 I believe. Im just curious I already have a logger. This is really interesting news though!

no closer to the $170 - $190 range. but still a lot better than 500plus. but like mama always said you get what you pay for.... there isn't nearly the support on this ecu yet like ECMlink or the EVO8 ecu. you might be waiting a little while for some of the cooler functions like NLTS, launch control, etc. etc. but i am sure it will beat the hell out of a SAFC or e-manage... with exception of the extra injector control of the e-manage ....

once a little more support comes on for this ecu :pray: i might be willing to switch from my EVO8 ecu just so i don't have to swap back and forth every year to get my car trough smog.......
 
Ceddy, THANK YOU! this is exciting stuff!

ECUs:

These are DSM ECUs that are Flashable.
1998 -> 7/97-5/98 MD346675 and MD346676
1999 -> 6/98-4/99 MD359402 and MD359403

The 1997 are also black plastic case, but are not flashable.
I have only tested a 98, which the 7202F CPU.
I assume the 99s use the 7202F, if they have a 7203F they are not flashable until a kernel is written for them.
Maybe someone could pop open a 99 ECU and check it out?



I'll add more info here...

My brothers 1997 (aug 1996: 1997 model year) talon had a metal cased ecu and it output to evoscan as fast as the 1998-1999 ecus. This was about 1 1/2 years ago when evoscan wasn't working well with 1995-1996 ecus. Not sure how that stands now. All original, VIRGIN car.
 
Ceddy, THANK YOU! this is exciting stuff!



My brothers 1997 (aug 1996: 1997 model year) talon had a metal cased ecu and it output to evoscan as fast as the 1998-1999 ecus. This was about 1 1/2 years ago when evoscan wasn't working well with 1995-1996 ecus. Not sure how that stands now. All original, VIRGIN car.

The 97s are a transitional ecu. They have the same type of ecu and MUT protocol as the 98/99s but are not flashable. I thought I saw some plastic case 97s on ebay.

Had my 98 ecu in my 95 with a 6-bolt swap today. Idles 1150cc injectors perfectly, and handles the 1G CAS fine. Idle and throttle response seen crisper than with my 95 ecu.

Drove around the parking lot a little, but then my old radiator decided to explode.
Hope to pick up another radiator this week, then test the ecu in high boost to see if fuel cut elimination works.
 
So I got to thinking while working my boring night shift job. Dangerous I know.

If the Openport 1.3 cable doesn't work because it can't output a high enough voltage with enough current, can't we just splice a little more power into that cable? Say three 6v batteries wired together? The extra 2 volts shouldn't make a difference. Those large batteries for flashlights should provide plenty of amperage.

Maybe even two 9v batteries could work? I have the 1.3 cable, as do many others.

I know it's the "cheap" way out. :p
 
So I got to thinking while working my boring night shift job. Dangerous I know.

If the Openport 1.3 cable doesn't work because it can't output a high enough voltage with enough current, can't we just splice a little more power into that cable? Say three 6v batteries wired together? The extra 2 volts shouldn't make a difference. Those large batteries for flashlights should provide plenty of amperage.

Maybe even two 9v batteries could work? I have the 1.3 cable, as do many others.

I know it's the "cheap" way out. :p

Yeah, I had the same thought. The 1.3 cable can't supply enough current so the voltage drops the required 16v to 8-9v.

I built a 12v to 16v converter using a National Semiconductor LM2586T that could supply 1500 mA at 16v. It was turned on by the 1.3 flash wire.
You must be logged in to view this image or video.


Couldn't get it to work though. Don't know if a 5v to 12v transition is required, like the JTAG or the older EcuFlash software has a bad H8 kernel.

The newest 1.41 EcuFlash won't allow the 1.3 cable to flash. I tried contacting Tactrix, but there customer support sucks.

I ended up selling my 1.3 cable on ebay for $100 to a WRX guy.
 

Attachments

You must be registered for see attachments list
Last edited by a moderator:
Just use the right cable, my understanding is that the H8 ecus are relatively easy to turn into a brick. The evo8 ecus have some support for returning them to useable status but the H8 ecus may have no second life abilities.
 
ceddy can you post the definition you wrote, want to try it with the 99 gsx rom. Did you find the wastegate duty cycle map?

I haven't looked for the WasteGate stuff yet. It would be nice for Traction Control for FWD guys. But from what I read its really hard to get it dialed in and consistent.

I have to figure something out for file hosting. I'll email you. The 98 I have is going to be totally different than your 99, but it will give you somewhere to start.

I wouldn't cross-flash different years. Always flash the image back that came from your ecu.
 
So I got to thinking while working my boring night shift job. Dangerous I know.

If the Openport 1.3 cable doesn't work because it can't output a high enough voltage with enough current, can't we just splice a little more power into that cable? Say three 6v batteries wired together? The extra 2 volts shouldn't make a difference. Those large batteries for flashlights should provide plenty of amperage.

Maybe even two 9v batteries could work? I have the 1.3 cable, as do many others.

I know it's the "cheap" way out. :p

You could always sell your 1.3 cable to someone like me and put that money towards the 2.0:D Just throwing it out there haha. (PM me if you agree)


And btw im really glad they finally figured this out, i hope support for these ecu's grows quickly
 
You could always sell your 1.3 cable to someone like me and put that money towards the 2.0:D Just throwing it out there haha. (PM me if you agree)

PM'd



It seems like I'll just buy the 2.0 cable. If my turbo didn't blow this weekend, I would have been all over getting the ECU and 2.0 cable this week. I guess I should start learning how to use EcuFlash and the hex stuff. :hmm: If we could get some ROMs and definitions posted, that'd be awesome.
 
Unless your developing there really isn't any hex work. The closest is copying a couple of hex variables which you can do with copy and paste. After that all you have to know is that any hex variable you encounter has to be added as 0xABCD after that it is all easy. Boolean settings are easy too, 1=yes or on and 0=no or off (usually).
 
Unless your developing there really isn't any hex work. The closest is copying a couple of hex variables which you can do with copy and paste. After that all you have to know is that any hex variable you encounter has to be added as 0xABCD after that it is all easy. Boolean settings are easy too, 1=yes or on and 0=no or off (usually).

Oh, if I'm doing this, I'm all in. I have a problem where I have to tinker, even if something works fine. :thumb: I've done HTML, QBasic, VB, C++, etc, etc.... I might as well at assembly type stuff.

That, and I want to eventually figure out a way to control an actuator (stepper motor or something similar) to control a VGT turbo. :D You can't argue with a 3.5 cm^2 exhaust housing for spool up and as large as 25cm^2 for top end flow. :cool:
 
To do some fancy stuff you need to dissemble the ROM via disassembler like Ida Pro, figure out how sensors are operating, and then patch the binary image.

It's not programming in a straight sense of word.
 
Anyway to make this work with the 1.3 evo cable? I would want to try it before I spend the money on it. Otherwise I may just sell my 98/99 ecu and stick with dsmlink which I'm 90& sure I will do.
 
You need 2.0 cable. 1.3 doesn't work with our ECUs. If you want, you can make your own programmer, but bare 1.3 wont do.

By the way, 2.0 doesn't allow ABS and AYC logging, 1.3 allows that. Then again, ABS logging always shows something bogus and activates ABS all the time while you drive.
 
why can´t open the rom file? ask me for definition but then opens and just give info about the rom can´t see any tables
 
why can´t open the rom file? ask me for definition but then opens and just give info about the rom can´t see any tables

You need to put EM2055.xml in ->
C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\eclipse\
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Build Thread Updates

Latest Classifieds

Back
Top