ECUFlash can't read ECU
 

So I'm helping a friend build up their 2008 Evo X MR that is a Canadian model as far as I know and attempted to read the ECU into ECUFlash so that I can start prepping for a few upgrades such as a bigger turbo and 1000cc injectors.

ECUFlash 1.42.2595 and 1.43.3150 both fail to read the ROM just as it starts to access the kernel. You hear a "click, click, click" and then it errors out right away.

I'm chosing 2006+ CAN vehicles and something just doesn't seem right trying to connect to this 2008 Evo X MR. Last I knew it was tuned by AMS in the spring of 2010 for last years One Lap, then a tuner up in Canada played with a tune on it and as far as I know they flashed back to the AMS tune before the car got transported to the States. I'm wondering if somehow it got bricked partially and now the ECU is hosed in some way.

The car runs fine and I can clear the catylist efficiency code with PCMScan as well as run EvoScan v2.8 for datalogging without any issues. I don't even know what ROM version this ECU is supposed to have but "Read from ECU" and "Test Write to ECU" both result in an error so I'm at a loss what the problem is here.

ECUFlash works great on my own car and I thought if it couldn't find correct ROM definitions it would still read the ROM just have no tables defiined.

[13:50:17.076] EcuFlash Version 1.42.2595
[13:50:17.076] OS Version Windows Vista
[13:50:17.076] Qt Version 4.5.0
[13:50:17.076] 56 memory models read.
[13:50:17.076] scanning for metadata models in C:/Users/CWirth/Desktop/Evo/ECUFlash 142/EcuFlash/rommetadata
[13:50:17.263] 346 ROM metadata models scanned.
[13:50:17.263] checksum module "subarudbw" loaded.
[13:50:17.263] checksum module "mitsucan" loaded.
[13:50:17.263] flashing tool "wrx02" loaded.
[13:50:17.263] flashing tool "wrx04" loaded.
[13:50:17.263] flashing tool "sti04" loaded.
[13:50:17.263] flashing tool "sti05" loaded.
[13:50:17.263] flashing tool "mitsukernel" loaded.
[13:50:17.263] flashing tool "mitsukernelocp" loaded.
[13:50:17.263] flashing tool "mitsubootloader" loaded.
[13:50:17.263] flashing tool "shbootmode" loaded.
[13:50:17.263] flashing tool "shaudmode" loaded.
[13:50:17.263] flashing tool "subarucan" loaded.
[13:50:17.263] flashing tool "mitsucan" loaded.
[13:50:34.404] J2534 API Version: 04.04
[13:50:34.404] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[13:50:34.404] Device Firmware Version: 1.07.2597
[13:50:50.193] -- loading kernel --
[13:50:50.193] -- connecting to kernel --
[13:50:50.193] kernel get version (audible click click click)
[13:50:51.020] interface close
[13:50:51.051] interface close

Ran into a similar problem and found out that the ECU was flashed with a corrupted ROM file. The vehicle ran fine but couldn't read or reflash the ROM. Had to bench it to the stock ROM and then it was fine.

That is what I'm suspecting at this point, of course I don't even know if anyone still has the stock ROM available. I'll have to find out all the details of who was flashing the car for him while in Canada and if they have the original ROM. Worst case I'm hoping AMS still has his ROM on file so that I can get it restored. I guess I need too look at what is involved with benching the ECU, just what I wanted to do this week. LOL.

We have a bench here so if you want to send it to us we can probably repair it.

Let me know if that would help.

Mitch

I probably have a stock rom for you, if you know the year, make and model of the car.

Ok, if my attempt at benching it fails I'll use that as a backup plan. Can you ask Chris or Martin if they might have Paul Seto's original ROM file on hand somewhere?

I was able to get a previous ROM of the car that had some basic mods to account for his intake which is a start. His original ROM was corrupt when I tried to open it though, possibly it got nailed while traveling the internets so they are trying to send me the file again in zipped format from the original source.

It's a 2008 Mitsubishi Evo X MR with internal ID 52690019 that inherits 52680015 based on the ROM that does work (USDM, 6MT, 2008).

So even if you replace the ROM with a base ROM what is the deal with the whole immobilizer thing? What would need to be done to get it to start? Does it need a dealership to re-sync the combo?

You can flash any rom with the same first 4 digits to the car. So a 5269xxxx rom will work for that one.

You can even grab Tephra Mods for it.

Interesting!

52690021 inherits 52680015 original ROM
52690019 inherits 52680015 Injen Intake ROM

Looks like the original ROM wasn't corrupt, I just didn't double check after my laptop crash that the XML's were there for a bunch of the ROMS I don't frequent as often. Is there any compelling reason that the recent ECUFlash releases still don't have a bunch of the known ROM definitions included with the base install? It would be nice if there was an updated XML definition package that we can just drop into place with all the Mode23, Maf compensation, Upper bound timing tables etc etc all fixed up and ready to go for all the known ROMS.

I still can't write it but made the wiring harness and will bench it after work tonight so we'll see.

Well first off, I don't like that 52690021 inherits 52680015 in most definition files, as this confuses people. Yes they are nearly identical in their lay out, but not exactly.

That is why my definition files don't inherit anything. It makes them straight forward and simple.

BTW: You can download new definitions at my site goldenevo.com if you want.

I'll check it out and download for sure!

Benching the ECU ended up recovering it 100% as far as I can tell, just took some extra muscle since the Canadian ECU had one of those tamper proof covers on it. Ended up taking a die grinder to the bolts which caused a bit of a cleanup mess. Then I had to fiddle with the connectors I made to get them to fit properly since there are different sized pins on the ECU and Tactrix cable.

Thanks for the help guys. :cool: