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 menu "PowerPC SPL Boot options"
66 depends on PPC && (SUPPORT_SPL && !SPL_FRAMEWORK)
69 bool "Load SPL from NAND flash"
72 bool "Load SPL from SD Card / eMMC"
75 bool "Load SPL from SPI flash"
78 bool "Create SPL in Freescale PBI format"
80 Create boot binary having SPL binary in PBI format concatenated with
86 bool "Pass hand-off information from SPL to U-Boot proper"
89 It is useful to be able to pass information from SPL to U-Boot
90 proper to preserve state that is known in SPL and is needed in U-Boot.
91 Enable this to locate the handoff information in U-Boot proper, early
92 in boot. It is available in gd->handoff. The state state is set up
93 in SPL (or TPL if that is being used).
98 bool "Pass hand-off information from SPL to U-Boot proper"
102 This option enables SPL to write handoff information. This can be
103 used to pass information like the size of SDRAM from SPL to U-Boot
104 proper. Also SPL can receive information from TPL in the same place
108 string "Linker script for the SPL stage"
109 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
111 The SPL stage will usually require a different linker-script
112 (as it runs from a different memory region) than the regular
113 U-Boot stage. Set this to the path of the linker-script to
118 default ISW_ENTRY_ADDR if AM43XX || AM33XX || OMAP54XX || ARCH_KEYSTONE
121 The address in memory that SPL will be running from.
123 config SPL_BOARD_INIT
124 bool "Call board-specific initialization in SPL"
126 If this option is enabled, U-Boot will call the function
127 spl_board_init() from board_init_r(). This function should be
128 provided by the board.
130 config SPL_BOOTROM_SUPPORT
131 bool "Support returning to the BOOTROM"
133 Some platforms (e.g. the Rockchip RK3368) provide support in their
134 ROM for loading the next boot-stage after performing basic setup
137 Enable this option, to return to the BOOTROM through the
138 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
139 boot device list, if not implemented for a given board)
141 config SPL_BOOTCOUNT_LIMIT
142 bool "Support bootcount in SPL"
143 depends on SPL_ENV_SUPPORT
145 On some boards, which use 'falcon' mode, it is necessary to check
146 and increment the number of boot attempts. Such boards do not
147 use proper U-Boot for normal boot flow and hence needs those
148 adjustments to be done in the SPL.
150 config SPL_RAW_IMAGE_SUPPORT
151 bool "Support SPL loading and booting of RAW images"
152 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
153 default y if !TI_SECURE_DEVICE
155 SPL will support loading and booting a RAW image when this option
156 is y. If this is not set, SPL will move on to other available
157 boot media to find a suitable image.
159 config SPL_LEGACY_IMAGE_SUPPORT
160 bool "Support SPL loading and booting of Legacy images"
161 default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
163 SPL will support loading and booting Legacy images when this option
164 is y. If this is not set, SPL will move on to other available
165 boot media to find a suitable image.
167 config SPL_LEGACY_IMAGE_CRC_CHECK
168 bool "Check CRC of Legacy images"
169 depends on SPL_LEGACY_IMAGE_SUPPORT
170 select SPL_CRC32_SUPPORT
172 Enable this to check the CRC of Legacy images. While this increases
173 reliability, it affects both code size and boot duration.
174 If disabled, Legacy images are booted if the image magic and size
175 are correct, without further integrity checks.
177 config SPL_SYS_MALLOC_SIMPLE
179 prompt "Only use malloc_simple functions in the SPL"
181 Say Y here to only use the *_simple malloc functions from
182 malloc_simple.c, rather then using the versions from dlmalloc.c;
183 this will make the SPL binary smaller at the cost of more heap
184 usage as the *_simple malloc functions do not re-use free-ed mem.
186 config TPL_SYS_MALLOC_SIMPLE
188 prompt "Only use malloc_simple functions in the TPL"
190 Say Y here to only use the *_simple malloc functions from
191 malloc_simple.c, rather then using the versions from dlmalloc.c;
192 this will make the TPL binary smaller at the cost of more heap
193 usage as the *_simple malloc functions do not re-use free-ed mem.
196 bool "Enable SDRAM location for SPL stack"
198 SPL starts off execution in SRAM and thus typically has only a small
199 stack available. Since SPL sets up DRAM while in its board_init_f()
200 function, it is possible for the stack to move there before
201 board_init_r() is reached. This option enables a special SDRAM
202 location for the SPL stack. U-Boot SPL switches to this after
203 board_init_f() completes, and before board_init_r() starts.
205 config SPL_STACK_R_ADDR
206 depends on SPL_STACK_R
207 hex "SDRAM location for SPL stack"
208 default 0x82000000 if ARCH_OMAP2PLUS
210 Specify the address in SDRAM for the SPL stack. This will be set up
211 before board_init_r() is called.
213 config SPL_STACK_R_MALLOC_SIMPLE_LEN
214 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
215 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
218 Specify the amount of the stack to use as memory pool for
219 malloc_simple after switching the stack to DRAM. This may be set
220 to give board_init_r() a larger heap then the initial heap in
221 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
223 config SPL_SEPARATE_BSS
224 bool "BSS section is in a different memory region from text"
226 Some platforms need a large BSS region in SPL and can provide this
227 because RAM is already set up. In this case BSS can be moved to RAM.
228 This option should then be enabled so that the correct device tree
229 location is used. Normally we put the device tree at the end of BSS
230 but with this option enabled, it goes at _image_binary_end.
232 config SPL_BANNER_PRINT
233 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
236 If this option is enabled, SPL will print the banner with version
237 info. Disabling this option could be useful to reduce TPL boot time
238 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
240 config TPL_BANNER_PRINT
241 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
244 If this option is enabled, SPL will not print the banner with version
245 info. Disabling this option could be useful to reduce SPL boot time
246 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
248 config SPL_DISPLAY_PRINT
249 bool "Display a board-specific message in SPL"
251 If this option is enabled, U-Boot will call the function
252 spl_display_print() immediately after displaying the SPL console
253 banner ("U-Boot SPL ..."). This function should be provided by
256 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
257 bool "MMC raw mode: by sector"
258 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
259 ARCH_MX6 || ARCH_MX7 || \
260 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
261 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
262 OMAP44XX || OMAP54XX || AM33XX || AM43XX
264 Use sector number for specifying U-Boot location on MMC/SD in
267 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
268 hex "Address on the MMC to load U-Boot from"
269 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
270 default 0x50 if ARCH_SUNXI
271 default 0x75 if ARCH_DAVINCI
272 default 0x8a if ARCH_MX6 || ARCH_MX7
273 default 0x100 if ARCH_UNIPHIER
274 default 0x140 if ARCH_MVEBU
275 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
276 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
277 OMAP54XX || AM33XX || AM43XX || ARCH_K3
278 default 0x4000 if ARCH_ROCKCHIP
280 Address on the MMC to load U-Boot from, when the MMC is being used
281 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
283 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
284 bool "MMC Raw mode: by partition"
286 Use a partition for loading U-Boot when using MMC/SD in raw mode.
288 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
289 hex "Partition to use to load U-Boot from"
290 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
293 Partition on the MMC to load U-Boot from when the MMC is being
296 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
297 bool "MMC raw mode: by partition type"
298 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
300 Use partition type for specifying U-Boot partition on MMC/SD in
301 raw mode. U-Boot will be loaded from the first partition of this
304 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
305 hex "Partition Type on the MMC to load U-Boot from"
306 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
308 Partition Type on the MMC to load U-Boot from, when the MMC is being
311 config SPL_CRC32_SUPPORT
313 default y if SPL_LEGACY_IMAGE_SUPPORT
315 Enable this to support CRC32 in uImages or FIT images within SPL.
316 This is a 32-bit checksum value that can be used to verify images.
317 For FIT images, this is the least secure type of checksum, suitable
318 for detected accidental image corruption. For secure applications you
319 should consider SHA1 or SHA256.
321 config SPL_MD5_SUPPORT
325 Enable this to support MD5 in FIT images within SPL. An MD5
326 checksum is a 128-bit hash value used to check that the image
327 contents have not been corrupted. Note that MD5 is not considered
328 secure as it is possible (with a brute-force attack) to adjust the
329 image while still retaining the same MD5 hash value. For secure
330 applications where images may be changed maliciously, you should
331 consider SHA1 or SHA256.
333 config SPL_SHA1_SUPPORT
338 Enable this to support SHA1 in FIT images within SPL. A SHA1
339 checksum is a 160-bit (20-byte) hash value used to check that the
340 image contents have not been corrupted or maliciously altered.
341 While SHA1 is fairly secure it is coming to the end of its life
342 due to the expanding computing power available to brute-force
343 attacks. For more security, consider SHA256.
345 config SPL_SHA256_SUPPORT
346 bool "Support SHA256"
350 Enable this to support SHA256 in FIT images within SPL. A SHA256
351 checksum is a 256-bit (32-byte) hash value used to check that the
352 image contents have not been corrupted. SHA256 is recommended for
353 use in secure applications since (as at 2016) there is no known
354 feasible attack that could produce a 'collision' with differing
355 input data. Use this for the highest security. Note that only the
356 SHA256 variant is supported: SHA512 and others are not currently
359 config SPL_FIT_IMAGE_TINY
360 bool "Remove functionality from SPL FIT loading to reduce size"
362 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
363 default y if ARCH_IMX8M
365 Enable this to reduce the size of the FIT image loading code
366 in SPL, if space for the SPL binary is very tight.
368 This removes the detection of image types (which forces the
369 first image to be treated as having a U-Boot style calling
370 convention) and skips the recording of each loaded payload
371 (i.e. loadable) into the FDT (modifying the loaded FDT to
372 ensure this information is available to the next image
375 config SPL_CPU_SUPPORT
376 bool "Support CPU drivers"
378 Enable this to support CPU drivers in SPL. These drivers can set
379 up CPUs and provide information about them such as the model and
380 name. This can be useful in SPL since setting up the CPUs earlier
381 may improve boot performance. Enable this option to build the
382 drivers in drivers/cpu as part of an SPL build.
384 config SPL_CRYPTO_SUPPORT
385 bool "Support crypto drivers"
387 Enable crypto drivers in SPL. These drivers can be used to
388 accelerate secure boot processing in secure applications. Enable
389 this option to build the drivers in drivers/crypto as part of an
392 config SPL_HASH_SUPPORT
393 bool "Support hashing drivers"
397 Enable hashing drivers in SPL. These drivers can be used to
398 accelerate secure boot processing in secure applications. Enable
399 this option to build system-specific drivers for hash acceleration
400 as part of an SPL build.
402 config TPL_HASH_SUPPORT
403 bool "Support hashing drivers in TPL"
407 Enable hashing drivers in SPL. These drivers can be used to
408 accelerate secure boot processing in secure applications. Enable
409 this option to build system-specific drivers for hash acceleration
410 as part of an SPL build.
412 config SPL_DMA_SUPPORT
413 bool "Support DMA drivers"
415 Enable DMA (direct-memory-access) drivers in SPL. These drivers
416 can be used to handle memory-to-peripheral data transfer without
417 the CPU moving the data. Enable this option to build the drivers
418 in drivers/dma as part of an SPL build.
420 config SPL_DRIVERS_MISC_SUPPORT
421 bool "Support misc drivers"
423 Enable miscellaneous drivers in SPL. These drivers perform various
424 tasks that don't fall nicely into other categories, Enable this
425 option to build the drivers in drivers/misc as part of an SPL
426 build, for those that support building in SPL (not all drivers do).
428 config SPL_ENV_SUPPORT
429 bool "Support an environment"
431 Enable environment support in SPL. The U-Boot environment provides
432 a number of settings (essentially name/value pairs) which can
433 control many aspects of U-Boot's operation. Normally this is not
434 needed in SPL as it has a much simpler task with less
435 configuration. But some boards use this to support 'Falcon' boot
436 on EXT2 and FAT, where SPL boots directly into Linux without
437 starting U-Boot first. Enabling this option will make env_get()
438 and env_set() available in SPL.
441 bool "Support save environment"
442 depends on SPL_ENV_SUPPORT
443 select SPL_MMC_WRITE if ENV_IS_IN_MMC
445 Enable save environment support in SPL after setenv. By default
446 the saveenv option is not provided in SPL, but some boards need
447 this support in 'Falcon' boot, where SPL need to boot from
448 different images based on environment variable set by OS. For
449 example OS may set "reboot_image" environment variable to
450 "recovery" inorder to boot recovery image by SPL. The SPL read
451 "reboot_image" and act accordingly and change the reboot_image
452 to default mode using setenv and save the environment.
454 config SPL_ETH_SUPPORT
455 bool "Support Ethernet"
456 depends on SPL_ENV_SUPPORT
458 Enable access to the network subsystem and associated Ethernet
459 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
460 link rather than from an on-board peripheral. Environment support
461 is required since the network stack uses a number of environment
462 variables. See also SPL_NET_SUPPORT.
465 bool "Support EXT filesystems"
467 Enable support for EXT2/3/4 filesystems with SPL. This permits
468 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
469 filesystem from within SPL. Support for the underlying block
470 device (e.g. MMC or USB) must be enabled separately.
473 bool "Support FAT filesystems"
476 Enable support for FAT and VFAT filesystems with SPL. This
477 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
478 filesystem from within SPL. Support for the underlying block
479 device (e.g. MMC or USB) must be enabled separately.
482 bool "Support write for FAT filesystems"
484 Enable write support for FAT and VFAT filesystems with SPL.
485 Support for the underlying block device (e.g. MMC or USB) must be
488 config SPL_FPGA_SUPPORT
491 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
492 provide software-configurable hardware which is typically used to
493 implement peripherals (such as UARTs, LCD displays, MMC) or
494 accelerate custom processing functions, such as image processing
495 or machine learning. Sometimes it is useful to program the FPGA
496 as early as possible during boot, and this option can enable that
499 config SPL_GPIO_SUPPORT
500 bool "Support GPIO in SPL"
502 Enable support for GPIOs (General-purpose Input/Output) in SPL.
503 GPIOs allow U-Boot to read the state of an input line (high or
504 low) and set the state of an output line. This can be used to
505 drive LEDs, control power to various system parts and read user
506 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
507 for example. Enable this option to build the drivers in
508 drivers/gpio as part of an SPL build.
510 config SPL_I2C_SUPPORT
513 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
514 I2C works with a clock and data line which can be driven by a
515 one or more masters or slaves. It is a fairly complex bus but is
516 widely used as it only needs two lines for communication. Speeds of
517 400kbps are typical but up to 3.4Mbps is supported by some
518 hardware. I2C can be useful in SPL to configure power management
519 ICs (PMICs) before raising the CPU clock speed, for example.
520 Enable this option to build the drivers in drivers/i2c as part of
523 config SPL_LIBCOMMON_SUPPORT
524 bool "Support common libraries"
526 Enable support for common U-Boot libraries within SPL. These
527 libraries include common code to deal with U-Boot images,
528 environment and USB, for example. This option is enabled on many
529 boards. Enable this option to build the code in common/ as part of
532 config SPL_LIBDISK_SUPPORT
533 bool "Support disk partitions"
536 Enable support for disk partitions within SPL. 'Disk' is something
537 of a misnomer as it includes non-spinning media such as flash (as
538 used in MMC and USB sticks). Partitions provide a way for a disk
539 to be split up into separate regions, with a partition table placed
540 at the start or end which describes the location and size of each
541 'partition'. These partitions are typically uses as individual block
542 devices, typically with an EXT2 or FAT filesystem in each. This
543 option enables whatever partition support has been enabled in
544 U-Boot to also be used in SPL. It brings in the code in disk/.
546 config SPL_LIBGENERIC_SUPPORT
547 bool "Support generic libraries"
549 Enable support for generic U-Boot libraries within SPL. These
550 libraries include generic code to deal with device tree, hashing,
551 printf(), compression and the like. This option is enabled on many
552 boards. Enable this option to build the code in lib/ as part of an
555 config SPL_DM_MAILBOX
556 bool "Support Mailbox"
558 Enable support for Mailbox within SPL. This enable the inter
559 processor communication protocols tobe used within SPL. Enable
560 this option to build the drivers in drivers/mailbox as part of
563 config SPL_MMC_SUPPORT
566 select HAVE_BLOCK_DEVICE
568 Enable support for MMC (Multimedia Card) within SPL. This enables
569 the MMC protocol implementation and allows any enabled drivers to
570 be used within SPL. MMC can be used with or without disk partition
571 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
572 this option to build the drivers in drivers/mmc as part of an SPL
576 bool "Tiny MMC framework in SPL"
577 depends on SPL_MMC_SUPPORT
580 Enable MMC framework tinification support. This option is useful if
581 if your SPL is extremely size constrained. Heed the warning, enable
582 this option if and only if you know exactly what you are doing, if
583 you are reading this help text, you most likely have no idea :-)
585 The MMC framework is reduced to bare minimum to be useful. No malloc
586 support is needed for the MMC framework operation with this option
587 enabled. The framework supports exactly one MMC device and exactly
588 one MMC driver. The MMC driver can be adjusted to avoid any malloc
589 operations too, which can remove the need for malloc support in SPL
590 and thus further reduce footprint.
593 bool "MMC/SD/SDIO card support for write operations in SPL"
594 depends on SPL_MMC_SUPPORT
597 Enable write access to MMC and SD Cards in SPL
600 config SPL_MPC8XXX_INIT_DDR_SUPPORT
601 bool "Support MPC8XXX DDR init"
603 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
604 random-access memory) on the MPC8XXX family within SPL. This
605 allows DRAM to be set up before loading U-Boot into that DRAM,
608 config SPL_MTD_SUPPORT
609 bool "Support MTD drivers"
611 Enable support for MTD (Memory Technology Device) within SPL. MTD
612 provides a block interface over raw NAND and can also be used with
613 SPI flash. This allows SPL to load U-Boot from supported MTD
614 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
615 to enable specific MTD drivers.
617 config SPL_MUSB_NEW_SUPPORT
618 bool "Support new Mentor Graphics USB"
620 Enable support for Mentor Graphics USB in SPL. This is a new
621 driver used by some boards. Enable this option to build
622 the drivers in drivers/usb/musb-new as part of an SPL build. The
623 old drivers are in drivers/usb/musb.
625 config SPL_NAND_SUPPORT
626 bool "Support NAND flash"
628 Enable support for NAND (Negative AND) flash in SPL. NAND flash
629 can be used to allow SPL to load U-Boot from supported devices.
630 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
636 Enable support for loading payloads from UBI. See
637 README.ubispl for more info.
640 config SPL_UBI_LOAD_BY_VOLNAME
641 bool "Support loading volumes by name"
643 This enables support for loading UBI volumes by name. When this
644 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
645 configure the volume name from which to load U-Boot.
647 config SPL_UBI_MAX_VOL_LEBS
648 int "Maximum number of LEBs per volume"
651 The maximum number of logical eraseblocks which a static volume
652 to load can contain. Used for sizing the scan data structure.
654 config SPL_UBI_MAX_PEB_SIZE
655 int "Maximum PEB size"
658 The maximum physical erase block size.
660 config SPL_UBI_MAX_PEBS
661 int "Maximum number of PEBs"
664 The maximum physical erase block size. If not overridden by
665 board code, this value will be used as the actual number of PEBs.
667 config SPL_UBI_PEB_OFFSET
668 int "Offset to first UBI PEB"
671 The offset in number of PEBs from the start of flash to the first
672 PEB part of the UBI image.
674 config SPL_UBI_VID_OFFSET
675 int "Offset to VID header"
678 config SPL_UBI_LEB_START
679 int "Offset to LEB in PEB"
682 The offset in bytes to the LEB within a PEB.
684 config SPL_UBI_INFO_ADDR
685 hex "Address to place UBI scan info"
688 Address for ubispl to place the scan info. Read README.ubispl to
689 determine the required size
691 config SPL_UBI_VOL_IDS
692 int "Maximum volume id"
695 The maximum volume id which can be loaded. Used for sizing the
698 config SPL_UBI_LOAD_MONITOR_ID
699 int "id of U-Boot volume"
702 The UBI volume id from which to load U-Boot
704 config SPL_UBI_LOAD_MONITOR_VOLNAME
705 string "volume name of U-Boot volume"
706 depends on SPL_UBI_LOAD_BY_VOLNAME
708 The UBI volume name from which to load U-Boot
710 config SPL_UBI_LOAD_KERNEL_ID
711 int "id of kernel volume"
712 depends on SPL_OS_BOOT && SPL_UBI
714 The UBI volume id from which to load the kernel
716 config SPL_UBI_LOAD_ARGS_ID
717 int "id of kernel args volume"
718 depends on SPL_OS_BOOT && SPL_UBI
720 The UBI volume id from which to load the device tree
722 config UBI_SPL_SILENCE_MSG
723 bool "silence UBI SPL messages"
726 Disable messages from UBI SPL. This leaves warnings
731 config SPL_NET_SUPPORT
732 bool "Support networking"
734 Enable support for network devices (such as Ethernet) in SPL.
735 This permits SPL to load U-Boot over a network link rather than
736 from an on-board peripheral. Environment support is required since
737 the network stack uses a number of environment variables. See also
741 config SPL_NET_VCI_STRING
742 string "BOOTP Vendor Class Identifier string sent by SPL"
744 As defined by RFC 2132 the vendor class identifier field can be
745 sent by the client to identify the vendor type and configuration
746 of a client. This is often used in practice to allow for the DHCP
747 server to specify different files to load depending on if the ROM,
748 SPL or U-Boot itself makes the request
749 endif # if SPL_NET_SUPPORT
751 config SPL_NO_CPU_SUPPORT
752 bool "Drop CPU code in SPL"
754 This is specific to the ARM926EJ-S CPU. It disables the standard
755 start.S start-up code, presumably so that a replacement can be
756 used on that CPU. You should not enable it unless you know what
759 config SPL_NOR_SUPPORT
760 bool "Support NOR flash"
762 Enable support for loading U-Boot from memory-mapped NOR (Negative
763 OR) flash in SPL. NOR flash is slow to write but fast to read, and
764 a memory-mapped device makes it very easy to access. Loading from
765 NOR is typically achieved with just a memcpy().
767 config SPL_XIP_SUPPORT
771 Enable support for execute in place of U-Boot or kernel image. There
772 is no need to copy image from flash to ram if flash supports execute
773 in place. Its very useful in systems having enough flash but not
774 enough ram to load the image.
776 config SPL_ONENAND_SUPPORT
777 bool "Support OneNAND flash"
779 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
780 a type of NAND flash and therefore can be used to allow SPL to
781 load U-Boot from supported devices. This enables the drivers in
782 drivers/mtd/onenand as part of an SPL build.
785 bool "Activate Falcon Mode"
786 depends on !TI_SECURE_DEVICE
789 Enable booting directly to an OS from SPL.
790 for more info read doc/README.falcon
794 hex "addr, where OS is found"
795 depends on SPL_NOR_SUPPORT
797 Specify the address, where the OS image is found, which
804 default "tpl/u-boot-with-tpl.bin" if TPL
807 Payload for SPL boot. For backward compatibility, default to
808 u-boot.bin, i.e. RAW image without any header. In case of
809 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
813 bool "Support PCI drivers"
815 Enable support for PCI in SPL. For platforms that need PCI to boot,
816 or must perform some init using PCI in SPL, this provides the
817 necessary driver support. This enables the drivers in drivers/pci
818 as part of an SPL build.
820 config SPL_PCH_SUPPORT
821 bool "Support PCH drivers"
823 Enable support for PCH (Platform Controller Hub) devices in SPL.
824 These are used to set up GPIOs and the SPI peripheral early in
825 boot. This enables the drivers in drivers/pch as part of an SPL
828 config SPL_POST_MEM_SUPPORT
829 bool "Support POST drivers"
831 Enable support for POST (Power-on Self Test) in SPL. POST is a
832 procedure that checks that the hardware (CPU or board) appears to
833 be functionally correctly. It is a sanity check that can be
834 performed before booting. This enables the drivers in post/drivers
835 as part of an SPL build.
838 bool "Support reset drivers"
841 Enable support for reset control in SPL.
842 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
843 by using the generic reset API provided by driver model.
844 This enables the drivers in drivers/reset as part of an SPL build.
846 config SPL_POWER_SUPPORT
847 bool "Support power drivers"
849 Enable support for power control in SPL. This includes support
850 for PMICs (Power-management Integrated Circuits) and some of the
851 features provided by PMICs. In particular, voltage regulators can
852 be used to enable/disable power and vary its voltage. That can be
853 useful in SPL to turn on boot peripherals and adjust CPU voltage
854 so that the clock speed can be increased. This enables the drivers
855 in drivers/power, drivers/power/pmic and drivers/power/regulator
856 as part of an SPL build.
858 config SPL_POWER_DOMAIN
859 bool "Support power domain drivers"
861 Enable support for power domain control in SPL. Many SoCs allow
862 power to be applied to or removed from portions of the SoC (power
863 domains). This may be used to save power. This API provides the
864 means to control such power management hardware. This enables
865 the drivers in drivers/power/domain as part of a SPL build.
867 config SPL_RAM_SUPPORT
868 bool "Support booting from RAM"
869 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
871 Enable booting of an image in RAM. The image can be preloaded or
872 it can be loaded by SPL directly into RAM (e.g. using USB).
874 config SPL_RAM_DEVICE
875 bool "Support booting from preloaded image in RAM"
876 depends on SPL_RAM_SUPPORT
877 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
879 Enable booting of an image already loaded in RAM. The image has to
880 be already in memory when SPL takes over, e.g. loaded by the boot
883 config SPL_REMOTEPROC
884 bool "Support REMOTEPROCS"
886 Enable support for REMOTEPROCs in SPL. This permits to load
887 a remote processor firmware in SPL.
889 config SPL_RTC_SUPPORT
890 bool "Support RTC drivers"
892 Enable RTC (Real-time Clock) support in SPL. This includes support
893 for reading and setting the time. Some RTC devices also have some
894 non-volatile (battery-backed) memory which is accessible if
895 needed. This enables the drivers in drivers/rtc as part of an SPL
898 config SPL_SATA_SUPPORT
899 bool "Support loading from SATA"
901 Enable support for SATA (Serial AT attachment) in SPL. This allows
902 use of SATA devices such as hard drives and flash drivers for
903 loading U-Boot. SATA is used in higher-end embedded systems and
904 can provide higher performance than MMC , at somewhat higher
905 expense and power consumption. This enables loading from SATA
906 using a configured device.
908 config SPL_SERIAL_SUPPORT
909 bool "Support serial"
913 Enable support for serial in SPL. This allows use of a serial UART
914 for displaying messages while SPL is running. It also brings in
915 printf() and panic() functions. This should normally be enabled
916 unless there are space reasons not to. Even then, consider
917 enabling USE_TINY_PRINTF which is a small printf() version.
919 config SPL_SPI_FLASH_SUPPORT
920 bool "Support SPI flash drivers"
922 Enable support for using SPI flash in SPL, and loading U-Boot from
923 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
924 the SPI bus that is used to connect it to a system. It is a simple
925 but fast bidirectional 4-wire bus (clock, chip select and two data
926 lines). This enables the drivers in drivers/mtd/spi as part of an
927 SPL build. This normally requires SPL_SPI_SUPPORT.
929 if SPL_SPI_FLASH_SUPPORT
931 config SPL_SPI_FLASH_TINY
932 bool "Enable low footprint SPL SPI Flash support"
933 depends on !SPI_FLASH_BAR
934 default y if SPI_FLASH
936 Enable lightweight SPL SPI Flash support that supports just reading
937 data/images from flash. No support to write/erase flash. Enable
938 this if you have SPL size limitations and don't need full
939 fledged SPI flash support.
941 config SPL_SPI_FLASH_SFDP_SUPPORT
942 bool "SFDP table parsing support for SPI NOR flashes"
943 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
945 Enable support for parsing and auto discovery of parameters for
946 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
947 tables as per JESD216 standard in SPL.
950 bool "Support loading from SPI flash"
952 Enable support for loading next stage, U-Boot or otherwise, from
953 SPI NOR in U-Boot SPL.
955 endif # SPL_SPI_FLASH_SUPPORT
957 config SPL_SPI_SUPPORT
958 bool "Support SPI drivers"
960 Enable support for using SPI in SPL. This is used for connecting
961 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
962 more details on that. The SPI driver provides the transport for
963 data between the SPI flash and the CPU. This option can be used to
964 enable SPI drivers that are needed for other purposes also, such
968 bool "Driver support for thermal devices"
970 Enable support for temperature-sensing devices. Some SoCs have on-chip
971 temperature sensors to permit warnings, speed throttling or even
972 automatic power-off when the temperature gets too high or low. Other
973 devices may be discrete but connected on a suitable bus.
975 config SPL_USB_HOST_SUPPORT
976 bool "Support USB host drivers"
977 select HAVE_BLOCK_DEVICE
979 Enable access to USB (Universal Serial Bus) host devices so that
980 SPL can load U-Boot from a connected USB peripheral, such as a USB
981 flash stick. While USB takes a little longer to start up than most
982 buses, it is very flexible since many different types of storage
983 device can be attached. This option enables the drivers in
984 drivers/usb/host as part of an SPL build.
986 config SPL_USB_STORAGE
987 bool "Support loading from USB"
988 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
990 Enable support for USB devices in SPL. This allows use of USB
991 devices such as hard drives and flash drivers for loading U-Boot.
992 The actual drivers are enabled separately using the normal U-Boot
993 config options. This enables loading from USB using a configured
996 config SPL_USB_GADGET
997 bool "Suppport USB Gadget drivers"
999 Enable USB Gadget API which allows to enable USB device functions
1004 config SPL_USB_ETHER
1005 bool "Support USB Ethernet drivers"
1007 Enable access to the USB network subsystem and associated
1008 drivers in SPL. This permits SPL to load U-Boot over a
1009 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1010 than from an onboard peripheral. Environment support is required
1011 since the network stack uses a number of environment variables.
1012 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1015 bool "Support DFU (Device Firmware Upgrade)"
1016 select SPL_HASH_SUPPORT
1017 select SPL_DFU_NO_RESET
1018 depends on SPL_RAM_SUPPORT
1020 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1021 RAM memory device support. The ROM code will load and execute
1022 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1023 selected device partition from host-pc using dfu-utils.
1024 This feature is useful to flash the binaries to factory or bare-metal
1025 boards using USB interface.
1028 bool "DFU device selection"
1033 depends on SPL_DFU && SPL_RAM_SUPPORT
1035 select RAM/DDR memory device for loading binary images
1036 (u-boot/kernel) to the selected device partition using
1037 DFU and execute the u-boot/kernel from RAM.
1041 config SPL_USB_SDP_SUPPORT
1042 bool "Support SDP (Serial Download Protocol)"
1044 Enable Serial Download Protocol (SDP) device support in SPL. This
1045 allows to download images into memory and execute (jump to) them
1046 using the same protocol as implemented by the i.MX family's boot ROM.
1049 config SPL_WATCHDOG_SUPPORT
1050 bool "Support watchdog drivers"
1052 Enable support for watchdog drivers in SPL. A watchdog is
1053 typically a hardware peripheral which can reset the system when it
1054 detects no activity for a while (such as a software crash). This
1055 enables the drivers in drivers/watchdog as part of an SPL build.
1057 config SPL_YMODEM_SUPPORT
1058 bool "Support loading using Ymodem"
1059 depends on SPL_SERIAL_SUPPORT
1061 While loading from serial is slow it can be a useful backup when
1062 there is no other option. The Ymodem protocol provides a reliable
1063 means of transmitting U-Boot over a serial line for using in SPL,
1064 with a checksum to ensure correctness.
1067 bool "Support ARM Trusted Firmware"
1070 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1071 is loaded by SPL (which is considered as BL2 in ATF terminology).
1072 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1074 config SPL_ATF_NO_PLATFORM_PARAM
1075 bool "Pass no platform parameter"
1078 While we expect to call a pointer to a valid FDT (or NULL)
1079 as the platform parameter to an ATF, some ATF versions are
1080 not U-Boot aware and have an insufficiently robust parameter
1081 validation to gracefully reject a FDT being passed.
1083 If this option is enabled, the spl_atf os-type handler will
1084 always pass NULL for the platform parameter.
1086 If your ATF is affected, say Y.
1088 config SPL_AM33XX_ENABLE_RTC32K_OSC
1089 bool "Enable the RTC32K OSC on AM33xx based platforms"
1092 Enable access to the AM33xx RTC and select the external 32kHz clock
1096 bool "Support OP-TEE Trusted OS"
1099 OP-TEE is an open source Trusted OS which is loaded by SPL.
1100 More detail at: https://github.com/OP-TEE/optee_os
1104 depends on SUPPORT_TPL
1107 If you want to build TPL as well as the normal image and SPL, say Y.
1112 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1116 This option enables TPL to write handoff information. This can be
1117 used to pass information like the size of SDRAM from TPL to U-Boot
1118 proper. The information is also available to SPL if it is useful
1121 config TPL_BOARD_INIT
1122 bool "Call board-specific initialization in TPL"
1124 If this option is enabled, U-Boot will call the function
1125 spl_board_init() from board_init_r(). This function should be
1126 provided by the board.
1129 string "Linker script for the TPL stage"
1131 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1132 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
1134 The TPL stage will usually require a different linker-script
1135 (as it runs from a different memory region) than the regular
1136 U-Boot stage. Set this to the path of the linker-script to
1139 May be left empty to trigger the Makefile infrastructure to
1140 fall back to the linker-script used for the SPL stage.
1142 config TPL_NEEDS_SEPARATE_TEXT_BASE
1143 bool "TPL needs a separate text-base"
1147 Enable, if the TPL stage should not inherit its text-base
1148 from the SPL stage. When enabled, a base address for the
1149 .text sections of the TPL stage has to be set below.
1151 config TPL_NEEDS_SEPARATE_STACK
1152 bool "TPL needs a separate initial stack-pointer"
1156 Enable, if the TPL stage should not inherit its initial
1157 stack-pointer from the settings for the SPL stage.
1159 config TPL_TEXT_BASE
1160 hex "Base address for the .text section of the TPL stage"
1161 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1163 The base address for the .text section of the TPL stage.
1166 int "Maximum size (in bytes) for the TPL stage"
1170 The maximum size (in bytes) of the TPL stage.
1173 hex "Address of the initial stack-pointer for the TPL stage"
1174 depends on TPL_NEEDS_SEPARATE_STACK
1176 The address of the initial stack-pointer for the TPL stage.
1177 Usually this will be the (aligned) top-of-stack.
1179 config TPL_BOOTROM_SUPPORT
1180 bool "Support returning to the BOOTROM (from TPL)"
1182 Some platforms (e.g. the Rockchip RK3368) provide support in their
1183 ROM for loading the next boot-stage after performing basic setup
1186 Enable this option, to return to the BOOTROM through the
1187 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1188 boot device list, if not implemented for a given board)
1190 config TPL_DRIVERS_MISC_SUPPORT
1191 bool "Support misc drivers in TPL"
1193 Enable miscellaneous drivers in TPL. These drivers perform various
1194 tasks that don't fall nicely into other categories, Enable this
1195 option to build the drivers in drivers/misc as part of an TPL
1196 build, for those that support building in TPL (not all drivers do).
1198 config TPL_ENV_SUPPORT
1199 bool "Support an environment"
1201 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1203 config TPL_GPIO_SUPPORT
1204 bool "Support GPIO in TPL"
1206 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1207 GPIOs allow U-Boot to read the state of an input line (high or
1208 low) and set the state of an output line. This can be used to
1209 drive LEDs, control power to various system parts and read user
1210 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1211 for example. Enable this option to build the drivers in
1212 drivers/gpio as part of an TPL build.
1214 config TPL_I2C_SUPPORT
1217 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1220 config TPL_LIBCOMMON_SUPPORT
1221 bool "Support common libraries"
1223 Enable support for common U-Boot libraries within TPL. See
1224 SPL_LIBCOMMON_SUPPORT for details.
1226 config TPL_LIBGENERIC_SUPPORT
1227 bool "Support generic libraries"
1229 Enable support for generic U-Boot libraries within TPL. See
1230 SPL_LIBGENERIC_SUPPORT for details.
1232 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1233 bool "Support MPC8XXX DDR init"
1235 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1236 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1238 config TPL_MMC_SUPPORT
1242 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1244 config TPL_NAND_SUPPORT
1245 bool "Support NAND flash"
1247 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1250 bool "Support PCI drivers"
1252 Enable support for PCI in TPL. For platforms that need PCI to boot,
1253 or must perform some init using PCI in SPL, this provides the
1254 necessary driver support. This enables the drivers in drivers/pci
1255 as part of a TPL build.
1257 config TPL_PCH_SUPPORT
1258 bool "Support PCH drivers"
1260 Enable support for PCH (Platform Controller Hub) devices in TPL.
1261 These are used to set up GPIOs and the SPI peripheral early in
1262 boot. This enables the drivers in drivers/pch as part of a TPL
1265 config TPL_RAM_SUPPORT
1266 bool "Support booting from RAM"
1268 Enable booting of an image in RAM. The image can be preloaded or
1269 it can be loaded by TPL directly into RAM (e.g. using USB).
1271 config TPL_RAM_DEVICE
1272 bool "Support booting from preloaded image in RAM"
1273 depends on TPL_RAM_SUPPORT
1275 Enable booting of an image already loaded in RAM. The image has to
1276 be already in memory when TPL takes over, e.g. loaded by the boot
1279 config TPL_RTC_SUPPORT
1280 bool "Support RTC drivers"
1282 Enable RTC (Real-time Clock) support in TPL. This includes support
1283 for reading and setting the time. Some RTC devices also have some
1284 non-volatile (battery-backed) memory which is accessible if
1285 needed. This enables the drivers in drivers/rtc as part of an TPL
1288 config TPL_SERIAL_SUPPORT
1289 bool "Support serial"
1293 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1296 config TPL_SPI_FLASH_SUPPORT
1297 bool "Support SPI flash drivers"
1299 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1303 bool "Support loading from SPI flash"
1304 depends on TPL_SPI_FLASH_SUPPORT
1306 Enable support for loading next stage, U-Boot or otherwise, from
1307 SPI NOR in U-Boot TPL.
1309 config TPL_SPI_SUPPORT
1310 bool "Support SPI drivers"
1312 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1315 config TPL_YMODEM_SUPPORT
1316 bool "Support loading using Ymodem"
1317 depends on TPL_SERIAL_SUPPORT
1319 While loading from serial is slow it can be a useful backup when
1320 there is no other option. The Ymodem protocol provides a reliable
1321 means of transmitting U-Boot over a serial line for using in TPL,
1322 with a checksum to ensure correctness.
1326 config SPL_AT91_MCK_BYPASS
1327 bool "Use external clock signal as a source of main clock for AT91 platforms"
1328 depends on ARCH_AT91
1331 Use external 8 to 24 Mhz clock signal as source of main clock instead
1332 of an external crystal oscillator.
1333 This option disables the internal driving on the XOUT pin.
1334 The external source has to provide a stable clock on the XIN pin.
1335 If this option is disabled, the SoC expects a crystal oscillator
1336 that needs driving on both XIN and XOUT lines.