I've been driving around untuned and it's really pissing me off because EcuFlash wont work on my car now. About a month and a half ago, my friend flashed my car and forgot to save the stock ROM ( ), so I end up having to go to Mitsu and they reprogram my car. The, when it's back in my possesion, we go to try and flash it here's exactly what happens:
-Hook up the cable and read the ROM
-Everything reads fine
-After reading, a prompt comes up saying "Undefined ROM" and gives me 3 choices
-Define ROM from scrtach, Inherit ROM from one of the below(has tons fo ECU's listed), and some other thing.

I don't want to do anything without being sure my car will run, and have a little bit of fear of losing that damn code again. Does anyone have any idea what I need to do?

 

It seems that the rom needs an xml definition and it would work.

 

When you first open ECUFlash, under "Task Info" is this what it reads?

[06:40:45.312] Version 1.28.716
[06:40:45.312] 8 memory models read.
[06:40:45.828] 71 ROM metadata models read.
[06:40:45.828] checksum module "subarudbw" loaded.
[06:40:45.828] flashing tool "wrx02" loaded.
[06:40:45.828] flashing tool "wrx04" loaded.
[06:40:45.828] flashing tool "sti04" loaded.
[06:40:45.828] flashing tool "sti05" loaded.
[06:40:45.828] flashing tool "mitsukernel" loaded.
[06:40:45.828] flashing tool "mitsukernelocp" loaded.
[06:40:45.828] flashing tool "mitsubootloader" loaded.


Make sure that there is a number of ROM metadat models read. This happend with the 1.27 version where it was changing by itself to "0 ROMs read" and some people along with myself were getting the "Define ROM from scrtach, Inherit ROM from one of the below" message.

*EDIT*
Here is the post and the thread on this.

Thread
Post

 

yeap thats how it reads =D

 

Theres a good chance (assuming all your data files are where their supposed to be) that your new ECU has a rom that just hasn't been documented yet. This happens pretty often, most often when Mitsubishi has a new reflash to fix a problem or an OEM Replacement ECU has a new or altered Rom version.

You need to be sure there is no definition file already (check how many metadata files you loaded as mentioned above) and then see what ECUID it is, and find the closest match, once you have a close match you'll probably have to fix a few of the tables up.

Nobody said this tool was intended to do all the work for you..

 

Thanks all for the replies, I'll check it out next week.

 

If an exact definition file can't be found, it seems to me that it wouldn't be a good idea to fix up any munged tables. This was discussed on some of the other undefined ROM threads.

 

If you find an ecu definition that is one or two revisions off you can sometimes get away with it.. but in generall your correct, if your not 100% sure what your doing I wouldn't do it and try to attempt it.

 

So what am I to do? I'm really lost...

 

Flash it to another rom. Find one that you like (for instance v15 since it has injector scaling) and flash it to that. REMEMBER YOUR IMMOBILISER this time.

EDIT- Just noticed that you have an 8...disregard the v15 comment, but just look for any other ROM, flash it, tune it, etc.

 

But it's not letting me get into the parameters, so I can't even view my immobilizer code, hence why I'm so apprehensive...

 

It can't hurt anything to download your ROM from the ECU and when ECUFlash asks for a definition to just pick one from the list in ECUFlash. After that, you can look in the ROM you downloaded and determine what definition you actually have.

So, when you download your ROM, at one point ECUFlash will ask for a definition. When that happens, navigate to:

c:\Program Files\OpenECU\ECUFlash\rommetadata\mitsubishi\evo\

You'll find a bunch of definitions. Try picking perhaps 94170014.xml which I'm guessing corresponds to an '03 definition. If the definition is close enough, you'll be able to read the immobilizer code from your downloaded ROM, and then you can switch to one of the "defined" ROMs.

 

The one that happens most frequently is the one on my car.. Its 94170008, and 94170007 shows up often enough.. The only major difference between roms with one or two revisions is the Axis data is relocated and possibly one of the Knock sum filters..

I have to be completely honest with you guys though.. I see alot of these types of questions come up, and it concerns me that people are not using basic logic to work these things out.. If your ECU type says 94170006 and there is none, I would logically look for one that was similar, and then look at all of the tables to see if the data looks right.. (Compare it with another map you have that does load without a problem)..

I'm not knocking the enthusiasm for people to tune their own cars, but some of this is pretty basic troubleshooting logic that you need to be able to work through when your tuning a car.

I have said this before, ECUFlash's rom wizard isn't the most intuitive and if you make a mistake with the definition, your stuck with it until you can find where the "broken file" you created ended up.. But its not very hard to find something called undefined.xml and delete it.. And if you can't remember what your ECUID is when it comes up, before you go to the next page in the wizard that asks to select an inheritance or copy, write the info down.. Then find a closest match, and fill out the data in the fields.. If you don't at least fill out the ECU ID info you'll end up with an undefined.xml file..

 

It's goes in stages, People don't know what to do, then they learn what to do and mess/blow up there cars, then the masses learns how to tune a evo without blowing it up

 

I have a map that is using evo9base for some reason and I cant seem to get the box to pop back up to try different xml file. Anyone know how to edit a map's xml definition? Ive even tried renaming the rom and still pulls up the wrong one