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'
41 config FIT_EXTERNAL_OFFSET
42 hex "FIT external data offset"
45 This specifies a data offset in fit image.
46 The offset is from data payload offset to the beginning of
47 fit image header. When specifies a offset, specific data
48 could be put in the hole between data payload and fit image
49 header, such as CSF data on i.MX platform.
52 bool "Do a full check of the FIT before using it"
55 Enable this do a full check of the FIT to make sure it is valid. This
56 helps to protect against carefully crafted FITs which take advantage
57 of bugs or omissions in the code. This includes a bad structure,
58 multiple root nodes and the like.
61 bool "Enable signature verification of FIT uImages"
66 select IMAGE_SIGN_INFO
69 This option enables signature verification of FIT uImages,
70 using a hash signed and verified using RSA. If
71 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
72 hashing is available using hardware, then the RSA library will use
73 it. See doc/uImage.FIT/signature.txt for more details.
75 WARNING: When relying on signed FIT images with a required signature
76 check the legacy image format is disabled by default, so that
77 unsigned images cannot be loaded. If a board needs the legacy image
78 format support in this case, enable it using
79 CONFIG_LEGACY_IMAGE_FORMAT.
81 config FIT_SIGNATURE_MAX_SIZE
82 hex "Max size of signed FIT structures"
83 depends on FIT_SIGNATURE
86 This option sets a max size in bytes for verified FIT uImages.
87 A sane value of 256MB protects corrupted DTB structures from overlapping
88 device memory. Assure this size does not extend past expected storage
92 bool "Support rsassa-pss signature scheme of FIT image contents"
93 depends on FIT_SIGNATURE
95 Enable this to support the pss padding algorithm as described
96 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
99 bool "Enable ciphering data in a FIT uImages"
103 Enable the feature of data ciphering/unciphering in the tool mkimage
104 and in the u-boot support of the FIT image.
107 bool "Show verbose messages when FIT images fail"
109 Generally a system will have valid FIT images so debug messages
110 are a waste of code space. If you are debugging your images then
111 you can enable this option to get more verbose information about
114 config FIT_BEST_MATCH
115 bool "Select the best match for the kernel device tree"
117 When no configuration is explicitly selected, default to the
118 one whose fdt's compatibility field best matches that of
119 U-Boot itself. A match is considered "best" if it matches the
120 most specific compatibility entry of U-Boot's fdt's root node.
121 The order of entries in the configuration's fdt is ignored.
123 config FIT_IMAGE_POST_PROCESS
124 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
125 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
126 default y if TI_SECURE_DEVICE
128 Allows doing any sort of manipulation to blobs after they got extracted
129 from FIT images like stripping off headers or modifying the size of the
130 blob, verification, authentication, decryption etc. in a platform or
131 board specific way. In order to use this feature a platform or board-
132 specific implementation of board_fit_image_post_process() must be
133 provided. Also, anything done during this post-processing step would
134 need to be comprehended in how the images were prepared before being
135 injected into the FIT creation (i.e. the blobs would have been pre-
136 processed before being added to the FIT image).
139 bool "Support FIT printing"
142 Support printing the content of the fitImage in a verbose manner.
147 bool "Support Flattened Image Tree within SPL"
153 bool "Support FIT printing within SPL"
156 Support printing the content of the fitImage in a verbose manner in SPL.
158 config SPL_FIT_FULL_CHECK
159 bool "Do a full check of the FIT before using it"
161 Enable this do a full check of the FIT to make sure it is valid. This
162 helps to protect against carefully crafted FITs which take advantage
163 of bugs or omissions in the code. This includes a bad structure,
164 multiple root nodes and the like.
167 config SPL_FIT_SIGNATURE
168 bool "Enable signature verification of FIT firmware within SPL"
170 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
177 select SPL_IMAGE_SIGN_INFO
178 select SPL_FIT_FULL_CHECK
180 config SPL_FIT_SIGNATURE_MAX_SIZE
181 hex "Max size of signed FIT structures in SPL"
182 depends on SPL_FIT_SIGNATURE
185 This option sets a max size in bytes for verified FIT uImages.
186 A sane value of 256MB protects corrupted DTB structures from overlapping
187 device memory. Assure this size does not extend past expected storage
190 config SPL_FIT_RSASSA_PSS
191 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
192 depends on SPL_FIT_SIGNATURE
194 Enable this to support the pss padding algorithm as described
195 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
198 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
201 Normally with the SPL framework a legacy image is generated as part
202 of the build. This contains U-Boot along with information as to
203 where it should be loaded. This option instead enables generation
204 of a FIT (Flat Image Tree) which provides more flexibility. In
205 particular it can handle selecting from multiple device tree
206 and passing the correct one to U-Boot.
208 This path has the following limitations:
210 1. "loadables" images, other than FDTs, which do not have a "load"
211 property will not be loaded. This limitation also applies to FPGA
212 images with the correct "compatible" string.
213 2. For FPGA images, the supported "compatible" list is in the
214 doc/uImage.FIT/source_file_format.txt.
215 3. FDTs are only loaded for images with an "os" property of "u-boot".
216 "linux" images are also supported with Falcon boot mode.
218 config SPL_LOAD_FIT_ADDRESS
219 hex "load address of fit image"
220 depends on SPL_LOAD_FIT
223 Specify the load address of the fit image that will be loaded
226 config SPL_LOAD_FIT_APPLY_OVERLAY
227 bool "Enable SPL applying DT overlays from FIT"
228 depends on SPL_LOAD_FIT
229 select OF_LIBFDT_OVERLAY
231 The device tree is loaded from the FIT image. Allow the SPL is to
232 also load device-tree overlays from the FIT image an apply them
233 over the device tree.
235 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
236 depends on SPL_LOAD_FIT_APPLY_OVERLAY
238 hex "size of temporary buffer used to load the overlays"
240 The size of the area where the overlays will be loaded and
241 uncompress. Must be at least as large as biggest overlay
244 config SPL_LOAD_FIT_FULL
245 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
248 Normally with the SPL framework a legacy image is generated as part
249 of the build. This contains U-Boot along with information as to
250 where it should be loaded. This option instead enables generation
251 of a FIT (Flat Image Tree) which provides more flexibility. In
252 particular it can handle selecting from multiple device tree
253 and passing the correct one to U-Boot.
255 config SPL_FIT_IMAGE_POST_PROCESS
256 bool "Enable post-processing of FIT artifacts after loading by the SPL"
257 depends on SPL_LOAD_FIT
258 default y if TI_SECURE_DEVICE
260 Allows doing any sort of manipulation to blobs after they got extracted
261 from the U-Boot FIT image like stripping off headers or modifying the
262 size of the blob, verification, authentication, decryption etc. in a
263 platform or board specific way. In order to use this feature a platform
264 or board-specific implementation of board_fit_image_post_process() must
265 be provided. Also, anything done during this post-processing step would
266 need to be comprehended in how the images were prepared before being
267 injected into the FIT creation (i.e. the blobs would have been pre-
268 processed before being added to the FIT image).
270 config SPL_FIT_SOURCE
271 string ".its source file for U-Boot FIT image"
274 Specifies a (platform specific) FIT source file to generate the
275 U-Boot FIT image. This could specify further image to load and/or
278 config USE_SPL_FIT_GENERATOR
279 bool "Use a script to generate the .its script"
280 default y if SPL_FIT && (!ARCH_SUNXI && !RISCV)
282 config SPL_FIT_GENERATOR
283 string ".its file generator script for U-Boot FIT image"
284 depends on USE_SPL_FIT_GENERATOR
285 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
286 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
288 Specifies a (platform specific) script file to generate the FIT
289 source file used to build the U-Boot FIT image file. This gets
290 passed a list of supported device tree file stub names to
291 include in the generated image.
298 bool "Support Flattened Image Tree within VPL"
305 bool "Support FIT printing within VPL"
309 Support printing the content of the fitImage in a verbose manner in VPL.
311 config VPL_FIT_FULL_CHECK
312 bool "Do a full check of the FIT before using it"
315 Enable this do a full check of the FIT to make sure it is valid. This
316 helps to protect against carefully crafted FITs which take advantage
317 of bugs or omissions in the code. This includes a bad structure,
318 multiple root nodes and the like.
320 config VPL_FIT_SIGNATURE
321 bool "Enable signature verification of FIT firmware within VPL"
323 depends on VPL_LOAD_FIT || VPL_LOAD_FIT_FULL
331 select VPL_IMAGE_SIGN_INFO
332 select VPL_FIT_FULL_CHECK
334 config VPL_FIT_SIGNATURE_MAX_SIZE
335 hex "Max size of signed FIT structures in VPL"
336 depends on VPL_FIT_SIGNATURE
339 This option sets a max size in bytes for verified FIT uImages.
340 A sane value of 256MB protects corrupted DTB structures from overlapping
341 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
560 config BOOTMETH_SANDBOX
564 This is a sandbox bootmeth driver used for testing. It always returns
565 -ENOTSUPP when attempting to boot.
567 config BOOTMETH_SCRIPT
568 bool "Bootdev support for U-Boot scripts"
569 default y if BOOTSTD_FULL
571 Enables support for booting a distro via a U-Boot script. This makes
572 the bootdevs look for a 'boot/boot.scr' file which can be used to
575 This provides a way to try out standard boot on an existing boot flow.
576 It is not enabled by default to save space.
580 config LEGACY_IMAGE_FORMAT
581 bool "Enable support for the legacy image format"
582 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
584 This option enables the legacy image format. It is enabled by
585 default for backward compatibility, unless FIT_SIGNATURE is
586 set where it is disabled so that unsigned images cannot be
587 loaded. If a board needs the legacy image format support in this
588 case, enable it here.
590 config SUPPORT_RAW_INITRD
591 bool "Enable raw initrd images"
593 Note, defining the SUPPORT_RAW_INITRD allows user to supply
594 kernel with raw initrd images. The syntax is slightly different, the
595 address of the initrd must be augmented by it's size, in the following
596 format: "<initrd address>:<initrd size>".
598 config OF_BOARD_SETUP
599 bool "Set up board-specific details in device tree before boot"
602 This causes U-Boot to call ft_board_setup() before booting into
603 the Operating System. This function can set up various
604 board-specific information in the device tree for use by the OS.
605 The device tree is then passed to the OS.
607 config OF_SYSTEM_SETUP
608 bool "Set up system-specific details in device tree before boot"
611 This causes U-Boot to call ft_system_setup() before booting into
612 the Operating System. This function can set up various
613 system-specific information in the device tree for use by the OS.
614 The device tree is then passed to the OS.
616 config OF_STDOUT_VIA_ALIAS
617 bool "Update the device-tree stdout alias from U-Boot"
620 This uses U-Boot's serial alias from the aliases node to update
621 the device tree passed to the OS. The "linux,stdout-path" property
622 in the chosen node is set to point to the correct serial node.
623 This option currently references CONFIG_CONS_INDEX, which is
624 incorrect when used with device tree as this option does not
625 exist / should not be used.
627 config HAVE_TEXT_BASE
629 depends on !NIOS2 && !XTENSA
634 depends on HAVE_TEXT_BASE
635 default 0x0 if POSITION_INDEPENDENT
636 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
637 default 0x81700000 if MACH_SUNIV
638 default 0x2a000000 if MACH_SUN9I
639 default 0x4a000000 if SUNXI_MINIMUM_DRAM_MB >= 256
640 default 0x42e00000 if SUNXI_MINIMUM_DRAM_MB >= 64
643 The address in memory that U-Boot will be running from, initially.
645 config HAVE_SYS_MONITOR_BASE
647 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
648 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
652 config SYS_MONITOR_BASE
653 depends on HAVE_SYS_MONITOR_BASE
654 hex "Physical start address of boot monitor code"
657 The physical start address of boot monitor code (which is the same as
658 CONFIG_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
659 when booting from flash.
661 config SPL_SYS_MONITOR_BASE
662 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
663 hex "Physical start address of SPL monitor code"
664 default SPL_TEXT_BASE
666 config TPL_SYS_MONITOR_BASE
667 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
668 hex "Physical start address of TPL monitor code"
670 config DYNAMIC_SYS_CLK_FREQ
671 bool "Determine CPU clock frequency at run-time"
673 Implement a get_board_sys_clk function that will determine the CPU
674 clock frequency at run time, rather than define it statically.
677 depends on !DYNAMIC_SYS_CLK_FREQ
678 int "CPU clock frequency"
679 default 125000000 if ARCH_LS1012A
680 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
681 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
682 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
683 default 66660000 if ARCH_T2080
684 default 33333333 if RCAR_GEN3
685 default 24000000 if ARCH_EXYNOS
686 default 20000000 if RCAR_GEN2
689 A static value for the CPU frequency. Note that if not required
690 for a given SoC, this can be left at 0.
692 config ARCH_FIXUP_FDT_MEMORY
693 bool "Enable arch_fixup_memory_banks() call"
696 Enable FDT memory map syncup before OS boot. This feature can be
697 used for booting OS with different memory setup where the part of
698 the memory location should be used for different purpose.
701 bool "Support booting Chrome OS"
703 Chrome OS requires U-Boot to set up a table indicating the boot mode
704 (e.g. Developer mode) and a few other things. Enable this if you are
705 booting on a Chromebook to avoid getting an error about an invalid
708 config CHROMEOS_VBOOT
709 bool "Support Chrome OS verified boot"
711 This is intended to enable the full Chrome OS verified boot support
712 in U-Boot. It is not actually implemented in the U-Boot source code
713 at present, so this option is always set to 'n'. It allows
714 distinguishing between booting Chrome OS in a basic way (developer
715 mode) and a full boot.
721 bool "Freescale PBL(pre-boot loader) image format support"
722 select SYS_RAMBOOT if PPC
724 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
725 For more details refer to doc/README.pblimage
728 prompt "Freescale PBL load location"
729 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
730 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
734 bool "Freescale PBL is found on SD card"
737 bool "Freescale PBL is found on SPI flash"
741 config FSL_FIXED_MMC_LOCATION
742 bool "PBL MMC is at a fixed location"
743 depends on SDCARD && !RAMBOOT_PBL
745 config ESDHC_HC_BLK_ADDR
747 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
749 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
750 code length of these soc specify the memory address in block address
751 format. Block length is fixed to 512 bytes as per the SD High
752 Capacity specification.
754 config SYS_FSL_PBL_PBI
755 string "PBI(pre-boot instructions) commands for the PBL image"
756 depends on RAMBOOT_PBL
758 PBI commands can be used to configure SoC before it starts the execution.
759 Please refer doc/README.pblimage for more details.
761 config SYS_FSL_PBL_RCW
762 string "Aadditional RCW (Power on reset configuration) for the PBL image"
763 depends on RAMBOOT_PBL
765 Enables addition of RCW (Power on reset configuration) in built image.
766 Please refer doc/README.pblimage for more details.
768 config SYS_BOOT_RAMDISK_HIGH
769 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
770 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
773 Enable initrd_high functionality. If defined then the initrd_high
774 feature is enabled and the boot* ramdisk subcommand is enabled.
776 endmenu # Boot images
781 bool "Boot timing and reporting"
783 Enable recording of boot time while booting. To use it, insert
784 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
785 bootstage.h. Only a single entry is recorded for each ID. You can
786 give the entry a name with bootstage_mark_name(). You can also
787 record elapsed time in a particular stage using bootstage_start()
788 before starting and bootstage_accum() when finished. Bootstage will
789 add up all the accumulated time and report it.
791 Normally, IDs are defined in bootstage.h but a small number of
792 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
795 Calls to show_boot_progress() will also result in log entries but
796 these will not have names.
799 bool "Boot timing and reported in SPL"
800 depends on BOOTSTAGE && SPL
802 Enable recording of boot time in SPL. To make this visible to U-Boot
803 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
804 information when SPL finishes and load it when U-Boot proper starts
808 bool "Boot timing and reported in TPL"
809 depends on BOOTSTAGE && TPL
811 Enable recording of boot time in SPL. To make this visible to U-Boot
812 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
813 information when TPL finishes and load it when U-Boot proper starts
816 config BOOTSTAGE_REPORT
817 bool "Display a detailed boot timing report before booting the OS"
820 Enable output of a boot time report just before the OS is booted.
821 This shows how long it took U-Boot to go through each stage of the
822 boot process. The report looks something like this:
824 Timer summary in microseconds:
827 3,575,678 3,575,678 board_init_f start
828 3,575,695 17 arch_cpu_init A9
829 3,575,777 82 arch_cpu_init done
830 3,659,598 83,821 board_init_r start
831 3,910,375 250,777 main_loop
832 29,916,167 26,005,792 bootm_start
833 30,361,327 445,160 start_kernel
835 config BOOTSTAGE_RECORD_COUNT
836 int "Number of boot stage records to store"
840 This is the size of the bootstage record list and is the maximum
841 number of bootstage records that can be recorded.
843 config SPL_BOOTSTAGE_RECORD_COUNT
844 int "Number of boot stage records to store for SPL"
845 depends on SPL_BOOTSTAGE
848 This is the size of the bootstage record list and is the maximum
849 number of bootstage records that can be recorded.
851 config TPL_BOOTSTAGE_RECORD_COUNT
852 int "Number of boot stage records to store for TPL"
853 depends on TPL_BOOTSTAGE
856 This is the size of the bootstage record list and is the maximum
857 number of bootstage records that can be recorded.
860 bool "Store boot timing information in the OS device tree"
863 Stash the bootstage information in the FDT. A root 'bootstage'
864 node is created with each bootstage id as a child. Each child
865 has a 'name' property and either 'mark' containing the
866 mark time in microseconds, or 'accum' containing the
867 accumulated time for that bootstage id in microseconds.
872 name = "board_init_f";
881 Code in the Linux kernel can find this in /proc/devicetree.
883 config BOOTSTAGE_STASH
884 bool "Stash the boot timing information in memory before booting OS"
887 Some OSes do not support device tree. Bootstage can instead write
888 the boot timing information in a binary format at a given address.
889 This happens through a call to bootstage_stash(), typically in
890 the CPU's cleanup_before_linux() function. You can use the
891 'bootstage stash' and 'bootstage unstash' commands to do this on
894 config BOOTSTAGE_STASH_ADDR
895 hex "Address to stash boot timing information"
898 Provide an address which will not be overwritten by the OS when it
899 starts, so that it can read this information when ready.
901 config BOOTSTAGE_STASH_SIZE
902 hex "Size of boot timing stash region"
905 This should be large enough to hold the bootstage stash. A value of
906 4096 (4KiB) is normally plenty.
908 config SHOW_BOOT_PROGRESS
909 bool "Show boot progress in a board-specific manner"
911 Defining this option allows to add some board-specific code (calling
912 a user-provided function show_boot_progress(int) that enables you to
913 show the system's boot progress on some display (for example, some
914 LEDs) on your board. At the moment, the following checkpoints are
917 Legacy uImage format:
920 1 common/cmd_bootm.c before attempting to boot an image
921 -1 common/cmd_bootm.c Image header has bad magic number
922 2 common/cmd_bootm.c Image header has correct magic number
923 -2 common/cmd_bootm.c Image header has bad checksum
924 3 common/cmd_bootm.c Image header has correct checksum
925 -3 common/cmd_bootm.c Image data has bad checksum
926 4 common/cmd_bootm.c Image data has correct checksum
927 -4 common/cmd_bootm.c Image is for unsupported architecture
928 5 common/cmd_bootm.c Architecture check OK
929 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
930 6 common/cmd_bootm.c Image Type check OK
931 -6 common/cmd_bootm.c gunzip uncompression error
932 -7 common/cmd_bootm.c Unimplemented compression type
933 7 common/cmd_bootm.c Uncompression OK
934 8 common/cmd_bootm.c No uncompress/copy overwrite error
935 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
937 9 common/image.c Start initial ramdisk verification
938 -10 common/image.c Ramdisk header has bad magic number
939 -11 common/image.c Ramdisk header has bad checksum
940 10 common/image.c Ramdisk header is OK
941 -12 common/image.c Ramdisk data has bad checksum
942 11 common/image.c Ramdisk data has correct checksum
943 12 common/image.c Ramdisk verification complete, start loading
944 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
945 13 common/image.c Start multifile image verification
946 14 common/image.c No initial ramdisk, no multifile, continue.
948 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
950 -30 arch/powerpc/lib/board.c Fatal error, hang the system
951 -31 post/post.c POST test failed, detected by post_output_backlog()
952 -32 post/post.c POST test failed, detected by post_run_single()
954 34 common/cmd_doc.c before loading a Image from a DOC device
955 -35 common/cmd_doc.c Bad usage of "doc" command
956 35 common/cmd_doc.c correct usage of "doc" command
957 -36 common/cmd_doc.c No boot device
958 36 common/cmd_doc.c correct boot device
959 -37 common/cmd_doc.c Unknown Chip ID on boot device
960 37 common/cmd_doc.c correct chip ID found, device available
961 -38 common/cmd_doc.c Read Error on boot device
962 38 common/cmd_doc.c reading Image header from DOC device OK
963 -39 common/cmd_doc.c Image header has bad magic number
964 39 common/cmd_doc.c Image header has correct magic number
965 -40 common/cmd_doc.c Error reading Image from DOC device
966 40 common/cmd_doc.c Image header has correct magic number
967 41 common/cmd_ide.c before loading a Image from a IDE device
968 -42 common/cmd_ide.c Bad usage of "ide" command
969 42 common/cmd_ide.c correct usage of "ide" command
970 -43 common/cmd_ide.c No boot device
971 43 common/cmd_ide.c boot device found
972 -44 common/cmd_ide.c Device not available
973 44 common/cmd_ide.c Device available
974 -45 common/cmd_ide.c wrong partition selected
975 45 common/cmd_ide.c partition selected
976 -46 common/cmd_ide.c Unknown partition table
977 46 common/cmd_ide.c valid partition table found
978 -47 common/cmd_ide.c Invalid partition type
979 47 common/cmd_ide.c correct partition type
980 -48 common/cmd_ide.c Error reading Image Header on boot device
981 48 common/cmd_ide.c reading Image Header from IDE device OK
982 -49 common/cmd_ide.c Image header has bad magic number
983 49 common/cmd_ide.c Image header has correct magic number
984 -50 common/cmd_ide.c Image header has bad checksum
985 50 common/cmd_ide.c Image header has correct checksum
986 -51 common/cmd_ide.c Error reading Image from IDE device
987 51 common/cmd_ide.c reading Image from IDE device OK
988 52 common/cmd_nand.c before loading a Image from a NAND device
989 -53 common/cmd_nand.c Bad usage of "nand" command
990 53 common/cmd_nand.c correct usage of "nand" command
991 -54 common/cmd_nand.c No boot device
992 54 common/cmd_nand.c boot device found
993 -55 common/cmd_nand.c Unknown Chip ID on boot device
994 55 common/cmd_nand.c correct chip ID found, device available
995 -56 common/cmd_nand.c Error reading Image Header on boot device
996 56 common/cmd_nand.c reading Image Header from NAND device OK
997 -57 common/cmd_nand.c Image header has bad magic number
998 57 common/cmd_nand.c Image header has correct magic number
999 -58 common/cmd_nand.c Error reading Image from NAND device
1000 58 common/cmd_nand.c reading Image from NAND device OK
1002 -60 common/env_common.c Environment has a bad CRC, using default
1004 64 net/eth.c starting with Ethernet configuration.
1005 -64 net/eth.c no Ethernet found.
1006 65 net/eth.c Ethernet found.
1008 -80 common/cmd_net.c usage wrong
1009 80 common/cmd_net.c before calling net_loop()
1010 -81 common/cmd_net.c some error in net_loop() occurred
1011 81 common/cmd_net.c net_loop() back without error
1012 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1013 82 common/cmd_net.c trying automatic boot
1014 83 common/cmd_net.c running "source" command
1015 -83 common/cmd_net.c some error in automatic boot or "source" command
1016 84 common/cmd_net.c end without errors
1021 100 common/cmd_bootm.c Kernel FIT Image has correct format
1022 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1023 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1024 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1025 102 common/cmd_bootm.c Kernel unit name specified
1026 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1027 103 common/cmd_bootm.c Found configuration node
1028 104 common/cmd_bootm.c Got kernel subimage node offset
1029 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1030 105 common/cmd_bootm.c Kernel subimage hash verification OK
1031 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1032 106 common/cmd_bootm.c Architecture check OK
1033 -106 common/cmd_bootm.c Kernel subimage has wrong type
1034 107 common/cmd_bootm.c Kernel subimage type OK
1035 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1036 108 common/cmd_bootm.c Got kernel subimage data/size
1037 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1038 -109 common/cmd_bootm.c Can't get kernel subimage type
1039 -110 common/cmd_bootm.c Can't get kernel subimage comp
1040 -111 common/cmd_bootm.c Can't get kernel subimage os
1041 -112 common/cmd_bootm.c Can't get kernel subimage load address
1042 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1044 120 common/image.c Start initial ramdisk verification
1045 -120 common/image.c Ramdisk FIT image has incorrect format
1046 121 common/image.c Ramdisk FIT image has correct format
1047 122 common/image.c No ramdisk subimage unit name, using configuration
1048 -122 common/image.c Can't get configuration for ramdisk subimage
1049 123 common/image.c Ramdisk unit name specified
1050 -124 common/image.c Can't get ramdisk subimage node offset
1051 125 common/image.c Got ramdisk subimage node offset
1052 -125 common/image.c Ramdisk subimage hash verification failed
1053 126 common/image.c Ramdisk subimage hash verification OK
1054 -126 common/image.c Ramdisk subimage for unsupported architecture
1055 127 common/image.c Architecture check OK
1056 -127 common/image.c Can't get ramdisk subimage data/size
1057 128 common/image.c Got ramdisk subimage data/size
1058 129 common/image.c Can't get ramdisk load address
1059 -129 common/image.c Got ramdisk load address
1061 -130 common/cmd_doc.c Incorrect FIT image format
1062 131 common/cmd_doc.c FIT image format OK
1064 -140 common/cmd_ide.c Incorrect FIT image format
1065 141 common/cmd_ide.c FIT image format OK
1067 -150 common/cmd_nand.c Incorrect FIT image format
1068 151 common/cmd_nand.c FIT image format OK
1070 config SPL_SHOW_BOOT_PROGRESS
1071 bool "Show boot progress in a board-specific manner in SPL"
1074 Defining this option allows to add some board-specific code (calling
1075 a user-provided function show_boot_progress(int) that enables you to
1076 show the system's boot progress on some display (for example, some
1077 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1084 bool "Support for booting from NOR flash"
1087 Enabling this will make a U-Boot binary that is capable of being
1088 booted via NOR. In this case we will enable certain pinmux early
1089 as the ROM only partially sets up pinmux. We also default to using
1090 NOR for environment.
1093 bool "Support for booting from NAND flash"
1096 Enabling this will make a U-Boot binary that is capable of being
1097 booted via NAND flash. This is not a must, some SoCs need this,
1101 bool "Support for booting from ONENAND"
1104 Enabling this will make a U-Boot binary that is capable of being
1105 booted via ONENAND. This is not a must, some SoCs need this,
1109 bool "Support for booting from QSPI flash"
1111 Enabling this will make a U-Boot binary that is capable of being
1112 booted via QSPI flash. This is not a must, some SoCs need this,
1116 bool "Support for booting from SATA"
1118 Enabling this will make a U-Boot binary that is capable of being
1119 booted via SATA. This is not a must, some SoCs need this,
1123 bool "Support for booting from SD/EMMC"
1125 Enabling this will make a U-Boot binary that is capable of being
1126 booted via SD/EMMC. This is not a must, some SoCs need this,
1130 bool "Support for booting from SD/EMMC and enable QSPI"
1132 Enabling this will make a U-Boot binary that is capable of being
1133 booted via SD/EMMC while enabling QSPI on the platform as well. This
1134 is not a must, some SoCs need this, some not.
1137 bool "Support for booting from SPI flash"
1139 Enabling this will make a U-Boot binary that is capable of being
1140 booted via SPI flash. This is not a must, some SoCs need this,
1145 menu "Autoboot options"
1151 This enables the autoboot. See doc/README.autoboot for detail.
1154 int "delay in seconds before automatically booting"
1158 Delay before automatically running bootcmd;
1159 set to 0 to autoboot with no delay, but you can stop it by key input.
1160 set to -1 to disable autoboot.
1161 set to -2 to autoboot with no delay and not check for abort
1163 If this value is >= 0 then it is also used for the default delay
1164 before starting the default entry in bootmenu. If it is < 0 then
1165 a default value of 10s is used.
1167 See doc/README.autoboot for details.
1169 config AUTOBOOT_KEYED
1170 bool "Stop autobooting via specific input key / string"
1172 This option enables stopping (aborting) of the automatic
1173 boot feature only by issuing a specific input key or
1174 string. If not enabled, any input key will abort the
1175 U-Boot automatic booting process and bring the device
1176 to the U-Boot prompt for user input.
1178 config AUTOBOOT_FLUSH_STDIN
1179 bool "Enable flushing stdin before starting to read the password"
1180 depends on AUTOBOOT_KEYED && !SANDBOX
1182 When this option is enabled stdin buffer will be flushed before
1183 starting to read the password.
1184 This can't be enabled for the sandbox as flushing stdin would
1185 break the autoboot unit tests.
1187 config AUTOBOOT_PROMPT
1188 string "Autoboot stop prompt"
1189 depends on AUTOBOOT_KEYED
1190 default "Autoboot in %d seconds\\n"
1192 This string is displayed before the boot delay selected by
1193 CONFIG_BOOTDELAY starts. If it is not defined there is no
1194 output indicating that autoboot is in progress.
1196 Note that this define is used as the (only) argument to a
1197 printf() call, so it may contain '%' format specifications,
1198 provided that it also includes, sepearated by commas exactly
1199 like in a printf statement, the required arguments. It is
1200 the responsibility of the user to select only such arguments
1201 that are valid in the given context.
1203 config AUTOBOOT_ENCRYPTION
1204 bool "Enable encryption in autoboot stopping"
1205 depends on AUTOBOOT_KEYED
1207 This option allows a string to be entered into U-Boot to stop the
1209 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1211 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1212 to the crypt-based functionality and be compared against the
1213 string in the environment variable 'bootstopkeycrypt'.
1214 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1215 and compared against the hash in the environment variable
1216 'bootstopkeysha256'.
1217 If it matches in either case then boot stops and
1218 a command-line prompt is presented.
1219 This provides a way to ship a secure production device which can also
1220 be accessed at the U-Boot command line.
1222 config AUTOBOOT_SHA256_FALLBACK
1223 bool "Allow fallback from crypt-hashed password to sha256"
1224 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1226 This option adds support to fall back from crypt-hashed
1227 passwords to checking a SHA256 hashed password in case the
1228 'bootstopusesha256' environment variable is set to 'true'.
1230 config AUTOBOOT_DELAY_STR
1231 string "Delay autobooting via specific input key / string"
1232 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1234 This option delays the automatic boot feature by issuing
1235 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1236 or the environment variable "bootdelaykey" is specified
1237 and this string is received from console input before
1238 autoboot starts booting, U-Boot gives a command prompt. The
1239 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1240 used, otherwise it never times out.
1242 config AUTOBOOT_STOP_STR
1243 string "Stop autobooting via specific input key / string"
1244 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1246 This option enables stopping (aborting) of the automatic
1247 boot feature only by issuing a specific input key or
1248 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1249 variable "bootstopkey" is specified and this string is
1250 received from console input before autoboot starts booting,
1251 U-Boot gives a command prompt. The U-Boot prompt never
1252 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1254 config AUTOBOOT_KEYED_CTRLC
1255 bool "Enable Ctrl-C autoboot interruption"
1256 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1258 This option allows for the boot sequence to be interrupted
1259 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1260 Setting this variable provides an escape sequence from the
1261 limited "password" strings.
1263 config AUTOBOOT_NEVER_TIMEOUT
1264 bool "Make the password entry never time-out"
1265 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1267 This option removes the timeout from the password entry
1268 when the user first presses the <Enter> key before entering
1269 any other character.
1271 config AUTOBOOT_STOP_STR_ENABLE
1272 bool "Enable fixed string to stop autobooting"
1273 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1275 This option enables the feature to add a fixed stop
1276 string that is defined at compile time.
1277 In every case it will be tried to load the stop
1278 string from the environment.
1279 In case this is enabled and there is no stop string
1280 in the environment, this will be used as default value.
1282 config AUTOBOOT_STOP_STR_CRYPT
1283 string "Stop autobooting via crypt-hashed password"
1284 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1286 This option adds the feature to only stop the autobooting,
1287 and therefore boot into the U-Boot prompt, when the input
1288 string / password matches a values that is hashed via
1289 one of the supported crypt-style password hashing options
1290 and saved in the environment variable "bootstopkeycrypt".
1292 config AUTOBOOT_STOP_STR_SHA256
1293 string "Stop autobooting via SHA256 hashed password"
1294 depends on AUTOBOOT_STOP_STR_ENABLE
1296 This option adds the feature to only stop the autobooting,
1297 and therefore boot into the U-Boot prompt, when the input
1298 string / password matches a values that is encypted via
1299 a SHA256 hash and saved in the environment variable
1300 "bootstopkeysha256". If the value in that variable
1301 includes a ":", the portion prior to the ":" will be treated
1304 config AUTOBOOT_USE_MENUKEY
1305 bool "Allow a specify key to run a menu from the environment"
1306 depends on !AUTOBOOT_KEYED
1308 If a specific key is pressed to stop autoboot, then the commands in
1309 the environment variable 'menucmd' are executed before boot starts.
1311 config AUTOBOOT_MENUKEY
1312 int "ASCII value of boot key to show a menu"
1314 depends on AUTOBOOT_USE_MENUKEY
1316 If this key is pressed to stop autoboot, then the commands in the
1317 environment variable 'menucmd' will be executed before boot starts.
1318 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1321 config AUTOBOOT_MENU_SHOW
1322 bool "Show a menu on boot"
1323 depends on CMD_BOOTMENU
1325 This enables the boot menu, controlled by environment variables
1326 defined by the board. The menu starts after running the 'preboot'
1327 environmnent variable (if enabled) and before handling the boot delay.
1328 See README.bootmenu for more details.
1330 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1331 bool "Disallow bootmenu to enter the U-Boot console"
1332 depends on AUTOBOOT_MENU_SHOW
1334 If this option is enabled, user can not enter the U-Boot console from
1335 bootmenu. It increases the system security.
1338 bool "Boot retry feature"
1340 Allow for having the U-Boot command prompt time out and attempt
1341 to boot again. If the environment variable "bootretry" is found then
1342 its value is used, otherwise the retry timeout is
1343 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1344 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1346 config BOOT_RETRY_TIME
1347 int "Timeout in seconds before attempting to boot again"
1348 depends on BOOT_RETRY
1350 Time in seconds before the U-Boot prompt will timeout and boot will
1353 config BOOT_RETRY_MIN
1354 int "Minimum timeout in seconds for 'bootretry'"
1355 depends on BOOT_RETRY
1356 default BOOT_RETRY_TIME
1358 The minimum time in seconds that "bootretry" can be set to.
1360 config RESET_TO_RETRY
1361 bool "Reset the board to retry autoboot"
1362 depends on BOOT_RETRY
1364 After the countdown timed out, the board will be reset to restart
1369 menu "Image support"
1371 config IMAGE_PRE_LOAD
1372 bool "Image pre-load support"
1374 Enable an image pre-load stage in the SPL.
1375 This pre-load stage allows to do some manipulation
1376 or check (for example signature check) on an image
1377 before launching it.
1379 config SPL_IMAGE_PRE_LOAD
1380 bool "Image pre-load support within SPL"
1381 depends on SPL && IMAGE_PRE_LOAD
1383 Enable an image pre-load stage in the SPL.
1384 This pre-load stage allows to do some manipulation
1385 or check (for example signature check) on an image
1386 before launching it.
1388 config IMAGE_PRE_LOAD_SIG
1389 bool "Image pre-load signature support"
1390 depends on IMAGE_PRE_LOAD
1391 select FIT_SIGNATURE
1393 select RSA_VERIFY_WITH_PKEY
1395 Enable signature check support in the pre-load stage.
1396 For this feature a very simple header is added before
1397 the image with few fields:
1401 All other information (header size, type of signature,
1402 ...) are provided in the node /image/pre-load/sig of
1405 config SPL_IMAGE_PRE_LOAD_SIG
1406 bool "Image pre-load signature support witin SPL"
1407 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1408 select SPL_FIT_SIGNATURE
1410 select SPL_RSA_VERIFY_WITH_PKEY
1412 Enable signature check support in the pre-load stage in the SPL.
1413 For this feature a very simple header is added before
1414 the image with few fields:
1418 All other information (header size, type of signature,
1419 ...) are provided in the node /image/pre-load/sig of
1425 bool "Enable boot arguments"
1427 Provide boot arguments to bootm command. Boot arguments are specified
1428 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1429 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1430 will be undefined and won't take any space in U-Boot image.
1433 string "Boot arguments"
1434 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1436 This can be used to pass arguments to the bootm command. The value of
1437 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1438 this value will also override the "chosen" node in FDT blob.
1440 config BOOTARGS_SUBST
1441 bool "Support substituting strings in boot arguments"
1443 This allows substituting string values in the boot arguments. These
1444 are applied after the commandline has been built.
1446 One use for this is to insert the root-disk UUID into the command
1447 line where bootargs contains "root=${uuid}"
1449 setenv bootargs "console= root=${uuid}"
1450 # Set the 'uuid' environment variable
1451 part uuid mmc 2:2 uuid
1453 # Command-line substitution will put the real uuid into the
1454 # kernel command line
1457 config USE_BOOTCOMMAND
1458 bool "Enable a default value for bootcmd"
1460 Provide a default value for the bootcmd entry in the environment. If
1461 autoboot is enabled this is what will be run automatically. Enable
1462 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1463 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1464 won't take any space in U-Boot image.
1467 string "bootcmd value"
1468 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1469 default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL
1470 default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL
1471 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1473 This is the string of commands that will be used as bootcmd and if
1474 AUTOBOOT is set, automatically run.
1477 bool "Enable preboot"
1479 When this option is enabled, the existence of the environment
1480 variable "preboot" will be checked immediately before starting the
1481 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1482 entering interactive mode.
1484 This feature is especially useful when "preboot" is automatically
1485 generated or modified. For example, the boot code can modify the
1486 "preboot" when a user holds down a certain combination of keys.
1489 string "preboot default value"
1490 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1491 default "usb start" if USB_KEYBOARD
1494 This is the default of "preboot" environment variable.
1496 config DEFAULT_FDT_FILE
1497 string "Default fdt file"
1499 This option is used to set the default fdt file to boot OS.
1501 config SAVE_PREV_BL_FDT_ADDR
1503 bool "Saves fdt address, passed by the previous bootloader, to env var"
1505 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1506 enable this option to save fdt address, passed by the
1507 previous bootloader for future use.
1508 Address is saved to `prevbl_fdt_addr` environment variable.
1510 If no fdt was provided by previous bootloader, no env variables
1513 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1515 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1517 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1518 enable this option to save initramfs address, passed by the
1519 previous bootloader for future use.
1520 Address is saved to `prevbl_initrd_start_addr` environment variable.
1522 If no initramfs was provided by previous bootloader, no env variables