2011 Candian ecu rom
Feb 5, 2012 | 09:45 PM
#32
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
No worries. And I see you've got a new quote in your sig... from some moron... 
The upshot of all this is that 56940009 would need a whole load of "discovery" work invested in it before it could be used as an effective tuning base. That's unlikely to happen any time soon.
So, for now, 56940009 is just another ROM to put on the shelf for use when "flashing back to stock".
56940007, in contrast, has been well researched, tables discovered, ROM patches written, logging addresses found, and v27 base map released.
That makes 56940007 the Chosen One (wieeooo).
Rich
The upshot of all this is that 56940009 would need a whole load of "discovery" work invested in it before it could be used as an effective tuning base. That's unlikely to happen any time soon.
So, for now, 56940009 is just another ROM to put on the shelf for use when "flashing back to stock".
56940007, in contrast, has been well researched, tables discovered, ROM patches written, logging addresses found, and v27 base map released.
That makes 56940007 the Chosen One (wieeooo).
Rich
Feb 5, 2012 | 09:52 PM
#33
Thread Starter
Newbie
Joined: Jul 2009
Posts: 50
Likes: 0
From: edmonton
No worries. And I see you've got a new quote in your sig... from some moron...
The upshot of all this is that 56940009 would need a whole load of "discovery" work invested in it before it could be used as an effective tuning base. That's unlikely to happen any time soon.
So, for now, 56940009 is just another ROM to put on the shelf for use when "flashing back to stock".
56940007, in contrast, has been well researched, tables discovered, ROM patches written, logging addresses found, and v27 base map released.
That makes 56940007 the Chosen One (wieeooo).
Rich
The upshot of all this is that 56940009 would need a whole load of "discovery" work invested in it before it could be used as an effective tuning base. That's unlikely to happen any time soon.
So, for now, 56940009 is just another ROM to put on the shelf for use when "flashing back to stock".
56940007, in contrast, has been well researched, tables discovered, ROM patches written, logging addresses found, and v27 base map released.
That makes 56940007 the Chosen One (wieeooo).
Rich
Feb 5, 2012 | 10:02 PM
#34
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
It's probably not Canada-specific. It'll either be a factory-flash ROM update (ie. part-way through the "year model" production), or a "dealer" applied reflash.
It's Mitsubishi tinkering with the engine management. Go check out the ROM IDs on "goldenevo.com". Loads of revisions - under the 2008 5MT list, there are eight variants of 5268xxxx... and there are doubtless more out there that didn't make it to Golden's database.
Rich
It's Mitsubishi tinkering with the engine management. Go check out the ROM IDs on "goldenevo.com". Loads of revisions - under the 2008 5MT list, there are eight variants of 5268xxxx... and there are doubtless more out there that didn't make it to Golden's database.
Rich
Feb 7, 2012 | 06:27 PM
#35
I think I am having this same issue. After finally getting EcuFlash to read my ECU, it came up with the Unknown Rom Image error. I had the 56940007 xml definition file in the rommetadata folder, but it still didn't like it. So I tried this advice from another EvoM thread:
OK. I tried that, and under ROM info I have an Internal ID: 56940010.
10 WTF??!?! ECU ID and Case ID are blank, and it gave me two error messages about checksum being incorrect - correct? Yes/No. I clicked yes twice, but it didn't do anything. The log just says 1048576 byte image read.
I really want to get the GST basemap on, but would like to be able to flash back to stock if needed. Would I be able to do that with this the way it is now?
EDIT: I tried the "Inherited" route and it had an address of 5002a and length of 4 bytes. The identifier again was 56940010. Now under ROM info, it says "Inherits: 56940007", and I didn't get any checksum errors pop up.
When EcuFlash gives you the unknown rom error it will let you create a new XML definition. Follow that process until it gives you the Rom ID, then you can grab that XML and put it in your ecuflash/rommetadata directory.
10 WTF??!?! ECU ID and Case ID are blank, and it gave me two error messages about checksum being incorrect - correct? Yes/No. I clicked yes twice, but it didn't do anything. The log just says 1048576 byte image read.
I really want to get the GST basemap on, but would like to be able to flash back to stock if needed. Would I be able to do that with this the way it is now?
EDIT: I tried the "Inherited" route and it had an address of 5002a and length of 4 bytes. The identifier again was 56940010. Now under ROM info, it says "Inherits: 56940007", and I didn't get any checksum errors pop up.
Last edited by Mu-Meson; Feb 7, 2012 at 06:38 PM.
Feb 7, 2012 | 06:38 PM
#36
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
If all you want to do is give EcuFlash a nod so it can flash the map back later:
Make a file named "56940010.xml" in your "rommetadata/mitsubishi/lancer" directory (or wherever), and put the following text in it:
That'll do. The tables and scales won't be referenced correctly, so stuff probably won't look right if you go digging through the ROM. So don't go editing it. 
But EcuFlash will be 100% happy. It'll open that ROM without complaining, and will be able to reflash it to your ECU.
Rich
Make a file named "56940010.xml" in your "rommetadata/mitsubishi/lancer" directory (or wherever), and put the following text in it:
Code:
<rom>
<romid>
<xmlid>56940010</xmlid>
<internalidaddress>5002a</internalidaddress>
<internalidhex>56940010</internalidhex>
<make>Mitsubishi</make>
<market>USDM</market>
<model>Lancer</model>
<submodel>Ralliart</submodel>
<transmission>SST</transmission>
<year>2011</year>
<flashmethod>mitsucan</flashmethod>
<memmodel>M32186F8</memmodel>
<checksummodule>mitsucan</checksummodule>
</romid>
<include>56940007</include>
</rom>
But EcuFlash will be 100% happy. It'll open that ROM without complaining, and will be able to reflash it to your ECU.
Rich
Feb 7, 2012 | 07:45 PM
#38
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Just to clarify, if your ECU came from factory with a "5694" series ROM, you should be able to reflash it with any other "5694" series ROM.
Ditto for any X/RA ECU, it seems. First 4 digits of ROM ID... that is the important bit.
Rich
Ditto for any X/RA ECU, it seems. First 4 digits of ROM ID... that is the important bit.
Rich
Mar 2, 2012 | 07:18 AM
#41
Registered User
Joined: Sep 2011
Posts: 32
Likes: 0
From: Toronto
Sep 15, 2012 | 03:49 PM
#43
Hey Rich, just curious if you can share that same info with me. I just flashed my car using the Pass Thru CAN stuff from Mitsu and this is my new ROM ID. I know I can go back to my old one, but would kind of like to have the update that Mitsu put out as it has to do with timing chain elongation, etc.
Sep 15, 2012 | 05:51 PM
#44
Newbie
Joined: Jan 2012
Posts: 97
Likes: 0
From: HELL
What is the "Pass Thru CAN stuff from Mitsu"? The mUT-III OEM tool?
Mart
Mart
Hey Rich, just curious if you can share that same info with me. I just flashed my car using the Pass Thru CAN stuff from Mitsu and this is my new ROM ID. I know I can go back to my old one, but would kind of like to have the update that Mitsu put out as it has to do with timing chain elongation, etc.
Sep 16, 2012 | 12:29 AM
#45