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.
382 config LEGACY_IMAGE_FORMAT
383 bool "Enable support for the legacy image format"
384 default y if !FIT_SIGNATURE
386 This option enables the legacy image format. It is enabled by
387 default for backward compatibility, unless FIT_SIGNATURE is
388 set where it is disabled so that unsigned images cannot be
389 loaded. If a board needs the legacy image format support in this
390 case, enable it here.
392 config SUPPORT_RAW_INITRD
393 bool "Enable raw initrd images"
395 Note, defining the SUPPORT_RAW_INITRD allows user to supply
396 kernel with raw initrd images. The syntax is slightly different, the
397 address of the initrd must be augmented by it's size, in the following
398 format: "<initrd address>:<initrd size>".
400 config OF_BOARD_SETUP
401 bool "Set up board-specific details in device tree before boot"
404 This causes U-Boot to call ft_board_setup() before booting into
405 the Operating System. This function can set up various
406 board-specific information in the device tree for use by the OS.
407 The device tree is then passed to the OS.
409 config OF_SYSTEM_SETUP
410 bool "Set up system-specific details in device tree before boot"
413 This causes U-Boot to call ft_system_setup() before booting into
414 the Operating System. This function can set up various
415 system-specific information in the device tree for use by the OS.
416 The device tree is then passed to the OS.
418 config OF_STDOUT_VIA_ALIAS
419 bool "Update the device-tree stdout alias from U-Boot"
422 This uses U-Boot's serial alias from the aliases node to update
423 the device tree passed to the OS. The "linux,stdout-path" property
424 in the chosen node is set to point to the correct serial node.
425 This option currently references CONFIG_CONS_INDEX, which is
426 incorrect when used with device tree as this option does not
427 exist / should not be used.
429 config SYS_EXTRA_OPTIONS
430 string "Extra Options (DEPRECATED)"
432 The old configuration infrastructure (= mkconfig + boards.cfg)
433 provided the extra options field. If you have something like
434 "HAS_BAR,BAZ=64", the optional options
436 #define CONFIG_BAZ 64
437 will be defined in include/config.h.
438 This option was prepared for the smooth migration from the old
439 configuration to Kconfig. Since this option will be removed sometime,
440 new boards should not use this option.
442 config HAVE_SYS_TEXT_BASE
444 depends on !NIOS2 && !XTENSA
449 depends on HAVE_SYS_TEXT_BASE
450 default 0x0 if POSITION_INDEPENDENT
451 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
452 default 0x81700000 if MACH_SUNIV
453 default 0x2a000000 if MACH_SUN9I
454 default 0x42e00000 if MACH_SUN8I_V3S
455 default 0x4a000000 if ARCH_SUNXI
458 The address in memory that U-Boot will be running from, initially.
460 config HAVE_SYS_MONITOR_BASE
462 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
463 || FLASH_PIC32 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
467 config SYS_MONITOR_BASE
468 depends on HAVE_SYS_MONITOR_BASE
469 hex "Physical start address of boot monitor code"
470 default SYS_TEXT_BASE
472 The physical start address of boot monitor code (which is the same as
473 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
474 when booting from flash.
476 config SPL_SYS_MONITOR_BASE
477 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
478 hex "Physical start address of SPL monitor code"
479 default SPL_TEXT_BASE
481 config TPL_SYS_MONITOR_BASE
482 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
483 hex "Physical start address of TPL monitor code"
485 config DYNAMIC_SYS_CLK_FREQ
486 bool "Determine CPU clock frequency at run-time"
488 Implement a get_board_sys_clk function that will determine the CPU
489 clock frequency at run time, rather than define it statically.
492 depends on !DYNAMIC_SYS_CLK_FREQ
493 int "CPU clock frequency"
494 default 125000000 if ARCH_LS1012A
495 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
496 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
497 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
498 default 66660000 if ARCH_T2080
499 default 33333333 if RCAR_GEN3
500 default 24000000 if ARCH_EXYNOS
501 default 20000000 if RCAR_GEN2
504 A static value for the CPU frequency. Note that if not required
505 for a given SoC, this can be left at 0.
507 config ARCH_FIXUP_FDT_MEMORY
508 bool "Enable arch_fixup_memory_banks() call"
511 Enable FDT memory map syncup before OS boot. This feature can be
512 used for booting OS with different memory setup where the part of
513 the memory location should be used for different purpose.
516 bool "Support booting Chrome OS"
518 Chrome OS requires U-Boot to set up a table indicating the boot mode
519 (e.g. Developer mode) and a few other things. Enable this if you are
520 booting on a Chromebook to avoid getting an error about an invalid
523 config CHROMEOS_VBOOT
524 bool "Support Chrome OS verified boot"
526 This is intended to enable the full Chrome OS verified boot support
527 in U-Boot. It is not actually implemented in the U-Boot source code
528 at present, so this option is always set to 'n'. It allows
529 distinguishing between booting Chrome OS in a basic way (developer
530 mode) and a full boot.
533 bool "Freescale PBL(pre-boot loader) image format support"
535 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
536 For more details refer to doc/README.pblimage
539 prompt "Freescale PBL load location"
540 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
541 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
545 bool "Freescale PBL is found on SD card"
548 bool "Freescale PBL is found on SPI flash"
552 config SYS_FSL_PBL_PBI
553 string "PBI(pre-boot instructions) commands for the PBL image"
554 depends on RAMBOOT_PBL
556 PBI commands can be used to configure SoC before it starts the execution.
557 Please refer doc/README.pblimage for more details.
559 config SYS_FSL_PBL_RCW
560 string "Aadditional RCW (Power on reset configuration) for the PBL image"
561 depends on RAMBOOT_PBL
563 Enables addition of RCW (Power on reset configuration) in built image.
564 Please refer doc/README.pblimage for more details.
566 endmenu # Boot images
571 bool "Boot timing and reporting"
573 Enable recording of boot time while booting. To use it, insert
574 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
575 bootstage.h. Only a single entry is recorded for each ID. You can
576 give the entry a name with bootstage_mark_name(). You can also
577 record elapsed time in a particular stage using bootstage_start()
578 before starting and bootstage_accum() when finished. Bootstage will
579 add up all the accumulated time and report it.
581 Normally, IDs are defined in bootstage.h but a small number of
582 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
585 Calls to show_boot_progress() will also result in log entries but
586 these will not have names.
589 bool "Boot timing and reported in SPL"
592 Enable recording of boot time in SPL. To make this visible to U-Boot
593 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
594 information when SPL finishes and load it when U-Boot proper starts
598 bool "Boot timing and reported in TPL"
601 Enable recording of boot time in SPL. To make this visible to U-Boot
602 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
603 information when TPL finishes and load it when U-Boot proper starts
606 config BOOTSTAGE_REPORT
607 bool "Display a detailed boot timing report before booting the OS"
610 Enable output of a boot time report just before the OS is booted.
611 This shows how long it took U-Boot to go through each stage of the
612 boot process. The report looks something like this:
614 Timer summary in microseconds:
617 3,575,678 3,575,678 board_init_f start
618 3,575,695 17 arch_cpu_init A9
619 3,575,777 82 arch_cpu_init done
620 3,659,598 83,821 board_init_r start
621 3,910,375 250,777 main_loop
622 29,916,167 26,005,792 bootm_start
623 30,361,327 445,160 start_kernel
625 config BOOTSTAGE_RECORD_COUNT
626 int "Number of boot stage records to store"
630 This is the size of the bootstage record list and is the maximum
631 number of bootstage records that can be recorded.
633 config SPL_BOOTSTAGE_RECORD_COUNT
634 int "Number of boot stage records to store for SPL"
635 depends on SPL_BOOTSTAGE
638 This is the size of the bootstage record list and is the maximum
639 number of bootstage records that can be recorded.
641 config TPL_BOOTSTAGE_RECORD_COUNT
642 int "Number of boot stage records to store for TPL"
643 depends on TPL_BOOTSTAGE
646 This is the size of the bootstage record list and is the maximum
647 number of bootstage records that can be recorded.
650 bool "Store boot timing information in the OS device tree"
653 Stash the bootstage information in the FDT. A root 'bootstage'
654 node is created with each bootstage id as a child. Each child
655 has a 'name' property and either 'mark' containing the
656 mark time in microseconds, or 'accum' containing the
657 accumulated time for that bootstage id in microseconds.
662 name = "board_init_f";
671 Code in the Linux kernel can find this in /proc/devicetree.
673 config BOOTSTAGE_STASH
674 bool "Stash the boot timing information in memory before booting OS"
677 Some OSes do not support device tree. Bootstage can instead write
678 the boot timing information in a binary format at a given address.
679 This happens through a call to bootstage_stash(), typically in
680 the CPU's cleanup_before_linux() function. You can use the
681 'bootstage stash' and 'bootstage unstash' commands to do this on
684 config BOOTSTAGE_STASH_ADDR
685 hex "Address to stash boot timing information"
688 Provide an address which will not be overwritten by the OS when it
689 starts, so that it can read this information when ready.
691 config BOOTSTAGE_STASH_SIZE
692 hex "Size of boot timing stash region"
695 This should be large enough to hold the bootstage stash. A value of
696 4096 (4KiB) is normally plenty.
698 config SHOW_BOOT_PROGRESS
699 bool "Show boot progress in a board-specific manner"
701 Defining this option allows to add some board-specific code (calling
702 a user-provided function show_boot_progress(int) that enables you to
703 show the system's boot progress on some display (for example, some
704 LEDs) on your board. At the moment, the following checkpoints are
707 Legacy uImage format:
710 1 common/cmd_bootm.c before attempting to boot an image
711 -1 common/cmd_bootm.c Image header has bad magic number
712 2 common/cmd_bootm.c Image header has correct magic number
713 -2 common/cmd_bootm.c Image header has bad checksum
714 3 common/cmd_bootm.c Image header has correct checksum
715 -3 common/cmd_bootm.c Image data has bad checksum
716 4 common/cmd_bootm.c Image data has correct checksum
717 -4 common/cmd_bootm.c Image is for unsupported architecture
718 5 common/cmd_bootm.c Architecture check OK
719 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
720 6 common/cmd_bootm.c Image Type check OK
721 -6 common/cmd_bootm.c gunzip uncompression error
722 -7 common/cmd_bootm.c Unimplemented compression type
723 7 common/cmd_bootm.c Uncompression OK
724 8 common/cmd_bootm.c No uncompress/copy overwrite error
725 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
727 9 common/image.c Start initial ramdisk verification
728 -10 common/image.c Ramdisk header has bad magic number
729 -11 common/image.c Ramdisk header has bad checksum
730 10 common/image.c Ramdisk header is OK
731 -12 common/image.c Ramdisk data has bad checksum
732 11 common/image.c Ramdisk data has correct checksum
733 12 common/image.c Ramdisk verification complete, start loading
734 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
735 13 common/image.c Start multifile image verification
736 14 common/image.c No initial ramdisk, no multifile, continue.
738 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
740 -30 arch/powerpc/lib/board.c Fatal error, hang the system
741 -31 post/post.c POST test failed, detected by post_output_backlog()
742 -32 post/post.c POST test failed, detected by post_run_single()
744 34 common/cmd_doc.c before loading a Image from a DOC device
745 -35 common/cmd_doc.c Bad usage of "doc" command
746 35 common/cmd_doc.c correct usage of "doc" command
747 -36 common/cmd_doc.c No boot device
748 36 common/cmd_doc.c correct boot device
749 -37 common/cmd_doc.c Unknown Chip ID on boot device
750 37 common/cmd_doc.c correct chip ID found, device available
751 -38 common/cmd_doc.c Read Error on boot device
752 38 common/cmd_doc.c reading Image header from DOC device OK
753 -39 common/cmd_doc.c Image header has bad magic number
754 39 common/cmd_doc.c Image header has correct magic number
755 -40 common/cmd_doc.c Error reading Image from DOC device
756 40 common/cmd_doc.c Image header has correct magic number
757 41 common/cmd_ide.c before loading a Image from a IDE device
758 -42 common/cmd_ide.c Bad usage of "ide" command
759 42 common/cmd_ide.c correct usage of "ide" command
760 -43 common/cmd_ide.c No boot device
761 43 common/cmd_ide.c boot device found
762 -44 common/cmd_ide.c Device not available
763 44 common/cmd_ide.c Device available
764 -45 common/cmd_ide.c wrong partition selected
765 45 common/cmd_ide.c partition selected
766 -46 common/cmd_ide.c Unknown partition table
767 46 common/cmd_ide.c valid partition table found
768 -47 common/cmd_ide.c Invalid partition type
769 47 common/cmd_ide.c correct partition type
770 -48 common/cmd_ide.c Error reading Image Header on boot device
771 48 common/cmd_ide.c reading Image Header from IDE device OK
772 -49 common/cmd_ide.c Image header has bad magic number
773 49 common/cmd_ide.c Image header has correct magic number
774 -50 common/cmd_ide.c Image header has bad checksum
775 50 common/cmd_ide.c Image header has correct checksum
776 -51 common/cmd_ide.c Error reading Image from IDE device
777 51 common/cmd_ide.c reading Image from IDE device OK
778 52 common/cmd_nand.c before loading a Image from a NAND device
779 -53 common/cmd_nand.c Bad usage of "nand" command
780 53 common/cmd_nand.c correct usage of "nand" command
781 -54 common/cmd_nand.c No boot device
782 54 common/cmd_nand.c boot device found
783 -55 common/cmd_nand.c Unknown Chip ID on boot device
784 55 common/cmd_nand.c correct chip ID found, device available
785 -56 common/cmd_nand.c Error reading Image Header on boot device
786 56 common/cmd_nand.c reading Image Header from NAND device OK
787 -57 common/cmd_nand.c Image header has bad magic number
788 57 common/cmd_nand.c Image header has correct magic number
789 -58 common/cmd_nand.c Error reading Image from NAND device
790 58 common/cmd_nand.c reading Image from NAND device OK
792 -60 common/env_common.c Environment has a bad CRC, using default
794 64 net/eth.c starting with Ethernet configuration.
795 -64 net/eth.c no Ethernet found.
796 65 net/eth.c Ethernet found.
798 -80 common/cmd_net.c usage wrong
799 80 common/cmd_net.c before calling net_loop()
800 -81 common/cmd_net.c some error in net_loop() occurred
801 81 common/cmd_net.c net_loop() back without error
802 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
803 82 common/cmd_net.c trying automatic boot
804 83 common/cmd_net.c running "source" command
805 -83 common/cmd_net.c some error in automatic boot or "source" command
806 84 common/cmd_net.c end without errors
811 100 common/cmd_bootm.c Kernel FIT Image has correct format
812 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
813 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
814 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
815 102 common/cmd_bootm.c Kernel unit name specified
816 -103 common/cmd_bootm.c Can't get kernel subimage node offset
817 103 common/cmd_bootm.c Found configuration node
818 104 common/cmd_bootm.c Got kernel subimage node offset
819 -104 common/cmd_bootm.c Kernel subimage hash verification failed
820 105 common/cmd_bootm.c Kernel subimage hash verification OK
821 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
822 106 common/cmd_bootm.c Architecture check OK
823 -106 common/cmd_bootm.c Kernel subimage has wrong type
824 107 common/cmd_bootm.c Kernel subimage type OK
825 -107 common/cmd_bootm.c Can't get kernel subimage data/size
826 108 common/cmd_bootm.c Got kernel subimage data/size
827 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
828 -109 common/cmd_bootm.c Can't get kernel subimage type
829 -110 common/cmd_bootm.c Can't get kernel subimage comp
830 -111 common/cmd_bootm.c Can't get kernel subimage os
831 -112 common/cmd_bootm.c Can't get kernel subimage load address
832 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
834 120 common/image.c Start initial ramdisk verification
835 -120 common/image.c Ramdisk FIT image has incorrect format
836 121 common/image.c Ramdisk FIT image has correct format
837 122 common/image.c No ramdisk subimage unit name, using configuration
838 -122 common/image.c Can't get configuration for ramdisk subimage
839 123 common/image.c Ramdisk unit name specified
840 -124 common/image.c Can't get ramdisk subimage node offset
841 125 common/image.c Got ramdisk subimage node offset
842 -125 common/image.c Ramdisk subimage hash verification failed
843 126 common/image.c Ramdisk subimage hash verification OK
844 -126 common/image.c Ramdisk subimage for unsupported architecture
845 127 common/image.c Architecture check OK
846 -127 common/image.c Can't get ramdisk subimage data/size
847 128 common/image.c Got ramdisk subimage data/size
848 129 common/image.c Can't get ramdisk load address
849 -129 common/image.c Got ramdisk load address
851 -130 common/cmd_doc.c Incorrect FIT image format
852 131 common/cmd_doc.c FIT image format OK
854 -140 common/cmd_ide.c Incorrect FIT image format
855 141 common/cmd_ide.c FIT image format OK
857 -150 common/cmd_nand.c Incorrect FIT image format
858 151 common/cmd_nand.c FIT image format OK
860 config SPL_SHOW_BOOT_PROGRESS
861 bool "Show boot progress in a board-specific manner in SPL"
864 Defining this option allows to add some board-specific code (calling
865 a user-provided function show_boot_progress(int) that enables you to
866 show the system's boot progress on some display (for example, some
867 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
874 bool "Support for booting from NOR flash"
877 Enabling this will make a U-Boot binary that is capable of being
878 booted via NOR. In this case we will enable certain pinmux early
879 as the ROM only partially sets up pinmux. We also default to using
883 bool "Support for booting from NAND flash"
886 Enabling this will make a U-Boot binary that is capable of being
887 booted via NAND flash. This is not a must, some SoCs need this,
891 bool "Support for booting from ONENAND"
894 Enabling this will make a U-Boot binary that is capable of being
895 booted via ONENAND. This is not a must, some SoCs need this,
899 bool "Support for booting from QSPI flash"
901 Enabling this will make a U-Boot binary that is capable of being
902 booted via QSPI flash. This is not a must, some SoCs need this,
906 bool "Support for booting from SATA"
908 Enabling this will make a U-Boot binary that is capable of being
909 booted via SATA. This is not a must, some SoCs need this,
913 bool "Support for booting from SD/EMMC"
915 Enabling this will make a U-Boot binary that is capable of being
916 booted via SD/EMMC. This is not a must, some SoCs need this,
920 bool "Support for booting from SD/EMMC and enable QSPI"
922 Enabling this will make a U-Boot binary that is capable of being
923 booted via SD/EMMC while enabling QSPI on the platform as well. This
924 is not a must, some SoCs need this, some not.
927 bool "Support for booting from SPI flash"
929 Enabling this will make a U-Boot binary that is capable of being
930 booted via SPI flash. This is not a must, some SoCs need this,
935 menu "Autoboot options"
941 This enables the autoboot. See doc/README.autoboot for detail.
944 int "delay in seconds before automatically booting"
948 Delay before automatically running bootcmd;
949 set to 0 to autoboot with no delay, but you can stop it by key input.
950 set to -1 to disable autoboot.
951 set to -2 to autoboot with no delay and not check for abort
953 If this value is >= 0 then it is also used for the default delay
954 before starting the default entry in bootmenu. If it is < 0 then
955 a default value of 10s is used.
957 See doc/README.autoboot for details.
959 config AUTOBOOT_KEYED
960 bool "Stop autobooting via specific input key / string"
962 This option enables stopping (aborting) of the automatic
963 boot feature only by issuing a specific input key or
964 string. If not enabled, any input key will abort the
965 U-Boot automatic booting process and bring the device
966 to the U-Boot prompt for user input.
968 config AUTOBOOT_FLUSH_STDIN
969 bool "Enable flushing stdin before starting to read the password"
970 depends on AUTOBOOT_KEYED && !SANDBOX
972 When this option is enabled stdin buffer will be flushed before
973 starting to read the password.
974 This can't be enabled for the sandbox as flushing stdin would
975 break the autoboot unit tests.
977 config AUTOBOOT_PROMPT
978 string "Autoboot stop prompt"
979 depends on AUTOBOOT_KEYED
980 default "Autoboot in %d seconds\\n"
982 This string is displayed before the boot delay selected by
983 CONFIG_BOOTDELAY starts. If it is not defined there is no
984 output indicating that autoboot is in progress.
986 Note that this define is used as the (only) argument to a
987 printf() call, so it may contain '%' format specifications,
988 provided that it also includes, sepearated by commas exactly
989 like in a printf statement, the required arguments. It is
990 the responsibility of the user to select only such arguments
991 that are valid in the given context.
993 config AUTOBOOT_ENCRYPTION
994 bool "Enable encryption in autoboot stopping"
995 depends on AUTOBOOT_KEYED
997 This option allows a string to be entered into U-Boot to stop the
999 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1001 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1002 to the crypt-based functionality and be compared against the
1003 string in the environment variable 'bootstopkeycrypt'.
1004 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1005 and compared against the hash in the environment variable
1006 'bootstopkeysha256'.
1007 If it matches in either case then boot stops and
1008 a command-line prompt is presented.
1009 This provides a way to ship a secure production device which can also
1010 be accessed at the U-Boot command line.
1012 config AUTOBOOT_SHA256_FALLBACK
1013 bool "Allow fallback from crypt-hashed password to sha256"
1014 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1016 This option adds support to fall back from crypt-hashed
1017 passwords to checking a SHA256 hashed password in case the
1018 'bootstopusesha256' environment variable is set to 'true'.
1020 config AUTOBOOT_DELAY_STR
1021 string "Delay autobooting via specific input key / string"
1022 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1024 This option delays the automatic boot feature by issuing
1025 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1026 or the environment variable "bootdelaykey" is specified
1027 and this string is received from console input before
1028 autoboot starts booting, U-Boot gives a command prompt. The
1029 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1030 used, otherwise it never times out.
1032 config AUTOBOOT_STOP_STR
1033 string "Stop autobooting via specific input key / string"
1034 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1036 This option enables stopping (aborting) of the automatic
1037 boot feature only by issuing a specific input key or
1038 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1039 variable "bootstopkey" is specified and this string is
1040 received from console input before autoboot starts booting,
1041 U-Boot gives a command prompt. The U-Boot prompt never
1042 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1044 config AUTOBOOT_KEYED_CTRLC
1045 bool "Enable Ctrl-C autoboot interruption"
1046 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1048 This option allows for the boot sequence to be interrupted
1049 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1050 Setting this variable provides an escape sequence from the
1051 limited "password" strings.
1053 config AUTOBOOT_NEVER_TIMEOUT
1054 bool "Make the password entry never time-out"
1055 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1057 This option removes the timeout from the password entry
1058 when the user first presses the <Enter> key before entering
1059 any other character.
1061 config AUTOBOOT_STOP_STR_ENABLE
1062 bool "Enable fixed string to stop autobooting"
1063 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1065 This option enables the feature to add a fixed stop
1066 string that is defined at compile time.
1067 In every case it will be tried to load the stop
1068 string from the environment.
1069 In case this is enabled and there is no stop string
1070 in the environment, this will be used as default value.
1072 config AUTOBOOT_STOP_STR_CRYPT
1073 string "Stop autobooting via crypt-hashed password"
1074 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1076 This option adds the feature to only stop the autobooting,
1077 and therefore boot into the U-Boot prompt, when the input
1078 string / password matches a values that is hashed via
1079 one of the supported crypt-style password hashing options
1080 and saved in the environment variable "bootstopkeycrypt".
1082 config AUTOBOOT_STOP_STR_SHA256
1083 string "Stop autobooting via SHA256 hashed password"
1084 depends on AUTOBOOT_STOP_STR_ENABLE
1086 This option adds the feature to only stop the autobooting,
1087 and therefore boot into the U-Boot prompt, when the input
1088 string / password matches a values that is encypted via
1089 a SHA256 hash and saved in the environment variable
1090 "bootstopkeysha256". If the value in that variable
1091 includes a ":", the portion prior to the ":" will be treated
1094 config AUTOBOOT_USE_MENUKEY
1095 bool "Allow a specify key to run a menu from the environment"
1096 depends on !AUTOBOOT_KEYED
1098 If a specific key is pressed to stop autoboot, then the commands in
1099 the environment variable 'menucmd' are executed before boot starts.
1101 config AUTOBOOT_MENUKEY
1102 int "ASCII value of boot key to show a menu"
1104 depends on AUTOBOOT_USE_MENUKEY
1106 If this key is pressed to stop autoboot, then the commands in the
1107 environment variable 'menucmd' will be executed before boot starts.
1108 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1111 config AUTOBOOT_MENU_SHOW
1112 bool "Show a menu on boot"
1113 depends on CMD_BOOTMENU
1115 This enables the boot menu, controlled by environment variables
1116 defined by the board. The menu starts after running the 'preboot'
1117 environmnent variable (if enabled) and before handling the boot delay.
1118 See README.bootmenu for more details.
1121 bool "Boot retry feature"
1123 Allow for having the U-Boot command prompt time out and attempt
1124 to boot again. If the environment variable "bootretry" is found then
1125 its value is used, otherwise the retry timeout is
1126 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1127 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1129 config BOOT_RETRY_TIME
1130 int "Timeout in seconds before attempting to boot again"
1131 depends on BOOT_RETRY
1133 Time in seconds before the U-Boot prompt will timeout and boot will
1136 config BOOT_RETRY_MIN
1137 int "Minimum timeout in seconds for 'bootretry'"
1138 depends on BOOT_RETRY
1139 default BOOT_RETRY_TIME
1141 The minimum time in seconds that "bootretry" can be set to.
1143 config RESET_TO_RETRY
1144 bool "Reset the board to retry autoboot"
1145 depends on BOOT_RETRY
1147 After the countdown timed out, the board will be reset to restart
1152 menu "Image support"
1154 config IMAGE_PRE_LOAD
1155 bool "Image pre-load support"
1157 Enable an image pre-load stage in the SPL.
1158 This pre-load stage allows to do some manipulation
1159 or check (for example signature check) on an image
1160 before launching it.
1162 config SPL_IMAGE_PRE_LOAD
1163 bool "Image pre-load support within SPL"
1164 depends on SPL && IMAGE_PRE_LOAD
1166 Enable an image pre-load stage in the SPL.
1167 This pre-load stage allows to do some manipulation
1168 or check (for example signature check) on an image
1169 before launching it.
1171 config IMAGE_PRE_LOAD_SIG
1172 bool "Image pre-load signature support"
1173 depends on IMAGE_PRE_LOAD
1174 select FIT_SIGNATURE
1176 select RSA_VERIFY_WITH_PKEY
1178 Enable signature check support in the pre-load stage.
1179 For this feature a very simple header is added before
1180 the image with few fields:
1184 All other information (header size, type of signature,
1185 ...) are provided in the node /image/pre-load/sig of
1188 config SPL_IMAGE_PRE_LOAD_SIG
1189 bool "Image pre-load signature support witin SPL"
1190 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1191 select SPL_FIT_SIGNATURE
1193 select SPL_RSA_VERIFY_WITH_PKEY
1195 Enable signature check support in the pre-load stage in the SPL.
1196 For this feature a very simple header is added before
1197 the image with few fields:
1201 All other information (header size, type of signature,
1202 ...) are provided in the node /image/pre-load/sig of
1208 bool "Enable boot arguments"
1210 Provide boot arguments to bootm command. Boot arguments are specified
1211 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1212 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1213 will be undefined and won't take any space in U-Boot image.
1216 string "Boot arguments"
1217 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1219 This can be used to pass arguments to the bootm command. The value of
1220 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1221 this value will also override the "chosen" node in FDT blob.
1223 config BOOTARGS_SUBST
1224 bool "Support substituting strings in boot arguments"
1226 This allows substituting string values in the boot arguments. These
1227 are applied after the commandline has been built.
1229 One use for this is to insert the root-disk UUID into the command
1230 line where bootargs contains "root=${uuid}"
1232 setenv bootargs "console= root=${uuid}"
1233 # Set the 'uuid' environment variable
1234 part uuid mmc 2:2 uuid
1236 # Command-line substitution will put the real uuid into the
1237 # kernel command line
1240 config USE_BOOTCOMMAND
1241 bool "Enable a default value for bootcmd"
1243 Provide a default value for the bootcmd entry in the environment. If
1244 autoboot is enabled this is what will be run automatically. Enable
1245 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1246 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1247 won't take any space in U-Boot image.
1250 string "bootcmd value"
1251 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1252 default "run distro_bootcmd" if DISTRO_DEFAULTS
1254 This is the string of commands that will be used as bootcmd and if
1255 AUTOBOOT is set, automatically run.
1258 bool "Enable preboot"
1260 When this option is enabled, the existence of the environment
1261 variable "preboot" will be checked immediately before starting the
1262 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1263 entering interactive mode.
1265 This feature is especially useful when "preboot" is automatically
1266 generated or modified. For example, the boot code can modify the
1267 "preboot" when a user holds down a certain combination of keys.
1270 string "preboot default value"
1271 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1272 default "usb start" if USB_KEYBOARD
1275 This is the default of "preboot" environment variable.
1277 config DEFAULT_FDT_FILE
1278 string "Default fdt file"
1280 This option is used to set the default fdt file to boot OS.
1282 config SAVE_PREV_BL_FDT_ADDR
1284 bool "Saves fdt address, passed by the previous bootloader, to env var"
1286 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1287 enable this option to save fdt address, passed by the
1288 previous bootloader for future use.
1289 Address is saved to `prevbl_fdt_addr` environment variable.
1291 If no fdt was provided by previous bootloader, no env variables
1294 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1296 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1298 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1299 enable this option to save initramfs address, passed by the
1300 previous bootloader for future use.
1301 Address is saved to `prevbl_initrd_start_addr` environment variable.
1303 If no initramfs was provided by previous bootloader, no env variables