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
127 Allows doing any sort of manipulation to blobs after they got extracted
128 from FIT images like stripping off headers or modifying the size of the
129 blob, verification, authentication, decryption etc. in a platform or
130 board specific way. In order to use this feature a platform or board-
131 specific implementation of board_fit_image_post_process() must be
132 provided. Also, anything done during this post-processing step would
133 need to be comprehended in how the images were prepared before being
134 injected into the FIT creation (i.e. the blobs would have been pre-
135 processed before being added to the FIT image).
138 bool "Support FIT printing"
141 Support printing the content of the fitImage in a verbose manner.
146 bool "Support Flattened Image Tree within SPL"
152 bool "Support FIT printing within SPL"
155 Support printing the content of the fitImage in a verbose manner in SPL.
157 config SPL_FIT_FULL_CHECK
158 bool "Do a full check of the FIT before using it"
160 Enable this do a full check of the FIT to make sure it is valid. This
161 helps to protect against carefully crafted FITs which take advantage
162 of bugs or omissions in the code. This includes a bad structure,
163 multiple root nodes and the like.
166 config SPL_FIT_SIGNATURE
167 bool "Enable signature verification of FIT firmware within SPL"
169 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
176 select SPL_IMAGE_SIGN_INFO
177 select SPL_FIT_FULL_CHECK
179 config SPL_FIT_SIGNATURE_MAX_SIZE
180 hex "Max size of signed FIT structures in SPL"
181 depends on SPL_FIT_SIGNATURE
184 This option sets a max size in bytes for verified FIT uImages.
185 A sane value of 256MB protects corrupted DTB structures from overlapping
186 device memory. Assure this size does not extend past expected storage
189 config SPL_FIT_RSASSA_PSS
190 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
191 depends on SPL_FIT_SIGNATURE
193 Enable this to support the pss padding algorithm as described
194 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
197 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
200 Normally with the SPL framework a legacy image is generated as part
201 of the build. This contains U-Boot along with information as to
202 where it should be loaded. This option instead enables generation
203 of a FIT (Flat Image Tree) which provides more flexibility. In
204 particular it can handle selecting from multiple device tree
205 and passing the correct one to U-Boot.
207 This path has the following limitations:
209 1. "loadables" images, other than FDTs, which do not have a "load"
210 property will not be loaded. This limitation also applies to FPGA
211 images with the correct "compatible" string.
212 2. For FPGA images, only the "compatible" = "u-boot,fpga-legacy"
213 loading method is supported.
214 3. FDTs are only loaded for images with an "os" property of "u-boot".
215 "linux" images are also supported with Falcon boot mode.
217 config SPL_LOAD_FIT_ADDRESS
218 hex "load address of fit image"
219 depends on SPL_LOAD_FIT
222 Specify the load address of the fit image that will be loaded
225 config SPL_LOAD_FIT_APPLY_OVERLAY
226 bool "Enable SPL applying DT overlays from FIT"
227 depends on SPL_LOAD_FIT
228 select OF_LIBFDT_OVERLAY
230 The device tree is loaded from the FIT image. Allow the SPL is to
231 also load device-tree overlays from the FIT image an apply them
232 over the device tree.
234 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
235 depends on SPL_LOAD_FIT_APPLY_OVERLAY
237 hex "size of temporary buffer used to load the overlays"
239 The size of the area where the overlays will be loaded and
240 uncompress. Must be at least as large as biggest overlay
243 config SPL_LOAD_FIT_FULL
244 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
247 Normally with the SPL framework a legacy image is generated as part
248 of the build. This contains U-Boot along with information as to
249 where it should be loaded. This option instead enables generation
250 of a FIT (Flat Image Tree) which provides more flexibility. In
251 particular it can handle selecting from multiple device tree
252 and passing the correct one to U-Boot.
254 config SPL_FIT_IMAGE_POST_PROCESS
255 bool "Enable post-processing of FIT artifacts after loading by the SPL"
256 depends on SPL_LOAD_FIT
258 Allows doing any sort of manipulation to blobs after they got extracted
259 from the U-Boot FIT image like stripping off headers or modifying the
260 size of the blob, verification, authentication, decryption etc. in a
261 platform or board specific way. In order to use this feature a platform
262 or board-specific implementation of board_fit_image_post_process() must
263 be provided. Also, anything done during this post-processing step would
264 need to be comprehended in how the images were prepared before being
265 injected into the FIT creation (i.e. the blobs would have been pre-
266 processed before being added to the FIT image).
268 config SPL_FIT_SOURCE
269 string ".its source file for U-Boot FIT image"
272 Specifies a (platform specific) FIT source file to generate the
273 U-Boot FIT image. This could specify further image to load and/or
276 config USE_SPL_FIT_GENERATOR
277 bool "Use a script to generate the .its script"
278 default y if SPL_FIT && (!ARCH_SUNXI && !RISCV)
280 config SPL_FIT_GENERATOR
281 string ".its file generator script for U-Boot FIT image"
282 depends on USE_SPL_FIT_GENERATOR
283 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
284 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
286 Specifies a (platform specific) script file to generate the FIT
287 source file used to build the U-Boot FIT image file. This gets
288 passed a list of supported device tree file stub names to
289 include in the generated image.
296 bool "Standard boot support"
298 depends on DM && OF_CONTROL && BLK
300 U-Boot supports a standard way of locating something to boot,
301 typically an Operating System such as Linux, provided by a distro such
302 as Arch Linux or Debian. Enable this to support iterating through
303 available bootdevs and using bootmeths to find bootflows suitable for
306 Standard boot is not a standard way of booting, just a framework
307 within U-Boot for supporting all the different ways that exist.
311 - bootdev - a device which can hold a distro (e.g. MMC)
312 - bootmeth - a method to scan a bootdev to find bootflows (owned by
314 - bootflow - a description of how to boot (owned by the distro)
317 bool "Enhanced features for standard boot"
320 This enables various useful features for standard boot, which are not
321 essential for operation:
323 - bootdev, bootmeth commands
324 - extra features in the bootflow command
325 - support for selecting the ordering of bootmeths ("bootmeth order")
326 - support for selecting the ordering of bootdevs using the devicetree
327 as well as the "boot_targets" environment variable
331 config BOOTSTD_BOOTCOMMAND
332 bool "Use bootstd to boot"
333 default y if !DISTRO_DEFAULTS
335 Enable this to select a default boot-command suitable for booting
336 with standard boot. This can be overridden by the board if needed,
337 but the default command should be enough for most boards which use
340 For now this is only selected if distro boot is NOT used, since
341 standard boot does not support all of the features of distro boot
344 config BOOTMETH_DISTRO
345 bool "Bootdev support for distro boot"
349 Enables support for distro boot using bootdevs. This makes the
350 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
353 This provides a way to try out standard boot on an existing boot flow.
355 config BOOTMETH_DISTRO_PXE
356 bool "Bootdev support for distro boot over network"
357 depends on CMD_PXE && CMD_NET && DM_ETH
360 Enables support for distro boot using bootdevs. This makes the
361 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
363 This provides a way to try out standard boot on an existing boot flow.
365 config BOOTMETH_EFILOADER
366 bool "Bootdev support for EFI boot"
367 depends on CMD_BOOTEFI
370 Enables support for EFI boot using bootdevs. This makes the
371 bootdevs look for a 'boot<arch>.efi' on each filesystem
372 they scan. The resulting file is booted after enabling U-Boot's
375 The <arch> depends on the architecture of the board:
377 aa64 - aarch64 (ARM 64-bit)
381 riscv32 - RISC-V 32-bit
382 riscv64 - RISC-V 64-bit
384 This provides a way to try out standard boot on an existing boot flow.
386 config BOOTMETH_SANDBOX
390 This is a sandbox bootmeth driver used for testing. It always returns
391 -ENOTSUPP when attempting to boot.
393 config BOOTMETH_SCRIPT
394 bool "Bootdev support for U-Boot scripts"
395 default y if BOOTSTD_FULL
397 Enables support for booting a distro via a U-Boot script. This makes
398 the bootdevs look for a 'boot/boot.scr' file which can be used to
401 This provides a way to try out standard boot on an existing boot flow.
402 It is not enabled by default to save space.
406 config LEGACY_IMAGE_FORMAT
407 bool "Enable support for the legacy image format"
408 default y if !FIT_SIGNATURE
410 This option enables the legacy image format. It is enabled by
411 default for backward compatibility, unless FIT_SIGNATURE is
412 set where it is disabled so that unsigned images cannot be
413 loaded. If a board needs the legacy image format support in this
414 case, enable it here.
416 config SUPPORT_RAW_INITRD
417 bool "Enable raw initrd images"
419 Note, defining the SUPPORT_RAW_INITRD allows user to supply
420 kernel with raw initrd images. The syntax is slightly different, the
421 address of the initrd must be augmented by it's size, in the following
422 format: "<initrd address>:<initrd size>".
424 config OF_BOARD_SETUP
425 bool "Set up board-specific details in device tree before boot"
428 This causes U-Boot to call ft_board_setup() before booting into
429 the Operating System. This function can set up various
430 board-specific information in the device tree for use by the OS.
431 The device tree is then passed to the OS.
433 config OF_SYSTEM_SETUP
434 bool "Set up system-specific details in device tree before boot"
437 This causes U-Boot to call ft_system_setup() before booting into
438 the Operating System. This function can set up various
439 system-specific information in the device tree for use by the OS.
440 The device tree is then passed to the OS.
442 config OF_STDOUT_VIA_ALIAS
443 bool "Update the device-tree stdout alias from U-Boot"
446 This uses U-Boot's serial alias from the aliases node to update
447 the device tree passed to the OS. The "linux,stdout-path" property
448 in the chosen node is set to point to the correct serial node.
449 This option currently references CONFIG_CONS_INDEX, which is
450 incorrect when used with device tree as this option does not
451 exist / should not be used.
453 config SYS_EXTRA_OPTIONS
454 string "Extra Options (DEPRECATED)"
456 The old configuration infrastructure (= mkconfig + boards.cfg)
457 provided the extra options field. If you have something like
458 "HAS_BAR,BAZ=64", the optional options
460 #define CONFIG_BAZ 64
461 will be defined in include/config.h.
462 This option was prepared for the smooth migration from the old
463 configuration to Kconfig. Since this option will be removed sometime,
464 new boards should not use this option.
466 config HAVE_SYS_TEXT_BASE
468 depends on !NIOS2 && !XTENSA
473 depends on HAVE_SYS_TEXT_BASE
474 default 0x0 if POSITION_INDEPENDENT
475 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
476 default 0x81700000 if MACH_SUNIV
477 default 0x2a000000 if MACH_SUN9I
478 default 0x42e00000 if MACH_SUN8I_V3S
479 default 0x4a000000 if ARCH_SUNXI
482 The address in memory that U-Boot will be running from, initially.
484 config HAVE_SYS_MONITOR_BASE
486 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
487 || FLASH_PIC32 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
491 config SYS_MONITOR_BASE
492 depends on HAVE_SYS_MONITOR_BASE
493 hex "Physical start address of boot monitor code"
494 default SYS_TEXT_BASE
496 The physical start address of boot monitor code (which is the same as
497 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
498 when booting from flash.
500 config SPL_SYS_MONITOR_BASE
501 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
502 hex "Physical start address of SPL monitor code"
503 default SPL_TEXT_BASE
505 config TPL_SYS_MONITOR_BASE
506 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
507 hex "Physical start address of TPL monitor code"
509 config DYNAMIC_SYS_CLK_FREQ
510 bool "Determine CPU clock frequency at run-time"
512 Implement a get_board_sys_clk function that will determine the CPU
513 clock frequency at run time, rather than define it statically.
516 depends on !DYNAMIC_SYS_CLK_FREQ
517 int "CPU clock frequency"
518 default 125000000 if ARCH_LS1012A
519 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
520 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
521 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
522 default 66660000 if ARCH_T2080
523 default 33333333 if RCAR_GEN3
524 default 24000000 if ARCH_EXYNOS
525 default 20000000 if RCAR_GEN2
528 A static value for the CPU frequency. Note that if not required
529 for a given SoC, this can be left at 0.
531 config ARCH_FIXUP_FDT_MEMORY
532 bool "Enable arch_fixup_memory_banks() call"
535 Enable FDT memory map syncup before OS boot. This feature can be
536 used for booting OS with different memory setup where the part of
537 the memory location should be used for different purpose.
540 bool "Support booting Chrome OS"
542 Chrome OS requires U-Boot to set up a table indicating the boot mode
543 (e.g. Developer mode) and a few other things. Enable this if you are
544 booting on a Chromebook to avoid getting an error about an invalid
547 config CHROMEOS_VBOOT
548 bool "Support Chrome OS verified boot"
550 This is intended to enable the full Chrome OS verified boot support
551 in U-Boot. It is not actually implemented in the U-Boot source code
552 at present, so this option is always set to 'n'. It allows
553 distinguishing between booting Chrome OS in a basic way (developer
554 mode) and a full boot.
557 bool "Freescale PBL(pre-boot loader) image format support"
559 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
560 For more details refer to doc/README.pblimage
563 prompt "Freescale PBL load location"
564 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
565 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
569 bool "Freescale PBL is found on SD card"
572 bool "Freescale PBL is found on SPI flash"
576 config SYS_FSL_PBL_PBI
577 string "PBI(pre-boot instructions) commands for the PBL image"
578 depends on RAMBOOT_PBL
580 PBI commands can be used to configure SoC before it starts the execution.
581 Please refer doc/README.pblimage for more details.
583 config SYS_FSL_PBL_RCW
584 string "Aadditional RCW (Power on reset configuration) for the PBL image"
585 depends on RAMBOOT_PBL
587 Enables addition of RCW (Power on reset configuration) in built image.
588 Please refer doc/README.pblimage for more details.
590 endmenu # Boot images
595 bool "Boot timing and reporting"
597 Enable recording of boot time while booting. To use it, insert
598 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
599 bootstage.h. Only a single entry is recorded for each ID. You can
600 give the entry a name with bootstage_mark_name(). You can also
601 record elapsed time in a particular stage using bootstage_start()
602 before starting and bootstage_accum() when finished. Bootstage will
603 add up all the accumulated time and report it.
605 Normally, IDs are defined in bootstage.h but a small number of
606 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
609 Calls to show_boot_progress() will also result in log entries but
610 these will not have names.
613 bool "Boot timing and reported in SPL"
616 Enable recording of boot time in SPL. To make this visible to U-Boot
617 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
618 information when SPL finishes and load it when U-Boot proper starts
622 bool "Boot timing and reported in TPL"
625 Enable recording of boot time in SPL. To make this visible to U-Boot
626 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
627 information when TPL finishes and load it when U-Boot proper starts
630 config BOOTSTAGE_REPORT
631 bool "Display a detailed boot timing report before booting the OS"
634 Enable output of a boot time report just before the OS is booted.
635 This shows how long it took U-Boot to go through each stage of the
636 boot process. The report looks something like this:
638 Timer summary in microseconds:
641 3,575,678 3,575,678 board_init_f start
642 3,575,695 17 arch_cpu_init A9
643 3,575,777 82 arch_cpu_init done
644 3,659,598 83,821 board_init_r start
645 3,910,375 250,777 main_loop
646 29,916,167 26,005,792 bootm_start
647 30,361,327 445,160 start_kernel
649 config BOOTSTAGE_RECORD_COUNT
650 int "Number of boot stage records to store"
654 This is the size of the bootstage record list and is the maximum
655 number of bootstage records that can be recorded.
657 config SPL_BOOTSTAGE_RECORD_COUNT
658 int "Number of boot stage records to store for SPL"
659 depends on SPL_BOOTSTAGE
662 This is the size of the bootstage record list and is the maximum
663 number of bootstage records that can be recorded.
665 config TPL_BOOTSTAGE_RECORD_COUNT
666 int "Number of boot stage records to store for TPL"
667 depends on TPL_BOOTSTAGE
670 This is the size of the bootstage record list and is the maximum
671 number of bootstage records that can be recorded.
674 bool "Store boot timing information in the OS device tree"
677 Stash the bootstage information in the FDT. A root 'bootstage'
678 node is created with each bootstage id as a child. Each child
679 has a 'name' property and either 'mark' containing the
680 mark time in microseconds, or 'accum' containing the
681 accumulated time for that bootstage id in microseconds.
686 name = "board_init_f";
695 Code in the Linux kernel can find this in /proc/devicetree.
697 config BOOTSTAGE_STASH
698 bool "Stash the boot timing information in memory before booting OS"
701 Some OSes do not support device tree. Bootstage can instead write
702 the boot timing information in a binary format at a given address.
703 This happens through a call to bootstage_stash(), typically in
704 the CPU's cleanup_before_linux() function. You can use the
705 'bootstage stash' and 'bootstage unstash' commands to do this on
708 config BOOTSTAGE_STASH_ADDR
709 hex "Address to stash boot timing information"
712 Provide an address which will not be overwritten by the OS when it
713 starts, so that it can read this information when ready.
715 config BOOTSTAGE_STASH_SIZE
716 hex "Size of boot timing stash region"
719 This should be large enough to hold the bootstage stash. A value of
720 4096 (4KiB) is normally plenty.
722 config SHOW_BOOT_PROGRESS
723 bool "Show boot progress in a board-specific manner"
725 Defining this option allows to add some board-specific code (calling
726 a user-provided function show_boot_progress(int) that enables you to
727 show the system's boot progress on some display (for example, some
728 LEDs) on your board. At the moment, the following checkpoints are
731 Legacy uImage format:
734 1 common/cmd_bootm.c before attempting to boot an image
735 -1 common/cmd_bootm.c Image header has bad magic number
736 2 common/cmd_bootm.c Image header has correct magic number
737 -2 common/cmd_bootm.c Image header has bad checksum
738 3 common/cmd_bootm.c Image header has correct checksum
739 -3 common/cmd_bootm.c Image data has bad checksum
740 4 common/cmd_bootm.c Image data has correct checksum
741 -4 common/cmd_bootm.c Image is for unsupported architecture
742 5 common/cmd_bootm.c Architecture check OK
743 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
744 6 common/cmd_bootm.c Image Type check OK
745 -6 common/cmd_bootm.c gunzip uncompression error
746 -7 common/cmd_bootm.c Unimplemented compression type
747 7 common/cmd_bootm.c Uncompression OK
748 8 common/cmd_bootm.c No uncompress/copy overwrite error
749 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
751 9 common/image.c Start initial ramdisk verification
752 -10 common/image.c Ramdisk header has bad magic number
753 -11 common/image.c Ramdisk header has bad checksum
754 10 common/image.c Ramdisk header is OK
755 -12 common/image.c Ramdisk data has bad checksum
756 11 common/image.c Ramdisk data has correct checksum
757 12 common/image.c Ramdisk verification complete, start loading
758 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
759 13 common/image.c Start multifile image verification
760 14 common/image.c No initial ramdisk, no multifile, continue.
762 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
764 -30 arch/powerpc/lib/board.c Fatal error, hang the system
765 -31 post/post.c POST test failed, detected by post_output_backlog()
766 -32 post/post.c POST test failed, detected by post_run_single()
768 34 common/cmd_doc.c before loading a Image from a DOC device
769 -35 common/cmd_doc.c Bad usage of "doc" command
770 35 common/cmd_doc.c correct usage of "doc" command
771 -36 common/cmd_doc.c No boot device
772 36 common/cmd_doc.c correct boot device
773 -37 common/cmd_doc.c Unknown Chip ID on boot device
774 37 common/cmd_doc.c correct chip ID found, device available
775 -38 common/cmd_doc.c Read Error on boot device
776 38 common/cmd_doc.c reading Image header from DOC device OK
777 -39 common/cmd_doc.c Image header has bad magic number
778 39 common/cmd_doc.c Image header has correct magic number
779 -40 common/cmd_doc.c Error reading Image from DOC device
780 40 common/cmd_doc.c Image header has correct magic number
781 41 common/cmd_ide.c before loading a Image from a IDE device
782 -42 common/cmd_ide.c Bad usage of "ide" command
783 42 common/cmd_ide.c correct usage of "ide" command
784 -43 common/cmd_ide.c No boot device
785 43 common/cmd_ide.c boot device found
786 -44 common/cmd_ide.c Device not available
787 44 common/cmd_ide.c Device available
788 -45 common/cmd_ide.c wrong partition selected
789 45 common/cmd_ide.c partition selected
790 -46 common/cmd_ide.c Unknown partition table
791 46 common/cmd_ide.c valid partition table found
792 -47 common/cmd_ide.c Invalid partition type
793 47 common/cmd_ide.c correct partition type
794 -48 common/cmd_ide.c Error reading Image Header on boot device
795 48 common/cmd_ide.c reading Image Header from IDE device OK
796 -49 common/cmd_ide.c Image header has bad magic number
797 49 common/cmd_ide.c Image header has correct magic number
798 -50 common/cmd_ide.c Image header has bad checksum
799 50 common/cmd_ide.c Image header has correct checksum
800 -51 common/cmd_ide.c Error reading Image from IDE device
801 51 common/cmd_ide.c reading Image from IDE device OK
802 52 common/cmd_nand.c before loading a Image from a NAND device
803 -53 common/cmd_nand.c Bad usage of "nand" command
804 53 common/cmd_nand.c correct usage of "nand" command
805 -54 common/cmd_nand.c No boot device
806 54 common/cmd_nand.c boot device found
807 -55 common/cmd_nand.c Unknown Chip ID on boot device
808 55 common/cmd_nand.c correct chip ID found, device available
809 -56 common/cmd_nand.c Error reading Image Header on boot device
810 56 common/cmd_nand.c reading Image Header from NAND device OK
811 -57 common/cmd_nand.c Image header has bad magic number
812 57 common/cmd_nand.c Image header has correct magic number
813 -58 common/cmd_nand.c Error reading Image from NAND device
814 58 common/cmd_nand.c reading Image from NAND device OK
816 -60 common/env_common.c Environment has a bad CRC, using default
818 64 net/eth.c starting with Ethernet configuration.
819 -64 net/eth.c no Ethernet found.
820 65 net/eth.c Ethernet found.
822 -80 common/cmd_net.c usage wrong
823 80 common/cmd_net.c before calling net_loop()
824 -81 common/cmd_net.c some error in net_loop() occurred
825 81 common/cmd_net.c net_loop() back without error
826 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
827 82 common/cmd_net.c trying automatic boot
828 83 common/cmd_net.c running "source" command
829 -83 common/cmd_net.c some error in automatic boot or "source" command
830 84 common/cmd_net.c end without errors
835 100 common/cmd_bootm.c Kernel FIT Image has correct format
836 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
837 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
838 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
839 102 common/cmd_bootm.c Kernel unit name specified
840 -103 common/cmd_bootm.c Can't get kernel subimage node offset
841 103 common/cmd_bootm.c Found configuration node
842 104 common/cmd_bootm.c Got kernel subimage node offset
843 -104 common/cmd_bootm.c Kernel subimage hash verification failed
844 105 common/cmd_bootm.c Kernel subimage hash verification OK
845 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
846 106 common/cmd_bootm.c Architecture check OK
847 -106 common/cmd_bootm.c Kernel subimage has wrong type
848 107 common/cmd_bootm.c Kernel subimage type OK
849 -107 common/cmd_bootm.c Can't get kernel subimage data/size
850 108 common/cmd_bootm.c Got kernel subimage data/size
851 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
852 -109 common/cmd_bootm.c Can't get kernel subimage type
853 -110 common/cmd_bootm.c Can't get kernel subimage comp
854 -111 common/cmd_bootm.c Can't get kernel subimage os
855 -112 common/cmd_bootm.c Can't get kernel subimage load address
856 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
858 120 common/image.c Start initial ramdisk verification
859 -120 common/image.c Ramdisk FIT image has incorrect format
860 121 common/image.c Ramdisk FIT image has correct format
861 122 common/image.c No ramdisk subimage unit name, using configuration
862 -122 common/image.c Can't get configuration for ramdisk subimage
863 123 common/image.c Ramdisk unit name specified
864 -124 common/image.c Can't get ramdisk subimage node offset
865 125 common/image.c Got ramdisk subimage node offset
866 -125 common/image.c Ramdisk subimage hash verification failed
867 126 common/image.c Ramdisk subimage hash verification OK
868 -126 common/image.c Ramdisk subimage for unsupported architecture
869 127 common/image.c Architecture check OK
870 -127 common/image.c Can't get ramdisk subimage data/size
871 128 common/image.c Got ramdisk subimage data/size
872 129 common/image.c Can't get ramdisk load address
873 -129 common/image.c Got ramdisk load address
875 -130 common/cmd_doc.c Incorrect FIT image format
876 131 common/cmd_doc.c FIT image format OK
878 -140 common/cmd_ide.c Incorrect FIT image format
879 141 common/cmd_ide.c FIT image format OK
881 -150 common/cmd_nand.c Incorrect FIT image format
882 151 common/cmd_nand.c FIT image format OK
884 config SPL_SHOW_BOOT_PROGRESS
885 bool "Show boot progress in a board-specific manner in SPL"
888 Defining this option allows to add some board-specific code (calling
889 a user-provided function show_boot_progress(int) that enables you to
890 show the system's boot progress on some display (for example, some
891 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
898 bool "Support for booting from NOR flash"
901 Enabling this will make a U-Boot binary that is capable of being
902 booted via NOR. In this case we will enable certain pinmux early
903 as the ROM only partially sets up pinmux. We also default to using
907 bool "Support for booting from NAND flash"
910 Enabling this will make a U-Boot binary that is capable of being
911 booted via NAND flash. This is not a must, some SoCs need this,
915 bool "Support for booting from ONENAND"
918 Enabling this will make a U-Boot binary that is capable of being
919 booted via ONENAND. This is not a must, some SoCs need this,
923 bool "Support for booting from QSPI flash"
925 Enabling this will make a U-Boot binary that is capable of being
926 booted via QSPI flash. This is not a must, some SoCs need this,
930 bool "Support for booting from SATA"
932 Enabling this will make a U-Boot binary that is capable of being
933 booted via SATA. This is not a must, some SoCs need this,
937 bool "Support for booting from SD/EMMC"
939 Enabling this will make a U-Boot binary that is capable of being
940 booted via SD/EMMC. This is not a must, some SoCs need this,
944 bool "Support for booting from SD/EMMC and enable QSPI"
946 Enabling this will make a U-Boot binary that is capable of being
947 booted via SD/EMMC while enabling QSPI on the platform as well. This
948 is not a must, some SoCs need this, some not.
951 bool "Support for booting from SPI flash"
953 Enabling this will make a U-Boot binary that is capable of being
954 booted via SPI flash. This is not a must, some SoCs need this,
959 menu "Autoboot options"
965 This enables the autoboot. See doc/README.autoboot for detail.
968 int "delay in seconds before automatically booting"
972 Delay before automatically running bootcmd;
973 set to 0 to autoboot with no delay, but you can stop it by key input.
974 set to -1 to disable autoboot.
975 set to -2 to autoboot with no delay and not check for abort
977 If this value is >= 0 then it is also used for the default delay
978 before starting the default entry in bootmenu. If it is < 0 then
979 a default value of 10s is used.
981 See doc/README.autoboot for details.
983 config AUTOBOOT_KEYED
984 bool "Stop autobooting via specific input key / string"
986 This option enables stopping (aborting) of the automatic
987 boot feature only by issuing a specific input key or
988 string. If not enabled, any input key will abort the
989 U-Boot automatic booting process and bring the device
990 to the U-Boot prompt for user input.
992 config AUTOBOOT_FLUSH_STDIN
993 bool "Enable flushing stdin before starting to read the password"
994 depends on AUTOBOOT_KEYED && !SANDBOX
996 When this option is enabled stdin buffer will be flushed before
997 starting to read the password.
998 This can't be enabled for the sandbox as flushing stdin would
999 break the autoboot unit tests.
1001 config AUTOBOOT_PROMPT
1002 string "Autoboot stop prompt"
1003 depends on AUTOBOOT_KEYED
1004 default "Autoboot in %d seconds\\n"
1006 This string is displayed before the boot delay selected by
1007 CONFIG_BOOTDELAY starts. If it is not defined there is no
1008 output indicating that autoboot is in progress.
1010 Note that this define is used as the (only) argument to a
1011 printf() call, so it may contain '%' format specifications,
1012 provided that it also includes, sepearated by commas exactly
1013 like in a printf statement, the required arguments. It is
1014 the responsibility of the user to select only such arguments
1015 that are valid in the given context.
1017 config AUTOBOOT_ENCRYPTION
1018 bool "Enable encryption in autoboot stopping"
1019 depends on AUTOBOOT_KEYED
1021 This option allows a string to be entered into U-Boot to stop the
1023 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1025 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1026 to the crypt-based functionality and be compared against the
1027 string in the environment variable 'bootstopkeycrypt'.
1028 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1029 and compared against the hash in the environment variable
1030 'bootstopkeysha256'.
1031 If it matches in either case then boot stops and
1032 a command-line prompt is presented.
1033 This provides a way to ship a secure production device which can also
1034 be accessed at the U-Boot command line.
1036 config AUTOBOOT_SHA256_FALLBACK
1037 bool "Allow fallback from crypt-hashed password to sha256"
1038 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1040 This option adds support to fall back from crypt-hashed
1041 passwords to checking a SHA256 hashed password in case the
1042 'bootstopusesha256' environment variable is set to 'true'.
1044 config AUTOBOOT_DELAY_STR
1045 string "Delay autobooting via specific input key / string"
1046 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1048 This option delays the automatic boot feature by issuing
1049 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1050 or the environment variable "bootdelaykey" is specified
1051 and this string is received from console input before
1052 autoboot starts booting, U-Boot gives a command prompt. The
1053 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1054 used, otherwise it never times out.
1056 config AUTOBOOT_STOP_STR
1057 string "Stop autobooting via specific input key / string"
1058 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1060 This option enables stopping (aborting) of the automatic
1061 boot feature only by issuing a specific input key or
1062 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1063 variable "bootstopkey" is specified and this string is
1064 received from console input before autoboot starts booting,
1065 U-Boot gives a command prompt. The U-Boot prompt never
1066 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1068 config AUTOBOOT_KEYED_CTRLC
1069 bool "Enable Ctrl-C autoboot interruption"
1070 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1072 This option allows for the boot sequence to be interrupted
1073 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1074 Setting this variable provides an escape sequence from the
1075 limited "password" strings.
1077 config AUTOBOOT_NEVER_TIMEOUT
1078 bool "Make the password entry never time-out"
1079 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1081 This option removes the timeout from the password entry
1082 when the user first presses the <Enter> key before entering
1083 any other character.
1085 config AUTOBOOT_STOP_STR_ENABLE
1086 bool "Enable fixed string to stop autobooting"
1087 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1089 This option enables the feature to add a fixed stop
1090 string that is defined at compile time.
1091 In every case it will be tried to load the stop
1092 string from the environment.
1093 In case this is enabled and there is no stop string
1094 in the environment, this will be used as default value.
1096 config AUTOBOOT_STOP_STR_CRYPT
1097 string "Stop autobooting via crypt-hashed password"
1098 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1100 This option adds the feature to only stop the autobooting,
1101 and therefore boot into the U-Boot prompt, when the input
1102 string / password matches a values that is hashed via
1103 one of the supported crypt-style password hashing options
1104 and saved in the environment variable "bootstopkeycrypt".
1106 config AUTOBOOT_STOP_STR_SHA256
1107 string "Stop autobooting via SHA256 hashed password"
1108 depends on AUTOBOOT_STOP_STR_ENABLE
1110 This option adds the feature to only stop the autobooting,
1111 and therefore boot into the U-Boot prompt, when the input
1112 string / password matches a values that is encypted via
1113 a SHA256 hash and saved in the environment variable
1114 "bootstopkeysha256". If the value in that variable
1115 includes a ":", the portion prior to the ":" will be treated
1118 config AUTOBOOT_USE_MENUKEY
1119 bool "Allow a specify key to run a menu from the environment"
1120 depends on !AUTOBOOT_KEYED
1122 If a specific key is pressed to stop autoboot, then the commands in
1123 the environment variable 'menucmd' are executed before boot starts.
1125 config AUTOBOOT_MENUKEY
1126 int "ASCII value of boot key to show a menu"
1128 depends on AUTOBOOT_USE_MENUKEY
1130 If this key is pressed to stop autoboot, then the commands in the
1131 environment variable 'menucmd' will be executed before boot starts.
1132 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1135 config AUTOBOOT_MENU_SHOW
1136 bool "Show a menu on boot"
1137 depends on CMD_BOOTMENU
1139 This enables the boot menu, controlled by environment variables
1140 defined by the board. The menu starts after running the 'preboot'
1141 environmnent variable (if enabled) and before handling the boot delay.
1142 See README.bootmenu for more details.
1145 bool "Boot retry feature"
1147 Allow for having the U-Boot command prompt time out and attempt
1148 to boot again. If the environment variable "bootretry" is found then
1149 its value is used, otherwise the retry timeout is
1150 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1151 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1153 config BOOT_RETRY_TIME
1154 int "Timeout in seconds before attempting to boot again"
1155 depends on BOOT_RETRY
1157 Time in seconds before the U-Boot prompt will timeout and boot will
1160 config BOOT_RETRY_MIN
1161 int "Minimum timeout in seconds for 'bootretry'"
1162 depends on BOOT_RETRY
1163 default BOOT_RETRY_TIME
1165 The minimum time in seconds that "bootretry" can be set to.
1167 config RESET_TO_RETRY
1168 bool "Reset the board to retry autoboot"
1169 depends on BOOT_RETRY
1171 After the countdown timed out, the board will be reset to restart
1176 menu "Image support"
1178 config IMAGE_PRE_LOAD
1179 bool "Image pre-load support"
1181 Enable an image pre-load stage in the SPL.
1182 This pre-load stage allows to do some manipulation
1183 or check (for example signature check) on an image
1184 before launching it.
1186 config SPL_IMAGE_PRE_LOAD
1187 bool "Image pre-load support within SPL"
1188 depends on SPL && IMAGE_PRE_LOAD
1190 Enable an image pre-load stage in the SPL.
1191 This pre-load stage allows to do some manipulation
1192 or check (for example signature check) on an image
1193 before launching it.
1195 config IMAGE_PRE_LOAD_SIG
1196 bool "Image pre-load signature support"
1197 depends on IMAGE_PRE_LOAD
1198 select FIT_SIGNATURE
1200 select RSA_VERIFY_WITH_PKEY
1202 Enable signature check support in the pre-load stage.
1203 For this feature a very simple header is added before
1204 the image with few fields:
1208 All other information (header size, type of signature,
1209 ...) are provided in the node /image/pre-load/sig of
1212 config SPL_IMAGE_PRE_LOAD_SIG
1213 bool "Image pre-load signature support witin SPL"
1214 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1215 select SPL_FIT_SIGNATURE
1217 select SPL_RSA_VERIFY_WITH_PKEY
1219 Enable signature check support in the pre-load stage in the SPL.
1220 For this feature a very simple header is added before
1221 the image with few fields:
1225 All other information (header size, type of signature,
1226 ...) are provided in the node /image/pre-load/sig of
1232 bool "Enable boot arguments"
1234 Provide boot arguments to bootm command. Boot arguments are specified
1235 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1236 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1237 will be undefined and won't take any space in U-Boot image.
1240 string "Boot arguments"
1241 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1243 This can be used to pass arguments to the bootm command. The value of
1244 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1245 this value will also override the "chosen" node in FDT blob.
1247 config BOOTARGS_SUBST
1248 bool "Support substituting strings in boot arguments"
1250 This allows substituting string values in the boot arguments. These
1251 are applied after the commandline has been built.
1253 One use for this is to insert the root-disk UUID into the command
1254 line where bootargs contains "root=${uuid}"
1256 setenv bootargs "console= root=${uuid}"
1257 # Set the 'uuid' environment variable
1258 part uuid mmc 2:2 uuid
1260 # Command-line substitution will put the real uuid into the
1261 # kernel command line
1264 config USE_BOOTCOMMAND
1265 bool "Enable a default value for bootcmd"
1267 Provide a default value for the bootcmd entry in the environment. If
1268 autoboot is enabled this is what will be run automatically. Enable
1269 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1270 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1271 won't take any space in U-Boot image.
1274 string "bootcmd value"
1275 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1276 default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL
1277 default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL
1278 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1280 This is the string of commands that will be used as bootcmd and if
1281 AUTOBOOT is set, automatically run.
1284 bool "Enable preboot"
1286 When this option is enabled, the existence of the environment
1287 variable "preboot" will be checked immediately before starting the
1288 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1289 entering interactive mode.
1291 This feature is especially useful when "preboot" is automatically
1292 generated or modified. For example, the boot code can modify the
1293 "preboot" when a user holds down a certain combination of keys.
1296 string "preboot default value"
1297 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1298 default "usb start" if USB_KEYBOARD
1301 This is the default of "preboot" environment variable.
1303 config DEFAULT_FDT_FILE
1304 string "Default fdt file"
1306 This option is used to set the default fdt file to boot OS.
1308 config SAVE_PREV_BL_FDT_ADDR
1310 bool "Saves fdt address, passed by the previous bootloader, to env var"
1312 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1313 enable this option to save fdt address, passed by the
1314 previous bootloader for future use.
1315 Address is saved to `prevbl_fdt_addr` environment variable.
1317 If no fdt was provided by previous bootloader, no env variables
1320 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1322 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1324 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1325 enable this option to save initramfs address, passed by the
1326 previous bootloader for future use.
1327 Address is saved to `prevbl_initrd_start_addr` environment variable.
1329 If no initramfs was provided by previous bootloader, no env variables