blob: 9f5b8a0cb2c8b686ddd7d42951359c396db052db [file] [log] [blame]
Simon Glasscf298162020-09-10 20:21:13 -06001menu "Boot options"
2
3menu "Boot images"
4
5config ANDROID_BOOT_IMAGE
Simon Glass47b18c02023-09-14 10:55:48 -06006 bool "Android Boot Images"
Simon Glasscf298162020-09-10 20:21:13 -06007 default y if FASTBOOT
8 help
9 This enables support for booting images which use the Android
10 image format header.
11
Simon Glass12a7ea02023-09-14 10:55:49 -060012config TIMESTAMP
13 bool "Show image date and time when displaying image information"
14 default y if CMD_DATE
15 help
16 When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of
17 an image is printed by image commands like bootm or iminfo. This
18 is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is
19 enabled, then U-Boot requires FITs to have a timestamp. If a FIT is
20 loaded that does not, the message 'Wrong FIT format: no timestamp'
21 is shown.
22
23menuconfig FIT
24 bool "Flattened Image Tree (FIT)"
Alexandru Gagniuc92055e12021-09-02 19:54:21 -050025 select HASH
Simon Glasscf298162020-09-10 20:21:13 -060026 select MD5
27 select SHA1
Alexandru Gagniuceb5171d2021-09-02 19:54:17 -050028 imply SHA256
Simon Glasscf298162020-09-10 20:21:13 -060029 help
30 This option allows you to boot the new uImage structure,
31 Flattened Image Tree. FIT is formally a FDT, which can include
32 images of various types (kernel, FDT blob, ramdisk, etc.)
33 in a single blob. To boot this new uImage structure,
34 pass the address of the blob to the "bootm" command.
35 FIT is very flexible, supporting compression, multiple images,
36 multiple configurations, verification through hashing and also
37 verified boot (secure boot using RSA).
38
Simon Glass12a7ea02023-09-14 10:55:49 -060039if FIT
Simon Glassd6b318d2021-12-18 11:27:50 -070040
Simon Glasscf298162020-09-10 20:21:13 -060041config 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"
Simon Glass12a7ea02023-09-14 10:55:49 -060062 depends on DM
Simon Glasscf298162020-09-10 20:21:13 -060063 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"
Simon Glass12a7ea02023-09-14 10:55:49 -0600100 depends on DM
Simon Glasscf298162020-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"
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"
Manorit Chawdhry86fab112023-07-14 11:22:40 +0530125 depends on SOCFPGA_SECURE_VAB_AUTH
Simon Glasscf298162020-09-10 20:21:13 -0600126 help
127 Allows doing any sort of manipulation to blobs after they got extracted
128 from FIT images like stripping off headers or modifying the size of the
129 blob, verification, authentication, decryption etc. in a platform or
130 board specific way. In order to use this feature a platform or board-
131 specific implementation of board_fit_image_post_process() must be
132 provided. Also, anything done during this post-processing step would
133 need to be comprehended in how the images were prepared before being
134 injected into the FIT creation (i.e. the blobs would have been pre-
135 processed before being added to the FIT image).
136
Ravik Hasija7a018822021-01-27 14:01:48 -0800137config FIT_PRINT
138 bool "Support FIT printing"
139 default y
140 help
141 Support printing the content of the fitImage in a verbose manner.
142
Simon Glasscf298162020-09-10 20:21:13 -0600143config SPL_FIT
144 bool "Support Flattened Image Tree within SPL"
Simon Glass4d8ea262023-09-14 10:55:52 -0600145 depends on SPL
Alexandru Gagniuc92055e12021-09-02 19:54:21 -0500146 select SPL_HASH
Simon Glasscf298162020-09-10 20:21:13 -0600147 select SPL_OF_LIBFDT
148
149config SPL_FIT_PRINT
150 bool "Support FIT printing within SPL"
151 depends on SPL_FIT
152 help
153 Support printing the content of the fitImage in a verbose manner in SPL.
154
Simon Glass6f3c2d82021-02-15 17:08:10 -0700155config SPL_FIT_FULL_CHECK
156 bool "Do a full check of the FIT before using it"
Tom Rini90c78882022-12-04 10:14:20 -0500157 depends on SPL_FIT
Simon Glass6f3c2d82021-02-15 17:08:10 -0700158 help
159 Enable this do a full check of the FIT to make sure it is valid. This
160 helps to protect against carefully crafted FITs which take advantage
161 of bugs or omissions in the code. This includes a bad structure,
162 multiple root nodes and the like.
163
Simon Glasscf298162020-09-10 20:21:13 -0600164config SPL_FIT_SIGNATURE
165 bool "Enable signature verification of FIT firmware within SPL"
166 depends on SPL_DM
Klaus Heinrich Kiwibdb7f262021-02-09 15:41:54 -0300167 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
Klaus Heinrich Kiwi6ce28132021-02-09 15:41:53 -0300168 select FIT_SIGNATURE
Simon Glasscf298162020-09-10 20:21:13 -0600169 select SPL_FIT
Simon Glass0c6bdbb2021-07-10 21:14:25 -0600170 select SPL_CRYPTO
Alexandru Gagniuc07212092021-09-02 19:54:19 -0500171 select SPL_HASH
Alexandru Gagniuc61416fe2021-07-29 11:47:18 -0500172 imply SPL_RSA
173 imply SPL_RSA_VERIFY
Simon Glasscf298162020-09-10 20:21:13 -0600174 select SPL_IMAGE_SIGN_INFO
Simon Glass6f3c2d82021-02-15 17:08:10 -0700175 select SPL_FIT_FULL_CHECK
Simon Glasscf298162020-09-10 20:21:13 -0600176
Simon Glassb53541f2021-09-25 19:43:39 -0600177config SPL_FIT_SIGNATURE_MAX_SIZE
178 hex "Max size of signed FIT structures in SPL"
179 depends on SPL_FIT_SIGNATURE
180 default 0x10000000
181 help
182 This option sets a max size in bytes for verified FIT uImages.
183 A sane value of 256MB protects corrupted DTB structures from overlapping
184 device memory. Assure this size does not extend past expected storage
185 space.
186
Philippe Reynes5d39c932021-10-15 11:35:03 +0200187config SPL_FIT_RSASSA_PSS
188 bool "Support rsassa-pss signature scheme of FIT image contents in SPL"
189 depends on SPL_FIT_SIGNATURE
190 help
191 Enable this to support the pss padding algorithm as described
192 in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL.
193
Simon Glasscf298162020-09-10 20:21:13 -0600194config SPL_LOAD_FIT
195 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
Simon Glass4d8ea262023-09-14 10:55:52 -0600196 depends on SPL
Simon Glasscf298162020-09-10 20:21:13 -0600197 select SPL_FIT
198 help
199 Normally with the SPL framework a legacy image is generated as part
200 of the build. This contains U-Boot along with information as to
201 where it should be loaded. This option instead enables generation
202 of a FIT (Flat Image Tree) which provides more flexibility. In
203 particular it can handle selecting from multiple device tree
204 and passing the correct one to U-Boot.
205
Alexandru Gagniucdf51ae72021-03-29 12:05:15 -0500206 This path has the following limitations:
207
Bin Meng6e847f62021-05-10 20:23:29 +0800208 1. "loadables" images, other than FDTs, which do not have a "load"
Alexandru Gagniucdf51ae72021-03-29 12:05:15 -0500209 property will not be loaded. This limitation also applies to FPGA
210 images with the correct "compatible" string.
Oleksandr Suvorova3a1afb2022-07-22 17:16:13 +0300211 2. For FPGA images, the supported "compatible" list is in the
212 doc/uImage.FIT/source_file_format.txt.
Alexandru Gagniucdf51ae72021-03-29 12:05:15 -0500213 3. FDTs are only loaded for images with an "os" property of "u-boot".
214 "linux" images are also supported with Falcon boot mode.
215
Simon Glasscf298162020-09-10 20:21:13 -0600216config SPL_LOAD_FIT_ADDRESS
217 hex "load address of fit image"
Simon Glass815f8d32023-09-14 10:55:51 -0600218 depends on SPL_LOAD_FIT
Simon Glasscf298162020-09-10 20:21:13 -0600219 default 0x0
220 help
221 Specify the load address of the fit image that will be loaded
222 by SPL.
223
224config SPL_LOAD_FIT_APPLY_OVERLAY
225 bool "Enable SPL applying DT overlays from FIT"
226 depends on SPL_LOAD_FIT
227 select OF_LIBFDT_OVERLAY
228 help
Hugo Villeneuveb4230372023-04-24 16:51:12 -0400229 The device tree is loaded from the FIT image. Allow the SPL to
Simon Glasscf298162020-09-10 20:21:13 -0600230 also load device-tree overlays from the FIT image an apply them
231 over the device tree.
232
233config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
234 depends on SPL_LOAD_FIT_APPLY_OVERLAY
235 default 0x10000
236 hex "size of temporary buffer used to load the overlays"
237 help
238 The size of the area where the overlays will be loaded and
239 uncompress. Must be at least as large as biggest overlay
240 (uncompressed)
241
242config SPL_LOAD_FIT_FULL
243 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
244 select SPL_FIT
245 help
246 Normally with the SPL framework a legacy image is generated as part
247 of the build. This contains U-Boot along with information as to
248 where it should be loaded. This option instead enables generation
249 of a FIT (Flat Image Tree) which provides more flexibility. In
250 particular it can handle selecting from multiple device tree
251 and passing the correct one to U-Boot.
252
253config SPL_FIT_IMAGE_POST_PROCESS
254 bool "Enable post-processing of FIT artifacts after loading by the SPL"
255 depends on SPL_LOAD_FIT
Andrew Davis042e87e2022-05-04 15:52:28 -0500256 default y if TI_SECURE_DEVICE
Simon Glasscf298162020-09-10 20:21:13 -0600257 help
258 Allows doing any sort of manipulation to blobs after they got extracted
259 from the U-Boot FIT image like stripping off headers or modifying the
260 size of the blob, verification, authentication, decryption etc. in a
261 platform or board specific way. In order to use this feature a platform
262 or board-specific implementation of board_fit_image_post_process() must
263 be provided. Also, anything done during this post-processing step would
264 need to be comprehended in how the images were prepared before being
265 injected into the FIT creation (i.e. the blobs would have been pre-
266 processed before being added to the FIT image).
267
268config SPL_FIT_SOURCE
269 string ".its source file for U-Boot FIT image"
270 depends on SPL_FIT
271 help
272 Specifies a (platform specific) FIT source file to generate the
273 U-Boot FIT image. This could specify further image to load and/or
274 execute.
275
276config USE_SPL_FIT_GENERATOR
277 bool "Use a script to generate the .its script"
Tom Rini90c78882022-12-04 10:14:20 -0500278 depends on SPL_FIT
Simon Glass31f35e82023-01-07 14:07:19 -0700279 default y if SPL_FIT && ARCH_ZYNQMP
Simon Glasscf298162020-09-10 20:21:13 -0600280
281config SPL_FIT_GENERATOR
282 string ".its file generator script for U-Boot FIT image"
283 depends on USE_SPL_FIT_GENERATOR
Simon Glasscf298162020-09-10 20:21:13 -0600284 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
Simon Glasscf298162020-09-10 20:21:13 -0600285 help
286 Specifies a (platform specific) script file to generate the FIT
287 source file used to build the U-Boot FIT image file. This gets
288 passed a list of supported device tree file stub names to
289 include in the generated image.
290
Simon Glass42184562022-10-20 18:23:13 -0600291if VPL
292
293config VPL_FIT
294 bool "Support Flattened Image Tree within VPL"
295 depends on VPL
296 default y
297 select VPL_HASH
298 select VPL_OF_LIBFDT
299
300config VPL_FIT_PRINT
301 bool "Support FIT printing within VPL"
302 depends on VPL_FIT
303 default y
304 help
305 Support printing the content of the fitImage in a verbose manner in VPL.
306
307config VPL_FIT_FULL_CHECK
308 bool "Do a full check of the FIT before using it"
309 default y
310 help
311 Enable this do a full check of the FIT to make sure it is valid. This
312 helps to protect against carefully crafted FITs which take advantage
313 of bugs or omissions in the code. This includes a bad structure,
314 multiple root nodes and the like.
315
316config VPL_FIT_SIGNATURE
317 bool "Enable signature verification of FIT firmware within VPL"
318 depends on VPL_DM
Simon Glass42184562022-10-20 18:23:13 -0600319 default y
320 select FIT_SIGNATURE
321 select VPL_FIT
322 select VPL_CRYPTO
323 select VPL_HASH
324 imply VPL_RSA
325 imply VPL_RSA_VERIFY
326 select VPL_IMAGE_SIGN_INFO
327 select VPL_FIT_FULL_CHECK
328
329config VPL_FIT_SIGNATURE_MAX_SIZE
330 hex "Max size of signed FIT structures in VPL"
331 depends on VPL_FIT_SIGNATURE
332 default 0x10000000
333 help
334 This option sets a max size in bytes for verified FIT uImages.
335 A sane value of 256MB protects corrupted DTB structures from overlapping
336 device memory. Assure this size does not extend past expected storage
337 space.
338
339endif # VPL
340
Simon Glass4d8ea262023-09-14 10:55:52 -0600341endif # FIT
342
John Keepingbe43a352022-07-28 11:19:15 +0100343config PXE_UTILS
344 bool
345 select MENU
346 help
347 Utilities for parsing PXE file formats.
348
Tom Rini2180a452023-10-26 14:31:24 -0400349config BOOT_DEFAULTS_FEATURES
350 bool
351 select SUPPORT_RAW_INITRD
352 select ENV_VARS_UBOOT_CONFIG
353 imply USB_STORAGE
354 imply EFI_PARTITION
355 imply ISO_PARTITION
356
357config BOOT_DEFAULTS_CMDS
358 bool
Simon Glassa0c739c2023-03-24 16:58:13 -0400359 imply USE_BOOTCOMMAND
360 select CMD_ENV_EXISTS
361 select CMD_EXT2
362 select CMD_EXT4
363 select CMD_FAT
364 select CMD_FS_GENERIC
365 select CMD_PART if PARTITIONS
366 select CMD_DHCP if CMD_NET
367 select CMD_PING if CMD_NET
368 select CMD_PXE if CMD_NET
Simon Glassa0c739c2023-03-24 16:58:13 -0400369 select CMD_BOOTI if ARM64
370 select CMD_BOOTZ if ARM && !ARM64
371 imply CMD_MII if NET
Tom Rini2180a452023-10-26 14:31:24 -0400372
373config BOOT_DEFAULTS
374 bool # Common defaults for standard boot and distroboot
375 select BOOT_DEFAULTS_FEATURES
376 select BOOT_DEFAULTS_CMDS if CMDLINE
Simon Glassa0c739c2023-03-24 16:58:13 -0400377 help
378 These are not required but are commonly needed to support a good
379 selection of booting methods. Enable this to improve the capability
380 of U-Boot to boot various images. Currently much functionality is
381 tied to enabling the command that exercises it.
382
Simon Glass4a8fcb62023-09-14 10:55:53 -0600383menuconfig BOOTSTD
384 bool "Standard boot"
Simon Glassef5e3892022-04-24 23:31:06 -0600385 default y
386 depends on DM && OF_CONTROL && BLK
387 help
388 U-Boot supports a standard way of locating something to boot,
389 typically an Operating System such as Linux, provided by a distro such
390 as Arch Linux or Debian. Enable this to support iterating through
391 available bootdevs and using bootmeths to find bootflows suitable for
392 booting.
393
394 Standard boot is not a standard way of booting, just a framework
395 within U-Boot for supporting all the different ways that exist.
396
397 Terminology:
398
399 - bootdev - a device which can hold a distro (e.g. MMC)
400 - bootmeth - a method to scan a bootdev to find bootflows (owned by
401 U-Boot)
402 - bootflow - a description of how to boot (owned by the distro)
403
Simon Glass4a8fcb62023-09-14 10:55:53 -0600404if BOOTSTD
405
Simon Glass42184562022-10-20 18:23:13 -0600406config SPL_BOOTSTD
Simon Glass1c419582023-02-22 09:33:58 -0700407 bool "Standard boot support in SPL"
Simon Glass42184562022-10-20 18:23:13 -0600408 depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK
409 default y if VPL
410 help
411 This enables standard boot in SPL. This is neeeded so that VBE
412 (Verified Boot for Embedded) can be used, since it depends on standard
413 boot. It is enabled by default since the main purpose of VPL is to
414 handle the firmware part of VBE.
415
416config VPL_BOOTSTD
417 bool "Standard boot support in VPL"
418 depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK
419 default y
420 help
421 This enables standard boot in SPL. This is neeeded so that VBE
422 (Verified Boot for Embedded) can be used, since it depends on standard
423 boot. It is enabled by default since the main purpose of VPL is to
424 handle the firmware part of VBE.
425
Simon Glassbcb1d262023-02-22 14:06:23 -0700426config BOOTSTD_FULL
427 bool "Enhanced features for standard boot"
428 default y if SANDBOX
429 help
430 This enables various useful features for standard boot, which are not
431 essential for operation:
432
433 - bootdev, bootmeth commands
434 - extra features in the bootflow command
435 - support for selecting the ordering of bootmeths ("bootmeth order")
436 - support for selecting the ordering of bootdevs using the devicetree
437 as well as the "boot_targets" environment variable
438
Simon Glass22353fa2023-01-28 15:00:21 -0700439config BOOTSTD_DEFAULTS
440 bool "Select some common defaults for standard boot"
441 depends on BOOTSTD
Simon Glassa0c739c2023-03-24 16:58:13 -0400442 select BOOT_DEFAULTS
Simon Glassfba0e732023-05-10 16:34:47 -0600443 select BOOTMETH_DISTRO
Simon Glass22353fa2023-01-28 15:00:21 -0700444 help
445 These are not required but are commonly needed to support a good
446 selection of booting methods. Enable this to improve the capability
447 of U-Boot to boot various images.
448
Simon Glassa91492b2022-04-24 23:31:27 -0600449config BOOTSTD_BOOTCOMMAND
450 bool "Use bootstd to boot"
451 default y if !DISTRO_DEFAULTS
452 help
453 Enable this to select a default boot-command suitable for booting
454 with standard boot. This can be overridden by the board if needed,
455 but the default command should be enough for most boards which use
456 standard boot.
457
458 For now this is only selected if distro boot is NOT used, since
459 standard boot does not support all of the features of distro boot
460 yet.
461
Simon Glass1047b532023-11-18 14:05:19 -0700462config BOOTSTD_PROG
463 bool "Use programmatic boot"
464 depends on !CMDLINE
465 default y
466 help
467 Enable this to provide a board_run_command() function which can boot
468 a systen without using commands. If the boot fails, then U-Boot will
469 panic.
470
471 Note: This currently has many limitations and is not a useful booting
472 solution. Future work will eventually make this a viable option.
473
Simon Glassbc06aa02022-07-30 15:52:21 -0600474config BOOTMETH_GLOBAL
475 bool
476 help
477 Add support for global bootmeths. This feature is used by VBE and
478 EFI bootmgr, since they take full control over which bootdevs are
479 selected to boot.
480
Simon Glassc88d67d2023-07-12 09:04:45 -0600481config BOOTMETH_CROS
482 bool "Bootdev support for Chromium OS"
Simon Glassdaffb0b2023-07-30 11:17:02 -0600483 depends on X86 || ARM || SANDBOX
484 default y if !ARM
Simon Glass71f634b2023-08-24 13:55:45 -0600485 select EFI_PARTITION
486 select PARTITION_TYPE_GUID
487 select PARTITION_UUIDS
Simon Glassc88d67d2023-07-12 09:04:45 -0600488 help
489 Enables support for booting Chromium OS using bootdevs. This uses the
490 kernel A slot and obtains the kernel command line from the parameters
491 provided there.
492
493 Note that only x86 devices are supported at present.
494
Simon Glass79f66352023-05-10 16:34:46 -0600495config BOOTMETH_EXTLINUX
496 bool "Bootdev support for extlinux boot"
John Keepingbe43a352022-07-28 11:19:15 +0100497 select PXE_UTILS
Simon Glass31aefaf2022-04-24 23:31:13 -0600498 default y
499 help
Simon Glass79f66352023-05-10 16:34:46 -0600500 Enables support for extlinux boot using bootdevs. This makes the
Simon Glass31aefaf2022-04-24 23:31:13 -0600501 bootdevs look for a 'extlinux/extlinux.conf' on each filesystem
502 they scan.
503
Simon Glass79f66352023-05-10 16:34:46 -0600504 The specification for this filed is here:
505
506 https://uapi-group.org/specifications/specs/boot_loader_specification/
507
Simon Glass31aefaf2022-04-24 23:31:13 -0600508 This provides a way to try out standard boot on an existing boot flow.
509
Simon Glass79f66352023-05-10 16:34:46 -0600510config BOOTMETH_EXTLINUX_PXE
511 bool "Bootdev support for extlinux boot over network"
Simon Glassdab2c282022-04-24 23:31:16 -0600512 depends on CMD_PXE && CMD_NET && DM_ETH
513 default y
514 help
Simon Glass79f66352023-05-10 16:34:46 -0600515 Enables support for extlinux boot using bootdevs. This makes the
Simon Glassdab2c282022-04-24 23:31:16 -0600516 bootdevs look for a 'extlinux/extlinux.conf' on the tftp server.
517
Simon Glass79f66352023-05-10 16:34:46 -0600518 The specification for this file is here:
519
520 https://uapi-group.org/specifications/specs/boot_loader_specification/
521
Simon Glassdab2c282022-04-24 23:31:16 -0600522 This provides a way to try out standard boot on an existing boot flow.
523
Simon Glassacfa9bd2022-04-24 23:31:17 -0600524config BOOTMETH_EFILOADER
525 bool "Bootdev support for EFI boot"
AKASHI Takahiro7017fc52023-11-21 10:29:46 +0900526 depends on BOOTEFI_BOOTMGR
Simon Glassacfa9bd2022-04-24 23:31:17 -0600527 default y
528 help
529 Enables support for EFI boot using bootdevs. This makes the
530 bootdevs look for a 'boot<arch>.efi' on each filesystem
531 they scan. The resulting file is booted after enabling U-Boot's
532 EFI loader support.
533
534 The <arch> depends on the architecture of the board:
535
536 aa64 - aarch64 (ARM 64-bit)
537 arm - ARM 32-bit
538 ia32 - x86 32-bit
539 x64 - x86 64-bit
540 riscv32 - RISC-V 32-bit
541 riscv64 - RISC-V 64-bit
542
543 This provides a way to try out standard boot on an existing boot flow.
544
Simon Glass4c7418f2022-07-30 15:52:32 -0600545config BOOTMETH_VBE
546 bool "Bootdev support for Verified Boot for Embedded"
547 depends on FIT
548 default y
549 select BOOTMETH_GLOBAL
Tom Rini448e2b62023-01-16 15:46:49 -0500550 select EVENT
Simon Glass4c7418f2022-07-30 15:52:32 -0600551 help
552 Enables support for VBE boot. This is a standard boot method which
553 supports selection of various firmware components, seleciton of an OS to
554 boot as well as updating these using fwupd.
555
Simon Glassfba0e732023-05-10 16:34:47 -0600556config BOOTMETH_DISTRO
557 bool # Options needed to boot any distro
Tom Rini558787f2023-10-26 14:31:27 -0400558 select BOOTMETH_SCRIPT if CMDLINE # E.g. Armbian uses scripts
Simon Glassfba0e732023-05-10 16:34:47 -0600559 select BOOTMETH_EXTLINUX # E.g. Debian uses these
560 select BOOTMETH_EXTLINUX_PXE if CMD_PXE && CMD_NET && DM_ETH
AKASHI Takahiro7017fc52023-11-21 10:29:46 +0900561 select BOOTMETH_EFILOADER if BOOTEFI_BOOTMGR # E.g. Ubuntu uses this
Simon Glassfba0e732023-05-10 16:34:47 -0600562
Simon Glass42184562022-10-20 18:23:13 -0600563config SPL_BOOTMETH_VBE
564 bool "Bootdev support for Verified Boot for Embedded (SPL)"
565 depends on SPL && FIT
Tom Rini448e2b62023-01-16 15:46:49 -0500566 select EVENT
Simon Glass42184562022-10-20 18:23:13 -0600567 default y if VPL
568 help
569 Enables support for VBE boot. This is a standard boot method which
570 supports selection of various firmware components, seleciton of an OS to
571 boot as well as updating these using fwupd.
572
573config VPL_BOOTMETH_VBE
574 bool "Bootdev support for Verified Boot for Embedded (VPL)"
575 depends on VPL && FIT
Tom Rini448e2b62023-01-16 15:46:49 -0500576 select EVENT
Simon Glass42184562022-10-20 18:23:13 -0600577 default y
578 help
579 Enables support for VBE boot. This is a standard boot method which
580 supports selection of various firmware components, seleciton of an OS to
581 boot as well as updating these using fwupd.
582
Simon Glasscb47e212022-07-30 15:52:33 -0600583if BOOTMETH_VBE
584
Simon Glassda900e52023-02-22 09:33:52 -0700585config BOOTMETH_VBE_REQUEST
586 bool "Support for serving VBE OS requests"
587 default y
588 help
589 Enables support for looking that the requests made by the
590 Operating System being booted. These requests result in additions to
591 the device tree /chosen node, added during the device tree fixup
592 phase.
593
594config SPL_BOOTMETH_VBE_REQUEST
595 bool "Support for serving VBE OS requests (SPL)"
596 depends on SPL
597 help
598 Enables support for looking that the requests made by the
599 Operating System being booted. These requests result in additions to
600 the device tree /chosen node, added during the device tree fixup
601 phase.
602
603 This is only useful if you are booting an OS direct from SPL.
604
Simon Glasscb47e212022-07-30 15:52:33 -0600605config BOOTMETH_VBE_SIMPLE
606 bool "Bootdev support for VBE 'simple' method"
607 default y
608 help
609 Enables support for VBE 'simple' boot. This allows updating a single
610 firmware image in boot media such as MMC. It does not support any sort
611 of rollback, recovery or A/B boot.
612
Simon Glass42184562022-10-20 18:23:13 -0600613config BOOTMETH_VBE_SIMPLE_OS
614 bool "Bootdev support for VBE 'simple' method OS phase"
615 default y
616 help
617 Enables support for the OS parts of VBE 'simple' boot. This includes
618 fixing up the device tree with the required VBE information, ready
619 for booting into the OS. This option is only enabled for U-Boot
620 proper, since it is the phase where device tree fixups happen.
621
622config SPL_BOOTMETH_VBE_SIMPLE
623 bool "Bootdev support for VBE 'simple' method (SPL)"
624 depends on SPL
625 default y if VPL
626 help
627 Enables support for VBE 'simple' boot. This allows updating a single
628 firmware image in boot media such as MMC. It does not support any sort
629 of rollback, recovery or A/B boot.
630
631config VPL_BOOTMETH_VBE_SIMPLE
632 bool "Bootdev support for VBE 'simple' method (VPL)"
633 depends on VPL
634 default y
635 help
636 Enables support for VBE 'simple' boot. This allows updating a single
637 firmware image in boot media such as MMC. It does not support any sort
638 of rollback, recovery or A/B boot.
639
640config SPL_BOOTMETH_VBE_SIMPLE_FW
641 bool "Bootdev support for VBE 'simple' method firmware phase (SPL)"
642 depends on VPL
643 default y
644 help
645 Enables support for the firmware parts of VBE 'simple' boot. This
646 includes an SPL loader which locates the correct U-Boot to boot into.
647 This option should really only be enabled for VPL, since it is the
648 phase where the SPL + U-Boot decision should be made. But for now,
649 SPL does its own FIT-configuration selection.
650
651config VPL_BOOTMETH_VBE_SIMPLE_FW
652 bool "Bootdev support for VBE 'simple' method firmware phase (VPL)"
653 depends on VPL
654 default y
655 help
656 Enables support for the firmware parts of VBE 'simple' boot. This
657 includes an SPL loader which locates the correct SPL to boot into.
658 This option enabled for VPL, since it is the phase where the SPL
659 decision is made.
660
Simon Glasscb47e212022-07-30 15:52:33 -0600661endif # BOOTMETH_VBE
662
Simon Glass87c6f8a2023-01-06 08:52:36 -0600663config EXPO
664 bool "Support for expos - groups of scenes displaying a UI"
Simon Glass0041b1c2023-01-28 15:00:18 -0700665 depends on VIDEO
Simon Glass87c6f8a2023-01-06 08:52:36 -0600666 default y if BOOTMETH_VBE
667 help
668 An expo is a way of presenting and collecting information from the
669 user. It consists of a collection of 'scenes' of which only one is
670 presented at a time. An expo is typically used to show a boot menu
671 and allow settings to be changed.
672
673 The expo can be presented in graphics form using a vidconsole, or in
674 text form on a serial console.
675
Simon Glass126947b2022-04-24 23:31:20 -0600676config BOOTMETH_SANDBOX
677 def_bool y
678 depends on SANDBOX
679 help
680 This is a sandbox bootmeth driver used for testing. It always returns
681 -ENOTSUPP when attempting to boot.
682
Simon Glassd9409242022-04-24 23:31:22 -0600683config BOOTMETH_SCRIPT
684 bool "Bootdev support for U-Boot scripts"
685 default y if BOOTSTD_FULL
Tom Rini558787f2023-10-26 14:31:27 -0400686 depends on CMDLINE
Simon Glassab16a3d2023-05-05 20:03:05 -0600687 select HUSH_PARSER
Simon Glassd9409242022-04-24 23:31:22 -0600688 help
689 Enables support for booting a distro via a U-Boot script. This makes
690 the bootdevs look for a 'boot/boot.scr' file which can be used to
691 boot the distro.
692
693 This provides a way to try out standard boot on an existing boot flow.
694 It is not enabled by default to save space.
695
Simon Glass4a8fcb62023-09-14 10:55:53 -0600696endif # BOOTSTD
Simon Glass31aefaf2022-04-24 23:31:13 -0600697
Simon Glasscf298162020-09-10 20:21:13 -0600698config LEGACY_IMAGE_FORMAT
699 bool "Enable support for the legacy image format"
Andrew Davis52dc3342022-05-04 15:52:27 -0500700 default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
Simon Glasscf298162020-09-10 20:21:13 -0600701 help
702 This option enables the legacy image format. It is enabled by
703 default for backward compatibility, unless FIT_SIGNATURE is
704 set where it is disabled so that unsigned images cannot be
705 loaded. If a board needs the legacy image format support in this
706 case, enable it here.
707
Eddie Jamesdec166d2023-10-24 10:43:50 -0500708config MEASURED_BOOT
709 bool "Measure boot images and configuration when booting without EFI"
710 depends on HASH && TPM_V2
711 help
712 This option enables measurement of the boot process when booting
713 without UEFI . Measurement involves creating cryptographic hashes
714 of the binary images that are booting and storing them in the TPM.
715 In addition, a log of these hashes is stored in memory for the OS
716 to verify the booted images and configuration. Enable this if the
717 OS has configured some memory area for the event log and you intend
718 to use some attestation tools on your system.
719
720if MEASURED_BOOT
721 config MEASURE_DEVICETREE
722 bool "Measure the devicetree image"
723 default y if MEASURED_BOOT
724 help
725 On some platforms, the devicetree is not static as it may contain
726 random MAC addresses or other such data that changes each boot.
727 Therefore, it should not be measured into the TPM. In that case,
728 disable the measurement here.
729
730 config MEASURE_IGNORE_LOG
731 bool "Ignore the existing event log"
732 default n
733 help
734 On platforms that use an event log memory region that persists
735 through system resets and are the first stage bootloader, then
736 this option should be enabled to ignore any existing data in the
737 event log memory region.
738endif # MEASURED_BOOT
739
Tom Rini9d298c92023-10-26 14:31:25 -0400740config SYS_BOOTM_LEN
741 hex "Maximum size of a decompresed OS image"
742 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ || \
743 LEGACY_IMAGE_FORMAT || SPL_LEGACY_IMAGE_FORMAT
744 default 0x4000000 if PPC || ARM64
745 default 0x1000000 if X86 || ARCH_MX6 || ARCH_MX7
746 default 0x800000
747 help
748 This is the maximum size of the buffer that is used to decompress the OS
749 image in to if attempting to boot a compressed image.
750
Simon Glassaefa34f2020-09-10 20:21:19 -0600751config SUPPORT_RAW_INITRD
752 bool "Enable raw initrd images"
753 help
754 Note, defining the SUPPORT_RAW_INITRD allows user to supply
755 kernel with raw initrd images. The syntax is slightly different, the
756 address of the initrd must be augmented by it's size, in the following
757 format: "<initrd address>:<initrd size>".
758
Simon Glass96d0aa92020-11-04 09:57:35 -0700759config CHROMEOS
760 bool "Support booting Chrome OS"
761 help
762 Chrome OS requires U-Boot to set up a table indicating the boot mode
763 (e.g. Developer mode) and a few other things. Enable this if you are
764 booting on a Chromebook to avoid getting an error about an invalid
765 firmware ID.
766
767config CHROMEOS_VBOOT
768 bool "Support Chrome OS verified boot"
769 help
770 This is intended to enable the full Chrome OS verified boot support
771 in U-Boot. It is not actually implemented in the U-Boot source code
772 at present, so this option is always set to 'n'. It allows
773 distinguishing between booting Chrome OS in a basic way (developer
774 mode) and a full boot.
775
Tom Rini5a446182022-06-25 11:02:44 -0400776config SYS_RAMBOOT
777 bool
778
Tom Rinid8ef01e2021-08-24 23:11:49 -0400779config RAMBOOT_PBL
780 bool "Freescale PBL(pre-boot loader) image format support"
Tom Rini5a446182022-06-25 11:02:44 -0400781 select SYS_RAMBOOT if PPC
Tom Rinid8ef01e2021-08-24 23:11:49 -0400782 help
783 Some SoCs use PBL to load RCW and/or pre-initialization instructions.
784 For more details refer to doc/README.pblimage
785
Tom Rinid433c742022-03-23 17:20:03 -0400786choice
Tom Riniec9efcf2022-12-28 10:52:51 -0500787 prompt "Freescale PBL (or predecessor) load location"
Tom Rinid433c742022-03-23 17:20:03 -0400788 depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \
789 || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \
790 && !CMD_NAND)
791
792config SDCARD
Tom Riniec9efcf2022-12-28 10:52:51 -0500793 bool "Freescale PBL (or similar) is found on SD card"
Tom Rinid433c742022-03-23 17:20:03 -0400794
795config SPIFLASH
Tom Riniec9efcf2022-12-28 10:52:51 -0500796 bool "Freescale PBL (or similar) is found on SPI flash"
797
798config NO_PBL
799 bool "Freescale PBL (or similar) is not used in this case"
Tom Rinid433c742022-03-23 17:20:03 -0400800
801endchoice
802
Tom Rinid8e84612022-06-20 08:07:42 -0400803config FSL_FIXED_MMC_LOCATION
804 bool "PBL MMC is at a fixed location"
805 depends on SDCARD && !RAMBOOT_PBL
806
807config ESDHC_HC_BLK_ADDR
808 def_bool y
809 depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010)
810 help
811 In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and
812 code length of these soc specify the memory address in block address
813 format. Block length is fixed to 512 bytes as per the SD High
814 Capacity specification.
815
Tom Rinid8ef01e2021-08-24 23:11:49 -0400816config SYS_FSL_PBL_PBI
817 string "PBI(pre-boot instructions) commands for the PBL image"
818 depends on RAMBOOT_PBL
819 help
820 PBI commands can be used to configure SoC before it starts the execution.
821 Please refer doc/README.pblimage for more details.
822
823config SYS_FSL_PBL_RCW
824 string "Aadditional RCW (Power on reset configuration) for the PBL image"
825 depends on RAMBOOT_PBL
826 help
827 Enables addition of RCW (Power on reset configuration) in built image.
828 Please refer doc/README.pblimage for more details.
829
Tom Rinibb20a102022-06-25 11:02:46 -0400830config SYS_BOOT_RAMDISK_HIGH
831 depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ
832 depends on !(NIOS2 || SANDBOX || SH || XTENSA)
833 def_bool y
Simon Glassfebb9852023-03-24 16:58:12 -0400834 select LMB
Tom Rinibb20a102022-06-25 11:02:46 -0400835 help
836 Enable initrd_high functionality. If defined then the initrd_high
837 feature is enabled and the boot* ramdisk subcommand is enabled.
838
Simon Glasscf298162020-09-10 20:21:13 -0600839endmenu # Boot images
840
Simon Glassc9d4abe2023-03-24 16:58:11 -0400841config DISTRO_DEFAULTS
Simon Glass3b58de42023-09-14 10:55:55 -0600842 bool "(deprecated) Script-based booting of Linux distributions"
Tom Rinifc97d932023-10-26 14:31:23 -0400843 select CMDLINE
Simon Glassa0c739c2023-03-24 16:58:13 -0400844 select BOOT_DEFAULTS
Simon Glassc9d4abe2023-03-24 16:58:11 -0400845 select AUTO_COMPLETE
846 select CMDLINE_EDITING
Simon Glassc9d4abe2023-03-24 16:58:11 -0400847 select CMD_SYSBOOT
Simon Glassc9d4abe2023-03-24 16:58:11 -0400848 select HUSH_PARSER
Simon Glassc9d4abe2023-03-24 16:58:11 -0400849 select SYS_LONGHELP
Simon Glassc9d4abe2023-03-24 16:58:11 -0400850 help
Simon Glass3b58de42023-09-14 10:55:55 -0600851 Note: These scripts have been replaced by Standard Boot. Do not use
852 them on new boards. See 'Migrating from distro_boot' at
853 doc/develop/bootstd.rst
854
Simon Glassc9d4abe2023-03-24 16:58:11 -0400855 Select this to enable various options and commands which are suitable
856 for building u-boot for booting general purpose Linux distributions.
857
Simon Glass75e65cc2020-09-10 20:21:14 -0600858menu "Boot timing"
859
860config BOOTSTAGE
861 bool "Boot timing and reporting"
862 help
863 Enable recording of boot time while booting. To use it, insert
864 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
865 bootstage.h. Only a single entry is recorded for each ID. You can
866 give the entry a name with bootstage_mark_name(). You can also
867 record elapsed time in a particular stage using bootstage_start()
868 before starting and bootstage_accum() when finished. Bootstage will
869 add up all the accumulated time and report it.
870
871 Normally, IDs are defined in bootstage.h but a small number of
872 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
873 as the ID.
874
875 Calls to show_boot_progress() will also result in log entries but
876 these will not have names.
877
878config SPL_BOOTSTAGE
879 bool "Boot timing and reported in SPL"
Tom Rinib3401992022-06-10 23:03:09 -0400880 depends on BOOTSTAGE && SPL
Simon Glass75e65cc2020-09-10 20:21:14 -0600881 help
882 Enable recording of boot time in SPL. To make this visible to U-Boot
883 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
884 information when SPL finishes and load it when U-Boot proper starts
885 up.
886
887config TPL_BOOTSTAGE
888 bool "Boot timing and reported in TPL"
Tom Rini8bea4bf2022-06-08 08:24:39 -0400889 depends on BOOTSTAGE && TPL
Simon Glass75e65cc2020-09-10 20:21:14 -0600890 help
891 Enable recording of boot time in SPL. To make this visible to U-Boot
892 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
893 information when TPL finishes and load it when U-Boot proper starts
894 up.
895
896config BOOTSTAGE_REPORT
897 bool "Display a detailed boot timing report before booting the OS"
898 depends on BOOTSTAGE
899 help
900 Enable output of a boot time report just before the OS is booted.
901 This shows how long it took U-Boot to go through each stage of the
902 boot process. The report looks something like this:
903
904 Timer summary in microseconds:
905 Mark Elapsed Stage
906 0 0 reset
907 3,575,678 3,575,678 board_init_f start
908 3,575,695 17 arch_cpu_init A9
909 3,575,777 82 arch_cpu_init done
910 3,659,598 83,821 board_init_r start
911 3,910,375 250,777 main_loop
912 29,916,167 26,005,792 bootm_start
913 30,361,327 445,160 start_kernel
914
915config BOOTSTAGE_RECORD_COUNT
916 int "Number of boot stage records to store"
Simon Glass939b04e2021-02-03 06:00:49 -0700917 depends on BOOTSTAGE
Simon Glass75e65cc2020-09-10 20:21:14 -0600918 default 30
919 help
920 This is the size of the bootstage record list and is the maximum
921 number of bootstage records that can be recorded.
922
923config SPL_BOOTSTAGE_RECORD_COUNT
924 int "Number of boot stage records to store for SPL"
Simon Glass939b04e2021-02-03 06:00:49 -0700925 depends on SPL_BOOTSTAGE
Simon Glass75e65cc2020-09-10 20:21:14 -0600926 default 5
927 help
928 This is the size of the bootstage record list and is the maximum
929 number of bootstage records that can be recorded.
930
931config TPL_BOOTSTAGE_RECORD_COUNT
932 int "Number of boot stage records to store for TPL"
Simon Glass939b04e2021-02-03 06:00:49 -0700933 depends on TPL_BOOTSTAGE
Simon Glass75e65cc2020-09-10 20:21:14 -0600934 default 5
935 help
936 This is the size of the bootstage record list and is the maximum
937 number of bootstage records that can be recorded.
938
939config BOOTSTAGE_FDT
940 bool "Store boot timing information in the OS device tree"
941 depends on BOOTSTAGE
942 help
943 Stash the bootstage information in the FDT. A root 'bootstage'
944 node is created with each bootstage id as a child. Each child
945 has a 'name' property and either 'mark' containing the
946 mark time in microseconds, or 'accum' containing the
947 accumulated time for that bootstage id in microseconds.
948 For example:
949
950 bootstage {
951 154 {
952 name = "board_init_f";
953 mark = <3575678>;
954 };
955 170 {
956 name = "lcd";
957 accum = <33482>;
958 };
959 };
960
961 Code in the Linux kernel can find this in /proc/devicetree.
962
963config BOOTSTAGE_STASH
964 bool "Stash the boot timing information in memory before booting OS"
965 depends on BOOTSTAGE
966 help
967 Some OSes do not support device tree. Bootstage can instead write
968 the boot timing information in a binary format at a given address.
969 This happens through a call to bootstage_stash(), typically in
970 the CPU's cleanup_before_linux() function. You can use the
971 'bootstage stash' and 'bootstage unstash' commands to do this on
972 the command line.
973
974config BOOTSTAGE_STASH_ADDR
975 hex "Address to stash boot timing information"
Tom Rinia077ac12023-08-02 11:09:43 -0400976 default 0x0
Simon Glass75e65cc2020-09-10 20:21:14 -0600977 help
978 Provide an address which will not be overwritten by the OS when it
979 starts, so that it can read this information when ready.
980
981config BOOTSTAGE_STASH_SIZE
982 hex "Size of boot timing stash region"
983 default 0x1000
984 help
985 This should be large enough to hold the bootstage stash. A value of
986 4096 (4KiB) is normally plenty.
987
988config SHOW_BOOT_PROGRESS
989 bool "Show boot progress in a board-specific manner"
990 help
991 Defining this option allows to add some board-specific code (calling
992 a user-provided function show_boot_progress(int) that enables you to
993 show the system's boot progress on some display (for example, some
994 LEDs) on your board. At the moment, the following checkpoints are
995 implemented:
996
997 Legacy uImage format:
998
999 Arg Where When
1000 1 common/cmd_bootm.c before attempting to boot an image
1001 -1 common/cmd_bootm.c Image header has bad magic number
1002 2 common/cmd_bootm.c Image header has correct magic number
1003 -2 common/cmd_bootm.c Image header has bad checksum
1004 3 common/cmd_bootm.c Image header has correct checksum
1005 -3 common/cmd_bootm.c Image data has bad checksum
1006 4 common/cmd_bootm.c Image data has correct checksum
1007 -4 common/cmd_bootm.c Image is for unsupported architecture
1008 5 common/cmd_bootm.c Architecture check OK
1009 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
1010 6 common/cmd_bootm.c Image Type check OK
1011 -6 common/cmd_bootm.c gunzip uncompression error
1012 -7 common/cmd_bootm.c Unimplemented compression type
1013 7 common/cmd_bootm.c Uncompression OK
1014 8 common/cmd_bootm.c No uncompress/copy overwrite error
1015 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
1016
1017 9 common/image.c Start initial ramdisk verification
1018 -10 common/image.c Ramdisk header has bad magic number
1019 -11 common/image.c Ramdisk header has bad checksum
1020 10 common/image.c Ramdisk header is OK
1021 -12 common/image.c Ramdisk data has bad checksum
1022 11 common/image.c Ramdisk data has correct checksum
1023 12 common/image.c Ramdisk verification complete, start loading
1024 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
1025 13 common/image.c Start multifile image verification
1026 14 common/image.c No initial ramdisk, no multifile, continue.
1027
1028 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
1029
1030 -30 arch/powerpc/lib/board.c Fatal error, hang the system
1031 -31 post/post.c POST test failed, detected by post_output_backlog()
1032 -32 post/post.c POST test failed, detected by post_run_single()
1033
1034 34 common/cmd_doc.c before loading a Image from a DOC device
1035 -35 common/cmd_doc.c Bad usage of "doc" command
1036 35 common/cmd_doc.c correct usage of "doc" command
1037 -36 common/cmd_doc.c No boot device
1038 36 common/cmd_doc.c correct boot device
1039 -37 common/cmd_doc.c Unknown Chip ID on boot device
1040 37 common/cmd_doc.c correct chip ID found, device available
1041 -38 common/cmd_doc.c Read Error on boot device
1042 38 common/cmd_doc.c reading Image header from DOC device OK
1043 -39 common/cmd_doc.c Image header has bad magic number
1044 39 common/cmd_doc.c Image header has correct magic number
1045 -40 common/cmd_doc.c Error reading Image from DOC device
1046 40 common/cmd_doc.c Image header has correct magic number
1047 41 common/cmd_ide.c before loading a Image from a IDE device
1048 -42 common/cmd_ide.c Bad usage of "ide" command
1049 42 common/cmd_ide.c correct usage of "ide" command
1050 -43 common/cmd_ide.c No boot device
1051 43 common/cmd_ide.c boot device found
1052 -44 common/cmd_ide.c Device not available
1053 44 common/cmd_ide.c Device available
1054 -45 common/cmd_ide.c wrong partition selected
1055 45 common/cmd_ide.c partition selected
1056 -46 common/cmd_ide.c Unknown partition table
1057 46 common/cmd_ide.c valid partition table found
1058 -47 common/cmd_ide.c Invalid partition type
1059 47 common/cmd_ide.c correct partition type
1060 -48 common/cmd_ide.c Error reading Image Header on boot device
1061 48 common/cmd_ide.c reading Image Header from IDE device OK
1062 -49 common/cmd_ide.c Image header has bad magic number
1063 49 common/cmd_ide.c Image header has correct magic number
1064 -50 common/cmd_ide.c Image header has bad checksum
1065 50 common/cmd_ide.c Image header has correct checksum
1066 -51 common/cmd_ide.c Error reading Image from IDE device
1067 51 common/cmd_ide.c reading Image from IDE device OK
1068 52 common/cmd_nand.c before loading a Image from a NAND device
1069 -53 common/cmd_nand.c Bad usage of "nand" command
1070 53 common/cmd_nand.c correct usage of "nand" command
1071 -54 common/cmd_nand.c No boot device
1072 54 common/cmd_nand.c boot device found
1073 -55 common/cmd_nand.c Unknown Chip ID on boot device
1074 55 common/cmd_nand.c correct chip ID found, device available
1075 -56 common/cmd_nand.c Error reading Image Header on boot device
1076 56 common/cmd_nand.c reading Image Header from NAND device OK
1077 -57 common/cmd_nand.c Image header has bad magic number
1078 57 common/cmd_nand.c Image header has correct magic number
1079 -58 common/cmd_nand.c Error reading Image from NAND device
1080 58 common/cmd_nand.c reading Image from NAND device OK
1081
1082 -60 common/env_common.c Environment has a bad CRC, using default
1083
1084 64 net/eth.c starting with Ethernet configuration.
1085 -64 net/eth.c no Ethernet found.
1086 65 net/eth.c Ethernet found.
1087
1088 -80 common/cmd_net.c usage wrong
1089 80 common/cmd_net.c before calling net_loop()
1090 -81 common/cmd_net.c some error in net_loop() occurred
1091 81 common/cmd_net.c net_loop() back without error
1092 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1093 82 common/cmd_net.c trying automatic boot
1094 83 common/cmd_net.c running "source" command
1095 -83 common/cmd_net.c some error in automatic boot or "source" command
1096 84 common/cmd_net.c end without errors
1097
1098 FIT uImage format:
1099
1100 Arg Where When
1101 100 common/cmd_bootm.c Kernel FIT Image has correct format
1102 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
1103 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
1104 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
1105 102 common/cmd_bootm.c Kernel unit name specified
1106 -103 common/cmd_bootm.c Can't get kernel subimage node offset
1107 103 common/cmd_bootm.c Found configuration node
1108 104 common/cmd_bootm.c Got kernel subimage node offset
1109 -104 common/cmd_bootm.c Kernel subimage hash verification failed
1110 105 common/cmd_bootm.c Kernel subimage hash verification OK
1111 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
1112 106 common/cmd_bootm.c Architecture check OK
1113 -106 common/cmd_bootm.c Kernel subimage has wrong type
1114 107 common/cmd_bootm.c Kernel subimage type OK
1115 -107 common/cmd_bootm.c Can't get kernel subimage data/size
1116 108 common/cmd_bootm.c Got kernel subimage data/size
1117 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
1118 -109 common/cmd_bootm.c Can't get kernel subimage type
1119 -110 common/cmd_bootm.c Can't get kernel subimage comp
1120 -111 common/cmd_bootm.c Can't get kernel subimage os
1121 -112 common/cmd_bootm.c Can't get kernel subimage load address
1122 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
1123
1124 120 common/image.c Start initial ramdisk verification
1125 -120 common/image.c Ramdisk FIT image has incorrect format
1126 121 common/image.c Ramdisk FIT image has correct format
1127 122 common/image.c No ramdisk subimage unit name, using configuration
1128 -122 common/image.c Can't get configuration for ramdisk subimage
1129 123 common/image.c Ramdisk unit name specified
1130 -124 common/image.c Can't get ramdisk subimage node offset
1131 125 common/image.c Got ramdisk subimage node offset
1132 -125 common/image.c Ramdisk subimage hash verification failed
1133 126 common/image.c Ramdisk subimage hash verification OK
1134 -126 common/image.c Ramdisk subimage for unsupported architecture
1135 127 common/image.c Architecture check OK
1136 -127 common/image.c Can't get ramdisk subimage data/size
1137 128 common/image.c Got ramdisk subimage data/size
1138 129 common/image.c Can't get ramdisk load address
1139 -129 common/image.c Got ramdisk load address
1140
1141 -130 common/cmd_doc.c Incorrect FIT image format
1142 131 common/cmd_doc.c FIT image format OK
1143
1144 -140 common/cmd_ide.c Incorrect FIT image format
1145 141 common/cmd_ide.c FIT image format OK
1146
1147 -150 common/cmd_nand.c Incorrect FIT image format
1148 151 common/cmd_nand.c FIT image format OK
1149
Marek Vasutb55881d2021-10-23 03:06:03 +02001150config SPL_SHOW_BOOT_PROGRESS
Jan Kiszkac1df3d52021-11-03 15:09:36 +01001151 bool "Show boot progress in a board-specific manner in SPL"
Marek Vasutb55881d2021-10-23 03:06:03 +02001152 depends on SPL
1153 help
1154 Defining this option allows to add some board-specific code (calling
1155 a user-provided function show_boot_progress(int) that enables you to
1156 show the system's boot progress on some display (for example, some
1157 LEDs) on your board. For details see SHOW_BOOT_PROGRESS.
1158
Simon Glass75e65cc2020-09-10 20:21:14 -06001159endmenu
1160
Simon Glass7b6baa32020-09-10 20:21:15 -06001161menu "Boot media"
1162
1163config NOR_BOOT
1164 bool "Support for booting from NOR flash"
1165 depends on NOR
1166 help
1167 Enabling this will make a U-Boot binary that is capable of being
1168 booted via NOR. In this case we will enable certain pinmux early
1169 as the ROM only partially sets up pinmux. We also default to using
1170 NOR for environment.
1171
1172config NAND_BOOT
1173 bool "Support for booting from NAND flash"
Simon Glass7b6baa32020-09-10 20:21:15 -06001174 imply MTD_RAW_NAND
1175 help
1176 Enabling this will make a U-Boot binary that is capable of being
1177 booted via NAND flash. This is not a must, some SoCs need this,
1178 some not.
1179
1180config ONENAND_BOOT
1181 bool "Support for booting from ONENAND"
Simon Glass7b6baa32020-09-10 20:21:15 -06001182 imply MTD_RAW_NAND
1183 help
1184 Enabling this will make a U-Boot binary that is capable of being
1185 booted via ONENAND. This is not a must, some SoCs need this,
1186 some not.
1187
1188config QSPI_BOOT
1189 bool "Support for booting from QSPI flash"
Simon Glass7b6baa32020-09-10 20:21:15 -06001190 help
1191 Enabling this will make a U-Boot binary that is capable of being
1192 booted via QSPI flash. This is not a must, some SoCs need this,
1193 some not.
1194
1195config SATA_BOOT
1196 bool "Support for booting from SATA"
Simon Glass7b6baa32020-09-10 20:21:15 -06001197 help
1198 Enabling this will make a U-Boot binary that is capable of being
1199 booted via SATA. This is not a must, some SoCs need this,
1200 some not.
1201
1202config SD_BOOT
1203 bool "Support for booting from SD/EMMC"
Simon Glass7b6baa32020-09-10 20:21:15 -06001204 help
1205 Enabling this will make a U-Boot binary that is capable of being
1206 booted via SD/EMMC. This is not a must, some SoCs need this,
1207 some not.
1208
Tom Rini66e0e2b2021-12-11 14:55:50 -05001209config SD_BOOT_QSPI
1210 bool "Support for booting from SD/EMMC and enable QSPI"
1211 help
1212 Enabling this will make a U-Boot binary that is capable of being
1213 booted via SD/EMMC while enabling QSPI on the platform as well. This
1214 is not a must, some SoCs need this, some not.
1215
Simon Glass7b6baa32020-09-10 20:21:15 -06001216config SPI_BOOT
1217 bool "Support for booting from SPI flash"
Simon Glass7b6baa32020-09-10 20:21:15 -06001218 help
1219 Enabling this will make a U-Boot binary that is capable of being
1220 booted via SPI flash. This is not a must, some SoCs need this,
1221 some not.
1222
1223endmenu
1224
Simon Glass98eed0d2020-09-10 20:21:16 -06001225menu "Autoboot options"
1226
1227config AUTOBOOT
1228 bool "Autoboot"
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001229 depends on CMDLINE
Simon Glass98eed0d2020-09-10 20:21:16 -06001230 default y
1231 help
1232 This enables the autoboot. See doc/README.autoboot for detail.
1233
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001234if AUTOBOOT
1235
Simon Glass95fd4f32020-09-10 20:21:17 -06001236config BOOTDELAY
1237 int "delay in seconds before automatically booting"
1238 default 2
Simon Glass95fd4f32020-09-10 20:21:17 -06001239 help
1240 Delay before automatically running bootcmd;
1241 set to 0 to autoboot with no delay, but you can stop it by key input.
1242 set to -1 to disable autoboot.
1243 set to -2 to autoboot with no delay and not check for abort
1244
1245 If this value is >= 0 then it is also used for the default delay
1246 before starting the default entry in bootmenu. If it is < 0 then
1247 a default value of 10s is used.
1248
1249 See doc/README.autoboot for details.
1250
Simon Glass98eed0d2020-09-10 20:21:16 -06001251config AUTOBOOT_KEYED
1252 bool "Stop autobooting via specific input key / string"
Simon Glass98eed0d2020-09-10 20:21:16 -06001253 help
1254 This option enables stopping (aborting) of the automatic
1255 boot feature only by issuing a specific input key or
1256 string. If not enabled, any input key will abort the
1257 U-Boot automatic booting process and bring the device
1258 to the U-Boot prompt for user input.
1259
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001260if AUTOBOOT_KEYED
1261
Steffen Jaeckeld199c3a2021-07-08 15:57:38 +02001262config AUTOBOOT_FLUSH_STDIN
1263 bool "Enable flushing stdin before starting to read the password"
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001264 depends on !SANDBOX
Steffen Jaeckeld199c3a2021-07-08 15:57:38 +02001265 help
1266 When this option is enabled stdin buffer will be flushed before
1267 starting to read the password.
1268 This can't be enabled for the sandbox as flushing stdin would
1269 break the autoboot unit tests.
1270
Simon Glass98eed0d2020-09-10 20:21:16 -06001271config AUTOBOOT_PROMPT
1272 string "Autoboot stop prompt"
Simon Glass98eed0d2020-09-10 20:21:16 -06001273 default "Autoboot in %d seconds\\n"
1274 help
1275 This string is displayed before the boot delay selected by
1276 CONFIG_BOOTDELAY starts. If it is not defined there is no
1277 output indicating that autoboot is in progress.
1278
1279 Note that this define is used as the (only) argument to a
1280 printf() call, so it may contain '%' format specifications,
1281 provided that it also includes, sepearated by commas exactly
1282 like in a printf statement, the required arguments. It is
1283 the responsibility of the user to select only such arguments
1284 that are valid in the given context.
1285
1286config AUTOBOOT_ENCRYPTION
1287 bool "Enable encryption in autoboot stopping"
Simon Glass98eed0d2020-09-10 20:21:16 -06001288 help
1289 This option allows a string to be entered into U-Boot to stop the
Steffen Jaeckel1a4a7782021-07-08 15:57:35 +02001290 autoboot.
1291 The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
1292 or not.
1293 In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
1294 to the crypt-based functionality and be compared against the
1295 string in the environment variable 'bootstopkeycrypt'.
1296 In case CONFIG_CRYPT_PW is disabled the string itself is hashed
1297 and compared against the hash in the environment variable
1298 'bootstopkeysha256'.
1299 If it matches in either case then boot stops and
1300 a command-line prompt is presented.
Simon Glass98eed0d2020-09-10 20:21:16 -06001301 This provides a way to ship a secure production device which can also
1302 be accessed at the U-Boot command line.
1303
Steffen Jaeckel33198742021-07-08 15:57:39 +02001304config AUTOBOOT_SHA256_FALLBACK
1305 bool "Allow fallback from crypt-hashed password to sha256"
1306 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
1307 help
1308 This option adds support to fall back from crypt-hashed
1309 passwords to checking a SHA256 hashed password in case the
1310 'bootstopusesha256' environment variable is set to 'true'.
1311
Simon Glass98eed0d2020-09-10 20:21:16 -06001312config AUTOBOOT_DELAY_STR
1313 string "Delay autobooting via specific input key / string"
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001314 depends on !AUTOBOOT_ENCRYPTION
Simon Glass98eed0d2020-09-10 20:21:16 -06001315 help
1316 This option delays the automatic boot feature by issuing
1317 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
1318 or the environment variable "bootdelaykey" is specified
1319 and this string is received from console input before
1320 autoboot starts booting, U-Boot gives a command prompt. The
1321 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
1322 used, otherwise it never times out.
1323
1324config AUTOBOOT_STOP_STR
1325 string "Stop autobooting via specific input key / string"
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001326 depends on !AUTOBOOT_ENCRYPTION
Simon Glass98eed0d2020-09-10 20:21:16 -06001327 help
1328 This option enables stopping (aborting) of the automatic
1329 boot feature only by issuing a specific input key or
1330 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
1331 variable "bootstopkey" is specified and this string is
1332 received from console input before autoboot starts booting,
1333 U-Boot gives a command prompt. The U-Boot prompt never
1334 times out, even if CONFIG_BOOT_RETRY_TIME is used.
1335
1336config AUTOBOOT_KEYED_CTRLC
1337 bool "Enable Ctrl-C autoboot interruption"
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001338 depends on !AUTOBOOT_ENCRYPTION
Simon Glass98eed0d2020-09-10 20:21:16 -06001339 help
1340 This option allows for the boot sequence to be interrupted
1341 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
1342 Setting this variable provides an escape sequence from the
1343 limited "password" strings.
1344
Steffen Jaeckel6c0ce6d2021-07-08 15:57:37 +02001345config AUTOBOOT_NEVER_TIMEOUT
1346 bool "Make the password entry never time-out"
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001347 depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
Steffen Jaeckel6c0ce6d2021-07-08 15:57:37 +02001348 help
1349 This option removes the timeout from the password entry
1350 when the user first presses the <Enter> key before entering
1351 any other character.
1352
Steffen Jaeckel1a4a7782021-07-08 15:57:35 +02001353config AUTOBOOT_STOP_STR_ENABLE
1354 bool "Enable fixed string to stop autobooting"
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001355 depends on AUTOBOOT_ENCRYPTION
Steffen Jaeckel1a4a7782021-07-08 15:57:35 +02001356 help
1357 This option enables the feature to add a fixed stop
1358 string that is defined at compile time.
1359 In every case it will be tried to load the stop
1360 string from the environment.
1361 In case this is enabled and there is no stop string
1362 in the environment, this will be used as default value.
1363
1364config AUTOBOOT_STOP_STR_CRYPT
1365 string "Stop autobooting via crypt-hashed password"
1366 depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
1367 help
1368 This option adds the feature to only stop the autobooting,
1369 and therefore boot into the U-Boot prompt, when the input
1370 string / password matches a values that is hashed via
1371 one of the supported crypt-style password hashing options
1372 and saved in the environment variable "bootstopkeycrypt".
1373
Simon Glass98eed0d2020-09-10 20:21:16 -06001374config AUTOBOOT_STOP_STR_SHA256
Steffen Jaeckel25c8b9f2021-07-08 15:57:40 +02001375 string "Stop autobooting via SHA256 hashed password"
Steffen Jaeckel1a4a7782021-07-08 15:57:35 +02001376 depends on AUTOBOOT_STOP_STR_ENABLE
Simon Glass98eed0d2020-09-10 20:21:16 -06001377 help
1378 This option adds the feature to only stop the autobooting,
1379 and therefore boot into the U-Boot prompt, when the input
1380 string / password matches a values that is encypted via
Joel Peshkin652b5042020-11-21 17:18:59 -08001381 a SHA256 hash and saved in the environment variable
1382 "bootstopkeysha256". If the value in that variable
1383 includes a ":", the portion prior to the ":" will be treated
1384 as a salt value.
Simon Glass98eed0d2020-09-10 20:21:16 -06001385
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001386endif # AUTOBOOT_KEYED
1387
1388if !AUTOBOOT_KEYED
1389
Simon Glass98eed0d2020-09-10 20:21:16 -06001390config AUTOBOOT_USE_MENUKEY
1391 bool "Allow a specify key to run a menu from the environment"
Simon Glass98eed0d2020-09-10 20:21:16 -06001392 help
1393 If a specific key is pressed to stop autoboot, then the commands in
1394 the environment variable 'menucmd' are executed before boot starts.
1395
1396config AUTOBOOT_MENUKEY
1397 int "ASCII value of boot key to show a menu"
1398 default 0
1399 depends on AUTOBOOT_USE_MENUKEY
1400 help
1401 If this key is pressed to stop autoboot, then the commands in the
1402 environment variable 'menucmd' will be executed before boot starts.
1403 For example, 33 means "!" in ASCII, so pressing ! at boot would take
1404 this action.
1405
Simon Glass5bcfc7a2023-10-26 14:31:22 -04001406endif
1407
1408endif # AUTOBOOT
1409
Simon Glass98eed0d2020-09-10 20:21:16 -06001410config AUTOBOOT_MENU_SHOW
1411 bool "Show a menu on boot"
1412 depends on CMD_BOOTMENU
1413 help
1414 This enables the boot menu, controlled by environment variables
1415 defined by the board. The menu starts after running the 'preboot'
1416 environmnent variable (if enabled) and before handling the boot delay.
Peter Robinsond1670622023-08-18 15:54:10 +01001417 See doc/usage/cmd/bootmenu.rst for more details.
Simon Glass98eed0d2020-09-10 20:21:16 -06001418
Masahisa Kojima83f73632022-05-26 19:09:38 +09001419config BOOTMENU_DISABLE_UBOOT_CONSOLE
1420 bool "Disallow bootmenu to enter the U-Boot console"
1421 depends on AUTOBOOT_MENU_SHOW
1422 help
1423 If this option is enabled, user can not enter the U-Boot console from
1424 bootmenu. It increases the system security.
1425
Tom Rini69c8a812022-03-11 09:12:04 -05001426config BOOT_RETRY
1427 bool "Boot retry feature"
1428 help
1429 Allow for having the U-Boot command prompt time out and attempt
1430 to boot again. If the environment variable "bootretry" is found then
1431 its value is used, otherwise the retry timeout is
1432 CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
1433 defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
1434
1435config BOOT_RETRY_TIME
1436 int "Timeout in seconds before attempting to boot again"
1437 depends on BOOT_RETRY
1438 help
1439 Time in seconds before the U-Boot prompt will timeout and boot will
1440 be attempted again.
1441
1442config BOOT_RETRY_MIN
1443 int "Minimum timeout in seconds for 'bootretry'"
1444 depends on BOOT_RETRY
1445 default BOOT_RETRY_TIME
1446 help
1447 The minimum time in seconds that "bootretry" can be set to.
1448
1449config RESET_TO_RETRY
1450 bool "Reset the board to retry autoboot"
1451 depends on BOOT_RETRY
1452 help
1453 After the countdown timed out, the board will be reset to restart
1454 again.
1455
Simon Glass98eed0d2020-09-10 20:21:16 -06001456endmenu
1457
Philippe Reynes98220742022-03-28 22:56:59 +02001458menu "Image support"
1459
1460config IMAGE_PRE_LOAD
1461 bool "Image pre-load support"
1462 help
1463 Enable an image pre-load stage in the SPL.
1464 This pre-load stage allows to do some manipulation
1465 or check (for example signature check) on an image
1466 before launching it.
1467
1468config SPL_IMAGE_PRE_LOAD
1469 bool "Image pre-load support within SPL"
1470 depends on SPL && IMAGE_PRE_LOAD
1471 help
1472 Enable an image pre-load stage in the SPL.
1473 This pre-load stage allows to do some manipulation
1474 or check (for example signature check) on an image
1475 before launching it.
1476
1477config IMAGE_PRE_LOAD_SIG
1478 bool "Image pre-load signature support"
1479 depends on IMAGE_PRE_LOAD
1480 select FIT_SIGNATURE
1481 select RSA
1482 select RSA_VERIFY_WITH_PKEY
1483 help
1484 Enable signature check support in the pre-load stage.
1485 For this feature a very simple header is added before
1486 the image with few fields:
1487 - a magic
1488 - the image size
1489 - the signature
1490 All other information (header size, type of signature,
1491 ...) are provided in the node /image/pre-load/sig of
1492 u-boot.
1493
1494config SPL_IMAGE_PRE_LOAD_SIG
1495 bool "Image pre-load signature support witin SPL"
1496 depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
1497 select SPL_FIT_SIGNATURE
1498 select SPL_RSA
1499 select SPL_RSA_VERIFY_WITH_PKEY
1500 help
1501 Enable signature check support in the pre-load stage in the SPL.
1502 For this feature a very simple header is added before
1503 the image with few fields:
1504 - a magic
1505 - the image size
1506 - the signature
1507 All other information (header size, type of signature,
1508 ...) are provided in the node /image/pre-load/sig of
1509 u-boot.
1510
1511endmenu
1512
Simon Glassddc5f9b2023-09-14 10:55:46 -06001513if OF_LIBFDT
1514
1515menu "Devicetree fixup"
1516
Matthias Schiffere91d6602023-12-11 12:03:17 +01001517config OF_ENV_SETUP
1518 bool "Run a command from environment to set up device tree before boot"
1519 depends on CMD_FDT
1520 help
1521 This causes U-Boot to run a command from the environment variable
1522 fdt_fixup before booting into the operating system, which can use the
1523 fdt command to modify the device tree. The device tree is then passed
1524 to the OS.
1525
Simon Glass96095e12023-09-14 10:55:47 -06001526config OF_BOARD_SETUP
1527 bool "Set up board-specific details in device tree before boot"
1528 help
1529 This causes U-Boot to call ft_board_setup() before booting into
1530 the Operating System. This function can set up various
1531 board-specific information in the device tree for use by the OS.
1532 The device tree is then passed to the OS.
1533
1534config OF_SYSTEM_SETUP
1535 bool "Set up system-specific details in device tree before boot"
1536 help
1537 This causes U-Boot to call ft_system_setup() before booting into
1538 the Operating System. This function can set up various
1539 system-specific information in the device tree for use by the OS.
1540 The device tree is then passed to the OS.
1541
1542config OF_STDOUT_VIA_ALIAS
1543 bool "Update the device-tree stdout alias from U-Boot"
1544 help
1545 This uses U-Boot's serial alias from the aliases node to update
1546 the device tree passed to the OS. The "linux,stdout-path" property
1547 in the chosen node is set to point to the correct serial node.
1548 This option currently references CONFIG_CONS_INDEX, which is
1549 incorrect when used with device tree as this option does not
1550 exist / should not be used.
1551
Simon Glass040a6042023-09-14 10:55:57 -06001552config FDT_FIXUP_PARTITIONS
Simon Glass400a6a32023-09-14 10:55:58 -06001553 bool "Overwrite MTD partitions in DTS through defined in 'mtdparts'"
Simon Glass040a6042023-09-14 10:55:57 -06001554 help
1555 Allow overwriting defined partitions in the device tree blob
1556 using partition info defined in the 'mtdparts' environment
1557 variable.
1558
Simon Glassddc5f9b2023-09-14 10:55:46 -06001559config FDT_SIMPLEFB
1560 bool "FDT tools for simplefb support"
1561 help
1562 Enable the fdt tools to manage the simple fb nodes in device tree.
1563 These functions can be used by board to indicate to the OS
1564 the presence of the simple frame buffer with associated reserved
1565 memory
1566
Simon Glassc0e5b0e2023-09-14 10:55:59 -06001567config ARCH_FIXUP_FDT_MEMORY
1568 bool "Enable arch_fixup_memory_banks() call"
1569 default y
1570 help
1571 Enable FDT memory map syncup before OS boot. This feature can be
1572 used for booting OS with different memory setup where the part of
1573 the memory location should be used for different purpose.
1574
Simon Glassddc5f9b2023-09-14 10:55:46 -06001575endmenu
1576
1577endif # OF_LIBFDT
1578
Simon Glassfe5db252020-09-10 20:21:18 -06001579config USE_BOOTARGS
1580 bool "Enable boot arguments"
1581 help
1582 Provide boot arguments to bootm command. Boot arguments are specified
1583 in CONFIG_BOOTARGS option. Enable this option to be able to specify
1584 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
1585 will be undefined and won't take any space in U-Boot image.
1586
1587config BOOTARGS
1588 string "Boot arguments"
1589 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
1590 help
1591 This can be used to pass arguments to the bootm command. The value of
1592 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
1593 this value will also override the "chosen" node in FDT blob.
1594
Simon Glass51bb3382020-11-05 10:33:48 -07001595config BOOTARGS_SUBST
1596 bool "Support substituting strings in boot arguments"
1597 help
1598 This allows substituting string values in the boot arguments. These
1599 are applied after the commandline has been built.
1600
1601 One use for this is to insert the root-disk UUID into the command
1602 line where bootargs contains "root=${uuid}"
1603
1604 setenv bootargs "console= root=${uuid}"
1605 # Set the 'uuid' environment variable
1606 part uuid mmc 2:2 uuid
1607
1608 # Command-line substitution will put the real uuid into the
1609 # kernel command line
1610 bootm
1611
Simon Glassfe5db252020-09-10 20:21:18 -06001612config USE_BOOTCOMMAND
1613 bool "Enable a default value for bootcmd"
Tom Rinidbdb4b32023-10-26 14:31:28 -04001614 depends on CMDLINE
Simon Glassfe5db252020-09-10 20:21:18 -06001615 help
1616 Provide a default value for the bootcmd entry in the environment. If
1617 autoboot is enabled this is what will be run automatically. Enable
1618 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
1619 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
1620 won't take any space in U-Boot image.
1621
1622config BOOTCOMMAND
1623 string "bootcmd value"
1624 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
Simon Glassd8d40bc2023-05-06 08:27:09 -06001625 default "bootflow scan -lb" if BOOTSTD_DEFAULTS && CMD_BOOTFLOW_FULL
1626 default "bootflow scan" if BOOTSTD_DEFAULTS && !CMD_BOOTFLOW_FULL
Simon Glassa91492b2022-04-24 23:31:27 -06001627 default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS
Simon Glassfe5db252020-09-10 20:21:18 -06001628 help
1629 This is the string of commands that will be used as bootcmd and if
1630 AUTOBOOT is set, automatically run.
1631
1632config USE_PREBOOT
1633 bool "Enable preboot"
Tom Rinidbdb4b32023-10-26 14:31:28 -04001634 depends on CMDLINE
Simon Glassfe5db252020-09-10 20:21:18 -06001635 help
1636 When this option is enabled, the existence of the environment
1637 variable "preboot" will be checked immediately before starting the
1638 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
1639 entering interactive mode.
1640
1641 This feature is especially useful when "preboot" is automatically
1642 generated or modified. For example, the boot code can modify the
1643 "preboot" when a user holds down a certain combination of keys.
1644
1645config PREBOOT
1646 string "preboot default value"
1647 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
Patrick Delaunay87459da2020-10-12 09:47:50 +02001648 default "usb start" if USB_KEYBOARD
Simon Glassfe5db252020-09-10 20:21:18 -06001649 default ""
1650 help
1651 This is the default of "preboot" environment variable.
1652
Pali Rohár2827c2f2022-07-10 13:42:55 +02001653config PREBOOT_DEFINED
1654 bool
1655 default y if PREBOOT != ""
1656
Simon Glass832876a2020-09-10 20:21:20 -06001657config DEFAULT_FDT_FILE
1658 string "Default fdt file"
1659 help
1660 This option is used to set the default fdt file to boot OS.
1661
Dzmitry Sankouski12a3e1a2022-02-22 21:49:52 +03001662config SAVE_PREV_BL_FDT_ADDR
1663 depends on ARM
1664 bool "Saves fdt address, passed by the previous bootloader, to env var"
1665 help
1666 When u-boot is used as a chain-loaded bootloader (replacing OS kernel),
1667 enable this option to save fdt address, passed by the
1668 previous bootloader for future use.
1669 Address is saved to `prevbl_fdt_addr` environment variable.
1670
1671 If no fdt was provided by previous bootloader, no env variables
1672 will be created.
1673
1674config SAVE_PREV_BL_INITRAMFS_START_ADDR
1675 depends on ARM
1676 bool "Saves initramfs address, passed by the previous bootloader, to env var"
1677 help
1678 When u-boot is used as a chain-loaded bootloader(replacing OS kernel),
1679 enable this option to save initramfs address, passed by the
1680 previous bootloader for future use.
1681 Address is saved to `prevbl_initrd_start_addr` environment variable.
1682
1683 If no initramfs was provided by previous bootloader, no env variables
1684 will be created.
1685
Simon Glassa0874dc2023-06-01 10:23:02 -06001686menu "Configuration editor"
1687
1688config CEDIT
1689 bool "Configuration editor"
1690 depends on BOOTSTD
1691 help
1692 Provides a way to deal with board configuration and present it to
1693 the user for adjustment.
1694
1695 This is intended to provide both graphical and text-based user
1696 interfaces, but only graphical is support at present.
1697
1698endmenu # Configuration editor
1699
Simon Glasscf298162020-09-10 20:21:13 -06001700endmenu # Booting