![]() One way to do this is to load the file in various architectures that seem most likely, then seeing how many functions Ghidra is able to sniff out and how many errors Ghidra mentions in the decompiled C code. Open up the printer and try to guess which chip on the board is the chip we’re flashing.But this hex file is flashing a microcontroller on the main board and we don’t know its architecture. We know the main board in the printer is ARMv5t little endian thanks to flashforge_init.sh. First, since we’re importing a hex file and not a binary, change the Format field to “Intel Hex.” Second is the Language field, which is harder. There are two fields that need to be adjusted. You should be at a screen similar to below: ![]() ![]() Hit File > Import File and select the finder_plus.hex firmware we identified in the previous post. Click on your project directory that was just created in the Ghidra window, then click the green dragon head right above it. Now you’re ready to import a file for disassembly. Go to File > New project > Non-shared project, then give it a project name. Click the New button on the right side of the window and type or paste in the JDK bin path, which would be C:\Program Files\Java\jdk-12.0.1\bin if you installed the 64bit JDK to the default path.Inside of the box that says “User variables for ” select Path, then click the Edit button.Click the best match result, “Edit the system environment variables”.In your Windows search bar type, “path”.By default it will install itself to C:\Programs Files\Java\jdk-12.0.1\ making the bin path C:\Program Files\Java\jdk-12.0.1\bin.Add the Java bin folder to your local user’s PATH environment variable. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |