5 config ANDROID_BOOT_IMAGE
6 bool "Enable support for Android Boot Images"
9 This enables support for booting images which use the Android
13 bool "Support Flattened Image Tree"
19 This option allows you to boot the new uImage structure,
20 Flattened Image Tree. FIT is formally a FDT, which can include
21 images of various types (kernel, FDT blob, ramdisk, etc.)
22 in a single blob. To boot this new uImage structure,
23 pass the address of the blob to the "bootm" command.
24 FIT is very flexible, supporting compression, multiple images,
25 multiple configurations, verification through hashing and also
26 verified boot (secure boot using RSA).
29 bool "Show image date and time when displaying image information"
32 When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of
33 an image is printed by image commands like bootm or iminfo. This
34 is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is
35 enabled, then U-Boot requires FITs to have a timestamp. If a FIT is
36 loaded that does not, the message 'Wrong FIT format: no timestamp'
41 config FIT_EXTERNAL_OFFSET
42 hex "FIT external data offset"
45 This specifies a data offset in fit image.
46 The offset is from data payload offset to the beginning of
47 fit image header. When specifies a offset, specific data
48 could be put in the hole between data payload and fit image
49 header, such as CSF data on i.MX platform.
52 bool "Do a full check of the FIT before using it"
55 Enable this do a full check of the FIT to make sure it is valid. This
56 helps to protect against carefully crafted FITs which take advantage
57 of bugs or omissions in the code. This includes a bad structure,
58 multiple root nodes and the like.
61 bool "Enable signature verification of FIT uImages"
66 select IMAGE_SIGN_INFO
69 This option enables signature verification of FIT uImages,
70 using a hash signed and verified using RSA. If
71 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
72 hashing is available using hardware, then the RSA library will use
73 it. See doc/uImage.FIT/signature.txt for more details.
75 WARNING: When relying on signed FIT images with a required signature
76 check the legacy image format is disabled by default, so that
77 unsigned images cannot be loaded. If a board needs the legacy image
78 format support in this case, enable it using
79 CONFIG_LEGACY_IMAGE_FORMAT.
81 config FIT_SIGNATURE_MAX_SIZE
82 hex "Max size of signed FIT structures"
83 depends on FIT_SIGNATURE
86 This option sets a max size in bytes for verified FIT uImages.
87 A sane value of 256MB protects corrupted DTB structures from overlapping
88 device memory. Assure this size does not extend past expected storage
92 bool "Support rsassa-pss signature scheme of FIT image contents"
93 depends on FIT_SIGNATURE
95 Enable this to support the pss padding algorithm as described
96 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
99 bool "Enable ciphering data in a FIT uImages"
103 Enable the feature of data ciphering/unciphering in the tool mkimage
104 and in the u-boot support of the FIT image.
107 bool "Show verbose messages when FIT images fail"
109 Generally a system will have valid FIT images so debug messages
110 are a waste of code space. If you are debugging your images then
111 you can enable this option to get more verbose information about
114 config FIT_BEST_MATCH
115 bool "Select the best match for the kernel device tree"
117 When no configuration is explicitly selected, default to the
118 one whose fdt's compatibility field best matches that of
119 U-Boot itself. A match is considered "best" if it matches the
120 most specific compatibility entry of U-Boot's fdt's root node.
121 The order of entries in the configuration's fdt is ignored.
123 config FIT_IMAGE_POST_PROCESS
124 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
125 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
126 default y if TI_SECURE_DEVICE
128 Allows doing any sort of manipulation to blobs after they got extracted
129 from FIT images like stripping off headers or modifying the size of the
130 blob, verification, authentication, decryption etc. in a platform or
131 board specific way. In order to use this feature a platform or board-
132 specific implementation of board_fit_image_post_process() must be
133 provided. Also, anything done during this post-processing step would
134 need to be comprehended in how the images were prepared before being
135 injected into the FIT creation (i.e. the blobs would have been pre-
136 processed before being added to the FIT image).
139 bool "Support FIT printing"
142 Support printing the content of the fitImage in a verbose manner.
147 bool "Support Flattened Image Tree within SPL"
153 bool "Support FIT printing within SPL"
156 Support printing the content of the fitImage in a verbose manner in SPL.
158 config SPL_FIT_FULL_CHECK
159 bool "Do a full check of the FIT before using it"
161 Enable this do a full check of the FIT to make sure it is valid. This
162 helps to protect against carefully crafted FITs which take advantage
163 of bugs or omissions in the code. This includes a bad structure,
164 multiple root nodes and the like.
167 config SPL_FIT_SIGNATURE
168 bool "Enable signature verification of FIT firmware within SPL"
170 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
177 select SPL_IMAGE_SIGN_INFO
178 select SPL_FIT_FULL_CHECK
180 config SPL_FIT_SIGNATURE_MAX_SIZE
181 hex "Max size of signed FIT structures in SPL"
182 depends on SPL_FIT_SIGNATURE
185 This option sets a max size in bytes for verified FIT uImages.
186 A sane value of 256MB protects corrupted DTB structures from overlapping
187 device memory. Assure this size does not extend past expected storage
190 config SPL_FIT_RSASSA_PSS
191 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
192 depends on SPL_FIT_SIGNATURE
194 Enable this to support the pss padding algorithm as described
195 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
198 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
201 Normally with the SPL framework a legacy image is generated as part
202 of the build. This contains U-Boot along with information as to
203 where it should be loaded. This option instead enables generation
204 of a FIT (Flat Image Tree) which provides more flexibility. In
205 particular it can handle selecting from multiple device tree
206 and passing the correct one to U-Boot.
208 This path has the following limitations:
210 1. "loadables" images, other than FDTs, which do not have a "load"
211 property will not be loaded. This limitation also applies to FPGA
212 images with the correct "compatible" string.
213 2. For FPGA images, only the "compatible" = "u-boot,fpga-legacy"
214 loading method is supported.
215 3. FDTs are only loaded for images with an "os" property of "u-boot".
216 "linux" images are also supported with Falcon boot mode.
218 config SPL_LOAD_FIT_ADDRESS
219 hex "load address of fit image"
220 depends on SPL_LOAD_FIT
223 Specify the load address of the fit image that will be loaded
226 config SPL_LOAD_FIT_APPLY_OVERLAY
227 bool "Enable SPL applying DT overlays from FIT"
228 depends on SPL_LOAD_FIT
229 select OF_LIBFDT_OVERLAY
231 The device tree is loaded from the FIT image. Allow the SPL is to
232 also load device-tree overlays from the FIT image an apply them
233 over the device tree.
235 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
236 depends on SPL_LOAD_FIT_APPLY_OVERLAY
238 hex "size of temporary buffer used to load the overlays"
240 The size of the area where the overlays will be loaded and
241 uncompress. Must be at least as large as biggest overlay
244 config SPL_LOAD_FIT_FULL
245 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
248 Normally with the SPL framework a legacy image is generated as part
249 of the build. This contains U-Boot along with information as to
250 where it should be loaded. This option instead enables generation
251 of a FIT (Flat Image Tree) which provides more flexibility. In
252 particular it can handle selecting from multiple device tree
253 and passing the correct one to U-Boot.
255 config SPL_FIT_IMAGE_POST_PROCESS
256 bool "Enable post-processing of FIT artifacts after loading by the SPL"
257 depends on SPL_LOAD_FIT
258 default y if TI_SECURE_DEVICE
260 Allows doing any sort of manipulation to blobs after they got extracted
261 from the U-Boot FIT image like stripping off headers or modifying the
262 size of the blob, verification, authentication, decryption etc. in a
263 platform or board specific way. In order to use this feature a platform
264 or board-specific implementation of board_fit_image_post_process() must
265 be provided. Also, anything done during this post-processing step would
266 need to be comprehended in how the images were prepared before being
267 injected into the FIT creation (i.e. the blobs would have been pre-
268 processed before being added to the FIT image).
270 config SPL_FIT_SOURCE
271 string ".its source file for U-Boot FIT image"
274 Specifies a (platform specific) FIT source file to generate the
275 U-Boot FIT image. This could specify further image to load and/or
278 config USE_SPL_FIT_GENERATOR
279 bool "Use a script to generate the .its script"
280 default y if SPL_FIT && (!ARCH_SUNXI && !RISCV)
282 config SPL_FIT_GENERATOR
283 string ".its file generator script for U-Boot FIT image"
284 depends on USE_SPL_FIT_GENERATOR
285 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
286 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
288 Specifies a (platform specific) script file to generate the FIT
289 source file used to build the U-Boot FIT image file. This gets
290 passed a list of supported device tree file stub names to
291 include in the generated image.
298 bool "Standard boot support"
300 depends on DM && OF_CONTROL && BLK
302 U-Boot supports a standard way of locating something to boot,
303 typically an Operating System such as Linux, provided by a distro such
304 as Arch Linux or Debian. Enable this to support iterating through
305 available bootdevs and using bootmeths to find bootflows suitable for
308 Standard boot is not a standard way of booting, just a framework
309 within U-Boot for supporting all the different ways that exist.
313 - bootdev - a device which can hold a distro (e.g. MMC)
314 - bootmeth - a method to scan a bootdev to find bootflows (owned by
316 - bootflow - a description of how to boot (owned by the distro)
319 bool "Enhanced features for standard boot"
322 This enables various useful features for standard boot, which are not
323 essential for operation:
325 - bootdev, bootmeth commands
326 - extra features in the bootflow command
327 - support for selecting the ordering of bootmeths ("bootmeth order")
328 - support for selecting the ordering of bootdevs using the devicetree
329 as well as the "boot_targets" environment variable
333 config BOOTSTD_BOOTCOMMAND
334 bool "Use bootstd to boot"
335 default y if !DISTRO_DEFAULTS
337 Enable this to select a default boot-command suitable for booting
338 with standard boot. This can be overridden by the board if needed,
339 but the default command should be enough for most boards which use
342 For now this is only selected if distro boot is NOT used, since
343 standard boot does not support all of the features of distro boot
346 config BOOTMETH_DISTRO
347 bool "Bootdev support for distro boot"
351 Enables support for distro boot using bootdevs. This makes the
352 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
355 This provides a way to try out standard boot on an existing boot flow.
357 config BOOTMETH_DISTRO_PXE
358 bool "Bootdev support for distro boot over network"
359 depends on CMD_PXE && CMD_NET && DM_ETH
362 Enables support for distro boot using bootdevs. This makes the
363 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
365 This provides a way to try out standard boot on an existing boot flow.
367 config BOOTMETH_EFILOADER
368 bool "Bootdev support for EFI boot"
369 depends on CMD_BOOTEFI
372 Enables support for EFI boot using bootdevs. This makes the
373 bootdevs look for a 'boot<arch>.efi' on each filesystem
374 they scan. The resulting file is booted after enabling U-Boot's
377 The <arch> depends on the architecture of the board:
379 aa64 - aarch64 (ARM 64-bit)
383 riscv32 - RISC-V 32-bit
384 riscv64 - RISC-V 64-bit
386 This provides a way to try out standard boot on an existing boot flow.
388 config BOOTMETH_SANDBOX
392 This is a sandbox bootmeth driver used for testing. It always returns
393 -ENOTSUPP when attempting to boot.
395 config BOOTMETH_SCRIPT
396 bool "Bootdev support for U-Boot scripts"
397 default y if BOOTSTD_FULL
399 Enables support for booting a distro via a U-Boot script. This makes
400 the bootdevs look for a 'boot/boot.scr' file which can be used to
403 This provides a way to try out standard boot on an existing boot flow.
404 It is not enabled by default to save space.
408 config LEGACY_IMAGE_FORMAT
409 bool "Enable support for the legacy image format"
410 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
412 This option enables the legacy image format. It is enabled by
413 default for backward compatibility, unless FIT_SIGNATURE is
414 set where it is disabled so that unsigned images cannot be
415 loaded. If a board needs the legacy image format support in this
416 case, enable it here.
418 config SUPPORT_RAW_INITRD
419 bool "Enable raw initrd images"
421 Note, defining the SUPPORT_RAW_INITRD allows user to supply
422 kernel with raw initrd images. The syntax is slightly different, the
423 address of the initrd must be augmented by it's size, in the following
424 format: "<initrd address>:<initrd size>".
426 config OF_BOARD_SETUP
427 bool "Set up board-specific details in device tree before boot"
430 This causes U-Boot to call ft_board_setup() before booting into
431 the Operating System. This function can set up various
432 board-specific information in the device tree for use by the OS.
433 The device tree is then passed to the OS.
435 config OF_SYSTEM_SETUP
436 bool "Set up system-specific details in device tree before boot"
439 This causes U-Boot to call ft_system_setup() before booting into
440 the Operating System. This function can set up various
441 system-specific information in the device tree for use by the OS.
442 The device tree is then passed to the OS.
444 config OF_STDOUT_VIA_ALIAS
445 bool "Update the device-tree stdout alias from U-Boot"
448 This uses U-Boot's serial alias from the aliases node to update
449 the device tree passed to the OS. The "linux,stdout-path" property
450 in the chosen node is set to point to the correct serial node.
451 This option currently references CONFIG_CONS_INDEX, which is
452 incorrect when used with device tree as this option does not
453 exist / should not be used.
455 config SYS_EXTRA_OPTIONS
456 string "Extra Options (DEPRECATED)"
458 The old configuration infrastructure (= mkconfig + boards.cfg)
459 provided the extra options field. If you have something like
460 "HAS_BAR,BAZ=64", the optional options
462 #define CONFIG_BAZ 64
463 will be defined in include/config.h.
464 This option was prepared for the smooth migration from the old
465 configuration to Kconfig. Since this option will be removed sometime,
466 new boards should not use this option.
468 config HAVE_SYS_TEXT_BASE
470 depends on !NIOS2 && !XTENSA
475 depends on HAVE_SYS_TEXT_BASE
476 default 0x0 if POSITION_INDEPENDENT
477 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
478 default 0x81700000 if MACH_SUNIV
479 default 0x2a000000 if MACH_SUN9I
480 default 0x42e00000 if MACH_SUN8I_V3S
481 default 0x4a000000 if ARCH_SUNXI
484 The address in memory that U-Boot will be running from, initially.
486 config HAVE_SYS_MONITOR_BASE
488 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
489 || FLASH_PIC32 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
493 config SYS_MONITOR_BASE
494 depends on HAVE_SYS_MONITOR_BASE
495 hex "Physical start address of boot monitor code"
496 default SYS_TEXT_BASE
498 The physical start address of boot monitor code (which is the same as
499 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
500 when booting from flash.
502 config SPL_SYS_MONITOR_BASE
503 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
504 hex "Physical start address of SPL monitor code"
505 default SPL_TEXT_BASE
507 config TPL_SYS_MONITOR_BASE
508 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
509 hex "Physical start address of TPL monitor code"
511 config DYNAMIC_SYS_CLK_FREQ
512 bool "Determine CPU clock frequency at run-time"
514 Implement a get_board_sys_clk function that will determine the CPU
515 clock frequency at run time, rather than define it statically.
518 depends on !DYNAMIC_SYS_CLK_FREQ
519 int "CPU clock frequency"
520 default 125000000 if ARCH_LS1012A
521 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
522 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
523 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
524 default 66660000 if ARCH_T2080
525 default 33333333 if RCAR_GEN3
526 default 24000000 if ARCH_EXYNOS
527 default 20000000 if RCAR_GEN2
530 A static value for the CPU frequency. Note that if not required
531 for a given SoC, this can be left at 0.
533 config ARCH_FIXUP_FDT_MEMORY
534 bool "Enable arch_fixup_memory_banks() call"
537 Enable FDT memory map syncup before OS boot. This feature can be
538 used for booting OS with different memory setup where the part of
539 the memory location should be used for different purpose.
542 bool "Support booting Chrome OS"
544 Chrome OS requires U-Boot to set up a table indicating the boot mode
545 (e.g. Developer mode) and a few other things. Enable this if you are
546 booting on a Chromebook to avoid getting an error about an invalid
549 config CHROMEOS_VBOOT
550 bool "Support Chrome OS verified boot"
552 This is intended to enable the full Chrome OS verified boot support
553 in U-Boot. It is not actually implemented in the U-Boot source code
554 at present, so this option is always set to 'n'. It allows
555 distinguishing between booting Chrome OS in a basic way (developer
556 mode) and a full boot.
562 bool "Freescale PBL(pre-boot loader) image format support"
563 select SYS_RAMBOOT if PPC
565 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
566 For more details refer to doc/README.pblimage
569 prompt "Freescale PBL load location"
570 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
571 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
575 bool "Freescale PBL is found on SD card"
578 bool "Freescale PBL is found on SPI flash"
582 config FSL_FIXED_MMC_LOCATION
583 bool "PBL MMC is at a fixed location"
584 depends on SDCARD && !RAMBOOT_PBL
586 config ESDHC_HC_BLK_ADDR
588 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
590 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
591 code length of these soc specify the memory address in block address
592 format. Block length is fixed to 512 bytes as per the SD High
593 Capacity specification.
595 config SYS_FSL_PBL_PBI
596 string "PBI(pre-boot instructions) commands for the PBL image"
597 depends on RAMBOOT_PBL
599 PBI commands can be used to configure SoC before it starts the execution.
600 Please refer doc/README.pblimage for more details.
602 config SYS_FSL_PBL_RCW
603 string "Aadditional RCW (Power on reset configuration) for the PBL image"
604 depends on RAMBOOT_PBL
606 Enables addition of RCW (Power on reset configuration) in built image.
607 Please refer doc/README.pblimage for more details.
609 endmenu # Boot images
614 bool "Boot timing and reporting"
616 Enable recording of boot time while booting. To use it, insert
617 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
618 bootstage.h. Only a single entry is recorded for each ID. You can
619 give the entry a name with bootstage_mark_name(). You can also
620 record elapsed time in a particular stage using bootstage_start()
621 before starting and bootstage_accum() when finished. Bootstage will
622 add up all the accumulated time and report it.
624 Normally, IDs are defined in bootstage.h but a small number of
625 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
628 Calls to show_boot_progress() will also result in log entries but
629 these will not have names.
632 bool "Boot timing and reported in SPL"
633 depends on BOOTSTAGE && SPL
635 Enable recording of boot time in SPL. To make this visible to U-Boot
636 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
637 information when SPL finishes and load it when U-Boot proper starts
641 bool "Boot timing and reported in TPL"
642 depends on BOOTSTAGE && TPL
644 Enable recording of boot time in SPL. To make this visible to U-Boot
645 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
646 information when TPL finishes and load it when U-Boot proper starts
649 config BOOTSTAGE_REPORT
650 bool "Display a detailed boot timing report before booting the OS"
653 Enable output of a boot time report just before the OS is booted.
654 This shows how long it took U-Boot to go through each stage of the
655 boot process. The report looks something like this:
657 Timer summary in microseconds:
660 3,575,678 3,575,678 board_init_f start
661 3,575,695 17 arch_cpu_init A9
662 3,575,777 82 arch_cpu_init done
663 3,659,598 83,821 board_init_r start
664 3,910,375 250,777 main_loop
665 29,916,167 26,005,792 bootm_start
666 30,361,327 445,160 start_kernel
668 config BOOTSTAGE_RECORD_COUNT
669 int "Number of boot stage records to store"
673 This is the size of the bootstage record list and is the maximum
674 number of bootstage records that can be recorded.
676 config SPL_BOOTSTAGE_RECORD_COUNT
677 int "Number of boot stage records to store for SPL"
678 depends on SPL_BOOTSTAGE
681 This is the size of the bootstage record list and is the maximum
682 number of bootstage records that can be recorded.
684 config TPL_BOOTSTAGE_RECORD_COUNT
685 int "Number of boot stage records to store for TPL"
686 depends on TPL_BOOTSTAGE
689 This is the size of the bootstage record list and is the maximum
690 number of bootstage records that can be recorded.
693 bool "Store boot timing information in the OS device tree"
696 Stash the bootstage information in the FDT. A root 'bootstage'
697 node is created with each bootstage id as a child. Each child
698 has a 'name' property and either 'mark' containing the
699 mark time in microseconds, or 'accum' containing the
700 accumulated time for that bootstage id in microseconds.
705 name = "board_init_f";
714 Code in the Linux kernel can find this in /proc/devicetree.
716 config BOOTSTAGE_STASH
717 bool "Stash the boot timing information in memory before booting OS"
720 Some OSes do not support device tree. Bootstage can instead write
721 the boot timing information in a binary format at a given address.
722 This happens through a call to bootstage_stash(), typically in
723 the CPU's cleanup_before_linux() function. You can use the
724 'bootstage stash' and 'bootstage unstash' commands to do this on
727 config BOOTSTAGE_STASH_ADDR
728 hex "Address to stash boot timing information"
731 Provide an address which will not be overwritten by the OS when it
732 starts, so that it can read this information when ready.
734 config BOOTSTAGE_STASH_SIZE
735 hex "Size of boot timing stash region"
738 This should be large enough to hold the bootstage stash. A value of
739 4096 (4KiB) is normally plenty.
741 config SHOW_BOOT_PROGRESS
742 bool "Show boot progress in a board-specific manner"
744 Defining this option allows to add some board-specific code (calling
745 a user-provided function show_boot_progress(int) that enables you to
746 show the system's boot progress on some display (for example, some
747 LEDs) on your board. At the moment, the following checkpoints are
750 Legacy uImage format:
753 1 common/cmd_bootm.c before attempting to boot an image
754 -1 common/cmd_bootm.c Image header has bad magic number
755 2 common/cmd_bootm.c Image header has correct magic number
756 -2 common/cmd_bootm.c Image header has bad checksum
757 3 common/cmd_bootm.c Image header has correct checksum
758 -3 common/cmd_bootm.c Image data has bad checksum
759 4 common/cmd_bootm.c Image data has correct checksum
760 -4 common/cmd_bootm.c Image is for unsupported architecture
761 5 common/cmd_bootm.c Architecture check OK
762 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
763 6 common/cmd_bootm.c Image Type check OK
764 -6 common/cmd_bootm.c gunzip uncompression error
765 -7 common/cmd_bootm.c Unimplemented compression type
766 7 common/cmd_bootm.c Uncompression OK
767 8 common/cmd_bootm.c No uncompress/copy overwrite error
768 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
770 9 common/image.c Start initial ramdisk verification
771 -10 common/image.c Ramdisk header has bad magic number
772 -11 common/image.c Ramdisk header has bad checksum
773 10 common/image.c Ramdisk header is OK
774 -12 common/image.c Ramdisk data has bad checksum
775 11 common/image.c Ramdisk data has correct checksum
776 12 common/image.c Ramdisk verification complete, start loading
777 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
778 13 common/image.c Start multifile image verification
779 14 common/image.c No initial ramdisk, no multifile, continue.
781 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
783 -30 arch/powerpc/lib/board.c Fatal error, hang the system
784 -31 post/post.c POST test failed, detected by post_output_backlog()
785 -32 post/post.c POST test failed, detected by post_run_single()
787 34 common/cmd_doc.c before loading a Image from a DOC device
788 -35 common/cmd_doc.c Bad usage of "doc" command
789 35 common/cmd_doc.c correct usage of "doc" command
790 -36 common/cmd_doc.c No boot device
791 36 common/cmd_doc.c correct boot device
792 -37 common/cmd_doc.c Unknown Chip ID on boot device
793 37 common/cmd_doc.c correct chip ID found, device available
794 -38 common/cmd_doc.c Read Error on boot device
795 38 common/cmd_doc.c reading Image header from DOC device OK
796 -39 common/cmd_doc.c Image header has bad magic number
797 39 common/cmd_doc.c Image header has correct magic number
798 -40 common/cmd_doc.c Error reading Image from DOC device
799 40 common/cmd_doc.c Image header has correct magic number
800 41 common/cmd_ide.c before loading a Image from a IDE device
801 -42 common/cmd_ide.c Bad usage of "ide" command
802 42 common/cmd_ide.c correct usage of "ide" command
803 -43 common/cmd_ide.c No boot device
804 43 common/cmd_ide.c boot device found
805 -44 common/cmd_ide.c Device not available
806 44 common/cmd_ide.c Device available
807 -45 common/cmd_ide.c wrong partition selected
808 45 common/cmd_ide.c partition selected
809 -46 common/cmd_ide.c Unknown partition table
810 46 common/cmd_ide.c valid partition table found
811 -47 common/cmd_ide.c Invalid partition type
812 47 common/cmd_ide.c correct partition type
813 -48 common/cmd_ide.c Error reading Image Header on boot device
814 48 common/cmd_ide.c reading Image Header from IDE device OK
815 -49 common/cmd_ide.c Image header has bad magic number
816 49 common/cmd_ide.c Image header has correct magic number
817 -50 common/cmd_ide.c Image header has bad checksum
818 50 common/cmd_ide.c Image header has correct checksum
819 -51 common/cmd_ide.c Error reading Image from IDE device
820 51 common/cmd_ide.c reading Image from IDE device OK
821 52 common/cmd_nand.c before loading a Image from a NAND device
822 -53 common/cmd_nand.c Bad usage of "nand" command
823 53 common/cmd_nand.c correct usage of "nand" command
824 -54 common/cmd_nand.c No boot device
825 54 common/cmd_nand.c boot device found
826 -55 common/cmd_nand.c Unknown Chip ID on boot device
827 55 common/cmd_nand.c correct chip ID found, device available
828 -56 common/cmd_nand.c Error reading Image Header on boot device
829 56 common/cmd_nand.c reading Image Header from NAND device OK
830 -57 common/cmd_nand.c Image header has bad magic number
831 57 common/cmd_nand.c Image header has correct magic number
832 -58 common/cmd_nand.c Error reading Image from NAND device
833 58 common/cmd_nand.c reading Image from NAND device OK
835 -60 common/env_common.c Environment has a bad CRC, using default
837 64 net/eth.c starting with Ethernet configuration.
838 -64 net/eth.c no Ethernet found.
839 65 net/eth.c Ethernet found.
841 -80 common/cmd_net.c usage wrong
842 80 common/cmd_net.c before calling net_loop()
843 -81 common/cmd_net.c some error in net_loop() occurred
844 81 common/cmd_net.c net_loop() back without error
845 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
846 82 common/cmd_net.c trying automatic boot
847 83 common/cmd_net.c running "source" command
848 -83 common/cmd_net.c some error in automatic boot or "source" command
849 84 common/cmd_net.c end without errors
854 100 common/cmd_bootm.c Kernel FIT Image has correct format
855 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
856 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
857 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
858 102 common/cmd_bootm.c Kernel unit name specified
859 -103 common/cmd_bootm.c Can't get kernel subimage node offset
860 103 common/cmd_bootm.c Found configuration node
861 104 common/cmd_bootm.c Got kernel subimage node offset
862 -104 common/cmd_bootm.c Kernel subimage hash verification failed
863 105 common/cmd_bootm.c Kernel subimage hash verification OK
864 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
865 106 common/cmd_bootm.c Architecture check OK
866 -106 common/cmd_bootm.c Kernel subimage has wrong type
867 107 common/cmd_bootm.c Kernel subimage type OK
868 -107 common/cmd_bootm.c Can't get kernel subimage data/size
869 108 common/cmd_bootm.c Got kernel subimage data/size
870 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
871 -109 common/cmd_bootm.c Can't get kernel subimage type
872 -110 common/cmd_bootm.c Can't get kernel subimage comp
873 -111 common/cmd_bootm.c Can't get kernel subimage os
874 -112 common/cmd_bootm.c Can't get kernel subimage load address
875 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
877 120 common/image.c Start initial ramdisk verification
878 -120 common/image.c Ramdisk FIT image has incorrect format
879 121 common/image.c Ramdisk FIT image has correct format
880 122 common/image.c No ramdisk subimage unit name, using configuration
881 -122 common/image.c Can't get configuration for ramdisk subimage
882 123 common/image.c Ramdisk unit name specified
883 -124 common/image.c Can't get ramdisk subimage node offset
884 125 common/image.c Got ramdisk subimage node offset
885 -125 common/image.c Ramdisk subimage hash verification failed
886 126 common/image.c Ramdisk subimage hash verification OK
887 -126 common/image.c Ramdisk subimage for unsupported architecture
888 127 common/image.c Architecture check OK
889 -127 common/image.c Can't get ramdisk subimage data/size
890 128 common/image.c Got ramdisk subimage data/size
891 129 common/image.c Can't get ramdisk load address
892 -129 common/image.c Got ramdisk load address
894 -130 common/cmd_doc.c Incorrect FIT image format
895 131 common/cmd_doc.c FIT image format OK
897 -140 common/cmd_ide.c Incorrect FIT image format
898 141 common/cmd_ide.c FIT image format OK
900 -150 common/cmd_nand.c Incorrect FIT image format
901 151 common/cmd_nand.c FIT image format OK
903 config SPL_SHOW_BOOT_PROGRESS
904 bool "Show boot progress in a board-specific manner in SPL"
907 Defining this option allows to add some board-specific code (calling
908 a user-provided function show_boot_progress(int) that enables you to
909 show the system's boot progress on some display (for example, some
910 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
917 bool "Support for booting from NOR flash"
920 Enabling this will make a U-Boot binary that is capable of being
921 booted via NOR. In this case we will enable certain pinmux early
922 as the ROM only partially sets up pinmux. We also default to using
926 bool "Support for booting from NAND flash"
929 Enabling this will make a U-Boot binary that is capable of being
930 booted via NAND flash. This is not a must, some SoCs need this,
934 bool "Support for booting from ONENAND"
937 Enabling this will make a U-Boot binary that is capable of being
938 booted via ONENAND. This is not a must, some SoCs need this,
942 bool "Support for booting from QSPI flash"
944 Enabling this will make a U-Boot binary that is capable of being
945 booted via QSPI flash. This is not a must, some SoCs need this,
949 bool "Support for booting from SATA"
951 Enabling this will make a U-Boot binary that is capable of being
952 booted via SATA. This is not a must, some SoCs need this,
956 bool "Support for booting from SD/EMMC"
958 Enabling this will make a U-Boot binary that is capable of being
959 booted via SD/EMMC. This is not a must, some SoCs need this,
963 bool "Support for booting from SD/EMMC and enable QSPI"
965 Enabling this will make a U-Boot binary that is capable of being
966 booted via SD/EMMC while enabling QSPI on the platform as well. This
967 is not a must, some SoCs need this, some not.
970 bool "Support for booting from SPI flash"
972 Enabling this will make a U-Boot binary that is capable of being
973 booted via SPI flash. This is not a must, some SoCs need this,
978 menu "Autoboot options"
984 This enables the autoboot. See doc/README.autoboot for detail.
987 int "delay in seconds before automatically booting"
991 Delay before automatically running bootcmd;
992 set to 0 to autoboot with no delay, but you can stop it by key input.
993 set to -1 to disable autoboot.
994 set to -2 to autoboot with no delay and not check for abort
996 If this value is >= 0 then it is also used for the default delay
997 before starting the default entry in bootmenu. If it is < 0 then
998 a default value of 10s is used.
1000 See doc/README.autoboot for details.
1002 config AUTOBOOT_KEYED
1003 bool "Stop autobooting via specific input key / string"
1005 This option enables stopping (aborting) of the automatic
1006 boot feature only by issuing a specific input key or
1007 string. If not enabled, any input key will abort the
1008 U-Boot automatic booting process and bring the device
1009 to the U-Boot prompt for user input.
1011 config AUTOBOOT_FLUSH_STDIN
1012 bool "Enable flushing stdin before starting to read the password"
1013 depends on AUTOBOOT_KEYED && !SANDBOX
1015 When this option is enabled stdin buffer will be flushed before
1016 starting to read the password.
1017 This can't be enabled for the sandbox as flushing stdin would
1018 break the autoboot unit tests.
1020 config AUTOBOOT_PROMPT
1021 string "Autoboot stop prompt"
1022 depends on AUTOBOOT_KEYED
1023 default "Autoboot in %d seconds\\n"
1025 This string is displayed before the boot delay selected by
1026 CONFIG_BOOTDELAY starts. If it is not defined there is no
1027 output indicating that autoboot is in progress.
1029 Note that this define is used as the (only) argument to a
1030 printf() call, so it may contain '%' format specifications,
1031 provided that it also includes, sepearated by commas exactly
1032 like in a printf statement, the required arguments. It is
1033 the responsibility of the user to select only such arguments
1034 that are valid in the given context.
1036 config AUTOBOOT_ENCRYPTION
1037 bool "Enable encryption in autoboot stopping"
1038 depends on AUTOBOOT_KEYED
1040 This option allows a string to be entered into U-Boot to stop the
1042 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1044 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1045 to the crypt-based functionality and be compared against the
1046 string in the environment variable 'bootstopkeycrypt'.
1047 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1048 and compared against the hash in the environment variable
1049 'bootstopkeysha256'.
1050 If it matches in either case then boot stops and
1051 a command-line prompt is presented.
1052 This provides a way to ship a secure production device which can also
1053 be accessed at the U-Boot command line.
1055 config AUTOBOOT_SHA256_FALLBACK
1056 bool "Allow fallback from crypt-hashed password to sha256"
1057 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1059 This option adds support to fall back from crypt-hashed
1060 passwords to checking a SHA256 hashed password in case the
1061 'bootstopusesha256' environment variable is set to 'true'.
1063 config AUTOBOOT_DELAY_STR
1064 string "Delay autobooting via specific input key / string"
1065 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1067 This option delays the automatic boot feature by issuing
1068 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1069 or the environment variable "bootdelaykey" is specified
1070 and this string is received from console input before
1071 autoboot starts booting, U-Boot gives a command prompt. The
1072 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1073 used, otherwise it never times out.
1075 config AUTOBOOT_STOP_STR
1076 string "Stop autobooting via specific input key / string"
1077 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1079 This option enables stopping (aborting) of the automatic
1080 boot feature only by issuing a specific input key or
1081 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1082 variable "bootstopkey" is specified and this string is
1083 received from console input before autoboot starts booting,
1084 U-Boot gives a command prompt. The U-Boot prompt never
1085 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1087 config AUTOBOOT_KEYED_CTRLC
1088 bool "Enable Ctrl-C autoboot interruption"
1089 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1091 This option allows for the boot sequence to be interrupted
1092 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1093 Setting this variable provides an escape sequence from the
1094 limited "password" strings.
1096 config AUTOBOOT_NEVER_TIMEOUT
1097 bool "Make the password entry never time-out"
1098 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1100 This option removes the timeout from the password entry
1101 when the user first presses the <Enter> key before entering
1102 any other character.
1104 config AUTOBOOT_STOP_STR_ENABLE
1105 bool "Enable fixed string to stop autobooting"
1106 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1108 This option enables the feature to add a fixed stop
1109 string that is defined at compile time.
1110 In every case it will be tried to load the stop
1111 string from the environment.
1112 In case this is enabled and there is no stop string
1113 in the environment, this will be used as default value.
1115 config AUTOBOOT_STOP_STR_CRYPT
1116 string "Stop autobooting via crypt-hashed password"
1117 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1119 This option adds the feature to only stop the autobooting,
1120 and therefore boot into the U-Boot prompt, when the input
1121 string / password matches a values that is hashed via
1122 one of the supported crypt-style password hashing options
1123 and saved in the environment variable "bootstopkeycrypt".
1125 config AUTOBOOT_STOP_STR_SHA256
1126 string "Stop autobooting via SHA256 hashed password"
1127 depends on AUTOBOOT_STOP_STR_ENABLE
1129 This option adds the feature to only stop the autobooting,
1130 and therefore boot into the U-Boot prompt, when the input
1131 string / password matches a values that is encypted via
1132 a SHA256 hash and saved in the environment variable
1133 "bootstopkeysha256". If the value in that variable
1134 includes a ":", the portion prior to the ":" will be treated
1137 config AUTOBOOT_USE_MENUKEY
1138 bool "Allow a specify key to run a menu from the environment"
1139 depends on !AUTOBOOT_KEYED
1141 If a specific key is pressed to stop autoboot, then the commands in
1142 the environment variable 'menucmd' are executed before boot starts.
1144 config AUTOBOOT_MENUKEY
1145 int "ASCII value of boot key to show a menu"
1147 depends on AUTOBOOT_USE_MENUKEY
1149 If this key is pressed to stop autoboot, then the commands in the
1150 environment variable 'menucmd' will be executed before boot starts.
1151 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1154 config AUTOBOOT_MENU_SHOW
1155 bool "Show a menu on boot"
1156 depends on CMD_BOOTMENU
1158 This enables the boot menu, controlled by environment variables
1159 defined by the board. The menu starts after running the 'preboot'
1160 environmnent variable (if enabled) and before handling the boot delay.
1161 See README.bootmenu for more details.
1163 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1164 bool "Disallow bootmenu to enter the U-Boot console"
1165 depends on AUTOBOOT_MENU_SHOW
1167 If this option is enabled, user can not enter the U-Boot console from
1168 bootmenu. It increases the system security.
1171 bool "Boot retry feature"
1173 Allow for having the U-Boot command prompt time out and attempt
1174 to boot again. If the environment variable "bootretry" is found then
1175 its value is used, otherwise the retry timeout is
1176 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1177 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1179 config BOOT_RETRY_TIME
1180 int "Timeout in seconds before attempting to boot again"
1181 depends on BOOT_RETRY
1183 Time in seconds before the U-Boot prompt will timeout and boot will
1186 config BOOT_RETRY_MIN
1187 int "Minimum timeout in seconds for 'bootretry'"
1188 depends on BOOT_RETRY
1189 default BOOT_RETRY_TIME
1191 The minimum time in seconds that "bootretry" can be set to.
1193 config RESET_TO_RETRY
1194 bool "Reset the board to retry autoboot"
1195 depends on BOOT_RETRY
1197 After the countdown timed out, the board will be reset to restart
1202 menu "Image support"
1204 config IMAGE_PRE_LOAD
1205 bool "Image pre-load support"
1207 Enable an image pre-load stage in the SPL.
1208 This pre-load stage allows to do some manipulation
1209 or check (for example signature check) on an image
1210 before launching it.
1212 config SPL_IMAGE_PRE_LOAD
1213 bool "Image pre-load support within SPL"
1214 depends on SPL && IMAGE_PRE_LOAD
1216 Enable an image pre-load stage in the SPL.
1217 This pre-load stage allows to do some manipulation
1218 or check (for example signature check) on an image
1219 before launching it.
1221 config IMAGE_PRE_LOAD_SIG
1222 bool "Image pre-load signature support"
1223 depends on IMAGE_PRE_LOAD
1224 select FIT_SIGNATURE
1226 select RSA_VERIFY_WITH_PKEY
1228 Enable signature check support in the pre-load stage.
1229 For this feature a very simple header is added before
1230 the image with few fields:
1234 All other information (header size, type of signature,
1235 ...) are provided in the node /image/pre-load/sig of
1238 config SPL_IMAGE_PRE_LOAD_SIG
1239 bool "Image pre-load signature support witin SPL"
1240 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1241 select SPL_FIT_SIGNATURE
1243 select SPL_RSA_VERIFY_WITH_PKEY
1245 Enable signature check support in the pre-load stage in the SPL.
1246 For this feature a very simple header is added before
1247 the image with few fields:
1251 All other information (header size, type of signature,
1252 ...) are provided in the node /image/pre-load/sig of
1258 bool "Enable boot arguments"
1260 Provide boot arguments to bootm command. Boot arguments are specified
1261 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1262 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1263 will be undefined and won't take any space in U-Boot image.
1266 string "Boot arguments"
1267 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1269 This can be used to pass arguments to the bootm command. The value of
1270 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1271 this value will also override the "chosen" node in FDT blob.
1273 config BOOTARGS_SUBST
1274 bool "Support substituting strings in boot arguments"
1276 This allows substituting string values in the boot arguments. These
1277 are applied after the commandline has been built.
1279 One use for this is to insert the root-disk UUID into the command
1280 line where bootargs contains "root=${uuid}"
1282 setenv bootargs "console= root=${uuid}"
1283 # Set the 'uuid' environment variable
1284 part uuid mmc 2:2 uuid
1286 # Command-line substitution will put the real uuid into the
1287 # kernel command line
1290 config USE_BOOTCOMMAND
1291 bool "Enable a default value for bootcmd"
1293 Provide a default value for the bootcmd entry in the environment. If
1294 autoboot is enabled this is what will be run automatically. Enable
1295 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1296 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1297 won't take any space in U-Boot image.
1300 string "bootcmd value"
1301 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1302 default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL
1303 default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL
1304 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1306 This is the string of commands that will be used as bootcmd and if
1307 AUTOBOOT is set, automatically run.
1310 bool "Enable preboot"
1312 When this option is enabled, the existence of the environment
1313 variable "preboot" will be checked immediately before starting the
1314 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1315 entering interactive mode.
1317 This feature is especially useful when "preboot" is automatically
1318 generated or modified. For example, the boot code can modify the
1319 "preboot" when a user holds down a certain combination of keys.
1322 string "preboot default value"
1323 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1324 default "usb start" if USB_KEYBOARD
1327 This is the default of "preboot" environment variable.
1329 config DEFAULT_FDT_FILE
1330 string "Default fdt file"
1332 This option is used to set the default fdt file to boot OS.
1334 config SAVE_PREV_BL_FDT_ADDR
1336 bool "Saves fdt address, passed by the previous bootloader, to env var"
1338 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1339 enable this option to save fdt address, passed by the
1340 previous bootloader for future use.
1341 Address is saved to `prevbl_fdt_addr` environment variable.
1343 If no fdt was provided by previous bootloader, no env variables
1346 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1348 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1350 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1351 enable this option to save initramfs address, passed by the
1352 previous bootloader for future use.
1353 Address is saved to `prevbl_initrd_start_addr` environment variable.
1355 If no initramfs was provided by previous bootloader, no env variables