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 is 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 "Standard boot support"
356 depends on DM && OF_CONTROL && BLK
358 U-Boot supports a standard way of locating something to boot,
359 typically an Operating System such as Linux, provided by a distro such
360 as Arch Linux or Debian. Enable this to support iterating through
361 available bootdevs and using bootmeths to find bootflows suitable for
364 Standard boot is not a standard way of booting, just a framework
365 within U-Boot for supporting all the different ways that exist.
369 - bootdev - a device which can hold a distro (e.g. MMC)
370 - bootmeth - a method to scan a bootdev to find bootflows (owned by
372 - bootflow - a description of how to boot (owned by the distro)
375 bool "Enhanced features for standard boot"
378 This enables various useful features for standard boot, which are not
379 essential for operation:
381 - bootdev, bootmeth commands
382 - extra features in the bootflow command
383 - support for selecting the ordering of bootmeths ("bootmeth order")
384 - support for selecting the ordering of bootdevs using the devicetree
385 as well as the "boot_targets" environment variable
388 bool "Standard boot support in SPL"
389 depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK
392 This enables standard boot in SPL. This is neeeded so that VBE
393 (Verified Boot for Embedded) can be used, since it depends on standard
394 boot. It is enabled by default since the main purpose of VPL is to
395 handle the firmware part of VBE.
398 bool "Standard boot support in VPL"
399 depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK
402 This enables standard boot in SPL. This is neeeded so that VBE
403 (Verified Boot for Embedded) can be used, since it depends on standard
404 boot. It is enabled by default since the main purpose of VPL is to
405 handle the firmware part of VBE.
409 config BOOTSTD_DEFAULTS
410 bool "Select some common defaults for standard boot"
412 imply USE_BOOTCOMMAND
413 # Bring in some defaults which are generally needed. Boards can drop
414 # these as needed to save code space. Bootstd does not generally require
415 # the commands themselves to be enabled, but this is how some of the
416 # functionality is controlled at present
422 imply CMD_DHCP if NET
424 imply CMD_PING if NET
427 imply SUPPORT_RAW_INITRD
428 imply ENV_VARS_UBOOT_CONFIG
432 These are not required but are commonly needed to support a good
433 selection of booting methods. Enable this to improve the capability
434 of U-Boot to boot various images.
436 config BOOTSTD_BOOTCOMMAND
437 bool "Use bootstd to boot"
438 default y if !DISTRO_DEFAULTS
440 Enable this to select a default boot-command suitable for booting
441 with standard boot. This can be overridden by the board if needed,
442 but the default command should be enough for most boards which use
445 For now this is only selected if distro boot is NOT used, since
446 standard boot does not support all of the features of distro boot
449 config BOOTMETH_GLOBAL
452 Add support for global bootmeths. This feature is used by VBE and
453 EFI bootmgr, since they take full control over which bootdevs are
456 config BOOTMETH_DISTRO
457 bool "Bootdev support for distro boot"
461 Enables support for distro boot using bootdevs. This makes the
462 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
465 This provides a way to try out standard boot on an existing boot flow.
467 config BOOTMETH_DISTRO_PXE
468 bool "Bootdev support for distro boot over network"
469 depends on CMD_PXE && CMD_NET && DM_ETH
472 Enables support for distro boot using bootdevs. This makes the
473 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
475 This provides a way to try out standard boot on an existing boot flow.
477 config BOOTMETH_EFILOADER
478 bool "Bootdev support for EFI boot"
479 depends on CMD_BOOTEFI
482 Enables support for EFI boot using bootdevs. This makes the
483 bootdevs look for a 'boot<arch>.efi' on each filesystem
484 they scan. The resulting file is booted after enabling U-Boot's
487 The <arch> depends on the architecture of the board:
489 aa64 - aarch64 (ARM 64-bit)
493 riscv32 - RISC-V 32-bit
494 riscv64 - RISC-V 64-bit
496 This provides a way to try out standard boot on an existing boot flow.
499 bool "Bootdev support for Verified Boot for Embedded"
502 select BOOTMETH_GLOBAL
505 Enables support for VBE boot. This is a standard boot method which
506 supports selection of various firmware components, seleciton of an OS to
507 boot as well as updating these using fwupd.
509 config SPL_BOOTMETH_VBE
510 bool "Bootdev support for Verified Boot for Embedded (SPL)"
511 depends on SPL && FIT
515 Enables support for VBE boot. This is a standard boot method which
516 supports selection of various firmware components, seleciton of an OS to
517 boot as well as updating these using fwupd.
519 config VPL_BOOTMETH_VBE
520 bool "Bootdev support for Verified Boot for Embedded (VPL)"
521 depends on VPL && FIT
525 Enables support for VBE boot. This is a standard boot method which
526 supports selection of various firmware components, seleciton of an OS to
527 boot as well as updating these using fwupd.
531 config BOOTMETH_VBE_REQUEST
532 bool "Support for serving VBE OS requests"
535 Enables support for looking that the requests made by the
536 Operating System being booted. These requests result in additions to
537 the device tree /chosen node, added during the device tree fixup
540 config SPL_BOOTMETH_VBE_REQUEST
541 bool "Support for serving VBE OS requests (SPL)"
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 This is only useful if you are booting an OS direct from SPL.
551 config BOOTMETH_VBE_SIMPLE
552 bool "Bootdev support for VBE 'simple' method"
555 Enables support for VBE 'simple' boot. This allows updating a single
556 firmware image in boot media such as MMC. It does not support any sort
557 of rollback, recovery or A/B boot.
559 config BOOTMETH_VBE_SIMPLE_OS
560 bool "Bootdev support for VBE 'simple' method OS phase"
563 Enables support for the OS parts of VBE 'simple' boot. This includes
564 fixing up the device tree with the required VBE information, ready
565 for booting into the OS. This option is only enabled for U-Boot
566 proper, since it is the phase where device tree fixups happen.
568 config SPL_BOOTMETH_VBE_SIMPLE
569 bool "Bootdev support for VBE 'simple' method (SPL)"
573 Enables support for VBE 'simple' boot. This allows updating a single
574 firmware image in boot media such as MMC. It does not support any sort
575 of rollback, recovery or A/B boot.
577 config VPL_BOOTMETH_VBE_SIMPLE
578 bool "Bootdev support for VBE 'simple' method (VPL)"
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 SPL_BOOTMETH_VBE_SIMPLE_FW
587 bool "Bootdev support for VBE 'simple' method firmware phase (SPL)"
591 Enables support for the firmware parts of VBE 'simple' boot. This
592 includes an SPL loader which locates the correct U-Boot to boot into.
593 This option should really only be enabled for VPL, since it is the
594 phase where the SPL + U-Boot decision should be made. But for now,
595 SPL does its own FIT-configuration selection.
597 config VPL_BOOTMETH_VBE_SIMPLE_FW
598 bool "Bootdev support for VBE 'simple' method firmware phase (VPL)"
602 Enables support for the firmware parts of VBE 'simple' boot. This
603 includes an SPL loader which locates the correct SPL to boot into.
604 This option enabled for VPL, since it is the phase where the SPL
610 bool "Support for expos - groups of scenes displaying a UI"
612 default y if BOOTMETH_VBE
614 An expo is a way of presenting and collecting information from the
615 user. It consists of a collection of 'scenes' of which only one is
616 presented at a time. An expo is typically used to show a boot menu
617 and allow settings to be changed.
619 The expo can be presented in graphics form using a vidconsole, or in
620 text form on a serial console.
622 config BOOTMETH_SANDBOX
626 This is a sandbox bootmeth driver used for testing. It always returns
627 -ENOTSUPP when attempting to boot.
629 config BOOTMETH_SCRIPT
630 bool "Bootdev support for U-Boot scripts"
631 default y if BOOTSTD_FULL
633 Enables support for booting a distro via a U-Boot script. This makes
634 the bootdevs look for a 'boot/boot.scr' file which can be used to
637 This provides a way to try out standard boot on an existing boot flow.
638 It is not enabled by default to save space.
642 config LEGACY_IMAGE_FORMAT
643 bool "Enable support for the legacy image format"
644 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
646 This option enables the legacy image format. It is enabled by
647 default for backward compatibility, unless FIT_SIGNATURE is
648 set where it is disabled so that unsigned images cannot be
649 loaded. If a board needs the legacy image format support in this
650 case, enable it here.
652 config SUPPORT_RAW_INITRD
653 bool "Enable raw initrd images"
655 Note, defining the SUPPORT_RAW_INITRD allows user to supply
656 kernel with raw initrd images. The syntax is slightly different, the
657 address of the initrd must be augmented by it's size, in the following
658 format: "<initrd address>:<initrd size>".
660 config OF_BOARD_SETUP
661 bool "Set up board-specific details in device tree before boot"
664 This causes U-Boot to call ft_board_setup() before booting into
665 the Operating System. This function can set up various
666 board-specific information in the device tree for use by the OS.
667 The device tree is then passed to the OS.
669 config OF_SYSTEM_SETUP
670 bool "Set up system-specific details in device tree before boot"
673 This causes U-Boot to call ft_system_setup() before booting into
674 the Operating System. This function can set up various
675 system-specific information in the device tree for use by the OS.
676 The device tree is then passed to the OS.
678 config OF_STDOUT_VIA_ALIAS
679 bool "Update the device-tree stdout alias from U-Boot"
682 This uses U-Boot's serial alias from the aliases node to update
683 the device tree passed to the OS. The "linux,stdout-path" property
684 in the chosen node is set to point to the correct serial node.
685 This option currently references CONFIG_CONS_INDEX, which is
686 incorrect when used with device tree as this option does not
687 exist / should not be used.
689 config HAVE_TEXT_BASE
691 depends on !NIOS2 && !XTENSA
696 depends on HAVE_TEXT_BASE
697 default 0x0 if POSITION_INDEPENDENT
698 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
699 default 0x81700000 if MACH_SUNIV
700 default 0x2a000000 if MACH_SUN9I
701 default 0x4a000000 if SUNXI_MINIMUM_DRAM_MB >= 256
702 default 0x42e00000 if SUNXI_MINIMUM_DRAM_MB >= 64
705 The address in memory that U-Boot will be running from, initially.
707 config HAVE_SYS_MONITOR_BASE
709 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
710 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
714 config SYS_MONITOR_BASE
715 depends on HAVE_SYS_MONITOR_BASE
716 hex "Physical start address of boot monitor code"
719 The physical start address of boot monitor code (which is the same as
720 CONFIG_TEXT_BASE when linking) and the same as CFG_SYS_FLASH_BASE
721 when booting from flash.
723 config SPL_SYS_MONITOR_BASE
724 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
725 hex "Physical start address of SPL monitor code"
726 default SPL_TEXT_BASE
728 config TPL_SYS_MONITOR_BASE
729 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
730 hex "Physical start address of TPL monitor code"
732 config DYNAMIC_SYS_CLK_FREQ
733 bool "Determine CPU clock frequency at run-time"
735 Implement a get_board_sys_clk function that will determine the CPU
736 clock frequency at run time, rather than define it statically.
739 depends on !DYNAMIC_SYS_CLK_FREQ
740 int "CPU clock frequency"
741 default 125000000 if ARCH_LS1012A
742 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
743 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
744 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
745 default 66660000 if ARCH_T2080
746 default 33333333 if RCAR_GEN3
747 default 24000000 if ARCH_EXYNOS
748 default 20000000 if RCAR_GEN2
751 A static value for the CPU frequency. Note that if not required
752 for a given SoC, this can be left at 0.
754 config ARCH_FIXUP_FDT_MEMORY
755 bool "Enable arch_fixup_memory_banks() call"
758 Enable FDT memory map syncup before OS boot. This feature can be
759 used for booting OS with different memory setup where the part of
760 the memory location should be used for different purpose.
763 bool "Support booting Chrome OS"
765 Chrome OS requires U-Boot to set up a table indicating the boot mode
766 (e.g. Developer mode) and a few other things. Enable this if you are
767 booting on a Chromebook to avoid getting an error about an invalid
770 config CHROMEOS_VBOOT
771 bool "Support Chrome OS verified boot"
773 This is intended to enable the full Chrome OS verified boot support
774 in U-Boot. It is not actually implemented in the U-Boot source code
775 at present, so this option is always set to 'n'. It allows
776 distinguishing between booting Chrome OS in a basic way (developer
777 mode) and a full boot.
783 bool "Freescale PBL(pre-boot loader) image format support"
784 select SYS_RAMBOOT if PPC
786 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
787 For more details refer to doc/README.pblimage
790 prompt "Freescale PBL (or predecessor) load location"
791 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
792 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
796 bool "Freescale PBL (or similar) is found on SD card"
799 bool "Freescale PBL (or similar) is found on SPI flash"
802 bool "Freescale PBL (or similar) is not used in this case"
806 config FSL_FIXED_MMC_LOCATION
807 bool "PBL MMC is at a fixed location"
808 depends on SDCARD && !RAMBOOT_PBL
810 config ESDHC_HC_BLK_ADDR
812 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
814 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
815 code length of these soc specify the memory address in block address
816 format. Block length is fixed to 512 bytes as per the SD High
817 Capacity specification.
819 config SYS_FSL_PBL_PBI
820 string "PBI(pre-boot instructions) commands for the PBL image"
821 depends on RAMBOOT_PBL
823 PBI commands can be used to configure SoC before it starts the execution.
824 Please refer doc/README.pblimage for more details.
826 config SYS_FSL_PBL_RCW
827 string "Aadditional RCW (Power on reset configuration) for the PBL image"
828 depends on RAMBOOT_PBL
830 Enables addition of RCW (Power on reset configuration) in built image.
831 Please refer doc/README.pblimage for more details.
833 config SYS_BOOT_RAMDISK_HIGH
834 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
835 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
838 Enable initrd_high functionality. If defined then the initrd_high
839 feature is enabled and the boot* ramdisk subcommand is enabled.
841 endmenu # Boot images
846 bool "Boot timing and reporting"
848 Enable recording of boot time while booting. To use it, insert
849 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
850 bootstage.h. Only a single entry is recorded for each ID. You can
851 give the entry a name with bootstage_mark_name(). You can also
852 record elapsed time in a particular stage using bootstage_start()
853 before starting and bootstage_accum() when finished. Bootstage will
854 add up all the accumulated time and report it.
856 Normally, IDs are defined in bootstage.h but a small number of
857 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
860 Calls to show_boot_progress() will also result in log entries but
861 these will not have names.
864 bool "Boot timing and reported in SPL"
865 depends on BOOTSTAGE && SPL
867 Enable recording of boot time in SPL. To make this visible to U-Boot
868 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
869 information when SPL finishes and load it when U-Boot proper starts
873 bool "Boot timing and reported in TPL"
874 depends on BOOTSTAGE && TPL
876 Enable recording of boot time in SPL. To make this visible to U-Boot
877 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
878 information when TPL finishes and load it when U-Boot proper starts
881 config BOOTSTAGE_REPORT
882 bool "Display a detailed boot timing report before booting the OS"
885 Enable output of a boot time report just before the OS is booted.
886 This shows how long it took U-Boot to go through each stage of the
887 boot process. The report looks something like this:
889 Timer summary in microseconds:
892 3,575,678 3,575,678 board_init_f start
893 3,575,695 17 arch_cpu_init A9
894 3,575,777 82 arch_cpu_init done
895 3,659,598 83,821 board_init_r start
896 3,910,375 250,777 main_loop
897 29,916,167 26,005,792 bootm_start
898 30,361,327 445,160 start_kernel
900 config BOOTSTAGE_RECORD_COUNT
901 int "Number of boot stage records to store"
905 This is the size of the bootstage record list and is the maximum
906 number of bootstage records that can be recorded.
908 config SPL_BOOTSTAGE_RECORD_COUNT
909 int "Number of boot stage records to store for SPL"
910 depends on SPL_BOOTSTAGE
913 This is the size of the bootstage record list and is the maximum
914 number of bootstage records that can be recorded.
916 config TPL_BOOTSTAGE_RECORD_COUNT
917 int "Number of boot stage records to store for TPL"
918 depends on TPL_BOOTSTAGE
921 This is the size of the bootstage record list and is the maximum
922 number of bootstage records that can be recorded.
925 bool "Store boot timing information in the OS device tree"
928 Stash the bootstage information in the FDT. A root 'bootstage'
929 node is created with each bootstage id as a child. Each child
930 has a 'name' property and either 'mark' containing the
931 mark time in microseconds, or 'accum' containing the
932 accumulated time for that bootstage id in microseconds.
937 name = "board_init_f";
946 Code in the Linux kernel can find this in /proc/devicetree.
948 config BOOTSTAGE_STASH
949 bool "Stash the boot timing information in memory before booting OS"
952 Some OSes do not support device tree. Bootstage can instead write
953 the boot timing information in a binary format at a given address.
954 This happens through a call to bootstage_stash(), typically in
955 the CPU's cleanup_before_linux() function. You can use the
956 'bootstage stash' and 'bootstage unstash' commands to do this on
959 config BOOTSTAGE_STASH_ADDR
960 hex "Address to stash boot timing information"
963 Provide an address which will not be overwritten by the OS when it
964 starts, so that it can read this information when ready.
966 config BOOTSTAGE_STASH_SIZE
967 hex "Size of boot timing stash region"
970 This should be large enough to hold the bootstage stash. A value of
971 4096 (4KiB) is normally plenty.
973 config SHOW_BOOT_PROGRESS
974 bool "Show boot progress in a board-specific manner"
976 Defining this option allows to add some board-specific code (calling
977 a user-provided function show_boot_progress(int) that enables you to
978 show the system's boot progress on some display (for example, some
979 LEDs) on your board. At the moment, the following checkpoints are
982 Legacy uImage format:
985 1 common/cmd_bootm.c before attempting to boot an image
986 -1 common/cmd_bootm.c Image header has bad magic number
987 2 common/cmd_bootm.c Image header has correct magic number
988 -2 common/cmd_bootm.c Image header has bad checksum
989 3 common/cmd_bootm.c Image header has correct checksum
990 -3 common/cmd_bootm.c Image data has bad checksum
991 4 common/cmd_bootm.c Image data has correct checksum
992 -4 common/cmd_bootm.c Image is for unsupported architecture
993 5 common/cmd_bootm.c Architecture check OK
994 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
995 6 common/cmd_bootm.c Image Type check OK
996 -6 common/cmd_bootm.c gunzip uncompression error
997 -7 common/cmd_bootm.c Unimplemented compression type
998 7 common/cmd_bootm.c Uncompression OK
999 8 common/cmd_bootm.c No uncompress/copy overwrite error
1000 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
1002 9 common/image.c Start initial ramdisk verification
1003 -10 common/image.c Ramdisk header has bad magic number
1004 -11 common/image.c Ramdisk header has bad checksum
1005 10 common/image.c Ramdisk header is OK
1006 -12 common/image.c Ramdisk data has bad checksum
1007 11 common/image.c Ramdisk data has correct checksum
1008 12 common/image.c Ramdisk verification complete, start loading
1009 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
1010 13 common/image.c Start multifile image verification
1011 14 common/image.c No initial ramdisk, no multifile, continue.
1013 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
1015 -30 arch/powerpc/lib/board.c Fatal error, hang the system
1016 -31 post/post.c POST test failed, detected by post_output_backlog()
1017 -32 post/post.c POST test failed, detected by post_run_single()
1019 34 common/cmd_doc.c before loading a Image from a DOC device
1020 -35 common/cmd_doc.c Bad usage of "doc" command
1021 35 common/cmd_doc.c correct usage of "doc" command
1022 -36 common/cmd_doc.c No boot device
1023 36 common/cmd_doc.c correct boot device
1024 -37 common/cmd_doc.c Unknown Chip ID on boot device
1025 37 common/cmd_doc.c correct chip ID found, device available
1026 -38 common/cmd_doc.c Read Error on boot device
1027 38 common/cmd_doc.c reading Image header from DOC device OK
1028 -39 common/cmd_doc.c Image header has bad magic number
1029 39 common/cmd_doc.c Image header has correct magic number
1030 -40 common/cmd_doc.c Error reading Image from DOC device
1031 40 common/cmd_doc.c Image header has correct magic number
1032 41 common/cmd_ide.c before loading a Image from a IDE device
1033 -42 common/cmd_ide.c Bad usage of "ide" command
1034 42 common/cmd_ide.c correct usage of "ide" command
1035 -43 common/cmd_ide.c No boot device
1036 43 common/cmd_ide.c boot device found
1037 -44 common/cmd_ide.c Device not available
1038 44 common/cmd_ide.c Device available
1039 -45 common/cmd_ide.c wrong partition selected
1040 45 common/cmd_ide.c partition selected
1041 -46 common/cmd_ide.c Unknown partition table
1042 46 common/cmd_ide.c valid partition table found
1043 -47 common/cmd_ide.c Invalid partition type
1044 47 common/cmd_ide.c correct partition type
1045 -48 common/cmd_ide.c Error reading Image Header on boot device
1046 48 common/cmd_ide.c reading Image Header from IDE device OK
1047 -49 common/cmd_ide.c Image header has bad magic number
1048 49 common/cmd_ide.c Image header has correct magic number
1049 -50 common/cmd_ide.c Image header has bad checksum
1050 50 common/cmd_ide.c Image header has correct checksum
1051 -51 common/cmd_ide.c Error reading Image from IDE device
1052 51 common/cmd_ide.c reading Image from IDE device OK
1053 52 common/cmd_nand.c before loading a Image from a NAND device
1054 -53 common/cmd_nand.c Bad usage of "nand" command
1055 53 common/cmd_nand.c correct usage of "nand" command
1056 -54 common/cmd_nand.c No boot device
1057 54 common/cmd_nand.c boot device found
1058 -55 common/cmd_nand.c Unknown Chip ID on boot device
1059 55 common/cmd_nand.c correct chip ID found, device available
1060 -56 common/cmd_nand.c Error reading Image Header on boot device
1061 56 common/cmd_nand.c reading Image Header from NAND device OK
1062 -57 common/cmd_nand.c Image header has bad magic number
1063 57 common/cmd_nand.c Image header has correct magic number
1064 -58 common/cmd_nand.c Error reading Image from NAND device
1065 58 common/cmd_nand.c reading Image from NAND device OK
1067 -60 common/env_common.c Environment has a bad CRC, using default
1069 64 net/eth.c starting with Ethernet configuration.
1070 -64 net/eth.c no Ethernet found.
1071 65 net/eth.c Ethernet found.
1073 -80 common/cmd_net.c usage wrong
1074 80 common/cmd_net.c before calling net_loop()
1075 -81 common/cmd_net.c some error in net_loop() occurred
1076 81 common/cmd_net.c net_loop() back without error
1077 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1078 82 common/cmd_net.c trying automatic boot
1079 83 common/cmd_net.c running "source" command
1080 -83 common/cmd_net.c some error in automatic boot or "source" command
1081 84 common/cmd_net.c end without errors
1086 100 common/cmd_bootm.c Kernel FIT Image has correct format
1087 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1088 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1089 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1090 102 common/cmd_bootm.c Kernel unit name specified
1091 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1092 103 common/cmd_bootm.c Found configuration node
1093 104 common/cmd_bootm.c Got kernel subimage node offset
1094 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1095 105 common/cmd_bootm.c Kernel subimage hash verification OK
1096 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1097 106 common/cmd_bootm.c Architecture check OK
1098 -106 common/cmd_bootm.c Kernel subimage has wrong type
1099 107 common/cmd_bootm.c Kernel subimage type OK
1100 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1101 108 common/cmd_bootm.c Got kernel subimage data/size
1102 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1103 -109 common/cmd_bootm.c Can't get kernel subimage type
1104 -110 common/cmd_bootm.c Can't get kernel subimage comp
1105 -111 common/cmd_bootm.c Can't get kernel subimage os
1106 -112 common/cmd_bootm.c Can't get kernel subimage load address
1107 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1109 120 common/image.c Start initial ramdisk verification
1110 -120 common/image.c Ramdisk FIT image has incorrect format
1111 121 common/image.c Ramdisk FIT image has correct format
1112 122 common/image.c No ramdisk subimage unit name, using configuration
1113 -122 common/image.c Can't get configuration for ramdisk subimage
1114 123 common/image.c Ramdisk unit name specified
1115 -124 common/image.c Can't get ramdisk subimage node offset
1116 125 common/image.c Got ramdisk subimage node offset
1117 -125 common/image.c Ramdisk subimage hash verification failed
1118 126 common/image.c Ramdisk subimage hash verification OK
1119 -126 common/image.c Ramdisk subimage for unsupported architecture
1120 127 common/image.c Architecture check OK
1121 -127 common/image.c Can't get ramdisk subimage data/size
1122 128 common/image.c Got ramdisk subimage data/size
1123 129 common/image.c Can't get ramdisk load address
1124 -129 common/image.c Got ramdisk load address
1126 -130 common/cmd_doc.c Incorrect FIT image format
1127 131 common/cmd_doc.c FIT image format OK
1129 -140 common/cmd_ide.c Incorrect FIT image format
1130 141 common/cmd_ide.c FIT image format OK
1132 -150 common/cmd_nand.c Incorrect FIT image format
1133 151 common/cmd_nand.c FIT image format OK
1135 config SPL_SHOW_BOOT_PROGRESS
1136 bool "Show boot progress in a board-specific manner in SPL"
1139 Defining this option allows to add some board-specific code (calling
1140 a user-provided function show_boot_progress(int) that enables you to
1141 show the system's boot progress on some display (for example, some
1142 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1149 bool "Support for booting from NOR flash"
1152 Enabling this will make a U-Boot binary that is capable of being
1153 booted via NOR. In this case we will enable certain pinmux early
1154 as the ROM only partially sets up pinmux. We also default to using
1155 NOR for environment.
1158 bool "Support for booting from NAND flash"
1161 Enabling this will make a U-Boot binary that is capable of being
1162 booted via NAND flash. This is not a must, some SoCs need this,
1166 bool "Support for booting from ONENAND"
1169 Enabling this will make a U-Boot binary that is capable of being
1170 booted via ONENAND. This is not a must, some SoCs need this,
1174 bool "Support for booting from QSPI flash"
1176 Enabling this will make a U-Boot binary that is capable of being
1177 booted via QSPI flash. This is not a must, some SoCs need this,
1181 bool "Support for booting from SATA"
1183 Enabling this will make a U-Boot binary that is capable of being
1184 booted via SATA. This is not a must, some SoCs need this,
1188 bool "Support for booting from SD/EMMC"
1190 Enabling this will make a U-Boot binary that is capable of being
1191 booted via SD/EMMC. This is not a must, some SoCs need this,
1195 bool "Support for booting from SD/EMMC and enable QSPI"
1197 Enabling this will make a U-Boot binary that is capable of being
1198 booted via SD/EMMC while enabling QSPI on the platform as well. This
1199 is not a must, some SoCs need this, some not.
1202 bool "Support for booting from SPI flash"
1204 Enabling this will make a U-Boot binary that is capable of being
1205 booted via SPI flash. This is not a must, some SoCs need this,
1210 menu "Autoboot options"
1216 This enables the autoboot. See doc/README.autoboot for detail.
1219 int "delay in seconds before automatically booting"
1223 Delay before automatically running bootcmd;
1224 set to 0 to autoboot with no delay, but you can stop it by key input.
1225 set to -1 to disable autoboot.
1226 set to -2 to autoboot with no delay and not check for abort
1228 If this value is >= 0 then it is also used for the default delay
1229 before starting the default entry in bootmenu. If it is < 0 then
1230 a default value of 10s is used.
1232 See doc/README.autoboot for details.
1234 config AUTOBOOT_KEYED
1235 bool "Stop autobooting via specific input key / string"
1237 This option enables stopping (aborting) of the automatic
1238 boot feature only by issuing a specific input key or
1239 string. If not enabled, any input key will abort the
1240 U-Boot automatic booting process and bring the device
1241 to the U-Boot prompt for user input.
1243 config AUTOBOOT_FLUSH_STDIN
1244 bool "Enable flushing stdin before starting to read the password"
1245 depends on AUTOBOOT_KEYED && !SANDBOX
1247 When this option is enabled stdin buffer will be flushed before
1248 starting to read the password.
1249 This can't be enabled for the sandbox as flushing stdin would
1250 break the autoboot unit tests.
1252 config AUTOBOOT_PROMPT
1253 string "Autoboot stop prompt"
1254 depends on AUTOBOOT_KEYED
1255 default "Autoboot in %d seconds\\n"
1257 This string is displayed before the boot delay selected by
1258 CONFIG_BOOTDELAY starts. If it is not defined there is no
1259 output indicating that autoboot is in progress.
1261 Note that this define is used as the (only) argument to a
1262 printf() call, so it may contain '%' format specifications,
1263 provided that it also includes, sepearated by commas exactly
1264 like in a printf statement, the required arguments. It is
1265 the responsibility of the user to select only such arguments
1266 that are valid in the given context.
1268 config AUTOBOOT_ENCRYPTION
1269 bool "Enable encryption in autoboot stopping"
1270 depends on AUTOBOOT_KEYED
1272 This option allows a string to be entered into U-Boot to stop the
1274 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1276 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1277 to the crypt-based functionality and be compared against the
1278 string in the environment variable 'bootstopkeycrypt'.
1279 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1280 and compared against the hash in the environment variable
1281 'bootstopkeysha256'.
1282 If it matches in either case then boot stops and
1283 a command-line prompt is presented.
1284 This provides a way to ship a secure production device which can also
1285 be accessed at the U-Boot command line.
1287 config AUTOBOOT_SHA256_FALLBACK
1288 bool "Allow fallback from crypt-hashed password to sha256"
1289 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1291 This option adds support to fall back from crypt-hashed
1292 passwords to checking a SHA256 hashed password in case the
1293 'bootstopusesha256' environment variable is set to 'true'.
1295 config AUTOBOOT_DELAY_STR
1296 string "Delay autobooting via specific input key / string"
1297 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1299 This option delays the automatic boot feature by issuing
1300 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1301 or the environment variable "bootdelaykey" is specified
1302 and this string is received from console input before
1303 autoboot starts booting, U-Boot gives a command prompt. The
1304 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1305 used, otherwise it never times out.
1307 config AUTOBOOT_STOP_STR
1308 string "Stop autobooting via specific input key / string"
1309 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1311 This option enables stopping (aborting) of the automatic
1312 boot feature only by issuing a specific input key or
1313 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1314 variable "bootstopkey" is specified and this string is
1315 received from console input before autoboot starts booting,
1316 U-Boot gives a command prompt. The U-Boot prompt never
1317 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1319 config AUTOBOOT_KEYED_CTRLC
1320 bool "Enable Ctrl-C autoboot interruption"
1321 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1323 This option allows for the boot sequence to be interrupted
1324 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1325 Setting this variable provides an escape sequence from the
1326 limited "password" strings.
1328 config AUTOBOOT_NEVER_TIMEOUT
1329 bool "Make the password entry never time-out"
1330 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1332 This option removes the timeout from the password entry
1333 when the user first presses the <Enter> key before entering
1334 any other character.
1336 config AUTOBOOT_STOP_STR_ENABLE
1337 bool "Enable fixed string to stop autobooting"
1338 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1340 This option enables the feature to add a fixed stop
1341 string that is defined at compile time.
1342 In every case it will be tried to load the stop
1343 string from the environment.
1344 In case this is enabled and there is no stop string
1345 in the environment, this will be used as default value.
1347 config AUTOBOOT_STOP_STR_CRYPT
1348 string "Stop autobooting via crypt-hashed password"
1349 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1351 This option adds the feature to only stop the autobooting,
1352 and therefore boot into the U-Boot prompt, when the input
1353 string / password matches a values that is hashed via
1354 one of the supported crypt-style password hashing options
1355 and saved in the environment variable "bootstopkeycrypt".
1357 config AUTOBOOT_STOP_STR_SHA256
1358 string "Stop autobooting via SHA256 hashed password"
1359 depends on AUTOBOOT_STOP_STR_ENABLE
1361 This option adds the feature to only stop the autobooting,
1362 and therefore boot into the U-Boot prompt, when the input
1363 string / password matches a values that is encypted via
1364 a SHA256 hash and saved in the environment variable
1365 "bootstopkeysha256". If the value in that variable
1366 includes a ":", the portion prior to the ":" will be treated
1369 config AUTOBOOT_USE_MENUKEY
1370 bool "Allow a specify key to run a menu from the environment"
1371 depends on !AUTOBOOT_KEYED
1373 If a specific key is pressed to stop autoboot, then the commands in
1374 the environment variable 'menucmd' are executed before boot starts.
1376 config AUTOBOOT_MENUKEY
1377 int "ASCII value of boot key to show a menu"
1379 depends on AUTOBOOT_USE_MENUKEY
1381 If this key is pressed to stop autoboot, then the commands in the
1382 environment variable 'menucmd' will be executed before boot starts.
1383 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1386 config AUTOBOOT_MENU_SHOW
1387 bool "Show a menu on boot"
1388 depends on CMD_BOOTMENU
1390 This enables the boot menu, controlled by environment variables
1391 defined by the board. The menu starts after running the 'preboot'
1392 environmnent variable (if enabled) and before handling the boot delay.
1393 See README.bootmenu for more details.
1395 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1396 bool "Disallow bootmenu to enter the U-Boot console"
1397 depends on AUTOBOOT_MENU_SHOW
1399 If this option is enabled, user can not enter the U-Boot console from
1400 bootmenu. It increases the system security.
1403 bool "Boot retry feature"
1405 Allow for having the U-Boot command prompt time out and attempt
1406 to boot again. If the environment variable "bootretry" is found then
1407 its value is used, otherwise the retry timeout is
1408 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1409 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1411 config BOOT_RETRY_TIME
1412 int "Timeout in seconds before attempting to boot again"
1413 depends on BOOT_RETRY
1415 Time in seconds before the U-Boot prompt will timeout and boot will
1418 config BOOT_RETRY_MIN
1419 int "Minimum timeout in seconds for 'bootretry'"
1420 depends on BOOT_RETRY
1421 default BOOT_RETRY_TIME
1423 The minimum time in seconds that "bootretry" can be set to.
1425 config RESET_TO_RETRY
1426 bool "Reset the board to retry autoboot"
1427 depends on BOOT_RETRY
1429 After the countdown timed out, the board will be reset to restart
1434 menu "Image support"
1436 config IMAGE_PRE_LOAD
1437 bool "Image pre-load support"
1439 Enable an image pre-load stage in the SPL.
1440 This pre-load stage allows to do some manipulation
1441 or check (for example signature check) on an image
1442 before launching it.
1444 config SPL_IMAGE_PRE_LOAD
1445 bool "Image pre-load support within SPL"
1446 depends on SPL && IMAGE_PRE_LOAD
1448 Enable an image pre-load stage in the SPL.
1449 This pre-load stage allows to do some manipulation
1450 or check (for example signature check) on an image
1451 before launching it.
1453 config IMAGE_PRE_LOAD_SIG
1454 bool "Image pre-load signature support"
1455 depends on IMAGE_PRE_LOAD
1456 select FIT_SIGNATURE
1458 select RSA_VERIFY_WITH_PKEY
1460 Enable signature check support in the pre-load stage.
1461 For this feature a very simple header is added before
1462 the image with few fields:
1466 All other information (header size, type of signature,
1467 ...) are provided in the node /image/pre-load/sig of
1470 config SPL_IMAGE_PRE_LOAD_SIG
1471 bool "Image pre-load signature support witin SPL"
1472 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1473 select SPL_FIT_SIGNATURE
1475 select SPL_RSA_VERIFY_WITH_PKEY
1477 Enable signature check support in the pre-load stage in the SPL.
1478 For this feature a very simple header is added before
1479 the image with few fields:
1483 All other information (header size, type of signature,
1484 ...) are provided in the node /image/pre-load/sig of
1490 bool "Enable boot arguments"
1492 Provide boot arguments to bootm command. Boot arguments are specified
1493 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1494 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1495 will be undefined and won't take any space in U-Boot image.
1498 string "Boot arguments"
1499 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1501 This can be used to pass arguments to the bootm command. The value of
1502 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1503 this value will also override the "chosen" node in FDT blob.
1505 config BOOTARGS_SUBST
1506 bool "Support substituting strings in boot arguments"
1508 This allows substituting string values in the boot arguments. These
1509 are applied after the commandline has been built.
1511 One use for this is to insert the root-disk UUID into the command
1512 line where bootargs contains "root=${uuid}"
1514 setenv bootargs "console= root=${uuid}"
1515 # Set the 'uuid' environment variable
1516 part uuid mmc 2:2 uuid
1518 # Command-line substitution will put the real uuid into the
1519 # kernel command line
1522 config USE_BOOTCOMMAND
1523 bool "Enable a default value for bootcmd"
1525 Provide a default value for the bootcmd entry in the environment. If
1526 autoboot is enabled this is what will be run automatically. Enable
1527 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1528 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1529 won't take any space in U-Boot image.
1532 string "bootcmd value"
1533 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1534 default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL
1535 default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL
1536 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1538 This is the string of commands that will be used as bootcmd and if
1539 AUTOBOOT is set, automatically run.
1542 bool "Enable preboot"
1544 When this option is enabled, the existence of the environment
1545 variable "preboot" will be checked immediately before starting the
1546 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1547 entering interactive mode.
1549 This feature is especially useful when "preboot" is automatically
1550 generated or modified. For example, the boot code can modify the
1551 "preboot" when a user holds down a certain combination of keys.
1554 string "preboot default value"
1555 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1556 default "usb start" if USB_KEYBOARD
1559 This is the default of "preboot" environment variable.
1561 config PREBOOT_DEFINED
1563 default y if PREBOOT != ""
1565 config DEFAULT_FDT_FILE
1566 string "Default fdt file"
1568 This option is used to set the default fdt file to boot OS.
1570 config SAVE_PREV_BL_FDT_ADDR
1572 bool "Saves fdt address, passed by the previous bootloader, to env var"
1574 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1575 enable this option to save fdt address, passed by the
1576 previous bootloader for future use.
1577 Address is saved to `prevbl_fdt_addr` environment variable.
1579 If no fdt was provided by previous bootloader, no env variables
1582 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1584 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1586 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1587 enable this option to save initramfs address, passed by the
1588 previous bootloader for future use.
1589 Address is saved to `prevbl_initrd_start_addr` environment variable.
1591 If no initramfs was provided by previous bootloader, no env variables