-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support uImage format and/or manual arch specification #3
Comments
Hello, Kudos for your work on IDA too. I can see multiple things that I could improve from your post:
In the end, it is possible that the best would be to add generic flags for information that are not 100 % sure to be inferred exactly by the tool ( I should get back at this soon. Other ideas are welcome. Regards, |
…certain input parameters (per issue #3)
…ertain OpenWRT settings (from the sample in issue #3)
Hello, For your information, your kernel now reconstructs well without extra arguments. Also, I have added support for the extra arguments that I have mentioned in the previous message. These have been documented in the Regards, |
Thanks! FYI found an example of a compressed uImage which seeems to be not handled out-of-box: openwrt-18.06.4-lantiq-falcon-lantiq_easy98000-nand-squashfs-sysupgrade.bin However no symbols found even after manual decompression :( Making an ELF with just code section may be useful although without .bss the analysis will not be too great... |
First, congrats on the awesome tool.
I decided to try it out and went to the OpenWRT release archive. The first one alphabetically was ARC and it failed:
In fact, the uImage header already includes the architecture, load address and even entrypoint:
openwrt-18.06.4-arc770-generic-uImage: u-boot legacy uImage, ARC OpenWrt Linux-4.9.184, Linux/DesignWare ARC, OS Kernel Image (Not compressed), 4522192 bytes, Thu Jun 27 12:18:52 2019, Load Address: 0x80000000, Entry Point: 0x8000A000, Header CRC: 0xA11EF4A4, Data CRC: 0xAC4BE39B
Additionally, there is no need to know the architecture if not writing out the ELF file (e.g. when just dumping symbols), so this step could be skipped until required. You could also let user specify it manually or just write 0 to e_machine.
Note: uImage format may employ its own compression (seen at least gzip used).
The text was updated successfully, but these errors were encountered: