summaryrefslogtreecommitdiff
path: root/common/cmd_diag.c
diff options
context:
space:
mode:
authorGuilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com>2013-12-01 12:43:11 -0700
committerTom Rini <trini@ti.com>2013-12-13 09:15:32 -0500
commita804b5ce2d84dca6f9e145003e588876adf2c71f (patch)
tree60342a722b9322a3672e7edd8d4ee260cbf44cf6 /common/cmd_diag.c
parentf86ed6a8d52c99bb2d17d3cac1647edca0c4399c (diff)
downloadu-boot-imx-a804b5ce2d84dca6f9e145003e588876adf2c71f.zip
u-boot-imx-a804b5ce2d84dca6f9e145003e588876adf2c71f.tar.gz
u-boot-imx-a804b5ce2d84dca6f9e145003e588876adf2c71f.tar.bz2
Add dumpimage, a tool to extract data from U-Boot images
Given a multi-file image created through the mkimage's -d option: $ mkimage -A x86 -O linux -T multi -n x86 -d vmlinuz:initrd.img:System.map \ multi.img Image Name: x86 Created: Thu Jul 25 10:29:13 2013 Image Type: Intel x86 Linux Multi-File Image (gzip compressed) Data Size: 13722956 Bytes = 13401.32 kB = 13.09 MB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 4040128 Bytes = 3945.44 kB = 3.85 MB Image 1: 7991719 Bytes = 7804.41 kB = 7.62 MB Image 2: 1691092 Bytes = 1651.46 kB = 1.61 MB It is possible to perform the innverse operation -- extracting any file from the image -- by using the dumpimage's -i option: $ dumpimage -i multi.img -p 2 System.map Although it's feasible to retrieve "data files" from image through scripting, the requirement to embed tools such 'dd', 'awk' and 'sed' for this sole purpose is cumbersome and unreliable -- once you must keep track of file sizes inside the image. Furthermore, extracting data files using "dumpimage" tool is faster than through scripting. Signed-off-by: Guilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com> Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'common/cmd_diag.c')
0 files changed, 0 insertions, 0 deletions