using ghidra with splat information

[alan-barzilay]

Is there a way to use ghidra with splat? When I tried opening my tony hawk ROM in ghidra i couldnt get much done since it wasnt getting the correct entry point (tonyhawk uses a non standard entry point, I' m assuming this was the problem). But since splat can find the correct entrypoint and correctly map some of the code and .data portions of the binary, i wanted to feed this information back into ghidra.

Is this possible? Am i missing something obvious? I am little new to this universe, so i apologize if this is a stupid question

[blackgamma7]

I have actually been developing a script for Ghidra to do just this - synchronize splat generated symbols with a project's. I need to do some updating on this, but I have a link to the current version here.

[alan-barzilay]

@blackgamma7 cool! thats exactly what I was looking for.

When you mention updating it, is there anything in particular that needs updating for newer releases or should I still be able to use it as is after compiling the java classes? also, is there any documentation on how to use your script? thank you!

[ethteck]

If you want to improve the n64-loading experience in ghidra, I recommend writing in the github repo for whichever n64 rom-loading plugin you're using. I believe you can also manually configure things like this in the Memory Map, but I'm not a ghidra expert

[blackgamma7]

@alan-barzilay Some of the "options" for symbols need updated support - several new ones have been added since I last updated the script. I also need to implement better support for memory overlays. You can run it by putting it in one of ghidra's script directories and searching for it in the script window.

@ethteck I considered this, but also wanted to keep my script as cross-platform as splat's is planned to be by making it independent of the platform-specific loaders.

[ethteck]

Your tools make sense in their own repo as they are imo @blackgamma7. My suggestion above was to @alan-barzilay in regards to the issue of telling ghidra where the entrypoint is.

The original question, as I understood it, was "how can I leverage splat's knowledge of where the entrypoint is to make my ghidra database better". And my answer is that this shouldn't be something that you need splat's help for - ideally the loader can figure that out. But failing that, you can tweak whatever you want in ghidra, so you can just look at the yaml and then adjust the ghidra database manually.

I don't think it would make sense for us to maintain a script that exports splat knowledge back to ghidra. Others (@blackgamma7) are clearly tackling that problem fine enough already :)