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'
39 config FIT_EXTERNAL_OFFSET
40 hex "FIT external data offset"
44 This specifies a data offset in fit image.
45 The offset is from data payload offset to the beginning of
46 fit image header. When specifies a offset, specific data
47 could be put in the hole between data payload and fit image
48 header, such as CSF data on i.MX platform.
51 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"
110 Generally a system will have valid FIT images so debug messages
111 are a waste of code space. If you are debugging your images then
112 you can enable this option to get more verbose information about
115 config FIT_BEST_MATCH
116 bool "Select the best match for the kernel device tree"
119 When no configuration is explicitly selected, default to the
120 one whose fdt's compatibility field best matches that of
121 U-Boot itself. A match is considered "best" if it matches the
122 most specific compatibility entry of U-Boot's fdt's root node.
123 The order of entries in the configuration's fdt is ignored.
125 config FIT_IMAGE_POST_PROCESS
126 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
128 depends on SOCFPGA_SECURE_VAB_AUTH
130 Allows doing any sort of manipulation to blobs after they got extracted
131 from FIT images like stripping off headers or modifying the size of the
132 blob, verification, authentication, decryption etc. in a platform or
133 board specific way. In order to use this feature a platform or board-
134 specific implementation of board_fit_image_post_process() must be
135 provided. Also, anything done during this post-processing step would
136 need to be comprehended in how the images were prepared before being
137 injected into the FIT creation (i.e. the blobs would have been pre-
138 processed before being added to the FIT image).
141 bool "Support FIT printing"
145 Support printing the content of the fitImage in a verbose manner.
148 bool "Support Flattened Image Tree within SPL"
149 depends on SPL && FIT
154 bool "Support FIT printing within SPL"
157 Support printing the content of the fitImage in a verbose manner in SPL.
159 config SPL_FIT_FULL_CHECK
160 bool "Do a full check of the FIT before using it"
163 Enable this do a full check of the FIT to make sure it is valid. This
164 helps to protect against carefully crafted FITs which take advantage
165 of bugs or omissions in the code. This includes a bad structure,
166 multiple root nodes and the like.
168 config SPL_FIT_SIGNATURE
169 bool "Enable signature verification of FIT firmware within SPL"
171 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
178 select SPL_IMAGE_SIGN_INFO
179 select SPL_FIT_FULL_CHECK
181 config SPL_FIT_SIGNATURE_MAX_SIZE
182 hex "Max size of signed FIT structures in SPL"
183 depends on SPL_FIT_SIGNATURE
186 This option sets a max size in bytes for verified FIT uImages.
187 A sane value of 256MB protects corrupted DTB structures from overlapping
188 device memory. Assure this size does not extend past expected storage
191 config SPL_FIT_RSASSA_PSS
192 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
193 depends on SPL_FIT_SIGNATURE
195 Enable this to support the pss padding algorithm as described
196 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
199 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
200 depends on SPL && FIT
203 Normally with the SPL framework a legacy image is generated as part
204 of the build. This contains U-Boot along with information as to
205 where it should be loaded. This option instead enables generation
206 of a FIT (Flat Image Tree) which provides more flexibility. In
207 particular it can handle selecting from multiple device tree
208 and passing the correct one to U-Boot.
210 This path has the following limitations:
212 1. "loadables" images, other than FDTs, which do not have a "load"
213 property will not be loaded. This limitation also applies to FPGA
214 images with the correct "compatible" string.
215 2. For FPGA images, the supported "compatible" list is in the
216 doc/uImage.FIT/source_file_format.txt.
217 3. FDTs are only loaded for images with an "os" property of "u-boot".
218 "linux" images are also supported with Falcon boot mode.
220 config SPL_LOAD_FIT_ADDRESS
221 hex "load address of fit image"
222 depends on SPL_LOAD_FIT || SPL_RAM_SUPPORT || TPL_RAM_SUPPORT
225 Specify the load address of the fit image that will be loaded
228 config SPL_LOAD_FIT_APPLY_OVERLAY
229 bool "Enable SPL applying DT overlays from FIT"
230 depends on SPL_LOAD_FIT
231 select OF_LIBFDT_OVERLAY
233 The device tree is loaded from the FIT image. Allow the SPL to
234 also load device-tree overlays from the FIT image an apply them
235 over the device tree.
237 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
238 depends on SPL_LOAD_FIT_APPLY_OVERLAY
240 hex "size of temporary buffer used to load the overlays"
242 The size of the area where the overlays will be loaded and
243 uncompress. Must be at least as large as biggest overlay
246 config SPL_LOAD_FIT_FULL
247 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
251 Normally with the SPL framework a legacy image is generated as part
252 of the build. This contains U-Boot along with information as to
253 where it should be loaded. This option instead enables generation
254 of a FIT (Flat Image Tree) which provides more flexibility. In
255 particular it can handle selecting from multiple device tree
256 and passing the correct one to U-Boot.
258 config SPL_FIT_IMAGE_POST_PROCESS
259 bool "Enable post-processing of FIT artifacts after loading by the SPL"
260 depends on SPL_LOAD_FIT
261 default y if TI_SECURE_DEVICE
263 Allows doing any sort of manipulation to blobs after they got extracted
264 from the U-Boot FIT image like stripping off headers or modifying the
265 size of the blob, verification, authentication, decryption etc. in a
266 platform or board specific way. In order to use this feature a platform
267 or board-specific implementation of board_fit_image_post_process() must
268 be provided. Also, anything done during this post-processing step would
269 need to be comprehended in how the images were prepared before being
270 injected into the FIT creation (i.e. the blobs would have been pre-
271 processed before being added to the FIT image).
273 config SPL_FIT_SOURCE
274 string ".its source file for U-Boot FIT image"
277 Specifies a (platform specific) FIT source file to generate the
278 U-Boot FIT image. This could specify further image to load and/or
281 config USE_SPL_FIT_GENERATOR
282 bool "Use a script to generate the .its script"
284 default y if SPL_FIT && ARCH_ZYNQMP
286 config SPL_FIT_GENERATOR
287 string ".its file generator script for U-Boot FIT image"
288 depends on USE_SPL_FIT_GENERATOR
289 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
291 Specifies a (platform specific) script file to generate the FIT
292 source file used to build the U-Boot FIT image file. This gets
293 passed a list of supported device tree file stub names to
294 include in the generated image.
299 bool "Support Flattened Image Tree within VPL"
306 bool "Support FIT printing within VPL"
310 Support printing the content of the fitImage in a verbose manner in VPL.
312 config VPL_FIT_FULL_CHECK
313 bool "Do a full check of the FIT before using it"
316 Enable this do a full check of the FIT to make sure it is valid. This
317 helps to protect against carefully crafted FITs which take advantage
318 of bugs or omissions in the code. This includes a bad structure,
319 multiple root nodes and the like.
321 config VPL_FIT_SIGNATURE
322 bool "Enable signature verification of FIT firmware within VPL"
331 select VPL_IMAGE_SIGN_INFO
332 select VPL_FIT_FULL_CHECK
334 config VPL_FIT_SIGNATURE_MAX_SIZE
335 hex "Max size of signed FIT structures in VPL"
336 depends on VPL_FIT_SIGNATURE
339 This option sets a max size in bytes for verified FIT uImages.
340 A sane value of 256MB protects corrupted DTB structures from overlapping
341 device memory. Assure this size does not extend past expected storage
350 Utilities for parsing PXE file formats.
353 bool # Common defaults for standard boot and distroboot
354 imply USE_BOOTCOMMAND
355 select CMD_ENV_EXISTS
359 select CMD_FS_GENERIC
360 select CMD_PART if PARTITIONS
361 select CMD_DHCP if CMD_NET
362 select CMD_PING if CMD_NET
363 select CMD_PXE if CMD_NET
364 select SUPPORT_RAW_INITRD
365 select ENV_VARS_UBOOT_CONFIG
366 select CMD_BOOTI if ARM64
367 select CMD_BOOTZ if ARM && !ARM64
373 These are not required but are commonly needed to support a good
374 selection of booting methods. Enable this to improve the capability
375 of U-Boot to boot various images. Currently much functionality is
376 tied to enabling the command that exercises it.
379 bool "Standard boot support"
381 depends on DM && OF_CONTROL && BLK
383 U-Boot supports a standard way of locating something to boot,
384 typically an Operating System such as Linux, provided by a distro such
385 as Arch Linux or Debian. Enable this to support iterating through
386 available bootdevs and using bootmeths to find bootflows suitable for
389 Standard boot is not a standard way of booting, just a framework
390 within U-Boot for supporting all the different ways that exist.
394 - bootdev - a device which can hold a distro (e.g. MMC)
395 - bootmeth - a method to scan a bootdev to find bootflows (owned by
397 - bootflow - a description of how to boot (owned by the distro)
400 bool "Standard boot support in SPL"
401 depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK
404 This enables standard boot in SPL. This is neeeded so that VBE
405 (Verified Boot for Embedded) can be used, since it depends on standard
406 boot. It is enabled by default since the main purpose of VPL is to
407 handle the firmware part of VBE.
410 bool "Standard boot support in VPL"
411 depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK
414 This enables standard boot in SPL. This is neeeded so that VBE
415 (Verified Boot for Embedded) can be used, since it depends on standard
416 boot. It is enabled by default since the main purpose of VPL is to
417 handle the firmware part of VBE.
422 bool "Enhanced features for standard boot"
425 This enables various useful features for standard boot, which are not
426 essential for operation:
428 - bootdev, bootmeth commands
429 - extra features in the bootflow command
430 - support for selecting the ordering of bootmeths ("bootmeth order")
431 - support for selecting the ordering of bootdevs using the devicetree
432 as well as the "boot_targets" environment variable
434 config BOOTSTD_DEFAULTS
435 bool "Select some common defaults for standard boot"
437 imply USE_BOOTCOMMAND
439 select BOOTMETH_DISTRO
441 These are not required but are commonly needed to support a good
442 selection of booting methods. Enable this to improve the capability
443 of U-Boot to boot various images.
445 config BOOTSTD_BOOTCOMMAND
446 bool "Use bootstd to boot"
447 default y if !DISTRO_DEFAULTS
449 Enable this to select a default boot-command suitable for booting
450 with standard boot. This can be overridden by the board if needed,
451 but the default command should be enough for most boards which use
454 For now this is only selected if distro boot is NOT used, since
455 standard boot does not support all of the features of distro boot
458 config BOOTMETH_GLOBAL
461 Add support for global bootmeths. This feature is used by VBE and
462 EFI bootmgr, since they take full control over which bootdevs are
466 bool "Bootdev support for Chromium OS"
467 depends on X86 || SANDBOX
470 Enables support for booting Chromium OS using bootdevs. This uses the
471 kernel A slot and obtains the kernel command line from the parameters
474 Note that only x86 devices are supported at present.
476 config BOOTMETH_EXTLINUX
477 bool "Bootdev support for extlinux boot"
481 Enables support for extlinux boot using bootdevs. This makes the
482 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
485 The specification for this filed is here:
487 https://uapi-group.org/specifications/specs/boot_loader_specification/
489 This provides a way to try out standard boot on an existing boot flow.
491 config BOOTMETH_EXTLINUX_PXE
492 bool "Bootdev support for extlinux boot over network"
493 depends on CMD_PXE && CMD_NET && DM_ETH
496 Enables support for extlinux boot using bootdevs. This makes the
497 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
499 The specification for this file is here:
501 https://uapi-group.org/specifications/specs/boot_loader_specification/
503 This provides a way to try out standard boot on an existing boot flow.
505 config BOOTMETH_EFILOADER
506 bool "Bootdev support for EFI boot"
507 depends on EFI_LOADER
510 Enables support for EFI boot using bootdevs. This makes the
511 bootdevs look for a 'boot<arch>.efi' on each filesystem
512 they scan. The resulting file is booted after enabling U-Boot's
515 The <arch> depends on the architecture of the board:
517 aa64 - aarch64 (ARM 64-bit)
521 riscv32 - RISC-V 32-bit
522 riscv64 - RISC-V 64-bit
524 This provides a way to try out standard boot on an existing boot flow.
527 bool "Bootdev support for Verified Boot for Embedded"
530 select BOOTMETH_GLOBAL
533 Enables support for VBE boot. This is a standard boot method which
534 supports selection of various firmware components, seleciton of an OS to
535 boot as well as updating these using fwupd.
537 config BOOTMETH_DISTRO
538 bool # Options needed to boot any distro
539 select BOOTMETH_SCRIPT # E.g. Armbian uses scripts
540 select BOOTMETH_EXTLINUX # E.g. Debian uses these
541 select BOOTMETH_EXTLINUX_PXE if CMD_PXE && CMD_NET && DM_ETH
542 select BOOTMETH_EFILOADER if EFI_LOADER # E.g. Ubuntu uses this
544 config SPL_BOOTMETH_VBE
545 bool "Bootdev support for Verified Boot for Embedded (SPL)"
546 depends on SPL && FIT
550 Enables support for VBE boot. This is a standard boot method which
551 supports selection of various firmware components, seleciton of an OS to
552 boot as well as updating these using fwupd.
554 config VPL_BOOTMETH_VBE
555 bool "Bootdev support for Verified Boot for Embedded (VPL)"
556 depends on VPL && FIT
560 Enables support for VBE boot. This is a standard boot method which
561 supports selection of various firmware components, seleciton of an OS to
562 boot as well as updating these using fwupd.
566 config BOOTMETH_VBE_REQUEST
567 bool "Support for serving VBE OS requests"
570 Enables support for looking that the requests made by the
571 Operating System being booted. These requests result in additions to
572 the device tree /chosen node, added during the device tree fixup
575 config SPL_BOOTMETH_VBE_REQUEST
576 bool "Support for serving VBE OS requests (SPL)"
579 Enables support for looking that the requests made by the
580 Operating System being booted. These requests result in additions to
581 the device tree /chosen node, added during the device tree fixup
584 This is only useful if you are booting an OS direct from SPL.
586 config BOOTMETH_VBE_SIMPLE
587 bool "Bootdev support for VBE 'simple' method"
590 Enables support for VBE 'simple' boot. This allows updating a single
591 firmware image in boot media such as MMC. It does not support any sort
592 of rollback, recovery or A/B boot.
594 config BOOTMETH_VBE_SIMPLE_OS
595 bool "Bootdev support for VBE 'simple' method OS phase"
598 Enables support for the OS parts of VBE 'simple' boot. This includes
599 fixing up the device tree with the required VBE information, ready
600 for booting into the OS. This option is only enabled for U-Boot
601 proper, since it is the phase where device tree fixups happen.
603 config SPL_BOOTMETH_VBE_SIMPLE
604 bool "Bootdev support for VBE 'simple' method (SPL)"
608 Enables support for VBE 'simple' boot. This allows updating a single
609 firmware image in boot media such as MMC. It does not support any sort
610 of rollback, recovery or A/B boot.
612 config VPL_BOOTMETH_VBE_SIMPLE
613 bool "Bootdev support for VBE 'simple' method (VPL)"
617 Enables support for VBE 'simple' boot. This allows updating a single
618 firmware image in boot media such as MMC. It does not support any sort
619 of rollback, recovery or A/B boot.
621 config SPL_BOOTMETH_VBE_SIMPLE_FW
622 bool "Bootdev support for VBE 'simple' method firmware phase (SPL)"
626 Enables support for the firmware parts of VBE 'simple' boot. This
627 includes an SPL loader which locates the correct U-Boot to boot into.
628 This option should really only be enabled for VPL, since it is the
629 phase where the SPL + U-Boot decision should be made. But for now,
630 SPL does its own FIT-configuration selection.
632 config VPL_BOOTMETH_VBE_SIMPLE_FW
633 bool "Bootdev support for VBE 'simple' method firmware phase (VPL)"
637 Enables support for the firmware parts of VBE 'simple' boot. This
638 includes an SPL loader which locates the correct SPL to boot into.
639 This option enabled for VPL, since it is the phase where the SPL
645 bool "Support for expos - groups of scenes displaying a UI"
647 default y if BOOTMETH_VBE
649 An expo is a way of presenting and collecting information from the
650 user. It consists of a collection of 'scenes' of which only one is
651 presented at a time. An expo is typically used to show a boot menu
652 and allow settings to be changed.
654 The expo can be presented in graphics form using a vidconsole, or in
655 text form on a serial console.
657 config BOOTMETH_SANDBOX
661 This is a sandbox bootmeth driver used for testing. It always returns
662 -ENOTSUPP when attempting to boot.
664 config BOOTMETH_SCRIPT
665 bool "Bootdev support for U-Boot scripts"
666 default y if BOOTSTD_FULL
669 Enables support for booting a distro via a U-Boot script. This makes
670 the bootdevs look for a 'boot/boot.scr' file which can be used to
673 This provides a way to try out standard boot on an existing boot flow.
674 It is not enabled by default to save space.
678 config LEGACY_IMAGE_FORMAT
679 bool "Enable support for the legacy image format"
680 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
682 This option enables the legacy image format. It is enabled by
683 default for backward compatibility, unless FIT_SIGNATURE is
684 set where it is disabled so that unsigned images cannot be
685 loaded. If a board needs the legacy image format support in this
686 case, enable it here.
688 config SUPPORT_RAW_INITRD
689 bool "Enable raw initrd images"
691 Note, defining the SUPPORT_RAW_INITRD allows user to supply
692 kernel with raw initrd images. The syntax is slightly different, the
693 address of the initrd must be augmented by it's size, in the following
694 format: "<initrd address>:<initrd size>".
696 config OF_BOARD_SETUP
697 bool "Set up board-specific details in device tree before boot"
700 This causes U-Boot to call ft_board_setup() before booting into
701 the Operating System. This function can set up various
702 board-specific information in the device tree for use by the OS.
703 The device tree is then passed to the OS.
705 config OF_SYSTEM_SETUP
706 bool "Set up system-specific details in device tree before boot"
709 This causes U-Boot to call ft_system_setup() before booting into
710 the Operating System. This function can set up various
711 system-specific information in the device tree for use by the OS.
712 The device tree is then passed to the OS.
714 config OF_STDOUT_VIA_ALIAS
715 bool "Update the device-tree stdout alias from U-Boot"
718 This uses U-Boot's serial alias from the aliases node to update
719 the device tree passed to the OS. The "linux,stdout-path" property
720 in the chosen node is set to point to the correct serial node.
721 This option currently references CONFIG_CONS_INDEX, which is
722 incorrect when used with device tree as this option does not
723 exist / should not be used.
725 config HAVE_TEXT_BASE
727 depends on !NIOS2 && !XTENSA
732 depends on HAVE_TEXT_BASE
733 default 0x0 if POSITION_INDEPENDENT
734 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
735 default 0x81700000 if MACH_SUNIV
736 default 0x2a000000 if MACH_SUN9I
737 default 0x4a000000 if SUNXI_MINIMUM_DRAM_MB >= 256
738 default 0x42e00000 if SUNXI_MINIMUM_DRAM_MB >= 64
741 The address in memory that U-Boot will be running from, initially.
743 config HAVE_SYS_MONITOR_BASE
745 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
746 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
750 config SYS_MONITOR_BASE
751 depends on HAVE_SYS_MONITOR_BASE
752 hex "Physical start address of boot monitor code"
755 The physical start address of boot monitor code (which is the same as
756 CONFIG_TEXT_BASE when linking) and the same as CFG_SYS_FLASH_BASE
757 when booting from flash.
759 config SPL_SYS_MONITOR_BASE
760 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
761 hex "Physical start address of SPL monitor code"
762 default SPL_TEXT_BASE
764 config TPL_SYS_MONITOR_BASE
765 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
766 hex "Physical start address of TPL monitor code"
768 config DYNAMIC_SYS_CLK_FREQ
769 bool "Determine CPU clock frequency at run-time"
771 Implement a get_board_sys_clk function that will determine the CPU
772 clock frequency at run time, rather than define it statically.
775 depends on !DYNAMIC_SYS_CLK_FREQ
776 int "CPU clock frequency"
777 default 125000000 if ARCH_LS1012A
778 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
779 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
780 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
781 default 66660000 if ARCH_T2080
782 default 33333333 if RCAR_GEN3
783 default 24000000 if ARCH_EXYNOS
784 default 20000000 if RCAR_GEN2
787 A static value for the CPU frequency. Note that if not required
788 for a given SoC, this can be left at 0.
790 config ARCH_FIXUP_FDT_MEMORY
791 bool "Enable arch_fixup_memory_banks() call"
794 Enable FDT memory map syncup before OS boot. This feature can be
795 used for booting OS with different memory setup where the part of
796 the memory location should be used for different purpose.
799 bool "Support booting Chrome OS"
801 Chrome OS requires U-Boot to set up a table indicating the boot mode
802 (e.g. Developer mode) and a few other things. Enable this if you are
803 booting on a Chromebook to avoid getting an error about an invalid
806 config CHROMEOS_VBOOT
807 bool "Support Chrome OS verified boot"
809 This is intended to enable the full Chrome OS verified boot support
810 in U-Boot. It is not actually implemented in the U-Boot source code
811 at present, so this option is always set to 'n'. It allows
812 distinguishing between booting Chrome OS in a basic way (developer
813 mode) and a full boot.
819 bool "Freescale PBL(pre-boot loader) image format support"
820 select SYS_RAMBOOT if PPC
822 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
823 For more details refer to doc/README.pblimage
826 prompt "Freescale PBL (or predecessor) load location"
827 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
828 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
832 bool "Freescale PBL (or similar) is found on SD card"
835 bool "Freescale PBL (or similar) is found on SPI flash"
838 bool "Freescale PBL (or similar) is not used in this case"
842 config FSL_FIXED_MMC_LOCATION
843 bool "PBL MMC is at a fixed location"
844 depends on SDCARD && !RAMBOOT_PBL
846 config ESDHC_HC_BLK_ADDR
848 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
850 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
851 code length of these soc specify the memory address in block address
852 format. Block length is fixed to 512 bytes as per the SD High
853 Capacity specification.
855 config SYS_FSL_PBL_PBI
856 string "PBI(pre-boot instructions) commands for the PBL image"
857 depends on RAMBOOT_PBL
859 PBI commands can be used to configure SoC before it starts the execution.
860 Please refer doc/README.pblimage for more details.
862 config SYS_FSL_PBL_RCW
863 string "Aadditional RCW (Power on reset configuration) for the PBL image"
864 depends on RAMBOOT_PBL
866 Enables addition of RCW (Power on reset configuration) in built image.
867 Please refer doc/README.pblimage for more details.
869 config SYS_BOOT_RAMDISK_HIGH
870 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
871 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
875 Enable initrd_high functionality. If defined then the initrd_high
876 feature is enabled and the boot* ramdisk subcommand is enabled.
878 endmenu # Boot images
880 config DISTRO_DEFAULTS
881 bool "Select defaults suitable for booting general purpose Linux distributions"
884 select CMDLINE_EDITING
889 Select this to enable various options and commands which are suitable
890 for building u-boot for booting general purpose Linux distributions.
895 bool "Boot timing and reporting"
897 Enable recording of boot time while booting. To use it, insert
898 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
899 bootstage.h. Only a single entry is recorded for each ID. You can
900 give the entry a name with bootstage_mark_name(). You can also
901 record elapsed time in a particular stage using bootstage_start()
902 before starting and bootstage_accum() when finished. Bootstage will
903 add up all the accumulated time and report it.
905 Normally, IDs are defined in bootstage.h but a small number of
906 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
909 Calls to show_boot_progress() will also result in log entries but
910 these will not have names.
913 bool "Boot timing and reported in SPL"
914 depends on BOOTSTAGE && SPL
916 Enable recording of boot time in SPL. To make this visible to U-Boot
917 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
918 information when SPL finishes and load it when U-Boot proper starts
922 bool "Boot timing and reported in TPL"
923 depends on BOOTSTAGE && TPL
925 Enable recording of boot time in SPL. To make this visible to U-Boot
926 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
927 information when TPL finishes and load it when U-Boot proper starts
930 config BOOTSTAGE_REPORT
931 bool "Display a detailed boot timing report before booting the OS"
934 Enable output of a boot time report just before the OS is booted.
935 This shows how long it took U-Boot to go through each stage of the
936 boot process. The report looks something like this:
938 Timer summary in microseconds:
941 3,575,678 3,575,678 board_init_f start
942 3,575,695 17 arch_cpu_init A9
943 3,575,777 82 arch_cpu_init done
944 3,659,598 83,821 board_init_r start
945 3,910,375 250,777 main_loop
946 29,916,167 26,005,792 bootm_start
947 30,361,327 445,160 start_kernel
949 config BOOTSTAGE_RECORD_COUNT
950 int "Number of boot stage records to store"
954 This is the size of the bootstage record list and is the maximum
955 number of bootstage records that can be recorded.
957 config SPL_BOOTSTAGE_RECORD_COUNT
958 int "Number of boot stage records to store for SPL"
959 depends on SPL_BOOTSTAGE
962 This is the size of the bootstage record list and is the maximum
963 number of bootstage records that can be recorded.
965 config TPL_BOOTSTAGE_RECORD_COUNT
966 int "Number of boot stage records to store for TPL"
967 depends on TPL_BOOTSTAGE
970 This is the size of the bootstage record list and is the maximum
971 number of bootstage records that can be recorded.
974 bool "Store boot timing information in the OS device tree"
977 Stash the bootstage information in the FDT. A root 'bootstage'
978 node is created with each bootstage id as a child. Each child
979 has a 'name' property and either 'mark' containing the
980 mark time in microseconds, or 'accum' containing the
981 accumulated time for that bootstage id in microseconds.
986 name = "board_init_f";
995 Code in the Linux kernel can find this in /proc/devicetree.
997 config BOOTSTAGE_STASH
998 bool "Stash the boot timing information in memory before booting OS"
1001 Some OSes do not support device tree. Bootstage can instead write
1002 the boot timing information in a binary format at a given address.
1003 This happens through a call to bootstage_stash(), typically in
1004 the CPU's cleanup_before_linux() function. You can use the
1005 'bootstage stash' and 'bootstage unstash' commands to do this on
1008 config BOOTSTAGE_STASH_ADDR
1009 hex "Address to stash boot timing information"
1012 Provide an address which will not be overwritten by the OS when it
1013 starts, so that it can read this information when ready.
1015 config BOOTSTAGE_STASH_SIZE
1016 hex "Size of boot timing stash region"
1019 This should be large enough to hold the bootstage stash. A value of
1020 4096 (4KiB) is normally plenty.
1022 config SHOW_BOOT_PROGRESS
1023 bool "Show boot progress in a board-specific manner"
1025 Defining this option allows to add some board-specific code (calling
1026 a user-provided function show_boot_progress(int) that enables you to
1027 show the system's boot progress on some display (for example, some
1028 LEDs) on your board. At the moment, the following checkpoints are
1031 Legacy uImage format:
1034 1 common/cmd_bootm.c before attempting to boot an image
1035 -1 common/cmd_bootm.c Image header has bad magic number
1036 2 common/cmd_bootm.c Image header has correct magic number
1037 -2 common/cmd_bootm.c Image header has bad checksum
1038 3 common/cmd_bootm.c Image header has correct checksum
1039 -3 common/cmd_bootm.c Image data has bad checksum
1040 4 common/cmd_bootm.c Image data has correct checksum
1041 -4 common/cmd_bootm.c Image is for unsupported architecture
1042 5 common/cmd_bootm.c Architecture check OK
1043 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
1044 6 common/cmd_bootm.c Image Type check OK
1045 -6 common/cmd_bootm.c gunzip uncompression error
1046 -7 common/cmd_bootm.c Unimplemented compression type
1047 7 common/cmd_bootm.c Uncompression OK
1048 8 common/cmd_bootm.c No uncompress/copy overwrite error
1049 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
1051 9 common/image.c Start initial ramdisk verification
1052 -10 common/image.c Ramdisk header has bad magic number
1053 -11 common/image.c Ramdisk header has bad checksum
1054 10 common/image.c Ramdisk header is OK
1055 -12 common/image.c Ramdisk data has bad checksum
1056 11 common/image.c Ramdisk data has correct checksum
1057 12 common/image.c Ramdisk verification complete, start loading
1058 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
1059 13 common/image.c Start multifile image verification
1060 14 common/image.c No initial ramdisk, no multifile, continue.
1062 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
1064 -30 arch/powerpc/lib/board.c Fatal error, hang the system
1065 -31 post/post.c POST test failed, detected by post_output_backlog()
1066 -32 post/post.c POST test failed, detected by post_run_single()
1068 34 common/cmd_doc.c before loading a Image from a DOC device
1069 -35 common/cmd_doc.c Bad usage of "doc" command
1070 35 common/cmd_doc.c correct usage of "doc" command
1071 -36 common/cmd_doc.c No boot device
1072 36 common/cmd_doc.c correct boot device
1073 -37 common/cmd_doc.c Unknown Chip ID on boot device
1074 37 common/cmd_doc.c correct chip ID found, device available
1075 -38 common/cmd_doc.c Read Error on boot device
1076 38 common/cmd_doc.c reading Image header from DOC device OK
1077 -39 common/cmd_doc.c Image header has bad magic number
1078 39 common/cmd_doc.c Image header has correct magic number
1079 -40 common/cmd_doc.c Error reading Image from DOC device
1080 40 common/cmd_doc.c Image header has correct magic number
1081 41 common/cmd_ide.c before loading a Image from a IDE device
1082 -42 common/cmd_ide.c Bad usage of "ide" command
1083 42 common/cmd_ide.c correct usage of "ide" command
1084 -43 common/cmd_ide.c No boot device
1085 43 common/cmd_ide.c boot device found
1086 -44 common/cmd_ide.c Device not available
1087 44 common/cmd_ide.c Device available
1088 -45 common/cmd_ide.c wrong partition selected
1089 45 common/cmd_ide.c partition selected
1090 -46 common/cmd_ide.c Unknown partition table
1091 46 common/cmd_ide.c valid partition table found
1092 -47 common/cmd_ide.c Invalid partition type
1093 47 common/cmd_ide.c correct partition type
1094 -48 common/cmd_ide.c Error reading Image Header on boot device
1095 48 common/cmd_ide.c reading Image Header from IDE device OK
1096 -49 common/cmd_ide.c Image header has bad magic number
1097 49 common/cmd_ide.c Image header has correct magic number
1098 -50 common/cmd_ide.c Image header has bad checksum
1099 50 common/cmd_ide.c Image header has correct checksum
1100 -51 common/cmd_ide.c Error reading Image from IDE device
1101 51 common/cmd_ide.c reading Image from IDE device OK
1102 52 common/cmd_nand.c before loading a Image from a NAND device
1103 -53 common/cmd_nand.c Bad usage of "nand" command
1104 53 common/cmd_nand.c correct usage of "nand" command
1105 -54 common/cmd_nand.c No boot device
1106 54 common/cmd_nand.c boot device found
1107 -55 common/cmd_nand.c Unknown Chip ID on boot device
1108 55 common/cmd_nand.c correct chip ID found, device available
1109 -56 common/cmd_nand.c Error reading Image Header on boot device
1110 56 common/cmd_nand.c reading Image Header from NAND device OK
1111 -57 common/cmd_nand.c Image header has bad magic number
1112 57 common/cmd_nand.c Image header has correct magic number
1113 -58 common/cmd_nand.c Error reading Image from NAND device
1114 58 common/cmd_nand.c reading Image from NAND device OK
1116 -60 common/env_common.c Environment has a bad CRC, using default
1118 64 net/eth.c starting with Ethernet configuration.
1119 -64 net/eth.c no Ethernet found.
1120 65 net/eth.c Ethernet found.
1122 -80 common/cmd_net.c usage wrong
1123 80 common/cmd_net.c before calling net_loop()
1124 -81 common/cmd_net.c some error in net_loop() occurred
1125 81 common/cmd_net.c net_loop() back without error
1126 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1127 82 common/cmd_net.c trying automatic boot
1128 83 common/cmd_net.c running "source" command
1129 -83 common/cmd_net.c some error in automatic boot or "source" command
1130 84 common/cmd_net.c end without errors
1135 100 common/cmd_bootm.c Kernel FIT Image has correct format
1136 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1137 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1138 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1139 102 common/cmd_bootm.c Kernel unit name specified
1140 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1141 103 common/cmd_bootm.c Found configuration node
1142 104 common/cmd_bootm.c Got kernel subimage node offset
1143 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1144 105 common/cmd_bootm.c Kernel subimage hash verification OK
1145 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1146 106 common/cmd_bootm.c Architecture check OK
1147 -106 common/cmd_bootm.c Kernel subimage has wrong type
1148 107 common/cmd_bootm.c Kernel subimage type OK
1149 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1150 108 common/cmd_bootm.c Got kernel subimage data/size
1151 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1152 -109 common/cmd_bootm.c Can't get kernel subimage type
1153 -110 common/cmd_bootm.c Can't get kernel subimage comp
1154 -111 common/cmd_bootm.c Can't get kernel subimage os
1155 -112 common/cmd_bootm.c Can't get kernel subimage load address
1156 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1158 120 common/image.c Start initial ramdisk verification
1159 -120 common/image.c Ramdisk FIT image has incorrect format
1160 121 common/image.c Ramdisk FIT image has correct format
1161 122 common/image.c No ramdisk subimage unit name, using configuration
1162 -122 common/image.c Can't get configuration for ramdisk subimage
1163 123 common/image.c Ramdisk unit name specified
1164 -124 common/image.c Can't get ramdisk subimage node offset
1165 125 common/image.c Got ramdisk subimage node offset
1166 -125 common/image.c Ramdisk subimage hash verification failed
1167 126 common/image.c Ramdisk subimage hash verification OK
1168 -126 common/image.c Ramdisk subimage for unsupported architecture
1169 127 common/image.c Architecture check OK
1170 -127 common/image.c Can't get ramdisk subimage data/size
1171 128 common/image.c Got ramdisk subimage data/size
1172 129 common/image.c Can't get ramdisk load address
1173 -129 common/image.c Got ramdisk load address
1175 -130 common/cmd_doc.c Incorrect FIT image format
1176 131 common/cmd_doc.c FIT image format OK
1178 -140 common/cmd_ide.c Incorrect FIT image format
1179 141 common/cmd_ide.c FIT image format OK
1181 -150 common/cmd_nand.c Incorrect FIT image format
1182 151 common/cmd_nand.c FIT image format OK
1184 config SPL_SHOW_BOOT_PROGRESS
1185 bool "Show boot progress in a board-specific manner in SPL"
1188 Defining this option allows to add some board-specific code (calling
1189 a user-provided function show_boot_progress(int) that enables you to
1190 show the system's boot progress on some display (for example, some
1191 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1198 bool "Support for booting from NOR flash"
1201 Enabling this will make a U-Boot binary that is capable of being
1202 booted via NOR. In this case we will enable certain pinmux early
1203 as the ROM only partially sets up pinmux. We also default to using
1204 NOR for environment.
1207 bool "Support for booting from NAND flash"
1210 Enabling this will make a U-Boot binary that is capable of being
1211 booted via NAND flash. This is not a must, some SoCs need this,
1215 bool "Support for booting from ONENAND"
1218 Enabling this will make a U-Boot binary that is capable of being
1219 booted via ONENAND. This is not a must, some SoCs need this,
1223 bool "Support for booting from QSPI flash"
1225 Enabling this will make a U-Boot binary that is capable of being
1226 booted via QSPI flash. This is not a must, some SoCs need this,
1230 bool "Support for booting from SATA"
1232 Enabling this will make a U-Boot binary that is capable of being
1233 booted via SATA. This is not a must, some SoCs need this,
1237 bool "Support for booting from SD/EMMC"
1239 Enabling this will make a U-Boot binary that is capable of being
1240 booted via SD/EMMC. This is not a must, some SoCs need this,
1244 bool "Support for booting from SD/EMMC and enable QSPI"
1246 Enabling this will make a U-Boot binary that is capable of being
1247 booted via SD/EMMC while enabling QSPI on the platform as well. This
1248 is not a must, some SoCs need this, some not.
1251 bool "Support for booting from SPI flash"
1253 Enabling this will make a U-Boot binary that is capable of being
1254 booted via SPI flash. This is not a must, some SoCs need this,
1259 menu "Autoboot options"
1265 This enables the autoboot. See doc/README.autoboot for detail.
1268 int "delay in seconds before automatically booting"
1272 Delay before automatically running bootcmd;
1273 set to 0 to autoboot with no delay, but you can stop it by key input.
1274 set to -1 to disable autoboot.
1275 set to -2 to autoboot with no delay and not check for abort
1277 If this value is >= 0 then it is also used for the default delay
1278 before starting the default entry in bootmenu. If it is < 0 then
1279 a default value of 10s is used.
1281 See doc/README.autoboot for details.
1283 config AUTOBOOT_KEYED
1284 bool "Stop autobooting via specific input key / string"
1286 This option enables stopping (aborting) of the automatic
1287 boot feature only by issuing a specific input key or
1288 string. If not enabled, any input key will abort the
1289 U-Boot automatic booting process and bring the device
1290 to the U-Boot prompt for user input.
1292 config AUTOBOOT_FLUSH_STDIN
1293 bool "Enable flushing stdin before starting to read the password"
1294 depends on AUTOBOOT_KEYED && !SANDBOX
1296 When this option is enabled stdin buffer will be flushed before
1297 starting to read the password.
1298 This can't be enabled for the sandbox as flushing stdin would
1299 break the autoboot unit tests.
1301 config AUTOBOOT_PROMPT
1302 string "Autoboot stop prompt"
1303 depends on AUTOBOOT_KEYED
1304 default "Autoboot in %d seconds\\n"
1306 This string is displayed before the boot delay selected by
1307 CONFIG_BOOTDELAY starts. If it is not defined there is no
1308 output indicating that autoboot is in progress.
1310 Note that this define is used as the (only) argument to a
1311 printf() call, so it may contain '%' format specifications,
1312 provided that it also includes, sepearated by commas exactly
1313 like in a printf statement, the required arguments. It is
1314 the responsibility of the user to select only such arguments
1315 that are valid in the given context.
1317 config AUTOBOOT_ENCRYPTION
1318 bool "Enable encryption in autoboot stopping"
1319 depends on AUTOBOOT_KEYED
1321 This option allows a string to be entered into U-Boot to stop the
1323 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1325 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1326 to the crypt-based functionality and be compared against the
1327 string in the environment variable 'bootstopkeycrypt'.
1328 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1329 and compared against the hash in the environment variable
1330 'bootstopkeysha256'.
1331 If it matches in either case then boot stops and
1332 a command-line prompt is presented.
1333 This provides a way to ship a secure production device which can also
1334 be accessed at the U-Boot command line.
1336 config AUTOBOOT_SHA256_FALLBACK
1337 bool "Allow fallback from crypt-hashed password to sha256"
1338 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1340 This option adds support to fall back from crypt-hashed
1341 passwords to checking a SHA256 hashed password in case the
1342 'bootstopusesha256' environment variable is set to 'true'.
1344 config AUTOBOOT_DELAY_STR
1345 string "Delay autobooting via specific input key / string"
1346 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1348 This option delays the automatic boot feature by issuing
1349 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1350 or the environment variable "bootdelaykey" is specified
1351 and this string is received from console input before
1352 autoboot starts booting, U-Boot gives a command prompt. The
1353 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1354 used, otherwise it never times out.
1356 config AUTOBOOT_STOP_STR
1357 string "Stop autobooting via specific input key / string"
1358 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1360 This option enables stopping (aborting) of the automatic
1361 boot feature only by issuing a specific input key or
1362 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1363 variable "bootstopkey" is specified and this string is
1364 received from console input before autoboot starts booting,
1365 U-Boot gives a command prompt. The U-Boot prompt never
1366 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1368 config AUTOBOOT_KEYED_CTRLC
1369 bool "Enable Ctrl-C autoboot interruption"
1370 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1372 This option allows for the boot sequence to be interrupted
1373 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1374 Setting this variable provides an escape sequence from the
1375 limited "password" strings.
1377 config AUTOBOOT_NEVER_TIMEOUT
1378 bool "Make the password entry never time-out"
1379 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1381 This option removes the timeout from the password entry
1382 when the user first presses the <Enter> key before entering
1383 any other character.
1385 config AUTOBOOT_STOP_STR_ENABLE
1386 bool "Enable fixed string to stop autobooting"
1387 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1389 This option enables the feature to add a fixed stop
1390 string that is defined at compile time.
1391 In every case it will be tried to load the stop
1392 string from the environment.
1393 In case this is enabled and there is no stop string
1394 in the environment, this will be used as default value.
1396 config AUTOBOOT_STOP_STR_CRYPT
1397 string "Stop autobooting via crypt-hashed password"
1398 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1400 This option adds the feature to only stop the autobooting,
1401 and therefore boot into the U-Boot prompt, when the input
1402 string / password matches a values that is hashed via
1403 one of the supported crypt-style password hashing options
1404 and saved in the environment variable "bootstopkeycrypt".
1406 config AUTOBOOT_STOP_STR_SHA256
1407 string "Stop autobooting via SHA256 hashed password"
1408 depends on AUTOBOOT_STOP_STR_ENABLE
1410 This option adds the feature to only stop the autobooting,
1411 and therefore boot into the U-Boot prompt, when the input
1412 string / password matches a values that is encypted via
1413 a SHA256 hash and saved in the environment variable
1414 "bootstopkeysha256". If the value in that variable
1415 includes a ":", the portion prior to the ":" will be treated
1418 config AUTOBOOT_USE_MENUKEY
1419 bool "Allow a specify key to run a menu from the environment"
1420 depends on !AUTOBOOT_KEYED
1422 If a specific key is pressed to stop autoboot, then the commands in
1423 the environment variable 'menucmd' are executed before boot starts.
1425 config AUTOBOOT_MENUKEY
1426 int "ASCII value of boot key to show a menu"
1428 depends on AUTOBOOT_USE_MENUKEY
1430 If this key is pressed to stop autoboot, then the commands in the
1431 environment variable 'menucmd' will be executed before boot starts.
1432 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1435 config AUTOBOOT_MENU_SHOW
1436 bool "Show a menu on boot"
1437 depends on CMD_BOOTMENU
1439 This enables the boot menu, controlled by environment variables
1440 defined by the board. The menu starts after running the 'preboot'
1441 environmnent variable (if enabled) and before handling the boot delay.
1442 See doc/usage/cmd/bootmenu.rst for more details.
1444 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1445 bool "Disallow bootmenu to enter the U-Boot console"
1446 depends on AUTOBOOT_MENU_SHOW
1448 If this option is enabled, user can not enter the U-Boot console from
1449 bootmenu. It increases the system security.
1452 bool "Boot retry feature"
1454 Allow for having the U-Boot command prompt time out and attempt
1455 to boot again. If the environment variable "bootretry" is found then
1456 its value is used, otherwise the retry timeout is
1457 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1458 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1460 config BOOT_RETRY_TIME
1461 int "Timeout in seconds before attempting to boot again"
1462 depends on BOOT_RETRY
1464 Time in seconds before the U-Boot prompt will timeout and boot will
1467 config BOOT_RETRY_MIN
1468 int "Minimum timeout in seconds for 'bootretry'"
1469 depends on BOOT_RETRY
1470 default BOOT_RETRY_TIME
1472 The minimum time in seconds that "bootretry" can be set to.
1474 config RESET_TO_RETRY
1475 bool "Reset the board to retry autoboot"
1476 depends on BOOT_RETRY
1478 After the countdown timed out, the board will be reset to restart
1483 menu "Image support"
1485 config IMAGE_PRE_LOAD
1486 bool "Image pre-load support"
1488 Enable an image pre-load stage in the SPL.
1489 This pre-load stage allows to do some manipulation
1490 or check (for example signature check) on an image
1491 before launching it.
1493 config SPL_IMAGE_PRE_LOAD
1494 bool "Image pre-load support within SPL"
1495 depends on SPL && IMAGE_PRE_LOAD
1497 Enable an image pre-load stage in the SPL.
1498 This pre-load stage allows to do some manipulation
1499 or check (for example signature check) on an image
1500 before launching it.
1502 config IMAGE_PRE_LOAD_SIG
1503 bool "Image pre-load signature support"
1504 depends on IMAGE_PRE_LOAD
1505 select FIT_SIGNATURE
1507 select RSA_VERIFY_WITH_PKEY
1509 Enable signature check support in the pre-load stage.
1510 For this feature a very simple header is added before
1511 the image with few fields:
1515 All other information (header size, type of signature,
1516 ...) are provided in the node /image/pre-load/sig of
1519 config SPL_IMAGE_PRE_LOAD_SIG
1520 bool "Image pre-load signature support witin SPL"
1521 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1522 select SPL_FIT_SIGNATURE
1524 select SPL_RSA_VERIFY_WITH_PKEY
1526 Enable signature check support in the pre-load stage in the SPL.
1527 For this feature a very simple header is added before
1528 the image with few fields:
1532 All other information (header size, type of signature,
1533 ...) are provided in the node /image/pre-load/sig of
1539 bool "Enable boot arguments"
1541 Provide boot arguments to bootm command. Boot arguments are specified
1542 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1543 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1544 will be undefined and won't take any space in U-Boot image.
1547 string "Boot arguments"
1548 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1550 This can be used to pass arguments to the bootm command. The value of
1551 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1552 this value will also override the "chosen" node in FDT blob.
1554 config BOOTARGS_SUBST
1555 bool "Support substituting strings in boot arguments"
1557 This allows substituting string values in the boot arguments. These
1558 are applied after the commandline has been built.
1560 One use for this is to insert the root-disk UUID into the command
1561 line where bootargs contains "root=${uuid}"
1563 setenv bootargs "console= root=${uuid}"
1564 # Set the 'uuid' environment variable
1565 part uuid mmc 2:2 uuid
1567 # Command-line substitution will put the real uuid into the
1568 # kernel command line
1571 config USE_BOOTCOMMAND
1572 bool "Enable a default value for bootcmd"
1574 Provide a default value for the bootcmd entry in the environment. If
1575 autoboot is enabled this is what will be run automatically. Enable
1576 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1577 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1578 won't take any space in U-Boot image.
1581 string "bootcmd value"
1582 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1583 default "bootflow scan -lb" if BOOTSTD_DEFAULTS && CMD_BOOTFLOW_FULL
1584 default "bootflow scan" if BOOTSTD_DEFAULTS && !CMD_BOOTFLOW_FULL
1585 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1587 This is the string of commands that will be used as bootcmd and if
1588 AUTOBOOT is set, automatically run.
1591 bool "Enable preboot"
1593 When this option is enabled, the existence of the environment
1594 variable "preboot" will be checked immediately before starting the
1595 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1596 entering interactive mode.
1598 This feature is especially useful when "preboot" is automatically
1599 generated or modified. For example, the boot code can modify the
1600 "preboot" when a user holds down a certain combination of keys.
1603 string "preboot default value"
1604 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1605 default "usb start" if USB_KEYBOARD
1608 This is the default of "preboot" environment variable.
1610 config PREBOOT_DEFINED
1612 default y if PREBOOT != ""
1614 config DEFAULT_FDT_FILE
1615 string "Default fdt file"
1617 This option is used to set the default fdt file to boot OS.
1619 config SAVE_PREV_BL_FDT_ADDR
1621 bool "Saves fdt address, passed by the previous bootloader, to env var"
1623 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1624 enable this option to save fdt address, passed by the
1625 previous bootloader for future use.
1626 Address is saved to `prevbl_fdt_addr` environment variable.
1628 If no fdt was provided by previous bootloader, no env variables
1631 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1633 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1635 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1636 enable this option to save initramfs address, passed by the
1637 previous bootloader for future use.
1638 Address is saved to `prevbl_initrd_start_addr` environment variable.
1640 If no initramfs was provided by previous bootloader, no env variables
1643 menu "Configuration editor"
1646 bool "Configuration editor"
1649 Provides a way to deal with board configuration and present it to
1650 the user for adjustment.
1652 This is intended to provide both graphical and text-based user
1653 interfaces, but only graphical is support at present.
1655 endmenu # Configuration editor