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 / TPL specific options"
223 depends on PPC && (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"
234 config SPL_RELOC_TEXT_BASE
235 hex "Address to relocate SPL to"
236 default SPL_TEXT_BASE
238 If unspecified, this is equal to CONFIG_SPL_TEXT_BASE (i.e. no
241 config SPL_RELOC_STACK
242 hex "Address of the start of the stack SPL will use after relocation."
244 If unspecified, this is equal to CONFIG_SYS_SPL_MALLOC_START. Starting
245 address of the malloc pool used in SPL. When this option is set the full
246 malloc is used in SPL and it is set up by spl_init() and before that, the
247 simple malloc() can be used if CONFIG_SYS_MALLOC_F is defined.
249 config SPL_RELOC_MALLOC
250 bool "SPL has malloc pool after relocation"
252 config SPL_RELOC_MALLOC_ADDR
253 hex "Address of malloc pool in SPL"
254 depends on SPL_RELOC_MALLOC
256 config SPL_RELOC_MALLOC_SIZE
257 hex "Size of malloc pool in SPL"
258 depends on SPL_RELOC_MALLOC
260 config TPL_RELOC_TEXT_BASE
261 hex "Address to relocate TPL to"
263 default TPL_TEXT_BASE
265 If unspecified, this is equal to CONFIG_TPL_TEXT_BASE (i.e. no
268 config TPL_RELOC_STACK
269 hex "Address of the start of the stack TPL will use after relocation."
272 If unspecified, this is equal to CONFIG_SYS_TPL_MALLOC_START. Starting
273 address of the malloc pool used in TPL. When this option is set the full
274 malloc is used in TPL and it is set up by spl_init() and before that, the
275 simple malloc() can be used if CONFIG_SYS_MALLOC_F is defined.
277 config TPL_RELOC_MALLOC
278 bool "TPL has malloc pool after relocation"
281 config TPL_RELOC_MALLOC_ADDR
282 hex "Address of malloc pool in TPL"
283 depends on TPL_RELOC_MALLOC
285 config TPL_RELOC_MALLOC_SIZE
286 hex "Size of malloc pool in TPL"
287 depends on TPL_RELOC_MALLOC
292 bool "Pass hand-off information from SPL to U-Boot proper"
293 depends on SPL && BLOBLIST
295 It is useful to be able to pass information from SPL to U-Boot
296 proper to preserve state that is known in SPL and is needed in U-Boot.
297 Enable this to locate the handoff information in U-Boot proper, early
298 in boot. It is available in gd->handoff. The state state is set up
299 in SPL (or TPL if that is being used).
304 bool "Pass hand-off information from SPL to U-Boot proper"
305 depends on HANDOFF && SPL_BLOBLIST
308 This option enables SPL to write handoff information. This can be
309 used to pass information like the size of SDRAM from SPL to U-Boot
310 proper. Also SPL can receive information from TPL in the same place
314 string "Linker script for the SPL stage"
315 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
317 The SPL stage will usually require a different linker-script
318 (as it runs from a different memory region) than the regular
319 U-Boot stage. Set this to the path of the linker-script to
324 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
325 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
326 default 0x20060 if SUN50I_GEN_H6
327 default 0x00060 if ARCH_SUNXI
328 default 0xfffc0000 if ARCH_ZYNQMP
331 The address in memory that SPL will be running from.
333 config SPL_BOARD_INIT
334 bool "Call board-specific initialization in SPL"
336 If this option is enabled, U-Boot will call the function
337 spl_board_init() from board_init_r(). This function should be
338 provided by the board.
340 config VPL_BOARD_INIT
341 bool "Call board-specific initialization in VPL"
343 If this option is enabled, U-Boot will call the function
344 spl_board_init() from board_init_r(). This function should be
345 provided by the board.
347 config SPL_BOOTROM_SUPPORT
348 bool "Support returning to the BOOTROM"
350 Some platforms (e.g. the Rockchip RK3368) provide support in their
351 ROM for loading the next boot-stage after performing basic setup
354 Enable this option, to return to the BOOTROM through the
355 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
356 boot device list, if not implemented for a given board)
358 config SPL_BOOTCOUNT_LIMIT
359 bool "Support bootcount in SPL"
360 depends on SPL_ENV_SUPPORT && !TPL_BOOTCOUNT_LIMIT
362 On some boards, which use 'falcon' mode, it is necessary to check
363 and increment the number of boot attempts. Such boards do not
364 use proper U-Boot for normal boot flow and hence needs those
365 adjustments to be done in the SPL.
367 config SPL_RAW_IMAGE_SUPPORT
368 bool "Support SPL loading and booting of RAW images"
369 default n if (ARCH_MX6 && (SPL_MMC || SPL_SATA))
371 depends on !TI_SECURE_DEVICE
373 SPL will support loading and booting a RAW image when this option
374 is y. If this is not set, SPL will move on to other available
375 boot media to find a suitable image.
377 config SPL_LEGACY_IMAGE_FORMAT
378 bool "Support SPL loading and booting of Legacy images"
379 default y if !SPL_LOAD_FIT
380 depends on !TI_SECURE_DEVICE
382 SPL will support loading and booting Legacy images when this option
383 is y. If this is not set, SPL will move on to other available
384 boot media to find a suitable image.
386 config SPL_LEGACY_IMAGE_CRC_CHECK
387 bool "Check CRC of Legacy images"
388 depends on SPL_LEGACY_IMAGE_FORMAT
391 Enable this to check the CRC of Legacy images. While this increases
392 reliability, it affects both code size and boot duration.
393 If disabled, Legacy images are booted if the image magic and size
394 are correct, without further integrity checks.
396 config SPL_SYS_MALLOC_SIMPLE
398 prompt "Only use malloc_simple functions in the SPL"
400 Say Y here to only use the *_simple malloc functions from
401 malloc_simple.c, rather then using the versions from dlmalloc.c;
402 this will make the SPL binary smaller at the cost of more heap
403 usage as the *_simple malloc functions do not re-use free-ed mem.
405 config TPL_SYS_MALLOC_SIMPLE
407 prompt "Only use malloc_simple functions in the TPL"
410 Say Y here to only use the *_simple malloc functions from
411 malloc_simple.c, rather then using the versions from dlmalloc.c;
412 this will make the TPL binary smaller at the cost of more heap
413 usage as the *_simple malloc functions do not re-use free-ed mem.
415 config SPL_SHARES_INIT_SP_ADDR
416 bool "SPL and U-Boot use the same initial stack pointer location"
417 depends on (ARM || ARCH_JZ47XX || MICROBLAZE || RISCV) && SPL_FRAMEWORK
418 default n if ARCH_SUNXI || ARCH_MX6 || ARCH_MX7
421 In many cases, we can use the same initial stack pointer address for
422 both SPL and U-Boot itself. If you need to specify a different address
423 however, say N here and then set a different value in CONFIG_SPL_STACK.
426 hex "Initial stack pointer location"
427 depends on (ARM || ARCH_JZ47XX || MICROBLAZE || RISCV) && SPL_FRAMEWORK
428 depends on !SPL_SHARES_INIT_SP_ADDR
429 default 0x946bb8 if ARCH_MX7
430 default 0x93ffb8 if ARCH_MX6 && MX6_OCRAM_256KB
431 default 0x91ffb8 if ARCH_MX6 && !MX6_OCRAM_256KB
433 Address of the start of the stack SPL will use before SDRAM is
437 bool "Enable SDRAM location for SPL stack"
439 SPL starts off execution in SRAM and thus typically has only a small
440 stack available. Since SPL sets up DRAM while in its board_init_f()
441 function, it is possible for the stack to move there before
442 board_init_r() is reached. This option enables a special SDRAM
443 location for the SPL stack. U-Boot SPL switches to this after
444 board_init_f() completes, and before board_init_r() starts.
446 config SPL_STACK_R_ADDR
447 depends on SPL_STACK_R
448 hex "SDRAM location for SPL stack"
449 default 0x82000000 if ARCH_OMAP2PLUS
451 Specify the address in SDRAM for the SPL stack. This will be set up
452 before board_init_r() is called.
454 config SPL_STACK_R_MALLOC_SIMPLE_LEN
455 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
456 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
459 Specify the amount of the stack to use as memory pool for
460 malloc_simple after switching the stack to DRAM. This may be set
461 to give board_init_r() a larger heap then the initial heap in
462 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
464 config SPL_SEPARATE_BSS
465 bool "BSS section is in a different memory region from text"
467 Some platforms need a large BSS region in SPL and can provide this
468 because RAM is already set up. In this case BSS can be moved to RAM.
469 This option should then be enabled so that the correct device tree
470 location is used. Normally we put the device tree at the end of BSS
471 but with this option enabled, it goes at _image_binary_end.
475 depends on SPL_OF_PLATDATA
476 # Bind cannot be supported because the udevice structs are in read-only
477 # memory so we cannot update the linked lists.
478 select SPL_OF_PLATDATA_NO_BIND
479 select SPL_OF_PLATDATA_RT
481 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
482 section of memory. This means that of-platdata must make a copy (in
483 writeable memory) of anything it wants to modify, such as
486 config TPL_SEPARATE_BSS
487 bool "BSS section is in a different memory region from text"
488 default y if SPL_SEPARATE_BSS
490 Some platforms need a large BSS region in TPL and can provide this
491 because RAM is already set up. In this case BSS can be moved to RAM.
492 This option should then be enabled so that the correct device tree
493 location is used. Normally we put the device tree at the end of BSS
494 but with this option enabled, it goes at _image_binary_end.
496 config SPL_BANNER_PRINT
497 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
500 If this option is enabled, SPL will print the banner with version
501 info. Disabling this option could be useful to reduce SPL boot time
502 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
504 config TPL_BANNER_PRINT
505 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
509 If this option is enabled, TPL will print the banner with version
510 info. Disabling this option could be useful to reduce TPL boot time
511 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
514 depends on ARM && !ARM64
515 bool "Allows initializing BSS early before entering board_init_f"
517 On some platform we have sufficient memory available early on to
518 allow setting up and using a basic BSS prior to entering
519 board_init_f. Activating this option will also de-activate the
520 clearing of BSS during the SPL relocation process, thus allowing
521 to carry state from board_init_f to board_init_r by way of BSS.
523 config SPL_DISPLAY_PRINT
524 bool "Display a board-specific message in SPL"
526 If this option is enabled, U-Boot will call the function
527 spl_display_print() immediately after displaying the SPL console
528 banner ("U-Boot SPL ..."). This function should be provided by
531 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
532 bool "MMC raw mode: by sector"
533 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
534 ARCH_MX6 || ARCH_MX7 || \
535 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
536 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
537 OMAP44XX || OMAP54XX || AM33XX || AM43XX || \
538 TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
540 Use sector number for specifying U-Boot location on MMC/SD in
543 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
544 hex "Address on the MMC to load U-Boot from"
545 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
546 default 0x40 if ARCH_SUNXI
547 default 0x75 if ARCH_DAVINCI
548 default 0x8a if ARCH_MX6 || ARCH_MX7
549 default 0x100 if ARCH_UNIPHIER
550 default 0x0 if ARCH_MVEBU
551 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
552 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
553 OMAP54XX || AM33XX || AM43XX || ARCH_K3
554 default 0x4000 if ARCH_ROCKCHIP
555 default 0x822 if TARGET_SIFIVE_UNLEASHED || TARGET_SIFIVE_UNMATCHED
557 Address on the MMC to load U-Boot from, when the MMC is being used
558 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
560 config SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET
561 hex "U-Boot main hardware partition image offset"
562 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
563 default 0x10 if ARCH_SUNXI
566 On some platforms SPL location depends on hardware partition. The ROM
567 code skips the MBR sector when loading SPL from main hardware data
568 partition. This adds offset to the main U-Boot image. Set this symbol
569 to the number of skipped sectors.
571 If unsure, leave the default.
573 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
574 bool "MMC Raw mode: by partition"
576 Use a partition for loading U-Boot when using MMC/SD in raw mode.
578 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
579 hex "Partition to use to load U-Boot from"
580 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
583 Partition on the MMC to load U-Boot from when the MMC is being
586 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
587 bool "MMC raw mode: by partition type"
588 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
590 Use partition type for specifying U-Boot partition on MMC/SD in
591 raw mode. U-Boot will be loaded from the first partition of this
594 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
595 hex "Partition Type on the MMC to load U-Boot from"
596 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
598 Partition Type on the MMC to load U-Boot from, when the MMC is being
601 config SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
602 bool "Override eMMC EXT_CSC_PART_CONFIG by user defined partition"
603 depends on SUPPORT_EMMC_BOOT
605 eMMC boot partition is normally configured by the bits of the EXT_CSD
606 register (EXT_CSC_PART_CONFIG), BOOT_PARTITION_ENABLE field. In some
607 cases it might be required in SPL to load the image from different
608 partition than the partition selected by EXT_CSC_PART_CONFIG register.
609 Enable this option if you intend to use an eMMC boot partition other
610 then selected via EXT_CSC_PART_CONFIG register and specify the custom
611 partition number by the CONFIG_SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
614 config SYS_MMCSD_RAW_MODE_EMMC_BOOT_PARTITION
615 int "Number of the eMMC boot partition to use"
616 depends on SUPPORT_EMMC_BOOT_OVERRIDE_PART_CONFIG
619 eMMC boot partition number to use when the eMMC in raw mode and
620 the eMMC EXT_CSC_PART_CONFIG selection should be overridden in SPL
621 by user defined partition number.
625 default y if SPL_LEGACY_IMAGE_FORMAT || SPL_EFI_PARTITION
626 default y if SPL_ENV_SUPPORT || TPL_BLOBLIST
628 Enable this to support CRC32 in uImages or FIT images within SPL.
629 This is a 32-bit checksum value that can be used to verify images.
630 For FIT images, this is the least secure type of checksum, suitable
631 for detected accidental image corruption. For secure applications you
632 should consider SHA1 or SHA256.
638 Enable this to support MD5 in FIT images within SPL. An MD5
639 checksum is a 128-bit hash value used to check that the image
640 contents have not been corrupted. Note that MD5 is not considered
641 secure as it is possible (with a brute-force attack) to adjust the
642 image while still retaining the same MD5 hash value. For secure
643 applications where images may be changed maliciously, you should
644 consider SHA256 or SHA384.
646 config SPL_FIT_IMAGE_TINY
647 bool "Remove functionality from SPL FIT loading to reduce size"
649 default y if MACH_SUN50I || MACH_SUN50I_H5 || SUN50I_GEN_H6
650 default y if ARCH_IMX8M
652 Enable this to reduce the size of the FIT image loading code
653 in SPL, if space for the SPL binary is very tight.
655 This skips the recording of each loaded payload
656 (i.e. loadable) into the FDT (modifying the loaded FDT to
657 ensure this information is available to the next image
661 bool "Support CACHE drivers"
663 Enable CACHE drivers in SPL. These drivers can keep data so that
664 future requests for that data can be served faster. Enable this option
665 to build the drivers in drivers/cache as part of an SPL build.
668 bool "Support CPU drivers"
670 Enable this to support CPU drivers in SPL. These drivers can set
671 up CPUs and provide information about them such as the model and
672 name. This can be useful in SPL since setting up the CPUs earlier
673 may improve boot performance. Enable this option to build the
674 drivers in drivers/cpu as part of an SPL build.
677 bool "Support crypto drivers"
679 Enable crypto drivers in SPL. These drivers can be used to
680 accelerate secure boot processing in secure applications. Enable
681 this option to build the drivers in drivers/crypto as part of an
685 bool "Support DMA drivers"
687 Enable DMA (direct-memory-access) drivers in SPL. These drivers
688 can be used to handle memory-to-peripheral data transfer without
689 the CPU moving the data. Enable this option to build the drivers
690 in drivers/dma as part of an SPL build.
692 config SPL_DRIVERS_MISC
693 bool "Support misc drivers"
695 Enable miscellaneous drivers in SPL. These drivers perform various
696 tasks that don't fall nicely into other categories, Enable this
697 option to build the drivers in drivers/misc as part of an SPL
698 build, for those that support building in SPL (not all drivers do).
700 config SPL_ENV_SUPPORT
701 bool "Support an environment"
703 Enable environment support in SPL. The U-Boot environment provides
704 a number of settings (essentially name/value pairs) which can
705 control many aspects of U-Boot's operation. Normally this is not
706 needed in SPL as it has a much simpler task with less
707 configuration. But some boards use this to support 'Falcon' boot
708 on EXT2 and FAT, where SPL boots directly into Linux without
709 starting U-Boot first. Enabling this option will make env_get()
710 and env_set() available in SPL.
713 bool "Support save environment"
714 depends on SPL_ENV_SUPPORT
715 select SPL_MMC_WRITE if ENV_IS_IN_MMC
717 Enable save environment support in SPL after setenv. By default
718 the saveenv option is not provided in SPL, but some boards need
719 this support in 'Falcon' boot, where SPL need to boot from
720 different images based on environment variable set by OS. For
721 example OS may set "reboot_image" environment variable to
722 "recovery" inorder to boot recovery image by SPL. The SPL read
723 "reboot_image" and act accordingly and change the reboot_image
724 to default mode using setenv and save the environment.
727 bool "Support Ethernet"
728 depends on SPL_ENV_SUPPORT
731 Enable access to the network subsystem and associated Ethernet
732 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
733 link rather than from an on-board peripheral. Environment support
734 is required since the network stack uses a number of environment
735 variables. See also SPL_NET.
738 bool "Support EXT filesystems"
740 Enable support for EXT2/3/4 filesystems with SPL. This permits
741 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
742 filesystem from within SPL. Support for the underlying block
743 device (e.g. MMC or USB) must be enabled separately.
745 config SPL_FS_SQUASHFS
746 bool "Support SquashFS filesystems"
749 Enable support for SquashFS filesystems with SPL. This permits
750 U-Boot (or Linux in Falcon mode) to be loaded from a SquashFS
751 filesystem from within SPL. Support for the underlying block
752 device (e.g. MMC or USB) must be enabled separately.
755 bool "Support FAT filesystems"
758 Enable support for FAT and VFAT filesystems with SPL. This
759 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
760 filesystem from within SPL. Support for the underlying block
761 device (e.g. MMC or USB) must be enabled separately.
763 config SPL_FS_LOAD_PAYLOAD_NAME
764 string "File to load for U-Boot from the filesystem"
765 depends on SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS
766 default "tispl.bin" if SYS_K3_SPL_ATF
767 default "u-boot.itb" if SPL_LOAD_FIT
770 Filename to read to load U-Boot when reading from filesystem.
772 config SPL_FS_LOAD_KERNEL_NAME
773 string "File to load for the OS kernel from the filesystem"
774 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
777 Filename to read to load for the OS kernel when reading from the
780 config SPL_FS_LOAD_ARGS_NAME
781 string "File to load for the OS kernel argument parameters from the filesystem"
782 depends on (SPL_FS_EXT4 || SPL_FS_FAT || SPL_FS_SQUASHFS) && SPL_OS_BOOT
785 Filename to read to load for the OS kernel argument parameters from
789 bool "Support write for FAT filesystems"
791 Enable write support for FAT and VFAT filesystems with SPL.
792 Support for the underlying block device (e.g. MMC or USB) must be
798 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
799 provide software-configurable hardware which is typically used to
800 implement peripherals (such as UARTs, LCD displays, MMC) or
801 accelerate custom processing functions, such as image processing
802 or machine learning. Sometimes it is useful to program the FPGA
803 as early as possible during boot, and this option can enable that
807 bool "Support GPIO in SPL"
809 Enable support for GPIOs (General-purpose Input/Output) in SPL.
810 GPIOs allow U-Boot to read the state of an input line (high or
811 low) and set the state of an output line. This can be used to
812 drive LEDs, control power to various system parts and read user
813 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
814 for example. Enable this option to build the drivers in
815 drivers/gpio as part of an SPL build.
820 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
821 I2C works with a clock and data line which can be driven by a
822 one or more masters or slaves. It is a fairly complex bus but is
823 widely used as it only needs two lines for communication. Speeds of
824 400kbps are typical but up to 3.4Mbps is supported by some
825 hardware. I2C can be useful in SPL to configure power management
826 ICs (PMICs) before raising the CPU clock speed, for example.
827 Enable this option to build the drivers in drivers/i2c as part of
830 config SPL_LIBCOMMON_SUPPORT
831 bool "Support common libraries"
833 Enable support for common U-Boot libraries within SPL. These
834 libraries include common code to deal with U-Boot images,
835 environment and USB, for example. This option is enabled on many
836 boards. Enable this option to build the code in common/ as part of
839 config SPL_LIBDISK_SUPPORT
840 bool "Support disk partitions"
843 Enable support for disk partitions within SPL. 'Disk' is something
844 of a misnomer as it includes non-spinning media such as flash (as
845 used in MMC and USB sticks). Partitions provide a way for a disk
846 to be split up into separate regions, with a partition table placed
847 at the start or end which describes the location and size of each
848 'partition'. These partitions are typically uses as individual block
849 devices, typically with an EXT2 or FAT filesystem in each. This
850 option enables whatever partition support has been enabled in
851 U-Boot to also be used in SPL. It brings in the code in disk/.
853 config SPL_LIBGENERIC_SUPPORT
854 bool "Support generic libraries"
856 Enable support for generic U-Boot libraries within SPL. These
857 libraries include generic code to deal with device tree, hashing,
858 printf(), compression and the like. This option is enabled on many
859 boards. Enable this option to build the code in lib/ as part of an
862 config SPL_DM_MAILBOX
863 bool "Support Mailbox"
865 Enable support for Mailbox within SPL. This enable the inter
866 processor communication protocols tobe used within SPL. Enable
867 this option to build the drivers in drivers/mailbox as part of
873 select HAVE_BLOCK_DEVICE
875 Enable support for MMC (Multimedia Card) within SPL. This enables
876 the MMC protocol implementation and allows any enabled drivers to
877 be used within SPL. MMC can be used with or without disk partition
878 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
879 this option to build the drivers in drivers/mmc as part of an SPL
882 config SYS_MMCSD_FS_BOOT_PARTITION
883 int "MMC Boot Partition"
886 Partition on the MMC to load U-Boot from when the MMC is being
888 Use -1 as a special value to use the first bootable partition.
891 bool "Tiny MMC framework in SPL"
894 Enable MMC framework tinification support. This option is useful if
895 if your SPL is extremely size constrained. Heed the warning, enable
896 this option if and only if you know exactly what you are doing, if
897 you are reading this help text, you most likely have no idea :-)
899 The MMC framework is reduced to bare minimum to be useful. No malloc
900 support is needed for the MMC framework operation with this option
901 enabled. The framework supports exactly one MMC device and exactly
902 one MMC driver. The MMC driver can be adjusted to avoid any malloc
903 operations too, which can remove the need for malloc support in SPL
904 and thus further reduce footprint.
907 bool "MMC/SD/SDIO card support for write operations in SPL"
910 Enable write access to MMC and SD Cards in SPL
913 config SPL_MPC8XXX_INIT_DDR
914 bool "Support MPC8XXX DDR init"
916 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
917 random-access memory) on the MPC8XXX family within SPL. This
918 allows DRAM to be set up before loading U-Boot into that DRAM,
921 config SPL_MTD_SUPPORT
922 bool "Support MTD drivers"
924 Enable support for MTD (Memory Technology Device) within SPL. MTD
925 provides a block interface over raw NAND and can also be used with
926 SPI flash. This allows SPL to load U-Boot from supported MTD
927 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
928 to enable specific MTD drivers.
931 bool "Support new Mentor Graphics USB"
933 Enable support for Mentor Graphics USB in SPL. This is a new
934 driver used by some boards. Enable this option to build
935 the drivers in drivers/usb/musb-new as part of an SPL build. The
936 old drivers are in drivers/usb/musb.
938 config SPL_NAND_SUPPORT
939 bool "Support NAND flash"
941 Enable support for NAND (Negative AND) flash in SPL. NAND flash
942 can be used to allow SPL to load U-Boot from supported devices.
943 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
946 config SPL_NAND_RAW_ONLY
947 bool "Support to boot only raw u-boot.bin images"
948 depends on SPL_NAND_SUPPORT
950 Use this only if you need to save space.
952 config SPL_NAND_DRIVERS
953 bool "Use standard NAND driver"
955 SPL uses normal NAND drivers, not minimal drivers.
958 bool "Include standard ECC in SPL"
960 config SPL_NAND_SOFTECC
961 bool "Use software ECC in SPL"
962 depends on SPL_NAND_ECC
964 config SPL_NAND_SIMPLE
965 bool "Support simple NAND drivers in SPL"
967 Support for NAND boot using simple NAND drivers that
968 expose the cmd_ctrl() interface.
971 depends on SPL_NAND_DRIVERS
972 bool "Use Base NAND Driver"
974 Include nand_base.c in the SPL.
976 config SPL_NAND_IDENT
977 depends on SPL_NAND_BASE
978 bool "Use chip ID to identify NAND flash"
980 SPL uses the chip ID list to identify the NAND flash.
985 Enable support for loading payloads from UBI. See
986 README.ubispl for more info.
990 bool "Support SPI DM drivers in SPL"
992 Enable support for SPI DM drivers in SPL.
994 config SPL_DM_SPI_FLASH
995 bool "Support SPI DM FLASH drivers in SPL"
997 Enable support for SPI DM flash drivers in SPL.
1001 config SPL_UBI_LOAD_BY_VOLNAME
1002 bool "Support loading volumes by name"
1004 This enables support for loading UBI volumes by name. When this
1005 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
1006 configure the volume name from which to load U-Boot.
1008 config SPL_UBI_MAX_VOL_LEBS
1009 int "Maximum number of LEBs per volume"
1012 The maximum number of logical eraseblocks which a static volume
1013 to load can contain. Used for sizing the scan data structure.
1015 config SPL_UBI_MAX_PEB_SIZE
1016 int "Maximum PEB size"
1019 The maximum physical erase block size.
1021 config SPL_UBI_MAX_PEBS
1022 int "Maximum number of PEBs"
1025 The maximum physical erase block size. If not overridden by
1026 board code, this value will be used as the actual number of PEBs.
1028 config SPL_UBI_PEB_OFFSET
1029 int "Offset to first UBI PEB"
1032 The offset in number of PEBs from the start of flash to the first
1033 PEB part of the UBI image.
1035 config SPL_UBI_VID_OFFSET
1036 int "Offset to VID header"
1039 config SPL_UBI_LEB_START
1040 int "Offset to LEB in PEB"
1043 The offset in bytes to the LEB within a PEB.
1045 config SPL_UBI_INFO_ADDR
1046 hex "Address to place UBI scan info"
1049 Address for ubispl to place the scan info. Read README.ubispl to
1050 determine the required size
1052 config SPL_UBI_VOL_IDS
1053 int "Maximum volume id"
1056 The maximum volume id which can be loaded. Used for sizing the
1057 scan data structure.
1059 config SPL_UBI_LOAD_MONITOR_ID
1060 int "id of U-Boot volume"
1063 The UBI volume id from which to load U-Boot
1065 config SPL_UBI_LOAD_MONITOR_VOLNAME
1066 string "volume name of U-Boot volume"
1067 depends on SPL_UBI_LOAD_BY_VOLNAME
1069 The UBI volume name from which to load U-Boot
1071 config SPL_UBI_LOAD_KERNEL_ID
1072 int "id of kernel volume"
1073 depends on SPL_OS_BOOT && SPL_UBI
1075 The UBI volume id from which to load the kernel
1077 config SPL_UBI_LOAD_ARGS_ID
1078 int "id of kernel args volume"
1079 depends on SPL_OS_BOOT && SPL_UBI
1081 The UBI volume id from which to load the device tree
1083 config UBI_SPL_SILENCE_MSG
1084 bool "silence UBI SPL messages"
1086 Disable messages from UBI SPL. This leaves warnings
1092 bool "Support networking"
1094 Enable support for network devices (such as Ethernet) in SPL.
1095 This permits SPL to load U-Boot over a network link rather than
1096 from an on-board peripheral. Environment support is required since
1097 the network stack uses a number of environment variables. See also
1101 config SPL_NET_VCI_STRING
1102 string "BOOTP Vendor Class Identifier string sent by SPL"
1104 As defined by RFC 2132 the vendor class identifier field can be
1105 sent by the client to identify the vendor type and configuration
1106 of a client. This is often used in practice to allow for the DHCP
1107 server to specify different files to load depending on if the ROM,
1108 SPL or U-Boot itself makes the request
1111 config SPL_NO_CPU_SUPPORT
1112 bool "Drop CPU code in SPL"
1114 This is specific to the ARM926EJ-S CPU. It disables the standard
1115 start.S start-up code, presumably so that a replacement can be
1116 used on that CPU. You should not enable it unless you know what
1119 config SPL_NOR_SUPPORT
1120 bool "Support NOR flash"
1122 Enable support for loading U-Boot from memory-mapped NOR (Negative
1123 OR) flash in SPL. NOR flash is slow to write but fast to read, and
1124 a memory-mapped device makes it very easy to access. Loading from
1125 NOR is typically achieved with just a memcpy().
1127 config SPL_XIP_SUPPORT
1131 Enable support for execute in place of U-Boot or kernel image. There
1132 is no need to copy image from flash to ram if flash supports execute
1133 in place. Its very useful in systems having enough flash but not
1134 enough ram to load the image.
1136 config SPL_ONENAND_SUPPORT
1137 bool "Support OneNAND flash"
1139 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
1140 a type of NAND flash and therefore can be used to allow SPL to
1141 load U-Boot from supported devices. This enables the drivers in
1142 drivers/mtd/onenand as part of an SPL build.
1145 bool "Activate Falcon Mode"
1146 depends on !TI_SECURE_DEVICE
1148 Enable booting directly to an OS from SPL.
1149 for more info read doc/README.falcon
1153 hex "addr, where OS is found"
1154 depends on SPL_NOR_SUPPORT
1156 Specify the address, where the OS image is found, which
1161 config SPL_FALCON_BOOT_MMCSD
1162 bool "Enable Falcon boot from MMC or SD media"
1163 depends on SPL_OS_BOOT && SPL_MMC
1165 Select this if the Falcon mode OS image mode is on MMC or SD media.
1167 config SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
1168 hex "Falcon mode: Sector to load kernel uImage from MMC"
1169 depends on SPL_FALCON_BOOT_MMCSD
1171 When Falcon mode is used with an MMC or SD media, SPL needs to know
1172 where to look for the kernel uImage. The image is expected to begin
1173 at the raw MMC specified in this config.
1174 Note that the Falcon mode image can also be a FIT, if FIT support is
1178 string "SPL payload"
1179 default "tpl/u-boot-with-tpl.bin" if TPL
1180 default "u-boot.bin"
1182 Payload for SPL boot. For backward compatibility, default to
1183 u-boot.bin, i.e. RAW image without any header. In case of
1184 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
1188 bool "Support PCI drivers"
1190 Enable support for PCI in SPL. For platforms that need PCI to boot,
1191 or must perform some init using PCI in SPL, this provides the
1192 necessary driver support. This enables the drivers in drivers/pci
1193 as part of an SPL build.
1196 bool "Support PCH drivers"
1198 Enable support for PCH (Platform Controller Hub) devices in SPL.
1199 These are used to set up GPIOs and the SPI peripheral early in
1200 boot. This enables the drivers in drivers/pch as part of an SPL
1203 config SPL_POST_MEM_SUPPORT
1204 bool "Support POST drivers"
1206 Enable support for POST (Power-on Self Test) in SPL. POST is a
1207 procedure that checks that the hardware (CPU or board) appears to
1208 be functionally correctly. It is a sanity check that can be
1209 performed before booting. This enables the drivers in post/drivers
1210 as part of an SPL build.
1213 bool "Support reset drivers"
1216 Enable support for reset control in SPL.
1217 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
1218 by using the generic reset API provided by driver model.
1219 This enables the drivers in drivers/reset as part of an SPL build.
1222 bool "Support power drivers"
1224 Enable support for power control in SPL. This includes support
1225 for PMICs (Power-management Integrated Circuits) and some of the
1226 features provided by PMICs. In particular, voltage regulators can
1227 be used to enable/disable power and vary its voltage. That can be
1228 useful in SPL to turn on boot peripherals and adjust CPU voltage
1229 so that the clock speed can be increased. This enables the drivers
1230 in drivers/power, drivers/power/pmic and drivers/power/regulator
1231 as part of an SPL build.
1233 config SPL_POWER_DOMAIN
1234 bool "Support power domain drivers"
1237 Enable support for power domain control in SPL. Many SoCs allow
1238 power to be applied to or removed from portions of the SoC (power
1239 domains). This may be used to save power. This API provides the
1240 means to control such power management hardware. This enables
1241 the drivers in drivers/power/domain as part of a SPL build.
1243 config SPL_RAM_SUPPORT
1244 bool "Support booting from RAM"
1245 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1247 Enable booting of an image in RAM. The image can be preloaded or
1248 it can be loaded by SPL directly into RAM (e.g. using USB).
1250 config SPL_RAM_DEVICE
1251 bool "Support booting from preloaded image in RAM"
1252 depends on SPL_RAM_SUPPORT
1253 default y if MICROBLAZE || ARCH_SOCFPGA || ARCH_TEGRA || ARCH_ZYNQ
1255 Enable booting of an image already loaded in RAM. The image has to
1256 be already in memory when SPL takes over, e.g. loaded by the boot
1259 config SPL_REMOTEPROC
1260 bool "Support REMOTEPROCS"
1262 Enable support for REMOTEPROCs in SPL. This permits to load
1263 a remote processor firmware in SPL.
1266 bool "Support RTC drivers"
1268 Enable RTC (Real-time Clock) support in SPL. This includes support
1269 for reading and setting the time. Some RTC devices also have some
1270 non-volatile (battery-backed) memory which is accessible if
1271 needed. This enables the drivers in drivers/rtc as part of an SPL
1275 bool "Support loading from SATA"
1277 Enable support for SATA (Serial AT attachment) in SPL. This allows
1278 use of SATA devices such as hard drives and flash drivers for
1279 loading U-Boot. SATA is used in higher-end embedded systems and
1280 can provide higher performance than MMC , at somewhat higher
1281 expense and power consumption. This enables loading from SATA
1282 using a configured device.
1284 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
1285 bool "SATA raw mode: by sector"
1287 default y if ARCH_MVEBU
1289 Use sector number for specifying U-Boot location on SATA disk in
1292 config SPL_SATA_RAW_U_BOOT_SECTOR
1293 hex "Sector on the SATA disk to load U-Boot from"
1294 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
1295 default 0x1 if ARCH_MVEBU
1297 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
1298 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
1301 bool "Support serial"
1305 Enable support for serial in SPL. This allows use of a serial UART
1306 for displaying messages while SPL is running. It also brings in
1307 printf() and panic() functions. This should normally be enabled
1308 unless there are space reasons not to. Even then, consider
1309 enabling SPL_USE_TINY_PRINTF which is a small printf() version.
1312 bool "Support SPI drivers"
1314 Enable support for using SPI in SPL. This is used for connecting
1315 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1316 more details on that. The SPI driver provides the transport for
1317 data between the SPI flash and the CPU. This option can be used to
1318 enable SPI drivers that are needed for other purposes also, such
1321 config SPL_SPI_FLASH_SUPPORT
1322 bool "Support SPI flash drivers"
1325 Enable support for using SPI flash in SPL, and loading U-Boot from
1326 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
1327 the SPI bus that is used to connect it to a system. It is a simple
1328 but fast bidirectional 4-wire bus (clock, chip select and two data
1329 lines). This enables the drivers in drivers/mtd/spi as part of an
1330 SPL build. This normally requires SPL_SPI.
1332 if SPL_SPI_FLASH_SUPPORT
1334 config SPL_SPI_FLASH_TINY
1335 bool "Enable low footprint SPL SPI Flash support"
1336 depends on !SPI_FLASH_BAR
1337 default y if SPI_FLASH
1339 Enable lightweight SPL SPI Flash support that supports just reading
1340 data/images from flash. No support to write/erase flash. Enable
1341 this if you have SPL size limitations and don't need full
1342 fledged SPI flash support.
1344 config SPL_SPI_FLASH_SFDP_SUPPORT
1345 bool "SFDP table parsing support for SPI NOR flashes"
1346 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
1348 Enable support for parsing and auto discovery of parameters for
1349 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
1350 tables as per JESD216 standard in SPL.
1352 config SPL_SPI_FLASH_MTD
1353 bool "Support for SPI flash MTD drivers in SPL"
1355 Enable support for SPI flash MTD drivers in SPL.
1358 bool "Support loading from SPI flash"
1360 Enable support for loading next stage, U-Boot or otherwise, from
1361 SPI NOR in U-Boot SPL.
1363 endif # SPL_SPI_FLASH_SUPPORT
1365 config SYS_SPI_U_BOOT_OFFS
1366 hex "address of u-boot payload in SPI flash"
1367 default 0x8000 if ARCH_SUNXI
1369 depends on SPL_SPI_LOAD || SPL_SPI_SUNXI
1371 Address within SPI-Flash from where the u-boot payload is fetched
1375 bool "Driver support for thermal devices"
1377 Enable support for temperature-sensing devices. Some SoCs have on-chip
1378 temperature sensors to permit warnings, speed throttling or even
1379 automatic power-off when the temperature gets too high or low. Other
1380 devices may be discrete but connected on a suitable bus.
1383 bool "Support USB host drivers"
1384 select HAVE_BLOCK_DEVICE
1386 Enable access to USB (Universal Serial Bus) host devices so that
1387 SPL can load U-Boot from a connected USB peripheral, such as a USB
1388 flash stick. While USB takes a little longer to start up than most
1389 buses, it is very flexible since many different types of storage
1390 device can be attached. This option enables the drivers in
1391 drivers/usb/host as part of an SPL build.
1393 config SPL_USB_STORAGE
1394 bool "Support loading from USB"
1395 depends on SPL_USB_HOST && !(BLK && !DM_USB)
1397 Enable support for USB devices in SPL. This allows use of USB
1398 devices such as hard drives and flash drivers for loading U-Boot.
1399 The actual drivers are enabled separately using the normal U-Boot
1400 config options. This enables loading from USB using a configured
1403 config SPL_USB_GADGET
1404 bool "Suppport USB Gadget drivers"
1406 Enable USB Gadget API which allows to enable USB device functions
1411 config SPL_USB_ETHER
1412 bool "Support USB Ethernet drivers"
1415 Enable access to the USB network subsystem and associated
1416 drivers in SPL. This permits SPL to load U-Boot over a
1417 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1418 than from an onboard peripheral. Environment support is required
1419 since the network stack uses a number of environment variables.
1420 See also SPL_NET and SPL_ETH.
1423 bool "Support DFU (Device Firmware Upgrade)"
1425 select SPL_DFU_NO_RESET
1426 depends on SPL_RAM_SUPPORT
1428 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1429 RAM memory device support. The ROM code will load and execute
1430 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1431 selected device partition from host-pc using dfu-utils.
1432 This feature is useful to flash the binaries to factory or bare-metal
1433 boards using USB interface.
1436 bool "DFU device selection"
1441 depends on SPL_DFU && SPL_RAM_SUPPORT
1443 select RAM/DDR memory device for loading binary images
1444 (u-boot/kernel) to the selected device partition using
1445 DFU and execute the u-boot/kernel from RAM.
1449 config SPL_USB_SDP_SUPPORT
1450 bool "Support SDP (Serial Download Protocol)"
1451 depends on SPL_SERIAL
1453 Enable Serial Download Protocol (SDP) device support in SPL. This
1454 allows to download images into memory and execute (jump to) them
1455 using the same protocol as implemented by the i.MX family's boot ROM.
1457 config SPL_SDP_USB_DEV
1458 int "SDP USB controller index"
1460 depends on SPL_USB_SDP_SUPPORT
1462 Some boards have USB controller other than 0. Define this option
1463 so it can be used in compiled environment.
1467 bool "Support watchdog drivers"
1468 imply SPL_WDT if !HW_WATCHDOG
1470 Enable support for watchdog drivers in SPL. A watchdog is
1471 typically a hardware peripheral which can reset the system when it
1472 detects no activity for a while (such as a software crash). This
1473 enables the drivers in drivers/watchdog as part of an SPL build.
1475 config SPL_YMODEM_SUPPORT
1476 bool "Support loading using Ymodem"
1477 depends on SPL_SERIAL
1479 While loading from serial is slow it can be a useful backup when
1480 there is no other option. The Ymodem protocol provides a reliable
1481 means of transmitting U-Boot over a serial line for using in SPL,
1482 with a checksum to ensure correctness.
1485 bool "Support ARM Trusted Firmware"
1486 depends on ARM64 && SPL_FIT
1488 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1489 is loaded by SPL (which is considered as BL2 in ATF terminology).
1490 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1492 config SPL_ATF_LOAD_IMAGE_V2
1493 bool "Use the new LOAD_IMAGE_V2 parameter passing"
1496 Some platforms use the newer LOAD_IMAGE_V2 parameter passing.
1498 If you want to load a bl31 image from the SPL and need the new
1501 config SPL_ATF_NO_PLATFORM_PARAM
1502 bool "Pass no platform parameter"
1505 While we expect to call a pointer to a valid FDT (or NULL)
1506 as the platform parameter to an ATF, some ATF versions are
1507 not U-Boot aware and have an insufficiently robust parameter
1508 validation to gracefully reject a FDT being passed.
1510 If this option is enabled, the spl_atf os-type handler will
1511 always pass NULL for the platform parameter.
1513 If your ATF is affected, say Y.
1515 config SPL_AM33XX_ENABLE_RTC32K_OSC
1516 bool "Enable the RTC32K OSC on AM33xx based platforms"
1519 Enable access to the AM33xx RTC and select the external 32kHz clock
1522 config SPL_OPTEE_IMAGE
1523 bool "Support OP-TEE Trusted OS image in SPL"
1526 OP-TEE is an open source Trusted OS which is loaded by SPL.
1527 More detail at: https://github.com/OP-TEE/optee_os
1530 bool "Support RISC-V OpenSBI"
1531 depends on RISCV && SPL_RISCV_MMODE && RISCV_SMODE
1533 OpenSBI is an open-source implementation of the RISC-V Supervisor Binary
1534 Interface (SBI) specification. U-Boot supports the OpenSBI FW_DYNAMIC
1535 firmware. It is loaded and started by U-Boot SPL.
1537 More details are available at https://github.com/riscv/opensbi and
1538 https://github.com/riscv/riscv-sbi-doc
1540 config SPL_OPENSBI_LOAD_ADDR
1541 hex "OpenSBI load address"
1542 depends on SPL_OPENSBI
1544 Load address of the OpenSBI binary.
1548 depends on SUPPORT_TPL
1551 If you want to build TPL as well as the normal image and SPL, say Y.
1555 config TPL_SIZE_LIMIT
1556 hex "Maximum size of TPL image"
1560 Specifies the maximum length of the U-Boot TPL image.
1561 If this value is zero, it is ignored.
1563 config TPL_BINMAN_SYMBOLS
1564 bool "Declare binman symbols in TPL"
1565 depends on SPL_FRAMEWORK && BINMAN
1568 This enables use of symbols in TPL which refer to U-Boot, enabling TPL
1569 to obtain the location of U-Boot simply by calling spl_get_image_pos()
1570 and spl_get_image_size().
1572 For this to work, you must have a U-Boot image in the binman image, so
1573 binman can update TPL with the location of it.
1575 config TPL_FRAMEWORK
1576 bool "Support TPL based upon the common SPL framework"
1577 default y if SPL_FRAMEWORK
1579 Enable the SPL framework under common/spl/ for TPL builds.
1580 This framework supports MMC, NAND and YMODEM and other methods
1581 loading of U-Boot's SPL stage. If unsure, say Y.
1584 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1585 depends on HANDOFF && TPL_BLOBLIST
1588 This option enables TPL to write handoff information. This can be
1589 used to pass information like the size of SDRAM from TPL to U-Boot
1590 proper. The information is also available to SPL if it is useful
1593 config TPL_BOARD_INIT
1594 bool "Call board-specific initialization in TPL"
1596 If this option is enabled, U-Boot will call the function
1597 spl_board_init() from board_init_r(). This function should be
1598 provided by the board.
1600 config TPL_BOOTCOUNT_LIMIT
1601 bool "Support bootcount in TPL"
1602 depends on TPL_ENV_SUPPORT
1604 If this option is enabled, the TPL will support bootcount.
1605 For example, it may be useful to choose the device to boot.
1608 string "Linker script for the TPL stage"
1610 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1611 default "arch/\$(ARCH)/cpu/u-boot-spl.lds"
1613 The TPL stage will usually require a different linker-script
1614 (as it runs from a different memory region) than the regular
1615 U-Boot stage. Set this to the path of the linker-script to
1618 May be left empty to trigger the Makefile infrastructure to
1619 fall back to the linker-script used for the SPL stage.
1621 config TPL_NEEDS_SEPARATE_STACK
1622 bool "TPL needs a separate initial stack-pointer"
1625 Enable, if the TPL stage should not inherit its initial
1626 stack-pointer from the settings for the SPL stage.
1629 bool "Support power drivers"
1631 Enable support for power control in TPL. This includes support
1632 for PMICs (Power-management Integrated Circuits) and some of the
1633 features provided by PMICs. In particular, voltage regulators can
1634 be used to enable/disable power and vary its voltage. That can be
1635 useful in TPL to turn on boot peripherals and adjust CPU voltage
1636 so that the clock speed can be increased. This enables the drivers
1637 in drivers/power, drivers/power/pmic and drivers/power/regulator
1638 as part of an TPL build.
1640 config TPL_TEXT_BASE
1641 hex "Base address for the .text section of the TPL stage"
1644 The base address for the .text section of the TPL stage.
1647 hex "Maximum size (in bytes) for the TPL stage"
1648 default 0x2e000 if ROCKCHIP_RK3399
1649 default 0x8000 if ROCKCHIP_RK3288
1650 default 0x7000 if ROCKCHIP_RK322X || ROCKCHIP_RK3328 || ROCKCHIP_RK3368
1651 default 0x2800 if ROCKCHIP_PX30
1654 The maximum size (in bytes) of the TPL stage.
1657 hex "Offset to which the TPL should be padded before appending the TPL payload"
1658 depends on !TPL_FRAMEWORK && PPC
1659 default TPL_MAX_SIZE
1661 Image offset to which the TPL should be padded before appending the
1662 TPL payload. By default, this is defined as CONFIG_TPL_MAX_SIZE, or 0 if
1663 CONFIG_TPL_MAX_SIZE is undefined. CONFIG_TPL_PAD_TO must be either
1664 0, meaning to append the TPL payload without any padding, or >=
1665 CONFIG_TPL_MAX_SIZE.
1668 hex "Address of the initial stack-pointer for the TPL stage"
1669 depends on TPL_NEEDS_SEPARATE_STACK
1671 The address of the initial stack-pointer for the TPL stage.
1672 Usually this will be the (aligned) top-of-stack.
1674 config TPL_READ_ONLY
1676 depends on TPL_OF_PLATDATA
1677 select TPL_OF_PLATDATA_NO_BIND
1678 select TPL_OF_PLATDATA_RT
1680 Some platforms (e.g. x86 Apollo Lake) load SPL into a read-only
1681 section of memory. This means that of-platdata must make a copy (in
1682 writeable memory) of anything it wants to modify, such as
1683 device-private data.
1685 config TPL_BOOTROM_SUPPORT
1686 bool "Support returning to the BOOTROM (from TPL)"
1688 Some platforms (e.g. the Rockchip RK3368) provide support in their
1689 ROM for loading the next boot-stage after performing basic setup
1692 Enable this option, to return to the BOOTROM through the
1693 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1694 boot device list, if not implemented for a given board)
1697 bool "Support CRC32 in TPL"
1698 default y if TPL_ENV_SUPPORT || TPL_BLOBLIST
1700 Enable this to support CRC32 in uImages or FIT images within SPL.
1701 This is a 32-bit checksum value that can be used to verify images.
1702 For FIT images, this is the least secure type of checksum, suitable
1703 for detected accidental image corruption. For secure applications you
1704 should consider SHA1 or SHA256.
1706 config TPL_DRIVERS_MISC
1707 bool "Support misc drivers in TPL"
1709 Enable miscellaneous drivers in TPL. These drivers perform various
1710 tasks that don't fall nicely into other categories, Enable this
1711 option to build the drivers in drivers/misc as part of an TPL
1712 build, for those that support building in TPL (not all drivers do).
1714 config TPL_ENV_SUPPORT
1715 bool "Support an environment"
1717 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1720 bool "Support GPIO in TPL"
1722 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1723 GPIOs allow U-Boot to read the state of an input line (high or
1724 low) and set the state of an output line. This can be used to
1725 drive LEDs, control power to various system parts and read user
1726 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1727 for example. Enable this option to build the drivers in
1728 drivers/gpio as part of an TPL build.
1733 Enable support for the I2C bus in TPL. See SPL_I2C for
1736 config TPL_LIBCOMMON_SUPPORT
1737 bool "Support common libraries"
1739 Enable support for common U-Boot libraries within TPL. See
1740 SPL_LIBCOMMON_SUPPORT for details.
1742 config TPL_LIBGENERIC_SUPPORT
1743 bool "Support generic libraries"
1745 Enable support for generic U-Boot libraries within TPL. See
1746 SPL_LIBGENERIC_SUPPORT for details.
1748 config TPL_MPC8XXX_INIT_DDR
1749 bool "Support MPC8XXX DDR init"
1751 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1752 SPL_MPC8XXX_INIT_DDR for details.
1758 Enable support for MMC within TPL. See SPL_MMC for details.
1760 config TPL_NAND_SUPPORT
1761 bool "Support NAND flash"
1763 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1766 bool "Support PCI drivers"
1768 Enable support for PCI in TPL. For platforms that need PCI to boot,
1769 or must perform some init using PCI in SPL, this provides the
1770 necessary driver support. This enables the drivers in drivers/pci
1771 as part of a TPL build.
1774 bool "Support PCH drivers"
1776 Enable support for PCH (Platform Controller Hub) devices in TPL.
1777 These are used to set up GPIOs and the SPI peripheral early in
1778 boot. This enables the drivers in drivers/pch as part of a TPL
1781 config TPL_RAM_SUPPORT
1782 bool "Support booting from RAM"
1784 Enable booting of an image in RAM. The image can be preloaded or
1785 it can be loaded by TPL directly into RAM (e.g. using USB).
1787 config TPL_RAM_DEVICE
1788 bool "Support booting from preloaded image in RAM"
1789 depends on TPL_RAM_SUPPORT
1791 Enable booting of an image already loaded in RAM. The image has to
1792 be already in memory when TPL takes over, e.g. loaded by the boot
1796 bool "Support RTC drivers"
1798 Enable RTC (Real-time Clock) support in TPL. This includes support
1799 for reading and setting the time. Some RTC devices also have some
1800 non-volatile (battery-backed) memory which is accessible if
1801 needed. This enables the drivers in drivers/rtc as part of an TPL
1805 bool "Support serial"
1809 Enable support for serial in TPL. See SPL_SERIAL for
1812 config TPL_SPI_FLASH_SUPPORT
1813 bool "Support SPI flash drivers"
1815 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1818 config TPL_SPI_FLASH_TINY
1819 bool "Enable low footprint TPL SPI Flash support"
1820 depends on TPL_SPI_FLASH_SUPPORT && !SPI_FLASH_BAR
1821 default y if SPI_FLASH
1823 Enable lightweight TPL SPI Flash support that supports just reading
1824 data/images from flash. No support to write/erase flash. Enable
1825 this if you have TPL size limitations and don't need full-fledged
1829 bool "Support loading from SPI flash"
1830 depends on TPL_SPI_FLASH_SUPPORT
1832 Enable support for loading next stage, U-Boot or otherwise, from
1833 SPI NOR in U-Boot TPL.
1836 bool "Support SPI drivers"
1838 Enable support for using SPI in TPL. See SPL_SPI for
1842 bool "Support SPI DM drivers in TPL"
1844 Enable support for SPI DM drivers in TPL.
1846 config TPL_DM_SPI_FLASH
1847 bool "Support SPI DM FLASH drivers in TPL"
1849 Enable support for SPI DM flash drivers in TPL.
1851 config TPL_YMODEM_SUPPORT
1852 bool "Support loading using Ymodem"
1853 depends on TPL_SERIAL
1855 While loading from serial is slow it can be a useful backup when
1856 there is no other option. The Ymodem protocol provides a reliable
1857 means of transmitting U-Boot over a serial line for using in TPL,
1858 with a checksum to ensure correctness.
1864 depends on SUPPORT_SPL
1867 If you want to build VPL as well as the normal image, TPL and SPL,
1872 config VPL_BANNER_PRINT
1873 bool "Enable output of the VPL banner 'U-Boot VPL ...'"
1877 If this option is enabled, VPL will print the banner with version
1878 info. Disabling this option could be useful to reduce VPL boot time
1879 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
1881 config VPL_BOARD_INIT
1882 bool "Call board-specific initialization in VPL"
1884 If this option is enabled, U-Boot will call the function
1885 spl_board_init() from board_init_r(). This function should be
1886 provided by the board.
1890 bool "Support cache drivers in VPL"
1892 Enable support for cache drivers in VPL.
1895 bool "Support CRC32 in VPL"
1896 default y if VPL_ENV_SUPPORT || VPL_BLOBLIST
1898 Enable this to support CRC32 in uImages or FIT images within VPL.
1899 This is a 32-bit checksum value that can be used to verify images.
1900 For FIT images, this is the least secure type of checksum, suitable
1901 for detected accidental image corruption. For secure applications you
1902 should consider SHA1 or SHA256.
1905 bool "Support SPI DM drivers in VPL"
1907 Enable support for SPI DM drivers in VPL.
1909 config VPL_DM_SPI_FLASH
1910 bool "Support SPI DM FLASH drivers in VPL"
1912 Enable support for SPI DM flash drivers in VPL.
1914 config VPL_FRAMEWORK
1915 bool "Support VPL based upon the common SPL framework"
1918 Enable the SPL framework under common/spl/ for VPL builds.
1919 This framework supports MMC, NAND and YMODEM and other methods
1920 loading of U-Boot's next stage. If unsure, say Y.
1923 bool "Pass hand-off information from VPL to SPL"
1924 depends on HANDOFF && VPL_BLOBLIST
1927 This option enables VPL to write handoff information. This can be
1928 used to pass information like the size of SDRAM from VPL to SPL. Also
1929 VPL can receive information from TPL in the same place if that is
1932 config VPL_LIBCOMMON_SUPPORT
1933 bool "Support common libraries"
1934 default y if SPL_LIBCOMMON_SUPPORT
1936 Enable support for common U-Boot libraries within VPL. See
1937 SPL_LIBCOMMON_SUPPORT for details.
1939 config VPL_LIBGENERIC_SUPPORT
1940 bool "Support generic libraries"
1941 default y if SPL_LIBGENERIC_SUPPORT
1943 Enable support for generic U-Boot libraries within VPL. These
1944 libraries include generic code to deal with device tree, hashing,
1945 printf(), compression and the like. This option is enabled on many
1946 boards. Enable this option to build the code in lib/ as part of a
1949 config VPL_DRIVERS_MISC
1950 bool "Support misc drivers"
1951 default y if TPL_DRIVERS_MISC
1953 Enable miscellaneous drivers in VPL. These drivers perform various
1954 tasks that don't fall nicely into other categories, Enable this
1955 option to build the drivers in drivers/misc as part of a VPL
1956 build, for those that support building in VPL (not all drivers do).
1958 config VPL_ENV_SUPPORT
1959 bool "Support an environment"
1961 Enable environment support in VPL. The U-Boot environment provides
1962 a number of settings (essentially name/value pairs) which can
1963 control many aspects of U-Boot's operation. Enabling this option will
1964 make env_get() and env_set() available in VSPL.
1967 bool "Support GPIO in VPL"
1968 default y if SPL_GPIO
1970 Enable support for GPIOs (General-purpose Input/Output) in VPL.
1971 GPIOs allow U-Boot to read the state of an input line (high or
1972 low) and set the state of an output line. This can be used to
1973 drive LEDs, control power to various system parts and read user
1974 input. GPIOs can be useful in VPL to enable a 'sign-of-life' LED,
1975 for example. Enable this option to build the drivers in
1976 drivers/gpio as part of a VPL build.
1979 bool "Pass hand-off information from VPL to SPL and U-Boot proper"
1980 depends on HANDOFF && VPL_BLOBLIST
1983 This option enables VPL to write handoff information. This can be
1984 used to pass information like the size of SDRAM from VPL to U-Boot
1985 proper. The information is also available to VPL if it is useful
1989 bool "Support hashing drivers in VPL"
1994 Enable hashing drivers in VPL. These drivers can be used to
1995 accelerate secure boot processing in secure applications. Enable
1996 this option to build system-specific drivers for hash acceleration
1997 as part of a VPL build.
1999 config VPL_I2C_SUPPORT
2000 bool "Support I2C in VPL"
2001 default y if SPL_I2C_SUPPORT
2003 Enable support for the I2C bus in VPL. Vee SPL_I2C_SUPPORT for
2006 config VPL_PCH_SUPPORT
2007 bool "Support PCH drivers"
2008 default y if TPL_PCH_SUPPORT
2010 Enable support for PCH (Platform Controller Hub) devices in VPL.
2011 These are used to set up GPIOs and the SPI peripheral early in
2012 boot. This enables the drivers in drivers/pch as part of a VPL
2016 bool "Support PCI drivers"
2017 default y if SPL_PCI
2019 Enable support for PCI in VPL. For platforms that need PCI to boot,
2020 or must perform some init using PCI in VPL, this provides the
2021 necessary driver support. This enables the drivers in drivers/pci
2022 as part of a VPL build.
2025 bool "Support RTC drivers"
2027 Enable RTC (Real-time Clock) support in VPL. This includes support
2028 for reading and setting the time. Some RTC devices also have some
2029 non-volatile (battery-backed) memory which is accessible if
2030 needed. This enables the drivers in drivers/rtc as part of a VPL
2034 bool "Support serial"
2035 default y if TPL_SERIAL
2039 Enable support for serial in VPL. See SPL_SERIAL_SUPPORT for
2042 config VPL_SIZE_LIMIT
2043 hex "Maximum size of VPL image"
2047 Specifies the maximum length of the U-Boot VPL image.
2048 If this value is zero, it is ignored.
2051 bool "Support SPI drivers"
2053 Enable support for using SPI in VPL. See SPL_SPI_SUPPORT for
2056 config VPL_SPI_FLASH_SUPPORT
2057 bool "Support SPI flash drivers"
2059 Enable support for using SPI flash in VPL, and loading U-Boot from
2060 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
2061 the SPI bus that is used to connect it to a system. It is a simple
2062 but fast bidirectional 4-wire bus (clock, chip select and two data
2063 lines). This enables the drivers in drivers/mtd/spi as part of a
2064 VPL build. This normally requires VPL_SPI_SUPPORT.
2066 config VPL_TEXT_BASE
2070 The address in memory that VPL will be running from.
2074 config SPL_AT91_MCK_BYPASS
2075 bool "Use external clock signal as a source of main clock for AT91 platforms"
2076 depends on ARCH_AT91
2078 Use external 8 to 24 Mhz clock signal as source of main clock instead
2079 of an external crystal oscillator.
2080 This option disables the internal driving on the XOUT pin.
2081 The external source has to provide a stable clock on the XIN pin.
2082 If this option is disabled, the SoC expects a crystal oscillator
2083 that needs driving on both XIN and XOUT lines.