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.
301 Utilities for parsing PXE file formats.
304 bool "Standard boot support"
306 depends on DM && OF_CONTROL && BLK
308 U-Boot supports a standard way of locating something to boot,
309 typically an Operating System such as Linux, provided by a distro such
310 as Arch Linux or Debian. Enable this to support iterating through
311 available bootdevs and using bootmeths to find bootflows suitable for
314 Standard boot is not a standard way of booting, just a framework
315 within U-Boot for supporting all the different ways that exist.
319 - bootdev - a device which can hold a distro (e.g. MMC)
320 - bootmeth - a method to scan a bootdev to find bootflows (owned by
322 - bootflow - a description of how to boot (owned by the distro)
325 bool "Enhanced features for standard boot"
328 This enables various useful features for standard boot, which are not
329 essential for operation:
331 - bootdev, bootmeth commands
332 - extra features in the bootflow command
333 - support for selecting the ordering of bootmeths ("bootmeth order")
334 - support for selecting the ordering of bootdevs using the devicetree
335 as well as the "boot_targets" environment variable
339 config BOOTSTD_BOOTCOMMAND
340 bool "Use bootstd to boot"
341 default y if !DISTRO_DEFAULTS
343 Enable this to select a default boot-command suitable for booting
344 with standard boot. This can be overridden by the board if needed,
345 but the default command should be enough for most boards which use
348 For now this is only selected if distro boot is NOT used, since
349 standard boot does not support all of the features of distro boot
352 config BOOTMETH_DISTRO
353 bool "Bootdev support for distro boot"
357 Enables support for distro boot using bootdevs. This makes the
358 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
361 This provides a way to try out standard boot on an existing boot flow.
363 config BOOTMETH_DISTRO_PXE
364 bool "Bootdev support for distro boot over network"
365 depends on CMD_PXE && CMD_NET && DM_ETH
368 Enables support for distro boot using bootdevs. This makes the
369 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
371 This provides a way to try out standard boot on an existing boot flow.
373 config BOOTMETH_EFILOADER
374 bool "Bootdev support for EFI boot"
375 depends on CMD_BOOTEFI
378 Enables support for EFI boot using bootdevs. This makes the
379 bootdevs look for a 'boot<arch>.efi' on each filesystem
380 they scan. The resulting file is booted after enabling U-Boot's
383 The <arch> depends on the architecture of the board:
385 aa64 - aarch64 (ARM 64-bit)
389 riscv32 - RISC-V 32-bit
390 riscv64 - RISC-V 64-bit
392 This provides a way to try out standard boot on an existing boot flow.
394 config BOOTMETH_SANDBOX
398 This is a sandbox bootmeth driver used for testing. It always returns
399 -ENOTSUPP when attempting to boot.
401 config BOOTMETH_SCRIPT
402 bool "Bootdev support for U-Boot scripts"
403 default y if BOOTSTD_FULL
405 Enables support for booting a distro via a U-Boot script. This makes
406 the bootdevs look for a 'boot/boot.scr' file which can be used to
409 This provides a way to try out standard boot on an existing boot flow.
410 It is not enabled by default to save space.
414 config LEGACY_IMAGE_FORMAT
415 bool "Enable support for the legacy image format"
416 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
418 This option enables the legacy image format. It is enabled by
419 default for backward compatibility, unless FIT_SIGNATURE is
420 set where it is disabled so that unsigned images cannot be
421 loaded. If a board needs the legacy image format support in this
422 case, enable it here.
424 config SUPPORT_RAW_INITRD
425 bool "Enable raw initrd images"
427 Note, defining the SUPPORT_RAW_INITRD allows user to supply
428 kernel with raw initrd images. The syntax is slightly different, the
429 address of the initrd must be augmented by it's size, in the following
430 format: "<initrd address>:<initrd size>".
432 config OF_BOARD_SETUP
433 bool "Set up board-specific details in device tree before boot"
436 This causes U-Boot to call ft_board_setup() before booting into
437 the Operating System. This function can set up various
438 board-specific information in the device tree for use by the OS.
439 The device tree is then passed to the OS.
441 config OF_SYSTEM_SETUP
442 bool "Set up system-specific details in device tree before boot"
445 This causes U-Boot to call ft_system_setup() before booting into
446 the Operating System. This function can set up various
447 system-specific information in the device tree for use by the OS.
448 The device tree is then passed to the OS.
450 config OF_STDOUT_VIA_ALIAS
451 bool "Update the device-tree stdout alias from U-Boot"
454 This uses U-Boot's serial alias from the aliases node to update
455 the device tree passed to the OS. The "linux,stdout-path" property
456 in the chosen node is set to point to the correct serial node.
457 This option currently references CONFIG_CONS_INDEX, which is
458 incorrect when used with device tree as this option does not
459 exist / should not be used.
461 config HAVE_SYS_TEXT_BASE
463 depends on !NIOS2 && !XTENSA
468 depends on HAVE_SYS_TEXT_BASE
469 default 0x0 if POSITION_INDEPENDENT
470 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
471 default 0x81700000 if MACH_SUNIV
472 default 0x2a000000 if MACH_SUN9I
473 default 0x42e00000 if MACH_SUN8I_V3S
474 default 0x4a000000 if ARCH_SUNXI
477 The address in memory that U-Boot will be running from, initially.
479 config HAVE_SYS_MONITOR_BASE
481 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
482 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
486 config SYS_MONITOR_BASE
487 depends on HAVE_SYS_MONITOR_BASE
488 hex "Physical start address of boot monitor code"
489 default SYS_TEXT_BASE
491 The physical start address of boot monitor code (which is the same as
492 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
493 when booting from flash.
495 config SPL_SYS_MONITOR_BASE
496 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
497 hex "Physical start address of SPL monitor code"
498 default SPL_TEXT_BASE
500 config TPL_SYS_MONITOR_BASE
501 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
502 hex "Physical start address of TPL monitor code"
504 config DYNAMIC_SYS_CLK_FREQ
505 bool "Determine CPU clock frequency at run-time"
507 Implement a get_board_sys_clk function that will determine the CPU
508 clock frequency at run time, rather than define it statically.
511 depends on !DYNAMIC_SYS_CLK_FREQ
512 int "CPU clock frequency"
513 default 125000000 if ARCH_LS1012A
514 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
515 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
516 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
517 default 66660000 if ARCH_T2080
518 default 33333333 if RCAR_GEN3
519 default 24000000 if ARCH_EXYNOS
520 default 20000000 if RCAR_GEN2
523 A static value for the CPU frequency. Note that if not required
524 for a given SoC, this can be left at 0.
526 config ARCH_FIXUP_FDT_MEMORY
527 bool "Enable arch_fixup_memory_banks() call"
530 Enable FDT memory map syncup before OS boot. This feature can be
531 used for booting OS with different memory setup where the part of
532 the memory location should be used for different purpose.
535 bool "Support booting Chrome OS"
537 Chrome OS requires U-Boot to set up a table indicating the boot mode
538 (e.g. Developer mode) and a few other things. Enable this if you are
539 booting on a Chromebook to avoid getting an error about an invalid
542 config CHROMEOS_VBOOT
543 bool "Support Chrome OS verified boot"
545 This is intended to enable the full Chrome OS verified boot support
546 in U-Boot. It is not actually implemented in the U-Boot source code
547 at present, so this option is always set to 'n'. It allows
548 distinguishing between booting Chrome OS in a basic way (developer
549 mode) and a full boot.
555 bool "Freescale PBL(pre-boot loader) image format support"
556 select SYS_RAMBOOT if PPC
558 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
559 For more details refer to doc/README.pblimage
562 prompt "Freescale PBL load location"
563 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
564 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
568 bool "Freescale PBL is found on SD card"
571 bool "Freescale PBL is found on SPI flash"
575 config FSL_FIXED_MMC_LOCATION
576 bool "PBL MMC is at a fixed location"
577 depends on SDCARD && !RAMBOOT_PBL
579 config ESDHC_HC_BLK_ADDR
581 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
583 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
584 code length of these soc specify the memory address in block address
585 format. Block length is fixed to 512 bytes as per the SD High
586 Capacity specification.
588 config SYS_FSL_PBL_PBI
589 string "PBI(pre-boot instructions) commands for the PBL image"
590 depends on RAMBOOT_PBL
592 PBI commands can be used to configure SoC before it starts the execution.
593 Please refer doc/README.pblimage for more details.
595 config SYS_FSL_PBL_RCW
596 string "Aadditional RCW (Power on reset configuration) for the PBL image"
597 depends on RAMBOOT_PBL
599 Enables addition of RCW (Power on reset configuration) in built image.
600 Please refer doc/README.pblimage for more details.
602 config SYS_BOOT_RAMDISK_HIGH
603 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
604 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
607 Enable initrd_high functionality. If defined then the initrd_high
608 feature is enabled and the boot* ramdisk subcommand is enabled.
610 endmenu # Boot images
615 bool "Boot timing and reporting"
617 Enable recording of boot time while booting. To use it, insert
618 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
619 bootstage.h. Only a single entry is recorded for each ID. You can
620 give the entry a name with bootstage_mark_name(). You can also
621 record elapsed time in a particular stage using bootstage_start()
622 before starting and bootstage_accum() when finished. Bootstage will
623 add up all the accumulated time and report it.
625 Normally, IDs are defined in bootstage.h but a small number of
626 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
629 Calls to show_boot_progress() will also result in log entries but
630 these will not have names.
633 bool "Boot timing and reported in SPL"
634 depends on BOOTSTAGE && SPL
636 Enable recording of boot time in SPL. To make this visible to U-Boot
637 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
638 information when SPL finishes and load it when U-Boot proper starts
642 bool "Boot timing and reported in TPL"
643 depends on BOOTSTAGE && TPL
645 Enable recording of boot time in SPL. To make this visible to U-Boot
646 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
647 information when TPL finishes and load it when U-Boot proper starts
650 config BOOTSTAGE_REPORT
651 bool "Display a detailed boot timing report before booting the OS"
654 Enable output of a boot time report just before the OS is booted.
655 This shows how long it took U-Boot to go through each stage of the
656 boot process. The report looks something like this:
658 Timer summary in microseconds:
661 3,575,678 3,575,678 board_init_f start
662 3,575,695 17 arch_cpu_init A9
663 3,575,777 82 arch_cpu_init done
664 3,659,598 83,821 board_init_r start
665 3,910,375 250,777 main_loop
666 29,916,167 26,005,792 bootm_start
667 30,361,327 445,160 start_kernel
669 config BOOTSTAGE_RECORD_COUNT
670 int "Number of boot stage records to store"
674 This is the size of the bootstage record list and is the maximum
675 number of bootstage records that can be recorded.
677 config SPL_BOOTSTAGE_RECORD_COUNT
678 int "Number of boot stage records to store for SPL"
679 depends on SPL_BOOTSTAGE
682 This is the size of the bootstage record list and is the maximum
683 number of bootstage records that can be recorded.
685 config TPL_BOOTSTAGE_RECORD_COUNT
686 int "Number of boot stage records to store for TPL"
687 depends on TPL_BOOTSTAGE
690 This is the size of the bootstage record list and is the maximum
691 number of bootstage records that can be recorded.
694 bool "Store boot timing information in the OS device tree"
697 Stash the bootstage information in the FDT. A root 'bootstage'
698 node is created with each bootstage id as a child. Each child
699 has a 'name' property and either 'mark' containing the
700 mark time in microseconds, or 'accum' containing the
701 accumulated time for that bootstage id in microseconds.
706 name = "board_init_f";
715 Code in the Linux kernel can find this in /proc/devicetree.
717 config BOOTSTAGE_STASH
718 bool "Stash the boot timing information in memory before booting OS"
721 Some OSes do not support device tree. Bootstage can instead write
722 the boot timing information in a binary format at a given address.
723 This happens through a call to bootstage_stash(), typically in
724 the CPU's cleanup_before_linux() function. You can use the
725 'bootstage stash' and 'bootstage unstash' commands to do this on
728 config BOOTSTAGE_STASH_ADDR
729 hex "Address to stash boot timing information"
732 Provide an address which will not be overwritten by the OS when it
733 starts, so that it can read this information when ready.
735 config BOOTSTAGE_STASH_SIZE
736 hex "Size of boot timing stash region"
739 This should be large enough to hold the bootstage stash. A value of
740 4096 (4KiB) is normally plenty.
742 config SHOW_BOOT_PROGRESS
743 bool "Show boot progress in a board-specific manner"
745 Defining this option allows to add some board-specific code (calling
746 a user-provided function show_boot_progress(int) that enables you to
747 show the system's boot progress on some display (for example, some
748 LEDs) on your board. At the moment, the following checkpoints are
751 Legacy uImage format:
754 1 common/cmd_bootm.c before attempting to boot an image
755 -1 common/cmd_bootm.c Image header has bad magic number
756 2 common/cmd_bootm.c Image header has correct magic number
757 -2 common/cmd_bootm.c Image header has bad checksum
758 3 common/cmd_bootm.c Image header has correct checksum
759 -3 common/cmd_bootm.c Image data has bad checksum
760 4 common/cmd_bootm.c Image data has correct checksum
761 -4 common/cmd_bootm.c Image is for unsupported architecture
762 5 common/cmd_bootm.c Architecture check OK
763 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
764 6 common/cmd_bootm.c Image Type check OK
765 -6 common/cmd_bootm.c gunzip uncompression error
766 -7 common/cmd_bootm.c Unimplemented compression type
767 7 common/cmd_bootm.c Uncompression OK
768 8 common/cmd_bootm.c No uncompress/copy overwrite error
769 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
771 9 common/image.c Start initial ramdisk verification
772 -10 common/image.c Ramdisk header has bad magic number
773 -11 common/image.c Ramdisk header has bad checksum
774 10 common/image.c Ramdisk header is OK
775 -12 common/image.c Ramdisk data has bad checksum
776 11 common/image.c Ramdisk data has correct checksum
777 12 common/image.c Ramdisk verification complete, start loading
778 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
779 13 common/image.c Start multifile image verification
780 14 common/image.c No initial ramdisk, no multifile, continue.
782 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
784 -30 arch/powerpc/lib/board.c Fatal error, hang the system
785 -31 post/post.c POST test failed, detected by post_output_backlog()
786 -32 post/post.c POST test failed, detected by post_run_single()
788 34 common/cmd_doc.c before loading a Image from a DOC device
789 -35 common/cmd_doc.c Bad usage of "doc" command
790 35 common/cmd_doc.c correct usage of "doc" command
791 -36 common/cmd_doc.c No boot device
792 36 common/cmd_doc.c correct boot device
793 -37 common/cmd_doc.c Unknown Chip ID on boot device
794 37 common/cmd_doc.c correct chip ID found, device available
795 -38 common/cmd_doc.c Read Error on boot device
796 38 common/cmd_doc.c reading Image header from DOC device OK
797 -39 common/cmd_doc.c Image header has bad magic number
798 39 common/cmd_doc.c Image header has correct magic number
799 -40 common/cmd_doc.c Error reading Image from DOC device
800 40 common/cmd_doc.c Image header has correct magic number
801 41 common/cmd_ide.c before loading a Image from a IDE device
802 -42 common/cmd_ide.c Bad usage of "ide" command
803 42 common/cmd_ide.c correct usage of "ide" command
804 -43 common/cmd_ide.c No boot device
805 43 common/cmd_ide.c boot device found
806 -44 common/cmd_ide.c Device not available
807 44 common/cmd_ide.c Device available
808 -45 common/cmd_ide.c wrong partition selected
809 45 common/cmd_ide.c partition selected
810 -46 common/cmd_ide.c Unknown partition table
811 46 common/cmd_ide.c valid partition table found
812 -47 common/cmd_ide.c Invalid partition type
813 47 common/cmd_ide.c correct partition type
814 -48 common/cmd_ide.c Error reading Image Header on boot device
815 48 common/cmd_ide.c reading Image Header from IDE device OK
816 -49 common/cmd_ide.c Image header has bad magic number
817 49 common/cmd_ide.c Image header has correct magic number
818 -50 common/cmd_ide.c Image header has bad checksum
819 50 common/cmd_ide.c Image header has correct checksum
820 -51 common/cmd_ide.c Error reading Image from IDE device
821 51 common/cmd_ide.c reading Image from IDE device OK
822 52 common/cmd_nand.c before loading a Image from a NAND device
823 -53 common/cmd_nand.c Bad usage of "nand" command
824 53 common/cmd_nand.c correct usage of "nand" command
825 -54 common/cmd_nand.c No boot device
826 54 common/cmd_nand.c boot device found
827 -55 common/cmd_nand.c Unknown Chip ID on boot device
828 55 common/cmd_nand.c correct chip ID found, device available
829 -56 common/cmd_nand.c Error reading Image Header on boot device
830 56 common/cmd_nand.c reading Image Header from NAND device OK
831 -57 common/cmd_nand.c Image header has bad magic number
832 57 common/cmd_nand.c Image header has correct magic number
833 -58 common/cmd_nand.c Error reading Image from NAND device
834 58 common/cmd_nand.c reading Image from NAND device OK
836 -60 common/env_common.c Environment has a bad CRC, using default
838 64 net/eth.c starting with Ethernet configuration.
839 -64 net/eth.c no Ethernet found.
840 65 net/eth.c Ethernet found.
842 -80 common/cmd_net.c usage wrong
843 80 common/cmd_net.c before calling net_loop()
844 -81 common/cmd_net.c some error in net_loop() occurred
845 81 common/cmd_net.c net_loop() back without error
846 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
847 82 common/cmd_net.c trying automatic boot
848 83 common/cmd_net.c running "source" command
849 -83 common/cmd_net.c some error in automatic boot or "source" command
850 84 common/cmd_net.c end without errors
855 100 common/cmd_bootm.c Kernel FIT Image has correct format
856 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
857 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
858 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
859 102 common/cmd_bootm.c Kernel unit name specified
860 -103 common/cmd_bootm.c Can't get kernel subimage node offset
861 103 common/cmd_bootm.c Found configuration node
862 104 common/cmd_bootm.c Got kernel subimage node offset
863 -104 common/cmd_bootm.c Kernel subimage hash verification failed
864 105 common/cmd_bootm.c Kernel subimage hash verification OK
865 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
866 106 common/cmd_bootm.c Architecture check OK
867 -106 common/cmd_bootm.c Kernel subimage has wrong type
868 107 common/cmd_bootm.c Kernel subimage type OK
869 -107 common/cmd_bootm.c Can't get kernel subimage data/size
870 108 common/cmd_bootm.c Got kernel subimage data/size
871 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
872 -109 common/cmd_bootm.c Can't get kernel subimage type
873 -110 common/cmd_bootm.c Can't get kernel subimage comp
874 -111 common/cmd_bootm.c Can't get kernel subimage os
875 -112 common/cmd_bootm.c Can't get kernel subimage load address
876 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
878 120 common/image.c Start initial ramdisk verification
879 -120 common/image.c Ramdisk FIT image has incorrect format
880 121 common/image.c Ramdisk FIT image has correct format
881 122 common/image.c No ramdisk subimage unit name, using configuration
882 -122 common/image.c Can't get configuration for ramdisk subimage
883 123 common/image.c Ramdisk unit name specified
884 -124 common/image.c Can't get ramdisk subimage node offset
885 125 common/image.c Got ramdisk subimage node offset
886 -125 common/image.c Ramdisk subimage hash verification failed
887 126 common/image.c Ramdisk subimage hash verification OK
888 -126 common/image.c Ramdisk subimage for unsupported architecture
889 127 common/image.c Architecture check OK
890 -127 common/image.c Can't get ramdisk subimage data/size
891 128 common/image.c Got ramdisk subimage data/size
892 129 common/image.c Can't get ramdisk load address
893 -129 common/image.c Got ramdisk load address
895 -130 common/cmd_doc.c Incorrect FIT image format
896 131 common/cmd_doc.c FIT image format OK
898 -140 common/cmd_ide.c Incorrect FIT image format
899 141 common/cmd_ide.c FIT image format OK
901 -150 common/cmd_nand.c Incorrect FIT image format
902 151 common/cmd_nand.c FIT image format OK
904 config SPL_SHOW_BOOT_PROGRESS
905 bool "Show boot progress in a board-specific manner in SPL"
908 Defining this option allows to add some board-specific code (calling
909 a user-provided function show_boot_progress(int) that enables you to
910 show the system's boot progress on some display (for example, some
911 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
918 bool "Support for booting from NOR flash"
921 Enabling this will make a U-Boot binary that is capable of being
922 booted via NOR. In this case we will enable certain pinmux early
923 as the ROM only partially sets up pinmux. We also default to using
927 bool "Support for booting from NAND flash"
930 Enabling this will make a U-Boot binary that is capable of being
931 booted via NAND flash. This is not a must, some SoCs need this,
935 bool "Support for booting from ONENAND"
938 Enabling this will make a U-Boot binary that is capable of being
939 booted via ONENAND. This is not a must, some SoCs need this,
943 bool "Support for booting from QSPI flash"
945 Enabling this will make a U-Boot binary that is capable of being
946 booted via QSPI flash. This is not a must, some SoCs need this,
950 bool "Support for booting from SATA"
952 Enabling this will make a U-Boot binary that is capable of being
953 booted via SATA. This is not a must, some SoCs need this,
957 bool "Support for booting from SD/EMMC"
959 Enabling this will make a U-Boot binary that is capable of being
960 booted via SD/EMMC. This is not a must, some SoCs need this,
964 bool "Support for booting from SD/EMMC and enable QSPI"
966 Enabling this will make a U-Boot binary that is capable of being
967 booted via SD/EMMC while enabling QSPI on the platform as well. This
968 is not a must, some SoCs need this, some not.
971 bool "Support for booting from SPI flash"
973 Enabling this will make a U-Boot binary that is capable of being
974 booted via SPI flash. This is not a must, some SoCs need this,
979 menu "Autoboot options"
985 This enables the autoboot. See doc/README.autoboot for detail.
988 int "delay in seconds before automatically booting"
992 Delay before automatically running bootcmd;
993 set to 0 to autoboot with no delay, but you can stop it by key input.
994 set to -1 to disable autoboot.
995 set to -2 to autoboot with no delay and not check for abort
997 If this value is >= 0 then it is also used for the default delay
998 before starting the default entry in bootmenu. If it is < 0 then
999 a default value of 10s is used.
1001 See doc/README.autoboot for details.
1003 config AUTOBOOT_KEYED
1004 bool "Stop autobooting via specific input key / string"
1006 This option enables stopping (aborting) of the automatic
1007 boot feature only by issuing a specific input key or
1008 string. If not enabled, any input key will abort the
1009 U-Boot automatic booting process and bring the device
1010 to the U-Boot prompt for user input.
1012 config AUTOBOOT_FLUSH_STDIN
1013 bool "Enable flushing stdin before starting to read the password"
1014 depends on AUTOBOOT_KEYED && !SANDBOX
1016 When this option is enabled stdin buffer will be flushed before
1017 starting to read the password.
1018 This can't be enabled for the sandbox as flushing stdin would
1019 break the autoboot unit tests.
1021 config AUTOBOOT_PROMPT
1022 string "Autoboot stop prompt"
1023 depends on AUTOBOOT_KEYED
1024 default "Autoboot in %d seconds\\n"
1026 This string is displayed before the boot delay selected by
1027 CONFIG_BOOTDELAY starts. If it is not defined there is no
1028 output indicating that autoboot is in progress.
1030 Note that this define is used as the (only) argument to a
1031 printf() call, so it may contain '%' format specifications,
1032 provided that it also includes, sepearated by commas exactly
1033 like in a printf statement, the required arguments. It is
1034 the responsibility of the user to select only such arguments
1035 that are valid in the given context.
1037 config AUTOBOOT_ENCRYPTION
1038 bool "Enable encryption in autoboot stopping"
1039 depends on AUTOBOOT_KEYED
1041 This option allows a string to be entered into U-Boot to stop the
1043 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1045 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1046 to the crypt-based functionality and be compared against the
1047 string in the environment variable 'bootstopkeycrypt'.
1048 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1049 and compared against the hash in the environment variable
1050 'bootstopkeysha256'.
1051 If it matches in either case then boot stops and
1052 a command-line prompt is presented.
1053 This provides a way to ship a secure production device which can also
1054 be accessed at the U-Boot command line.
1056 config AUTOBOOT_SHA256_FALLBACK
1057 bool "Allow fallback from crypt-hashed password to sha256"
1058 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1060 This option adds support to fall back from crypt-hashed
1061 passwords to checking a SHA256 hashed password in case the
1062 'bootstopusesha256' environment variable is set to 'true'.
1064 config AUTOBOOT_DELAY_STR
1065 string "Delay autobooting via specific input key / string"
1066 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1068 This option delays the automatic boot feature by issuing
1069 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1070 or the environment variable "bootdelaykey" is specified
1071 and this string is received from console input before
1072 autoboot starts booting, U-Boot gives a command prompt. The
1073 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1074 used, otherwise it never times out.
1076 config AUTOBOOT_STOP_STR
1077 string "Stop autobooting via specific input key / string"
1078 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1080 This option enables stopping (aborting) of the automatic
1081 boot feature only by issuing a specific input key or
1082 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1083 variable "bootstopkey" is specified and this string is
1084 received from console input before autoboot starts booting,
1085 U-Boot gives a command prompt. The U-Boot prompt never
1086 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1088 config AUTOBOOT_KEYED_CTRLC
1089 bool "Enable Ctrl-C autoboot interruption"
1090 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1092 This option allows for the boot sequence to be interrupted
1093 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1094 Setting this variable provides an escape sequence from the
1095 limited "password" strings.
1097 config AUTOBOOT_NEVER_TIMEOUT
1098 bool "Make the password entry never time-out"
1099 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1101 This option removes the timeout from the password entry
1102 when the user first presses the <Enter> key before entering
1103 any other character.
1105 config AUTOBOOT_STOP_STR_ENABLE
1106 bool "Enable fixed string to stop autobooting"
1107 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1109 This option enables the feature to add a fixed stop
1110 string that is defined at compile time.
1111 In every case it will be tried to load the stop
1112 string from the environment.
1113 In case this is enabled and there is no stop string
1114 in the environment, this will be used as default value.
1116 config AUTOBOOT_STOP_STR_CRYPT
1117 string "Stop autobooting via crypt-hashed password"
1118 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1120 This option adds the feature to only stop the autobooting,
1121 and therefore boot into the U-Boot prompt, when the input
1122 string / password matches a values that is hashed via
1123 one of the supported crypt-style password hashing options
1124 and saved in the environment variable "bootstopkeycrypt".
1126 config AUTOBOOT_STOP_STR_SHA256
1127 string "Stop autobooting via SHA256 hashed password"
1128 depends on AUTOBOOT_STOP_STR_ENABLE
1130 This option adds the feature to only stop the autobooting,
1131 and therefore boot into the U-Boot prompt, when the input
1132 string / password matches a values that is encypted via
1133 a SHA256 hash and saved in the environment variable
1134 "bootstopkeysha256". If the value in that variable
1135 includes a ":", the portion prior to the ":" will be treated
1138 config AUTOBOOT_USE_MENUKEY
1139 bool "Allow a specify key to run a menu from the environment"
1140 depends on !AUTOBOOT_KEYED
1142 If a specific key is pressed to stop autoboot, then the commands in
1143 the environment variable 'menucmd' are executed before boot starts.
1145 config AUTOBOOT_MENUKEY
1146 int "ASCII value of boot key to show a menu"
1148 depends on AUTOBOOT_USE_MENUKEY
1150 If this key is pressed to stop autoboot, then the commands in the
1151 environment variable 'menucmd' will be executed before boot starts.
1152 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1155 config AUTOBOOT_MENU_SHOW
1156 bool "Show a menu on boot"
1157 depends on CMD_BOOTMENU
1159 This enables the boot menu, controlled by environment variables
1160 defined by the board. The menu starts after running the 'preboot'
1161 environmnent variable (if enabled) and before handling the boot delay.
1162 See README.bootmenu for more details.
1164 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1165 bool "Disallow bootmenu to enter the U-Boot console"
1166 depends on AUTOBOOT_MENU_SHOW
1168 If this option is enabled, user can not enter the U-Boot console from
1169 bootmenu. It increases the system security.
1172 bool "Boot retry feature"
1174 Allow for having the U-Boot command prompt time out and attempt
1175 to boot again. If the environment variable "bootretry" is found then
1176 its value is used, otherwise the retry timeout is
1177 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1178 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1180 config BOOT_RETRY_TIME
1181 int "Timeout in seconds before attempting to boot again"
1182 depends on BOOT_RETRY
1184 Time in seconds before the U-Boot prompt will timeout and boot will
1187 config BOOT_RETRY_MIN
1188 int "Minimum timeout in seconds for 'bootretry'"
1189 depends on BOOT_RETRY
1190 default BOOT_RETRY_TIME
1192 The minimum time in seconds that "bootretry" can be set to.
1194 config RESET_TO_RETRY
1195 bool "Reset the board to retry autoboot"
1196 depends on BOOT_RETRY
1198 After the countdown timed out, the board will be reset to restart
1203 menu "Image support"
1205 config IMAGE_PRE_LOAD
1206 bool "Image pre-load support"
1208 Enable an image pre-load stage in the SPL.
1209 This pre-load stage allows to do some manipulation
1210 or check (for example signature check) on an image
1211 before launching it.
1213 config SPL_IMAGE_PRE_LOAD
1214 bool "Image pre-load support within SPL"
1215 depends on SPL && IMAGE_PRE_LOAD
1217 Enable an image pre-load stage in the SPL.
1218 This pre-load stage allows to do some manipulation
1219 or check (for example signature check) on an image
1220 before launching it.
1222 config IMAGE_PRE_LOAD_SIG
1223 bool "Image pre-load signature support"
1224 depends on IMAGE_PRE_LOAD
1225 select FIT_SIGNATURE
1227 select RSA_VERIFY_WITH_PKEY
1229 Enable signature check support in the pre-load stage.
1230 For this feature a very simple header is added before
1231 the image with few fields:
1235 All other information (header size, type of signature,
1236 ...) are provided in the node /image/pre-load/sig of
1239 config SPL_IMAGE_PRE_LOAD_SIG
1240 bool "Image pre-load signature support witin SPL"
1241 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1242 select SPL_FIT_SIGNATURE
1244 select SPL_RSA_VERIFY_WITH_PKEY
1246 Enable signature check support in the pre-load stage in the SPL.
1247 For this feature a very simple header is added before
1248 the image with few fields:
1252 All other information (header size, type of signature,
1253 ...) are provided in the node /image/pre-load/sig of
1259 bool "Enable boot arguments"
1261 Provide boot arguments to bootm command. Boot arguments are specified
1262 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1263 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1264 will be undefined and won't take any space in U-Boot image.
1267 string "Boot arguments"
1268 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1270 This can be used to pass arguments to the bootm command. The value of
1271 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1272 this value will also override the "chosen" node in FDT blob.
1274 config BOOTARGS_SUBST
1275 bool "Support substituting strings in boot arguments"
1277 This allows substituting string values in the boot arguments. These
1278 are applied after the commandline has been built.
1280 One use for this is to insert the root-disk UUID into the command
1281 line where bootargs contains "root=${uuid}"
1283 setenv bootargs "console= root=${uuid}"
1284 # Set the 'uuid' environment variable
1285 part uuid mmc 2:2 uuid
1287 # Command-line substitution will put the real uuid into the
1288 # kernel command line
1291 config USE_BOOTCOMMAND
1292 bool "Enable a default value for bootcmd"
1294 Provide a default value for the bootcmd entry in the environment. If
1295 autoboot is enabled this is what will be run automatically. Enable
1296 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1297 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1298 won't take any space in U-Boot image.
1301 string "bootcmd value"
1302 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1303 default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL
1304 default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL
1305 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1307 This is the string of commands that will be used as bootcmd and if
1308 AUTOBOOT is set, automatically run.
1311 bool "Enable preboot"
1313 When this option is enabled, the existence of the environment
1314 variable "preboot" will be checked immediately before starting the
1315 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1316 entering interactive mode.
1318 This feature is especially useful when "preboot" is automatically
1319 generated or modified. For example, the boot code can modify the
1320 "preboot" when a user holds down a certain combination of keys.
1323 string "preboot default value"
1324 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1325 default "usb start" if USB_KEYBOARD
1328 This is the default of "preboot" environment variable.
1330 config DEFAULT_FDT_FILE
1331 string "Default fdt file"
1333 This option is used to set the default fdt file to boot OS.
1335 config SAVE_PREV_BL_FDT_ADDR
1337 bool "Saves fdt address, passed by the previous bootloader, to env var"
1339 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1340 enable this option to save fdt address, passed by the
1341 previous bootloader for future use.
1342 Address is saved to `prevbl_fdt_addr` environment variable.
1344 If no fdt was provided by previous bootloader, no env variables
1347 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1349 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1351 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1352 enable this option to save initramfs address, passed by the
1353 previous bootloader for future use.
1354 Address is saved to `prevbl_initrd_start_addr` environment variable.
1356 If no initramfs was provided by previous bootloader, no env variables