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 BOOTMETH_DISTRO
332 bool "Bootdev support for distro boot"
336 Enables support for distro boot using bootdevs. This makes the
337 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
340 This provides a way to try out standard boot on an existing boot flow.
342 config BOOTMETH_DISTRO_PXE
343 bool "Bootdev support for distro boot over network"
344 depends on CMD_PXE && CMD_NET && DM_ETH
347 Enables support for distro boot using bootdevs. This makes the
348 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
350 This provides a way to try out standard boot on an existing boot flow.
352 config BOOTMETH_EFILOADER
353 bool "Bootdev support for EFI boot"
354 depends on CMD_BOOTEFI
357 Enables support for EFI boot using bootdevs. This makes the
358 bootdevs look for a 'boot<arch>.efi' on each filesystem
359 they scan. The resulting file is booted after enabling U-Boot's
362 The <arch> depends on the architecture of the board:
364 aa64 - aarch64 (ARM 64-bit)
368 riscv32 - RISC-V 32-bit
369 riscv64 - RISC-V 64-bit
371 This provides a way to try out standard boot on an existing boot flow.
373 config BOOTMETH_SANDBOX
377 This is a sandbox bootmeth driver used for testing. It always returns
378 -ENOTSUPP when attempting to boot.
380 config BOOTMETH_SCRIPT
381 bool "Bootdev support for U-Boot scripts"
382 default y if BOOTSTD_FULL
384 Enables support for booting a distro via a U-Boot script. This makes
385 the bootdevs look for a 'boot/boot.scr' file which can be used to
388 This provides a way to try out standard boot on an existing boot flow.
389 It is not enabled by default to save space.
393 config LEGACY_IMAGE_FORMAT
394 bool "Enable support for the legacy image format"
395 default y if !FIT_SIGNATURE
397 This option enables the legacy image format. It is enabled by
398 default for backward compatibility, unless FIT_SIGNATURE is
399 set where it is disabled so that unsigned images cannot be
400 loaded. If a board needs the legacy image format support in this
401 case, enable it here.
403 config SUPPORT_RAW_INITRD
404 bool "Enable raw initrd images"
406 Note, defining the SUPPORT_RAW_INITRD allows user to supply
407 kernel with raw initrd images. The syntax is slightly different, the
408 address of the initrd must be augmented by it's size, in the following
409 format: "<initrd address>:<initrd size>".
411 config OF_BOARD_SETUP
412 bool "Set up board-specific details in device tree before boot"
415 This causes U-Boot to call ft_board_setup() before booting into
416 the Operating System. This function can set up various
417 board-specific information in the device tree for use by the OS.
418 The device tree is then passed to the OS.
420 config OF_SYSTEM_SETUP
421 bool "Set up system-specific details in device tree before boot"
424 This causes U-Boot to call ft_system_setup() before booting into
425 the Operating System. This function can set up various
426 system-specific information in the device tree for use by the OS.
427 The device tree is then passed to the OS.
429 config OF_STDOUT_VIA_ALIAS
430 bool "Update the device-tree stdout alias from U-Boot"
433 This uses U-Boot's serial alias from the aliases node to update
434 the device tree passed to the OS. The "linux,stdout-path" property
435 in the chosen node is set to point to the correct serial node.
436 This option currently references CONFIG_CONS_INDEX, which is
437 incorrect when used with device tree as this option does not
438 exist / should not be used.
440 config SYS_EXTRA_OPTIONS
441 string "Extra Options (DEPRECATED)"
443 The old configuration infrastructure (= mkconfig + boards.cfg)
444 provided the extra options field. If you have something like
445 "HAS_BAR,BAZ=64", the optional options
447 #define CONFIG_BAZ 64
448 will be defined in include/config.h.
449 This option was prepared for the smooth migration from the old
450 configuration to Kconfig. Since this option will be removed sometime,
451 new boards should not use this option.
453 config HAVE_SYS_TEXT_BASE
455 depends on !NIOS2 && !XTENSA
460 depends on HAVE_SYS_TEXT_BASE
461 default 0x0 if POSITION_INDEPENDENT
462 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
463 default 0x81700000 if MACH_SUNIV
464 default 0x2a000000 if MACH_SUN9I
465 default 0x42e00000 if MACH_SUN8I_V3S
466 default 0x4a000000 if ARCH_SUNXI
469 The address in memory that U-Boot will be running from, initially.
471 config HAVE_SYS_MONITOR_BASE
473 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
474 || FLASH_PIC32 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
478 config SYS_MONITOR_BASE
479 depends on HAVE_SYS_MONITOR_BASE
480 hex "Physical start address of boot monitor code"
481 default SYS_TEXT_BASE
483 The physical start address of boot monitor code (which is the same as
484 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
485 when booting from flash.
487 config SPL_SYS_MONITOR_BASE
488 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
489 hex "Physical start address of SPL monitor code"
490 default SPL_TEXT_BASE
492 config TPL_SYS_MONITOR_BASE
493 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
494 hex "Physical start address of TPL monitor code"
496 config DYNAMIC_SYS_CLK_FREQ
497 bool "Determine CPU clock frequency at run-time"
499 Implement a get_board_sys_clk function that will determine the CPU
500 clock frequency at run time, rather than define it statically.
503 depends on !DYNAMIC_SYS_CLK_FREQ
504 int "CPU clock frequency"
505 default 125000000 if ARCH_LS1012A
506 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
507 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
508 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
509 default 66660000 if ARCH_T2080
510 default 33333333 if RCAR_GEN3
511 default 24000000 if ARCH_EXYNOS
512 default 20000000 if RCAR_GEN2
515 A static value for the CPU frequency. Note that if not required
516 for a given SoC, this can be left at 0.
518 config ARCH_FIXUP_FDT_MEMORY
519 bool "Enable arch_fixup_memory_banks() call"
522 Enable FDT memory map syncup before OS boot. This feature can be
523 used for booting OS with different memory setup where the part of
524 the memory location should be used for different purpose.
527 bool "Support booting Chrome OS"
529 Chrome OS requires U-Boot to set up a table indicating the boot mode
530 (e.g. Developer mode) and a few other things. Enable this if you are
531 booting on a Chromebook to avoid getting an error about an invalid
534 config CHROMEOS_VBOOT
535 bool "Support Chrome OS verified boot"
537 This is intended to enable the full Chrome OS verified boot support
538 in U-Boot. It is not actually implemented in the U-Boot source code
539 at present, so this option is always set to 'n'. It allows
540 distinguishing between booting Chrome OS in a basic way (developer
541 mode) and a full boot.
544 bool "Freescale PBL(pre-boot loader) image format support"
546 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
547 For more details refer to doc/README.pblimage
550 prompt "Freescale PBL load location"
551 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
552 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
556 bool "Freescale PBL is found on SD card"
559 bool "Freescale PBL is found on SPI flash"
563 config SYS_FSL_PBL_PBI
564 string "PBI(pre-boot instructions) commands for the PBL image"
565 depends on RAMBOOT_PBL
567 PBI commands can be used to configure SoC before it starts the execution.
568 Please refer doc/README.pblimage for more details.
570 config SYS_FSL_PBL_RCW
571 string "Aadditional RCW (Power on reset configuration) for the PBL image"
572 depends on RAMBOOT_PBL
574 Enables addition of RCW (Power on reset configuration) in built image.
575 Please refer doc/README.pblimage for more details.
577 endmenu # Boot images
582 bool "Boot timing and reporting"
584 Enable recording of boot time while booting. To use it, insert
585 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
586 bootstage.h. Only a single entry is recorded for each ID. You can
587 give the entry a name with bootstage_mark_name(). You can also
588 record elapsed time in a particular stage using bootstage_start()
589 before starting and bootstage_accum() when finished. Bootstage will
590 add up all the accumulated time and report it.
592 Normally, IDs are defined in bootstage.h but a small number of
593 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
596 Calls to show_boot_progress() will also result in log entries but
597 these will not have names.
600 bool "Boot timing and reported in SPL"
603 Enable recording of boot time in SPL. To make this visible to U-Boot
604 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
605 information when SPL finishes and load it when U-Boot proper starts
609 bool "Boot timing and reported in TPL"
612 Enable recording of boot time in SPL. To make this visible to U-Boot
613 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
614 information when TPL finishes and load it when U-Boot proper starts
617 config BOOTSTAGE_REPORT
618 bool "Display a detailed boot timing report before booting the OS"
621 Enable output of a boot time report just before the OS is booted.
622 This shows how long it took U-Boot to go through each stage of the
623 boot process. The report looks something like this:
625 Timer summary in microseconds:
628 3,575,678 3,575,678 board_init_f start
629 3,575,695 17 arch_cpu_init A9
630 3,575,777 82 arch_cpu_init done
631 3,659,598 83,821 board_init_r start
632 3,910,375 250,777 main_loop
633 29,916,167 26,005,792 bootm_start
634 30,361,327 445,160 start_kernel
636 config BOOTSTAGE_RECORD_COUNT
637 int "Number of boot stage records to store"
641 This is the size of the bootstage record list and is the maximum
642 number of bootstage records that can be recorded.
644 config SPL_BOOTSTAGE_RECORD_COUNT
645 int "Number of boot stage records to store for SPL"
646 depends on SPL_BOOTSTAGE
649 This is the size of the bootstage record list and is the maximum
650 number of bootstage records that can be recorded.
652 config TPL_BOOTSTAGE_RECORD_COUNT
653 int "Number of boot stage records to store for TPL"
654 depends on TPL_BOOTSTAGE
657 This is the size of the bootstage record list and is the maximum
658 number of bootstage records that can be recorded.
661 bool "Store boot timing information in the OS device tree"
664 Stash the bootstage information in the FDT. A root 'bootstage'
665 node is created with each bootstage id as a child. Each child
666 has a 'name' property and either 'mark' containing the
667 mark time in microseconds, or 'accum' containing the
668 accumulated time for that bootstage id in microseconds.
673 name = "board_init_f";
682 Code in the Linux kernel can find this in /proc/devicetree.
684 config BOOTSTAGE_STASH
685 bool "Stash the boot timing information in memory before booting OS"
688 Some OSes do not support device tree. Bootstage can instead write
689 the boot timing information in a binary format at a given address.
690 This happens through a call to bootstage_stash(), typically in
691 the CPU's cleanup_before_linux() function. You can use the
692 'bootstage stash' and 'bootstage unstash' commands to do this on
695 config BOOTSTAGE_STASH_ADDR
696 hex "Address to stash boot timing information"
699 Provide an address which will not be overwritten by the OS when it
700 starts, so that it can read this information when ready.
702 config BOOTSTAGE_STASH_SIZE
703 hex "Size of boot timing stash region"
706 This should be large enough to hold the bootstage stash. A value of
707 4096 (4KiB) is normally plenty.
709 config SHOW_BOOT_PROGRESS
710 bool "Show boot progress in a board-specific manner"
712 Defining this option allows to add some board-specific code (calling
713 a user-provided function show_boot_progress(int) that enables you to
714 show the system's boot progress on some display (for example, some
715 LEDs) on your board. At the moment, the following checkpoints are
718 Legacy uImage format:
721 1 common/cmd_bootm.c before attempting to boot an image
722 -1 common/cmd_bootm.c Image header has bad magic number
723 2 common/cmd_bootm.c Image header has correct magic number
724 -2 common/cmd_bootm.c Image header has bad checksum
725 3 common/cmd_bootm.c Image header has correct checksum
726 -3 common/cmd_bootm.c Image data has bad checksum
727 4 common/cmd_bootm.c Image data has correct checksum
728 -4 common/cmd_bootm.c Image is for unsupported architecture
729 5 common/cmd_bootm.c Architecture check OK
730 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
731 6 common/cmd_bootm.c Image Type check OK
732 -6 common/cmd_bootm.c gunzip uncompression error
733 -7 common/cmd_bootm.c Unimplemented compression type
734 7 common/cmd_bootm.c Uncompression OK
735 8 common/cmd_bootm.c No uncompress/copy overwrite error
736 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
738 9 common/image.c Start initial ramdisk verification
739 -10 common/image.c Ramdisk header has bad magic number
740 -11 common/image.c Ramdisk header has bad checksum
741 10 common/image.c Ramdisk header is OK
742 -12 common/image.c Ramdisk data has bad checksum
743 11 common/image.c Ramdisk data has correct checksum
744 12 common/image.c Ramdisk verification complete, start loading
745 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
746 13 common/image.c Start multifile image verification
747 14 common/image.c No initial ramdisk, no multifile, continue.
749 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
751 -30 arch/powerpc/lib/board.c Fatal error, hang the system
752 -31 post/post.c POST test failed, detected by post_output_backlog()
753 -32 post/post.c POST test failed, detected by post_run_single()
755 34 common/cmd_doc.c before loading a Image from a DOC device
756 -35 common/cmd_doc.c Bad usage of "doc" command
757 35 common/cmd_doc.c correct usage of "doc" command
758 -36 common/cmd_doc.c No boot device
759 36 common/cmd_doc.c correct boot device
760 -37 common/cmd_doc.c Unknown Chip ID on boot device
761 37 common/cmd_doc.c correct chip ID found, device available
762 -38 common/cmd_doc.c Read Error on boot device
763 38 common/cmd_doc.c reading Image header from DOC device OK
764 -39 common/cmd_doc.c Image header has bad magic number
765 39 common/cmd_doc.c Image header has correct magic number
766 -40 common/cmd_doc.c Error reading Image from DOC device
767 40 common/cmd_doc.c Image header has correct magic number
768 41 common/cmd_ide.c before loading a Image from a IDE device
769 -42 common/cmd_ide.c Bad usage of "ide" command
770 42 common/cmd_ide.c correct usage of "ide" command
771 -43 common/cmd_ide.c No boot device
772 43 common/cmd_ide.c boot device found
773 -44 common/cmd_ide.c Device not available
774 44 common/cmd_ide.c Device available
775 -45 common/cmd_ide.c wrong partition selected
776 45 common/cmd_ide.c partition selected
777 -46 common/cmd_ide.c Unknown partition table
778 46 common/cmd_ide.c valid partition table found
779 -47 common/cmd_ide.c Invalid partition type
780 47 common/cmd_ide.c correct partition type
781 -48 common/cmd_ide.c Error reading Image Header on boot device
782 48 common/cmd_ide.c reading Image Header from IDE device OK
783 -49 common/cmd_ide.c Image header has bad magic number
784 49 common/cmd_ide.c Image header has correct magic number
785 -50 common/cmd_ide.c Image header has bad checksum
786 50 common/cmd_ide.c Image header has correct checksum
787 -51 common/cmd_ide.c Error reading Image from IDE device
788 51 common/cmd_ide.c reading Image from IDE device OK
789 52 common/cmd_nand.c before loading a Image from a NAND device
790 -53 common/cmd_nand.c Bad usage of "nand" command
791 53 common/cmd_nand.c correct usage of "nand" command
792 -54 common/cmd_nand.c No boot device
793 54 common/cmd_nand.c boot device found
794 -55 common/cmd_nand.c Unknown Chip ID on boot device
795 55 common/cmd_nand.c correct chip ID found, device available
796 -56 common/cmd_nand.c Error reading Image Header on boot device
797 56 common/cmd_nand.c reading Image Header from NAND device OK
798 -57 common/cmd_nand.c Image header has bad magic number
799 57 common/cmd_nand.c Image header has correct magic number
800 -58 common/cmd_nand.c Error reading Image from NAND device
801 58 common/cmd_nand.c reading Image from NAND device OK
803 -60 common/env_common.c Environment has a bad CRC, using default
805 64 net/eth.c starting with Ethernet configuration.
806 -64 net/eth.c no Ethernet found.
807 65 net/eth.c Ethernet found.
809 -80 common/cmd_net.c usage wrong
810 80 common/cmd_net.c before calling net_loop()
811 -81 common/cmd_net.c some error in net_loop() occurred
812 81 common/cmd_net.c net_loop() back without error
813 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
814 82 common/cmd_net.c trying automatic boot
815 83 common/cmd_net.c running "source" command
816 -83 common/cmd_net.c some error in automatic boot or "source" command
817 84 common/cmd_net.c end without errors
822 100 common/cmd_bootm.c Kernel FIT Image has correct format
823 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
824 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
825 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
826 102 common/cmd_bootm.c Kernel unit name specified
827 -103 common/cmd_bootm.c Can't get kernel subimage node offset
828 103 common/cmd_bootm.c Found configuration node
829 104 common/cmd_bootm.c Got kernel subimage node offset
830 -104 common/cmd_bootm.c Kernel subimage hash verification failed
831 105 common/cmd_bootm.c Kernel subimage hash verification OK
832 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
833 106 common/cmd_bootm.c Architecture check OK
834 -106 common/cmd_bootm.c Kernel subimage has wrong type
835 107 common/cmd_bootm.c Kernel subimage type OK
836 -107 common/cmd_bootm.c Can't get kernel subimage data/size
837 108 common/cmd_bootm.c Got kernel subimage data/size
838 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
839 -109 common/cmd_bootm.c Can't get kernel subimage type
840 -110 common/cmd_bootm.c Can't get kernel subimage comp
841 -111 common/cmd_bootm.c Can't get kernel subimage os
842 -112 common/cmd_bootm.c Can't get kernel subimage load address
843 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
845 120 common/image.c Start initial ramdisk verification
846 -120 common/image.c Ramdisk FIT image has incorrect format
847 121 common/image.c Ramdisk FIT image has correct format
848 122 common/image.c No ramdisk subimage unit name, using configuration
849 -122 common/image.c Can't get configuration for ramdisk subimage
850 123 common/image.c Ramdisk unit name specified
851 -124 common/image.c Can't get ramdisk subimage node offset
852 125 common/image.c Got ramdisk subimage node offset
853 -125 common/image.c Ramdisk subimage hash verification failed
854 126 common/image.c Ramdisk subimage hash verification OK
855 -126 common/image.c Ramdisk subimage for unsupported architecture
856 127 common/image.c Architecture check OK
857 -127 common/image.c Can't get ramdisk subimage data/size
858 128 common/image.c Got ramdisk subimage data/size
859 129 common/image.c Can't get ramdisk load address
860 -129 common/image.c Got ramdisk load address
862 -130 common/cmd_doc.c Incorrect FIT image format
863 131 common/cmd_doc.c FIT image format OK
865 -140 common/cmd_ide.c Incorrect FIT image format
866 141 common/cmd_ide.c FIT image format OK
868 -150 common/cmd_nand.c Incorrect FIT image format
869 151 common/cmd_nand.c FIT image format OK
871 config SPL_SHOW_BOOT_PROGRESS
872 bool "Show boot progress in a board-specific manner in SPL"
875 Defining this option allows to add some board-specific code (calling
876 a user-provided function show_boot_progress(int) that enables you to
877 show the system's boot progress on some display (for example, some
878 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
885 bool "Support for booting from NOR flash"
888 Enabling this will make a U-Boot binary that is capable of being
889 booted via NOR. In this case we will enable certain pinmux early
890 as the ROM only partially sets up pinmux. We also default to using
894 bool "Support for booting from NAND flash"
897 Enabling this will make a U-Boot binary that is capable of being
898 booted via NAND flash. This is not a must, some SoCs need this,
902 bool "Support for booting from ONENAND"
905 Enabling this will make a U-Boot binary that is capable of being
906 booted via ONENAND. This is not a must, some SoCs need this,
910 bool "Support for booting from QSPI flash"
912 Enabling this will make a U-Boot binary that is capable of being
913 booted via QSPI flash. This is not a must, some SoCs need this,
917 bool "Support for booting from SATA"
919 Enabling this will make a U-Boot binary that is capable of being
920 booted via SATA. This is not a must, some SoCs need this,
924 bool "Support for booting from SD/EMMC"
926 Enabling this will make a U-Boot binary that is capable of being
927 booted via SD/EMMC. This is not a must, some SoCs need this,
931 bool "Support for booting from SD/EMMC and enable QSPI"
933 Enabling this will make a U-Boot binary that is capable of being
934 booted via SD/EMMC while enabling QSPI on the platform as well. This
935 is not a must, some SoCs need this, some not.
938 bool "Support for booting from SPI flash"
940 Enabling this will make a U-Boot binary that is capable of being
941 booted via SPI flash. This is not a must, some SoCs need this,
946 menu "Autoboot options"
952 This enables the autoboot. See doc/README.autoboot for detail.
955 int "delay in seconds before automatically booting"
959 Delay before automatically running bootcmd;
960 set to 0 to autoboot with no delay, but you can stop it by key input.
961 set to -1 to disable autoboot.
962 set to -2 to autoboot with no delay and not check for abort
964 If this value is >= 0 then it is also used for the default delay
965 before starting the default entry in bootmenu. If it is < 0 then
966 a default value of 10s is used.
968 See doc/README.autoboot for details.
970 config AUTOBOOT_KEYED
971 bool "Stop autobooting via specific input key / string"
973 This option enables stopping (aborting) of the automatic
974 boot feature only by issuing a specific input key or
975 string. If not enabled, any input key will abort the
976 U-Boot automatic booting process and bring the device
977 to the U-Boot prompt for user input.
979 config AUTOBOOT_FLUSH_STDIN
980 bool "Enable flushing stdin before starting to read the password"
981 depends on AUTOBOOT_KEYED && !SANDBOX
983 When this option is enabled stdin buffer will be flushed before
984 starting to read the password.
985 This can't be enabled for the sandbox as flushing stdin would
986 break the autoboot unit tests.
988 config AUTOBOOT_PROMPT
989 string "Autoboot stop prompt"
990 depends on AUTOBOOT_KEYED
991 default "Autoboot in %d seconds\\n"
993 This string is displayed before the boot delay selected by
994 CONFIG_BOOTDELAY starts. If it is not defined there is no
995 output indicating that autoboot is in progress.
997 Note that this define is used as the (only) argument to a
998 printf() call, so it may contain '%' format specifications,
999 provided that it also includes, sepearated by commas exactly
1000 like in a printf statement, the required arguments. It is
1001 the responsibility of the user to select only such arguments
1002 that are valid in the given context.
1004 config AUTOBOOT_ENCRYPTION
1005 bool "Enable encryption in autoboot stopping"
1006 depends on AUTOBOOT_KEYED
1008 This option allows a string to be entered into U-Boot to stop the
1010 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1012 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1013 to the crypt-based functionality and be compared against the
1014 string in the environment variable 'bootstopkeycrypt'.
1015 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1016 and compared against the hash in the environment variable
1017 'bootstopkeysha256'.
1018 If it matches in either case then boot stops and
1019 a command-line prompt is presented.
1020 This provides a way to ship a secure production device which can also
1021 be accessed at the U-Boot command line.
1023 config AUTOBOOT_SHA256_FALLBACK
1024 bool "Allow fallback from crypt-hashed password to sha256"
1025 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1027 This option adds support to fall back from crypt-hashed
1028 passwords to checking a SHA256 hashed password in case the
1029 'bootstopusesha256' environment variable is set to 'true'.
1031 config AUTOBOOT_DELAY_STR
1032 string "Delay autobooting via specific input key / string"
1033 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1035 This option delays the automatic boot feature by issuing
1036 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1037 or the environment variable "bootdelaykey" is specified
1038 and this string is received from console input before
1039 autoboot starts booting, U-Boot gives a command prompt. The
1040 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1041 used, otherwise it never times out.
1043 config AUTOBOOT_STOP_STR
1044 string "Stop autobooting via specific input key / string"
1045 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1047 This option enables stopping (aborting) of the automatic
1048 boot feature only by issuing a specific input key or
1049 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1050 variable "bootstopkey" is specified and this string is
1051 received from console input before autoboot starts booting,
1052 U-Boot gives a command prompt. The U-Boot prompt never
1053 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1055 config AUTOBOOT_KEYED_CTRLC
1056 bool "Enable Ctrl-C autoboot interruption"
1057 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1059 This option allows for the boot sequence to be interrupted
1060 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1061 Setting this variable provides an escape sequence from the
1062 limited "password" strings.
1064 config AUTOBOOT_NEVER_TIMEOUT
1065 bool "Make the password entry never time-out"
1066 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1068 This option removes the timeout from the password entry
1069 when the user first presses the <Enter> key before entering
1070 any other character.
1072 config AUTOBOOT_STOP_STR_ENABLE
1073 bool "Enable fixed string to stop autobooting"
1074 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1076 This option enables the feature to add a fixed stop
1077 string that is defined at compile time.
1078 In every case it will be tried to load the stop
1079 string from the environment.
1080 In case this is enabled and there is no stop string
1081 in the environment, this will be used as default value.
1083 config AUTOBOOT_STOP_STR_CRYPT
1084 string "Stop autobooting via crypt-hashed password"
1085 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1087 This option adds the feature to only stop the autobooting,
1088 and therefore boot into the U-Boot prompt, when the input
1089 string / password matches a values that is hashed via
1090 one of the supported crypt-style password hashing options
1091 and saved in the environment variable "bootstopkeycrypt".
1093 config AUTOBOOT_STOP_STR_SHA256
1094 string "Stop autobooting via SHA256 hashed password"
1095 depends on AUTOBOOT_STOP_STR_ENABLE
1097 This option adds the feature to only stop the autobooting,
1098 and therefore boot into the U-Boot prompt, when the input
1099 string / password matches a values that is encypted via
1100 a SHA256 hash and saved in the environment variable
1101 "bootstopkeysha256". If the value in that variable
1102 includes a ":", the portion prior to the ":" will be treated
1105 config AUTOBOOT_USE_MENUKEY
1106 bool "Allow a specify key to run a menu from the environment"
1107 depends on !AUTOBOOT_KEYED
1109 If a specific key is pressed to stop autoboot, then the commands in
1110 the environment variable 'menucmd' are executed before boot starts.
1112 config AUTOBOOT_MENUKEY
1113 int "ASCII value of boot key to show a menu"
1115 depends on AUTOBOOT_USE_MENUKEY
1117 If this key is pressed to stop autoboot, then the commands in the
1118 environment variable 'menucmd' will be executed before boot starts.
1119 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1122 config AUTOBOOT_MENU_SHOW
1123 bool "Show a menu on boot"
1124 depends on CMD_BOOTMENU
1126 This enables the boot menu, controlled by environment variables
1127 defined by the board. The menu starts after running the 'preboot'
1128 environmnent variable (if enabled) and before handling the boot delay.
1129 See README.bootmenu for more details.
1132 bool "Boot retry feature"
1134 Allow for having the U-Boot command prompt time out and attempt
1135 to boot again. If the environment variable "bootretry" is found then
1136 its value is used, otherwise the retry timeout is
1137 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1138 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1140 config BOOT_RETRY_TIME
1141 int "Timeout in seconds before attempting to boot again"
1142 depends on BOOT_RETRY
1144 Time in seconds before the U-Boot prompt will timeout and boot will
1147 config BOOT_RETRY_MIN
1148 int "Minimum timeout in seconds for 'bootretry'"
1149 depends on BOOT_RETRY
1150 default BOOT_RETRY_TIME
1152 The minimum time in seconds that "bootretry" can be set to.
1154 config RESET_TO_RETRY
1155 bool "Reset the board to retry autoboot"
1156 depends on BOOT_RETRY
1158 After the countdown timed out, the board will be reset to restart
1163 menu "Image support"
1165 config IMAGE_PRE_LOAD
1166 bool "Image pre-load support"
1168 Enable an image pre-load stage in the SPL.
1169 This pre-load stage allows to do some manipulation
1170 or check (for example signature check) on an image
1171 before launching it.
1173 config SPL_IMAGE_PRE_LOAD
1174 bool "Image pre-load support within SPL"
1175 depends on SPL && IMAGE_PRE_LOAD
1177 Enable an image pre-load stage in the SPL.
1178 This pre-load stage allows to do some manipulation
1179 or check (for example signature check) on an image
1180 before launching it.
1182 config IMAGE_PRE_LOAD_SIG
1183 bool "Image pre-load signature support"
1184 depends on IMAGE_PRE_LOAD
1185 select FIT_SIGNATURE
1187 select RSA_VERIFY_WITH_PKEY
1189 Enable signature check support in the pre-load stage.
1190 For this feature a very simple header is added before
1191 the image with few fields:
1195 All other information (header size, type of signature,
1196 ...) are provided in the node /image/pre-load/sig of
1199 config SPL_IMAGE_PRE_LOAD_SIG
1200 bool "Image pre-load signature support witin SPL"
1201 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1202 select SPL_FIT_SIGNATURE
1204 select SPL_RSA_VERIFY_WITH_PKEY
1206 Enable signature check support in the pre-load stage in the SPL.
1207 For this feature a very simple header is added before
1208 the image with few fields:
1212 All other information (header size, type of signature,
1213 ...) are provided in the node /image/pre-load/sig of
1219 bool "Enable boot arguments"
1221 Provide boot arguments to bootm command. Boot arguments are specified
1222 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1223 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1224 will be undefined and won't take any space in U-Boot image.
1227 string "Boot arguments"
1228 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1230 This can be used to pass arguments to the bootm command. The value of
1231 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1232 this value will also override the "chosen" node in FDT blob.
1234 config BOOTARGS_SUBST
1235 bool "Support substituting strings in boot arguments"
1237 This allows substituting string values in the boot arguments. These
1238 are applied after the commandline has been built.
1240 One use for this is to insert the root-disk UUID into the command
1241 line where bootargs contains "root=${uuid}"
1243 setenv bootargs "console= root=${uuid}"
1244 # Set the 'uuid' environment variable
1245 part uuid mmc 2:2 uuid
1247 # Command-line substitution will put the real uuid into the
1248 # kernel command line
1251 config USE_BOOTCOMMAND
1252 bool "Enable a default value for bootcmd"
1254 Provide a default value for the bootcmd entry in the environment. If
1255 autoboot is enabled this is what will be run automatically. Enable
1256 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1257 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1258 won't take any space in U-Boot image.
1261 string "bootcmd value"
1262 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1263 default "run distro_bootcmd" if DISTRO_DEFAULTS
1265 This is the string of commands that will be used as bootcmd and if
1266 AUTOBOOT is set, automatically run.
1269 bool "Enable preboot"
1271 When this option is enabled, the existence of the environment
1272 variable "preboot" will be checked immediately before starting the
1273 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1274 entering interactive mode.
1276 This feature is especially useful when "preboot" is automatically
1277 generated or modified. For example, the boot code can modify the
1278 "preboot" when a user holds down a certain combination of keys.
1281 string "preboot default value"
1282 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1283 default "usb start" if USB_KEYBOARD
1286 This is the default of "preboot" environment variable.
1288 config DEFAULT_FDT_FILE
1289 string "Default fdt file"
1291 This option is used to set the default fdt file to boot OS.
1293 config SAVE_PREV_BL_FDT_ADDR
1295 bool "Saves fdt address, passed by the previous bootloader, to env var"
1297 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1298 enable this option to save fdt address, passed by the
1299 previous bootloader for future use.
1300 Address is saved to `prevbl_fdt_addr` environment variable.
1302 If no fdt was provided by previous bootloader, no env variables
1305 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1307 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1309 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1310 enable this option to save initramfs address, passed by the
1311 previous bootloader for future use.
1312 Address is saved to `prevbl_initrd_start_addr` environment variable.
1314 If no initramfs was provided by previous bootloader, no env variables