Bought a brand new OP2.0 cable from tactrix. Installed Ecuflash 1.44.4503. Brand new laptop running windows10 with only Ecuflash and Evoscan installed.

Ecuflash appears to be able to talk to the ECU, performs the read from ECU apparently fine, then says unknown rom image. It will let me save it.

When I try to check it with goldenevo's rom checker, it returns FFFFffff.

My goal was just to enable mode23 so that I can log with Evoscan.

What am I doing wrong?

Attached is the rom file that I retrieved. Had to append .bin to the filename end for the forum to allow me to upload it.

Thanks!

 

Pretty sure on the USDM rom if you have xml for the 2015 GSR, you can just change the ROMID parameters from 59580006 to the FE's 52680002 and it will line up nicely for you.

Our aussie rom is very similar

 

I'm having the same issue on my 2015 X.. Not sure what to do!!

 

This is not my own work - but here it is for the USDM FE

 

Where do I paste this to make it work??

 

program files (x86)/openecu/ecuflash/rommetadata/Mitsubishi/evo


then open up ecuflash and when you read the tune or open up a saved tune file it should be happy

 

This is what I'm dealing with..

 

can you save the file and post it up here?
save it as a .bin or .hex rather than .srf if you can (I use a very old version of ecuflash, not sure what the new options are)

 

Can you read from your ECU again and post the ROM again? It has some kind of memory issue.

 

Rom Id is @ 50141...

No memory issue.

Vin, ECU Hardware & Ecu SW has been added in the beginning of the rom program data area. The whole data has been shifted. If anyone else has a 2015 FE model Evo, could you post up your stock rom for comparison?

In the picture, the 2015 FE is on the left and the mem dump on right is a 2014 GSR stock read

 

Here is an aussie one if you're interested

 

Thank you. took a quick look with my map vector script. It seems the data in his memory on his ecu is modified. I don't have an idea who would put the VIN, HW, & SW in the beginning of the memory but it did shift the whole data points for the data, x axis, y axis, and table data.

The best thing he can do is upload a 100% stock rom/bin back into his car and use the xml you posted up for the 52680002.

I will post up a 52680002 I have in my repository. It is the only one I have for a 2015 FE That came off a supposed stock car.

 

how does this one compare?


I have it on file but not sure if it was the one he posted above or not... lots of FE roms so I need to make sure I have a clean one - I'll use the one you posted though.




edit - the file you posted is the mode23 and fuel map modified one. I think mine is completely stock

 

Yep this one is 100% untouched 2015 FE. Nothing has been changed at all in this one. The OP should flash this one in and will be good to go

Thank you Beeble for your contributions in helping the problem of the OP with me.
Whenever I have some free time, I try to contribute to the car communities. Nice to see others still helping out.

 

I know this is an older thread but wanted to add some clarification in case someone else stumbles on this. The ROM with the shifted data is a SRF (Structured ROM Format) ROM image file. That's like a bin file with a header on the front. The header section contains additional non-ROM image info that can be helpful in decoding the ROM image data. If you open the SRF file in EcuFlash, you can then select the "File->Save As" menu option to save it as a bin, which would then let you do a direct comparison against another ROM image in bin format. When you do a read of an ECU in EcuFlash, you can save it in either SRF or bin format.

-Mike
Tactrix