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"
18 This option allows you to boot the new uImage structure,
19 Flattened Image Tree. FIT is formally a FDT, which can include
20 images of various types (kernel, FDT blob, ramdisk, etc.)
21 in a single blob. To boot this new uImage structure,
22 pass the address of the blob to the "bootm" command.
23 FIT is very flexible, supporting compression, multiple images,
24 multiple configurations, verification through hashing and also
25 verified boot (secure boot using RSA).
29 config FIT_EXTERNAL_OFFSET
30 hex "FIT external data offset"
33 This specifies a data offset in fit image.
34 The offset is from data payload offset to the beginning of
35 fit image header. When specifies a offset, specific data
36 could be put in the hole between data payload and fit image
37 header, such as CSF data on i.MX platform.
40 bool "Do a full check of the FIT before using it"
43 Enable this do a full check of the FIT to make sure it is valid. This
44 helps to protect against carefully crafted FITs which take advantage
45 of bugs or omissions in the code. This includes a bad structure,
46 multiple root nodes and the like.
49 bool "Enable signature verification of FIT uImages"
54 select IMAGE_SIGN_INFO
57 This option enables signature verification of FIT uImages,
58 using a hash signed and verified using RSA. If
59 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
60 hashing is available using hardware, then the RSA library will use
61 it. See doc/uImage.FIT/signature.txt for more details.
63 WARNING: When relying on signed FIT images with a required signature
64 check the legacy image format is disabled by default, so that
65 unsigned images cannot be loaded. If a board needs the legacy image
66 format support in this case, enable it using
67 CONFIG_LEGACY_IMAGE_FORMAT.
69 config FIT_SIGNATURE_MAX_SIZE
70 hex "Max size of signed FIT structures"
71 depends on FIT_SIGNATURE
74 This option sets a max size in bytes for verified FIT uImages.
75 A sane value of 256MB protects corrupted DTB structures from overlapping
76 device memory. Assure this size does not extend past expected storage
80 bool "Support rsassa-pss signature scheme of FIT image contents"
81 depends on FIT_SIGNATURE
84 Enable this to support the pss padding algorithm as described
85 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
88 bool "Enable ciphering data in a FIT uImages"
92 Enable the feature of data ciphering/unciphering in the tool mkimage
93 and in the u-boot support of the FIT image.
96 bool "Show verbose messages when FIT images fail"
98 Generally a system will have valid FIT images so debug messages
99 are a waste of code space. If you are debugging your images then
100 you can enable this option to get more verbose information about
103 config FIT_BEST_MATCH
104 bool "Select the best match for the kernel device tree"
106 When no configuration is explicitly selected, default to the
107 one whose fdt's compatibility field best matches that of
108 U-Boot itself. A match is considered "best" if it matches the
109 most specific compatibility entry of U-Boot's fdt's root node.
110 The order of entries in the configuration's fdt is ignored.
112 config FIT_IMAGE_POST_PROCESS
113 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
114 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
116 Allows doing any sort of manipulation to blobs after they got extracted
117 from FIT images like stripping off headers or modifying the size of the
118 blob, verification, authentication, decryption etc. in a platform or
119 board specific way. In order to use this feature a platform or board-
120 specific implementation of board_fit_image_post_process() must be
121 provided. Also, anything done during this post-processing step would
122 need to be comprehended in how the images were prepared before being
123 injected into the FIT creation (i.e. the blobs would have been pre-
124 processed before being added to the FIT image).
127 bool "Support FIT printing"
130 Support printing the content of the fitImage in a verbose manner.
135 bool "Support Flattened Image Tree within SPL"
140 bool "Support FIT printing within SPL"
143 Support printing the content of the fitImage in a verbose manner in SPL.
145 config SPL_FIT_FULL_CHECK
146 bool "Do a full check of the FIT before using it"
148 Enable this do a full check of the FIT to make sure it is valid. This
149 helps to protect against carefully crafted FITs which take advantage
150 of bugs or omissions in the code. This includes a bad structure,
151 multiple root nodes and the like.
154 config SPL_FIT_SIGNATURE
155 bool "Enable signature verification of FIT firmware within SPL"
157 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
161 select SPL_HASH_SUPPORT
164 select SPL_IMAGE_SIGN_INFO
165 select SPL_FIT_FULL_CHECK
168 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
171 Normally with the SPL framework a legacy image is generated as part
172 of the build. This contains U-Boot along with information as to
173 where it should be loaded. This option instead enables generation
174 of a FIT (Flat Image Tree) which provides more flexibility. In
175 particular it can handle selecting from multiple device tree
176 and passing the correct one to U-Boot.
178 This path has the following limitations:
180 1. "loadables" images, other than FDTs, which do not have a "load"
181 property will not be loaded. This limitation also applies to FPGA
182 images with the correct "compatible" string.
183 2. For FPGA images, only the "compatible" = "u-boot,fpga-legacy"
184 loading method is supported.
185 3. FDTs are only loaded for images with an "os" property of "u-boot".
186 "linux" images are also supported with Falcon boot mode.
188 config SPL_LOAD_FIT_ADDRESS
189 hex "load address of fit image"
190 depends on SPL_LOAD_FIT
193 Specify the load address of the fit image that will be loaded
196 config SPL_LOAD_FIT_APPLY_OVERLAY
197 bool "Enable SPL applying DT overlays from FIT"
198 depends on SPL_LOAD_FIT
199 select OF_LIBFDT_OVERLAY
201 The device tree is loaded from the FIT image. Allow the SPL is to
202 also load device-tree overlays from the FIT image an apply them
203 over the device tree.
205 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
206 depends on SPL_LOAD_FIT_APPLY_OVERLAY
208 hex "size of temporary buffer used to load the overlays"
210 The size of the area where the overlays will be loaded and
211 uncompress. Must be at least as large as biggest overlay
214 config SPL_LOAD_FIT_FULL
215 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
218 Normally with the SPL framework a legacy image is generated as part
219 of the build. This contains U-Boot along with information as to
220 where it should be loaded. This option instead enables generation
221 of a FIT (Flat Image Tree) which provides more flexibility. In
222 particular it can handle selecting from multiple device tree
223 and passing the correct one to U-Boot.
225 config SPL_FIT_IMAGE_POST_PROCESS
226 bool "Enable post-processing of FIT artifacts after loading by the SPL"
227 depends on SPL_LOAD_FIT
229 Allows doing any sort of manipulation to blobs after they got extracted
230 from the U-Boot FIT image like stripping off headers or modifying the
231 size of the blob, verification, authentication, decryption etc. in a
232 platform or board specific way. In order to use this feature a platform
233 or board-specific implementation of board_fit_image_post_process() must
234 be provided. Also, anything done during this post-processing step would
235 need to be comprehended in how the images were prepared before being
236 injected into the FIT creation (i.e. the blobs would have been pre-
237 processed before being added to the FIT image).
239 config SPL_FIT_SOURCE
240 string ".its source file for U-Boot FIT image"
243 Specifies a (platform specific) FIT source file to generate the
244 U-Boot FIT image. This could specify further image to load and/or
247 config USE_SPL_FIT_GENERATOR
248 bool "Use a script to generate the .its script"
249 default y if SPL_FIT && (!ARCH_SUNXI && !RISCV)
251 config SPL_FIT_GENERATOR
252 string ".its file generator script for U-Boot FIT image"
253 depends on USE_SPL_FIT_GENERATOR
254 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
255 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
257 Specifies a (platform specific) script file to generate the FIT
258 source file used to build the U-Boot FIT image file. This gets
259 passed a list of supported device tree file stub names to
260 include in the generated image.
266 config LEGACY_IMAGE_FORMAT
267 bool "Enable support for the legacy image format"
268 default y if !FIT_SIGNATURE
270 This option enables the legacy image format. It is enabled by
271 default for backward compatibility, unless FIT_SIGNATURE is
272 set where it is disabled so that unsigned images cannot be
273 loaded. If a board needs the legacy image format support in this
274 case, enable it here.
276 config SUPPORT_RAW_INITRD
277 bool "Enable raw initrd images"
279 Note, defining the SUPPORT_RAW_INITRD allows user to supply
280 kernel with raw initrd images. The syntax is slightly different, the
281 address of the initrd must be augmented by it's size, in the following
282 format: "<initrd address>:<initrd size>".
284 config OF_BOARD_SETUP
285 bool "Set up board-specific details in device tree before boot"
288 This causes U-Boot to call ft_board_setup() before booting into
289 the Operating System. This function can set up various
290 board-specific information in the device tree for use by the OS.
291 The device tree is then passed to the OS.
293 config OF_SYSTEM_SETUP
294 bool "Set up system-specific details in device tree before boot"
297 This causes U-Boot to call ft_system_setup() before booting into
298 the Operating System. This function can set up various
299 system-specific information in the device tree for use by the OS.
300 The device tree is then passed to the OS.
302 config OF_STDOUT_VIA_ALIAS
303 bool "Update the device-tree stdout alias from U-Boot"
306 This uses U-Boot's serial alias from the aliases node to update
307 the device tree passed to the OS. The "linux,stdout-path" property
308 in the chosen node is set to point to the correct serial node.
309 This option currently references CONFIG_CONS_INDEX, which is
310 incorrect when used with device tree as this option does not
311 exist / should not be used.
313 config SYS_EXTRA_OPTIONS
314 string "Extra Options (DEPRECATED)"
316 The old configuration infrastructure (= mkconfig + boards.cfg)
317 provided the extra options field. If you have something like
318 "HAS_BAR,BAZ=64", the optional options
320 #define CONFIG_BAZ 64
321 will be defined in include/config.h.
322 This option was prepared for the smooth migration from the old
323 configuration to Kconfig. Since this option will be removed sometime,
324 new boards should not use this option.
326 config HAVE_SYS_TEXT_BASE
328 depends on !NIOS2 && !XTENSA
333 depends on HAVE_SYS_TEXT_BASE
334 default 0x0 if POSITION_INDEPENDENT
335 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
336 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
337 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
338 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
341 The address in memory that U-Boot will be running from, initially.
344 depends on ARC || ARCH_SUNXI || MPC83xx
345 int "CPU clock frequency"
347 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
349 config ARCH_FIXUP_FDT_MEMORY
350 bool "Enable arch_fixup_memory_banks() call"
353 Enable FDT memory map syncup before OS boot. This feature can be
354 used for booting OS with different memory setup where the part of
355 the memory location should be used for different purpose.
358 bool "Support booting Chrome OS"
360 Chrome OS requires U-Boot to set up a table indicating the boot mode
361 (e.g. Developer mode) and a few other things. Enable this if you are
362 booting on a Chromebook to avoid getting an error about an invalid
365 config CHROMEOS_VBOOT
366 bool "Support Chrome OS verified boot"
368 This is intended to enable the full Chrome OS verified boot support
369 in U-Boot. It is not actually implemented in the U-Boot source code
370 at present, so this option is always set to 'n'. It allows
371 distinguishing between booting Chrome OS in a basic way (developer
372 mode) and a full boot.
374 endmenu # Boot images
379 bool "Boot timing and reporting"
381 Enable recording of boot time while booting. To use it, insert
382 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
383 bootstage.h. Only a single entry is recorded for each ID. You can
384 give the entry a name with bootstage_mark_name(). You can also
385 record elapsed time in a particular stage using bootstage_start()
386 before starting and bootstage_accum() when finished. Bootstage will
387 add up all the accumulated time and report it.
389 Normally, IDs are defined in bootstage.h but a small number of
390 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
393 Calls to show_boot_progress() will also result in log entries but
394 these will not have names.
397 bool "Boot timing and reported in SPL"
400 Enable recording of boot time in SPL. To make this visible to U-Boot
401 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
402 information when SPL finishes and load it when U-Boot proper starts
406 bool "Boot timing and reported in TPL"
409 Enable recording of boot time in SPL. To make this visible to U-Boot
410 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
411 information when TPL finishes and load it when U-Boot proper starts
414 config BOOTSTAGE_REPORT
415 bool "Display a detailed boot timing report before booting the OS"
418 Enable output of a boot time report just before the OS is booted.
419 This shows how long it took U-Boot to go through each stage of the
420 boot process. The report looks something like this:
422 Timer summary in microseconds:
425 3,575,678 3,575,678 board_init_f start
426 3,575,695 17 arch_cpu_init A9
427 3,575,777 82 arch_cpu_init done
428 3,659,598 83,821 board_init_r start
429 3,910,375 250,777 main_loop
430 29,916,167 26,005,792 bootm_start
431 30,361,327 445,160 start_kernel
433 config BOOTSTAGE_RECORD_COUNT
434 int "Number of boot stage records to store"
438 This is the size of the bootstage record list and is the maximum
439 number of bootstage records that can be recorded.
441 config SPL_BOOTSTAGE_RECORD_COUNT
442 int "Number of boot stage records to store for SPL"
443 depends on SPL_BOOTSTAGE
446 This is the size of the bootstage record list and is the maximum
447 number of bootstage records that can be recorded.
449 config TPL_BOOTSTAGE_RECORD_COUNT
450 int "Number of boot stage records to store for TPL"
451 depends on TPL_BOOTSTAGE
454 This is the size of the bootstage record list and is the maximum
455 number of bootstage records that can be recorded.
458 bool "Store boot timing information in the OS device tree"
461 Stash the bootstage information in the FDT. A root 'bootstage'
462 node is created with each bootstage id as a child. Each child
463 has a 'name' property and either 'mark' containing the
464 mark time in microseconds, or 'accum' containing the
465 accumulated time for that bootstage id in microseconds.
470 name = "board_init_f";
479 Code in the Linux kernel can find this in /proc/devicetree.
481 config BOOTSTAGE_STASH
482 bool "Stash the boot timing information in memory before booting OS"
485 Some OSes do not support device tree. Bootstage can instead write
486 the boot timing information in a binary format at a given address.
487 This happens through a call to bootstage_stash(), typically in
488 the CPU's cleanup_before_linux() function. You can use the
489 'bootstage stash' and 'bootstage unstash' commands to do this on
492 config BOOTSTAGE_STASH_ADDR
493 hex "Address to stash boot timing information"
496 Provide an address which will not be overwritten by the OS when it
497 starts, so that it can read this information when ready.
499 config BOOTSTAGE_STASH_SIZE
500 hex "Size of boot timing stash region"
503 This should be large enough to hold the bootstage stash. A value of
504 4096 (4KiB) is normally plenty.
506 config SHOW_BOOT_PROGRESS
507 bool "Show boot progress in a board-specific manner"
509 Defining this option allows to add some board-specific code (calling
510 a user-provided function show_boot_progress(int) that enables you to
511 show the system's boot progress on some display (for example, some
512 LEDs) on your board. At the moment, the following checkpoints are
515 Legacy uImage format:
518 1 common/cmd_bootm.c before attempting to boot an image
519 -1 common/cmd_bootm.c Image header has bad magic number
520 2 common/cmd_bootm.c Image header has correct magic number
521 -2 common/cmd_bootm.c Image header has bad checksum
522 3 common/cmd_bootm.c Image header has correct checksum
523 -3 common/cmd_bootm.c Image data has bad checksum
524 4 common/cmd_bootm.c Image data has correct checksum
525 -4 common/cmd_bootm.c Image is for unsupported architecture
526 5 common/cmd_bootm.c Architecture check OK
527 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
528 6 common/cmd_bootm.c Image Type check OK
529 -6 common/cmd_bootm.c gunzip uncompression error
530 -7 common/cmd_bootm.c Unimplemented compression type
531 7 common/cmd_bootm.c Uncompression OK
532 8 common/cmd_bootm.c No uncompress/copy overwrite error
533 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
535 9 common/image.c Start initial ramdisk verification
536 -10 common/image.c Ramdisk header has bad magic number
537 -11 common/image.c Ramdisk header has bad checksum
538 10 common/image.c Ramdisk header is OK
539 -12 common/image.c Ramdisk data has bad checksum
540 11 common/image.c Ramdisk data has correct checksum
541 12 common/image.c Ramdisk verification complete, start loading
542 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
543 13 common/image.c Start multifile image verification
544 14 common/image.c No initial ramdisk, no multifile, continue.
546 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
548 -30 arch/powerpc/lib/board.c Fatal error, hang the system
549 -31 post/post.c POST test failed, detected by post_output_backlog()
550 -32 post/post.c POST test failed, detected by post_run_single()
552 34 common/cmd_doc.c before loading a Image from a DOC device
553 -35 common/cmd_doc.c Bad usage of "doc" command
554 35 common/cmd_doc.c correct usage of "doc" command
555 -36 common/cmd_doc.c No boot device
556 36 common/cmd_doc.c correct boot device
557 -37 common/cmd_doc.c Unknown Chip ID on boot device
558 37 common/cmd_doc.c correct chip ID found, device available
559 -38 common/cmd_doc.c Read Error on boot device
560 38 common/cmd_doc.c reading Image header from DOC device OK
561 -39 common/cmd_doc.c Image header has bad magic number
562 39 common/cmd_doc.c Image header has correct magic number
563 -40 common/cmd_doc.c Error reading Image from DOC device
564 40 common/cmd_doc.c Image header has correct magic number
565 41 common/cmd_ide.c before loading a Image from a IDE device
566 -42 common/cmd_ide.c Bad usage of "ide" command
567 42 common/cmd_ide.c correct usage of "ide" command
568 -43 common/cmd_ide.c No boot device
569 43 common/cmd_ide.c boot device found
570 -44 common/cmd_ide.c Device not available
571 44 common/cmd_ide.c Device available
572 -45 common/cmd_ide.c wrong partition selected
573 45 common/cmd_ide.c partition selected
574 -46 common/cmd_ide.c Unknown partition table
575 46 common/cmd_ide.c valid partition table found
576 -47 common/cmd_ide.c Invalid partition type
577 47 common/cmd_ide.c correct partition type
578 -48 common/cmd_ide.c Error reading Image Header on boot device
579 48 common/cmd_ide.c reading Image Header from IDE device OK
580 -49 common/cmd_ide.c Image header has bad magic number
581 49 common/cmd_ide.c Image header has correct magic number
582 -50 common/cmd_ide.c Image header has bad checksum
583 50 common/cmd_ide.c Image header has correct checksum
584 -51 common/cmd_ide.c Error reading Image from IDE device
585 51 common/cmd_ide.c reading Image from IDE device OK
586 52 common/cmd_nand.c before loading a Image from a NAND device
587 -53 common/cmd_nand.c Bad usage of "nand" command
588 53 common/cmd_nand.c correct usage of "nand" command
589 -54 common/cmd_nand.c No boot device
590 54 common/cmd_nand.c boot device found
591 -55 common/cmd_nand.c Unknown Chip ID on boot device
592 55 common/cmd_nand.c correct chip ID found, device available
593 -56 common/cmd_nand.c Error reading Image Header on boot device
594 56 common/cmd_nand.c reading Image Header from NAND device OK
595 -57 common/cmd_nand.c Image header has bad magic number
596 57 common/cmd_nand.c Image header has correct magic number
597 -58 common/cmd_nand.c Error reading Image from NAND device
598 58 common/cmd_nand.c reading Image from NAND device OK
600 -60 common/env_common.c Environment has a bad CRC, using default
602 64 net/eth.c starting with Ethernet configuration.
603 -64 net/eth.c no Ethernet found.
604 65 net/eth.c Ethernet found.
606 -80 common/cmd_net.c usage wrong
607 80 common/cmd_net.c before calling net_loop()
608 -81 common/cmd_net.c some error in net_loop() occurred
609 81 common/cmd_net.c net_loop() back without error
610 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
611 82 common/cmd_net.c trying automatic boot
612 83 common/cmd_net.c running "source" command
613 -83 common/cmd_net.c some error in automatic boot or "source" command
614 84 common/cmd_net.c end without errors
619 100 common/cmd_bootm.c Kernel FIT Image has correct format
620 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
621 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
622 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
623 102 common/cmd_bootm.c Kernel unit name specified
624 -103 common/cmd_bootm.c Can't get kernel subimage node offset
625 103 common/cmd_bootm.c Found configuration node
626 104 common/cmd_bootm.c Got kernel subimage node offset
627 -104 common/cmd_bootm.c Kernel subimage hash verification failed
628 105 common/cmd_bootm.c Kernel subimage hash verification OK
629 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
630 106 common/cmd_bootm.c Architecture check OK
631 -106 common/cmd_bootm.c Kernel subimage has wrong type
632 107 common/cmd_bootm.c Kernel subimage type OK
633 -107 common/cmd_bootm.c Can't get kernel subimage data/size
634 108 common/cmd_bootm.c Got kernel subimage data/size
635 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
636 -109 common/cmd_bootm.c Can't get kernel subimage type
637 -110 common/cmd_bootm.c Can't get kernel subimage comp
638 -111 common/cmd_bootm.c Can't get kernel subimage os
639 -112 common/cmd_bootm.c Can't get kernel subimage load address
640 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
642 120 common/image.c Start initial ramdisk verification
643 -120 common/image.c Ramdisk FIT image has incorrect format
644 121 common/image.c Ramdisk FIT image has correct format
645 122 common/image.c No ramdisk subimage unit name, using configuration
646 -122 common/image.c Can't get configuration for ramdisk subimage
647 123 common/image.c Ramdisk unit name specified
648 -124 common/image.c Can't get ramdisk subimage node offset
649 125 common/image.c Got ramdisk subimage node offset
650 -125 common/image.c Ramdisk subimage hash verification failed
651 126 common/image.c Ramdisk subimage hash verification OK
652 -126 common/image.c Ramdisk subimage for unsupported architecture
653 127 common/image.c Architecture check OK
654 -127 common/image.c Can't get ramdisk subimage data/size
655 128 common/image.c Got ramdisk subimage data/size
656 129 common/image.c Can't get ramdisk load address
657 -129 common/image.c Got ramdisk load address
659 -130 common/cmd_doc.c Incorrect FIT image format
660 131 common/cmd_doc.c FIT image format OK
662 -140 common/cmd_ide.c Incorrect FIT image format
663 141 common/cmd_ide.c FIT image format OK
665 -150 common/cmd_nand.c Incorrect FIT image format
666 151 common/cmd_nand.c FIT image format OK
673 bool "Support for booting from NOR flash"
676 Enabling this will make a U-Boot binary that is capable of being
677 booted via NOR. In this case we will enable certain pinmux early
678 as the ROM only partially sets up pinmux. We also default to using
682 bool "Support for booting from NAND flash"
686 Enabling this will make a U-Boot binary that is capable of being
687 booted via NAND flash. This is not a must, some SoCs need this,
691 bool "Support for booting from ONENAND"
695 Enabling this will make a U-Boot binary that is capable of being
696 booted via ONENAND. This is not a must, some SoCs need this,
700 bool "Support for booting from QSPI flash"
703 Enabling this will make a U-Boot binary that is capable of being
704 booted via QSPI flash. This is not a must, some SoCs need this,
708 bool "Support for booting from SATA"
711 Enabling this will make a U-Boot binary that is capable of being
712 booted via SATA. This is not a must, some SoCs need this,
716 bool "Support for booting from SD/EMMC"
719 Enabling this will make a U-Boot binary that is capable of being
720 booted via SD/EMMC. This is not a must, some SoCs need this,
724 bool "Support for booting from SPI flash"
727 Enabling this will make a U-Boot binary that is capable of being
728 booted via SPI flash. This is not a must, some SoCs need this,
733 menu "Autoboot options"
739 This enables the autoboot. See doc/README.autoboot for detail.
742 int "delay in seconds before automatically booting"
746 Delay before automatically running bootcmd;
747 set to 0 to autoboot with no delay, but you can stop it by key input.
748 set to -1 to disable autoboot.
749 set to -2 to autoboot with no delay and not check for abort
751 If this value is >= 0 then it is also used for the default delay
752 before starting the default entry in bootmenu. If it is < 0 then
753 a default value of 10s is used.
755 See doc/README.autoboot for details.
757 config AUTOBOOT_KEYED
758 bool "Stop autobooting via specific input key / string"
761 This option enables stopping (aborting) of the automatic
762 boot feature only by issuing a specific input key or
763 string. If not enabled, any input key will abort the
764 U-Boot automatic booting process and bring the device
765 to the U-Boot prompt for user input.
767 config AUTOBOOT_FLUSH_STDIN
768 bool "Enable flushing stdin before starting to read the password"
769 depends on AUTOBOOT_KEYED && !SANDBOX
771 When this option is enabled stdin buffer will be flushed before
772 starting to read the password.
773 This can't be enabled for the sandbox as flushing stdin would
774 break the autoboot unit tests.
776 config AUTOBOOT_PROMPT
777 string "Autoboot stop prompt"
778 depends on AUTOBOOT_KEYED
779 default "Autoboot in %d seconds\\n"
781 This string is displayed before the boot delay selected by
782 CONFIG_BOOTDELAY starts. If it is not defined there is no
783 output indicating that autoboot is in progress.
785 Note that this define is used as the (only) argument to a
786 printf() call, so it may contain '%' format specifications,
787 provided that it also includes, sepearated by commas exactly
788 like in a printf statement, the required arguments. It is
789 the responsibility of the user to select only such arguments
790 that are valid in the given context.
792 config AUTOBOOT_ENCRYPTION
793 bool "Enable encryption in autoboot stopping"
794 depends on AUTOBOOT_KEYED
796 This option allows a string to be entered into U-Boot to stop the
798 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
800 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
801 to the crypt-based functionality and be compared against the
802 string in the environment variable 'bootstopkeycrypt'.
803 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
804 and compared against the hash in the environment variable
806 If it matches in either case then boot stops and
807 a command-line prompt is presented.
808 This provides a way to ship a secure production device which can also
809 be accessed at the U-Boot command line.
811 config AUTOBOOT_SHA256_FALLBACK
812 bool "Allow fallback from crypt-hashed password to sha256"
813 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
815 This option adds support to fall back from crypt-hashed
816 passwords to checking a SHA256 hashed password in case the
817 'bootstopusesha256' environment variable is set to 'true'.
819 config AUTOBOOT_DELAY_STR
820 string "Delay autobooting via specific input key / string"
821 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
823 This option delays the automatic boot feature by issuing
824 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
825 or the environment variable "bootdelaykey" is specified
826 and this string is received from console input before
827 autoboot starts booting, U-Boot gives a command prompt. The
828 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
829 used, otherwise it never times out.
831 config AUTOBOOT_STOP_STR
832 string "Stop autobooting via specific input key / string"
833 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
835 This option enables stopping (aborting) of the automatic
836 boot feature only by issuing a specific input key or
837 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
838 variable "bootstopkey" is specified and this string is
839 received from console input before autoboot starts booting,
840 U-Boot gives a command prompt. The U-Boot prompt never
841 times out, even if CONFIG_BOOT_RETRY_TIME is used.
843 config AUTOBOOT_KEYED_CTRLC
844 bool "Enable Ctrl-C autoboot interruption"
845 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
848 This option allows for the boot sequence to be interrupted
849 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
850 Setting this variable provides an escape sequence from the
851 limited "password" strings.
853 config AUTOBOOT_NEVER_TIMEOUT
854 bool "Make the password entry never time-out"
855 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
857 This option removes the timeout from the password entry
858 when the user first presses the <Enter> key before entering
861 config AUTOBOOT_STOP_STR_ENABLE
862 bool "Enable fixed string to stop autobooting"
863 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
865 This option enables the feature to add a fixed stop
866 string that is defined at compile time.
867 In every case it will be tried to load the stop
868 string from the environment.
869 In case this is enabled and there is no stop string
870 in the environment, this will be used as default value.
872 config AUTOBOOT_STOP_STR_CRYPT
873 string "Stop autobooting via crypt-hashed password"
874 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
876 This option adds the feature to only stop the autobooting,
877 and therefore boot into the U-Boot prompt, when the input
878 string / password matches a values that is hashed via
879 one of the supported crypt-style password hashing options
880 and saved in the environment variable "bootstopkeycrypt".
882 config AUTOBOOT_STOP_STR_SHA256
883 string "Stop autobooting via SHA256 hashed password"
884 depends on AUTOBOOT_STOP_STR_ENABLE
886 This option adds the feature to only stop the autobooting,
887 and therefore boot into the U-Boot prompt, when the input
888 string / password matches a values that is encypted via
889 a SHA256 hash and saved in the environment variable
890 "bootstopkeysha256". If the value in that variable
891 includes a ":", the portion prior to the ":" will be treated
894 config AUTOBOOT_USE_MENUKEY
895 bool "Allow a specify key to run a menu from the environment"
896 depends on !AUTOBOOT_KEYED
898 If a specific key is pressed to stop autoboot, then the commands in
899 the environment variable 'menucmd' are executed before boot starts.
901 config AUTOBOOT_MENUKEY
902 int "ASCII value of boot key to show a menu"
904 depends on AUTOBOOT_USE_MENUKEY
906 If this key is pressed to stop autoboot, then the commands in the
907 environment variable 'menucmd' will be executed before boot starts.
908 For example, 33 means "!" in ASCII, so pressing ! at boot would take
911 config AUTOBOOT_MENU_SHOW
912 bool "Show a menu on boot"
913 depends on CMD_BOOTMENU
915 This enables the boot menu, controlled by environment variables
916 defined by the board. The menu starts after running the 'preboot'
917 environmnent variable (if enabled) and before handling the boot delay.
918 See README.bootmenu for more details.
923 bool "Enable boot arguments"
925 Provide boot arguments to bootm command. Boot arguments are specified
926 in CONFIG_BOOTARGS option. Enable this option to be able to specify
927 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
928 will be undefined and won't take any space in U-Boot image.
931 string "Boot arguments"
932 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
934 This can be used to pass arguments to the bootm command. The value of
935 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
936 this value will also override the "chosen" node in FDT blob.
938 config BOOTARGS_SUBST
939 bool "Support substituting strings in boot arguments"
941 This allows substituting string values in the boot arguments. These
942 are applied after the commandline has been built.
944 One use for this is to insert the root-disk UUID into the command
945 line where bootargs contains "root=${uuid}"
947 setenv bootargs "console= root=${uuid}"
948 # Set the 'uuid' environment variable
949 part uuid mmc 2:2 uuid
951 # Command-line substitution will put the real uuid into the
952 # kernel command line
955 config USE_BOOTCOMMAND
956 bool "Enable a default value for bootcmd"
958 Provide a default value for the bootcmd entry in the environment. If
959 autoboot is enabled this is what will be run automatically. Enable
960 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
961 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
962 won't take any space in U-Boot image.
965 string "bootcmd value"
966 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
967 default "run distro_bootcmd" if DISTRO_DEFAULTS
969 This is the string of commands that will be used as bootcmd and if
970 AUTOBOOT is set, automatically run.
973 bool "Enable preboot"
975 When this option is enabled, the existence of the environment
976 variable "preboot" will be checked immediately before starting the
977 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
978 entering interactive mode.
980 This feature is especially useful when "preboot" is automatically
981 generated or modified. For example, the boot code can modify the
982 "preboot" when a user holds down a certain combination of keys.
985 string "preboot default value"
986 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
987 default "usb start" if USB_KEYBOARD
990 This is the default of "preboot" environment variable.
992 config DEFAULT_FDT_FILE
993 string "Default fdt file"
995 This option is used to set the default fdt file to boot OS.