5 config ANDROID_BOOT_IMAGE
6 bool "Enable support for Android Boot Images"
9 This enables support for booting images which use the Android
13 bool "Support Flattened Image Tree"
19 This option allows you to boot the new uImage structure,
20 Flattened Image Tree. FIT is formally a FDT, which can include
21 images of various types (kernel, FDT blob, ramdisk, etc.)
22 in a single blob. To boot this new uImage structure,
23 pass the address of the blob to the "bootm" command.
24 FIT is very flexible, supporting compression, multiple images,
25 multiple configurations, verification through hashing and also
26 verified boot (secure boot using RSA).
29 bool "Show image date and time when displaying image information"
32 When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of
33 an image is printed by image commands like bootm or iminfo. This
34 is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is
35 enabled, then U-Boot requires FITs to have a timestamp. If a FIT is
36 loaded that does not, the message 'Wrong FIT format: no timestamp'
41 config FIT_EXTERNAL_OFFSET
42 hex "FIT external data offset"
45 This specifies a data offset in fit image.
46 The offset is from data payload offset to the beginning of
47 fit image header. When specifies a offset, specific data
48 could be put in the hole between data payload and fit image
49 header, such as CSF data on i.MX platform.
52 bool "Do a full check of the FIT before using it"
55 Enable this do a full check of the FIT to make sure it is valid. This
56 helps to protect against carefully crafted FITs which take advantage
57 of bugs or omissions in the code. This includes a bad structure,
58 multiple root nodes and the like.
61 bool "Enable signature verification of FIT uImages"
66 select IMAGE_SIGN_INFO
69 This option enables signature verification of FIT uImages,
70 using a hash signed and verified using RSA. If
71 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
72 hashing is available using hardware, then the RSA library will use
73 it. See doc/uImage.FIT/signature.txt for more details.
75 WARNING: When relying on signed FIT images with a required signature
76 check the legacy image format is disabled by default, so that
77 unsigned images cannot be loaded. If a board needs the legacy image
78 format support in this case, enable it using
79 CONFIG_LEGACY_IMAGE_FORMAT.
81 config FIT_SIGNATURE_MAX_SIZE
82 hex "Max size of signed FIT structures"
83 depends on FIT_SIGNATURE
86 This option sets a max size in bytes for verified FIT uImages.
87 A sane value of 256MB protects corrupted DTB structures from overlapping
88 device memory. Assure this size does not extend past expected storage
92 bool "Support rsassa-pss signature scheme of FIT image contents"
93 depends on FIT_SIGNATURE
95 Enable this to support the pss padding algorithm as described
96 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
99 bool "Enable ciphering data in a FIT uImages"
103 Enable the feature of data ciphering/unciphering in the tool mkimage
104 and in the u-boot support of the FIT image.
107 bool "Show verbose messages when FIT images fail"
109 Generally a system will have valid FIT images so debug messages
110 are a waste of code space. If you are debugging your images then
111 you can enable this option to get more verbose information about
114 config FIT_BEST_MATCH
115 bool "Select the best match for the kernel device tree"
117 When no configuration is explicitly selected, default to the
118 one whose fdt's compatibility field best matches that of
119 U-Boot itself. A match is considered "best" if it matches the
120 most specific compatibility entry of U-Boot's fdt's root node.
121 The order of entries in the configuration's fdt is ignored.
123 config FIT_IMAGE_POST_PROCESS
124 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
125 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
127 Allows doing any sort of manipulation to blobs after they got extracted
128 from FIT images like stripping off headers or modifying the size of the
129 blob, verification, authentication, decryption etc. in a platform or
130 board specific way. In order to use this feature a platform or board-
131 specific implementation of board_fit_image_post_process() must be
132 provided. Also, anything done during this post-processing step would
133 need to be comprehended in how the images were prepared before being
134 injected into the FIT creation (i.e. the blobs would have been pre-
135 processed before being added to the FIT image).
138 bool "Support FIT printing"
141 Support printing the content of the fitImage in a verbose manner.
146 bool "Support Flattened Image Tree within SPL"
152 bool "Support FIT printing within SPL"
155 Support printing the content of the fitImage in a verbose manner in SPL.
157 config SPL_FIT_FULL_CHECK
158 bool "Do a full check of the FIT before using it"
160 Enable this do a full check of the FIT to make sure it is valid. This
161 helps to protect against carefully crafted FITs which take advantage
162 of bugs or omissions in the code. This includes a bad structure,
163 multiple root nodes and the like.
166 config SPL_FIT_SIGNATURE
167 bool "Enable signature verification of FIT firmware within SPL"
169 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
176 select SPL_IMAGE_SIGN_INFO
177 select SPL_FIT_FULL_CHECK
179 config SPL_FIT_SIGNATURE_MAX_SIZE
180 hex "Max size of signed FIT structures in SPL"
181 depends on SPL_FIT_SIGNATURE
184 This option sets a max size in bytes for verified FIT uImages.
185 A sane value of 256MB protects corrupted DTB structures from overlapping
186 device memory. Assure this size does not extend past expected storage
189 config SPL_FIT_RSASSA_PSS
190 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
191 depends on SPL_FIT_SIGNATURE
193 Enable this to support the pss padding algorithm as described
194 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
197 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
200 Normally with the SPL framework a legacy image is generated as part
201 of the build. This contains U-Boot along with information as to
202 where it should be loaded. This option instead enables generation
203 of a FIT (Flat Image Tree) which provides more flexibility. In
204 particular it can handle selecting from multiple device tree
205 and passing the correct one to U-Boot.
207 This path has the following limitations:
209 1. "loadables" images, other than FDTs, which do not have a "load"
210 property will not be loaded. This limitation also applies to FPGA
211 images with the correct "compatible" string.
212 2. For FPGA images, only the "compatible" = "u-boot,fpga-legacy"
213 loading method is supported.
214 3. FDTs are only loaded for images with an "os" property of "u-boot".
215 "linux" images are also supported with Falcon boot mode.
217 config SPL_LOAD_FIT_ADDRESS
218 hex "load address of fit image"
219 depends on SPL_LOAD_FIT
222 Specify the load address of the fit image that will be loaded
225 config SPL_LOAD_FIT_APPLY_OVERLAY
226 bool "Enable SPL applying DT overlays from FIT"
227 depends on SPL_LOAD_FIT
228 select OF_LIBFDT_OVERLAY
230 The device tree is loaded from the FIT image. Allow the SPL is to
231 also load device-tree overlays from the FIT image an apply them
232 over the device tree.
234 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
235 depends on SPL_LOAD_FIT_APPLY_OVERLAY
237 hex "size of temporary buffer used to load the overlays"
239 The size of the area where the overlays will be loaded and
240 uncompress. Must be at least as large as biggest overlay
243 config SPL_LOAD_FIT_FULL
244 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
247 Normally with the SPL framework a legacy image is generated as part
248 of the build. This contains U-Boot along with information as to
249 where it should be loaded. This option instead enables generation
250 of a FIT (Flat Image Tree) which provides more flexibility. In
251 particular it can handle selecting from multiple device tree
252 and passing the correct one to U-Boot.
254 config SPL_FIT_IMAGE_POST_PROCESS
255 bool "Enable post-processing of FIT artifacts after loading by the SPL"
256 depends on SPL_LOAD_FIT
258 Allows doing any sort of manipulation to blobs after they got extracted
259 from the U-Boot FIT image like stripping off headers or modifying the
260 size of the blob, verification, authentication, decryption etc. in a
261 platform or board specific way. In order to use this feature a platform
262 or board-specific implementation of board_fit_image_post_process() must
263 be provided. Also, anything done during this post-processing step would
264 need to be comprehended in how the images were prepared before being
265 injected into the FIT creation (i.e. the blobs would have been pre-
266 processed before being added to the FIT image).
268 config SPL_FIT_SOURCE
269 string ".its source file for U-Boot FIT image"
272 Specifies a (platform specific) FIT source file to generate the
273 U-Boot FIT image. This could specify further image to load and/or
276 config USE_SPL_FIT_GENERATOR
277 bool "Use a script to generate the .its script"
278 default y if SPL_FIT && (!ARCH_SUNXI && !RISCV)
280 config SPL_FIT_GENERATOR
281 string ".its file generator script for U-Boot FIT image"
282 depends on USE_SPL_FIT_GENERATOR
283 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
284 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
286 Specifies a (platform specific) script file to generate the FIT
287 source file used to build the U-Boot FIT image file. This gets
288 passed a list of supported device tree file stub names to
289 include in the generated image.
296 bool "Standard boot support"
298 depends on DM && OF_CONTROL && BLK
300 U-Boot supports a standard way of locating something to boot,
301 typically an Operating System such as Linux, provided by a distro such
302 as Arch Linux or Debian. Enable this to support iterating through
303 available bootdevs and using bootmeths to find bootflows suitable for
306 Standard boot is not a standard way of booting, just a framework
307 within U-Boot for supporting all the different ways that exist.
311 - bootdev - a device which can hold a distro (e.g. MMC)
312 - bootmeth - a method to scan a bootdev to find bootflows (owned by
314 - bootflow - a description of how to boot (owned by the distro)
317 bool "Enhanced features for standard boot"
320 This enables various useful features for standard boot, which are not
321 essential for operation:
323 - bootdev, bootmeth commands
324 - extra features in the bootflow command
325 - support for selecting the ordering of bootmeths ("bootmeth order")
326 - support for selecting the ordering of bootdevs using the devicetree
327 as well as the "boot_targets" environment variable
329 config LEGACY_IMAGE_FORMAT
330 bool "Enable support for the legacy image format"
331 default y if !FIT_SIGNATURE
333 This option enables the legacy image format. It is enabled by
334 default for backward compatibility, unless FIT_SIGNATURE is
335 set where it is disabled so that unsigned images cannot be
336 loaded. If a board needs the legacy image format support in this
337 case, enable it here.
339 config SUPPORT_RAW_INITRD
340 bool "Enable raw initrd images"
342 Note, defining the SUPPORT_RAW_INITRD allows user to supply
343 kernel with raw initrd images. The syntax is slightly different, the
344 address of the initrd must be augmented by it's size, in the following
345 format: "<initrd address>:<initrd size>".
347 config OF_BOARD_SETUP
348 bool "Set up board-specific details in device tree before boot"
351 This causes U-Boot to call ft_board_setup() before booting into
352 the Operating System. This function can set up various
353 board-specific information in the device tree for use by the OS.
354 The device tree is then passed to the OS.
356 config OF_SYSTEM_SETUP
357 bool "Set up system-specific details in device tree before boot"
360 This causes U-Boot to call ft_system_setup() before booting into
361 the Operating System. This function can set up various
362 system-specific information in the device tree for use by the OS.
363 The device tree is then passed to the OS.
365 config OF_STDOUT_VIA_ALIAS
366 bool "Update the device-tree stdout alias from U-Boot"
369 This uses U-Boot's serial alias from the aliases node to update
370 the device tree passed to the OS. The "linux,stdout-path" property
371 in the chosen node is set to point to the correct serial node.
372 This option currently references CONFIG_CONS_INDEX, which is
373 incorrect when used with device tree as this option does not
374 exist / should not be used.
376 config SYS_EXTRA_OPTIONS
377 string "Extra Options (DEPRECATED)"
379 The old configuration infrastructure (= mkconfig + boards.cfg)
380 provided the extra options field. If you have something like
381 "HAS_BAR,BAZ=64", the optional options
383 #define CONFIG_BAZ 64
384 will be defined in include/config.h.
385 This option was prepared for the smooth migration from the old
386 configuration to Kconfig. Since this option will be removed sometime,
387 new boards should not use this option.
389 config HAVE_SYS_TEXT_BASE
391 depends on !NIOS2 && !XTENSA
396 depends on HAVE_SYS_TEXT_BASE
397 default 0x0 if POSITION_INDEPENDENT
398 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
399 default 0x81700000 if MACH_SUNIV
400 default 0x2a000000 if MACH_SUN9I
401 default 0x42e00000 if MACH_SUN8I_V3S
402 default 0x4a000000 if ARCH_SUNXI
405 The address in memory that U-Boot will be running from, initially.
407 config HAVE_SYS_MONITOR_BASE
409 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
410 || FLASH_PIC32 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
414 config SYS_MONITOR_BASE
415 depends on HAVE_SYS_MONITOR_BASE
416 hex "Physical start address of boot monitor code"
417 default SYS_TEXT_BASE
419 The physical start address of boot monitor code (which is the same as
420 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
421 when booting from flash.
423 config SPL_SYS_MONITOR_BASE
424 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
425 hex "Physical start address of SPL monitor code"
426 default SPL_TEXT_BASE
428 config TPL_SYS_MONITOR_BASE
429 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
430 hex "Physical start address of TPL monitor code"
432 config DYNAMIC_SYS_CLK_FREQ
433 bool "Determine CPU clock frequency at run-time"
435 Implement a get_board_sys_clk function that will determine the CPU
436 clock frequency at run time, rather than define it statically.
439 depends on !DYNAMIC_SYS_CLK_FREQ
440 int "CPU clock frequency"
441 default 125000000 if ARCH_LS1012A
442 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
443 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
444 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
445 default 66660000 if ARCH_T2080
446 default 33333333 if RCAR_GEN3
447 default 24000000 if ARCH_EXYNOS
448 default 20000000 if RCAR_GEN2
451 A static value for the CPU frequency. Note that if not required
452 for a given SoC, this can be left at 0.
454 config ARCH_FIXUP_FDT_MEMORY
455 bool "Enable arch_fixup_memory_banks() call"
458 Enable FDT memory map syncup before OS boot. This feature can be
459 used for booting OS with different memory setup where the part of
460 the memory location should be used for different purpose.
463 bool "Support booting Chrome OS"
465 Chrome OS requires U-Boot to set up a table indicating the boot mode
466 (e.g. Developer mode) and a few other things. Enable this if you are
467 booting on a Chromebook to avoid getting an error about an invalid
470 config CHROMEOS_VBOOT
471 bool "Support Chrome OS verified boot"
473 This is intended to enable the full Chrome OS verified boot support
474 in U-Boot. It is not actually implemented in the U-Boot source code
475 at present, so this option is always set to 'n'. It allows
476 distinguishing between booting Chrome OS in a basic way (developer
477 mode) and a full boot.
480 bool "Freescale PBL(pre-boot loader) image format support"
482 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
483 For more details refer to doc/README.pblimage
486 prompt "Freescale PBL load location"
487 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
488 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
492 bool "Freescale PBL is found on SD card"
495 bool "Freescale PBL is found on SPI flash"
499 config SYS_FSL_PBL_PBI
500 string "PBI(pre-boot instructions) commands for the PBL image"
501 depends on RAMBOOT_PBL
503 PBI commands can be used to configure SoC before it starts the execution.
504 Please refer doc/README.pblimage for more details.
506 config SYS_FSL_PBL_RCW
507 string "Aadditional RCW (Power on reset configuration) for the PBL image"
508 depends on RAMBOOT_PBL
510 Enables addition of RCW (Power on reset configuration) in built image.
511 Please refer doc/README.pblimage for more details.
513 endmenu # Boot images
518 bool "Boot timing and reporting"
520 Enable recording of boot time while booting. To use it, insert
521 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
522 bootstage.h. Only a single entry is recorded for each ID. You can
523 give the entry a name with bootstage_mark_name(). You can also
524 record elapsed time in a particular stage using bootstage_start()
525 before starting and bootstage_accum() when finished. Bootstage will
526 add up all the accumulated time and report it.
528 Normally, IDs are defined in bootstage.h but a small number of
529 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
532 Calls to show_boot_progress() will also result in log entries but
533 these will not have names.
536 bool "Boot timing and reported in SPL"
539 Enable recording of boot time in SPL. To make this visible to U-Boot
540 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
541 information when SPL finishes and load it when U-Boot proper starts
545 bool "Boot timing and reported in TPL"
548 Enable recording of boot time in SPL. To make this visible to U-Boot
549 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
550 information when TPL finishes and load it when U-Boot proper starts
553 config BOOTSTAGE_REPORT
554 bool "Display a detailed boot timing report before booting the OS"
557 Enable output of a boot time report just before the OS is booted.
558 This shows how long it took U-Boot to go through each stage of the
559 boot process. The report looks something like this:
561 Timer summary in microseconds:
564 3,575,678 3,575,678 board_init_f start
565 3,575,695 17 arch_cpu_init A9
566 3,575,777 82 arch_cpu_init done
567 3,659,598 83,821 board_init_r start
568 3,910,375 250,777 main_loop
569 29,916,167 26,005,792 bootm_start
570 30,361,327 445,160 start_kernel
572 config BOOTSTAGE_RECORD_COUNT
573 int "Number of boot stage records to store"
577 This is the size of the bootstage record list and is the maximum
578 number of bootstage records that can be recorded.
580 config SPL_BOOTSTAGE_RECORD_COUNT
581 int "Number of boot stage records to store for SPL"
582 depends on SPL_BOOTSTAGE
585 This is the size of the bootstage record list and is the maximum
586 number of bootstage records that can be recorded.
588 config TPL_BOOTSTAGE_RECORD_COUNT
589 int "Number of boot stage records to store for TPL"
590 depends on TPL_BOOTSTAGE
593 This is the size of the bootstage record list and is the maximum
594 number of bootstage records that can be recorded.
597 bool "Store boot timing information in the OS device tree"
600 Stash the bootstage information in the FDT. A root 'bootstage'
601 node is created with each bootstage id as a child. Each child
602 has a 'name' property and either 'mark' containing the
603 mark time in microseconds, or 'accum' containing the
604 accumulated time for that bootstage id in microseconds.
609 name = "board_init_f";
618 Code in the Linux kernel can find this in /proc/devicetree.
620 config BOOTSTAGE_STASH
621 bool "Stash the boot timing information in memory before booting OS"
624 Some OSes do not support device tree. Bootstage can instead write
625 the boot timing information in a binary format at a given address.
626 This happens through a call to bootstage_stash(), typically in
627 the CPU's cleanup_before_linux() function. You can use the
628 'bootstage stash' and 'bootstage unstash' commands to do this on
631 config BOOTSTAGE_STASH_ADDR
632 hex "Address to stash boot timing information"
635 Provide an address which will not be overwritten by the OS when it
636 starts, so that it can read this information when ready.
638 config BOOTSTAGE_STASH_SIZE
639 hex "Size of boot timing stash region"
642 This should be large enough to hold the bootstage stash. A value of
643 4096 (4KiB) is normally plenty.
645 config SHOW_BOOT_PROGRESS
646 bool "Show boot progress in a board-specific manner"
648 Defining this option allows to add some board-specific code (calling
649 a user-provided function show_boot_progress(int) that enables you to
650 show the system's boot progress on some display (for example, some
651 LEDs) on your board. At the moment, the following checkpoints are
654 Legacy uImage format:
657 1 common/cmd_bootm.c before attempting to boot an image
658 -1 common/cmd_bootm.c Image header has bad magic number
659 2 common/cmd_bootm.c Image header has correct magic number
660 -2 common/cmd_bootm.c Image header has bad checksum
661 3 common/cmd_bootm.c Image header has correct checksum
662 -3 common/cmd_bootm.c Image data has bad checksum
663 4 common/cmd_bootm.c Image data has correct checksum
664 -4 common/cmd_bootm.c Image is for unsupported architecture
665 5 common/cmd_bootm.c Architecture check OK
666 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
667 6 common/cmd_bootm.c Image Type check OK
668 -6 common/cmd_bootm.c gunzip uncompression error
669 -7 common/cmd_bootm.c Unimplemented compression type
670 7 common/cmd_bootm.c Uncompression OK
671 8 common/cmd_bootm.c No uncompress/copy overwrite error
672 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
674 9 common/image.c Start initial ramdisk verification
675 -10 common/image.c Ramdisk header has bad magic number
676 -11 common/image.c Ramdisk header has bad checksum
677 10 common/image.c Ramdisk header is OK
678 -12 common/image.c Ramdisk data has bad checksum
679 11 common/image.c Ramdisk data has correct checksum
680 12 common/image.c Ramdisk verification complete, start loading
681 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
682 13 common/image.c Start multifile image verification
683 14 common/image.c No initial ramdisk, no multifile, continue.
685 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
687 -30 arch/powerpc/lib/board.c Fatal error, hang the system
688 -31 post/post.c POST test failed, detected by post_output_backlog()
689 -32 post/post.c POST test failed, detected by post_run_single()
691 34 common/cmd_doc.c before loading a Image from a DOC device
692 -35 common/cmd_doc.c Bad usage of "doc" command
693 35 common/cmd_doc.c correct usage of "doc" command
694 -36 common/cmd_doc.c No boot device
695 36 common/cmd_doc.c correct boot device
696 -37 common/cmd_doc.c Unknown Chip ID on boot device
697 37 common/cmd_doc.c correct chip ID found, device available
698 -38 common/cmd_doc.c Read Error on boot device
699 38 common/cmd_doc.c reading Image header from DOC device OK
700 -39 common/cmd_doc.c Image header has bad magic number
701 39 common/cmd_doc.c Image header has correct magic number
702 -40 common/cmd_doc.c Error reading Image from DOC device
703 40 common/cmd_doc.c Image header has correct magic number
704 41 common/cmd_ide.c before loading a Image from a IDE device
705 -42 common/cmd_ide.c Bad usage of "ide" command
706 42 common/cmd_ide.c correct usage of "ide" command
707 -43 common/cmd_ide.c No boot device
708 43 common/cmd_ide.c boot device found
709 -44 common/cmd_ide.c Device not available
710 44 common/cmd_ide.c Device available
711 -45 common/cmd_ide.c wrong partition selected
712 45 common/cmd_ide.c partition selected
713 -46 common/cmd_ide.c Unknown partition table
714 46 common/cmd_ide.c valid partition table found
715 -47 common/cmd_ide.c Invalid partition type
716 47 common/cmd_ide.c correct partition type
717 -48 common/cmd_ide.c Error reading Image Header on boot device
718 48 common/cmd_ide.c reading Image Header from IDE device OK
719 -49 common/cmd_ide.c Image header has bad magic number
720 49 common/cmd_ide.c Image header has correct magic number
721 -50 common/cmd_ide.c Image header has bad checksum
722 50 common/cmd_ide.c Image header has correct checksum
723 -51 common/cmd_ide.c Error reading Image from IDE device
724 51 common/cmd_ide.c reading Image from IDE device OK
725 52 common/cmd_nand.c before loading a Image from a NAND device
726 -53 common/cmd_nand.c Bad usage of "nand" command
727 53 common/cmd_nand.c correct usage of "nand" command
728 -54 common/cmd_nand.c No boot device
729 54 common/cmd_nand.c boot device found
730 -55 common/cmd_nand.c Unknown Chip ID on boot device
731 55 common/cmd_nand.c correct chip ID found, device available
732 -56 common/cmd_nand.c Error reading Image Header on boot device
733 56 common/cmd_nand.c reading Image Header from NAND device OK
734 -57 common/cmd_nand.c Image header has bad magic number
735 57 common/cmd_nand.c Image header has correct magic number
736 -58 common/cmd_nand.c Error reading Image from NAND device
737 58 common/cmd_nand.c reading Image from NAND device OK
739 -60 common/env_common.c Environment has a bad CRC, using default
741 64 net/eth.c starting with Ethernet configuration.
742 -64 net/eth.c no Ethernet found.
743 65 net/eth.c Ethernet found.
745 -80 common/cmd_net.c usage wrong
746 80 common/cmd_net.c before calling net_loop()
747 -81 common/cmd_net.c some error in net_loop() occurred
748 81 common/cmd_net.c net_loop() back without error
749 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
750 82 common/cmd_net.c trying automatic boot
751 83 common/cmd_net.c running "source" command
752 -83 common/cmd_net.c some error in automatic boot or "source" command
753 84 common/cmd_net.c end without errors
758 100 common/cmd_bootm.c Kernel FIT Image has correct format
759 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
760 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
761 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
762 102 common/cmd_bootm.c Kernel unit name specified
763 -103 common/cmd_bootm.c Can't get kernel subimage node offset
764 103 common/cmd_bootm.c Found configuration node
765 104 common/cmd_bootm.c Got kernel subimage node offset
766 -104 common/cmd_bootm.c Kernel subimage hash verification failed
767 105 common/cmd_bootm.c Kernel subimage hash verification OK
768 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
769 106 common/cmd_bootm.c Architecture check OK
770 -106 common/cmd_bootm.c Kernel subimage has wrong type
771 107 common/cmd_bootm.c Kernel subimage type OK
772 -107 common/cmd_bootm.c Can't get kernel subimage data/size
773 108 common/cmd_bootm.c Got kernel subimage data/size
774 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
775 -109 common/cmd_bootm.c Can't get kernel subimage type
776 -110 common/cmd_bootm.c Can't get kernel subimage comp
777 -111 common/cmd_bootm.c Can't get kernel subimage os
778 -112 common/cmd_bootm.c Can't get kernel subimage load address
779 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
781 120 common/image.c Start initial ramdisk verification
782 -120 common/image.c Ramdisk FIT image has incorrect format
783 121 common/image.c Ramdisk FIT image has correct format
784 122 common/image.c No ramdisk subimage unit name, using configuration
785 -122 common/image.c Can't get configuration for ramdisk subimage
786 123 common/image.c Ramdisk unit name specified
787 -124 common/image.c Can't get ramdisk subimage node offset
788 125 common/image.c Got ramdisk subimage node offset
789 -125 common/image.c Ramdisk subimage hash verification failed
790 126 common/image.c Ramdisk subimage hash verification OK
791 -126 common/image.c Ramdisk subimage for unsupported architecture
792 127 common/image.c Architecture check OK
793 -127 common/image.c Can't get ramdisk subimage data/size
794 128 common/image.c Got ramdisk subimage data/size
795 129 common/image.c Can't get ramdisk load address
796 -129 common/image.c Got ramdisk load address
798 -130 common/cmd_doc.c Incorrect FIT image format
799 131 common/cmd_doc.c FIT image format OK
801 -140 common/cmd_ide.c Incorrect FIT image format
802 141 common/cmd_ide.c FIT image format OK
804 -150 common/cmd_nand.c Incorrect FIT image format
805 151 common/cmd_nand.c FIT image format OK
807 config SPL_SHOW_BOOT_PROGRESS
808 bool "Show boot progress in a board-specific manner in SPL"
811 Defining this option allows to add some board-specific code (calling
812 a user-provided function show_boot_progress(int) that enables you to
813 show the system's boot progress on some display (for example, some
814 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
821 bool "Support for booting from NOR flash"
824 Enabling this will make a U-Boot binary that is capable of being
825 booted via NOR. In this case we will enable certain pinmux early
826 as the ROM only partially sets up pinmux. We also default to using
830 bool "Support for booting from NAND flash"
833 Enabling this will make a U-Boot binary that is capable of being
834 booted via NAND flash. This is not a must, some SoCs need this,
838 bool "Support for booting from ONENAND"
841 Enabling this will make a U-Boot binary that is capable of being
842 booted via ONENAND. This is not a must, some SoCs need this,
846 bool "Support for booting from QSPI flash"
848 Enabling this will make a U-Boot binary that is capable of being
849 booted via QSPI flash. This is not a must, some SoCs need this,
853 bool "Support for booting from SATA"
855 Enabling this will make a U-Boot binary that is capable of being
856 booted via SATA. This is not a must, some SoCs need this,
860 bool "Support for booting from SD/EMMC"
862 Enabling this will make a U-Boot binary that is capable of being
863 booted via SD/EMMC. This is not a must, some SoCs need this,
867 bool "Support for booting from SD/EMMC and enable QSPI"
869 Enabling this will make a U-Boot binary that is capable of being
870 booted via SD/EMMC while enabling QSPI on the platform as well. This
871 is not a must, some SoCs need this, some not.
874 bool "Support for booting from SPI flash"
876 Enabling this will make a U-Boot binary that is capable of being
877 booted via SPI flash. This is not a must, some SoCs need this,
882 menu "Autoboot options"
888 This enables the autoboot. See doc/README.autoboot for detail.
891 int "delay in seconds before automatically booting"
895 Delay before automatically running bootcmd;
896 set to 0 to autoboot with no delay, but you can stop it by key input.
897 set to -1 to disable autoboot.
898 set to -2 to autoboot with no delay and not check for abort
900 If this value is >= 0 then it is also used for the default delay
901 before starting the default entry in bootmenu. If it is < 0 then
902 a default value of 10s is used.
904 See doc/README.autoboot for details.
906 config AUTOBOOT_KEYED
907 bool "Stop autobooting via specific input key / string"
909 This option enables stopping (aborting) of the automatic
910 boot feature only by issuing a specific input key or
911 string. If not enabled, any input key will abort the
912 U-Boot automatic booting process and bring the device
913 to the U-Boot prompt for user input.
915 config AUTOBOOT_FLUSH_STDIN
916 bool "Enable flushing stdin before starting to read the password"
917 depends on AUTOBOOT_KEYED && !SANDBOX
919 When this option is enabled stdin buffer will be flushed before
920 starting to read the password.
921 This can't be enabled for the sandbox as flushing stdin would
922 break the autoboot unit tests.
924 config AUTOBOOT_PROMPT
925 string "Autoboot stop prompt"
926 depends on AUTOBOOT_KEYED
927 default "Autoboot in %d seconds\\n"
929 This string is displayed before the boot delay selected by
930 CONFIG_BOOTDELAY starts. If it is not defined there is no
931 output indicating that autoboot is in progress.
933 Note that this define is used as the (only) argument to a
934 printf() call, so it may contain '%' format specifications,
935 provided that it also includes, sepearated by commas exactly
936 like in a printf statement, the required arguments. It is
937 the responsibility of the user to select only such arguments
938 that are valid in the given context.
940 config AUTOBOOT_ENCRYPTION
941 bool "Enable encryption in autoboot stopping"
942 depends on AUTOBOOT_KEYED
944 This option allows a string to be entered into U-Boot to stop the
946 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
948 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
949 to the crypt-based functionality and be compared against the
950 string in the environment variable 'bootstopkeycrypt'.
951 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
952 and compared against the hash in the environment variable
954 If it matches in either case then boot stops and
955 a command-line prompt is presented.
956 This provides a way to ship a secure production device which can also
957 be accessed at the U-Boot command line.
959 config AUTOBOOT_SHA256_FALLBACK
960 bool "Allow fallback from crypt-hashed password to sha256"
961 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
963 This option adds support to fall back from crypt-hashed
964 passwords to checking a SHA256 hashed password in case the
965 'bootstopusesha256' environment variable is set to 'true'.
967 config AUTOBOOT_DELAY_STR
968 string "Delay autobooting via specific input key / string"
969 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
971 This option delays the automatic boot feature by issuing
972 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
973 or the environment variable "bootdelaykey" is specified
974 and this string is received from console input before
975 autoboot starts booting, U-Boot gives a command prompt. The
976 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
977 used, otherwise it never times out.
979 config AUTOBOOT_STOP_STR
980 string "Stop autobooting via specific input key / string"
981 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
983 This option enables stopping (aborting) of the automatic
984 boot feature only by issuing a specific input key or
985 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
986 variable "bootstopkey" is specified and this string is
987 received from console input before autoboot starts booting,
988 U-Boot gives a command prompt. The U-Boot prompt never
989 times out, even if CONFIG_BOOT_RETRY_TIME is used.
991 config AUTOBOOT_KEYED_CTRLC
992 bool "Enable Ctrl-C autoboot interruption"
993 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
995 This option allows for the boot sequence to be interrupted
996 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
997 Setting this variable provides an escape sequence from the
998 limited "password" strings.
1000 config AUTOBOOT_NEVER_TIMEOUT
1001 bool "Make the password entry never time-out"
1002 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1004 This option removes the timeout from the password entry
1005 when the user first presses the <Enter> key before entering
1006 any other character.
1008 config AUTOBOOT_STOP_STR_ENABLE
1009 bool "Enable fixed string to stop autobooting"
1010 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1012 This option enables the feature to add a fixed stop
1013 string that is defined at compile time.
1014 In every case it will be tried to load the stop
1015 string from the environment.
1016 In case this is enabled and there is no stop string
1017 in the environment, this will be used as default value.
1019 config AUTOBOOT_STOP_STR_CRYPT
1020 string "Stop autobooting via crypt-hashed password"
1021 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1023 This option adds the feature to only stop the autobooting,
1024 and therefore boot into the U-Boot prompt, when the input
1025 string / password matches a values that is hashed via
1026 one of the supported crypt-style password hashing options
1027 and saved in the environment variable "bootstopkeycrypt".
1029 config AUTOBOOT_STOP_STR_SHA256
1030 string "Stop autobooting via SHA256 hashed password"
1031 depends on AUTOBOOT_STOP_STR_ENABLE
1033 This option adds the feature to only stop the autobooting,
1034 and therefore boot into the U-Boot prompt, when the input
1035 string / password matches a values that is encypted via
1036 a SHA256 hash and saved in the environment variable
1037 "bootstopkeysha256". If the value in that variable
1038 includes a ":", the portion prior to the ":" will be treated
1041 config AUTOBOOT_USE_MENUKEY
1042 bool "Allow a specify key to run a menu from the environment"
1043 depends on !AUTOBOOT_KEYED
1045 If a specific key is pressed to stop autoboot, then the commands in
1046 the environment variable 'menucmd' are executed before boot starts.
1048 config AUTOBOOT_MENUKEY
1049 int "ASCII value of boot key to show a menu"
1051 depends on AUTOBOOT_USE_MENUKEY
1053 If this key is pressed to stop autoboot, then the commands in the
1054 environment variable 'menucmd' will be executed before boot starts.
1055 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1058 config AUTOBOOT_MENU_SHOW
1059 bool "Show a menu on boot"
1060 depends on CMD_BOOTMENU
1062 This enables the boot menu, controlled by environment variables
1063 defined by the board. The menu starts after running the 'preboot'
1064 environmnent variable (if enabled) and before handling the boot delay.
1065 See README.bootmenu for more details.
1068 bool "Boot retry feature"
1070 Allow for having the U-Boot command prompt time out and attempt
1071 to boot again. If the environment variable "bootretry" is found then
1072 its value is used, otherwise the retry timeout is
1073 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1074 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1076 config BOOT_RETRY_TIME
1077 int "Timeout in seconds before attempting to boot again"
1078 depends on BOOT_RETRY
1080 Time in seconds before the U-Boot prompt will timeout and boot will
1083 config BOOT_RETRY_MIN
1084 int "Minimum timeout in seconds for 'bootretry'"
1085 depends on BOOT_RETRY
1086 default BOOT_RETRY_TIME
1088 The minimum time in seconds that "bootretry" can be set to.
1090 config RESET_TO_RETRY
1091 bool "Reset the board to retry autoboot"
1092 depends on BOOT_RETRY
1094 After the countdown timed out, the board will be reset to restart
1099 menu "Image support"
1101 config IMAGE_PRE_LOAD
1102 bool "Image pre-load support"
1104 Enable an image pre-load stage in the SPL.
1105 This pre-load stage allows to do some manipulation
1106 or check (for example signature check) on an image
1107 before launching it.
1109 config SPL_IMAGE_PRE_LOAD
1110 bool "Image pre-load support within SPL"
1111 depends on SPL && IMAGE_PRE_LOAD
1113 Enable an image pre-load stage in the SPL.
1114 This pre-load stage allows to do some manipulation
1115 or check (for example signature check) on an image
1116 before launching it.
1118 config IMAGE_PRE_LOAD_SIG
1119 bool "Image pre-load signature support"
1120 depends on IMAGE_PRE_LOAD
1121 select FIT_SIGNATURE
1123 select RSA_VERIFY_WITH_PKEY
1125 Enable signature check support in the pre-load stage.
1126 For this feature a very simple header is added before
1127 the image with few fields:
1131 All other information (header size, type of signature,
1132 ...) are provided in the node /image/pre-load/sig of
1135 config SPL_IMAGE_PRE_LOAD_SIG
1136 bool "Image pre-load signature support witin SPL"
1137 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1138 select SPL_FIT_SIGNATURE
1140 select SPL_RSA_VERIFY_WITH_PKEY
1142 Enable signature check support in the pre-load stage in the SPL.
1143 For this feature a very simple header is added before
1144 the image with few fields:
1148 All other information (header size, type of signature,
1149 ...) are provided in the node /image/pre-load/sig of
1155 bool "Enable boot arguments"
1157 Provide boot arguments to bootm command. Boot arguments are specified
1158 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1159 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1160 will be undefined and won't take any space in U-Boot image.
1163 string "Boot arguments"
1164 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1166 This can be used to pass arguments to the bootm command. The value of
1167 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1168 this value will also override the "chosen" node in FDT blob.
1170 config BOOTARGS_SUBST
1171 bool "Support substituting strings in boot arguments"
1173 This allows substituting string values in the boot arguments. These
1174 are applied after the commandline has been built.
1176 One use for this is to insert the root-disk UUID into the command
1177 line where bootargs contains "root=${uuid}"
1179 setenv bootargs "console= root=${uuid}"
1180 # Set the 'uuid' environment variable
1181 part uuid mmc 2:2 uuid
1183 # Command-line substitution will put the real uuid into the
1184 # kernel command line
1187 config USE_BOOTCOMMAND
1188 bool "Enable a default value for bootcmd"
1190 Provide a default value for the bootcmd entry in the environment. If
1191 autoboot is enabled this is what will be run automatically. Enable
1192 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1193 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1194 won't take any space in U-Boot image.
1197 string "bootcmd value"
1198 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1199 default "run distro_bootcmd" if DISTRO_DEFAULTS
1201 This is the string of commands that will be used as bootcmd and if
1202 AUTOBOOT is set, automatically run.
1205 bool "Enable preboot"
1207 When this option is enabled, the existence of the environment
1208 variable "preboot" will be checked immediately before starting the
1209 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1210 entering interactive mode.
1212 This feature is especially useful when "preboot" is automatically
1213 generated or modified. For example, the boot code can modify the
1214 "preboot" when a user holds down a certain combination of keys.
1217 string "preboot default value"
1218 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1219 default "usb start" if USB_KEYBOARD
1222 This is the default of "preboot" environment variable.
1224 config DEFAULT_FDT_FILE
1225 string "Default fdt file"
1227 This option is used to set the default fdt file to boot OS.
1229 config SAVE_PREV_BL_FDT_ADDR
1231 bool "Saves fdt address, passed by the previous bootloader, to env var"
1233 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1234 enable this option to save fdt address, passed by the
1235 previous bootloader for future use.
1236 Address is saved to `prevbl_fdt_addr` environment variable.
1238 If no fdt was provided by previous bootloader, no env variables
1241 config SAVE_PREV_BL_INITRAMFS_START_ADDR
1243 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1245 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1246 enable this option to save initramfs address, passed by the
1247 previous bootloader for future use.
1248 Address is saved to `prevbl_initrd_start_addr` environment variable.
1250 If no initramfs was provided by previous bootloader, no env variables