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
85 This option enables signature verification of FIT uImages,
86 using a hash signed and verified using RSA. If
87 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
88 hashing is available using hardware, then the RSA library will use
89 it. See doc/uImage.FIT/signature.txt for more details.
91 WARNING: When relying on signed FIT images with a required signature
92 check the legacy image format is disabled by default, so that
93 unsigned images cannot be loaded. If a board needs the legacy image
94 format support in this case, enable it using
95 CONFIG_LEGACY_IMAGE_FORMAT.
97 config FIT_SIGNATURE_MAX_SIZE
98 hex "Max size of signed FIT structures"
99 depends on FIT_SIGNATURE
102 This option sets a max size in bytes for verified FIT uImages.
103 A sane value of 256MB protects corrupted DTB structures from overlapping
104 device memory. Assure this size does not extend past expected storage
107 config FIT_ENABLE_RSASSA_PSS_SUPPORT
108 bool "Support rsassa-pss signature scheme of FIT image contents"
109 depends on FIT_SIGNATURE
112 Enable this to support the pss padding algorithm as described
113 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
116 bool "Enable ciphering data in a FIT uImages"
120 Enable the feature of data ciphering/unciphering in the tool mkimage
121 and in the u-boot support of the FIT image.
124 bool "Show verbose messages when FIT images fail"
126 Generally a system will have valid FIT images so debug messages
127 are a waste of code space. If you are debugging your images then
128 you can enable this option to get more verbose information about
131 config FIT_BEST_MATCH
132 bool "Select the best match for the kernel device tree"
134 When no configuration is explicitly selected, default to the
135 one whose fdt's compatibility field best matches that of
136 U-Boot itself. A match is considered "best" if it matches the
137 most specific compatibility entry of U-Boot's fdt's root node.
138 The order of entries in the configuration's fdt is ignored.
140 config FIT_IMAGE_POST_PROCESS
141 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
142 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
144 Allows doing any sort of manipulation to blobs after they got extracted
145 from FIT images like stripping off headers or modifying the size of the
146 blob, verification, authentication, decryption etc. in a platform or
147 board specific way. In order to use this feature a platform or board-
148 specific implementation of board_fit_image_post_process() must be
149 provided. Also, anything done during this post-processing step would
150 need to be comprehended in how the images were prepared before being
151 injected into the FIT creation (i.e. the blobs would have been pre-
152 processed before being added to the FIT image).
155 bool "Support FIT printing"
158 Support printing the content of the fitImage in a verbose manner.
163 bool "Support Flattened Image Tree within SPL"
168 bool "Support FIT printing within SPL"
171 Support printing the content of the fitImage in a verbose manner in SPL.
173 config SPL_FIT_FULL_CHECK
174 bool "Do a full check of the FIT before using it"
176 Enable this do a full check of the FIT to make sure it is valid. This
177 helps to protect against carefully crafted FITs which take advantage
178 of bugs or omissions in the code. This includes a bad structure,
179 multiple root nodes and the like.
182 config SPL_FIT_SIGNATURE
183 bool "Enable signature verification of FIT firmware within SPL"
185 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
188 select SPL_CRYPTO_SUPPORT
189 select SPL_HASH_SUPPORT
191 select SPL_RSA_VERIFY
192 select SPL_IMAGE_SIGN_INFO
193 select SPL_FIT_FULL_CHECK
196 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
199 Normally with the SPL framework a legacy image is generated as part
200 of the build. This contains U-Boot along with information as to
201 where it should be loaded. This option instead enables generation
202 of a FIT (Flat Image Tree) which provides more flexibility. In
203 particular it can handle selecting from multiple device tree
204 and passing the correct one to U-Boot.
206 This path has the following limitations:
208 1. "loadables" images, other than FDTs, which do not have a "load"
209 property will not be loaded. This limitation also applies to FPGA
210 images with the correct "compatible" string.
211 2. For FPGA images, only the "compatible" = "u-boot,fpga-legacy"
212 loading method is supported.
213 3. FDTs are only loaded for images with an "os" property of "u-boot".
214 "linux" images are also supported with Falcon boot mode.
216 config SPL_LOAD_FIT_ADDRESS
217 hex "load address of fit image"
218 depends on SPL_LOAD_FIT
221 Specify the load address of the fit image that will be loaded
224 config SPL_LOAD_FIT_APPLY_OVERLAY
225 bool "Enable SPL applying DT overlays from FIT"
226 depends on SPL_LOAD_FIT
227 select OF_LIBFDT_OVERLAY
229 The device tree is loaded from the FIT image. Allow the SPL is to
230 also load device-tree overlays from the FIT image an apply them
231 over the device tree.
233 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
234 depends on SPL_LOAD_FIT_APPLY_OVERLAY
236 hex "size of temporary buffer used to load the overlays"
238 The size of the area where the overlays will be loaded and
239 uncompress. Must be at least as large as biggest overlay
242 config SPL_LOAD_FIT_FULL
243 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
246 Normally with the SPL framework a legacy image is generated as part
247 of the build. This contains U-Boot along with information as to
248 where it should be loaded. This option instead enables generation
249 of a FIT (Flat Image Tree) which provides more flexibility. In
250 particular it can handle selecting from multiple device tree
251 and passing the correct one to U-Boot.
253 config SPL_FIT_IMAGE_POST_PROCESS
254 bool "Enable post-processing of FIT artifacts after loading by the SPL"
255 depends on SPL_LOAD_FIT
257 Allows doing any sort of manipulation to blobs after they got extracted
258 from the U-Boot FIT image like stripping off headers or modifying the
259 size of the blob, verification, authentication, decryption etc. in a
260 platform or board specific way. In order to use this feature a platform
261 or board-specific implementation of board_fit_image_post_process() must
262 be provided. Also, anything done during this post-processing step would
263 need to be comprehended in how the images were prepared before being
264 injected into the FIT creation (i.e. the blobs would have been pre-
265 processed before being added to the FIT image).
267 config SPL_FIT_SOURCE
268 string ".its source file for U-Boot FIT image"
271 Specifies a (platform specific) FIT source file to generate the
272 U-Boot FIT image. This could specify further image to load and/or
275 config USE_SPL_FIT_GENERATOR
276 bool "Use a script to generate the .its script"
277 default y if SPL_FIT && !ARCH_SUNXI
279 config SPL_FIT_GENERATOR
280 string ".its file generator script for U-Boot FIT image"
281 depends on USE_SPL_FIT_GENERATOR
282 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
283 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
284 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
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.
295 config LEGACY_IMAGE_FORMAT
296 bool "Enable support for the legacy image format"
297 default y if !FIT_SIGNATURE
299 This option enables the legacy image format. It is enabled by
300 default for backward compatibility, unless FIT_SIGNATURE is
301 set where it is disabled so that unsigned images cannot be
302 loaded. If a board needs the legacy image format support in this
303 case, enable it here.
305 config SUPPORT_RAW_INITRD
306 bool "Enable raw initrd images"
308 Note, defining the SUPPORT_RAW_INITRD allows user to supply
309 kernel with raw initrd images. The syntax is slightly different, the
310 address of the initrd must be augmented by it's size, in the following
311 format: "<initrd address>:<initrd size>".
313 config OF_BOARD_SETUP
314 bool "Set up board-specific details in device tree before boot"
317 This causes U-Boot to call ft_board_setup() before booting into
318 the Operating System. This function can set up various
319 board-specific information in the device tree for use by the OS.
320 The device tree is then passed to the OS.
322 config OF_SYSTEM_SETUP
323 bool "Set up system-specific details in device tree before boot"
326 This causes U-Boot to call ft_system_setup() before booting into
327 the Operating System. This function can set up various
328 system-specific information in the device tree for use by the OS.
329 The device tree is then passed to the OS.
331 config OF_STDOUT_VIA_ALIAS
332 bool "Update the device-tree stdout alias from U-Boot"
335 This uses U-Boot's serial alias from the aliases node to update
336 the device tree passed to the OS. The "linux,stdout-path" property
337 in the chosen node is set to point to the correct serial node.
338 This option currently references CONFIG_CONS_INDEX, which is
339 incorrect when used with device tree as this option does not
340 exist / should not be used.
342 config SYS_EXTRA_OPTIONS
343 string "Extra Options (DEPRECATED)"
345 The old configuration infrastructure (= mkconfig + boards.cfg)
346 provided the extra options field. If you have something like
347 "HAS_BAR,BAZ=64", the optional options
349 #define CONFIG_BAZ 64
350 will be defined in include/config.h.
351 This option was prepared for the smooth migration from the old
352 configuration to Kconfig. Since this option will be removed sometime,
353 new boards should not use this option.
355 config HAVE_SYS_TEXT_BASE
357 depends on !NIOS2 && !XTENSA
362 depends on HAVE_SYS_TEXT_BASE
363 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
364 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
365 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
366 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
369 The address in memory that U-Boot will be running from, initially.
372 depends on ARC || ARCH_SUNXI || MPC83xx
373 int "CPU clock frequency"
375 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
377 config ARCH_FIXUP_FDT_MEMORY
378 bool "Enable arch_fixup_memory_banks() call"
381 Enable FDT memory map syncup before OS boot. This feature can be
382 used for booting OS with different memory setup where the part of
383 the memory location should be used for different purpose.
386 bool "Support booting Chrome OS"
388 Chrome OS requires U-Boot to set up a table indicating the boot mode
389 (e.g. Developer mode) and a few other things. Enable this if you are
390 booting on a Chromebook to avoid getting an error about an invalid
393 config CHROMEOS_VBOOT
394 bool "Support Chrome OS verified boot"
396 This is intended to enable the full Chrome OS verified boot support
397 in U-Boot. It is not actually implemented in the U-Boot source code
398 at present, so this option is always set to 'n'. It allows
399 distinguishing between booting Chrome OS in a basic way (developer
400 mode) and a full boot.
402 endmenu # Boot images
407 bool "Boot timing and reporting"
409 Enable recording of boot time while booting. To use it, insert
410 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
411 bootstage.h. Only a single entry is recorded for each ID. You can
412 give the entry a name with bootstage_mark_name(). You can also
413 record elapsed time in a particular stage using bootstage_start()
414 before starting and bootstage_accum() when finished. Bootstage will
415 add up all the accumulated time and report it.
417 Normally, IDs are defined in bootstage.h but a small number of
418 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
421 Calls to show_boot_progress() will also result in log entries but
422 these will not have names.
425 bool "Boot timing and reported in SPL"
428 Enable recording of boot time in SPL. To make this visible to U-Boot
429 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
430 information when SPL finishes and load it when U-Boot proper starts
434 bool "Boot timing and reported in TPL"
437 Enable recording of boot time in SPL. To make this visible to U-Boot
438 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
439 information when TPL finishes and load it when U-Boot proper starts
442 config BOOTSTAGE_REPORT
443 bool "Display a detailed boot timing report before booting the OS"
446 Enable output of a boot time report just before the OS is booted.
447 This shows how long it took U-Boot to go through each stage of the
448 boot process. The report looks something like this:
450 Timer summary in microseconds:
453 3,575,678 3,575,678 board_init_f start
454 3,575,695 17 arch_cpu_init A9
455 3,575,777 82 arch_cpu_init done
456 3,659,598 83,821 board_init_r start
457 3,910,375 250,777 main_loop
458 29,916,167 26,005,792 bootm_start
459 30,361,327 445,160 start_kernel
461 config BOOTSTAGE_RECORD_COUNT
462 int "Number of boot stage records to store"
466 This is the size of the bootstage record list and is the maximum
467 number of bootstage records that can be recorded.
469 config SPL_BOOTSTAGE_RECORD_COUNT
470 int "Number of boot stage records to store for SPL"
471 depends on SPL_BOOTSTAGE
474 This is the size of the bootstage record list and is the maximum
475 number of bootstage records that can be recorded.
477 config TPL_BOOTSTAGE_RECORD_COUNT
478 int "Number of boot stage records to store for TPL"
479 depends on TPL_BOOTSTAGE
482 This is the size of the bootstage record list and is the maximum
483 number of bootstage records that can be recorded.
486 bool "Store boot timing information in the OS device tree"
489 Stash the bootstage information in the FDT. A root 'bootstage'
490 node is created with each bootstage id as a child. Each child
491 has a 'name' property and either 'mark' containing the
492 mark time in microseconds, or 'accum' containing the
493 accumulated time for that bootstage id in microseconds.
498 name = "board_init_f";
507 Code in the Linux kernel can find this in /proc/devicetree.
509 config BOOTSTAGE_STASH
510 bool "Stash the boot timing information in memory before booting OS"
513 Some OSes do not support device tree. Bootstage can instead write
514 the boot timing information in a binary format at a given address.
515 This happens through a call to bootstage_stash(), typically in
516 the CPU's cleanup_before_linux() function. You can use the
517 'bootstage stash' and 'bootstage unstash' commands to do this on
520 config BOOTSTAGE_STASH_ADDR
521 hex "Address to stash boot timing information"
524 Provide an address which will not be overwritten by the OS when it
525 starts, so that it can read this information when ready.
527 config BOOTSTAGE_STASH_SIZE
528 hex "Size of boot timing stash region"
531 This should be large enough to hold the bootstage stash. A value of
532 4096 (4KiB) is normally plenty.
534 config SHOW_BOOT_PROGRESS
535 bool "Show boot progress in a board-specific manner"
537 Defining this option allows to add some board-specific code (calling
538 a user-provided function show_boot_progress(int) that enables you to
539 show the system's boot progress on some display (for example, some
540 LEDs) on your board. At the moment, the following checkpoints are
543 Legacy uImage format:
546 1 common/cmd_bootm.c before attempting to boot an image
547 -1 common/cmd_bootm.c Image header has bad magic number
548 2 common/cmd_bootm.c Image header has correct magic number
549 -2 common/cmd_bootm.c Image header has bad checksum
550 3 common/cmd_bootm.c Image header has correct checksum
551 -3 common/cmd_bootm.c Image data has bad checksum
552 4 common/cmd_bootm.c Image data has correct checksum
553 -4 common/cmd_bootm.c Image is for unsupported architecture
554 5 common/cmd_bootm.c Architecture check OK
555 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
556 6 common/cmd_bootm.c Image Type check OK
557 -6 common/cmd_bootm.c gunzip uncompression error
558 -7 common/cmd_bootm.c Unimplemented compression type
559 7 common/cmd_bootm.c Uncompression OK
560 8 common/cmd_bootm.c No uncompress/copy overwrite error
561 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
563 9 common/image.c Start initial ramdisk verification
564 -10 common/image.c Ramdisk header has bad magic number
565 -11 common/image.c Ramdisk header has bad checksum
566 10 common/image.c Ramdisk header is OK
567 -12 common/image.c Ramdisk data has bad checksum
568 11 common/image.c Ramdisk data has correct checksum
569 12 common/image.c Ramdisk verification complete, start loading
570 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
571 13 common/image.c Start multifile image verification
572 14 common/image.c No initial ramdisk, no multifile, continue.
574 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
576 -30 arch/powerpc/lib/board.c Fatal error, hang the system
577 -31 post/post.c POST test failed, detected by post_output_backlog()
578 -32 post/post.c POST test failed, detected by post_run_single()
580 34 common/cmd_doc.c before loading a Image from a DOC device
581 -35 common/cmd_doc.c Bad usage of "doc" command
582 35 common/cmd_doc.c correct usage of "doc" command
583 -36 common/cmd_doc.c No boot device
584 36 common/cmd_doc.c correct boot device
585 -37 common/cmd_doc.c Unknown Chip ID on boot device
586 37 common/cmd_doc.c correct chip ID found, device available
587 -38 common/cmd_doc.c Read Error on boot device
588 38 common/cmd_doc.c reading Image header from DOC device OK
589 -39 common/cmd_doc.c Image header has bad magic number
590 39 common/cmd_doc.c Image header has correct magic number
591 -40 common/cmd_doc.c Error reading Image from DOC device
592 40 common/cmd_doc.c Image header has correct magic number
593 41 common/cmd_ide.c before loading a Image from a IDE device
594 -42 common/cmd_ide.c Bad usage of "ide" command
595 42 common/cmd_ide.c correct usage of "ide" command
596 -43 common/cmd_ide.c No boot device
597 43 common/cmd_ide.c boot device found
598 -44 common/cmd_ide.c Device not available
599 44 common/cmd_ide.c Device available
600 -45 common/cmd_ide.c wrong partition selected
601 45 common/cmd_ide.c partition selected
602 -46 common/cmd_ide.c Unknown partition table
603 46 common/cmd_ide.c valid partition table found
604 -47 common/cmd_ide.c Invalid partition type
605 47 common/cmd_ide.c correct partition type
606 -48 common/cmd_ide.c Error reading Image Header on boot device
607 48 common/cmd_ide.c reading Image Header from IDE device OK
608 -49 common/cmd_ide.c Image header has bad magic number
609 49 common/cmd_ide.c Image header has correct magic number
610 -50 common/cmd_ide.c Image header has bad checksum
611 50 common/cmd_ide.c Image header has correct checksum
612 -51 common/cmd_ide.c Error reading Image from IDE device
613 51 common/cmd_ide.c reading Image from IDE device OK
614 52 common/cmd_nand.c before loading a Image from a NAND device
615 -53 common/cmd_nand.c Bad usage of "nand" command
616 53 common/cmd_nand.c correct usage of "nand" command
617 -54 common/cmd_nand.c No boot device
618 54 common/cmd_nand.c boot device found
619 -55 common/cmd_nand.c Unknown Chip ID on boot device
620 55 common/cmd_nand.c correct chip ID found, device available
621 -56 common/cmd_nand.c Error reading Image Header on boot device
622 56 common/cmd_nand.c reading Image Header from NAND device OK
623 -57 common/cmd_nand.c Image header has bad magic number
624 57 common/cmd_nand.c Image header has correct magic number
625 -58 common/cmd_nand.c Error reading Image from NAND device
626 58 common/cmd_nand.c reading Image from NAND device OK
628 -60 common/env_common.c Environment has a bad CRC, using default
630 64 net/eth.c starting with Ethernet configuration.
631 -64 net/eth.c no Ethernet found.
632 65 net/eth.c Ethernet found.
634 -80 common/cmd_net.c usage wrong
635 80 common/cmd_net.c before calling net_loop()
636 -81 common/cmd_net.c some error in net_loop() occurred
637 81 common/cmd_net.c net_loop() back without error
638 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
639 82 common/cmd_net.c trying automatic boot
640 83 common/cmd_net.c running "source" command
641 -83 common/cmd_net.c some error in automatic boot or "source" command
642 84 common/cmd_net.c end without errors
647 100 common/cmd_bootm.c Kernel FIT Image has correct format
648 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
649 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
650 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
651 102 common/cmd_bootm.c Kernel unit name specified
652 -103 common/cmd_bootm.c Can't get kernel subimage node offset
653 103 common/cmd_bootm.c Found configuration node
654 104 common/cmd_bootm.c Got kernel subimage node offset
655 -104 common/cmd_bootm.c Kernel subimage hash verification failed
656 105 common/cmd_bootm.c Kernel subimage hash verification OK
657 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
658 106 common/cmd_bootm.c Architecture check OK
659 -106 common/cmd_bootm.c Kernel subimage has wrong type
660 107 common/cmd_bootm.c Kernel subimage type OK
661 -107 common/cmd_bootm.c Can't get kernel subimage data/size
662 108 common/cmd_bootm.c Got kernel subimage data/size
663 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
664 -109 common/cmd_bootm.c Can't get kernel subimage type
665 -110 common/cmd_bootm.c Can't get kernel subimage comp
666 -111 common/cmd_bootm.c Can't get kernel subimage os
667 -112 common/cmd_bootm.c Can't get kernel subimage load address
668 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
670 120 common/image.c Start initial ramdisk verification
671 -120 common/image.c Ramdisk FIT image has incorrect format
672 121 common/image.c Ramdisk FIT image has correct format
673 122 common/image.c No ramdisk subimage unit name, using configuration
674 -122 common/image.c Can't get configuration for ramdisk subimage
675 123 common/image.c Ramdisk unit name specified
676 -124 common/image.c Can't get ramdisk subimage node offset
677 125 common/image.c Got ramdisk subimage node offset
678 -125 common/image.c Ramdisk subimage hash verification failed
679 126 common/image.c Ramdisk subimage hash verification OK
680 -126 common/image.c Ramdisk subimage for unsupported architecture
681 127 common/image.c Architecture check OK
682 -127 common/image.c Can't get ramdisk subimage data/size
683 128 common/image.c Got ramdisk subimage data/size
684 129 common/image.c Can't get ramdisk load address
685 -129 common/image.c Got ramdisk load address
687 -130 common/cmd_doc.c Incorrect FIT image format
688 131 common/cmd_doc.c FIT image format OK
690 -140 common/cmd_ide.c Incorrect FIT image format
691 141 common/cmd_ide.c FIT image format OK
693 -150 common/cmd_nand.c Incorrect FIT image format
694 151 common/cmd_nand.c FIT image format OK
701 bool "Support for booting from NOR flash"
704 Enabling this will make a U-Boot binary that is capable of being
705 booted via NOR. In this case we will enable certain pinmux early
706 as the ROM only partially sets up pinmux. We also default to using
710 bool "Support for booting from NAND flash"
714 Enabling this will make a U-Boot binary that is capable of being
715 booted via NAND flash. This is not a must, some SoCs need this,
719 bool "Support for booting from ONENAND"
723 Enabling this will make a U-Boot binary that is capable of being
724 booted via ONENAND. This is not a must, some SoCs need this,
728 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"
739 Enabling this will make a U-Boot binary that is capable of being
740 booted via SATA. This is not a must, some SoCs need this,
744 bool "Support for booting from SD/EMMC"
747 Enabling this will make a U-Boot binary that is capable of being
748 booted via SD/EMMC. This is not a must, some SoCs need this,
752 bool "Support for booting from SPI flash"
755 Enabling this will make a U-Boot binary that is capable of being
756 booted via SPI flash. This is not a must, some SoCs need this,
761 menu "Autoboot options"
767 This enables the autoboot. See doc/README.autoboot for detail.
770 int "delay in seconds before automatically booting"
774 Delay before automatically running bootcmd;
775 set to 0 to autoboot with no delay, but you can stop it by key input.
776 set to -1 to disable autoboot.
777 set to -2 to autoboot with no delay and not check for abort
779 If this value is >= 0 then it is also used for the default delay
780 before starting the default entry in bootmenu. If it is < 0 then
781 a default value of 10s is used.
783 See doc/README.autoboot for details.
785 config AUTOBOOT_KEYED
786 bool "Stop autobooting via specific input key / string"
789 This option enables stopping (aborting) of the automatic
790 boot feature only by issuing a specific input key or
791 string. If not enabled, any input key will abort the
792 U-Boot automatic booting process and bring the device
793 to the U-Boot prompt for user input.
795 config AUTOBOOT_PROMPT
796 string "Autoboot stop prompt"
797 depends on AUTOBOOT_KEYED
798 default "Autoboot in %d seconds\\n"
800 This string is displayed before the boot delay selected by
801 CONFIG_BOOTDELAY starts. If it is not defined there is no
802 output indicating that autoboot is in progress.
804 Note that this define is used as the (only) argument to a
805 printf() call, so it may contain '%' format specifications,
806 provided that it also includes, sepearated by commas exactly
807 like in a printf statement, the required arguments. It is
808 the responsibility of the user to select only such arguments
809 that are valid in the given context.
811 config AUTOBOOT_ENCRYPTION
812 bool "Enable encryption in autoboot stopping"
813 depends on AUTOBOOT_KEYED
815 This option allows a string to be entered into U-Boot to stop the
816 autoboot. The string itself is hashed and compared against the hash
817 in the environment variable 'bootstopkeysha256'. If it matches then
818 boot stops and a command-line prompt is presented.
820 This provides a way to ship a secure production device which can also
821 be accessed at the U-Boot command line.
823 config AUTOBOOT_DELAY_STR
824 string "Delay autobooting via specific input key / string"
825 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
827 This option delays the automatic boot feature by issuing
828 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
829 or the environment variable "bootdelaykey" is specified
830 and this string is received from console input before
831 autoboot starts booting, U-Boot gives a command prompt. The
832 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
833 used, otherwise it never times out.
835 config AUTOBOOT_STOP_STR
836 string "Stop autobooting via specific input key / string"
837 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
839 This option enables stopping (aborting) of the automatic
840 boot feature only by issuing a specific input key or
841 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
842 variable "bootstopkey" is specified and this string is
843 received from console input before autoboot starts booting,
844 U-Boot gives a command prompt. The U-Boot prompt never
845 times out, even if CONFIG_BOOT_RETRY_TIME is used.
847 config AUTOBOOT_KEYED_CTRLC
848 bool "Enable Ctrl-C autoboot interruption"
849 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
852 This option allows for the boot sequence to be interrupted
853 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
854 Setting this variable provides an escape sequence from the
855 limited "password" strings.
857 config AUTOBOOT_STOP_STR_SHA256
858 string "Stop autobooting via SHA256 encrypted password"
859 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
861 This option adds the feature to only stop the autobooting,
862 and therefore boot into the U-Boot prompt, when the input
863 string / password matches a values that is encypted via
864 a SHA256 hash and saved in the environment variable
865 "bootstopkeysha256". If the value in that variable
866 includes a ":", the portion prior to the ":" will be treated
869 config AUTOBOOT_USE_MENUKEY
870 bool "Allow a specify key to run a menu from the environment"
871 depends on !AUTOBOOT_KEYED
873 If a specific key is pressed to stop autoboot, then the commands in
874 the environment variable 'menucmd' are executed before boot starts.
876 config AUTOBOOT_MENUKEY
877 int "ASCII value of boot key to show a menu"
879 depends on AUTOBOOT_USE_MENUKEY
881 If this key is pressed to stop autoboot, then the commands in the
882 environment variable 'menucmd' will be executed before boot starts.
883 For example, 33 means "!" in ASCII, so pressing ! at boot would take
886 config AUTOBOOT_MENU_SHOW
887 bool "Show a menu on boot"
888 depends on CMD_BOOTMENU
890 This enables the boot menu, controlled by environment variables
891 defined by the board. The menu starts after running the 'preboot'
892 environmnent variable (if enabled) and before handling the boot delay.
893 See README.bootmenu for more details.
898 bool "Enable boot arguments"
900 Provide boot arguments to bootm command. Boot arguments are specified
901 in CONFIG_BOOTARGS option. Enable this option to be able to specify
902 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
903 will be undefined and won't take any space in U-Boot image.
906 string "Boot arguments"
907 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
909 This can be used to pass arguments to the bootm command. The value of
910 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
911 this value will also override the "chosen" node in FDT blob.
913 config BOOTARGS_SUBST
914 bool "Support substituting strings in boot arguments"
916 This allows substituting string values in the boot arguments. These
917 are applied after the commandline has been built.
919 One use for this is to insert the root-disk UUID into the command
920 line where bootargs contains "root=${uuid}"
922 setenv bootargs "console= root=${uuid}"
923 # Set the 'uuid' environment variable
924 part uuid mmc 2:2 uuid
926 # Command-line substitution will put the real uuid into the
927 # kernel command line
930 config USE_BOOTCOMMAND
931 bool "Enable a default value for bootcmd"
933 Provide a default value for the bootcmd entry in the environment. If
934 autoboot is enabled this is what will be run automatically. Enable
935 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
936 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
937 won't take any space in U-Boot image.
940 string "bootcmd value"
941 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
942 default "run distro_bootcmd" if DISTRO_DEFAULTS
944 This is the string of commands that will be used as bootcmd and if
945 AUTOBOOT is set, automatically run.
948 bool "Enable preboot"
950 When this option is enabled, the existence of the environment
951 variable "preboot" will be checked immediately before starting the
952 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
953 entering interactive mode.
955 This feature is especially useful when "preboot" is automatically
956 generated or modified. For example, the boot code can modify the
957 "preboot" when a user holds down a certain combination of keys.
960 string "preboot default value"
961 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
962 default "usb start" if USB_KEYBOARD
965 This is the default of "preboot" environment variable.
967 config DEFAULT_FDT_FILE
968 string "Default fdt file"
970 This option is used to set the default fdt file to boot OS.