[x] I have reviewed the OFRAK contributor guide and attest that this pull request is in accordance with it.
One sentence summary of this PR (This should go in the CHANGELOG!)
Add a Ghidra script to create a memory map for a binary, mirroring OFRAK's, when Ghidra cannot load the target binary itself.
Link to Related Issue(s)
Ghidra has loaders for some formats, but OFRAK has unpackers for some programs that Ghidra does not (e.g. Uimage). So although OFRAK unpacks these and can find the memory sections, Ghidra cannot analyze any of the code. It would be desirable for future formats as well, once an OFRAK unpacker is written, for them to automatically be supported by Ghidra (as best they can).
Please describe the changes in your request.
Custom Ghidra "loader" that runs as a pre-script, creating memory blocks and marking code blocks
Minor fix to m68k toolchain, some optimization levels led to empty arguments that made the toolchain invocation fail
Anyone you think should look at this, specifically?
One sentence summary of this PR (This should go in the CHANGELOG!) Add a Ghidra script to create a memory map for a binary, mirroring OFRAK's, when Ghidra cannot load the target binary itself.
Link to Related Issue(s) Ghidra has loaders for some formats, but OFRAK has unpackers for some programs that Ghidra does not (e.g. Uimage). So although OFRAK unpacks these and can find the memory sections, Ghidra cannot analyze any of the code. It would be desirable for future formats as well, once an OFRAK unpacker is written, for them to automatically be supported by Ghidra (as best they can).
Please describe the changes in your request.
Anyone you think should look at this, specifically?