openecu.org

I want to use ecuflash to edit ROM's for my 1g DSM. I was wondering how I begin making a custom definition for my from. I know most of the addresses of my maps, I just don't know how to get started.

thanks,
dan

The best advice I can give is to follow by example. Most of it can be worked out by looking at the XML files supplied with ECUFlash or ROMRaider.

radsdau wrote:The best advice I can give is to follow by example. Most of it can be worked out by looking at the XML files supplied with ECUFlash or ROMRaider.

I do not think it is possible, because ECUflash does not support memory model of MH6111 MCU. You will have to stay with Tunerpro.

You won't be using ECUFlash for the reflashing, only the ROM editing. You can write your own definitions to tune ANY ROM type, so long as you work out where the maps are and what format they're in, etc. It doesn't matter what micro or memory model the ROM uses.

You won't be using ECUFlash for the reflashing, only the ROM editing. You can write your own definitions to tune ANY ROM type, so long as you work out where the maps are and what format they're in, etc. It doesn't matter what micro or memory model the ROM uses.

I dunno about that. As xor said, EcuFlash doesn't support the MH61xx MCU.

EcuFlash requires you to be able to specify the location of the map, AND the location of the axes in the ROM.

The DSMs don't have the axes stored in the ROM. They're calculated and/or implied. They're not explicitly stated like other Mitsu models...

Gatecrasher wrote:I dunno about that. As xor said, EcuFlash doesn't support the MH61xx MCU.

EcuFlash requires you to be able to specify the location of the map, AND the location of the axes in the ROM.

The DSMs don't have the axes stored in the ROM. They're calculated and/or implied. They're not explicitly stated like other Mitsu models...

The requirement of ECUFlash to 'support a particular processor' is only for reflashing, and that's a very specific subset of MCUs in particular ECUs.
For ROM editing, it just considers files as a bunch of numbers, so as long as you can find the memory locations of the data you want to change, it can edit that ROM.
If the axes don't exist in explicit form in the ROM, then there are ways of making them up so they display correctly in the map editing window. I can't recall how this is done; follow by example again.

I have not seen such an example for falsifying axes on things like fuel maps.

On the other hand, Tuner Pro RT truely does not care about MCUs or anything else, and has some very easy to use menus for specifying data that does not exist in the ROM. The DSM guys on the DSM-ECU group on Yahoo also have extensive experience with it.

Honesty, after trying to use ECUFlash to map out some non-flashable 3000GT ROM files, I'm convinced that there's better tools for the job. ECUFlash is good for what it does, but for the stuff it wasn't meant to do, there are better alternatives in my opinion.