RomRaider

Ok, there is not so much info on this, and ECU Analysis seems to be the right place to start discussion about flashing foreign ROM files to ECUs
1st, thanks to merchgod we have such big list of supported ECUs, that this post may never appear
2nd, I've read this: http://www.scoobypedia.co.uk/index.php/ ... bilityList
and this:

And I'm asking about compatibility for educational purposes rather than practical use. However, there are few older ECUs remain uncovered. Mostly N/A. and it's obviously easier to flash compatible ROM than to do full disassembly. I know flashing other ROMs that's what ecutek occasionally does (and what PGMFI guys always do)
What we know? There are:
- ROM IDs that absolutely interchangable (same model year same model revisions)
- ROM IDs that absolutely NOT interchangable (32bit / 16-bit; 6-cyl / 4 cyl, Turbo / N/A and other combinations looking weird)
- something in the middle something that may work.

So, looking at "something in the middle". How 'bout flashing Impreza 2.5i ROM on same year/transmission non-CAN Forester 2.5X? Or flashing USDM ROM on EDM car (yeah, we've learned there are some minor emission-related issues with similar ECU swap) ?

If the NA model is not the 32-bit ECU (ex. USDM 04 and prior RS with is JECS), then you cannot read/flash with Ecuflash anyway.

As far as for experimental purposes, you should be able to flash any ROM that uses the same flash method as the ECU you are attempting to flash it to (flash methods are: wrx02, wrx04, sti04, sti05, subarucan). However, if you are not sure, then I wouldn't attempt it.

Oh, I wanted to say older than current CANbus ECUs, 32-bit
Flashing other ROM, that's something I wouldn't do without reason. The last "undefined" car I'd like to flash was EDM Legacy 3.0R, which became supported faster than I posted def.request

If you want to explore flashing 32-bit ECUs with non-supported ROMs, then you should first build the SH Boot Mode reflashing device described at http://openecu.org/index.php?title=SHBootMode. This will allow you to experiment without fear that your 32-bit ECU will become useless. Let us know which combinations work and which don't.

I'm waiting my OP2.0, then I'll probably convert 1.3 to SHBootmode adapter.

Recently I had a talk with Evo (ecutek'd) owner. He said, at time of reflash, year ago or so, e-tek tuners were unable to work with evo9 (MIVEC) ROM, and his tuner simply flashed evo8 ROM, which forced Intake Cam to stay advanced (yes, he said advanced - I'm not too familar with evo, maybe that's the way MiVEC works). I just wondered that defective tune

If the flash method is the same, you shouldn't have any problem with "bricking" your ECU. The car might not start, you might get a bunch of CELs, but you should be able to flash back to the original map without issue. Of course, there are no guarantees, but this should be the case.

USDM and ADM ROM's will flash on EDM equivalent year ECU's, you get a couple of CEL's that can be fixed via RR no probs. I haven't tried SADM ROM's but i imagine they will work the same way.

The odd one out seems to be JDM ROM's. They flash over no probs, the car will start and drive but you cannot get rid of the very fast flashing dashboard CEL's even if you fix them in RR. They just won't go away. These ROM's seem to have other stuff on them that all the other ROM's don't have so i imagine thats the issue.

I'm no ROM hacker so i really don't know what the tech differences are but I know both of the above to be true as i have flashed both USDM, ADM and JDM ROM's to my old 16-bit EDM 02 WRX ECU and the EDM 02 STi ECU i currently use.

HTH

thx for the input.