blob: 39c51e9e2fe8ec845bb7946f4b047b1808cc4824 [file] [log] [blame]
Simon Glassb45b1632020-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 Gagniuc650b7862021-09-02 19:54:21 -050014 select HASH
Simon Glassb45b1632020-09-10 20:21:13 -060015 select MD5
16 select SHA1
Alexandru Gagniuc8d310ef2021-09-02 19:54:17 -050017 imply SHA256
Simon Glassb45b1632020-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 Glass65831d92021-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 Glassb45b1632020-09-10 20:21:13 -060039config FIT_EXTERNAL_OFFSET
40 hex "FIT external data offset"
Tom Rini0f3d1de2022-12-04 10:14:20 -050041 depends on FIT
Simon Glassb45b1632020-09-10 20:21:13 -060042 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
Simon Glass244705b2021-02-15 17:08:10 -070050config FIT_FULL_CHECK
51 bool "Do a full check of the FIT before using it"
Tom Rini0f3d1de2022-12-04 10:14:20 -050052 depends on FIT
Simon Glass244705b2021-02-15 17:08:10 -070053 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 Glassb45b1632020-09-10 20:21:13 -060060config FIT_SIGNATURE
61 bool "Enable signature verification of FIT uImages"
Tom Rini0f3d1de2022-12-04 10:14:20 -050062 depends on DM && FIT
Simon Glassb45b1632020-09-10 20:21:13 -060063 select HASH
Alexandru Gagniuc1f2e2312021-07-29 11:47:18 -050064 imply RSA
65 imply RSA_VERIFY
Simon Glassb45b1632020-09-10 20:21:13 -060066 select IMAGE_SIGN_INFO
Simon Glass244705b2021-02-15 17:08:10 -070067 select FIT_FULL_CHECK
Simon Glassb45b1632020-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 Glass66b00c82021-07-14 17:05:31 -050091config FIT_RSASSA_PSS
Simon Glassb45b1632020-09-10 20:21:13 -060092 bool "Support rsassa-pss signature scheme of FIT image contents"
93 depends on FIT_SIGNATURE
Simon Glassb45b1632020-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"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500100 depends on DM && FIT
Simon Glassb45b1632020-09-10 20:21:13 -0600101 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"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500108 depends on FIT
Simon Glassb45b1632020-09-10 20:21:13 -0600109 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"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500117 depends on FIT
Simon Glassb45b1632020-09-10 20:21:13 -0600118 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"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500127 depends on FIT
Manorit Chawdhryf65cdf72023-07-14 11:22:40 +0530128 depends on SOCFPGA_SECURE_VAB_AUTH
Simon Glassb45b1632020-09-10 20:21:13 -0600129 help
130 Allows doing any sort of manipulation to blobs after they got extracted
131 from FIT images like stripping off headers or modifying the size of the
132 blob, verification, authentication, decryption etc. in a platform or
133 board specific way. In order to use this feature a platform or board-
134 specific implementation of board_fit_image_post_process() must be
135 provided. Also, anything done during this post-processing step would
136 need to be comprehended in how the images were prepared before being
137 injected into the FIT creation (i.e. the blobs would have been pre-
138 processed before being added to the FIT image).
139
Ravik Hasija11dac412021-01-27 14:01:48 -0800140config FIT_PRINT
141 bool "Support FIT printing"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500142 depends on FIT
Ravik Hasija11dac412021-01-27 14:01:48 -0800143 default y
144 help
145 Support printing the content of the fitImage in a verbose manner.
146
Simon Glassb45b1632020-09-10 20:21:13 -0600147config SPL_FIT
148 bool "Support Flattened Image Tree within SPL"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500149 depends on SPL && FIT
Alexandru Gagniuc650b7862021-09-02 19:54:21 -0500150 select SPL_HASH
Simon Glassb45b1632020-09-10 20:21:13 -0600151 select SPL_OF_LIBFDT
152
153config SPL_FIT_PRINT
154 bool "Support FIT printing within SPL"
155 depends on SPL_FIT
156 help
157 Support printing the content of the fitImage in a verbose manner in SPL.
158
Simon Glass244705b2021-02-15 17:08:10 -0700159config SPL_FIT_FULL_CHECK
160 bool "Do a full check of the FIT before using it"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500161 depends on SPL_FIT
Simon Glass244705b2021-02-15 17:08:10 -0700162 help
163 Enable this do a full check of the FIT to make sure it is valid. This
164 helps to protect against carefully crafted FITs which take advantage
165 of bugs or omissions in the code. This includes a bad structure,
166 multiple root nodes and the like.
167
Simon Glassb45b1632020-09-10 20:21:13 -0600168config SPL_FIT_SIGNATURE
169 bool "Enable signature verification of FIT firmware within SPL"
170 depends on SPL_DM
Klaus Heinrich Kiwiae5073f2021-02-09 15:41:54 -0300171 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
Klaus Heinrich Kiwic9796e62021-02-09 15:41:53 -0300172 select FIT_SIGNATURE
Simon Glassb45b1632020-09-10 20:21:13 -0600173 select SPL_FIT
Simon Glassa8437ce2021-07-10 21:14:25 -0600174 select SPL_CRYPTO
Alexandru Gagniuc97464ff2021-09-02 19:54:19 -0500175 select SPL_HASH
Alexandru Gagniuc1f2e2312021-07-29 11:47:18 -0500176 imply SPL_RSA
177 imply SPL_RSA_VERIFY
Simon Glassb45b1632020-09-10 20:21:13 -0600178 select SPL_IMAGE_SIGN_INFO
Simon Glass244705b2021-02-15 17:08:10 -0700179 select SPL_FIT_FULL_CHECK
Simon Glassb45b1632020-09-10 20:21:13 -0600180
Simon Glassc0cabbc2021-09-25 19:43:39 -0600181config SPL_FIT_SIGNATURE_MAX_SIZE
182 hex "Max size of signed FIT structures in SPL"
183 depends on SPL_FIT_SIGNATURE
184 default 0x10000000
185 help
186 This option sets a max size in bytes for verified FIT uImages.
187 A sane value of 256MB protects corrupted DTB structures from overlapping
188 device memory. Assure this size does not extend past expected storage
189 space.
190
Philippe Reynes47f3eb22021-10-15 11:35:03 +0200191config SPL_FIT_RSASSA_PSS
192 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
193 depends on SPL_FIT_SIGNATURE
194 help
195 Enable this to support the pss padding algorithm as described
196 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
197
Simon Glassb45b1632020-09-10 20:21:13 -0600198config SPL_LOAD_FIT
199 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500200 depends on SPL && FIT
Simon Glassb45b1632020-09-10 20:21:13 -0600201 select SPL_FIT
202 help
203 Normally with the SPL framework a legacy image is generated as part
204 of the build. This contains U-Boot along with information as to
205 where it should be loaded. This option instead enables generation
206 of a FIT (Flat Image Tree) which provides more flexibility. In
207 particular it can handle selecting from multiple device tree
208 and passing the correct one to U-Boot.
209
Alexandru Gagniuc064c9c22021-03-29 12:05:15 -0500210 This path has the following limitations:
211
Bin Meng91cdcb92021-05-10 20:23:29 +0800212 1. "loadables" images, other than FDTs, which do not have a "load"
Alexandru Gagniuc064c9c22021-03-29 12:05:15 -0500213 property will not be loaded. This limitation also applies to FPGA
214 images with the correct "compatible" string.
Oleksandr Suvorov17773572022-07-22 17:16:13 +0300215 2. For FPGA images, the supported "compatible" list is in the
216 doc/uImage.FIT/source_file_format.txt.
Alexandru Gagniuc064c9c22021-03-29 12:05:15 -0500217 3. FDTs are only loaded for images with an "os" property of "u-boot".
218 "linux" images are also supported with Falcon boot mode.
219
Simon Glassb45b1632020-09-10 20:21:13 -0600220config SPL_LOAD_FIT_ADDRESS
221 hex "load address of fit image"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500222 depends on SPL_LOAD_FIT || SPL_RAM_SUPPORT || TPL_RAM_SUPPORT
Simon Glassb45b1632020-09-10 20:21:13 -0600223 default 0x0
224 help
225 Specify the load address of the fit image that will be loaded
226 by SPL.
227
228config SPL_LOAD_FIT_APPLY_OVERLAY
229 bool "Enable SPL applying DT overlays from FIT"
230 depends on SPL_LOAD_FIT
231 select OF_LIBFDT_OVERLAY
232 help
Hugo Villeneuve5c1c6cc2023-04-24 16:51:12 -0400233 The device tree is loaded from the FIT image. Allow the SPL to
Simon Glassb45b1632020-09-10 20:21:13 -0600234 also load device-tree overlays from the FIT image an apply them
235 over the device tree.
236
237config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
238 depends on SPL_LOAD_FIT_APPLY_OVERLAY
239 default 0x10000
240 hex "size of temporary buffer used to load the overlays"
241 help
242 The size of the area where the overlays will be loaded and
243 uncompress. Must be at least as large as biggest overlay
244 (uncompressed)
245
246config SPL_LOAD_FIT_FULL
247 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500248 depends on FIT
Simon Glassb45b1632020-09-10 20:21:13 -0600249 select SPL_FIT
250 help
251 Normally with the SPL framework a legacy image is generated as part
252 of the build. This contains U-Boot along with information as to
253 where it should be loaded. This option instead enables generation
254 of a FIT (Flat Image Tree) which provides more flexibility. In
255 particular it can handle selecting from multiple device tree
256 and passing the correct one to U-Boot.
257
258config SPL_FIT_IMAGE_POST_PROCESS
259 bool "Enable post-processing of FIT artifacts after loading by the SPL"
260 depends on SPL_LOAD_FIT
Andrew Davis4ba9e6e2022-05-04 15:52:28 -0500261 default y if TI_SECURE_DEVICE
Simon Glassb45b1632020-09-10 20:21:13 -0600262 help
263 Allows doing any sort of manipulation to blobs after they got extracted
264 from the U-Boot FIT image like stripping off headers or modifying the
265 size of the blob, verification, authentication, decryption etc. in a
266 platform or board specific way. In order to use this feature a platform
267 or board-specific implementation of board_fit_image_post_process() must
268 be provided. Also, anything done during this post-processing step would
269 need to be comprehended in how the images were prepared before being
270 injected into the FIT creation (i.e. the blobs would have been pre-
271 processed before being added to the FIT image).
272
273config SPL_FIT_SOURCE
274 string ".its source file for U-Boot FIT image"
275 depends on SPL_FIT
276 help
277 Specifies a (platform specific) FIT source file to generate the
278 U-Boot FIT image. This could specify further image to load and/or
279 execute.
280
281config USE_SPL_FIT_GENERATOR
282 bool "Use a script to generate the .its script"
Tom Rini0f3d1de2022-12-04 10:14:20 -0500283 depends on SPL_FIT
Simon Glassbd7694f2023-01-07 14:07:19 -0700284 default y if SPL_FIT && ARCH_ZYNQMP
Simon Glassb45b1632020-09-10 20:21:13 -0600285
286config SPL_FIT_GENERATOR
287 string ".its file generator script for U-Boot FIT image"
288 depends on USE_SPL_FIT_GENERATOR
Simon Glassb45b1632020-09-10 20:21:13 -0600289 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
Simon Glassb45b1632020-09-10 20:21:13 -0600290 help
291 Specifies a (platform specific) script file to generate the FIT
292 source file used to build the U-Boot FIT image file. This gets
293 passed a list of supported device tree file stub names to
294 include in the generated image.
295
Simon Glassbc993e52022-10-20 18:23:13 -0600296if VPL
297
298config VPL_FIT
299 bool "Support Flattened Image Tree within VPL"
300 depends on VPL
301 default y
302 select VPL_HASH
303 select VPL_OF_LIBFDT
304
305config VPL_FIT_PRINT
306 bool "Support FIT printing within VPL"
307 depends on VPL_FIT
308 default y
309 help
310 Support printing the content of the fitImage in a verbose manner in VPL.
311
312config VPL_FIT_FULL_CHECK
313 bool "Do a full check of the FIT before using it"
314 default y
315 help
316 Enable this do a full check of the FIT to make sure it is valid. This
317 helps to protect against carefully crafted FITs which take advantage
318 of bugs or omissions in the code. This includes a bad structure,
319 multiple root nodes and the like.
320
321config VPL_FIT_SIGNATURE
322 bool "Enable signature verification of FIT firmware within VPL"
323 depends on VPL_DM
Simon Glassbc993e52022-10-20 18:23:13 -0600324 default y
325 select FIT_SIGNATURE
326 select VPL_FIT
327 select VPL_CRYPTO
328 select VPL_HASH
329 imply VPL_RSA
330 imply VPL_RSA_VERIFY
331 select VPL_IMAGE_SIGN_INFO
332 select VPL_FIT_FULL_CHECK
333
334config VPL_FIT_SIGNATURE_MAX_SIZE
335 hex "Max size of signed FIT structures in VPL"
336 depends on VPL_FIT_SIGNATURE
337 default 0x10000000
338 help
339 This option sets a max size in bytes for verified FIT uImages.
340 A sane value of 256MB protects corrupted DTB structures from overlapping
341 device memory. Assure this size does not extend past expected storage
342 space.
343
344endif # VPL
345
John Keeping9b60a172022-07-28 11:19:15 +0100346config PXE_UTILS
347 bool
348 select MENU
349 help
350 Utilities for parsing PXE file formats.
351
Simon Glass054d0182023-03-24 16:58:13 -0400352config BOOT_DEFAULTS
353 bool # Common defaults for standard boot and distroboot
354 imply USE_BOOTCOMMAND
355 select CMD_ENV_EXISTS
356 select CMD_EXT2
357 select CMD_EXT4
358 select CMD_FAT
359 select CMD_FS_GENERIC
360 select CMD_PART if PARTITIONS
361 select CMD_DHCP if CMD_NET
362 select CMD_PING if CMD_NET
363 select CMD_PXE if CMD_NET
364 select SUPPORT_RAW_INITRD
365 select ENV_VARS_UBOOT_CONFIG
366 select CMD_BOOTI if ARM64
367 select CMD_BOOTZ if ARM && !ARM64
368 imply CMD_MII if NET
369 imply USB_STORAGE
370 imply EFI_PARTITION
371 imply ISO_PARTITION
372 help
373 These are not required but are commonly needed to support a good
374 selection of booting methods. Enable this to improve the capability
375 of U-Boot to boot various images. Currently much functionality is
376 tied to enabling the command that exercises it.
377
Simon Glass08ad13e2022-04-24 23:31:06 -0600378config BOOTSTD
379 bool "Standard boot support"
380 default y
381 depends on DM && OF_CONTROL && BLK
382 help
383 U-Boot supports a standard way of locating something to boot,
384 typically an Operating System such as Linux, provided by a distro such
385 as Arch Linux or Debian. Enable this to support iterating through
386 available bootdevs and using bootmeths to find bootflows suitable for
387 booting.
388
389 Standard boot is not a standard way of booting, just a framework
390 within U-Boot for supporting all the different ways that exist.
391
392 Terminology:
393
394 - bootdev - a device which can hold a distro (e.g. MMC)
395 - bootmeth - a method to scan a bootdev to find bootflows (owned by
396 U-Boot)
397 - bootflow - a description of how to boot (owned by the distro)
398
Simon Glassbc993e52022-10-20 18:23:13 -0600399config SPL_BOOTSTD
Simon Glass4aa874f2023-02-22 09:33:58 -0700400 bool "Standard boot support in SPL"
Simon Glassbc993e52022-10-20 18:23:13 -0600401 depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK
402 default y if VPL
403 help
404 This enables standard boot in SPL. This is neeeded so that VBE
405 (Verified Boot for Embedded) can be used, since it depends on standard
406 boot. It is enabled by default since the main purpose of VPL is to
407 handle the firmware part of VBE.
408
409config VPL_BOOTSTD
410 bool "Standard boot support in VPL"
411 depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK
412 default y
413 help
414 This enables standard boot in SPL. This is neeeded so that VBE
415 (Verified Boot for Embedded) can be used, since it depends on standard
416 boot. It is enabled by default since the main purpose of VPL is to
417 handle the firmware part of VBE.
418
Simon Glassad8ec372022-04-24 23:31:13 -0600419if BOOTSTD
420
Simon Glass78c79dd2023-02-22 14:06:23 -0700421config BOOTSTD_FULL
422 bool "Enhanced features for standard boot"
423 default y if SANDBOX
424 help
425 This enables various useful features for standard boot, which are not
426 essential for operation:
427
428 - bootdev, bootmeth commands
429 - extra features in the bootflow command
430 - support for selecting the ordering of bootmeths ("bootmeth order")
431 - support for selecting the ordering of bootdevs using the devicetree
432 as well as the "boot_targets" environment variable
433
Simon Glass2e5161eb2023-01-28 15:00:21 -0700434config BOOTSTD_DEFAULTS
435 bool "Select some common defaults for standard boot"
436 depends on BOOTSTD
437 imply USE_BOOTCOMMAND
Simon Glass054d0182023-03-24 16:58:13 -0400438 select BOOT_DEFAULTS
Simon Glassdb92e782023-05-10 16:34:47 -0600439 select BOOTMETH_DISTRO
Simon Glass2e5161eb2023-01-28 15:00:21 -0700440 help
441 These are not required but are commonly needed to support a good
442 selection of booting methods. Enable this to improve the capability
443 of U-Boot to boot various images.
444
Simon Glassbe661cb2022-04-24 23:31:27 -0600445config BOOTSTD_BOOTCOMMAND
446 bool "Use bootstd to boot"
447 default y if !DISTRO_DEFAULTS
448 help
449 Enable this to select a default boot-command suitable for booting
450 with standard boot. This can be overridden by the board if needed,
451 but the default command should be enough for most boards which use
452 standard boot.
453
454 For now this is only selected if distro boot is NOT used, since
455 standard boot does not support all of the features of distro boot
456 yet.
457
Simon Glass4f8633d2022-07-30 15:52:21 -0600458config BOOTMETH_GLOBAL
459 bool
460 help
461 Add support for global bootmeths. This feature is used by VBE and
462 EFI bootmgr, since they take full control over which bootdevs are
463 selected to boot.
464
Simon Glassd74e62a2023-07-12 09:04:45 -0600465config BOOTMETH_CROS
466 bool "Bootdev support for Chromium OS"
Simon Glass18700262023-07-30 11:17:02 -0600467 depends on X86 || ARM || SANDBOX
468 default y if !ARM
Simon Glassd7d3a972023-08-24 13:55:45 -0600469 select EFI_PARTITION
470 select PARTITION_TYPE_GUID
471 select PARTITION_UUIDS
Simon Glassd74e62a2023-07-12 09:04:45 -0600472 help
473 Enables support for booting Chromium OS using bootdevs. This uses the
474 kernel A slot and obtains the kernel command line from the parameters
475 provided there.
476
477 Note that only x86 devices are supported at present.
478
Simon Glassb71d7f72023-05-10 16:34:46 -0600479config BOOTMETH_EXTLINUX
480 bool "Bootdev support for extlinux boot"
John Keeping9b60a172022-07-28 11:19:15 +0100481 select PXE_UTILS
Simon Glassad8ec372022-04-24 23:31:13 -0600482 default y
483 help
Simon Glassb71d7f72023-05-10 16:34:46 -0600484 Enables support for extlinux boot using bootdevs. This makes the
Simon Glassad8ec372022-04-24 23:31:13 -0600485 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
486 they scan.
487
Simon Glassb71d7f72023-05-10 16:34:46 -0600488 The specification for this filed is here:
489
490 https://uapi-group.org/specifications/specs/boot_loader_specification/
491
Simon Glassad8ec372022-04-24 23:31:13 -0600492 This provides a way to try out standard boot on an existing boot flow.
493
Simon Glassb71d7f72023-05-10 16:34:46 -0600494config BOOTMETH_EXTLINUX_PXE
495 bool "Bootdev support for extlinux boot over network"
Simon Glass83144612022-04-24 23:31:16 -0600496 depends on CMD_PXE && CMD_NET && DM_ETH
497 default y
498 help
Simon Glassb71d7f72023-05-10 16:34:46 -0600499 Enables support for extlinux boot using bootdevs. This makes the
Simon Glass83144612022-04-24 23:31:16 -0600500 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
501
Simon Glassb71d7f72023-05-10 16:34:46 -0600502 The specification for this file is here:
503
504 https://uapi-group.org/specifications/specs/boot_loader_specification/
505
Simon Glass83144612022-04-24 23:31:16 -0600506 This provides a way to try out standard boot on an existing boot flow.
507
Simon Glass66f62552022-04-24 23:31:17 -0600508config BOOTMETH_EFILOADER
509 bool "Bootdev support for EFI boot"
Simon Glassdb92e782023-05-10 16:34:47 -0600510 depends on EFI_LOADER
Simon Glass66f62552022-04-24 23:31:17 -0600511 default y
512 help
513 Enables support for EFI boot using bootdevs. This makes the
514 bootdevs look for a 'boot<arch>.efi' on each filesystem
515 they scan. The resulting file is booted after enabling U-Boot's
516 EFI loader support.
517
518 The <arch> depends on the architecture of the board:
519
520 aa64 - aarch64 (ARM 64-bit)
521 arm - ARM 32-bit
522 ia32 - x86 32-bit
523 x64 - x86 64-bit
524 riscv32 - RISC-V 32-bit
525 riscv64 - RISC-V 64-bit
526
527 This provides a way to try out standard boot on an existing boot flow.
528
Simon Glass0a9f4262022-07-30 15:52:32 -0600529config BOOTMETH_VBE
530 bool "Bootdev support for Verified Boot for Embedded"
531 depends on FIT
532 default y
533 select BOOTMETH_GLOBAL
Tom Rini7d3684a2023-01-16 15:46:49 -0500534 select EVENT
Simon Glass0a9f4262022-07-30 15:52:32 -0600535 help
536 Enables support for VBE boot. This is a standard boot method which
537 supports selection of various firmware components, seleciton of an OS to
538 boot as well as updating these using fwupd.
539
Simon Glassdb92e782023-05-10 16:34:47 -0600540config BOOTMETH_DISTRO
541 bool # Options needed to boot any distro
542 select BOOTMETH_SCRIPT # E.g. Armbian uses scripts
543 select BOOTMETH_EXTLINUX # E.g. Debian uses these
544 select BOOTMETH_EXTLINUX_PXE if CMD_PXE && CMD_NET && DM_ETH
545 select BOOTMETH_EFILOADER if EFI_LOADER # E.g. Ubuntu uses this
546
Simon Glassbc993e52022-10-20 18:23:13 -0600547config SPL_BOOTMETH_VBE
548 bool "Bootdev support for Verified Boot for Embedded (SPL)"
549 depends on SPL && FIT
Tom Rini7d3684a2023-01-16 15:46:49 -0500550 select EVENT
Simon Glassbc993e52022-10-20 18:23:13 -0600551 default y if VPL
552 help
553 Enables support for VBE boot. This is a standard boot method which
554 supports selection of various firmware components, seleciton of an OS to
555 boot as well as updating these using fwupd.
556
557config VPL_BOOTMETH_VBE
558 bool "Bootdev support for Verified Boot for Embedded (VPL)"
559 depends on VPL && FIT
Tom Rini7d3684a2023-01-16 15:46:49 -0500560 select EVENT
Simon Glassbc993e52022-10-20 18:23:13 -0600561 default y
562 help
563 Enables support for VBE boot. This is a standard boot method which
564 supports selection of various firmware components, seleciton of an OS to
565 boot as well as updating these using fwupd.
566
Simon Glassd0af04c2022-07-30 15:52:33 -0600567if BOOTMETH_VBE
568
Simon Glass513eeed2023-02-22 09:33:52 -0700569config BOOTMETH_VBE_REQUEST
570 bool "Support for serving VBE OS requests"
571 default y
572 help
573 Enables support for looking that the requests made by the
574 Operating System being booted. These requests result in additions to
575 the device tree /chosen node, added during the device tree fixup
576 phase.
577
578config SPL_BOOTMETH_VBE_REQUEST
579 bool "Support for serving VBE OS requests (SPL)"
580 depends on SPL
581 help
582 Enables support for looking that the requests made by the
583 Operating System being booted. These requests result in additions to
584 the device tree /chosen node, added during the device tree fixup
585 phase.
586
587 This is only useful if you are booting an OS direct from SPL.
588
Simon Glassd0af04c2022-07-30 15:52:33 -0600589config BOOTMETH_VBE_SIMPLE
590 bool "Bootdev support for VBE 'simple' method"
591 default y
592 help
593 Enables support for VBE 'simple' boot. This allows updating a single
594 firmware image in boot media such as MMC. It does not support any sort
595 of rollback, recovery or A/B boot.
596
Simon Glassbc993e52022-10-20 18:23:13 -0600597config BOOTMETH_VBE_SIMPLE_OS
598 bool "Bootdev support for VBE 'simple' method OS phase"
599 default y
600 help
601 Enables support for the OS parts of VBE 'simple' boot. This includes
602 fixing up the device tree with the required VBE information, ready
603 for booting into the OS. This option is only enabled for U-Boot
604 proper, since it is the phase where device tree fixups happen.
605
606config SPL_BOOTMETH_VBE_SIMPLE
607 bool "Bootdev support for VBE 'simple' method (SPL)"
608 depends on SPL
609 default y if VPL
610 help
611 Enables support for VBE 'simple' boot. This allows updating a single
612 firmware image in boot media such as MMC. It does not support any sort
613 of rollback, recovery or A/B boot.
614
615config VPL_BOOTMETH_VBE_SIMPLE
616 bool "Bootdev support for VBE 'simple' method (VPL)"
617 depends on VPL
618 default y
619 help
620 Enables support for VBE 'simple' boot. This allows updating a single
621 firmware image in boot media such as MMC. It does not support any sort
622 of rollback, recovery or A/B boot.
623
624config SPL_BOOTMETH_VBE_SIMPLE_FW
625 bool "Bootdev support for VBE 'simple' method firmware phase (SPL)"
626 depends on VPL
627 default y
628 help
629 Enables support for the firmware parts of VBE 'simple' boot. This
630 includes an SPL loader which locates the correct U-Boot to boot into.
631 This option should really only be enabled for VPL, since it is the
632 phase where the SPL + U-Boot decision should be made. But for now,
633 SPL does its own FIT-configuration selection.
634
635config VPL_BOOTMETH_VBE_SIMPLE_FW
636 bool "Bootdev support for VBE 'simple' method firmware phase (VPL)"
637 depends on VPL
638 default y
639 help
640 Enables support for the firmware parts of VBE 'simple' boot. This
641 includes an SPL loader which locates the correct SPL to boot into.
642 This option enabled for VPL, since it is the phase where the SPL
643 decision is made.
644
Simon Glassd0af04c2022-07-30 15:52:33 -0600645endif # BOOTMETH_VBE
646
Simon Glassd8adbe92023-01-06 08:52:36 -0600647config EXPO
648 bool "Support for expos - groups of scenes displaying a UI"
Simon Glass389a4582023-01-28 15:00:18 -0700649 depends on VIDEO
Simon Glassd8adbe92023-01-06 08:52:36 -0600650 default y if BOOTMETH_VBE
651 help
652 An expo is a way of presenting and collecting information from the
653 user. It consists of a collection of 'scenes' of which only one is
654 presented at a time. An expo is typically used to show a boot menu
655 and allow settings to be changed.
656
657 The expo can be presented in graphics form using a vidconsole, or in
658 text form on a serial console.
659
Simon Glass423994e2022-04-24 23:31:20 -0600660config BOOTMETH_SANDBOX
661 def_bool y
662 depends on SANDBOX
663 help
664 This is a sandbox bootmeth driver used for testing. It always returns
665 -ENOTSUPP when attempting to boot.
666
Simon Glass7e03e742022-04-24 23:31:22 -0600667config BOOTMETH_SCRIPT
668 bool "Bootdev support for U-Boot scripts"
669 default y if BOOTSTD_FULL
Simon Glassb4b7ebe2023-05-05 20:03:05 -0600670 select HUSH_PARSER
Simon Glass7e03e742022-04-24 23:31:22 -0600671 help
672 Enables support for booting a distro via a U-Boot script. This makes
673 the bootdevs look for a 'boot/boot.scr' file which can be used to
674 boot the distro.
675
676 This provides a way to try out standard boot on an existing boot flow.
677 It is not enabled by default to save space.
678
Simon Glassad8ec372022-04-24 23:31:13 -0600679endif
680
Simon Glassb45b1632020-09-10 20:21:13 -0600681config LEGACY_IMAGE_FORMAT
682 bool "Enable support for the legacy image format"
Andrew Davis98a22d02022-05-04 15:52:27 -0500683 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
Simon Glassb45b1632020-09-10 20:21:13 -0600684 help
685 This option enables the legacy image format. It is enabled by
686 default for backward compatibility, unless FIT_SIGNATURE is
687 set where it is disabled so that unsigned images cannot be
688 loaded. If a board needs the legacy image format support in this
689 case, enable it here.
690
Simon Glassf11d6132020-09-10 20:21:19 -0600691config SUPPORT_RAW_INITRD
692 bool "Enable raw initrd images"
693 help
694 Note, defining the SUPPORT_RAW_INITRD allows user to supply
695 kernel with raw initrd images. The syntax is slightly different, the
696 address of the initrd must be augmented by it's size, in the following
697 format: "<initrd address>:<initrd size>".
698
Simon Glassb45b1632020-09-10 20:21:13 -0600699config OF_BOARD_SETUP
700 bool "Set up board-specific details in device tree before boot"
701 depends on OF_LIBFDT
702 help
703 This causes U-Boot to call ft_board_setup() before booting into
704 the Operating System. This function can set up various
705 board-specific information in the device tree for use by the OS.
706 The device tree is then passed to the OS.
707
708config OF_SYSTEM_SETUP
709 bool "Set up system-specific details in device tree before boot"
710 depends on OF_LIBFDT
711 help
712 This causes U-Boot to call ft_system_setup() before booting into
713 the Operating System. This function can set up various
714 system-specific information in the device tree for use by the OS.
715 The device tree is then passed to the OS.
716
717config OF_STDOUT_VIA_ALIAS
718 bool "Update the device-tree stdout alias from U-Boot"
719 depends on OF_LIBFDT
720 help
721 This uses U-Boot's serial alias from the aliases node to update
722 the device tree passed to the OS. The "linux,stdout-path" property
723 in the chosen node is set to point to the correct serial node.
724 This option currently references CONFIG_CONS_INDEX, which is
725 incorrect when used with device tree as this option does not
726 exist / should not be used.
727
Simon Glass72cc5382022-10-20 18:22:39 -0600728config HAVE_TEXT_BASE
Simon Glassb45b1632020-09-10 20:21:13 -0600729 bool
730 depends on !NIOS2 && !XTENSA
731 depends on !EFI_APP
732 default y
733
Simon Glass72cc5382022-10-20 18:22:39 -0600734config TEXT_BASE
735 depends on HAVE_TEXT_BASE
Tom Rini63471d52021-07-09 10:39:21 -0400736 default 0x0 if POSITION_INDEPENDENT
Simon Glassb45b1632020-09-10 20:21:13 -0600737 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
Icenowy Zheng711fab32022-01-29 10:23:09 -0500738 default 0x81700000 if MACH_SUNIV
739 default 0x2a000000 if MACH_SUN9I
Andre Przywaraa2860fb2022-07-03 00:47:20 +0100740 default 0x4a000000 if SUNXI_MINIMUM_DRAM_MB >= 256
741 default 0x42e00000 if SUNXI_MINIMUM_DRAM_MB >= 64
Simon Glassb45b1632020-09-10 20:21:13 -0600742 hex "Text Base"
743 help
744 The address in memory that U-Boot will be running from, initially.
745
Tom Rini03becca2022-03-24 17:18:05 -0400746config HAVE_SYS_MONITOR_BASE
747 bool
748 depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \
Tom Rini57f2c292022-07-23 13:05:01 -0400749 || ENV_IS_IN_FLASH || MTD_NOR_FLASH
Tom Rini03becca2022-03-24 17:18:05 -0400750 depends on !EFI_APP
751 default y
752
753config SYS_MONITOR_BASE
754 depends on HAVE_SYS_MONITOR_BASE
755 hex "Physical start address of boot monitor code"
Simon Glass72cc5382022-10-20 18:22:39 -0600756 default TEXT_BASE
Tom Rini03becca2022-03-24 17:18:05 -0400757 help
758 The physical start address of boot monitor code (which is the same as
Tom Rini6a5dccc2022-11-16 13:10:41 -0500759 CONFIG_TEXT_BASE when linking) and the same as CFG_SYS_FLASH_BASE
Tom Rini03becca2022-03-24 17:18:05 -0400760 when booting from flash.
761
762config SPL_SYS_MONITOR_BASE
763 depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE
764 hex "Physical start address of SPL monitor code"
765 default SPL_TEXT_BASE
766
767config TPL_SYS_MONITOR_BASE
768 depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE
769 hex "Physical start address of TPL monitor code"
770
Tom Rini8c70baa2021-12-14 13:36:40 -0500771config DYNAMIC_SYS_CLK_FREQ
772 bool "Determine CPU clock frequency at run-time"
773 help
774 Implement a get_board_sys_clk function that will determine the CPU
775 clock frequency at run time, rather than define it statically.
776
Simon Glassb45b1632020-09-10 20:21:13 -0600777config SYS_CLK_FREQ
Tom Rini8c70baa2021-12-14 13:36:40 -0500778 depends on !DYNAMIC_SYS_CLK_FREQ
Simon Glassb45b1632020-09-10 20:21:13 -0600779 int "CPU clock frequency"
Tom Rini8c70baa2021-12-14 13:36:40 -0500780 default 125000000 if ARCH_LS1012A
781 default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \
782 ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3
783 default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240
784 default 66660000 if ARCH_T2080
785 default 33333333 if RCAR_GEN3
786 default 24000000 if ARCH_EXYNOS
787 default 20000000 if RCAR_GEN2
788 default 0
Simon Glassb45b1632020-09-10 20:21:13 -0600789 help
Tom Rini8c70baa2021-12-14 13:36:40 -0500790 A static value for the CPU frequency. Note that if not required
791 for a given SoC, this can be left at 0.
Simon Glassb45b1632020-09-10 20:21:13 -0600792
793config ARCH_FIXUP_FDT_MEMORY
794 bool "Enable arch_fixup_memory_banks() call"
795 default y
796 help
797 Enable FDT memory map syncup before OS boot. This feature can be
798 used for booting OS with different memory setup where the part of
799 the memory location should be used for different purpose.
800
Simon Glassd81f07f2020-11-04 09:57:35 -0700801config CHROMEOS
802 bool "Support booting Chrome OS"
803 help
804 Chrome OS requires U-Boot to set up a table indicating the boot mode
805 (e.g. Developer mode) and a few other things. Enable this if you are
806 booting on a Chromebook to avoid getting an error about an invalid
807 firmware ID.
808
809config CHROMEOS_VBOOT
810 bool "Support Chrome OS verified boot"
811 help
812 This is intended to enable the full Chrome OS verified boot support
813 in U-Boot. It is not actually implemented in the U-Boot source code
814 at present, so this option is always set to 'n'. It allows
815 distinguishing between booting Chrome OS in a basic way (developer
816 mode) and a full boot.
817
Tom Rinieb4f2de2022-06-25 11:02:44 -0400818config SYS_RAMBOOT
819 bool
820
Tom Rini9ff815a2021-08-24 23:11:49 -0400821config RAMBOOT_PBL
822 bool "Freescale PBL(pre-boot loader) image format support"
Tom Rinieb4f2de2022-06-25 11:02:44 -0400823 select SYS_RAMBOOT if PPC
Tom Rini9ff815a2021-08-24 23:11:49 -0400824 help
825 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
826 For more details refer to doc/README.pblimage
827
Tom Rini886e6e32022-03-23 17:20:03 -0400828choice
Tom Rini489f4022022-12-28 10:52:51 -0500829 prompt "Freescale PBL (or predecessor) load location"
Tom Rini886e6e32022-03-23 17:20:03 -0400830 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
831 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
832 && !CMD_NAND)
833
834config SDCARD
Tom Rini489f4022022-12-28 10:52:51 -0500835 bool "Freescale PBL (or similar) is found on SD card"
Tom Rini886e6e32022-03-23 17:20:03 -0400836
837config SPIFLASH
Tom Rini489f4022022-12-28 10:52:51 -0500838 bool "Freescale PBL (or similar) is found on SPI flash"
839
840config NO_PBL
841 bool "Freescale PBL (or similar) is not used in this case"
Tom Rini886e6e32022-03-23 17:20:03 -0400842
843endchoice
844
Tom Rini5989fd42022-06-20 08:07:42 -0400845config FSL_FIXED_MMC_LOCATION
846 bool "PBL MMC is at a fixed location"
847 depends on SDCARD && !RAMBOOT_PBL
848
849config ESDHC_HC_BLK_ADDR
850 def_bool y
851 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
852 help
853 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
854 code length of these soc specify the memory address in block address
855 format. Block length is fixed to 512 bytes as per the SD High
856 Capacity specification.
857
Tom Rini9ff815a2021-08-24 23:11:49 -0400858config SYS_FSL_PBL_PBI
859 string "PBI(pre-boot instructions) commands for the PBL image"
860 depends on RAMBOOT_PBL
861 help
862 PBI commands can be used to configure SoC before it starts the execution.
863 Please refer doc/README.pblimage for more details.
864
865config SYS_FSL_PBL_RCW
866 string "Aadditional RCW (Power on reset configuration) for the PBL image"
867 depends on RAMBOOT_PBL
868 help
869 Enables addition of RCW (Power on reset configuration) in built image.
870 Please refer doc/README.pblimage for more details.
871
Tom Rini94b4fec2022-06-25 11:02:46 -0400872config SYS_BOOT_RAMDISK_HIGH
873 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
874 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
875 def_bool y
Simon Glass65edcd32023-03-24 16:58:12 -0400876 select LMB
Tom Rini94b4fec2022-06-25 11:02:46 -0400877 help
878 Enable initrd_high functionality. If defined then the initrd_high
879 feature is enabled and the boot* ramdisk subcommand is enabled.
880
Simon Glassb45b1632020-09-10 20:21:13 -0600881endmenu # Boot images
882
Simon Glassf111bf72023-03-24 16:58:11 -0400883config DISTRO_DEFAULTS
884 bool "Select defaults suitable for booting general purpose Linux distributions"
Simon Glass054d0182023-03-24 16:58:13 -0400885 select BOOT_DEFAULTS
Simon Glassf111bf72023-03-24 16:58:11 -0400886 select AUTO_COMPLETE
887 select CMDLINE_EDITING
Simon Glassf111bf72023-03-24 16:58:11 -0400888 select CMD_SYSBOOT
Simon Glassf111bf72023-03-24 16:58:11 -0400889 select HUSH_PARSER
Simon Glassf111bf72023-03-24 16:58:11 -0400890 select SYS_LONGHELP
Simon Glassf111bf72023-03-24 16:58:11 -0400891 help
892 Select this to enable various options and commands which are suitable
893 for building u-boot for booting general purpose Linux distributions.
894
Simon Glassd02ddcf2020-09-10 20:21:14 -0600895menu "Boot timing"
896
897config BOOTSTAGE
898 bool "Boot timing and reporting"
899 help
900 Enable recording of boot time while booting. To use it, insert
901 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
902 bootstage.h. Only a single entry is recorded for each ID. You can
903 give the entry a name with bootstage_mark_name(). You can also
904 record elapsed time in a particular stage using bootstage_start()
905 before starting and bootstage_accum() when finished. Bootstage will
906 add up all the accumulated time and report it.
907
908 Normally, IDs are defined in bootstage.h but a small number of
909 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
910 as the ID.
911
912 Calls to show_boot_progress() will also result in log entries but
913 these will not have names.
914
915config SPL_BOOTSTAGE
916 bool "Boot timing and reported in SPL"
Tom Rini0a83cc22022-06-10 23:03:09 -0400917 depends on BOOTSTAGE && SPL
Simon Glassd02ddcf2020-09-10 20:21:14 -0600918 help
919 Enable recording of boot time in SPL. To make this visible to U-Boot
920 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
921 information when SPL finishes and load it when U-Boot proper starts
922 up.
923
924config TPL_BOOTSTAGE
925 bool "Boot timing and reported in TPL"
Tom Rini36a4ca02022-06-08 08:24:39 -0400926 depends on BOOTSTAGE && TPL
Simon Glassd02ddcf2020-09-10 20:21:14 -0600927 help
928 Enable recording of boot time in SPL. To make this visible to U-Boot
929 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
930 information when TPL finishes and load it when U-Boot proper starts
931 up.
932
933config BOOTSTAGE_REPORT
934 bool "Display a detailed boot timing report before booting the OS"
935 depends on BOOTSTAGE
936 help
937 Enable output of a boot time report just before the OS is booted.
938 This shows how long it took U-Boot to go through each stage of the
939 boot process. The report looks something like this:
940
941 Timer summary in microseconds:
942 Mark Elapsed Stage
943 0 0 reset
944 3,575,678 3,575,678 board_init_f start
945 3,575,695 17 arch_cpu_init A9
946 3,575,777 82 arch_cpu_init done
947 3,659,598 83,821 board_init_r start
948 3,910,375 250,777 main_loop
949 29,916,167 26,005,792 bootm_start
950 30,361,327 445,160 start_kernel
951
952config BOOTSTAGE_RECORD_COUNT
953 int "Number of boot stage records to store"
Simon Glass051ddfb2021-02-03 06:00:49 -0700954 depends on BOOTSTAGE
Simon Glassd02ddcf2020-09-10 20:21:14 -0600955 default 30
956 help
957 This is the size of the bootstage record list and is the maximum
958 number of bootstage records that can be recorded.
959
960config SPL_BOOTSTAGE_RECORD_COUNT
961 int "Number of boot stage records to store for SPL"
Simon Glass051ddfb2021-02-03 06:00:49 -0700962 depends on SPL_BOOTSTAGE
Simon Glassd02ddcf2020-09-10 20:21:14 -0600963 default 5
964 help
965 This is the size of the bootstage record list and is the maximum
966 number of bootstage records that can be recorded.
967
968config TPL_BOOTSTAGE_RECORD_COUNT
969 int "Number of boot stage records to store for TPL"
Simon Glass051ddfb2021-02-03 06:00:49 -0700970 depends on TPL_BOOTSTAGE
Simon Glassd02ddcf2020-09-10 20:21:14 -0600971 default 5
972 help
973 This is the size of the bootstage record list and is the maximum
974 number of bootstage records that can be recorded.
975
976config BOOTSTAGE_FDT
977 bool "Store boot timing information in the OS device tree"
978 depends on BOOTSTAGE
979 help
980 Stash the bootstage information in the FDT. A root 'bootstage'
981 node is created with each bootstage id as a child. Each child
982 has a 'name' property and either 'mark' containing the
983 mark time in microseconds, or 'accum' containing the
984 accumulated time for that bootstage id in microseconds.
985 For example:
986
987 bootstage {
988 154 {
989 name = "board_init_f";
990 mark = <3575678>;
991 };
992 170 {
993 name = "lcd";
994 accum = <33482>;
995 };
996 };
997
998 Code in the Linux kernel can find this in /proc/devicetree.
999
1000config BOOTSTAGE_STASH
1001 bool "Stash the boot timing information in memory before booting OS"
1002 depends on BOOTSTAGE
1003 help
1004 Some OSes do not support device tree. Bootstage can instead write
1005 the boot timing information in a binary format at a given address.
1006 This happens through a call to bootstage_stash(), typically in
1007 the CPU's cleanup_before_linux() function. You can use the
1008 'bootstage stash' and 'bootstage unstash' commands to do this on
1009 the command line.
1010
1011config BOOTSTAGE_STASH_ADDR
1012 hex "Address to stash boot timing information"
Tom Rinif18679c2023-08-02 11:09:43 -04001013 default 0x0
Simon Glassd02ddcf2020-09-10 20:21:14 -06001014 help
1015 Provide an address which will not be overwritten by the OS when it
1016 starts, so that it can read this information when ready.
1017
1018config BOOTSTAGE_STASH_SIZE
1019 hex "Size of boot timing stash region"
1020 default 0x1000
1021 help
1022 This should be large enough to hold the bootstage stash. A value of
1023 4096 (4KiB) is normally plenty.
1024
1025config SHOW_BOOT_PROGRESS
1026 bool "Show boot progress in a board-specific manner"
1027 help
1028 Defining this option allows to add some board-specific code (calling
1029 a user-provided function show_boot_progress(int) that enables you to
1030 show the system's boot progress on some display (for example, some
1031 LEDs) on your board. At the moment, the following checkpoints are
1032 implemented:
1033
1034 Legacy uImage format:
1035
1036 Arg Where When
1037 1 common/cmd_bootm.c before attempting to boot an image
1038 -1 common/cmd_bootm.c Image header has bad magic number
1039 2 common/cmd_bootm.c Image header has correct magic number
1040 -2 common/cmd_bootm.c Image header has bad checksum
1041 3 common/cmd_bootm.c Image header has correct checksum
1042 -3 common/cmd_bootm.c Image data has bad checksum
1043 4 common/cmd_bootm.c Image data has correct checksum
1044 -4 common/cmd_bootm.c Image is for unsupported architecture
1045 5 common/cmd_bootm.c Architecture check OK
1046 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
1047 6 common/cmd_bootm.c Image Type check OK
1048 -6 common/cmd_bootm.c gunzip uncompression error
1049 -7 common/cmd_bootm.c Unimplemented compression type
1050 7 common/cmd_bootm.c Uncompression OK
1051 8 common/cmd_bootm.c No uncompress/copy overwrite error
1052 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
1053
1054 9 common/image.c Start initial ramdisk verification
1055 -10 common/image.c Ramdisk header has bad magic number
1056 -11 common/image.c Ramdisk header has bad checksum
1057 10 common/image.c Ramdisk header is OK
1058 -12 common/image.c Ramdisk data has bad checksum
1059 11 common/image.c Ramdisk data has correct checksum
1060 12 common/image.c Ramdisk verification complete, start loading
1061 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
1062 13 common/image.c Start multifile image verification
1063 14 common/image.c No initial ramdisk, no multifile, continue.
1064
1065 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
1066
1067 -30 arch/powerpc/lib/board.c Fatal error, hang the system
1068 -31 post/post.c POST test failed, detected by post_output_backlog()
1069 -32 post/post.c POST test failed, detected by post_run_single()
1070
1071 34 common/cmd_doc.c before loading a Image from a DOC device
1072 -35 common/cmd_doc.c Bad usage of "doc" command
1073 35 common/cmd_doc.c correct usage of "doc" command
1074 -36 common/cmd_doc.c No boot device
1075 36 common/cmd_doc.c correct boot device
1076 -37 common/cmd_doc.c Unknown Chip ID on boot device
1077 37 common/cmd_doc.c correct chip ID found, device available
1078 -38 common/cmd_doc.c Read Error on boot device
1079 38 common/cmd_doc.c reading Image header from DOC device OK
1080 -39 common/cmd_doc.c Image header has bad magic number
1081 39 common/cmd_doc.c Image header has correct magic number
1082 -40 common/cmd_doc.c Error reading Image from DOC device
1083 40 common/cmd_doc.c Image header has correct magic number
1084 41 common/cmd_ide.c before loading a Image from a IDE device
1085 -42 common/cmd_ide.c Bad usage of "ide" command
1086 42 common/cmd_ide.c correct usage of "ide" command
1087 -43 common/cmd_ide.c No boot device
1088 43 common/cmd_ide.c boot device found
1089 -44 common/cmd_ide.c Device not available
1090 44 common/cmd_ide.c Device available
1091 -45 common/cmd_ide.c wrong partition selected
1092 45 common/cmd_ide.c partition selected
1093 -46 common/cmd_ide.c Unknown partition table
1094 46 common/cmd_ide.c valid partition table found
1095 -47 common/cmd_ide.c Invalid partition type
1096 47 common/cmd_ide.c correct partition type
1097 -48 common/cmd_ide.c Error reading Image Header on boot device
1098 48 common/cmd_ide.c reading Image Header from IDE device OK
1099 -49 common/cmd_ide.c Image header has bad magic number
1100 49 common/cmd_ide.c Image header has correct magic number
1101 -50 common/cmd_ide.c Image header has bad checksum
1102 50 common/cmd_ide.c Image header has correct checksum
1103 -51 common/cmd_ide.c Error reading Image from IDE device
1104 51 common/cmd_ide.c reading Image from IDE device OK
1105 52 common/cmd_nand.c before loading a Image from a NAND device
1106 -53 common/cmd_nand.c Bad usage of "nand" command
1107 53 common/cmd_nand.c correct usage of "nand" command
1108 -54 common/cmd_nand.c No boot device
1109 54 common/cmd_nand.c boot device found
1110 -55 common/cmd_nand.c Unknown Chip ID on boot device
1111 55 common/cmd_nand.c correct chip ID found, device available
1112 -56 common/cmd_nand.c Error reading Image Header on boot device
1113 56 common/cmd_nand.c reading Image Header from NAND device OK
1114 -57 common/cmd_nand.c Image header has bad magic number
1115 57 common/cmd_nand.c Image header has correct magic number
1116 -58 common/cmd_nand.c Error reading Image from NAND device
1117 58 common/cmd_nand.c reading Image from NAND device OK
1118
1119 -60 common/env_common.c Environment has a bad CRC, using default
1120
1121 64 net/eth.c starting with Ethernet configuration.
1122 -64 net/eth.c no Ethernet found.
1123 65 net/eth.c Ethernet found.
1124
1125 -80 common/cmd_net.c usage wrong
1126 80 common/cmd_net.c before calling net_loop()
1127 -81 common/cmd_net.c some error in net_loop() occurred
1128 81 common/cmd_net.c net_loop() back without error
1129 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1130 82 common/cmd_net.c trying automatic boot
1131 83 common/cmd_net.c running "source" command
1132 -83 common/cmd_net.c some error in automatic boot or "source" command
1133 84 common/cmd_net.c end without errors
1134
1135 FIT uImage format:
1136
1137 Arg Where When
1138 100 common/cmd_bootm.c Kernel FIT Image has correct format
1139 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1140 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1141 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1142 102 common/cmd_bootm.c Kernel unit name specified
1143 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1144 103 common/cmd_bootm.c Found configuration node
1145 104 common/cmd_bootm.c Got kernel subimage node offset
1146 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1147 105 common/cmd_bootm.c Kernel subimage hash verification OK
1148 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1149 106 common/cmd_bootm.c Architecture check OK
1150 -106 common/cmd_bootm.c Kernel subimage has wrong type
1151 107 common/cmd_bootm.c Kernel subimage type OK
1152 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1153 108 common/cmd_bootm.c Got kernel subimage data/size
1154 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1155 -109 common/cmd_bootm.c Can't get kernel subimage type
1156 -110 common/cmd_bootm.c Can't get kernel subimage comp
1157 -111 common/cmd_bootm.c Can't get kernel subimage os
1158 -112 common/cmd_bootm.c Can't get kernel subimage load address
1159 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1160
1161 120 common/image.c Start initial ramdisk verification
1162 -120 common/image.c Ramdisk FIT image has incorrect format
1163 121 common/image.c Ramdisk FIT image has correct format
1164 122 common/image.c No ramdisk subimage unit name, using configuration
1165 -122 common/image.c Can't get configuration for ramdisk subimage
1166 123 common/image.c Ramdisk unit name specified
1167 -124 common/image.c Can't get ramdisk subimage node offset
1168 125 common/image.c Got ramdisk subimage node offset
1169 -125 common/image.c Ramdisk subimage hash verification failed
1170 126 common/image.c Ramdisk subimage hash verification OK
1171 -126 common/image.c Ramdisk subimage for unsupported architecture
1172 127 common/image.c Architecture check OK
1173 -127 common/image.c Can't get ramdisk subimage data/size
1174 128 common/image.c Got ramdisk subimage data/size
1175 129 common/image.c Can't get ramdisk load address
1176 -129 common/image.c Got ramdisk load address
1177
1178 -130 common/cmd_doc.c Incorrect FIT image format
1179 131 common/cmd_doc.c FIT image format OK
1180
1181 -140 common/cmd_ide.c Incorrect FIT image format
1182 141 common/cmd_ide.c FIT image format OK
1183
1184 -150 common/cmd_nand.c Incorrect FIT image format
1185 151 common/cmd_nand.c FIT image format OK
1186
Marek Vasut98154342021-10-23 03:06:03 +02001187config SPL_SHOW_BOOT_PROGRESS
Jan Kiszka5780edb2021-11-03 15:09:36 +01001188 bool "Show boot progress in a board-specific manner in SPL"
Marek Vasut98154342021-10-23 03:06:03 +02001189 depends on SPL
1190 help
1191 Defining this option allows to add some board-specific code (calling
1192 a user-provided function show_boot_progress(int) that enables you to
1193 show the system's boot progress on some display (for example, some
1194 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1195
Simon Glassd02ddcf2020-09-10 20:21:14 -06001196endmenu
1197
Simon Glasseebed782020-09-10 20:21:15 -06001198menu "Boot media"
1199
1200config NOR_BOOT
1201 bool "Support for booting from NOR flash"
1202 depends on NOR
1203 help
1204 Enabling this will make a U-Boot binary that is capable of being
1205 booted via NOR. In this case we will enable certain pinmux early
1206 as the ROM only partially sets up pinmux. We also default to using
1207 NOR for environment.
1208
1209config NAND_BOOT
1210 bool "Support for booting from NAND flash"
Simon Glasseebed782020-09-10 20:21:15 -06001211 imply MTD_RAW_NAND
1212 help
1213 Enabling this will make a U-Boot binary that is capable of being
1214 booted via NAND flash. This is not a must, some SoCs need this,
1215 some not.
1216
1217config ONENAND_BOOT
1218 bool "Support for booting from ONENAND"
Simon Glasseebed782020-09-10 20:21:15 -06001219 imply MTD_RAW_NAND
1220 help
1221 Enabling this will make a U-Boot binary that is capable of being
1222 booted via ONENAND. This is not a must, some SoCs need this,
1223 some not.
1224
1225config QSPI_BOOT
1226 bool "Support for booting from QSPI flash"
Simon Glasseebed782020-09-10 20:21:15 -06001227 help
1228 Enabling this will make a U-Boot binary that is capable of being
1229 booted via QSPI flash. This is not a must, some SoCs need this,
1230 some not.
1231
1232config SATA_BOOT
1233 bool "Support for booting from SATA"
Simon Glasseebed782020-09-10 20:21:15 -06001234 help
1235 Enabling this will make a U-Boot binary that is capable of being
1236 booted via SATA. This is not a must, some SoCs need this,
1237 some not.
1238
1239config SD_BOOT
1240 bool "Support for booting from SD/EMMC"
Simon Glasseebed782020-09-10 20:21:15 -06001241 help
1242 Enabling this will make a U-Boot binary that is capable of being
1243 booted via SD/EMMC. This is not a must, some SoCs need this,
1244 some not.
1245
Tom Rinia43bf4e2021-12-11 14:55:50 -05001246config SD_BOOT_QSPI
1247 bool "Support for booting from SD/EMMC and enable QSPI"
1248 help
1249 Enabling this will make a U-Boot binary that is capable of being
1250 booted via SD/EMMC while enabling QSPI on the platform as well. This
1251 is not a must, some SoCs need this, some not.
1252
Simon Glasseebed782020-09-10 20:21:15 -06001253config SPI_BOOT
1254 bool "Support for booting from SPI flash"
Simon Glasseebed782020-09-10 20:21:15 -06001255 help
1256 Enabling this will make a U-Boot binary that is capable of being
1257 booted via SPI flash. This is not a must, some SoCs need this,
1258 some not.
1259
1260endmenu
1261
Simon Glasse9d54d72020-09-10 20:21:16 -06001262menu "Autoboot options"
1263
1264config AUTOBOOT
1265 bool "Autoboot"
1266 default y
1267 help
1268 This enables the autoboot. See doc/README.autoboot for detail.
1269
Simon Glass1b6cbaa2020-09-10 20:21:17 -06001270config BOOTDELAY
1271 int "delay in seconds before automatically booting"
1272 default 2
1273 depends on AUTOBOOT
1274 help
1275 Delay before automatically running bootcmd;
1276 set to 0 to autoboot with no delay, but you can stop it by key input.
1277 set to -1 to disable autoboot.
1278 set to -2 to autoboot with no delay and not check for abort
1279
1280 If this value is >= 0 then it is also used for the default delay
1281 before starting the default entry in bootmenu. If it is < 0 then
1282 a default value of 10s is used.
1283
1284 See doc/README.autoboot for details.
1285
Simon Glasse9d54d72020-09-10 20:21:16 -06001286config AUTOBOOT_KEYED
1287 bool "Stop autobooting via specific input key / string"
Simon Glasse9d54d72020-09-10 20:21:16 -06001288 help
1289 This option enables stopping (aborting) of the automatic
1290 boot feature only by issuing a specific input key or
1291 string. If not enabled, any input key will abort the
1292 U-Boot automatic booting process and bring the device
1293 to the U-Boot prompt for user input.
1294
Steffen Jaeckeldfc97322021-07-08 15:57:38 +02001295config AUTOBOOT_FLUSH_STDIN
1296 bool "Enable flushing stdin before starting to read the password"
1297 depends on AUTOBOOT_KEYED && !SANDBOX
1298 help
1299 When this option is enabled stdin buffer will be flushed before
1300 starting to read the password.
1301 This can't be enabled for the sandbox as flushing stdin would
1302 break the autoboot unit tests.
1303
Simon Glasse9d54d72020-09-10 20:21:16 -06001304config AUTOBOOT_PROMPT
1305 string "Autoboot stop prompt"
1306 depends on AUTOBOOT_KEYED
1307 default "Autoboot in %d seconds\\n"
1308 help
1309 This string is displayed before the boot delay selected by
1310 CONFIG_BOOTDELAY starts. If it is not defined there is no
1311 output indicating that autoboot is in progress.
1312
1313 Note that this define is used as the (only) argument to a
1314 printf() call, so it may contain '%' format specifications,
1315 provided that it also includes, sepearated by commas exactly
1316 like in a printf statement, the required arguments. It is
1317 the responsibility of the user to select only such arguments
1318 that are valid in the given context.
1319
1320config AUTOBOOT_ENCRYPTION
1321 bool "Enable encryption in autoboot stopping"
1322 depends on AUTOBOOT_KEYED
1323 help
1324 This option allows a string to be entered into U-Boot to stop the
Steffen Jaeckel6aa6bfb2021-07-08 15:57:35 +02001325 autoboot.
1326 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1327 or not.
1328 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1329 to the crypt-based functionality and be compared against the
1330 string in the environment variable 'bootstopkeycrypt'.
1331 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1332 and compared against the hash in the environment variable
1333 'bootstopkeysha256'.
1334 If it matches in either case then boot stops and
1335 a command-line prompt is presented.
Simon Glasse9d54d72020-09-10 20:21:16 -06001336 This provides a way to ship a secure production device which can also
1337 be accessed at the U-Boot command line.
1338
Steffen Jaeckel28be70d2021-07-08 15:57:39 +02001339config AUTOBOOT_SHA256_FALLBACK
1340 bool "Allow fallback from crypt-hashed password to sha256"
1341 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1342 help
1343 This option adds support to fall back from crypt-hashed
1344 passwords to checking a SHA256 hashed password in case the
1345 'bootstopusesha256' environment variable is set to 'true'.
1346
Simon Glasse9d54d72020-09-10 20:21:16 -06001347config AUTOBOOT_DELAY_STR
1348 string "Delay autobooting via specific input key / string"
1349 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1350 help
1351 This option delays the automatic boot feature by issuing
1352 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1353 or the environment variable "bootdelaykey" is specified
1354 and this string is received from console input before
1355 autoboot starts booting, U-Boot gives a command prompt. The
1356 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1357 used, otherwise it never times out.
1358
1359config AUTOBOOT_STOP_STR
1360 string "Stop autobooting via specific input key / string"
1361 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
1362 help
1363 This option enables stopping (aborting) of the automatic
1364 boot feature only by issuing a specific input key or
1365 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1366 variable "bootstopkey" is specified and this string is
1367 received from console input before autoboot starts booting,
1368 U-Boot gives a command prompt. The U-Boot prompt never
1369 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1370
1371config AUTOBOOT_KEYED_CTRLC
1372 bool "Enable Ctrl-C autoboot interruption"
1373 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
Simon Glasse9d54d72020-09-10 20:21:16 -06001374 help
1375 This option allows for the boot sequence to be interrupted
1376 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1377 Setting this variable provides an escape sequence from the
1378 limited "password" strings.
1379
Steffen Jaeckel792a13f2021-07-08 15:57:37 +02001380config AUTOBOOT_NEVER_TIMEOUT
1381 bool "Make the password entry never time-out"
1382 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
1383 help
1384 This option removes the timeout from the password entry
1385 when the user first presses the <Enter> key before entering
1386 any other character.
1387
Steffen Jaeckel6aa6bfb2021-07-08 15:57:35 +02001388config AUTOBOOT_STOP_STR_ENABLE
1389 bool "Enable fixed string to stop autobooting"
1390 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
1391 help
1392 This option enables the feature to add a fixed stop
1393 string that is defined at compile time.
1394 In every case it will be tried to load the stop
1395 string from the environment.
1396 In case this is enabled and there is no stop string
1397 in the environment, this will be used as default value.
1398
1399config AUTOBOOT_STOP_STR_CRYPT
1400 string "Stop autobooting via crypt-hashed password"
1401 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1402 help
1403 This option adds the feature to only stop the autobooting,
1404 and therefore boot into the U-Boot prompt, when the input
1405 string / password matches a values that is hashed via
1406 one of the supported crypt-style password hashing options
1407 and saved in the environment variable "bootstopkeycrypt".
1408
Simon Glasse9d54d72020-09-10 20:21:16 -06001409config AUTOBOOT_STOP_STR_SHA256
Steffen Jaeckele1788f92021-07-08 15:57:40 +02001410 string "Stop autobooting via SHA256 hashed password"
Steffen Jaeckel6aa6bfb2021-07-08 15:57:35 +02001411 depends on AUTOBOOT_STOP_STR_ENABLE
Simon Glasse9d54d72020-09-10 20:21:16 -06001412 help
1413 This option adds the feature to only stop the autobooting,
1414 and therefore boot into the U-Boot prompt, when the input
1415 string / password matches a values that is encypted via
Joel Peshkin8b7bf532020-11-21 17:18:59 -08001416 a SHA256 hash and saved in the environment variable
1417 "bootstopkeysha256". If the value in that variable
1418 includes a ":", the portion prior to the ":" will be treated
1419 as a salt value.
Simon Glasse9d54d72020-09-10 20:21:16 -06001420
1421config AUTOBOOT_USE_MENUKEY
1422 bool "Allow a specify key to run a menu from the environment"
1423 depends on !AUTOBOOT_KEYED
1424 help
1425 If a specific key is pressed to stop autoboot, then the commands in
1426 the environment variable 'menucmd' are executed before boot starts.
1427
1428config AUTOBOOT_MENUKEY
1429 int "ASCII value of boot key to show a menu"
1430 default 0
1431 depends on AUTOBOOT_USE_MENUKEY
1432 help
1433 If this key is pressed to stop autoboot, then the commands in the
1434 environment variable 'menucmd' will be executed before boot starts.
1435 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1436 this action.
1437
1438config AUTOBOOT_MENU_SHOW
1439 bool "Show a menu on boot"
1440 depends on CMD_BOOTMENU
1441 help
1442 This enables the boot menu, controlled by environment variables
1443 defined by the board. The menu starts after running the 'preboot'
1444 environmnent variable (if enabled) and before handling the boot delay.
Peter Robinson16e0b8f2023-08-18 15:54:10 +01001445 See doc/usage/cmd/bootmenu.rst for more details.
Simon Glasse9d54d72020-09-10 20:21:16 -06001446
Masahisa Kojima97cbcc42022-05-26 19:09:38 +09001447config BOOTMENU_DISABLE_UBOOT_CONSOLE
1448 bool "Disallow bootmenu to enter the U-Boot console"
1449 depends on AUTOBOOT_MENU_SHOW
1450 help
1451 If this option is enabled, user can not enter the U-Boot console from
1452 bootmenu. It increases the system security.
1453
Tom Rinia45a3ef2022-03-11 09:12:04 -05001454config BOOT_RETRY
1455 bool "Boot retry feature"
1456 help
1457 Allow for having the U-Boot command prompt time out and attempt
1458 to boot again. If the environment variable "bootretry" is found then
1459 its value is used, otherwise the retry timeout is
1460 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1461 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1462
1463config BOOT_RETRY_TIME
1464 int "Timeout in seconds before attempting to boot again"
1465 depends on BOOT_RETRY
1466 help
1467 Time in seconds before the U-Boot prompt will timeout and boot will
1468 be attempted again.
1469
1470config BOOT_RETRY_MIN
1471 int "Minimum timeout in seconds for 'bootretry'"
1472 depends on BOOT_RETRY
1473 default BOOT_RETRY_TIME
1474 help
1475 The minimum time in seconds that "bootretry" can be set to.
1476
1477config RESET_TO_RETRY
1478 bool "Reset the board to retry autoboot"
1479 depends on BOOT_RETRY
1480 help
1481 After the countdown timed out, the board will be reset to restart
1482 again.
1483
Simon Glasse9d54d72020-09-10 20:21:16 -06001484endmenu
1485
Philippe Reynesd28484e2022-03-28 22:56:59 +02001486menu "Image support"
1487
1488config IMAGE_PRE_LOAD
1489 bool "Image pre-load support"
1490 help
1491 Enable an image pre-load stage in the SPL.
1492 This pre-load stage allows to do some manipulation
1493 or check (for example signature check) on an image
1494 before launching it.
1495
1496config SPL_IMAGE_PRE_LOAD
1497 bool "Image pre-load support within SPL"
1498 depends on SPL && IMAGE_PRE_LOAD
1499 help
1500 Enable an image pre-load stage in the SPL.
1501 This pre-load stage allows to do some manipulation
1502 or check (for example signature check) on an image
1503 before launching it.
1504
1505config IMAGE_PRE_LOAD_SIG
1506 bool "Image pre-load signature support"
1507 depends on IMAGE_PRE_LOAD
1508 select FIT_SIGNATURE
1509 select RSA
1510 select RSA_VERIFY_WITH_PKEY
1511 help
1512 Enable signature check support in the pre-load stage.
1513 For this feature a very simple header is added before
1514 the image with few fields:
1515 - a magic
1516 - the image size
1517 - the signature
1518 All other information (header size, type of signature,
1519 ...) are provided in the node /image/pre-load/sig of
1520 u-boot.
1521
1522config SPL_IMAGE_PRE_LOAD_SIG
1523 bool "Image pre-load signature support witin SPL"
1524 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1525 select SPL_FIT_SIGNATURE
1526 select SPL_RSA
1527 select SPL_RSA_VERIFY_WITH_PKEY
1528 help
1529 Enable signature check support in the pre-load stage in the SPL.
1530 For this feature a very simple header is added before
1531 the image with few fields:
1532 - a magic
1533 - the image size
1534 - the signature
1535 All other information (header size, type of signature,
1536 ...) are provided in the node /image/pre-load/sig of
1537 u-boot.
1538
1539endmenu
1540
Simon Glass27367192023-09-14 10:55:46 -06001541if OF_LIBFDT
1542
1543menu "Devicetree fixup"
1544
1545config FDT_SIMPLEFB
1546 bool "FDT tools for simplefb support"
1547 help
1548 Enable the fdt tools to manage the simple fb nodes in device tree.
1549 These functions can be used by board to indicate to the OS
1550 the presence of the simple frame buffer with associated reserved
1551 memory
1552
1553endmenu
1554
1555endif # OF_LIBFDT
1556
Simon Glass5e958642020-09-10 20:21:18 -06001557config USE_BOOTARGS
1558 bool "Enable boot arguments"
1559 help
1560 Provide boot arguments to bootm command. Boot arguments are specified
1561 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1562 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1563 will be undefined and won't take any space in U-Boot image.
1564
1565config BOOTARGS
1566 string "Boot arguments"
1567 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1568 help
1569 This can be used to pass arguments to the bootm command. The value of
1570 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1571 this value will also override the "chosen" node in FDT blob.
1572
Simon Glass529e2082020-11-05 10:33:48 -07001573config BOOTARGS_SUBST
1574 bool "Support substituting strings in boot arguments"
1575 help
1576 This allows substituting string values in the boot arguments. These
1577 are applied after the commandline has been built.
1578
1579 One use for this is to insert the root-disk UUID into the command
1580 line where bootargs contains "root=${uuid}"
1581
1582 setenv bootargs "console= root=${uuid}"
1583 # Set the 'uuid' environment variable
1584 part uuid mmc 2:2 uuid
1585
1586 # Command-line substitution will put the real uuid into the
1587 # kernel command line
1588 bootm
1589
Simon Glass5e958642020-09-10 20:21:18 -06001590config USE_BOOTCOMMAND
1591 bool "Enable a default value for bootcmd"
1592 help
1593 Provide a default value for the bootcmd entry in the environment. If
1594 autoboot is enabled this is what will be run automatically. Enable
1595 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1596 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1597 won't take any space in U-Boot image.
1598
1599config BOOTCOMMAND
1600 string "bootcmd value"
1601 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
Simon Glass2d5a8e12023-05-06 08:27:09 -06001602 default "bootflow scan -lb" if BOOTSTD_DEFAULTS && CMD_BOOTFLOW_FULL
1603 default "bootflow scan" if BOOTSTD_DEFAULTS && !CMD_BOOTFLOW_FULL
Simon Glassbe661cb2022-04-24 23:31:27 -06001604 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
Simon Glass5e958642020-09-10 20:21:18 -06001605 help
1606 This is the string of commands that will be used as bootcmd and if
1607 AUTOBOOT is set, automatically run.
1608
1609config USE_PREBOOT
1610 bool "Enable preboot"
1611 help
1612 When this option is enabled, the existence of the environment
1613 variable "preboot" will be checked immediately before starting the
1614 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1615 entering interactive mode.
1616
1617 This feature is especially useful when "preboot" is automatically
1618 generated or modified. For example, the boot code can modify the
1619 "preboot" when a user holds down a certain combination of keys.
1620
1621config PREBOOT
1622 string "preboot default value"
1623 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
Patrick Delaunaybb15d402020-10-12 09:47:50 +02001624 default "usb start" if USB_KEYBOARD
Simon Glass5e958642020-09-10 20:21:18 -06001625 default ""
1626 help
1627 This is the default of "preboot" environment variable.
1628
Pali Rohár39c43c32022-07-10 13:42:55 +02001629config PREBOOT_DEFINED
1630 bool
1631 default y if PREBOOT != ""
1632
Simon Glassc10ddfd2020-09-10 20:21:20 -06001633config DEFAULT_FDT_FILE
1634 string "Default fdt file"
1635 help
1636 This option is used to set the default fdt file to boot OS.
1637
Dzmitry Sankouskia3463062022-02-22 21:49:52 +03001638config SAVE_PREV_BL_FDT_ADDR
1639 depends on ARM
1640 bool "Saves fdt address, passed by the previous bootloader, to env var"
1641 help
1642 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1643 enable this option to save fdt address, passed by the
1644 previous bootloader for future use.
1645 Address is saved to `prevbl_fdt_addr` environment variable.
1646
1647 If no fdt was provided by previous bootloader, no env variables
1648 will be created.
1649
1650config SAVE_PREV_BL_INITRAMFS_START_ADDR
1651 depends on ARM
1652 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1653 help
1654 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1655 enable this option to save initramfs address, passed by the
1656 previous bootloader for future use.
1657 Address is saved to `prevbl_initrd_start_addr` environment variable.
1658
1659 If no initramfs was provided by previous bootloader, no env variables
1660 will be created.
1661
Simon Glassc8925112023-06-01 10:23:02 -06001662menu "Configuration editor"
1663
1664config CEDIT
1665 bool "Configuration editor"
1666 depends on BOOTSTD
1667 help
1668 Provides a way to deal with board configuration and present it to
1669 the user for adjustment.
1670
1671 This is intended to provide both graphical and text-based user
1672 interfaces, but only graphical is support at present.
1673
1674endmenu # Configuration editor
1675
Simon Glassb45b1632020-09-10 20:21:13 -06001676endmenu # Booting