5 config ANDROID_BOOT_IMAGE
6 bool "Enable support for Android Boot Images"
9 This enables support for booting images which use the Android
13 bool "Support Flattened Image Tree"
19 This option allows you to boot the new uImage structure,
20 Flattened Image Tree. FIT is formally a FDT, which can include
21 images of various types (kernel, FDT blob, ramdisk, etc.)
22 in a single blob. To boot this new uImage structure,
23 pass the address of the blob to the "bootm" command.
24 FIT is very flexible, supporting compression, multiple images,
25 multiple configurations, verification through hashing and also
26 verified boot (secure boot using RSA).
29 bool "Show image date and time when displaying image information"
32 When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of
33 an image is printed by image commands like bootm or iminfo. This
34 is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is
35 enabled, then U-Boot requires FITs to have a timestamp. If a FIT is
36 loaded that does not, the message 'Wrong FIT format: no timestamp'
41 config FIT_EXTERNAL_OFFSET
42 hex "FIT external data offset"
45 This specifies a data offset in fit image.
46 The offset is from data payload offset to the beginning of
47 fit image header. When specifies a offset, specific data
48 could be put in the hole between data payload and fit image
49 header, such as CSF data on i.MX platform.
52 bool "Do a full check of the FIT before using it"
55 Enable this do a full check of the FIT to make sure it is valid. This
56 helps to protect against carefully crafted FITs which take advantage
57 of bugs or omissions in the code. This includes a bad structure,
58 multiple root nodes and the like.
61 bool "Enable signature verification of FIT uImages"
66 select IMAGE_SIGN_INFO
69 This option enables signature verification of FIT uImages,
70 using a hash signed and verified using RSA. If
71 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
72 hashing is available using hardware, then the RSA library will use
73 it. See doc/uImage.FIT/signature.txt for more details.
75 WARNING: When relying on signed FIT images with a required signature
76 check the legacy image format is disabled by default, so that
77 unsigned images cannot be loaded. If a board needs the legacy image
78 format support in this case, enable it using
79 CONFIG_LEGACY_IMAGE_FORMAT.
81 config FIT_SIGNATURE_MAX_SIZE
82 hex "Max size of signed FIT structures"
83 depends on FIT_SIGNATURE
86 This option sets a max size in bytes for verified FIT uImages.
87 A sane value of 256MB protects corrupted DTB structures from overlapping
88 device memory. Assure this size does not extend past expected storage
92 bool "Support rsassa-pss signature scheme of FIT image contents"
93 depends on FIT_SIGNATURE
95 Enable this to support the pss padding algorithm as described
96 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
99 bool "Enable ciphering data in a FIT uImages"
103 Enable the feature of data ciphering/unciphering in the tool mkimage
104 and in the u-boot support of the FIT image.
107 bool "Show verbose messages when FIT images fail"
109 Generally a system will have valid FIT images so debug messages
110 are a waste of code space. If you are debugging your images then
111 you can enable this option to get more verbose information about
114 config FIT_BEST_MATCH
115 bool "Select the best match for the kernel device tree"
117 When no configuration is explicitly selected, default to the
118 one whose fdt's compatibility field best matches that of
119 U-Boot itself. A match is considered "best" if it matches the
120 most specific compatibility entry of U-Boot's fdt's root node.
121 The order of entries in the configuration's fdt is ignored.
123 config FIT_IMAGE_POST_PROCESS
124 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
125 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
127 Allows doing any sort of manipulation to blobs after they got extracted
128 from FIT images like stripping off headers or modifying the size of the
129 blob, verification, authentication, decryption etc. in a platform or
130 board specific way. In order to use this feature a platform or board-
131 specific implementation of board_fit_image_post_process() must be
132 provided. Also, anything done during this post-processing step would
133 need to be comprehended in how the images were prepared before being
134 injected into the FIT creation (i.e. the blobs would have been pre-
135 processed before being added to the FIT image).
138 bool "Support FIT printing"
141 Support printing the content of the fitImage in a verbose manner.
146 bool "Support Flattened Image Tree within SPL"
152 bool "Support FIT printing within SPL"
155 Support printing the content of the fitImage in a verbose manner in SPL.
157 config SPL_FIT_FULL_CHECK
158 bool "Do a full check of the FIT before using it"
160 Enable this do a full check of the FIT to make sure it is valid. This
161 helps to protect against carefully crafted FITs which take advantage
162 of bugs or omissions in the code. This includes a bad structure,
163 multiple root nodes and the like.
166 config SPL_FIT_SIGNATURE
167 bool "Enable signature verification of FIT firmware within SPL"
169 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
176 select SPL_IMAGE_SIGN_INFO
177 select SPL_FIT_FULL_CHECK
179 config SPL_FIT_SIGNATURE_MAX_SIZE
180 hex "Max size of signed FIT structures in SPL"
181 depends on SPL_FIT_SIGNATURE
184 This option sets a max size in bytes for verified FIT uImages.
185 A sane value of 256MB protects corrupted DTB structures from overlapping
186 device memory. Assure this size does not extend past expected storage
189 config SPL_FIT_RSASSA_PSS
190 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
191 depends on SPL_FIT_SIGNATURE
193 Enable this to support the pss padding algorithm as described
194 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
197 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
200 Normally with the SPL framework a legacy image is generated as part
201 of the build. This contains U-Boot along with information as to
202 where it should be loaded. This option instead enables generation
203 of a FIT (Flat Image Tree) which provides more flexibility. In
204 particular it can handle selecting from multiple device tree
205 and passing the correct one to U-Boot.
207 This path has the following limitations:
209 1. "loadables" images, other than FDTs, which do not have a "load"
210 property will not be loaded. This limitation also applies to FPGA
211 images with the correct "compatible" string.
212 2. For FPGA images, only the "compatible" = "u-boot,fpga-legacy"
213 loading method is supported.
214 3. FDTs are only loaded for images with an "os" property of "u-boot".
215 "linux" images are also supported with Falcon boot mode.
217 config SPL_LOAD_FIT_ADDRESS
218 hex "load address of fit image"
219 depends on SPL_LOAD_FIT
222 Specify the load address of the fit image that will be loaded
225 config SPL_LOAD_FIT_APPLY_OVERLAY
226 bool "Enable SPL applying DT overlays from FIT"
227 depends on SPL_LOAD_FIT
228 select OF_LIBFDT_OVERLAY
230 The device tree is loaded from the FIT image. Allow the SPL is to
231 also load device-tree overlays from the FIT image an apply them
232 over the device tree.
234 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
235 depends on SPL_LOAD_FIT_APPLY_OVERLAY
237 hex "size of temporary buffer used to load the overlays"
239 The size of the area where the overlays will be loaded and
240 uncompress. Must be at least as large as biggest overlay
243 config SPL_LOAD_FIT_FULL
244 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
247 Normally with the SPL framework a legacy image is generated as part
248 of the build. This contains U-Boot along with information as to
249 where it should be loaded. This option instead enables generation
250 of a FIT (Flat Image Tree) which provides more flexibility. In
251 particular it can handle selecting from multiple device tree
252 and passing the correct one to U-Boot.
254 config SPL_FIT_IMAGE_POST_PROCESS
255 bool "Enable post-processing of FIT artifacts after loading by the SPL"
256 depends on SPL_LOAD_FIT
258 Allows doing any sort of manipulation to blobs after they got extracted
259 from the U-Boot FIT image like stripping off headers or modifying the
260 size of the blob, verification, authentication, decryption etc. in a
261 platform or board specific way. In order to use this feature a platform
262 or board-specific implementation of board_fit_image_post_process() must
263 be provided. Also, anything done during this post-processing step would
264 need to be comprehended in how the images were prepared before being
265 injected into the FIT creation (i.e. the blobs would have been pre-
266 processed before being added to the FIT image).
268 config SPL_FIT_SOURCE
269 string ".its source file for U-Boot FIT image"
272 Specifies a (platform specific) FIT source file to generate the
273 U-Boot FIT image. This could specify further image to load and/or
276 config USE_SPL_FIT_GENERATOR
277 bool "Use a script to generate the .its script"
278 default y if SPL_FIT && (!ARCH_SUNXI && !RISCV)
280 config SPL_FIT_GENERATOR
281 string ".its file generator script for U-Boot FIT image"
282 depends on USE_SPL_FIT_GENERATOR
283 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
284 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
286 Specifies a (platform specific) script file to generate the FIT
287 source file used to build the U-Boot FIT image file. This gets
288 passed a list of supported device tree file stub names to
289 include in the generated image.
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 HAVE_SYS_TEXT_BASE
344 depends on !NIOS2 && !XTENSA
349 depends on HAVE_SYS_TEXT_BASE
350 default 0x0 if POSITION_INDEPENDENT
351 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
352 default 0x81700000 if MACH_SUNIV
353 default 0x2a000000 if MACH_SUN9I
354 default 0x42e00000 if MACH_SUN8I_V3S
355 default 0x4a000000 if ARCH_SUNXI
358 The address in memory that U-Boot will be running from, initially.
360 config HAVE_SYS_MONITOR_BASE
362 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
363 || FLASH_PIC32 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
367 config SYS_MONITOR_BASE
368 depends on HAVE_SYS_MONITOR_BASE
369 hex "Physical start address of boot monitor code"
370 default SYS_TEXT_BASE
372 The physical start address of boot monitor code (which is the same as
373 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
374 when booting from flash.
376 config SPL_SYS_MONITOR_BASE
377 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
378 hex "Physical start address of SPL monitor code"
379 default SPL_TEXT_BASE
381 config TPL_SYS_MONITOR_BASE
382 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
383 hex "Physical start address of TPL monitor code"
385 config DYNAMIC_SYS_CLK_FREQ
386 bool "Determine CPU clock frequency at run-time"
388 Implement a get_board_sys_clk function that will determine the CPU
389 clock frequency at run time, rather than define it statically.
392 depends on !DYNAMIC_SYS_CLK_FREQ
393 int "CPU clock frequency"
394 default 125000000 if ARCH_LS1012A
395 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
396 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
397 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
398 default 66660000 if ARCH_T2080
399 default 33333333 if RCAR_GEN3
400 default 24000000 if ARCH_EXYNOS
401 default 20000000 if RCAR_GEN2
404 A static value for the CPU frequency. Note that if not required
405 for a given SoC, this can be left at 0.
407 config ARCH_FIXUP_FDT_MEMORY
408 bool "Enable arch_fixup_memory_banks() call"
411 Enable FDT memory map syncup before OS boot. This feature can be
412 used for booting OS with different memory setup where the part of
413 the memory location should be used for different purpose.
416 bool "Support booting Chrome OS"
418 Chrome OS requires U-Boot to set up a table indicating the boot mode
419 (e.g. Developer mode) and a few other things. Enable this if you are
420 booting on a Chromebook to avoid getting an error about an invalid
423 config CHROMEOS_VBOOT
424 bool "Support Chrome OS verified boot"
426 This is intended to enable the full Chrome OS verified boot support
427 in U-Boot. It is not actually implemented in the U-Boot source code
428 at present, so this option is always set to 'n'. It allows
429 distinguishing between booting Chrome OS in a basic way (developer
430 mode) and a full boot.
433 bool "Freescale PBL(pre-boot loader) image format support"
435 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
436 For more details refer to doc/README.pblimage
439 prompt "Freescale PBL load location"
440 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
441 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
445 bool "Freescale PBL is found on SD card"
448 bool "Freescale PBL is found on SPI flash"
452 config SYS_FSL_PBL_PBI
453 string "PBI(pre-boot instructions) commands for the PBL image"
454 depends on RAMBOOT_PBL
456 PBI commands can be used to configure SoC before it starts the execution.
457 Please refer doc/README.pblimage for more details.
459 config SYS_FSL_PBL_RCW
460 string "Aadditional RCW (Power on reset configuration) for the PBL image"
461 depends on RAMBOOT_PBL
463 Enables addition of RCW (Power on reset configuration) in built image.
464 Please refer doc/README.pblimage for more details.
466 endmenu # Boot images
471 bool "Boot timing and reporting"
473 Enable recording of boot time while booting. To use it, insert
474 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
475 bootstage.h. Only a single entry is recorded for each ID. You can
476 give the entry a name with bootstage_mark_name(). You can also
477 record elapsed time in a particular stage using bootstage_start()
478 before starting and bootstage_accum() when finished. Bootstage will
479 add up all the accumulated time and report it.
481 Normally, IDs are defined in bootstage.h but a small number of
482 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
485 Calls to show_boot_progress() will also result in log entries but
486 these will not have names.
489 bool "Boot timing and reported in SPL"
492 Enable recording of boot time in SPL. To make this visible to U-Boot
493 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
494 information when SPL finishes and load it when U-Boot proper starts
498 bool "Boot timing and reported in TPL"
501 Enable recording of boot time in SPL. To make this visible to U-Boot
502 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
503 information when TPL finishes and load it when U-Boot proper starts
506 config BOOTSTAGE_REPORT
507 bool "Display a detailed boot timing report before booting the OS"
510 Enable output of a boot time report just before the OS is booted.
511 This shows how long it took U-Boot to go through each stage of the
512 boot process. The report looks something like this:
514 Timer summary in microseconds:
517 3,575,678 3,575,678 board_init_f start
518 3,575,695 17 arch_cpu_init A9
519 3,575,777 82 arch_cpu_init done
520 3,659,598 83,821 board_init_r start
521 3,910,375 250,777 main_loop
522 29,916,167 26,005,792 bootm_start
523 30,361,327 445,160 start_kernel
525 config BOOTSTAGE_RECORD_COUNT
526 int "Number of boot stage records to store"
530 This is the size of the bootstage record list and is the maximum
531 number of bootstage records that can be recorded.
533 config SPL_BOOTSTAGE_RECORD_COUNT
534 int "Number of boot stage records to store for SPL"
535 depends on SPL_BOOTSTAGE
538 This is the size of the bootstage record list and is the maximum
539 number of bootstage records that can be recorded.
541 config TPL_BOOTSTAGE_RECORD_COUNT
542 int "Number of boot stage records to store for TPL"
543 depends on TPL_BOOTSTAGE
546 This is the size of the bootstage record list and is the maximum
547 number of bootstage records that can be recorded.
550 bool "Store boot timing information in the OS device tree"
553 Stash the bootstage information in the FDT. A root 'bootstage'
554 node is created with each bootstage id as a child. Each child
555 has a 'name' property and either 'mark' containing the
556 mark time in microseconds, or 'accum' containing the
557 accumulated time for that bootstage id in microseconds.
562 name = "board_init_f";
571 Code in the Linux kernel can find this in /proc/devicetree.
573 config BOOTSTAGE_STASH
574 bool "Stash the boot timing information in memory before booting OS"
577 Some OSes do not support device tree. Bootstage can instead write
578 the boot timing information in a binary format at a given address.
579 This happens through a call to bootstage_stash(), typically in
580 the CPU's cleanup_before_linux() function. You can use the
581 'bootstage stash' and 'bootstage unstash' commands to do this on
584 config BOOTSTAGE_STASH_ADDR
585 hex "Address to stash boot timing information"
588 Provide an address which will not be overwritten by the OS when it
589 starts, so that it can read this information when ready.
591 config BOOTSTAGE_STASH_SIZE
592 hex "Size of boot timing stash region"
595 This should be large enough to hold the bootstage stash. A value of
596 4096 (4KiB) is normally plenty.
598 config SHOW_BOOT_PROGRESS
599 bool "Show boot progress in a board-specific manner"
601 Defining this option allows to add some board-specific code (calling
602 a user-provided function show_boot_progress(int) that enables you to
603 show the system's boot progress on some display (for example, some
604 LEDs) on your board. At the moment, the following checkpoints are
607 Legacy uImage format:
610 1 common/cmd_bootm.c before attempting to boot an image
611 -1 common/cmd_bootm.c Image header has bad magic number
612 2 common/cmd_bootm.c Image header has correct magic number
613 -2 common/cmd_bootm.c Image header has bad checksum
614 3 common/cmd_bootm.c Image header has correct checksum
615 -3 common/cmd_bootm.c Image data has bad checksum
616 4 common/cmd_bootm.c Image data has correct checksum
617 -4 common/cmd_bootm.c Image is for unsupported architecture
618 5 common/cmd_bootm.c Architecture check OK
619 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
620 6 common/cmd_bootm.c Image Type check OK
621 -6 common/cmd_bootm.c gunzip uncompression error
622 -7 common/cmd_bootm.c Unimplemented compression type
623 7 common/cmd_bootm.c Uncompression OK
624 8 common/cmd_bootm.c No uncompress/copy overwrite error
625 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
627 9 common/image.c Start initial ramdisk verification
628 -10 common/image.c Ramdisk header has bad magic number
629 -11 common/image.c Ramdisk header has bad checksum
630 10 common/image.c Ramdisk header is OK
631 -12 common/image.c Ramdisk data has bad checksum
632 11 common/image.c Ramdisk data has correct checksum
633 12 common/image.c Ramdisk verification complete, start loading
634 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
635 13 common/image.c Start multifile image verification
636 14 common/image.c No initial ramdisk, no multifile, continue.
638 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
640 -30 arch/powerpc/lib/board.c Fatal error, hang the system
641 -31 post/post.c POST test failed, detected by post_output_backlog()
642 -32 post/post.c POST test failed, detected by post_run_single()
644 34 common/cmd_doc.c before loading a Image from a DOC device
645 -35 common/cmd_doc.c Bad usage of "doc" command
646 35 common/cmd_doc.c correct usage of "doc" command
647 -36 common/cmd_doc.c No boot device
648 36 common/cmd_doc.c correct boot device
649 -37 common/cmd_doc.c Unknown Chip ID on boot device
650 37 common/cmd_doc.c correct chip ID found, device available
651 -38 common/cmd_doc.c Read Error on boot device
652 38 common/cmd_doc.c reading Image header from DOC device OK
653 -39 common/cmd_doc.c Image header has bad magic number
654 39 common/cmd_doc.c Image header has correct magic number
655 -40 common/cmd_doc.c Error reading Image from DOC device
656 40 common/cmd_doc.c Image header has correct magic number
657 41 common/cmd_ide.c before loading a Image from a IDE device
658 -42 common/cmd_ide.c Bad usage of "ide" command
659 42 common/cmd_ide.c correct usage of "ide" command
660 -43 common/cmd_ide.c No boot device
661 43 common/cmd_ide.c boot device found
662 -44 common/cmd_ide.c Device not available
663 44 common/cmd_ide.c Device available
664 -45 common/cmd_ide.c wrong partition selected
665 45 common/cmd_ide.c partition selected
666 -46 common/cmd_ide.c Unknown partition table
667 46 common/cmd_ide.c valid partition table found
668 -47 common/cmd_ide.c Invalid partition type
669 47 common/cmd_ide.c correct partition type
670 -48 common/cmd_ide.c Error reading Image Header on boot device
671 48 common/cmd_ide.c reading Image Header from IDE device OK
672 -49 common/cmd_ide.c Image header has bad magic number
673 49 common/cmd_ide.c Image header has correct magic number
674 -50 common/cmd_ide.c Image header has bad checksum
675 50 common/cmd_ide.c Image header has correct checksum
676 -51 common/cmd_ide.c Error reading Image from IDE device
677 51 common/cmd_ide.c reading Image from IDE device OK
678 52 common/cmd_nand.c before loading a Image from a NAND device
679 -53 common/cmd_nand.c Bad usage of "nand" command
680 53 common/cmd_nand.c correct usage of "nand" command
681 -54 common/cmd_nand.c No boot device
682 54 common/cmd_nand.c boot device found
683 -55 common/cmd_nand.c Unknown Chip ID on boot device
684 55 common/cmd_nand.c correct chip ID found, device available
685 -56 common/cmd_nand.c Error reading Image Header on boot device
686 56 common/cmd_nand.c reading Image Header from NAND device OK
687 -57 common/cmd_nand.c Image header has bad magic number
688 57 common/cmd_nand.c Image header has correct magic number
689 -58 common/cmd_nand.c Error reading Image from NAND device
690 58 common/cmd_nand.c reading Image from NAND device OK
692 -60 common/env_common.c Environment has a bad CRC, using default
694 64 net/eth.c starting with Ethernet configuration.
695 -64 net/eth.c no Ethernet found.
696 65 net/eth.c Ethernet found.
698 -80 common/cmd_net.c usage wrong
699 80 common/cmd_net.c before calling net_loop()
700 -81 common/cmd_net.c some error in net_loop() occurred
701 81 common/cmd_net.c net_loop() back without error
702 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
703 82 common/cmd_net.c trying automatic boot
704 83 common/cmd_net.c running "source" command
705 -83 common/cmd_net.c some error in automatic boot or "source" command
706 84 common/cmd_net.c end without errors
711 100 common/cmd_bootm.c Kernel FIT Image has correct format
712 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
713 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
714 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
715 102 common/cmd_bootm.c Kernel unit name specified
716 -103 common/cmd_bootm.c Can't get kernel subimage node offset
717 103 common/cmd_bootm.c Found configuration node
718 104 common/cmd_bootm.c Got kernel subimage node offset
719 -104 common/cmd_bootm.c Kernel subimage hash verification failed
720 105 common/cmd_bootm.c Kernel subimage hash verification OK
721 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
722 106 common/cmd_bootm.c Architecture check OK
723 -106 common/cmd_bootm.c Kernel subimage has wrong type
724 107 common/cmd_bootm.c Kernel subimage type OK
725 -107 common/cmd_bootm.c Can't get kernel subimage data/size
726 108 common/cmd_bootm.c Got kernel subimage data/size
727 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
728 -109 common/cmd_bootm.c Can't get kernel subimage type
729 -110 common/cmd_bootm.c Can't get kernel subimage comp
730 -111 common/cmd_bootm.c Can't get kernel subimage os
731 -112 common/cmd_bootm.c Can't get kernel subimage load address
732 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
734 120 common/image.c Start initial ramdisk verification
735 -120 common/image.c Ramdisk FIT image has incorrect format
736 121 common/image.c Ramdisk FIT image has correct format
737 122 common/image.c No ramdisk subimage unit name, using configuration
738 -122 common/image.c Can't get configuration for ramdisk subimage
739 123 common/image.c Ramdisk unit name specified
740 -124 common/image.c Can't get ramdisk subimage node offset
741 125 common/image.c Got ramdisk subimage node offset
742 -125 common/image.c Ramdisk subimage hash verification failed
743 126 common/image.c Ramdisk subimage hash verification OK
744 -126 common/image.c Ramdisk subimage for unsupported architecture
745 127 common/image.c Architecture check OK
746 -127 common/image.c Can't get ramdisk subimage data/size
747 128 common/image.c Got ramdisk subimage data/size
748 129 common/image.c Can't get ramdisk load address
749 -129 common/image.c Got ramdisk load address
751 -130 common/cmd_doc.c Incorrect FIT image format
752 131 common/cmd_doc.c FIT image format OK
754 -140 common/cmd_ide.c Incorrect FIT image format
755 141 common/cmd_ide.c FIT image format OK
757 -150 common/cmd_nand.c Incorrect FIT image format
758 151 common/cmd_nand.c FIT image format OK
760 config SPL_SHOW_BOOT_PROGRESS
761 bool "Show boot progress in a board-specific manner in SPL"
764 Defining this option allows to add some board-specific code (calling
765 a user-provided function show_boot_progress(int) that enables you to
766 show the system's boot progress on some display (for example, some
767 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
774 bool "Support for booting from NOR flash"
777 Enabling this will make a U-Boot binary that is capable of being
778 booted via NOR. In this case we will enable certain pinmux early
779 as the ROM only partially sets up pinmux. We also default to using
783 bool "Support for booting from NAND flash"
786 Enabling this will make a U-Boot binary that is capable of being
787 booted via NAND flash. This is not a must, some SoCs need this,
791 bool "Support for booting from ONENAND"
794 Enabling this will make a U-Boot binary that is capable of being
795 booted via ONENAND. This is not a must, some SoCs need this,
799 bool "Support for booting from QSPI flash"
801 Enabling this will make a U-Boot binary that is capable of being
802 booted via QSPI flash. This is not a must, some SoCs need this,
806 bool "Support for booting from SATA"
808 Enabling this will make a U-Boot binary that is capable of being
809 booted via SATA. This is not a must, some SoCs need this,
813 bool "Support for booting from SD/EMMC"
815 Enabling this will make a U-Boot binary that is capable of being
816 booted via SD/EMMC. This is not a must, some SoCs need this,
820 bool "Support for booting from SD/EMMC and enable QSPI"
822 Enabling this will make a U-Boot binary that is capable of being
823 booted via SD/EMMC while enabling QSPI on the platform as well. This
824 is not a must, some SoCs need this, some not.
827 bool "Support for booting from SPI flash"
829 Enabling this will make a U-Boot binary that is capable of being
830 booted via SPI flash. This is not a must, some SoCs need this,
835 menu "Autoboot options"
841 This enables the autoboot. See doc/README.autoboot for detail.
844 int "delay in seconds before automatically booting"
848 Delay before automatically running bootcmd;
849 set to 0 to autoboot with no delay, but you can stop it by key input.
850 set to -1 to disable autoboot.
851 set to -2 to autoboot with no delay and not check for abort
853 If this value is >= 0 then it is also used for the default delay
854 before starting the default entry in bootmenu. If it is < 0 then
855 a default value of 10s is used.
857 See doc/README.autoboot for details.
859 config AUTOBOOT_KEYED
860 bool "Stop autobooting via specific input key / string"
862 This option enables stopping (aborting) of the automatic
863 boot feature only by issuing a specific input key or
864 string. If not enabled, any input key will abort the
865 U-Boot automatic booting process and bring the device
866 to the U-Boot prompt for user input.
868 config AUTOBOOT_FLUSH_STDIN
869 bool "Enable flushing stdin before starting to read the password"
870 depends on AUTOBOOT_KEYED && !SANDBOX
872 When this option is enabled stdin buffer will be flushed before
873 starting to read the password.
874 This can't be enabled for the sandbox as flushing stdin would
875 break the autoboot unit tests.
877 config AUTOBOOT_PROMPT
878 string "Autoboot stop prompt"
879 depends on AUTOBOOT_KEYED
880 default "Autoboot in %d seconds\\n"
882 This string is displayed before the boot delay selected by
883 CONFIG_BOOTDELAY starts. If it is not defined there is no
884 output indicating that autoboot is in progress.
886 Note that this define is used as the (only) argument to a
887 printf() call, so it may contain '%' format specifications,
888 provided that it also includes, sepearated by commas exactly
889 like in a printf statement, the required arguments. It is
890 the responsibility of the user to select only such arguments
891 that are valid in the given context.
893 config AUTOBOOT_ENCRYPTION
894 bool "Enable encryption in autoboot stopping"
895 depends on AUTOBOOT_KEYED
897 This option allows a string to be entered into U-Boot to stop the
899 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
901 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
902 to the crypt-based functionality and be compared against the
903 string in the environment variable 'bootstopkeycrypt'.
904 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
905 and compared against the hash in the environment variable
907 If it matches in either case then boot stops and
908 a command-line prompt is presented.
909 This provides a way to ship a secure production device which can also
910 be accessed at the U-Boot command line.
912 config AUTOBOOT_SHA256_FALLBACK
913 bool "Allow fallback from crypt-hashed password to sha256"
914 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
916 This option adds support to fall back from crypt-hashed
917 passwords to checking a SHA256 hashed password in case the
918 'bootstopusesha256' environment variable is set to 'true'.
920 config AUTOBOOT_DELAY_STR
921 string "Delay autobooting via specific input key / string"
922 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
924 This option delays the automatic boot feature by issuing
925 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
926 or the environment variable "bootdelaykey" is specified
927 and this string is received from console input before
928 autoboot starts booting, U-Boot gives a command prompt. The
929 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
930 used, otherwise it never times out.
932 config AUTOBOOT_STOP_STR
933 string "Stop autobooting via specific input key / string"
934 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
936 This option enables stopping (aborting) of the automatic
937 boot feature only by issuing a specific input key or
938 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
939 variable "bootstopkey" is specified and this string is
940 received from console input before autoboot starts booting,
941 U-Boot gives a command prompt. The U-Boot prompt never
942 times out, even if CONFIG_BOOT_RETRY_TIME is used.
944 config AUTOBOOT_KEYED_CTRLC
945 bool "Enable Ctrl-C autoboot interruption"
946 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
948 This option allows for the boot sequence to be interrupted
949 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
950 Setting this variable provides an escape sequence from the
951 limited "password" strings.
953 config AUTOBOOT_NEVER_TIMEOUT
954 bool "Make the password entry never time-out"
955 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
957 This option removes the timeout from the password entry
958 when the user first presses the <Enter> key before entering
961 config AUTOBOOT_STOP_STR_ENABLE
962 bool "Enable fixed string to stop autobooting"
963 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
965 This option enables the feature to add a fixed stop
966 string that is defined at compile time.
967 In every case it will be tried to load the stop
968 string from the environment.
969 In case this is enabled and there is no stop string
970 in the environment, this will be used as default value.
972 config AUTOBOOT_STOP_STR_CRYPT
973 string "Stop autobooting via crypt-hashed password"
974 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
976 This option adds the feature to only stop the autobooting,
977 and therefore boot into the U-Boot prompt, when the input
978 string / password matches a values that is hashed via
979 one of the supported crypt-style password hashing options
980 and saved in the environment variable "bootstopkeycrypt".
982 config AUTOBOOT_STOP_STR_SHA256
983 string "Stop autobooting via SHA256 hashed password"
984 depends on AUTOBOOT_STOP_STR_ENABLE
986 This option adds the feature to only stop the autobooting,
987 and therefore boot into the U-Boot prompt, when the input
988 string / password matches a values that is encypted via
989 a SHA256 hash and saved in the environment variable
990 "bootstopkeysha256". If the value in that variable
991 includes a ":", the portion prior to the ":" will be treated
994 config AUTOBOOT_USE_MENUKEY
995 bool "Allow a specify key to run a menu from the environment"
996 depends on !AUTOBOOT_KEYED
998 If a specific key is pressed to stop autoboot, then the commands in
999 the environment variable 'menucmd' are executed before boot starts.
1001 config AUTOBOOT_MENUKEY
1002 int "ASCII value of boot key to show a menu"
1004 depends on AUTOBOOT_USE_MENUKEY
1006 If this key is pressed to stop autoboot, then the commands in the
1007 environment variable 'menucmd' will be executed before boot starts.
1008 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1011 config AUTOBOOT_MENU_SHOW
1012 bool "Show a menu on boot"
1013 depends on CMD_BOOTMENU
1015 This enables the boot menu, controlled by environment variables
1016 defined by the board. The menu starts after running the 'preboot'
1017 environmnent variable (if enabled) and before handling the boot delay.
1018 See README.bootmenu for more details.
1021 bool "Boot retry feature"
1023 Allow for having the U-Boot command prompt time out and attempt
1024 to boot again. If the environment variable "bootretry" is found then
1025 its value is used, otherwise the retry timeout is
1026 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1027 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1029 config BOOT_RETRY_TIME
1030 int "Timeout in seconds before attempting to boot again"
1031 depends on BOOT_RETRY
1033 Time in seconds before the U-Boot prompt will timeout and boot will
1036 config BOOT_RETRY_MIN
1037 int "Minimum timeout in seconds for 'bootretry'"
1038 depends on BOOT_RETRY
1039 default BOOT_RETRY_TIME
1041 The minimum time in seconds that "bootretry" can be set to.
1043 config RESET_TO_RETRY
1044 bool "Reset the board to retry autoboot"
1045 depends on BOOT_RETRY
1047 After the countdown timed out, the board will be reset to restart
1052 menu "Image support"
1054 config IMAGE_PRE_LOAD
1055 bool "Image pre-load support"
1057 Enable an image pre-load stage in the SPL.
1058 This pre-load stage allows to do some manipulation
1059 or check (for example signature check) on an image
1060 before launching it.
1062 config SPL_IMAGE_PRE_LOAD
1063 bool "Image pre-load support within SPL"
1064 depends on SPL && IMAGE_PRE_LOAD
1066 Enable an image pre-load stage in the SPL.
1067 This pre-load stage allows to do some manipulation
1068 or check (for example signature check) on an image
1069 before launching it.
1071 config IMAGE_PRE_LOAD_SIG
1072 bool "Image pre-load signature support"
1073 depends on IMAGE_PRE_LOAD
1074 select FIT_SIGNATURE
1076 select RSA_VERIFY_WITH_PKEY
1078 Enable signature check support in the pre-load stage.
1079 For this feature a very simple header is added before
1080 the image with few fields:
1084 All other information (header size, type of signature,
1085 ...) are provided in the node /image/pre-load/sig of
1088 config SPL_IMAGE_PRE_LOAD_SIG
1089 bool "Image pre-load signature support witin SPL"
1090 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1091 select SPL_FIT_SIGNATURE
1093 select SPL_RSA_VERIFY_WITH_PKEY
1095 Enable signature check support in the pre-load stage in the SPL.
1096 For this feature a very simple header is added before
1097 the image with few fields:
1101 All other information (header size, type of signature,
1102 ...) are provided in the node /image/pre-load/sig of
1108 bool "Enable boot arguments"
1110 Provide boot arguments to bootm command. Boot arguments are specified
1111 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1112 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1113 will be undefined and won't take any space in U-Boot image.
1116 string "Boot arguments"
1117 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1119 This can be used to pass arguments to the bootm command. The value of
1120 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1121 this value will also override the "chosen" node in FDT blob.
1123 config BOOTARGS_SUBST
1124 bool "Support substituting strings in boot arguments"
1126 This allows substituting string values in the boot arguments. These
1127 are applied after the commandline has been built.
1129 One use for this is to insert the root-disk UUID into the command
1130 line where bootargs contains "root=${uuid}"
1132 setenv bootargs "console= root=${uuid}"
1133 # Set the 'uuid' environment variable
1134 part uuid mmc 2:2 uuid
1136 # Command-line substitution will put the real uuid into the
1137 # kernel command line
1140 config USE_BOOTCOMMAND
1141 bool "Enable a default value for bootcmd"
1143 Provide a default value for the bootcmd entry in the environment. If
1144 autoboot is enabled this is what will be run automatically. Enable
1145 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1146 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1147 won't take any space in U-Boot image.
1150 string "bootcmd value"
1151 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1152 default "run distro_bootcmd" if DISTRO_DEFAULTS
1154 This is the string of commands that will be used as bootcmd and if
1155 AUTOBOOT is set, automatically run.
1158 bool "Enable preboot"
1160 When this option is enabled, the existence of the environment
1161 variable "preboot" will be checked immediately before starting the
1162 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1163 entering interactive mode.
1165 This feature is especially useful when "preboot" is automatically
1166 generated or modified. For example, the boot code can modify the
1167 "preboot" when a user holds down a certain combination of keys.
1170 string "preboot default value"
1171 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1172 default "usb start" if USB_KEYBOARD
1175 This is the default of "preboot" environment variable.
1177 config DEFAULT_FDT_FILE
1178 string "Default fdt file"
1180 This option is used to set the default fdt file to boot OS.