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 "Flattened Image Tree (FIT)"
30 This option allows you to boot the new uImage structure,
31 Flattened Image Tree. FIT is formally a FDT, which can include
32 images of various types (kernel, FDT blob, ramdisk, etc.)
33 in a single blob. To boot this new uImage structure,
34 pass the address of the blob to the "bootm" command.
35 FIT is very flexible, supporting compression, multiple images,
36 multiple configurations, verification through hashing and also
37 verified boot (secure boot using RSA).
41 config FIT_EXTERNAL_OFFSET
42 hex "FIT external data offset"
45 This specifies a data offset in fit image.
46 The offset is from data payload offset to the beginning of
47 fit image header. When specifies a offset, specific data
48 could be put in the hole between data payload and fit image
49 header, such as CSF data on i.MX platform.
52 bool "Do a full check of the FIT before using it"
55 Enable this do a full check of the FIT to make sure it is valid. This
56 helps to protect against carefully crafted FITs which take advantage
57 of bugs or omissions in the code. This includes a bad structure,
58 multiple root nodes and the like.
61 bool "Enable signature verification of FIT uImages"
66 select IMAGE_SIGN_INFO
69 This option enables signature verification of FIT uImages,
70 using a hash signed and verified using RSA. If
71 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
72 hashing is available using hardware, then the RSA library will use
73 it. See doc/uImage.FIT/signature.txt for more details.
75 WARNING: When relying on signed FIT images with a required signature
76 check the legacy image format is disabled by default, so that
77 unsigned images cannot be loaded. If a board needs the legacy image
78 format support in this case, enable it using
79 CONFIG_LEGACY_IMAGE_FORMAT.
81 config FIT_SIGNATURE_MAX_SIZE
82 hex "Max size of signed FIT structures"
83 depends on FIT_SIGNATURE
86 This option sets a max size in bytes for verified FIT uImages.
87 A sane value of 256MB protects corrupted DTB structures from overlapping
88 device memory. Assure this size does not extend past expected storage
92 bool "Support rsassa-pss signature scheme of FIT image contents"
93 depends on FIT_SIGNATURE
95 Enable this to support the pss padding algorithm as described
96 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
99 bool "Enable ciphering data in a FIT uImages"
103 Enable the feature of data ciphering/unciphering in the tool mkimage
104 and in the u-boot support of the FIT image.
107 bool "Show verbose messages when FIT images fail"
109 Generally a system will have valid FIT images so debug messages
110 are a waste of code space. If you are debugging your images then
111 you can enable this option to get more verbose information about
114 config FIT_BEST_MATCH
115 bool "Select the best match for the kernel device tree"
117 When no configuration is explicitly selected, default to the
118 one whose fdt's compatibility field best matches that of
119 U-Boot itself. A match is considered "best" if it matches the
120 most specific compatibility entry of U-Boot's fdt's root node.
121 The order of entries in the configuration's fdt is ignored.
123 config FIT_IMAGE_POST_PROCESS
124 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
125 depends on SOCFPGA_SECURE_VAB_AUTH
127 Allows doing any sort of manipulation to blobs after they got extracted
128 from FIT images like stripping off headers or modifying the size of the
129 blob, verification, authentication, decryption etc. in a platform or
130 board specific way. In order to use this feature a platform or board-
131 specific implementation of board_fit_image_post_process() must be
132 provided. Also, anything done during this post-processing step would
133 need to be comprehended in how the images were prepared before being
134 injected into the FIT creation (i.e. the blobs would have been pre-
135 processed before being added to the FIT image).
138 bool "Support FIT printing"
141 Support printing the content of the fitImage in a verbose manner.
144 bool "Support Flattened Image Tree within SPL"
150 bool "Support FIT printing within SPL"
153 Support printing the content of the fitImage in a verbose manner in SPL.
155 config SPL_FIT_FULL_CHECK
156 bool "Do a full check of the FIT before using it"
159 Enable this do a full check of the FIT to make sure it is valid. This
160 helps to protect against carefully crafted FITs which take advantage
161 of bugs or omissions in the code. This includes a bad structure,
162 multiple root nodes and the like.
164 config SPL_FIT_SIGNATURE
165 bool "Enable signature verification of FIT firmware within SPL"
167 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
174 select SPL_IMAGE_SIGN_INFO
175 select SPL_FIT_FULL_CHECK
177 config SPL_FIT_SIGNATURE_MAX_SIZE
178 hex "Max size of signed FIT structures in SPL"
179 depends on SPL_FIT_SIGNATURE
182 This option sets a max size in bytes for verified FIT uImages.
183 A sane value of 256MB protects corrupted DTB structures from overlapping
184 device memory. Assure this size does not extend past expected storage
187 config SPL_FIT_RSASSA_PSS
188 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
189 depends on SPL_FIT_SIGNATURE
191 Enable this to support the pss padding algorithm as described
192 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
195 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
199 Normally with the SPL framework a legacy image is generated as part
200 of the build. This contains U-Boot along with information as to
201 where it should be loaded. This option instead enables generation
202 of a FIT (Flat Image Tree) which provides more flexibility. In
203 particular it can handle selecting from multiple device tree
204 and passing the correct one to U-Boot.
206 This path has the following limitations:
208 1. "loadables" images, other than FDTs, which do not have a "load"
209 property will not be loaded. This limitation also applies to FPGA
210 images with the correct "compatible" string.
211 2. For FPGA images, the supported "compatible" list is in the
212 doc/uImage.FIT/source_file_format.txt.
213 3. FDTs are only loaded for images with an "os" property of "u-boot".
214 "linux" images are also supported with Falcon boot mode.
216 config SPL_LOAD_FIT_ADDRESS
217 hex "load address of fit image"
218 depends on SPL_LOAD_FIT
221 Specify the load address of the fit image that will be loaded
224 config SPL_LOAD_FIT_APPLY_OVERLAY
225 bool "Enable SPL applying DT overlays from FIT"
226 depends on SPL_LOAD_FIT
227 select OF_LIBFDT_OVERLAY
229 The device tree is loaded from the FIT image. Allow the SPL to
230 also load device-tree overlays from the FIT image an apply them
231 over the device tree.
233 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
234 depends on SPL_LOAD_FIT_APPLY_OVERLAY
236 hex "size of temporary buffer used to load the overlays"
238 The size of the area where the overlays will be loaded and
239 uncompress. Must be at least as large as biggest overlay
242 config SPL_LOAD_FIT_FULL
243 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
246 Normally with the SPL framework a legacy image is generated as part
247 of the build. This contains U-Boot along with information as to
248 where it should be loaded. This option instead enables generation
249 of a FIT (Flat Image Tree) which provides more flexibility. In
250 particular it can handle selecting from multiple device tree
251 and passing the correct one to U-Boot.
253 config SPL_FIT_IMAGE_POST_PROCESS
254 bool "Enable post-processing of FIT artifacts after loading by the SPL"
255 depends on SPL_LOAD_FIT
256 default y if TI_SECURE_DEVICE
258 Allows doing any sort of manipulation to blobs after they got extracted
259 from the U-Boot FIT image like stripping off headers or modifying the
260 size of the blob, verification, authentication, decryption etc. in a
261 platform or board specific way. In order to use this feature a platform
262 or board-specific implementation of board_fit_image_post_process() must
263 be provided. Also, anything done during this post-processing step would
264 need to be comprehended in how the images were prepared before being
265 injected into the FIT creation (i.e. the blobs would have been pre-
266 processed before being added to the FIT image).
268 config SPL_FIT_SOURCE
269 string ".its source file for U-Boot FIT image"
272 Specifies a (platform specific) FIT source file to generate the
273 U-Boot FIT image. This could specify further image to load and/or
276 config USE_SPL_FIT_GENERATOR
277 bool "Use a script to generate the .its script"
279 default y if SPL_FIT && ARCH_ZYNQMP
281 config SPL_FIT_GENERATOR
282 string ".its file generator script for U-Boot FIT image"
283 depends on USE_SPL_FIT_GENERATOR
284 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
286 Specifies a (platform specific) script file to generate the FIT
287 source file used to build the U-Boot FIT image file. This gets
288 passed a list of supported device tree file stub names to
289 include in the generated image.
294 bool "Support Flattened Image Tree within VPL"
301 bool "Support FIT printing within VPL"
305 Support printing the content of the fitImage in a verbose manner in VPL.
307 config VPL_FIT_FULL_CHECK
308 bool "Do a full check of the FIT before using it"
311 Enable this do a full check of the FIT to make sure it is valid. This
312 helps to protect against carefully crafted FITs which take advantage
313 of bugs or omissions in the code. This includes a bad structure,
314 multiple root nodes and the like.
316 config VPL_FIT_SIGNATURE
317 bool "Enable signature verification of FIT firmware within VPL"
326 select VPL_IMAGE_SIGN_INFO
327 select VPL_FIT_FULL_CHECK
329 config VPL_FIT_SIGNATURE_MAX_SIZE
330 hex "Max size of signed FIT structures in VPL"
331 depends on VPL_FIT_SIGNATURE
334 This option sets a max size in bytes for verified FIT uImages.
335 A sane value of 256MB protects corrupted DTB structures from overlapping
336 device memory. Assure this size does not extend past expected storage
347 Utilities for parsing PXE file formats.
350 bool # Common defaults for standard boot and distroboot
351 imply USE_BOOTCOMMAND
352 select CMD_ENV_EXISTS
356 select CMD_FS_GENERIC
357 select CMD_PART if PARTITIONS
358 select CMD_DHCP if CMD_NET
359 select CMD_PING if CMD_NET
360 select CMD_PXE if CMD_NET
361 select SUPPORT_RAW_INITRD
362 select ENV_VARS_UBOOT_CONFIG
363 select CMD_BOOTI if ARM64
364 select CMD_BOOTZ if ARM && !ARM64
370 These are not required but are commonly needed to support a good
371 selection of booting methods. Enable this to improve the capability
372 of U-Boot to boot various images. Currently much functionality is
373 tied to enabling the command that exercises it.
378 depends on DM && OF_CONTROL && BLK
380 U-Boot supports a standard way of locating something to boot,
381 typically an Operating System such as Linux, provided by a distro such
382 as Arch Linux or Debian. Enable this to support iterating through
383 available bootdevs and using bootmeths to find bootflows suitable for
386 Standard boot is not a standard way of booting, just a framework
387 within U-Boot for supporting all the different ways that exist.
391 - bootdev - a device which can hold a distro (e.g. MMC)
392 - bootmeth - a method to scan a bootdev to find bootflows (owned by
394 - bootflow - a description of how to boot (owned by the distro)
399 bool "Standard boot support in SPL"
400 depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK
403 This enables standard boot in SPL. This is neeeded so that VBE
404 (Verified Boot for Embedded) can be used, since it depends on standard
405 boot. It is enabled by default since the main purpose of VPL is to
406 handle the firmware part of VBE.
409 bool "Standard boot support in VPL"
410 depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK
413 This enables standard boot in SPL. This is neeeded so that VBE
414 (Verified Boot for Embedded) can be used, since it depends on standard
415 boot. It is enabled by default since the main purpose of VPL is to
416 handle the firmware part of VBE.
419 bool "Enhanced features for standard boot"
422 This enables various useful features for standard boot, which are not
423 essential for operation:
425 - bootdev, bootmeth commands
426 - extra features in the bootflow command
427 - support for selecting the ordering of bootmeths ("bootmeth order")
428 - support for selecting the ordering of bootdevs using the devicetree
429 as well as the "boot_targets" environment variable
431 config BOOTSTD_DEFAULTS
432 bool "Select some common defaults for standard boot"
434 imply USE_BOOTCOMMAND
436 select BOOTMETH_DISTRO
438 These are not required but are commonly needed to support a good
439 selection of booting methods. Enable this to improve the capability
440 of U-Boot to boot various images.
442 config BOOTSTD_BOOTCOMMAND
443 bool "Use bootstd to boot"
444 default y if !DISTRO_DEFAULTS
446 Enable this to select a default boot-command suitable for booting
447 with standard boot. This can be overridden by the board if needed,
448 but the default command should be enough for most boards which use
451 For now this is only selected if distro boot is NOT used, since
452 standard boot does not support all of the features of distro boot
455 config BOOTMETH_GLOBAL
458 Add support for global bootmeths. This feature is used by VBE and
459 EFI bootmgr, since they take full control over which bootdevs are
463 bool "Bootdev support for Chromium OS"
464 depends on X86 || ARM || SANDBOX
467 select PARTITION_TYPE_GUID
468 select PARTITION_UUIDS
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 ARCH_FIXUP_FDT_MEMORY
697 bool "Enable arch_fixup_memory_banks() call"
700 Enable FDT memory map syncup before OS boot. This feature can be
701 used for booting OS with different memory setup where the part of
702 the memory location should be used for different purpose.
705 bool "Support booting Chrome OS"
707 Chrome OS requires U-Boot to set up a table indicating the boot mode
708 (e.g. Developer mode) and a few other things. Enable this if you are
709 booting on a Chromebook to avoid getting an error about an invalid
712 config CHROMEOS_VBOOT
713 bool "Support Chrome OS verified boot"
715 This is intended to enable the full Chrome OS verified boot support
716 in U-Boot. It is not actually implemented in the U-Boot source code
717 at present, so this option is always set to 'n'. It allows
718 distinguishing between booting Chrome OS in a basic way (developer
719 mode) and a full boot.
725 bool "Freescale PBL(pre-boot loader) image format support"
726 select SYS_RAMBOOT if PPC
728 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
729 For more details refer to doc/README.pblimage
732 prompt "Freescale PBL (or predecessor) load location"
733 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
734 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
738 bool "Freescale PBL (or similar) is found on SD card"
741 bool "Freescale PBL (or similar) is found on SPI flash"
744 bool "Freescale PBL (or similar) is not used in this case"
748 config FSL_FIXED_MMC_LOCATION
749 bool "PBL MMC is at a fixed location"
750 depends on SDCARD && !RAMBOOT_PBL
752 config ESDHC_HC_BLK_ADDR
754 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
756 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
757 code length of these soc specify the memory address in block address
758 format. Block length is fixed to 512 bytes as per the SD High
759 Capacity specification.
761 config SYS_FSL_PBL_PBI
762 string "PBI(pre-boot instructions) commands for the PBL image"
763 depends on RAMBOOT_PBL
765 PBI commands can be used to configure SoC before it starts the execution.
766 Please refer doc/README.pblimage for more details.
768 config SYS_FSL_PBL_RCW
769 string "Aadditional RCW (Power on reset configuration) for the PBL image"
770 depends on RAMBOOT_PBL
772 Enables addition of RCW (Power on reset configuration) in built image.
773 Please refer doc/README.pblimage for more details.
775 config SYS_BOOT_RAMDISK_HIGH
776 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
777 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
781 Enable initrd_high functionality. If defined then the initrd_high
782 feature is enabled and the boot* ramdisk subcommand is enabled.
784 endmenu # Boot images
786 config DISTRO_DEFAULTS
787 bool "Select defaults suitable for booting general purpose Linux distributions"
790 select CMDLINE_EDITING
795 Select this to enable various options and commands which are suitable
796 for building u-boot for booting general purpose Linux distributions.
801 bool "Boot timing and reporting"
803 Enable recording of boot time while booting. To use it, insert
804 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
805 bootstage.h. Only a single entry is recorded for each ID. You can
806 give the entry a name with bootstage_mark_name(). You can also
807 record elapsed time in a particular stage using bootstage_start()
808 before starting and bootstage_accum() when finished. Bootstage will
809 add up all the accumulated time and report it.
811 Normally, IDs are defined in bootstage.h but a small number of
812 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
815 Calls to show_boot_progress() will also result in log entries but
816 these will not have names.
819 bool "Boot timing and reported in SPL"
820 depends on BOOTSTAGE && SPL
822 Enable recording of boot time in SPL. To make this visible to U-Boot
823 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
824 information when SPL finishes and load it when U-Boot proper starts
828 bool "Boot timing and reported in TPL"
829 depends on BOOTSTAGE && TPL
831 Enable recording of boot time in SPL. To make this visible to U-Boot
832 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
833 information when TPL finishes and load it when U-Boot proper starts
836 config BOOTSTAGE_REPORT
837 bool "Display a detailed boot timing report before booting the OS"
840 Enable output of a boot time report just before the OS is booted.
841 This shows how long it took U-Boot to go through each stage of the
842 boot process. The report looks something like this:
844 Timer summary in microseconds:
847 3,575,678 3,575,678 board_init_f start
848 3,575,695 17 arch_cpu_init A9
849 3,575,777 82 arch_cpu_init done
850 3,659,598 83,821 board_init_r start
851 3,910,375 250,777 main_loop
852 29,916,167 26,005,792 bootm_start
853 30,361,327 445,160 start_kernel
855 config BOOTSTAGE_RECORD_COUNT
856 int "Number of boot stage records to store"
860 This is the size of the bootstage record list and is the maximum
861 number of bootstage records that can be recorded.
863 config SPL_BOOTSTAGE_RECORD_COUNT
864 int "Number of boot stage records to store for SPL"
865 depends on SPL_BOOTSTAGE
868 This is the size of the bootstage record list and is the maximum
869 number of bootstage records that can be recorded.
871 config TPL_BOOTSTAGE_RECORD_COUNT
872 int "Number of boot stage records to store for TPL"
873 depends on TPL_BOOTSTAGE
876 This is the size of the bootstage record list and is the maximum
877 number of bootstage records that can be recorded.
880 bool "Store boot timing information in the OS device tree"
883 Stash the bootstage information in the FDT. A root 'bootstage'
884 node is created with each bootstage id as a child. Each child
885 has a 'name' property and either 'mark' containing the
886 mark time in microseconds, or 'accum' containing the
887 accumulated time for that bootstage id in microseconds.
892 name = "board_init_f";
901 Code in the Linux kernel can find this in /proc/devicetree.
903 config BOOTSTAGE_STASH
904 bool "Stash the boot timing information in memory before booting OS"
907 Some OSes do not support device tree. Bootstage can instead write
908 the boot timing information in a binary format at a given address.
909 This happens through a call to bootstage_stash(), typically in
910 the CPU's cleanup_before_linux() function. You can use the
911 'bootstage stash' and 'bootstage unstash' commands to do this on
914 config BOOTSTAGE_STASH_ADDR
915 hex "Address to stash boot timing information"
918 Provide an address which will not be overwritten by the OS when it
919 starts, so that it can read this information when ready.
921 config BOOTSTAGE_STASH_SIZE
922 hex "Size of boot timing stash region"
925 This should be large enough to hold the bootstage stash. A value of
926 4096 (4KiB) is normally plenty.
928 config SHOW_BOOT_PROGRESS
929 bool "Show boot progress in a board-specific manner"
931 Defining this option allows to add some board-specific code (calling
932 a user-provided function show_boot_progress(int) that enables you to
933 show the system's boot progress on some display (for example, some
934 LEDs) on your board. At the moment, the following checkpoints are
937 Legacy uImage format:
940 1 common/cmd_bootm.c before attempting to boot an image
941 -1 common/cmd_bootm.c Image header has bad magic number
942 2 common/cmd_bootm.c Image header has correct magic number
943 -2 common/cmd_bootm.c Image header has bad checksum
944 3 common/cmd_bootm.c Image header has correct checksum
945 -3 common/cmd_bootm.c Image data has bad checksum
946 4 common/cmd_bootm.c Image data has correct checksum
947 -4 common/cmd_bootm.c Image is for unsupported architecture
948 5 common/cmd_bootm.c Architecture check OK
949 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
950 6 common/cmd_bootm.c Image Type check OK
951 -6 common/cmd_bootm.c gunzip uncompression error
952 -7 common/cmd_bootm.c Unimplemented compression type
953 7 common/cmd_bootm.c Uncompression OK
954 8 common/cmd_bootm.c No uncompress/copy overwrite error
955 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
957 9 common/image.c Start initial ramdisk verification
958 -10 common/image.c Ramdisk header has bad magic number
959 -11 common/image.c Ramdisk header has bad checksum
960 10 common/image.c Ramdisk header is OK
961 -12 common/image.c Ramdisk data has bad checksum
962 11 common/image.c Ramdisk data has correct checksum
963 12 common/image.c Ramdisk verification complete, start loading
964 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
965 13 common/image.c Start multifile image verification
966 14 common/image.c No initial ramdisk, no multifile, continue.
968 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
970 -30 arch/powerpc/lib/board.c Fatal error, hang the system
971 -31 post/post.c POST test failed, detected by post_output_backlog()
972 -32 post/post.c POST test failed, detected by post_run_single()
974 34 common/cmd_doc.c before loading a Image from a DOC device
975 -35 common/cmd_doc.c Bad usage of "doc" command
976 35 common/cmd_doc.c correct usage of "doc" command
977 -36 common/cmd_doc.c No boot device
978 36 common/cmd_doc.c correct boot device
979 -37 common/cmd_doc.c Unknown Chip ID on boot device
980 37 common/cmd_doc.c correct chip ID found, device available
981 -38 common/cmd_doc.c Read Error on boot device
982 38 common/cmd_doc.c reading Image header from DOC device OK
983 -39 common/cmd_doc.c Image header has bad magic number
984 39 common/cmd_doc.c Image header has correct magic number
985 -40 common/cmd_doc.c Error reading Image from DOC device
986 40 common/cmd_doc.c Image header has correct magic number
987 41 common/cmd_ide.c before loading a Image from a IDE device
988 -42 common/cmd_ide.c Bad usage of "ide" command
989 42 common/cmd_ide.c correct usage of "ide" command
990 -43 common/cmd_ide.c No boot device
991 43 common/cmd_ide.c boot device found
992 -44 common/cmd_ide.c Device not available
993 44 common/cmd_ide.c Device available
994 -45 common/cmd_ide.c wrong partition selected
995 45 common/cmd_ide.c partition selected
996 -46 common/cmd_ide.c Unknown partition table
997 46 common/cmd_ide.c valid partition table found
998 -47 common/cmd_ide.c Invalid partition type
999 47 common/cmd_ide.c correct partition type
1000 -48 common/cmd_ide.c Error reading Image Header on boot device
1001 48 common/cmd_ide.c reading Image Header from IDE device OK
1002 -49 common/cmd_ide.c Image header has bad magic number
1003 49 common/cmd_ide.c Image header has correct magic number
1004 -50 common/cmd_ide.c Image header has bad checksum
1005 50 common/cmd_ide.c Image header has correct checksum
1006 -51 common/cmd_ide.c Error reading Image from IDE device
1007 51 common/cmd_ide.c reading Image from IDE device OK
1008 52 common/cmd_nand.c before loading a Image from a NAND device
1009 -53 common/cmd_nand.c Bad usage of "nand" command
1010 53 common/cmd_nand.c correct usage of "nand" command
1011 -54 common/cmd_nand.c No boot device
1012 54 common/cmd_nand.c boot device found
1013 -55 common/cmd_nand.c Unknown Chip ID on boot device
1014 55 common/cmd_nand.c correct chip ID found, device available
1015 -56 common/cmd_nand.c Error reading Image Header on boot device
1016 56 common/cmd_nand.c reading Image Header from NAND device OK
1017 -57 common/cmd_nand.c Image header has bad magic number
1018 57 common/cmd_nand.c Image header has correct magic number
1019 -58 common/cmd_nand.c Error reading Image from NAND device
1020 58 common/cmd_nand.c reading Image from NAND device OK
1022 -60 common/env_common.c Environment has a bad CRC, using default
1024 64 net/eth.c starting with Ethernet configuration.
1025 -64 net/eth.c no Ethernet found.
1026 65 net/eth.c Ethernet found.
1028 -80 common/cmd_net.c usage wrong
1029 80 common/cmd_net.c before calling net_loop()
1030 -81 common/cmd_net.c some error in net_loop() occurred
1031 81 common/cmd_net.c net_loop() back without error
1032 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1033 82 common/cmd_net.c trying automatic boot
1034 83 common/cmd_net.c running "source" command
1035 -83 common/cmd_net.c some error in automatic boot or "source" command
1036 84 common/cmd_net.c end without errors
1041 100 common/cmd_bootm.c Kernel FIT Image has correct format
1042 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1043 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1044 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1045 102 common/cmd_bootm.c Kernel unit name specified
1046 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1047 103 common/cmd_bootm.c Found configuration node
1048 104 common/cmd_bootm.c Got kernel subimage node offset
1049 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1050 105 common/cmd_bootm.c Kernel subimage hash verification OK
1051 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1052 106 common/cmd_bootm.c Architecture check OK
1053 -106 common/cmd_bootm.c Kernel subimage has wrong type
1054 107 common/cmd_bootm.c Kernel subimage type OK
1055 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1056 108 common/cmd_bootm.c Got kernel subimage data/size
1057 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1058 -109 common/cmd_bootm.c Can't get kernel subimage type
1059 -110 common/cmd_bootm.c Can't get kernel subimage comp
1060 -111 common/cmd_bootm.c Can't get kernel subimage os
1061 -112 common/cmd_bootm.c Can't get kernel subimage load address
1062 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1064 120 common/image.c Start initial ramdisk verification
1065 -120 common/image.c Ramdisk FIT image has incorrect format
1066 121 common/image.c Ramdisk FIT image has correct format
1067 122 common/image.c No ramdisk subimage unit name, using configuration
1068 -122 common/image.c Can't get configuration for ramdisk subimage
1069 123 common/image.c Ramdisk unit name specified
1070 -124 common/image.c Can't get ramdisk subimage node offset
1071 125 common/image.c Got ramdisk subimage node offset
1072 -125 common/image.c Ramdisk subimage hash verification failed
1073 126 common/image.c Ramdisk subimage hash verification OK
1074 -126 common/image.c Ramdisk subimage for unsupported architecture
1075 127 common/image.c Architecture check OK
1076 -127 common/image.c Can't get ramdisk subimage data/size
1077 128 common/image.c Got ramdisk subimage data/size
1078 129 common/image.c Can't get ramdisk load address
1079 -129 common/image.c Got ramdisk load address
1081 -130 common/cmd_doc.c Incorrect FIT image format
1082 131 common/cmd_doc.c FIT image format OK
1084 -140 common/cmd_ide.c Incorrect FIT image format
1085 141 common/cmd_ide.c FIT image format OK
1087 -150 common/cmd_nand.c Incorrect FIT image format
1088 151 common/cmd_nand.c FIT image format OK
1090 config SPL_SHOW_BOOT_PROGRESS
1091 bool "Show boot progress in a board-specific manner in SPL"
1094 Defining this option allows to add some board-specific code (calling
1095 a user-provided function show_boot_progress(int) that enables you to
1096 show the system's boot progress on some display (for example, some
1097 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1104 bool "Support for booting from NOR flash"
1107 Enabling this will make a U-Boot binary that is capable of being
1108 booted via NOR. In this case we will enable certain pinmux early
1109 as the ROM only partially sets up pinmux. We also default to using
1110 NOR for environment.
1113 bool "Support for booting from NAND flash"
1116 Enabling this will make a U-Boot binary that is capable of being
1117 booted via NAND flash. This is not a must, some SoCs need this,
1121 bool "Support for booting from ONENAND"
1124 Enabling this will make a U-Boot binary that is capable of being
1125 booted via ONENAND. This is not a must, some SoCs need this,
1129 bool "Support for booting from QSPI flash"
1131 Enabling this will make a U-Boot binary that is capable of being
1132 booted via QSPI flash. This is not a must, some SoCs need this,
1136 bool "Support for booting from SATA"
1138 Enabling this will make a U-Boot binary that is capable of being
1139 booted via SATA. This is not a must, some SoCs need this,
1143 bool "Support for booting from SD/EMMC"
1145 Enabling this will make a U-Boot binary that is capable of being
1146 booted via SD/EMMC. This is not a must, some SoCs need this,
1150 bool "Support for booting from SD/EMMC and enable QSPI"
1152 Enabling this will make a U-Boot binary that is capable of being
1153 booted via SD/EMMC while enabling QSPI on the platform as well. This
1154 is not a must, some SoCs need this, some not.
1157 bool "Support for booting from SPI flash"
1159 Enabling this will make a U-Boot binary that is capable of being
1160 booted via SPI flash. This is not a must, some SoCs need this,
1165 menu "Autoboot options"
1171 This enables the autoboot. See doc/README.autoboot for detail.
1174 int "delay in seconds before automatically booting"
1178 Delay before automatically running bootcmd;
1179 set to 0 to autoboot with no delay, but you can stop it by key input.
1180 set to -1 to disable autoboot.
1181 set to -2 to autoboot with no delay and not check for abort
1183 If this value is >= 0 then it is also used for the default delay
1184 before starting the default entry in bootmenu. If it is < 0 then
1185 a default value of 10s is used.
1187 See doc/README.autoboot for details.
1189 config AUTOBOOT_KEYED
1190 bool "Stop autobooting via specific input key / string"
1192 This option enables stopping (aborting) of the automatic
1193 boot feature only by issuing a specific input key or
1194 string. If not enabled, any input key will abort the
1195 U-Boot automatic booting process and bring the device
1196 to the U-Boot prompt for user input.
1198 config AUTOBOOT_FLUSH_STDIN
1199 bool "Enable flushing stdin before starting to read the password"
1200 depends on AUTOBOOT_KEYED && !SANDBOX
1202 When this option is enabled stdin buffer will be flushed before
1203 starting to read the password.
1204 This can't be enabled for the sandbox as flushing stdin would
1205 break the autoboot unit tests.
1207 config AUTOBOOT_PROMPT
1208 string "Autoboot stop prompt"
1209 depends on AUTOBOOT_KEYED
1210 default "Autoboot in %d seconds\\n"
1212 This string is displayed before the boot delay selected by
1213 CONFIG_BOOTDELAY starts. If it is not defined there is no
1214 output indicating that autoboot is in progress.
1216 Note that this define is used as the (only) argument to a
1217 printf() call, so it may contain '%' format specifications,
1218 provided that it also includes, sepearated by commas exactly
1219 like in a printf statement, the required arguments. It is
1220 the responsibility of the user to select only such arguments
1221 that are valid in the given context.
1223 config AUTOBOOT_ENCRYPTION
1224 bool "Enable encryption in autoboot stopping"
1225 depends on AUTOBOOT_KEYED
1227 This option allows a string to be entered into U-Boot to stop the
1229 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1231 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1232 to the crypt-based functionality and be compared against the
1233 string in the environment variable 'bootstopkeycrypt'.
1234 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1235 and compared against the hash in the environment variable
1236 'bootstopkeysha256'.
1237 If it matches in either case then boot stops and
1238 a command-line prompt is presented.
1239 This provides a way to ship a secure production device which can also
1240 be accessed at the U-Boot command line.
1242 config AUTOBOOT_SHA256_FALLBACK
1243 bool "Allow fallback from crypt-hashed password to sha256"
1244 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1246 This option adds support to fall back from crypt-hashed
1247 passwords to checking a SHA256 hashed password in case the
1248 'bootstopusesha256' environment variable is set to 'true'.
1250 config AUTOBOOT_DELAY_STR
1251 string "Delay autobooting via specific input key / string"
1252 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1254 This option delays the automatic boot feature by issuing
1255 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1256 or the environment variable "bootdelaykey" is specified
1257 and this string is received from console input before
1258 autoboot starts booting, U-Boot gives a command prompt. The
1259 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1260 used, otherwise it never times out.
1262 config AUTOBOOT_STOP_STR
1263 string "Stop autobooting via specific input key / string"
1264 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1266 This option enables stopping (aborting) of the automatic
1267 boot feature only by issuing a specific input key or
1268 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1269 variable "bootstopkey" is specified and this string is
1270 received from console input before autoboot starts booting,
1271 U-Boot gives a command prompt. The U-Boot prompt never
1272 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1274 config AUTOBOOT_KEYED_CTRLC
1275 bool "Enable Ctrl-C autoboot interruption"
1276 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1278 This option allows for the boot sequence to be interrupted
1279 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1280 Setting this variable provides an escape sequence from the
1281 limited "password" strings.
1283 config AUTOBOOT_NEVER_TIMEOUT
1284 bool "Make the password entry never time-out"
1285 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1287 This option removes the timeout from the password entry
1288 when the user first presses the <Enter> key before entering
1289 any other character.
1291 config AUTOBOOT_STOP_STR_ENABLE
1292 bool "Enable fixed string to stop autobooting"
1293 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1295 This option enables the feature to add a fixed stop
1296 string that is defined at compile time.
1297 In every case it will be tried to load the stop
1298 string from the environment.
1299 In case this is enabled and there is no stop string
1300 in the environment, this will be used as default value.
1302 config AUTOBOOT_STOP_STR_CRYPT
1303 string "Stop autobooting via crypt-hashed password"
1304 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1306 This option adds the feature to only stop the autobooting,
1307 and therefore boot into the U-Boot prompt, when the input
1308 string / password matches a values that is hashed via
1309 one of the supported crypt-style password hashing options
1310 and saved in the environment variable "bootstopkeycrypt".
1312 config AUTOBOOT_STOP_STR_SHA256
1313 string "Stop autobooting via SHA256 hashed password"
1314 depends on AUTOBOOT_STOP_STR_ENABLE
1316 This option adds the feature to only stop the autobooting,
1317 and therefore boot into the U-Boot prompt, when the input
1318 string / password matches a values that is encypted via
1319 a SHA256 hash and saved in the environment variable
1320 "bootstopkeysha256". If the value in that variable
1321 includes a ":", the portion prior to the ":" will be treated
1324 config AUTOBOOT_USE_MENUKEY
1325 bool "Allow a specify key to run a menu from the environment"
1326 depends on !AUTOBOOT_KEYED
1328 If a specific key is pressed to stop autoboot, then the commands in
1329 the environment variable 'menucmd' are executed before boot starts.
1331 config AUTOBOOT_MENUKEY
1332 int "ASCII value of boot key to show a menu"
1334 depends on AUTOBOOT_USE_MENUKEY
1336 If this key is pressed to stop autoboot, then the commands in the
1337 environment variable 'menucmd' will be executed before boot starts.
1338 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1341 config AUTOBOOT_MENU_SHOW
1342 bool "Show a menu on boot"
1343 depends on CMD_BOOTMENU
1345 This enables the boot menu, controlled by environment variables
1346 defined by the board. The menu starts after running the 'preboot'
1347 environmnent variable (if enabled) and before handling the boot delay.
1348 See doc/usage/cmd/bootmenu.rst for more details.
1350 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1351 bool "Disallow bootmenu to enter the U-Boot console"
1352 depends on AUTOBOOT_MENU_SHOW
1354 If this option is enabled, user can not enter the U-Boot console from
1355 bootmenu. It increases the system security.
1358 bool "Boot retry feature"
1360 Allow for having the U-Boot command prompt time out and attempt
1361 to boot again. If the environment variable "bootretry" is found then
1362 its value is used, otherwise the retry timeout is
1363 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1364 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1366 config BOOT_RETRY_TIME
1367 int "Timeout in seconds before attempting to boot again"
1368 depends on BOOT_RETRY
1370 Time in seconds before the U-Boot prompt will timeout and boot will
1373 config BOOT_RETRY_MIN
1374 int "Minimum timeout in seconds for 'bootretry'"
1375 depends on BOOT_RETRY
1376 default BOOT_RETRY_TIME
1378 The minimum time in seconds that "bootretry" can be set to.
1380 config RESET_TO_RETRY
1381 bool "Reset the board to retry autoboot"
1382 depends on BOOT_RETRY
1384 After the countdown timed out, the board will be reset to restart
1389 menu "Image support"
1391 config IMAGE_PRE_LOAD
1392 bool "Image pre-load support"
1394 Enable an image pre-load stage in the SPL.
1395 This pre-load stage allows to do some manipulation
1396 or check (for example signature check) on an image
1397 before launching it.
1399 config SPL_IMAGE_PRE_LOAD
1400 bool "Image pre-load support within SPL"
1401 depends on SPL && IMAGE_PRE_LOAD
1403 Enable an image pre-load stage in the SPL.
1404 This pre-load stage allows to do some manipulation
1405 or check (for example signature check) on an image
1406 before launching it.
1408 config IMAGE_PRE_LOAD_SIG
1409 bool "Image pre-load signature support"
1410 depends on IMAGE_PRE_LOAD
1411 select FIT_SIGNATURE
1413 select RSA_VERIFY_WITH_PKEY
1415 Enable signature check support in the pre-load stage.
1416 For this feature a very simple header is added before
1417 the image with few fields:
1421 All other information (header size, type of signature,
1422 ...) are provided in the node /image/pre-load/sig of
1425 config SPL_IMAGE_PRE_LOAD_SIG
1426 bool "Image pre-load signature support witin SPL"
1427 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1428 select SPL_FIT_SIGNATURE
1430 select SPL_RSA_VERIFY_WITH_PKEY
1432 Enable signature check support in the pre-load stage in the SPL.
1433 For this feature a very simple header is added before
1434 the image with few fields:
1438 All other information (header size, type of signature,
1439 ...) are provided in the node /image/pre-load/sig of
1446 menu "Devicetree fixup"
1448 config OF_BOARD_SETUP
1449 bool "Set up board-specific details in device tree before boot"
1451 This causes U-Boot to call ft_board_setup() before booting into
1452 the Operating System. This function can set up various
1453 board-specific information in the device tree for use by the OS.
1454 The device tree is then passed to the OS.
1456 config OF_SYSTEM_SETUP
1457 bool "Set up system-specific details in device tree before boot"
1459 This causes U-Boot to call ft_system_setup() before booting into
1460 the Operating System. This function can set up various
1461 system-specific information in the device tree for use by the OS.
1462 The device tree is then passed to the OS.
1464 config OF_STDOUT_VIA_ALIAS
1465 bool "Update the device-tree stdout alias from U-Boot"
1467 This uses U-Boot's serial alias from the aliases node to update
1468 the device tree passed to the OS. The "linux,stdout-path" property
1469 in the chosen node is set to point to the correct serial node.
1470 This option currently references CONFIG_CONS_INDEX, which is
1471 incorrect when used with device tree as this option does not
1472 exist / should not be used.
1475 bool "FDT tools for simplefb support"
1477 Enable the fdt tools to manage the simple fb nodes in device tree.
1478 These functions can be used by board to indicate to the OS
1479 the presence of the simple frame buffer with associated reserved
1487 bool "Enable boot arguments"
1489 Provide boot arguments to bootm command. Boot arguments are specified
1490 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1491 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1492 will be undefined and won't take any space in U-Boot image.
1495 string "Boot arguments"
1496 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1498 This can be used to pass arguments to the bootm command. The value of
1499 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1500 this value will also override the "chosen" node in FDT blob.
1502 config BOOTARGS_SUBST
1503 bool "Support substituting strings in boot arguments"
1505 This allows substituting string values in the boot arguments. These
1506 are applied after the commandline has been built.
1508 One use for this is to insert the root-disk UUID into the command
1509 line where bootargs contains "root=${uuid}"
1511 setenv bootargs "console= root=${uuid}"
1512 # Set the 'uuid' environment variable
1513 part uuid mmc 2:2 uuid
1515 # Command-line substitution will put the real uuid into the
1516 # kernel command line
1519 config USE_BOOTCOMMAND
1520 bool "Enable a default value for bootcmd"
1522 Provide a default value for the bootcmd entry in the environment. If
1523 autoboot is enabled this is what will be run automatically. Enable
1524 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1525 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1526 won't take any space in U-Boot image.
1529 string "bootcmd value"
1530 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1531 default "bootflow scan -lb" if BOOTSTD_DEFAULTS && CMD_BOOTFLOW_FULL
1532 default "bootflow scan" if BOOTSTD_DEFAULTS && !CMD_BOOTFLOW_FULL
1533 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1535 This is the string of commands that will be used as bootcmd and if
1536 AUTOBOOT is set, automatically run.
1539 bool "Enable preboot"
1541 When this option is enabled, the existence of the environment
1542 variable "preboot" will be checked immediately before starting the
1543 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1544 entering interactive mode.
1546 This feature is especially useful when "preboot" is automatically
1547 generated or modified. For example, the boot code can modify the
1548 "preboot" when a user holds down a certain combination of keys.
1551 string "preboot default value"
1552 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1553 default "usb start" if USB_KEYBOARD
1556 This is the default of "preboot" environment variable.
1558 config PREBOOT_DEFINED
1560 default y if PREBOOT != ""
1562 config DEFAULT_FDT_FILE
1563 string "Default fdt file"
1565 This option is used to set the default fdt file to boot OS.
1567 config SAVE_PREV_BL_FDT_ADDR
1569 bool "Saves fdt address, passed by the previous bootloader, to env var"
1571 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1572 enable this option to save fdt address, passed by the
1573 previous bootloader for future use.
1574 Address is saved to `prevbl_fdt_addr` environment variable.
1576 If no fdt was provided by previous bootloader, no env variables
1579 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1581 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1583 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1584 enable this option to save initramfs address, passed by the
1585 previous bootloader for future use.
1586 Address is saved to `prevbl_initrd_start_addr` environment variable.
1588 If no initramfs was provided by previous bootloader, no env variables
1591 menu "Configuration editor"
1594 bool "Configuration editor"
1597 Provides a way to deal with board configuration and present it to
1598 the user for adjustment.
1600 This is intended to provide both graphical and text-based user
1601 interfaces, but only graphical is support at present.
1603 endmenu # Configuration editor