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.
354 config LEGACY_IMAGE_FORMAT
355 bool "Enable support for the legacy image format"
356 default y if !FIT_SIGNATURE
358 This option enables the legacy image format. It is enabled by
359 default for backward compatibility, unless FIT_SIGNATURE is
360 set where it is disabled so that unsigned images cannot be
361 loaded. If a board needs the legacy image format support in this
362 case, enable it here.
364 config SUPPORT_RAW_INITRD
365 bool "Enable raw initrd images"
367 Note, defining the SUPPORT_RAW_INITRD allows user to supply
368 kernel with raw initrd images. The syntax is slightly different, the
369 address of the initrd must be augmented by it's size, in the following
370 format: "<initrd address>:<initrd size>".
372 config OF_BOARD_SETUP
373 bool "Set up board-specific details in device tree before boot"
376 This causes U-Boot to call ft_board_setup() before booting into
377 the Operating System. This function can set up various
378 board-specific information in the device tree for use by the OS.
379 The device tree is then passed to the OS.
381 config OF_SYSTEM_SETUP
382 bool "Set up system-specific details in device tree before boot"
385 This causes U-Boot to call ft_system_setup() before booting into
386 the Operating System. This function can set up various
387 system-specific information in the device tree for use by the OS.
388 The device tree is then passed to the OS.
390 config OF_STDOUT_VIA_ALIAS
391 bool "Update the device-tree stdout alias from U-Boot"
394 This uses U-Boot's serial alias from the aliases node to update
395 the device tree passed to the OS. The "linux,stdout-path" property
396 in the chosen node is set to point to the correct serial node.
397 This option currently references CONFIG_CONS_INDEX, which is
398 incorrect when used with device tree as this option does not
399 exist / should not be used.
401 config SYS_EXTRA_OPTIONS
402 string "Extra Options (DEPRECATED)"
404 The old configuration infrastructure (= mkconfig + boards.cfg)
405 provided the extra options field. If you have something like
406 "HAS_BAR,BAZ=64", the optional options
408 #define CONFIG_BAZ 64
409 will be defined in include/config.h.
410 This option was prepared for the smooth migration from the old
411 configuration to Kconfig. Since this option will be removed sometime,
412 new boards should not use this option.
414 config HAVE_SYS_TEXT_BASE
416 depends on !NIOS2 && !XTENSA
421 depends on HAVE_SYS_TEXT_BASE
422 default 0x0 if POSITION_INDEPENDENT
423 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
424 default 0x81700000 if MACH_SUNIV
425 default 0x2a000000 if MACH_SUN9I
426 default 0x42e00000 if MACH_SUN8I_V3S
427 default 0x4a000000 if ARCH_SUNXI
430 The address in memory that U-Boot will be running from, initially.
432 config HAVE_SYS_MONITOR_BASE
434 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
435 || FLASH_PIC32 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
439 config SYS_MONITOR_BASE
440 depends on HAVE_SYS_MONITOR_BASE
441 hex "Physical start address of boot monitor code"
442 default SYS_TEXT_BASE
444 The physical start address of boot monitor code (which is the same as
445 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
446 when booting from flash.
448 config SPL_SYS_MONITOR_BASE
449 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
450 hex "Physical start address of SPL monitor code"
451 default SPL_TEXT_BASE
453 config TPL_SYS_MONITOR_BASE
454 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
455 hex "Physical start address of TPL monitor code"
457 config DYNAMIC_SYS_CLK_FREQ
458 bool "Determine CPU clock frequency at run-time"
460 Implement a get_board_sys_clk function that will determine the CPU
461 clock frequency at run time, rather than define it statically.
464 depends on !DYNAMIC_SYS_CLK_FREQ
465 int "CPU clock frequency"
466 default 125000000 if ARCH_LS1012A
467 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
468 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
469 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
470 default 66660000 if ARCH_T2080
471 default 33333333 if RCAR_GEN3
472 default 24000000 if ARCH_EXYNOS
473 default 20000000 if RCAR_GEN2
476 A static value for the CPU frequency. Note that if not required
477 for a given SoC, this can be left at 0.
479 config ARCH_FIXUP_FDT_MEMORY
480 bool "Enable arch_fixup_memory_banks() call"
483 Enable FDT memory map syncup before OS boot. This feature can be
484 used for booting OS with different memory setup where the part of
485 the memory location should be used for different purpose.
488 bool "Support booting Chrome OS"
490 Chrome OS requires U-Boot to set up a table indicating the boot mode
491 (e.g. Developer mode) and a few other things. Enable this if you are
492 booting on a Chromebook to avoid getting an error about an invalid
495 config CHROMEOS_VBOOT
496 bool "Support Chrome OS verified boot"
498 This is intended to enable the full Chrome OS verified boot support
499 in U-Boot. It is not actually implemented in the U-Boot source code
500 at present, so this option is always set to 'n'. It allows
501 distinguishing between booting Chrome OS in a basic way (developer
502 mode) and a full boot.
505 bool "Freescale PBL(pre-boot loader) image format support"
507 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
508 For more details refer to doc/README.pblimage
511 prompt "Freescale PBL load location"
512 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
513 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
517 bool "Freescale PBL is found on SD card"
520 bool "Freescale PBL is found on SPI flash"
524 config SYS_FSL_PBL_PBI
525 string "PBI(pre-boot instructions) commands for the PBL image"
526 depends on RAMBOOT_PBL
528 PBI commands can be used to configure SoC before it starts the execution.
529 Please refer doc/README.pblimage for more details.
531 config SYS_FSL_PBL_RCW
532 string "Aadditional RCW (Power on reset configuration) for the PBL image"
533 depends on RAMBOOT_PBL
535 Enables addition of RCW (Power on reset configuration) in built image.
536 Please refer doc/README.pblimage for more details.
538 endmenu # Boot images
543 bool "Boot timing and reporting"
545 Enable recording of boot time while booting. To use it, insert
546 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
547 bootstage.h. Only a single entry is recorded for each ID. You can
548 give the entry a name with bootstage_mark_name(). You can also
549 record elapsed time in a particular stage using bootstage_start()
550 before starting and bootstage_accum() when finished. Bootstage will
551 add up all the accumulated time and report it.
553 Normally, IDs are defined in bootstage.h but a small number of
554 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
557 Calls to show_boot_progress() will also result in log entries but
558 these will not have names.
561 bool "Boot timing and reported in SPL"
564 Enable recording of boot time in SPL. To make this visible to U-Boot
565 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
566 information when SPL finishes and load it when U-Boot proper starts
570 bool "Boot timing and reported in TPL"
573 Enable recording of boot time in SPL. To make this visible to U-Boot
574 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
575 information when TPL finishes and load it when U-Boot proper starts
578 config BOOTSTAGE_REPORT
579 bool "Display a detailed boot timing report before booting the OS"
582 Enable output of a boot time report just before the OS is booted.
583 This shows how long it took U-Boot to go through each stage of the
584 boot process. The report looks something like this:
586 Timer summary in microseconds:
589 3,575,678 3,575,678 board_init_f start
590 3,575,695 17 arch_cpu_init A9
591 3,575,777 82 arch_cpu_init done
592 3,659,598 83,821 board_init_r start
593 3,910,375 250,777 main_loop
594 29,916,167 26,005,792 bootm_start
595 30,361,327 445,160 start_kernel
597 config BOOTSTAGE_RECORD_COUNT
598 int "Number of boot stage records to store"
602 This is the size of the bootstage record list and is the maximum
603 number of bootstage records that can be recorded.
605 config SPL_BOOTSTAGE_RECORD_COUNT
606 int "Number of boot stage records to store for SPL"
607 depends on SPL_BOOTSTAGE
610 This is the size of the bootstage record list and is the maximum
611 number of bootstage records that can be recorded.
613 config TPL_BOOTSTAGE_RECORD_COUNT
614 int "Number of boot stage records to store for TPL"
615 depends on TPL_BOOTSTAGE
618 This is the size of the bootstage record list and is the maximum
619 number of bootstage records that can be recorded.
622 bool "Store boot timing information in the OS device tree"
625 Stash the bootstage information in the FDT. A root 'bootstage'
626 node is created with each bootstage id as a child. Each child
627 has a 'name' property and either 'mark' containing the
628 mark time in microseconds, or 'accum' containing the
629 accumulated time for that bootstage id in microseconds.
634 name = "board_init_f";
643 Code in the Linux kernel can find this in /proc/devicetree.
645 config BOOTSTAGE_STASH
646 bool "Stash the boot timing information in memory before booting OS"
649 Some OSes do not support device tree. Bootstage can instead write
650 the boot timing information in a binary format at a given address.
651 This happens through a call to bootstage_stash(), typically in
652 the CPU's cleanup_before_linux() function. You can use the
653 'bootstage stash' and 'bootstage unstash' commands to do this on
656 config BOOTSTAGE_STASH_ADDR
657 hex "Address to stash boot timing information"
660 Provide an address which will not be overwritten by the OS when it
661 starts, so that it can read this information when ready.
663 config BOOTSTAGE_STASH_SIZE
664 hex "Size of boot timing stash region"
667 This should be large enough to hold the bootstage stash. A value of
668 4096 (4KiB) is normally plenty.
670 config SHOW_BOOT_PROGRESS
671 bool "Show boot progress in a board-specific manner"
673 Defining this option allows to add some board-specific code (calling
674 a user-provided function show_boot_progress(int) that enables you to
675 show the system's boot progress on some display (for example, some
676 LEDs) on your board. At the moment, the following checkpoints are
679 Legacy uImage format:
682 1 common/cmd_bootm.c before attempting to boot an image
683 -1 common/cmd_bootm.c Image header has bad magic number
684 2 common/cmd_bootm.c Image header has correct magic number
685 -2 common/cmd_bootm.c Image header has bad checksum
686 3 common/cmd_bootm.c Image header has correct checksum
687 -3 common/cmd_bootm.c Image data has bad checksum
688 4 common/cmd_bootm.c Image data has correct checksum
689 -4 common/cmd_bootm.c Image is for unsupported architecture
690 5 common/cmd_bootm.c Architecture check OK
691 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
692 6 common/cmd_bootm.c Image Type check OK
693 -6 common/cmd_bootm.c gunzip uncompression error
694 -7 common/cmd_bootm.c Unimplemented compression type
695 7 common/cmd_bootm.c Uncompression OK
696 8 common/cmd_bootm.c No uncompress/copy overwrite error
697 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
699 9 common/image.c Start initial ramdisk verification
700 -10 common/image.c Ramdisk header has bad magic number
701 -11 common/image.c Ramdisk header has bad checksum
702 10 common/image.c Ramdisk header is OK
703 -12 common/image.c Ramdisk data has bad checksum
704 11 common/image.c Ramdisk data has correct checksum
705 12 common/image.c Ramdisk verification complete, start loading
706 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
707 13 common/image.c Start multifile image verification
708 14 common/image.c No initial ramdisk, no multifile, continue.
710 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
712 -30 arch/powerpc/lib/board.c Fatal error, hang the system
713 -31 post/post.c POST test failed, detected by post_output_backlog()
714 -32 post/post.c POST test failed, detected by post_run_single()
716 34 common/cmd_doc.c before loading a Image from a DOC device
717 -35 common/cmd_doc.c Bad usage of "doc" command
718 35 common/cmd_doc.c correct usage of "doc" command
719 -36 common/cmd_doc.c No boot device
720 36 common/cmd_doc.c correct boot device
721 -37 common/cmd_doc.c Unknown Chip ID on boot device
722 37 common/cmd_doc.c correct chip ID found, device available
723 -38 common/cmd_doc.c Read Error on boot device
724 38 common/cmd_doc.c reading Image header from DOC device OK
725 -39 common/cmd_doc.c Image header has bad magic number
726 39 common/cmd_doc.c Image header has correct magic number
727 -40 common/cmd_doc.c Error reading Image from DOC device
728 40 common/cmd_doc.c Image header has correct magic number
729 41 common/cmd_ide.c before loading a Image from a IDE device
730 -42 common/cmd_ide.c Bad usage of "ide" command
731 42 common/cmd_ide.c correct usage of "ide" command
732 -43 common/cmd_ide.c No boot device
733 43 common/cmd_ide.c boot device found
734 -44 common/cmd_ide.c Device not available
735 44 common/cmd_ide.c Device available
736 -45 common/cmd_ide.c wrong partition selected
737 45 common/cmd_ide.c partition selected
738 -46 common/cmd_ide.c Unknown partition table
739 46 common/cmd_ide.c valid partition table found
740 -47 common/cmd_ide.c Invalid partition type
741 47 common/cmd_ide.c correct partition type
742 -48 common/cmd_ide.c Error reading Image Header on boot device
743 48 common/cmd_ide.c reading Image Header from IDE device OK
744 -49 common/cmd_ide.c Image header has bad magic number
745 49 common/cmd_ide.c Image header has correct magic number
746 -50 common/cmd_ide.c Image header has bad checksum
747 50 common/cmd_ide.c Image header has correct checksum
748 -51 common/cmd_ide.c Error reading Image from IDE device
749 51 common/cmd_ide.c reading Image from IDE device OK
750 52 common/cmd_nand.c before loading a Image from a NAND device
751 -53 common/cmd_nand.c Bad usage of "nand" command
752 53 common/cmd_nand.c correct usage of "nand" command
753 -54 common/cmd_nand.c No boot device
754 54 common/cmd_nand.c boot device found
755 -55 common/cmd_nand.c Unknown Chip ID on boot device
756 55 common/cmd_nand.c correct chip ID found, device available
757 -56 common/cmd_nand.c Error reading Image Header on boot device
758 56 common/cmd_nand.c reading Image Header from NAND device OK
759 -57 common/cmd_nand.c Image header has bad magic number
760 57 common/cmd_nand.c Image header has correct magic number
761 -58 common/cmd_nand.c Error reading Image from NAND device
762 58 common/cmd_nand.c reading Image from NAND device OK
764 -60 common/env_common.c Environment has a bad CRC, using default
766 64 net/eth.c starting with Ethernet configuration.
767 -64 net/eth.c no Ethernet found.
768 65 net/eth.c Ethernet found.
770 -80 common/cmd_net.c usage wrong
771 80 common/cmd_net.c before calling net_loop()
772 -81 common/cmd_net.c some error in net_loop() occurred
773 81 common/cmd_net.c net_loop() back without error
774 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
775 82 common/cmd_net.c trying automatic boot
776 83 common/cmd_net.c running "source" command
777 -83 common/cmd_net.c some error in automatic boot or "source" command
778 84 common/cmd_net.c end without errors
783 100 common/cmd_bootm.c Kernel FIT Image has correct format
784 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
785 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
786 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
787 102 common/cmd_bootm.c Kernel unit name specified
788 -103 common/cmd_bootm.c Can't get kernel subimage node offset
789 103 common/cmd_bootm.c Found configuration node
790 104 common/cmd_bootm.c Got kernel subimage node offset
791 -104 common/cmd_bootm.c Kernel subimage hash verification failed
792 105 common/cmd_bootm.c Kernel subimage hash verification OK
793 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
794 106 common/cmd_bootm.c Architecture check OK
795 -106 common/cmd_bootm.c Kernel subimage has wrong type
796 107 common/cmd_bootm.c Kernel subimage type OK
797 -107 common/cmd_bootm.c Can't get kernel subimage data/size
798 108 common/cmd_bootm.c Got kernel subimage data/size
799 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
800 -109 common/cmd_bootm.c Can't get kernel subimage type
801 -110 common/cmd_bootm.c Can't get kernel subimage comp
802 -111 common/cmd_bootm.c Can't get kernel subimage os
803 -112 common/cmd_bootm.c Can't get kernel subimage load address
804 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
806 120 common/image.c Start initial ramdisk verification
807 -120 common/image.c Ramdisk FIT image has incorrect format
808 121 common/image.c Ramdisk FIT image has correct format
809 122 common/image.c No ramdisk subimage unit name, using configuration
810 -122 common/image.c Can't get configuration for ramdisk subimage
811 123 common/image.c Ramdisk unit name specified
812 -124 common/image.c Can't get ramdisk subimage node offset
813 125 common/image.c Got ramdisk subimage node offset
814 -125 common/image.c Ramdisk subimage hash verification failed
815 126 common/image.c Ramdisk subimage hash verification OK
816 -126 common/image.c Ramdisk subimage for unsupported architecture
817 127 common/image.c Architecture check OK
818 -127 common/image.c Can't get ramdisk subimage data/size
819 128 common/image.c Got ramdisk subimage data/size
820 129 common/image.c Can't get ramdisk load address
821 -129 common/image.c Got ramdisk load address
823 -130 common/cmd_doc.c Incorrect FIT image format
824 131 common/cmd_doc.c FIT image format OK
826 -140 common/cmd_ide.c Incorrect FIT image format
827 141 common/cmd_ide.c FIT image format OK
829 -150 common/cmd_nand.c Incorrect FIT image format
830 151 common/cmd_nand.c FIT image format OK
832 config SPL_SHOW_BOOT_PROGRESS
833 bool "Show boot progress in a board-specific manner in SPL"
836 Defining this option allows to add some board-specific code (calling
837 a user-provided function show_boot_progress(int) that enables you to
838 show the system's boot progress on some display (for example, some
839 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
846 bool "Support for booting from NOR flash"
849 Enabling this will make a U-Boot binary that is capable of being
850 booted via NOR. In this case we will enable certain pinmux early
851 as the ROM only partially sets up pinmux. We also default to using
855 bool "Support for booting from NAND flash"
858 Enabling this will make a U-Boot binary that is capable of being
859 booted via NAND flash. This is not a must, some SoCs need this,
863 bool "Support for booting from ONENAND"
866 Enabling this will make a U-Boot binary that is capable of being
867 booted via ONENAND. This is not a must, some SoCs need this,
871 bool "Support for booting from QSPI flash"
873 Enabling this will make a U-Boot binary that is capable of being
874 booted via QSPI flash. This is not a must, some SoCs need this,
878 bool "Support for booting from SATA"
880 Enabling this will make a U-Boot binary that is capable of being
881 booted via SATA. This is not a must, some SoCs need this,
885 bool "Support for booting from SD/EMMC"
887 Enabling this will make a U-Boot binary that is capable of being
888 booted via SD/EMMC. This is not a must, some SoCs need this,
892 bool "Support for booting from SD/EMMC and enable QSPI"
894 Enabling this will make a U-Boot binary that is capable of being
895 booted via SD/EMMC while enabling QSPI on the platform as well. This
896 is not a must, some SoCs need this, some not.
899 bool "Support for booting from SPI flash"
901 Enabling this will make a U-Boot binary that is capable of being
902 booted via SPI flash. This is not a must, some SoCs need this,
907 menu "Autoboot options"
913 This enables the autoboot. See doc/README.autoboot for detail.
916 int "delay in seconds before automatically booting"
920 Delay before automatically running bootcmd;
921 set to 0 to autoboot with no delay, but you can stop it by key input.
922 set to -1 to disable autoboot.
923 set to -2 to autoboot with no delay and not check for abort
925 If this value is >= 0 then it is also used for the default delay
926 before starting the default entry in bootmenu. If it is < 0 then
927 a default value of 10s is used.
929 See doc/README.autoboot for details.
931 config AUTOBOOT_KEYED
932 bool "Stop autobooting via specific input key / string"
934 This option enables stopping (aborting) of the automatic
935 boot feature only by issuing a specific input key or
936 string. If not enabled, any input key will abort the
937 U-Boot automatic booting process and bring the device
938 to the U-Boot prompt for user input.
940 config AUTOBOOT_FLUSH_STDIN
941 bool "Enable flushing stdin before starting to read the password"
942 depends on AUTOBOOT_KEYED && !SANDBOX
944 When this option is enabled stdin buffer will be flushed before
945 starting to read the password.
946 This can't be enabled for the sandbox as flushing stdin would
947 break the autoboot unit tests.
949 config AUTOBOOT_PROMPT
950 string "Autoboot stop prompt"
951 depends on AUTOBOOT_KEYED
952 default "Autoboot in %d seconds\\n"
954 This string is displayed before the boot delay selected by
955 CONFIG_BOOTDELAY starts. If it is not defined there is no
956 output indicating that autoboot is in progress.
958 Note that this define is used as the (only) argument to a
959 printf() call, so it may contain '%' format specifications,
960 provided that it also includes, sepearated by commas exactly
961 like in a printf statement, the required arguments. It is
962 the responsibility of the user to select only such arguments
963 that are valid in the given context.
965 config AUTOBOOT_ENCRYPTION
966 bool "Enable encryption in autoboot stopping"
967 depends on AUTOBOOT_KEYED
969 This option allows a string to be entered into U-Boot to stop the
971 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
973 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
974 to the crypt-based functionality and be compared against the
975 string in the environment variable 'bootstopkeycrypt'.
976 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
977 and compared against the hash in the environment variable
979 If it matches in either case then boot stops and
980 a command-line prompt is presented.
981 This provides a way to ship a secure production device which can also
982 be accessed at the U-Boot command line.
984 config AUTOBOOT_SHA256_FALLBACK
985 bool "Allow fallback from crypt-hashed password to sha256"
986 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
988 This option adds support to fall back from crypt-hashed
989 passwords to checking a SHA256 hashed password in case the
990 'bootstopusesha256' environment variable is set to 'true'.
992 config AUTOBOOT_DELAY_STR
993 string "Delay autobooting via specific input key / string"
994 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
996 This option delays the automatic boot feature by issuing
997 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
998 or the environment variable "bootdelaykey" is specified
999 and this string is received from console input before
1000 autoboot starts booting, U-Boot gives a command prompt. The
1001 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1002 used, otherwise it never times out.
1004 config AUTOBOOT_STOP_STR
1005 string "Stop autobooting via specific input key / string"
1006 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1008 This option enables stopping (aborting) of the automatic
1009 boot feature only by issuing a specific input key or
1010 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1011 variable "bootstopkey" is specified and this string is
1012 received from console input before autoboot starts booting,
1013 U-Boot gives a command prompt. The U-Boot prompt never
1014 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1016 config AUTOBOOT_KEYED_CTRLC
1017 bool "Enable Ctrl-C autoboot interruption"
1018 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1020 This option allows for the boot sequence to be interrupted
1021 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1022 Setting this variable provides an escape sequence from the
1023 limited "password" strings.
1025 config AUTOBOOT_NEVER_TIMEOUT
1026 bool "Make the password entry never time-out"
1027 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1029 This option removes the timeout from the password entry
1030 when the user first presses the <Enter> key before entering
1031 any other character.
1033 config AUTOBOOT_STOP_STR_ENABLE
1034 bool "Enable fixed string to stop autobooting"
1035 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1037 This option enables the feature to add a fixed stop
1038 string that is defined at compile time.
1039 In every case it will be tried to load the stop
1040 string from the environment.
1041 In case this is enabled and there is no stop string
1042 in the environment, this will be used as default value.
1044 config AUTOBOOT_STOP_STR_CRYPT
1045 string "Stop autobooting via crypt-hashed password"
1046 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1048 This option adds the feature to only stop the autobooting,
1049 and therefore boot into the U-Boot prompt, when the input
1050 string / password matches a values that is hashed via
1051 one of the supported crypt-style password hashing options
1052 and saved in the environment variable "bootstopkeycrypt".
1054 config AUTOBOOT_STOP_STR_SHA256
1055 string "Stop autobooting via SHA256 hashed password"
1056 depends on AUTOBOOT_STOP_STR_ENABLE
1058 This option adds the feature to only stop the autobooting,
1059 and therefore boot into the U-Boot prompt, when the input
1060 string / password matches a values that is encypted via
1061 a SHA256 hash and saved in the environment variable
1062 "bootstopkeysha256". If the value in that variable
1063 includes a ":", the portion prior to the ":" will be treated
1066 config AUTOBOOT_USE_MENUKEY
1067 bool "Allow a specify key to run a menu from the environment"
1068 depends on !AUTOBOOT_KEYED
1070 If a specific key is pressed to stop autoboot, then the commands in
1071 the environment variable 'menucmd' are executed before boot starts.
1073 config AUTOBOOT_MENUKEY
1074 int "ASCII value of boot key to show a menu"
1076 depends on AUTOBOOT_USE_MENUKEY
1078 If this key is pressed to stop autoboot, then the commands in the
1079 environment variable 'menucmd' will be executed before boot starts.
1080 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1083 config AUTOBOOT_MENU_SHOW
1084 bool "Show a menu on boot"
1085 depends on CMD_BOOTMENU
1087 This enables the boot menu, controlled by environment variables
1088 defined by the board. The menu starts after running the 'preboot'
1089 environmnent variable (if enabled) and before handling the boot delay.
1090 See README.bootmenu for more details.
1093 bool "Boot retry feature"
1095 Allow for having the U-Boot command prompt time out and attempt
1096 to boot again. If the environment variable "bootretry" is found then
1097 its value is used, otherwise the retry timeout is
1098 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1099 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1101 config BOOT_RETRY_TIME
1102 int "Timeout in seconds before attempting to boot again"
1103 depends on BOOT_RETRY
1105 Time in seconds before the U-Boot prompt will timeout and boot will
1108 config BOOT_RETRY_MIN
1109 int "Minimum timeout in seconds for 'bootretry'"
1110 depends on BOOT_RETRY
1111 default BOOT_RETRY_TIME
1113 The minimum time in seconds that "bootretry" can be set to.
1115 config RESET_TO_RETRY
1116 bool "Reset the board to retry autoboot"
1117 depends on BOOT_RETRY
1119 After the countdown timed out, the board will be reset to restart
1124 menu "Image support"
1126 config IMAGE_PRE_LOAD
1127 bool "Image pre-load support"
1129 Enable an image pre-load stage in the SPL.
1130 This pre-load stage allows to do some manipulation
1131 or check (for example signature check) on an image
1132 before launching it.
1134 config SPL_IMAGE_PRE_LOAD
1135 bool "Image pre-load support within SPL"
1136 depends on SPL && IMAGE_PRE_LOAD
1138 Enable an image pre-load stage in the SPL.
1139 This pre-load stage allows to do some manipulation
1140 or check (for example signature check) on an image
1141 before launching it.
1143 config IMAGE_PRE_LOAD_SIG
1144 bool "Image pre-load signature support"
1145 depends on IMAGE_PRE_LOAD
1146 select FIT_SIGNATURE
1148 select RSA_VERIFY_WITH_PKEY
1150 Enable signature check support in the pre-load stage.
1151 For this feature a very simple header is added before
1152 the image with few fields:
1156 All other information (header size, type of signature,
1157 ...) are provided in the node /image/pre-load/sig of
1160 config SPL_IMAGE_PRE_LOAD_SIG
1161 bool "Image pre-load signature support witin SPL"
1162 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1163 select SPL_FIT_SIGNATURE
1165 select SPL_RSA_VERIFY_WITH_PKEY
1167 Enable signature check support in the pre-load stage in the SPL.
1168 For this feature a very simple header is added before
1169 the image with few fields:
1173 All other information (header size, type of signature,
1174 ...) are provided in the node /image/pre-load/sig of
1180 bool "Enable boot arguments"
1182 Provide boot arguments to bootm command. Boot arguments are specified
1183 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1184 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1185 will be undefined and won't take any space in U-Boot image.
1188 string "Boot arguments"
1189 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1191 This can be used to pass arguments to the bootm command. The value of
1192 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1193 this value will also override the "chosen" node in FDT blob.
1195 config BOOTARGS_SUBST
1196 bool "Support substituting strings in boot arguments"
1198 This allows substituting string values in the boot arguments. These
1199 are applied after the commandline has been built.
1201 One use for this is to insert the root-disk UUID into the command
1202 line where bootargs contains "root=${uuid}"
1204 setenv bootargs "console= root=${uuid}"
1205 # Set the 'uuid' environment variable
1206 part uuid mmc 2:2 uuid
1208 # Command-line substitution will put the real uuid into the
1209 # kernel command line
1212 config USE_BOOTCOMMAND
1213 bool "Enable a default value for bootcmd"
1215 Provide a default value for the bootcmd entry in the environment. If
1216 autoboot is enabled this is what will be run automatically. Enable
1217 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1218 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1219 won't take any space in U-Boot image.
1222 string "bootcmd value"
1223 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1224 default "run distro_bootcmd" if DISTRO_DEFAULTS
1226 This is the string of commands that will be used as bootcmd and if
1227 AUTOBOOT is set, automatically run.
1230 bool "Enable preboot"
1232 When this option is enabled, the existence of the environment
1233 variable "preboot" will be checked immediately before starting the
1234 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1235 entering interactive mode.
1237 This feature is especially useful when "preboot" is automatically
1238 generated or modified. For example, the boot code can modify the
1239 "preboot" when a user holds down a certain combination of keys.
1242 string "preboot default value"
1243 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1244 default "usb start" if USB_KEYBOARD
1247 This is the default of "preboot" environment variable.
1249 config DEFAULT_FDT_FILE
1250 string "Default fdt file"
1252 This option is used to set the default fdt file to boot OS.
1254 config SAVE_PREV_BL_FDT_ADDR
1256 bool "Saves fdt address, passed by the previous bootloader, to env var"
1258 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1259 enable this option to save fdt address, passed by the
1260 previous bootloader for future use.
1261 Address is saved to `prevbl_fdt_addr` environment variable.
1263 If no fdt was provided by previous bootloader, no env variables
1266 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1268 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1270 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1271 enable this option to save initramfs address, passed by the
1272 previous bootloader for future use.
1273 Address is saved to `prevbl_initrd_start_addr` environment variable.
1275 If no initramfs was provided by previous bootloader, no env variables