RomRaider

Can we start a thread or a git repo or something sharing database dumps? There's so much info we all have, but no central place for them. Mine's a mess, but I'd like to sift through and see what I've got and also see what I'm missing.

Most interested in A8dh202x, but I think a database for the databases is a good idea. Certainly gets the ball rolling for others to quickly get going and help find more...

Anybody care to share?

Since an IDA database dump is just plain text it could go into a Git repo. A hierarchy of CAL IDs would need to be created since there's well over 400 if you go by this list.

With the repo people could add their specific changes per CAL ID in their own fork, but the master repo could easily get really messy if no one manages it (just look at the defs repo).
The other thing you may end up seeing is how many people are using a pirated copy of IDA since the dump includes the licencee's name and number which may open them up other issues.

Each CAL ID should have a base dis-assembly and then people work from it rather than creating their own or I imagine the variations in dump results could result it numerous lines of unnecessary diffs in the repo making it difficult to determine what the real change was.
And dis-assemblies should all use a well defined parameter syntax to avoid naming/renaming changes across dumps of parameters and subroutines.

Also some ROMs are very similar so maybe an inheritance scheme could be made so the base that applies to the sibling ROMs all get the same updates.

It's certainly doable but it should be well planned and managed otherwise it's not worth do at all.

Just some thoughts to ponder.

Or we can use the forum, similar to "Stock ROM list" thread ... either way I feel that even if it's not well organized (at the beginning at least) more info is always better than less ... at least for me the definition repo was very very useful ...

This would be amazing to get up and going!

Yes there's certainly a lot to make it clean, but just having them up somewhere even if each user has their own branch could speed up searching and finding routines and values. Cleaning it all up is an entire project in itself, but sharing the basic knowledge takes very little.

As far as the possible pirate aspect, everyone just delete the line out of the file before uploading.

For now a master branch could be comprised of a fresh .IDB with the correct segments and the XMLTOIDC scripts run through??

You can't share database files (IDB). IDA will not open them, specifically the hacked ones.
Additionally it would not look good for the project if we started distributing such hacked versions. Go legit or not at all.

BTW, you are using the wrong processor (SetPrcsr("SH2A")) in your configuration.
SH4B is what you need: SH-2E big endian with float support.
viewtopic.php?t=5825

That was a quick setup I did. I haven't disassebled that rom. That was just to try to get it going. oh well.

Ah, OK.

Here is the most extensive dump that I have.
View with the CAL ID.

Here's my mess.

Any update on this?
Has a repo been made?

I have a repo here, for stuff I've done with my A2WC522N ROM:

https://github.com/LegacyNsfw/EcuHacks

My IDC file is there too.