]> git.ipfire.org Git - people/ms/u-boot.git/blame - doc/mkimage.1
powerpc: remove rsdproto board support
[people/ms/u-boot.git] / doc / mkimage.1
CommitLineData
cd153556
NI
1.TH MKIMAGE 1 "2010-05-16"
2
3.SH NAME
4mkimage \- Generate image for U-Boot
5.SH SYNOPSIS
6.B mkimage
80e4df8a
SG
7.RB "\-l [" "uimage file name" "]"
8
9.B mkimage
10.RB [\fIoptions\fP] " \-f [" "image tree source file" "]" " [" "uimage file name" "]"
11
95d77b44
SG
12.B mkimage
13.RB [\fIoptions\fP] " \-F [" "uimage file name" "]"
14
80e4df8a
SG
15.B mkimage
16.RB [\fIoptions\fP] " (legacy mode)"
17
cd153556
NI
18.SH "DESCRIPTION"
19The
20.B mkimage
21command is used to create images for use with the U-Boot boot loader.
7aecfdd0 22These images can contain the linux kernel, device tree blob, root file
cd153556
NI
23system image, firmware images etc., either separate or combined.
24
25.B mkimage
26supports two different formats:
27
7aecfdd0 28The old
cd153556
NI
29.I legacy image
30format concatenates the individual parts (for example, kernel image,
31device tree blob and ramdisk image) and adds a 64 bytes header
32containing information about target architecture, operating system,
33image type, compression method, entry points, time stamp, checksums,
34etc.
35
7aecfdd0 36The new
cd153556 37.I FIT (Flattened Image Tree) format
7aecfdd0 38allows for more flexibility in handling images of various types and also
80e4df8a
SG
39enhances integrity protection of images with stronger checksums. It also
40supports verified boot.
cd153556
NI
41
42.SH "OPTIONS"
43
44.B List image information:
45
46.TP
47.BI "\-l [" "uimage file name" "]"
48mkimage lists the information contained in the header of an existing U-Boot image.
49
50.P
51.B Create old legacy image:
52
53.TP
54.BI "\-A [" "architecture" "]"
3f1266d6 55Set architecture. Pass \-h as the architecture to see the list of supported architectures.
cd153556
NI
56
57.TP
58.BI "\-O [" "os" "]"
59Set operating system. bootm command of u-boot changes boot method by os type.
3f1266d6 60Pass \-h as the OS to see the list of supported OS.
cd153556
NI
61
62.TP
63.BI "\-T [" "image type" "]"
64Set image type.
3f1266d6 65Pass \-h as the image to see the list of supported image type.
cd153556
NI
66
67.TP
68.BI "\-C [" "compression type" "]"
69Set compression type.
3f1266d6 70Pass \-h as the compression to see the list of supported compression type.
cd153556
NI
71
72.TP
73.BI "\-a [" "load addess" "]"
74Set load address with a hex number.
75
76.TP
77.BI "\-e [" "entry point" "]"
78Set entry point with a hex number.
79
80e4df8a
SG
80.TP
81.BI "\-l"
82List the contents of an image.
83
cd153556
NI
84.TP
85.BI "\-n [" "image name" "]"
86Set image name to 'image name'.
87
88.TP
89.BI "\-d [" "image data file" "]"
90Use image data from 'image data file'.
91
92.TP
93.BI "\-x"
94Set XIP (execute in place) flag.
95
96.P
97.B Create FIT image:
98
4f610427
SG
99.TP
100.BI "\-c [" "comment" "]"
101Specifies a comment to be added when signing. This is typically a useful
102message which describes how the image was signed or some other useful
103information.
104
cd153556 105.TP
49fbf437 106.BI "\-D [" "dtc options" "]"
cd153556
NI
107Provide special options to the device tree compiler that is used to
108create the image.
109
110.TP
49fbf437 111.BI "\-f [" "image tree source file" "]"
7aecfdd0 112Image tree source file that describes the structure and contents of the
cd153556
NI
113FIT image.
114
95d77b44
SG
115.TP
116.BI "\-F"
117Indicates that an existing FIT image should be modified. No dtc
118compilation is performed and the -f flag should not be given.
119This can be used to sign images with additional keys after initial image
120creation.
121
80e4df8a
SG
122.TP
123.BI "\-k [" "key_directory" "]"
124Specifies the directory containing keys to use for signing. This directory
125should contain a private key file <name>.key for use with signing and a
126certificate <name>.crt (containing the public key) for use with verification.
127
e29495d3
SG
128.TP
129.BI "\-K [" "key_destination" "]"
130Specifies a compiled device tree binary file (typically .dtb) to write
131public key information into. When a private key is used to sign an image,
132the corresponding public key is written into this file for for run-time
133verification. Typically the file here is the device tree binary used by
134CONFIG_OF_CONTROL in U-Boot.
135
399c744b
SG
136.TP
137.BI "\-r
138Specifies that keys used to sign the FIT are required. This means that they
139must be verified for the image to boot. Without this option, the verification
140will be optional (useful for testing but not for release).
141
7aecfdd0 142.SH EXAMPLES
cd153556
NI
143
144List image information:
145.nf
146.B mkimage -l uImage
147.fi
148.P
149Create legacy image with compressed PowerPC Linux kernel:
150.nf
151.B mkimage -A powerpc -O linux -T kernel -C gzip \\\\
152.br
153.B -a 0 -e 0 -n Linux -d vmlinux.gz uImage
154.fi
155.P
156Create FIT image with compressed PowerPC Linux kernel:
157.nf
158.B mkimage -f kernel.its kernel.itb
159.fi
e29495d3
SG
160.P
161Create FIT image with compressed kernel and sign it with keys in the
162/public/signing-keys directory. Add corresponding public keys into u-boot.dtb,
163skipping those for which keys cannot be found. Also add a comment.
164.nf
165.B mkimage -f kernel.its -k /public/signing-keys -K u-boot.dtb \\\\
166-c "Kernel 3.8 image for production devices" kernel.itb
167.fi
cd153556 168
95d77b44
SG
169.P
170Update an existing FIT image, signing it with additional keys.
171Add corresponding public keys into u-boot.dtb. This will resign all images
172with keys that are available in the new directory. Images that request signing
173with unavailable keys are skipped.
174.nf
175.B mkimage -F -k /secret/signing-keys -K u-boot.dtb \\\\
176-c "Kernel 3.8 image for production devices" kernel.itb
177.fi
178
cd153556
NI
179.SH HOMEPAGE
180http://www.denx.de/wiki/U-Boot/WebHome
181.PP
182.SH AUTHOR
183This manual page was written by Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
80e4df8a
SG
184and Wolfgang Denk <wd@denx.de>. It was updated for image signing by
185Simon Glass <sjg@chromium.org>.