RomRaider

I've been copying over Evo definitions from Ecuflash for RomRaider (with Colby's permission), but I have a few issues. I can't open any roms because the id for Evos is represented in hex and not the ascii string that the subarus are read in. Ecuflash has a different tag for reading their id, which is <internalidhex> instead of <internalidstring> (tried this, but still didn't work). For example, one of the ids for the evo9 is 0x88590014.

Also, the immobilizer code should be displayed in hex and not the decimal conversion. Anyway to display hex in a table?

Without at least the first fix, I can't test any of the evo defs, so I am kind of stuck at the first definition.

Ooo.. yeah, I can work that in to the next release relatively easily I think. I'll probably have some more questions in the next couple days but it shouldn't be a problem.

Can you put it in a test release? I'm kinda stuck without a way of testing the first definition.

Yeah, I'll try to get it done tomorrow.. I don't think it should take long.

thanks!

Ok, it's looking to be a bit more work than I expected.. or maybe I'm just too tired. I probably won't finish this till wednesday. But I may be wrong.

That's cool. Didn't want to put any pressure on ya! Figured it would be nice to have some Evo definitions ready for the next new release.

Just to clarify, here's a screenshot of the calibration id for the 88590014:

I havent done the revision code yet. I'm thinking this'll be easier than the immobiliser code I'm working on now. The immobiliser code is being pretty frustrating and I didn't get any sleep last night

Edit: It occurs to me the immobiliser code isn't totally necessary. They'll still be able to view and change it (ie, look at theirs and paste it in to the new ROM). I'll keep working on it though..

I wouldn't worry about the immobilizer code for now since they can still read and edit it - just something for the future to be consistent with Ecuflash.

I'll look at it some more.. might as well get it right the first time. Is the rom ID an actual identifier or just a series of bytes that happen to be unique?

They seem to be an identifier as the next revision is 8859 0015, for example.

Location 0x0F50 is the ROM ID. (xxxx)
Location 0x03FFFA is the Hex for ROM ID. (JMxxxx)
Location 0x0F54 is the Revision number. (xxxx)

For all 256kb and 512kb ROM's.

Since RomRaider is currently built to read the String data(ex. "JM8859" ) and not the actual HEX for the identifier you will only get the correct readings for a single revision that matches the original Definitions.

Basically RomRaider needs to read from the HEX itself to determine the revision correctly.
0xF50 = 8859
0xF54 = 0014 (Revision 14)
0xF54 = 0015 (Revision 15)

This can be used in the meantime to open most ROMs. Most tables don't display correctly due to other things you guys are working on currently, but it's a start.

Jared's already fixed that in 3.2b. Just add 0x in front of the id. For example,

<internalidstring>0x88590014</internalidstring>