I have used ecuflash on many times with no problem. A friend brought his evo over 03' everytime we try to pull his rom we get the message that asks how it wants us to save the rom image. Inheriate? from what? We where able to save the *.bin file it is 256k in size, but unable to see any of the options...

I have not seen this before. It works fine on other cars but not this one. the ecu ha never been flashed. I am using ver 1.28.716...

Any ideas?

thanks

 

Its possible that he has an ECU version that does not have a metadata file yet.

 

Is there anything that can be done with the current version of ecuflash?

 

inherit from the EVO 7 base and try again.

 

I'll give it a shot.

 

any success? post back when you know maybe?


Trav

 

I tried the evo7 and didnt work. Didnt see any of the detailed settings... example launch control, or timing and fuel curve...

any more ideas? anyone?

 

bump , i need to know also ?

 

up up up

 

If you can't read the map, try and find out if the ECU has been reflashed with one of the ~14 different maps used by to solve this problem. I had my EVO reflashed with v14 I think, and ECUFlash does not have the proper definitions for this ROM image yet.

Depending on your ECU type, you might be able to reflash with a non-patched ECU. I was able to do so, and after reflashing with a 1st allocation rom, I have been able to flash away with no problems.

If you are going to try this, be aware that you could really screw up and leave the ECU in an unusable state if you put the incorrect image onto ROM!!!

If you visit openECU.org you can find maps that should be correct for the version of the ECUs CPU. The ROM image that you download from the ECU should provide the type of CPU, from there you need to find a matching ROM image.

 

Hi

I would sugest you get the codes of of the ECU box itself and then ask around to see if anyone has an XML for that ECU.

Another way would be to try and associate the ROM image with one from an EVO of the same year and see if you have any luck that way. If you post the rom at openECU as well someone maybe able to help you.

MB

 

Most of us end up finding an ECUID very close to the one that can't match.. and import the values from that map.. .Then we go through all of the parameters and make sure they match up to the new identifier..

Honestly its a bit convoluted and can be more complex than it needs to be due to how Evoscan works with XML files, how it saves them, and the order of the screens it uses to identify and match a new ECU.. If you hit the forward and back button a few times to compare info it crashes when using that wizard..

I had this problem with my ECU specifically.. It turned out another definition was an exact match except for one axis in one location..