blob: 4c99239dfbbdee981ebf8638b69830481b259057 [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
66config FIT_SIGNATURE
67 bool "Enable signature verification of FIT uImages"
68 depends on DM
69 select HASH
70 select RSA
71 select RSA_VERIFY
72 select IMAGE_SIGN_INFO
73 help
74 This option enables signature verification of FIT uImages,
75 using a hash signed and verified using RSA. If
76 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
77 hashing is available using hardware, then the RSA library will use
78 it. See doc/uImage.FIT/signature.txt for more details.
79
80 WARNING: When relying on signed FIT images with a required signature
81 check the legacy image format is disabled by default, so that
82 unsigned images cannot be loaded. If a board needs the legacy image
83 format support in this case, enable it using
84 CONFIG_LEGACY_IMAGE_FORMAT.
85
86config FIT_SIGNATURE_MAX_SIZE
87 hex "Max size of signed FIT structures"
88 depends on FIT_SIGNATURE
89 default 0x10000000
90 help
91 This option sets a max size in bytes for verified FIT uImages.
92 A sane value of 256MB protects corrupted DTB structures from overlapping
93 device memory. Assure this size does not extend past expected storage
94 space.
95
96config FIT_ENABLE_RSASSA_PSS_SUPPORT
97 bool "Support rsassa-pss signature scheme of FIT image contents"
98 depends on FIT_SIGNATURE
99 default n
100 help
101 Enable this to support the pss padding algorithm as described
102 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
103
104config FIT_CIPHER
105 bool "Enable ciphering data in a FIT uImages"
106 depends on DM
107 select AES
108 help
109 Enable the feature of data ciphering/unciphering in the tool mkimage
110 and in the u-boot support of the FIT image.
111
112config FIT_VERBOSE
113 bool "Show verbose messages when FIT images fail"
114 help
115 Generally a system will have valid FIT images so debug messages
116 are a waste of code space. If you are debugging your images then
117 you can enable this option to get more verbose information about
118 failures.
119
120config FIT_BEST_MATCH
121 bool "Select the best match for the kernel device tree"
122 help
123 When no configuration is explicitly selected, default to the
124 one whose fdt's compatibility field best matches that of
125 U-Boot itself. A match is considered "best" if it matches the
126 most specific compatibility entry of U-Boot's fdt's root node.
127 The order of entries in the configuration's fdt is ignored.
128
129config FIT_IMAGE_POST_PROCESS
130 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
131 depends on TI_SECURE_DEVICE
132 help
133 Allows doing any sort of manipulation to blobs after they got extracted
134 from FIT images like stripping off headers or modifying the size of the
135 blob, verification, authentication, decryption etc. in a platform or
136 board specific way. In order to use this feature a platform or board-
137 specific implementation of board_fit_image_post_process() must be
138 provided. Also, anything done during this post-processing step would
139 need to be comprehended in how the images were prepared before being
140 injected into the FIT creation (i.e. the blobs would have been pre-
141 processed before being added to the FIT image).
142
143if SPL
144
145config SPL_FIT
146 bool "Support Flattened Image Tree within SPL"
147 depends on SPL
148 select SPL_OF_LIBFDT
149
150config SPL_FIT_PRINT
151 bool "Support FIT printing within SPL"
152 depends on SPL_FIT
153 help
154 Support printing the content of the fitImage in a verbose manner in SPL.
155
156config SPL_FIT_SIGNATURE
157 bool "Enable signature verification of FIT firmware within SPL"
158 depends on SPL_DM
159 select SPL_FIT
160 select SPL_CRYPTO_SUPPORT
161 select SPL_HASH_SUPPORT
162 select SPL_RSA
163 select SPL_RSA_VERIFY
164 select SPL_IMAGE_SIGN_INFO
165
166config SPL_LOAD_FIT
167 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
168 select SPL_FIT
169 help
170 Normally with the SPL framework a legacy image is generated as part
171 of the build. This contains U-Boot along with information as to
172 where it should be loaded. This option instead enables generation
173 of a FIT (Flat Image Tree) which provides more flexibility. In
174 particular it can handle selecting from multiple device tree
175 and passing the correct one to U-Boot.
176
177config SPL_LOAD_FIT_ADDRESS
178 hex "load address of fit image"
179 depends on SPL_LOAD_FIT
180 default 0x0
181 help
182 Specify the load address of the fit image that will be loaded
183 by SPL.
184
185config SPL_LOAD_FIT_APPLY_OVERLAY
186 bool "Enable SPL applying DT overlays from FIT"
187 depends on SPL_LOAD_FIT
188 select OF_LIBFDT_OVERLAY
189 help
190 The device tree is loaded from the FIT image. Allow the SPL is to
191 also load device-tree overlays from the FIT image an apply them
192 over the device tree.
193
194config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
195 depends on SPL_LOAD_FIT_APPLY_OVERLAY
196 default 0x10000
197 hex "size of temporary buffer used to load the overlays"
198 help
199 The size of the area where the overlays will be loaded and
200 uncompress. Must be at least as large as biggest overlay
201 (uncompressed)
202
203config SPL_LOAD_FIT_FULL
204 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
205 select SPL_FIT
206 help
207 Normally with the SPL framework a legacy image is generated as part
208 of the build. This contains U-Boot along with information as to
209 where it should be loaded. This option instead enables generation
210 of a FIT (Flat Image Tree) which provides more flexibility. In
211 particular it can handle selecting from multiple device tree
212 and passing the correct one to U-Boot.
213
214config SPL_FIT_IMAGE_POST_PROCESS
215 bool "Enable post-processing of FIT artifacts after loading by the SPL"
216 depends on SPL_LOAD_FIT
217 help
218 Allows doing any sort of manipulation to blobs after they got extracted
219 from the U-Boot FIT image like stripping off headers or modifying the
220 size of the blob, verification, authentication, decryption etc. in a
221 platform or board specific way. In order to use this feature a platform
222 or board-specific implementation of board_fit_image_post_process() must
223 be provided. Also, anything done during this post-processing step would
224 need to be comprehended in how the images were prepared before being
225 injected into the FIT creation (i.e. the blobs would have been pre-
226 processed before being added to the FIT image).
227
228config SPL_FIT_SOURCE
229 string ".its source file for U-Boot FIT image"
230 depends on SPL_FIT
231 help
232 Specifies a (platform specific) FIT source file to generate the
233 U-Boot FIT image. This could specify further image to load and/or
234 execute.
235
236config USE_SPL_FIT_GENERATOR
237 bool "Use a script to generate the .its script"
238 default y if SPL_FIT && !ARCH_SUNXI
239
240config SPL_FIT_GENERATOR
241 string ".its file generator script for U-Boot FIT image"
242 depends on USE_SPL_FIT_GENERATOR
243 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
244 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
245 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
246 help
247 Specifies a (platform specific) script file to generate the FIT
248 source file used to build the U-Boot FIT image file. This gets
249 passed a list of supported device tree file stub names to
250 include in the generated image.
251
252endif # SPL
253
254endif # FIT
255
256config LEGACY_IMAGE_FORMAT
257 bool "Enable support for the legacy image format"
258 default y if !FIT_SIGNATURE
259 help
260 This option enables the legacy image format. It is enabled by
261 default for backward compatibility, unless FIT_SIGNATURE is
262 set where it is disabled so that unsigned images cannot be
263 loaded. If a board needs the legacy image format support in this
264 case, enable it here.
265
266config OF_BOARD_SETUP
267 bool "Set up board-specific details in device tree before boot"
268 depends on OF_LIBFDT
269 help
270 This causes U-Boot to call ft_board_setup() before booting into
271 the Operating System. This function can set up various
272 board-specific information in the device tree for use by the OS.
273 The device tree is then passed to the OS.
274
275config OF_SYSTEM_SETUP
276 bool "Set up system-specific details in device tree before boot"
277 depends on OF_LIBFDT
278 help
279 This causes U-Boot to call ft_system_setup() before booting into
280 the Operating System. This function can set up various
281 system-specific information in the device tree for use by the OS.
282 The device tree is then passed to the OS.
283
284config OF_STDOUT_VIA_ALIAS
285 bool "Update the device-tree stdout alias from U-Boot"
286 depends on OF_LIBFDT
287 help
288 This uses U-Boot's serial alias from the aliases node to update
289 the device tree passed to the OS. The "linux,stdout-path" property
290 in the chosen node is set to point to the correct serial node.
291 This option currently references CONFIG_CONS_INDEX, which is
292 incorrect when used with device tree as this option does not
293 exist / should not be used.
294
295config SYS_EXTRA_OPTIONS
296 string "Extra Options (DEPRECATED)"
297 help
298 The old configuration infrastructure (= mkconfig + boards.cfg)
299 provided the extra options field. If you have something like
300 "HAS_BAR,BAZ=64", the optional options
301 #define CONFIG_HAS
302 #define CONFIG_BAZ 64
303 will be defined in include/config.h.
304 This option was prepared for the smooth migration from the old
305 configuration to Kconfig. Since this option will be removed sometime,
306 new boards should not use this option.
307
308config HAVE_SYS_TEXT_BASE
309 bool
310 depends on !NIOS2 && !XTENSA
311 depends on !EFI_APP
312 default y
313
314config SYS_TEXT_BASE
315 depends on HAVE_SYS_TEXT_BASE
316 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
317 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
318 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
319 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
320 hex "Text Base"
321 help
322 The address in memory that U-Boot will be running from, initially.
323
324config SYS_CLK_FREQ
325 depends on ARC || ARCH_SUNXI || MPC83xx
326 int "CPU clock frequency"
327 help
328 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
329
330config ARCH_FIXUP_FDT_MEMORY
331 bool "Enable arch_fixup_memory_banks() call"
332 default y
333 help
334 Enable FDT memory map syncup before OS boot. This feature can be
335 used for booting OS with different memory setup where the part of
336 the memory location should be used for different purpose.
337
338endmenu # Boot images
339
Simon Glass75e65cc2020-09-10 20:21:14 -0600340menu "Boot timing"
341
342config BOOTSTAGE
343 bool "Boot timing and reporting"
344 help
345 Enable recording of boot time while booting. To use it, insert
346 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
347 bootstage.h. Only a single entry is recorded for each ID. You can
348 give the entry a name with bootstage_mark_name(). You can also
349 record elapsed time in a particular stage using bootstage_start()
350 before starting and bootstage_accum() when finished. Bootstage will
351 add up all the accumulated time and report it.
352
353 Normally, IDs are defined in bootstage.h but a small number of
354 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
355 as the ID.
356
357 Calls to show_boot_progress() will also result in log entries but
358 these will not have names.
359
360config SPL_BOOTSTAGE
361 bool "Boot timing and reported in SPL"
362 depends on BOOTSTAGE
363 help
364 Enable recording of boot time in SPL. To make this visible to U-Boot
365 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
366 information when SPL finishes and load it when U-Boot proper starts
367 up.
368
369config TPL_BOOTSTAGE
370 bool "Boot timing and reported in TPL"
371 depends on BOOTSTAGE
372 help
373 Enable recording of boot time in SPL. To make this visible to U-Boot
374 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
375 information when TPL finishes and load it when U-Boot proper starts
376 up.
377
378config BOOTSTAGE_REPORT
379 bool "Display a detailed boot timing report before booting the OS"
380 depends on BOOTSTAGE
381 help
382 Enable output of a boot time report just before the OS is booted.
383 This shows how long it took U-Boot to go through each stage of the
384 boot process. The report looks something like this:
385
386 Timer summary in microseconds:
387 Mark Elapsed Stage
388 0 0 reset
389 3,575,678 3,575,678 board_init_f start
390 3,575,695 17 arch_cpu_init A9
391 3,575,777 82 arch_cpu_init done
392 3,659,598 83,821 board_init_r start
393 3,910,375 250,777 main_loop
394 29,916,167 26,005,792 bootm_start
395 30,361,327 445,160 start_kernel
396
397config BOOTSTAGE_RECORD_COUNT
398 int "Number of boot stage records to store"
399 default 30
400 help
401 This is the size of the bootstage record list and is the maximum
402 number of bootstage records that can be recorded.
403
404config SPL_BOOTSTAGE_RECORD_COUNT
405 int "Number of boot stage records to store for SPL"
406 default 5
407 help
408 This is the size of the bootstage record list and is the maximum
409 number of bootstage records that can be recorded.
410
411config TPL_BOOTSTAGE_RECORD_COUNT
412 int "Number of boot stage records to store for TPL"
413 default 5
414 help
415 This is the size of the bootstage record list and is the maximum
416 number of bootstage records that can be recorded.
417
418config BOOTSTAGE_FDT
419 bool "Store boot timing information in the OS device tree"
420 depends on BOOTSTAGE
421 help
422 Stash the bootstage information in the FDT. A root 'bootstage'
423 node is created with each bootstage id as a child. Each child
424 has a 'name' property and either 'mark' containing the
425 mark time in microseconds, or 'accum' containing the
426 accumulated time for that bootstage id in microseconds.
427 For example:
428
429 bootstage {
430 154 {
431 name = "board_init_f";
432 mark = <3575678>;
433 };
434 170 {
435 name = "lcd";
436 accum = <33482>;
437 };
438 };
439
440 Code in the Linux kernel can find this in /proc/devicetree.
441
442config BOOTSTAGE_STASH
443 bool "Stash the boot timing information in memory before booting OS"
444 depends on BOOTSTAGE
445 help
446 Some OSes do not support device tree. Bootstage can instead write
447 the boot timing information in a binary format at a given address.
448 This happens through a call to bootstage_stash(), typically in
449 the CPU's cleanup_before_linux() function. You can use the
450 'bootstage stash' and 'bootstage unstash' commands to do this on
451 the command line.
452
453config BOOTSTAGE_STASH_ADDR
454 hex "Address to stash boot timing information"
455 default 0
456 help
457 Provide an address which will not be overwritten by the OS when it
458 starts, so that it can read this information when ready.
459
460config BOOTSTAGE_STASH_SIZE
461 hex "Size of boot timing stash region"
462 default 0x1000
463 help
464 This should be large enough to hold the bootstage stash. A value of
465 4096 (4KiB) is normally plenty.
466
467config SHOW_BOOT_PROGRESS
468 bool "Show boot progress in a board-specific manner"
469 help
470 Defining this option allows to add some board-specific code (calling
471 a user-provided function show_boot_progress(int) that enables you to
472 show the system's boot progress on some display (for example, some
473 LEDs) on your board. At the moment, the following checkpoints are
474 implemented:
475
476 Legacy uImage format:
477
478 Arg Where When
479 1 common/cmd_bootm.c before attempting to boot an image
480 -1 common/cmd_bootm.c Image header has bad magic number
481 2 common/cmd_bootm.c Image header has correct magic number
482 -2 common/cmd_bootm.c Image header has bad checksum
483 3 common/cmd_bootm.c Image header has correct checksum
484 -3 common/cmd_bootm.c Image data has bad checksum
485 4 common/cmd_bootm.c Image data has correct checksum
486 -4 common/cmd_bootm.c Image is for unsupported architecture
487 5 common/cmd_bootm.c Architecture check OK
488 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
489 6 common/cmd_bootm.c Image Type check OK
490 -6 common/cmd_bootm.c gunzip uncompression error
491 -7 common/cmd_bootm.c Unimplemented compression type
492 7 common/cmd_bootm.c Uncompression OK
493 8 common/cmd_bootm.c No uncompress/copy overwrite error
494 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
495
496 9 common/image.c Start initial ramdisk verification
497 -10 common/image.c Ramdisk header has bad magic number
498 -11 common/image.c Ramdisk header has bad checksum
499 10 common/image.c Ramdisk header is OK
500 -12 common/image.c Ramdisk data has bad checksum
501 11 common/image.c Ramdisk data has correct checksum
502 12 common/image.c Ramdisk verification complete, start loading
503 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
504 13 common/image.c Start multifile image verification
505 14 common/image.c No initial ramdisk, no multifile, continue.
506
507 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
508
509 -30 arch/powerpc/lib/board.c Fatal error, hang the system
510 -31 post/post.c POST test failed, detected by post_output_backlog()
511 -32 post/post.c POST test failed, detected by post_run_single()
512
513 34 common/cmd_doc.c before loading a Image from a DOC device
514 -35 common/cmd_doc.c Bad usage of "doc" command
515 35 common/cmd_doc.c correct usage of "doc" command
516 -36 common/cmd_doc.c No boot device
517 36 common/cmd_doc.c correct boot device
518 -37 common/cmd_doc.c Unknown Chip ID on boot device
519 37 common/cmd_doc.c correct chip ID found, device available
520 -38 common/cmd_doc.c Read Error on boot device
521 38 common/cmd_doc.c reading Image header from DOC device OK
522 -39 common/cmd_doc.c Image header has bad magic number
523 39 common/cmd_doc.c Image header has correct magic number
524 -40 common/cmd_doc.c Error reading Image from DOC device
525 40 common/cmd_doc.c Image header has correct magic number
526 41 common/cmd_ide.c before loading a Image from a IDE device
527 -42 common/cmd_ide.c Bad usage of "ide" command
528 42 common/cmd_ide.c correct usage of "ide" command
529 -43 common/cmd_ide.c No boot device
530 43 common/cmd_ide.c boot device found
531 -44 common/cmd_ide.c Device not available
532 44 common/cmd_ide.c Device available
533 -45 common/cmd_ide.c wrong partition selected
534 45 common/cmd_ide.c partition selected
535 -46 common/cmd_ide.c Unknown partition table
536 46 common/cmd_ide.c valid partition table found
537 -47 common/cmd_ide.c Invalid partition type
538 47 common/cmd_ide.c correct partition type
539 -48 common/cmd_ide.c Error reading Image Header on boot device
540 48 common/cmd_ide.c reading Image Header from IDE device OK
541 -49 common/cmd_ide.c Image header has bad magic number
542 49 common/cmd_ide.c Image header has correct magic number
543 -50 common/cmd_ide.c Image header has bad checksum
544 50 common/cmd_ide.c Image header has correct checksum
545 -51 common/cmd_ide.c Error reading Image from IDE device
546 51 common/cmd_ide.c reading Image from IDE device OK
547 52 common/cmd_nand.c before loading a Image from a NAND device
548 -53 common/cmd_nand.c Bad usage of "nand" command
549 53 common/cmd_nand.c correct usage of "nand" command
550 -54 common/cmd_nand.c No boot device
551 54 common/cmd_nand.c boot device found
552 -55 common/cmd_nand.c Unknown Chip ID on boot device
553 55 common/cmd_nand.c correct chip ID found, device available
554 -56 common/cmd_nand.c Error reading Image Header on boot device
555 56 common/cmd_nand.c reading Image Header from NAND device OK
556 -57 common/cmd_nand.c Image header has bad magic number
557 57 common/cmd_nand.c Image header has correct magic number
558 -58 common/cmd_nand.c Error reading Image from NAND device
559 58 common/cmd_nand.c reading Image from NAND device OK
560
561 -60 common/env_common.c Environment has a bad CRC, using default
562
563 64 net/eth.c starting with Ethernet configuration.
564 -64 net/eth.c no Ethernet found.
565 65 net/eth.c Ethernet found.
566
567 -80 common/cmd_net.c usage wrong
568 80 common/cmd_net.c before calling net_loop()
569 -81 common/cmd_net.c some error in net_loop() occurred
570 81 common/cmd_net.c net_loop() back without error
571 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
572 82 common/cmd_net.c trying automatic boot
573 83 common/cmd_net.c running "source" command
574 -83 common/cmd_net.c some error in automatic boot or "source" command
575 84 common/cmd_net.c end without errors
576
577 FIT uImage format:
578
579 Arg Where When
580 100 common/cmd_bootm.c Kernel FIT Image has correct format
581 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
582 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
583 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
584 102 common/cmd_bootm.c Kernel unit name specified
585 -103 common/cmd_bootm.c Can't get kernel subimage node offset
586 103 common/cmd_bootm.c Found configuration node
587 104 common/cmd_bootm.c Got kernel subimage node offset
588 -104 common/cmd_bootm.c Kernel subimage hash verification failed
589 105 common/cmd_bootm.c Kernel subimage hash verification OK
590 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
591 106 common/cmd_bootm.c Architecture check OK
592 -106 common/cmd_bootm.c Kernel subimage has wrong type
593 107 common/cmd_bootm.c Kernel subimage type OK
594 -107 common/cmd_bootm.c Can't get kernel subimage data/size
595 108 common/cmd_bootm.c Got kernel subimage data/size
596 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
597 -109 common/cmd_bootm.c Can't get kernel subimage type
598 -110 common/cmd_bootm.c Can't get kernel subimage comp
599 -111 common/cmd_bootm.c Can't get kernel subimage os
600 -112 common/cmd_bootm.c Can't get kernel subimage load address
601 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
602
603 120 common/image.c Start initial ramdisk verification
604 -120 common/image.c Ramdisk FIT image has incorrect format
605 121 common/image.c Ramdisk FIT image has correct format
606 122 common/image.c No ramdisk subimage unit name, using configuration
607 -122 common/image.c Can't get configuration for ramdisk subimage
608 123 common/image.c Ramdisk unit name specified
609 -124 common/image.c Can't get ramdisk subimage node offset
610 125 common/image.c Got ramdisk subimage node offset
611 -125 common/image.c Ramdisk subimage hash verification failed
612 126 common/image.c Ramdisk subimage hash verification OK
613 -126 common/image.c Ramdisk subimage for unsupported architecture
614 127 common/image.c Architecture check OK
615 -127 common/image.c Can't get ramdisk subimage data/size
616 128 common/image.c Got ramdisk subimage data/size
617 129 common/image.c Can't get ramdisk load address
618 -129 common/image.c Got ramdisk load address
619
620 -130 common/cmd_doc.c Incorrect FIT image format
621 131 common/cmd_doc.c FIT image format OK
622
623 -140 common/cmd_ide.c Incorrect FIT image format
624 141 common/cmd_ide.c FIT image format OK
625
626 -150 common/cmd_nand.c Incorrect FIT image format
627 151 common/cmd_nand.c FIT image format OK
628
629endmenu
630
Simon Glass7b6baa32020-09-10 20:21:15 -0600631menu "Boot media"
632
633config NOR_BOOT
634 bool "Support for booting from NOR flash"
635 depends on NOR
636 help
637 Enabling this will make a U-Boot binary that is capable of being
638 booted via NOR. In this case we will enable certain pinmux early
639 as the ROM only partially sets up pinmux. We also default to using
640 NOR for environment.
641
642config NAND_BOOT
643 bool "Support for booting from NAND flash"
644 default n
645 imply MTD_RAW_NAND
646 help
647 Enabling this will make a U-Boot binary that is capable of being
648 booted via NAND flash. This is not a must, some SoCs need this,
649 some not.
650
651config ONENAND_BOOT
652 bool "Support for booting from ONENAND"
653 default n
654 imply MTD_RAW_NAND
655 help
656 Enabling this will make a U-Boot binary that is capable of being
657 booted via ONENAND. This is not a must, some SoCs need this,
658 some not.
659
660config QSPI_BOOT
661 bool "Support for booting from QSPI flash"
662 default n
663 help
664 Enabling this will make a U-Boot binary that is capable of being
665 booted via QSPI flash. This is not a must, some SoCs need this,
666 some not.
667
668config SATA_BOOT
669 bool "Support for booting from SATA"
670 default n
671 help
672 Enabling this will make a U-Boot binary that is capable of being
673 booted via SATA. This is not a must, some SoCs need this,
674 some not.
675
676config SD_BOOT
677 bool "Support for booting from SD/EMMC"
678 default n
679 help
680 Enabling this will make a U-Boot binary that is capable of being
681 booted via SD/EMMC. This is not a must, some SoCs need this,
682 some not.
683
684config SPI_BOOT
685 bool "Support for booting from SPI flash"
686 default n
687 help
688 Enabling this will make a U-Boot binary that is capable of being
689 booted via SPI flash. This is not a must, some SoCs need this,
690 some not.
691
692endmenu
693
Simon Glasscf298162020-09-10 20:21:13 -0600694endmenu # Booting