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-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
478 Enables support for VBE boot. This is a standard boot method which
479 supports selection of various firmware components, seleciton of an OS to
480 boot as well as updating these using fwupd.
482 config SPL_BOOTMETH_VBE
483 bool "Bootdev support for Verified Boot for Embedded (SPL)"
484 depends on SPL && FIT
487 Enables support for VBE boot. This is a standard boot method which
488 supports selection of various firmware components, seleciton of an OS to
489 boot as well as updating these using fwupd.
491 config VPL_BOOTMETH_VBE
492 bool "Bootdev support for Verified Boot for Embedded (VPL)"
493 depends on VPL && FIT
496 Enables support for VBE boot. This is a standard boot method which
497 supports selection of various firmware components, seleciton of an OS to
498 boot as well as updating these using fwupd.
502 config BOOTMETH_VBE_SIMPLE
503 bool "Bootdev support for VBE 'simple' method"
506 Enables support for VBE 'simple' boot. This allows updating a single
507 firmware image in boot media such as MMC. It does not support any sort
508 of rollback, recovery or A/B boot.
510 config BOOTMETH_VBE_SIMPLE_OS
511 bool "Bootdev support for VBE 'simple' method OS phase"
514 Enables support for the OS parts of VBE 'simple' boot. This includes
515 fixing up the device tree with the required VBE information, ready
516 for booting into the OS. This option is only enabled for U-Boot
517 proper, since it is the phase where device tree fixups happen.
519 config SPL_BOOTMETH_VBE_SIMPLE
520 bool "Bootdev support for VBE 'simple' method (SPL)"
524 Enables support for VBE 'simple' boot. This allows updating a single
525 firmware image in boot media such as MMC. It does not support any sort
526 of rollback, recovery or A/B boot.
528 config VPL_BOOTMETH_VBE_SIMPLE
529 bool "Bootdev support for VBE 'simple' method (VPL)"
533 Enables support for VBE 'simple' boot. This allows updating a single
534 firmware image in boot media such as MMC. It does not support any sort
535 of rollback, recovery or A/B boot.
537 config SPL_BOOTMETH_VBE_SIMPLE_FW
538 bool "Bootdev support for VBE 'simple' method firmware phase (SPL)"
542 Enables support for the firmware parts of VBE 'simple' boot. This
543 includes an SPL loader which locates the correct U-Boot to boot into.
544 This option should really only be enabled for VPL, since it is the
545 phase where the SPL + U-Boot decision should be made. But for now,
546 SPL does its own FIT-configuration selection.
548 config VPL_BOOTMETH_VBE_SIMPLE_FW
549 bool "Bootdev support for VBE 'simple' method firmware phase (VPL)"
553 Enables support for the firmware parts of VBE 'simple' boot. This
554 includes an SPL loader which locates the correct SPL to boot into.
555 This option enabled for VPL, since it is the phase where the SPL
561 bool "Support for expos - groups of scenes displaying a UI"
562 default y if BOOTMETH_VBE
564 An expo is a way of presenting and collecting information from the
565 user. It consists of a collection of 'scenes' of which only one is
566 presented at a time. An expo is typically used to show a boot menu
567 and allow settings to be changed.
569 The expo can be presented in graphics form using a vidconsole, or in
570 text form on a serial console.
572 config BOOTMETH_SANDBOX
576 This is a sandbox bootmeth driver used for testing. It always returns
577 -ENOTSUPP when attempting to boot.
579 config BOOTMETH_SCRIPT
580 bool "Bootdev support for U-Boot scripts"
581 default y if BOOTSTD_FULL
583 Enables support for booting a distro via a U-Boot script. This makes
584 the bootdevs look for a 'boot/boot.scr' file which can be used to
587 This provides a way to try out standard boot on an existing boot flow.
588 It is not enabled by default to save space.
592 config LEGACY_IMAGE_FORMAT
593 bool "Enable support for the legacy image format"
594 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
596 This option enables the legacy image format. It is enabled by
597 default for backward compatibility, unless FIT_SIGNATURE is
598 set where it is disabled so that unsigned images cannot be
599 loaded. If a board needs the legacy image format support in this
600 case, enable it here.
602 config SUPPORT_RAW_INITRD
603 bool "Enable raw initrd images"
605 Note, defining the SUPPORT_RAW_INITRD allows user to supply
606 kernel with raw initrd images. The syntax is slightly different, the
607 address of the initrd must be augmented by it's size, in the following
608 format: "<initrd address>:<initrd size>".
610 config OF_BOARD_SETUP
611 bool "Set up board-specific details in device tree before boot"
614 This causes U-Boot to call ft_board_setup() before booting into
615 the Operating System. This function can set up various
616 board-specific information in the device tree for use by the OS.
617 The device tree is then passed to the OS.
619 config OF_SYSTEM_SETUP
620 bool "Set up system-specific details in device tree before boot"
623 This causes U-Boot to call ft_system_setup() before booting into
624 the Operating System. This function can set up various
625 system-specific information in the device tree for use by the OS.
626 The device tree is then passed to the OS.
628 config OF_STDOUT_VIA_ALIAS
629 bool "Update the device-tree stdout alias from U-Boot"
632 This uses U-Boot's serial alias from the aliases node to update
633 the device tree passed to the OS. The "linux,stdout-path" property
634 in the chosen node is set to point to the correct serial node.
635 This option currently references CONFIG_CONS_INDEX, which is
636 incorrect when used with device tree as this option does not
637 exist / should not be used.
639 config HAVE_TEXT_BASE
641 depends on !NIOS2 && !XTENSA
646 depends on HAVE_TEXT_BASE
647 default 0x0 if POSITION_INDEPENDENT
648 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
649 default 0x81700000 if MACH_SUNIV
650 default 0x2a000000 if MACH_SUN9I
651 default 0x4a000000 if SUNXI_MINIMUM_DRAM_MB >= 256
652 default 0x42e00000 if SUNXI_MINIMUM_DRAM_MB >= 64
655 The address in memory that U-Boot will be running from, initially.
657 config HAVE_SYS_MONITOR_BASE
659 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
660 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
664 config SYS_MONITOR_BASE
665 depends on HAVE_SYS_MONITOR_BASE
666 hex "Physical start address of boot monitor code"
669 The physical start address of boot monitor code (which is the same as
670 CONFIG_TEXT_BASE when linking) and the same as CFG_SYS_FLASH_BASE
671 when booting from flash.
673 config SPL_SYS_MONITOR_BASE
674 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
675 hex "Physical start address of SPL monitor code"
676 default SPL_TEXT_BASE
678 config TPL_SYS_MONITOR_BASE
679 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
680 hex "Physical start address of TPL monitor code"
682 config DYNAMIC_SYS_CLK_FREQ
683 bool "Determine CPU clock frequency at run-time"
685 Implement a get_board_sys_clk function that will determine the CPU
686 clock frequency at run time, rather than define it statically.
689 depends on !DYNAMIC_SYS_CLK_FREQ
690 int "CPU clock frequency"
691 default 125000000 if ARCH_LS1012A
692 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
693 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
694 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
695 default 66660000 if ARCH_T2080
696 default 33333333 if RCAR_GEN3
697 default 24000000 if ARCH_EXYNOS
698 default 20000000 if RCAR_GEN2
701 A static value for the CPU frequency. Note that if not required
702 for a given SoC, this can be left at 0.
704 config ARCH_FIXUP_FDT_MEMORY
705 bool "Enable arch_fixup_memory_banks() call"
708 Enable FDT memory map syncup before OS boot. This feature can be
709 used for booting OS with different memory setup where the part of
710 the memory location should be used for different purpose.
713 bool "Support booting Chrome OS"
715 Chrome OS requires U-Boot to set up a table indicating the boot mode
716 (e.g. Developer mode) and a few other things. Enable this if you are
717 booting on a Chromebook to avoid getting an error about an invalid
720 config CHROMEOS_VBOOT
721 bool "Support Chrome OS verified boot"
723 This is intended to enable the full Chrome OS verified boot support
724 in U-Boot. It is not actually implemented in the U-Boot source code
725 at present, so this option is always set to 'n'. It allows
726 distinguishing between booting Chrome OS in a basic way (developer
727 mode) and a full boot.
733 bool "Freescale PBL(pre-boot loader) image format support"
734 select SYS_RAMBOOT if PPC
736 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
737 For more details refer to doc/README.pblimage
740 prompt "Freescale PBL (or predecessor) load location"
741 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
742 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
746 bool "Freescale PBL (or similar) is found on SD card"
749 bool "Freescale PBL (or similar) is found on SPI flash"
752 bool "Freescale PBL (or similar) is not used in this case"
756 config FSL_FIXED_MMC_LOCATION
757 bool "PBL MMC is at a fixed location"
758 depends on SDCARD && !RAMBOOT_PBL
760 config ESDHC_HC_BLK_ADDR
762 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
764 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
765 code length of these soc specify the memory address in block address
766 format. Block length is fixed to 512 bytes as per the SD High
767 Capacity specification.
769 config SYS_FSL_PBL_PBI
770 string "PBI(pre-boot instructions) commands for the PBL image"
771 depends on RAMBOOT_PBL
773 PBI commands can be used to configure SoC before it starts the execution.
774 Please refer doc/README.pblimage for more details.
776 config SYS_FSL_PBL_RCW
777 string "Aadditional RCW (Power on reset configuration) for the PBL image"
778 depends on RAMBOOT_PBL
780 Enables addition of RCW (Power on reset configuration) in built image.
781 Please refer doc/README.pblimage for more details.
783 config SYS_BOOT_RAMDISK_HIGH
784 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
785 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
788 Enable initrd_high functionality. If defined then the initrd_high
789 feature is enabled and the boot* ramdisk subcommand is enabled.
791 endmenu # Boot images
796 bool "Boot timing and reporting"
798 Enable recording of boot time while booting. To use it, insert
799 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
800 bootstage.h. Only a single entry is recorded for each ID. You can
801 give the entry a name with bootstage_mark_name(). You can also
802 record elapsed time in a particular stage using bootstage_start()
803 before starting and bootstage_accum() when finished. Bootstage will
804 add up all the accumulated time and report it.
806 Normally, IDs are defined in bootstage.h but a small number of
807 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
810 Calls to show_boot_progress() will also result in log entries but
811 these will not have names.
814 bool "Boot timing and reported in SPL"
815 depends on BOOTSTAGE && SPL
817 Enable recording of boot time in SPL. To make this visible to U-Boot
818 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
819 information when SPL finishes and load it when U-Boot proper starts
823 bool "Boot timing and reported in TPL"
824 depends on BOOTSTAGE && TPL
826 Enable recording of boot time in SPL. To make this visible to U-Boot
827 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
828 information when TPL finishes and load it when U-Boot proper starts
831 config BOOTSTAGE_REPORT
832 bool "Display a detailed boot timing report before booting the OS"
835 Enable output of a boot time report just before the OS is booted.
836 This shows how long it took U-Boot to go through each stage of the
837 boot process. The report looks something like this:
839 Timer summary in microseconds:
842 3,575,678 3,575,678 board_init_f start
843 3,575,695 17 arch_cpu_init A9
844 3,575,777 82 arch_cpu_init done
845 3,659,598 83,821 board_init_r start
846 3,910,375 250,777 main_loop
847 29,916,167 26,005,792 bootm_start
848 30,361,327 445,160 start_kernel
850 config BOOTSTAGE_RECORD_COUNT
851 int "Number of boot stage records to store"
855 This is the size of the bootstage record list and is the maximum
856 number of bootstage records that can be recorded.
858 config SPL_BOOTSTAGE_RECORD_COUNT
859 int "Number of boot stage records to store for SPL"
860 depends on SPL_BOOTSTAGE
863 This is the size of the bootstage record list and is the maximum
864 number of bootstage records that can be recorded.
866 config TPL_BOOTSTAGE_RECORD_COUNT
867 int "Number of boot stage records to store for TPL"
868 depends on TPL_BOOTSTAGE
871 This is the size of the bootstage record list and is the maximum
872 number of bootstage records that can be recorded.
875 bool "Store boot timing information in the OS device tree"
878 Stash the bootstage information in the FDT. A root 'bootstage'
879 node is created with each bootstage id as a child. Each child
880 has a 'name' property and either 'mark' containing the
881 mark time in microseconds, or 'accum' containing the
882 accumulated time for that bootstage id in microseconds.
887 name = "board_init_f";
896 Code in the Linux kernel can find this in /proc/devicetree.
898 config BOOTSTAGE_STASH
899 bool "Stash the boot timing information in memory before booting OS"
902 Some OSes do not support device tree. Bootstage can instead write
903 the boot timing information in a binary format at a given address.
904 This happens through a call to bootstage_stash(), typically in
905 the CPU's cleanup_before_linux() function. You can use the
906 'bootstage stash' and 'bootstage unstash' commands to do this on
909 config BOOTSTAGE_STASH_ADDR
910 hex "Address to stash boot timing information"
913 Provide an address which will not be overwritten by the OS when it
914 starts, so that it can read this information when ready.
916 config BOOTSTAGE_STASH_SIZE
917 hex "Size of boot timing stash region"
920 This should be large enough to hold the bootstage stash. A value of
921 4096 (4KiB) is normally plenty.
923 config SHOW_BOOT_PROGRESS
924 bool "Show boot progress in a board-specific manner"
926 Defining this option allows to add some board-specific code (calling
927 a user-provided function show_boot_progress(int) that enables you to
928 show the system's boot progress on some display (for example, some
929 LEDs) on your board. At the moment, the following checkpoints are
932 Legacy uImage format:
935 1 common/cmd_bootm.c before attempting to boot an image
936 -1 common/cmd_bootm.c Image header has bad magic number
937 2 common/cmd_bootm.c Image header has correct magic number
938 -2 common/cmd_bootm.c Image header has bad checksum
939 3 common/cmd_bootm.c Image header has correct checksum
940 -3 common/cmd_bootm.c Image data has bad checksum
941 4 common/cmd_bootm.c Image data has correct checksum
942 -4 common/cmd_bootm.c Image is for unsupported architecture
943 5 common/cmd_bootm.c Architecture check OK
944 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
945 6 common/cmd_bootm.c Image Type check OK
946 -6 common/cmd_bootm.c gunzip uncompression error
947 -7 common/cmd_bootm.c Unimplemented compression type
948 7 common/cmd_bootm.c Uncompression OK
949 8 common/cmd_bootm.c No uncompress/copy overwrite error
950 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
952 9 common/image.c Start initial ramdisk verification
953 -10 common/image.c Ramdisk header has bad magic number
954 -11 common/image.c Ramdisk header has bad checksum
955 10 common/image.c Ramdisk header is OK
956 -12 common/image.c Ramdisk data has bad checksum
957 11 common/image.c Ramdisk data has correct checksum
958 12 common/image.c Ramdisk verification complete, start loading
959 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
960 13 common/image.c Start multifile image verification
961 14 common/image.c No initial ramdisk, no multifile, continue.
963 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
965 -30 arch/powerpc/lib/board.c Fatal error, hang the system
966 -31 post/post.c POST test failed, detected by post_output_backlog()
967 -32 post/post.c POST test failed, detected by post_run_single()
969 34 common/cmd_doc.c before loading a Image from a DOC device
970 -35 common/cmd_doc.c Bad usage of "doc" command
971 35 common/cmd_doc.c correct usage of "doc" command
972 -36 common/cmd_doc.c No boot device
973 36 common/cmd_doc.c correct boot device
974 -37 common/cmd_doc.c Unknown Chip ID on boot device
975 37 common/cmd_doc.c correct chip ID found, device available
976 -38 common/cmd_doc.c Read Error on boot device
977 38 common/cmd_doc.c reading Image header from DOC device OK
978 -39 common/cmd_doc.c Image header has bad magic number
979 39 common/cmd_doc.c Image header has correct magic number
980 -40 common/cmd_doc.c Error reading Image from DOC device
981 40 common/cmd_doc.c Image header has correct magic number
982 41 common/cmd_ide.c before loading a Image from a IDE device
983 -42 common/cmd_ide.c Bad usage of "ide" command
984 42 common/cmd_ide.c correct usage of "ide" command
985 -43 common/cmd_ide.c No boot device
986 43 common/cmd_ide.c boot device found
987 -44 common/cmd_ide.c Device not available
988 44 common/cmd_ide.c Device available
989 -45 common/cmd_ide.c wrong partition selected
990 45 common/cmd_ide.c partition selected
991 -46 common/cmd_ide.c Unknown partition table
992 46 common/cmd_ide.c valid partition table found
993 -47 common/cmd_ide.c Invalid partition type
994 47 common/cmd_ide.c correct partition type
995 -48 common/cmd_ide.c Error reading Image Header on boot device
996 48 common/cmd_ide.c reading Image Header from IDE device OK
997 -49 common/cmd_ide.c Image header has bad magic number
998 49 common/cmd_ide.c Image header has correct magic number
999 -50 common/cmd_ide.c Image header has bad checksum
1000 50 common/cmd_ide.c Image header has correct checksum
1001 -51 common/cmd_ide.c Error reading Image from IDE device
1002 51 common/cmd_ide.c reading Image from IDE device OK
1003 52 common/cmd_nand.c before loading a Image from a NAND device
1004 -53 common/cmd_nand.c Bad usage of "nand" command
1005 53 common/cmd_nand.c correct usage of "nand" command
1006 -54 common/cmd_nand.c No boot device
1007 54 common/cmd_nand.c boot device found
1008 -55 common/cmd_nand.c Unknown Chip ID on boot device
1009 55 common/cmd_nand.c correct chip ID found, device available
1010 -56 common/cmd_nand.c Error reading Image Header on boot device
1011 56 common/cmd_nand.c reading Image Header from NAND device OK
1012 -57 common/cmd_nand.c Image header has bad magic number
1013 57 common/cmd_nand.c Image header has correct magic number
1014 -58 common/cmd_nand.c Error reading Image from NAND device
1015 58 common/cmd_nand.c reading Image from NAND device OK
1017 -60 common/env_common.c Environment has a bad CRC, using default
1019 64 net/eth.c starting with Ethernet configuration.
1020 -64 net/eth.c no Ethernet found.
1021 65 net/eth.c Ethernet found.
1023 -80 common/cmd_net.c usage wrong
1024 80 common/cmd_net.c before calling net_loop()
1025 -81 common/cmd_net.c some error in net_loop() occurred
1026 81 common/cmd_net.c net_loop() back without error
1027 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1028 82 common/cmd_net.c trying automatic boot
1029 83 common/cmd_net.c running "source" command
1030 -83 common/cmd_net.c some error in automatic boot or "source" command
1031 84 common/cmd_net.c end without errors
1036 100 common/cmd_bootm.c Kernel FIT Image has correct format
1037 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1038 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1039 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1040 102 common/cmd_bootm.c Kernel unit name specified
1041 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1042 103 common/cmd_bootm.c Found configuration node
1043 104 common/cmd_bootm.c Got kernel subimage node offset
1044 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1045 105 common/cmd_bootm.c Kernel subimage hash verification OK
1046 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1047 106 common/cmd_bootm.c Architecture check OK
1048 -106 common/cmd_bootm.c Kernel subimage has wrong type
1049 107 common/cmd_bootm.c Kernel subimage type OK
1050 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1051 108 common/cmd_bootm.c Got kernel subimage data/size
1052 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1053 -109 common/cmd_bootm.c Can't get kernel subimage type
1054 -110 common/cmd_bootm.c Can't get kernel subimage comp
1055 -111 common/cmd_bootm.c Can't get kernel subimage os
1056 -112 common/cmd_bootm.c Can't get kernel subimage load address
1057 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1059 120 common/image.c Start initial ramdisk verification
1060 -120 common/image.c Ramdisk FIT image has incorrect format
1061 121 common/image.c Ramdisk FIT image has correct format
1062 122 common/image.c No ramdisk subimage unit name, using configuration
1063 -122 common/image.c Can't get configuration for ramdisk subimage
1064 123 common/image.c Ramdisk unit name specified
1065 -124 common/image.c Can't get ramdisk subimage node offset
1066 125 common/image.c Got ramdisk subimage node offset
1067 -125 common/image.c Ramdisk subimage hash verification failed
1068 126 common/image.c Ramdisk subimage hash verification OK
1069 -126 common/image.c Ramdisk subimage for unsupported architecture
1070 127 common/image.c Architecture check OK
1071 -127 common/image.c Can't get ramdisk subimage data/size
1072 128 common/image.c Got ramdisk subimage data/size
1073 129 common/image.c Can't get ramdisk load address
1074 -129 common/image.c Got ramdisk load address
1076 -130 common/cmd_doc.c Incorrect FIT image format
1077 131 common/cmd_doc.c FIT image format OK
1079 -140 common/cmd_ide.c Incorrect FIT image format
1080 141 common/cmd_ide.c FIT image format OK
1082 -150 common/cmd_nand.c Incorrect FIT image format
1083 151 common/cmd_nand.c FIT image format OK
1085 config SPL_SHOW_BOOT_PROGRESS
1086 bool "Show boot progress in a board-specific manner in SPL"
1089 Defining this option allows to add some board-specific code (calling
1090 a user-provided function show_boot_progress(int) that enables you to
1091 show the system's boot progress on some display (for example, some
1092 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1099 bool "Support for booting from NOR flash"
1102 Enabling this will make a U-Boot binary that is capable of being
1103 booted via NOR. In this case we will enable certain pinmux early
1104 as the ROM only partially sets up pinmux. We also default to using
1105 NOR for environment.
1108 bool "Support for booting from NAND flash"
1111 Enabling this will make a U-Boot binary that is capable of being
1112 booted via NAND flash. This is not a must, some SoCs need this,
1116 bool "Support for booting from ONENAND"
1119 Enabling this will make a U-Boot binary that is capable of being
1120 booted via ONENAND. This is not a must, some SoCs need this,
1124 bool "Support for booting from QSPI flash"
1126 Enabling this will make a U-Boot binary that is capable of being
1127 booted via QSPI flash. This is not a must, some SoCs need this,
1131 bool "Support for booting from SATA"
1133 Enabling this will make a U-Boot binary that is capable of being
1134 booted via SATA. This is not a must, some SoCs need this,
1138 bool "Support for booting from SD/EMMC"
1140 Enabling this will make a U-Boot binary that is capable of being
1141 booted via SD/EMMC. This is not a must, some SoCs need this,
1145 bool "Support for booting from SD/EMMC and enable QSPI"
1147 Enabling this will make a U-Boot binary that is capable of being
1148 booted via SD/EMMC while enabling QSPI on the platform as well. This
1149 is not a must, some SoCs need this, some not.
1152 bool "Support for booting from SPI flash"
1154 Enabling this will make a U-Boot binary that is capable of being
1155 booted via SPI flash. This is not a must, some SoCs need this,
1160 menu "Autoboot options"
1166 This enables the autoboot. See doc/README.autoboot for detail.
1169 int "delay in seconds before automatically booting"
1173 Delay before automatically running bootcmd;
1174 set to 0 to autoboot with no delay, but you can stop it by key input.
1175 set to -1 to disable autoboot.
1176 set to -2 to autoboot with no delay and not check for abort
1178 If this value is >= 0 then it is also used for the default delay
1179 before starting the default entry in bootmenu. If it is < 0 then
1180 a default value of 10s is used.
1182 See doc/README.autoboot for details.
1184 config AUTOBOOT_KEYED
1185 bool "Stop autobooting via specific input key / string"
1187 This option enables stopping (aborting) of the automatic
1188 boot feature only by issuing a specific input key or
1189 string. If not enabled, any input key will abort the
1190 U-Boot automatic booting process and bring the device
1191 to the U-Boot prompt for user input.
1193 config AUTOBOOT_FLUSH_STDIN
1194 bool "Enable flushing stdin before starting to read the password"
1195 depends on AUTOBOOT_KEYED && !SANDBOX
1197 When this option is enabled stdin buffer will be flushed before
1198 starting to read the password.
1199 This can't be enabled for the sandbox as flushing stdin would
1200 break the autoboot unit tests.
1202 config AUTOBOOT_PROMPT
1203 string "Autoboot stop prompt"
1204 depends on AUTOBOOT_KEYED
1205 default "Autoboot in %d seconds\\n"
1207 This string is displayed before the boot delay selected by
1208 CONFIG_BOOTDELAY starts. If it is not defined there is no
1209 output indicating that autoboot is in progress.
1211 Note that this define is used as the (only) argument to a
1212 printf() call, so it may contain '%' format specifications,
1213 provided that it also includes, sepearated by commas exactly
1214 like in a printf statement, the required arguments. It is
1215 the responsibility of the user to select only such arguments
1216 that are valid in the given context.
1218 config AUTOBOOT_ENCRYPTION
1219 bool "Enable encryption in autoboot stopping"
1220 depends on AUTOBOOT_KEYED
1222 This option allows a string to be entered into U-Boot to stop the
1224 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1226 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1227 to the crypt-based functionality and be compared against the
1228 string in the environment variable 'bootstopkeycrypt'.
1229 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1230 and compared against the hash in the environment variable
1231 'bootstopkeysha256'.
1232 If it matches in either case then boot stops and
1233 a command-line prompt is presented.
1234 This provides a way to ship a secure production device which can also
1235 be accessed at the U-Boot command line.
1237 config AUTOBOOT_SHA256_FALLBACK
1238 bool "Allow fallback from crypt-hashed password to sha256"
1239 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1241 This option adds support to fall back from crypt-hashed
1242 passwords to checking a SHA256 hashed password in case the
1243 'bootstopusesha256' environment variable is set to 'true'.
1245 config AUTOBOOT_DELAY_STR
1246 string "Delay autobooting via specific input key / string"
1247 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1249 This option delays the automatic boot feature by issuing
1250 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1251 or the environment variable "bootdelaykey" is specified
1252 and this string is received from console input before
1253 autoboot starts booting, U-Boot gives a command prompt. The
1254 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1255 used, otherwise it never times out.
1257 config AUTOBOOT_STOP_STR
1258 string "Stop autobooting via specific input key / string"
1259 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1261 This option enables stopping (aborting) of the automatic
1262 boot feature only by issuing a specific input key or
1263 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1264 variable "bootstopkey" is specified and this string is
1265 received from console input before autoboot starts booting,
1266 U-Boot gives a command prompt. The U-Boot prompt never
1267 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1269 config AUTOBOOT_KEYED_CTRLC
1270 bool "Enable Ctrl-C autoboot interruption"
1271 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1273 This option allows for the boot sequence to be interrupted
1274 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1275 Setting this variable provides an escape sequence from the
1276 limited "password" strings.
1278 config AUTOBOOT_NEVER_TIMEOUT
1279 bool "Make the password entry never time-out"
1280 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1282 This option removes the timeout from the password entry
1283 when the user first presses the <Enter> key before entering
1284 any other character.
1286 config AUTOBOOT_STOP_STR_ENABLE
1287 bool "Enable fixed string to stop autobooting"
1288 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1290 This option enables the feature to add a fixed stop
1291 string that is defined at compile time.
1292 In every case it will be tried to load the stop
1293 string from the environment.
1294 In case this is enabled and there is no stop string
1295 in the environment, this will be used as default value.
1297 config AUTOBOOT_STOP_STR_CRYPT
1298 string "Stop autobooting via crypt-hashed password"
1299 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1301 This option adds the feature to only stop the autobooting,
1302 and therefore boot into the U-Boot prompt, when the input
1303 string / password matches a values that is hashed via
1304 one of the supported crypt-style password hashing options
1305 and saved in the environment variable "bootstopkeycrypt".
1307 config AUTOBOOT_STOP_STR_SHA256
1308 string "Stop autobooting via SHA256 hashed password"
1309 depends on AUTOBOOT_STOP_STR_ENABLE
1311 This option adds the feature to only stop the autobooting,
1312 and therefore boot into the U-Boot prompt, when the input
1313 string / password matches a values that is encypted via
1314 a SHA256 hash and saved in the environment variable
1315 "bootstopkeysha256". If the value in that variable
1316 includes a ":", the portion prior to the ":" will be treated
1319 config AUTOBOOT_USE_MENUKEY
1320 bool "Allow a specify key to run a menu from the environment"
1321 depends on !AUTOBOOT_KEYED
1323 If a specific key is pressed to stop autoboot, then the commands in
1324 the environment variable 'menucmd' are executed before boot starts.
1326 config AUTOBOOT_MENUKEY
1327 int "ASCII value of boot key to show a menu"
1329 depends on AUTOBOOT_USE_MENUKEY
1331 If this key is pressed to stop autoboot, then the commands in the
1332 environment variable 'menucmd' will be executed before boot starts.
1333 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1336 config AUTOBOOT_MENU_SHOW
1337 bool "Show a menu on boot"
1338 depends on CMD_BOOTMENU
1340 This enables the boot menu, controlled by environment variables
1341 defined by the board. The menu starts after running the 'preboot'
1342 environmnent variable (if enabled) and before handling the boot delay.
1343 See README.bootmenu for more details.
1345 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1346 bool "Disallow bootmenu to enter the U-Boot console"
1347 depends on AUTOBOOT_MENU_SHOW
1349 If this option is enabled, user can not enter the U-Boot console from
1350 bootmenu. It increases the system security.
1353 bool "Boot retry feature"
1355 Allow for having the U-Boot command prompt time out and attempt
1356 to boot again. If the environment variable "bootretry" is found then
1357 its value is used, otherwise the retry timeout is
1358 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1359 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1361 config BOOT_RETRY_TIME
1362 int "Timeout in seconds before attempting to boot again"
1363 depends on BOOT_RETRY
1365 Time in seconds before the U-Boot prompt will timeout and boot will
1368 config BOOT_RETRY_MIN
1369 int "Minimum timeout in seconds for 'bootretry'"
1370 depends on BOOT_RETRY
1371 default BOOT_RETRY_TIME
1373 The minimum time in seconds that "bootretry" can be set to.
1375 config RESET_TO_RETRY
1376 bool "Reset the board to retry autoboot"
1377 depends on BOOT_RETRY
1379 After the countdown timed out, the board will be reset to restart
1384 menu "Image support"
1386 config IMAGE_PRE_LOAD
1387 bool "Image pre-load support"
1389 Enable an image pre-load stage in the SPL.
1390 This pre-load stage allows to do some manipulation
1391 or check (for example signature check) on an image
1392 before launching it.
1394 config SPL_IMAGE_PRE_LOAD
1395 bool "Image pre-load support within SPL"
1396 depends on SPL && IMAGE_PRE_LOAD
1398 Enable an image pre-load stage in the SPL.
1399 This pre-load stage allows to do some manipulation
1400 or check (for example signature check) on an image
1401 before launching it.
1403 config IMAGE_PRE_LOAD_SIG
1404 bool "Image pre-load signature support"
1405 depends on IMAGE_PRE_LOAD
1406 select FIT_SIGNATURE
1408 select RSA_VERIFY_WITH_PKEY
1410 Enable signature check support in the pre-load stage.
1411 For this feature a very simple header is added before
1412 the image with few fields:
1416 All other information (header size, type of signature,
1417 ...) are provided in the node /image/pre-load/sig of
1420 config SPL_IMAGE_PRE_LOAD_SIG
1421 bool "Image pre-load signature support witin SPL"
1422 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1423 select SPL_FIT_SIGNATURE
1425 select SPL_RSA_VERIFY_WITH_PKEY
1427 Enable signature check support in the pre-load stage in the SPL.
1428 For this feature a very simple header is added before
1429 the image with few fields:
1433 All other information (header size, type of signature,
1434 ...) are provided in the node /image/pre-load/sig of
1440 bool "Enable boot arguments"
1442 Provide boot arguments to bootm command. Boot arguments are specified
1443 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1444 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1445 will be undefined and won't take any space in U-Boot image.
1448 string "Boot arguments"
1449 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1451 This can be used to pass arguments to the bootm command. The value of
1452 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1453 this value will also override the "chosen" node in FDT blob.
1455 config BOOTARGS_SUBST
1456 bool "Support substituting strings in boot arguments"
1458 This allows substituting string values in the boot arguments. These
1459 are applied after the commandline has been built.
1461 One use for this is to insert the root-disk UUID into the command
1462 line where bootargs contains "root=${uuid}"
1464 setenv bootargs "console= root=${uuid}"
1465 # Set the 'uuid' environment variable
1466 part uuid mmc 2:2 uuid
1468 # Command-line substitution will put the real uuid into the
1469 # kernel command line
1472 config USE_BOOTCOMMAND
1473 bool "Enable a default value for bootcmd"
1475 Provide a default value for the bootcmd entry in the environment. If
1476 autoboot is enabled this is what will be run automatically. Enable
1477 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1478 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1479 won't take any space in U-Boot image.
1482 string "bootcmd value"
1483 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1484 default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL
1485 default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL
1486 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1488 This is the string of commands that will be used as bootcmd and if
1489 AUTOBOOT is set, automatically run.
1492 bool "Enable preboot"
1494 When this option is enabled, the existence of the environment
1495 variable "preboot" will be checked immediately before starting the
1496 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1497 entering interactive mode.
1499 This feature is especially useful when "preboot" is automatically
1500 generated or modified. For example, the boot code can modify the
1501 "preboot" when a user holds down a certain combination of keys.
1504 string "preboot default value"
1505 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1506 default "usb start" if USB_KEYBOARD
1509 This is the default of "preboot" environment variable.
1511 config PREBOOT_DEFINED
1513 default y if PREBOOT != ""
1515 config DEFAULT_FDT_FILE
1516 string "Default fdt file"
1518 This option is used to set the default fdt file to boot OS.
1520 config SAVE_PREV_BL_FDT_ADDR
1522 bool "Saves fdt address, passed by the previous bootloader, to env var"
1524 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1525 enable this option to save fdt address, passed by the
1526 previous bootloader for future use.
1527 Address is saved to `prevbl_fdt_addr` environment variable.
1529 If no fdt was provided by previous bootloader, no env variables
1532 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1534 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1536 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1537 enable this option to save initramfs address, passed by the
1538 previous bootloader for future use.
1539 Address is saved to `prevbl_initrd_start_addr` environment variable.
1541 If no initramfs was provided by previous bootloader, no env variables