12 config SPL_DFU_NO_RESET
17 depends on SUPPORT_SPL
20 If you want to build SPL as well as the normal image, say Y.
23 bool "Support SPL based upon the common SPL framework"
27 Enable the SPL framework under common/spl/. This framework
28 supports MMC, NAND and YMODEM and other methods loading of U-Boot
29 and the Linux Kernel. If unsure, say Y.
31 config SPL_FRAMEWORK_BOARD_INIT_F
32 bool "Define a generic function board_init_f"
33 depends on SPL_FRAMEWORK
35 Define a generic function board_init_f that:
36 - initialize the spl (spl_early_init)
37 - initialize the serial (preloader_console_init)
38 Unless you want to provide your own board_init_f, you should say Y.
41 hex "Maximum size of SPL image"
43 default 0x11000 if ARCH_MX6 && !MX6_OCRAM_256KB
44 default 0x31000 if ARCH_MX6 && MX6_OCRAM_256KB
47 Specifies the maximum length of the U-Boot SPL image.
48 If this value is zero, it is ignored.
50 config SPL_SIZE_LIMIT_SUBTRACT_GD
51 bool "SPL image size check: provide space for global data"
52 depends on SPL_SIZE_LIMIT > 0
54 If enabled, aligned size of global data is reserved in
55 SPL_SIZE_LIMIT check to ensure such an image does not overflow SRAM
56 if SPL_SIZE_LIMIT describes the size of SRAM available for SPL when
57 pre-reloc global data is put into this SRAM, too.
59 config SPL_SIZE_LIMIT_SUBTRACT_MALLOC
60 bool "SPL image size check: provide space for malloc() pool before relocation"
61 depends on SPL_SIZE_LIMIT > 0
63 If enabled, SPL_SYS_MALLOC_F_LEN is reserved in SPL_SIZE_LIMIT check
64 to ensure such an image does not overflow SRAM if SPL_SIZE_LIMIT
65 describes the size of SRAM available for SPL when pre-reloc malloc
66 pool is put into this SRAM, too.
68 config SPL_SIZE_LIMIT_PROVIDE_STACK
69 hex "SPL image size check: provide stack space before relocation"
70 depends on SPL_SIZE_LIMIT > 0
73 If set, this size is reserved in SPL_SIZE_LIMIT check to ensure such
74 an image does not overflow SRAM if SPL_SIZE_LIMIT describes the size
75 of SRAM available for SPL when the stack required before reolcation
79 hex "Maximum size of the SPL image, excluding BSS"
80 default 0x30000 if ARCH_MX6 && MX6_OCRAM_256KB
81 default 0x1b000 if AM33XX && !TI_SECURE_DEVICE
82 default 0x10000 if ARCH_MX6 && !MX6_OCRAM_256KB
83 default 0x7fa0 if SUNXI_SRAM_ADDRESS = 0x10000
84 default 0x7fa0 if SUNXI_SRAM_ADDRESS = 0x20000 && !MACH_SUN50I_H616
85 default 0x7000 if RCAR_GEN3
86 default 0x5fa0 if SUNXI_SRAM_ADDRESS = 0x0
89 Maximum size of the SPL image (text, data, rodata, and linker lists
90 sections), BSS excluded. When defined, the linker checks that the
91 actual size does not exceed it.
94 hex "Offset to which the SPL should be padded before appending the SPL payload"
95 default 0x31000 if ARCH_MX6 && MX6_OCRAM_256KB
96 default 0x11000 if ARCH_MX7 || (ARCH_MX6 && !MX6_OCRAM_256KB)
97 default 0x10000 if ARCH_KEYSTONE
98 default 0x8000 if ARCH_SUNXI && !MACH_SUN50I_H616
99 default TPL_MAX_SIZE if TPL_MAX_SIZE > SPL_MAX_SIZE
102 Image offset to which the SPL should be padded before appending the
103 SPL payload. By default, this is defined as CONFIG_SPL_MAX_SIZE, or 0 if
104 CONFIG_SPL_MAX_SIZE is undefined. CONFIG_SPL_PAD_TO must be either
105 0, meaning to append the SPL payload without any padding, or >=
109 prompt "Enforce SPL BSS limit"
110 depends on SPL && !PPC
111 default SPL_BSS_LIMIT
113 In some platforms we only want to enforce a limit on the size of the
114 BSS in memory. On other platforms we need to enforce a limit on the
115 whole of the memory allocation as we're strictly limited to a small
116 typically non-DRAM location. Finally, other platforms do not enforce
117 a memory limit within SPL.
119 config SPL_NO_BSS_LIMIT
120 bool "Do not enforce a build time limit on the size of the BSS"
123 bool "Enforce a limit on the size of the BSS only"
125 config SPL_FOOTPRINT_LIMIT
126 bool "Enforce a limit on the whole of memory allocated to SPL, BSS included"
130 config SPL_BSS_MAX_SIZE
131 hex "Maximum size in memory allocated to the SPL BSS"
132 depends on SPL_BSS_LIMIT
133 default 0x100000 if ARCH_MX6 || RISCV
134 default 0x80000 if ARCH_OMAP2PLUS || ARCH_SUNXI
136 When non-zero, the linker checks that the actual memory used by SPL
137 from __bss_start to __bss_end does not exceed it.
139 config SPL_MAX_FOOTPRINT
140 hex "Maximum size in memory allocated to the SPL, BSS included"
141 depends on SPL_FOOTPRINT_LIMIT
143 When non-zero, the linker checks that the actual memory used by SPL
144 from _start to __bss_end does not exceed it.
146 config SPL_SYS_STACK_F_CHECK_BYTE
150 Constant used to check the stack
152 config SPL_SYS_REPORT_STACK_F_USAGE
153 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
154 bool "Check and report stack usage in SPL before relocation"
156 If this option is enabled, the initial SPL stack is filled with 0xaa
157 very early, up to the size configured with
158 SPL_SIZE_LIMIT_PROVIDE_STACK.
159 Later when SPL is done using this initial stack and switches to a
160 stack in DRAM, the actually used size of this initial stack is
161 reported by examining the memory and searching for the lowest
162 occurrence of non 0xaa bytes.
163 This default implementation works for stacks growing down only.
165 config SPL_SHOW_ERRORS
166 bool "Show more information when something goes wrong"
168 This enabled more verbose error messages and checking when something
169 goes wrong in SPL. For example, it shows the error code when U-Boot
170 cannot be located. This can help to diagnose the problem and figure
171 out a fix, particularly during development.
173 This adds a small amount to SPL code size, perhaps 100 bytes.
175 config SPL_BINMAN_SYMBOLS
176 bool "Declare binman symbols in SPL"
177 depends on SPL_FRAMEWORK && BINMAN
180 This enables use of symbols in SPL which refer to U-Boot, enabling SPL
181 to obtain the location of U-Boot simply by calling spl_get_image_pos()
182 and spl_get_image_size().
184 For this to work, you must have a U-Boot image in the binman image, so
185 binman can update SPL with the location of it.
187 menu "PowerPC and LayerScape SPL Boot options"
190 bool "Load SPL from NAND flash"
191 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
194 bool "Load SPL from SD Card / eMMC"
195 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
198 bool "Load SPL from SPI flash"
199 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
202 bool "Create SPL in Freescale PBI format"
203 depends on (PPC || ARCH_LS1021A || ARCH_LS1043A || ARCH_LS1046A) && \
206 Create boot binary having SPL binary in PBI format concatenated with
209 config SPL_SYS_CCSR_DO_NOT_RELOCATE
210 bool "Ensures that CCSR is not relocated"
213 If this is defined, then CONFIG_SYS_CCSRBAR_PHYS will be forced to a
214 value that ensures that CCSR is not relocated.
216 config TPL_SYS_CCSR_DO_NOT_RELOCATE
218 depends on SPL_SYS_CCSR_DO_NOT_RELOCATE
222 menu "PowerPC SPL specific options"
223 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
225 config SPL_INIT_MINIMAL
226 bool "Arch init code will be built for a very small image"
228 config SPL_FLUSH_IMAGE
229 bool "Clean dcache and invalidate icache after loading the image"
231 config SPL_SKIP_RELOCATE
232 bool "Skip relocating SPL"
237 bool "Pass hand-off information from SPL to U-Boot proper"
238 depends on SPL && BLOBLIST
240 It is useful to be able to pass information from SPL to U-Boot
241 proper to preserve state that is known in SPL and is needed in U-Boot.
242 Enable this to locate the handoff information in U-Boot proper, early
243 in boot. It is available in gd->handoff. The state state is set up
244 in SPL (or TPL if that is being used).
249 bool "Pass hand-off information from SPL to U-Boot proper"
250 depends on HANDOFF && SPL_BLOBLIST
253 This option enables SPL to write handoff information. This can be
254 used to pass information like the size of SDRAM from SPL to U-Boot
255 proper. Also SPL can receive information from TPL in the same place
259 string "Linker script for the SPL stage"
260 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
262 The SPL stage will usually require a different linker-script
263 (as it runs from a different memory region) than the regular
264 U-Boot stage. Set this to the path of the linker-script to
269 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
270 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
271 default 0x20060 if SUN50I_GEN_H6
272 default 0x00060 if ARCH_SUNXI
273 default 0xfffc0000 if ARCH_ZYNQMP
276 The address in memory that SPL will be running from.
278 config SPL_BOARD_INIT
279 bool "Call board-specific initialization in SPL"
281 If this option is enabled, U-Boot will call the function
282 spl_board_init() from board_init_r(). This function should be
283 provided by the board.
285 config VPL_BOARD_INIT
286 bool "Call board-specific initialization in VPL"
288 If this option is enabled, U-Boot will call the function
289 spl_board_init() from board_init_r(). This function should be
290 provided by the board.
292 config SPL_BOOTROM_SUPPORT
293 bool "Support returning to the BOOTROM"
295 Some platforms (e.g. the Rockchip RK3368) provide support in their
296 ROM for loading the next boot-stage after performing basic setup
299 Enable this option, to return to the BOOTROM through the
300 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
301 boot device list, if not implemented for a given board)
303 config SPL_BOOTCOUNT_LIMIT
304 bool "Support bootcount in SPL"
305 depends on SPL_ENV_SUPPORT && !TPL_BOOTCOUNT_LIMIT
307 On some boards, which use 'falcon' mode, it is necessary to check
308 and increment the number of boot attempts. Such boards do not
309 use proper U-Boot for normal boot flow and hence needs those
310 adjustments to be done in the SPL.
312 config SPL_RAW_IMAGE_SUPPORT
313 bool "Support SPL loading and booting of RAW images"
314 default n if (ARCH_MX6 && (SPL_MMC || SPL_SATA))
316 depends on !TI_SECURE_DEVICE
318 SPL will support loading and booting a RAW image when this option
319 is y. If this is not set, SPL will move on to other available
320 boot media to find a suitable image.
322 config SPL_LEGACY_IMAGE_FORMAT
323 bool "Support SPL loading and booting of Legacy images"
324 default y if !SPL_LOAD_FIT
325 depends on !TI_SECURE_DEVICE
327 SPL will support loading and booting Legacy images when this option
328 is y. If this is not set, SPL will move on to other available
329 boot media to find a suitable image.
331 config SPL_LEGACY_IMAGE_CRC_CHECK
332 bool "Check CRC of Legacy images"
333 depends on SPL_LEGACY_IMAGE_FORMAT
336 Enable this to check the CRC of Legacy images. While this increases
337 reliability, it affects both code size and boot duration.
338 If disabled, Legacy images are booted if the image magic and size
339 are correct, without further integrity checks.
341 config SPL_SYS_MALLOC_SIMPLE
343 prompt "Only use malloc_simple functions in the SPL"
345 Say Y here to only use the *_simple malloc functions from
346 malloc_simple.c, rather then using the versions from dlmalloc.c;
347 this will make the SPL binary smaller at the cost of more heap
348 usage as the *_simple malloc functions do not re-use free-ed mem.
350 config TPL_SYS_MALLOC_SIMPLE
352 prompt "Only use malloc_simple functions in the TPL"
355 Say Y here to only use the *_simple malloc functions from
356 malloc_simple.c, rather then using the versions from dlmalloc.c;
357 this will make the TPL binary smaller at the cost of more heap
358 usage as the *_simple malloc functions do not re-use free-ed mem.
360 config SPL_SHARES_INIT_SP_ADDR
361 bool "SPL and U-Boot use the same initial stack pointer location"
362 depends on (ARM || ARCH_JZ47XX || MICROBLAZE || RISCV) && SPL_FRAMEWORK
363 default n if ARCH_SUNXI
366 In many cases, we can use the same initial stack pointer address for
367 both SPL and U-Boot itself. If you need to specify a different address
368 however, say N here and then set a different value in CONFIG_SPL_STACK.
371 hex "Initial stack pointer location"
372 depends on (ARM || ARCH_JZ47XX || MICROBLAZE || RISCV) && SPL_FRAMEWORK
373 depends on !SPL_SHARES_INIT_SP_ADDR
375 Address of the start of the stack SPL will use before SDRAM is
379 bool "Enable SDRAM location for SPL stack"
381 SPL starts off execution in SRAM and thus typically has only a small
382 stack available. Since SPL sets up DRAM while in its board_init_f()
383 function, it is possible for the stack to move there before
384 board_init_r() is reached. This option enables a special SDRAM
385 location for the SPL stack. U-Boot SPL switches to this after
386 board_init_f() completes, and before board_init_r() starts.
388 config SPL_STACK_R_ADDR
389 depends on SPL_STACK_R
390 hex "SDRAM location for SPL stack"
391 default 0x82000000 if ARCH_OMAP2PLUS
393 Specify the address in SDRAM for the SPL stack. This will be set up
394 before board_init_r() is called.
396 config SPL_STACK_R_MALLOC_SIMPLE_LEN
397 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
398 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
401 Specify the amount of the stack to use as memory pool for
402 malloc_simple after switching the stack to DRAM. This may be set
403 to give board_init_r() a larger heap then the initial heap in
404 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
406 config SPL_SEPARATE_BSS
407 bool "BSS section is in a different memory region from text"
409 Some platforms need a large BSS region in SPL and can provide this
410 because RAM is already set up. In this case BSS can be moved to RAM.
411 This option should then be enabled so that the correct device tree
412 location is used. Normally we put the device tree at the end of BSS
413 but with this option enabled, it goes at _image_binary_end.
417 depends on SPL_OF_PLATDATA
418 # Bind cannot be supported because the udevice structs are in read-only
419 # memory so we cannot update the linked lists.
420 select SPL_OF_PLATDATA_NO_BIND
421 select SPL_OF_PLATDATA_RT
423 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
424 section of memory. This means that of-platdata must make a copy (in
425 writeable memory) of anything it wants to modify, such as
428 config TPL_SEPARATE_BSS
429 bool "BSS section is in a different memory region from text"
430 default y if SPL_SEPARATE_BSS
432 Some platforms need a large BSS region in TPL and can provide this
433 because RAM is already set up. In this case BSS can be moved to RAM.
434 This option should then be enabled so that the correct device tree
435 location is used. Normally we put the device tree at the end of BSS
436 but with this option enabled, it goes at _image_binary_end.
438 config SPL_BANNER_PRINT
439 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
442 If this option is enabled, SPL will print the banner with version
443 info. Disabling this option could be useful to reduce SPL boot time
444 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
446 config TPL_BANNER_PRINT
447 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
451 If this option is enabled, TPL will print the banner with version
452 info. Disabling this option could be useful to reduce TPL boot time
453 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
456 depends on ARM && !ARM64
457 bool "Allows initializing BSS early before entering board_init_f"
459 On some platform we have sufficient memory available early on to
460 allow setting up and using a basic BSS prior to entering
461 board_init_f. Activating this option will also de-activate the
462 clearing of BSS during the SPL relocation process, thus allowing
463 to carry state from board_init_f to board_init_r by way of BSS.
465 config SPL_DISPLAY_PRINT
466 bool "Display a board-specific message in SPL"
468 If this option is enabled, U-Boot will call the function
469 spl_display_print() immediately after displaying the SPL console
470 banner ("U-Boot SPL ..."). This function should be provided by
473 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
474 bool "MMC raw mode: by sector"
475 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
476 ARCH_MX6 || ARCH_MX7 || \
477 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
478 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
479 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
480 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
482 Use sector number for specifying U-Boot location on MMC/SD in
485 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
486 hex "Address on the MMC to load U-Boot from"
487 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
488 default 0x40 if ARCH_SUNXI
489 default 0x75 if ARCH_DAVINCI
490 default 0x8a if ARCH_MX6 || ARCH_MX7
491 default 0x100 if ARCH_UNIPHIER
492 default 0x0 if ARCH_MVEBU
493 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
494 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
495 OMAP54XX || AM33XX || AM43XX || ARCH_K3
496 default 0x4000 if ARCH_ROCKCHIP
497 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
499 Address on the MMC to load U-Boot from, when the MMC is being used
500 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
502 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
503 hex "U-Boot main hardware partition image offset"
504 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
505 default 0x10 if ARCH_SUNXI
508 On some platforms SPL location depends on hardware partition. The ROM
509 code skips the MBR sector when loading SPL from main hardware data
510 partition. This adds offset to the main U-Boot image. Set this symbol
511 to the number of skipped sectors.
513 If unsure, leave the default.
515 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
516 bool "MMC Raw mode: by partition"
518 Use a partition for loading U-Boot when using MMC/SD in raw mode.
520 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
521 hex "Partition to use to load U-Boot from"
522 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
525 Partition on the MMC to load U-Boot from when the MMC is being
528 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
529 bool "MMC raw mode: by partition type"
530 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
532 Use partition type for specifying U-Boot partition on MMC/SD in
533 raw mode. U-Boot will be loaded from the first partition of this
536 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
537 hex "Partition Type on the MMC to load U-Boot from"
538 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
540 Partition Type on the MMC to load U-Boot from, when the MMC is being
543 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
544 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
545 depends on SUPPORT_EMMC_BOOT
547 eMMC boot partition is normally configured by the bits of the EXT_CSD
548 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
549 cases it might be required in SPL to load the image from different
550 partition than the partition selected by EXT_CSC_PART_CONFIG register.
551 Enable this option if you intend to use an eMMC boot partition other
552 then selected via EXT_CSC_PART_CONFIG register and specify the custom
553 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
556 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
557 int "Number of the eMMC boot partition to use"
558 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
561 eMMC boot partition number to use when the eMMC in raw mode and
562 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
563 by user defined partition number.
567 default y if SPL_LEGACY_IMAGE_FORMAT || SPL_EFI_PARTITION
568 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
570 Enable this to support CRC32 in uImages or FIT images within SPL.
571 This is a 32-bit checksum value that can be used to verify images.
572 For FIT images, this is the least secure type of checksum, suitable
573 for detected accidental image corruption. For secure applications you
574 should consider SHA1 or SHA256.
580 Enable this to support MD5 in FIT images within SPL. An MD5
581 checksum is a 128-bit hash value used to check that the image
582 contents have not been corrupted. Note that MD5 is not considered
583 secure as it is possible (with a brute-force attack) to adjust the
584 image while still retaining the same MD5 hash value. For secure
585 applications where images may be changed maliciously, you should
586 consider SHA256 or SHA384.
588 config SPL_FIT_IMAGE_TINY
589 bool "Remove functionality from SPL FIT loading to reduce size"
591 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
592 default y if ARCH_IMX8M
594 Enable this to reduce the size of the FIT image loading code
595 in SPL, if space for the SPL binary is very tight.
597 This skips the recording of each loaded payload
598 (i.e. loadable) into the FDT (modifying the loaded FDT to
599 ensure this information is available to the next image
603 bool "Support CACHE drivers"
605 Enable CACHE drivers in SPL. These drivers can keep data so that
606 future requests for that data can be served faster. Enable this option
607 to build the drivers in drivers/cache as part of an SPL build.
610 bool "Support CPU drivers"
612 Enable this to support CPU drivers in SPL. These drivers can set
613 up CPUs and provide information about them such as the model and
614 name. This can be useful in SPL since setting up the CPUs earlier
615 may improve boot performance. Enable this option to build the
616 drivers in drivers/cpu as part of an SPL build.
619 bool "Support crypto drivers"
621 Enable crypto drivers in SPL. These drivers can be used to
622 accelerate secure boot processing in secure applications. Enable
623 this option to build the drivers in drivers/crypto as part of an
627 bool "Support DMA drivers"
629 Enable DMA (direct-memory-access) drivers in SPL. These drivers
630 can be used to handle memory-to-peripheral data transfer without
631 the CPU moving the data. Enable this option to build the drivers
632 in drivers/dma as part of an SPL build.
634 config SPL_DRIVERS_MISC
635 bool "Support misc drivers"
637 Enable miscellaneous drivers in SPL. These drivers perform various
638 tasks that don't fall nicely into other categories, Enable this
639 option to build the drivers in drivers/misc as part of an SPL
640 build, for those that support building in SPL (not all drivers do).
642 config SPL_ENV_SUPPORT
643 bool "Support an environment"
645 Enable environment support in SPL. The U-Boot environment provides
646 a number of settings (essentially name/value pairs) which can
647 control many aspects of U-Boot's operation. Normally this is not
648 needed in SPL as it has a much simpler task with less
649 configuration. But some boards use this to support 'Falcon' boot
650 on EXT2 and FAT, where SPL boots directly into Linux without
651 starting U-Boot first. Enabling this option will make env_get()
652 and env_set() available in SPL.
655 bool "Support save environment"
656 depends on SPL_ENV_SUPPORT
657 select SPL_MMC_WRITE if ENV_IS_IN_MMC
659 Enable save environment support in SPL after setenv. By default
660 the saveenv option is not provided in SPL, but some boards need
661 this support in 'Falcon' boot, where SPL need to boot from
662 different images based on environment variable set by OS. For
663 example OS may set "reboot_image" environment variable to
664 "recovery" inorder to boot recovery image by SPL. The SPL read
665 "reboot_image" and act accordingly and change the reboot_image
666 to default mode using setenv and save the environment.
669 bool "Support Ethernet"
670 depends on SPL_ENV_SUPPORT
673 Enable access to the network subsystem and associated Ethernet
674 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
675 link rather than from an on-board peripheral. Environment support
676 is required since the network stack uses a number of environment
677 variables. See also SPL_NET.
680 bool "Support EXT filesystems"
682 Enable support for EXT2/3/4 filesystems with SPL. This permits
683 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
684 filesystem from within SPL. Support for the underlying block
685 device (e.g. MMC or USB) must be enabled separately.
687 config SPL_FS_SQUASHFS
688 bool "Support SquashFS filesystems"
691 Enable support for SquashFS filesystems with SPL. This permits
692 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
693 filesystem from within SPL. Support for the underlying block
694 device (e.g. MMC or USB) must be enabled separately.
697 bool "Support FAT filesystems"
700 Enable support for FAT and VFAT filesystems with SPL. This
701 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
702 filesystem from within SPL. Support for the underlying block
703 device (e.g. MMC or USB) must be enabled separately.
705 config SPL_FS_LOAD_PAYLOAD_NAME
706 string "File to load for U-Boot from the filesystem"
707 depends on SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS
708 default "tispl.bin" if SYS_K3_SPL_ATF
709 default "u-boot.itb" if SPL_LOAD_FIT
712 Filename to read to load U-Boot when reading from filesystem.
714 config SPL_FS_LOAD_KERNEL_NAME
715 string "File to load for the OS kernel from the filesystem"
716 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
719 Filename to read to load for the OS kernel when reading from the
722 config SPL_FS_LOAD_ARGS_NAME
723 string "File to load for the OS kernel argument parameters from the filesystem"
724 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
727 Filename to read to load for the OS kernel argument parameters from
731 bool "Support write for FAT filesystems"
733 Enable write support for FAT and VFAT filesystems with SPL.
734 Support for the underlying block device (e.g. MMC or USB) must be
740 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
741 provide software-configurable hardware which is typically used to
742 implement peripherals (such as UARTs, LCD displays, MMC) or
743 accelerate custom processing functions, such as image processing
744 or machine learning. Sometimes it is useful to program the FPGA
745 as early as possible during boot, and this option can enable that
749 bool "Support GPIO in SPL"
751 Enable support for GPIOs (General-purpose Input/Output) in SPL.
752 GPIOs allow U-Boot to read the state of an input line (high or
753 low) and set the state of an output line. This can be used to
754 drive LEDs, control power to various system parts and read user
755 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
756 for example. Enable this option to build the drivers in
757 drivers/gpio as part of an SPL build.
762 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
763 I2C works with a clock and data line which can be driven by a
764 one or more masters or slaves. It is a fairly complex bus but is
765 widely used as it only needs two lines for communication. Speeds of
766 400kbps are typical but up to 3.4Mbps is supported by some
767 hardware. I2C can be useful in SPL to configure power management
768 ICs (PMICs) before raising the CPU clock speed, for example.
769 Enable this option to build the drivers in drivers/i2c as part of
772 config SPL_LIBCOMMON_SUPPORT
773 bool "Support common libraries"
775 Enable support for common U-Boot libraries within SPL. These
776 libraries include common code to deal with U-Boot images,
777 environment and USB, for example. This option is enabled on many
778 boards. Enable this option to build the code in common/ as part of
781 config SPL_LIBDISK_SUPPORT
782 bool "Support disk partitions"
785 Enable support for disk partitions within SPL. 'Disk' is something
786 of a misnomer as it includes non-spinning media such as flash (as
787 used in MMC and USB sticks). Partitions provide a way for a disk
788 to be split up into separate regions, with a partition table placed
789 at the start or end which describes the location and size of each
790 'partition'. These partitions are typically uses as individual block
791 devices, typically with an EXT2 or FAT filesystem in each. This
792 option enables whatever partition support has been enabled in
793 U-Boot to also be used in SPL. It brings in the code in disk/.
795 config SPL_LIBGENERIC_SUPPORT
796 bool "Support generic libraries"
798 Enable support for generic U-Boot libraries within SPL. These
799 libraries include generic code to deal with device tree, hashing,
800 printf(), compression and the like. This option is enabled on many
801 boards. Enable this option to build the code in lib/ as part of an
804 config SPL_DM_MAILBOX
805 bool "Support Mailbox"
807 Enable support for Mailbox within SPL. This enable the inter
808 processor communication protocols tobe used within SPL. Enable
809 this option to build the drivers in drivers/mailbox as part of
815 select HAVE_BLOCK_DEVICE
817 Enable support for MMC (Multimedia Card) within SPL. This enables
818 the MMC protocol implementation and allows any enabled drivers to
819 be used within SPL. MMC can be used with or without disk partition
820 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
821 this option to build the drivers in drivers/mmc as part of an SPL
824 config SYS_MMCSD_FS_BOOT_PARTITION
825 int "MMC Boot Partition"
828 Partition on the MMC to load U-Boot from when the MMC is being
830 Use -1 as a special value to use the first bootable partition.
833 bool "Tiny MMC framework in SPL"
836 Enable MMC framework tinification support. This option is useful if
837 if your SPL is extremely size constrained. Heed the warning, enable
838 this option if and only if you know exactly what you are doing, if
839 you are reading this help text, you most likely have no idea :-)
841 The MMC framework is reduced to bare minimum to be useful. No malloc
842 support is needed for the MMC framework operation with this option
843 enabled. The framework supports exactly one MMC device and exactly
844 one MMC driver. The MMC driver can be adjusted to avoid any malloc
845 operations too, which can remove the need for malloc support in SPL
846 and thus further reduce footprint.
849 bool "MMC/SD/SDIO card support for write operations in SPL"
852 Enable write access to MMC and SD Cards in SPL
855 config SPL_MPC8XXX_INIT_DDR
856 bool "Support MPC8XXX DDR init"
858 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
859 random-access memory) on the MPC8XXX family within SPL. This
860 allows DRAM to be set up before loading U-Boot into that DRAM,
863 config SPL_MTD_SUPPORT
864 bool "Support MTD drivers"
866 Enable support for MTD (Memory Technology Device) within SPL. MTD
867 provides a block interface over raw NAND and can also be used with
868 SPI flash. This allows SPL to load U-Boot from supported MTD
869 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
870 to enable specific MTD drivers.
873 bool "Support new Mentor Graphics USB"
875 Enable support for Mentor Graphics USB in SPL. This is a new
876 driver used by some boards. Enable this option to build
877 the drivers in drivers/usb/musb-new as part of an SPL build. The
878 old drivers are in drivers/usb/musb.
880 config SPL_NAND_SUPPORT
881 bool "Support NAND flash"
883 Enable support for NAND (Negative AND) flash in SPL. NAND flash
884 can be used to allow SPL to load U-Boot from supported devices.
885 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
888 config SPL_NAND_RAW_ONLY
889 bool "Support to boot only raw u-boot.bin images"
890 depends on SPL_NAND_SUPPORT
892 Use this only if you need to save space.
894 config SPL_NAND_DRIVERS
895 bool "Use standard NAND driver"
897 SPL uses normal NAND drivers, not minimal drivers.
900 bool "Include standard ECC in SPL"
902 config SPL_NAND_SOFTECC
903 bool "Use software ECC in SPL"
904 depends on SPL_NAND_ECC
906 config SPL_NAND_SIMPLE
907 bool "Support simple NAND drivers in SPL"
909 Support for NAND boot using simple NAND drivers that
910 expose the cmd_ctrl() interface.
913 depends on SPL_NAND_DRIVERS
914 bool "Use Base NAND Driver"
916 Include nand_base.c in the SPL.
918 config SPL_NAND_IDENT
919 depends on SPL_NAND_BASE
920 bool "Use chip ID to identify NAND flash"
922 SPL uses the chip ID list to identify the NAND flash.
927 Enable support for loading payloads from UBI. See
928 README.ubispl for more info.
932 bool "Support SPI DM drivers in SPL"
934 Enable support for SPI DM drivers in SPL.
936 config SPL_DM_SPI_FLASH
937 bool "Support SPI DM FLASH drivers in SPL"
939 Enable support for SPI DM flash drivers in SPL.
943 config SPL_UBI_LOAD_BY_VOLNAME
944 bool "Support loading volumes by name"
946 This enables support for loading UBI volumes by name. When this
947 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
948 configure the volume name from which to load U-Boot.
950 config SPL_UBI_MAX_VOL_LEBS
951 int "Maximum number of LEBs per volume"
954 The maximum number of logical eraseblocks which a static volume
955 to load can contain. Used for sizing the scan data structure.
957 config SPL_UBI_MAX_PEB_SIZE
958 int "Maximum PEB size"
961 The maximum physical erase block size.
963 config SPL_UBI_MAX_PEBS
964 int "Maximum number of PEBs"
967 The maximum physical erase block size. If not overridden by
968 board code, this value will be used as the actual number of PEBs.
970 config SPL_UBI_PEB_OFFSET
971 int "Offset to first UBI PEB"
974 The offset in number of PEBs from the start of flash to the first
975 PEB part of the UBI image.
977 config SPL_UBI_VID_OFFSET
978 int "Offset to VID header"
981 config SPL_UBI_LEB_START
982 int "Offset to LEB in PEB"
985 The offset in bytes to the LEB within a PEB.
987 config SPL_UBI_INFO_ADDR
988 hex "Address to place UBI scan info"
991 Address for ubispl to place the scan info. Read README.ubispl to
992 determine the required size
994 config SPL_UBI_VOL_IDS
995 int "Maximum volume id"
998 The maximum volume id which can be loaded. Used for sizing the
1001 config SPL_UBI_LOAD_MONITOR_ID
1002 int "id of U-Boot volume"
1005 The UBI volume id from which to load U-Boot
1007 config SPL_UBI_LOAD_MONITOR_VOLNAME
1008 string "volume name of U-Boot volume"
1009 depends on SPL_UBI_LOAD_BY_VOLNAME
1011 The UBI volume name from which to load U-Boot
1013 config SPL_UBI_LOAD_KERNEL_ID
1014 int "id of kernel volume"
1015 depends on SPL_OS_BOOT && SPL_UBI
1017 The UBI volume id from which to load the kernel
1019 config SPL_UBI_LOAD_ARGS_ID
1020 int "id of kernel args volume"
1021 depends on SPL_OS_BOOT && SPL_UBI
1023 The UBI volume id from which to load the device tree
1025 config UBI_SPL_SILENCE_MSG
1026 bool "silence UBI SPL messages"
1028 Disable messages from UBI SPL. This leaves warnings
1034 bool "Support networking"
1036 Enable support for network devices (such as Ethernet) in SPL.
1037 This permits SPL to load U-Boot over a network link rather than
1038 from an on-board peripheral. Environment support is required since
1039 the network stack uses a number of environment variables. See also
1043 config SPL_NET_VCI_STRING
1044 string "BOOTP Vendor Class Identifier string sent by SPL"
1046 As defined by RFC 2132 the vendor class identifier field can be
1047 sent by the client to identify the vendor type and configuration
1048 of a client. This is often used in practice to allow for the DHCP
1049 server to specify different files to load depending on if the ROM,
1050 SPL or U-Boot itself makes the request
1053 config SPL_NO_CPU_SUPPORT
1054 bool "Drop CPU code in SPL"
1056 This is specific to the ARM926EJ-S CPU. It disables the standard
1057 start.S start-up code, presumably so that a replacement can be
1058 used on that CPU. You should not enable it unless you know what
1061 config SPL_NOR_SUPPORT
1062 bool "Support NOR flash"
1064 Enable support for loading U-Boot from memory-mapped NOR (Negative
1065 OR) flash in SPL. NOR flash is slow to write but fast to read, and
1066 a memory-mapped device makes it very easy to access. Loading from
1067 NOR is typically achieved with just a memcpy().
1069 config SPL_XIP_SUPPORT
1073 Enable support for execute in place of U-Boot or kernel image. There
1074 is no need to copy image from flash to ram if flash supports execute
1075 in place. Its very useful in systems having enough flash but not
1076 enough ram to load the image.
1078 config SPL_ONENAND_SUPPORT
1079 bool "Support OneNAND flash"
1081 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
1082 a type of NAND flash and therefore can be used to allow SPL to
1083 load U-Boot from supported devices. This enables the drivers in
1084 drivers/mtd/onenand as part of an SPL build.
1087 bool "Activate Falcon Mode"
1088 depends on !TI_SECURE_DEVICE
1090 Enable booting directly to an OS from SPL.
1091 for more info read doc/README.falcon
1095 hex "addr, where OS is found"
1096 depends on SPL_NOR_SUPPORT
1098 Specify the address, where the OS image is found, which
1103 config SPL_FALCON_BOOT_MMCSD
1104 bool "Enable Falcon boot from MMC or SD media"
1105 depends on SPL_OS_BOOT && SPL_MMC
1107 Select this if the Falcon mode OS image mode is on MMC or SD media.
1109 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
1110 hex "Falcon mode: Sector to load kernel uImage from MMC"
1111 depends on SPL_FALCON_BOOT_MMCSD
1113 When Falcon mode is used with an MMC or SD media, SPL needs to know
1114 where to look for the kernel uImage. The image is expected to begin
1115 at the raw MMC specified in this config.
1116 Note that the Falcon mode image can also be a FIT, if FIT support is
1120 string "SPL payload"
1121 default "tpl/u-boot-with-tpl.bin" if TPL
1122 default "u-boot.bin"
1124 Payload for SPL boot. For backward compatibility, default to
1125 u-boot.bin, i.e. RAW image without any header. In case of
1126 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
1130 bool "Support PCI drivers"
1132 Enable support for PCI in SPL. For platforms that need PCI to boot,
1133 or must perform some init using PCI in SPL, this provides the
1134 necessary driver support. This enables the drivers in drivers/pci
1135 as part of an SPL build.
1138 bool "Support PCH drivers"
1140 Enable support for PCH (Platform Controller Hub) devices in SPL.
1141 These are used to set up GPIOs and the SPI peripheral early in
1142 boot. This enables the drivers in drivers/pch as part of an SPL
1145 config SPL_POST_MEM_SUPPORT
1146 bool "Support POST drivers"
1148 Enable support for POST (Power-on Self Test) in SPL. POST is a
1149 procedure that checks that the hardware (CPU or board) appears to
1150 be functionally correctly. It is a sanity check that can be
1151 performed before booting. This enables the drivers in post/drivers
1152 as part of an SPL build.
1155 bool "Support reset drivers"
1158 Enable support for reset control in SPL.
1159 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1160 by using the generic reset API provided by driver model.
1161 This enables the drivers in drivers/reset as part of an SPL build.
1164 bool "Support power drivers"
1166 Enable support for power control in SPL. This includes support
1167 for PMICs (Power-management Integrated Circuits) and some of the
1168 features provided by PMICs. In particular, voltage regulators can
1169 be used to enable/disable power and vary its voltage. That can be
1170 useful in SPL to turn on boot peripherals and adjust CPU voltage
1171 so that the clock speed can be increased. This enables the drivers
1172 in drivers/power, drivers/power/pmic and drivers/power/regulator
1173 as part of an SPL build.
1175 config SPL_POWER_DOMAIN
1176 bool "Support power domain drivers"
1179 Enable support for power domain control in SPL. Many SoCs allow
1180 power to be applied to or removed from portions of the SoC (power
1181 domains). This may be used to save power. This API provides the
1182 means to control such power management hardware. This enables
1183 the drivers in drivers/power/domain as part of a SPL build.
1185 config SPL_RAM_SUPPORT
1186 bool "Support booting from RAM"
1187 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1189 Enable booting of an image in RAM. The image can be preloaded or
1190 it can be loaded by SPL directly into RAM (e.g. using USB).
1192 config SPL_RAM_DEVICE
1193 bool "Support booting from preloaded image in RAM"
1194 depends on SPL_RAM_SUPPORT
1195 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1197 Enable booting of an image already loaded in RAM. The image has to
1198 be already in memory when SPL takes over, e.g. loaded by the boot
1201 config SPL_REMOTEPROC
1202 bool "Support REMOTEPROCS"
1204 Enable support for REMOTEPROCs in SPL. This permits to load
1205 a remote processor firmware in SPL.
1208 bool "Support RTC drivers"
1210 Enable RTC (Real-time Clock) support in SPL. This includes support
1211 for reading and setting the time. Some RTC devices also have some
1212 non-volatile (battery-backed) memory which is accessible if
1213 needed. This enables the drivers in drivers/rtc as part of an SPL
1217 bool "Support loading from SATA"
1219 Enable support for SATA (Serial AT attachment) in SPL. This allows
1220 use of SATA devices such as hard drives and flash drivers for
1221 loading U-Boot. SATA is used in higher-end embedded systems and
1222 can provide higher performance than MMC , at somewhat higher
1223 expense and power consumption. This enables loading from SATA
1224 using a configured device.
1226 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1227 bool "SATA raw mode: by sector"
1229 default y if ARCH_MVEBU
1231 Use sector number for specifying U-Boot location on SATA disk in
1234 config SPL_SATA_RAW_U_BOOT_SECTOR
1235 hex "Sector on the SATA disk to load U-Boot from"
1236 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1237 default 0x1 if ARCH_MVEBU
1239 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1240 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1243 bool "Support serial"
1247 Enable support for serial in SPL. This allows use of a serial UART
1248 for displaying messages while SPL is running. It also brings in
1249 printf() and panic() functions. This should normally be enabled
1250 unless there are space reasons not to. Even then, consider
1251 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1254 bool "Support SPI drivers"
1256 Enable support for using SPI in SPL. This is used for connecting
1257 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1258 more details on that. The SPI driver provides the transport for
1259 data between the SPI flash and the CPU. This option can be used to
1260 enable SPI drivers that are needed for other purposes also, such
1263 config SPL_SPI_FLASH_SUPPORT
1264 bool "Support SPI flash drivers"
1267 Enable support for using SPI flash in SPL, and loading U-Boot from
1268 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1269 the SPI bus that is used to connect it to a system. It is a simple
1270 but fast bidirectional 4-wire bus (clock, chip select and two data
1271 lines). This enables the drivers in drivers/mtd/spi as part of an
1272 SPL build. This normally requires SPL_SPI.
1274 if SPL_SPI_FLASH_SUPPORT
1276 config SPL_SPI_FLASH_TINY
1277 bool "Enable low footprint SPL SPI Flash support"
1278 depends on !SPI_FLASH_BAR
1279 default y if SPI_FLASH
1281 Enable lightweight SPL SPI Flash support that supports just reading
1282 data/images from flash. No support to write/erase flash. Enable
1283 this if you have SPL size limitations and don't need full
1284 fledged SPI flash support.
1286 config SPL_SPI_FLASH_SFDP_SUPPORT
1287 bool "SFDP table parsing support for SPI NOR flashes"
1288 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1290 Enable support for parsing and auto discovery of parameters for
1291 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1292 tables as per JESD216 standard in SPL.
1294 config SPL_SPI_FLASH_MTD
1295 bool "Support for SPI flash MTD drivers in SPL"
1297 Enable support for SPI flash MTD drivers in SPL.
1300 bool "Support loading from SPI flash"
1302 Enable support for loading next stage, U-Boot or otherwise, from
1303 SPI NOR in U-Boot SPL.
1305 endif # SPL_SPI_FLASH_SUPPORT
1307 config SYS_SPI_U_BOOT_OFFS
1308 hex "address of u-boot payload in SPI flash"
1309 default 0x8000 if ARCH_SUNXI
1311 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1313 Address within SPI-Flash from where the u-boot payload is fetched
1317 bool "Driver support for thermal devices"
1319 Enable support for temperature-sensing devices. Some SoCs have on-chip
1320 temperature sensors to permit warnings, speed throttling or even
1321 automatic power-off when the temperature gets too high or low. Other
1322 devices may be discrete but connected on a suitable bus.
1325 bool "Support USB host drivers"
1326 select HAVE_BLOCK_DEVICE
1328 Enable access to USB (Universal Serial Bus) host devices so that
1329 SPL can load U-Boot from a connected USB peripheral, such as a USB
1330 flash stick. While USB takes a little longer to start up than most
1331 buses, it is very flexible since many different types of storage
1332 device can be attached. This option enables the drivers in
1333 drivers/usb/host as part of an SPL build.
1335 config SPL_USB_STORAGE
1336 bool "Support loading from USB"
1337 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1339 Enable support for USB devices in SPL. This allows use of USB
1340 devices such as hard drives and flash drivers for loading U-Boot.
1341 The actual drivers are enabled separately using the normal U-Boot
1342 config options. This enables loading from USB using a configured
1345 config SPL_USB_GADGET
1346 bool "Suppport USB Gadget drivers"
1348 Enable USB Gadget API which allows to enable USB device functions
1353 config SPL_USB_ETHER
1354 bool "Support USB Ethernet drivers"
1357 Enable access to the USB network subsystem and associated
1358 drivers in SPL. This permits SPL to load U-Boot over a
1359 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1360 than from an onboard peripheral. Environment support is required
1361 since the network stack uses a number of environment variables.
1362 See also SPL_NET and SPL_ETH.
1365 bool "Support DFU (Device Firmware Upgrade)"
1367 select SPL_DFU_NO_RESET
1368 depends on SPL_RAM_SUPPORT
1370 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1371 RAM memory device support. The ROM code will load and execute
1372 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1373 selected device partition from host-pc using dfu-utils.
1374 This feature is useful to flash the binaries to factory or bare-metal
1375 boards using USB interface.
1378 bool "DFU device selection"
1383 depends on SPL_DFU && SPL_RAM_SUPPORT
1385 select RAM/DDR memory device for loading binary images
1386 (u-boot/kernel) to the selected device partition using
1387 DFU and execute the u-boot/kernel from RAM.
1391 config SPL_USB_SDP_SUPPORT
1392 bool "Support SDP (Serial Download Protocol)"
1393 depends on SPL_SERIAL
1395 Enable Serial Download Protocol (SDP) device support in SPL. This
1396 allows to download images into memory and execute (jump to) them
1397 using the same protocol as implemented by the i.MX family's boot ROM.
1399 config SPL_SDP_USB_DEV
1400 int "SDP USB controller index"
1402 depends on SPL_USB_SDP_SUPPORT
1404 Some boards have USB controller other than 0. Define this option
1405 so it can be used in compiled environment.
1409 bool "Support watchdog drivers"
1410 imply SPL_WDT if !HW_WATCHDOG
1412 Enable support for watchdog drivers in SPL. A watchdog is
1413 typically a hardware peripheral which can reset the system when it
1414 detects no activity for a while (such as a software crash). This
1415 enables the drivers in drivers/watchdog as part of an SPL build.
1417 config SPL_YMODEM_SUPPORT
1418 bool "Support loading using Ymodem"
1419 depends on SPL_SERIAL
1421 While loading from serial is slow it can be a useful backup when
1422 there is no other option. The Ymodem protocol provides a reliable
1423 means of transmitting U-Boot over a serial line for using in SPL,
1424 with a checksum to ensure correctness.
1427 bool "Support ARM Trusted Firmware"
1428 depends on ARM64 && SPL_FIT
1430 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1431 is loaded by SPL (which is considered as BL2 in ATF terminology).
1432 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1434 config SPL_ATF_LOAD_IMAGE_V2
1435 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1438 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1440 If you want to load a bl31 image from the SPL and need the new
1443 config SPL_ATF_NO_PLATFORM_PARAM
1444 bool "Pass no platform parameter"
1447 While we expect to call a pointer to a valid FDT (or NULL)
1448 as the platform parameter to an ATF, some ATF versions are
1449 not U-Boot aware and have an insufficiently robust parameter
1450 validation to gracefully reject a FDT being passed.
1452 If this option is enabled, the spl_atf os-type handler will
1453 always pass NULL for the platform parameter.
1455 If your ATF is affected, say Y.
1457 config SPL_AM33XX_ENABLE_RTC32K_OSC
1458 bool "Enable the RTC32K OSC on AM33xx based platforms"
1461 Enable access to the AM33xx RTC and select the external 32kHz clock
1464 config SPL_OPTEE_IMAGE
1465 bool "Support OP-TEE Trusted OS image in SPL"
1468 OP-TEE is an open source Trusted OS which is loaded by SPL.
1469 More detail at: https://github.com/OP-TEE/optee_os
1472 bool "Support RISC-V OpenSBI"
1473 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1475 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1476 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1477 firmware. It is loaded and started by U-Boot SPL.
1479 More details are available at https://github.com/riscv/opensbi and
1480 https://github.com/riscv/riscv-sbi-doc
1482 config SPL_OPENSBI_LOAD_ADDR
1483 hex "OpenSBI load address"
1484 depends on SPL_OPENSBI
1486 Load address of the OpenSBI binary.
1490 depends on SUPPORT_TPL
1493 If you want to build TPL as well as the normal image and SPL, say Y.
1497 config TPL_SIZE_LIMIT
1498 hex "Maximum size of TPL image"
1502 Specifies the maximum length of the U-Boot TPL image.
1503 If this value is zero, it is ignored.
1505 config TPL_BINMAN_SYMBOLS
1506 bool "Declare binman symbols in TPL"
1507 depends on SPL_FRAMEWORK && BINMAN
1510 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1511 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1512 and spl_get_image_size().
1514 For this to work, you must have a U-Boot image in the binman image, so
1515 binman can update TPL with the location of it.
1517 config TPL_FRAMEWORK
1518 bool "Support TPL based upon the common SPL framework"
1519 default y if SPL_FRAMEWORK
1521 Enable the SPL framework under common/spl/ for TPL builds.
1522 This framework supports MMC, NAND and YMODEM and other methods
1523 loading of U-Boot's SPL stage. If unsure, say Y.
1526 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1527 depends on HANDOFF && TPL_BLOBLIST
1530 This option enables TPL to write handoff information. This can be
1531 used to pass information like the size of SDRAM from TPL to U-Boot
1532 proper. The information is also available to SPL if it is useful
1535 config TPL_BOARD_INIT
1536 bool "Call board-specific initialization in TPL"
1538 If this option is enabled, U-Boot will call the function
1539 spl_board_init() from board_init_r(). This function should be
1540 provided by the board.
1542 config TPL_BOOTCOUNT_LIMIT
1543 bool "Support bootcount in TPL"
1544 depends on TPL_ENV_SUPPORT
1546 If this option is enabled, the TPL will support bootcount.
1547 For example, it may be useful to choose the device to boot.
1550 string "Linker script for the TPL stage"
1552 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1553 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1555 The TPL stage will usually require a different linker-script
1556 (as it runs from a different memory region) than the regular
1557 U-Boot stage. Set this to the path of the linker-script to
1560 May be left empty to trigger the Makefile infrastructure to
1561 fall back to the linker-script used for the SPL stage.
1563 config TPL_NEEDS_SEPARATE_STACK
1564 bool "TPL needs a separate initial stack-pointer"
1567 Enable, if the TPL stage should not inherit its initial
1568 stack-pointer from the settings for the SPL stage.
1571 bool "Support power drivers"
1573 Enable support for power control in TPL. This includes support
1574 for PMICs (Power-management Integrated Circuits) and some of the
1575 features provided by PMICs. In particular, voltage regulators can
1576 be used to enable/disable power and vary its voltage. That can be
1577 useful in TPL to turn on boot peripherals and adjust CPU voltage
1578 so that the clock speed can be increased. This enables the drivers
1579 in drivers/power, drivers/power/pmic and drivers/power/regulator
1580 as part of an TPL build.
1582 config TPL_TEXT_BASE
1583 hex "Base address for the .text section of the TPL stage"
1586 The base address for the .text section of the TPL stage.
1589 hex "Maximum size (in bytes) for the TPL stage"
1590 default 0x2e000 if ROCKCHIP_RK3399
1591 default 0x8000 if ROCKCHIP_RK3288
1592 default 0x7000 if ROCKCHIP_RK322X || ROCKCHIP_RK3328 || ROCKCHIP_RK3368
1593 default 0x2800 if ROCKCHIP_PX30
1596 The maximum size (in bytes) of the TPL stage.
1599 hex "Offset to which the TPL should be padded before appending the TPL payload"
1600 depends on !TPL_FRAMEWORK && PPC
1601 default TPL_MAX_SIZE
1603 Image offset to which the TPL should be padded before appending the
1604 TPL payload. By default, this is defined as CONFIG_TPL_MAX_SIZE, or 0 if
1605 CONFIG_TPL_MAX_SIZE is undefined. CONFIG_TPL_PAD_TO must be either
1606 0, meaning to append the TPL payload without any padding, or >=
1607 CONFIG_TPL_MAX_SIZE.
1610 hex "Address of the initial stack-pointer for the TPL stage"
1611 depends on TPL_NEEDS_SEPARATE_STACK
1613 The address of the initial stack-pointer for the TPL stage.
1614 Usually this will be the (aligned) top-of-stack.
1616 config TPL_READ_ONLY
1618 depends on TPL_OF_PLATDATA
1619 select TPL_OF_PLATDATA_NO_BIND
1620 select TPL_OF_PLATDATA_RT
1622 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1623 section of memory. This means that of-platdata must make a copy (in
1624 writeable memory) of anything it wants to modify, such as
1625 device-private data.
1627 config TPL_BOOTROM_SUPPORT
1628 bool "Support returning to the BOOTROM (from TPL)"
1630 Some platforms (e.g. the Rockchip RK3368) provide support in their
1631 ROM for loading the next boot-stage after performing basic setup
1634 Enable this option, to return to the BOOTROM through the
1635 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1636 boot device list, if not implemented for a given board)
1639 bool "Support CRC32 in TPL"
1640 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1642 Enable this to support CRC32 in uImages or FIT images within SPL.
1643 This is a 32-bit checksum value that can be used to verify images.
1644 For FIT images, this is the least secure type of checksum, suitable
1645 for detected accidental image corruption. For secure applications you
1646 should consider SHA1 or SHA256.
1648 config TPL_DRIVERS_MISC
1649 bool "Support misc drivers in TPL"
1651 Enable miscellaneous drivers in TPL. These drivers perform various
1652 tasks that don't fall nicely into other categories, Enable this
1653 option to build the drivers in drivers/misc as part of an TPL
1654 build, for those that support building in TPL (not all drivers do).
1656 config TPL_ENV_SUPPORT
1657 bool "Support an environment"
1659 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1662 bool "Support GPIO in TPL"
1664 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1665 GPIOs allow U-Boot to read the state of an input line (high or
1666 low) and set the state of an output line. This can be used to
1667 drive LEDs, control power to various system parts and read user
1668 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1669 for example. Enable this option to build the drivers in
1670 drivers/gpio as part of an TPL build.
1675 Enable support for the I2C bus in TPL. See SPL_I2C for
1678 config TPL_LIBCOMMON_SUPPORT
1679 bool "Support common libraries"
1681 Enable support for common U-Boot libraries within TPL. See
1682 SPL_LIBCOMMON_SUPPORT for details.
1684 config TPL_LIBGENERIC_SUPPORT
1685 bool "Support generic libraries"
1687 Enable support for generic U-Boot libraries within TPL. See
1688 SPL_LIBGENERIC_SUPPORT for details.
1690 config TPL_MPC8XXX_INIT_DDR
1691 bool "Support MPC8XXX DDR init"
1693 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1694 SPL_MPC8XXX_INIT_DDR for details.
1700 Enable support for MMC within TPL. See SPL_MMC for details.
1702 config TPL_NAND_SUPPORT
1703 bool "Support NAND flash"
1705 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1708 bool "Support PCI drivers"
1710 Enable support for PCI in TPL. For platforms that need PCI to boot,
1711 or must perform some init using PCI in SPL, this provides the
1712 necessary driver support. This enables the drivers in drivers/pci
1713 as part of a TPL build.
1716 bool "Support PCH drivers"
1718 Enable support for PCH (Platform Controller Hub) devices in TPL.
1719 These are used to set up GPIOs and the SPI peripheral early in
1720 boot. This enables the drivers in drivers/pch as part of a TPL
1723 config TPL_RAM_SUPPORT
1724 bool "Support booting from RAM"
1726 Enable booting of an image in RAM. The image can be preloaded or
1727 it can be loaded by TPL directly into RAM (e.g. using USB).
1729 config TPL_RAM_DEVICE
1730 bool "Support booting from preloaded image in RAM"
1731 depends on TPL_RAM_SUPPORT
1733 Enable booting of an image already loaded in RAM. The image has to
1734 be already in memory when TPL takes over, e.g. loaded by the boot
1738 bool "Support RTC drivers"
1740 Enable RTC (Real-time Clock) support in TPL. This includes support
1741 for reading and setting the time. Some RTC devices also have some
1742 non-volatile (battery-backed) memory which is accessible if
1743 needed. This enables the drivers in drivers/rtc as part of an TPL
1747 bool "Support serial"
1751 Enable support for serial in TPL. See SPL_SERIAL for
1754 config TPL_SPI_FLASH_SUPPORT
1755 bool "Support SPI flash drivers"
1757 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1760 config TPL_SPI_FLASH_TINY
1761 bool "Enable low footprint TPL SPI Flash support"
1762 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1763 default y if SPI_FLASH
1765 Enable lightweight TPL SPI Flash support that supports just reading
1766 data/images from flash. No support to write/erase flash. Enable
1767 this if you have TPL size limitations and don't need full-fledged
1771 bool "Support loading from SPI flash"
1772 depends on TPL_SPI_FLASH_SUPPORT
1774 Enable support for loading next stage, U-Boot or otherwise, from
1775 SPI NOR in U-Boot TPL.
1778 bool "Support SPI drivers"
1780 Enable support for using SPI in TPL. See SPL_SPI for
1784 bool "Support SPI DM drivers in TPL"
1786 Enable support for SPI DM drivers in TPL.
1788 config TPL_DM_SPI_FLASH
1789 bool "Support SPI DM FLASH drivers in TPL"
1791 Enable support for SPI DM flash drivers in TPL.
1793 config TPL_YMODEM_SUPPORT
1794 bool "Support loading using Ymodem"
1795 depends on TPL_SERIAL
1797 While loading from serial is slow it can be a useful backup when
1798 there is no other option. The Ymodem protocol provides a reliable
1799 means of transmitting U-Boot over a serial line for using in TPL,
1800 with a checksum to ensure correctness.
1806 depends on SUPPORT_SPL
1809 If you want to build VPL as well as the normal image, TPL and SPL,
1814 config VPL_BANNER_PRINT
1815 bool "Enable output of the VPL banner 'U-Boot VPL ...'"
1819 If this option is enabled, VPL will print the banner with version
1820 info. Disabling this option could be useful to reduce VPL boot time
1821 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
1823 config VPL_BOARD_INIT
1824 bool "Call board-specific initialization in VPL"
1826 If this option is enabled, U-Boot will call the function
1827 spl_board_init() from board_init_r(). This function should be
1828 provided by the board.
1832 bool "Support cache drivers in VPL"
1834 Enable support for cache drivers in VPL.
1837 bool "Support CRC32 in VPL"
1838 default y if VPL_ENV_SUPPORT || VPL_BLOBLIST
1840 Enable this to support CRC32 in uImages or FIT images within VPL.
1841 This is a 32-bit checksum value that can be used to verify images.
1842 For FIT images, this is the least secure type of checksum, suitable
1843 for detected accidental image corruption. For secure applications you
1844 should consider SHA1 or SHA256.
1847 bool "Support SPI DM drivers in VPL"
1849 Enable support for SPI DM drivers in VPL.
1851 config VPL_DM_SPI_FLASH
1852 bool "Support SPI DM FLASH drivers in VPL"
1854 Enable support for SPI DM flash drivers in VPL.
1856 config VPL_FRAMEWORK
1857 bool "Support VPL based upon the common SPL framework"
1860 Enable the SPL framework under common/spl/ for VPL builds.
1861 This framework supports MMC, NAND and YMODEM and other methods
1862 loading of U-Boot's next stage. If unsure, say Y.
1865 bool "Pass hand-off information from VPL to SPL"
1866 depends on HANDOFF && VPL_BLOBLIST
1869 This option enables VPL to write handoff information. This can be
1870 used to pass information like the size of SDRAM from VPL to SPL. Also
1871 VPL can receive information from TPL in the same place if that is
1874 config VPL_LIBCOMMON_SUPPORT
1875 bool "Support common libraries"
1876 default y if SPL_LIBCOMMON_SUPPORT
1878 Enable support for common U-Boot libraries within VPL. See
1879 SPL_LIBCOMMON_SUPPORT for details.
1881 config VPL_LIBGENERIC_SUPPORT
1882 bool "Support generic libraries"
1883 default y if SPL_LIBGENERIC_SUPPORT
1885 Enable support for generic U-Boot libraries within VPL. These
1886 libraries include generic code to deal with device tree, hashing,
1887 printf(), compression and the like. This option is enabled on many
1888 boards. Enable this option to build the code in lib/ as part of a
1891 config VPL_DRIVERS_MISC
1892 bool "Support misc drivers"
1893 default y if TPL_DRIVERS_MISC
1895 Enable miscellaneous drivers in VPL. These drivers perform various
1896 tasks that don't fall nicely into other categories, Enable this
1897 option to build the drivers in drivers/misc as part of a VPL
1898 build, for those that support building in VPL (not all drivers do).
1900 config VPL_ENV_SUPPORT
1901 bool "Support an environment"
1903 Enable environment support in VPL. The U-Boot environment provides
1904 a number of settings (essentially name/value pairs) which can
1905 control many aspects of U-Boot's operation. Enabling this option will
1906 make env_get() and env_set() available in VSPL.
1909 bool "Support GPIO in VPL"
1910 default y if SPL_GPIO
1912 Enable support for GPIOs (General-purpose Input/Output) in VPL.
1913 GPIOs allow U-Boot to read the state of an input line (high or
1914 low) and set the state of an output line. This can be used to
1915 drive LEDs, control power to various system parts and read user
1916 input. GPIOs can be useful in VPL to enable a 'sign-of-life' LED,
1917 for example. Enable this option to build the drivers in
1918 drivers/gpio as part of a VPL build.
1921 bool "Pass hand-off information from VPL to SPL and U-Boot proper"
1922 depends on HANDOFF && VPL_BLOBLIST
1925 This option enables VPL to write handoff information. This can be
1926 used to pass information like the size of SDRAM from VPL to U-Boot
1927 proper. The information is also available to VPL if it is useful
1931 bool "Support hashing drivers in VPL"
1936 Enable hashing drivers in VPL. These drivers can be used to
1937 accelerate secure boot processing in secure applications. Enable
1938 this option to build system-specific drivers for hash acceleration
1939 as part of a VPL build.
1941 config VPL_I2C_SUPPORT
1942 bool "Support I2C in VPL"
1943 default y if SPL_I2C_SUPPORT
1945 Enable support for the I2C bus in VPL. Vee SPL_I2C_SUPPORT for
1948 config VPL_PCH_SUPPORT
1949 bool "Support PCH drivers"
1950 default y if TPL_PCH_SUPPORT
1952 Enable support for PCH (Platform Controller Hub) devices in VPL.
1953 These are used to set up GPIOs and the SPI peripheral early in
1954 boot. This enables the drivers in drivers/pch as part of a VPL
1958 bool "Support PCI drivers"
1959 default y if SPL_PCI
1961 Enable support for PCI in VPL. For platforms that need PCI to boot,
1962 or must perform some init using PCI in VPL, this provides the
1963 necessary driver support. This enables the drivers in drivers/pci
1964 as part of a VPL build.
1967 bool "Support RTC drivers"
1969 Enable RTC (Real-time Clock) support in VPL. This includes support
1970 for reading and setting the time. Some RTC devices also have some
1971 non-volatile (battery-backed) memory which is accessible if
1972 needed. This enables the drivers in drivers/rtc as part of a VPL
1976 bool "Support serial"
1977 default y if TPL_SERIAL
1981 Enable support for serial in VPL. See SPL_SERIAL_SUPPORT for
1984 config VPL_SIZE_LIMIT
1985 hex "Maximum size of VPL image"
1989 Specifies the maximum length of the U-Boot VPL image.
1990 If this value is zero, it is ignored.
1993 bool "Support SPI drivers"
1995 Enable support for using SPI in VPL. See SPL_SPI_SUPPORT for
1998 config VPL_SPI_FLASH_SUPPORT
1999 bool "Support SPI flash drivers"
2001 Enable support for using SPI flash in VPL, and loading U-Boot from
2002 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
2003 the SPI bus that is used to connect it to a system. It is a simple
2004 but fast bidirectional 4-wire bus (clock, chip select and two data
2005 lines). This enables the drivers in drivers/mtd/spi as part of a
2006 VPL build. This normally requires VPL_SPI_SUPPORT.
2008 config VPL_TEXT_BASE
2012 The address in memory that VPL will be running from.
2016 config SPL_AT91_MCK_BYPASS
2017 bool "Use external clock signal as a source of main clock for AT91 platforms"
2018 depends on ARCH_AT91
2020 Use external 8 to 24 Mhz clock signal as source of main clock instead
2021 of an external crystal oscillator.
2022 This option disables the internal driving on the XOUT pin.
2023 The external source has to provide a stable clock on the XIN pin.
2024 If this option is disabled, the SoC expects a crystal oscillator
2025 that needs driving on both XIN and XOUT lines.