openecu.org

The revision history of the latest version 1.41 of ECUFlash released just yesterday claims that the 2.0 cable has fixed the lockout issues with these ECUs. Does this mean that 2000 Eclipse GT computers can now be read successfully and written as well? Last I knew, these cars were not even supported as read only. The 4cyl were, but I have yet to see a 2000 Eclipse GT rom posted anywhere. I own a 1.3 cable which for my purposes is nothing more than an extremely good data logger, so if I am to purchase a 2.0 cable, I want it to know that it support my car, not too much to ask right? I would feel rather stupid if I purchase the cable and can not do any more with it than I can already with my 1.3 cable.

Does anyone have a rom from one of these cars yet?

Wow this is great news. I know there are 2000 GT roms out there, but I will have to find one. If I recall correctly, a rom could be pulled from a federal emission spec 2000 GT but not from a california emission spec GT.

I had these two hex on my computer, but cannot remember which eclipse it was from.

Using OP2, read still works no problem. I tried a test reflash on an EVO 6 and got this:

[11:58:40.681] kernel flash enable
[11:58:40.696] kernel blank flash page: addr: 00010000
[11:58:55.711] WARNING: failed to erase page at 00010000!
[11:58:55.711] kernel flash disable
[11:58:57.726] interface close

I would be interested to know if this is a fault with my OP2 or ECU, or if there is more software involved.

MattS00 wrote:I had these two hex on my computer, but cannot remember which eclipse it was from.

Those look like the 2001 roms. Which of course probably contains very similar maps to the 2000 rom. I really want to see someone be able to flash a 2000 Eclipse GT Cali spec before I go out and buy a OP2 cable to replace my 1.3 . This decision is reinforced by the news that there are problems with the Evoscan software and the OP2 cable. Evoscan is extremely useful(even tho the support kinda sucks and the evaluation expressions for fuel trims are flawed, which the developer refused to layout the proper syntax for the correct expression which is (x-128)/5 as verified by my Snap-On Solis and my Autoenginuity cable and software oh yeah, and my CarChip, and the MUT3, not to mention, even though he charges for the software, he does not offer free updates) and at this point, it is the only thing I actually can use my cable for on my own car. But enough of my ranting... anyone have an OP2 cable and live in southern new england so we can test this thing?

Hello everybody first of all sorry for my offtopic but I have no other idea where should I ask my question I'm from Europe and have an Outlander Turbo similar as the Evo 8 engine but with smaller turbine and electric gaspedal and canbus system. So 4G63 engine with MH8202F ECU processor, what do you think can I read and write with an openport 2 cable and the new ecuflash 1.41 ?

the 1.41 ecuflash and the openport2 cable are working with the Eclipse 4G, outlander 4G69mivec or with any other CAN mitsubishi except the evo x ?

Thank You, Gergo

I just found out I can use the schools decompiler which supports the H8 processor, cant wait to get my hands on a cali spec 2000 Eclipse GT rom and crack it open!!

Still no news about the california spec H8 flashability.... I might just have to bite the 200$ bullet and buy a cable to find out for myself. I might just try bypassing the voltage issue in my 1.3 cable by using an external supply for flash voltage. If it works, great!

eh, using the most up to date ECUFlash software still wont read my ROM. I will probably just give up on flashing at this point and use the cable for the datalogging that it is awesome for and build a live tuning application using the data from it to tune my Emanage Ultimate.

LOL @ me, there is no Emanage SDK

mh8305 is the same as H8 (MH8305f = H8)?

No