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, the supported "compatible" list is in the
214 doc/uImage.FIT/source_file_format.txt.
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 HAVE_SYS_TEXT_BASE
457 depends on !NIOS2 && !XTENSA
462 depends on HAVE_SYS_TEXT_BASE
463 default 0x0 if POSITION_INDEPENDENT
464 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
465 default 0x81700000 if MACH_SUNIV
466 default 0x2a000000 if MACH_SUN9I
467 default 0x42e00000 if MACH_SUN8I_V3S
468 default 0x4a000000 if ARCH_SUNXI
471 The address in memory that U-Boot will be running from, initially.
473 config HAVE_SYS_MONITOR_BASE
475 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
476 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
480 config SYS_MONITOR_BASE
481 depends on HAVE_SYS_MONITOR_BASE
482 hex "Physical start address of boot monitor code"
483 default SYS_TEXT_BASE
485 The physical start address of boot monitor code (which is the same as
486 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
487 when booting from flash.
489 config SPL_SYS_MONITOR_BASE
490 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
491 hex "Physical start address of SPL monitor code"
492 default SPL_TEXT_BASE
494 config TPL_SYS_MONITOR_BASE
495 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
496 hex "Physical start address of TPL monitor code"
498 config DYNAMIC_SYS_CLK_FREQ
499 bool "Determine CPU clock frequency at run-time"
501 Implement a get_board_sys_clk function that will determine the CPU
502 clock frequency at run time, rather than define it statically.
505 depends on !DYNAMIC_SYS_CLK_FREQ
506 int "CPU clock frequency"
507 default 125000000 if ARCH_LS1012A
508 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
509 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
510 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
511 default 66660000 if ARCH_T2080
512 default 33333333 if RCAR_GEN3
513 default 24000000 if ARCH_EXYNOS
514 default 20000000 if RCAR_GEN2
517 A static value for the CPU frequency. Note that if not required
518 for a given SoC, this can be left at 0.
520 config ARCH_FIXUP_FDT_MEMORY
521 bool "Enable arch_fixup_memory_banks() call"
524 Enable FDT memory map syncup before OS boot. This feature can be
525 used for booting OS with different memory setup where the part of
526 the memory location should be used for different purpose.
529 bool "Support booting Chrome OS"
531 Chrome OS requires U-Boot to set up a table indicating the boot mode
532 (e.g. Developer mode) and a few other things. Enable this if you are
533 booting on a Chromebook to avoid getting an error about an invalid
536 config CHROMEOS_VBOOT
537 bool "Support Chrome OS verified boot"
539 This is intended to enable the full Chrome OS verified boot support
540 in U-Boot. It is not actually implemented in the U-Boot source code
541 at present, so this option is always set to 'n'. It allows
542 distinguishing between booting Chrome OS in a basic way (developer
543 mode) and a full boot.
549 bool "Freescale PBL(pre-boot loader) image format support"
550 select SYS_RAMBOOT if PPC
552 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
553 For more details refer to doc/README.pblimage
556 prompt "Freescale PBL load location"
557 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
558 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
562 bool "Freescale PBL is found on SD card"
565 bool "Freescale PBL is found on SPI flash"
569 config FSL_FIXED_MMC_LOCATION
570 bool "PBL MMC is at a fixed location"
571 depends on SDCARD && !RAMBOOT_PBL
573 config ESDHC_HC_BLK_ADDR
575 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
577 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
578 code length of these soc specify the memory address in block address
579 format. Block length is fixed to 512 bytes as per the SD High
580 Capacity specification.
582 config SYS_FSL_PBL_PBI
583 string "PBI(pre-boot instructions) commands for the PBL image"
584 depends on RAMBOOT_PBL
586 PBI commands can be used to configure SoC before it starts the execution.
587 Please refer doc/README.pblimage for more details.
589 config SYS_FSL_PBL_RCW
590 string "Aadditional RCW (Power on reset configuration) for the PBL image"
591 depends on RAMBOOT_PBL
593 Enables addition of RCW (Power on reset configuration) in built image.
594 Please refer doc/README.pblimage for more details.
596 config SYS_BOOT_RAMDISK_HIGH
597 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
598 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
601 Enable initrd_high functionality. If defined then the initrd_high
602 feature is enabled and the boot* ramdisk subcommand is enabled.
604 endmenu # Boot images
609 bool "Boot timing and reporting"
611 Enable recording of boot time while booting. To use it, insert
612 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
613 bootstage.h. Only a single entry is recorded for each ID. You can
614 give the entry a name with bootstage_mark_name(). You can also
615 record elapsed time in a particular stage using bootstage_start()
616 before starting and bootstage_accum() when finished. Bootstage will
617 add up all the accumulated time and report it.
619 Normally, IDs are defined in bootstage.h but a small number of
620 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
623 Calls to show_boot_progress() will also result in log entries but
624 these will not have names.
627 bool "Boot timing and reported in SPL"
628 depends on BOOTSTAGE && SPL
630 Enable recording of boot time in SPL. To make this visible to U-Boot
631 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
632 information when SPL finishes and load it when U-Boot proper starts
636 bool "Boot timing and reported in TPL"
637 depends on BOOTSTAGE && TPL
639 Enable recording of boot time in SPL. To make this visible to U-Boot
640 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
641 information when TPL finishes and load it when U-Boot proper starts
644 config BOOTSTAGE_REPORT
645 bool "Display a detailed boot timing report before booting the OS"
648 Enable output of a boot time report just before the OS is booted.
649 This shows how long it took U-Boot to go through each stage of the
650 boot process. The report looks something like this:
652 Timer summary in microseconds:
655 3,575,678 3,575,678 board_init_f start
656 3,575,695 17 arch_cpu_init A9
657 3,575,777 82 arch_cpu_init done
658 3,659,598 83,821 board_init_r start
659 3,910,375 250,777 main_loop
660 29,916,167 26,005,792 bootm_start
661 30,361,327 445,160 start_kernel
663 config BOOTSTAGE_RECORD_COUNT
664 int "Number of boot stage records to store"
668 This is the size of the bootstage record list and is the maximum
669 number of bootstage records that can be recorded.
671 config SPL_BOOTSTAGE_RECORD_COUNT
672 int "Number of boot stage records to store for SPL"
673 depends on SPL_BOOTSTAGE
676 This is the size of the bootstage record list and is the maximum
677 number of bootstage records that can be recorded.
679 config TPL_BOOTSTAGE_RECORD_COUNT
680 int "Number of boot stage records to store for TPL"
681 depends on TPL_BOOTSTAGE
684 This is the size of the bootstage record list and is the maximum
685 number of bootstage records that can be recorded.
688 bool "Store boot timing information in the OS device tree"
691 Stash the bootstage information in the FDT. A root 'bootstage'
692 node is created with each bootstage id as a child. Each child
693 has a 'name' property and either 'mark' containing the
694 mark time in microseconds, or 'accum' containing the
695 accumulated time for that bootstage id in microseconds.
700 name = "board_init_f";
709 Code in the Linux kernel can find this in /proc/devicetree.
711 config BOOTSTAGE_STASH
712 bool "Stash the boot timing information in memory before booting OS"
715 Some OSes do not support device tree. Bootstage can instead write
716 the boot timing information in a binary format at a given address.
717 This happens through a call to bootstage_stash(), typically in
718 the CPU's cleanup_before_linux() function. You can use the
719 'bootstage stash' and 'bootstage unstash' commands to do this on
722 config BOOTSTAGE_STASH_ADDR
723 hex "Address to stash boot timing information"
726 Provide an address which will not be overwritten by the OS when it
727 starts, so that it can read this information when ready.
729 config BOOTSTAGE_STASH_SIZE
730 hex "Size of boot timing stash region"
733 This should be large enough to hold the bootstage stash. A value of
734 4096 (4KiB) is normally plenty.
736 config SHOW_BOOT_PROGRESS
737 bool "Show boot progress in a board-specific manner"
739 Defining this option allows to add some board-specific code (calling
740 a user-provided function show_boot_progress(int) that enables you to
741 show the system's boot progress on some display (for example, some
742 LEDs) on your board. At the moment, the following checkpoints are
745 Legacy uImage format:
748 1 common/cmd_bootm.c before attempting to boot an image
749 -1 common/cmd_bootm.c Image header has bad magic number
750 2 common/cmd_bootm.c Image header has correct magic number
751 -2 common/cmd_bootm.c Image header has bad checksum
752 3 common/cmd_bootm.c Image header has correct checksum
753 -3 common/cmd_bootm.c Image data has bad checksum
754 4 common/cmd_bootm.c Image data has correct checksum
755 -4 common/cmd_bootm.c Image is for unsupported architecture
756 5 common/cmd_bootm.c Architecture check OK
757 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
758 6 common/cmd_bootm.c Image Type check OK
759 -6 common/cmd_bootm.c gunzip uncompression error
760 -7 common/cmd_bootm.c Unimplemented compression type
761 7 common/cmd_bootm.c Uncompression OK
762 8 common/cmd_bootm.c No uncompress/copy overwrite error
763 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
765 9 common/image.c Start initial ramdisk verification
766 -10 common/image.c Ramdisk header has bad magic number
767 -11 common/image.c Ramdisk header has bad checksum
768 10 common/image.c Ramdisk header is OK
769 -12 common/image.c Ramdisk data has bad checksum
770 11 common/image.c Ramdisk data has correct checksum
771 12 common/image.c Ramdisk verification complete, start loading
772 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
773 13 common/image.c Start multifile image verification
774 14 common/image.c No initial ramdisk, no multifile, continue.
776 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
778 -30 arch/powerpc/lib/board.c Fatal error, hang the system
779 -31 post/post.c POST test failed, detected by post_output_backlog()
780 -32 post/post.c POST test failed, detected by post_run_single()
782 34 common/cmd_doc.c before loading a Image from a DOC device
783 -35 common/cmd_doc.c Bad usage of "doc" command
784 35 common/cmd_doc.c correct usage of "doc" command
785 -36 common/cmd_doc.c No boot device
786 36 common/cmd_doc.c correct boot device
787 -37 common/cmd_doc.c Unknown Chip ID on boot device
788 37 common/cmd_doc.c correct chip ID found, device available
789 -38 common/cmd_doc.c Read Error on boot device
790 38 common/cmd_doc.c reading Image header from DOC device OK
791 -39 common/cmd_doc.c Image header has bad magic number
792 39 common/cmd_doc.c Image header has correct magic number
793 -40 common/cmd_doc.c Error reading Image from DOC device
794 40 common/cmd_doc.c Image header has correct magic number
795 41 common/cmd_ide.c before loading a Image from a IDE device
796 -42 common/cmd_ide.c Bad usage of "ide" command
797 42 common/cmd_ide.c correct usage of "ide" command
798 -43 common/cmd_ide.c No boot device
799 43 common/cmd_ide.c boot device found
800 -44 common/cmd_ide.c Device not available
801 44 common/cmd_ide.c Device available
802 -45 common/cmd_ide.c wrong partition selected
803 45 common/cmd_ide.c partition selected
804 -46 common/cmd_ide.c Unknown partition table
805 46 common/cmd_ide.c valid partition table found
806 -47 common/cmd_ide.c Invalid partition type
807 47 common/cmd_ide.c correct partition type
808 -48 common/cmd_ide.c Error reading Image Header on boot device
809 48 common/cmd_ide.c reading Image Header from IDE device OK
810 -49 common/cmd_ide.c Image header has bad magic number
811 49 common/cmd_ide.c Image header has correct magic number
812 -50 common/cmd_ide.c Image header has bad checksum
813 50 common/cmd_ide.c Image header has correct checksum
814 -51 common/cmd_ide.c Error reading Image from IDE device
815 51 common/cmd_ide.c reading Image from IDE device OK
816 52 common/cmd_nand.c before loading a Image from a NAND device
817 -53 common/cmd_nand.c Bad usage of "nand" command
818 53 common/cmd_nand.c correct usage of "nand" command
819 -54 common/cmd_nand.c No boot device
820 54 common/cmd_nand.c boot device found
821 -55 common/cmd_nand.c Unknown Chip ID on boot device
822 55 common/cmd_nand.c correct chip ID found, device available
823 -56 common/cmd_nand.c Error reading Image Header on boot device
824 56 common/cmd_nand.c reading Image Header from NAND device OK
825 -57 common/cmd_nand.c Image header has bad magic number
826 57 common/cmd_nand.c Image header has correct magic number
827 -58 common/cmd_nand.c Error reading Image from NAND device
828 58 common/cmd_nand.c reading Image from NAND device OK
830 -60 common/env_common.c Environment has a bad CRC, using default
832 64 net/eth.c starting with Ethernet configuration.
833 -64 net/eth.c no Ethernet found.
834 65 net/eth.c Ethernet found.
836 -80 common/cmd_net.c usage wrong
837 80 common/cmd_net.c before calling net_loop()
838 -81 common/cmd_net.c some error in net_loop() occurred
839 81 common/cmd_net.c net_loop() back without error
840 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
841 82 common/cmd_net.c trying automatic boot
842 83 common/cmd_net.c running "source" command
843 -83 common/cmd_net.c some error in automatic boot or "source" command
844 84 common/cmd_net.c end without errors
849 100 common/cmd_bootm.c Kernel FIT Image has correct format
850 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
851 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
852 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
853 102 common/cmd_bootm.c Kernel unit name specified
854 -103 common/cmd_bootm.c Can't get kernel subimage node offset
855 103 common/cmd_bootm.c Found configuration node
856 104 common/cmd_bootm.c Got kernel subimage node offset
857 -104 common/cmd_bootm.c Kernel subimage hash verification failed
858 105 common/cmd_bootm.c Kernel subimage hash verification OK
859 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
860 106 common/cmd_bootm.c Architecture check OK
861 -106 common/cmd_bootm.c Kernel subimage has wrong type
862 107 common/cmd_bootm.c Kernel subimage type OK
863 -107 common/cmd_bootm.c Can't get kernel subimage data/size
864 108 common/cmd_bootm.c Got kernel subimage data/size
865 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
866 -109 common/cmd_bootm.c Can't get kernel subimage type
867 -110 common/cmd_bootm.c Can't get kernel subimage comp
868 -111 common/cmd_bootm.c Can't get kernel subimage os
869 -112 common/cmd_bootm.c Can't get kernel subimage load address
870 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
872 120 common/image.c Start initial ramdisk verification
873 -120 common/image.c Ramdisk FIT image has incorrect format
874 121 common/image.c Ramdisk FIT image has correct format
875 122 common/image.c No ramdisk subimage unit name, using configuration
876 -122 common/image.c Can't get configuration for ramdisk subimage
877 123 common/image.c Ramdisk unit name specified
878 -124 common/image.c Can't get ramdisk subimage node offset
879 125 common/image.c Got ramdisk subimage node offset
880 -125 common/image.c Ramdisk subimage hash verification failed
881 126 common/image.c Ramdisk subimage hash verification OK
882 -126 common/image.c Ramdisk subimage for unsupported architecture
883 127 common/image.c Architecture check OK
884 -127 common/image.c Can't get ramdisk subimage data/size
885 128 common/image.c Got ramdisk subimage data/size
886 129 common/image.c Can't get ramdisk load address
887 -129 common/image.c Got ramdisk load address
889 -130 common/cmd_doc.c Incorrect FIT image format
890 131 common/cmd_doc.c FIT image format OK
892 -140 common/cmd_ide.c Incorrect FIT image format
893 141 common/cmd_ide.c FIT image format OK
895 -150 common/cmd_nand.c Incorrect FIT image format
896 151 common/cmd_nand.c FIT image format OK
898 config SPL_SHOW_BOOT_PROGRESS
899 bool "Show boot progress in a board-specific manner in SPL"
902 Defining this option allows to add some board-specific code (calling
903 a user-provided function show_boot_progress(int) that enables you to
904 show the system's boot progress on some display (for example, some
905 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
912 bool "Support for booting from NOR flash"
915 Enabling this will make a U-Boot binary that is capable of being
916 booted via NOR. In this case we will enable certain pinmux early
917 as the ROM only partially sets up pinmux. We also default to using
921 bool "Support for booting from NAND flash"
924 Enabling this will make a U-Boot binary that is capable of being
925 booted via NAND flash. This is not a must, some SoCs need this,
929 bool "Support for booting from ONENAND"
932 Enabling this will make a U-Boot binary that is capable of being
933 booted via ONENAND. This is not a must, some SoCs need this,
937 bool "Support for booting from QSPI flash"
939 Enabling this will make a U-Boot binary that is capable of being
940 booted via QSPI flash. This is not a must, some SoCs need this,
944 bool "Support for booting from SATA"
946 Enabling this will make a U-Boot binary that is capable of being
947 booted via SATA. This is not a must, some SoCs need this,
951 bool "Support for booting from SD/EMMC"
953 Enabling this will make a U-Boot binary that is capable of being
954 booted via SD/EMMC. This is not a must, some SoCs need this,
958 bool "Support for booting from SD/EMMC and enable QSPI"
960 Enabling this will make a U-Boot binary that is capable of being
961 booted via SD/EMMC while enabling QSPI on the platform as well. This
962 is not a must, some SoCs need this, some not.
965 bool "Support for booting from SPI flash"
967 Enabling this will make a U-Boot binary that is capable of being
968 booted via SPI flash. This is not a must, some SoCs need this,
973 menu "Autoboot options"
979 This enables the autoboot. See doc/README.autoboot for detail.
982 int "delay in seconds before automatically booting"
986 Delay before automatically running bootcmd;
987 set to 0 to autoboot with no delay, but you can stop it by key input.
988 set to -1 to disable autoboot.
989 set to -2 to autoboot with no delay and not check for abort
991 If this value is >= 0 then it is also used for the default delay
992 before starting the default entry in bootmenu. If it is < 0 then
993 a default value of 10s is used.
995 See doc/README.autoboot for details.
997 config AUTOBOOT_KEYED
998 bool "Stop autobooting via specific input key / string"
1000 This option enables stopping (aborting) of the automatic
1001 boot feature only by issuing a specific input key or
1002 string. If not enabled, any input key will abort the
1003 U-Boot automatic booting process and bring the device
1004 to the U-Boot prompt for user input.
1006 config AUTOBOOT_FLUSH_STDIN
1007 bool "Enable flushing stdin before starting to read the password"
1008 depends on AUTOBOOT_KEYED && !SANDBOX
1010 When this option is enabled stdin buffer will be flushed before
1011 starting to read the password.
1012 This can't be enabled for the sandbox as flushing stdin would
1013 break the autoboot unit tests.
1015 config AUTOBOOT_PROMPT
1016 string "Autoboot stop prompt"
1017 depends on AUTOBOOT_KEYED
1018 default "Autoboot in %d seconds\\n"
1020 This string is displayed before the boot delay selected by
1021 CONFIG_BOOTDELAY starts. If it is not defined there is no
1022 output indicating that autoboot is in progress.
1024 Note that this define is used as the (only) argument to a
1025 printf() call, so it may contain '%' format specifications,
1026 provided that it also includes, sepearated by commas exactly
1027 like in a printf statement, the required arguments. It is
1028 the responsibility of the user to select only such arguments
1029 that are valid in the given context.
1031 config AUTOBOOT_ENCRYPTION
1032 bool "Enable encryption in autoboot stopping"
1033 depends on AUTOBOOT_KEYED
1035 This option allows a string to be entered into U-Boot to stop the
1037 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1039 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1040 to the crypt-based functionality and be compared against the
1041 string in the environment variable 'bootstopkeycrypt'.
1042 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1043 and compared against the hash in the environment variable
1044 'bootstopkeysha256'.
1045 If it matches in either case then boot stops and
1046 a command-line prompt is presented.
1047 This provides a way to ship a secure production device which can also
1048 be accessed at the U-Boot command line.
1050 config AUTOBOOT_SHA256_FALLBACK
1051 bool "Allow fallback from crypt-hashed password to sha256"
1052 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1054 This option adds support to fall back from crypt-hashed
1055 passwords to checking a SHA256 hashed password in case the
1056 'bootstopusesha256' environment variable is set to 'true'.
1058 config AUTOBOOT_DELAY_STR
1059 string "Delay autobooting via specific input key / string"
1060 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1062 This option delays the automatic boot feature by issuing
1063 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1064 or the environment variable "bootdelaykey" is specified
1065 and this string is received from console input before
1066 autoboot starts booting, U-Boot gives a command prompt. The
1067 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1068 used, otherwise it never times out.
1070 config AUTOBOOT_STOP_STR
1071 string "Stop autobooting via specific input key / string"
1072 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1074 This option enables stopping (aborting) of the automatic
1075 boot feature only by issuing a specific input key or
1076 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1077 variable "bootstopkey" is specified and this string is
1078 received from console input before autoboot starts booting,
1079 U-Boot gives a command prompt. The U-Boot prompt never
1080 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1082 config AUTOBOOT_KEYED_CTRLC
1083 bool "Enable Ctrl-C autoboot interruption"
1084 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1086 This option allows for the boot sequence to be interrupted
1087 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1088 Setting this variable provides an escape sequence from the
1089 limited "password" strings.
1091 config AUTOBOOT_NEVER_TIMEOUT
1092 bool "Make the password entry never time-out"
1093 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1095 This option removes the timeout from the password entry
1096 when the user first presses the <Enter> key before entering
1097 any other character.
1099 config AUTOBOOT_STOP_STR_ENABLE
1100 bool "Enable fixed string to stop autobooting"
1101 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1103 This option enables the feature to add a fixed stop
1104 string that is defined at compile time.
1105 In every case it will be tried to load the stop
1106 string from the environment.
1107 In case this is enabled and there is no stop string
1108 in the environment, this will be used as default value.
1110 config AUTOBOOT_STOP_STR_CRYPT
1111 string "Stop autobooting via crypt-hashed password"
1112 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1114 This option adds the feature to only stop the autobooting,
1115 and therefore boot into the U-Boot prompt, when the input
1116 string / password matches a values that is hashed via
1117 one of the supported crypt-style password hashing options
1118 and saved in the environment variable "bootstopkeycrypt".
1120 config AUTOBOOT_STOP_STR_SHA256
1121 string "Stop autobooting via SHA256 hashed password"
1122 depends on AUTOBOOT_STOP_STR_ENABLE
1124 This option adds the feature to only stop the autobooting,
1125 and therefore boot into the U-Boot prompt, when the input
1126 string / password matches a values that is encypted via
1127 a SHA256 hash and saved in the environment variable
1128 "bootstopkeysha256". If the value in that variable
1129 includes a ":", the portion prior to the ":" will be treated
1132 config AUTOBOOT_USE_MENUKEY
1133 bool "Allow a specify key to run a menu from the environment"
1134 depends on !AUTOBOOT_KEYED
1136 If a specific key is pressed to stop autoboot, then the commands in
1137 the environment variable 'menucmd' are executed before boot starts.
1139 config AUTOBOOT_MENUKEY
1140 int "ASCII value of boot key to show a menu"
1142 depends on AUTOBOOT_USE_MENUKEY
1144 If this key is pressed to stop autoboot, then the commands in the
1145 environment variable 'menucmd' will be executed before boot starts.
1146 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1149 config AUTOBOOT_MENU_SHOW
1150 bool "Show a menu on boot"
1151 depends on CMD_BOOTMENU
1153 This enables the boot menu, controlled by environment variables
1154 defined by the board. The menu starts after running the 'preboot'
1155 environmnent variable (if enabled) and before handling the boot delay.
1156 See README.bootmenu for more details.
1158 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1159 bool "Disallow bootmenu to enter the U-Boot console"
1160 depends on AUTOBOOT_MENU_SHOW
1162 If this option is enabled, user can not enter the U-Boot console from
1163 bootmenu. It increases the system security.
1166 bool "Boot retry feature"
1168 Allow for having the U-Boot command prompt time out and attempt
1169 to boot again. If the environment variable "bootretry" is found then
1170 its value is used, otherwise the retry timeout is
1171 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1172 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1174 config BOOT_RETRY_TIME
1175 int "Timeout in seconds before attempting to boot again"
1176 depends on BOOT_RETRY
1178 Time in seconds before the U-Boot prompt will timeout and boot will
1181 config BOOT_RETRY_MIN
1182 int "Minimum timeout in seconds for 'bootretry'"
1183 depends on BOOT_RETRY
1184 default BOOT_RETRY_TIME
1186 The minimum time in seconds that "bootretry" can be set to.
1188 config RESET_TO_RETRY
1189 bool "Reset the board to retry autoboot"
1190 depends on BOOT_RETRY
1192 After the countdown timed out, the board will be reset to restart
1197 menu "Image support"
1199 config IMAGE_PRE_LOAD
1200 bool "Image pre-load support"
1202 Enable an image pre-load stage in the SPL.
1203 This pre-load stage allows to do some manipulation
1204 or check (for example signature check) on an image
1205 before launching it.
1207 config SPL_IMAGE_PRE_LOAD
1208 bool "Image pre-load support within SPL"
1209 depends on SPL && IMAGE_PRE_LOAD
1211 Enable an image pre-load stage in the SPL.
1212 This pre-load stage allows to do some manipulation
1213 or check (for example signature check) on an image
1214 before launching it.
1216 config IMAGE_PRE_LOAD_SIG
1217 bool "Image pre-load signature support"
1218 depends on IMAGE_PRE_LOAD
1219 select FIT_SIGNATURE
1221 select RSA_VERIFY_WITH_PKEY
1223 Enable signature check support in the pre-load stage.
1224 For this feature a very simple header is added before
1225 the image with few fields:
1229 All other information (header size, type of signature,
1230 ...) are provided in the node /image/pre-load/sig of
1233 config SPL_IMAGE_PRE_LOAD_SIG
1234 bool "Image pre-load signature support witin SPL"
1235 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1236 select SPL_FIT_SIGNATURE
1238 select SPL_RSA_VERIFY_WITH_PKEY
1240 Enable signature check support in the pre-load stage in the SPL.
1241 For this feature a very simple header is added before
1242 the image with few fields:
1246 All other information (header size, type of signature,
1247 ...) are provided in the node /image/pre-load/sig of
1253 bool "Enable boot arguments"
1255 Provide boot arguments to bootm command. Boot arguments are specified
1256 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1257 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1258 will be undefined and won't take any space in U-Boot image.
1261 string "Boot arguments"
1262 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1264 This can be used to pass arguments to the bootm command. The value of
1265 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1266 this value will also override the "chosen" node in FDT blob.
1268 config BOOTARGS_SUBST
1269 bool "Support substituting strings in boot arguments"
1271 This allows substituting string values in the boot arguments. These
1272 are applied after the commandline has been built.
1274 One use for this is to insert the root-disk UUID into the command
1275 line where bootargs contains "root=${uuid}"
1277 setenv bootargs "console= root=${uuid}"
1278 # Set the 'uuid' environment variable
1279 part uuid mmc 2:2 uuid
1281 # Command-line substitution will put the real uuid into the
1282 # kernel command line
1285 config USE_BOOTCOMMAND
1286 bool "Enable a default value for bootcmd"
1288 Provide a default value for the bootcmd entry in the environment. If
1289 autoboot is enabled this is what will be run automatically. Enable
1290 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1291 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1292 won't take any space in U-Boot image.
1295 string "bootcmd value"
1296 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1297 default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL
1298 default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL
1299 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1301 This is the string of commands that will be used as bootcmd and if
1302 AUTOBOOT is set, automatically run.
1305 bool "Enable preboot"
1307 When this option is enabled, the existence of the environment
1308 variable "preboot" will be checked immediately before starting the
1309 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1310 entering interactive mode.
1312 This feature is especially useful when "preboot" is automatically
1313 generated or modified. For example, the boot code can modify the
1314 "preboot" when a user holds down a certain combination of keys.
1317 string "preboot default value"
1318 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1319 default "usb start" if USB_KEYBOARD
1322 This is the default of "preboot" environment variable.
1324 config DEFAULT_FDT_FILE
1325 string "Default fdt file"
1327 This option is used to set the default fdt file to boot OS.
1329 config SAVE_PREV_BL_FDT_ADDR
1331 bool "Saves fdt address, passed by the previous bootloader, to env var"
1333 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1334 enable this option to save fdt address, passed by the
1335 previous bootloader for future use.
1336 Address is saved to `prevbl_fdt_addr` environment variable.
1338 If no fdt was provided by previous bootloader, no env variables
1341 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1343 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1345 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1346 enable this option to save initramfs address, passed by the
1347 previous bootloader for future use.
1348 Address is saved to `prevbl_initrd_start_addr` environment variable.
1350 If no initramfs was provided by previous bootloader, no env variables