Default ghidra doesn't handle firmware very well, as they're not formed like regular elf files and can't find the entrypoints or data maps without help. Can we feed AST data obtained from other tools to ghidra to ID entrypoint candidates, and try to align them and return the one that is "best fit"?
Expected behavior:
- In: Text or JSON list of start address candidates
- Out: Return a JSON? of candidates ranked on likelihood/number of functions found and ask user which one to use
Default ghidra doesn't handle firmware very well, as they're not formed like regular
elffiles and can't find the entrypoints or data maps without help. Can we feed AST data obtained from other tools to ghidra to ID entrypoint candidates, and try to align them and return the one that is "best fit"?Expected behavior: