1 .. SPDX-License-Identifier: GPL-2.0+
2 .. Copyright (c) 2016 Google, Inc
7 Firmware often consists of several components which must be packaged together.
8 For example, we may have SPL, U-Boot, a device tree and an environment area
9 grouped together and placed in MMC flash. When the system starts, it must be
10 able to find these pieces.
12 So far U-Boot has not provided a way to handle creating such images in a
13 general way. Each SoC does what it needs to build an image, often packing or
14 concatenating images in the U-Boot build system.
16 Binman aims to provide a mechanism for building images, from simple
17 SPL + U-Boot combinations, to more complex arrangements with many parts.
23 Binman reads your board's device tree and finds a node which describes the
24 required image layout. It uses this to work out what to place where. The
25 output file normally contains the device tree, so it is in principle possible
26 to read an image and extract its constituent parts.
32 So far binman is pretty simple. It supports binary blobs, such as 'u-boot',
33 'spl' and 'fdt'. It supports empty entries (such as setting to 0xff). It can
34 place entries at a fixed location in the image, or fit them together with
35 suitable padding and alignment. It provides a way to process binaries before
36 they are included, by adding a Python plug-in. The device tree is available
37 to U-Boot at run-time so that the images can be interpreted.
39 Binman can update the device tree with the final location of everything when it
40 is done. Entry positions can be provided to U-Boot SPL as run-time symbols,
41 avoiding device-tree code overhead.
43 Binman can also support incorporating filesystems in the image if required.
44 For example x86 platforms may use CBFS in some cases.
46 Binman is intended for use with U-Boot but is designed to be general enough
47 to be useful in other image-packaging situations.
53 Packaging of firmware is quite a different task from building the various
54 parts. In many cases the various binaries which go into the image come from
55 separate build systems. For example, ARM Trusted Firmware is used on ARMv8
56 devices but is not built in the U-Boot tree. If a Linux kernel is included
57 in the firmware image, it is built elsewhere.
59 It is of course possible to add more and more build rules to the U-Boot
60 build system to cover these cases. It can shell out to other Makefiles and
61 build scripts. But it seems better to create a clear divide between building
62 software and packaging it.
64 At present this is handled by manual instructions, different for each board,
65 on how to create images that will boot. By turning these instructions into a
66 standard format, we can support making valid images for any board without
67 manual effort, lots of READMEs, etc.
71 - Each binary can have its own build system and tool chain without creating
72 any dependencies between them
73 - Avoids the need for a single-shot build: individual parts can be updated
74 and brought in as needed
75 - Provides for a standard image description available in the build and at
77 - SoC-specific image-signing tools can be accommodated
78 - Avoids cluttering the U-Boot build system with image-building code
79 - The image description is automatically available at run-time in U-Boot,
80 SPL. It can be made available to other software also
81 - The image description is easily readable (it's a text file in device-tree
82 format) and permits flexible packing of binaries
88 Binman uses the following terms:
90 - image - an output file containing a firmware image
91 - binary - an input binary that goes into the image
97 FIT is U-Boot's official image format. It supports multiple binaries with
98 load / execution addresses, compression. It also supports verification
99 through hashing and RSA signatures.
101 FIT was originally designed to support booting a Linux kernel (with an
102 optional ramdisk) and device tree chosen from various options in the FIT.
103 Now that U-Boot supports configuration via device tree, it is possible to
104 load U-Boot from a FIT, with the device tree chosen by SPL.
106 Binman considers FIT to be one of the binaries it can place in the image.
108 Where possible it is best to put as much as possible in the FIT, with binman
109 used to deal with cases not covered by FIT. Examples include initial
110 execution (since FIT itself does not have an executable header) and dealing
111 with device boundaries, such as the read-only/read-write separation in SPI
114 For U-Boot, binman should not be used to create ad-hoc images in place of
118 Relationship to mkimage
119 -----------------------
121 The mkimage tool provides a means to create a FIT. Traditionally it has
122 needed an image description file: a device tree, like binman, but in a
123 different format. More recently it has started to support a '-f auto' mode
124 which can generate that automatically.
126 More relevant to binman, mkimage also permits creation of many SoC-specific
127 image types. These can be listed by running 'mkimage -T list'. Examples
128 include 'rksd', the Rockchip SD/MMC boot format. The mkimage tool is often
129 called from the U-Boot build system for this reason.
131 Binman considers the output files created by mkimage to be binary blobs
132 which it can place in an image. Binman does not replace the mkimage tool or
133 this purpose. It would be possible in some situations to create a new entry
134 type for the images in mkimage, but this would not add functionality. It
135 seems better to use the mkimage tool to generate binaries and avoid blurring
136 the boundaries between building input files (mkimage) and packaging then
137 into a final image (binman).
143 Example use of binman in U-Boot
144 -------------------------------
146 Binman aims to replace some of the ad-hoc image creation in the U-Boot
149 Consider sunxi. It has the following steps:
151 #. It uses a custom mksunxiboot tool to build an SPL image called
152 sunxi-spl.bin. This should probably move into mkimage.
154 #. It uses mkimage to package U-Boot into a legacy image file (so that it can
155 hold the load and execution address) called u-boot.img.
157 #. It builds a final output image called u-boot-sunxi-with-spl.bin which
158 consists of sunxi-spl.bin, some padding and u-boot.img.
160 Binman is intended to replace the last step. The U-Boot build system builds
161 u-boot.bin and sunxi-spl.bin. Binman can then take over creation of
162 sunxi-spl.bin (by calling mksunxiboot, or hopefully one day mkimage). In any
163 case, it would then create the image from the component parts.
165 This simplifies the U-Boot Makefile somewhat, since various pieces of logic
166 can be replaced by a call to binman.
169 Example use of binman for x86
170 -----------------------------
172 In most cases x86 images have a lot of binary blobs, 'black-box' code
173 provided by Intel which must be run for the platform to work. Typically
174 these blobs are not relocatable and must be placed at fixed areas in the
177 Currently this is handled by ifdtool, which places microcode, FSP, MRC, VGA
178 BIOS, reference code and Intel ME binaries into a u-boot.rom file.
180 Binman is intended to replace all of this, with ifdtool left to handle only
181 the configuration of the Intel-format descriptor.
187 First install prerequisites, e.g::
189 sudo apt-get install python-pyelftools python3-pyelftools lzma-alone \
194 binman build -b <board_name>
196 to build an image for a board. The board name is the same name used when
197 configuring U-Boot (e.g. for sandbox_defconfig the board name is 'sandbox').
198 Binman assumes that the input files for the build are in ../b/<board_name>.
200 Or you can specify this explicitly::
202 binman build -I <build_path>
204 where <build_path> is the build directory containing the output of the U-Boot
207 (Future work will make this more configurable)
209 In either case, binman picks up the device tree file (u-boot.dtb) and looks
210 for its instructions in the 'binman' node.
212 Binman has a few other options which you can see by running 'binman -h'.
215 Enabling binman for a board
216 ---------------------------
218 At present binman is invoked from a rule in the main Makefile. Typically you
219 will have a rule like::
221 ifneq ($(CONFIG_ARCH_<something>),)
222 u-boot-<your_suffix>.bin: <input_file_1> <input_file_2> checkbinman FORCE
223 $(call if_changed,binman)
226 This assumes that u-boot-<your_suffix>.bin is a target, and is the final file
227 that you need to produce. You can make it a target by adding it to INPUTS-y
228 either in the main Makefile or in a config.mk file in your arch subdirectory.
230 Once binman is executed it will pick up its instructions from a device-tree
231 file, typically <soc>-u-boot.dtsi, where <soc> is your CONFIG_SYS_SOC value.
232 You can use other, more specific CONFIG options - see 'Automatic .dtsi
236 Access to binman entry offsets at run time (symbols)
237 ----------------------------------------------------
239 Binman assembles images and determines where each entry is placed in the image.
240 This information may be useful to U-Boot at run time. For example, in SPL it
241 is useful to be able to find the location of U-Boot so that it can be executed
242 when SPL is finished.
244 Binman allows you to declare symbols in the SPL image which are filled in
245 with their correct values during the build. For example::
247 binman_sym_declare(ulong, u_boot_any, image_pos);
249 declares a ulong value which will be assigned to the image-pos of any U-Boot
250 image (u-boot.bin, u-boot.img, u-boot-nodtb.bin) that is present in the image.
251 You can access this value with something like::
253 ulong u_boot_offset = binman_sym(ulong, u_boot_any, image_pos);
255 Thus u_boot_offset will be set to the image-pos of U-Boot in memory, assuming
256 that the whole image has been loaded, or is available in flash. You can then
257 jump to that address to start U-Boot.
259 At present this feature is only supported in SPL and TPL. In principle it is
260 possible to fill in such symbols in U-Boot proper, as well, but a future C
261 library is planned for this instead, to read from the device tree.
263 As well as image-pos, it is possible to read the size of an entry and its
264 offset (which is the start position of the entry within its parent).
266 A small technical note: Binman automatically adds the base address of the image
267 (i.e. __image_copy_start) to the value of the image-pos symbol, so that when the
268 image is loaded to its linked address, the value will be correct and actually
269 point into the image.
271 For example, say SPL is at the start of the image and linked to start at address
272 80108000. If U-Boot's image-pos is 0x8000 then binman will write an image-pos
273 for U-Boot of 80110000 into the SPL binary, since it assumes the image is loaded
274 to 80108000, with SPL at 80108000 and U-Boot at 80110000.
276 For x86 devices (with the end-at-4gb property) this base address is not added
277 since it is assumed that images are XIP and the offsets already include the
281 Access to binman entry offsets at run time (fdt)
282 ------------------------------------------------
284 Binman can update the U-Boot FDT to include the final position and size of
285 each entry in the images it processes. The option to enable this is -u and it
286 causes binman to make sure that the 'offset', 'image-pos' and 'size' properties
287 are set correctly for every entry. Since it is not necessary to specify these in
288 the image definition, binman calculates the final values and writes these to
289 the device tree. These can be used by U-Boot at run-time to find the location
292 Alternatively, an FDT map entry can be used to add a special FDT containing
293 just the information about the image. This is preceded by a magic string so can
294 be located anywhere in the image. An image header (typically at the start or end
295 of the image) can be used to point to the FDT map. See fdtmap and image-header
296 entries for more information.
302 The -m option causes binman to output a .map file for each image that it
303 generates. This shows the offset and size of each entry. For example::
306 00000000 00000028 main-section
307 00000000 00000010 section@0
308 00000000 00000004 u-boot
309 00000010 00000010 section@1
310 00000000 00000004 u-boot
312 This shows a hierarchical image with two sections, each with a single entry. The
313 offsets of the sections are absolute hex byte offsets within the image. The
314 offsets of the entries are relative to their respective sections. The size of
315 each entry is also shown, in bytes (hex). The indentation shows the entries
316 nested inside their sections.
319 Passing command-line arguments to entries
320 -----------------------------------------
322 Sometimes it is useful to pass binman the value of an entry property from the
323 command line. For example some entries need access to files and it is not
324 always convenient to put these filenames in the image definition (device tree).
326 The-a option supports this::
332 <prop> is the property to set
333 <value> is the value to set it to
335 Not all properties can be provided this way. Only some entries support it,
336 typically for filenames.
339 Image description format
340 ========================
342 The binman node is called 'binman'. An example image description is shown
346 filename = "u-boot-sunxi-with-spl.bin";
349 filename = "spl/sunxi-spl.bin";
352 offset = <CONFIG_SPL_PAD_TO>;
357 This requests binman to create an image file called u-boot-sunxi-with-spl.bin
358 consisting of a specially formatted SPL (spl/sunxi-spl.bin, built by the
359 normal U-Boot Makefile), some 0xff padding, and a U-Boot legacy image. The
360 padding comes from the fact that the second binary is placed at
361 CONFIG_SPL_PAD_TO. If that line were omitted then the U-Boot binary would
362 immediately follow the SPL binary.
364 The binman node describes an image. The sub-nodes describe entries in the
365 image. Each entry represents a region within the overall image. The name of
366 the entry (blob, u-boot) tells binman what to put there. For 'blob' we must
367 provide a filename. For 'u-boot', binman knows that this means 'u-boot.bin'.
369 Entries are normally placed into the image sequentially, one after the other.
370 The image size is the total size of all entries. As you can see, you can
371 specify the start offset of an entry using the 'offset' property.
373 Note that due to a device tree requirement, all entries must have a unique
374 name. If you want to put the same binary in the image multiple times, you can
375 use any unique name, with the 'type' property providing the type.
377 The attributes supported for entries are described below.
380 This sets the offset of an entry within the image or section containing
381 it. The first byte of the image is normally at offset 0. If 'offset' is
382 not provided, binman sets it to the end of the previous region, or the
383 start of the image's entry area (normally 0) if there is no previous
387 This sets the alignment of the entry. The entry offset is adjusted
388 so that the entry starts on an aligned boundary within the containing
389 section or image. For example 'align = <16>' means that the entry will
390 start on a 16-byte boundary. This may mean that padding is added before
391 the entry. The padding is part of the containing section but is not
392 included in the entry, meaning that an empty space may be created before
393 the entry starts. Alignment should be a power of 2. If 'align' is not
394 provided, no alignment is performed.
397 This sets the size of the entry. The contents will be padded out to
398 this size. If this is not provided, it will be set to the size of the
402 Padding before the contents of the entry. Normally this is 0, meaning
403 that the contents start at the beginning of the entry. This can be used
404 to offset the entry contents a little. While this does not affect the
405 contents of the entry within binman itself (the padding is performed
406 only when its parent section is assembled), the end result will be that
407 the entry starts with the padding bytes, so may grow. Defaults to 0.
410 Padding after the contents of the entry. Normally this is 0, meaning
411 that the entry ends at the last byte of content (unless adjusted by
412 other properties). This allows room to be created in the image for
413 this entry to expand later. While this does not affect the contents of
414 the entry within binman itself (the padding is performed only when its
415 parent section is assembled), the end result will be that the entry ends
416 with the padding bytes, so may grow. Defaults to 0.
419 This sets the alignment of the entry size. For example, to ensure
420 that the size of an entry is a multiple of 64 bytes, set this to 64.
421 While this does not affect the contents of the entry within binman
422 itself (the padding is performed only when its parent section is
423 assembled), the end result is that the entry ends with the padding
424 bytes, so may grow. If 'align-size' is not provided, no alignment is
428 This sets the alignment of the end of an entry with respect to the
429 containing section. Some entries require that they end on an alignment
430 boundary, regardless of where they start. This does not move the start
431 of the entry, so the contents of the entry will still start at the
432 beginning. But there may be padding at the end. While this does not
433 affect the contents of the entry within binman itself (the padding is
434 performed only when its parent section is assembled), the end result
435 is that the entry ends with the padding bytes, so may grow.
436 If 'align-end' is not provided, no alignment is performed.
439 For 'blob' types this provides the filename containing the binary to
440 put into the entry. If binman knows about the entry type (like
441 u-boot-bin), then there is no need to specify this.
444 Sets the type of an entry. This defaults to the entry name, but it is
445 possible to use any name, and then add (for example) 'type = "u-boot"'
449 Indicates that the offset of this entry should not be set by placing
450 it immediately after the entry before. Instead, is set by another
451 entry which knows where this entry should go. When this boolean
452 property is present, binman will give an error if another entry does
453 not set the offset (with the GetOffsets() method).
456 This cannot be set on entry (or at least it is ignored if it is), but
457 with the -u option, binman will set it to the absolute image position
458 for each entry. This makes it easy to find out exactly where the entry
459 ended up in the image, regardless of parent sections, etc.
462 Expand the size of this entry to fit available space. This space is only
463 limited by the size of the image/section and the position of the next
467 Sets the compression algortihm to use (for blobs only). See the entry
468 documentation for details.
471 Sets the tag of the message to show if this entry is missing. This is
472 used for external blobs. When they are missing it is helpful to show
473 information about what needs to be fixed. See missing-blob-help for the
474 message for each tag.
476 The attributes supported for images and sections are described below. Several
477 are similar to those for entries.
480 Sets the image size in bytes, for example 'size = <0x100000>' for a
484 This is similar to 'offset' in entries, setting the offset of a section
485 within the image or section containing it. The first byte of the section
486 is normally at offset 0. If 'offset' is not provided, binman sets it to
487 the end of the previous region, or the start of the image's entry area
488 (normally 0) if there is no previous region.
491 This sets the alignment of the image size. For example, to ensure
492 that the image ends on a 512-byte boundary, use 'align-size = <512>'.
493 If 'align-size' is not provided, no alignment is performed.
496 This sets the padding before the image entries. The first entry will
497 be positioned after the padding. This defaults to 0.
500 This sets the padding after the image entries. The padding will be
501 placed after the last entry. This defaults to 0.
504 This specifies the pad byte to use when padding in the image. It
505 defaults to 0. To use 0xff, you would add 'pad-byte = <0xff>'.
508 This specifies the image filename. It defaults to 'image.bin'.
511 This causes binman to reorder the entries as needed to make sure they
512 are in increasing positional order. This can be used when your entry
513 order may not match the positional order. A common situation is where
514 the 'offset' properties are set by CONFIG options, so their ordering is
517 This is a boolean property so needs no value. To enable it, add a
518 line 'sort-by-offset;' to your description.
521 Normally only a single image is generated. To create more than one
522 image, put this property in the binman node. For example, this will
523 create image1.bin containing u-boot.bin, and image2.bin containing
524 both spl/u-boot-spl.bin and u-boot.bin::
542 For x86 machines the ROM offsets start just before 4GB and extend
543 up so that the image finished at the 4GB boundary. This boolean
544 option can be enabled to support this. The image size must be
545 provided so that binman knows when the image should start. For an
546 8MB ROM, the offset of the first entry would be 0xfff80000 with
547 this option, instead of 0 without this option.
550 This property specifies the entry offset of the first entry.
552 For PowerPC mpc85xx based CPU, CONFIG_SYS_TEXT_BASE is the entry
553 offset of the first entry. It can be 0xeff40000 or 0xfff40000 for
554 nor flash boot, 0x201000 for sd boot etc.
556 'end-at-4gb' property is not applicable where CONFIG_SYS_TEXT_BASE +
559 Examples of the above options can be found in the tests. See the
560 tools/binman/test directory.
562 It is possible to have the same binary appear multiple times in the image,
563 either by using a unit number suffix (u-boot@0, u-boot@1) or by using a
564 different name for each and specifying the type with the 'type' attribute.
567 Sections and hierachical images
568 -------------------------------
570 Sometimes it is convenient to split an image into several pieces, each of which
571 contains its own set of binaries. An example is a flash device where part of
572 the image is read-only and part is read-write. We can set up sections for each
573 of these, and place binaries in them independently. The image is still produced
574 as a single output file.
576 This feature provides a way of creating hierarchical images. For example here
577 is an example image with two copies of U-Boot. One is read-only (ro), intended
578 to be written only in the factory. Another is read-write (rw), so that it can be
579 upgraded in the field. The sizes are fixed so that the ro/rw boundary is known
580 and can be programmed::
598 This image could be placed into a SPI flash chip, with the protection boundary
601 A few special properties are provided for sections:
604 Indicates that this section is read-only. This has no impact on binman's
605 operation, but his property can be read at run time.
608 This string is prepended to all the names of the binaries in the
609 section. In the example above, the 'u-boot' binaries which actually be
610 renamed to 'ro-u-boot' and 'rw-u-boot'. This can be useful to
611 distinguish binaries with otherwise identical names.
617 Image nodes act like sections but also have a few extra properties:
620 Output filename for the image. This defaults to image.bin (or in the
621 case of multiple images <nodename>.bin where <nodename> is the name of
625 Create an image that can be repacked. With this option it is possible
626 to change anything in the image after it is created, including updating
627 the position and size of image components. By default this is not
628 permitted since it is not possibly to know whether this might violate a
629 constraint in the image description. For example, if a section has to
630 increase in size to hold a larger binary, that might cause the section
631 to fall out of its allow region (e.g. read-only portion of flash).
633 Adding this property causes the original offset and size values in the
634 image description to be stored in the FDT and fdtmap.
640 It is possible to ask binman to hash the contents of an entry and write that
641 value back to the device-tree node. For example::
651 Here, a new 'value' property will be written to the 'hash' node containing
652 the hash of the 'u-boot' entry. Only SHA256 is supported at present. Whole
653 sections can be hased if desired, by adding the 'hash' node to the section.
655 The has value can be chcked at runtime by hashing the data actually read and
656 comparing this has to the value in the device tree.
662 Binman automatically replaces 'u-boot' with an expanded version of that, i.e.
663 'u-boot-expanded'. This means that when you write::
671 type = "u-boot-expanded';
674 which in turn expands to::
686 U-Boot's various phase binaries actually comprise two or three pieces.
687 For example, u-boot.bin has the executable followed by a devicetree.
689 With binman we want to be able to update that devicetree with full image
690 information so that it is accessible to the executable. This is tricky
691 if it is not clear where the devicetree starts.
693 The above feature ensures that the devicetree is clearly separated from the
694 U-Boot executable and can be updated separately by binman as needed. It can be
695 disabled with the --no-expanded flag if required.
697 The same applies for u-boot-spl and u-boot-spl. In those cases, the expansion
698 includes the BSS padding, so for example::
707 type = "u-boot-expanded';
710 which in turn expands to::
725 Of course we should not expand SPL if it has no devicetree. Also if the BSS
726 padding is not needed (because BSS is in RAM as with CONFIG_SPL_SEPARATE_BSS),
727 the 'u-boot-spl-bss-pad' subnode should not be created. The use of the expaned
728 entry type is controlled by the UseExpanded() method. In the SPL case it checks
729 the 'spl-dtb' entry arg, which is 'y' or '1' if SPL has a devicetree.
731 For the BSS case, a 'spl-bss-pad' entry arg controls whether it is present. All
732 entry args are provided by the U-Boot Makefile.
738 Binman support compression for 'blob' entries (those of type 'blob' and
739 derivatives). To enable this for an entry, add a 'compress' property::
742 filename = "datafile";
746 The entry will then contain the compressed data, using the 'lz4' compression
747 algorithm. Currently this is the only one that is supported. The uncompressed
748 size is written to the node in an 'uncomp-size' property, if -u is used.
750 Compression is also supported for sections. In that case the entire section is
751 compressed in one block, including all its contents. This means that accessing
752 an entry from the section required decompressing the entire section. Also, the
753 size of a section indicates the space that it consumes in its parent section
754 (and typically the image). With compression, the section may contain more data,
755 and the uncomp-size property indicates that, as above. The contents of the
756 section is compressed first, before any padding is added. This ensures that the
757 padding itself is not compressed, which would be a waste of time.
760 Automatic .dtsi inclusion
761 -------------------------
763 It is sometimes inconvenient to add a 'binman' node to the .dts file for each
764 board. This can be done by using #include to bring in a common file. Another
765 approach supported by the U-Boot build system is to automatically include
766 a common header. You can then put the binman node (and anything else that is
767 specific to U-Boot, such as u-boot,dm-pre-reloc properies) in that header
770 Binman will search for the following files in arch/<arch>/dts::
772 <dts>-u-boot.dtsi where <dts> is the base name of the .dts file
773 <CONFIG_SYS_SOC>-u-boot.dtsi
774 <CONFIG_SYS_CPU>-u-boot.dtsi
775 <CONFIG_SYS_VENDOR>-u-boot.dtsi
778 U-Boot will only use the first one that it finds. If you need to include a
779 more general file you can do that from the more specific file using #include.
780 If you are having trouble figuring out what is going on, you can uncomment
781 the 'warning' line in scripts/Makefile.lib to see what it has found::
783 # Uncomment for debugging
784 # This shows all the files that were considered and the one that we chose.
785 # u_boot_dtsi_options_debug = $(u_boot_dtsi_options_raw)
791 For details on the various entry types supported by binman and how to use them,
792 see README.entries. This is generated from the source code using:
794 binman entry-docs >tools/binman/README.entries
803 It is possible to list the entries in an existing firmware image created by
804 binman, provided that there is an 'fdtmap' entry in the image. For example::
806 $ binman ls -i image.bin
807 Name Image-pos Size Entry-type Offset Uncomp-size
808 ----------------------------------------------------------------------
809 main-section c00 section 0
811 section 5fc section 4
813 u-boot 138 4 u-boot 38
814 u-boot-dtb 180 108 u-boot-dtb 80 3b5
815 u-boot-dtb 500 1ff u-boot-dtb 400 3b5
816 fdtmap 6fc 381 fdtmap 6fc
817 image-header bf8 8 image-header bf8
819 This shows the hierarchy of the image, the position, size and type of each
820 entry, the offset of each entry within its parent and the uncompressed size if
821 the entry is compressed.
823 It is also possible to list just some files in an image, e.g.::
825 $ binman ls -i image.bin section/cbfs
826 Name Image-pos Size Entry-type Offset Uncomp-size
827 --------------------------------------------------------------------
829 u-boot 138 4 u-boot 38
830 u-boot-dtb 180 108 u-boot-dtb 80 3b5
834 $ binman ls -i image.bin "*cb*" "*head*"
835 Name Image-pos Size Entry-type Offset Uncomp-size
836 ----------------------------------------------------------------------
838 u-boot 138 4 u-boot 38
839 u-boot-dtb 180 108 u-boot-dtb 80 3b5
840 image-header bf8 8 image-header bf8
843 Extracting files from images
844 ----------------------------
846 You can extract files from an existing firmware image created by binman,
847 provided that there is an 'fdtmap' entry in the image. For example::
849 $ binman extract -i image.bin section/cbfs/u-boot
851 which will write the uncompressed contents of that entry to the file 'u-boot' in
852 the current directory. You can also extract to a particular file, in this case
855 $ binman extract -i image.bin section/cbfs/u-boot -f u-boot.bin
857 It is possible to extract all files into a destination directory, which will
858 put files in subdirectories matching the entry hierarchy::
860 $ binman extract -i image.bin -O outdir
862 or just a selection::
864 $ binman extract -i image.bin "*u-boot*" -O outdir
867 Replacing files in an image
868 ---------------------------
870 You can replace files in an existing firmware image created by binman, provided
871 that there is an 'fdtmap' entry in the image. For example:
873 $ binman replace -i image.bin section/cbfs/u-boot
875 which will write the contents of the file 'u-boot' from the current directory
876 to the that entry, compressing if necessary. If the entry size changes, you must
877 add the 'allow-repack' property to the original image before generating it (see
878 above), otherwise you will get an error.
880 You can also use a particular file, in this case u-boot.bin::
882 $ binman replace -i image.bin section/cbfs/u-boot -f u-boot.bin
884 It is possible to replace all files from a source directory which uses the same
885 hierarchy as the entries::
887 $ binman replace -i image.bin -I indir
889 Files that are missing will generate a warning.
891 You can also replace just a selection of entries::
893 $ binman replace -i image.bin "*u-boot*" -I indir
899 Binman normally operates silently unless there is an error, in which case it
900 just displays the error. The -D/--debug option can be used to create a full
901 backtrace when errors occur. You can use BINMAN_DEBUG=1 when building to select
904 Internally binman logs some output while it is running. This can be displayed
905 by increasing the -v/--verbosity from the default of 1:
909 2: notices (important messages)
910 3: info about major operations
911 4: detailed information about each operation
912 5: debug (all output)
914 You can use BINMAN_VERBOSE=5 (for example) when building to select this.
920 Order of image creation
921 -----------------------
923 Image creation proceeds in the following order, for each entry in the image.
925 1. AddMissingProperties() - binman can add calculated values to the device
926 tree as part of its processing, for example the offset and size of each
927 entry. This method adds any properties associated with this, expanding the
928 device tree as needed. These properties can have placeholder values which are
929 set later by SetCalculatedProperties(). By that stage the size of sections
930 cannot be changed (since it would cause the images to need to be repacked),
931 but the correct values can be inserted.
933 2. ProcessFdt() - process the device tree information as required by the
934 particular entry. This may involve adding or deleting properties. If the
935 processing is complete, this method should return True. If the processing
936 cannot complete because it needs the ProcessFdt() method of another entry to
937 run first, this method should return False, in which case it will be called
940 3. GetEntryContents() - the contents of each entry are obtained, normally by
941 reading from a file. This calls the Entry.ObtainContents() to read the
942 contents. The default version of Entry.ObtainContents() calls
943 Entry.GetDefaultFilename() and then reads that file. So a common mechanism
944 to select a file to read is to override that function in the subclass. The
945 functions must return True when they have read the contents. Binman will
946 retry calling the functions a few times if False is returned, allowing
947 dependencies between the contents of different entries.
949 4. GetEntryOffsets() - calls Entry.GetOffsets() for each entry. This can
950 return a dict containing entries that need updating. The key should be the
951 entry name and the value is a tuple (offset, size). This allows an entry to
952 provide the offset and size for other entries. The default implementation
953 of GetEntryOffsets() returns {}.
955 5. PackEntries() - calls Entry.Pack() which figures out the offset and
956 size of an entry. The 'current' image offset is passed in, and the function
957 returns the offset immediately after the entry being packed. The default
958 implementation of Pack() is usually sufficient.
960 Note: for sections, this also checks that the entries do not overlap, nor extend
961 outside the section. If the section does not have a defined size, the size is
962 set large enough to hold all the entries.
964 6. SetImagePos() - sets the image position of every entry. This is the absolute
965 position 'image-pos', as opposed to 'offset' which is relative to the containing
966 section. This must be done after all offsets are known, which is why it is quite
967 late in the ordering.
969 7. SetCalculatedProperties() - update any calculated properties in the device
970 tree. This sets the correct 'offset' and 'size' vaues, for example.
972 8. ProcessEntryContents() - this calls Entry.ProcessContents() on each entry.
973 The default implementatoin does nothing. This can be overriden to adjust the
974 contents of an entry in some way. For example, it would be possible to create
975 an entry containing a hash of the contents of some other entries. At this
976 stage the offset and size of entries should not be adjusted unless absolutely
977 necessary, since it requires a repack (going back to PackEntries()).
979 9. ResetForPack() - if the ProcessEntryContents() step failed, in that an entry
980 has changed its size, then there is no alternative but to go back to step 5 and
981 try again, repacking the entries with the updated size. ResetForPack() removes
982 the fixed offset/size values added by binman, so that the packing can start from
985 10. WriteSymbols() - write the value of symbols into the U-Boot SPL binary.
986 See 'Access to binman entry offsets at run time' below for a description of
987 what happens in this stage.
989 11. BuildImage() - builds the image and writes it to a file
991 12. WriteMap() - writes a text file containing a map of the image. This is the
998 Binman can make use of external command-line tools to handle processing of
999 entry contents or to generate entry contents. These tools are executed using
1000 the 'tools' module's Run() method. The tools generally must exist on the PATH,
1001 but the --toolpath option can be used to specify additional search paths to
1002 use. This option can be specified multiple times to add more than one path.
1004 For some compile tools binman will use the versions specified by commonly-used
1005 environment variables like CC and HOSTCC for the C compiler, based on whether
1006 the tool's output will be used for the target or for the host machine. If those
1007 aren't given, it will also try to derive target-specific versions from the
1008 CROSS_COMPILE environment variable during a cross-compilation.
1014 Binman is a critical tool and is designed to be very testable. Entry
1015 implementations target 100% test coverage. Run 'binman test -T' to check this.
1017 To enable Python test coverage on Debian-type distributions (e.g. Ubuntu)::
1019 $ sudo apt-get install python-coverage python3-coverage python-pytest
1025 Binman tries to run tests concurrently. This means that the tests make use of
1026 all available CPUs to run.
1030 $ sudo apt-get install python-subunit python3-subunit
1032 Use '-P 1' to disable this. It is automatically disabled when code coverage is
1033 being used (-T) since they are incompatible.
1039 Sometimes when debugging tests it is useful to keep the input and output
1040 directories so they can be examined later. Use -X or --test-preserve-dirs for
1044 Running tests on non-x86 architectures
1045 --------------------------------------
1047 Binman's tests have been written under the assumption that they'll be run on a
1048 x86-like host and there hasn't been an attempt to make them portable yet.
1049 However, it's possible to run the tests by cross-compiling to x86.
1051 To install an x86 cross-compiler on Debian-type distributions (e.g. Ubuntu)::
1053 $ sudo apt-get install gcc-x86-64-linux-gnu
1055 Then, you can run the tests under cross-compilation::
1057 $ CROSS_COMPILE=x86_64-linux-gnu- binman test -T
1059 You can also use gcc-i686-linux-gnu similar to the above.
1062 Writing new entries and debugging
1063 ---------------------------------
1065 The behaviour of entries is defined by the Entry class. All other entries are
1066 a subclass of this. An important subclass is Entry_blob which takes binary
1067 data from a file and places it in the entry. In fact most entry types are
1068 subclasses of Entry_blob.
1070 Each entry type is a separate file in the tools/binman/etype directory. Each
1071 file contains a class called Entry_<type> where <type> is the entry type.
1072 New entry types can be supported by adding new files in that directory.
1073 These will automatically be detected by binman when needed.
1075 Entry properties are documented in entry.py. The entry subclasses are free
1076 to change the values of properties to support special behaviour. For example,
1077 when Entry_blob loads a file, it sets content_size to the size of the file.
1078 Entry classes can adjust other entries. For example, an entry that knows
1079 where other entries should be positioned can set up those entries' offsets
1080 so they don't need to be set in the binman decription. It can also adjust
1083 Most of the time such essoteric behaviour is not needed, but it can be
1084 essential for complex images.
1086 If you need to specify a particular device-tree compiler to use, you can define
1087 the DTC environment variable. This can be useful when the system dtc is too
1090 To enable a full backtrace and other debugging features in binman, pass
1091 BINMAN_DEBUG=1 to your build::
1093 make qemu-x86_defconfig
1096 To enable verbose logging from binman, base BINMAN_VERBOSE to your build, which
1097 adds a -v<level> option to the call to binman::
1099 make qemu-x86_defconfig
1100 make BINMAN_VERBOSE=5
1106 Binman takes a lot of inspiration from a Chrome OS tool called
1107 'cros_bundle_firmware', which I wrote some years ago. That tool was based on
1108 a reasonably simple and sound design but has expanded greatly over the
1109 years. In particular its handling of x86 images is convoluted.
1111 Quite a few lessons have been learned which are hopefully applied here.
1117 On the face of it, a tool to create firmware images should be fairly simple:
1118 just find all the input binaries and place them at the right place in the
1119 image. The difficulty comes from the wide variety of input types (simple
1120 flat binaries containing code, packaged data with various headers), packing
1121 requirments (alignment, spacing, device boundaries) and other required
1122 features such as hierarchical images.
1124 The design challenge is to make it easy to create simple images, while
1125 allowing the more complex cases to be supported. For example, for most
1126 images we don't much care exactly where each binary ends up, so we should
1127 not have to specify that unnecessarily.
1129 New entry types should aim to provide simple usage where possible. If new
1130 core features are needed, they can be added in the Entry base class.
1138 - Use of-platdata to make the information available to code that is unable
1139 to use device tree (such as a very small SPL image)
1140 - Allow easy building of images by specifying just the board name
1141 - Support building an image for a board (-b) more completely, with a
1142 configurable build directory
1143 - Detect invalid properties in nodes
1144 - Sort the fdtmap by offset
1145 - Output temporary files to a different directory
1148 Simon Glass <sjg@chromium.org>