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, only the "compatible" = "u-boot,fpga-legacy"
214 loading method is supported.
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.
298 bool "Standard boot support"
300 depends on DM && OF_CONTROL && BLK
302 U-Boot supports a standard way of locating something to boot,
303 typically an Operating System such as Linux, provided by a distro such
304 as Arch Linux or Debian. Enable this to support iterating through
305 available bootdevs and using bootmeths to find bootflows suitable for
308 Standard boot is not a standard way of booting, just a framework
309 within U-Boot for supporting all the different ways that exist.
313 - bootdev - a device which can hold a distro (e.g. MMC)
314 - bootmeth - a method to scan a bootdev to find bootflows (owned by
316 - bootflow - a description of how to boot (owned by the distro)
319 bool "Enhanced features for standard boot"
322 This enables various useful features for standard boot, which are not
323 essential for operation:
325 - bootdev, bootmeth commands
326 - extra features in the bootflow command
327 - support for selecting the ordering of bootmeths ("bootmeth order")
328 - support for selecting the ordering of bootdevs using the devicetree
329 as well as the "boot_targets" environment variable
333 config BOOTSTD_BOOTCOMMAND
334 bool "Use bootstd to boot"
335 default y if !DISTRO_DEFAULTS
337 Enable this to select a default boot-command suitable for booting
338 with standard boot. This can be overridden by the board if needed,
339 but the default command should be enough for most boards which use
342 For now this is only selected if distro boot is NOT used, since
343 standard boot does not support all of the features of distro boot
346 config BOOTMETH_DISTRO
347 bool "Bootdev support for distro boot"
351 Enables support for distro boot using bootdevs. This makes the
352 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
355 This provides a way to try out standard boot on an existing boot flow.
357 config BOOTMETH_DISTRO_PXE
358 bool "Bootdev support for distro boot over network"
359 depends on CMD_PXE && CMD_NET && DM_ETH
362 Enables support for distro boot using bootdevs. This makes the
363 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
365 This provides a way to try out standard boot on an existing boot flow.
367 config BOOTMETH_EFILOADER
368 bool "Bootdev support for EFI boot"
369 depends on CMD_BOOTEFI
372 Enables support for EFI boot using bootdevs. This makes the
373 bootdevs look for a 'boot<arch>.efi' on each filesystem
374 they scan. The resulting file is booted after enabling U-Boot's
377 The <arch> depends on the architecture of the board:
379 aa64 - aarch64 (ARM 64-bit)
383 riscv32 - RISC-V 32-bit
384 riscv64 - RISC-V 64-bit
386 This provides a way to try out standard boot on an existing boot flow.
388 config BOOTMETH_SANDBOX
392 This is a sandbox bootmeth driver used for testing. It always returns
393 -ENOTSUPP when attempting to boot.
395 config BOOTMETH_SCRIPT
396 bool "Bootdev support for U-Boot scripts"
397 default y if BOOTSTD_FULL
399 Enables support for booting a distro via a U-Boot script. This makes
400 the bootdevs look for a 'boot/boot.scr' file which can be used to
403 This provides a way to try out standard boot on an existing boot flow.
404 It is not enabled by default to save space.
408 config LEGACY_IMAGE_FORMAT
409 bool "Enable support for the legacy image format"
410 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
412 This option enables the legacy image format. It is enabled by
413 default for backward compatibility, unless FIT_SIGNATURE is
414 set where it is disabled so that unsigned images cannot be
415 loaded. If a board needs the legacy image format support in this
416 case, enable it here.
418 config SUPPORT_RAW_INITRD
419 bool "Enable raw initrd images"
421 Note, defining the SUPPORT_RAW_INITRD allows user to supply
422 kernel with raw initrd images. The syntax is slightly different, the
423 address of the initrd must be augmented by it's size, in the following
424 format: "<initrd address>:<initrd size>".
426 config OF_BOARD_SETUP
427 bool "Set up board-specific details in device tree before boot"
430 This causes U-Boot to call ft_board_setup() before booting into
431 the Operating System. This function can set up various
432 board-specific information in the device tree for use by the OS.
433 The device tree is then passed to the OS.
435 config OF_SYSTEM_SETUP
436 bool "Set up system-specific details in device tree before boot"
439 This causes U-Boot to call ft_system_setup() before booting into
440 the Operating System. This function can set up various
441 system-specific information in the device tree for use by the OS.
442 The device tree is then passed to the OS.
444 config OF_STDOUT_VIA_ALIAS
445 bool "Update the device-tree stdout alias from U-Boot"
448 This uses U-Boot's serial alias from the aliases node to update
449 the device tree passed to the OS. The "linux,stdout-path" property
450 in the chosen node is set to point to the correct serial node.
451 This option currently references CONFIG_CONS_INDEX, which is
452 incorrect when used with device tree as this option does not
453 exist / should not be used.
455 config SYS_EXTRA_OPTIONS
456 string "Extra Options (DEPRECATED)"
458 The old configuration infrastructure (= mkconfig + boards.cfg)
459 provided the extra options field. If you have something like
460 "HAS_BAR,BAZ=64", the optional options
462 #define CONFIG_BAZ 64
463 will be defined in include/config.h.
464 This option was prepared for the smooth migration from the old
465 configuration to Kconfig. Since this option will be removed sometime,
466 new boards should not use this option.
468 config HAVE_SYS_TEXT_BASE
470 depends on !NIOS2 && !XTENSA
475 depends on HAVE_SYS_TEXT_BASE
476 default 0x0 if POSITION_INDEPENDENT
477 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
478 default 0x81700000 if MACH_SUNIV
479 default 0x2a000000 if MACH_SUN9I
480 default 0x42e00000 if MACH_SUN8I_V3S
481 default 0x4a000000 if ARCH_SUNXI
484 The address in memory that U-Boot will be running from, initially.
486 config HAVE_SYS_MONITOR_BASE
488 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
489 || FLASH_PIC32 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
493 config SYS_MONITOR_BASE
494 depends on HAVE_SYS_MONITOR_BASE
495 hex "Physical start address of boot monitor code"
496 default SYS_TEXT_BASE
498 The physical start address of boot monitor code (which is the same as
499 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
500 when booting from flash.
502 config SPL_SYS_MONITOR_BASE
503 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
504 hex "Physical start address of SPL monitor code"
505 default SPL_TEXT_BASE
507 config TPL_SYS_MONITOR_BASE
508 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
509 hex "Physical start address of TPL monitor code"
511 config DYNAMIC_SYS_CLK_FREQ
512 bool "Determine CPU clock frequency at run-time"
514 Implement a get_board_sys_clk function that will determine the CPU
515 clock frequency at run time, rather than define it statically.
518 depends on !DYNAMIC_SYS_CLK_FREQ
519 int "CPU clock frequency"
520 default 125000000 if ARCH_LS1012A
521 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
522 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
523 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
524 default 66660000 if ARCH_T2080
525 default 33333333 if RCAR_GEN3
526 default 24000000 if ARCH_EXYNOS
527 default 20000000 if RCAR_GEN2
530 A static value for the CPU frequency. Note that if not required
531 for a given SoC, this can be left at 0.
533 config ARCH_FIXUP_FDT_MEMORY
534 bool "Enable arch_fixup_memory_banks() call"
537 Enable FDT memory map syncup before OS boot. This feature can be
538 used for booting OS with different memory setup where the part of
539 the memory location should be used for different purpose.
542 bool "Support booting Chrome OS"
544 Chrome OS requires U-Boot to set up a table indicating the boot mode
545 (e.g. Developer mode) and a few other things. Enable this if you are
546 booting on a Chromebook to avoid getting an error about an invalid
549 config CHROMEOS_VBOOT
550 bool "Support Chrome OS verified boot"
552 This is intended to enable the full Chrome OS verified boot support
553 in U-Boot. It is not actually implemented in the U-Boot source code
554 at present, so this option is always set to 'n'. It allows
555 distinguishing between booting Chrome OS in a basic way (developer
556 mode) and a full boot.
559 bool "Freescale PBL(pre-boot loader) image format support"
561 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
562 For more details refer to doc/README.pblimage
565 prompt "Freescale PBL load location"
566 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
567 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
571 bool "Freescale PBL is found on SD card"
574 bool "Freescale PBL is found on SPI flash"
578 config SYS_FSL_PBL_PBI
579 string "PBI(pre-boot instructions) commands for the PBL image"
580 depends on RAMBOOT_PBL
582 PBI commands can be used to configure SoC before it starts the execution.
583 Please refer doc/README.pblimage for more details.
585 config SYS_FSL_PBL_RCW
586 string "Aadditional RCW (Power on reset configuration) for the PBL image"
587 depends on RAMBOOT_PBL
589 Enables addition of RCW (Power on reset configuration) in built image.
590 Please refer doc/README.pblimage for more details.
592 endmenu # Boot images
597 bool "Boot timing and reporting"
599 Enable recording of boot time while booting. To use it, insert
600 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
601 bootstage.h. Only a single entry is recorded for each ID. You can
602 give the entry a name with bootstage_mark_name(). You can also
603 record elapsed time in a particular stage using bootstage_start()
604 before starting and bootstage_accum() when finished. Bootstage will
605 add up all the accumulated time and report it.
607 Normally, IDs are defined in bootstage.h but a small number of
608 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
611 Calls to show_boot_progress() will also result in log entries but
612 these will not have names.
615 bool "Boot timing and reported in SPL"
618 Enable recording of boot time in SPL. To make this visible to U-Boot
619 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
620 information when SPL finishes and load it when U-Boot proper starts
624 bool "Boot timing and reported in TPL"
625 depends on BOOTSTAGE && TPL
627 Enable recording of boot time in SPL. To make this visible to U-Boot
628 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
629 information when TPL finishes and load it when U-Boot proper starts
632 config BOOTSTAGE_REPORT
633 bool "Display a detailed boot timing report before booting the OS"
636 Enable output of a boot time report just before the OS is booted.
637 This shows how long it took U-Boot to go through each stage of the
638 boot process. The report looks something like this:
640 Timer summary in microseconds:
643 3,575,678 3,575,678 board_init_f start
644 3,575,695 17 arch_cpu_init A9
645 3,575,777 82 arch_cpu_init done
646 3,659,598 83,821 board_init_r start
647 3,910,375 250,777 main_loop
648 29,916,167 26,005,792 bootm_start
649 30,361,327 445,160 start_kernel
651 config BOOTSTAGE_RECORD_COUNT
652 int "Number of boot stage records to store"
656 This is the size of the bootstage record list and is the maximum
657 number of bootstage records that can be recorded.
659 config SPL_BOOTSTAGE_RECORD_COUNT
660 int "Number of boot stage records to store for SPL"
661 depends on SPL_BOOTSTAGE
664 This is the size of the bootstage record list and is the maximum
665 number of bootstage records that can be recorded.
667 config TPL_BOOTSTAGE_RECORD_COUNT
668 int "Number of boot stage records to store for TPL"
669 depends on TPL_BOOTSTAGE
672 This is the size of the bootstage record list and is the maximum
673 number of bootstage records that can be recorded.
676 bool "Store boot timing information in the OS device tree"
679 Stash the bootstage information in the FDT. A root 'bootstage'
680 node is created with each bootstage id as a child. Each child
681 has a 'name' property and either 'mark' containing the
682 mark time in microseconds, or 'accum' containing the
683 accumulated time for that bootstage id in microseconds.
688 name = "board_init_f";
697 Code in the Linux kernel can find this in /proc/devicetree.
699 config BOOTSTAGE_STASH
700 bool "Stash the boot timing information in memory before booting OS"
703 Some OSes do not support device tree. Bootstage can instead write
704 the boot timing information in a binary format at a given address.
705 This happens through a call to bootstage_stash(), typically in
706 the CPU's cleanup_before_linux() function. You can use the
707 'bootstage stash' and 'bootstage unstash' commands to do this on
710 config BOOTSTAGE_STASH_ADDR
711 hex "Address to stash boot timing information"
714 Provide an address which will not be overwritten by the OS when it
715 starts, so that it can read this information when ready.
717 config BOOTSTAGE_STASH_SIZE
718 hex "Size of boot timing stash region"
721 This should be large enough to hold the bootstage stash. A value of
722 4096 (4KiB) is normally plenty.
724 config SHOW_BOOT_PROGRESS
725 bool "Show boot progress in a board-specific manner"
727 Defining this option allows to add some board-specific code (calling
728 a user-provided function show_boot_progress(int) that enables you to
729 show the system's boot progress on some display (for example, some
730 LEDs) on your board. At the moment, the following checkpoints are
733 Legacy uImage format:
736 1 common/cmd_bootm.c before attempting to boot an image
737 -1 common/cmd_bootm.c Image header has bad magic number
738 2 common/cmd_bootm.c Image header has correct magic number
739 -2 common/cmd_bootm.c Image header has bad checksum
740 3 common/cmd_bootm.c Image header has correct checksum
741 -3 common/cmd_bootm.c Image data has bad checksum
742 4 common/cmd_bootm.c Image data has correct checksum
743 -4 common/cmd_bootm.c Image is for unsupported architecture
744 5 common/cmd_bootm.c Architecture check OK
745 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
746 6 common/cmd_bootm.c Image Type check OK
747 -6 common/cmd_bootm.c gunzip uncompression error
748 -7 common/cmd_bootm.c Unimplemented compression type
749 7 common/cmd_bootm.c Uncompression OK
750 8 common/cmd_bootm.c No uncompress/copy overwrite error
751 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
753 9 common/image.c Start initial ramdisk verification
754 -10 common/image.c Ramdisk header has bad magic number
755 -11 common/image.c Ramdisk header has bad checksum
756 10 common/image.c Ramdisk header is OK
757 -12 common/image.c Ramdisk data has bad checksum
758 11 common/image.c Ramdisk data has correct checksum
759 12 common/image.c Ramdisk verification complete, start loading
760 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
761 13 common/image.c Start multifile image verification
762 14 common/image.c No initial ramdisk, no multifile, continue.
764 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
766 -30 arch/powerpc/lib/board.c Fatal error, hang the system
767 -31 post/post.c POST test failed, detected by post_output_backlog()
768 -32 post/post.c POST test failed, detected by post_run_single()
770 34 common/cmd_doc.c before loading a Image from a DOC device
771 -35 common/cmd_doc.c Bad usage of "doc" command
772 35 common/cmd_doc.c correct usage of "doc" command
773 -36 common/cmd_doc.c No boot device
774 36 common/cmd_doc.c correct boot device
775 -37 common/cmd_doc.c Unknown Chip ID on boot device
776 37 common/cmd_doc.c correct chip ID found, device available
777 -38 common/cmd_doc.c Read Error on boot device
778 38 common/cmd_doc.c reading Image header from DOC device OK
779 -39 common/cmd_doc.c Image header has bad magic number
780 39 common/cmd_doc.c Image header has correct magic number
781 -40 common/cmd_doc.c Error reading Image from DOC device
782 40 common/cmd_doc.c Image header has correct magic number
783 41 common/cmd_ide.c before loading a Image from a IDE device
784 -42 common/cmd_ide.c Bad usage of "ide" command
785 42 common/cmd_ide.c correct usage of "ide" command
786 -43 common/cmd_ide.c No boot device
787 43 common/cmd_ide.c boot device found
788 -44 common/cmd_ide.c Device not available
789 44 common/cmd_ide.c Device available
790 -45 common/cmd_ide.c wrong partition selected
791 45 common/cmd_ide.c partition selected
792 -46 common/cmd_ide.c Unknown partition table
793 46 common/cmd_ide.c valid partition table found
794 -47 common/cmd_ide.c Invalid partition type
795 47 common/cmd_ide.c correct partition type
796 -48 common/cmd_ide.c Error reading Image Header on boot device
797 48 common/cmd_ide.c reading Image Header from IDE device OK
798 -49 common/cmd_ide.c Image header has bad magic number
799 49 common/cmd_ide.c Image header has correct magic number
800 -50 common/cmd_ide.c Image header has bad checksum
801 50 common/cmd_ide.c Image header has correct checksum
802 -51 common/cmd_ide.c Error reading Image from IDE device
803 51 common/cmd_ide.c reading Image from IDE device OK
804 52 common/cmd_nand.c before loading a Image from a NAND device
805 -53 common/cmd_nand.c Bad usage of "nand" command
806 53 common/cmd_nand.c correct usage of "nand" command
807 -54 common/cmd_nand.c No boot device
808 54 common/cmd_nand.c boot device found
809 -55 common/cmd_nand.c Unknown Chip ID on boot device
810 55 common/cmd_nand.c correct chip ID found, device available
811 -56 common/cmd_nand.c Error reading Image Header on boot device
812 56 common/cmd_nand.c reading Image Header from NAND device OK
813 -57 common/cmd_nand.c Image header has bad magic number
814 57 common/cmd_nand.c Image header has correct magic number
815 -58 common/cmd_nand.c Error reading Image from NAND device
816 58 common/cmd_nand.c reading Image from NAND device OK
818 -60 common/env_common.c Environment has a bad CRC, using default
820 64 net/eth.c starting with Ethernet configuration.
821 -64 net/eth.c no Ethernet found.
822 65 net/eth.c Ethernet found.
824 -80 common/cmd_net.c usage wrong
825 80 common/cmd_net.c before calling net_loop()
826 -81 common/cmd_net.c some error in net_loop() occurred
827 81 common/cmd_net.c net_loop() back without error
828 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
829 82 common/cmd_net.c trying automatic boot
830 83 common/cmd_net.c running "source" command
831 -83 common/cmd_net.c some error in automatic boot or "source" command
832 84 common/cmd_net.c end without errors
837 100 common/cmd_bootm.c Kernel FIT Image has correct format
838 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
839 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
840 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
841 102 common/cmd_bootm.c Kernel unit name specified
842 -103 common/cmd_bootm.c Can't get kernel subimage node offset
843 103 common/cmd_bootm.c Found configuration node
844 104 common/cmd_bootm.c Got kernel subimage node offset
845 -104 common/cmd_bootm.c Kernel subimage hash verification failed
846 105 common/cmd_bootm.c Kernel subimage hash verification OK
847 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
848 106 common/cmd_bootm.c Architecture check OK
849 -106 common/cmd_bootm.c Kernel subimage has wrong type
850 107 common/cmd_bootm.c Kernel subimage type OK
851 -107 common/cmd_bootm.c Can't get kernel subimage data/size
852 108 common/cmd_bootm.c Got kernel subimage data/size
853 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
854 -109 common/cmd_bootm.c Can't get kernel subimage type
855 -110 common/cmd_bootm.c Can't get kernel subimage comp
856 -111 common/cmd_bootm.c Can't get kernel subimage os
857 -112 common/cmd_bootm.c Can't get kernel subimage load address
858 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
860 120 common/image.c Start initial ramdisk verification
861 -120 common/image.c Ramdisk FIT image has incorrect format
862 121 common/image.c Ramdisk FIT image has correct format
863 122 common/image.c No ramdisk subimage unit name, using configuration
864 -122 common/image.c Can't get configuration for ramdisk subimage
865 123 common/image.c Ramdisk unit name specified
866 -124 common/image.c Can't get ramdisk subimage node offset
867 125 common/image.c Got ramdisk subimage node offset
868 -125 common/image.c Ramdisk subimage hash verification failed
869 126 common/image.c Ramdisk subimage hash verification OK
870 -126 common/image.c Ramdisk subimage for unsupported architecture
871 127 common/image.c Architecture check OK
872 -127 common/image.c Can't get ramdisk subimage data/size
873 128 common/image.c Got ramdisk subimage data/size
874 129 common/image.c Can't get ramdisk load address
875 -129 common/image.c Got ramdisk load address
877 -130 common/cmd_doc.c Incorrect FIT image format
878 131 common/cmd_doc.c FIT image format OK
880 -140 common/cmd_ide.c Incorrect FIT image format
881 141 common/cmd_ide.c FIT image format OK
883 -150 common/cmd_nand.c Incorrect FIT image format
884 151 common/cmd_nand.c FIT image format OK
886 config SPL_SHOW_BOOT_PROGRESS
887 bool "Show boot progress in a board-specific manner in SPL"
890 Defining this option allows to add some board-specific code (calling
891 a user-provided function show_boot_progress(int) that enables you to
892 show the system's boot progress on some display (for example, some
893 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
900 bool "Support for booting from NOR flash"
903 Enabling this will make a U-Boot binary that is capable of being
904 booted via NOR. In this case we will enable certain pinmux early
905 as the ROM only partially sets up pinmux. We also default to using
909 bool "Support for booting from NAND flash"
912 Enabling this will make a U-Boot binary that is capable of being
913 booted via NAND flash. This is not a must, some SoCs need this,
917 bool "Support for booting from ONENAND"
920 Enabling this will make a U-Boot binary that is capable of being
921 booted via ONENAND. This is not a must, some SoCs need this,
925 bool "Support for booting from QSPI flash"
927 Enabling this will make a U-Boot binary that is capable of being
928 booted via QSPI flash. This is not a must, some SoCs need this,
932 bool "Support for booting from SATA"
934 Enabling this will make a U-Boot binary that is capable of being
935 booted via SATA. This is not a must, some SoCs need this,
939 bool "Support for booting from SD/EMMC"
941 Enabling this will make a U-Boot binary that is capable of being
942 booted via SD/EMMC. This is not a must, some SoCs need this,
946 bool "Support for booting from SD/EMMC and enable QSPI"
948 Enabling this will make a U-Boot binary that is capable of being
949 booted via SD/EMMC while enabling QSPI on the platform as well. This
950 is not a must, some SoCs need this, some not.
953 bool "Support for booting from SPI flash"
955 Enabling this will make a U-Boot binary that is capable of being
956 booted via SPI flash. This is not a must, some SoCs need this,
961 menu "Autoboot options"
967 This enables the autoboot. See doc/README.autoboot for detail.
970 int "delay in seconds before automatically booting"
974 Delay before automatically running bootcmd;
975 set to 0 to autoboot with no delay, but you can stop it by key input.
976 set to -1 to disable autoboot.
977 set to -2 to autoboot with no delay and not check for abort
979 If this value is >= 0 then it is also used for the default delay
980 before starting the default entry in bootmenu. If it is < 0 then
981 a default value of 10s is used.
983 See doc/README.autoboot for details.
985 config AUTOBOOT_KEYED
986 bool "Stop autobooting via specific input key / string"
988 This option enables stopping (aborting) of the automatic
989 boot feature only by issuing a specific input key or
990 string. If not enabled, any input key will abort the
991 U-Boot automatic booting process and bring the device
992 to the U-Boot prompt for user input.
994 config AUTOBOOT_FLUSH_STDIN
995 bool "Enable flushing stdin before starting to read the password"
996 depends on AUTOBOOT_KEYED && !SANDBOX
998 When this option is enabled stdin buffer will be flushed before
999 starting to read the password.
1000 This can't be enabled for the sandbox as flushing stdin would
1001 break the autoboot unit tests.
1003 config AUTOBOOT_PROMPT
1004 string "Autoboot stop prompt"
1005 depends on AUTOBOOT_KEYED
1006 default "Autoboot in %d seconds\\n"
1008 This string is displayed before the boot delay selected by
1009 CONFIG_BOOTDELAY starts. If it is not defined there is no
1010 output indicating that autoboot is in progress.
1012 Note that this define is used as the (only) argument to a
1013 printf() call, so it may contain '%' format specifications,
1014 provided that it also includes, sepearated by commas exactly
1015 like in a printf statement, the required arguments. It is
1016 the responsibility of the user to select only such arguments
1017 that are valid in the given context.
1019 config AUTOBOOT_ENCRYPTION
1020 bool "Enable encryption in autoboot stopping"
1021 depends on AUTOBOOT_KEYED
1023 This option allows a string to be entered into U-Boot to stop the
1025 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1027 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1028 to the crypt-based functionality and be compared against the
1029 string in the environment variable 'bootstopkeycrypt'.
1030 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1031 and compared against the hash in the environment variable
1032 'bootstopkeysha256'.
1033 If it matches in either case then boot stops and
1034 a command-line prompt is presented.
1035 This provides a way to ship a secure production device which can also
1036 be accessed at the U-Boot command line.
1038 config AUTOBOOT_SHA256_FALLBACK
1039 bool "Allow fallback from crypt-hashed password to sha256"
1040 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1042 This option adds support to fall back from crypt-hashed
1043 passwords to checking a SHA256 hashed password in case the
1044 'bootstopusesha256' environment variable is set to 'true'.
1046 config AUTOBOOT_DELAY_STR
1047 string "Delay autobooting via specific input key / string"
1048 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1050 This option delays the automatic boot feature by issuing
1051 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1052 or the environment variable "bootdelaykey" is specified
1053 and this string is received from console input before
1054 autoboot starts booting, U-Boot gives a command prompt. The
1055 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1056 used, otherwise it never times out.
1058 config AUTOBOOT_STOP_STR
1059 string "Stop autobooting via specific input key / string"
1060 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1062 This option enables stopping (aborting) of the automatic
1063 boot feature only by issuing a specific input key or
1064 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1065 variable "bootstopkey" is specified and this string is
1066 received from console input before autoboot starts booting,
1067 U-Boot gives a command prompt. The U-Boot prompt never
1068 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1070 config AUTOBOOT_KEYED_CTRLC
1071 bool "Enable Ctrl-C autoboot interruption"
1072 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1074 This option allows for the boot sequence to be interrupted
1075 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1076 Setting this variable provides an escape sequence from the
1077 limited "password" strings.
1079 config AUTOBOOT_NEVER_TIMEOUT
1080 bool "Make the password entry never time-out"
1081 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1083 This option removes the timeout from the password entry
1084 when the user first presses the <Enter> key before entering
1085 any other character.
1087 config AUTOBOOT_STOP_STR_ENABLE
1088 bool "Enable fixed string to stop autobooting"
1089 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1091 This option enables the feature to add a fixed stop
1092 string that is defined at compile time.
1093 In every case it will be tried to load the stop
1094 string from the environment.
1095 In case this is enabled and there is no stop string
1096 in the environment, this will be used as default value.
1098 config AUTOBOOT_STOP_STR_CRYPT
1099 string "Stop autobooting via crypt-hashed password"
1100 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1102 This option adds the feature to only stop the autobooting,
1103 and therefore boot into the U-Boot prompt, when the input
1104 string / password matches a values that is hashed via
1105 one of the supported crypt-style password hashing options
1106 and saved in the environment variable "bootstopkeycrypt".
1108 config AUTOBOOT_STOP_STR_SHA256
1109 string "Stop autobooting via SHA256 hashed password"
1110 depends on AUTOBOOT_STOP_STR_ENABLE
1112 This option adds the feature to only stop the autobooting,
1113 and therefore boot into the U-Boot prompt, when the input
1114 string / password matches a values that is encypted via
1115 a SHA256 hash and saved in the environment variable
1116 "bootstopkeysha256". If the value in that variable
1117 includes a ":", the portion prior to the ":" will be treated
1120 config AUTOBOOT_USE_MENUKEY
1121 bool "Allow a specify key to run a menu from the environment"
1122 depends on !AUTOBOOT_KEYED
1124 If a specific key is pressed to stop autoboot, then the commands in
1125 the environment variable 'menucmd' are executed before boot starts.
1127 config AUTOBOOT_MENUKEY
1128 int "ASCII value of boot key to show a menu"
1130 depends on AUTOBOOT_USE_MENUKEY
1132 If this key is pressed to stop autoboot, then the commands in the
1133 environment variable 'menucmd' will be executed before boot starts.
1134 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1137 config AUTOBOOT_MENU_SHOW
1138 bool "Show a menu on boot"
1139 depends on CMD_BOOTMENU
1141 This enables the boot menu, controlled by environment variables
1142 defined by the board. The menu starts after running the 'preboot'
1143 environmnent variable (if enabled) and before handling the boot delay.
1144 See README.bootmenu for more details.
1146 config BOOTMENU_DISABLE_UBOOT_CONSOLE
1147 bool "Disallow bootmenu to enter the U-Boot console"
1148 depends on AUTOBOOT_MENU_SHOW
1150 If this option is enabled, user can not enter the U-Boot console from
1151 bootmenu. It increases the system security.
1154 bool "Boot retry feature"
1156 Allow for having the U-Boot command prompt time out and attempt
1157 to boot again. If the environment variable "bootretry" is found then
1158 its value is used, otherwise the retry timeout is
1159 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1160 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1162 config BOOT_RETRY_TIME
1163 int "Timeout in seconds before attempting to boot again"
1164 depends on BOOT_RETRY
1166 Time in seconds before the U-Boot prompt will timeout and boot will
1169 config BOOT_RETRY_MIN
1170 int "Minimum timeout in seconds for 'bootretry'"
1171 depends on BOOT_RETRY
1172 default BOOT_RETRY_TIME
1174 The minimum time in seconds that "bootretry" can be set to.
1176 config RESET_TO_RETRY
1177 bool "Reset the board to retry autoboot"
1178 depends on BOOT_RETRY
1180 After the countdown timed out, the board will be reset to restart
1185 menu "Image support"
1187 config IMAGE_PRE_LOAD
1188 bool "Image pre-load support"
1190 Enable an image pre-load stage in the SPL.
1191 This pre-load stage allows to do some manipulation
1192 or check (for example signature check) on an image
1193 before launching it.
1195 config SPL_IMAGE_PRE_LOAD
1196 bool "Image pre-load support within SPL"
1197 depends on SPL && IMAGE_PRE_LOAD
1199 Enable an image pre-load stage in the SPL.
1200 This pre-load stage allows to do some manipulation
1201 or check (for example signature check) on an image
1202 before launching it.
1204 config IMAGE_PRE_LOAD_SIG
1205 bool "Image pre-load signature support"
1206 depends on IMAGE_PRE_LOAD
1207 select FIT_SIGNATURE
1209 select RSA_VERIFY_WITH_PKEY
1211 Enable signature check support in the pre-load stage.
1212 For this feature a very simple header is added before
1213 the image with few fields:
1217 All other information (header size, type of signature,
1218 ...) are provided in the node /image/pre-load/sig of
1221 config SPL_IMAGE_PRE_LOAD_SIG
1222 bool "Image pre-load signature support witin SPL"
1223 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1224 select SPL_FIT_SIGNATURE
1226 select SPL_RSA_VERIFY_WITH_PKEY
1228 Enable signature check support in the pre-load stage in the SPL.
1229 For this feature a very simple header is added before
1230 the image with few fields:
1234 All other information (header size, type of signature,
1235 ...) are provided in the node /image/pre-load/sig of
1241 bool "Enable boot arguments"
1243 Provide boot arguments to bootm command. Boot arguments are specified
1244 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1245 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1246 will be undefined and won't take any space in U-Boot image.
1249 string "Boot arguments"
1250 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1252 This can be used to pass arguments to the bootm command. The value of
1253 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1254 this value will also override the "chosen" node in FDT blob.
1256 config BOOTARGS_SUBST
1257 bool "Support substituting strings in boot arguments"
1259 This allows substituting string values in the boot arguments. These
1260 are applied after the commandline has been built.
1262 One use for this is to insert the root-disk UUID into the command
1263 line where bootargs contains "root=${uuid}"
1265 setenv bootargs "console= root=${uuid}"
1266 # Set the 'uuid' environment variable
1267 part uuid mmc 2:2 uuid
1269 # Command-line substitution will put the real uuid into the
1270 # kernel command line
1273 config USE_BOOTCOMMAND
1274 bool "Enable a default value for bootcmd"
1276 Provide a default value for the bootcmd entry in the environment. If
1277 autoboot is enabled this is what will be run automatically. Enable
1278 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1279 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1280 won't take any space in U-Boot image.
1283 string "bootcmd value"
1284 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1285 default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL
1286 default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL
1287 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1289 This is the string of commands that will be used as bootcmd and if
1290 AUTOBOOT is set, automatically run.
1293 bool "Enable preboot"
1295 When this option is enabled, the existence of the environment
1296 variable "preboot" will be checked immediately before starting the
1297 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1298 entering interactive mode.
1300 This feature is especially useful when "preboot" is automatically
1301 generated or modified. For example, the boot code can modify the
1302 "preboot" when a user holds down a certain combination of keys.
1305 string "preboot default value"
1306 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1307 default "usb start" if USB_KEYBOARD
1310 This is the default of "preboot" environment variable.
1312 config DEFAULT_FDT_FILE
1313 string "Default fdt file"
1315 This option is used to set the default fdt file to boot OS.
1317 config SAVE_PREV_BL_FDT_ADDR
1319 bool "Saves fdt address, passed by the previous bootloader, to env var"
1321 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1322 enable this option to save fdt address, passed by the
1323 previous bootloader for future use.
1324 Address is saved to `prevbl_fdt_addr` environment variable.
1326 If no fdt was provided by previous bootloader, no env variables
1329 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1331 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1333 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1334 enable this option to save initramfs address, passed by the
1335 previous bootloader for future use.
1336 Address is saved to `prevbl_initrd_start_addr` environment variable.
1338 If no initramfs was provided by previous bootloader, no env variables