IDA as is hex-rays? Im not familiar with scoobyrom....
What if you dont have an existing rom? Or wanted to start from scratch? I guess it would all be guess and check? kind of a pita...
I guess the process in making these defs is the same for ecu flash as well...
I ask about ecu flash since in most cases if the def does not work with romraider chances are there is not a def for ecu flash... ANd with that being said I have never tried to flash a car with ecu flash and not have the definitions... Is that even possible? or does one have to make all three? Make the def for logging and the editing (although this could be done in ecu flash but prefer romradier) and then one to flash the car using ecu flash... correct?
edit> i guess i should have posted this in ecu analysis... reading > me
From one MY to the next the maps may be the same or similar but the logic can change and the location of the map data can change quite a bit. Once you have the addresses, writing them to an EcuFlash or RR def is easy. I actually define everything in IDA first, dump the address, from that address list I create a RR Editor def & Logger def. From the RR Editor def I can create the Ecuflash def, all within a few minutes via some scripts I wrote.
If you start here
and skip the bits about loading a ROM in IDA, the rest gives a good overview of how the tables and references to the tables are laid out in the ROM.
ScoobyROM can instantly allow you to visualize the tables in the ROM. But you need IDA to follow the logic to determine if/how a table is used. Most ROMs have both AT & MT tables defined so many will appear to be duplicated. It's all trial and error to figure out which are the correct tables without disassembling the ROM. 1D values, forget it, you won't find them without IDA.
If you don't have IDA there's a basic SH2 dis-assembler here