Yep, that's all there is to it. If you don't have that stock ROM, you can grab it from the top of this thread:

http://www.evoxforums.com/forums/sho...=19274&page=12

 

Awesome,

Thanks again for the help

Damon

 

Mike,

I got it to work but now when I open ecuflash the maps are not reading correctly. The scaling is not correct. I'm not sure what I did or how to fix it.
I have attached my rom could you take a look at it.

 

Do you now have a definition for 52680028? If so, where did you get it? Can you send it to me at support at tactrix dot com?

 

No, It inherited the 56280024 the attachment is what I got from the ecu

 

Also when I open it in notepad its a bunch of crap

 

When you try to create a definition by inheriting from another existing definition, not everything will necessarily work. EcuFlash is happy to help you try, but you need to take a look at the results and verify that everything is logical before attempting to use the inherited definition, since using an incorrect definition can have negative consequences. If there are only minor differences, you can override those tables as needed in the new definition while inheriting unchanged table definitions from the older definition file.

It's important to understand what the general differences are between ROMs, even in the same model/year. You'll often just have a simple data change in a new ROM revision. If this was the case between 56280024 and 56280028, then all the tables would look correct, but some of the data in the tables would be slightly different. But, 56280028 actually has structural table differences, so simply inheriting from 56280024 won't work. By inheriting from a previous definition you're saying that just like that previous ROM, the new ROM also has table W in location X with dimensions Y and Z. That's not accurate here, otherwise we'd already have a definition for 56280028 included in EcuFlash. There is real decoding work to be done to understand the changes.

Have you watched many of those youtube videos I referred you to? I'm pretty sure he goes over some of these concepts in there.

Notepad is a text editor. A ROM image is not plain text. That's like trying to open an image file with Notepad.

-Mike

 

Mike here is what i get when i open the bin file i attached. I think I messed up the first download from my ecu. I did the inherit from and it inherited from a 2014 EDM evo x. Does that make sense

[20:22:25.948] EcuFlash Version 1.44.4347
[20:22:25.948] OS Version Windows Vista
[20:22:25.948] Qt Version 5.2.0
[20:22:25.964] 67 memory models read.
[20:22:25.964] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[20:22:32.188] 749 ROM metadata models scanned.
[20:22:32.188] checksum module "subarudbw" loaded.
[20:22:32.188] checksum module "subarudiesel" loaded.
[20:22:32.188] checksum module "mitsucan" loaded.
[20:22:32.188] checksum module "mitsuh8" loaded.
[20:22:32.188] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[20:22:32.188] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[20:22:32.204] using metadata XML ID read_mitsum32186f8can from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_mitsum32186f8can.xml
[20:22:32.204] flashing tool "wrx02" loaded.
[20:22:32.219] flashing tool "wrx04" loaded.
[20:22:32.219] flashing tool "sti04" loaded.
[20:22:32.219] flashing tool "sti05" loaded.
[20:22:32.219] flashing tool "mitsukernel" loaded.
[20:22:32.219] flashing tool "mitsukernelocp" loaded.
[20:22:32.219] flashing tool "mitsubootloader" loaded.
[20:22:32.219] flashing tool "shbootmode" loaded.
[20:22:32.219] flashing tool "shaudmode" loaded.
[20:22:32.235] flashing tool "subarucan" loaded.
[20:22:32.235] flashing tool "subarucand" loaded.
[20:22:32.235] flashing tool "subarubrz" loaded.
[20:22:32.250] flashing tool "subaruhitachi" loaded.
[20:22:32.250] flashing tool "mitsucan" loaded.
[20:22:37.458] opening rom file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/52680028finally.bin
[20:22:37.520] 52680024 (169 tables) inheriting evo10base (326 tables)
[20:22:37.536] 52680028 (0 tables) inheriting 52680024 (326 tables)
[20:22:37.583] 1048576 byte image read.
[20:22:37.583] mitsucan checksum module determined checksum area to be {{0x00000000-0x000fffff}}
[20:22:37.614] using metadata XML ID 52680028 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/52680028usdm.xml
which inherits XML ID 52680024 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/52680024 2008 USDM Lancer Evolution X 5MT.xml
which inherits XML ID evo10base from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/evo10base.xml
[20:22:37.614] ---notes for evo10base---
2012/10/26 [Tactrix] Updating using multiple base file data sources including base file from Golden Evo repository.
2012/11/01 [Tactrix] Moved most non-address attributes from child files to base class. Standardized file naming. Change scalings on some code modifying tables (i.e. Mode 23 - IFMode 0x05 -> 0x23) to more strongly typed bloblist scalings.
2014/05/20 [Tactrix] Tactrix definition auto cleaned|merged w/ GoldenEvoMay2014.
---notes for 52680024---
2014/05/01 [Tactrix] Original file from Golden Evo repository. If this file is useful to you, please consider donating at http://goldenevo.com/
2014/05/01 [Tactrix] Moved most non-address attributes to evoxbase.xml base class. Standardized file naming.
2014/05/01 [Tactrix] Visually examined tables for obvious errors, but no in-car verification has been done.
2014/05/20 [Tactrix] Tactrix definition auto cleaned|merged w/ GoldenEvoMay2014.

 

Yes, it makes total sense. You told it to attempt to make a definition for 52680028 by inheriting from 52680024. EcuFlash is reporting that from the lines we see here:


[20:22:37.614] using metadata XML ID 52680028 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/52680028usdm.xml
which inherits XML ID 52680024 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/52680024 2008 USDM Lancer Evolution X 5MT.xml


But what I'm telling you is that you can't do that because 52680028 is not simply a minor data change from 52680024. There are structural changes that will require real work on a new definition to make it correct. If it were only data changes, a simple inherit from a close numerical ROM revision will often do the trick.

 

Also how do I change from the 52680028 rom to one that has been defined .

Thanks
Damon

 

Sorry forget the last post can I change my ecu to an older ROM. Im trying to learn this I live in Asheville nc and there are no tuners around here.

 

Yes, as I said before, grab 52680024 from the discussion I linked to earlier ("If you don't have that stock ROM, you can grab it from the top of this thread"), open it in EcuFlash, and flash it to your car. You will then have 52680024 in your car. That's all there is to it.

-Mike

 

Thank you again I'll give it try

 

Mike,

I am having a problem, ecuflash keeps crashing when I try to test or write the 52680024 to my car. What am I doing wrong? It gets to 40% and it crashes.
Please help

 

I'm guessing you mean you're seeing an error not 'crashing' as in the program is shutting down. Is that right? I'm getting ready to head out of the office so I might be able to look at it until Monday, but can you try a test write and when you encounter the error, copy everything from top to bottom in the EcuFlash 'Task Info' logging window, and paste that in an email sent to support at tactrix dot com? If you aren't able to complete a test write then don't try a real write.