1menu "Boot options"
2
3menu "Boot images"
4
5config ANDROID_BOOT_IMAGE
6 bool "Enable support for Android Boot Images"
7 default y if FASTBOOT
8 help
9 This enables support for booting images which use the Android
10 image format header.
11
12config FIT
13 bool "Support Flattened Image Tree"
14 select HASH
15 select MD5
16 select SHA1
17 imply SHA256
18 help
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).
27
28config TIMESTAMP
29 bool "Show image date and time when displaying image information"
30 default y if CMD_DATE
31 help
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'
37 is shown.
38
39config FIT_EXTERNAL_OFFSET
40 hex "FIT external data offset"
41 depends on FIT
42 default 0x0
43 help
44 This specifies a data offset in fit image.
45 The offset is from data payload offset to the beginning of
46 fit image header. When specifies a offset, specific data
47 could be put in the hole between data payload and fit image
48 header, such as CSF data on i.MX platform.
49
50config FIT_FULL_CHECK
51 bool "Do a full check of the FIT before using it"
52 depends on FIT
53 default y
54 help
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.
59
60config FIT_SIGNATURE
61 bool "Enable signature verification of FIT uImages"
62 depends on DM && FIT
63 select HASH
64 imply RSA
65 imply RSA_VERIFY
66 select IMAGE_SIGN_INFO
67 select FIT_FULL_CHECK
68 help
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.
74
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.
80
81config FIT_SIGNATURE_MAX_SIZE
82 hex "Max size of signed FIT structures"
83 depends on FIT_SIGNATURE
84 default 0x10000000
85 help
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
89 space.
90
91config FIT_RSASSA_PSS
92 bool "Support rsassa-pss signature scheme of FIT image contents"
93 depends on FIT_SIGNATURE
94 help
95 Enable this to support the pss padding algorithm as described
96 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
97
98config FIT_CIPHER
99 bool "Enable ciphering data in a FIT uImages"
100 depends on DM && FIT
101 select AES
102 help
103 Enable the feature of data ciphering/unciphering in the tool mkimage
104 and in the u-boot support of the FIT image.
105
106config FIT_VERBOSE
107 bool "Show verbose messages when FIT images fail"
108 depends on FIT
109 help
110 Generally a system will have valid FIT images so debug messages
111 are a waste of code space. If you are debugging your images then
112 you can enable this option to get more verbose information about
113 failures.
114
115config FIT_BEST_MATCH
116 bool "Select the best match for the kernel device tree"
117 depends on FIT
118 help
119 When no configuration is explicitly selected, default to the
120 one whose fdt's compatibility field best matches that of
121 U-Boot itself. A match is considered "best" if it matches the
122 most specific compatibility entry of U-Boot's fdt's root node.
123 The order of entries in the configuration's fdt is ignored.
124
125config FIT_IMAGE_POST_PROCESS
126 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
127 depends on FIT
128 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
129 default y if TI_SECURE_DEVICE
130 help
131 Allows doing any sort of manipulation to blobs after they got extracted
132 from FIT images like stripping off headers or modifying the size of the
133 blob, verification, authentication, decryption etc. in a platform or
134 board specific way. In order to use this feature a platform or board-
135 specific implementation of board_fit_image_post_process() must be
136 provided. Also, anything done during this post-processing step would
137 need to be comprehended in how the images were prepared before being
138 injected into the FIT creation (i.e. the blobs would have been pre-
139 processed before being added to the FIT image).
140
141config FIT_PRINT
142 bool "Support FIT printing"
143 depends on FIT
144 default y
145 help
146 Support printing the content of the fitImage in a verbose manner.
147
148config SPL_FIT
149 bool "Support Flattened Image Tree within SPL"
150 depends on SPL && FIT
151 select SPL_HASH
152 select SPL_OF_LIBFDT
153
154config SPL_FIT_PRINT
155 bool "Support FIT printing within SPL"
156 depends on SPL_FIT
157 help
158 Support printing the content of the fitImage in a verbose manner in SPL.
159
160config SPL_FIT_FULL_CHECK
161 bool "Do a full check of the FIT before using it"
162 depends on SPL_FIT
163 help
164 Enable this do a full check of the FIT to make sure it is valid. This
165 helps to protect against carefully crafted FITs which take advantage
166 of bugs or omissions in the code. This includes a bad structure,
167 multiple root nodes and the like.
168
169config SPL_FIT_SIGNATURE
170 bool "Enable signature verification of FIT firmware within SPL"
171 depends on SPL_DM
172 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
173 select FIT_SIGNATURE
174 select SPL_FIT
175 select SPL_CRYPTO
176 select SPL_HASH
177 imply SPL_RSA
178 imply SPL_RSA_VERIFY
179 select SPL_IMAGE_SIGN_INFO
180 select SPL_FIT_FULL_CHECK
181
182config SPL_FIT_SIGNATURE_MAX_SIZE
183 hex "Max size of signed FIT structures in SPL"
184 depends on SPL_FIT_SIGNATURE
185 default 0x10000000
186 help
187 This option sets a max size in bytes for verified FIT uImages.
188 A sane value of 256MB protects corrupted DTB structures from overlapping
189 device memory. Assure this size does not extend past expected storage
190 space.
191
192config SPL_FIT_RSASSA_PSS
193 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
194 depends on SPL_FIT_SIGNATURE
195 help
196 Enable this to support the pss padding algorithm as described
197 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
198
199config SPL_LOAD_FIT
200 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
201 depends on SPL && FIT
202 select SPL_FIT
203 help
204 Normally with the SPL framework a legacy image is generated as part
205 of the build. This contains U-Boot along with information as to
206 where it should be loaded. This option instead enables generation
207 of a FIT (Flat Image Tree) which provides more flexibility. In
208 particular it can handle selecting from multiple device tree
209 and passing the correct one to U-Boot.
210
211 This path has the following limitations:
212
213 1. "loadables" images, other than FDTs, which do not have a "load"
214 property will not be loaded. This limitation also applies to FPGA
215 images with the correct "compatible" string.
216 2. For FPGA images, the supported "compatible" list is in the
217 doc/uImage.FIT/source_file_format.txt.
218 3. FDTs are only loaded for images with an "os" property of "u-boot".
219 "linux" images are also supported with Falcon boot mode.
220
221config SPL_LOAD_FIT_ADDRESS
222 hex "load address of fit image"
223 depends on SPL_LOAD_FIT || SPL_RAM_SUPPORT || TPL_RAM_SUPPORT
224 default 0x0
225 help
226 Specify the load address of the fit image that will be loaded
227 by SPL.
228
229config SPL_LOAD_FIT_APPLY_OVERLAY
230 bool "Enable SPL applying DT overlays from FIT"
231 depends on SPL_LOAD_FIT
232 select OF_LIBFDT_OVERLAY
233 help
234 The device tree is loaded from the FIT image. Allow the SPL to
235 also load device-tree overlays from the FIT image an apply them
236 over the device tree.
237
238config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
239 depends on SPL_LOAD_FIT_APPLY_OVERLAY
240 default 0x10000
241 hex "size of temporary buffer used to load the overlays"
242 help
243 The size of the area where the overlays will be loaded and
244 uncompress. Must be at least as large as biggest overlay
245 (uncompressed)
246
247config SPL_LOAD_FIT_FULL
248 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
249 depends on FIT
250 select SPL_FIT
251 help
252 Normally with the SPL framework a legacy image is generated as part
253 of the build. This contains U-Boot along with information as to
254 where it should be loaded. This option instead enables generation
255 of a FIT (Flat Image Tree) which provides more flexibility. In
256 particular it can handle selecting from multiple device tree
257 and passing the correct one to U-Boot.
258
259config SPL_FIT_IMAGE_POST_PROCESS
260 bool "Enable post-processing of FIT artifacts after loading by the SPL"
261 depends on SPL_LOAD_FIT
262 default y if TI_SECURE_DEVICE
263 help
264 Allows doing any sort of manipulation to blobs after they got extracted
265 from the U-Boot FIT image like stripping off headers or modifying the
266 size of the blob, verification, authentication, decryption etc. in a
267 platform or board specific way. In order to use this feature a platform
268 or board-specific implementation of board_fit_image_post_process() must
269 be provided. Also, anything done during this post-processing step would
270 need to be comprehended in how the images were prepared before being
271 injected into the FIT creation (i.e. the blobs would have been pre-
272 processed before being added to the FIT image).
273
274config SPL_FIT_SOURCE
275 string ".its source file for U-Boot FIT image"
276 depends on SPL_FIT
277 help
278 Specifies a (platform specific) FIT source file to generate the
279 U-Boot FIT image. This could specify further image to load and/or
280 execute.
281
282config USE_SPL_FIT_GENERATOR
283 bool "Use a script to generate the .its script"
284 depends on SPL_FIT
285 default y if SPL_FIT && ARCH_ZYNQMP
286
287config SPL_FIT_GENERATOR
288 string ".its file generator script for U-Boot FIT image"
289 depends on USE_SPL_FIT_GENERATOR
290 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
291 help
292 Specifies a (platform specific) script file to generate the FIT
293 source file used to build the U-Boot FIT image file. This gets
294 passed a list of supported device tree file stub names to
295 include in the generated image.
296
297if VPL
298
299config VPL_FIT
300 bool "Support Flattened Image Tree within VPL"
301 depends on VPL
302 default y
303 select VPL_HASH
304 select VPL_OF_LIBFDT
305
306config VPL_FIT_PRINT
307 bool "Support FIT printing within VPL"
308 depends on VPL_FIT
309 default y
310 help
311 Support printing the content of the fitImage in a verbose manner in VPL.
312
313config VPL_FIT_FULL_CHECK
314 bool "Do a full check of the FIT before using it"
315 default y
316 help
317 Enable this do a full check of the FIT to make sure it is valid. This
318 helps to protect against carefully crafted FITs which take advantage
319 of bugs or omissions in the code. This includes a bad structure,
320 multiple root nodes and the like.
321
322config VPL_FIT_SIGNATURE
323 bool "Enable signature verification of FIT firmware within VPL"
324 depends on VPL_DM
325 default y
326 select FIT_SIGNATURE
327 select VPL_FIT
328 select VPL_CRYPTO
329 select VPL_HASH
330 imply VPL_RSA
331 imply VPL_RSA_VERIFY
332 select VPL_IMAGE_SIGN_INFO
333 select VPL_FIT_FULL_CHECK
334
335config VPL_FIT_SIGNATURE_MAX_SIZE
336 hex "Max size of signed FIT structures in VPL"
337 depends on VPL_FIT_SIGNATURE
338 default 0x10000000
339 help
340 This option sets a max size in bytes for verified FIT uImages.
341 A sane value of 256MB protects corrupted DTB structures from overlapping
342 device memory. Assure this size does not extend past expected storage
343 space.
344
345endif
346
347config PXE_UTILS
348 bool
349 select MENU
350 help
351 Utilities for parsing PXE file formats.
352
353config BOOT_DEFAULTS
354 bool
355 imply USE_BOOTCOMMAND
356 select CMD_ENV_EXISTS
357 select CMD_EXT2
358 select CMD_EXT4
359 select CMD_FAT
360 select CMD_FS_GENERIC
361 select CMD_PART if PARTITIONS
362 select CMD_DHCP if CMD_NET
363 select CMD_PING if CMD_NET
364 select CMD_PXE if CMD_NET
365 select SUPPORT_RAW_INITRD
366 select ENV_VARS_UBOOT_CONFIG
367 select CMD_BOOTI if ARM64
368 select CMD_BOOTZ if ARM && !ARM64
369 imply CMD_MII if NET
370 imply USB_STORAGE
371 imply EFI_PARTITION
372 imply ISO_PARTITION
373 help
374 These are not required but are commonly needed to support a good
375 selection of booting methods. Enable this to improve the capability
376 of U-Boot to boot various images. Currently much functionality is
377 tied to enabling the command that exercises it.
378
379config BOOTSTD
380 bool "Standard boot support"
381 default y
382 depends on DM && OF_CONTROL && BLK
383 help
384 U-Boot supports a standard way of locating something to boot,
385 typically an Operating System such as Linux, provided by a distro such
386 as Arch Linux or Debian. Enable this to support iterating through
387 available bootdevs and using bootmeths to find bootflows suitable for
388 booting.
389
390 Standard boot is not a standard way of booting, just a framework
391 within U-Boot for supporting all the different ways that exist.
392
393 Terminology:
394
395 - bootdev - a device which can hold a distro (e.g. MMC)
396 - bootmeth - a method to scan a bootdev to find bootflows (owned by
397 U-Boot)
398 - bootflow - a description of how to boot (owned by the distro)
399
400config SPL_BOOTSTD
401 bool "Standard boot support in SPL"
402 depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK
403 default y if VPL
404 help
405 This enables standard boot in SPL. This is neeeded so that VBE
406 (Verified Boot for Embedded) can be used, since it depends on standard
407 boot. It is enabled by default since the main purpose of VPL is to
408 handle the firmware part of VBE.
409
410config VPL_BOOTSTD
411 bool "Standard boot support in VPL"
412 depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK
413 default y
414 help
415 This enables standard boot in SPL. This is neeeded so that VBE
416 (Verified Boot for Embedded) can be used, since it depends on standard
417 boot. It is enabled by default since the main purpose of VPL is to
418 handle the firmware part of VBE.
419
420if BOOTSTD
421
422config BOOTSTD_FULL
423 bool "Enhanced features for standard boot"
424 default y if SANDBOX
425 help
426 This enables various useful features for standard boot, which are not
427 essential for operation:
428
429 - bootdev, bootmeth commands
430 - extra features in the bootflow command
431 - support for selecting the ordering of bootmeths ("bootmeth order")
432 - support for selecting the ordering of bootdevs using the devicetree
433 as well as the "boot_targets" environment variable
434
435config BOOTSTD_DEFAULTS
436 bool "Select some common defaults for standard boot"
437 depends on BOOTSTD
438 imply USE_BOOTCOMMAND
439 select BOOT_DEFAULTS
440 select BOOTMETH_DISTRO
441 help
442 These are not required but are commonly needed to support a good
443 selection of booting methods. Enable this to improve the capability
444 of U-Boot to boot various images.
445
446config BOOTSTD_BOOTCOMMAND
447 bool "Use bootstd to boot"
448 default y if !DISTRO_DEFAULTS
449 help
450 Enable this to select a default boot-command suitable for booting
451 with standard boot. This can be overridden by the board if needed,
452 but the default command should be enough for most boards which use
453 standard boot.
454
455 For now this is only selected if distro boot is NOT used, since
456 standard boot does not support all of the features of distro boot
457 yet.
458
459config BOOTMETH_GLOBAL
460 bool
461 help
462 Add support for global bootmeths. This feature is used by VBE and
463 EFI bootmgr, since they take full control over which bootdevs are
464 selected to boot.
465
466config BOOTMETH_EXTLINUX
467 bool "Bootdev support for extlinux boot"
468 select PXE_UTILS
469 default y
470 help
471 Enables support for extlinux boot using bootdevs. This makes the
472 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
473 they scan.
474
475 The specification for this filed is here:
476
477 https://uapi-group.org/specifications/specs/boot_loader_specification/
478
479 This provides a way to try out standard boot on an existing boot flow.
480
481config BOOTMETH_EXTLINUX_PXE
482 bool "Bootdev support for extlinux boot over network"
483 depends on CMD_PXE && CMD_NET && DM_ETH
484 default y
485 help
486 Enables support for extlinux boot using bootdevs. This makes the
487 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
488
489 The specification for this file is here:
490
491 https://uapi-group.org/specifications/specs/boot_loader_specification/
492
493 This provides a way to try out standard boot on an existing boot flow.
494
495config BOOTMETH_EFILOADER
496 bool "Bootdev support for EFI boot"
497 depends on EFI_LOADER
498 default y
499 help
500 Enables support for EFI boot using bootdevs. This makes the
501 bootdevs look for a 'boot<arch>.efi' on each filesystem
502 they scan. The resulting file is booted after enabling U-Boot's
503 EFI loader support.
504
505 The <arch> depends on the architecture of the board:
506
507 aa64 - aarch64 (ARM 64-bit)
508 arm - ARM 32-bit
509 ia32 - x86 32-bit
510 x64 - x86 64-bit
511 riscv32 - RISC-V 32-bit
512 riscv64 - RISC-V 64-bit
513
514 This provides a way to try out standard boot on an existing boot flow.
515
516config BOOTMETH_VBE
517 bool "Bootdev support for Verified Boot for Embedded"
518 depends on FIT
519 default y
520 select BOOTMETH_GLOBAL
521 select EVENT
522 help
523 Enables support for VBE boot. This is a standard boot method which
524 supports selection of various firmware components, seleciton of an OS to
525 boot as well as updating these using fwupd.
526
527config BOOTMETH_DISTRO
528 bool
529 select BOOTMETH_SCRIPT
530 select BOOTMETH_EXTLINUX
531 select BOOTMETH_EXTLINUX_PXE if CMD_PXE && CMD_NET && DM_ETH
532 select BOOTMETH_EFILOADER if EFI_LOADER
533
534config SPL_BOOTMETH_VBE
535 bool "Bootdev support for Verified Boot for Embedded (SPL)"
536 depends on SPL && FIT
537 select EVENT
538 default y if VPL
539 help
540 Enables support for VBE boot. This is a standard boot method which
541 supports selection of various firmware components, seleciton of an OS to
542 boot as well as updating these using fwupd.
543
544config VPL_BOOTMETH_VBE
545 bool "Bootdev support for Verified Boot for Embedded (VPL)"
546 depends on VPL && FIT
547 select EVENT
548 default y
549 help
550 Enables support for VBE boot. This is a standard boot method which
551 supports selection of various firmware components, seleciton of an OS to
552 boot as well as updating these using fwupd.
553
554if BOOTMETH_VBE
555
556config BOOTMETH_VBE_REQUEST
557 bool "Support for serving VBE OS requests"
558 default y
559 help
560 Enables support for looking that the requests made by the
561 Operating System being booted. These requests result in additions to
562 the device tree /chosen node, added during the device tree fixup
563 phase.
564
565config SPL_BOOTMETH_VBE_REQUEST
566 bool "Support for serving VBE OS requests (SPL)"
567 depends on SPL
568 help
569 Enables support for looking that the requests made by the
570 Operating System being booted. These requests result in additions to
571 the device tree /chosen node, added during the device tree fixup
572 phase.
573
574 This is only useful if you are booting an OS direct from SPL.
575
576config BOOTMETH_VBE_SIMPLE
577 bool "Bootdev support for VBE 'simple' method"
578 default y
579 help
580 Enables support for VBE 'simple' boot. This allows updating a single
581 firmware image in boot media such as MMC. It does not support any sort
582 of rollback, recovery or A/B boot.
583
584config BOOTMETH_VBE_SIMPLE_OS
585 bool "Bootdev support for VBE 'simple' method OS phase"
586 default y
587 help
588 Enables support for the OS parts of VBE 'simple' boot. This includes
589 fixing up the device tree with the required VBE information, ready
590 for booting into the OS. This option is only enabled for U-Boot
591 proper, since it is the phase where device tree fixups happen.
592
593config SPL_BOOTMETH_VBE_SIMPLE
594 bool "Bootdev support for VBE 'simple' method (SPL)"
595 depends on SPL
596 default y if VPL
597 help
598 Enables support for VBE 'simple' boot. This allows updating a single
599 firmware image in boot media such as MMC. It does not support any sort
600 of rollback, recovery or A/B boot.
601
602config VPL_BOOTMETH_VBE_SIMPLE
603 bool "Bootdev support for VBE 'simple' method (VPL)"
604 depends on VPL
605 default y
606 help
607 Enables support for VBE 'simple' boot. This allows updating a single
608 firmware image in boot media such as MMC. It does not support any sort
609 of rollback, recovery or A/B boot.
610
611config SPL_BOOTMETH_VBE_SIMPLE_FW
612 bool "Bootdev support for VBE 'simple' method firmware phase (SPL)"
613 depends on VPL
614 default y
615 help
616 Enables support for the firmware parts of VBE 'simple' boot. This
617 includes an SPL loader which locates the correct U-Boot to boot into.
618 This option should really only be enabled for VPL, since it is the
619 phase where the SPL + U-Boot decision should be made. But for now,
620 SPL does its own FIT-configuration selection.
621
622config VPL_BOOTMETH_VBE_SIMPLE_FW
623 bool "Bootdev support for VBE 'simple' method firmware phase (VPL)"
624 depends on VPL
625 default y
626 help
627 Enables support for the firmware parts of VBE 'simple' boot. This
628 includes an SPL loader which locates the correct SPL to boot into.
629 This option enabled for VPL, since it is the phase where the SPL
630 decision is made.
631
632endif
633
634config EXPO
635 bool "Support for expos - groups of scenes displaying a UI"
636 depends on VIDEO
637 default y if BOOTMETH_VBE
638 help
639 An expo is a way of presenting and collecting information from the
640 user. It consists of a collection of 'scenes' of which only one is
641 presented at a time. An expo is typically used to show a boot menu
642 and allow settings to be changed.
643
644 The expo can be presented in graphics form using a vidconsole, or in
645 text form on a serial console.
646
647config BOOTMETH_SANDBOX
648 def_bool y
649 depends on SANDBOX
650 help
651 This is a sandbox bootmeth driver used for testing. It always returns
652 -ENOTSUPP when attempting to boot.
653
654config BOOTMETH_SCRIPT
655 bool "Bootdev support for U-Boot scripts"
656 default y if BOOTSTD_FULL
657 select HUSH_PARSER
658 help
659 Enables support for booting a distro via a U-Boot script. This makes
660 the bootdevs look for a 'boot/boot.scr' file which can be used to
661 boot the distro.
662
663 This provides a way to try out standard boot on an existing boot flow.
664 It is not enabled by default to save space.
665
666endif
667
668config LEGACY_IMAGE_FORMAT
669 bool "Enable support for the legacy image format"
670 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
671 help
672 This option enables the legacy image format. It is enabled by
673 default for backward compatibility, unless FIT_SIGNATURE is
674 set where it is disabled so that unsigned images cannot be
675 loaded. If a board needs the legacy image format support in this
676 case, enable it here.
677
678config SUPPORT_RAW_INITRD
679 bool "Enable raw initrd images"
680 help
681 Note, defining the SUPPORT_RAW_INITRD allows user to supply
682 kernel with raw initrd images. The syntax is slightly different, the
683 address of the initrd must be augmented by it's size, in the following
684 format: "<initrd address>:<initrd size>".
685
686config OF_BOARD_SETUP
687 bool "Set up board-specific details in device tree before boot"
688 depends on OF_LIBFDT
689 help
690 This causes U-Boot to call ft_board_setup() before booting into
691 the Operating System. This function can set up various
692 board-specific information in the device tree for use by the OS.
693 The device tree is then passed to the OS.
694
695config OF_SYSTEM_SETUP
696 bool "Set up system-specific details in device tree before boot"
697 depends on OF_LIBFDT
698 help
699 This causes U-Boot to call ft_system_setup() before booting into
700 the Operating System. This function can set up various
701 system-specific information in the device tree for use by the OS.
702 The device tree is then passed to the OS.
703
704config OF_STDOUT_VIA_ALIAS
705 bool "Update the device-tree stdout alias from U-Boot"
706 depends on OF_LIBFDT
707 help
708 This uses U-Boot's serial alias from the aliases node to update
709 the device tree passed to the OS. The "linux,stdout-path" property
710 in the chosen node is set to point to the correct serial node.
711 This option currently references CONFIG_CONS_INDEX, which is
712 incorrect when used with device tree as this option does not
713 exist / should not be used.
714
715config HAVE_TEXT_BASE
716 bool
717 depends on !NIOS2 && !XTENSA
718 depends on !EFI_APP
719 default y
720
721config TEXT_BASE
722 depends on HAVE_TEXT_BASE
723 default 0x0 if POSITION_INDEPENDENT
724 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
725 default 0x81700000 if MACH_SUNIV
726 default 0x2a000000 if MACH_SUN9I
727 default 0x4a000000 if SUNXI_MINIMUM_DRAM_MB >= 256
728 default 0x42e00000 if SUNXI_MINIMUM_DRAM_MB >= 64
729 hex "Text Base"
730 help
731 The address in memory that U-Boot will be running from, initially.
732
733config HAVE_SYS_MONITOR_BASE
734 bool
735 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
736 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
737 depends on !EFI_APP
738 default y
739
740config SYS_MONITOR_BASE
741 depends on HAVE_SYS_MONITOR_BASE
742 hex "Physical start address of boot monitor code"
743 default TEXT_BASE
744 help
745 The physical start address of boot monitor code (which is the same as
746 CONFIG_TEXT_BASE when linking) and the same as CFG_SYS_FLASH_BASE
747 when booting from flash.
748
749config SPL_SYS_MONITOR_BASE
750 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
751 hex "Physical start address of SPL monitor code"
752 default SPL_TEXT_BASE
753
754config TPL_SYS_MONITOR_BASE
755 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
756 hex "Physical start address of TPL monitor code"
757
758config DYNAMIC_SYS_CLK_FREQ
759 bool "Determine CPU clock frequency at run-time"
760 help
761 Implement a get_board_sys_clk function that will determine the CPU
762 clock frequency at run time, rather than define it statically.
763
764config SYS_CLK_FREQ
765 depends on !DYNAMIC_SYS_CLK_FREQ
766 int "CPU clock frequency"
767 default 125000000 if ARCH_LS1012A
768 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
769 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
770 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
771 default 66660000 if ARCH_T2080
772 default 33333333 if RCAR_GEN3
773 default 24000000 if ARCH_EXYNOS
774 default 20000000 if RCAR_GEN2
775 default 0
776 help
777 A static value for the CPU frequency. Note that if not required
778 for a given SoC, this can be left at 0.
779
780config ARCH_FIXUP_FDT_MEMORY
781 bool "Enable arch_fixup_memory_banks() call"
782 default y
783 help
784 Enable FDT memory map syncup before OS boot. This feature can be
785 used for booting OS with different memory setup where the part of
786 the memory location should be used for different purpose.
787
788config CHROMEOS
789 bool "Support booting Chrome OS"
790 help
791 Chrome OS requires U-Boot to set up a table indicating the boot mode
792 (e.g. Developer mode) and a few other things. Enable this if you are
793 booting on a Chromebook to avoid getting an error about an invalid
794 firmware ID.
795
796config CHROMEOS_VBOOT
797 bool "Support Chrome OS verified boot"
798 help
799 This is intended to enable the full Chrome OS verified boot support
800 in U-Boot. It is not actually implemented in the U-Boot source code
801 at present, so this option is always set to 'n'. It allows
802 distinguishing between booting Chrome OS in a basic way (developer
803 mode) and a full boot.
804
805config SYS_RAMBOOT
806 bool
807
808config RAMBOOT_PBL
809 bool "Freescale PBL(pre-boot loader) image format support"
810 select SYS_RAMBOOT if PPC
811 help
812 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
813 For more details refer to doc/README.pblimage
814
815choice
816 prompt "Freescale PBL (or predecessor) load location"
817 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
818 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
819 && !CMD_NAND)
820
821config SDCARD
822 bool "Freescale PBL (or similar) is found on SD card"
823
824config SPIFLASH
825 bool "Freescale PBL (or similar) is found on SPI flash"
826
827config NO_PBL
828 bool "Freescale PBL (or similar) is not used in this case"
829
830endchoice
831
832config FSL_FIXED_MMC_LOCATION
833 bool "PBL MMC is at a fixed location"
834 depends on SDCARD && !RAMBOOT_PBL
835
836config ESDHC_HC_BLK_ADDR
837 def_bool y
838 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
839 help
840 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
841 code length of these soc specify the memory address in block address
842 format. Block length is fixed to 512 bytes as per the SD High
843 Capacity specification.
844
845config SYS_FSL_PBL_PBI
846 string "PBI(pre-boot instructions) commands for the PBL image"
847 depends on RAMBOOT_PBL
848 help
849 PBI commands can be used to configure SoC before it starts the execution.
850 Please refer doc/README.pblimage for more details.
851
852config SYS_FSL_PBL_RCW
853 string "Aadditional RCW (Power on reset configuration) for the PBL image"
854 depends on RAMBOOT_PBL
855 help
856 Enables addition of RCW (Power on reset configuration) in built image.
857 Please refer doc/README.pblimage for more details.
858
859config SYS_BOOT_RAMDISK_HIGH
860 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
861 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
862 def_bool y
863 select LMB
864 help
865 Enable initrd_high functionality. If defined then the initrd_high
866 feature is enabled and the boot* ramdisk subcommand is enabled.
867
868endmenu
869
870config DISTRO_DEFAULTS
871 bool "Select defaults suitable for booting general purpose Linux distributions"
872 select BOOT_DEFAULTS
873 select AUTO_COMPLETE
874 select CMDLINE_EDITING
875 select CMD_SYSBOOT
876 select HUSH_PARSER
877 select SYS_LONGHELP
878 help
879 Select this to enable various options and commands which are suitable
880 for building u-boot for booting general purpose Linux distributions.
881
882menu "Boot timing"
883
884config BOOTSTAGE
885 bool "Boot timing and reporting"
886 help
887 Enable recording of boot time while booting. To use it, insert
888 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
889 bootstage.h. Only a single entry is recorded for each ID. You can
890 give the entry a name with bootstage_mark_name(). You can also
891 record elapsed time in a particular stage using bootstage_start()
892 before starting and bootstage_accum() when finished. Bootstage will
893 add up all the accumulated time and report it.
894
895 Normally, IDs are defined in bootstage.h but a small number of
896 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
897 as the ID.
898
899 Calls to show_boot_progress() will also result in log entries but
900 these will not have names.
901
902config SPL_BOOTSTAGE
903 bool "Boot timing and reported in SPL"
904 depends on BOOTSTAGE && SPL
905 help
906 Enable recording of boot time in SPL. To make this visible to U-Boot
907 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
908 information when SPL finishes and load it when U-Boot proper starts
909 up.
910
911config TPL_BOOTSTAGE
912 bool "Boot timing and reported in TPL"
913 depends on BOOTSTAGE && TPL
914 help
915 Enable recording of boot time in SPL. To make this visible to U-Boot
916 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
917 information when TPL finishes and load it when U-Boot proper starts
918 up.
919
920config BOOTSTAGE_REPORT
921 bool "Display a detailed boot timing report before booting the OS"
922 depends on BOOTSTAGE
923 help
924 Enable output of a boot time report just before the OS is booted.
925 This shows how long it took U-Boot to go through each stage of the
926 boot process. The report looks something like this:
927
928 Timer summary in microseconds:
929 Mark Elapsed Stage
930 0 0 reset
931 3,575,678 3,575,678 board_init_f start
932 3,575,695 17 arch_cpu_init A9
933 3,575,777 82 arch_cpu_init done
934 3,659,598 83,821 board_init_r start
935 3,910,375 250,777 main_loop
936 29,916,167 26,005,792 bootm_start
937 30,361,327 445,160 start_kernel
938
939config BOOTSTAGE_RECORD_COUNT
940 int "Number of boot stage records to store"
941 depends on BOOTSTAGE
942 default 30
943 help
944 This is the size of the bootstage record list and is the maximum
945 number of bootstage records that can be recorded.
946
947config SPL_BOOTSTAGE_RECORD_COUNT
948 int "Number of boot stage records to store for SPL"
949 depends on SPL_BOOTSTAGE
950 default 5
951 help
952 This is the size of the bootstage record list and is the maximum
953 number of bootstage records that can be recorded.
954
955config TPL_BOOTSTAGE_RECORD_COUNT
956 int "Number of boot stage records to store for TPL"
957 depends on TPL_BOOTSTAGE
958 default 5
959 help
960 This is the size of the bootstage record list and is the maximum
961 number of bootstage records that can be recorded.
962
963config BOOTSTAGE_FDT
964 bool "Store boot timing information in the OS device tree"
965 depends on BOOTSTAGE
966 help
967 Stash the bootstage information in the FDT. A root 'bootstage'
968 node is created with each bootstage id as a child. Each child
969 has a 'name' property and either 'mark' containing the
970 mark time in microseconds, or 'accum' containing the
971 accumulated time for that bootstage id in microseconds.
972 For example:
973
974 bootstage {
975 154 {
976 name = "board_init_f";
977 mark = <3575678>;
978 };
979 170 {
980 name = "lcd";
981 accum = <33482>;
982 };
983 };
984
985 Code in the Linux kernel can find this in /proc/devicetree.
986
987config BOOTSTAGE_STASH
988 bool "Stash the boot timing information in memory before booting OS"
989 depends on BOOTSTAGE
990 help
991 Some OSes do not support device tree. Bootstage can instead write
992 the boot timing information in a binary format at a given address.
993 This happens through a call to bootstage_stash(), typically in
994 the CPU's cleanup_before_linux() function. You can use the
995 'bootstage stash' and 'bootstage unstash' commands to do this on
996 the command line.
997
998config BOOTSTAGE_STASH_ADDR
999 hex "Address to stash boot timing information"
1000 default 0
1001 help
1002 Provide an address which will not be overwritten by the OS when it
1003 starts, so that it can read this information when ready.
1004
1005config BOOTSTAGE_STASH_SIZE
1006 hex "Size of boot timing stash region"
1007 default 0x1000
1008 help
1009 This should be large enough to hold the bootstage stash. A value of
1010 4096 (4KiB) is normally plenty.
1011
1012config SHOW_BOOT_PROGRESS
1013 bool "Show boot progress in a board-specific manner"
1014 help
1015 Defining this option allows to add some board-specific code (calling
1016 a user-provided function show_boot_progress(int) that enables you to
1017 show the system's boot progress on some display (for example, some
1018 LEDs) on your board. At the moment, the following checkpoints are
1019 implemented:
1020
1021 Legacy uImage format:
1022
1023 Arg Where When
1024 1 common/cmd_bootm.c before attempting to boot an image
1025 -1 common/cmd_bootm.c Image header has bad magic number
1026 2 common/cmd_bootm.c Image header has correct magic number
1027 -2 common/cmd_bootm.c Image header has bad checksum
1028 3 common/cmd_bootm.c Image header has correct checksum
1029 -3 common/cmd_bootm.c Image data has bad checksum
1030 4 common/cmd_bootm.c Image data has correct checksum
1031 -4 common/cmd_bootm.c Image is for unsupported architecture
1032 5 common/cmd_bootm.c Architecture check OK
1033 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
1034 6 common/cmd_bootm.c Image Type check OK
1035 -6 common/cmd_bootm.c gunzip uncompression error
1036 -7 common/cmd_bootm.c Unimplemented compression type
1037 7 common/cmd_bootm.c Uncompression OK
1038 8 common/cmd_bootm.c No uncompress/copy overwrite error
1039 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
1040
1041 9 common/image.c Start initial ramdisk verification
1042 -10 common/image.c Ramdisk header has bad magic number
1043 -11 common/image.c Ramdisk header has bad checksum
1044 10 common/image.c Ramdisk header is OK
1045 -12 common/image.c Ramdisk data has bad checksum
1046 11 common/image.c Ramdisk data has correct checksum
1047 12 common/image.c Ramdisk verification complete, start loading
1048 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
1049 13 common/image.c Start multifile image verification
1050 14 common/image.c No initial ramdisk, no multifile, continue.
1051
1052 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
1053
1054 -30 arch/powerpc/lib/board.c Fatal error, hang the system
1055 -31 post/post.c POST test failed, detected by post_output_backlog()
1056 -32 post/post.c POST test failed, detected by post_run_single()
1057
1058 34 common/cmd_doc.c before loading a Image from a DOC device
1059 -35 common/cmd_doc.c Bad usage of "doc" command
1060 35 common/cmd_doc.c correct usage of "doc" command
1061 -36 common/cmd_doc.c No boot device
1062 36 common/cmd_doc.c correct boot device
1063 -37 common/cmd_doc.c Unknown Chip ID on boot device
1064 37 common/cmd_doc.c correct chip ID found, device available
1065 -38 common/cmd_doc.c Read Error on boot device
1066 38 common/cmd_doc.c reading Image header from DOC device OK
1067 -39 common/cmd_doc.c Image header has bad magic number
1068 39 common/cmd_doc.c Image header has correct magic number
1069 -40 common/cmd_doc.c Error reading Image from DOC device
1070 40 common/cmd_doc.c Image header has correct magic number
1071 41 common/cmd_ide.c before loading a Image from a IDE device
1072 -42 common/cmd_ide.c Bad usage of "ide" command
1073 42 common/cmd_ide.c correct usage of "ide" command
1074 -43 common/cmd_ide.c No boot device
1075 43 common/cmd_ide.c boot device found
1076 -44 common/cmd_ide.c Device not available
1077 44 common/cmd_ide.c Device available
1078 -45 common/cmd_ide.c wrong partition selected
1079 45 common/cmd_ide.c partition selected
1080 -46 common/cmd_ide.c Unknown partition table
1081 46 common/cmd_ide.c valid partition table found
1082 -47 common/cmd_ide.c Invalid partition type
1083 47 common/cmd_ide.c correct partition type
1084 -48 common/cmd_ide.c Error reading Image Header on boot device
1085 48 common/cmd_ide.c reading Image Header from IDE device OK
1086 -49 common/cmd_ide.c Image header has bad magic number
1087 49 common/cmd_ide.c Image header has correct magic number
1088 -50 common/cmd_ide.c Image header has bad checksum
1089 50 common/cmd_ide.c Image header has correct checksum
1090 -51 common/cmd_ide.c Error reading Image from IDE device
1091 51 common/cmd_ide.c reading Image from IDE device OK
1092 52 common/cmd_nand.c before loading a Image from a NAND device
1093 -53 common/cmd_nand.c Bad usage of "nand" command
1094 53 common/cmd_nand.c correct usage of "nand" command
1095 -54 common/cmd_nand.c No boot device
1096 54 common/cmd_nand.c boot device found
1097 -55 common/cmd_nand.c Unknown Chip ID on boot device
1098 55 common/cmd_nand.c correct chip ID found, device available
1099 -56 common/cmd_nand.c Error reading Image Header on boot device
1100 56 common/cmd_nand.c reading Image Header from NAND device OK
1101 -57 common/cmd_nand.c Image header has bad magic number
1102 57 common/cmd_nand.c Image header has correct magic number
1103 -58 common/cmd_nand.c Error reading Image from NAND device
1104 58 common/cmd_nand.c reading Image from NAND device OK
1105
1106 -60 common/env_common.c Environment has a bad CRC, using default
1107
1108 64 net/eth.c starting with Ethernet configuration.
1109 -64 net/eth.c no Ethernet found.
1110 65 net/eth.c Ethernet found.
1111
1112 -80 common/cmd_net.c usage wrong
1113 80 common/cmd_net.c before calling net_loop()
1114 -81 common/cmd_net.c some error in net_loop() occurred
1115 81 common/cmd_net.c net_loop() back without error
1116 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1117 82 common/cmd_net.c trying automatic boot
1118 83 common/cmd_net.c running "source" command
1119 -83 common/cmd_net.c some error in automatic boot or "source" command
1120 84 common/cmd_net.c end without errors
1121
1122 FIT uImage format:
1123
1124 Arg Where When
1125 100 common/cmd_bootm.c Kernel FIT Image has correct format
1126 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1127 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1128 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1129 102 common/cmd_bootm.c Kernel unit name specified
1130 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1131 103 common/cmd_bootm.c Found configuration node
1132 104 common/cmd_bootm.c Got kernel subimage node offset
1133 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1134 105 common/cmd_bootm.c Kernel subimage hash verification OK
1135 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1136 106 common/cmd_bootm.c Architecture check OK
1137 -106 common/cmd_bootm.c Kernel subimage has wrong type
1138 107 common/cmd_bootm.c Kernel subimage type OK
1139 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1140 108 common/cmd_bootm.c Got kernel subimage data/size
1141 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1142 -109 common/cmd_bootm.c Can't get kernel subimage type
1143 -110 common/cmd_bootm.c Can't get kernel subimage comp
1144 -111 common/cmd_bootm.c Can't get kernel subimage os
1145 -112 common/cmd_bootm.c Can't get kernel subimage load address
1146 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1147
1148 120 common/image.c Start initial ramdisk verification
1149 -120 common/image.c Ramdisk FIT image has incorrect format
1150 121 common/image.c Ramdisk FIT image has correct format
1151 122 common/image.c No ramdisk subimage unit name, using configuration
1152 -122 common/image.c Can't get configuration for ramdisk subimage
1153 123 common/image.c Ramdisk unit name specified
1154 -124 common/image.c Can't get ramdisk subimage node offset
1155 125 common/image.c Got ramdisk subimage node offset
1156 -125 common/image.c Ramdisk subimage hash verification failed
1157 126 common/image.c Ramdisk subimage hash verification OK
1158 -126 common/image.c Ramdisk subimage for unsupported architecture
1159 127 common/image.c Architecture check OK
1160 -127 common/image.c Can't get ramdisk subimage data/size
1161 128 common/image.c Got ramdisk subimage data/size
1162 129 common/image.c Can't get ramdisk load address
1163 -129 common/image.c Got ramdisk load address
1164
1165 -130 common/cmd_doc.c Incorrect FIT image format
1166 131 common/cmd_doc.c FIT image format OK
1167
1168 -140 common/cmd_ide.c Incorrect FIT image format
1169 141 common/cmd_ide.c FIT image format OK
1170
1171 -150 common/cmd_nand.c Incorrect FIT image format
1172 151 common/cmd_nand.c FIT image format OK
1173
1174config SPL_SHOW_BOOT_PROGRESS
1175 bool "Show boot progress in a board-specific manner in SPL"
1176 depends on SPL
1177 help
1178 Defining this option allows to add some board-specific code (calling
1179 a user-provided function show_boot_progress(int) that enables you to
1180 show the system's boot progress on some display (for example, some
1181 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1182
1183endmenu
1184
1185menu "Boot media"
1186
1187config NOR_BOOT
1188 bool "Support for booting from NOR flash"
1189 depends on NOR
1190 help
1191 Enabling this will make a U-Boot binary that is capable of being
1192 booted via NOR. In this case we will enable certain pinmux early
1193 as the ROM only partially sets up pinmux. We also default to using
1194 NOR for environment.
1195
1196config NAND_BOOT
1197 bool "Support for booting from NAND flash"
1198 imply MTD_RAW_NAND
1199 help
1200 Enabling this will make a U-Boot binary that is capable of being
1201 booted via NAND flash. This is not a must, some SoCs need this,
1202 some not.
1203
1204config ONENAND_BOOT
1205 bool "Support for booting from ONENAND"
1206 imply MTD_RAW_NAND
1207 help
1208 Enabling this will make a U-Boot binary that is capable of being
1209 booted via ONENAND. This is not a must, some SoCs need this,
1210 some not.
1211
1212config QSPI_BOOT
1213 bool "Support for booting from QSPI flash"
1214 help
1215 Enabling this will make a U-Boot binary that is capable of being
1216 booted via QSPI flash. This is not a must, some SoCs need this,
1217 some not.
1218
1219config SATA_BOOT
1220 bool "Support for booting from SATA"
1221 help
1222 Enabling this will make a U-Boot binary that is capable of being
1223 booted via SATA. This is not a must, some SoCs need this,
1224 some not.
1225
1226config SD_BOOT
1227 bool "Support for booting from SD/EMMC"
1228 help
1229 Enabling this will make a U-Boot binary that is capable of being
1230 booted via SD/EMMC. This is not a must, some SoCs need this,
1231 some not.
1232
1233config SD_BOOT_QSPI
1234 bool "Support for booting from SD/EMMC and enable QSPI"
1235 help
1236 Enabling this will make a U-Boot binary that is capable of being
1237 booted via SD/EMMC while enabling QSPI on the platform as well. This
1238 is not a must, some SoCs need this, some not.
1239
1240config SPI_BOOT
1241 bool "Support for booting from SPI flash"
1242 help
1243 Enabling this will make a U-Boot binary that is capable of being
1244 booted via SPI flash. This is not a must, some SoCs need this,
1245 some not.
1246
1247endmenu
1248
1249menu "Autoboot options"
1250
1251config AUTOBOOT
1252 bool "Autoboot"
1253 default y
1254 help
1255 This enables the autoboot. See doc/README.autoboot for detail.
1256
1257config BOOTDELAY
1258 int "delay in seconds before automatically booting"
1259 default 2
1260 depends on AUTOBOOT
1261 help
1262 Delay before automatically running bootcmd;
1263 set to 0 to autoboot with no delay, but you can stop it by key input.
1264 set to -1 to disable autoboot.
1265 set to -2 to autoboot with no delay and not check for abort
1266
1267 If this value is >= 0 then it is also used for the default delay
1268 before starting the default entry in bootmenu. If it is < 0 then
1269 a default value of 10s is used.
1270
1271 See doc/README.autoboot for details.
1272
1273config AUTOBOOT_KEYED
1274 bool "Stop autobooting via specific input key / string"
1275 help
1276 This option enables stopping (aborting) of the automatic
1277 boot feature only by issuing a specific input key or
1278 string. If not enabled, any input key will abort the
1279 U-Boot automatic booting process and bring the device
1280 to the U-Boot prompt for user input.
1281
1282config AUTOBOOT_FLUSH_STDIN
1283 bool "Enable flushing stdin before starting to read the password"
1284 depends on AUTOBOOT_KEYED && !SANDBOX
1285 help
1286 When this option is enabled stdin buffer will be flushed before
1287 starting to read the password.
1288 This can't be enabled for the sandbox as flushing stdin would
1289 break the autoboot unit tests.
1290
1291config AUTOBOOT_PROMPT
1292 string "Autoboot stop prompt"
1293 depends on AUTOBOOT_KEYED
1294 default "Autoboot in %d seconds\\n"
1295 help
1296 This string is displayed before the boot delay selected by
1297 CONFIG_BOOTDELAY starts. If it is not defined there is no
1298 output indicating that autoboot is in progress.
1299
1300 Note that this define is used as the (only) argument to a
1301 printf() call, so it may contain '%' format specifications,
1302 provided that it also includes, sepearated by commas exactly
1303 like in a printf statement, the required arguments. It is
1304 the responsibility of the user to select only such arguments
1305 that are valid in the given context.
1306
1307config AUTOBOOT_ENCRYPTION
1308 bool "Enable encryption in autoboot stopping"
1309 depends on AUTOBOOT_KEYED
1310 help
1311 This option allows a string to be entered into U-Boot to stop the
1312 autoboot.
1313 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1314 or not.
1315 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1316 to the crypt-based functionality and be compared against the
1317 string in the environment variable 'bootstopkeycrypt'.
1318 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1319 and compared against the hash in the environment variable
1320 'bootstopkeysha256'.
1321 If it matches in either case then boot stops and
1322 a command-line prompt is presented.
1323 This provides a way to ship a secure production device which can also
1324 be accessed at the U-Boot command line.
1325
1326config AUTOBOOT_SHA256_FALLBACK
1327 bool "Allow fallback from crypt-hashed password to sha256"
1328 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1329 help
1330 This option adds support to fall back from crypt-hashed
1331 passwords to checking a SHA256 hashed password in case the
1332 'bootstopusesha256' environment variable is set to 'true'.
1333
1334config AUTOBOOT_DELAY_STR
1335 string "Delay autobooting via specific input key / string"
1336 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1337 help
1338 This option delays the automatic boot feature by issuing
1339 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1340 or the environment variable "bootdelaykey" is specified
1341 and this string is received from console input before
1342 autoboot starts booting, U-Boot gives a command prompt. The
1343 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1344 used, otherwise it never times out.
1345
1346config AUTOBOOT_STOP_STR
1347 string "Stop autobooting via specific input key / string"
1348 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1349 help
1350 This option enables stopping (aborting) of the automatic
1351 boot feature only by issuing a specific input key or
1352 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1353 variable "bootstopkey" is specified and this string is
1354 received from console input before autoboot starts booting,
1355 U-Boot gives a command prompt. The U-Boot prompt never
1356 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1357
1358config AUTOBOOT_KEYED_CTRLC
1359 bool "Enable Ctrl-C autoboot interruption"
1360 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1361 help
1362 This option allows for the boot sequence to be interrupted
1363 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1364 Setting this variable provides an escape sequence from the
1365 limited "password" strings.
1366
1367config AUTOBOOT_NEVER_TIMEOUT
1368 bool "Make the password entry never time-out"
1369 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1370 help
1371 This option removes the timeout from the password entry
1372 when the user first presses the <Enter> key before entering
1373 any other character.
1374
1375config AUTOBOOT_STOP_STR_ENABLE
1376 bool "Enable fixed string to stop autobooting"
1377 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1378 help
1379 This option enables the feature to add a fixed stop
1380 string that is defined at compile time.
1381 In every case it will be tried to load the stop
1382 string from the environment.
1383 In case this is enabled and there is no stop string
1384 in the environment, this will be used as default value.
1385
1386config AUTOBOOT_STOP_STR_CRYPT
1387 string "Stop autobooting via crypt-hashed password"
1388 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1389 help
1390 This option adds the feature to only stop the autobooting,
1391 and therefore boot into the U-Boot prompt, when the input
1392 string / password matches a values that is hashed via
1393 one of the supported crypt-style password hashing options
1394 and saved in the environment variable "bootstopkeycrypt".
1395
1396config AUTOBOOT_STOP_STR_SHA256
1397 string "Stop autobooting via SHA256 hashed password"
1398 depends on AUTOBOOT_STOP_STR_ENABLE
1399 help
1400 This option adds the feature to only stop the autobooting,
1401 and therefore boot into the U-Boot prompt, when the input
1402 string / password matches a values that is encypted via
1403 a SHA256 hash and saved in the environment variable
1404 "bootstopkeysha256". If the value in that variable
1405 includes a ":", the portion prior to the ":" will be treated
1406 as a salt value.
1407
1408config AUTOBOOT_USE_MENUKEY
1409 bool "Allow a specify key to run a menu from the environment"
1410 depends on !AUTOBOOT_KEYED
1411 help
1412 If a specific key is pressed to stop autoboot, then the commands in
1413 the environment variable 'menucmd' are executed before boot starts.
1414
1415config AUTOBOOT_MENUKEY
1416 int "ASCII value of boot key to show a menu"
1417 default 0
1418 depends on AUTOBOOT_USE_MENUKEY
1419 help
1420 If this key is pressed to stop autoboot, then the commands in the
1421 environment variable 'menucmd' will be executed before boot starts.
1422 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1423 this action.
1424
1425config AUTOBOOT_MENU_SHOW
1426 bool "Show a menu on boot"
1427 depends on CMD_BOOTMENU
1428 help
1429 This enables the boot menu, controlled by environment variables
1430 defined by the board. The menu starts after running the 'preboot'
1431 environmnent variable (if enabled) and before handling the boot delay.
1432 See README.bootmenu for more details.
1433
1434config BOOTMENU_DISABLE_UBOOT_CONSOLE
1435 bool "Disallow bootmenu to enter the U-Boot console"
1436 depends on AUTOBOOT_MENU_SHOW
1437 help
1438 If this option is enabled, user can not enter the U-Boot console from
1439 bootmenu. It increases the system security.
1440
1441config BOOT_RETRY
1442 bool "Boot retry feature"
1443 help
1444 Allow for having the U-Boot command prompt time out and attempt
1445 to boot again. If the environment variable "bootretry" is found then
1446 its value is used, otherwise the retry timeout is
1447 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1448 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1449
1450config BOOT_RETRY_TIME
1451 int "Timeout in seconds before attempting to boot again"
1452 depends on BOOT_RETRY
1453 help
1454 Time in seconds before the U-Boot prompt will timeout and boot will
1455 be attempted again.
1456
1457config BOOT_RETRY_MIN
1458 int "Minimum timeout in seconds for 'bootretry'"
1459 depends on BOOT_RETRY
1460 default BOOT_RETRY_TIME
1461 help
1462 The minimum time in seconds that "bootretry" can be set to.
1463
1464config RESET_TO_RETRY
1465 bool "Reset the board to retry autoboot"
1466 depends on BOOT_RETRY
1467 help
1468 After the countdown timed out, the board will be reset to restart
1469 again.
1470
1471endmenu
1472
1473menu "Image support"
1474
1475config IMAGE_PRE_LOAD
1476 bool "Image pre-load support"
1477 help
1478 Enable an image pre-load stage in the SPL.
1479 This pre-load stage allows to do some manipulation
1480 or check (for example signature check) on an image
1481 before launching it.
1482
1483config SPL_IMAGE_PRE_LOAD
1484 bool "Image pre-load support within SPL"
1485 depends on SPL && IMAGE_PRE_LOAD
1486 help
1487 Enable an image pre-load stage in the SPL.
1488 This pre-load stage allows to do some manipulation
1489 or check (for example signature check) on an image
1490 before launching it.
1491
1492config IMAGE_PRE_LOAD_SIG
1493 bool "Image pre-load signature support"
1494 depends on IMAGE_PRE_LOAD
1495 select FIT_SIGNATURE
1496 select RSA
1497 select RSA_VERIFY_WITH_PKEY
1498 help
1499 Enable signature check support in the pre-load stage.
1500 For this feature a very simple header is added before
1501 the image with few fields:
1502 - a magic
1503 - the image size
1504 - the signature
1505 All other information (header size, type of signature,
1506 ...) are provided in the node /image/pre-load/sig of
1507 u-boot.
1508
1509config SPL_IMAGE_PRE_LOAD_SIG
1510 bool "Image pre-load signature support witin SPL"
1511 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1512 select SPL_FIT_SIGNATURE
1513 select SPL_RSA
1514 select SPL_RSA_VERIFY_WITH_PKEY
1515 help
1516 Enable signature check support in the pre-load stage in the SPL.
1517 For this feature a very simple header is added before
1518 the image with few fields:
1519 - a magic
1520 - the image size
1521 - the signature
1522 All other information (header size, type of signature,
1523 ...) are provided in the node /image/pre-load/sig of
1524 u-boot.
1525
1526endmenu
1527
1528config USE_BOOTARGS
1529 bool "Enable boot arguments"
1530 help
1531 Provide boot arguments to bootm command. Boot arguments are specified
1532 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1533 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1534 will be undefined and won't take any space in U-Boot image.
1535
1536config BOOTARGS
1537 string "Boot arguments"
1538 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1539 help
1540 This can be used to pass arguments to the bootm command. The value of
1541 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1542 this value will also override the "chosen" node in FDT blob.
1543
1544config BOOTARGS_SUBST
1545 bool "Support substituting strings in boot arguments"
1546 help
1547 This allows substituting string values in the boot arguments. These
1548 are applied after the commandline has been built.
1549
1550 One use for this is to insert the root-disk UUID into the command
1551 line where bootargs contains "root=${uuid}"
1552
1553 setenv bootargs "console= root=${uuid}"
1554 # Set the 'uuid' environment variable
1555 part uuid mmc 2:2 uuid
1556
1557 # Command-line substitution will put the real uuid into the
1558 # kernel command line
1559 bootm
1560
1561config USE_BOOTCOMMAND
1562 bool "Enable a default value for bootcmd"
1563 help
1564 Provide a default value for the bootcmd entry in the environment. If
1565 autoboot is enabled this is what will be run automatically. Enable
1566 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1567 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1568 won't take any space in U-Boot image.
1569
1570config BOOTCOMMAND
1571 string "bootcmd value"
1572 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
1573 default "bootflow scan -lb" if BOOTSTD_DEFAULTS && CMD_BOOTFLOW_FULL
1574 default "bootflow scan" if BOOTSTD_DEFAULTS && !CMD_BOOTFLOW_FULL
1575 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
1576 help
1577 This is the string of commands that will be used as bootcmd and if
1578 AUTOBOOT is set, automatically run.
1579
1580config USE_PREBOOT
1581 bool "Enable preboot"
1582 help
1583 When this option is enabled, the existence of the environment
1584 variable "preboot" will be checked immediately before starting the
1585 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1586 entering interactive mode.
1587
1588 This feature is especially useful when "preboot" is automatically
1589 generated or modified. For example, the boot code can modify the
1590 "preboot" when a user holds down a certain combination of keys.
1591
1592config PREBOOT
1593 string "preboot default value"
1594 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
1595 default "usb start" if USB_KEYBOARD
1596 default ""
1597 help
1598 This is the default of "preboot" environment variable.
1599
1600config PREBOOT_DEFINED
1601 bool
1602 default y if PREBOOT != ""
1603
1604config DEFAULT_FDT_FILE
1605 string "Default fdt file"
1606 help
1607 This option is used to set the default fdt file to boot OS.
1608
1609config SAVE_PREV_BL_FDT_ADDR
1610 depends on ARM
1611 bool "Saves fdt address, passed by the previous bootloader, to env var"
1612 help
1613 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1614 enable this option to save fdt address, passed by the
1615 previous bootloader for future use.
1616 Address is saved to `prevbl_fdt_addr` environment variable.
1617
1618 If no fdt was provided by previous bootloader, no env variables
1619 will be created.
1620
1621config SAVE_PREV_BL_INITRAMFS_START_ADDR
1622 depends on ARM
1623 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1624 help
1625 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1626 enable this option to save initramfs address, passed by the
1627 previous bootloader for future use.
1628 Address is saved to `prevbl_initrd_start_addr` environment variable.
1629
1630 If no initramfs was provided by previous bootloader, no env variables
1631 will be created.
1632
1633endmenu
1634
