New ROMs database website is now up and running...

http://www.evoscan.com/roms/mitsubishi/

When you upload a ROM File zip, it must not contain any folders/subfolders. Same goes for XML Definition zip files
(yes you can have multiple base files)

icon at the top here for Vehicle Make: i.e. Mitsubishi / Subaru / Nissan
Download Selected ROMs (zips all roms in one file for download)96940011

Master Base XML Files

Vehicle Glossary:
JDM = Japanese Domestic Market (built and sold in japan - quite often exported to New Zealand, Malaysia, Australia.)
USDM = United States Domestic Market (vehicle built and sold domestically in USA. normally a JDM based model to suit USA Emissions and other local Govt laws)
EDM = European Domestic Market (vehicle built and sold domestically in Europe. normally a JDM based model to suit Europe Emissions and other local Govt laws)
FQ320 = European Lancer Evo model modified by Mitsubishi Factory with performance parts and ecu rom.
EcuTek modified ecu rom done by Mitsubishi factory technicians before sale. other models include FQ320, FQ400.  the number refers to the HorsePower rating on the dyno.
Import = Bought from another country and imported into another country, i.e  import from Japan to United States.
Evo = Mitsubishi Lancer Evolution
RA = RalliArt. 2008-2010 mitsuishi evo that has performance, technology, and price higher than a standard Lancer but a does not performe as well as a full EvoX GSR or EvoX MR. 
It is the middle point of performance and price of the two models.
RS = RalliSport, a lightweight model of Evo, used for street and rallying.  because it has less weight, the vehicle is stronger, stiffer, and noiser due to less padding.
GSR = Standard Trim Lancer or Lancer Evo
MR = Standard Trim Lancer or Lancer EvoX
SST = Automatic TipTronic Paddle style gearbox.
S-AYC = Super Active Yaw Control. See this page for more details.
ROM = Read Only Memory - this is the software program and settings that can be overwritten by uploading a new ROM file to the vehicle's Electronic Computer Unit (ECU)
ECU = Electronic Computer Unit - there can be up to 5 or more ECUs in a vehicle, such as SRS (Airbag ECU) ABS (Active Braking System)
AYC (Active Yaw Control) EFI (Fuel Injection) ACD (Active Centre Differential) ETACS (Door/Alarms/AirCon) 
EFI = Electronic Fuel Injection - normally used to describe
ECM = Electronic Computer Management - this is usually used to describe the main EFI Fuel Injection ECU in the vehicle.
Stock = Original ROM as uploaded by the Vehicle Factory during manufacture of the ECU.
5-speed Automatic INVECS-II =

Commonly known as the Evo 7.5 due to the vehicle being an Evo 7 that was released at the same time as the Evo 8. The major ROM difference between the Evo 7 and the Evo 7.5 GTA is the GTA being a 512k 8000 series ROM and not a 256k 9000 series ROM file as used in most Evo 7 and 8 models. Along with the engine, the rom file also includes the automatic transmission code along with it's own MUT table. It is also unique in that it uses different main fuel, ignition, and boost maps depending on the selected gear. To read the full 512k rom size a new READ_TEMPLATE files should be used with a 7055 memmodel.

Also have a read of the Mitsubishi Lancer Evolution Wiki... it is keep up to date fairly well.

96530006 is a 2005 EDM Evo ROM, commonly used to replace the 96940011 USDM ROM, and has been successfully used to replace many other Evo VIII ROMs as well.

96940011 (and other) Replacement Notes

The immobilizer functions differently between 96940011 (or your original ROM) and 96530006, and you will need to change the behavior for the car to start correctly. You can either disable the immobilizer completely, or change the 96530006 immobilizer behavior to function like your original ROM did. Only do one, or the other; if you disable the immobilizer completely, there is no need to do the following, and if you do the following you should definitely leave the immobilizer enabled for your own security.

To change the behavior, you'll need to add the following to both 96940011.xml and 96530006.xml (or the base XML for the ROM you're coming from):

Then, open your original 96940011 ROM, and copy the value from the "Immobilizer Hex" table under the  "Misc" section (probably 0x0058). Open your new 96530006 ROM, and open the "Immobilizer Hex" table. You'll see that the value is  probably 0x004D; paste in the value you copied from your 96940011 ROM in its place.
Then, do the same thing for the "Immobilizer" table under the "Misc"  section.
At this point, your car should start as expected, with the  immobilizer functioning correctly.
For more information on this swap, please read the original threads on EvoM.
Download
File:96530006.HEX
File:Def  file 96530006 tephra510 new tables 20081101.zip
EcuFlash Definition Errors
Injector Battery Voltage Latency Compensation is incorrect in the  original EcuFlash 96539996.xml file. Replace it with:



 


 

Note: The zipped xml on this page has this corrected already. The error is located in the standard xml which comes with Ecuflash intallation.

Addresses

MUT Table

36200

There are 4 different 2-byte Load choices each with different correction factors.

2-byte LOAD_Raw (no temp compensation)

MUT00 = 8984

MUT01 = 8985

2-byte LOAD_Temp_Compensated

MUT00 = 8986

MUT01 = 8987

2-byte LOAD_Baro_Compensated

MUT00 = 8988

MUT01 = 8989

2-byte LOAD_Temp_and_Baro_Compensated

MUT00 = 898A

MUT01 = 898B

Load correction note: The ECU uses the following logic to find the lookup info it needs:

Fuel maps will either use Load_Raw OR LOAD_Temp_and_Baro_Compensated depending on an certain conditions

Ignition Maps will either use LOAD_Baro_Compensated OR LOAD_Temp_and_Baro_Compensated depending on the MAF IAT. (Thanks to Tephra for this info).

It is typically best to use the 2-byte LOAD_Temp_and_Baro_Compensated for tuning, while taking into account the lookup factors mentioned above for both Fuel and Ignition Timing. This will allow the tuner to accurately tune ignition timing while being able to compensate for the lookup logic for fueling. LOAD_Raw is typically 10-20 points higher than LOAD_Temp_and_Baro_Compensated at peak boost. You must take this into account when tuning using the 2-byte loads. With the advent of Tehpra's 1byte load(using a Tephra Mod ROM), you can use 1byte load(which is actually LOAD_Raw) to log LOAD_Raw. You can setup your 2byte load to be LOAD_Temp_and_Baro_Compensated, this will allow the tuner to see both compensated load and LOAD_Raw. Ultimatly, how you decide to set-up your 2-byte load and the methods you use to tune are up to you.