diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/mkimage.1 | 42 | ||||
| -rw-r--r-- | doc/uImage.FIT/source_file_format.txt | 20 |
2 files changed, 58 insertions, 4 deletions
diff --git a/doc/mkimage.1 b/doc/mkimage.1 index b48f70bb3c..e0f210ab52 100644 --- a/doc/mkimage.1 +++ b/doc/mkimage.1 @@ -97,6 +97,10 @@ Set XIP (execute in place) flag. .B Create FIT image: .TP +.BI "\-b +Specifies that the following arguments are device tree binary files (.dtb). + +.TP .BI "\-c [" "comment" "]" Specifies a comment to be added when signing. This is typically a useful message which describes how the image was signed or some other useful @@ -108,10 +112,24 @@ Provide special options to the device tree compiler that is used to create the image. .TP -.BI "\-f [" "image tree source file" "]" +.BI "\-E +After processing, move the image data outside the FIT and store a data offset +in the FIT. Images will be placed one after the other immediately after the +FIT, with each one aligned to a 4-byte boundary. The existing 'data' property +in each image will be replaced with 'data-offset' and 'data-size' properties. +A 'data-offset' of 0 indicates that it starts in the first (4-byte aligned) +byte after the FIT. + +.TP +.BI "\-f [" "image tree source file" " | " "auto" "]" Image tree source file that describes the structure and contents of the FIT image. +This can be automatically generated for some simple cases. +Use "-f auto" for this. In that case the arguments -d, -A, -O, -T, -C, -a +and -e are used to specify the image to include in the FIT and its attributes. +No .its file is required. + .TP .BI "\-F" Indicates that an existing FIT image should be modified. No dtc @@ -164,7 +182,7 @@ skipping those for which keys cannot be found. Also add a comment. .nf .B mkimage -f kernel.its -k /public/signing-keys -K u-boot.dtb \\\\ .br -.B -c "Kernel 3.8 image for production devices" kernel.itb +.B -c """Kernel 3.8 image for production devices""" kernel.itb .fi .P @@ -175,7 +193,25 @@ with unavailable keys are skipped. .nf .B mkimage -F -k /secret/signing-keys -K u-boot.dtb \\\\ .br -.B -c "Kernel 3.8 image for production devices" kernel.itb +.B -c """Kernel 3.8 image for production devices""" kernel.itb +.fi + +.P +Create a FIT image containing a kernel, using automatic mode. No .its file +is required. +.nf +.B mkimage -f auto -A arm -O linux -T kernel -C none -a 43e00000 -e 0 \\\\ +.br +.B -c """Kernel 4.4 image for production devices""" -d vmlinuz kernel.itb +.fi +.P +Create a FIT image containing a kernel and some device tree files, using +automatic mode. No .its file is required. +.nf +.B mkimage -f auto -A arm -O linux -T kernel -C none -a 43e00000 -e 0 \\\\ +.br +.B -c """Kernel 4.4 image for production devices""" -d vmlinuz \\\\ +.B -b /path/to/rk3288-firefly.dtb /path/to/rk3288-jerry.dtb kernel.itb .fi .SH HOMEPAGE diff --git a/doc/uImage.FIT/source_file_format.txt b/doc/uImage.FIT/source_file_format.txt index 3175c9f0b7..3db068d6c8 100644 --- a/doc/uImage.FIT/source_file_format.txt +++ b/doc/uImage.FIT/source_file_format.txt @@ -2,6 +2,7 @@ U-Boot new uImage source file format (bindings definition) ========================================================== Author: Marian Balakowicz <m8@semihalf.com> +External data additions, 25/1/16 Simon Glass <sjg@chromium.org> 1) Introduction --------------- @@ -262,7 +263,24 @@ Older, 2.4 kernel and 2.6 non-FDT kernel do not use FDT blob, in such cases not* be specified in a configuration node. -8) Examples +8) External data +---------------- + +The above format shows a 'data' property which holds the data for each image. +It is also possible for this data to reside outside the FIT itself. This +allows the FIT to be quite small, so that it can be loaded and scanned +without loading a large amount of data. Then when an image is needed it can +be loaded from an external source. + +In this case the 'data' property is omitted. Instead you can use: + + - data-offset : offset of the data in a separate image store. The image + store is placed immediately after the last byte of the device tree binary, + aligned to a 4-byte boundary. + - data-size : size of the data in bytes + + +9) Examples ----------- Please see doc/uImage.FIT/*.its for actual image source files. |
