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 !ARCH_SUNXI && !RISCV
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-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
291 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
293 Specifies a (platform specific) script file to generate the FIT
294 source file used to build the U-Boot FIT image file. This gets
295 passed a list of supported device tree file stub names to
296 include in the generated image.
301 bool "Support Flattened Image Tree within VPL"
308 bool "Support FIT printing within VPL"
312 Support printing the content of the fitImage in a verbose manner in VPL.
314 config VPL_FIT_FULL_CHECK
315 bool "Do a full check of the FIT before using it"
318 Enable this do a full check of the FIT to make sure it is valid. This
319 helps to protect against carefully crafted FITs which take advantage
320 of bugs or omissions in the code. This includes a bad structure,
321 multiple root nodes and the like.
323 config VPL_FIT_SIGNATURE
324 bool "Enable signature verification of FIT firmware within VPL"
333 select VPL_IMAGE_SIGN_INFO
334 select VPL_FIT_FULL_CHECK
336 config VPL_FIT_SIGNATURE_MAX_SIZE
337 hex "Max size of signed FIT structures in VPL"
338 depends on VPL_FIT_SIGNATURE
341 This option sets a max size in bytes for verified FIT uImages.
342 A sane value of 256MB protects corrupted DTB structures from overlapping
343 device memory. Assure this size does not extend past expected storage
352 Utilities for parsing PXE file formats.
355 bool "Standard boot support"
357 depends on DM && OF_CONTROL && BLK
359 U-Boot supports a standard way of locating something to boot,
360 typically an Operating System such as Linux, provided by a distro such
361 as Arch Linux or Debian. Enable this to support iterating through
362 available bootdevs and using bootmeths to find bootflows suitable for
365 Standard boot is not a standard way of booting, just a framework
366 within U-Boot for supporting all the different ways that exist.
370 - bootdev - a device which can hold a distro (e.g. MMC)
371 - bootmeth - a method to scan a bootdev to find bootflows (owned by
373 - bootflow - a description of how to boot (owned by the distro)
376 bool "Enhanced features for standard boot"
379 This enables various useful features for standard boot, which are not
380 essential for operation:
382 - bootdev, bootmeth commands
383 - extra features in the bootflow command
384 - support for selecting the ordering of bootmeths ("bootmeth order")
385 - support for selecting the ordering of bootdevs using the devicetree
386 as well as the "boot_targets" environment variable
389 bool "Standard boot support in VPL"
390 depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK
393 This enables standard boot in SPL. This is neeeded so that VBE
394 (Verified Boot for Embedded) can be used, since it depends on standard
395 boot. It is enabled by default since the main purpose of VPL is to
396 handle the firmware part of VBE.
399 bool "Standard boot support in VPL"
400 depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK
403 This enables standard boot in SPL. This is neeeded so that VBE
404 (Verified Boot for Embedded) can be used, since it depends on standard
405 boot. It is enabled by default since the main purpose of VPL is to
406 handle the firmware part of VBE.
410 config BOOTSTD_BOOTCOMMAND
411 bool "Use bootstd to boot"
412 default y if !DISTRO_DEFAULTS
414 Enable this to select a default boot-command suitable for booting
415 with standard boot. This can be overridden by the board if needed,
416 but the default command should be enough for most boards which use
419 For now this is only selected if distro boot is NOT used, since
420 standard boot does not support all of the features of distro boot
423 config BOOTMETH_GLOBAL
426 Add support for global bootmeths. This feature is used by VBE and
427 EFI bootmgr, since they take full control over which bootdevs are
430 config BOOTMETH_DISTRO
431 bool "Bootdev support for distro boot"
435 Enables support for distro boot using bootdevs. This makes the
436 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
439 This provides a way to try out standard boot on an existing boot flow.
441 config BOOTMETH_DISTRO_PXE
442 bool "Bootdev support for distro boot over network"
443 depends on CMD_PXE && CMD_NET && DM_ETH
446 Enables support for distro boot using bootdevs. This makes the
447 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
449 This provides a way to try out standard boot on an existing boot flow.
451 config BOOTMETH_EFILOADER
452 bool "Bootdev support for EFI boot"
453 depends on CMD_BOOTEFI
456 Enables support for EFI boot using bootdevs. This makes the
457 bootdevs look for a 'boot<arch>.efi' on each filesystem
458 they scan. The resulting file is booted after enabling U-Boot's
461 The <arch> depends on the architecture of the board:
463 aa64 - aarch64 (ARM 64-bit)
467 riscv32 - RISC-V 32-bit
468 riscv64 - RISC-V 64-bit
470 This provides a way to try out standard boot on an existing boot flow.
473 bool "Bootdev support for Verified Boot for Embedded"
476 select BOOTMETH_GLOBAL
479 Enables support for VBE boot. This is a standard boot method which
480 supports selection of various firmware components, seleciton of an OS to
481 boot as well as updating these using fwupd.
483 config SPL_BOOTMETH_VBE
484 bool "Bootdev support for Verified Boot for Embedded (SPL)"
485 depends on SPL && FIT
489 Enables support for VBE boot. This is a standard boot method which
490 supports selection of various firmware components, seleciton of an OS to
491 boot as well as updating these using fwupd.
493 config VPL_BOOTMETH_VBE
494 bool "Bootdev support for Verified Boot for Embedded (VPL)"
495 depends on VPL && FIT
499 Enables support for VBE boot. This is a standard boot method which
500 supports selection of various firmware components, seleciton of an OS to
501 boot as well as updating these using fwupd.
505 config BOOTMETH_VBE_SIMPLE
506 bool "Bootdev support for VBE 'simple' method"
509 Enables support for VBE 'simple' boot. This allows updating a single
510 firmware image in boot media such as MMC. It does not support any sort
511 of rollback, recovery or A/B boot.
513 config BOOTMETH_VBE_SIMPLE_OS
514 bool "Bootdev support for VBE 'simple' method OS phase"
517 Enables support for the OS parts of VBE 'simple' boot. This includes
518 fixing up the device tree with the required VBE information, ready
519 for booting into the OS. This option is only enabled for U-Boot
520 proper, since it is the phase where device tree fixups happen.
522 config SPL_BOOTMETH_VBE_SIMPLE
523 bool "Bootdev support for VBE 'simple' method (SPL)"
527 Enables support for VBE 'simple' boot. This allows updating a single
528 firmware image in boot media such as MMC. It does not support any sort
529 of rollback, recovery or A/B boot.
531 config VPL_BOOTMETH_VBE_SIMPLE
532 bool "Bootdev support for VBE 'simple' method (VPL)"
536 Enables support for VBE 'simple' boot. This allows updating a single
537 firmware image in boot media such as MMC. It does not support any sort
538 of rollback, recovery or A/B boot.
540 config SPL_BOOTMETH_VBE_SIMPLE_FW
541 bool "Bootdev support for VBE 'simple' method firmware phase (SPL)"
545 Enables support for the firmware parts of VBE 'simple' boot. This
546 includes an SPL loader which locates the correct U-Boot to boot into.
547 This option should really only be enabled for VPL, since it is the
548 phase where the SPL + U-Boot decision should be made. But for now,
549 SPL does its own FIT-configuration selection.
551 config VPL_BOOTMETH_VBE_SIMPLE_FW
552 bool "Bootdev support for VBE 'simple' method firmware phase (VPL)"
556 Enables support for the firmware parts of VBE 'simple' boot. This
557 includes an SPL loader which locates the correct SPL to boot into.
558 This option enabled for VPL, since it is the phase where the SPL
564 bool "Support for expos - groups of scenes displaying a UI"
565 default y if BOOTMETH_VBE
567 An expo is a way of presenting and collecting information from the
568 user. It consists of a collection of 'scenes' of which only one is
569 presented at a time. An expo is typically used to show a boot menu
570 and allow settings to be changed.
572 The expo can be presented in graphics form using a vidconsole, or in
573 text form on a serial console.
575 config BOOTMETH_SANDBOX
579 This is a sandbox bootmeth driver used for testing. It always returns
580 -ENOTSUPP when attempting to boot.
582 config BOOTMETH_SCRIPT
583 bool "Bootdev support for U-Boot scripts"
584 default y if BOOTSTD_FULL
586 Enables support for booting a distro via a U-Boot script. This makes
587 the bootdevs look for a 'boot/boot.scr' file which can be used to
590 This provides a way to try out standard boot on an existing boot flow.
591 It is not enabled by default to save space.
595 config LEGACY_IMAGE_FORMAT
596 bool "Enable support for the legacy image format"
597 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
599 This option enables the legacy image format. It is enabled by
600 default for backward compatibility, unless FIT_SIGNATURE is
601 set where it is disabled so that unsigned images cannot be
602 loaded. If a board needs the legacy image format support in this
603 case, enable it here.
605 config SUPPORT_RAW_INITRD
606 bool "Enable raw initrd images"
608 Note, defining the SUPPORT_RAW_INITRD allows user to supply
609 kernel with raw initrd images. The syntax is slightly different, the
610 address of the initrd must be augmented by it's size, in the following
611 format: "<initrd address>:<initrd size>".
613 config OF_BOARD_SETUP
614 bool "Set up board-specific details in device tree before boot"
617 This causes U-Boot to call ft_board_setup() before booting into
618 the Operating System. This function can set up various
619 board-specific information in the device tree for use by the OS.
620 The device tree is then passed to the OS.
622 config OF_SYSTEM_SETUP
623 bool "Set up system-specific details in device tree before boot"
626 This causes U-Boot to call ft_system_setup() before booting into
627 the Operating System. This function can set up various
628 system-specific information in the device tree for use by the OS.
629 The device tree is then passed to the OS.
631 config OF_STDOUT_VIA_ALIAS
632 bool "Update the device-tree stdout alias from U-Boot"
635 This uses U-Boot's serial alias from the aliases node to update
636 the device tree passed to the OS. The "linux,stdout-path" property
637 in the chosen node is set to point to the correct serial node.
638 This option currently references CONFIG_CONS_INDEX, which is
639 incorrect when used with device tree as this option does not
640 exist / should not be used.
642 config HAVE_TEXT_BASE
644 depends on !NIOS2 && !XTENSA
649 depends on HAVE_TEXT_BASE
650 default 0x0 if POSITION_INDEPENDENT
651 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
652 default 0x81700000 if MACH_SUNIV
653 default 0x2a000000 if MACH_SUN9I
654 default 0x4a000000 if SUNXI_MINIMUM_DRAM_MB >= 256
655 default 0x42e00000 if SUNXI_MINIMUM_DRAM_MB >= 64
658 The address in memory that U-Boot will be running from, initially.
660 config HAVE_SYS_MONITOR_BASE
662 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
663 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
667 config SYS_MONITOR_BASE
668 depends on HAVE_SYS_MONITOR_BASE
669 hex "Physical start address of boot monitor code"
672 The physical start address of boot monitor code (which is the same as
673 CONFIG_TEXT_BASE when linking) and the same as CFG_SYS_FLASH_BASE
674 when booting from flash.
676 config SPL_SYS_MONITOR_BASE
677 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
678 hex "Physical start address of SPL monitor code"
679 default SPL_TEXT_BASE
681 config TPL_SYS_MONITOR_BASE
682 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
683 hex "Physical start address of TPL monitor code"
685 config DYNAMIC_SYS_CLK_FREQ
686 bool "Determine CPU clock frequency at run-time"
688 Implement a get_board_sys_clk function that will determine the CPU
689 clock frequency at run time, rather than define it statically.
692 depends on !DYNAMIC_SYS_CLK_FREQ
693 int "CPU clock frequency"
694 default 125000000 if ARCH_LS1012A
695 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
696 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
697 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
698 default 66660000 if ARCH_T2080
699 default 33333333 if RCAR_GEN3
700 default 24000000 if ARCH_EXYNOS
701 default 20000000 if RCAR_GEN2
704 A static value for the CPU frequency. Note that if not required
705 for a given SoC, this can be left at 0.
707 config ARCH_FIXUP_FDT_MEMORY
708 bool "Enable arch_fixup_memory_banks() call"
711 Enable FDT memory map syncup before OS boot. This feature can be
712 used for booting OS with different memory setup where the part of
713 the memory location should be used for different purpose.
716 bool "Support booting Chrome OS"
718 Chrome OS requires U-Boot to set up a table indicating the boot mode
719 (e.g. Developer mode) and a few other things. Enable this if you are
720 booting on a Chromebook to avoid getting an error about an invalid
723 config CHROMEOS_VBOOT
724 bool "Support Chrome OS verified boot"
726 This is intended to enable the full Chrome OS verified boot support
727 in U-Boot. It is not actually implemented in the U-Boot source code
728 at present, so this option is always set to 'n'. It allows
729 distinguishing between booting Chrome OS in a basic way (developer
730 mode) and a full boot.
736 bool "Freescale PBL(pre-boot loader) image format support"
737 select SYS_RAMBOOT if PPC
739 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
740 For more details refer to doc/README.pblimage
743 prompt "Freescale PBL (or predecessor) load location"
744 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
745 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
749 bool "Freescale PBL (or similar) is found on SD card"
752 bool "Freescale PBL (or similar) is found on SPI flash"
755 bool "Freescale PBL (or similar) is not used in this case"
759 config FSL_FIXED_MMC_LOCATION
760 bool "PBL MMC is at a fixed location"
761 depends on SDCARD && !RAMBOOT_PBL
763 config ESDHC_HC_BLK_ADDR
765 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
767 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
768 code length of these soc specify the memory address in block address
769 format. Block length is fixed to 512 bytes as per the SD High
770 Capacity specification.
772 config SYS_FSL_PBL_PBI
773 string "PBI(pre-boot instructions) commands for the PBL image"
774 depends on RAMBOOT_PBL
776 PBI commands can be used to configure SoC before it starts the execution.
777 Please refer doc/README.pblimage for more details.
779 config SYS_FSL_PBL_RCW
780 string "Aadditional RCW (Power on reset configuration) for the PBL image"
781 depends on RAMBOOT_PBL
783 Enables addition of RCW (Power on reset configuration) in built image.
784 Please refer doc/README.pblimage for more details.
786 config SYS_BOOT_RAMDISK_HIGH
787 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
788 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
791 Enable initrd_high functionality. If defined then the initrd_high
792 feature is enabled and the boot* ramdisk subcommand is enabled.
794 endmenu # Boot images
799 bool "Boot timing and reporting"
801 Enable recording of boot time while booting. To use it, insert
802 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
803 bootstage.h. Only a single entry is recorded for each ID. You can
804 give the entry a name with bootstage_mark_name(). You can also
805 record elapsed time in a particular stage using bootstage_start()
806 before starting and bootstage_accum() when finished. Bootstage will
807 add up all the accumulated time and report it.
809 Normally, IDs are defined in bootstage.h but a small number of
810 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
813 Calls to show_boot_progress() will also result in log entries but
814 these will not have names.
817 bool "Boot timing and reported in SPL"
818 depends on BOOTSTAGE && SPL
820 Enable recording of boot time in SPL. To make this visible to U-Boot
821 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
822 information when SPL finishes and load it when U-Boot proper starts
826 bool "Boot timing and reported in TPL"
827 depends on BOOTSTAGE && TPL
829 Enable recording of boot time in SPL. To make this visible to U-Boot
830 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
831 information when TPL finishes and load it when U-Boot proper starts
834 config BOOTSTAGE_REPORT
835 bool "Display a detailed boot timing report before booting the OS"
838 Enable output of a boot time report just before the OS is booted.
839 This shows how long it took U-Boot to go through each stage of the
840 boot process. The report looks something like this:
842 Timer summary in microseconds:
845 3,575,678 3,575,678 board_init_f start
846 3,575,695 17 arch_cpu_init A9
847 3,575,777 82 arch_cpu_init done
848 3,659,598 83,821 board_init_r start
849 3,910,375 250,777 main_loop
850 29,916,167 26,005,792 bootm_start
851 30,361,327 445,160 start_kernel
853 config BOOTSTAGE_RECORD_COUNT
854 int "Number of boot stage records to store"
858 This is the size of the bootstage record list and is the maximum
859 number of bootstage records that can be recorded.
861 config SPL_BOOTSTAGE_RECORD_COUNT
862 int "Number of boot stage records to store for SPL"
863 depends on SPL_BOOTSTAGE
866 This is the size of the bootstage record list and is the maximum
867 number of bootstage records that can be recorded.
869 config TPL_BOOTSTAGE_RECORD_COUNT
870 int "Number of boot stage records to store for TPL"
871 depends on TPL_BOOTSTAGE
874 This is the size of the bootstage record list and is the maximum
875 number of bootstage records that can be recorded.
878 bool "Store boot timing information in the OS device tree"
881 Stash the bootstage information in the FDT. A root 'bootstage'
882 node is created with each bootstage id as a child. Each child
883 has a 'name' property and either 'mark' containing the
884 mark time in microseconds, or 'accum' containing the
885 accumulated time for that bootstage id in microseconds.
890 name = "board_init_f";
899 Code in the Linux kernel can find this in /proc/devicetree.
901 config BOOTSTAGE_STASH
902 bool "Stash the boot timing information in memory before booting OS"
905 Some OSes do not support device tree. Bootstage can instead write
906 the boot timing information in a binary format at a given address.
907 This happens through a call to bootstage_stash(), typically in
908 the CPU's cleanup_before_linux() function. You can use the
909 'bootstage stash' and 'bootstage unstash' commands to do this on
912 config BOOTSTAGE_STASH_ADDR
913 hex "Address to stash boot timing information"
916 Provide an address which will not be overwritten by the OS when it
917 starts, so that it can read this information when ready.
919 config BOOTSTAGE_STASH_SIZE
920 hex "Size of boot timing stash region"
923 This should be large enough to hold the bootstage stash. A value of
924 4096 (4KiB) is normally plenty.
926 config SHOW_BOOT_PROGRESS
927 bool "Show boot progress in a board-specific manner"
929 Defining this option allows to add some board-specific code (calling
930 a user-provided function show_boot_progress(int) that enables you to
931 show the system's boot progress on some display (for example, some
932 LEDs) on your board. At the moment, the following checkpoints are
935 Legacy uImage format:
938 1 common/cmd_bootm.c before attempting to boot an image
939 -1 common/cmd_bootm.c Image header has bad magic number
940 2 common/cmd_bootm.c Image header has correct magic number
941 -2 common/cmd_bootm.c Image header has bad checksum
942 3 common/cmd_bootm.c Image header has correct checksum
943 -3 common/cmd_bootm.c Image data has bad checksum
944 4 common/cmd_bootm.c Image data has correct checksum
945 -4 common/cmd_bootm.c Image is for unsupported architecture
946 5 common/cmd_bootm.c Architecture check OK
947 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
948 6 common/cmd_bootm.c Image Type check OK
949 -6 common/cmd_bootm.c gunzip uncompression error
950 -7 common/cmd_bootm.c Unimplemented compression type
951 7 common/cmd_bootm.c Uncompression OK
952 8 common/cmd_bootm.c No uncompress/copy overwrite error
953 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
955 9 common/image.c Start initial ramdisk verification
956 -10 common/image.c Ramdisk header has bad magic number
957 -11 common/image.c Ramdisk header has bad checksum
958 10 common/image.c Ramdisk header is OK
959 -12 common/image.c Ramdisk data has bad checksum
960 11 common/image.c Ramdisk data has correct checksum
961 12 common/image.c Ramdisk verification complete, start loading
962 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
963 13 common/image.c Start multifile image verification
964 14 common/image.c No initial ramdisk, no multifile, continue.
966 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
968 -30 arch/powerpc/lib/board.c Fatal error, hang the system
969 -31 post/post.c POST test failed, detected by post_output_backlog()
970 -32 post/post.c POST test failed, detected by post_run_single()
972 34 common/cmd_doc.c before loading a Image from a DOC device
973 -35 common/cmd_doc.c Bad usage of "doc" command
974 35 common/cmd_doc.c correct usage of "doc" command
975 -36 common/cmd_doc.c No boot device
976 36 common/cmd_doc.c correct boot device
977 -37 common/cmd_doc.c Unknown Chip ID on boot device
978 37 common/cmd_doc.c correct chip ID found, device available
979 -38 common/cmd_doc.c Read Error on boot device
980 38 common/cmd_doc.c reading Image header from DOC device OK
981 -39 common/cmd_doc.c Image header has bad magic number
982 39 common/cmd_doc.c Image header has correct magic number
983 -40 common/cmd_doc.c Error reading Image from DOC device
984 40 common/cmd_doc.c Image header has correct magic number
985 41 common/cmd_ide.c before loading a Image from a IDE device
986 -42 common/cmd_ide.c Bad usage of "ide" command
987 42 common/cmd_ide.c correct usage of "ide" command
988 -43 common/cmd_ide.c No boot device
989 43 common/cmd_ide.c boot device found
990 -44 common/cmd_ide.c Device not available
991 44 common/cmd_ide.c Device available
992 -45 common/cmd_ide.c wrong partition selected
993 45 common/cmd_ide.c partition selected
994 -46 common/cmd_ide.c Unknown partition table
995 46 common/cmd_ide.c valid partition table found
996 -47 common/cmd_ide.c Invalid partition type
997 47 common/cmd_ide.c correct partition type
998 -48 common/cmd_ide.c Error reading Image Header on boot device
999 48 common/cmd_ide.c reading Image Header from IDE device OK
1000 -49 common/cmd_ide.c Image header has bad magic number
1001 49 common/cmd_ide.c Image header has correct magic number
1002 -50 common/cmd_ide.c Image header has bad checksum
1003 50 common/cmd_ide.c Image header has correct checksum
1004 -51 common/cmd_ide.c Error reading Image from IDE device
1005 51 common/cmd_ide.c reading Image from IDE device OK
1006 52 common/cmd_nand.c before loading a Image from a NAND device
1007 -53 common/cmd_nand.c Bad usage of "nand" command
1008 53 common/cmd_nand.c correct usage of "nand" command
1009 -54 common/cmd_nand.c No boot device
1010 54 common/cmd_nand.c boot device found
1011 -55 common/cmd_nand.c Unknown Chip ID on boot device
1012 55 common/cmd_nand.c correct chip ID found, device available
1013 -56 common/cmd_nand.c Error reading Image Header on boot device
1014 56 common/cmd_nand.c reading Image Header from NAND device OK
1015 -57 common/cmd_nand.c Image header has bad magic number
1016 57 common/cmd_nand.c Image header has correct magic number
1017 -58 common/cmd_nand.c Error reading Image from NAND device
1018 58 common/cmd_nand.c reading Image from NAND device OK
1020 -60 common/env_common.c Environment has a bad CRC, using default
1022 64 net/eth.c starting with Ethernet configuration.
1023 -64 net/eth.c no Ethernet found.
1024 65 net/eth.c Ethernet found.
1026 -80 common/cmd_net.c usage wrong
1027 80 common/cmd_net.c before calling net_loop()
1028 -81 common/cmd_net.c some error in net_loop() occurred
1029 81 common/cmd_net.c net_loop() back without error
1030 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1031 82 common/cmd_net.c trying automatic boot
1032 83 common/cmd_net.c running "source" command
1033 -83 common/cmd_net.c some error in automatic boot or "source" command
1034 84 common/cmd_net.c end without errors
1039 100 common/cmd_bootm.c Kernel FIT Image has correct format
1040 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1041 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1042 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1043 102 common/cmd_bootm.c Kernel unit name specified
1044 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1045 103 common/cmd_bootm.c Found configuration node
1046 104 common/cmd_bootm.c Got kernel subimage node offset
1047 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1048 105 common/cmd_bootm.c Kernel subimage hash verification OK
1049 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1050 106 common/cmd_bootm.c Architecture check OK
1051 -106 common/cmd_bootm.c Kernel subimage has wrong type
1052 107 common/cmd_bootm.c Kernel subimage type OK
1053 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1054 108 common/cmd_bootm.c Got kernel subimage data/size
1055 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1056 -109 common/cmd_bootm.c Can't get kernel subimage type
1057 -110 common/cmd_bootm.c Can't get kernel subimage comp
1058 -111 common/cmd_bootm.c Can't get kernel subimage os
1059 -112 common/cmd_bootm.c Can't get kernel subimage load address
1060 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1062 120 common/image.c Start initial ramdisk verification
1063 -120 common/image.c Ramdisk FIT image has incorrect format
1064 121 common/image.c Ramdisk FIT image has correct format
1065 122 common/image.c No ramdisk subimage unit name, using configuration
1066 -122 common/image.c Can't get configuration for ramdisk subimage
1067 123 common/image.c Ramdisk unit name specified
1068 -124 common/image.c Can't get ramdisk subimage node offset
1069 125 common/image.c Got ramdisk subimage node offset
1070 -125 common/image.c Ramdisk subimage hash verification failed
1071 126 common/image.c Ramdisk subimage hash verification OK
1072 -126 common/image.c Ramdisk subimage for unsupported architecture
1073 127 common/image.c Architecture check OK
1074 -127 common/image.c Can't get ramdisk subimage data/size
1075 128 common/image.c Got ramdisk subimage data/size
1076 129 common/image.c Can't get ramdisk load address
1077 -129 common/image.c Got ramdisk load address
1079 -130 common/cmd_doc.c Incorrect FIT image format
1080 131 common/cmd_doc.c FIT image format OK
1082 -140 common/cmd_ide.c Incorrect FIT image format
1083 141 common/cmd_ide.c FIT image format OK
1085 -150 common/cmd_nand.c Incorrect FIT image format
1086 151 common/cmd_nand.c FIT image format OK
1088 config SPL_SHOW_BOOT_PROGRESS
1089 bool "Show boot progress in a board-specific manner in SPL"
1092 Defining this option allows to add some board-specific code (calling
1093 a user-provided function show_boot_progress(int) that enables you to
1094 show the system's boot progress on some display (for example, some
1095 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1102 bool "Support for booting from NOR flash"
1105 Enabling this will make a U-Boot binary that is capable of being
1106 booted via NOR. In this case we will enable certain pinmux early
1107 as the ROM only partially sets up pinmux. We also default to using
1108 NOR for environment.
1111 bool "Support for booting from NAND flash"
1114 Enabling this will make a U-Boot binary that is capable of being
1115 booted via NAND flash. This is not a must, some SoCs need this,
1119 bool "Support for booting from ONENAND"
1122 Enabling this will make a U-Boot binary that is capable of being
1123 booted via ONENAND. This is not a must, some SoCs need this,
1127 bool "Support for booting from QSPI flash"
1129 Enabling this will make a U-Boot binary that is capable of being
1130 booted via QSPI flash. This is not a must, some SoCs need this,
1134 bool "Support for booting from SATA"
1136 Enabling this will make a U-Boot binary that is capable of being
1137 booted via SATA. This is not a must, some SoCs need this,
1141 bool "Support for booting from SD/EMMC"
1143 Enabling this will make a U-Boot binary that is capable of being
1144 booted via SD/EMMC. This is not a must, some SoCs need this,
1148 bool "Support for booting from SD/EMMC and enable QSPI"
1150 Enabling this will make a U-Boot binary that is capable of being
1151 booted via SD/EMMC while enabling QSPI on the platform as well. This
1152 is not a must, some SoCs need this, some not.
1155 bool "Support for booting from SPI flash"
1157 Enabling this will make a U-Boot binary that is capable of being
1158 booted via SPI flash. This is not a must, some SoCs need this,
1163 menu "Autoboot options"
1169 This enables the autoboot. See doc/README.autoboot for detail.
1172 int "delay in seconds before automatically booting"
1176 Delay before automatically running bootcmd;
1177 set to 0 to autoboot with no delay, but you can stop it by key input.
1178 set to -1 to disable autoboot.
1179 set to -2 to autoboot with no delay and not check for abort
1181 If this value is >= 0 then it is also used for the default delay
1182 before starting the default entry in bootmenu. If it is < 0 then
1183 a default value of 10s is used.
1185 See doc/README.autoboot for details.
1187 config AUTOBOOT_KEYED
1188 bool "Stop autobooting via specific input key / string"
1190 This option enables stopping (aborting) of the automatic
1191 boot feature only by issuing a specific input key or
1192 string. If not enabled, any input key will abort the
1193 U-Boot automatic booting process and bring the device
1194 to the U-Boot prompt for user input.
1196 config AUTOBOOT_FLUSH_STDIN
1197 bool "Enable flushing stdin before starting to read the password"
1198 depends on AUTOBOOT_KEYED && !SANDBOX
1200 When this option is enabled stdin buffer will be flushed before
1201 starting to read the password.
1202 This can't be enabled for the sandbox as flushing stdin would
1203 break the autoboot unit tests.
1205 config AUTOBOOT_PROMPT
1206 string "Autoboot stop prompt"
1207 depends on AUTOBOOT_KEYED
1208 default "Autoboot in %d seconds\\n"
1210 This string is displayed before the boot delay selected by
1211 CONFIG_BOOTDELAY starts. If it is not defined there is no
1212 output indicating that autoboot is in progress.
1214 Note that this define is used as the (only) argument to a
1215 printf() call, so it may contain '%' format specifications,
1216 provided that it also includes, sepearated by commas exactly
1217 like in a printf statement, the required arguments. It is
1218 the responsibility of the user to select only such arguments
1219 that are valid in the given context.
1221 config AUTOBOOT_ENCRYPTION
1222 bool "Enable encryption in autoboot stopping"
1223 depends on AUTOBOOT_KEYED
1225 This option allows a string to be entered into U-Boot to stop the
1227 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1229 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1230 to the crypt-based functionality and be compared against the
1231 string in the environment variable 'bootstopkeycrypt'.
1232 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1233 and compared against the hash in the environment variable
1234 'bootstopkeysha256'.
1235 If it matches in either case then boot stops and
1236 a command-line prompt is presented.
1237 This provides a way to ship a secure production device which can also
1238 be accessed at the U-Boot command line.
1240 config AUTOBOOT_SHA256_FALLBACK
1241 bool "Allow fallback from crypt-hashed password to sha256"
1242 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1244 This option adds support to fall back from crypt-hashed
1245 passwords to checking a SHA256 hashed password in case the
1246 'bootstopusesha256' environment variable is set to 'true'.
1248 config AUTOBOOT_DELAY_STR
1249 string "Delay autobooting via specific input key / string"
1250 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1252 This option delays the automatic boot feature by issuing
1253 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1254 or the environment variable "bootdelaykey" is specified
1255 and this string is received from console input before
1256 autoboot starts booting, U-Boot gives a command prompt. The
1257 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1258 used, otherwise it never times out.
1260 config AUTOBOOT_STOP_STR
1261 string "Stop autobooting via specific input key / string"
1262 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1264 This option enables stopping (aborting) of the automatic
1265 boot feature only by issuing a specific input key or
1266 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1267 variable "bootstopkey" is specified and this string is
1268 received from console input before autoboot starts booting,
1269 U-Boot gives a command prompt. The U-Boot prompt never
1270 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1272 config AUTOBOOT_KEYED_CTRLC
1273 bool "Enable Ctrl-C autoboot interruption"
1274 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1276 This option allows for the boot sequence to be interrupted
1277 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1278 Setting this variable provides an escape sequence from the
1279 limited "password" strings.
1281 config AUTOBOOT_NEVER_TIMEOUT
1282 bool "Make the password entry never time-out"
1283 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1285 This option removes the timeout from the password entry
1286 when the user first presses the <Enter> key before entering
1287 any other character.
1289 config AUTOBOOT_STOP_STR_ENABLE
1290 bool "Enable fixed string to stop autobooting"
1291 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1293 This option enables the feature to add a fixed stop
1294 string that is defined at compile time.
1295 In every case it will be tried to load the stop
1296 string from the environment.
1297 In case this is enabled and there is no stop string
1298 in the environment, this will be used as default value.
1300 config AUTOBOOT_STOP_STR_CRYPT
1301 string "Stop autobooting via crypt-hashed password"
1302 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1304 This option adds the feature to only stop the autobooting,
1305 and therefore boot into the U-Boot prompt, when the input
1306 string / password matches a values that is hashed via
1307 one of the supported crypt-style password hashing options
1308 and saved in the environment variable "bootstopkeycrypt".
1310 config AUTOBOOT_STOP_STR_SHA256
1311 string "Stop autobooting via SHA256 hashed password"
1312 depends on AUTOBOOT_STOP_STR_ENABLE
1314 This option adds the feature to only stop the autobooting,
1315 and therefore boot into the U-Boot prompt, when the input
1316 string / password matches a values that is encypted via
1317 a SHA256 hash and saved in the environment variable
1318 "bootstopkeysha256". If the value in that variable
1319 includes a ":", the portion prior to the ":" will be treated
1322 config AUTOBOOT_USE_MENUKEY
1323 bool "Allow a specify key to run a menu from the environment"
1324 depends on !AUTOBOOT_KEYED
1326 If a specific key is pressed to stop autoboot, then the commands in
1327 the environment variable 'menucmd' are executed before boot starts.
1329 config AUTOBOOT_MENUKEY
1330 int "ASCII value of boot key to show a menu"
1332 depends on AUTOBOOT_USE_MENUKEY
1334 If this key is pressed to stop autoboot, then the commands in the
1335 environment variable 'menucmd' will be executed before boot starts.
1336 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1339 config AUTOBOOT_MENU_SHOW
1340 bool "Show a menu on boot"
1341 depends on CMD_BOOTMENU
1343 This enables the boot menu, controlled by environment variables
1344 defined by the board. The menu starts after running the 'preboot'
1345 environmnent variable (if enabled) and before handling the boot delay.
1346 See README.bootmenu for more details.
1348 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1349 bool "Disallow bootmenu to enter the U-Boot console"
1350 depends on AUTOBOOT_MENU_SHOW
1352 If this option is enabled, user can not enter the U-Boot console from
1353 bootmenu. It increases the system security.
1356 bool "Boot retry feature"
1358 Allow for having the U-Boot command prompt time out and attempt
1359 to boot again. If the environment variable "bootretry" is found then
1360 its value is used, otherwise the retry timeout is
1361 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1362 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1364 config BOOT_RETRY_TIME
1365 int "Timeout in seconds before attempting to boot again"
1366 depends on BOOT_RETRY
1368 Time in seconds before the U-Boot prompt will timeout and boot will
1371 config BOOT_RETRY_MIN
1372 int "Minimum timeout in seconds for 'bootretry'"
1373 depends on BOOT_RETRY
1374 default BOOT_RETRY_TIME
1376 The minimum time in seconds that "bootretry" can be set to.
1378 config RESET_TO_RETRY
1379 bool "Reset the board to retry autoboot"
1380 depends on BOOT_RETRY
1382 After the countdown timed out, the board will be reset to restart
1387 menu "Image support"
1389 config IMAGE_PRE_LOAD
1390 bool "Image pre-load support"
1392 Enable an image pre-load stage in the SPL.
1393 This pre-load stage allows to do some manipulation
1394 or check (for example signature check) on an image
1395 before launching it.
1397 config SPL_IMAGE_PRE_LOAD
1398 bool "Image pre-load support within SPL"
1399 depends on SPL && IMAGE_PRE_LOAD
1401 Enable an image pre-load stage in the SPL.
1402 This pre-load stage allows to do some manipulation
1403 or check (for example signature check) on an image
1404 before launching it.
1406 config IMAGE_PRE_LOAD_SIG
1407 bool "Image pre-load signature support"
1408 depends on IMAGE_PRE_LOAD
1409 select FIT_SIGNATURE
1411 select RSA_VERIFY_WITH_PKEY
1413 Enable signature check support in the pre-load stage.
1414 For this feature a very simple header is added before
1415 the image with few fields:
1419 All other information (header size, type of signature,
1420 ...) are provided in the node /image/pre-load/sig of
1423 config SPL_IMAGE_PRE_LOAD_SIG
1424 bool "Image pre-load signature support witin SPL"
1425 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1426 select SPL_FIT_SIGNATURE
1428 select SPL_RSA_VERIFY_WITH_PKEY
1430 Enable signature check support in the pre-load stage in the SPL.
1431 For this feature a very simple header is added before
1432 the image with few fields:
1436 All other information (header size, type of signature,
1437 ...) are provided in the node /image/pre-load/sig of
1443 bool "Enable boot arguments"
1445 Provide boot arguments to bootm command. Boot arguments are specified
1446 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1447 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1448 will be undefined and won't take any space in U-Boot image.
1451 string "Boot arguments"
1452 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1454 This can be used to pass arguments to the bootm command. The value of
1455 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1456 this value will also override the "chosen" node in FDT blob.
1458 config BOOTARGS_SUBST
1459 bool "Support substituting strings in boot arguments"
1461 This allows substituting string values in the boot arguments. These
1462 are applied after the commandline has been built.
1464 One use for this is to insert the root-disk UUID into the command
1465 line where bootargs contains "root=${uuid}"
1467 setenv bootargs "console= root=${uuid}"
1468 # Set the 'uuid' environment variable
1469 part uuid mmc 2:2 uuid
1471 # Command-line substitution will put the real uuid into the
1472 # kernel command line
1475 config USE_BOOTCOMMAND
1476 bool "Enable a default value for bootcmd"
1478 Provide a default value for the bootcmd entry in the environment. If
1479 autoboot is enabled this is what will be run automatically. Enable
1480 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1481 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1482 won't take any space in U-Boot image.
1485 string "bootcmd value"
1486 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1487 default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL
1488 default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL
1489 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1491 This is the string of commands that will be used as bootcmd and if
1492 AUTOBOOT is set, automatically run.
1495 bool "Enable preboot"
1497 When this option is enabled, the existence of the environment
1498 variable "preboot" will be checked immediately before starting the
1499 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1500 entering interactive mode.
1502 This feature is especially useful when "preboot" is automatically
1503 generated or modified. For example, the boot code can modify the
1504 "preboot" when a user holds down a certain combination of keys.
1507 string "preboot default value"
1508 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1509 default "usb start" if USB_KEYBOARD
1512 This is the default of "preboot" environment variable.
1514 config PREBOOT_DEFINED
1516 default y if PREBOOT != ""
1518 config DEFAULT_FDT_FILE
1519 string "Default fdt file"
1521 This option is used to set the default fdt file to boot OS.
1523 config SAVE_PREV_BL_FDT_ADDR
1525 bool "Saves fdt address, passed by the previous bootloader, to env var"
1527 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1528 enable this option to save fdt address, passed by the
1529 previous bootloader for future use.
1530 Address is saved to `prevbl_fdt_addr` environment variable.
1532 If no fdt was provided by previous bootloader, no env variables
1535 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1537 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1539 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1540 enable this option to save initramfs address, passed by the
1541 previous bootloader for future use.
1542 Address is saved to `prevbl_initrd_start_addr` environment variable.
1544 If no initramfs was provided by previous bootloader, no env variables