blob: e0f09e21efd7eca08f9f57a730b8846b3c71744c [file] [log] [blame]
Simon Glasscf298162020-09-10 20:21:13 -06001menu "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"
Alexandru Gagniuc92055e12021-09-02 19:54:21 -050014 select HASH
Simon Glasscf298162020-09-10 20:21:13 -060015 select MD5
16 select SHA1
Alexandru Gagniuceb5171d2021-09-02 19:54:17 -050017 imply SHA256
Simon Glasscf298162020-09-10 20:21:13 -060018 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
Simon Glassd6b318d2021-12-18 11:27:50 -070028config 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
Simon Glasscf298162020-09-10 20:21:13 -060039if FIT
40
41config FIT_EXTERNAL_OFFSET
42 hex "FIT external data offset"
43 default 0x0
44 help
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.
50
Simon Glass6f3c2d82021-02-15 17:08:10 -070051config FIT_FULL_CHECK
52 bool "Do a full check of the FIT before using it"
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
Simon Glasscf298162020-09-10 20:21:13 -060060config FIT_SIGNATURE
61 bool "Enable signature verification of FIT uImages"
62 depends on DM
63 select HASH
Alexandru Gagniuc61416fe2021-07-29 11:47:18 -050064 imply RSA
65 imply RSA_VERIFY
Simon Glasscf298162020-09-10 20:21:13 -060066 select IMAGE_SIGN_INFO
Simon Glass6f3c2d82021-02-15 17:08:10 -070067 select FIT_FULL_CHECK
Simon Glasscf298162020-09-10 20:21:13 -060068 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
Simon Glassad74aed2021-07-14 17:05:31 -050091config FIT_RSASSA_PSS
Simon Glasscf298162020-09-10 20:21:13 -060092 bool "Support rsassa-pss signature scheme of FIT image contents"
93 depends on FIT_SIGNATURE
Simon Glasscf298162020-09-10 20:21:13 -060094 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
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 help
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
112 failures.
113
114config FIT_BEST_MATCH
115 bool "Select the best match for the kernel device tree"
116 help
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.
122
123config FIT_IMAGE_POST_PROCESS
124 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
Siew Chin Lim1bc20892021-03-01 20:04:11 +0800125 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
Andrew Davis042e87e2022-05-04 15:52:28 -0500126 default y if TI_SECURE_DEVICE
Simon Glasscf298162020-09-10 20:21:13 -0600127 help
128 Allows doing any sort of manipulation to blobs after they got extracted
129 from FIT images like stripping off headers or modifying the size of the
130 blob, verification, authentication, decryption etc. in a platform or
131 board specific way. In order to use this feature a platform or board-
132 specific implementation of board_fit_image_post_process() must be
133 provided. Also, anything done during this post-processing step would
134 need to be comprehended in how the images were prepared before being
135 injected into the FIT creation (i.e. the blobs would have been pre-
136 processed before being added to the FIT image).
137
Ravik Hasija7a018822021-01-27 14:01:48 -0800138config FIT_PRINT
139 bool "Support FIT printing"
140 default y
141 help
142 Support printing the content of the fitImage in a verbose manner.
143
Simon Glasscf298162020-09-10 20:21:13 -0600144if SPL
145
146config SPL_FIT
147 bool "Support Flattened Image Tree within SPL"
148 depends on SPL
Alexandru Gagniuc92055e12021-09-02 19:54:21 -0500149 select SPL_HASH
Simon Glasscf298162020-09-10 20:21:13 -0600150 select SPL_OF_LIBFDT
151
152config SPL_FIT_PRINT
153 bool "Support FIT printing within SPL"
154 depends on SPL_FIT
155 help
156 Support printing the content of the fitImage in a verbose manner in SPL.
157
Simon Glass6f3c2d82021-02-15 17:08:10 -0700158config SPL_FIT_FULL_CHECK
159 bool "Do a full check of the FIT before using it"
160 help
161 Enable this do a full check of the FIT to make sure it is valid. This
162 helps to protect against carefully crafted FITs which take advantage
163 of bugs or omissions in the code. This includes a bad structure,
164 multiple root nodes and the like.
165
166
Simon Glasscf298162020-09-10 20:21:13 -0600167config SPL_FIT_SIGNATURE
168 bool "Enable signature verification of FIT firmware within SPL"
169 depends on SPL_DM
Klaus Heinrich Kiwibdb7f262021-02-09 15:41:54 -0300170 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
Klaus Heinrich Kiwi6ce28132021-02-09 15:41:53 -0300171 select FIT_SIGNATURE
Simon Glasscf298162020-09-10 20:21:13 -0600172 select SPL_FIT
Simon Glass0c6bdbb2021-07-10 21:14:25 -0600173 select SPL_CRYPTO
Alexandru Gagniuc07212092021-09-02 19:54:19 -0500174 select SPL_HASH
Alexandru Gagniuc61416fe2021-07-29 11:47:18 -0500175 imply SPL_RSA
176 imply SPL_RSA_VERIFY
Simon Glasscf298162020-09-10 20:21:13 -0600177 select SPL_IMAGE_SIGN_INFO
Simon Glass6f3c2d82021-02-15 17:08:10 -0700178 select SPL_FIT_FULL_CHECK
Simon Glasscf298162020-09-10 20:21:13 -0600179
Simon Glassb53541f2021-09-25 19:43:39 -0600180config SPL_FIT_SIGNATURE_MAX_SIZE
181 hex "Max size of signed FIT structures in SPL"
182 depends on SPL_FIT_SIGNATURE
183 default 0x10000000
184 help
185 This option sets a max size in bytes for verified FIT uImages.
186 A sane value of 256MB protects corrupted DTB structures from overlapping
187 device memory. Assure this size does not extend past expected storage
188 space.
189
Philippe Reynes5d39c932021-10-15 11:35:03 +0200190config SPL_FIT_RSASSA_PSS
191 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
192 depends on SPL_FIT_SIGNATURE
193 help
194 Enable this to support the pss padding algorithm as described
195 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
196
Simon Glasscf298162020-09-10 20:21:13 -0600197config SPL_LOAD_FIT
198 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
199 select SPL_FIT
200 help
201 Normally with the SPL framework a legacy image is generated as part
202 of the build. This contains U-Boot along with information as to
203 where it should be loaded. This option instead enables generation
204 of a FIT (Flat Image Tree) which provides more flexibility. In
205 particular it can handle selecting from multiple device tree
206 and passing the correct one to U-Boot.
207
Alexandru Gagniucdf51ae72021-03-29 12:05:15 -0500208 This path has the following limitations:
209
Bin Meng6e847f62021-05-10 20:23:29 +0800210 1. "loadables" images, other than FDTs, which do not have a "load"
Alexandru Gagniucdf51ae72021-03-29 12:05:15 -0500211 property will not be loaded. This limitation also applies to FPGA
212 images with the correct "compatible" string.
Oleksandr Suvorova3a1afb2022-07-22 17:16:13 +0300213 2. For FPGA images, the supported "compatible" list is in the
214 doc/uImage.FIT/source_file_format.txt.
Alexandru Gagniucdf51ae72021-03-29 12:05:15 -0500215 3. FDTs are only loaded for images with an "os" property of "u-boot".
216 "linux" images are also supported with Falcon boot mode.
217
Simon Glasscf298162020-09-10 20:21:13 -0600218config SPL_LOAD_FIT_ADDRESS
219 hex "load address of fit image"
220 depends on SPL_LOAD_FIT
221 default 0x0
222 help
223 Specify the load address of the fit image that will be loaded
224 by SPL.
225
226config SPL_LOAD_FIT_APPLY_OVERLAY
227 bool "Enable SPL applying DT overlays from FIT"
228 depends on SPL_LOAD_FIT
229 select OF_LIBFDT_OVERLAY
230 help
231 The device tree is loaded from the FIT image. Allow the SPL is to
232 also load device-tree overlays from the FIT image an apply them
233 over the device tree.
234
235config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
236 depends on SPL_LOAD_FIT_APPLY_OVERLAY
237 default 0x10000
238 hex "size of temporary buffer used to load the overlays"
239 help
240 The size of the area where the overlays will be loaded and
241 uncompress. Must be at least as large as biggest overlay
242 (uncompressed)
243
244config SPL_LOAD_FIT_FULL
245 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
246 select SPL_FIT
247 help
248 Normally with the SPL framework a legacy image is generated as part
249 of the build. This contains U-Boot along with information as to
250 where it should be loaded. This option instead enables generation
251 of a FIT (Flat Image Tree) which provides more flexibility. In
252 particular it can handle selecting from multiple device tree
253 and passing the correct one to U-Boot.
254
255config SPL_FIT_IMAGE_POST_PROCESS
256 bool "Enable post-processing of FIT artifacts after loading by the SPL"
257 depends on SPL_LOAD_FIT
Andrew Davis042e87e2022-05-04 15:52:28 -0500258 default y if TI_SECURE_DEVICE
Simon Glasscf298162020-09-10 20:21:13 -0600259 help
260 Allows doing any sort of manipulation to blobs after they got extracted
261 from the U-Boot FIT image like stripping off headers or modifying the
262 size of the blob, verification, authentication, decryption etc. in a
263 platform or board specific way. In order to use this feature a platform
264 or board-specific implementation of board_fit_image_post_process() must
265 be provided. Also, anything done during this post-processing step would
266 need to be comprehended in how the images were prepared before being
267 injected into the FIT creation (i.e. the blobs would have been pre-
268 processed before being added to the FIT image).
269
270config SPL_FIT_SOURCE
271 string ".its source file for U-Boot FIT image"
272 depends on SPL_FIT
273 help
274 Specifies a (platform specific) FIT source file to generate the
275 U-Boot FIT image. This could specify further image to load and/or
276 execute.
277
278config USE_SPL_FIT_GENERATOR
279 bool "Use a script to generate the .its script"
Bin Meng84dee332021-05-10 20:23:41 +0800280 default y if SPL_FIT && (!ARCH_SUNXI && !RISCV)
Simon Glasscf298162020-09-10 20:21:13 -0600281
282config SPL_FIT_GENERATOR
283 string ".its file generator script for U-Boot FIT image"
284 depends on USE_SPL_FIT_GENERATOR
285 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
286 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
Simon Glasscf298162020-09-10 20:21:13 -0600287 help
288 Specifies a (platform specific) script file to generate the FIT
289 source file used to build the U-Boot FIT image file. This gets
290 passed a list of supported device tree file stub names to
291 include in the generated image.
292
293endif # SPL
294
295endif # FIT
296
John Keepingbe43a352022-07-28 11:19:15 +0100297config PXE_UTILS
298 bool
299 select MENU
300 help
301 Utilities for parsing PXE file formats.
302
Simon Glassef5e3892022-04-24 23:31:06 -0600303config BOOTSTD
304 bool "Standard boot support"
305 default y
306 depends on DM && OF_CONTROL && BLK
307 help
308 U-Boot supports a standard way of locating something to boot,
309 typically an Operating System such as Linux, provided by a distro such
310 as Arch Linux or Debian. Enable this to support iterating through
311 available bootdevs and using bootmeths to find bootflows suitable for
312 booting.
313
314 Standard boot is not a standard way of booting, just a framework
315 within U-Boot for supporting all the different ways that exist.
316
317 Terminology:
318
319 - bootdev - a device which can hold a distro (e.g. MMC)
320 - bootmeth - a method to scan a bootdev to find bootflows (owned by
321 U-Boot)
322 - bootflow - a description of how to boot (owned by the distro)
323
324config BOOTSTD_FULL
325 bool "Enhanced features for standard boot"
326 default y if SANDBOX
327 help
328 This enables various useful features for standard boot, which are not
329 essential for operation:
330
331 - bootdev, bootmeth commands
332 - extra features in the bootflow command
333 - support for selecting the ordering of bootmeths ("bootmeth order")
334 - support for selecting the ordering of bootdevs using the devicetree
335 as well as the "boot_targets" environment variable
336
Simon Glass31aefaf2022-04-24 23:31:13 -0600337if BOOTSTD
338
Simon Glassa91492b2022-04-24 23:31:27 -0600339config BOOTSTD_BOOTCOMMAND
340 bool "Use bootstd to boot"
341 default y if !DISTRO_DEFAULTS
342 help
343 Enable this to select a default boot-command suitable for booting
344 with standard boot. This can be overridden by the board if needed,
345 but the default command should be enough for most boards which use
346 standard boot.
347
348 For now this is only selected if distro boot is NOT used, since
349 standard boot does not support all of the features of distro boot
350 yet.
351
Simon Glassbc06aa02022-07-30 15:52:21 -0600352config BOOTMETH_GLOBAL
353 bool
354 help
355 Add support for global bootmeths. This feature is used by VBE and
356 EFI bootmgr, since they take full control over which bootdevs are
357 selected to boot.
358
Simon Glass31aefaf2022-04-24 23:31:13 -0600359config BOOTMETH_DISTRO
360 bool "Bootdev support for distro boot"
John Keepingbe43a352022-07-28 11:19:15 +0100361 select PXE_UTILS
Simon Glass31aefaf2022-04-24 23:31:13 -0600362 default y
363 help
364 Enables support for distro boot using bootdevs. This makes the
365 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
366 they scan.
367
368 This provides a way to try out standard boot on an existing boot flow.
369
Simon Glassdab2c282022-04-24 23:31:16 -0600370config BOOTMETH_DISTRO_PXE
371 bool "Bootdev support for distro boot over network"
372 depends on CMD_PXE && CMD_NET && DM_ETH
373 default y
374 help
375 Enables support for distro boot using bootdevs. This makes the
376 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
377
378 This provides a way to try out standard boot on an existing boot flow.
379
Simon Glassacfa9bd2022-04-24 23:31:17 -0600380config BOOTMETH_EFILOADER
381 bool "Bootdev support for EFI boot"
382 depends on CMD_BOOTEFI
383 default y
384 help
385 Enables support for EFI boot using bootdevs. This makes the
386 bootdevs look for a 'boot<arch>.efi' on each filesystem
387 they scan. The resulting file is booted after enabling U-Boot's
388 EFI loader support.
389
390 The <arch> depends on the architecture of the board:
391
392 aa64 - aarch64 (ARM 64-bit)
393 arm - ARM 32-bit
394 ia32 - x86 32-bit
395 x64 - x86 64-bit
396 riscv32 - RISC-V 32-bit
397 riscv64 - RISC-V 64-bit
398
399 This provides a way to try out standard boot on an existing boot flow.
400
Simon Glass4c7418f2022-07-30 15:52:32 -0600401config BOOTMETH_VBE
402 bool "Bootdev support for Verified Boot for Embedded"
403 depends on FIT
404 default y
405 select BOOTMETH_GLOBAL
406 help
407 Enables support for VBE boot. This is a standard boot method which
408 supports selection of various firmware components, seleciton of an OS to
409 boot as well as updating these using fwupd.
410
Simon Glass126947b2022-04-24 23:31:20 -0600411config BOOTMETH_SANDBOX
412 def_bool y
413 depends on SANDBOX
414 help
415 This is a sandbox bootmeth driver used for testing. It always returns
416 -ENOTSUPP when attempting to boot.
417
Simon Glassd9409242022-04-24 23:31:22 -0600418config BOOTMETH_SCRIPT
419 bool "Bootdev support for U-Boot scripts"
420 default y if BOOTSTD_FULL
421 help
422 Enables support for booting a distro via a U-Boot script. This makes
423 the bootdevs look for a 'boot/boot.scr' file which can be used to
424 boot the distro.
425
426 This provides a way to try out standard boot on an existing boot flow.
427 It is not enabled by default to save space.
428
Simon Glass31aefaf2022-04-24 23:31:13 -0600429endif
430
Simon Glasscf298162020-09-10 20:21:13 -0600431config LEGACY_IMAGE_FORMAT
432 bool "Enable support for the legacy image format"
Andrew Davis52dc3342022-05-04 15:52:27 -0500433 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
Simon Glasscf298162020-09-10 20:21:13 -0600434 help
435 This option enables the legacy image format. It is enabled by
436 default for backward compatibility, unless FIT_SIGNATURE is
437 set where it is disabled so that unsigned images cannot be
438 loaded. If a board needs the legacy image format support in this
439 case, enable it here.
440
Simon Glassaefa34f2020-09-10 20:21:19 -0600441config SUPPORT_RAW_INITRD
442 bool "Enable raw initrd images"
443 help
444 Note, defining the SUPPORT_RAW_INITRD allows user to supply
445 kernel with raw initrd images. The syntax is slightly different, the
446 address of the initrd must be augmented by it's size, in the following
447 format: "<initrd address>:<initrd size>".
448
Simon Glasscf298162020-09-10 20:21:13 -0600449config OF_BOARD_SETUP
450 bool "Set up board-specific details in device tree before boot"
451 depends on OF_LIBFDT
452 help
453 This causes U-Boot to call ft_board_setup() before booting into
454 the Operating System. This function can set up various
455 board-specific information in the device tree for use by the OS.
456 The device tree is then passed to the OS.
457
458config OF_SYSTEM_SETUP
459 bool "Set up system-specific details in device tree before boot"
460 depends on OF_LIBFDT
461 help
462 This causes U-Boot to call ft_system_setup() before booting into
463 the Operating System. This function can set up various
464 system-specific information in the device tree for use by the OS.
465 The device tree is then passed to the OS.
466
467config OF_STDOUT_VIA_ALIAS
468 bool "Update the device-tree stdout alias from U-Boot"
469 depends on OF_LIBFDT
470 help
471 This uses U-Boot's serial alias from the aliases node to update
472 the device tree passed to the OS. The "linux,stdout-path" property
473 in the chosen node is set to point to the correct serial node.
474 This option currently references CONFIG_CONS_INDEX, which is
475 incorrect when used with device tree as this option does not
476 exist / should not be used.
477
Simon Glasscf298162020-09-10 20:21:13 -0600478config HAVE_SYS_TEXT_BASE
479 bool
480 depends on !NIOS2 && !XTENSA
481 depends on !EFI_APP
482 default y
483
484config SYS_TEXT_BASE
485 depends on HAVE_SYS_TEXT_BASE
Tom Rini55adabb2021-07-09 10:39:21 -0400486 default 0x0 if POSITION_INDEPENDENT
Simon Glasscf298162020-09-10 20:21:13 -0600487 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
Icenowy Zhengb6ffd582022-01-29 10:23:09 -0500488 default 0x81700000 if MACH_SUNIV
489 default 0x2a000000 if MACH_SUN9I
490 default 0x42e00000 if MACH_SUN8I_V3S
491 default 0x4a000000 if ARCH_SUNXI
Simon Glasscf298162020-09-10 20:21:13 -0600492 hex "Text Base"
493 help
494 The address in memory that U-Boot will be running from, initially.
495
Tom Rinie4d741f2022-03-24 17:18:05 -0400496config HAVE_SYS_MONITOR_BASE
497 bool
498 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
Tom Rinicc1015f2022-07-23 13:05:01 -0400499 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
Tom Rinie4d741f2022-03-24 17:18:05 -0400500 depends on !EFI_APP
501 default y
502
503config SYS_MONITOR_BASE
504 depends on HAVE_SYS_MONITOR_BASE
505 hex "Physical start address of boot monitor code"
506 default SYS_TEXT_BASE
507 help
508 The physical start address of boot monitor code (which is the same as
509 CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE
510 when booting from flash.
511
512config SPL_SYS_MONITOR_BASE
513 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
514 hex "Physical start address of SPL monitor code"
515 default SPL_TEXT_BASE
516
517config TPL_SYS_MONITOR_BASE
518 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
519 hex "Physical start address of TPL monitor code"
520
Tom Rini2f8a6db2021-12-14 13:36:40 -0500521config DYNAMIC_SYS_CLK_FREQ
522 bool "Determine CPU clock frequency at run-time"
Simon Glasscf298162020-09-10 20:21:13 -0600523 help
Tom Rini2f8a6db2021-12-14 13:36:40 -0500524 Implement a get_board_sys_clk function that will determine the CPU
525 clock frequency at run time, rather than define it statically.
526
527config SYS_CLK_FREQ
528 depends on !DYNAMIC_SYS_CLK_FREQ
529 int "CPU clock frequency"
530 default 125000000 if ARCH_LS1012A
531 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
532 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
533 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
534 default 66660000 if ARCH_T2080
535 default 33333333 if RCAR_GEN3
536 default 24000000 if ARCH_EXYNOS
537 default 20000000 if RCAR_GEN2
538 default 0
539 help
540 A static value for the CPU frequency. Note that if not required
541 for a given SoC, this can be left at 0.
Simon Glasscf298162020-09-10 20:21:13 -0600542
543config ARCH_FIXUP_FDT_MEMORY
544 bool "Enable arch_fixup_memory_banks() call"
545 default y
546 help
547 Enable FDT memory map syncup before OS boot. This feature can be
548 used for booting OS with different memory setup where the part of
549 the memory location should be used for different purpose.
550
Simon Glass96d0aa92020-11-04 09:57:35 -0700551config CHROMEOS
552 bool "Support booting Chrome OS"
553 help
554 Chrome OS requires U-Boot to set up a table indicating the boot mode
555 (e.g. Developer mode) and a few other things. Enable this if you are
556 booting on a Chromebook to avoid getting an error about an invalid
557 firmware ID.
558
559config CHROMEOS_VBOOT
560 bool "Support Chrome OS verified boot"
561 help
562 This is intended to enable the full Chrome OS verified boot support
563 in U-Boot. It is not actually implemented in the U-Boot source code
564 at present, so this option is always set to 'n'. It allows
565 distinguishing between booting Chrome OS in a basic way (developer
566 mode) and a full boot.
567
Tom Rini5a446182022-06-25 11:02:44 -0400568config SYS_RAMBOOT
569 bool
570
Tom Rinid8ef01e2021-08-24 23:11:49 -0400571config RAMBOOT_PBL
572 bool "Freescale PBL(pre-boot loader) image format support"
Tom Rini5a446182022-06-25 11:02:44 -0400573 select SYS_RAMBOOT if PPC
Tom Rinid8ef01e2021-08-24 23:11:49 -0400574 help
575 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
576 For more details refer to doc/README.pblimage
577
Tom Rinid433c742022-03-23 17:20:03 -0400578choice
579 prompt "Freescale PBL load location"
580 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
581 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
582 && !CMD_NAND)
583
584config SDCARD
585 bool "Freescale PBL is found on SD card"
586
587config SPIFLASH
588 bool "Freescale PBL is found on SPI flash"
589
590endchoice
591
Tom Rinid8e84612022-06-20 08:07:42 -0400592config FSL_FIXED_MMC_LOCATION
593 bool "PBL MMC is at a fixed location"
594 depends on SDCARD && !RAMBOOT_PBL
595
596config ESDHC_HC_BLK_ADDR
597 def_bool y
598 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
599 help
600 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
601 code length of these soc specify the memory address in block address
602 format. Block length is fixed to 512 bytes as per the SD High
603 Capacity specification.
604
Tom Rinid8ef01e2021-08-24 23:11:49 -0400605config SYS_FSL_PBL_PBI
606 string "PBI(pre-boot instructions) commands for the PBL image"
607 depends on RAMBOOT_PBL
608 help
609 PBI commands can be used to configure SoC before it starts the execution.
610 Please refer doc/README.pblimage for more details.
611
612config SYS_FSL_PBL_RCW
613 string "Aadditional RCW (Power on reset configuration) for the PBL image"
614 depends on RAMBOOT_PBL
615 help
616 Enables addition of RCW (Power on reset configuration) in built image.
617 Please refer doc/README.pblimage for more details.
618
Tom Rinibb20a102022-06-25 11:02:46 -0400619config SYS_BOOT_RAMDISK_HIGH
620 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
621 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
622 def_bool y
623 help
624 Enable initrd_high functionality. If defined then the initrd_high
625 feature is enabled and the boot* ramdisk subcommand is enabled.
626
Simon Glasscf298162020-09-10 20:21:13 -0600627endmenu # Boot images
628
Simon Glass75e65cc2020-09-10 20:21:14 -0600629menu "Boot timing"
630
631config BOOTSTAGE
632 bool "Boot timing and reporting"
633 help
634 Enable recording of boot time while booting. To use it, insert
635 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
636 bootstage.h. Only a single entry is recorded for each ID. You can
637 give the entry a name with bootstage_mark_name(). You can also
638 record elapsed time in a particular stage using bootstage_start()
639 before starting and bootstage_accum() when finished. Bootstage will
640 add up all the accumulated time and report it.
641
642 Normally, IDs are defined in bootstage.h but a small number of
643 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
644 as the ID.
645
646 Calls to show_boot_progress() will also result in log entries but
647 these will not have names.
648
649config SPL_BOOTSTAGE
650 bool "Boot timing and reported in SPL"
Tom Rinib3401992022-06-10 23:03:09 -0400651 depends on BOOTSTAGE && SPL
Simon Glass75e65cc2020-09-10 20:21:14 -0600652 help
653 Enable recording of boot time in SPL. To make this visible to U-Boot
654 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
655 information when SPL finishes and load it when U-Boot proper starts
656 up.
657
658config TPL_BOOTSTAGE
659 bool "Boot timing and reported in TPL"
Tom Rini8bea4bf2022-06-08 08:24:39 -0400660 depends on BOOTSTAGE && TPL
Simon Glass75e65cc2020-09-10 20:21:14 -0600661 help
662 Enable recording of boot time in SPL. To make this visible to U-Boot
663 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
664 information when TPL finishes and load it when U-Boot proper starts
665 up.
666
667config BOOTSTAGE_REPORT
668 bool "Display a detailed boot timing report before booting the OS"
669 depends on BOOTSTAGE
670 help
671 Enable output of a boot time report just before the OS is booted.
672 This shows how long it took U-Boot to go through each stage of the
673 boot process. The report looks something like this:
674
675 Timer summary in microseconds:
676 Mark Elapsed Stage
677 0 0 reset
678 3,575,678 3,575,678 board_init_f start
679 3,575,695 17 arch_cpu_init A9
680 3,575,777 82 arch_cpu_init done
681 3,659,598 83,821 board_init_r start
682 3,910,375 250,777 main_loop
683 29,916,167 26,005,792 bootm_start
684 30,361,327 445,160 start_kernel
685
686config BOOTSTAGE_RECORD_COUNT
687 int "Number of boot stage records to store"
Simon Glass939b04e2021-02-03 06:00:49 -0700688 depends on BOOTSTAGE
Simon Glass75e65cc2020-09-10 20:21:14 -0600689 default 30
690 help
691 This is the size of the bootstage record list and is the maximum
692 number of bootstage records that can be recorded.
693
694config SPL_BOOTSTAGE_RECORD_COUNT
695 int "Number of boot stage records to store for SPL"
Simon Glass939b04e2021-02-03 06:00:49 -0700696 depends on SPL_BOOTSTAGE
Simon Glass75e65cc2020-09-10 20:21:14 -0600697 default 5
698 help
699 This is the size of the bootstage record list and is the maximum
700 number of bootstage records that can be recorded.
701
702config TPL_BOOTSTAGE_RECORD_COUNT
703 int "Number of boot stage records to store for TPL"
Simon Glass939b04e2021-02-03 06:00:49 -0700704 depends on TPL_BOOTSTAGE
Simon Glass75e65cc2020-09-10 20:21:14 -0600705 default 5
706 help
707 This is the size of the bootstage record list and is the maximum
708 number of bootstage records that can be recorded.
709
710config BOOTSTAGE_FDT
711 bool "Store boot timing information in the OS device tree"
712 depends on BOOTSTAGE
713 help
714 Stash the bootstage information in the FDT. A root 'bootstage'
715 node is created with each bootstage id as a child. Each child
716 has a 'name' property and either 'mark' containing the
717 mark time in microseconds, or 'accum' containing the
718 accumulated time for that bootstage id in microseconds.
719 For example:
720
721 bootstage {
722 154 {
723 name = "board_init_f";
724 mark = <3575678>;
725 };
726 170 {
727 name = "lcd";
728 accum = <33482>;
729 };
730 };
731
732 Code in the Linux kernel can find this in /proc/devicetree.
733
734config BOOTSTAGE_STASH
735 bool "Stash the boot timing information in memory before booting OS"
736 depends on BOOTSTAGE
737 help
738 Some OSes do not support device tree. Bootstage can instead write
739 the boot timing information in a binary format at a given address.
740 This happens through a call to bootstage_stash(), typically in
741 the CPU's cleanup_before_linux() function. You can use the
742 'bootstage stash' and 'bootstage unstash' commands to do this on
743 the command line.
744
745config BOOTSTAGE_STASH_ADDR
746 hex "Address to stash boot timing information"
747 default 0
748 help
749 Provide an address which will not be overwritten by the OS when it
750 starts, so that it can read this information when ready.
751
752config BOOTSTAGE_STASH_SIZE
753 hex "Size of boot timing stash region"
754 default 0x1000
755 help
756 This should be large enough to hold the bootstage stash. A value of
757 4096 (4KiB) is normally plenty.
758
759config SHOW_BOOT_PROGRESS
760 bool "Show boot progress in a board-specific manner"
761 help
762 Defining this option allows to add some board-specific code (calling
763 a user-provided function show_boot_progress(int) that enables you to
764 show the system's boot progress on some display (for example, some
765 LEDs) on your board. At the moment, the following checkpoints are
766 implemented:
767
768 Legacy uImage format:
769
770 Arg Where When
771 1 common/cmd_bootm.c before attempting to boot an image
772 -1 common/cmd_bootm.c Image header has bad magic number
773 2 common/cmd_bootm.c Image header has correct magic number
774 -2 common/cmd_bootm.c Image header has bad checksum
775 3 common/cmd_bootm.c Image header has correct checksum
776 -3 common/cmd_bootm.c Image data has bad checksum
777 4 common/cmd_bootm.c Image data has correct checksum
778 -4 common/cmd_bootm.c Image is for unsupported architecture
779 5 common/cmd_bootm.c Architecture check OK
780 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
781 6 common/cmd_bootm.c Image Type check OK
782 -6 common/cmd_bootm.c gunzip uncompression error
783 -7 common/cmd_bootm.c Unimplemented compression type
784 7 common/cmd_bootm.c Uncompression OK
785 8 common/cmd_bootm.c No uncompress/copy overwrite error
786 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
787
788 9 common/image.c Start initial ramdisk verification
789 -10 common/image.c Ramdisk header has bad magic number
790 -11 common/image.c Ramdisk header has bad checksum
791 10 common/image.c Ramdisk header is OK
792 -12 common/image.c Ramdisk data has bad checksum
793 11 common/image.c Ramdisk data has correct checksum
794 12 common/image.c Ramdisk verification complete, start loading
795 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
796 13 common/image.c Start multifile image verification
797 14 common/image.c No initial ramdisk, no multifile, continue.
798
799 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
800
801 -30 arch/powerpc/lib/board.c Fatal error, hang the system
802 -31 post/post.c POST test failed, detected by post_output_backlog()
803 -32 post/post.c POST test failed, detected by post_run_single()
804
805 34 common/cmd_doc.c before loading a Image from a DOC device
806 -35 common/cmd_doc.c Bad usage of "doc" command
807 35 common/cmd_doc.c correct usage of "doc" command
808 -36 common/cmd_doc.c No boot device
809 36 common/cmd_doc.c correct boot device
810 -37 common/cmd_doc.c Unknown Chip ID on boot device
811 37 common/cmd_doc.c correct chip ID found, device available
812 -38 common/cmd_doc.c Read Error on boot device
813 38 common/cmd_doc.c reading Image header from DOC device OK
814 -39 common/cmd_doc.c Image header has bad magic number
815 39 common/cmd_doc.c Image header has correct magic number
816 -40 common/cmd_doc.c Error reading Image from DOC device
817 40 common/cmd_doc.c Image header has correct magic number
818 41 common/cmd_ide.c before loading a Image from a IDE device
819 -42 common/cmd_ide.c Bad usage of "ide" command
820 42 common/cmd_ide.c correct usage of "ide" command
821 -43 common/cmd_ide.c No boot device
822 43 common/cmd_ide.c boot device found
823 -44 common/cmd_ide.c Device not available
824 44 common/cmd_ide.c Device available
825 -45 common/cmd_ide.c wrong partition selected
826 45 common/cmd_ide.c partition selected
827 -46 common/cmd_ide.c Unknown partition table
828 46 common/cmd_ide.c valid partition table found
829 -47 common/cmd_ide.c Invalid partition type
830 47 common/cmd_ide.c correct partition type
831 -48 common/cmd_ide.c Error reading Image Header on boot device
832 48 common/cmd_ide.c reading Image Header from IDE device OK
833 -49 common/cmd_ide.c Image header has bad magic number
834 49 common/cmd_ide.c Image header has correct magic number
835 -50 common/cmd_ide.c Image header has bad checksum
836 50 common/cmd_ide.c Image header has correct checksum
837 -51 common/cmd_ide.c Error reading Image from IDE device
838 51 common/cmd_ide.c reading Image from IDE device OK
839 52 common/cmd_nand.c before loading a Image from a NAND device
840 -53 common/cmd_nand.c Bad usage of "nand" command
841 53 common/cmd_nand.c correct usage of "nand" command
842 -54 common/cmd_nand.c No boot device
843 54 common/cmd_nand.c boot device found
844 -55 common/cmd_nand.c Unknown Chip ID on boot device
845 55 common/cmd_nand.c correct chip ID found, device available
846 -56 common/cmd_nand.c Error reading Image Header on boot device
847 56 common/cmd_nand.c reading Image Header from NAND device OK
848 -57 common/cmd_nand.c Image header has bad magic number
849 57 common/cmd_nand.c Image header has correct magic number
850 -58 common/cmd_nand.c Error reading Image from NAND device
851 58 common/cmd_nand.c reading Image from NAND device OK
852
853 -60 common/env_common.c Environment has a bad CRC, using default
854
855 64 net/eth.c starting with Ethernet configuration.
856 -64 net/eth.c no Ethernet found.
857 65 net/eth.c Ethernet found.
858
859 -80 common/cmd_net.c usage wrong
860 80 common/cmd_net.c before calling net_loop()
861 -81 common/cmd_net.c some error in net_loop() occurred
862 81 common/cmd_net.c net_loop() back without error
863 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
864 82 common/cmd_net.c trying automatic boot
865 83 common/cmd_net.c running "source" command
866 -83 common/cmd_net.c some error in automatic boot or "source" command
867 84 common/cmd_net.c end without errors
868
869 FIT uImage format:
870
871 Arg Where When
872 100 common/cmd_bootm.c Kernel FIT Image has correct format
873 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
874 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
875 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
876 102 common/cmd_bootm.c Kernel unit name specified
877 -103 common/cmd_bootm.c Can't get kernel subimage node offset
878 103 common/cmd_bootm.c Found configuration node
879 104 common/cmd_bootm.c Got kernel subimage node offset
880 -104 common/cmd_bootm.c Kernel subimage hash verification failed
881 105 common/cmd_bootm.c Kernel subimage hash verification OK
882 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
883 106 common/cmd_bootm.c Architecture check OK
884 -106 common/cmd_bootm.c Kernel subimage has wrong type
885 107 common/cmd_bootm.c Kernel subimage type OK
886 -107 common/cmd_bootm.c Can't get kernel subimage data/size
887 108 common/cmd_bootm.c Got kernel subimage data/size
888 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
889 -109 common/cmd_bootm.c Can't get kernel subimage type
890 -110 common/cmd_bootm.c Can't get kernel subimage comp
891 -111 common/cmd_bootm.c Can't get kernel subimage os
892 -112 common/cmd_bootm.c Can't get kernel subimage load address
893 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
894
895 120 common/image.c Start initial ramdisk verification
896 -120 common/image.c Ramdisk FIT image has incorrect format
897 121 common/image.c Ramdisk FIT image has correct format
898 122 common/image.c No ramdisk subimage unit name, using configuration
899 -122 common/image.c Can't get configuration for ramdisk subimage
900 123 common/image.c Ramdisk unit name specified
901 -124 common/image.c Can't get ramdisk subimage node offset
902 125 common/image.c Got ramdisk subimage node offset
903 -125 common/image.c Ramdisk subimage hash verification failed
904 126 common/image.c Ramdisk subimage hash verification OK
905 -126 common/image.c Ramdisk subimage for unsupported architecture
906 127 common/image.c Architecture check OK
907 -127 common/image.c Can't get ramdisk subimage data/size
908 128 common/image.c Got ramdisk subimage data/size
909 129 common/image.c Can't get ramdisk load address
910 -129 common/image.c Got ramdisk load address
911
912 -130 common/cmd_doc.c Incorrect FIT image format
913 131 common/cmd_doc.c FIT image format OK
914
915 -140 common/cmd_ide.c Incorrect FIT image format
916 141 common/cmd_ide.c FIT image format OK
917
918 -150 common/cmd_nand.c Incorrect FIT image format
919 151 common/cmd_nand.c FIT image format OK
920
Marek Vasutb55881d2021-10-23 03:06:03 +0200921config SPL_SHOW_BOOT_PROGRESS
Jan Kiszkac1df3d52021-11-03 15:09:36 +0100922 bool "Show boot progress in a board-specific manner in SPL"
Marek Vasutb55881d2021-10-23 03:06:03 +0200923 depends on SPL
924 help
925 Defining this option allows to add some board-specific code (calling
926 a user-provided function show_boot_progress(int) that enables you to
927 show the system's boot progress on some display (for example, some
928 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
929
Simon Glass75e65cc2020-09-10 20:21:14 -0600930endmenu
931
Simon Glass7b6baa32020-09-10 20:21:15 -0600932menu "Boot media"
933
934config NOR_BOOT
935 bool "Support for booting from NOR flash"
936 depends on NOR
937 help
938 Enabling this will make a U-Boot binary that is capable of being
939 booted via NOR. In this case we will enable certain pinmux early
940 as the ROM only partially sets up pinmux. We also default to using
941 NOR for environment.
942
943config NAND_BOOT
944 bool "Support for booting from NAND flash"
Simon Glass7b6baa32020-09-10 20:21:15 -0600945 imply MTD_RAW_NAND
946 help
947 Enabling this will make a U-Boot binary that is capable of being
948 booted via NAND flash. This is not a must, some SoCs need this,
949 some not.
950
951config ONENAND_BOOT
952 bool "Support for booting from ONENAND"
Simon Glass7b6baa32020-09-10 20:21:15 -0600953 imply MTD_RAW_NAND
954 help
955 Enabling this will make a U-Boot binary that is capable of being
956 booted via ONENAND. This is not a must, some SoCs need this,
957 some not.
958
959config QSPI_BOOT
960 bool "Support for booting from QSPI flash"
Simon Glass7b6baa32020-09-10 20:21:15 -0600961 help
962 Enabling this will make a U-Boot binary that is capable of being
963 booted via QSPI flash. This is not a must, some SoCs need this,
964 some not.
965
966config SATA_BOOT
967 bool "Support for booting from SATA"
Simon Glass7b6baa32020-09-10 20:21:15 -0600968 help
969 Enabling this will make a U-Boot binary that is capable of being
970 booted via SATA. This is not a must, some SoCs need this,
971 some not.
972
973config SD_BOOT
974 bool "Support for booting from SD/EMMC"
Simon Glass7b6baa32020-09-10 20:21:15 -0600975 help
976 Enabling this will make a U-Boot binary that is capable of being
977 booted via SD/EMMC. This is not a must, some SoCs need this,
978 some not.
979
Tom Rini66e0e2b2021-12-11 14:55:50 -0500980config SD_BOOT_QSPI
981 bool "Support for booting from SD/EMMC and enable QSPI"
982 help
983 Enabling this will make a U-Boot binary that is capable of being
984 booted via SD/EMMC while enabling QSPI on the platform as well. This
985 is not a must, some SoCs need this, some not.
986
Simon Glass7b6baa32020-09-10 20:21:15 -0600987config SPI_BOOT
988 bool "Support for booting from SPI flash"
Simon Glass7b6baa32020-09-10 20:21:15 -0600989 help
990 Enabling this will make a U-Boot binary that is capable of being
991 booted via SPI flash. This is not a must, some SoCs need this,
992 some not.
993
994endmenu
995
Simon Glass98eed0d2020-09-10 20:21:16 -0600996menu "Autoboot options"
997
998config AUTOBOOT
999 bool "Autoboot"
1000 default y
1001 help
1002 This enables the autoboot. See doc/README.autoboot for detail.
1003
Simon Glass95fd4f32020-09-10 20:21:17 -06001004config BOOTDELAY
1005 int "delay in seconds before automatically booting"
1006 default 2
1007 depends on AUTOBOOT
1008 help
1009 Delay before automatically running bootcmd;
1010 set to 0 to autoboot with no delay, but you can stop it by key input.
1011 set to -1 to disable autoboot.
1012 set to -2 to autoboot with no delay and not check for abort
1013
1014 If this value is >= 0 then it is also used for the default delay
1015 before starting the default entry in bootmenu. If it is < 0 then
1016 a default value of 10s is used.
1017
1018 See doc/README.autoboot for details.
1019
Simon Glass98eed0d2020-09-10 20:21:16 -06001020config AUTOBOOT_KEYED
1021 bool "Stop autobooting via specific input key / string"
Simon Glass98eed0d2020-09-10 20:21:16 -06001022 help
1023 This option enables stopping (aborting) of the automatic
1024 boot feature only by issuing a specific input key or
1025 string. If not enabled, any input key will abort the
1026 U-Boot automatic booting process and bring the device
1027 to the U-Boot prompt for user input.
1028
Steffen Jaeckeld199c3a2021-07-08 15:57:38 +02001029config AUTOBOOT_FLUSH_STDIN
1030 bool "Enable flushing stdin before starting to read the password"
1031 depends on AUTOBOOT_KEYED && !SANDBOX
1032 help
1033 When this option is enabled stdin buffer will be flushed before
1034 starting to read the password.
1035 This can't be enabled for the sandbox as flushing stdin would
1036 break the autoboot unit tests.
1037
Simon Glass98eed0d2020-09-10 20:21:16 -06001038config AUTOBOOT_PROMPT
1039 string "Autoboot stop prompt"
1040 depends on AUTOBOOT_KEYED
1041 default "Autoboot in %d seconds\\n"
1042 help
1043 This string is displayed before the boot delay selected by
1044 CONFIG_BOOTDELAY starts. If it is not defined there is no
1045 output indicating that autoboot is in progress.
1046
1047 Note that this define is used as the (only) argument to a
1048 printf() call, so it may contain '%' format specifications,
1049 provided that it also includes, sepearated by commas exactly
1050 like in a printf statement, the required arguments. It is
1051 the responsibility of the user to select only such arguments
1052 that are valid in the given context.
1053
1054config AUTOBOOT_ENCRYPTION
1055 bool "Enable encryption in autoboot stopping"
1056 depends on AUTOBOOT_KEYED
1057 help
1058 This option allows a string to be entered into U-Boot to stop the
Steffen Jaeckel1a4a7782021-07-08 15:57:35 +02001059 autoboot.
1060 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1061 or not.
1062 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1063 to the crypt-based functionality and be compared against the
1064 string in the environment variable 'bootstopkeycrypt'.
1065 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1066 and compared against the hash in the environment variable
1067 'bootstopkeysha256'.
1068 If it matches in either case then boot stops and
1069 a command-line prompt is presented.
Simon Glass98eed0d2020-09-10 20:21:16 -06001070 This provides a way to ship a secure production device which can also
1071 be accessed at the U-Boot command line.
1072
Steffen Jaeckel33198742021-07-08 15:57:39 +02001073config AUTOBOOT_SHA256_FALLBACK
1074 bool "Allow fallback from crypt-hashed password to sha256"
1075 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1076 help
1077 This option adds support to fall back from crypt-hashed
1078 passwords to checking a SHA256 hashed password in case the
1079 'bootstopusesha256' environment variable is set to 'true'.
1080
Simon Glass98eed0d2020-09-10 20:21:16 -06001081config AUTOBOOT_DELAY_STR
1082 string "Delay autobooting via specific input key / string"
1083 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1084 help
1085 This option delays the automatic boot feature by issuing
1086 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1087 or the environment variable "bootdelaykey" is specified
1088 and this string is received from console input before
1089 autoboot starts booting, U-Boot gives a command prompt. The
1090 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1091 used, otherwise it never times out.
1092
1093config AUTOBOOT_STOP_STR
1094 string "Stop autobooting via specific input key / string"
1095 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1096 help
1097 This option enables stopping (aborting) of the automatic
1098 boot feature only by issuing a specific input key or
1099 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1100 variable "bootstopkey" is specified and this string is
1101 received from console input before autoboot starts booting,
1102 U-Boot gives a command prompt. The U-Boot prompt never
1103 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1104
1105config AUTOBOOT_KEYED_CTRLC
1106 bool "Enable Ctrl-C autoboot interruption"
1107 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
Simon Glass98eed0d2020-09-10 20:21:16 -06001108 help
1109 This option allows for the boot sequence to be interrupted
1110 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1111 Setting this variable provides an escape sequence from the
1112 limited "password" strings.
1113
Steffen Jaeckel6c0ce6d2021-07-08 15:57:37 +02001114config AUTOBOOT_NEVER_TIMEOUT
1115 bool "Make the password entry never time-out"
1116 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1117 help
1118 This option removes the timeout from the password entry
1119 when the user first presses the <Enter> key before entering
1120 any other character.
1121
Steffen Jaeckel1a4a7782021-07-08 15:57:35 +02001122config AUTOBOOT_STOP_STR_ENABLE
1123 bool "Enable fixed string to stop autobooting"
1124 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1125 help
1126 This option enables the feature to add a fixed stop
1127 string that is defined at compile time.
1128 In every case it will be tried to load the stop
1129 string from the environment.
1130 In case this is enabled and there is no stop string
1131 in the environment, this will be used as default value.
1132
1133config AUTOBOOT_STOP_STR_CRYPT
1134 string "Stop autobooting via crypt-hashed password"
1135 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1136 help
1137 This option adds the feature to only stop the autobooting,
1138 and therefore boot into the U-Boot prompt, when the input
1139 string / password matches a values that is hashed via
1140 one of the supported crypt-style password hashing options
1141 and saved in the environment variable "bootstopkeycrypt".
1142
Simon Glass98eed0d2020-09-10 20:21:16 -06001143config AUTOBOOT_STOP_STR_SHA256
Steffen Jaeckel25c8b9f2021-07-08 15:57:40 +02001144 string "Stop autobooting via SHA256 hashed password"
Steffen Jaeckel1a4a7782021-07-08 15:57:35 +02001145 depends on AUTOBOOT_STOP_STR_ENABLE
Simon Glass98eed0d2020-09-10 20:21:16 -06001146 help
1147 This option adds the feature to only stop the autobooting,
1148 and therefore boot into the U-Boot prompt, when the input
1149 string / password matches a values that is encypted via
Joel Peshkin652b5042020-11-21 17:18:59 -08001150 a SHA256 hash and saved in the environment variable
1151 "bootstopkeysha256". If the value in that variable
1152 includes a ":", the portion prior to the ":" will be treated
1153 as a salt value.
Simon Glass98eed0d2020-09-10 20:21:16 -06001154
1155config AUTOBOOT_USE_MENUKEY
1156 bool "Allow a specify key to run a menu from the environment"
1157 depends on !AUTOBOOT_KEYED
1158 help
1159 If a specific key is pressed to stop autoboot, then the commands in
1160 the environment variable 'menucmd' are executed before boot starts.
1161
1162config AUTOBOOT_MENUKEY
1163 int "ASCII value of boot key to show a menu"
1164 default 0
1165 depends on AUTOBOOT_USE_MENUKEY
1166 help
1167 If this key is pressed to stop autoboot, then the commands in the
1168 environment variable 'menucmd' will be executed before boot starts.
1169 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1170 this action.
1171
1172config AUTOBOOT_MENU_SHOW
1173 bool "Show a menu on boot"
1174 depends on CMD_BOOTMENU
1175 help
1176 This enables the boot menu, controlled by environment variables
1177 defined by the board. The menu starts after running the 'preboot'
1178 environmnent variable (if enabled) and before handling the boot delay.
1179 See README.bootmenu for more details.
1180
Masahisa Kojima83f73632022-05-26 19:09:38 +09001181config BOOTMENU_DISABLE_UBOOT_CONSOLE
1182 bool "Disallow bootmenu to enter the U-Boot console"
1183 depends on AUTOBOOT_MENU_SHOW
1184 help
1185 If this option is enabled, user can not enter the U-Boot console from
1186 bootmenu. It increases the system security.
1187
Tom Rini69c8a812022-03-11 09:12:04 -05001188config BOOT_RETRY
1189 bool "Boot retry feature"
1190 help
1191 Allow for having the U-Boot command prompt time out and attempt
1192 to boot again. If the environment variable "bootretry" is found then
1193 its value is used, otherwise the retry timeout is
1194 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1195 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1196
1197config BOOT_RETRY_TIME
1198 int "Timeout in seconds before attempting to boot again"
1199 depends on BOOT_RETRY
1200 help
1201 Time in seconds before the U-Boot prompt will timeout and boot will
1202 be attempted again.
1203
1204config BOOT_RETRY_MIN
1205 int "Minimum timeout in seconds for 'bootretry'"
1206 depends on BOOT_RETRY
1207 default BOOT_RETRY_TIME
1208 help
1209 The minimum time in seconds that "bootretry" can be set to.
1210
1211config RESET_TO_RETRY
1212 bool "Reset the board to retry autoboot"
1213 depends on BOOT_RETRY
1214 help
1215 After the countdown timed out, the board will be reset to restart
1216 again.
1217
Simon Glass98eed0d2020-09-10 20:21:16 -06001218endmenu
1219
Philippe Reynes98220742022-03-28 22:56:59 +02001220menu "Image support"
1221
1222config IMAGE_PRE_LOAD
1223 bool "Image pre-load support"
1224 help
1225 Enable an image pre-load stage in the SPL.
1226 This pre-load stage allows to do some manipulation
1227 or check (for example signature check) on an image
1228 before launching it.
1229
1230config SPL_IMAGE_PRE_LOAD
1231 bool "Image pre-load support within SPL"
1232 depends on SPL && IMAGE_PRE_LOAD
1233 help
1234 Enable an image pre-load stage in the SPL.
1235 This pre-load stage allows to do some manipulation
1236 or check (for example signature check) on an image
1237 before launching it.
1238
1239config IMAGE_PRE_LOAD_SIG
1240 bool "Image pre-load signature support"
1241 depends on IMAGE_PRE_LOAD
1242 select FIT_SIGNATURE
1243 select RSA
1244 select RSA_VERIFY_WITH_PKEY
1245 help
1246 Enable signature check support in the pre-load stage.
1247 For this feature a very simple header is added before
1248 the image with few fields:
1249 - a magic
1250 - the image size
1251 - the signature
1252 All other information (header size, type of signature,
1253 ...) are provided in the node /image/pre-load/sig of
1254 u-boot.
1255
1256config SPL_IMAGE_PRE_LOAD_SIG
1257 bool "Image pre-load signature support witin SPL"
1258 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1259 select SPL_FIT_SIGNATURE
1260 select SPL_RSA
1261 select SPL_RSA_VERIFY_WITH_PKEY
1262 help
1263 Enable signature check support in the pre-load stage in the SPL.
1264 For this feature a very simple header is added before
1265 the image with few fields:
1266 - a magic
1267 - the image size
1268 - the signature
1269 All other information (header size, type of signature,
1270 ...) are provided in the node /image/pre-load/sig of
1271 u-boot.
1272
1273endmenu
1274
Simon Glassfe5db252020-09-10 20:21:18 -06001275config USE_BOOTARGS
1276 bool "Enable boot arguments"
1277 help
1278 Provide boot arguments to bootm command. Boot arguments are specified
1279 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1280 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1281 will be undefined and won't take any space in U-Boot image.
1282
1283config BOOTARGS
1284 string "Boot arguments"
1285 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1286 help
1287 This can be used to pass arguments to the bootm command. The value of
1288 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1289 this value will also override the "chosen" node in FDT blob.
1290
Simon Glass51bb3382020-11-05 10:33:48 -07001291config BOOTARGS_SUBST
1292 bool "Support substituting strings in boot arguments"
1293 help
1294 This allows substituting string values in the boot arguments. These
1295 are applied after the commandline has been built.
1296
1297 One use for this is to insert the root-disk UUID into the command
1298 line where bootargs contains "root=${uuid}"
1299
1300 setenv bootargs "console= root=${uuid}"
1301 # Set the 'uuid' environment variable
1302 part uuid mmc 2:2 uuid
1303
1304 # Command-line substitution will put the real uuid into the
1305 # kernel command line
1306 bootm
1307
Simon Glassfe5db252020-09-10 20:21:18 -06001308config USE_BOOTCOMMAND
1309 bool "Enable a default value for bootcmd"
1310 help
1311 Provide a default value for the bootcmd entry in the environment. If
1312 autoboot is enabled this is what will be run automatically. Enable
1313 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1314 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1315 won't take any space in U-Boot image.
1316
1317config BOOTCOMMAND
1318 string "bootcmd value"
1319 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
Simon Glassa91492b2022-04-24 23:31:27 -06001320 default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL
1321 default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL
1322 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
Simon Glassfe5db252020-09-10 20:21:18 -06001323 help
1324 This is the string of commands that will be used as bootcmd and if
1325 AUTOBOOT is set, automatically run.
1326
1327config USE_PREBOOT
1328 bool "Enable preboot"
1329 help
1330 When this option is enabled, the existence of the environment
1331 variable "preboot" will be checked immediately before starting the
1332 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1333 entering interactive mode.
1334
1335 This feature is especially useful when "preboot" is automatically
1336 generated or modified. For example, the boot code can modify the
1337 "preboot" when a user holds down a certain combination of keys.
1338
1339config PREBOOT
1340 string "preboot default value"
1341 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
Patrick Delaunay87459da2020-10-12 09:47:50 +02001342 default "usb start" if USB_KEYBOARD
Simon Glassfe5db252020-09-10 20:21:18 -06001343 default ""
1344 help
1345 This is the default of "preboot" environment variable.
1346
Simon Glass832876a2020-09-10 20:21:20 -06001347config DEFAULT_FDT_FILE
1348 string "Default fdt file"
1349 help
1350 This option is used to set the default fdt file to boot OS.
1351
Dzmitry Sankouski12a3e1a2022-02-22 21:49:52 +03001352config SAVE_PREV_BL_FDT_ADDR
1353 depends on ARM
1354 bool "Saves fdt address, passed by the previous bootloader, to env var"
1355 help
1356 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1357 enable this option to save fdt address, passed by the
1358 previous bootloader for future use.
1359 Address is saved to `prevbl_fdt_addr` environment variable.
1360
1361 If no fdt was provided by previous bootloader, no env variables
1362 will be created.
1363
1364config SAVE_PREV_BL_INITRAMFS_START_ADDR
1365 depends on ARM
1366 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1367 help
1368 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1369 enable this option to save initramfs address, passed by the
1370 previous bootloader for future use.
1371 Address is saved to `prevbl_initrd_start_addr` environment variable.
1372
1373 If no initramfs was provided by previous bootloader, no env variables
1374 will be created.
1375
Simon Glasscf298162020-09-10 20:21:13 -06001376endmenu # Booting