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.
344 config LEGACY_IMAGE_FORMAT
345 bool "Enable support for the legacy image format"
346 default y if !FIT_SIGNATURE
348 This option enables the legacy image format. It is enabled by
349 default for backward compatibility, unless FIT_SIGNATURE is
350 set where it is disabled so that unsigned images cannot be
351 loaded. If a board needs the legacy image format support in this
352 case, enable it here.
354 config SUPPORT_RAW_INITRD
355 bool "Enable raw initrd images"
357 Note, defining the SUPPORT_RAW_INITRD allows user to supply
358 kernel with raw initrd images. The syntax is slightly different, the
359 address of the initrd must be augmented by it's size, in the following
360 format: "<initrd address>:<initrd size>".
362 config OF_BOARD_SETUP
363 bool "Set up board-specific details in device tree before boot"
366 This causes U-Boot to call ft_board_setup() before booting into
367 the Operating System. This function can set up various
368 board-specific information in the device tree for use by the OS.
369 The device tree is then passed to the OS.
371 config OF_SYSTEM_SETUP
372 bool "Set up system-specific details in device tree before boot"
375 This causes U-Boot to call ft_system_setup() before booting into
376 the Operating System. This function can set up various
377 system-specific information in the device tree for use by the OS.
378 The device tree is then passed to the OS.
380 config OF_STDOUT_VIA_ALIAS
381 bool "Update the device-tree stdout alias from U-Boot"
384 This uses U-Boot's serial alias from the aliases node to update
385 the device tree passed to the OS. The "linux,stdout-path" property
386 in the chosen node is set to point to the correct serial node.
387 This option currently references CONFIG_CONS_INDEX, which is
388 incorrect when used with device tree as this option does not
389 exist / should not be used.
391 config SYS_EXTRA_OPTIONS
392 string "Extra Options (DEPRECATED)"
394 The old configuration infrastructure (= mkconfig + boards.cfg)
395 provided the extra options field. If you have something like
396 "HAS_BAR,BAZ=64", the optional options
398 #define CONFIG_BAZ 64
399 will be defined in include/config.h.
400 This option was prepared for the smooth migration from the old
401 configuration to Kconfig. Since this option will be removed sometime,
402 new boards should not use this option.
404 config HAVE_SYS_TEXT_BASE
406 depends on !NIOS2 && !XTENSA
411 depends on HAVE_SYS_TEXT_BASE
412 default 0x0 if POSITION_INDEPENDENT
413 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
414 default 0x81700000 if MACH_SUNIV
415 default 0x2a000000 if MACH_SUN9I
416 default 0x42e00000 if MACH_SUN8I_V3S
417 default 0x4a000000 if ARCH_SUNXI
420 The address in memory that U-Boot will be running from, initially.
422 config HAVE_SYS_MONITOR_BASE
424 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
425 || FLASH_PIC32 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
429 config SYS_MONITOR_BASE
430 depends on HAVE_SYS_MONITOR_BASE
431 hex "Physical start address of boot monitor code"
432 default SYS_TEXT_BASE
434 The physical start address of boot monitor code (which is the same as
435 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
436 when booting from flash.
438 config SPL_SYS_MONITOR_BASE
439 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
440 hex "Physical start address of SPL monitor code"
441 default SPL_TEXT_BASE
443 config TPL_SYS_MONITOR_BASE
444 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
445 hex "Physical start address of TPL monitor code"
447 config DYNAMIC_SYS_CLK_FREQ
448 bool "Determine CPU clock frequency at run-time"
450 Implement a get_board_sys_clk function that will determine the CPU
451 clock frequency at run time, rather than define it statically.
454 depends on !DYNAMIC_SYS_CLK_FREQ
455 int "CPU clock frequency"
456 default 125000000 if ARCH_LS1012A
457 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
458 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
459 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
460 default 66660000 if ARCH_T2080
461 default 33333333 if RCAR_GEN3
462 default 24000000 if ARCH_EXYNOS
463 default 20000000 if RCAR_GEN2
466 A static value for the CPU frequency. Note that if not required
467 for a given SoC, this can be left at 0.
469 config ARCH_FIXUP_FDT_MEMORY
470 bool "Enable arch_fixup_memory_banks() call"
473 Enable FDT memory map syncup before OS boot. This feature can be
474 used for booting OS with different memory setup where the part of
475 the memory location should be used for different purpose.
478 bool "Support booting Chrome OS"
480 Chrome OS requires U-Boot to set up a table indicating the boot mode
481 (e.g. Developer mode) and a few other things. Enable this if you are
482 booting on a Chromebook to avoid getting an error about an invalid
485 config CHROMEOS_VBOOT
486 bool "Support Chrome OS verified boot"
488 This is intended to enable the full Chrome OS verified boot support
489 in U-Boot. It is not actually implemented in the U-Boot source code
490 at present, so this option is always set to 'n'. It allows
491 distinguishing between booting Chrome OS in a basic way (developer
492 mode) and a full boot.
495 bool "Freescale PBL(pre-boot loader) image format support"
497 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
498 For more details refer to doc/README.pblimage
501 prompt "Freescale PBL load location"
502 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
503 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
507 bool "Freescale PBL is found on SD card"
510 bool "Freescale PBL is found on SPI flash"
514 config SYS_FSL_PBL_PBI
515 string "PBI(pre-boot instructions) commands for the PBL image"
516 depends on RAMBOOT_PBL
518 PBI commands can be used to configure SoC before it starts the execution.
519 Please refer doc/README.pblimage for more details.
521 config SYS_FSL_PBL_RCW
522 string "Aadditional RCW (Power on reset configuration) for the PBL image"
523 depends on RAMBOOT_PBL
525 Enables addition of RCW (Power on reset configuration) in built image.
526 Please refer doc/README.pblimage for more details.
528 endmenu # Boot images
533 bool "Boot timing and reporting"
535 Enable recording of boot time while booting. To use it, insert
536 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
537 bootstage.h. Only a single entry is recorded for each ID. You can
538 give the entry a name with bootstage_mark_name(). You can also
539 record elapsed time in a particular stage using bootstage_start()
540 before starting and bootstage_accum() when finished. Bootstage will
541 add up all the accumulated time and report it.
543 Normally, IDs are defined in bootstage.h but a small number of
544 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
547 Calls to show_boot_progress() will also result in log entries but
548 these will not have names.
551 bool "Boot timing and reported in SPL"
554 Enable recording of boot time in SPL. To make this visible to U-Boot
555 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
556 information when SPL finishes and load it when U-Boot proper starts
560 bool "Boot timing and reported in TPL"
563 Enable recording of boot time in SPL. To make this visible to U-Boot
564 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
565 information when TPL finishes and load it when U-Boot proper starts
568 config BOOTSTAGE_REPORT
569 bool "Display a detailed boot timing report before booting the OS"
572 Enable output of a boot time report just before the OS is booted.
573 This shows how long it took U-Boot to go through each stage of the
574 boot process. The report looks something like this:
576 Timer summary in microseconds:
579 3,575,678 3,575,678 board_init_f start
580 3,575,695 17 arch_cpu_init A9
581 3,575,777 82 arch_cpu_init done
582 3,659,598 83,821 board_init_r start
583 3,910,375 250,777 main_loop
584 29,916,167 26,005,792 bootm_start
585 30,361,327 445,160 start_kernel
587 config BOOTSTAGE_RECORD_COUNT
588 int "Number of boot stage records to store"
592 This is the size of the bootstage record list and is the maximum
593 number of bootstage records that can be recorded.
595 config SPL_BOOTSTAGE_RECORD_COUNT
596 int "Number of boot stage records to store for SPL"
597 depends on SPL_BOOTSTAGE
600 This is the size of the bootstage record list and is the maximum
601 number of bootstage records that can be recorded.
603 config TPL_BOOTSTAGE_RECORD_COUNT
604 int "Number of boot stage records to store for TPL"
605 depends on TPL_BOOTSTAGE
608 This is the size of the bootstage record list and is the maximum
609 number of bootstage records that can be recorded.
612 bool "Store boot timing information in the OS device tree"
615 Stash the bootstage information in the FDT. A root 'bootstage'
616 node is created with each bootstage id as a child. Each child
617 has a 'name' property and either 'mark' containing the
618 mark time in microseconds, or 'accum' containing the
619 accumulated time for that bootstage id in microseconds.
624 name = "board_init_f";
633 Code in the Linux kernel can find this in /proc/devicetree.
635 config BOOTSTAGE_STASH
636 bool "Stash the boot timing information in memory before booting OS"
639 Some OSes do not support device tree. Bootstage can instead write
640 the boot timing information in a binary format at a given address.
641 This happens through a call to bootstage_stash(), typically in
642 the CPU's cleanup_before_linux() function. You can use the
643 'bootstage stash' and 'bootstage unstash' commands to do this on
646 config BOOTSTAGE_STASH_ADDR
647 hex "Address to stash boot timing information"
650 Provide an address which will not be overwritten by the OS when it
651 starts, so that it can read this information when ready.
653 config BOOTSTAGE_STASH_SIZE
654 hex "Size of boot timing stash region"
657 This should be large enough to hold the bootstage stash. A value of
658 4096 (4KiB) is normally plenty.
660 config SHOW_BOOT_PROGRESS
661 bool "Show boot progress in a board-specific manner"
663 Defining this option allows to add some board-specific code (calling
664 a user-provided function show_boot_progress(int) that enables you to
665 show the system's boot progress on some display (for example, some
666 LEDs) on your board. At the moment, the following checkpoints are
669 Legacy uImage format:
672 1 common/cmd_bootm.c before attempting to boot an image
673 -1 common/cmd_bootm.c Image header has bad magic number
674 2 common/cmd_bootm.c Image header has correct magic number
675 -2 common/cmd_bootm.c Image header has bad checksum
676 3 common/cmd_bootm.c Image header has correct checksum
677 -3 common/cmd_bootm.c Image data has bad checksum
678 4 common/cmd_bootm.c Image data has correct checksum
679 -4 common/cmd_bootm.c Image is for unsupported architecture
680 5 common/cmd_bootm.c Architecture check OK
681 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
682 6 common/cmd_bootm.c Image Type check OK
683 -6 common/cmd_bootm.c gunzip uncompression error
684 -7 common/cmd_bootm.c Unimplemented compression type
685 7 common/cmd_bootm.c Uncompression OK
686 8 common/cmd_bootm.c No uncompress/copy overwrite error
687 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
689 9 common/image.c Start initial ramdisk verification
690 -10 common/image.c Ramdisk header has bad magic number
691 -11 common/image.c Ramdisk header has bad checksum
692 10 common/image.c Ramdisk header is OK
693 -12 common/image.c Ramdisk data has bad checksum
694 11 common/image.c Ramdisk data has correct checksum
695 12 common/image.c Ramdisk verification complete, start loading
696 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
697 13 common/image.c Start multifile image verification
698 14 common/image.c No initial ramdisk, no multifile, continue.
700 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
702 -30 arch/powerpc/lib/board.c Fatal error, hang the system
703 -31 post/post.c POST test failed, detected by post_output_backlog()
704 -32 post/post.c POST test failed, detected by post_run_single()
706 34 common/cmd_doc.c before loading a Image from a DOC device
707 -35 common/cmd_doc.c Bad usage of "doc" command
708 35 common/cmd_doc.c correct usage of "doc" command
709 -36 common/cmd_doc.c No boot device
710 36 common/cmd_doc.c correct boot device
711 -37 common/cmd_doc.c Unknown Chip ID on boot device
712 37 common/cmd_doc.c correct chip ID found, device available
713 -38 common/cmd_doc.c Read Error on boot device
714 38 common/cmd_doc.c reading Image header from DOC device OK
715 -39 common/cmd_doc.c Image header has bad magic number
716 39 common/cmd_doc.c Image header has correct magic number
717 -40 common/cmd_doc.c Error reading Image from DOC device
718 40 common/cmd_doc.c Image header has correct magic number
719 41 common/cmd_ide.c before loading a Image from a IDE device
720 -42 common/cmd_ide.c Bad usage of "ide" command
721 42 common/cmd_ide.c correct usage of "ide" command
722 -43 common/cmd_ide.c No boot device
723 43 common/cmd_ide.c boot device found
724 -44 common/cmd_ide.c Device not available
725 44 common/cmd_ide.c Device available
726 -45 common/cmd_ide.c wrong partition selected
727 45 common/cmd_ide.c partition selected
728 -46 common/cmd_ide.c Unknown partition table
729 46 common/cmd_ide.c valid partition table found
730 -47 common/cmd_ide.c Invalid partition type
731 47 common/cmd_ide.c correct partition type
732 -48 common/cmd_ide.c Error reading Image Header on boot device
733 48 common/cmd_ide.c reading Image Header from IDE device OK
734 -49 common/cmd_ide.c Image header has bad magic number
735 49 common/cmd_ide.c Image header has correct magic number
736 -50 common/cmd_ide.c Image header has bad checksum
737 50 common/cmd_ide.c Image header has correct checksum
738 -51 common/cmd_ide.c Error reading Image from IDE device
739 51 common/cmd_ide.c reading Image from IDE device OK
740 52 common/cmd_nand.c before loading a Image from a NAND device
741 -53 common/cmd_nand.c Bad usage of "nand" command
742 53 common/cmd_nand.c correct usage of "nand" command
743 -54 common/cmd_nand.c No boot device
744 54 common/cmd_nand.c boot device found
745 -55 common/cmd_nand.c Unknown Chip ID on boot device
746 55 common/cmd_nand.c correct chip ID found, device available
747 -56 common/cmd_nand.c Error reading Image Header on boot device
748 56 common/cmd_nand.c reading Image Header from NAND device OK
749 -57 common/cmd_nand.c Image header has bad magic number
750 57 common/cmd_nand.c Image header has correct magic number
751 -58 common/cmd_nand.c Error reading Image from NAND device
752 58 common/cmd_nand.c reading Image from NAND device OK
754 -60 common/env_common.c Environment has a bad CRC, using default
756 64 net/eth.c starting with Ethernet configuration.
757 -64 net/eth.c no Ethernet found.
758 65 net/eth.c Ethernet found.
760 -80 common/cmd_net.c usage wrong
761 80 common/cmd_net.c before calling net_loop()
762 -81 common/cmd_net.c some error in net_loop() occurred
763 81 common/cmd_net.c net_loop() back without error
764 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
765 82 common/cmd_net.c trying automatic boot
766 83 common/cmd_net.c running "source" command
767 -83 common/cmd_net.c some error in automatic boot or "source" command
768 84 common/cmd_net.c end without errors
773 100 common/cmd_bootm.c Kernel FIT Image has correct format
774 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
775 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
776 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
777 102 common/cmd_bootm.c Kernel unit name specified
778 -103 common/cmd_bootm.c Can't get kernel subimage node offset
779 103 common/cmd_bootm.c Found configuration node
780 104 common/cmd_bootm.c Got kernel subimage node offset
781 -104 common/cmd_bootm.c Kernel subimage hash verification failed
782 105 common/cmd_bootm.c Kernel subimage hash verification OK
783 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
784 106 common/cmd_bootm.c Architecture check OK
785 -106 common/cmd_bootm.c Kernel subimage has wrong type
786 107 common/cmd_bootm.c Kernel subimage type OK
787 -107 common/cmd_bootm.c Can't get kernel subimage data/size
788 108 common/cmd_bootm.c Got kernel subimage data/size
789 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
790 -109 common/cmd_bootm.c Can't get kernel subimage type
791 -110 common/cmd_bootm.c Can't get kernel subimage comp
792 -111 common/cmd_bootm.c Can't get kernel subimage os
793 -112 common/cmd_bootm.c Can't get kernel subimage load address
794 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
796 120 common/image.c Start initial ramdisk verification
797 -120 common/image.c Ramdisk FIT image has incorrect format
798 121 common/image.c Ramdisk FIT image has correct format
799 122 common/image.c No ramdisk subimage unit name, using configuration
800 -122 common/image.c Can't get configuration for ramdisk subimage
801 123 common/image.c Ramdisk unit name specified
802 -124 common/image.c Can't get ramdisk subimage node offset
803 125 common/image.c Got ramdisk subimage node offset
804 -125 common/image.c Ramdisk subimage hash verification failed
805 126 common/image.c Ramdisk subimage hash verification OK
806 -126 common/image.c Ramdisk subimage for unsupported architecture
807 127 common/image.c Architecture check OK
808 -127 common/image.c Can't get ramdisk subimage data/size
809 128 common/image.c Got ramdisk subimage data/size
810 129 common/image.c Can't get ramdisk load address
811 -129 common/image.c Got ramdisk load address
813 -130 common/cmd_doc.c Incorrect FIT image format
814 131 common/cmd_doc.c FIT image format OK
816 -140 common/cmd_ide.c Incorrect FIT image format
817 141 common/cmd_ide.c FIT image format OK
819 -150 common/cmd_nand.c Incorrect FIT image format
820 151 common/cmd_nand.c FIT image format OK
822 config SPL_SHOW_BOOT_PROGRESS
823 bool "Show boot progress in a board-specific manner in SPL"
826 Defining this option allows to add some board-specific code (calling
827 a user-provided function show_boot_progress(int) that enables you to
828 show the system's boot progress on some display (for example, some
829 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
836 bool "Support for booting from NOR flash"
839 Enabling this will make a U-Boot binary that is capable of being
840 booted via NOR. In this case we will enable certain pinmux early
841 as the ROM only partially sets up pinmux. We also default to using
845 bool "Support for booting from NAND flash"
848 Enabling this will make a U-Boot binary that is capable of being
849 booted via NAND flash. This is not a must, some SoCs need this,
853 bool "Support for booting from ONENAND"
856 Enabling this will make a U-Boot binary that is capable of being
857 booted via ONENAND. This is not a must, some SoCs need this,
861 bool "Support for booting from QSPI flash"
863 Enabling this will make a U-Boot binary that is capable of being
864 booted via QSPI flash. This is not a must, some SoCs need this,
868 bool "Support for booting from SATA"
870 Enabling this will make a U-Boot binary that is capable of being
871 booted via SATA. This is not a must, some SoCs need this,
875 bool "Support for booting from SD/EMMC"
877 Enabling this will make a U-Boot binary that is capable of being
878 booted via SD/EMMC. This is not a must, some SoCs need this,
882 bool "Support for booting from SD/EMMC and enable QSPI"
884 Enabling this will make a U-Boot binary that is capable of being
885 booted via SD/EMMC while enabling QSPI on the platform as well. This
886 is not a must, some SoCs need this, some not.
889 bool "Support for booting from SPI flash"
891 Enabling this will make a U-Boot binary that is capable of being
892 booted via SPI flash. This is not a must, some SoCs need this,
897 menu "Autoboot options"
903 This enables the autoboot. See doc/README.autoboot for detail.
906 int "delay in seconds before automatically booting"
910 Delay before automatically running bootcmd;
911 set to 0 to autoboot with no delay, but you can stop it by key input.
912 set to -1 to disable autoboot.
913 set to -2 to autoboot with no delay and not check for abort
915 If this value is >= 0 then it is also used for the default delay
916 before starting the default entry in bootmenu. If it is < 0 then
917 a default value of 10s is used.
919 See doc/README.autoboot for details.
921 config AUTOBOOT_KEYED
922 bool "Stop autobooting via specific input key / string"
924 This option enables stopping (aborting) of the automatic
925 boot feature only by issuing a specific input key or
926 string. If not enabled, any input key will abort the
927 U-Boot automatic booting process and bring the device
928 to the U-Boot prompt for user input.
930 config AUTOBOOT_FLUSH_STDIN
931 bool "Enable flushing stdin before starting to read the password"
932 depends on AUTOBOOT_KEYED && !SANDBOX
934 When this option is enabled stdin buffer will be flushed before
935 starting to read the password.
936 This can't be enabled for the sandbox as flushing stdin would
937 break the autoboot unit tests.
939 config AUTOBOOT_PROMPT
940 string "Autoboot stop prompt"
941 depends on AUTOBOOT_KEYED
942 default "Autoboot in %d seconds\\n"
944 This string is displayed before the boot delay selected by
945 CONFIG_BOOTDELAY starts. If it is not defined there is no
946 output indicating that autoboot is in progress.
948 Note that this define is used as the (only) argument to a
949 printf() call, so it may contain '%' format specifications,
950 provided that it also includes, sepearated by commas exactly
951 like in a printf statement, the required arguments. It is
952 the responsibility of the user to select only such arguments
953 that are valid in the given context.
955 config AUTOBOOT_ENCRYPTION
956 bool "Enable encryption in autoboot stopping"
957 depends on AUTOBOOT_KEYED
959 This option allows a string to be entered into U-Boot to stop the
961 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
963 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
964 to the crypt-based functionality and be compared against the
965 string in the environment variable 'bootstopkeycrypt'.
966 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
967 and compared against the hash in the environment variable
969 If it matches in either case then boot stops and
970 a command-line prompt is presented.
971 This provides a way to ship a secure production device which can also
972 be accessed at the U-Boot command line.
974 config AUTOBOOT_SHA256_FALLBACK
975 bool "Allow fallback from crypt-hashed password to sha256"
976 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
978 This option adds support to fall back from crypt-hashed
979 passwords to checking a SHA256 hashed password in case the
980 'bootstopusesha256' environment variable is set to 'true'.
982 config AUTOBOOT_DELAY_STR
983 string "Delay autobooting via specific input key / string"
984 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
986 This option delays the automatic boot feature by issuing
987 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
988 or the environment variable "bootdelaykey" is specified
989 and this string is received from console input before
990 autoboot starts booting, U-Boot gives a command prompt. The
991 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
992 used, otherwise it never times out.
994 config AUTOBOOT_STOP_STR
995 string "Stop autobooting via specific input key / string"
996 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
998 This option enables stopping (aborting) of the automatic
999 boot feature only by issuing a specific input key or
1000 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1001 variable "bootstopkey" is specified and this string is
1002 received from console input before autoboot starts booting,
1003 U-Boot gives a command prompt. The U-Boot prompt never
1004 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1006 config AUTOBOOT_KEYED_CTRLC
1007 bool "Enable Ctrl-C autoboot interruption"
1008 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1010 This option allows for the boot sequence to be interrupted
1011 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1012 Setting this variable provides an escape sequence from the
1013 limited "password" strings.
1015 config AUTOBOOT_NEVER_TIMEOUT
1016 bool "Make the password entry never time-out"
1017 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1019 This option removes the timeout from the password entry
1020 when the user first presses the <Enter> key before entering
1021 any other character.
1023 config AUTOBOOT_STOP_STR_ENABLE
1024 bool "Enable fixed string to stop autobooting"
1025 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1027 This option enables the feature to add a fixed stop
1028 string that is defined at compile time.
1029 In every case it will be tried to load the stop
1030 string from the environment.
1031 In case this is enabled and there is no stop string
1032 in the environment, this will be used as default value.
1034 config AUTOBOOT_STOP_STR_CRYPT
1035 string "Stop autobooting via crypt-hashed password"
1036 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1038 This option adds the feature to only stop the autobooting,
1039 and therefore boot into the U-Boot prompt, when the input
1040 string / password matches a values that is hashed via
1041 one of the supported crypt-style password hashing options
1042 and saved in the environment variable "bootstopkeycrypt".
1044 config AUTOBOOT_STOP_STR_SHA256
1045 string "Stop autobooting via SHA256 hashed password"
1046 depends on AUTOBOOT_STOP_STR_ENABLE
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 encypted via
1051 a SHA256 hash and saved in the environment variable
1052 "bootstopkeysha256". If the value in that variable
1053 includes a ":", the portion prior to the ":" will be treated
1056 config AUTOBOOT_USE_MENUKEY
1057 bool "Allow a specify key to run a menu from the environment"
1058 depends on !AUTOBOOT_KEYED
1060 If a specific key is pressed to stop autoboot, then the commands in
1061 the environment variable 'menucmd' are executed before boot starts.
1063 config AUTOBOOT_MENUKEY
1064 int "ASCII value of boot key to show a menu"
1066 depends on AUTOBOOT_USE_MENUKEY
1068 If this key is pressed to stop autoboot, then the commands in the
1069 environment variable 'menucmd' will be executed before boot starts.
1070 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1073 config AUTOBOOT_MENU_SHOW
1074 bool "Show a menu on boot"
1075 depends on CMD_BOOTMENU
1077 This enables the boot menu, controlled by environment variables
1078 defined by the board. The menu starts after running the 'preboot'
1079 environmnent variable (if enabled) and before handling the boot delay.
1080 See README.bootmenu for more details.
1083 bool "Boot retry feature"
1085 Allow for having the U-Boot command prompt time out and attempt
1086 to boot again. If the environment variable "bootretry" is found then
1087 its value is used, otherwise the retry timeout is
1088 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1089 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1091 config BOOT_RETRY_TIME
1092 int "Timeout in seconds before attempting to boot again"
1093 depends on BOOT_RETRY
1095 Time in seconds before the U-Boot prompt will timeout and boot will
1098 config BOOT_RETRY_MIN
1099 int "Minimum timeout in seconds for 'bootretry'"
1100 depends on BOOT_RETRY
1101 default BOOT_RETRY_TIME
1103 The minimum time in seconds that "bootretry" can be set to.
1105 config RESET_TO_RETRY
1106 bool "Reset the board to retry autoboot"
1107 depends on BOOT_RETRY
1109 After the countdown timed out, the board will be reset to restart
1114 menu "Image support"
1116 config IMAGE_PRE_LOAD
1117 bool "Image pre-load support"
1119 Enable an image pre-load stage in the SPL.
1120 This pre-load stage allows to do some manipulation
1121 or check (for example signature check) on an image
1122 before launching it.
1124 config SPL_IMAGE_PRE_LOAD
1125 bool "Image pre-load support within SPL"
1126 depends on SPL && IMAGE_PRE_LOAD
1128 Enable an image pre-load stage in the SPL.
1129 This pre-load stage allows to do some manipulation
1130 or check (for example signature check) on an image
1131 before launching it.
1133 config IMAGE_PRE_LOAD_SIG
1134 bool "Image pre-load signature support"
1135 depends on IMAGE_PRE_LOAD
1136 select FIT_SIGNATURE
1138 select RSA_VERIFY_WITH_PKEY
1140 Enable signature check support in the pre-load stage.
1141 For this feature a very simple header is added before
1142 the image with few fields:
1146 All other information (header size, type of signature,
1147 ...) are provided in the node /image/pre-load/sig of
1150 config SPL_IMAGE_PRE_LOAD_SIG
1151 bool "Image pre-load signature support witin SPL"
1152 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1153 select SPL_FIT_SIGNATURE
1155 select SPL_RSA_VERIFY_WITH_PKEY
1157 Enable signature check support in the pre-load stage in the SPL.
1158 For this feature a very simple header is added before
1159 the image with few fields:
1163 All other information (header size, type of signature,
1164 ...) are provided in the node /image/pre-load/sig of
1170 bool "Enable boot arguments"
1172 Provide boot arguments to bootm command. Boot arguments are specified
1173 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1174 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1175 will be undefined and won't take any space in U-Boot image.
1178 string "Boot arguments"
1179 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1181 This can be used to pass arguments to the bootm command. The value of
1182 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1183 this value will also override the "chosen" node in FDT blob.
1185 config BOOTARGS_SUBST
1186 bool "Support substituting strings in boot arguments"
1188 This allows substituting string values in the boot arguments. These
1189 are applied after the commandline has been built.
1191 One use for this is to insert the root-disk UUID into the command
1192 line where bootargs contains "root=${uuid}"
1194 setenv bootargs "console= root=${uuid}"
1195 # Set the 'uuid' environment variable
1196 part uuid mmc 2:2 uuid
1198 # Command-line substitution will put the real uuid into the
1199 # kernel command line
1202 config USE_BOOTCOMMAND
1203 bool "Enable a default value for bootcmd"
1205 Provide a default value for the bootcmd entry in the environment. If
1206 autoboot is enabled this is what will be run automatically. Enable
1207 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1208 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1209 won't take any space in U-Boot image.
1212 string "bootcmd value"
1213 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1214 default "run distro_bootcmd" if DISTRO_DEFAULTS
1216 This is the string of commands that will be used as bootcmd and if
1217 AUTOBOOT is set, automatically run.
1220 bool "Enable preboot"
1222 When this option is enabled, the existence of the environment
1223 variable "preboot" will be checked immediately before starting the
1224 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1225 entering interactive mode.
1227 This feature is especially useful when "preboot" is automatically
1228 generated or modified. For example, the boot code can modify the
1229 "preboot" when a user holds down a certain combination of keys.
1232 string "preboot default value"
1233 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1234 default "usb start" if USB_KEYBOARD
1237 This is the default of "preboot" environment variable.
1239 config DEFAULT_FDT_FILE
1240 string "Default fdt file"
1242 This option is used to set the default fdt file to boot OS.
1244 config SAVE_PREV_BL_FDT_ADDR
1246 bool "Saves fdt address, passed by the previous bootloader, to env var"
1248 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1249 enable this option to save fdt address, passed by the
1250 previous bootloader for future use.
1251 Address is saved to `prevbl_fdt_addr` environment variable.
1253 If no fdt was provided by previous bootloader, no env variables
1256 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1258 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1260 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1261 enable this option to save initramfs address, passed by the
1262 previous bootloader for future use.
1263 Address is saved to `prevbl_initrd_start_addr` environment variable.
1265 If no initramfs was provided by previous bootloader, no env variables