9 config SPL_DFU_NO_RESET
14 depends on SUPPORT_SPL
17 If you want to build SPL as well as the normal image, say Y.
20 bool "Support SPL based upon the common SPL framework"
24 Enable the SPL framework under common/spl/. This framework
25 supports MMC, NAND and YMODEM and other methods loading of U-Boot
26 and the Linux Kernel. If unsure, say Y.
29 int "Maximum size of SPL image"
31 default 69632 if ARCH_MX6
34 Specifies the maximum length of the U-Boot SPL image.
35 If this value is zero, it is ignored.
37 config SPL_SIZE_LIMIT_SUBTRACT_GD
38 bool "SPL image size check: provide space for global data"
39 depends on SPL_SIZE_LIMIT > 0
41 If enabled, aligned size of global data is reserved in
42 SPL_SIZE_LIMIT check to ensure such an image does not overflow SRAM
43 if SPL_SIZE_LIMIT describes the size of SRAM available for SPL when
44 pre-reloc global data is put into this SRAM, too.
46 config SPL_SIZE_LIMIT_SUBTRACT_MALLOC
47 bool "SPL image size check: provide space for malloc() pool before relocation"
48 depends on SPL_SIZE_LIMIT > 0
50 If enabled, SPL_SYS_MALLOC_F_LEN is reserved in SPL_SIZE_LIMIT check
51 to ensure such an image does not overflow SRAM if SPL_SIZE_LIMIT
52 describes the size of SRAM available for SPL when pre-reloc malloc
53 pool is put into this SRAM, too.
55 config SPL_SIZE_LIMIT_PROVIDE_STACK
56 hex "SPL image size check: provide stack space before relocation"
57 depends on SPL_SIZE_LIMIT > 0
60 If set, this size is reserved in SPL_SIZE_LIMIT check to ensure such
61 an image does not overflow SRAM if SPL_SIZE_LIMIT describes the size
62 of SRAM available for SPL when the stack required before reolcation
65 config SPL_SYS_STACK_F_CHECK_BYTE
69 Constant used to check the stack
71 config SPL_SYS_REPORT_STACK_F_USAGE
72 depends on SPL_SIZE_LIMIT_PROVIDE_STACK != 0
73 bool "Check and report stack usage in SPL before relocation"
75 If this option is enabled, the initial SPL stack is filled with 0xaa
76 very early, up to the size configured with
77 SPL_SIZE_LIMIT_PROVIDE_STACK.
78 Later when SPL is done using this initial stack and switches to a
79 stack in DRAM, the actually used size of this initial stack is
80 reported by examining the memory and searching for the lowest
81 occurrence of non 0xaa bytes.
82 This default implementation works for stacks growing down only.
84 menu "PowerPC SPL Boot options"
85 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
88 bool "Load SPL from NAND flash"
91 bool "Load SPL from SD Card / eMMC"
94 bool "Load SPL from SPI flash"
97 bool "Create SPL in Freescale PBI format"
99 Create boot binary having SPL binary in PBI format concatenated with
105 bool "Pass hand-off information from SPL to U-Boot proper"
108 It is useful to be able to pass information from SPL to U-Boot
109 proper to preserve state that is known in SPL and is needed in U-Boot.
110 Enable this to locate the handoff information in U-Boot proper, early
111 in boot. It is available in gd->handoff. The state state is set up
112 in SPL (or TPL if that is being used).
117 bool "Pass hand-off information from SPL to U-Boot proper"
121 This option enables SPL to write handoff information. This can be
122 used to pass information like the size of SDRAM from SPL to U-Boot
123 proper. Also SPL can receive information from TPL in the same place
127 string "Linker script for the SPL stage"
128 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
130 The SPL stage will usually require a different linker-script
131 (as it runs from a different memory region) than the regular
132 U-Boot stage. Set this to the path of the linker-script to
137 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
138 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
139 default 0x20060 if MACH_SUN50I_H6
140 default 0x00060 if ARCH_SUNXI
143 The address in memory that SPL will be running from.
145 config SPL_BOARD_INIT
146 bool "Call board-specific initialization in SPL"
148 If this option is enabled, U-Boot will call the function
149 spl_board_init() from board_init_r(). This function should be
150 provided by the board.
152 config SPL_BOOTROM_SUPPORT
153 bool "Support returning to the BOOTROM"
155 Some platforms (e.g. the Rockchip RK3368) provide support in their
156 ROM for loading the next boot-stage after performing basic setup
159 Enable this option, to return to the BOOTROM through the
160 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
161 boot device list, if not implemented for a given board)
163 config SPL_BOOTCOUNT_LIMIT
164 bool "Support bootcount in SPL"
165 depends on SPL_ENV_SUPPORT
167 On some boards, which use 'falcon' mode, it is necessary to check
168 and increment the number of boot attempts. Such boards do not
169 use proper U-Boot for normal boot flow and hence needs those
170 adjustments to be done in the SPL.
172 config SPL_RAW_IMAGE_SUPPORT
173 bool "Support SPL loading and booting of RAW images"
174 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
175 default y if !TI_SECURE_DEVICE
177 SPL will support loading and booting a RAW image when this option
178 is y. If this is not set, SPL will move on to other available
179 boot media to find a suitable image.
181 config SPL_LEGACY_IMAGE_SUPPORT
182 bool "Support SPL loading and booting of Legacy images"
183 default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
185 SPL will support loading and booting Legacy images when this option
186 is y. If this is not set, SPL will move on to other available
187 boot media to find a suitable image.
189 config SPL_LEGACY_IMAGE_CRC_CHECK
190 bool "Check CRC of Legacy images"
191 depends on SPL_LEGACY_IMAGE_SUPPORT
192 select SPL_CRC32_SUPPORT
194 Enable this to check the CRC of Legacy images. While this increases
195 reliability, it affects both code size and boot duration.
196 If disabled, Legacy images are booted if the image magic and size
197 are correct, without further integrity checks.
199 config SPL_SYS_MALLOC_SIMPLE
201 prompt "Only use malloc_simple functions in the SPL"
203 Say Y here to only use the *_simple malloc functions from
204 malloc_simple.c, rather then using the versions from dlmalloc.c;
205 this will make the SPL binary smaller at the cost of more heap
206 usage as the *_simple malloc functions do not re-use free-ed mem.
208 config TPL_SYS_MALLOC_SIMPLE
210 prompt "Only use malloc_simple functions in the TPL"
213 Say Y here to only use the *_simple malloc functions from
214 malloc_simple.c, rather then using the versions from dlmalloc.c;
215 this will make the TPL binary smaller at the cost of more heap
216 usage as the *_simple malloc functions do not re-use free-ed mem.
219 bool "Enable SDRAM location for SPL stack"
221 SPL starts off execution in SRAM and thus typically has only a small
222 stack available. Since SPL sets up DRAM while in its board_init_f()
223 function, it is possible for the stack to move there before
224 board_init_r() is reached. This option enables a special SDRAM
225 location for the SPL stack. U-Boot SPL switches to this after
226 board_init_f() completes, and before board_init_r() starts.
228 config SPL_STACK_R_ADDR
229 depends on SPL_STACK_R
230 hex "SDRAM location for SPL stack"
231 default 0x82000000 if ARCH_OMAP2PLUS
233 Specify the address in SDRAM for the SPL stack. This will be set up
234 before board_init_r() is called.
236 config SPL_STACK_R_MALLOC_SIMPLE_LEN
237 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
238 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
241 Specify the amount of the stack to use as memory pool for
242 malloc_simple after switching the stack to DRAM. This may be set
243 to give board_init_r() a larger heap then the initial heap in
244 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
246 config SPL_SEPARATE_BSS
247 bool "BSS section is in a different memory region from text"
249 Some platforms need a large BSS region in SPL and can provide this
250 because RAM is already set up. In this case BSS can be moved to RAM.
251 This option should then be enabled so that the correct device tree
252 location is used. Normally we put the device tree at the end of BSS
253 but with this option enabled, it goes at _image_binary_end.
255 config SPL_BANNER_PRINT
256 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
259 If this option is enabled, SPL will print the banner with version
260 info. Disabling this option could be useful to reduce TPL boot time
261 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
263 config TPL_BANNER_PRINT
264 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
268 If this option is enabled, SPL will not print the banner with version
269 info. Disabling this option could be useful to reduce SPL boot time
270 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
273 depends on ARM && !ARM64
274 bool "Allows initializing BSS early before entering board_init_f"
276 On some platform we have sufficient memory available early on to
277 allow setting up and using a basic BSS prior to entering
278 board_init_f. Activating this option will also de-activate the
279 clearing of BSS during the SPL relocation process, thus allowing
280 to carry state from board_init_f to board_init_r by way of BSS.
282 config SPL_DISPLAY_PRINT
283 bool "Display a board-specific message in SPL"
285 If this option is enabled, U-Boot will call the function
286 spl_display_print() immediately after displaying the SPL console
287 banner ("U-Boot SPL ..."). This function should be provided by
290 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
291 bool "MMC raw mode: by sector"
292 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
293 ARCH_MX6 || ARCH_MX7 || \
294 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
295 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
296 OMAP44XX || OMAP54XX || AM33XX || AM43XX
298 Use sector number for specifying U-Boot location on MMC/SD in
301 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
302 hex "Address on the MMC to load U-Boot from"
303 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
304 default 0x50 if ARCH_SUNXI
305 default 0x75 if ARCH_DAVINCI
306 default 0x8a if ARCH_MX6 || ARCH_MX7
307 default 0x100 if ARCH_UNIPHIER
308 default 0x140 if ARCH_MVEBU
309 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
310 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
311 OMAP54XX || AM33XX || AM43XX || ARCH_K3
312 default 0x4000 if ARCH_ROCKCHIP
314 Address on the MMC to load U-Boot from, when the MMC is being used
315 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
317 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
318 bool "MMC Raw mode: by partition"
320 Use a partition for loading U-Boot when using MMC/SD in raw mode.
322 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
323 hex "Partition to use to load U-Boot from"
324 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
327 Partition on the MMC to load U-Boot from when the MMC is being
330 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
331 bool "MMC raw mode: by partition type"
332 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
334 Use partition type for specifying U-Boot partition on MMC/SD in
335 raw mode. U-Boot will be loaded from the first partition of this
338 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
339 hex "Partition Type on the MMC to load U-Boot from"
340 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
342 Partition Type on the MMC to load U-Boot from, when the MMC is being
345 config SPL_CRC32_SUPPORT
347 default y if SPL_LEGACY_IMAGE_SUPPORT
349 Enable this to support CRC32 in uImages or FIT images within SPL.
350 This is a 32-bit checksum value that can be used to verify images.
351 For FIT images, this is the least secure type of checksum, suitable
352 for detected accidental image corruption. For secure applications you
353 should consider SHA1 or SHA256.
355 config SPL_MD5_SUPPORT
359 Enable this to support MD5 in FIT images within SPL. An MD5
360 checksum is a 128-bit hash value used to check that the image
361 contents have not been corrupted. Note that MD5 is not considered
362 secure as it is possible (with a brute-force attack) to adjust the
363 image while still retaining the same MD5 hash value. For secure
364 applications where images may be changed maliciously, you should
365 consider SHA1 or SHA256.
367 config SPL_SHA1_SUPPORT
372 Enable this to support SHA1 in FIT images within SPL. A SHA1
373 checksum is a 160-bit (20-byte) hash value used to check that the
374 image contents have not been corrupted or maliciously altered.
375 While SHA1 is fairly secure it is coming to the end of its life
376 due to the expanding computing power available to brute-force
377 attacks. For more security, consider SHA256.
379 config SPL_SHA256_SUPPORT
380 bool "Support SHA256"
384 Enable this to support SHA256 in FIT images within SPL. A SHA256
385 checksum is a 256-bit (32-byte) hash value used to check that the
386 image contents have not been corrupted. SHA256 is recommended for
387 use in secure applications since (as at 2016) there is no known
388 feasible attack that could produce a 'collision' with differing
389 input data. Use this for the highest security. Note that only the
390 SHA256 variant is supported: SHA512 and others are not currently
393 config SPL_FIT_IMAGE_TINY
394 bool "Remove functionality from SPL FIT loading to reduce size"
396 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
397 default y if ARCH_IMX8M
399 Enable this to reduce the size of the FIT image loading code
400 in SPL, if space for the SPL binary is very tight.
402 This removes the detection of image types (which forces the
403 first image to be treated as having a U-Boot style calling
404 convention) and skips the recording of each loaded payload
405 (i.e. loadable) into the FDT (modifying the loaded FDT to
406 ensure this information is available to the next image
409 config SPL_CPU_SUPPORT
410 bool "Support CPU drivers"
412 Enable this to support CPU drivers in SPL. These drivers can set
413 up CPUs and provide information about them such as the model and
414 name. This can be useful in SPL since setting up the CPUs earlier
415 may improve boot performance. Enable this option to build the
416 drivers in drivers/cpu as part of an SPL build.
418 config SPL_CRYPTO_SUPPORT
419 bool "Support crypto drivers"
421 Enable crypto drivers in SPL. These drivers can be used to
422 accelerate secure boot processing in secure applications. Enable
423 this option to build the drivers in drivers/crypto as part of an
426 config SPL_HASH_SUPPORT
427 bool "Support hashing drivers"
431 Enable hashing drivers in SPL. These drivers can be used to
432 accelerate secure boot processing in secure applications. Enable
433 this option to build system-specific drivers for hash acceleration
434 as part of an SPL build.
436 config TPL_HASH_SUPPORT
437 bool "Support hashing drivers in TPL"
441 Enable hashing drivers in SPL. These drivers can be used to
442 accelerate secure boot processing in secure applications. Enable
443 this option to build system-specific drivers for hash acceleration
444 as part of an SPL build.
446 config SPL_DMA_SUPPORT
447 bool "Support DMA drivers"
449 Enable DMA (direct-memory-access) drivers in SPL. These drivers
450 can be used to handle memory-to-peripheral data transfer without
451 the CPU moving the data. Enable this option to build the drivers
452 in drivers/dma as part of an SPL build.
454 config SPL_DRIVERS_MISC_SUPPORT
455 bool "Support misc drivers"
457 Enable miscellaneous drivers in SPL. These drivers perform various
458 tasks that don't fall nicely into other categories, Enable this
459 option to build the drivers in drivers/misc as part of an SPL
460 build, for those that support building in SPL (not all drivers do).
462 config SPL_ENV_SUPPORT
463 bool "Support an environment"
465 Enable environment support in SPL. The U-Boot environment provides
466 a number of settings (essentially name/value pairs) which can
467 control many aspects of U-Boot's operation. Normally this is not
468 needed in SPL as it has a much simpler task with less
469 configuration. But some boards use this to support 'Falcon' boot
470 on EXT2 and FAT, where SPL boots directly into Linux without
471 starting U-Boot first. Enabling this option will make env_get()
472 and env_set() available in SPL.
475 bool "Support save environment"
476 depends on SPL_ENV_SUPPORT
477 select SPL_MMC_WRITE if ENV_IS_IN_MMC
479 Enable save environment support in SPL after setenv. By default
480 the saveenv option is not provided in SPL, but some boards need
481 this support in 'Falcon' boot, where SPL need to boot from
482 different images based on environment variable set by OS. For
483 example OS may set "reboot_image" environment variable to
484 "recovery" inorder to boot recovery image by SPL. The SPL read
485 "reboot_image" and act accordingly and change the reboot_image
486 to default mode using setenv and save the environment.
488 config SPL_ETH_SUPPORT
489 bool "Support Ethernet"
490 depends on SPL_ENV_SUPPORT
492 Enable access to the network subsystem and associated Ethernet
493 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
494 link rather than from an on-board peripheral. Environment support
495 is required since the network stack uses a number of environment
496 variables. See also SPL_NET_SUPPORT.
499 bool "Support EXT filesystems"
501 Enable support for EXT2/3/4 filesystems with SPL. This permits
502 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
503 filesystem from within SPL. Support for the underlying block
504 device (e.g. MMC or USB) must be enabled separately.
507 bool "Support FAT filesystems"
510 Enable support for FAT and VFAT filesystems with SPL. This
511 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
512 filesystem from within SPL. Support for the underlying block
513 device (e.g. MMC or USB) must be enabled separately.
516 bool "Support write for FAT filesystems"
518 Enable write support for FAT and VFAT filesystems with SPL.
519 Support for the underlying block device (e.g. MMC or USB) must be
522 config SPL_FPGA_SUPPORT
525 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
526 provide software-configurable hardware which is typically used to
527 implement peripherals (such as UARTs, LCD displays, MMC) or
528 accelerate custom processing functions, such as image processing
529 or machine learning. Sometimes it is useful to program the FPGA
530 as early as possible during boot, and this option can enable that
533 config SPL_GPIO_SUPPORT
534 bool "Support GPIO in SPL"
536 Enable support for GPIOs (General-purpose Input/Output) in SPL.
537 GPIOs allow U-Boot to read the state of an input line (high or
538 low) and set the state of an output line. This can be used to
539 drive LEDs, control power to various system parts and read user
540 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
541 for example. Enable this option to build the drivers in
542 drivers/gpio as part of an SPL build.
544 config SPL_I2C_SUPPORT
547 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
548 I2C works with a clock and data line which can be driven by a
549 one or more masters or slaves. It is a fairly complex bus but is
550 widely used as it only needs two lines for communication. Speeds of
551 400kbps are typical but up to 3.4Mbps is supported by some
552 hardware. I2C can be useful in SPL to configure power management
553 ICs (PMICs) before raising the CPU clock speed, for example.
554 Enable this option to build the drivers in drivers/i2c as part of
557 config SPL_LIBCOMMON_SUPPORT
558 bool "Support common libraries"
560 Enable support for common U-Boot libraries within SPL. These
561 libraries include common code to deal with U-Boot images,
562 environment and USB, for example. This option is enabled on many
563 boards. Enable this option to build the code in common/ as part of
566 config SPL_LIBDISK_SUPPORT
567 bool "Support disk partitions"
570 Enable support for disk partitions within SPL. 'Disk' is something
571 of a misnomer as it includes non-spinning media such as flash (as
572 used in MMC and USB sticks). Partitions provide a way for a disk
573 to be split up into separate regions, with a partition table placed
574 at the start or end which describes the location and size of each
575 'partition'. These partitions are typically uses as individual block
576 devices, typically with an EXT2 or FAT filesystem in each. This
577 option enables whatever partition support has been enabled in
578 U-Boot to also be used in SPL. It brings in the code in disk/.
580 config SPL_LIBGENERIC_SUPPORT
581 bool "Support generic libraries"
583 Enable support for generic U-Boot libraries within SPL. These
584 libraries include generic code to deal with device tree, hashing,
585 printf(), compression and the like. This option is enabled on many
586 boards. Enable this option to build the code in lib/ as part of an
589 config SPL_DM_MAILBOX
590 bool "Support Mailbox"
592 Enable support for Mailbox within SPL. This enable the inter
593 processor communication protocols tobe used within SPL. Enable
594 this option to build the drivers in drivers/mailbox as part of
597 config SPL_MMC_SUPPORT
600 select HAVE_BLOCK_DEVICE
602 Enable support for MMC (Multimedia Card) within SPL. This enables
603 the MMC protocol implementation and allows any enabled drivers to
604 be used within SPL. MMC can be used with or without disk partition
605 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
606 this option to build the drivers in drivers/mmc as part of an SPL
610 bool "Tiny MMC framework in SPL"
611 depends on SPL_MMC_SUPPORT
614 Enable MMC framework tinification support. This option is useful if
615 if your SPL is extremely size constrained. Heed the warning, enable
616 this option if and only if you know exactly what you are doing, if
617 you are reading this help text, you most likely have no idea :-)
619 The MMC framework is reduced to bare minimum to be useful. No malloc
620 support is needed for the MMC framework operation with this option
621 enabled. The framework supports exactly one MMC device and exactly
622 one MMC driver. The MMC driver can be adjusted to avoid any malloc
623 operations too, which can remove the need for malloc support in SPL
624 and thus further reduce footprint.
627 bool "MMC/SD/SDIO card support for write operations in SPL"
628 depends on SPL_MMC_SUPPORT
631 Enable write access to MMC and SD Cards in SPL
634 config SPL_MPC8XXX_INIT_DDR_SUPPORT
635 bool "Support MPC8XXX DDR init"
637 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
638 random-access memory) on the MPC8XXX family within SPL. This
639 allows DRAM to be set up before loading U-Boot into that DRAM,
642 config SPL_MTD_SUPPORT
643 bool "Support MTD drivers"
645 Enable support for MTD (Memory Technology Device) within SPL. MTD
646 provides a block interface over raw NAND and can also be used with
647 SPI flash. This allows SPL to load U-Boot from supported MTD
648 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
649 to enable specific MTD drivers.
651 config SPL_MUSB_NEW_SUPPORT
652 bool "Support new Mentor Graphics USB"
654 Enable support for Mentor Graphics USB in SPL. This is a new
655 driver used by some boards. Enable this option to build
656 the drivers in drivers/usb/musb-new as part of an SPL build. The
657 old drivers are in drivers/usb/musb.
659 config SPL_NAND_SUPPORT
660 bool "Support NAND flash"
662 Enable support for NAND (Negative AND) flash in SPL. NAND flash
663 can be used to allow SPL to load U-Boot from supported devices.
664 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
670 Enable support for loading payloads from UBI. See
671 README.ubispl for more info.
674 config SPL_UBI_LOAD_BY_VOLNAME
675 bool "Support loading volumes by name"
677 This enables support for loading UBI volumes by name. When this
678 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
679 configure the volume name from which to load U-Boot.
681 config SPL_UBI_MAX_VOL_LEBS
682 int "Maximum number of LEBs per volume"
685 The maximum number of logical eraseblocks which a static volume
686 to load can contain. Used for sizing the scan data structure.
688 config SPL_UBI_MAX_PEB_SIZE
689 int "Maximum PEB size"
692 The maximum physical erase block size.
694 config SPL_UBI_MAX_PEBS
695 int "Maximum number of PEBs"
698 The maximum physical erase block size. If not overridden by
699 board code, this value will be used as the actual number of PEBs.
701 config SPL_UBI_PEB_OFFSET
702 int "Offset to first UBI PEB"
705 The offset in number of PEBs from the start of flash to the first
706 PEB part of the UBI image.
708 config SPL_UBI_VID_OFFSET
709 int "Offset to VID header"
712 config SPL_UBI_LEB_START
713 int "Offset to LEB in PEB"
716 The offset in bytes to the LEB within a PEB.
718 config SPL_UBI_INFO_ADDR
719 hex "Address to place UBI scan info"
722 Address for ubispl to place the scan info. Read README.ubispl to
723 determine the required size
725 config SPL_UBI_VOL_IDS
726 int "Maximum volume id"
729 The maximum volume id which can be loaded. Used for sizing the
732 config SPL_UBI_LOAD_MONITOR_ID
733 int "id of U-Boot volume"
736 The UBI volume id from which to load U-Boot
738 config SPL_UBI_LOAD_MONITOR_VOLNAME
739 string "volume name of U-Boot volume"
740 depends on SPL_UBI_LOAD_BY_VOLNAME
742 The UBI volume name from which to load U-Boot
744 config SPL_UBI_LOAD_KERNEL_ID
745 int "id of kernel volume"
746 depends on SPL_OS_BOOT && SPL_UBI
748 The UBI volume id from which to load the kernel
750 config SPL_UBI_LOAD_ARGS_ID
751 int "id of kernel args volume"
752 depends on SPL_OS_BOOT && SPL_UBI
754 The UBI volume id from which to load the device tree
756 config UBI_SPL_SILENCE_MSG
757 bool "silence UBI SPL messages"
760 Disable messages from UBI SPL. This leaves warnings
765 config SPL_NET_SUPPORT
766 bool "Support networking"
768 Enable support for network devices (such as Ethernet) in SPL.
769 This permits SPL to load U-Boot over a network link rather than
770 from an on-board peripheral. Environment support is required since
771 the network stack uses a number of environment variables. See also
775 config SPL_NET_VCI_STRING
776 string "BOOTP Vendor Class Identifier string sent by SPL"
778 As defined by RFC 2132 the vendor class identifier field can be
779 sent by the client to identify the vendor type and configuration
780 of a client. This is often used in practice to allow for the DHCP
781 server to specify different files to load depending on if the ROM,
782 SPL or U-Boot itself makes the request
783 endif # if SPL_NET_SUPPORT
785 config SPL_NO_CPU_SUPPORT
786 bool "Drop CPU code in SPL"
788 This is specific to the ARM926EJ-S CPU. It disables the standard
789 start.S start-up code, presumably so that a replacement can be
790 used on that CPU. You should not enable it unless you know what
793 config SPL_NOR_SUPPORT
794 bool "Support NOR flash"
796 Enable support for loading U-Boot from memory-mapped NOR (Negative
797 OR) flash in SPL. NOR flash is slow to write but fast to read, and
798 a memory-mapped device makes it very easy to access. Loading from
799 NOR is typically achieved with just a memcpy().
801 config SPL_XIP_SUPPORT
805 Enable support for execute in place of U-Boot or kernel image. There
806 is no need to copy image from flash to ram if flash supports execute
807 in place. Its very useful in systems having enough flash but not
808 enough ram to load the image.
810 config SPL_ONENAND_SUPPORT
811 bool "Support OneNAND flash"
813 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
814 a type of NAND flash and therefore can be used to allow SPL to
815 load U-Boot from supported devices. This enables the drivers in
816 drivers/mtd/onenand as part of an SPL build.
819 bool "Activate Falcon Mode"
820 depends on !TI_SECURE_DEVICE
823 Enable booting directly to an OS from SPL.
824 for more info read doc/README.falcon
828 hex "addr, where OS is found"
829 depends on SPL_NOR_SUPPORT
831 Specify the address, where the OS image is found, which
838 default "tpl/u-boot-with-tpl.bin" if TPL
841 Payload for SPL boot. For backward compatibility, default to
842 u-boot.bin, i.e. RAW image without any header. In case of
843 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
847 bool "Support PCI drivers"
849 Enable support for PCI in SPL. For platforms that need PCI to boot,
850 or must perform some init using PCI in SPL, this provides the
851 necessary driver support. This enables the drivers in drivers/pci
852 as part of an SPL build.
854 config SPL_PCH_SUPPORT
855 bool "Support PCH drivers"
857 Enable support for PCH (Platform Controller Hub) devices in SPL.
858 These are used to set up GPIOs and the SPI peripheral early in
859 boot. This enables the drivers in drivers/pch as part of an SPL
862 config SPL_POST_MEM_SUPPORT
863 bool "Support POST drivers"
865 Enable support for POST (Power-on Self Test) in SPL. POST is a
866 procedure that checks that the hardware (CPU or board) appears to
867 be functionally correctly. It is a sanity check that can be
868 performed before booting. This enables the drivers in post/drivers
869 as part of an SPL build.
872 bool "Support reset drivers"
875 Enable support for reset control in SPL.
876 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
877 by using the generic reset API provided by driver model.
878 This enables the drivers in drivers/reset as part of an SPL build.
880 config SPL_POWER_SUPPORT
881 bool "Support power drivers"
883 Enable support for power control in SPL. This includes support
884 for PMICs (Power-management Integrated Circuits) and some of the
885 features provided by PMICs. In particular, voltage regulators can
886 be used to enable/disable power and vary its voltage. That can be
887 useful in SPL to turn on boot peripherals and adjust CPU voltage
888 so that the clock speed can be increased. This enables the drivers
889 in drivers/power, drivers/power/pmic and drivers/power/regulator
890 as part of an SPL build.
892 config SPL_POWER_DOMAIN
893 bool "Support power domain drivers"
895 Enable support for power domain control in SPL. Many SoCs allow
896 power to be applied to or removed from portions of the SoC (power
897 domains). This may be used to save power. This API provides the
898 means to control such power management hardware. This enables
899 the drivers in drivers/power/domain as part of a SPL build.
901 config SPL_RAM_SUPPORT
902 bool "Support booting from RAM"
903 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
905 Enable booting of an image in RAM. The image can be preloaded or
906 it can be loaded by SPL directly into RAM (e.g. using USB).
908 config SPL_RAM_DEVICE
909 bool "Support booting from preloaded image in RAM"
910 depends on SPL_RAM_SUPPORT
911 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
913 Enable booting of an image already loaded in RAM. The image has to
914 be already in memory when SPL takes over, e.g. loaded by the boot
917 config SPL_REMOTEPROC
918 bool "Support REMOTEPROCS"
920 Enable support for REMOTEPROCs in SPL. This permits to load
921 a remote processor firmware in SPL.
923 config SPL_RTC_SUPPORT
924 bool "Support RTC drivers"
926 Enable RTC (Real-time Clock) support in SPL. This includes support
927 for reading and setting the time. Some RTC devices also have some
928 non-volatile (battery-backed) memory which is accessible if
929 needed. This enables the drivers in drivers/rtc as part of an SPL
932 config SPL_SATA_SUPPORT
933 bool "Support loading from SATA"
935 Enable support for SATA (Serial AT attachment) in SPL. This allows
936 use of SATA devices such as hard drives and flash drivers for
937 loading U-Boot. SATA is used in higher-end embedded systems and
938 can provide higher performance than MMC , at somewhat higher
939 expense and power consumption. This enables loading from SATA
940 using a configured device.
942 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
943 bool "SATA raw mode: by sector"
944 depends on SPL_SATA_SUPPORT
946 Use sector number for specifying U-Boot location on SATA disk in
949 config SPL_SATA_RAW_U_BOOT_SECTOR
950 hex "Sector on the SATA disk to load U-Boot from"
951 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
953 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
954 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
956 config SPL_SERIAL_SUPPORT
957 bool "Support serial"
961 Enable support for serial in SPL. This allows use of a serial UART
962 for displaying messages while SPL is running. It also brings in
963 printf() and panic() functions. This should normally be enabled
964 unless there are space reasons not to. Even then, consider
965 enabling USE_TINY_PRINTF which is a small printf() version.
967 config SPL_SPI_FLASH_SUPPORT
968 bool "Support SPI flash drivers"
970 Enable support for using SPI flash in SPL, and loading U-Boot from
971 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
972 the SPI bus that is used to connect it to a system. It is a simple
973 but fast bidirectional 4-wire bus (clock, chip select and two data
974 lines). This enables the drivers in drivers/mtd/spi as part of an
975 SPL build. This normally requires SPL_SPI_SUPPORT.
977 if SPL_SPI_FLASH_SUPPORT
979 config SPL_SPI_FLASH_TINY
980 bool "Enable low footprint SPL SPI Flash support"
981 depends on !SPI_FLASH_BAR
982 default y if SPI_FLASH
984 Enable lightweight SPL SPI Flash support that supports just reading
985 data/images from flash. No support to write/erase flash. Enable
986 this if you have SPL size limitations and don't need full
987 fledged SPI flash support.
989 config SPL_SPI_FLASH_SFDP_SUPPORT
990 bool "SFDP table parsing support for SPI NOR flashes"
991 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
993 Enable support for parsing and auto discovery of parameters for
994 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
995 tables as per JESD216 standard in SPL.
998 bool "Support loading from SPI flash"
1000 Enable support for loading next stage, U-Boot or otherwise, from
1001 SPI NOR in U-Boot SPL.
1003 endif # SPL_SPI_FLASH_SUPPORT
1005 config SPL_SPI_SUPPORT
1006 bool "Support SPI drivers"
1008 Enable support for using SPI in SPL. This is used for connecting
1009 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1010 more details on that. The SPI driver provides the transport for
1011 data between the SPI flash and the CPU. This option can be used to
1012 enable SPI drivers that are needed for other purposes also, such
1016 bool "Driver support for thermal devices"
1018 Enable support for temperature-sensing devices. Some SoCs have on-chip
1019 temperature sensors to permit warnings, speed throttling or even
1020 automatic power-off when the temperature gets too high or low. Other
1021 devices may be discrete but connected on a suitable bus.
1023 config SPL_USB_HOST_SUPPORT
1024 bool "Support USB host drivers"
1025 select HAVE_BLOCK_DEVICE
1027 Enable access to USB (Universal Serial Bus) host devices so that
1028 SPL can load U-Boot from a connected USB peripheral, such as a USB
1029 flash stick. While USB takes a little longer to start up than most
1030 buses, it is very flexible since many different types of storage
1031 device can be attached. This option enables the drivers in
1032 drivers/usb/host as part of an SPL build.
1034 config SPL_USB_STORAGE
1035 bool "Support loading from USB"
1036 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1038 Enable support for USB devices in SPL. This allows use of USB
1039 devices such as hard drives and flash drivers for loading U-Boot.
1040 The actual drivers are enabled separately using the normal U-Boot
1041 config options. This enables loading from USB using a configured
1044 config SPL_USB_GADGET
1045 bool "Suppport USB Gadget drivers"
1047 Enable USB Gadget API which allows to enable USB device functions
1052 config SPL_USB_ETHER
1053 bool "Support USB Ethernet drivers"
1055 Enable access to the USB network subsystem and associated
1056 drivers in SPL. This permits SPL to load U-Boot over a
1057 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1058 than from an onboard peripheral. Environment support is required
1059 since the network stack uses a number of environment variables.
1060 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1063 bool "Support DFU (Device Firmware Upgrade)"
1064 select SPL_HASH_SUPPORT
1065 select SPL_DFU_NO_RESET
1066 depends on SPL_RAM_SUPPORT
1068 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1069 RAM memory device support. The ROM code will load and execute
1070 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1071 selected device partition from host-pc using dfu-utils.
1072 This feature is useful to flash the binaries to factory or bare-metal
1073 boards using USB interface.
1076 bool "DFU device selection"
1081 depends on SPL_DFU && SPL_RAM_SUPPORT
1083 select RAM/DDR memory device for loading binary images
1084 (u-boot/kernel) to the selected device partition using
1085 DFU and execute the u-boot/kernel from RAM.
1089 config SPL_USB_SDP_SUPPORT
1090 bool "Support SDP (Serial Download Protocol)"
1092 Enable Serial Download Protocol (SDP) device support in SPL. This
1093 allows to download images into memory and execute (jump to) them
1094 using the same protocol as implemented by the i.MX family's boot ROM.
1097 config SPL_WATCHDOG_SUPPORT
1098 bool "Support watchdog drivers"
1099 imply SPL_WDT if !HW_WATCHDOG
1101 Enable support for watchdog drivers in SPL. A watchdog is
1102 typically a hardware peripheral which can reset the system when it
1103 detects no activity for a while (such as a software crash). This
1104 enables the drivers in drivers/watchdog as part of an SPL build.
1106 config SPL_YMODEM_SUPPORT
1107 bool "Support loading using Ymodem"
1108 depends on SPL_SERIAL_SUPPORT
1110 While loading from serial is slow it can be a useful backup when
1111 there is no other option. The Ymodem protocol provides a reliable
1112 means of transmitting U-Boot over a serial line for using in SPL,
1113 with a checksum to ensure correctness.
1116 bool "Support ARM Trusted Firmware"
1119 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1120 is loaded by SPL (which is considered as BL2 in ATF terminology).
1121 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1123 config SPL_ATF_NO_PLATFORM_PARAM
1124 bool "Pass no platform parameter"
1127 While we expect to call a pointer to a valid FDT (or NULL)
1128 as the platform parameter to an ATF, some ATF versions are
1129 not U-Boot aware and have an insufficiently robust parameter
1130 validation to gracefully reject a FDT being passed.
1132 If this option is enabled, the spl_atf os-type handler will
1133 always pass NULL for the platform parameter.
1135 If your ATF is affected, say Y.
1137 config SPL_AM33XX_ENABLE_RTC32K_OSC
1138 bool "Enable the RTC32K OSC on AM33xx based platforms"
1141 Enable access to the AM33xx RTC and select the external 32kHz clock
1145 bool "Support OP-TEE Trusted OS"
1148 OP-TEE is an open source Trusted OS which is loaded by SPL.
1149 More detail at: https://github.com/OP-TEE/optee_os
1153 depends on SUPPORT_TPL
1156 If you want to build TPL as well as the normal image and SPL, say Y.
1161 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1165 This option enables TPL to write handoff information. This can be
1166 used to pass information like the size of SDRAM from TPL to U-Boot
1167 proper. The information is also available to SPL if it is useful
1170 config TPL_BOARD_INIT
1171 bool "Call board-specific initialization in TPL"
1173 If this option is enabled, U-Boot will call the function
1174 spl_board_init() from board_init_r(). This function should be
1175 provided by the board.
1178 string "Linker script for the TPL stage"
1180 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1181 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
1183 The TPL stage will usually require a different linker-script
1184 (as it runs from a different memory region) than the regular
1185 U-Boot stage. Set this to the path of the linker-script to
1188 May be left empty to trigger the Makefile infrastructure to
1189 fall back to the linker-script used for the SPL stage.
1191 config TPL_NEEDS_SEPARATE_TEXT_BASE
1192 bool "TPL needs a separate text-base"
1196 Enable, if the TPL stage should not inherit its text-base
1197 from the SPL stage. When enabled, a base address for the
1198 .text sections of the TPL stage has to be set below.
1200 config TPL_NEEDS_SEPARATE_STACK
1201 bool "TPL needs a separate initial stack-pointer"
1205 Enable, if the TPL stage should not inherit its initial
1206 stack-pointer from the settings for the SPL stage.
1208 config TPL_TEXT_BASE
1209 hex "Base address for the .text section of the TPL stage"
1210 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1212 The base address for the .text section of the TPL stage.
1215 int "Maximum size (in bytes) for the TPL stage"
1219 The maximum size (in bytes) of the TPL stage.
1222 hex "Address of the initial stack-pointer for the TPL stage"
1223 depends on TPL_NEEDS_SEPARATE_STACK
1225 The address of the initial stack-pointer for the TPL stage.
1226 Usually this will be the (aligned) top-of-stack.
1228 config TPL_BOOTROM_SUPPORT
1229 bool "Support returning to the BOOTROM (from TPL)"
1231 Some platforms (e.g. the Rockchip RK3368) provide support in their
1232 ROM for loading the next boot-stage after performing basic setup
1235 Enable this option, to return to the BOOTROM through the
1236 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1237 boot device list, if not implemented for a given board)
1239 config TPL_DRIVERS_MISC_SUPPORT
1240 bool "Support misc drivers in TPL"
1242 Enable miscellaneous drivers in TPL. These drivers perform various
1243 tasks that don't fall nicely into other categories, Enable this
1244 option to build the drivers in drivers/misc as part of an TPL
1245 build, for those that support building in TPL (not all drivers do).
1247 config TPL_ENV_SUPPORT
1248 bool "Support an environment"
1250 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1252 config TPL_GPIO_SUPPORT
1253 bool "Support GPIO in TPL"
1255 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1256 GPIOs allow U-Boot to read the state of an input line (high or
1257 low) and set the state of an output line. This can be used to
1258 drive LEDs, control power to various system parts and read user
1259 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1260 for example. Enable this option to build the drivers in
1261 drivers/gpio as part of an TPL build.
1263 config TPL_I2C_SUPPORT
1266 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1269 config TPL_LIBCOMMON_SUPPORT
1270 bool "Support common libraries"
1272 Enable support for common U-Boot libraries within TPL. See
1273 SPL_LIBCOMMON_SUPPORT for details.
1275 config TPL_LIBGENERIC_SUPPORT
1276 bool "Support generic libraries"
1278 Enable support for generic U-Boot libraries within TPL. See
1279 SPL_LIBGENERIC_SUPPORT for details.
1281 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1282 bool "Support MPC8XXX DDR init"
1284 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1285 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1287 config TPL_MMC_SUPPORT
1291 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1293 config TPL_NAND_SUPPORT
1294 bool "Support NAND flash"
1296 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1299 bool "Support PCI drivers"
1301 Enable support for PCI in TPL. For platforms that need PCI to boot,
1302 or must perform some init using PCI in SPL, this provides the
1303 necessary driver support. This enables the drivers in drivers/pci
1304 as part of a TPL build.
1306 config TPL_PCH_SUPPORT
1307 bool "Support PCH drivers"
1309 Enable support for PCH (Platform Controller Hub) devices in TPL.
1310 These are used to set up GPIOs and the SPI peripheral early in
1311 boot. This enables the drivers in drivers/pch as part of a TPL
1314 config TPL_RAM_SUPPORT
1315 bool "Support booting from RAM"
1317 Enable booting of an image in RAM. The image can be preloaded or
1318 it can be loaded by TPL directly into RAM (e.g. using USB).
1320 config TPL_RAM_DEVICE
1321 bool "Support booting from preloaded image in RAM"
1322 depends on TPL_RAM_SUPPORT
1324 Enable booting of an image already loaded in RAM. The image has to
1325 be already in memory when TPL takes over, e.g. loaded by the boot
1328 config TPL_RTC_SUPPORT
1329 bool "Support RTC drivers"
1331 Enable RTC (Real-time Clock) support in TPL. This includes support
1332 for reading and setting the time. Some RTC devices also have some
1333 non-volatile (battery-backed) memory which is accessible if
1334 needed. This enables the drivers in drivers/rtc as part of an TPL
1337 config TPL_SERIAL_SUPPORT
1338 bool "Support serial"
1342 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1345 config TPL_SPI_FLASH_SUPPORT
1346 bool "Support SPI flash drivers"
1348 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1352 bool "Support loading from SPI flash"
1353 depends on TPL_SPI_FLASH_SUPPORT
1355 Enable support for loading next stage, U-Boot or otherwise, from
1356 SPI NOR in U-Boot TPL.
1358 config TPL_SPI_SUPPORT
1359 bool "Support SPI drivers"
1361 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1364 config TPL_YMODEM_SUPPORT
1365 bool "Support loading using Ymodem"
1366 depends on TPL_SERIAL_SUPPORT
1368 While loading from serial is slow it can be a useful backup when
1369 there is no other option. The Ymodem protocol provides a reliable
1370 means of transmitting U-Boot over a serial line for using in TPL,
1371 with a checksum to ensure correctness.
1375 config SPL_AT91_MCK_BYPASS
1376 bool "Use external clock signal as a source of main clock for AT91 platforms"
1377 depends on ARCH_AT91
1380 Use external 8 to 24 Mhz clock signal as source of main clock instead
1381 of an external crystal oscillator.
1382 This option disables the internal driving on the XOUT pin.
1383 The external source has to provide a stable clock on the XIN pin.
1384 If this option is disabled, the SoC expects a crystal oscillator
1385 that needs driving on both XIN and XOUT lines.