blob: 5a18d62d78007db39cbb96de442ec16b61f6d3b0 [file] [log] [blame]
Simon Glasscf298162020-09-10 20:21:13 -06001menu "Boot options"
2
3menu "Boot images"
4
5config ANDROID_BOOT_IMAGE
6 bool "Enable support for Android Boot Images"
7 default y if FASTBOOT
8 help
9 This enables support for booting images which use the Android
10 image format header.
11
12config FIT
13 bool "Support Flattened Image Tree"
14 select MD5
15 select SHA1
16 help
17 This option allows you to boot the new uImage structure,
18 Flattened Image Tree. FIT is formally a FDT, which can include
19 images of various types (kernel, FDT blob, ramdisk, etc.)
20 in a single blob. To boot this new uImage structure,
21 pass the address of the blob to the "bootm" command.
22 FIT is very flexible, supporting compression, multiple images,
23 multiple configurations, verification through hashing and also
24 verified boot (secure boot using RSA).
25
26if FIT
27
28config FIT_EXTERNAL_OFFSET
29 hex "FIT external data offset"
30 default 0x0
31 help
32 This specifies a data offset in fit image.
33 The offset is from data payload offset to the beginning of
34 fit image header. When specifies a offset, specific data
35 could be put in the hole between data payload and fit image
36 header, such as CSF data on i.MX platform.
37
38config FIT_ENABLE_SHA256_SUPPORT
39 bool "Support SHA256 checksum of FIT image contents"
40 default y
41 select SHA256
42 help
43 Enable this to support SHA256 checksum of FIT image contents. A
44 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
45 the image contents have not been corrupted.
46
47config FIT_ENABLE_SHA384_SUPPORT
48 bool "Support SHA384 checksum of FIT image contents"
49 default n
50 select SHA384
51 help
52 Enable this to support SHA384 checksum of FIT image contents. A
53 SHA384 checksum is a 384-bit (48-byte) hash value used to check that
54 the image contents have not been corrupted. Use this for the highest
55 security.
56
57config FIT_ENABLE_SHA512_SUPPORT
58 bool "Support SHA512 checksum of FIT image contents"
59 default n
60 select SHA512
61 help
62 Enable this to support SHA512 checksum of FIT image contents. A
63 SHA512 checksum is a 512-bit (64-byte) hash value used to check that
64 the image contents have not been corrupted.
65
Simon Glass6f3c2d82021-02-15 17:08:10 -070066config FIT_FULL_CHECK
67 bool "Do a full check of the FIT before using it"
68 default y
69 help
70 Enable this do a full check of the FIT to make sure it is valid. This
71 helps to protect against carefully crafted FITs which take advantage
72 of bugs or omissions in the code. This includes a bad structure,
73 multiple root nodes and the like.
74
Simon Glasscf298162020-09-10 20:21:13 -060075config FIT_SIGNATURE
76 bool "Enable signature verification of FIT uImages"
77 depends on DM
78 select HASH
79 select RSA
80 select RSA_VERIFY
81 select IMAGE_SIGN_INFO
Simon Glass6f3c2d82021-02-15 17:08:10 -070082 select FIT_FULL_CHECK
Simon Glasscf298162020-09-10 20:21:13 -060083 help
84 This option enables signature verification of FIT uImages,
85 using a hash signed and verified using RSA. If
86 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
87 hashing is available using hardware, then the RSA library will use
88 it. See doc/uImage.FIT/signature.txt for more details.
89
90 WARNING: When relying on signed FIT images with a required signature
91 check the legacy image format is disabled by default, so that
92 unsigned images cannot be loaded. If a board needs the legacy image
93 format support in this case, enable it using
94 CONFIG_LEGACY_IMAGE_FORMAT.
95
96config FIT_SIGNATURE_MAX_SIZE
97 hex "Max size of signed FIT structures"
98 depends on FIT_SIGNATURE
99 default 0x10000000
100 help
101 This option sets a max size in bytes for verified FIT uImages.
102 A sane value of 256MB protects corrupted DTB structures from overlapping
103 device memory. Assure this size does not extend past expected storage
104 space.
105
106config FIT_ENABLE_RSASSA_PSS_SUPPORT
107 bool "Support rsassa-pss signature scheme of FIT image contents"
108 depends on FIT_SIGNATURE
109 default n
110 help
111 Enable this to support the pss padding algorithm as described
112 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
113
114config FIT_CIPHER
115 bool "Enable ciphering data in a FIT uImages"
116 depends on DM
117 select AES
118 help
119 Enable the feature of data ciphering/unciphering in the tool mkimage
120 and in the u-boot support of the FIT image.
121
122config FIT_VERBOSE
123 bool "Show verbose messages when FIT images fail"
124 help
125 Generally a system will have valid FIT images so debug messages
126 are a waste of code space. If you are debugging your images then
127 you can enable this option to get more verbose information about
128 failures.
129
130config FIT_BEST_MATCH
131 bool "Select the best match for the kernel device tree"
132 help
133 When no configuration is explicitly selected, default to the
134 one whose fdt's compatibility field best matches that of
135 U-Boot itself. A match is considered "best" if it matches the
136 most specific compatibility entry of U-Boot's fdt's root node.
137 The order of entries in the configuration's fdt is ignored.
138
139config FIT_IMAGE_POST_PROCESS
140 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
Siew Chin Lim1bc20892021-03-01 20:04:11 +0800141 depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
Simon Glasscf298162020-09-10 20:21:13 -0600142 help
143 Allows doing any sort of manipulation to blobs after they got extracted
144 from FIT images like stripping off headers or modifying the size of the
145 blob, verification, authentication, decryption etc. in a platform or
146 board specific way. In order to use this feature a platform or board-
147 specific implementation of board_fit_image_post_process() must be
148 provided. Also, anything done during this post-processing step would
149 need to be comprehended in how the images were prepared before being
150 injected into the FIT creation (i.e. the blobs would have been pre-
151 processed before being added to the FIT image).
152
Ravik Hasija7a018822021-01-27 14:01:48 -0800153config FIT_PRINT
154 bool "Support FIT printing"
155 default y
156 help
157 Support printing the content of the fitImage in a verbose manner.
158
Simon Glasscf298162020-09-10 20:21:13 -0600159if SPL
160
161config SPL_FIT
162 bool "Support Flattened Image Tree within SPL"
163 depends on SPL
164 select SPL_OF_LIBFDT
165
166config SPL_FIT_PRINT
167 bool "Support FIT printing within SPL"
168 depends on SPL_FIT
169 help
170 Support printing the content of the fitImage in a verbose manner in SPL.
171
Simon Glass6f3c2d82021-02-15 17:08:10 -0700172config SPL_FIT_FULL_CHECK
173 bool "Do a full check of the FIT before using it"
174 help
175 Enable this do a full check of the FIT to make sure it is valid. This
176 helps to protect against carefully crafted FITs which take advantage
177 of bugs or omissions in the code. This includes a bad structure,
178 multiple root nodes and the like.
179
180
Simon Glasscf298162020-09-10 20:21:13 -0600181config SPL_FIT_SIGNATURE
182 bool "Enable signature verification of FIT firmware within SPL"
183 depends on SPL_DM
Klaus Heinrich Kiwibdb7f262021-02-09 15:41:54 -0300184 depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
Klaus Heinrich Kiwi6ce28132021-02-09 15:41:53 -0300185 select FIT_SIGNATURE
Simon Glasscf298162020-09-10 20:21:13 -0600186 select SPL_FIT
187 select SPL_CRYPTO_SUPPORT
188 select SPL_HASH_SUPPORT
189 select SPL_RSA
190 select SPL_RSA_VERIFY
191 select SPL_IMAGE_SIGN_INFO
Simon Glass6f3c2d82021-02-15 17:08:10 -0700192 select SPL_FIT_FULL_CHECK
Simon Glasscf298162020-09-10 20:21:13 -0600193
194config SPL_LOAD_FIT
195 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
196 select SPL_FIT
197 help
198 Normally with the SPL framework a legacy image is generated as part
199 of the build. This contains U-Boot along with information as to
200 where it should be loaded. This option instead enables generation
201 of a FIT (Flat Image Tree) which provides more flexibility. In
202 particular it can handle selecting from multiple device tree
203 and passing the correct one to U-Boot.
204
Alexandru Gagniucdf51ae72021-03-29 12:05:15 -0500205 This path has the following limitations:
206
207 1. "loadables" images, other than FTDs, which do not have a "load"
208 property will not be loaded. This limitation also applies to FPGA
209 images with the correct "compatible" string.
210 2. For FPGA images, only the "compatible" = "u-boot,fpga-legacy"
211 loading method is supported.
212 3. FDTs are only loaded for images with an "os" property of "u-boot".
213 "linux" images are also supported with Falcon boot mode.
214
Simon Glasscf298162020-09-10 20:21:13 -0600215config SPL_LOAD_FIT_ADDRESS
216 hex "load address of fit image"
217 depends on SPL_LOAD_FIT
218 default 0x0
219 help
220 Specify the load address of the fit image that will be loaded
221 by SPL.
222
223config SPL_LOAD_FIT_APPLY_OVERLAY
224 bool "Enable SPL applying DT overlays from FIT"
225 depends on SPL_LOAD_FIT
226 select OF_LIBFDT_OVERLAY
227 help
228 The device tree is loaded from the FIT image. Allow the SPL is to
229 also load device-tree overlays from the FIT image an apply them
230 over the device tree.
231
232config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
233 depends on SPL_LOAD_FIT_APPLY_OVERLAY
234 default 0x10000
235 hex "size of temporary buffer used to load the overlays"
236 help
237 The size of the area where the overlays will be loaded and
238 uncompress. Must be at least as large as biggest overlay
239 (uncompressed)
240
241config SPL_LOAD_FIT_FULL
242 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
243 select SPL_FIT
244 help
245 Normally with the SPL framework a legacy image is generated as part
246 of the build. This contains U-Boot along with information as to
247 where it should be loaded. This option instead enables generation
248 of a FIT (Flat Image Tree) which provides more flexibility. In
249 particular it can handle selecting from multiple device tree
250 and passing the correct one to U-Boot.
251
252config SPL_FIT_IMAGE_POST_PROCESS
253 bool "Enable post-processing of FIT artifacts after loading by the SPL"
254 depends on SPL_LOAD_FIT
255 help
256 Allows doing any sort of manipulation to blobs after they got extracted
257 from the U-Boot FIT image like stripping off headers or modifying the
258 size of the blob, verification, authentication, decryption etc. in a
259 platform or board specific way. In order to use this feature a platform
260 or board-specific implementation of board_fit_image_post_process() must
261 be provided. Also, anything done during this post-processing step would
262 need to be comprehended in how the images were prepared before being
263 injected into the FIT creation (i.e. the blobs would have been pre-
264 processed before being added to the FIT image).
265
266config SPL_FIT_SOURCE
267 string ".its source file for U-Boot FIT image"
268 depends on SPL_FIT
269 help
270 Specifies a (platform specific) FIT source file to generate the
271 U-Boot FIT image. This could specify further image to load and/or
272 execute.
273
274config USE_SPL_FIT_GENERATOR
275 bool "Use a script to generate the .its script"
276 default y if SPL_FIT && !ARCH_SUNXI
277
278config SPL_FIT_GENERATOR
279 string ".its file generator script for U-Boot FIT image"
280 depends on USE_SPL_FIT_GENERATOR
281 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
282 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
283 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
284 help
285 Specifies a (platform specific) script file to generate the FIT
286 source file used to build the U-Boot FIT image file. This gets
287 passed a list of supported device tree file stub names to
288 include in the generated image.
289
290endif # SPL
291
292endif # FIT
293
294config LEGACY_IMAGE_FORMAT
295 bool "Enable support for the legacy image format"
296 default y if !FIT_SIGNATURE
297 help
298 This option enables the legacy image format. It is enabled by
299 default for backward compatibility, unless FIT_SIGNATURE is
300 set where it is disabled so that unsigned images cannot be
301 loaded. If a board needs the legacy image format support in this
302 case, enable it here.
303
Simon Glassaefa34f2020-09-10 20:21:19 -0600304config SUPPORT_RAW_INITRD
305 bool "Enable raw initrd images"
306 help
307 Note, defining the SUPPORT_RAW_INITRD allows user to supply
308 kernel with raw initrd images. The syntax is slightly different, the
309 address of the initrd must be augmented by it's size, in the following
310 format: "<initrd address>:<initrd size>".
311
Simon Glasscf298162020-09-10 20:21:13 -0600312config OF_BOARD_SETUP
313 bool "Set up board-specific details in device tree before boot"
314 depends on OF_LIBFDT
315 help
316 This causes U-Boot to call ft_board_setup() before booting into
317 the Operating System. This function can set up various
318 board-specific information in the device tree for use by the OS.
319 The device tree is then passed to the OS.
320
321config OF_SYSTEM_SETUP
322 bool "Set up system-specific details in device tree before boot"
323 depends on OF_LIBFDT
324 help
325 This causes U-Boot to call ft_system_setup() before booting into
326 the Operating System. This function can set up various
327 system-specific information in the device tree for use by the OS.
328 The device tree is then passed to the OS.
329
330config OF_STDOUT_VIA_ALIAS
331 bool "Update the device-tree stdout alias from U-Boot"
332 depends on OF_LIBFDT
333 help
334 This uses U-Boot's serial alias from the aliases node to update
335 the device tree passed to the OS. The "linux,stdout-path" property
336 in the chosen node is set to point to the correct serial node.
337 This option currently references CONFIG_CONS_INDEX, which is
338 incorrect when used with device tree as this option does not
339 exist / should not be used.
340
341config SYS_EXTRA_OPTIONS
342 string "Extra Options (DEPRECATED)"
343 help
344 The old configuration infrastructure (= mkconfig + boards.cfg)
345 provided the extra options field. If you have something like
346 "HAS_BAR,BAZ=64", the optional options
347 #define CONFIG_HAS
348 #define CONFIG_BAZ 64
349 will be defined in include/config.h.
350 This option was prepared for the smooth migration from the old
351 configuration to Kconfig. Since this option will be removed sometime,
352 new boards should not use this option.
353
354config HAVE_SYS_TEXT_BASE
355 bool
356 depends on !NIOS2 && !XTENSA
357 depends on !EFI_APP
358 default y
359
360config SYS_TEXT_BASE
361 depends on HAVE_SYS_TEXT_BASE
362 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
363 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
364 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
365 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
366 hex "Text Base"
367 help
368 The address in memory that U-Boot will be running from, initially.
369
370config SYS_CLK_FREQ
371 depends on ARC || ARCH_SUNXI || MPC83xx
372 int "CPU clock frequency"
373 help
374 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
375
376config ARCH_FIXUP_FDT_MEMORY
377 bool "Enable arch_fixup_memory_banks() call"
378 default y
379 help
380 Enable FDT memory map syncup before OS boot. This feature can be
381 used for booting OS with different memory setup where the part of
382 the memory location should be used for different purpose.
383
Simon Glass96d0aa92020-11-04 09:57:35 -0700384config CHROMEOS
385 bool "Support booting Chrome OS"
386 help
387 Chrome OS requires U-Boot to set up a table indicating the boot mode
388 (e.g. Developer mode) and a few other things. Enable this if you are
389 booting on a Chromebook to avoid getting an error about an invalid
390 firmware ID.
391
392config CHROMEOS_VBOOT
393 bool "Support Chrome OS verified boot"
394 help
395 This is intended to enable the full Chrome OS verified boot support
396 in U-Boot. It is not actually implemented in the U-Boot source code
397 at present, so this option is always set to 'n'. It allows
398 distinguishing between booting Chrome OS in a basic way (developer
399 mode) and a full boot.
400
Simon Glasscf298162020-09-10 20:21:13 -0600401endmenu # Boot images
402
Simon Glass75e65cc2020-09-10 20:21:14 -0600403menu "Boot timing"
404
405config BOOTSTAGE
406 bool "Boot timing and reporting"
407 help
408 Enable recording of boot time while booting. To use it, insert
409 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
410 bootstage.h. Only a single entry is recorded for each ID. You can
411 give the entry a name with bootstage_mark_name(). You can also
412 record elapsed time in a particular stage using bootstage_start()
413 before starting and bootstage_accum() when finished. Bootstage will
414 add up all the accumulated time and report it.
415
416 Normally, IDs are defined in bootstage.h but a small number of
417 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
418 as the ID.
419
420 Calls to show_boot_progress() will also result in log entries but
421 these will not have names.
422
423config SPL_BOOTSTAGE
424 bool "Boot timing and reported in SPL"
425 depends on BOOTSTAGE
426 help
427 Enable recording of boot time in SPL. To make this visible to U-Boot
428 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
429 information when SPL finishes and load it when U-Boot proper starts
430 up.
431
432config TPL_BOOTSTAGE
433 bool "Boot timing and reported in TPL"
434 depends on BOOTSTAGE
435 help
436 Enable recording of boot time in SPL. To make this visible to U-Boot
437 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
438 information when TPL finishes and load it when U-Boot proper starts
439 up.
440
441config BOOTSTAGE_REPORT
442 bool "Display a detailed boot timing report before booting the OS"
443 depends on BOOTSTAGE
444 help
445 Enable output of a boot time report just before the OS is booted.
446 This shows how long it took U-Boot to go through each stage of the
447 boot process. The report looks something like this:
448
449 Timer summary in microseconds:
450 Mark Elapsed Stage
451 0 0 reset
452 3,575,678 3,575,678 board_init_f start
453 3,575,695 17 arch_cpu_init A9
454 3,575,777 82 arch_cpu_init done
455 3,659,598 83,821 board_init_r start
456 3,910,375 250,777 main_loop
457 29,916,167 26,005,792 bootm_start
458 30,361,327 445,160 start_kernel
459
460config BOOTSTAGE_RECORD_COUNT
461 int "Number of boot stage records to store"
Simon Glass939b04e2021-02-03 06:00:49 -0700462 depends on BOOTSTAGE
Simon Glass75e65cc2020-09-10 20:21:14 -0600463 default 30
464 help
465 This is the size of the bootstage record list and is the maximum
466 number of bootstage records that can be recorded.
467
468config SPL_BOOTSTAGE_RECORD_COUNT
469 int "Number of boot stage records to store for SPL"
Simon Glass939b04e2021-02-03 06:00:49 -0700470 depends on SPL_BOOTSTAGE
Simon Glass75e65cc2020-09-10 20:21:14 -0600471 default 5
472 help
473 This is the size of the bootstage record list and is the maximum
474 number of bootstage records that can be recorded.
475
476config TPL_BOOTSTAGE_RECORD_COUNT
477 int "Number of boot stage records to store for TPL"
Simon Glass939b04e2021-02-03 06:00:49 -0700478 depends on TPL_BOOTSTAGE
Simon Glass75e65cc2020-09-10 20:21:14 -0600479 default 5
480 help
481 This is the size of the bootstage record list and is the maximum
482 number of bootstage records that can be recorded.
483
484config BOOTSTAGE_FDT
485 bool "Store boot timing information in the OS device tree"
486 depends on BOOTSTAGE
487 help
488 Stash the bootstage information in the FDT. A root 'bootstage'
489 node is created with each bootstage id as a child. Each child
490 has a 'name' property and either 'mark' containing the
491 mark time in microseconds, or 'accum' containing the
492 accumulated time for that bootstage id in microseconds.
493 For example:
494
495 bootstage {
496 154 {
497 name = "board_init_f";
498 mark = <3575678>;
499 };
500 170 {
501 name = "lcd";
502 accum = <33482>;
503 };
504 };
505
506 Code in the Linux kernel can find this in /proc/devicetree.
507
508config BOOTSTAGE_STASH
509 bool "Stash the boot timing information in memory before booting OS"
510 depends on BOOTSTAGE
511 help
512 Some OSes do not support device tree. Bootstage can instead write
513 the boot timing information in a binary format at a given address.
514 This happens through a call to bootstage_stash(), typically in
515 the CPU's cleanup_before_linux() function. You can use the
516 'bootstage stash' and 'bootstage unstash' commands to do this on
517 the command line.
518
519config BOOTSTAGE_STASH_ADDR
520 hex "Address to stash boot timing information"
521 default 0
522 help
523 Provide an address which will not be overwritten by the OS when it
524 starts, so that it can read this information when ready.
525
526config BOOTSTAGE_STASH_SIZE
527 hex "Size of boot timing stash region"
528 default 0x1000
529 help
530 This should be large enough to hold the bootstage stash. A value of
531 4096 (4KiB) is normally plenty.
532
533config SHOW_BOOT_PROGRESS
534 bool "Show boot progress in a board-specific manner"
535 help
536 Defining this option allows to add some board-specific code (calling
537 a user-provided function show_boot_progress(int) that enables you to
538 show the system's boot progress on some display (for example, some
539 LEDs) on your board. At the moment, the following checkpoints are
540 implemented:
541
542 Legacy uImage format:
543
544 Arg Where When
545 1 common/cmd_bootm.c before attempting to boot an image
546 -1 common/cmd_bootm.c Image header has bad magic number
547 2 common/cmd_bootm.c Image header has correct magic number
548 -2 common/cmd_bootm.c Image header has bad checksum
549 3 common/cmd_bootm.c Image header has correct checksum
550 -3 common/cmd_bootm.c Image data has bad checksum
551 4 common/cmd_bootm.c Image data has correct checksum
552 -4 common/cmd_bootm.c Image is for unsupported architecture
553 5 common/cmd_bootm.c Architecture check OK
554 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
555 6 common/cmd_bootm.c Image Type check OK
556 -6 common/cmd_bootm.c gunzip uncompression error
557 -7 common/cmd_bootm.c Unimplemented compression type
558 7 common/cmd_bootm.c Uncompression OK
559 8 common/cmd_bootm.c No uncompress/copy overwrite error
560 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
561
562 9 common/image.c Start initial ramdisk verification
563 -10 common/image.c Ramdisk header has bad magic number
564 -11 common/image.c Ramdisk header has bad checksum
565 10 common/image.c Ramdisk header is OK
566 -12 common/image.c Ramdisk data has bad checksum
567 11 common/image.c Ramdisk data has correct checksum
568 12 common/image.c Ramdisk verification complete, start loading
569 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
570 13 common/image.c Start multifile image verification
571 14 common/image.c No initial ramdisk, no multifile, continue.
572
573 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
574
575 -30 arch/powerpc/lib/board.c Fatal error, hang the system
576 -31 post/post.c POST test failed, detected by post_output_backlog()
577 -32 post/post.c POST test failed, detected by post_run_single()
578
579 34 common/cmd_doc.c before loading a Image from a DOC device
580 -35 common/cmd_doc.c Bad usage of "doc" command
581 35 common/cmd_doc.c correct usage of "doc" command
582 -36 common/cmd_doc.c No boot device
583 36 common/cmd_doc.c correct boot device
584 -37 common/cmd_doc.c Unknown Chip ID on boot device
585 37 common/cmd_doc.c correct chip ID found, device available
586 -38 common/cmd_doc.c Read Error on boot device
587 38 common/cmd_doc.c reading Image header from DOC device OK
588 -39 common/cmd_doc.c Image header has bad magic number
589 39 common/cmd_doc.c Image header has correct magic number
590 -40 common/cmd_doc.c Error reading Image from DOC device
591 40 common/cmd_doc.c Image header has correct magic number
592 41 common/cmd_ide.c before loading a Image from a IDE device
593 -42 common/cmd_ide.c Bad usage of "ide" command
594 42 common/cmd_ide.c correct usage of "ide" command
595 -43 common/cmd_ide.c No boot device
596 43 common/cmd_ide.c boot device found
597 -44 common/cmd_ide.c Device not available
598 44 common/cmd_ide.c Device available
599 -45 common/cmd_ide.c wrong partition selected
600 45 common/cmd_ide.c partition selected
601 -46 common/cmd_ide.c Unknown partition table
602 46 common/cmd_ide.c valid partition table found
603 -47 common/cmd_ide.c Invalid partition type
604 47 common/cmd_ide.c correct partition type
605 -48 common/cmd_ide.c Error reading Image Header on boot device
606 48 common/cmd_ide.c reading Image Header from IDE device OK
607 -49 common/cmd_ide.c Image header has bad magic number
608 49 common/cmd_ide.c Image header has correct magic number
609 -50 common/cmd_ide.c Image header has bad checksum
610 50 common/cmd_ide.c Image header has correct checksum
611 -51 common/cmd_ide.c Error reading Image from IDE device
612 51 common/cmd_ide.c reading Image from IDE device OK
613 52 common/cmd_nand.c before loading a Image from a NAND device
614 -53 common/cmd_nand.c Bad usage of "nand" command
615 53 common/cmd_nand.c correct usage of "nand" command
616 -54 common/cmd_nand.c No boot device
617 54 common/cmd_nand.c boot device found
618 -55 common/cmd_nand.c Unknown Chip ID on boot device
619 55 common/cmd_nand.c correct chip ID found, device available
620 -56 common/cmd_nand.c Error reading Image Header on boot device
621 56 common/cmd_nand.c reading Image Header from NAND device OK
622 -57 common/cmd_nand.c Image header has bad magic number
623 57 common/cmd_nand.c Image header has correct magic number
624 -58 common/cmd_nand.c Error reading Image from NAND device
625 58 common/cmd_nand.c reading Image from NAND device OK
626
627 -60 common/env_common.c Environment has a bad CRC, using default
628
629 64 net/eth.c starting with Ethernet configuration.
630 -64 net/eth.c no Ethernet found.
631 65 net/eth.c Ethernet found.
632
633 -80 common/cmd_net.c usage wrong
634 80 common/cmd_net.c before calling net_loop()
635 -81 common/cmd_net.c some error in net_loop() occurred
636 81 common/cmd_net.c net_loop() back without error
637 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
638 82 common/cmd_net.c trying automatic boot
639 83 common/cmd_net.c running "source" command
640 -83 common/cmd_net.c some error in automatic boot or "source" command
641 84 common/cmd_net.c end without errors
642
643 FIT uImage format:
644
645 Arg Where When
646 100 common/cmd_bootm.c Kernel FIT Image has correct format
647 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
648 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
649 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
650 102 common/cmd_bootm.c Kernel unit name specified
651 -103 common/cmd_bootm.c Can't get kernel subimage node offset
652 103 common/cmd_bootm.c Found configuration node
653 104 common/cmd_bootm.c Got kernel subimage node offset
654 -104 common/cmd_bootm.c Kernel subimage hash verification failed
655 105 common/cmd_bootm.c Kernel subimage hash verification OK
656 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
657 106 common/cmd_bootm.c Architecture check OK
658 -106 common/cmd_bootm.c Kernel subimage has wrong type
659 107 common/cmd_bootm.c Kernel subimage type OK
660 -107 common/cmd_bootm.c Can't get kernel subimage data/size
661 108 common/cmd_bootm.c Got kernel subimage data/size
662 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
663 -109 common/cmd_bootm.c Can't get kernel subimage type
664 -110 common/cmd_bootm.c Can't get kernel subimage comp
665 -111 common/cmd_bootm.c Can't get kernel subimage os
666 -112 common/cmd_bootm.c Can't get kernel subimage load address
667 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
668
669 120 common/image.c Start initial ramdisk verification
670 -120 common/image.c Ramdisk FIT image has incorrect format
671 121 common/image.c Ramdisk FIT image has correct format
672 122 common/image.c No ramdisk subimage unit name, using configuration
673 -122 common/image.c Can't get configuration for ramdisk subimage
674 123 common/image.c Ramdisk unit name specified
675 -124 common/image.c Can't get ramdisk subimage node offset
676 125 common/image.c Got ramdisk subimage node offset
677 -125 common/image.c Ramdisk subimage hash verification failed
678 126 common/image.c Ramdisk subimage hash verification OK
679 -126 common/image.c Ramdisk subimage for unsupported architecture
680 127 common/image.c Architecture check OK
681 -127 common/image.c Can't get ramdisk subimage data/size
682 128 common/image.c Got ramdisk subimage data/size
683 129 common/image.c Can't get ramdisk load address
684 -129 common/image.c Got ramdisk load address
685
686 -130 common/cmd_doc.c Incorrect FIT image format
687 131 common/cmd_doc.c FIT image format OK
688
689 -140 common/cmd_ide.c Incorrect FIT image format
690 141 common/cmd_ide.c FIT image format OK
691
692 -150 common/cmd_nand.c Incorrect FIT image format
693 151 common/cmd_nand.c FIT image format OK
694
695endmenu
696
Simon Glass7b6baa32020-09-10 20:21:15 -0600697menu "Boot media"
698
699config NOR_BOOT
700 bool "Support for booting from NOR flash"
701 depends on NOR
702 help
703 Enabling this will make a U-Boot binary that is capable of being
704 booted via NOR. In this case we will enable certain pinmux early
705 as the ROM only partially sets up pinmux. We also default to using
706 NOR for environment.
707
708config NAND_BOOT
709 bool "Support for booting from NAND flash"
710 default n
711 imply MTD_RAW_NAND
712 help
713 Enabling this will make a U-Boot binary that is capable of being
714 booted via NAND flash. This is not a must, some SoCs need this,
715 some not.
716
717config ONENAND_BOOT
718 bool "Support for booting from ONENAND"
719 default n
720 imply MTD_RAW_NAND
721 help
722 Enabling this will make a U-Boot binary that is capable of being
723 booted via ONENAND. This is not a must, some SoCs need this,
724 some not.
725
726config QSPI_BOOT
727 bool "Support for booting from QSPI flash"
728 default n
729 help
730 Enabling this will make a U-Boot binary that is capable of being
731 booted via QSPI flash. This is not a must, some SoCs need this,
732 some not.
733
734config SATA_BOOT
735 bool "Support for booting from SATA"
736 default n
737 help
738 Enabling this will make a U-Boot binary that is capable of being
739 booted via SATA. This is not a must, some SoCs need this,
740 some not.
741
742config SD_BOOT
743 bool "Support for booting from SD/EMMC"
744 default n
745 help
746 Enabling this will make a U-Boot binary that is capable of being
747 booted via SD/EMMC. This is not a must, some SoCs need this,
748 some not.
749
750config SPI_BOOT
751 bool "Support for booting from SPI flash"
752 default n
753 help
754 Enabling this will make a U-Boot binary that is capable of being
755 booted via SPI flash. This is not a must, some SoCs need this,
756 some not.
757
758endmenu
759
Simon Glass98eed0d2020-09-10 20:21:16 -0600760menu "Autoboot options"
761
762config AUTOBOOT
763 bool "Autoboot"
764 default y
765 help
766 This enables the autoboot. See doc/README.autoboot for detail.
767
Simon Glass95fd4f32020-09-10 20:21:17 -0600768config BOOTDELAY
769 int "delay in seconds before automatically booting"
770 default 2
771 depends on AUTOBOOT
772 help
773 Delay before automatically running bootcmd;
774 set to 0 to autoboot with no delay, but you can stop it by key input.
775 set to -1 to disable autoboot.
776 set to -2 to autoboot with no delay and not check for abort
777
778 If this value is >= 0 then it is also used for the default delay
779 before starting the default entry in bootmenu. If it is < 0 then
780 a default value of 10s is used.
781
782 See doc/README.autoboot for details.
783
Simon Glass98eed0d2020-09-10 20:21:16 -0600784config AUTOBOOT_KEYED
785 bool "Stop autobooting via specific input key / string"
786 default n
787 help
788 This option enables stopping (aborting) of the automatic
789 boot feature only by issuing a specific input key or
790 string. If not enabled, any input key will abort the
791 U-Boot automatic booting process and bring the device
792 to the U-Boot prompt for user input.
793
794config AUTOBOOT_PROMPT
795 string "Autoboot stop prompt"
796 depends on AUTOBOOT_KEYED
797 default "Autoboot in %d seconds\\n"
798 help
799 This string is displayed before the boot delay selected by
800 CONFIG_BOOTDELAY starts. If it is not defined there is no
801 output indicating that autoboot is in progress.
802
803 Note that this define is used as the (only) argument to a
804 printf() call, so it may contain '%' format specifications,
805 provided that it also includes, sepearated by commas exactly
806 like in a printf statement, the required arguments. It is
807 the responsibility of the user to select only such arguments
808 that are valid in the given context.
809
810config AUTOBOOT_ENCRYPTION
811 bool "Enable encryption in autoboot stopping"
812 depends on AUTOBOOT_KEYED
813 help
814 This option allows a string to be entered into U-Boot to stop the
815 autoboot. The string itself is hashed and compared against the hash
816 in the environment variable 'bootstopkeysha256'. If it matches then
817 boot stops and a command-line prompt is presented.
818
819 This provides a way to ship a secure production device which can also
820 be accessed at the U-Boot command line.
821
822config AUTOBOOT_DELAY_STR
823 string "Delay autobooting via specific input key / string"
824 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
825 help
826 This option delays the automatic boot feature by issuing
827 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
828 or the environment variable "bootdelaykey" is specified
829 and this string is received from console input before
830 autoboot starts booting, U-Boot gives a command prompt. The
831 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
832 used, otherwise it never times out.
833
834config AUTOBOOT_STOP_STR
835 string "Stop autobooting via specific input key / string"
836 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
837 help
838 This option enables stopping (aborting) of the automatic
839 boot feature only by issuing a specific input key or
840 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
841 variable "bootstopkey" is specified and this string is
842 received from console input before autoboot starts booting,
843 U-Boot gives a command prompt. The U-Boot prompt never
844 times out, even if CONFIG_BOOT_RETRY_TIME is used.
845
846config AUTOBOOT_KEYED_CTRLC
847 bool "Enable Ctrl-C autoboot interruption"
848 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
849 default n
850 help
851 This option allows for the boot sequence to be interrupted
852 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
853 Setting this variable provides an escape sequence from the
854 limited "password" strings.
855
856config AUTOBOOT_STOP_STR_SHA256
857 string "Stop autobooting via SHA256 encrypted password"
858 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
859 help
860 This option adds the feature to only stop the autobooting,
861 and therefore boot into the U-Boot prompt, when the input
862 string / password matches a values that is encypted via
Joel Peshkin652b5042020-11-21 17:18:59 -0800863 a SHA256 hash and saved in the environment variable
864 "bootstopkeysha256". If the value in that variable
865 includes a ":", the portion prior to the ":" will be treated
866 as a salt value.
Simon Glass98eed0d2020-09-10 20:21:16 -0600867
868config AUTOBOOT_USE_MENUKEY
869 bool "Allow a specify key to run a menu from the environment"
870 depends on !AUTOBOOT_KEYED
871 help
872 If a specific key is pressed to stop autoboot, then the commands in
873 the environment variable 'menucmd' are executed before boot starts.
874
875config AUTOBOOT_MENUKEY
876 int "ASCII value of boot key to show a menu"
877 default 0
878 depends on AUTOBOOT_USE_MENUKEY
879 help
880 If this key is pressed to stop autoboot, then the commands in the
881 environment variable 'menucmd' will be executed before boot starts.
882 For example, 33 means "!" in ASCII, so pressing ! at boot would take
883 this action.
884
885config AUTOBOOT_MENU_SHOW
886 bool "Show a menu on boot"
887 depends on CMD_BOOTMENU
888 help
889 This enables the boot menu, controlled by environment variables
890 defined by the board. The menu starts after running the 'preboot'
891 environmnent variable (if enabled) and before handling the boot delay.
892 See README.bootmenu for more details.
893
894endmenu
895
Simon Glassfe5db252020-09-10 20:21:18 -0600896config USE_BOOTARGS
897 bool "Enable boot arguments"
898 help
899 Provide boot arguments to bootm command. Boot arguments are specified
900 in CONFIG_BOOTARGS option. Enable this option to be able to specify
901 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
902 will be undefined and won't take any space in U-Boot image.
903
904config BOOTARGS
905 string "Boot arguments"
906 depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
907 help
908 This can be used to pass arguments to the bootm command. The value of
909 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
910 this value will also override the "chosen" node in FDT blob.
911
Simon Glass51bb3382020-11-05 10:33:48 -0700912config BOOTARGS_SUBST
913 bool "Support substituting strings in boot arguments"
914 help
915 This allows substituting string values in the boot arguments. These
916 are applied after the commandline has been built.
917
918 One use for this is to insert the root-disk UUID into the command
919 line where bootargs contains "root=${uuid}"
920
921 setenv bootargs "console= root=${uuid}"
922 # Set the 'uuid' environment variable
923 part uuid mmc 2:2 uuid
924
925 # Command-line substitution will put the real uuid into the
926 # kernel command line
927 bootm
928
Simon Glassfe5db252020-09-10 20:21:18 -0600929config USE_BOOTCOMMAND
930 bool "Enable a default value for bootcmd"
931 help
932 Provide a default value for the bootcmd entry in the environment. If
933 autoboot is enabled this is what will be run automatically. Enable
934 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
935 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
936 won't take any space in U-Boot image.
937
938config BOOTCOMMAND
939 string "bootcmd value"
940 depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
941 default "run distro_bootcmd" if DISTRO_DEFAULTS
942 help
943 This is the string of commands that will be used as bootcmd and if
944 AUTOBOOT is set, automatically run.
945
946config USE_PREBOOT
947 bool "Enable preboot"
948 help
949 When this option is enabled, the existence of the environment
950 variable "preboot" will be checked immediately before starting the
951 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
952 entering interactive mode.
953
954 This feature is especially useful when "preboot" is automatically
955 generated or modified. For example, the boot code can modify the
956 "preboot" when a user holds down a certain combination of keys.
957
958config PREBOOT
959 string "preboot default value"
960 depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
Patrick Delaunay87459da2020-10-12 09:47:50 +0200961 default "usb start" if USB_KEYBOARD
Simon Glassfe5db252020-09-10 20:21:18 -0600962 default ""
963 help
964 This is the default of "preboot" environment variable.
965
Simon Glass832876a2020-09-10 20:21:20 -0600966config DEFAULT_FDT_FILE
967 string "Default fdt file"
968 help
969 This option is used to set the default fdt file to boot OS.
970
Simon Glasscf298162020-09-10 20:21:13 -0600971endmenu # Booting