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).
30 config FIT_EXTERNAL_OFFSET
31 hex "FIT external data offset"
34 This specifies a data offset in fit image.
35 The offset is from data payload offset to the beginning of
36 fit image header. When specifies a offset, specific data
37 could be put in the hole between data payload and fit image
38 header, such as CSF data on i.MX platform.
41 bool "Do a full check of the FIT before using it"
44 Enable this do a full check of the FIT to make sure it is valid. This
45 helps to protect against carefully crafted FITs which take advantage
46 of bugs or omissions in the code. This includes a bad structure,
47 multiple root nodes and the like.
50 bool "Enable signature verification of FIT uImages"
55 select IMAGE_SIGN_INFO
58 This option enables signature verification of FIT uImages,
59 using a hash signed and verified using RSA. If
60 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
61 hashing is available using hardware, then the RSA library will use
62 it. See doc/uImage.FIT/signature.txt for more details.
64 WARNING: When relying on signed FIT images with a required signature
65 check the legacy image format is disabled by default, so that
66 unsigned images cannot be loaded. If a board needs the legacy image
67 format support in this case, enable it using
68 CONFIG_LEGACY_IMAGE_FORMAT.
70 config FIT_SIGNATURE_MAX_SIZE
71 hex "Max size of signed FIT structures"
72 depends on FIT_SIGNATURE
75 This option sets a max size in bytes for verified FIT uImages.
76 A sane value of 256MB protects corrupted DTB structures from overlapping
77 device memory. Assure this size does not extend past expected storage
81 bool "Support rsassa-pss signature scheme of FIT image contents"
82 depends on FIT_SIGNATURE
84 Enable this to support the pss padding algorithm as described
85 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
88 bool "Enable ciphering data in a FIT uImages"
92 Enable the feature of data ciphering/unciphering in the tool mkimage
93 and in the u-boot support of the FIT image.
96 bool "Show verbose messages when FIT images fail"
98 Generally a system will have valid FIT images so debug messages
99 are a waste of code space. If you are debugging your images then
100 you can enable this option to get more verbose information about
103 config FIT_BEST_MATCH
104 bool "Select the best match for the kernel device tree"
106 When no configuration is explicitly selected, default to the
107 one whose fdt's compatibility field best matches that of
108 U-Boot itself. A match is considered "best" if it matches the
109 most specific compatibility entry of U-Boot's fdt's root node.
110 The order of entries in the configuration's fdt is ignored.
112 config FIT_IMAGE_POST_PROCESS
113 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
114 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
116 Allows doing any sort of manipulation to blobs after they got extracted
117 from FIT images like stripping off headers or modifying the size of the
118 blob, verification, authentication, decryption etc. in a platform or
119 board specific way. In order to use this feature a platform or board-
120 specific implementation of board_fit_image_post_process() must be
121 provided. Also, anything done during this post-processing step would
122 need to be comprehended in how the images were prepared before being
123 injected into the FIT creation (i.e. the blobs would have been pre-
124 processed before being added to the FIT image).
127 bool "Support FIT printing"
130 Support printing the content of the fitImage in a verbose manner.
135 bool "Support Flattened Image Tree within SPL"
141 bool "Support FIT printing within SPL"
144 Support printing the content of the fitImage in a verbose manner in SPL.
146 config SPL_FIT_FULL_CHECK
147 bool "Do a full check of the FIT before using it"
149 Enable this do a full check of the FIT to make sure it is valid. This
150 helps to protect against carefully crafted FITs which take advantage
151 of bugs or omissions in the code. This includes a bad structure,
152 multiple root nodes and the like.
155 config SPL_FIT_SIGNATURE
156 bool "Enable signature verification of FIT firmware within SPL"
158 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
165 select SPL_IMAGE_SIGN_INFO
166 select SPL_FIT_FULL_CHECK
168 config SPL_FIT_SIGNATURE_MAX_SIZE
169 hex "Max size of signed FIT structures in SPL"
170 depends on SPL_FIT_SIGNATURE
173 This option sets a max size in bytes for verified FIT uImages.
174 A sane value of 256MB protects corrupted DTB structures from overlapping
175 device memory. Assure this size does not extend past expected storage
179 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
182 Normally with the SPL framework a legacy image is generated as part
183 of the build. This contains U-Boot along with information as to
184 where it should be loaded. This option instead enables generation
185 of a FIT (Flat Image Tree) which provides more flexibility. In
186 particular it can handle selecting from multiple device tree
187 and passing the correct one to U-Boot.
189 This path has the following limitations:
191 1. "loadables" images, other than FDTs, which do not have a "load"
192 property will not be loaded. This limitation also applies to FPGA
193 images with the correct "compatible" string.
194 2. For FPGA images, only the "compatible" = "u-boot,fpga-legacy"
195 loading method is supported.
196 3. FDTs are only loaded for images with an "os" property of "u-boot".
197 "linux" images are also supported with Falcon boot mode.
199 config SPL_LOAD_FIT_ADDRESS
200 hex "load address of fit image"
201 depends on SPL_LOAD_FIT
204 Specify the load address of the fit image that will be loaded
207 config SPL_LOAD_FIT_APPLY_OVERLAY
208 bool "Enable SPL applying DT overlays from FIT"
209 depends on SPL_LOAD_FIT
210 select OF_LIBFDT_OVERLAY
212 The device tree is loaded from the FIT image. Allow the SPL is to
213 also load device-tree overlays from the FIT image an apply them
214 over the device tree.
216 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
217 depends on SPL_LOAD_FIT_APPLY_OVERLAY
219 hex "size of temporary buffer used to load the overlays"
221 The size of the area where the overlays will be loaded and
222 uncompress. Must be at least as large as biggest overlay
225 config SPL_LOAD_FIT_FULL
226 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
229 Normally with the SPL framework a legacy image is generated as part
230 of the build. This contains U-Boot along with information as to
231 where it should be loaded. This option instead enables generation
232 of a FIT (Flat Image Tree) which provides more flexibility. In
233 particular it can handle selecting from multiple device tree
234 and passing the correct one to U-Boot.
236 config SPL_FIT_IMAGE_POST_PROCESS
237 bool "Enable post-processing of FIT artifacts after loading by the SPL"
238 depends on SPL_LOAD_FIT
240 Allows doing any sort of manipulation to blobs after they got extracted
241 from the U-Boot FIT image like stripping off headers or modifying the
242 size of the blob, verification, authentication, decryption etc. in a
243 platform or board specific way. In order to use this feature a platform
244 or board-specific implementation of board_fit_image_post_process() must
245 be provided. Also, anything done during this post-processing step would
246 need to be comprehended in how the images were prepared before being
247 injected into the FIT creation (i.e. the blobs would have been pre-
248 processed before being added to the FIT image).
250 config SPL_FIT_SOURCE
251 string ".its source file for U-Boot FIT image"
254 Specifies a (platform specific) FIT source file to generate the
255 U-Boot FIT image. This could specify further image to load and/or
258 config USE_SPL_FIT_GENERATOR
259 bool "Use a script to generate the .its script"
260 default y if SPL_FIT && (!ARCH_SUNXI && !RISCV)
262 config SPL_FIT_GENERATOR
263 string ".its file generator script for U-Boot FIT image"
264 depends on USE_SPL_FIT_GENERATOR
265 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
266 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
268 Specifies a (platform specific) script file to generate the FIT
269 source file used to build the U-Boot FIT image file. This gets
270 passed a list of supported device tree file stub names to
271 include in the generated image.
277 config LEGACY_IMAGE_FORMAT
278 bool "Enable support for the legacy image format"
279 default y if !FIT_SIGNATURE
281 This option enables the legacy image format. It is enabled by
282 default for backward compatibility, unless FIT_SIGNATURE is
283 set where it is disabled so that unsigned images cannot be
284 loaded. If a board needs the legacy image format support in this
285 case, enable it here.
287 config SUPPORT_RAW_INITRD
288 bool "Enable raw initrd images"
290 Note, defining the SUPPORT_RAW_INITRD allows user to supply
291 kernel with raw initrd images. The syntax is slightly different, the
292 address of the initrd must be augmented by it's size, in the following
293 format: "<initrd address>:<initrd size>".
295 config OF_BOARD_SETUP
296 bool "Set up board-specific details in device tree before boot"
299 This causes U-Boot to call ft_board_setup() before booting into
300 the Operating System. This function can set up various
301 board-specific information in the device tree for use by the OS.
302 The device tree is then passed to the OS.
304 config OF_SYSTEM_SETUP
305 bool "Set up system-specific details in device tree before boot"
308 This causes U-Boot to call ft_system_setup() before booting into
309 the Operating System. This function can set up various
310 system-specific information in the device tree for use by the OS.
311 The device tree is then passed to the OS.
313 config OF_STDOUT_VIA_ALIAS
314 bool "Update the device-tree stdout alias from U-Boot"
317 This uses U-Boot's serial alias from the aliases node to update
318 the device tree passed to the OS. The "linux,stdout-path" property
319 in the chosen node is set to point to the correct serial node.
320 This option currently references CONFIG_CONS_INDEX, which is
321 incorrect when used with device tree as this option does not
322 exist / should not be used.
324 config SYS_EXTRA_OPTIONS
325 string "Extra Options (DEPRECATED)"
327 The old configuration infrastructure (= mkconfig + boards.cfg)
328 provided the extra options field. If you have something like
329 "HAS_BAR,BAZ=64", the optional options
331 #define CONFIG_BAZ 64
332 will be defined in include/config.h.
333 This option was prepared for the smooth migration from the old
334 configuration to Kconfig. Since this option will be removed sometime,
335 new boards should not use this option.
337 config HAVE_SYS_TEXT_BASE
339 depends on !NIOS2 && !XTENSA
344 depends on HAVE_SYS_TEXT_BASE
345 default 0x0 if POSITION_INDEPENDENT
346 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
347 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
348 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
349 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
352 The address in memory that U-Boot will be running from, initially.
355 depends on ARC || ARCH_SUNXI || MPC83xx
356 int "CPU clock frequency"
358 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
360 config ARCH_FIXUP_FDT_MEMORY
361 bool "Enable arch_fixup_memory_banks() call"
364 Enable FDT memory map syncup before OS boot. This feature can be
365 used for booting OS with different memory setup where the part of
366 the memory location should be used for different purpose.
369 bool "Support booting Chrome OS"
371 Chrome OS requires U-Boot to set up a table indicating the boot mode
372 (e.g. Developer mode) and a few other things. Enable this if you are
373 booting on a Chromebook to avoid getting an error about an invalid
376 config CHROMEOS_VBOOT
377 bool "Support Chrome OS verified boot"
379 This is intended to enable the full Chrome OS verified boot support
380 in U-Boot. It is not actually implemented in the U-Boot source code
381 at present, so this option is always set to 'n'. It allows
382 distinguishing between booting Chrome OS in a basic way (developer
383 mode) and a full boot.
386 bool "Freescale PBL(pre-boot loader) image format support"
388 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
389 For more details refer to doc/README.pblimage
391 config SYS_FSL_PBL_PBI
392 string "PBI(pre-boot instructions) commands for the PBL image"
393 depends on RAMBOOT_PBL
395 PBI commands can be used to configure SoC before it starts the execution.
396 Please refer doc/README.pblimage for more details.
398 config SYS_FSL_PBL_RCW
399 string "Aadditional RCW (Power on reset configuration) for the PBL image"
400 depends on RAMBOOT_PBL
402 Enables addition of RCW (Power on reset configuration) in built image.
403 Please refer doc/README.pblimage for more details.
405 endmenu # Boot images
410 bool "Boot timing and reporting"
412 Enable recording of boot time while booting. To use it, insert
413 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
414 bootstage.h. Only a single entry is recorded for each ID. You can
415 give the entry a name with bootstage_mark_name(). You can also
416 record elapsed time in a particular stage using bootstage_start()
417 before starting and bootstage_accum() when finished. Bootstage will
418 add up all the accumulated time and report it.
420 Normally, IDs are defined in bootstage.h but a small number of
421 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
424 Calls to show_boot_progress() will also result in log entries but
425 these will not have names.
428 bool "Boot timing and reported in SPL"
431 Enable recording of boot time in SPL. To make this visible to U-Boot
432 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
433 information when SPL finishes and load it when U-Boot proper starts
437 bool "Boot timing and reported in TPL"
440 Enable recording of boot time in SPL. To make this visible to U-Boot
441 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
442 information when TPL finishes and load it when U-Boot proper starts
445 config BOOTSTAGE_REPORT
446 bool "Display a detailed boot timing report before booting the OS"
449 Enable output of a boot time report just before the OS is booted.
450 This shows how long it took U-Boot to go through each stage of the
451 boot process. The report looks something like this:
453 Timer summary in microseconds:
456 3,575,678 3,575,678 board_init_f start
457 3,575,695 17 arch_cpu_init A9
458 3,575,777 82 arch_cpu_init done
459 3,659,598 83,821 board_init_r start
460 3,910,375 250,777 main_loop
461 29,916,167 26,005,792 bootm_start
462 30,361,327 445,160 start_kernel
464 config BOOTSTAGE_RECORD_COUNT
465 int "Number of boot stage records to store"
469 This is the size of the bootstage record list and is the maximum
470 number of bootstage records that can be recorded.
472 config SPL_BOOTSTAGE_RECORD_COUNT
473 int "Number of boot stage records to store for SPL"
474 depends on SPL_BOOTSTAGE
477 This is the size of the bootstage record list and is the maximum
478 number of bootstage records that can be recorded.
480 config TPL_BOOTSTAGE_RECORD_COUNT
481 int "Number of boot stage records to store for TPL"
482 depends on TPL_BOOTSTAGE
485 This is the size of the bootstage record list and is the maximum
486 number of bootstage records that can be recorded.
489 bool "Store boot timing information in the OS device tree"
492 Stash the bootstage information in the FDT. A root 'bootstage'
493 node is created with each bootstage id as a child. Each child
494 has a 'name' property and either 'mark' containing the
495 mark time in microseconds, or 'accum' containing the
496 accumulated time for that bootstage id in microseconds.
501 name = "board_init_f";
510 Code in the Linux kernel can find this in /proc/devicetree.
512 config BOOTSTAGE_STASH
513 bool "Stash the boot timing information in memory before booting OS"
516 Some OSes do not support device tree. Bootstage can instead write
517 the boot timing information in a binary format at a given address.
518 This happens through a call to bootstage_stash(), typically in
519 the CPU's cleanup_before_linux() function. You can use the
520 'bootstage stash' and 'bootstage unstash' commands to do this on
523 config BOOTSTAGE_STASH_ADDR
524 hex "Address to stash boot timing information"
527 Provide an address which will not be overwritten by the OS when it
528 starts, so that it can read this information when ready.
530 config BOOTSTAGE_STASH_SIZE
531 hex "Size of boot timing stash region"
534 This should be large enough to hold the bootstage stash. A value of
535 4096 (4KiB) is normally plenty.
537 config SHOW_BOOT_PROGRESS
538 bool "Show boot progress in a board-specific manner"
540 Defining this option allows to add some board-specific code (calling
541 a user-provided function show_boot_progress(int) that enables you to
542 show the system's boot progress on some display (for example, some
543 LEDs) on your board. At the moment, the following checkpoints are
546 Legacy uImage format:
549 1 common/cmd_bootm.c before attempting to boot an image
550 -1 common/cmd_bootm.c Image header has bad magic number
551 2 common/cmd_bootm.c Image header has correct magic number
552 -2 common/cmd_bootm.c Image header has bad checksum
553 3 common/cmd_bootm.c Image header has correct checksum
554 -3 common/cmd_bootm.c Image data has bad checksum
555 4 common/cmd_bootm.c Image data has correct checksum
556 -4 common/cmd_bootm.c Image is for unsupported architecture
557 5 common/cmd_bootm.c Architecture check OK
558 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
559 6 common/cmd_bootm.c Image Type check OK
560 -6 common/cmd_bootm.c gunzip uncompression error
561 -7 common/cmd_bootm.c Unimplemented compression type
562 7 common/cmd_bootm.c Uncompression OK
563 8 common/cmd_bootm.c No uncompress/copy overwrite error
564 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
566 9 common/image.c Start initial ramdisk verification
567 -10 common/image.c Ramdisk header has bad magic number
568 -11 common/image.c Ramdisk header has bad checksum
569 10 common/image.c Ramdisk header is OK
570 -12 common/image.c Ramdisk data has bad checksum
571 11 common/image.c Ramdisk data has correct checksum
572 12 common/image.c Ramdisk verification complete, start loading
573 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
574 13 common/image.c Start multifile image verification
575 14 common/image.c No initial ramdisk, no multifile, continue.
577 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
579 -30 arch/powerpc/lib/board.c Fatal error, hang the system
580 -31 post/post.c POST test failed, detected by post_output_backlog()
581 -32 post/post.c POST test failed, detected by post_run_single()
583 34 common/cmd_doc.c before loading a Image from a DOC device
584 -35 common/cmd_doc.c Bad usage of "doc" command
585 35 common/cmd_doc.c correct usage of "doc" command
586 -36 common/cmd_doc.c No boot device
587 36 common/cmd_doc.c correct boot device
588 -37 common/cmd_doc.c Unknown Chip ID on boot device
589 37 common/cmd_doc.c correct chip ID found, device available
590 -38 common/cmd_doc.c Read Error on boot device
591 38 common/cmd_doc.c reading Image header from DOC device OK
592 -39 common/cmd_doc.c Image header has bad magic number
593 39 common/cmd_doc.c Image header has correct magic number
594 -40 common/cmd_doc.c Error reading Image from DOC device
595 40 common/cmd_doc.c Image header has correct magic number
596 41 common/cmd_ide.c before loading a Image from a IDE device
597 -42 common/cmd_ide.c Bad usage of "ide" command
598 42 common/cmd_ide.c correct usage of "ide" command
599 -43 common/cmd_ide.c No boot device
600 43 common/cmd_ide.c boot device found
601 -44 common/cmd_ide.c Device not available
602 44 common/cmd_ide.c Device available
603 -45 common/cmd_ide.c wrong partition selected
604 45 common/cmd_ide.c partition selected
605 -46 common/cmd_ide.c Unknown partition table
606 46 common/cmd_ide.c valid partition table found
607 -47 common/cmd_ide.c Invalid partition type
608 47 common/cmd_ide.c correct partition type
609 -48 common/cmd_ide.c Error reading Image Header on boot device
610 48 common/cmd_ide.c reading Image Header from IDE device OK
611 -49 common/cmd_ide.c Image header has bad magic number
612 49 common/cmd_ide.c Image header has correct magic number
613 -50 common/cmd_ide.c Image header has bad checksum
614 50 common/cmd_ide.c Image header has correct checksum
615 -51 common/cmd_ide.c Error reading Image from IDE device
616 51 common/cmd_ide.c reading Image from IDE device OK
617 52 common/cmd_nand.c before loading a Image from a NAND device
618 -53 common/cmd_nand.c Bad usage of "nand" command
619 53 common/cmd_nand.c correct usage of "nand" command
620 -54 common/cmd_nand.c No boot device
621 54 common/cmd_nand.c boot device found
622 -55 common/cmd_nand.c Unknown Chip ID on boot device
623 55 common/cmd_nand.c correct chip ID found, device available
624 -56 common/cmd_nand.c Error reading Image Header on boot device
625 56 common/cmd_nand.c reading Image Header from NAND device OK
626 -57 common/cmd_nand.c Image header has bad magic number
627 57 common/cmd_nand.c Image header has correct magic number
628 -58 common/cmd_nand.c Error reading Image from NAND device
629 58 common/cmd_nand.c reading Image from NAND device OK
631 -60 common/env_common.c Environment has a bad CRC, using default
633 64 net/eth.c starting with Ethernet configuration.
634 -64 net/eth.c no Ethernet found.
635 65 net/eth.c Ethernet found.
637 -80 common/cmd_net.c usage wrong
638 80 common/cmd_net.c before calling net_loop()
639 -81 common/cmd_net.c some error in net_loop() occurred
640 81 common/cmd_net.c net_loop() back without error
641 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
642 82 common/cmd_net.c trying automatic boot
643 83 common/cmd_net.c running "source" command
644 -83 common/cmd_net.c some error in automatic boot or "source" command
645 84 common/cmd_net.c end without errors
650 100 common/cmd_bootm.c Kernel FIT Image has correct format
651 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
652 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
653 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
654 102 common/cmd_bootm.c Kernel unit name specified
655 -103 common/cmd_bootm.c Can't get kernel subimage node offset
656 103 common/cmd_bootm.c Found configuration node
657 104 common/cmd_bootm.c Got kernel subimage node offset
658 -104 common/cmd_bootm.c Kernel subimage hash verification failed
659 105 common/cmd_bootm.c Kernel subimage hash verification OK
660 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
661 106 common/cmd_bootm.c Architecture check OK
662 -106 common/cmd_bootm.c Kernel subimage has wrong type
663 107 common/cmd_bootm.c Kernel subimage type OK
664 -107 common/cmd_bootm.c Can't get kernel subimage data/size
665 108 common/cmd_bootm.c Got kernel subimage data/size
666 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
667 -109 common/cmd_bootm.c Can't get kernel subimage type
668 -110 common/cmd_bootm.c Can't get kernel subimage comp
669 -111 common/cmd_bootm.c Can't get kernel subimage os
670 -112 common/cmd_bootm.c Can't get kernel subimage load address
671 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
673 120 common/image.c Start initial ramdisk verification
674 -120 common/image.c Ramdisk FIT image has incorrect format
675 121 common/image.c Ramdisk FIT image has correct format
676 122 common/image.c No ramdisk subimage unit name, using configuration
677 -122 common/image.c Can't get configuration for ramdisk subimage
678 123 common/image.c Ramdisk unit name specified
679 -124 common/image.c Can't get ramdisk subimage node offset
680 125 common/image.c Got ramdisk subimage node offset
681 -125 common/image.c Ramdisk subimage hash verification failed
682 126 common/image.c Ramdisk subimage hash verification OK
683 -126 common/image.c Ramdisk subimage for unsupported architecture
684 127 common/image.c Architecture check OK
685 -127 common/image.c Can't get ramdisk subimage data/size
686 128 common/image.c Got ramdisk subimage data/size
687 129 common/image.c Can't get ramdisk load address
688 -129 common/image.c Got ramdisk load address
690 -130 common/cmd_doc.c Incorrect FIT image format
691 131 common/cmd_doc.c FIT image format OK
693 -140 common/cmd_ide.c Incorrect FIT image format
694 141 common/cmd_ide.c FIT image format OK
696 -150 common/cmd_nand.c Incorrect FIT image format
697 151 common/cmd_nand.c FIT image format OK
704 bool "Support for booting from NOR flash"
707 Enabling this will make a U-Boot binary that is capable of being
708 booted via NOR. In this case we will enable certain pinmux early
709 as the ROM only partially sets up pinmux. We also default to using
713 bool "Support for booting from NAND flash"
716 Enabling this will make a U-Boot binary that is capable of being
717 booted via NAND flash. This is not a must, some SoCs need this,
721 bool "Support for booting from ONENAND"
724 Enabling this will make a U-Boot binary that is capable of being
725 booted via ONENAND. This is not a must, some SoCs need this,
729 bool "Support for booting from QSPI flash"
731 Enabling this will make a U-Boot binary that is capable of being
732 booted via QSPI flash. This is not a must, some SoCs need this,
736 bool "Support for booting from SATA"
738 Enabling this will make a U-Boot binary that is capable of being
739 booted via SATA. This is not a must, some SoCs need this,
743 bool "Support for booting from SD/EMMC"
745 Enabling this will make a U-Boot binary that is capable of being
746 booted via SD/EMMC. This is not a must, some SoCs need this,
750 bool "Support for booting from SPI flash"
752 Enabling this will make a U-Boot binary that is capable of being
753 booted via SPI flash. This is not a must, some SoCs need this,
758 menu "Autoboot options"
764 This enables the autoboot. See doc/README.autoboot for detail.
767 int "delay in seconds before automatically booting"
771 Delay before automatically running bootcmd;
772 set to 0 to autoboot with no delay, but you can stop it by key input.
773 set to -1 to disable autoboot.
774 set to -2 to autoboot with no delay and not check for abort
776 If this value is >= 0 then it is also used for the default delay
777 before starting the default entry in bootmenu. If it is < 0 then
778 a default value of 10s is used.
780 See doc/README.autoboot for details.
782 config AUTOBOOT_KEYED
783 bool "Stop autobooting via specific input key / string"
785 This option enables stopping (aborting) of the automatic
786 boot feature only by issuing a specific input key or
787 string. If not enabled, any input key will abort the
788 U-Boot automatic booting process and bring the device
789 to the U-Boot prompt for user input.
791 config AUTOBOOT_FLUSH_STDIN
792 bool "Enable flushing stdin before starting to read the password"
793 depends on AUTOBOOT_KEYED && !SANDBOX
795 When this option is enabled stdin buffer will be flushed before
796 starting to read the password.
797 This can't be enabled for the sandbox as flushing stdin would
798 break the autoboot unit tests.
800 config AUTOBOOT_PROMPT
801 string "Autoboot stop prompt"
802 depends on AUTOBOOT_KEYED
803 default "Autoboot in %d seconds\\n"
805 This string is displayed before the boot delay selected by
806 CONFIG_BOOTDELAY starts. If it is not defined there is no
807 output indicating that autoboot is in progress.
809 Note that this define is used as the (only) argument to a
810 printf() call, so it may contain '%' format specifications,
811 provided that it also includes, sepearated by commas exactly
812 like in a printf statement, the required arguments. It is
813 the responsibility of the user to select only such arguments
814 that are valid in the given context.
816 config AUTOBOOT_ENCRYPTION
817 bool "Enable encryption in autoboot stopping"
818 depends on AUTOBOOT_KEYED
820 This option allows a string to be entered into U-Boot to stop the
822 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
824 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
825 to the crypt-based functionality and be compared against the
826 string in the environment variable 'bootstopkeycrypt'.
827 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
828 and compared against the hash in the environment variable
830 If it matches in either case then boot stops and
831 a command-line prompt is presented.
832 This provides a way to ship a secure production device which can also
833 be accessed at the U-Boot command line.
835 config AUTOBOOT_SHA256_FALLBACK
836 bool "Allow fallback from crypt-hashed password to sha256"
837 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
839 This option adds support to fall back from crypt-hashed
840 passwords to checking a SHA256 hashed password in case the
841 'bootstopusesha256' environment variable is set to 'true'.
843 config AUTOBOOT_DELAY_STR
844 string "Delay autobooting via specific input key / string"
845 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
847 This option delays the automatic boot feature by issuing
848 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
849 or the environment variable "bootdelaykey" is specified
850 and this string is received from console input before
851 autoboot starts booting, U-Boot gives a command prompt. The
852 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
853 used, otherwise it never times out.
855 config AUTOBOOT_STOP_STR
856 string "Stop autobooting via specific input key / string"
857 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
859 This option enables stopping (aborting) of the automatic
860 boot feature only by issuing a specific input key or
861 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
862 variable "bootstopkey" is specified and this string is
863 received from console input before autoboot starts booting,
864 U-Boot gives a command prompt. The U-Boot prompt never
865 times out, even if CONFIG_BOOT_RETRY_TIME is used.
867 config AUTOBOOT_KEYED_CTRLC
868 bool "Enable Ctrl-C autoboot interruption"
869 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
871 This option allows for the boot sequence to be interrupted
872 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
873 Setting this variable provides an escape sequence from the
874 limited "password" strings.
876 config AUTOBOOT_NEVER_TIMEOUT
877 bool "Make the password entry never time-out"
878 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
880 This option removes the timeout from the password entry
881 when the user first presses the <Enter> key before entering
884 config AUTOBOOT_STOP_STR_ENABLE
885 bool "Enable fixed string to stop autobooting"
886 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
888 This option enables the feature to add a fixed stop
889 string that is defined at compile time.
890 In every case it will be tried to load the stop
891 string from the environment.
892 In case this is enabled and there is no stop string
893 in the environment, this will be used as default value.
895 config AUTOBOOT_STOP_STR_CRYPT
896 string "Stop autobooting via crypt-hashed password"
897 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
899 This option adds the feature to only stop the autobooting,
900 and therefore boot into the U-Boot prompt, when the input
901 string / password matches a values that is hashed via
902 one of the supported crypt-style password hashing options
903 and saved in the environment variable "bootstopkeycrypt".
905 config AUTOBOOT_STOP_STR_SHA256
906 string "Stop autobooting via SHA256 hashed password"
907 depends on AUTOBOOT_STOP_STR_ENABLE
909 This option adds the feature to only stop the autobooting,
910 and therefore boot into the U-Boot prompt, when the input
911 string / password matches a values that is encypted via
912 a SHA256 hash and saved in the environment variable
913 "bootstopkeysha256". If the value in that variable
914 includes a ":", the portion prior to the ":" will be treated
917 config AUTOBOOT_USE_MENUKEY
918 bool "Allow a specify key to run a menu from the environment"
919 depends on !AUTOBOOT_KEYED
921 If a specific key is pressed to stop autoboot, then the commands in
922 the environment variable 'menucmd' are executed before boot starts.
924 config AUTOBOOT_MENUKEY
925 int "ASCII value of boot key to show a menu"
927 depends on AUTOBOOT_USE_MENUKEY
929 If this key is pressed to stop autoboot, then the commands in the
930 environment variable 'menucmd' will be executed before boot starts.
931 For example, 33 means "!" in ASCII, so pressing ! at boot would take
934 config AUTOBOOT_MENU_SHOW
935 bool "Show a menu on boot"
936 depends on CMD_BOOTMENU
938 This enables the boot menu, controlled by environment variables
939 defined by the board. The menu starts after running the 'preboot'
940 environmnent variable (if enabled) and before handling the boot delay.
941 See README.bootmenu for more details.
946 bool "Enable boot arguments"
948 Provide boot arguments to bootm command. Boot arguments are specified
949 in CONFIG_BOOTARGS option. Enable this option to be able to specify
950 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
951 will be undefined and won't take any space in U-Boot image.
954 string "Boot arguments"
955 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
957 This can be used to pass arguments to the bootm command. The value of
958 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
959 this value will also override the "chosen" node in FDT blob.
961 config BOOTARGS_SUBST
962 bool "Support substituting strings in boot arguments"
964 This allows substituting string values in the boot arguments. These
965 are applied after the commandline has been built.
967 One use for this is to insert the root-disk UUID into the command
968 line where bootargs contains "root=${uuid}"
970 setenv bootargs "console= root=${uuid}"
971 # Set the 'uuid' environment variable
972 part uuid mmc 2:2 uuid
974 # Command-line substitution will put the real uuid into the
975 # kernel command line
978 config USE_BOOTCOMMAND
979 bool "Enable a default value for bootcmd"
981 Provide a default value for the bootcmd entry in the environment. If
982 autoboot is enabled this is what will be run automatically. Enable
983 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
984 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
985 won't take any space in U-Boot image.
988 string "bootcmd value"
989 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
990 default "run distro_bootcmd" if DISTRO_DEFAULTS
992 This is the string of commands that will be used as bootcmd and if
993 AUTOBOOT is set, automatically run.
996 bool "Enable preboot"
998 When this option is enabled, the existence of the environment
999 variable "preboot" will be checked immediately before starting the
1000 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1001 entering interactive mode.
1003 This feature is especially useful when "preboot" is automatically
1004 generated or modified. For example, the boot code can modify the
1005 "preboot" when a user holds down a certain combination of keys.
1008 string "preboot default value"
1009 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1010 default "usb start" if USB_KEYBOARD
1013 This is the default of "preboot" environment variable.
1015 config DEFAULT_FDT_FILE
1016 string "Default fdt file"
1018 This option is used to set the default fdt file to boot OS.