5 config ANDROID_BOOT_IMAGE
6 bool "Enable support for Android Boot Images"
9 This enables support for booting images which use the Android
13 bool "Support Flattened Image Tree"
19 This option allows you to boot the new uImage structure,
20 Flattened Image Tree. FIT is formally a FDT, which can include
21 images of various types (kernel, FDT blob, ramdisk, etc.)
22 in a single blob. To boot this new uImage structure,
23 pass the address of the blob to the "bootm" command.
24 FIT is very flexible, supporting compression, multiple images,
25 multiple configurations, verification through hashing and also
26 verified boot (secure boot using RSA).
29 bool "Show image date and time when displaying image information"
32 When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of
33 an image is printed by image commands like bootm or iminfo. This
34 is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is
35 enabled, then U-Boot requires FITs to have a timestamp. If a FIT is
36 loaded that does not, the message 'Wrong FIT format: no timestamp'
39 config FIT_EXTERNAL_OFFSET
40 hex "FIT external data offset"
44 This specifies a data offset in fit image.
45 The offset is from data payload offset to the beginning of
46 fit image header. When specifies a offset, specific data
47 could be put in the hole between data payload and fit image
48 header, such as CSF data on i.MX platform.
51 bool "Do a full check of the FIT before using it"
55 Enable this do a full check of the FIT to make sure it is valid. This
56 helps to protect against carefully crafted FITs which take advantage
57 of bugs or omissions in the code. This includes a bad structure,
58 multiple root nodes and the like.
61 bool "Enable signature verification of FIT uImages"
66 select IMAGE_SIGN_INFO
69 This option enables signature verification of FIT uImages,
70 using a hash signed and verified using RSA. If
71 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
72 hashing is available using hardware, then the RSA library will use
73 it. See doc/uImage.FIT/signature.txt for more details.
75 WARNING: When relying on signed FIT images with a required signature
76 check the legacy image format is disabled by default, so that
77 unsigned images cannot be loaded. If a board needs the legacy image
78 format support in this case, enable it using
79 CONFIG_LEGACY_IMAGE_FORMAT.
81 config FIT_SIGNATURE_MAX_SIZE
82 hex "Max size of signed FIT structures"
83 depends on FIT_SIGNATURE
86 This option sets a max size in bytes for verified FIT uImages.
87 A sane value of 256MB protects corrupted DTB structures from overlapping
88 device memory. Assure this size does not extend past expected storage
92 bool "Support rsassa-pss signature scheme of FIT image contents"
93 depends on FIT_SIGNATURE
95 Enable this to support the pss padding algorithm as described
96 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
99 bool "Enable ciphering data in a FIT uImages"
103 Enable the feature of data ciphering/unciphering in the tool mkimage
104 and in the u-boot support of the FIT image.
107 bool "Show verbose messages when FIT images fail"
110 Generally a system will have valid FIT images so debug messages
111 are a waste of code space. If you are debugging your images then
112 you can enable this option to get more verbose information about
115 config FIT_BEST_MATCH
116 bool "Select the best match for the kernel device tree"
119 When no configuration is explicitly selected, default to the
120 one whose fdt's compatibility field best matches that of
121 U-Boot itself. A match is considered "best" if it matches the
122 most specific compatibility entry of U-Boot's fdt's root node.
123 The order of entries in the configuration's fdt is ignored.
125 config FIT_IMAGE_POST_PROCESS
126 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
128 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
129 default y if TI_SECURE_DEVICE
131 Allows doing any sort of manipulation to blobs after they got extracted
132 from FIT images like stripping off headers or modifying the size of the
133 blob, verification, authentication, decryption etc. in a platform or
134 board specific way. In order to use this feature a platform or board-
135 specific implementation of board_fit_image_post_process() must be
136 provided. Also, anything done during this post-processing step would
137 need to be comprehended in how the images were prepared before being
138 injected into the FIT creation (i.e. the blobs would have been pre-
139 processed before being added to the FIT image).
142 bool "Support FIT printing"
146 Support printing the content of the fitImage in a verbose manner.
149 bool "Support Flattened Image Tree within SPL"
150 depends on SPL && FIT
155 bool "Support FIT printing within SPL"
158 Support printing the content of the fitImage in a verbose manner in SPL.
160 config SPL_FIT_FULL_CHECK
161 bool "Do a full check of the FIT before using it"
164 Enable this do a full check of the FIT to make sure it is valid. This
165 helps to protect against carefully crafted FITs which take advantage
166 of bugs or omissions in the code. This includes a bad structure,
167 multiple root nodes and the like.
169 config SPL_FIT_SIGNATURE
170 bool "Enable signature verification of FIT firmware within SPL"
172 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
179 select SPL_IMAGE_SIGN_INFO
180 select SPL_FIT_FULL_CHECK
182 config SPL_FIT_SIGNATURE_MAX_SIZE
183 hex "Max size of signed FIT structures in SPL"
184 depends on SPL_FIT_SIGNATURE
187 This option sets a max size in bytes for verified FIT uImages.
188 A sane value of 256MB protects corrupted DTB structures from overlapping
189 device memory. Assure this size does not extend past expected storage
192 config SPL_FIT_RSASSA_PSS
193 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
194 depends on SPL_FIT_SIGNATURE
196 Enable this to support the pss padding algorithm as described
197 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
200 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
201 depends on SPL && FIT
204 Normally with the SPL framework a legacy image is generated as part
205 of the build. This contains U-Boot along with information as to
206 where it should be loaded. This option instead enables generation
207 of a FIT (Flat Image Tree) which provides more flexibility. In
208 particular it can handle selecting from multiple device tree
209 and passing the correct one to U-Boot.
211 This path has the following limitations:
213 1. "loadables" images, other than FDTs, which do not have a "load"
214 property will not be loaded. This limitation also applies to FPGA
215 images with the correct "compatible" string.
216 2. For FPGA images, the supported "compatible" list is in the
217 doc/uImage.FIT/source_file_format.txt.
218 3. FDTs are only loaded for images with an "os" property of "u-boot".
219 "linux" images are also supported with Falcon boot mode.
221 config SPL_LOAD_FIT_ADDRESS
222 hex "load address of fit image"
223 depends on SPL_LOAD_FIT || SPL_RAM_SUPPORT || TPL_RAM_SUPPORT
226 Specify the load address of the fit image that will be loaded
229 config SPL_LOAD_FIT_APPLY_OVERLAY
230 bool "Enable SPL applying DT overlays from FIT"
231 depends on SPL_LOAD_FIT
232 select OF_LIBFDT_OVERLAY
234 The device tree is loaded from the FIT image. Allow the SPL to
235 also load device-tree overlays from the FIT image an apply them
236 over the device tree.
238 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
239 depends on SPL_LOAD_FIT_APPLY_OVERLAY
241 hex "size of temporary buffer used to load the overlays"
243 The size of the area where the overlays will be loaded and
244 uncompress. Must be at least as large as biggest overlay
247 config SPL_LOAD_FIT_FULL
248 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
252 Normally with the SPL framework a legacy image is generated as part
253 of the build. This contains U-Boot along with information as to
254 where it should be loaded. This option instead enables generation
255 of a FIT (Flat Image Tree) which provides more flexibility. In
256 particular it can handle selecting from multiple device tree
257 and passing the correct one to U-Boot.
259 config SPL_FIT_IMAGE_POST_PROCESS
260 bool "Enable post-processing of FIT artifacts after loading by the SPL"
261 depends on SPL_LOAD_FIT
262 default y if TI_SECURE_DEVICE
264 Allows doing any sort of manipulation to blobs after they got extracted
265 from the U-Boot FIT image like stripping off headers or modifying the
266 size of the blob, verification, authentication, decryption etc. in a
267 platform or board specific way. In order to use this feature a platform
268 or board-specific implementation of board_fit_image_post_process() must
269 be provided. Also, anything done during this post-processing step would
270 need to be comprehended in how the images were prepared before being
271 injected into the FIT creation (i.e. the blobs would have been pre-
272 processed before being added to the FIT image).
274 config SPL_FIT_SOURCE
275 string ".its source file for U-Boot FIT image"
278 Specifies a (platform specific) FIT source file to generate the
279 U-Boot FIT image. This could specify further image to load and/or
282 config USE_SPL_FIT_GENERATOR
283 bool "Use a script to generate the .its script"
285 default y if SPL_FIT && ARCH_ZYNQMP
287 config SPL_FIT_GENERATOR
288 string ".its file generator script for U-Boot FIT image"
289 depends on USE_SPL_FIT_GENERATOR
290 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
292 Specifies a (platform specific) script file to generate the FIT
293 source file used to build the U-Boot FIT image file. This gets
294 passed a list of supported device tree file stub names to
295 include in the generated image.
300 bool "Support Flattened Image Tree within VPL"
307 bool "Support FIT printing within VPL"
311 Support printing the content of the fitImage in a verbose manner in VPL.
313 config VPL_FIT_FULL_CHECK
314 bool "Do a full check of the FIT before using it"
317 Enable this do a full check of the FIT to make sure it is valid. This
318 helps to protect against carefully crafted FITs which take advantage
319 of bugs or omissions in the code. This includes a bad structure,
320 multiple root nodes and the like.
322 config VPL_FIT_SIGNATURE
323 bool "Enable signature verification of FIT firmware within VPL"
332 select VPL_IMAGE_SIGN_INFO
333 select VPL_FIT_FULL_CHECK
335 config VPL_FIT_SIGNATURE_MAX_SIZE
336 hex "Max size of signed FIT structures in VPL"
337 depends on VPL_FIT_SIGNATURE
340 This option sets a max size in bytes for verified FIT uImages.
341 A sane value of 256MB protects corrupted DTB structures from overlapping
342 device memory. Assure this size does not extend past expected storage
351 Utilities for parsing PXE file formats.
354 bool # Common defaults for standard boot and distroboot
355 imply USE_BOOTCOMMAND
356 select CMD_ENV_EXISTS
360 select CMD_FS_GENERIC
361 select CMD_PART if PARTITIONS
362 select CMD_DHCP if CMD_NET
363 select CMD_PING if CMD_NET
364 select CMD_PXE if CMD_NET
365 select SUPPORT_RAW_INITRD
366 select ENV_VARS_UBOOT_CONFIG
367 select CMD_BOOTI if ARM64
368 select CMD_BOOTZ if ARM && !ARM64
374 These are not required but are commonly needed to support a good
375 selection of booting methods. Enable this to improve the capability
376 of U-Boot to boot various images. Currently much functionality is
377 tied to enabling the command that exercises it.
380 bool "Standard boot support"
382 depends on DM && OF_CONTROL && BLK
384 U-Boot supports a standard way of locating something to boot,
385 typically an Operating System such as Linux, provided by a distro such
386 as Arch Linux or Debian. Enable this to support iterating through
387 available bootdevs and using bootmeths to find bootflows suitable for
390 Standard boot is not a standard way of booting, just a framework
391 within U-Boot for supporting all the different ways that exist.
395 - bootdev - a device which can hold a distro (e.g. MMC)
396 - bootmeth - a method to scan a bootdev to find bootflows (owned by
398 - bootflow - a description of how to boot (owned by the distro)
401 bool "Enhanced features for standard boot"
404 This enables various useful features for standard boot, which are not
405 essential for operation:
407 - bootdev, bootmeth commands
408 - extra features in the bootflow command
409 - support for selecting the ordering of bootmeths ("bootmeth order")
410 - support for selecting the ordering of bootdevs using the devicetree
411 as well as the "boot_targets" environment variable
414 bool "Standard boot support in SPL"
415 depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK
418 This enables standard boot in SPL. This is neeeded so that VBE
419 (Verified Boot for Embedded) can be used, since it depends on standard
420 boot. It is enabled by default since the main purpose of VPL is to
421 handle the firmware part of VBE.
424 bool "Standard boot support in VPL"
425 depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK
428 This enables standard boot in SPL. This is neeeded so that VBE
429 (Verified Boot for Embedded) can be used, since it depends on standard
430 boot. It is enabled by default since the main purpose of VPL is to
431 handle the firmware part of VBE.
435 config BOOTSTD_DEFAULTS
436 bool "Select some common defaults for standard boot"
438 imply USE_BOOTCOMMAND
441 These are not required but are commonly needed to support a good
442 selection of booting methods. Enable this to improve the capability
443 of U-Boot to boot various images.
445 config BOOTSTD_BOOTCOMMAND
446 bool "Use bootstd to boot"
447 default y if !DISTRO_DEFAULTS
449 Enable this to select a default boot-command suitable for booting
450 with standard boot. This can be overridden by the board if needed,
451 but the default command should be enough for most boards which use
454 For now this is only selected if distro boot is NOT used, since
455 standard boot does not support all of the features of distro boot
458 config BOOTMETH_GLOBAL
461 Add support for global bootmeths. This feature is used by VBE and
462 EFI bootmgr, since they take full control over which bootdevs are
465 config BOOTMETH_DISTRO
466 bool "Bootdev support for distro boot"
470 Enables support for distro boot using bootdevs. This makes the
471 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
474 This provides a way to try out standard boot on an existing boot flow.
476 config BOOTMETH_DISTRO_PXE
477 bool "Bootdev support for distro boot over network"
478 depends on CMD_PXE && CMD_NET && DM_ETH
481 Enables support for distro boot using bootdevs. This makes the
482 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
484 This provides a way to try out standard boot on an existing boot flow.
486 config BOOTMETH_EFILOADER
487 bool "Bootdev support for EFI boot"
488 depends on CMD_BOOTEFI
491 Enables support for EFI boot using bootdevs. This makes the
492 bootdevs look for a 'boot<arch>.efi' on each filesystem
493 they scan. The resulting file is booted after enabling U-Boot's
496 The <arch> depends on the architecture of the board:
498 aa64 - aarch64 (ARM 64-bit)
502 riscv32 - RISC-V 32-bit
503 riscv64 - RISC-V 64-bit
505 This provides a way to try out standard boot on an existing boot flow.
508 bool "Bootdev support for Verified Boot for Embedded"
511 select BOOTMETH_GLOBAL
514 Enables support for VBE boot. This is a standard boot method which
515 supports selection of various firmware components, seleciton of an OS to
516 boot as well as updating these using fwupd.
518 config SPL_BOOTMETH_VBE
519 bool "Bootdev support for Verified Boot for Embedded (SPL)"
520 depends on SPL && FIT
524 Enables support for VBE boot. This is a standard boot method which
525 supports selection of various firmware components, seleciton of an OS to
526 boot as well as updating these using fwupd.
528 config VPL_BOOTMETH_VBE
529 bool "Bootdev support for Verified Boot for Embedded (VPL)"
530 depends on VPL && FIT
534 Enables support for VBE boot. This is a standard boot method which
535 supports selection of various firmware components, seleciton of an OS to
536 boot as well as updating these using fwupd.
540 config BOOTMETH_VBE_REQUEST
541 bool "Support for serving VBE OS requests"
544 Enables support for looking that the requests made by the
545 Operating System being booted. These requests result in additions to
546 the device tree /chosen node, added during the device tree fixup
549 config SPL_BOOTMETH_VBE_REQUEST
550 bool "Support for serving VBE OS requests (SPL)"
553 Enables support for looking that the requests made by the
554 Operating System being booted. These requests result in additions to
555 the device tree /chosen node, added during the device tree fixup
558 This is only useful if you are booting an OS direct from SPL.
560 config BOOTMETH_VBE_SIMPLE
561 bool "Bootdev support for VBE 'simple' method"
564 Enables support for VBE 'simple' boot. This allows updating a single
565 firmware image in boot media such as MMC. It does not support any sort
566 of rollback, recovery or A/B boot.
568 config BOOTMETH_VBE_SIMPLE_OS
569 bool "Bootdev support for VBE 'simple' method OS phase"
572 Enables support for the OS parts of VBE 'simple' boot. This includes
573 fixing up the device tree with the required VBE information, ready
574 for booting into the OS. This option is only enabled for U-Boot
575 proper, since it is the phase where device tree fixups happen.
577 config SPL_BOOTMETH_VBE_SIMPLE
578 bool "Bootdev support for VBE 'simple' method (SPL)"
582 Enables support for VBE 'simple' boot. This allows updating a single
583 firmware image in boot media such as MMC. It does not support any sort
584 of rollback, recovery or A/B boot.
586 config VPL_BOOTMETH_VBE_SIMPLE
587 bool "Bootdev support for VBE 'simple' method (VPL)"
591 Enables support for VBE 'simple' boot. This allows updating a single
592 firmware image in boot media such as MMC. It does not support any sort
593 of rollback, recovery or A/B boot.
595 config SPL_BOOTMETH_VBE_SIMPLE_FW
596 bool "Bootdev support for VBE 'simple' method firmware phase (SPL)"
600 Enables support for the firmware parts of VBE 'simple' boot. This
601 includes an SPL loader which locates the correct U-Boot to boot into.
602 This option should really only be enabled for VPL, since it is the
603 phase where the SPL + U-Boot decision should be made. But for now,
604 SPL does its own FIT-configuration selection.
606 config VPL_BOOTMETH_VBE_SIMPLE_FW
607 bool "Bootdev support for VBE 'simple' method firmware phase (VPL)"
611 Enables support for the firmware parts of VBE 'simple' boot. This
612 includes an SPL loader which locates the correct SPL to boot into.
613 This option enabled for VPL, since it is the phase where the SPL
619 bool "Support for expos - groups of scenes displaying a UI"
621 default y if BOOTMETH_VBE
623 An expo is a way of presenting and collecting information from the
624 user. It consists of a collection of 'scenes' of which only one is
625 presented at a time. An expo is typically used to show a boot menu
626 and allow settings to be changed.
628 The expo can be presented in graphics form using a vidconsole, or in
629 text form on a serial console.
631 config BOOTMETH_SANDBOX
635 This is a sandbox bootmeth driver used for testing. It always returns
636 -ENOTSUPP when attempting to boot.
638 config BOOTMETH_SCRIPT
639 bool "Bootdev support for U-Boot scripts"
640 default y if BOOTSTD_FULL
643 Enables support for booting a distro via a U-Boot script. This makes
644 the bootdevs look for a 'boot/boot.scr' file which can be used to
647 This provides a way to try out standard boot on an existing boot flow.
648 It is not enabled by default to save space.
652 config LEGACY_IMAGE_FORMAT
653 bool "Enable support for the legacy image format"
654 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
656 This option enables the legacy image format. It is enabled by
657 default for backward compatibility, unless FIT_SIGNATURE is
658 set where it is disabled so that unsigned images cannot be
659 loaded. If a board needs the legacy image format support in this
660 case, enable it here.
662 config SUPPORT_RAW_INITRD
663 bool "Enable raw initrd images"
665 Note, defining the SUPPORT_RAW_INITRD allows user to supply
666 kernel with raw initrd images. The syntax is slightly different, the
667 address of the initrd must be augmented by it's size, in the following
668 format: "<initrd address>:<initrd size>".
670 config OF_BOARD_SETUP
671 bool "Set up board-specific details in device tree before boot"
674 This causes U-Boot to call ft_board_setup() before booting into
675 the Operating System. This function can set up various
676 board-specific information in the device tree for use by the OS.
677 The device tree is then passed to the OS.
679 config OF_SYSTEM_SETUP
680 bool "Set up system-specific details in device tree before boot"
683 This causes U-Boot to call ft_system_setup() before booting into
684 the Operating System. This function can set up various
685 system-specific information in the device tree for use by the OS.
686 The device tree is then passed to the OS.
688 config OF_STDOUT_VIA_ALIAS
689 bool "Update the device-tree stdout alias from U-Boot"
692 This uses U-Boot's serial alias from the aliases node to update
693 the device tree passed to the OS. The "linux,stdout-path" property
694 in the chosen node is set to point to the correct serial node.
695 This option currently references CONFIG_CONS_INDEX, which is
696 incorrect when used with device tree as this option does not
697 exist / should not be used.
699 config HAVE_TEXT_BASE
701 depends on !NIOS2 && !XTENSA
706 depends on HAVE_TEXT_BASE
707 default 0x0 if POSITION_INDEPENDENT
708 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
709 default 0x81700000 if MACH_SUNIV
710 default 0x2a000000 if MACH_SUN9I
711 default 0x4a000000 if SUNXI_MINIMUM_DRAM_MB >= 256
712 default 0x42e00000 if SUNXI_MINIMUM_DRAM_MB >= 64
715 The address in memory that U-Boot will be running from, initially.
717 config HAVE_SYS_MONITOR_BASE
719 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
720 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
724 config SYS_MONITOR_BASE
725 depends on HAVE_SYS_MONITOR_BASE
726 hex "Physical start address of boot monitor code"
729 The physical start address of boot monitor code (which is the same as
730 CONFIG_TEXT_BASE when linking) and the same as CFG_SYS_FLASH_BASE
731 when booting from flash.
733 config SPL_SYS_MONITOR_BASE
734 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
735 hex "Physical start address of SPL monitor code"
736 default SPL_TEXT_BASE
738 config TPL_SYS_MONITOR_BASE
739 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
740 hex "Physical start address of TPL monitor code"
742 config DYNAMIC_SYS_CLK_FREQ
743 bool "Determine CPU clock frequency at run-time"
745 Implement a get_board_sys_clk function that will determine the CPU
746 clock frequency at run time, rather than define it statically.
749 depends on !DYNAMIC_SYS_CLK_FREQ
750 int "CPU clock frequency"
751 default 125000000 if ARCH_LS1012A
752 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
753 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
754 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
755 default 66660000 if ARCH_T2080
756 default 33333333 if RCAR_GEN3
757 default 24000000 if ARCH_EXYNOS
758 default 20000000 if RCAR_GEN2
761 A static value for the CPU frequency. Note that if not required
762 for a given SoC, this can be left at 0.
764 config ARCH_FIXUP_FDT_MEMORY
765 bool "Enable arch_fixup_memory_banks() call"
768 Enable FDT memory map syncup before OS boot. This feature can be
769 used for booting OS with different memory setup where the part of
770 the memory location should be used for different purpose.
773 bool "Support booting Chrome OS"
775 Chrome OS requires U-Boot to set up a table indicating the boot mode
776 (e.g. Developer mode) and a few other things. Enable this if you are
777 booting on a Chromebook to avoid getting an error about an invalid
780 config CHROMEOS_VBOOT
781 bool "Support Chrome OS verified boot"
783 This is intended to enable the full Chrome OS verified boot support
784 in U-Boot. It is not actually implemented in the U-Boot source code
785 at present, so this option is always set to 'n'. It allows
786 distinguishing between booting Chrome OS in a basic way (developer
787 mode) and a full boot.
793 bool "Freescale PBL(pre-boot loader) image format support"
794 select SYS_RAMBOOT if PPC
796 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
797 For more details refer to doc/README.pblimage
800 prompt "Freescale PBL (or predecessor) load location"
801 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
802 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
806 bool "Freescale PBL (or similar) is found on SD card"
809 bool "Freescale PBL (or similar) is found on SPI flash"
812 bool "Freescale PBL (or similar) is not used in this case"
816 config FSL_FIXED_MMC_LOCATION
817 bool "PBL MMC is at a fixed location"
818 depends on SDCARD && !RAMBOOT_PBL
820 config ESDHC_HC_BLK_ADDR
822 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
824 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
825 code length of these soc specify the memory address in block address
826 format. Block length is fixed to 512 bytes as per the SD High
827 Capacity specification.
829 config SYS_FSL_PBL_PBI
830 string "PBI(pre-boot instructions) commands for the PBL image"
831 depends on RAMBOOT_PBL
833 PBI commands can be used to configure SoC before it starts the execution.
834 Please refer doc/README.pblimage for more details.
836 config SYS_FSL_PBL_RCW
837 string "Aadditional RCW (Power on reset configuration) for the PBL image"
838 depends on RAMBOOT_PBL
840 Enables addition of RCW (Power on reset configuration) in built image.
841 Please refer doc/README.pblimage for more details.
843 config SYS_BOOT_RAMDISK_HIGH
844 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
845 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
849 Enable initrd_high functionality. If defined then the initrd_high
850 feature is enabled and the boot* ramdisk subcommand is enabled.
852 endmenu # Boot images
854 config DISTRO_DEFAULTS
855 bool "Select defaults suitable for booting general purpose Linux distributions"
858 select CMDLINE_EDITING
863 Select this to enable various options and commands which are suitable
864 for building u-boot for booting general purpose Linux distributions.
869 bool "Boot timing and reporting"
871 Enable recording of boot time while booting. To use it, insert
872 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
873 bootstage.h. Only a single entry is recorded for each ID. You can
874 give the entry a name with bootstage_mark_name(). You can also
875 record elapsed time in a particular stage using bootstage_start()
876 before starting and bootstage_accum() when finished. Bootstage will
877 add up all the accumulated time and report it.
879 Normally, IDs are defined in bootstage.h but a small number of
880 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
883 Calls to show_boot_progress() will also result in log entries but
884 these will not have names.
887 bool "Boot timing and reported in SPL"
888 depends on BOOTSTAGE && SPL
890 Enable recording of boot time in SPL. To make this visible to U-Boot
891 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
892 information when SPL finishes and load it when U-Boot proper starts
896 bool "Boot timing and reported in TPL"
897 depends on BOOTSTAGE && TPL
899 Enable recording of boot time in SPL. To make this visible to U-Boot
900 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
901 information when TPL finishes and load it when U-Boot proper starts
904 config BOOTSTAGE_REPORT
905 bool "Display a detailed boot timing report before booting the OS"
908 Enable output of a boot time report just before the OS is booted.
909 This shows how long it took U-Boot to go through each stage of the
910 boot process. The report looks something like this:
912 Timer summary in microseconds:
915 3,575,678 3,575,678 board_init_f start
916 3,575,695 17 arch_cpu_init A9
917 3,575,777 82 arch_cpu_init done
918 3,659,598 83,821 board_init_r start
919 3,910,375 250,777 main_loop
920 29,916,167 26,005,792 bootm_start
921 30,361,327 445,160 start_kernel
923 config BOOTSTAGE_RECORD_COUNT
924 int "Number of boot stage records to store"
928 This is the size of the bootstage record list and is the maximum
929 number of bootstage records that can be recorded.
931 config SPL_BOOTSTAGE_RECORD_COUNT
932 int "Number of boot stage records to store for SPL"
933 depends on SPL_BOOTSTAGE
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 TPL_BOOTSTAGE_RECORD_COUNT
940 int "Number of boot stage records to store for TPL"
941 depends on TPL_BOOTSTAGE
944 This is the size of the bootstage record list and is the maximum
945 number of bootstage records that can be recorded.
948 bool "Store boot timing information in the OS device tree"
951 Stash the bootstage information in the FDT. A root 'bootstage'
952 node is created with each bootstage id as a child. Each child
953 has a 'name' property and either 'mark' containing the
954 mark time in microseconds, or 'accum' containing the
955 accumulated time for that bootstage id in microseconds.
960 name = "board_init_f";
969 Code in the Linux kernel can find this in /proc/devicetree.
971 config BOOTSTAGE_STASH
972 bool "Stash the boot timing information in memory before booting OS"
975 Some OSes do not support device tree. Bootstage can instead write
976 the boot timing information in a binary format at a given address.
977 This happens through a call to bootstage_stash(), typically in
978 the CPU's cleanup_before_linux() function. You can use the
979 'bootstage stash' and 'bootstage unstash' commands to do this on
982 config BOOTSTAGE_STASH_ADDR
983 hex "Address to stash boot timing information"
986 Provide an address which will not be overwritten by the OS when it
987 starts, so that it can read this information when ready.
989 config BOOTSTAGE_STASH_SIZE
990 hex "Size of boot timing stash region"
993 This should be large enough to hold the bootstage stash. A value of
994 4096 (4KiB) is normally plenty.
996 config SHOW_BOOT_PROGRESS
997 bool "Show boot progress in a board-specific manner"
999 Defining this option allows to add some board-specific code (calling
1000 a user-provided function show_boot_progress(int) that enables you to
1001 show the system's boot progress on some display (for example, some
1002 LEDs) on your board. At the moment, the following checkpoints are
1005 Legacy uImage format:
1008 1 common/cmd_bootm.c before attempting to boot an image
1009 -1 common/cmd_bootm.c Image header has bad magic number
1010 2 common/cmd_bootm.c Image header has correct magic number
1011 -2 common/cmd_bootm.c Image header has bad checksum
1012 3 common/cmd_bootm.c Image header has correct checksum
1013 -3 common/cmd_bootm.c Image data has bad checksum
1014 4 common/cmd_bootm.c Image data has correct checksum
1015 -4 common/cmd_bootm.c Image is for unsupported architecture
1016 5 common/cmd_bootm.c Architecture check OK
1017 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
1018 6 common/cmd_bootm.c Image Type check OK
1019 -6 common/cmd_bootm.c gunzip uncompression error
1020 -7 common/cmd_bootm.c Unimplemented compression type
1021 7 common/cmd_bootm.c Uncompression OK
1022 8 common/cmd_bootm.c No uncompress/copy overwrite error
1023 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
1025 9 common/image.c Start initial ramdisk verification
1026 -10 common/image.c Ramdisk header has bad magic number
1027 -11 common/image.c Ramdisk header has bad checksum
1028 10 common/image.c Ramdisk header is OK
1029 -12 common/image.c Ramdisk data has bad checksum
1030 11 common/image.c Ramdisk data has correct checksum
1031 12 common/image.c Ramdisk verification complete, start loading
1032 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
1033 13 common/image.c Start multifile image verification
1034 14 common/image.c No initial ramdisk, no multifile, continue.
1036 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
1038 -30 arch/powerpc/lib/board.c Fatal error, hang the system
1039 -31 post/post.c POST test failed, detected by post_output_backlog()
1040 -32 post/post.c POST test failed, detected by post_run_single()
1042 34 common/cmd_doc.c before loading a Image from a DOC device
1043 -35 common/cmd_doc.c Bad usage of "doc" command
1044 35 common/cmd_doc.c correct usage of "doc" command
1045 -36 common/cmd_doc.c No boot device
1046 36 common/cmd_doc.c correct boot device
1047 -37 common/cmd_doc.c Unknown Chip ID on boot device
1048 37 common/cmd_doc.c correct chip ID found, device available
1049 -38 common/cmd_doc.c Read Error on boot device
1050 38 common/cmd_doc.c reading Image header from DOC device OK
1051 -39 common/cmd_doc.c Image header has bad magic number
1052 39 common/cmd_doc.c Image header has correct magic number
1053 -40 common/cmd_doc.c Error reading Image from DOC device
1054 40 common/cmd_doc.c Image header has correct magic number
1055 41 common/cmd_ide.c before loading a Image from a IDE device
1056 -42 common/cmd_ide.c Bad usage of "ide" command
1057 42 common/cmd_ide.c correct usage of "ide" command
1058 -43 common/cmd_ide.c No boot device
1059 43 common/cmd_ide.c boot device found
1060 -44 common/cmd_ide.c Device not available
1061 44 common/cmd_ide.c Device available
1062 -45 common/cmd_ide.c wrong partition selected
1063 45 common/cmd_ide.c partition selected
1064 -46 common/cmd_ide.c Unknown partition table
1065 46 common/cmd_ide.c valid partition table found
1066 -47 common/cmd_ide.c Invalid partition type
1067 47 common/cmd_ide.c correct partition type
1068 -48 common/cmd_ide.c Error reading Image Header on boot device
1069 48 common/cmd_ide.c reading Image Header from IDE device OK
1070 -49 common/cmd_ide.c Image header has bad magic number
1071 49 common/cmd_ide.c Image header has correct magic number
1072 -50 common/cmd_ide.c Image header has bad checksum
1073 50 common/cmd_ide.c Image header has correct checksum
1074 -51 common/cmd_ide.c Error reading Image from IDE device
1075 51 common/cmd_ide.c reading Image from IDE device OK
1076 52 common/cmd_nand.c before loading a Image from a NAND device
1077 -53 common/cmd_nand.c Bad usage of "nand" command
1078 53 common/cmd_nand.c correct usage of "nand" command
1079 -54 common/cmd_nand.c No boot device
1080 54 common/cmd_nand.c boot device found
1081 -55 common/cmd_nand.c Unknown Chip ID on boot device
1082 55 common/cmd_nand.c correct chip ID found, device available
1083 -56 common/cmd_nand.c Error reading Image Header on boot device
1084 56 common/cmd_nand.c reading Image Header from NAND device OK
1085 -57 common/cmd_nand.c Image header has bad magic number
1086 57 common/cmd_nand.c Image header has correct magic number
1087 -58 common/cmd_nand.c Error reading Image from NAND device
1088 58 common/cmd_nand.c reading Image from NAND device OK
1090 -60 common/env_common.c Environment has a bad CRC, using default
1092 64 net/eth.c starting with Ethernet configuration.
1093 -64 net/eth.c no Ethernet found.
1094 65 net/eth.c Ethernet found.
1096 -80 common/cmd_net.c usage wrong
1097 80 common/cmd_net.c before calling net_loop()
1098 -81 common/cmd_net.c some error in net_loop() occurred
1099 81 common/cmd_net.c net_loop() back without error
1100 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1101 82 common/cmd_net.c trying automatic boot
1102 83 common/cmd_net.c running "source" command
1103 -83 common/cmd_net.c some error in automatic boot or "source" command
1104 84 common/cmd_net.c end without errors
1109 100 common/cmd_bootm.c Kernel FIT Image has correct format
1110 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1111 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1112 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1113 102 common/cmd_bootm.c Kernel unit name specified
1114 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1115 103 common/cmd_bootm.c Found configuration node
1116 104 common/cmd_bootm.c Got kernel subimage node offset
1117 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1118 105 common/cmd_bootm.c Kernel subimage hash verification OK
1119 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1120 106 common/cmd_bootm.c Architecture check OK
1121 -106 common/cmd_bootm.c Kernel subimage has wrong type
1122 107 common/cmd_bootm.c Kernel subimage type OK
1123 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1124 108 common/cmd_bootm.c Got kernel subimage data/size
1125 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1126 -109 common/cmd_bootm.c Can't get kernel subimage type
1127 -110 common/cmd_bootm.c Can't get kernel subimage comp
1128 -111 common/cmd_bootm.c Can't get kernel subimage os
1129 -112 common/cmd_bootm.c Can't get kernel subimage load address
1130 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1132 120 common/image.c Start initial ramdisk verification
1133 -120 common/image.c Ramdisk FIT image has incorrect format
1134 121 common/image.c Ramdisk FIT image has correct format
1135 122 common/image.c No ramdisk subimage unit name, using configuration
1136 -122 common/image.c Can't get configuration for ramdisk subimage
1137 123 common/image.c Ramdisk unit name specified
1138 -124 common/image.c Can't get ramdisk subimage node offset
1139 125 common/image.c Got ramdisk subimage node offset
1140 -125 common/image.c Ramdisk subimage hash verification failed
1141 126 common/image.c Ramdisk subimage hash verification OK
1142 -126 common/image.c Ramdisk subimage for unsupported architecture
1143 127 common/image.c Architecture check OK
1144 -127 common/image.c Can't get ramdisk subimage data/size
1145 128 common/image.c Got ramdisk subimage data/size
1146 129 common/image.c Can't get ramdisk load address
1147 -129 common/image.c Got ramdisk load address
1149 -130 common/cmd_doc.c Incorrect FIT image format
1150 131 common/cmd_doc.c FIT image format OK
1152 -140 common/cmd_ide.c Incorrect FIT image format
1153 141 common/cmd_ide.c FIT image format OK
1155 -150 common/cmd_nand.c Incorrect FIT image format
1156 151 common/cmd_nand.c FIT image format OK
1158 config SPL_SHOW_BOOT_PROGRESS
1159 bool "Show boot progress in a board-specific manner in SPL"
1162 Defining this option allows to add some board-specific code (calling
1163 a user-provided function show_boot_progress(int) that enables you to
1164 show the system's boot progress on some display (for example, some
1165 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1172 bool "Support for booting from NOR flash"
1175 Enabling this will make a U-Boot binary that is capable of being
1176 booted via NOR. In this case we will enable certain pinmux early
1177 as the ROM only partially sets up pinmux. We also default to using
1178 NOR for environment.
1181 bool "Support for booting from NAND flash"
1184 Enabling this will make a U-Boot binary that is capable of being
1185 booted via NAND flash. This is not a must, some SoCs need this,
1189 bool "Support for booting from ONENAND"
1192 Enabling this will make a U-Boot binary that is capable of being
1193 booted via ONENAND. This is not a must, some SoCs need this,
1197 bool "Support for booting from QSPI flash"
1199 Enabling this will make a U-Boot binary that is capable of being
1200 booted via QSPI flash. This is not a must, some SoCs need this,
1204 bool "Support for booting from SATA"
1206 Enabling this will make a U-Boot binary that is capable of being
1207 booted via SATA. This is not a must, some SoCs need this,
1211 bool "Support for booting from SD/EMMC"
1213 Enabling this will make a U-Boot binary that is capable of being
1214 booted via SD/EMMC. This is not a must, some SoCs need this,
1218 bool "Support for booting from SD/EMMC and enable QSPI"
1220 Enabling this will make a U-Boot binary that is capable of being
1221 booted via SD/EMMC while enabling QSPI on the platform as well. This
1222 is not a must, some SoCs need this, some not.
1225 bool "Support for booting from SPI flash"
1227 Enabling this will make a U-Boot binary that is capable of being
1228 booted via SPI flash. This is not a must, some SoCs need this,
1233 menu "Autoboot options"
1239 This enables the autoboot. See doc/README.autoboot for detail.
1242 int "delay in seconds before automatically booting"
1246 Delay before automatically running bootcmd;
1247 set to 0 to autoboot with no delay, but you can stop it by key input.
1248 set to -1 to disable autoboot.
1249 set to -2 to autoboot with no delay and not check for abort
1251 If this value is >= 0 then it is also used for the default delay
1252 before starting the default entry in bootmenu. If it is < 0 then
1253 a default value of 10s is used.
1255 See doc/README.autoboot for details.
1257 config AUTOBOOT_KEYED
1258 bool "Stop autobooting via specific input key / string"
1260 This option enables stopping (aborting) of the automatic
1261 boot feature only by issuing a specific input key or
1262 string. If not enabled, any input key will abort the
1263 U-Boot automatic booting process and bring the device
1264 to the U-Boot prompt for user input.
1266 config AUTOBOOT_FLUSH_STDIN
1267 bool "Enable flushing stdin before starting to read the password"
1268 depends on AUTOBOOT_KEYED && !SANDBOX
1270 When this option is enabled stdin buffer will be flushed before
1271 starting to read the password.
1272 This can't be enabled for the sandbox as flushing stdin would
1273 break the autoboot unit tests.
1275 config AUTOBOOT_PROMPT
1276 string "Autoboot stop prompt"
1277 depends on AUTOBOOT_KEYED
1278 default "Autoboot in %d seconds\\n"
1280 This string is displayed before the boot delay selected by
1281 CONFIG_BOOTDELAY starts. If it is not defined there is no
1282 output indicating that autoboot is in progress.
1284 Note that this define is used as the (only) argument to a
1285 printf() call, so it may contain '%' format specifications,
1286 provided that it also includes, sepearated by commas exactly
1287 like in a printf statement, the required arguments. It is
1288 the responsibility of the user to select only such arguments
1289 that are valid in the given context.
1291 config AUTOBOOT_ENCRYPTION
1292 bool "Enable encryption in autoboot stopping"
1293 depends on AUTOBOOT_KEYED
1295 This option allows a string to be entered into U-Boot to stop the
1297 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1299 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1300 to the crypt-based functionality and be compared against the
1301 string in the environment variable 'bootstopkeycrypt'.
1302 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1303 and compared against the hash in the environment variable
1304 'bootstopkeysha256'.
1305 If it matches in either case then boot stops and
1306 a command-line prompt is presented.
1307 This provides a way to ship a secure production device which can also
1308 be accessed at the U-Boot command line.
1310 config AUTOBOOT_SHA256_FALLBACK
1311 bool "Allow fallback from crypt-hashed password to sha256"
1312 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1314 This option adds support to fall back from crypt-hashed
1315 passwords to checking a SHA256 hashed password in case the
1316 'bootstopusesha256' environment variable is set to 'true'.
1318 config AUTOBOOT_DELAY_STR
1319 string "Delay autobooting via specific input key / string"
1320 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1322 This option delays the automatic boot feature by issuing
1323 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1324 or the environment variable "bootdelaykey" is specified
1325 and this string is received from console input before
1326 autoboot starts booting, U-Boot gives a command prompt. The
1327 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1328 used, otherwise it never times out.
1330 config AUTOBOOT_STOP_STR
1331 string "Stop autobooting via specific input key / string"
1332 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1334 This option enables stopping (aborting) of the automatic
1335 boot feature only by issuing a specific input key or
1336 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1337 variable "bootstopkey" is specified and this string is
1338 received from console input before autoboot starts booting,
1339 U-Boot gives a command prompt. The U-Boot prompt never
1340 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1342 config AUTOBOOT_KEYED_CTRLC
1343 bool "Enable Ctrl-C autoboot interruption"
1344 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1346 This option allows for the boot sequence to be interrupted
1347 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1348 Setting this variable provides an escape sequence from the
1349 limited "password" strings.
1351 config AUTOBOOT_NEVER_TIMEOUT
1352 bool "Make the password entry never time-out"
1353 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1355 This option removes the timeout from the password entry
1356 when the user first presses the <Enter> key before entering
1357 any other character.
1359 config AUTOBOOT_STOP_STR_ENABLE
1360 bool "Enable fixed string to stop autobooting"
1361 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1363 This option enables the feature to add a fixed stop
1364 string that is defined at compile time.
1365 In every case it will be tried to load the stop
1366 string from the environment.
1367 In case this is enabled and there is no stop string
1368 in the environment, this will be used as default value.
1370 config AUTOBOOT_STOP_STR_CRYPT
1371 string "Stop autobooting via crypt-hashed password"
1372 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1374 This option adds the feature to only stop the autobooting,
1375 and therefore boot into the U-Boot prompt, when the input
1376 string / password matches a values that is hashed via
1377 one of the supported crypt-style password hashing options
1378 and saved in the environment variable "bootstopkeycrypt".
1380 config AUTOBOOT_STOP_STR_SHA256
1381 string "Stop autobooting via SHA256 hashed password"
1382 depends on AUTOBOOT_STOP_STR_ENABLE
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 encypted via
1387 a SHA256 hash and saved in the environment variable
1388 "bootstopkeysha256". If the value in that variable
1389 includes a ":", the portion prior to the ":" will be treated
1392 config AUTOBOOT_USE_MENUKEY
1393 bool "Allow a specify key to run a menu from the environment"
1394 depends on !AUTOBOOT_KEYED
1396 If a specific key is pressed to stop autoboot, then the commands in
1397 the environment variable 'menucmd' are executed before boot starts.
1399 config AUTOBOOT_MENUKEY
1400 int "ASCII value of boot key to show a menu"
1402 depends on AUTOBOOT_USE_MENUKEY
1404 If this key is pressed to stop autoboot, then the commands in the
1405 environment variable 'menucmd' will be executed before boot starts.
1406 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1409 config AUTOBOOT_MENU_SHOW
1410 bool "Show a menu on boot"
1411 depends on CMD_BOOTMENU
1413 This enables the boot menu, controlled by environment variables
1414 defined by the board. The menu starts after running the 'preboot'
1415 environmnent variable (if enabled) and before handling the boot delay.
1416 See README.bootmenu for more details.
1418 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1419 bool "Disallow bootmenu to enter the U-Boot console"
1420 depends on AUTOBOOT_MENU_SHOW
1422 If this option is enabled, user can not enter the U-Boot console from
1423 bootmenu. It increases the system security.
1426 bool "Boot retry feature"
1428 Allow for having the U-Boot command prompt time out and attempt
1429 to boot again. If the environment variable "bootretry" is found then
1430 its value is used, otherwise the retry timeout is
1431 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1432 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1434 config BOOT_RETRY_TIME
1435 int "Timeout in seconds before attempting to boot again"
1436 depends on BOOT_RETRY
1438 Time in seconds before the U-Boot prompt will timeout and boot will
1441 config BOOT_RETRY_MIN
1442 int "Minimum timeout in seconds for 'bootretry'"
1443 depends on BOOT_RETRY
1444 default BOOT_RETRY_TIME
1446 The minimum time in seconds that "bootretry" can be set to.
1448 config RESET_TO_RETRY
1449 bool "Reset the board to retry autoboot"
1450 depends on BOOT_RETRY
1452 After the countdown timed out, the board will be reset to restart
1457 menu "Image support"
1459 config IMAGE_PRE_LOAD
1460 bool "Image pre-load support"
1462 Enable an image pre-load stage in the SPL.
1463 This pre-load stage allows to do some manipulation
1464 or check (for example signature check) on an image
1465 before launching it.
1467 config SPL_IMAGE_PRE_LOAD
1468 bool "Image pre-load support within SPL"
1469 depends on SPL && IMAGE_PRE_LOAD
1471 Enable an image pre-load stage in the SPL.
1472 This pre-load stage allows to do some manipulation
1473 or check (for example signature check) on an image
1474 before launching it.
1476 config IMAGE_PRE_LOAD_SIG
1477 bool "Image pre-load signature support"
1478 depends on IMAGE_PRE_LOAD
1479 select FIT_SIGNATURE
1481 select RSA_VERIFY_WITH_PKEY
1483 Enable signature check support in the pre-load stage.
1484 For this feature a very simple header is added before
1485 the image with few fields:
1489 All other information (header size, type of signature,
1490 ...) are provided in the node /image/pre-load/sig of
1493 config SPL_IMAGE_PRE_LOAD_SIG
1494 bool "Image pre-load signature support witin SPL"
1495 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1496 select SPL_FIT_SIGNATURE
1498 select SPL_RSA_VERIFY_WITH_PKEY
1500 Enable signature check support in the pre-load stage in the SPL.
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
1513 bool "Enable boot arguments"
1515 Provide boot arguments to bootm command. Boot arguments are specified
1516 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1517 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1518 will be undefined and won't take any space in U-Boot image.
1521 string "Boot arguments"
1522 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1524 This can be used to pass arguments to the bootm command. The value of
1525 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1526 this value will also override the "chosen" node in FDT blob.
1528 config BOOTARGS_SUBST
1529 bool "Support substituting strings in boot arguments"
1531 This allows substituting string values in the boot arguments. These
1532 are applied after the commandline has been built.
1534 One use for this is to insert the root-disk UUID into the command
1535 line where bootargs contains "root=${uuid}"
1537 setenv bootargs "console= root=${uuid}"
1538 # Set the 'uuid' environment variable
1539 part uuid mmc 2:2 uuid
1541 # Command-line substitution will put the real uuid into the
1542 # kernel command line
1545 config USE_BOOTCOMMAND
1546 bool "Enable a default value for bootcmd"
1548 Provide a default value for the bootcmd entry in the environment. If
1549 autoboot is enabled this is what will be run automatically. Enable
1550 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1551 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1552 won't take any space in U-Boot image.
1555 string "bootcmd value"
1556 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1557 default "bootflow scan -lb" if BOOTSTD_DEFAULTS && CMD_BOOTFLOW_FULL
1558 default "bootflow scan" if BOOTSTD_DEFAULTS && !CMD_BOOTFLOW_FULL
1559 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1561 This is the string of commands that will be used as bootcmd and if
1562 AUTOBOOT is set, automatically run.
1565 bool "Enable preboot"
1567 When this option is enabled, the existence of the environment
1568 variable "preboot" will be checked immediately before starting the
1569 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1570 entering interactive mode.
1572 This feature is especially useful when "preboot" is automatically
1573 generated or modified. For example, the boot code can modify the
1574 "preboot" when a user holds down a certain combination of keys.
1577 string "preboot default value"
1578 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1579 default "usb start" if USB_KEYBOARD
1582 This is the default of "preboot" environment variable.
1584 config PREBOOT_DEFINED
1586 default y if PREBOOT != ""
1588 config DEFAULT_FDT_FILE
1589 string "Default fdt file"
1591 This option is used to set the default fdt file to boot OS.
1593 config SAVE_PREV_BL_FDT_ADDR
1595 bool "Saves fdt address, passed by the previous bootloader, to env var"
1597 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1598 enable this option to save fdt address, passed by the
1599 previous bootloader for future use.
1600 Address is saved to `prevbl_fdt_addr` environment variable.
1602 If no fdt was provided by previous bootloader, no env variables
1605 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1607 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1609 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1610 enable this option to save initramfs address, passed by the
1611 previous bootloader for future use.
1612 Address is saved to `prevbl_initrd_start_addr` environment variable.
1614 If no initramfs was provided by previous bootloader, no env variables