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"
17 This option allows you to boot the new uImage structure,
18 Flattened Image Tree. FIT is formally a FDT, which can include
19 images of various types (kernel, FDT blob, ramdisk, etc.)
20 in a single blob. To boot this new uImage structure,
21 pass the address of the blob to the "bootm" command.
22 FIT is very flexible, supporting compression, multiple images,
23 multiple configurations, verification through hashing and also
24 verified boot (secure boot using RSA).
28 config FIT_EXTERNAL_OFFSET
29 hex "FIT external data offset"
32 This specifies a data offset in fit image.
33 The offset is from data payload offset to the beginning of
34 fit image header. When specifies a offset, specific data
35 could be put in the hole between data payload and fit image
36 header, such as CSF data on i.MX platform.
38 config FIT_ENABLE_SHA256_SUPPORT
39 bool "Support SHA256 checksum of FIT image contents"
43 Enable this to support SHA256 checksum of FIT image contents. A
44 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
45 the image contents have not been corrupted.
47 config FIT_ENABLE_SHA384_SUPPORT
48 bool "Support SHA384 checksum of FIT image contents"
52 Enable this to support SHA384 checksum of FIT image contents. A
53 SHA384 checksum is a 384-bit (48-byte) hash value used to check that
54 the image contents have not been corrupted. Use this for the highest
57 config FIT_ENABLE_SHA512_SUPPORT
58 bool "Support SHA512 checksum of FIT image contents"
62 Enable this to support SHA512 checksum of FIT image contents. A
63 SHA512 checksum is a 512-bit (64-byte) hash value used to check that
64 the image contents have not been corrupted.
67 bool "Do a full check of the FIT before using it"
70 Enable this do a full check of the FIT to make sure it is valid. This
71 helps to protect against carefully crafted FITs which take advantage
72 of bugs or omissions in the code. This includes a bad structure,
73 multiple root nodes and the like.
76 bool "Enable signature verification of FIT uImages"
81 select IMAGE_SIGN_INFO
84 This option enables signature verification of FIT uImages,
85 using a hash signed and verified using RSA. If
86 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
87 hashing is available using hardware, then the RSA library will use
88 it. See doc/uImage.FIT/signature.txt for more details.
90 WARNING: When relying on signed FIT images with a required signature
91 check the legacy image format is disabled by default, so that
92 unsigned images cannot be loaded. If a board needs the legacy image
93 format support in this case, enable it using
94 CONFIG_LEGACY_IMAGE_FORMAT.
96 config FIT_SIGNATURE_MAX_SIZE
97 hex "Max size of signed FIT structures"
98 depends on FIT_SIGNATURE
101 This option sets a max size in bytes for verified FIT uImages.
102 A sane value of 256MB protects corrupted DTB structures from overlapping
103 device memory. Assure this size does not extend past expected storage
106 config FIT_ENABLE_RSASSA_PSS_SUPPORT
107 bool "Support rsassa-pss signature scheme of FIT image contents"
108 depends on FIT_SIGNATURE
111 Enable this to support the pss padding algorithm as described
112 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
115 bool "Enable ciphering data in a FIT uImages"
119 Enable the feature of data ciphering/unciphering in the tool mkimage
120 and in the u-boot support of the FIT image.
123 bool "Show verbose messages when FIT images fail"
125 Generally a system will have valid FIT images so debug messages
126 are a waste of code space. If you are debugging your images then
127 you can enable this option to get more verbose information about
130 config FIT_BEST_MATCH
131 bool "Select the best match for the kernel device tree"
133 When no configuration is explicitly selected, default to the
134 one whose fdt's compatibility field best matches that of
135 U-Boot itself. A match is considered "best" if it matches the
136 most specific compatibility entry of U-Boot's fdt's root node.
137 The order of entries in the configuration's fdt is ignored.
139 config FIT_IMAGE_POST_PROCESS
140 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
141 depends on TI_SECURE_DEVICE
143 Allows doing any sort of manipulation to blobs after they got extracted
144 from FIT images like stripping off headers or modifying the size of the
145 blob, verification, authentication, decryption etc. in a platform or
146 board specific way. In order to use this feature a platform or board-
147 specific implementation of board_fit_image_post_process() must be
148 provided. Also, anything done during this post-processing step would
149 need to be comprehended in how the images were prepared before being
150 injected into the FIT creation (i.e. the blobs would have been pre-
151 processed before being added to the FIT image).
154 bool "Support FIT printing"
157 Support printing the content of the fitImage in a verbose manner.
162 bool "Support Flattened Image Tree within SPL"
167 bool "Support FIT printing within SPL"
170 Support printing the content of the fitImage in a verbose manner in SPL.
172 config SPL_FIT_FULL_CHECK
173 bool "Do a full check of the FIT before using it"
175 Enable this do a full check of the FIT to make sure it is valid. This
176 helps to protect against carefully crafted FITs which take advantage
177 of bugs or omissions in the code. This includes a bad structure,
178 multiple root nodes and the like.
181 config SPL_FIT_SIGNATURE
182 bool "Enable signature verification of FIT firmware within SPL"
184 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
187 select SPL_CRYPTO_SUPPORT
188 select SPL_HASH_SUPPORT
190 select SPL_RSA_VERIFY
191 select SPL_IMAGE_SIGN_INFO
192 select SPL_FIT_FULL_CHECK
195 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
198 Normally with the SPL framework a legacy image is generated as part
199 of the build. This contains U-Boot along with information as to
200 where it should be loaded. This option instead enables generation
201 of a FIT (Flat Image Tree) which provides more flexibility. In
202 particular it can handle selecting from multiple device tree
203 and passing the correct one to U-Boot.
205 config SPL_LOAD_FIT_ADDRESS
206 hex "load address of fit image"
207 depends on SPL_LOAD_FIT
210 Specify the load address of the fit image that will be loaded
213 config SPL_LOAD_FIT_APPLY_OVERLAY
214 bool "Enable SPL applying DT overlays from FIT"
215 depends on SPL_LOAD_FIT
216 select OF_LIBFDT_OVERLAY
218 The device tree is loaded from the FIT image. Allow the SPL is to
219 also load device-tree overlays from the FIT image an apply them
220 over the device tree.
222 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
223 depends on SPL_LOAD_FIT_APPLY_OVERLAY
225 hex "size of temporary buffer used to load the overlays"
227 The size of the area where the overlays will be loaded and
228 uncompress. Must be at least as large as biggest overlay
231 config SPL_LOAD_FIT_FULL
232 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
235 Normally with the SPL framework a legacy image is generated as part
236 of the build. This contains U-Boot along with information as to
237 where it should be loaded. This option instead enables generation
238 of a FIT (Flat Image Tree) which provides more flexibility. In
239 particular it can handle selecting from multiple device tree
240 and passing the correct one to U-Boot.
242 config SPL_FIT_IMAGE_POST_PROCESS
243 bool "Enable post-processing of FIT artifacts after loading by the SPL"
244 depends on SPL_LOAD_FIT
246 Allows doing any sort of manipulation to blobs after they got extracted
247 from the U-Boot FIT image like stripping off headers or modifying the
248 size of the blob, verification, authentication, decryption etc. in a
249 platform or board specific way. In order to use this feature a platform
250 or board-specific implementation of board_fit_image_post_process() must
251 be provided. Also, anything done during this post-processing step would
252 need to be comprehended in how the images were prepared before being
253 injected into the FIT creation (i.e. the blobs would have been pre-
254 processed before being added to the FIT image).
256 config SPL_FIT_SOURCE
257 string ".its source file for U-Boot FIT image"
260 Specifies a (platform specific) FIT source file to generate the
261 U-Boot FIT image. This could specify further image to load and/or
264 config USE_SPL_FIT_GENERATOR
265 bool "Use a script to generate the .its script"
266 default y if SPL_FIT && !ARCH_SUNXI
268 config SPL_FIT_GENERATOR
269 string ".its file generator script for U-Boot FIT image"
270 depends on USE_SPL_FIT_GENERATOR
271 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
272 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
273 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
275 Specifies a (platform specific) script file to generate the FIT
276 source file used to build the U-Boot FIT image file. This gets
277 passed a list of supported device tree file stub names to
278 include in the generated image.
284 config LEGACY_IMAGE_FORMAT
285 bool "Enable support for the legacy image format"
286 default y if !FIT_SIGNATURE
288 This option enables the legacy image format. It is enabled by
289 default for backward compatibility, unless FIT_SIGNATURE is
290 set where it is disabled so that unsigned images cannot be
291 loaded. If a board needs the legacy image format support in this
292 case, enable it here.
294 config SUPPORT_RAW_INITRD
295 bool "Enable raw initrd images"
297 Note, defining the SUPPORT_RAW_INITRD allows user to supply
298 kernel with raw initrd images. The syntax is slightly different, the
299 address of the initrd must be augmented by it's size, in the following
300 format: "<initrd address>:<initrd size>".
302 config OF_BOARD_SETUP
303 bool "Set up board-specific details in device tree before boot"
306 This causes U-Boot to call ft_board_setup() before booting into
307 the Operating System. This function can set up various
308 board-specific information in the device tree for use by the OS.
309 The device tree is then passed to the OS.
311 config OF_SYSTEM_SETUP
312 bool "Set up system-specific details in device tree before boot"
315 This causes U-Boot to call ft_system_setup() before booting into
316 the Operating System. This function can set up various
317 system-specific information in the device tree for use by the OS.
318 The device tree is then passed to the OS.
320 config OF_STDOUT_VIA_ALIAS
321 bool "Update the device-tree stdout alias from U-Boot"
324 This uses U-Boot's serial alias from the aliases node to update
325 the device tree passed to the OS. The "linux,stdout-path" property
326 in the chosen node is set to point to the correct serial node.
327 This option currently references CONFIG_CONS_INDEX, which is
328 incorrect when used with device tree as this option does not
329 exist / should not be used.
331 config SYS_EXTRA_OPTIONS
332 string "Extra Options (DEPRECATED)"
334 The old configuration infrastructure (= mkconfig + boards.cfg)
335 provided the extra options field. If you have something like
336 "HAS_BAR,BAZ=64", the optional options
338 #define CONFIG_BAZ 64
339 will be defined in include/config.h.
340 This option was prepared for the smooth migration from the old
341 configuration to Kconfig. Since this option will be removed sometime,
342 new boards should not use this option.
344 config HAVE_SYS_TEXT_BASE
346 depends on !NIOS2 && !XTENSA
351 depends on HAVE_SYS_TEXT_BASE
352 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
353 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
354 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
355 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
358 The address in memory that U-Boot will be running from, initially.
361 depends on ARC || ARCH_SUNXI || MPC83xx
362 int "CPU clock frequency"
364 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
366 config ARCH_FIXUP_FDT_MEMORY
367 bool "Enable arch_fixup_memory_banks() call"
370 Enable FDT memory map syncup before OS boot. This feature can be
371 used for booting OS with different memory setup where the part of
372 the memory location should be used for different purpose.
375 bool "Support booting Chrome OS"
377 Chrome OS requires U-Boot to set up a table indicating the boot mode
378 (e.g. Developer mode) and a few other things. Enable this if you are
379 booting on a Chromebook to avoid getting an error about an invalid
382 config CHROMEOS_VBOOT
383 bool "Support Chrome OS verified boot"
385 This is intended to enable the full Chrome OS verified boot support
386 in U-Boot. It is not actually implemented in the U-Boot source code
387 at present, so this option is always set to 'n'. It allows
388 distinguishing between booting Chrome OS in a basic way (developer
389 mode) and a full boot.
391 endmenu # Boot images
396 bool "Boot timing and reporting"
398 Enable recording of boot time while booting. To use it, insert
399 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
400 bootstage.h. Only a single entry is recorded for each ID. You can
401 give the entry a name with bootstage_mark_name(). You can also
402 record elapsed time in a particular stage using bootstage_start()
403 before starting and bootstage_accum() when finished. Bootstage will
404 add up all the accumulated time and report it.
406 Normally, IDs are defined in bootstage.h but a small number of
407 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
410 Calls to show_boot_progress() will also result in log entries but
411 these will not have names.
414 bool "Boot timing and reported in SPL"
417 Enable recording of boot time in SPL. To make this visible to U-Boot
418 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
419 information when SPL finishes and load it when U-Boot proper starts
423 bool "Boot timing and reported in TPL"
426 Enable recording of boot time in SPL. To make this visible to U-Boot
427 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
428 information when TPL finishes and load it when U-Boot proper starts
431 config BOOTSTAGE_REPORT
432 bool "Display a detailed boot timing report before booting the OS"
435 Enable output of a boot time report just before the OS is booted.
436 This shows how long it took U-Boot to go through each stage of the
437 boot process. The report looks something like this:
439 Timer summary in microseconds:
442 3,575,678 3,575,678 board_init_f start
443 3,575,695 17 arch_cpu_init A9
444 3,575,777 82 arch_cpu_init done
445 3,659,598 83,821 board_init_r start
446 3,910,375 250,777 main_loop
447 29,916,167 26,005,792 bootm_start
448 30,361,327 445,160 start_kernel
450 config BOOTSTAGE_RECORD_COUNT
451 int "Number of boot stage records to store"
454 This is the size of the bootstage record list and is the maximum
455 number of bootstage records that can be recorded.
457 config SPL_BOOTSTAGE_RECORD_COUNT
458 int "Number of boot stage records to store for SPL"
461 This is the size of the bootstage record list and is the maximum
462 number of bootstage records that can be recorded.
464 config TPL_BOOTSTAGE_RECORD_COUNT
465 int "Number of boot stage records to store for TPL"
468 This is the size of the bootstage record list and is the maximum
469 number of bootstage records that can be recorded.
472 bool "Store boot timing information in the OS device tree"
475 Stash the bootstage information in the FDT. A root 'bootstage'
476 node is created with each bootstage id as a child. Each child
477 has a 'name' property and either 'mark' containing the
478 mark time in microseconds, or 'accum' containing the
479 accumulated time for that bootstage id in microseconds.
484 name = "board_init_f";
493 Code in the Linux kernel can find this in /proc/devicetree.
495 config BOOTSTAGE_STASH
496 bool "Stash the boot timing information in memory before booting OS"
499 Some OSes do not support device tree. Bootstage can instead write
500 the boot timing information in a binary format at a given address.
501 This happens through a call to bootstage_stash(), typically in
502 the CPU's cleanup_before_linux() function. You can use the
503 'bootstage stash' and 'bootstage unstash' commands to do this on
506 config BOOTSTAGE_STASH_ADDR
507 hex "Address to stash boot timing information"
510 Provide an address which will not be overwritten by the OS when it
511 starts, so that it can read this information when ready.
513 config BOOTSTAGE_STASH_SIZE
514 hex "Size of boot timing stash region"
517 This should be large enough to hold the bootstage stash. A value of
518 4096 (4KiB) is normally plenty.
520 config SHOW_BOOT_PROGRESS
521 bool "Show boot progress in a board-specific manner"
523 Defining this option allows to add some board-specific code (calling
524 a user-provided function show_boot_progress(int) that enables you to
525 show the system's boot progress on some display (for example, some
526 LEDs) on your board. At the moment, the following checkpoints are
529 Legacy uImage format:
532 1 common/cmd_bootm.c before attempting to boot an image
533 -1 common/cmd_bootm.c Image header has bad magic number
534 2 common/cmd_bootm.c Image header has correct magic number
535 -2 common/cmd_bootm.c Image header has bad checksum
536 3 common/cmd_bootm.c Image header has correct checksum
537 -3 common/cmd_bootm.c Image data has bad checksum
538 4 common/cmd_bootm.c Image data has correct checksum
539 -4 common/cmd_bootm.c Image is for unsupported architecture
540 5 common/cmd_bootm.c Architecture check OK
541 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
542 6 common/cmd_bootm.c Image Type check OK
543 -6 common/cmd_bootm.c gunzip uncompression error
544 -7 common/cmd_bootm.c Unimplemented compression type
545 7 common/cmd_bootm.c Uncompression OK
546 8 common/cmd_bootm.c No uncompress/copy overwrite error
547 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
549 9 common/image.c Start initial ramdisk verification
550 -10 common/image.c Ramdisk header has bad magic number
551 -11 common/image.c Ramdisk header has bad checksum
552 10 common/image.c Ramdisk header is OK
553 -12 common/image.c Ramdisk data has bad checksum
554 11 common/image.c Ramdisk data has correct checksum
555 12 common/image.c Ramdisk verification complete, start loading
556 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
557 13 common/image.c Start multifile image verification
558 14 common/image.c No initial ramdisk, no multifile, continue.
560 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
562 -30 arch/powerpc/lib/board.c Fatal error, hang the system
563 -31 post/post.c POST test failed, detected by post_output_backlog()
564 -32 post/post.c POST test failed, detected by post_run_single()
566 34 common/cmd_doc.c before loading a Image from a DOC device
567 -35 common/cmd_doc.c Bad usage of "doc" command
568 35 common/cmd_doc.c correct usage of "doc" command
569 -36 common/cmd_doc.c No boot device
570 36 common/cmd_doc.c correct boot device
571 -37 common/cmd_doc.c Unknown Chip ID on boot device
572 37 common/cmd_doc.c correct chip ID found, device available
573 -38 common/cmd_doc.c Read Error on boot device
574 38 common/cmd_doc.c reading Image header from DOC device OK
575 -39 common/cmd_doc.c Image header has bad magic number
576 39 common/cmd_doc.c Image header has correct magic number
577 -40 common/cmd_doc.c Error reading Image from DOC device
578 40 common/cmd_doc.c Image header has correct magic number
579 41 common/cmd_ide.c before loading a Image from a IDE device
580 -42 common/cmd_ide.c Bad usage of "ide" command
581 42 common/cmd_ide.c correct usage of "ide" command
582 -43 common/cmd_ide.c No boot device
583 43 common/cmd_ide.c boot device found
584 -44 common/cmd_ide.c Device not available
585 44 common/cmd_ide.c Device available
586 -45 common/cmd_ide.c wrong partition selected
587 45 common/cmd_ide.c partition selected
588 -46 common/cmd_ide.c Unknown partition table
589 46 common/cmd_ide.c valid partition table found
590 -47 common/cmd_ide.c Invalid partition type
591 47 common/cmd_ide.c correct partition type
592 -48 common/cmd_ide.c Error reading Image Header on boot device
593 48 common/cmd_ide.c reading Image Header from IDE device OK
594 -49 common/cmd_ide.c Image header has bad magic number
595 49 common/cmd_ide.c Image header has correct magic number
596 -50 common/cmd_ide.c Image header has bad checksum
597 50 common/cmd_ide.c Image header has correct checksum
598 -51 common/cmd_ide.c Error reading Image from IDE device
599 51 common/cmd_ide.c reading Image from IDE device OK
600 52 common/cmd_nand.c before loading a Image from a NAND device
601 -53 common/cmd_nand.c Bad usage of "nand" command
602 53 common/cmd_nand.c correct usage of "nand" command
603 -54 common/cmd_nand.c No boot device
604 54 common/cmd_nand.c boot device found
605 -55 common/cmd_nand.c Unknown Chip ID on boot device
606 55 common/cmd_nand.c correct chip ID found, device available
607 -56 common/cmd_nand.c Error reading Image Header on boot device
608 56 common/cmd_nand.c reading Image Header from NAND device OK
609 -57 common/cmd_nand.c Image header has bad magic number
610 57 common/cmd_nand.c Image header has correct magic number
611 -58 common/cmd_nand.c Error reading Image from NAND device
612 58 common/cmd_nand.c reading Image from NAND device OK
614 -60 common/env_common.c Environment has a bad CRC, using default
616 64 net/eth.c starting with Ethernet configuration.
617 -64 net/eth.c no Ethernet found.
618 65 net/eth.c Ethernet found.
620 -80 common/cmd_net.c usage wrong
621 80 common/cmd_net.c before calling net_loop()
622 -81 common/cmd_net.c some error in net_loop() occurred
623 81 common/cmd_net.c net_loop() back without error
624 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
625 82 common/cmd_net.c trying automatic boot
626 83 common/cmd_net.c running "source" command
627 -83 common/cmd_net.c some error in automatic boot or "source" command
628 84 common/cmd_net.c end without errors
633 100 common/cmd_bootm.c Kernel FIT Image has correct format
634 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
635 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
636 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
637 102 common/cmd_bootm.c Kernel unit name specified
638 -103 common/cmd_bootm.c Can't get kernel subimage node offset
639 103 common/cmd_bootm.c Found configuration node
640 104 common/cmd_bootm.c Got kernel subimage node offset
641 -104 common/cmd_bootm.c Kernel subimage hash verification failed
642 105 common/cmd_bootm.c Kernel subimage hash verification OK
643 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
644 106 common/cmd_bootm.c Architecture check OK
645 -106 common/cmd_bootm.c Kernel subimage has wrong type
646 107 common/cmd_bootm.c Kernel subimage type OK
647 -107 common/cmd_bootm.c Can't get kernel subimage data/size
648 108 common/cmd_bootm.c Got kernel subimage data/size
649 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
650 -109 common/cmd_bootm.c Can't get kernel subimage type
651 -110 common/cmd_bootm.c Can't get kernel subimage comp
652 -111 common/cmd_bootm.c Can't get kernel subimage os
653 -112 common/cmd_bootm.c Can't get kernel subimage load address
654 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
656 120 common/image.c Start initial ramdisk verification
657 -120 common/image.c Ramdisk FIT image has incorrect format
658 121 common/image.c Ramdisk FIT image has correct format
659 122 common/image.c No ramdisk subimage unit name, using configuration
660 -122 common/image.c Can't get configuration for ramdisk subimage
661 123 common/image.c Ramdisk unit name specified
662 -124 common/image.c Can't get ramdisk subimage node offset
663 125 common/image.c Got ramdisk subimage node offset
664 -125 common/image.c Ramdisk subimage hash verification failed
665 126 common/image.c Ramdisk subimage hash verification OK
666 -126 common/image.c Ramdisk subimage for unsupported architecture
667 127 common/image.c Architecture check OK
668 -127 common/image.c Can't get ramdisk subimage data/size
669 128 common/image.c Got ramdisk subimage data/size
670 129 common/image.c Can't get ramdisk load address
671 -129 common/image.c Got ramdisk load address
673 -130 common/cmd_doc.c Incorrect FIT image format
674 131 common/cmd_doc.c FIT image format OK
676 -140 common/cmd_ide.c Incorrect FIT image format
677 141 common/cmd_ide.c FIT image format OK
679 -150 common/cmd_nand.c Incorrect FIT image format
680 151 common/cmd_nand.c FIT image format OK
687 bool "Support for booting from NOR flash"
690 Enabling this will make a U-Boot binary that is capable of being
691 booted via NOR. In this case we will enable certain pinmux early
692 as the ROM only partially sets up pinmux. We also default to using
696 bool "Support for booting from NAND flash"
700 Enabling this will make a U-Boot binary that is capable of being
701 booted via NAND flash. This is not a must, some SoCs need this,
705 bool "Support for booting from ONENAND"
709 Enabling this will make a U-Boot binary that is capable of being
710 booted via ONENAND. This is not a must, some SoCs need this,
714 bool "Support for booting from QSPI flash"
717 Enabling this will make a U-Boot binary that is capable of being
718 booted via QSPI flash. This is not a must, some SoCs need this,
722 bool "Support for booting from SATA"
725 Enabling this will make a U-Boot binary that is capable of being
726 booted via SATA. This is not a must, some SoCs need this,
730 bool "Support for booting from SD/EMMC"
733 Enabling this will make a U-Boot binary that is capable of being
734 booted via SD/EMMC. This is not a must, some SoCs need this,
738 bool "Support for booting from SPI flash"
741 Enabling this will make a U-Boot binary that is capable of being
742 booted via SPI flash. This is not a must, some SoCs need this,
747 menu "Autoboot options"
753 This enables the autoboot. See doc/README.autoboot for detail.
756 int "delay in seconds before automatically booting"
760 Delay before automatically running bootcmd;
761 set to 0 to autoboot with no delay, but you can stop it by key input.
762 set to -1 to disable autoboot.
763 set to -2 to autoboot with no delay and not check for abort
765 If this value is >= 0 then it is also used for the default delay
766 before starting the default entry in bootmenu. If it is < 0 then
767 a default value of 10s is used.
769 See doc/README.autoboot for details.
771 config AUTOBOOT_KEYED
772 bool "Stop autobooting via specific input key / string"
775 This option enables stopping (aborting) of the automatic
776 boot feature only by issuing a specific input key or
777 string. If not enabled, any input key will abort the
778 U-Boot automatic booting process and bring the device
779 to the U-Boot prompt for user input.
781 config AUTOBOOT_PROMPT
782 string "Autoboot stop prompt"
783 depends on AUTOBOOT_KEYED
784 default "Autoboot in %d seconds\\n"
786 This string is displayed before the boot delay selected by
787 CONFIG_BOOTDELAY starts. If it is not defined there is no
788 output indicating that autoboot is in progress.
790 Note that this define is used as the (only) argument to a
791 printf() call, so it may contain '%' format specifications,
792 provided that it also includes, sepearated by commas exactly
793 like in a printf statement, the required arguments. It is
794 the responsibility of the user to select only such arguments
795 that are valid in the given context.
797 config AUTOBOOT_ENCRYPTION
798 bool "Enable encryption in autoboot stopping"
799 depends on AUTOBOOT_KEYED
801 This option allows a string to be entered into U-Boot to stop the
802 autoboot. The string itself is hashed and compared against the hash
803 in the environment variable 'bootstopkeysha256'. If it matches then
804 boot stops and a command-line prompt is presented.
806 This provides a way to ship a secure production device which can also
807 be accessed at the U-Boot command line.
809 config AUTOBOOT_DELAY_STR
810 string "Delay autobooting via specific input key / string"
811 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
813 This option delays the automatic boot feature by issuing
814 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
815 or the environment variable "bootdelaykey" is specified
816 and this string is received from console input before
817 autoboot starts booting, U-Boot gives a command prompt. The
818 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
819 used, otherwise it never times out.
821 config AUTOBOOT_STOP_STR
822 string "Stop autobooting via specific input key / string"
823 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
825 This option enables stopping (aborting) of the automatic
826 boot feature only by issuing a specific input key or
827 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
828 variable "bootstopkey" is specified and this string is
829 received from console input before autoboot starts booting,
830 U-Boot gives a command prompt. The U-Boot prompt never
831 times out, even if CONFIG_BOOT_RETRY_TIME is used.
833 config AUTOBOOT_KEYED_CTRLC
834 bool "Enable Ctrl-C autoboot interruption"
835 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
838 This option allows for the boot sequence to be interrupted
839 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
840 Setting this variable provides an escape sequence from the
841 limited "password" strings.
843 config AUTOBOOT_STOP_STR_SHA256
844 string "Stop autobooting via SHA256 encrypted password"
845 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
847 This option adds the feature to only stop the autobooting,
848 and therefore boot into the U-Boot prompt, when the input
849 string / password matches a values that is encypted via
850 a SHA256 hash and saved in the environment variable
851 "bootstopkeysha256". If the value in that variable
852 includes a ":", the portion prior to the ":" will be treated
855 config AUTOBOOT_USE_MENUKEY
856 bool "Allow a specify key to run a menu from the environment"
857 depends on !AUTOBOOT_KEYED
859 If a specific key is pressed to stop autoboot, then the commands in
860 the environment variable 'menucmd' are executed before boot starts.
862 config AUTOBOOT_MENUKEY
863 int "ASCII value of boot key to show a menu"
865 depends on AUTOBOOT_USE_MENUKEY
867 If this key is pressed to stop autoboot, then the commands in the
868 environment variable 'menucmd' will be executed before boot starts.
869 For example, 33 means "!" in ASCII, so pressing ! at boot would take
872 config AUTOBOOT_MENU_SHOW
873 bool "Show a menu on boot"
874 depends on CMD_BOOTMENU
876 This enables the boot menu, controlled by environment variables
877 defined by the board. The menu starts after running the 'preboot'
878 environmnent variable (if enabled) and before handling the boot delay.
879 See README.bootmenu for more details.
884 bool "Enable boot arguments"
886 Provide boot arguments to bootm command. Boot arguments are specified
887 in CONFIG_BOOTARGS option. Enable this option to be able to specify
888 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
889 will be undefined and won't take any space in U-Boot image.
892 string "Boot arguments"
893 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
895 This can be used to pass arguments to the bootm command. The value of
896 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
897 this value will also override the "chosen" node in FDT blob.
899 config BOOTARGS_SUBST
900 bool "Support substituting strings in boot arguments"
902 This allows substituting string values in the boot arguments. These
903 are applied after the commandline has been built.
905 One use for this is to insert the root-disk UUID into the command
906 line where bootargs contains "root=${uuid}"
908 setenv bootargs "console= root=${uuid}"
909 # Set the 'uuid' environment variable
910 part uuid mmc 2:2 uuid
912 # Command-line substitution will put the real uuid into the
913 # kernel command line
916 config USE_BOOTCOMMAND
917 bool "Enable a default value for bootcmd"
919 Provide a default value for the bootcmd entry in the environment. If
920 autoboot is enabled this is what will be run automatically. Enable
921 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
922 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
923 won't take any space in U-Boot image.
926 string "bootcmd value"
927 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
928 default "run distro_bootcmd" if DISTRO_DEFAULTS
930 This is the string of commands that will be used as bootcmd and if
931 AUTOBOOT is set, automatically run.
934 bool "Enable preboot"
936 When this option is enabled, the existence of the environment
937 variable "preboot" will be checked immediately before starting the
938 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
939 entering interactive mode.
941 This feature is especially useful when "preboot" is automatically
942 generated or modified. For example, the boot code can modify the
943 "preboot" when a user holds down a certain combination of keys.
946 string "preboot default value"
947 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
948 default "usb start" if USB_KEYBOARD
951 This is the default of "preboot" environment variable.
953 config DEFAULT_FDT_FILE
954 string "Default fdt file"
956 This option is used to set the default fdt file to boot OS.