| commit | 906963ae7667ae06951e12c0f02032184a4e23fd | |
| author | Amaury Pouly <amaury.pouly@gmail.com> | |
| Tue, 19 Jun 2012 20:52:18 +0000 (19 22:52 +0200) | ||
| committer | Amaury Pouly <amaury.pouly@gmail.com> | |
| Tue, 19 Jun 2012 20:54:41 +0000 (19 22:54 +0200) | ||
| tree | 105b9ded4736810f9d62512f7f966abf6ba91799 | treesnapshot (tar.gz zip) |
| parent | 715111122837440d3a1463d0d6932c469418dcbb | commitdiff |
rknanoutils: much more sensible format guess
I finally found a sensible format for the executable files.
The tool now can output the loading entry to elf files. Some
disassembly and analysis suggest the phys/virt addresses are
correct. However the entries are somehow linked and it is
still unclear how (are there "calls" to the code ? when ?).
Change-Id: Ied38b5bb297176c5755b5ecb3309f4a259c18cd4
I finally found a sensible format for the executable files.
The tool now can output the loading entry to elf files. Some
disassembly and analysis suggest the phys/virt addresses are
correct. However the entries are somehow linked and it is
still unclear how (are there "calls" to the code ? when ?).
Change-Id: Ied38b5bb297176c5755b5ecb3309f4a259c18cd4