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