5 config ANDROID_BOOT_IMAGE
6 bool "Android Boot Images"
9 This enables support for booting images which use the Android
13 bool "Show image date and time when displaying image information"
16 When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of
17 an image is printed by image commands like bootm or iminfo. This
18 is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is
19 enabled, then U-Boot requires FITs to have a timestamp. If a FIT is
20 loaded that does not, the message 'Wrong FIT format: no timestamp'
24 bool "Support for running a command if a button is held during boot"
28 For many embedded devices it's useful to enter a special flashing mode
29 such as fastboot mode when a button is held during boot. This option
30 allows arbitrary commands to be assigned to specific buttons. These will
31 be run after "preboot" if the button is held. Configuration is done via
32 the environment variables "button_cmd_N_name" and "button_cmd_N" where n is
33 the button number (starting from 0). e.g:
35 "button_cmd_0_name=vol_down"
36 "button_cmd_0=fastboot usb 0"
39 bool "Flattened Image Tree (FIT)"
45 This option allows you to boot the new uImage structure,
46 Flattened Image Tree. FIT is formally a FDT, which can include
47 images of various types (kernel, FDT blob, ramdisk, etc.)
48 in a single blob. To boot this new uImage structure,
49 pass the address of the blob to the "bootm" command.
50 FIT is very flexible, supporting compression, multiple images,
51 multiple configurations, verification through hashing and also
52 verified boot (secure boot using RSA).
56 config FIT_EXTERNAL_OFFSET
57 hex "FIT external data offset"
60 This specifies a data offset in fit image.
61 The offset is from data payload offset to the beginning of
62 fit image header. When specifies a offset, specific data
63 could be put in the hole between data payload and fit image
64 header, such as CSF data on i.MX platform.
67 bool "Do a full check of the FIT before using it"
70 Enable this do a full check of the FIT to make sure it is valid. This
71 helps to protect against carefully crafted FITs which take advantage
72 of bugs or omissions in the code. This includes a bad structure,
73 multiple root nodes and the like.
76 bool "Enable signature verification of FIT uImages"
81 select IMAGE_SIGN_INFO
84 This option enables signature verification of FIT uImages,
85 using a hash signed and verified using RSA. If
86 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
87 hashing is available using hardware, then the RSA library will use
88 it. See doc/uImage.FIT/signature.txt for more details.
90 WARNING: When relying on signed FIT images with a required signature
91 check the legacy image format is disabled by default, so that
92 unsigned images cannot be loaded. If a board needs the legacy image
93 format support in this case, enable it using
94 CONFIG_LEGACY_IMAGE_FORMAT.
96 config FIT_SIGNATURE_MAX_SIZE
97 hex "Max size of signed FIT structures"
98 depends on FIT_SIGNATURE
101 This option sets a max size in bytes for verified FIT uImages.
102 A sane value of 256MB protects corrupted DTB structures from overlapping
103 device memory. Assure this size does not extend past expected storage
106 config FIT_RSASSA_PSS
107 bool "Support rsassa-pss signature scheme of FIT image contents"
108 depends on FIT_SIGNATURE
110 Enable this to support the pss padding algorithm as described
111 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
114 bool "Enable ciphering data in a FIT uImages"
118 Enable the feature of data ciphering/unciphering in the tool mkimage
119 and in the u-boot support of the FIT image.
122 bool "Show verbose messages when FIT images fail"
124 Generally a system will have valid FIT images so debug messages
125 are a waste of code space. If you are debugging your images then
126 you can enable this option to get more verbose information about
129 config FIT_BEST_MATCH
130 bool "Select the best match for the kernel device tree"
132 When no configuration is explicitly selected, default to the
133 one whose fdt's compatibility field best matches that of
134 U-Boot itself. A match is considered "best" if it matches the
135 most specific compatibility entry of U-Boot's fdt's root node.
136 The order of entries in the configuration's fdt is ignored.
138 config FIT_IMAGE_POST_PROCESS
139 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
140 depends on SOCFPGA_SECURE_VAB_AUTH
142 Allows doing any sort of manipulation to blobs after they got extracted
143 from FIT images like stripping off headers or modifying the size of the
144 blob, verification, authentication, decryption etc. in a platform or
145 board specific way. In order to use this feature a platform or board-
146 specific implementation of board_fit_image_post_process() must be
147 provided. Also, anything done during this post-processing step would
148 need to be comprehended in how the images were prepared before being
149 injected into the FIT creation (i.e. the blobs would have been pre-
150 processed before being added to the FIT image).
153 bool "Support FIT printing"
156 Support printing the content of the fitImage in a verbose manner.
159 bool "Support Flattened Image Tree within SPL"
165 bool "Support FIT printing within SPL"
168 Support printing the content of the fitImage in a verbose manner in SPL.
170 config SPL_FIT_FULL_CHECK
171 bool "Do a full check of the FIT before using it"
174 Enable this do a full check of the FIT to make sure it is valid. This
175 helps to protect against carefully crafted FITs which take advantage
176 of bugs or omissions in the code. This includes a bad structure,
177 multiple root nodes and the like.
179 config SPL_FIT_SIGNATURE
180 bool "Enable signature verification of FIT firmware within SPL"
182 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
189 select SPL_IMAGE_SIGN_INFO
190 select SPL_FIT_FULL_CHECK
192 config SPL_FIT_SIGNATURE_MAX_SIZE
193 hex "Max size of signed FIT structures in SPL"
194 depends on SPL_FIT_SIGNATURE
197 This option sets a max size in bytes for verified FIT uImages.
198 A sane value of 256MB protects corrupted DTB structures from overlapping
199 device memory. Assure this size does not extend past expected storage
202 config SPL_FIT_RSASSA_PSS
203 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
204 depends on SPL_FIT_SIGNATURE
206 Enable this to support the pss padding algorithm as described
207 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
210 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
214 Normally with the SPL framework a legacy image is generated as part
215 of the build. This contains U-Boot along with information as to
216 where it should be loaded. This option instead enables generation
217 of a FIT (Flat Image Tree) which provides more flexibility. In
218 particular it can handle selecting from multiple device tree
219 and passing the correct one to U-Boot.
221 This path has the following limitations:
223 1. "loadables" images, other than FDTs, which do not have a "load"
224 property will not be loaded. This limitation also applies to FPGA
225 images with the correct "compatible" string.
226 2. For FPGA images, the supported "compatible" list is in the
227 doc/uImage.FIT/source_file_format.txt.
228 3. FDTs are only loaded for images with an "os" property of "u-boot".
229 "linux" images are also supported with Falcon boot mode.
231 config SPL_LOAD_FIT_ADDRESS
232 hex "load address of fit image"
233 depends on SPL_LOAD_FIT
236 Specify the load address of the fit image that will be loaded
239 config SPL_LOAD_FIT_APPLY_OVERLAY
240 bool "Enable SPL applying DT overlays from FIT"
241 depends on SPL_LOAD_FIT
242 select OF_LIBFDT_OVERLAY
244 The device tree is loaded from the FIT image. Allow the SPL to
245 also load device-tree overlays from the FIT image an apply them
246 over the device tree.
248 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
249 depends on SPL_LOAD_FIT_APPLY_OVERLAY
251 hex "size of temporary buffer used to load the overlays"
253 The size of the area where the overlays will be loaded and
254 uncompress. Must be at least as large as biggest overlay
257 config SPL_LOAD_FIT_FULL
258 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
261 Normally with the SPL framework a legacy image is generated as part
262 of the build. This contains U-Boot along with information as to
263 where it should be loaded. This option instead enables generation
264 of a FIT (Flat Image Tree) which provides more flexibility. In
265 particular it can handle selecting from multiple device tree
266 and passing the correct one to U-Boot.
268 config SPL_FIT_IMAGE_POST_PROCESS
269 bool "Enable post-processing of FIT artifacts after loading by the SPL"
270 depends on SPL_LOAD_FIT
271 default y if TI_SECURE_DEVICE
273 Allows doing any sort of manipulation to blobs after they got extracted
274 from the U-Boot FIT image like stripping off headers or modifying the
275 size of the blob, verification, authentication, decryption etc. in a
276 platform or board specific way. In order to use this feature a platform
277 or board-specific implementation of board_fit_image_post_process() must
278 be provided. Also, anything done during this post-processing step would
279 need to be comprehended in how the images were prepared before being
280 injected into the FIT creation (i.e. the blobs would have been pre-
281 processed before being added to the FIT image).
283 config SPL_FIT_SOURCE
284 string ".its source file for U-Boot FIT image"
287 Specifies a (platform specific) FIT source file to generate the
288 U-Boot FIT image. This could specify further image to load and/or
291 config USE_SPL_FIT_GENERATOR
292 bool "Use a script to generate the .its script"
294 default y if SPL_FIT && ARCH_ZYNQMP
296 config SPL_FIT_GENERATOR
297 string ".its file generator script for U-Boot FIT image"
298 depends on USE_SPL_FIT_GENERATOR
299 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
301 Specifies a (platform specific) script file to generate the FIT
302 source file used to build the U-Boot FIT image file. This gets
303 passed a list of supported device tree file stub names to
304 include in the generated image.
309 bool "Support Flattened Image Tree within VPL"
316 bool "Support FIT printing within VPL"
320 Support printing the content of the fitImage in a verbose manner in VPL.
322 config VPL_FIT_FULL_CHECK
323 bool "Do a full check of the FIT before using it"
326 Enable this do a full check of the FIT to make sure it is valid. This
327 helps to protect against carefully crafted FITs which take advantage
328 of bugs or omissions in the code. This includes a bad structure,
329 multiple root nodes and the like.
331 config VPL_FIT_SIGNATURE
332 bool "Enable signature verification of FIT firmware within VPL"
341 select VPL_IMAGE_SIGN_INFO
342 select VPL_FIT_FULL_CHECK
344 config VPL_FIT_SIGNATURE_MAX_SIZE
345 hex "Max size of signed FIT structures in VPL"
346 depends on VPL_FIT_SIGNATURE
349 This option sets a max size in bytes for verified FIT uImages.
350 A sane value of 256MB protects corrupted DTB structures from overlapping
351 device memory. Assure this size does not extend past expected storage
362 Utilities for parsing PXE file formats.
364 config BOOT_DEFAULTS_FEATURES
366 select SUPPORT_RAW_INITRD
367 select ENV_VARS_UBOOT_CONFIG
372 config BOOT_DEFAULTS_CMDS
374 imply USE_BOOTCOMMAND
375 select CMD_ENV_EXISTS
379 select CMD_FS_GENERIC
380 select CMD_PART if PARTITIONS
381 select CMD_DHCP if CMD_NET
382 select CMD_PING if CMD_NET
383 select CMD_PXE if CMD_NET
384 select CMD_BOOTI if ARM64
385 select CMD_BOOTZ if ARM && !ARM64
389 bool # Common defaults for standard boot and distroboot
390 select BOOT_DEFAULTS_FEATURES
391 select BOOT_DEFAULTS_CMDS if CMDLINE
393 These are not required but are commonly needed to support a good
394 selection of booting methods. Enable this to improve the capability
395 of U-Boot to boot various images. Currently much functionality is
396 tied to enabling the command that exercises it.
401 depends on DM && OF_CONTROL && BLK
403 U-Boot supports a standard way of locating something to boot,
404 typically an Operating System such as Linux, provided by a distro such
405 as Arch Linux or Debian. Enable this to support iterating through
406 available bootdevs and using bootmeths to find bootflows suitable for
409 Standard boot is not a standard way of booting, just a framework
410 within U-Boot for supporting all the different ways that exist.
414 - bootdev - a device which can hold a distro (e.g. MMC)
415 - bootmeth - a method to scan a bootdev to find bootflows (owned by
417 - bootflow - a description of how to boot (owned by the distro)
422 bool "Standard boot support in SPL"
423 depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK
426 This enables standard boot in SPL. This is neeeded so that VBE
427 (Verified Boot for Embedded) can be used, since it depends on standard
428 boot. It is enabled by default since the main purpose of VPL is to
429 handle the firmware part of VBE.
432 bool "Standard boot support in VPL"
433 depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK
436 This enables standard boot in SPL. This is neeeded so that VBE
437 (Verified Boot for Embedded) can be used, since it depends on standard
438 boot. It is enabled by default since the main purpose of VPL is to
439 handle the firmware part of VBE.
442 bool "Enhanced features for standard boot"
444 imply BOOTSTD_DEFAULTS
446 This enables various useful features for standard boot, which are not
447 essential for operation:
449 - bootdev, bootmeth commands
450 - extra features in the bootflow command
451 - support for selecting the ordering of bootmeths ("bootmeth order")
452 - support for selecting the ordering of bootdevs using the devicetree
453 as well as the "boot_targets" environment variable
455 config BOOTSTD_DEFAULTS
456 bool "Select some common defaults for standard boot"
459 select BOOTMETH_DISTRO
461 These are not required but are commonly needed to support a good
462 selection of booting methods. Enable this to improve the capability
463 of U-Boot to boot various images.
465 config BOOTSTD_BOOTCOMMAND
466 bool "Use bootstd to boot"
467 default y if !DISTRO_DEFAULTS
469 Enable this to select a default boot-command suitable for booting
470 with standard boot. This can be overridden by the board if needed,
471 but the default command should be enough for most boards which use
474 For now this is only selected if distro boot is NOT used, since
475 standard boot does not support all of the features of distro boot
479 bool "Use programmatic boot"
483 Enable this to provide a board_run_command() function which can boot
484 a systen without using commands. If the boot fails, then U-Boot will
487 Note: This currently has many limitations and is not a useful booting
488 solution. Future work will eventually make this a viable option.
490 config BOOTMETH_GLOBAL
493 Add support for global bootmeths. This feature is used by VBE and
494 EFI bootmgr, since they take full control over which bootdevs are
498 bool "Bootdev support for Chromium OS"
499 depends on X86 || ARM || SANDBOX
502 select PARTITION_TYPE_GUID
503 select PARTITION_UUIDS
505 Enables support for booting Chromium OS using bootdevs. This uses the
506 kernel A slot and obtains the kernel command line from the parameters
509 Note that only x86 devices are supported at present.
511 config BOOTMETH_EXTLINUX
512 bool "Bootdev support for extlinux boot"
516 Enables support for extlinux boot using bootdevs. This makes the
517 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
520 The specification for this filed is here:
522 https://uapi-group.org/specifications/specs/boot_loader_specification/
524 This provides a way to try out standard boot on an existing boot flow.
526 config BOOTMETH_EXTLINUX_PXE
527 bool "Bootdev support for extlinux boot over network"
528 depends on CMD_PXE && CMD_NET && DM_ETH
531 Enables support for extlinux boot using bootdevs. This makes the
532 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
534 The specification for this file is here:
536 https://uapi-group.org/specifications/specs/boot_loader_specification/
538 This provides a way to try out standard boot on an existing boot flow.
540 config BOOTMETH_EFILOADER
541 bool "Bootdev support for EFI boot"
542 depends on EFI_BINARY_EXEC
545 Enables support for EFI boot using bootdevs. This makes the
546 bootdevs look for a 'boot<arch>.efi' on each filesystem
547 they scan. The resulting file is booted after enabling U-Boot's
550 The <arch> depends on the architecture of the board:
552 aa64 - aarch64 (ARM 64-bit)
556 riscv32 - RISC-V 32-bit
557 riscv64 - RISC-V 64-bit
559 This provides a way to try out standard boot on an existing boot flow.
562 bool "Bootdev support for Verified Boot for Embedded"
565 select BOOTMETH_GLOBAL
568 Enables support for VBE boot. This is a standard boot method which
569 supports selection of various firmware components, seleciton of an OS to
570 boot as well as updating these using fwupd.
572 config BOOTMETH_DISTRO
573 bool # Options needed to boot any distro
574 select BOOTMETH_SCRIPT if CMDLINE # E.g. Armbian uses scripts
575 select BOOTMETH_EXTLINUX # E.g. Debian uses these
576 select BOOTMETH_EXTLINUX_PXE if CMD_PXE && CMD_NET && DM_ETH
577 select BOOTMETH_EFILOADER if EFI_BINARY_EXEC # E.g. Ubuntu uses this
579 config SPL_BOOTMETH_VBE
580 bool "Bootdev support for Verified Boot for Embedded (SPL)"
581 depends on SPL && FIT
585 Enables support for VBE boot. This is a standard boot method which
586 supports selection of various firmware components, seleciton of an OS to
587 boot as well as updating these using fwupd.
589 config VPL_BOOTMETH_VBE
590 bool "Bootdev support for Verified Boot for Embedded (VPL)"
591 depends on VPL && FIT
595 Enables support for VBE boot. This is a standard boot method which
596 supports selection of various firmware components, seleciton of an OS to
597 boot as well as updating these using fwupd.
601 config BOOTMETH_VBE_REQUEST
602 bool "Support for serving VBE OS requests"
605 Enables support for looking that the requests made by the
606 Operating System being booted. These requests result in additions to
607 the device tree /chosen node, added during the device tree fixup
610 config SPL_BOOTMETH_VBE_REQUEST
611 bool "Support for serving VBE OS requests (SPL)"
614 Enables support for looking that the requests made by the
615 Operating System being booted. These requests result in additions to
616 the device tree /chosen node, added during the device tree fixup
619 This is only useful if you are booting an OS direct from SPL.
621 config BOOTMETH_VBE_SIMPLE
622 bool "Bootdev support for VBE 'simple' method"
625 Enables support for VBE 'simple' boot. This allows updating a single
626 firmware image in boot media such as MMC. It does not support any sort
627 of rollback, recovery or A/B boot.
629 config BOOTMETH_VBE_SIMPLE_OS
630 bool "Bootdev support for VBE 'simple' method OS phase"
633 Enables support for the OS parts of VBE 'simple' boot. This includes
634 fixing up the device tree with the required VBE information, ready
635 for booting into the OS. This option is only enabled for U-Boot
636 proper, since it is the phase where device tree fixups happen.
638 config SPL_BOOTMETH_VBE_SIMPLE
639 bool "Bootdev support for VBE 'simple' method (SPL)"
643 Enables support for VBE 'simple' boot. This allows updating a single
644 firmware image in boot media such as MMC. It does not support any sort
645 of rollback, recovery or A/B boot.
647 config VPL_BOOTMETH_VBE_SIMPLE
648 bool "Bootdev support for VBE 'simple' method (VPL)"
652 Enables support for VBE 'simple' boot. This allows updating a single
653 firmware image in boot media such as MMC. It does not support any sort
654 of rollback, recovery or A/B boot.
656 config SPL_BOOTMETH_VBE_SIMPLE_FW
657 bool "Bootdev support for VBE 'simple' method firmware phase (SPL)"
661 Enables support for the firmware parts of VBE 'simple' boot. This
662 includes an SPL loader which locates the correct U-Boot to boot into.
663 This option should really only be enabled for VPL, since it is the
664 phase where the SPL + U-Boot decision should be made. But for now,
665 SPL does its own FIT-configuration selection.
667 config VPL_BOOTMETH_VBE_SIMPLE_FW
668 bool "Bootdev support for VBE 'simple' method firmware phase (VPL)"
672 Enables support for the firmware parts of VBE 'simple' boot. This
673 includes an SPL loader which locates the correct SPL to boot into.
674 This option enabled for VPL, since it is the phase where the SPL
680 bool "Support for expos - groups of scenes displaying a UI"
682 default y if BOOTMETH_VBE
684 An expo is a way of presenting and collecting information from the
685 user. It consists of a collection of 'scenes' of which only one is
686 presented at a time. An expo is typically used to show a boot menu
687 and allow settings to be changed.
689 The expo can be presented in graphics form using a vidconsole, or in
690 text form on a serial console.
692 config BOOTMETH_SANDBOX
696 This is a sandbox bootmeth driver used for testing. It always returns
697 -ENOTSUPP when attempting to boot.
699 config BOOTMETH_SCRIPT
700 bool "Bootdev support for U-Boot scripts"
701 default y if BOOTSTD_FULL
705 Enables support for booting a distro via a U-Boot script. This makes
706 the bootdevs look for a 'boot/boot.scr' file which can be used to
709 This provides a way to try out standard boot on an existing boot flow.
710 It is not enabled by default to save space.
714 config LEGACY_IMAGE_FORMAT
715 bool "Enable support for the legacy image format"
716 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
718 This option enables the legacy image format. It is enabled by
719 default for backward compatibility, unless FIT_SIGNATURE is
720 set where it is disabled so that unsigned images cannot be
721 loaded. If a board needs the legacy image format support in this
722 case, enable it here.
725 bool "Measure boot images and configuration when booting without EFI"
726 depends on HASH && TPM_V2
728 This option enables measurement of the boot process when booting
729 without UEFI . Measurement involves creating cryptographic hashes
730 of the binary images that are booting and storing them in the TPM.
731 In addition, a log of these hashes is stored in memory for the OS
732 to verify the booted images and configuration. Enable this if the
733 OS has configured some memory area for the event log and you intend
734 to use some attestation tools on your system.
737 config MEASURE_DEVICETREE
738 bool "Measure the devicetree image"
739 default y if MEASURED_BOOT
741 On some platforms, the devicetree is not static as it may contain
742 random MAC addresses or other such data that changes each boot.
743 Therefore, it should not be measured into the TPM. In that case,
744 disable the measurement here.
746 config MEASURE_IGNORE_LOG
747 bool "Ignore the existing event log"
750 On platforms that use an event log memory region that persists
751 through system resets and are the first stage bootloader, then
752 this option should be enabled to ignore any existing data in the
753 event log memory region.
754 endif # MEASURED_BOOT
757 hex "Maximum size of a decompresed OS image"
758 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ || \
759 LEGACY_IMAGE_FORMAT || SPL_LEGACY_IMAGE_FORMAT
760 default 0x4000000 if PPC || ARM64
761 default 0x1000000 if X86 || ARCH_MX6 || ARCH_MX7
764 This is the maximum size of the buffer that is used to decompress the OS
765 image in to if attempting to boot a compressed image.
767 config SUPPORT_RAW_INITRD
768 bool "Enable raw initrd images"
770 Note, defining the SUPPORT_RAW_INITRD allows user to supply
771 kernel with raw initrd images. The syntax is slightly different, the
772 address of the initrd must be augmented by it's size, in the following
773 format: "<initrd address>:<initrd size>".
776 bool "Support booting Chrome OS"
778 Chrome OS requires U-Boot to set up a table indicating the boot mode
779 (e.g. Developer mode) and a few other things. Enable this if you are
780 booting on a Chromebook to avoid getting an error about an invalid
783 config CHROMEOS_VBOOT
784 bool "Support Chrome OS verified boot"
786 This is intended to enable the full Chrome OS verified boot support
787 in U-Boot. It is not actually implemented in the U-Boot source code
788 at present, so this option is always set to 'n'. It allows
789 distinguishing between booting Chrome OS in a basic way (developer
790 mode) and a full boot.
796 bool "Freescale PBL(pre-boot loader) image format support"
797 select SYS_RAMBOOT if PPC
799 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
800 For more details refer to doc/README.pblimage
803 prompt "Freescale PBL (or predecessor) load location"
804 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
805 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
809 bool "Freescale PBL (or similar) is found on SD card"
812 bool "Freescale PBL (or similar) is found on SPI flash"
815 bool "Freescale PBL (or similar) is not used in this case"
819 config FSL_FIXED_MMC_LOCATION
820 bool "PBL MMC is at a fixed location"
821 depends on SDCARD && !RAMBOOT_PBL
823 config ESDHC_HC_BLK_ADDR
825 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
827 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
828 code length of these soc specify the memory address in block address
829 format. Block length is fixed to 512 bytes as per the SD High
830 Capacity specification.
832 config SYS_FSL_PBL_PBI
833 string "PBI(pre-boot instructions) commands for the PBL image"
834 depends on RAMBOOT_PBL
836 PBI commands can be used to configure SoC before it starts the execution.
837 Please refer doc/README.pblimage for more details.
839 config SYS_FSL_PBL_RCW
840 string "Aadditional RCW (Power on reset configuration) for the PBL image"
841 depends on RAMBOOT_PBL
843 Enables addition of RCW (Power on reset configuration) in built image.
844 Please refer doc/README.pblimage for more details.
846 config SYS_BOOT_RAMDISK_HIGH
847 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
848 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
852 Enable initrd_high functionality. If defined then the initrd_high
853 feature is enabled and the boot* ramdisk subcommand is enabled.
855 endmenu # Boot images
857 config DISTRO_DEFAULTS
858 bool "(deprecated) Script-based booting of Linux distributions"
862 select CMDLINE_EDITING
867 Note: These scripts have been replaced by Standard Boot. Do not use
868 them on new boards. See 'Migrating from distro_boot' at
869 doc/develop/bootstd.rst
871 Select this to enable various options and commands which are suitable
872 for building u-boot for booting general purpose Linux distributions.
877 bool "Boot timing and reporting"
879 Enable recording of boot time while booting. To use it, insert
880 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
881 bootstage.h. Only a single entry is recorded for each ID. You can
882 give the entry a name with bootstage_mark_name(). You can also
883 record elapsed time in a particular stage using bootstage_start()
884 before starting and bootstage_accum() when finished. Bootstage will
885 add up all the accumulated time and report it.
887 Normally, IDs are defined in bootstage.h but a small number of
888 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
891 Calls to show_boot_progress() will also result in log entries but
892 these will not have names.
895 bool "Boot timing and reported in SPL"
896 depends on BOOTSTAGE && SPL
898 Enable recording of boot time in SPL. To make this visible to U-Boot
899 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
900 information when SPL finishes and load it when U-Boot proper starts
904 bool "Boot timing and reported in TPL"
905 depends on BOOTSTAGE && TPL
907 Enable recording of boot time in SPL. To make this visible to U-Boot
908 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
909 information when TPL finishes and load it when U-Boot proper starts
912 config BOOTSTAGE_REPORT
913 bool "Display a detailed boot timing report before booting the OS"
916 Enable output of a boot time report just before the OS is booted.
917 This shows how long it took U-Boot to go through each stage of the
918 boot process. The report looks something like this:
920 Timer summary in microseconds:
923 3,575,678 3,575,678 board_init_f start
924 3,575,695 17 arch_cpu_init A9
925 3,575,777 82 arch_cpu_init done
926 3,659,598 83,821 board_init_r start
927 3,910,375 250,777 main_loop
928 29,916,167 26,005,792 bootm_start
929 30,361,327 445,160 start_kernel
931 config BOOTSTAGE_RECORD_COUNT
932 int "Number of boot stage records to store"
936 This is the size of the bootstage record list and is the maximum
937 number of bootstage records that can be recorded.
939 config SPL_BOOTSTAGE_RECORD_COUNT
940 int "Number of boot stage records to store for SPL"
941 depends on SPL_BOOTSTAGE
944 This is the size of the bootstage record list and is the maximum
945 number of bootstage records that can be recorded.
947 config TPL_BOOTSTAGE_RECORD_COUNT
948 int "Number of boot stage records to store for TPL"
949 depends on TPL_BOOTSTAGE
952 This is the size of the bootstage record list and is the maximum
953 number of bootstage records that can be recorded.
956 bool "Store boot timing information in the OS device tree"
959 Stash the bootstage information in the FDT. A root 'bootstage'
960 node is created with each bootstage id as a child. Each child
961 has a 'name' property and either 'mark' containing the
962 mark time in microseconds, or 'accum' containing the
963 accumulated time for that bootstage id in microseconds.
968 name = "board_init_f";
977 Code in the Linux kernel can find this in /proc/devicetree.
979 config BOOTSTAGE_STASH
980 bool "Stash the boot timing information in memory before booting OS"
983 Some OSes do not support device tree. Bootstage can instead write
984 the boot timing information in a binary format at a given address.
985 This happens through a call to bootstage_stash(), typically in
986 the CPU's cleanup_before_linux() function. You can use the
987 'bootstage stash' and 'bootstage unstash' commands to do this on
990 config BOOTSTAGE_STASH_ADDR
991 hex "Address to stash boot timing information"
994 Provide an address which will not be overwritten by the OS when it
995 starts, so that it can read this information when ready.
997 config BOOTSTAGE_STASH_SIZE
998 hex "Size of boot timing stash region"
1001 This should be large enough to hold the bootstage stash. A value of
1002 4096 (4KiB) is normally plenty.
1004 config SHOW_BOOT_PROGRESS
1005 bool "Show boot progress in a board-specific manner"
1007 Defining this option allows to add some board-specific code (calling
1008 a user-provided function show_boot_progress(int) that enables you to
1009 show the system's boot progress on some display (for example, some
1010 LEDs) on your board. At the moment, the following checkpoints are
1013 Legacy uImage format:
1016 1 common/cmd_bootm.c before attempting to boot an image
1017 -1 common/cmd_bootm.c Image header has bad magic number
1018 2 common/cmd_bootm.c Image header has correct magic number
1019 -2 common/cmd_bootm.c Image header has bad checksum
1020 3 common/cmd_bootm.c Image header has correct checksum
1021 -3 common/cmd_bootm.c Image data has bad checksum
1022 4 common/cmd_bootm.c Image data has correct checksum
1023 -4 common/cmd_bootm.c Image is for unsupported architecture
1024 5 common/cmd_bootm.c Architecture check OK
1025 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
1026 6 common/cmd_bootm.c Image Type check OK
1027 -6 common/cmd_bootm.c gunzip uncompression error
1028 -7 common/cmd_bootm.c Unimplemented compression type
1029 7 common/cmd_bootm.c Uncompression OK
1030 8 common/cmd_bootm.c No uncompress/copy overwrite error
1031 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
1033 9 common/image.c Start initial ramdisk verification
1034 -10 common/image.c Ramdisk header has bad magic number
1035 -11 common/image.c Ramdisk header has bad checksum
1036 10 common/image.c Ramdisk header is OK
1037 -12 common/image.c Ramdisk data has bad checksum
1038 11 common/image.c Ramdisk data has correct checksum
1039 12 common/image.c Ramdisk verification complete, start loading
1040 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
1041 13 common/image.c Start multifile image verification
1042 14 common/image.c No initial ramdisk, no multifile, continue.
1044 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
1046 -30 arch/powerpc/lib/board.c Fatal error, hang the system
1047 -31 post/post.c POST test failed, detected by post_output_backlog()
1048 -32 post/post.c POST test failed, detected by post_run_single()
1050 34 common/cmd_doc.c before loading a Image from a DOC device
1051 -35 common/cmd_doc.c Bad usage of "doc" command
1052 35 common/cmd_doc.c correct usage of "doc" command
1053 -36 common/cmd_doc.c No boot device
1054 36 common/cmd_doc.c correct boot device
1055 -37 common/cmd_doc.c Unknown Chip ID on boot device
1056 37 common/cmd_doc.c correct chip ID found, device available
1057 -38 common/cmd_doc.c Read Error on boot device
1058 38 common/cmd_doc.c reading Image header from DOC device OK
1059 -39 common/cmd_doc.c Image header has bad magic number
1060 39 common/cmd_doc.c Image header has correct magic number
1061 -40 common/cmd_doc.c Error reading Image from DOC device
1062 40 common/cmd_doc.c Image header has correct magic number
1063 41 common/cmd_ide.c before loading a Image from a IDE device
1064 -42 common/cmd_ide.c Bad usage of "ide" command
1065 42 common/cmd_ide.c correct usage of "ide" command
1066 -43 common/cmd_ide.c No boot device
1067 43 common/cmd_ide.c boot device found
1068 -44 common/cmd_ide.c Device not available
1069 44 common/cmd_ide.c Device available
1070 -45 common/cmd_ide.c wrong partition selected
1071 45 common/cmd_ide.c partition selected
1072 -46 common/cmd_ide.c Unknown partition table
1073 46 common/cmd_ide.c valid partition table found
1074 -47 common/cmd_ide.c Invalid partition type
1075 47 common/cmd_ide.c correct partition type
1076 -48 common/cmd_ide.c Error reading Image Header on boot device
1077 48 common/cmd_ide.c reading Image Header from IDE device OK
1078 -49 common/cmd_ide.c Image header has bad magic number
1079 49 common/cmd_ide.c Image header has correct magic number
1080 -50 common/cmd_ide.c Image header has bad checksum
1081 50 common/cmd_ide.c Image header has correct checksum
1082 -51 common/cmd_ide.c Error reading Image from IDE device
1083 51 common/cmd_ide.c reading Image from IDE device OK
1084 52 common/cmd_nand.c before loading a Image from a NAND device
1085 -53 common/cmd_nand.c Bad usage of "nand" command
1086 53 common/cmd_nand.c correct usage of "nand" command
1087 -54 common/cmd_nand.c No boot device
1088 54 common/cmd_nand.c boot device found
1089 -55 common/cmd_nand.c Unknown Chip ID on boot device
1090 55 common/cmd_nand.c correct chip ID found, device available
1091 -56 common/cmd_nand.c Error reading Image Header on boot device
1092 56 common/cmd_nand.c reading Image Header from NAND device OK
1093 -57 common/cmd_nand.c Image header has bad magic number
1094 57 common/cmd_nand.c Image header has correct magic number
1095 -58 common/cmd_nand.c Error reading Image from NAND device
1096 58 common/cmd_nand.c reading Image from NAND device OK
1098 -60 common/env_common.c Environment has a bad CRC, using default
1100 64 net/eth.c starting with Ethernet configuration.
1101 -64 net/eth.c no Ethernet found.
1102 65 net/eth.c Ethernet found.
1104 -80 common/cmd_net.c usage wrong
1105 80 common/cmd_net.c before calling net_loop()
1106 -81 common/cmd_net.c some error in net_loop() occurred
1107 81 common/cmd_net.c net_loop() back without error
1108 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1109 82 common/cmd_net.c trying automatic boot
1110 83 common/cmd_net.c running "source" command
1111 -83 common/cmd_net.c some error in automatic boot or "source" command
1112 84 common/cmd_net.c end without errors
1117 100 common/cmd_bootm.c Kernel FIT Image has correct format
1118 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1119 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1120 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1121 102 common/cmd_bootm.c Kernel unit name specified
1122 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1123 103 common/cmd_bootm.c Found configuration node
1124 104 common/cmd_bootm.c Got kernel subimage node offset
1125 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1126 105 common/cmd_bootm.c Kernel subimage hash verification OK
1127 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1128 106 common/cmd_bootm.c Architecture check OK
1129 -106 common/cmd_bootm.c Kernel subimage has wrong type
1130 107 common/cmd_bootm.c Kernel subimage type OK
1131 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1132 108 common/cmd_bootm.c Got kernel subimage data/size
1133 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1134 -109 common/cmd_bootm.c Can't get kernel subimage type
1135 -110 common/cmd_bootm.c Can't get kernel subimage comp
1136 -111 common/cmd_bootm.c Can't get kernel subimage os
1137 -112 common/cmd_bootm.c Can't get kernel subimage load address
1138 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1140 120 common/image.c Start initial ramdisk verification
1141 -120 common/image.c Ramdisk FIT image has incorrect format
1142 121 common/image.c Ramdisk FIT image has correct format
1143 122 common/image.c No ramdisk subimage unit name, using configuration
1144 -122 common/image.c Can't get configuration for ramdisk subimage
1145 123 common/image.c Ramdisk unit name specified
1146 -124 common/image.c Can't get ramdisk subimage node offset
1147 125 common/image.c Got ramdisk subimage node offset
1148 -125 common/image.c Ramdisk subimage hash verification failed
1149 126 common/image.c Ramdisk subimage hash verification OK
1150 -126 common/image.c Ramdisk subimage for unsupported architecture
1151 127 common/image.c Architecture check OK
1152 -127 common/image.c Can't get ramdisk subimage data/size
1153 128 common/image.c Got ramdisk subimage data/size
1154 129 common/image.c Can't get ramdisk load address
1155 -129 common/image.c Got ramdisk load address
1157 -130 common/cmd_doc.c Incorrect FIT image format
1158 131 common/cmd_doc.c FIT image format OK
1160 -140 common/cmd_ide.c Incorrect FIT image format
1161 141 common/cmd_ide.c FIT image format OK
1163 -150 common/cmd_nand.c Incorrect FIT image format
1164 151 common/cmd_nand.c FIT image format OK
1166 config SPL_SHOW_BOOT_PROGRESS
1167 bool "Show boot progress in a board-specific manner in SPL"
1170 Defining this option allows to add some board-specific code (calling
1171 a user-provided function show_boot_progress(int) that enables you to
1172 show the system's boot progress on some display (for example, some
1173 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1180 bool "Support for booting from NOR flash"
1183 Enabling this will make a U-Boot binary that is capable of being
1184 booted via NOR. In this case we will enable certain pinmux early
1185 as the ROM only partially sets up pinmux. We also default to using
1186 NOR for environment.
1189 bool "Support for booting from NAND flash"
1192 Enabling this will make a U-Boot binary that is capable of being
1193 booted via NAND flash. This is not a must, some SoCs need this,
1197 bool "Support for booting from ONENAND"
1200 Enabling this will make a U-Boot binary that is capable of being
1201 booted via ONENAND. This is not a must, some SoCs need this,
1205 bool "Support for booting from QSPI flash"
1207 Enabling this will make a U-Boot binary that is capable of being
1208 booted via QSPI flash. This is not a must, some SoCs need this,
1212 bool "Support for booting from SATA"
1214 Enabling this will make a U-Boot binary that is capable of being
1215 booted via SATA. This is not a must, some SoCs need this,
1219 bool "Support for booting from SD/EMMC"
1221 Enabling this will make a U-Boot binary that is capable of being
1222 booted via SD/EMMC. This is not a must, some SoCs need this,
1226 bool "Support for booting from SD/EMMC and enable QSPI"
1228 Enabling this will make a U-Boot binary that is capable of being
1229 booted via SD/EMMC while enabling QSPI on the platform as well. This
1230 is not a must, some SoCs need this, some not.
1233 bool "Support for booting from SPI flash"
1235 Enabling this will make a U-Boot binary that is capable of being
1236 booted via SPI flash. This is not a must, some SoCs need this,
1241 menu "Autoboot options"
1248 This enables the autoboot. See doc/README.autoboot for detail.
1253 int "delay in seconds before automatically booting"
1256 Delay before automatically running bootcmd;
1257 set to 0 to autoboot with no delay, but you can stop it by key input.
1258 set to -1 to disable autoboot.
1259 set to -2 to autoboot with no delay and not check for abort
1261 If this value is >= 0 then it is also used for the default delay
1262 before starting the default entry in bootmenu. If it is < 0 then
1263 a default value of 10s is used.
1265 See doc/README.autoboot for details.
1267 config AUTOBOOT_KEYED
1268 bool "Stop autobooting via specific input key / string"
1270 This option enables stopping (aborting) of the automatic
1271 boot feature only by issuing a specific input key or
1272 string. If not enabled, any input key will abort the
1273 U-Boot automatic booting process and bring the device
1274 to the U-Boot prompt for user input.
1278 config AUTOBOOT_FLUSH_STDIN
1279 bool "Enable flushing stdin before starting to read the password"
1282 When this option is enabled stdin buffer will be flushed before
1283 starting to read the password.
1284 This can't be enabled for the sandbox as flushing stdin would
1285 break the autoboot unit tests.
1287 config AUTOBOOT_PROMPT
1288 string "Autoboot stop prompt"
1289 default "Autoboot in %d seconds\\n"
1291 This string is displayed before the boot delay selected by
1292 CONFIG_BOOTDELAY starts. If it is not defined there is no
1293 output indicating that autoboot is in progress.
1295 Note that this define is used as the (only) argument to a
1296 printf() call, so it may contain '%' format specifications,
1297 provided that it also includes, sepearated by commas exactly
1298 like in a printf statement, the required arguments. It is
1299 the responsibility of the user to select only such arguments
1300 that are valid in the given context.
1302 config AUTOBOOT_ENCRYPTION
1303 bool "Enable encryption in autoboot stopping"
1305 This option allows a string to be entered into U-Boot to stop the
1307 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1309 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1310 to the crypt-based functionality and be compared against the
1311 string in the environment variable 'bootstopkeycrypt'.
1312 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1313 and compared against the hash in the environment variable
1314 'bootstopkeysha256'.
1315 If it matches in either case then boot stops and
1316 a command-line prompt is presented.
1317 This provides a way to ship a secure production device which can also
1318 be accessed at the U-Boot command line.
1320 config AUTOBOOT_SHA256_FALLBACK
1321 bool "Allow fallback from crypt-hashed password to sha256"
1322 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1324 This option adds support to fall back from crypt-hashed
1325 passwords to checking a SHA256 hashed password in case the
1326 'bootstopusesha256' environment variable is set to 'true'.
1328 config AUTOBOOT_DELAY_STR
1329 string "Delay autobooting via specific input key / string"
1330 depends on !AUTOBOOT_ENCRYPTION
1332 This option delays the automatic boot feature by issuing
1333 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1334 or the environment variable "bootdelaykey" is specified
1335 and this string is received from console input before
1336 autoboot starts booting, U-Boot gives a command prompt. The
1337 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1338 used, otherwise it never times out.
1340 config AUTOBOOT_STOP_STR
1341 string "Stop autobooting via specific input key / string"
1342 depends on !AUTOBOOT_ENCRYPTION
1344 This option enables stopping (aborting) of the automatic
1345 boot feature only by issuing a specific input key or
1346 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1347 variable "bootstopkey" is specified and this string is
1348 received from console input before autoboot starts booting,
1349 U-Boot gives a command prompt. The U-Boot prompt never
1350 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1352 config AUTOBOOT_KEYED_CTRLC
1353 bool "Enable Ctrl-C autoboot interruption"
1354 depends on !AUTOBOOT_ENCRYPTION
1356 This option allows for the boot sequence to be interrupted
1357 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1358 Setting this variable provides an escape sequence from the
1359 limited "password" strings.
1361 config AUTOBOOT_NEVER_TIMEOUT
1362 bool "Make the password entry never time-out"
1363 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1365 This option removes the timeout from the password entry
1366 when the user first presses the <Enter> key before entering
1367 any other character.
1369 config AUTOBOOT_STOP_STR_ENABLE
1370 bool "Enable fixed string to stop autobooting"
1371 depends on AUTOBOOT_ENCRYPTION
1373 This option enables the feature to add a fixed stop
1374 string that is defined at compile time.
1375 In every case it will be tried to load the stop
1376 string from the environment.
1377 In case this is enabled and there is no stop string
1378 in the environment, this will be used as default value.
1380 config AUTOBOOT_STOP_STR_CRYPT
1381 string "Stop autobooting via crypt-hashed password"
1382 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1384 This option adds the feature to only stop the autobooting,
1385 and therefore boot into the U-Boot prompt, when the input
1386 string / password matches a values that is hashed via
1387 one of the supported crypt-style password hashing options
1388 and saved in the environment variable "bootstopkeycrypt".
1390 config AUTOBOOT_STOP_STR_SHA256
1391 string "Stop autobooting via SHA256 hashed password"
1392 depends on AUTOBOOT_STOP_STR_ENABLE
1394 This option adds the feature to only stop the autobooting,
1395 and therefore boot into the U-Boot prompt, when the input
1396 string / password matches a values that is encypted via
1397 a SHA256 hash and saved in the environment variable
1398 "bootstopkeysha256". If the value in that variable
1399 includes a ":", the portion prior to the ":" will be treated
1402 endif # AUTOBOOT_KEYED
1406 config AUTOBOOT_USE_MENUKEY
1407 bool "Allow a specify key to run a menu from the environment"
1409 If a specific key is pressed to stop autoboot, then the commands in
1410 the environment variable 'menucmd' are executed before boot starts.
1412 config AUTOBOOT_MENUKEY
1413 int "ASCII value of boot key to show a menu"
1415 depends on AUTOBOOT_USE_MENUKEY
1417 If this key is pressed to stop autoboot, then the commands in the
1418 environment variable 'menucmd' will be executed before boot starts.
1419 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1426 config AUTOBOOT_MENU_SHOW
1427 bool "Show a menu on boot"
1428 depends on CMD_BOOTMENU
1430 This enables the boot menu, controlled by environment variables
1431 defined by the board. The menu starts after running the 'preboot'
1432 environmnent variable (if enabled) and before handling the boot delay.
1433 See doc/usage/cmd/bootmenu.rst for more details.
1435 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1436 bool "Disallow bootmenu to enter the U-Boot console"
1437 depends on AUTOBOOT_MENU_SHOW
1439 If this option is enabled, user can not enter the U-Boot console from
1440 bootmenu. It increases the system security.
1443 bool "Boot retry feature"
1445 Allow for having the U-Boot command prompt time out and attempt
1446 to boot again. If the environment variable "bootretry" is found then
1447 its value is used, otherwise the retry timeout is
1448 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1449 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1451 config BOOT_RETRY_TIME
1452 int "Timeout in seconds before attempting to boot again"
1453 depends on BOOT_RETRY
1455 Time in seconds before the U-Boot prompt will timeout and boot will
1458 config BOOT_RETRY_MIN
1459 int "Minimum timeout in seconds for 'bootretry'"
1460 depends on BOOT_RETRY
1461 default BOOT_RETRY_TIME
1463 The minimum time in seconds that "bootretry" can be set to.
1465 config RESET_TO_RETRY
1466 bool "Reset the board to retry autoboot"
1467 depends on BOOT_RETRY
1469 After the countdown timed out, the board will be reset to restart
1474 menu "Image support"
1476 config IMAGE_PRE_LOAD
1477 bool "Image pre-load support"
1479 Enable an image pre-load stage in the SPL.
1480 This pre-load stage allows to do some manipulation
1481 or check (for example signature check) on an image
1482 before launching it.
1484 config SPL_IMAGE_PRE_LOAD
1485 bool "Image pre-load support within SPL"
1486 depends on SPL && IMAGE_PRE_LOAD
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 IMAGE_PRE_LOAD_SIG
1494 bool "Image pre-load signature support"
1495 depends on IMAGE_PRE_LOAD
1496 select FIT_SIGNATURE
1498 select RSA_VERIFY_WITH_PKEY
1500 Enable signature check support in the pre-load stage.
1501 For this feature a very simple header is added before
1502 the image with few fields:
1506 All other information (header size, type of signature,
1507 ...) are provided in the node /image/pre-load/sig of
1510 config SPL_IMAGE_PRE_LOAD_SIG
1511 bool "Image pre-load signature support witin SPL"
1512 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1513 select SPL_FIT_SIGNATURE
1515 select SPL_RSA_VERIFY_WITH_PKEY
1517 Enable signature check support in the pre-load stage in the SPL.
1518 For this feature a very simple header is added before
1519 the image with few fields:
1523 All other information (header size, type of signature,
1524 ...) are provided in the node /image/pre-load/sig of
1531 menu "Devicetree fixup"
1534 bool "Run a command from environment to set up device tree before boot"
1537 This causes U-Boot to run a command from the environment variable
1538 fdt_fixup before booting into the operating system, which can use the
1539 fdt command to modify the device tree. The device tree is then passed
1542 config OF_BOARD_SETUP
1543 bool "Set up board-specific details in device tree before boot"
1545 This causes U-Boot to call ft_board_setup() before booting into
1546 the Operating System. This function can set up various
1547 board-specific information in the device tree for use by the OS.
1548 The device tree is then passed to the OS.
1550 config OF_SYSTEM_SETUP
1551 bool "Set up system-specific details in device tree before boot"
1553 This causes U-Boot to call ft_system_setup() before booting into
1554 the Operating System. This function can set up various
1555 system-specific information in the device tree for use by the OS.
1556 The device tree is then passed to the OS.
1558 config OF_STDOUT_VIA_ALIAS
1559 bool "Update the device-tree stdout alias from U-Boot"
1561 This uses U-Boot's serial alias from the aliases node to update
1562 the device tree passed to the OS. The "linux,stdout-path" property
1563 in the chosen node is set to point to the correct serial node.
1564 This option currently references CONFIG_CONS_INDEX, which is
1565 incorrect when used with device tree as this option does not
1566 exist / should not be used.
1568 config FDT_FIXUP_PARTITIONS
1569 bool "Overwrite MTD partitions in DTS through defined in 'mtdparts'"
1571 Allow overwriting defined partitions in the device tree blob
1572 using partition info defined in the 'mtdparts' environment
1576 bool "FDT tools for simplefb support"
1578 Enable the fdt tools to manage the simple fb nodes in device tree.
1579 These functions can be used by board to indicate to the OS
1580 the presence of the simple frame buffer with associated reserved
1583 config ARCH_FIXUP_FDT_MEMORY
1584 bool "Enable arch_fixup_memory_banks() call"
1587 Enable FDT memory map syncup before OS boot. This feature can be
1588 used for booting OS with different memory setup where the part of
1589 the memory location should be used for different purpose.
1596 bool "Enable boot arguments"
1598 Provide boot arguments to bootm command. Boot arguments are specified
1599 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1600 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1601 will be undefined and won't take any space in U-Boot image.
1604 string "Boot arguments"
1605 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1607 This can be used to pass arguments to the bootm command. The value of
1608 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1609 this value will also override the "chosen" node in FDT blob.
1611 config BOOTARGS_SUBST
1612 bool "Support substituting strings in boot arguments"
1614 This allows substituting string values in the boot arguments. These
1615 are applied after the commandline has been built.
1617 One use for this is to insert the root-disk UUID into the command
1618 line where bootargs contains "root=${uuid}"
1620 setenv bootargs "console= root=${uuid}"
1621 # Set the 'uuid' environment variable
1622 part uuid mmc 2:2 uuid
1624 # Command-line substitution will put the real uuid into the
1625 # kernel command line
1628 config USE_BOOTCOMMAND
1629 bool "Enable a default value for bootcmd"
1632 Provide a default value for the bootcmd entry in the environment. If
1633 autoboot is enabled this is what will be run automatically. Enable
1634 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1635 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1636 won't take any space in U-Boot image.
1639 string "bootcmd value"
1640 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1641 default "bootflow scan -lb" if BOOTSTD_DEFAULTS && CMD_BOOTFLOW_FULL
1642 default "bootflow scan" if BOOTSTD_DEFAULTS && !CMD_BOOTFLOW_FULL
1643 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1645 This is the string of commands that will be used as bootcmd and if
1646 AUTOBOOT is set, automatically run.
1649 bool "Enable preboot"
1652 When this option is enabled, the existence of the environment
1653 variable "preboot" will be checked immediately before starting the
1654 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1655 entering interactive mode.
1657 This feature is especially useful when "preboot" is automatically
1658 generated or modified. For example, the boot code can modify the
1659 "preboot" when a user holds down a certain combination of keys.
1662 string "preboot default value"
1663 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1664 default "usb start" if USB_KEYBOARD
1667 This is the default of "preboot" environment variable.
1669 config PREBOOT_DEFINED
1671 default y if PREBOOT != ""
1673 config DEFAULT_FDT_FILE
1674 string "Default fdt file"
1676 This option is used to set the default fdt file to boot OS.
1678 config SAVE_PREV_BL_FDT_ADDR
1680 bool "Saves fdt address, passed by the previous bootloader, to env var"
1682 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1683 enable this option to save fdt address, passed by the
1684 previous bootloader for future use.
1685 Address is saved to `prevbl_fdt_addr` environment variable.
1687 If no fdt was provided by previous bootloader, no env variables
1690 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1692 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1694 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1695 enable this option to save initramfs address, passed by the
1696 previous bootloader for future use.
1697 Address is saved to `prevbl_initrd_start_addr` environment variable.
1699 If no initramfs was provided by previous bootloader, no env variables
1702 menu "Configuration editor"
1705 bool "Configuration editor"
1708 Provides a way to deal with board configuration and present it to
1709 the user for adjustment.
1711 This is intended to provide both graphical and text-based user
1712 interfaces, but only graphical is support at present.
1714 endmenu # Configuration editor