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
119 default 0x10060 if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN9I
120 default 0x20060 if MACH_SUN50I_H6
121 default 0x00060 if ARCH_SUNXI
124 The address in memory that SPL will be running from.
126 config SPL_BOARD_INIT
127 bool "Call board-specific initialization in SPL"
129 If this option is enabled, U-Boot will call the function
130 spl_board_init() from board_init_r(). This function should be
131 provided by the board.
133 config SPL_BOOTROM_SUPPORT
134 bool "Support returning to the BOOTROM"
136 Some platforms (e.g. the Rockchip RK3368) provide support in their
137 ROM for loading the next boot-stage after performing basic setup
140 Enable this option, to return to the BOOTROM through the
141 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
142 boot device list, if not implemented for a given board)
144 config SPL_BOOTCOUNT_LIMIT
145 bool "Support bootcount in SPL"
146 depends on SPL_ENV_SUPPORT
148 On some boards, which use 'falcon' mode, it is necessary to check
149 and increment the number of boot attempts. Such boards do not
150 use proper U-Boot for normal boot flow and hence needs those
151 adjustments to be done in the SPL.
153 config SPL_RAW_IMAGE_SUPPORT
154 bool "Support SPL loading and booting of RAW images"
155 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
156 default y if !TI_SECURE_DEVICE
158 SPL will support loading and booting a RAW image when this option
159 is y. If this is not set, SPL will move on to other available
160 boot media to find a suitable image.
162 config SPL_LEGACY_IMAGE_SUPPORT
163 bool "Support SPL loading and booting of Legacy images"
164 default y if !TI_SECURE_DEVICE && !SPL_LOAD_FIT
166 SPL will support loading and booting Legacy images when this option
167 is y. If this is not set, SPL will move on to other available
168 boot media to find a suitable image.
170 config SPL_LEGACY_IMAGE_CRC_CHECK
171 bool "Check CRC of Legacy images"
172 depends on SPL_LEGACY_IMAGE_SUPPORT
173 select SPL_CRC32_SUPPORT
175 Enable this to check the CRC of Legacy images. While this increases
176 reliability, it affects both code size and boot duration.
177 If disabled, Legacy images are booted if the image magic and size
178 are correct, without further integrity checks.
180 config SPL_SYS_MALLOC_SIMPLE
182 prompt "Only use malloc_simple functions in the SPL"
184 Say Y here to only use the *_simple malloc functions from
185 malloc_simple.c, rather then using the versions from dlmalloc.c;
186 this will make the SPL binary smaller at the cost of more heap
187 usage as the *_simple malloc functions do not re-use free-ed mem.
189 config TPL_SYS_MALLOC_SIMPLE
191 prompt "Only use malloc_simple functions in the TPL"
193 Say Y here to only use the *_simple malloc functions from
194 malloc_simple.c, rather then using the versions from dlmalloc.c;
195 this will make the TPL binary smaller at the cost of more heap
196 usage as the *_simple malloc functions do not re-use free-ed mem.
199 bool "Enable SDRAM location for SPL stack"
201 SPL starts off execution in SRAM and thus typically has only a small
202 stack available. Since SPL sets up DRAM while in its board_init_f()
203 function, it is possible for the stack to move there before
204 board_init_r() is reached. This option enables a special SDRAM
205 location for the SPL stack. U-Boot SPL switches to this after
206 board_init_f() completes, and before board_init_r() starts.
208 config SPL_STACK_R_ADDR
209 depends on SPL_STACK_R
210 hex "SDRAM location for SPL stack"
211 default 0x82000000 if ARCH_OMAP2PLUS
213 Specify the address in SDRAM for the SPL stack. This will be set up
214 before board_init_r() is called.
216 config SPL_STACK_R_MALLOC_SIMPLE_LEN
217 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
218 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
221 Specify the amount of the stack to use as memory pool for
222 malloc_simple after switching the stack to DRAM. This may be set
223 to give board_init_r() a larger heap then the initial heap in
224 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
226 config SPL_SEPARATE_BSS
227 bool "BSS section is in a different memory region from text"
229 Some platforms need a large BSS region in SPL and can provide this
230 because RAM is already set up. In this case BSS can be moved to RAM.
231 This option should then be enabled so that the correct device tree
232 location is used. Normally we put the device tree at the end of BSS
233 but with this option enabled, it goes at _image_binary_end.
235 config SPL_BANNER_PRINT
236 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
239 If this option is enabled, SPL will print the banner with version
240 info. Disabling this option could be useful to reduce TPL boot time
241 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
243 config TPL_BANNER_PRINT
244 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
247 If this option is enabled, SPL will not print the banner with version
248 info. Disabling this option could be useful to reduce SPL boot time
249 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
251 config SPL_DISPLAY_PRINT
252 bool "Display a board-specific message in SPL"
254 If this option is enabled, U-Boot will call the function
255 spl_display_print() immediately after displaying the SPL console
256 banner ("U-Boot SPL ..."). This function should be provided by
259 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
260 bool "MMC raw mode: by sector"
261 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
262 ARCH_MX6 || ARCH_MX7 || \
263 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
264 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
265 OMAP44XX || OMAP54XX || AM33XX || AM43XX
267 Use sector number for specifying U-Boot location on MMC/SD in
270 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
271 hex "Address on the MMC to load U-Boot from"
272 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
273 default 0x50 if ARCH_SUNXI
274 default 0x75 if ARCH_DAVINCI
275 default 0x8a if ARCH_MX6 || ARCH_MX7
276 default 0x100 if ARCH_UNIPHIER
277 default 0x140 if ARCH_MVEBU
278 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
279 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
280 OMAP54XX || AM33XX || AM43XX || ARCH_K3
281 default 0x4000 if ARCH_ROCKCHIP
283 Address on the MMC to load U-Boot from, when the MMC is being used
284 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
286 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
287 bool "MMC Raw mode: by partition"
289 Use a partition for loading U-Boot when using MMC/SD in raw mode.
291 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
292 hex "Partition to use to load U-Boot from"
293 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
296 Partition on the MMC to load U-Boot from when the MMC is being
299 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
300 bool "MMC raw mode: by partition type"
301 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
303 Use partition type for specifying U-Boot partition on MMC/SD in
304 raw mode. U-Boot will be loaded from the first partition of this
307 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
308 hex "Partition Type on the MMC to load U-Boot from"
309 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
311 Partition Type on the MMC to load U-Boot from, when the MMC is being
314 config SPL_CRC32_SUPPORT
316 default y if SPL_LEGACY_IMAGE_SUPPORT
318 Enable this to support CRC32 in uImages or FIT images within SPL.
319 This is a 32-bit checksum value that can be used to verify images.
320 For FIT images, this is the least secure type of checksum, suitable
321 for detected accidental image corruption. For secure applications you
322 should consider SHA1 or SHA256.
324 config SPL_MD5_SUPPORT
328 Enable this to support MD5 in FIT images within SPL. An MD5
329 checksum is a 128-bit hash value used to check that the image
330 contents have not been corrupted. Note that MD5 is not considered
331 secure as it is possible (with a brute-force attack) to adjust the
332 image while still retaining the same MD5 hash value. For secure
333 applications where images may be changed maliciously, you should
334 consider SHA1 or SHA256.
336 config SPL_SHA1_SUPPORT
341 Enable this to support SHA1 in FIT images within SPL. A SHA1
342 checksum is a 160-bit (20-byte) hash value used to check that the
343 image contents have not been corrupted or maliciously altered.
344 While SHA1 is fairly secure it is coming to the end of its life
345 due to the expanding computing power available to brute-force
346 attacks. For more security, consider SHA256.
348 config SPL_SHA256_SUPPORT
349 bool "Support SHA256"
353 Enable this to support SHA256 in FIT images within SPL. A SHA256
354 checksum is a 256-bit (32-byte) hash value used to check that the
355 image contents have not been corrupted. SHA256 is recommended for
356 use in secure applications since (as at 2016) there is no known
357 feasible attack that could produce a 'collision' with differing
358 input data. Use this for the highest security. Note that only the
359 SHA256 variant is supported: SHA512 and others are not currently
362 config SPL_FIT_IMAGE_TINY
363 bool "Remove functionality from SPL FIT loading to reduce size"
365 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
366 default y if ARCH_IMX8M
368 Enable this to reduce the size of the FIT image loading code
369 in SPL, if space for the SPL binary is very tight.
371 This removes the detection of image types (which forces the
372 first image to be treated as having a U-Boot style calling
373 convention) and skips the recording of each loaded payload
374 (i.e. loadable) into the FDT (modifying the loaded FDT to
375 ensure this information is available to the next image
378 config SPL_CPU_SUPPORT
379 bool "Support CPU drivers"
381 Enable this to support CPU drivers in SPL. These drivers can set
382 up CPUs and provide information about them such as the model and
383 name. This can be useful in SPL since setting up the CPUs earlier
384 may improve boot performance. Enable this option to build the
385 drivers in drivers/cpu as part of an SPL build.
387 config SPL_CRYPTO_SUPPORT
388 bool "Support crypto drivers"
390 Enable crypto drivers in SPL. These drivers can be used to
391 accelerate secure boot processing in secure applications. Enable
392 this option to build the drivers in drivers/crypto as part of an
395 config SPL_HASH_SUPPORT
396 bool "Support hashing drivers"
400 Enable hashing drivers in SPL. These drivers can be used to
401 accelerate secure boot processing in secure applications. Enable
402 this option to build system-specific drivers for hash acceleration
403 as part of an SPL build.
405 config TPL_HASH_SUPPORT
406 bool "Support hashing drivers in TPL"
410 Enable hashing drivers in SPL. These drivers can be used to
411 accelerate secure boot processing in secure applications. Enable
412 this option to build system-specific drivers for hash acceleration
413 as part of an SPL build.
415 config SPL_DMA_SUPPORT
416 bool "Support DMA drivers"
418 Enable DMA (direct-memory-access) drivers in SPL. These drivers
419 can be used to handle memory-to-peripheral data transfer without
420 the CPU moving the data. Enable this option to build the drivers
421 in drivers/dma as part of an SPL build.
423 config SPL_DRIVERS_MISC_SUPPORT
424 bool "Support misc drivers"
426 Enable miscellaneous drivers in SPL. These drivers perform various
427 tasks that don't fall nicely into other categories, Enable this
428 option to build the drivers in drivers/misc as part of an SPL
429 build, for those that support building in SPL (not all drivers do).
431 config SPL_ENV_SUPPORT
432 bool "Support an environment"
434 Enable environment support in SPL. The U-Boot environment provides
435 a number of settings (essentially name/value pairs) which can
436 control many aspects of U-Boot's operation. Normally this is not
437 needed in SPL as it has a much simpler task with less
438 configuration. But some boards use this to support 'Falcon' boot
439 on EXT2 and FAT, where SPL boots directly into Linux without
440 starting U-Boot first. Enabling this option will make env_get()
441 and env_set() available in SPL.
444 bool "Support save environment"
445 depends on SPL_ENV_SUPPORT
446 select SPL_MMC_WRITE if ENV_IS_IN_MMC
448 Enable save environment support in SPL after setenv. By default
449 the saveenv option is not provided in SPL, but some boards need
450 this support in 'Falcon' boot, where SPL need to boot from
451 different images based on environment variable set by OS. For
452 example OS may set "reboot_image" environment variable to
453 "recovery" inorder to boot recovery image by SPL. The SPL read
454 "reboot_image" and act accordingly and change the reboot_image
455 to default mode using setenv and save the environment.
457 config SPL_ETH_SUPPORT
458 bool "Support Ethernet"
459 depends on SPL_ENV_SUPPORT
461 Enable access to the network subsystem and associated Ethernet
462 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
463 link rather than from an on-board peripheral. Environment support
464 is required since the network stack uses a number of environment
465 variables. See also SPL_NET_SUPPORT.
468 bool "Support EXT filesystems"
470 Enable support for EXT2/3/4 filesystems with SPL. This permits
471 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
472 filesystem from within SPL. Support for the underlying block
473 device (e.g. MMC or USB) must be enabled separately.
476 bool "Support FAT filesystems"
479 Enable support for FAT and VFAT filesystems with SPL. This
480 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
481 filesystem from within SPL. Support for the underlying block
482 device (e.g. MMC or USB) must be enabled separately.
485 bool "Support write for FAT filesystems"
487 Enable write support for FAT and VFAT filesystems with SPL.
488 Support for the underlying block device (e.g. MMC or USB) must be
491 config SPL_FPGA_SUPPORT
494 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
495 provide software-configurable hardware which is typically used to
496 implement peripherals (such as UARTs, LCD displays, MMC) or
497 accelerate custom processing functions, such as image processing
498 or machine learning. Sometimes it is useful to program the FPGA
499 as early as possible during boot, and this option can enable that
502 config SPL_GPIO_SUPPORT
503 bool "Support GPIO in SPL"
505 Enable support for GPIOs (General-purpose Input/Output) in SPL.
506 GPIOs allow U-Boot to read the state of an input line (high or
507 low) and set the state of an output line. This can be used to
508 drive LEDs, control power to various system parts and read user
509 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
510 for example. Enable this option to build the drivers in
511 drivers/gpio as part of an SPL build.
513 config SPL_I2C_SUPPORT
516 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
517 I2C works with a clock and data line which can be driven by a
518 one or more masters or slaves. It is a fairly complex bus but is
519 widely used as it only needs two lines for communication. Speeds of
520 400kbps are typical but up to 3.4Mbps is supported by some
521 hardware. I2C can be useful in SPL to configure power management
522 ICs (PMICs) before raising the CPU clock speed, for example.
523 Enable this option to build the drivers in drivers/i2c as part of
526 config SPL_LIBCOMMON_SUPPORT
527 bool "Support common libraries"
529 Enable support for common U-Boot libraries within SPL. These
530 libraries include common code to deal with U-Boot images,
531 environment and USB, for example. This option is enabled on many
532 boards. Enable this option to build the code in common/ as part of
535 config SPL_LIBDISK_SUPPORT
536 bool "Support disk partitions"
539 Enable support for disk partitions within SPL. 'Disk' is something
540 of a misnomer as it includes non-spinning media such as flash (as
541 used in MMC and USB sticks). Partitions provide a way for a disk
542 to be split up into separate regions, with a partition table placed
543 at the start or end which describes the location and size of each
544 'partition'. These partitions are typically uses as individual block
545 devices, typically with an EXT2 or FAT filesystem in each. This
546 option enables whatever partition support has been enabled in
547 U-Boot to also be used in SPL. It brings in the code in disk/.
549 config SPL_LIBGENERIC_SUPPORT
550 bool "Support generic libraries"
552 Enable support for generic U-Boot libraries within SPL. These
553 libraries include generic code to deal with device tree, hashing,
554 printf(), compression and the like. This option is enabled on many
555 boards. Enable this option to build the code in lib/ as part of an
558 config SPL_DM_MAILBOX
559 bool "Support Mailbox"
561 Enable support for Mailbox within SPL. This enable the inter
562 processor communication protocols tobe used within SPL. Enable
563 this option to build the drivers in drivers/mailbox as part of
566 config SPL_MMC_SUPPORT
569 select HAVE_BLOCK_DEVICE
571 Enable support for MMC (Multimedia Card) within SPL. This enables
572 the MMC protocol implementation and allows any enabled drivers to
573 be used within SPL. MMC can be used with or without disk partition
574 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
575 this option to build the drivers in drivers/mmc as part of an SPL
579 bool "Tiny MMC framework in SPL"
580 depends on SPL_MMC_SUPPORT
583 Enable MMC framework tinification support. This option is useful if
584 if your SPL is extremely size constrained. Heed the warning, enable
585 this option if and only if you know exactly what you are doing, if
586 you are reading this help text, you most likely have no idea :-)
588 The MMC framework is reduced to bare minimum to be useful. No malloc
589 support is needed for the MMC framework operation with this option
590 enabled. The framework supports exactly one MMC device and exactly
591 one MMC driver. The MMC driver can be adjusted to avoid any malloc
592 operations too, which can remove the need for malloc support in SPL
593 and thus further reduce footprint.
596 bool "MMC/SD/SDIO card support for write operations in SPL"
597 depends on SPL_MMC_SUPPORT
600 Enable write access to MMC and SD Cards in SPL
603 config SPL_MPC8XXX_INIT_DDR_SUPPORT
604 bool "Support MPC8XXX DDR init"
606 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
607 random-access memory) on the MPC8XXX family within SPL. This
608 allows DRAM to be set up before loading U-Boot into that DRAM,
611 config SPL_MTD_SUPPORT
612 bool "Support MTD drivers"
614 Enable support for MTD (Memory Technology Device) within SPL. MTD
615 provides a block interface over raw NAND and can also be used with
616 SPI flash. This allows SPL to load U-Boot from supported MTD
617 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
618 to enable specific MTD drivers.
620 config SPL_MUSB_NEW_SUPPORT
621 bool "Support new Mentor Graphics USB"
623 Enable support for Mentor Graphics USB in SPL. This is a new
624 driver used by some boards. Enable this option to build
625 the drivers in drivers/usb/musb-new as part of an SPL build. The
626 old drivers are in drivers/usb/musb.
628 config SPL_NAND_SUPPORT
629 bool "Support NAND flash"
631 Enable support for NAND (Negative AND) flash in SPL. NAND flash
632 can be used to allow SPL to load U-Boot from supported devices.
633 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
639 Enable support for loading payloads from UBI. See
640 README.ubispl for more info.
643 config SPL_UBI_LOAD_BY_VOLNAME
644 bool "Support loading volumes by name"
646 This enables support for loading UBI volumes by name. When this
647 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
648 configure the volume name from which to load U-Boot.
650 config SPL_UBI_MAX_VOL_LEBS
651 int "Maximum number of LEBs per volume"
654 The maximum number of logical eraseblocks which a static volume
655 to load can contain. Used for sizing the scan data structure.
657 config SPL_UBI_MAX_PEB_SIZE
658 int "Maximum PEB size"
661 The maximum physical erase block size.
663 config SPL_UBI_MAX_PEBS
664 int "Maximum number of PEBs"
667 The maximum physical erase block size. If not overridden by
668 board code, this value will be used as the actual number of PEBs.
670 config SPL_UBI_PEB_OFFSET
671 int "Offset to first UBI PEB"
674 The offset in number of PEBs from the start of flash to the first
675 PEB part of the UBI image.
677 config SPL_UBI_VID_OFFSET
678 int "Offset to VID header"
681 config SPL_UBI_LEB_START
682 int "Offset to LEB in PEB"
685 The offset in bytes to the LEB within a PEB.
687 config SPL_UBI_INFO_ADDR
688 hex "Address to place UBI scan info"
691 Address for ubispl to place the scan info. Read README.ubispl to
692 determine the required size
694 config SPL_UBI_VOL_IDS
695 int "Maximum volume id"
698 The maximum volume id which can be loaded. Used for sizing the
701 config SPL_UBI_LOAD_MONITOR_ID
702 int "id of U-Boot volume"
705 The UBI volume id from which to load U-Boot
707 config SPL_UBI_LOAD_MONITOR_VOLNAME
708 string "volume name of U-Boot volume"
709 depends on SPL_UBI_LOAD_BY_VOLNAME
711 The UBI volume name from which to load U-Boot
713 config SPL_UBI_LOAD_KERNEL_ID
714 int "id of kernel volume"
715 depends on SPL_OS_BOOT && SPL_UBI
717 The UBI volume id from which to load the kernel
719 config SPL_UBI_LOAD_ARGS_ID
720 int "id of kernel args volume"
721 depends on SPL_OS_BOOT && SPL_UBI
723 The UBI volume id from which to load the device tree
725 config UBI_SPL_SILENCE_MSG
726 bool "silence UBI SPL messages"
729 Disable messages from UBI SPL. This leaves warnings
734 config SPL_NET_SUPPORT
735 bool "Support networking"
737 Enable support for network devices (such as Ethernet) in SPL.
738 This permits SPL to load U-Boot over a network link rather than
739 from an on-board peripheral. Environment support is required since
740 the network stack uses a number of environment variables. See also
744 config SPL_NET_VCI_STRING
745 string "BOOTP Vendor Class Identifier string sent by SPL"
747 As defined by RFC 2132 the vendor class identifier field can be
748 sent by the client to identify the vendor type and configuration
749 of a client. This is often used in practice to allow for the DHCP
750 server to specify different files to load depending on if the ROM,
751 SPL or U-Boot itself makes the request
752 endif # if SPL_NET_SUPPORT
754 config SPL_NO_CPU_SUPPORT
755 bool "Drop CPU code in SPL"
757 This is specific to the ARM926EJ-S CPU. It disables the standard
758 start.S start-up code, presumably so that a replacement can be
759 used on that CPU. You should not enable it unless you know what
762 config SPL_NOR_SUPPORT
763 bool "Support NOR flash"
765 Enable support for loading U-Boot from memory-mapped NOR (Negative
766 OR) flash in SPL. NOR flash is slow to write but fast to read, and
767 a memory-mapped device makes it very easy to access. Loading from
768 NOR is typically achieved with just a memcpy().
770 config SPL_XIP_SUPPORT
774 Enable support for execute in place of U-Boot or kernel image. There
775 is no need to copy image from flash to ram if flash supports execute
776 in place. Its very useful in systems having enough flash but not
777 enough ram to load the image.
779 config SPL_ONENAND_SUPPORT
780 bool "Support OneNAND flash"
782 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
783 a type of NAND flash and therefore can be used to allow SPL to
784 load U-Boot from supported devices. This enables the drivers in
785 drivers/mtd/onenand as part of an SPL build.
788 bool "Activate Falcon Mode"
789 depends on !TI_SECURE_DEVICE
792 Enable booting directly to an OS from SPL.
793 for more info read doc/README.falcon
797 hex "addr, where OS is found"
798 depends on SPL_NOR_SUPPORT
800 Specify the address, where the OS image is found, which
807 default "tpl/u-boot-with-tpl.bin" if TPL
810 Payload for SPL boot. For backward compatibility, default to
811 u-boot.bin, i.e. RAW image without any header. In case of
812 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
816 bool "Support PCI drivers"
818 Enable support for PCI in SPL. For platforms that need PCI to boot,
819 or must perform some init using PCI in SPL, this provides the
820 necessary driver support. This enables the drivers in drivers/pci
821 as part of an SPL build.
823 config SPL_PCH_SUPPORT
824 bool "Support PCH drivers"
826 Enable support for PCH (Platform Controller Hub) devices in SPL.
827 These are used to set up GPIOs and the SPI peripheral early in
828 boot. This enables the drivers in drivers/pch as part of an SPL
831 config SPL_POST_MEM_SUPPORT
832 bool "Support POST drivers"
834 Enable support for POST (Power-on Self Test) in SPL. POST is a
835 procedure that checks that the hardware (CPU or board) appears to
836 be functionally correctly. It is a sanity check that can be
837 performed before booting. This enables the drivers in post/drivers
838 as part of an SPL build.
841 bool "Support reset drivers"
844 Enable support for reset control in SPL.
845 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
846 by using the generic reset API provided by driver model.
847 This enables the drivers in drivers/reset as part of an SPL build.
849 config SPL_POWER_SUPPORT
850 bool "Support power drivers"
852 Enable support for power control in SPL. This includes support
853 for PMICs (Power-management Integrated Circuits) and some of the
854 features provided by PMICs. In particular, voltage regulators can
855 be used to enable/disable power and vary its voltage. That can be
856 useful in SPL to turn on boot peripherals and adjust CPU voltage
857 so that the clock speed can be increased. This enables the drivers
858 in drivers/power, drivers/power/pmic and drivers/power/regulator
859 as part of an SPL build.
861 config SPL_POWER_DOMAIN
862 bool "Support power domain drivers"
864 Enable support for power domain control in SPL. Many SoCs allow
865 power to be applied to or removed from portions of the SoC (power
866 domains). This may be used to save power. This API provides the
867 means to control such power management hardware. This enables
868 the drivers in drivers/power/domain as part of a SPL build.
870 config SPL_RAM_SUPPORT
871 bool "Support booting from RAM"
872 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
874 Enable booting of an image in RAM. The image can be preloaded or
875 it can be loaded by SPL directly into RAM (e.g. using USB).
877 config SPL_RAM_DEVICE
878 bool "Support booting from preloaded image in RAM"
879 depends on SPL_RAM_SUPPORT
880 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
882 Enable booting of an image already loaded in RAM. The image has to
883 be already in memory when SPL takes over, e.g. loaded by the boot
886 config SPL_REMOTEPROC
887 bool "Support REMOTEPROCS"
889 Enable support for REMOTEPROCs in SPL. This permits to load
890 a remote processor firmware in SPL.
892 config SPL_RTC_SUPPORT
893 bool "Support RTC drivers"
895 Enable RTC (Real-time Clock) support in SPL. This includes support
896 for reading and setting the time. Some RTC devices also have some
897 non-volatile (battery-backed) memory which is accessible if
898 needed. This enables the drivers in drivers/rtc as part of an SPL
901 config SPL_SATA_SUPPORT
902 bool "Support loading from SATA"
904 Enable support for SATA (Serial AT attachment) in SPL. This allows
905 use of SATA devices such as hard drives and flash drivers for
906 loading U-Boot. SATA is used in higher-end embedded systems and
907 can provide higher performance than MMC , at somewhat higher
908 expense and power consumption. This enables loading from SATA
909 using a configured device.
911 config SPL_SERIAL_SUPPORT
912 bool "Support serial"
916 Enable support for serial in SPL. This allows use of a serial UART
917 for displaying messages while SPL is running. It also brings in
918 printf() and panic() functions. This should normally be enabled
919 unless there are space reasons not to. Even then, consider
920 enabling USE_TINY_PRINTF which is a small printf() version.
922 config SPL_SPI_FLASH_SUPPORT
923 bool "Support SPI flash drivers"
925 Enable support for using SPI flash in SPL, and loading U-Boot from
926 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
927 the SPI bus that is used to connect it to a system. It is a simple
928 but fast bidirectional 4-wire bus (clock, chip select and two data
929 lines). This enables the drivers in drivers/mtd/spi as part of an
930 SPL build. This normally requires SPL_SPI_SUPPORT.
932 if SPL_SPI_FLASH_SUPPORT
934 config SPL_SPI_FLASH_TINY
935 bool "Enable low footprint SPL SPI Flash support"
936 depends on !SPI_FLASH_BAR
937 default y if SPI_FLASH
939 Enable lightweight SPL SPI Flash support that supports just reading
940 data/images from flash. No support to write/erase flash. Enable
941 this if you have SPL size limitations and don't need full
942 fledged SPI flash support.
944 config SPL_SPI_FLASH_SFDP_SUPPORT
945 bool "SFDP table parsing support for SPI NOR flashes"
946 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
948 Enable support for parsing and auto discovery of parameters for
949 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
950 tables as per JESD216 standard in SPL.
953 bool "Support loading from SPI flash"
955 Enable support for loading next stage, U-Boot or otherwise, from
956 SPI NOR in U-Boot SPL.
958 endif # SPL_SPI_FLASH_SUPPORT
960 config SPL_SPI_SUPPORT
961 bool "Support SPI drivers"
963 Enable support for using SPI in SPL. This is used for connecting
964 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
965 more details on that. The SPI driver provides the transport for
966 data between the SPI flash and the CPU. This option can be used to
967 enable SPI drivers that are needed for other purposes also, such
971 bool "Driver support for thermal devices"
973 Enable support for temperature-sensing devices. Some SoCs have on-chip
974 temperature sensors to permit warnings, speed throttling or even
975 automatic power-off when the temperature gets too high or low. Other
976 devices may be discrete but connected on a suitable bus.
978 config SPL_USB_HOST_SUPPORT
979 bool "Support USB host drivers"
980 select HAVE_BLOCK_DEVICE
982 Enable access to USB (Universal Serial Bus) host devices so that
983 SPL can load U-Boot from a connected USB peripheral, such as a USB
984 flash stick. While USB takes a little longer to start up than most
985 buses, it is very flexible since many different types of storage
986 device can be attached. This option enables the drivers in
987 drivers/usb/host as part of an SPL build.
989 config SPL_USB_STORAGE
990 bool "Support loading from USB"
991 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
993 Enable support for USB devices in SPL. This allows use of USB
994 devices such as hard drives and flash drivers for loading U-Boot.
995 The actual drivers are enabled separately using the normal U-Boot
996 config options. This enables loading from USB using a configured
999 config SPL_USB_GADGET
1000 bool "Suppport USB Gadget drivers"
1002 Enable USB Gadget API which allows to enable USB device functions
1007 config SPL_USB_ETHER
1008 bool "Support USB Ethernet drivers"
1010 Enable access to the USB network subsystem and associated
1011 drivers in SPL. This permits SPL to load U-Boot over a
1012 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1013 than from an onboard peripheral. Environment support is required
1014 since the network stack uses a number of environment variables.
1015 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1018 bool "Support DFU (Device Firmware Upgrade)"
1019 select SPL_HASH_SUPPORT
1020 select SPL_DFU_NO_RESET
1021 depends on SPL_RAM_SUPPORT
1023 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1024 RAM memory device support. The ROM code will load and execute
1025 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1026 selected device partition from host-pc using dfu-utils.
1027 This feature is useful to flash the binaries to factory or bare-metal
1028 boards using USB interface.
1031 bool "DFU device selection"
1036 depends on SPL_DFU && SPL_RAM_SUPPORT
1038 select RAM/DDR memory device for loading binary images
1039 (u-boot/kernel) to the selected device partition using
1040 DFU and execute the u-boot/kernel from RAM.
1044 config SPL_USB_SDP_SUPPORT
1045 bool "Support SDP (Serial Download Protocol)"
1047 Enable Serial Download Protocol (SDP) device support in SPL. This
1048 allows to download images into memory and execute (jump to) them
1049 using the same protocol as implemented by the i.MX family's boot ROM.
1052 config SPL_WATCHDOG_SUPPORT
1053 bool "Support watchdog drivers"
1055 Enable support for watchdog drivers in SPL. A watchdog is
1056 typically a hardware peripheral which can reset the system when it
1057 detects no activity for a while (such as a software crash). This
1058 enables the drivers in drivers/watchdog as part of an SPL build.
1060 config SPL_YMODEM_SUPPORT
1061 bool "Support loading using Ymodem"
1062 depends on SPL_SERIAL_SUPPORT
1064 While loading from serial is slow it can be a useful backup when
1065 there is no other option. The Ymodem protocol provides a reliable
1066 means of transmitting U-Boot over a serial line for using in SPL,
1067 with a checksum to ensure correctness.
1070 bool "Support ARM Trusted Firmware"
1073 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1074 is loaded by SPL (which is considered as BL2 in ATF terminology).
1075 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1077 config SPL_ATF_NO_PLATFORM_PARAM
1078 bool "Pass no platform parameter"
1081 While we expect to call a pointer to a valid FDT (or NULL)
1082 as the platform parameter to an ATF, some ATF versions are
1083 not U-Boot aware and have an insufficiently robust parameter
1084 validation to gracefully reject a FDT being passed.
1086 If this option is enabled, the spl_atf os-type handler will
1087 always pass NULL for the platform parameter.
1089 If your ATF is affected, say Y.
1091 config SPL_AM33XX_ENABLE_RTC32K_OSC
1092 bool "Enable the RTC32K OSC on AM33xx based platforms"
1095 Enable access to the AM33xx RTC and select the external 32kHz clock
1099 bool "Support OP-TEE Trusted OS"
1102 OP-TEE is an open source Trusted OS which is loaded by SPL.
1103 More detail at: https://github.com/OP-TEE/optee_os
1107 depends on SUPPORT_TPL
1110 If you want to build TPL as well as the normal image and SPL, say Y.
1115 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1119 This option enables TPL to write handoff information. This can be
1120 used to pass information like the size of SDRAM from TPL to U-Boot
1121 proper. The information is also available to SPL if it is useful
1124 config TPL_BOARD_INIT
1125 bool "Call board-specific initialization in TPL"
1127 If this option is enabled, U-Boot will call the function
1128 spl_board_init() from board_init_r(). This function should be
1129 provided by the board.
1132 string "Linker script for the TPL stage"
1134 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1135 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
1137 The TPL stage will usually require a different linker-script
1138 (as it runs from a different memory region) than the regular
1139 U-Boot stage. Set this to the path of the linker-script to
1142 May be left empty to trigger the Makefile infrastructure to
1143 fall back to the linker-script used for the SPL stage.
1145 config TPL_NEEDS_SEPARATE_TEXT_BASE
1146 bool "TPL needs a separate text-base"
1150 Enable, if the TPL stage should not inherit its text-base
1151 from the SPL stage. When enabled, a base address for the
1152 .text sections of the TPL stage has to be set below.
1154 config TPL_NEEDS_SEPARATE_STACK
1155 bool "TPL needs a separate initial stack-pointer"
1159 Enable, if the TPL stage should not inherit its initial
1160 stack-pointer from the settings for the SPL stage.
1162 config TPL_TEXT_BASE
1163 hex "Base address for the .text section of the TPL stage"
1164 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1166 The base address for the .text section of the TPL stage.
1169 int "Maximum size (in bytes) for the TPL stage"
1173 The maximum size (in bytes) of the TPL stage.
1176 hex "Address of the initial stack-pointer for the TPL stage"
1177 depends on TPL_NEEDS_SEPARATE_STACK
1179 The address of the initial stack-pointer for the TPL stage.
1180 Usually this will be the (aligned) top-of-stack.
1182 config TPL_BOOTROM_SUPPORT
1183 bool "Support returning to the BOOTROM (from TPL)"
1185 Some platforms (e.g. the Rockchip RK3368) provide support in their
1186 ROM for loading the next boot-stage after performing basic setup
1189 Enable this option, to return to the BOOTROM through the
1190 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1191 boot device list, if not implemented for a given board)
1193 config TPL_DRIVERS_MISC_SUPPORT
1194 bool "Support misc drivers in TPL"
1196 Enable miscellaneous drivers in TPL. These drivers perform various
1197 tasks that don't fall nicely into other categories, Enable this
1198 option to build the drivers in drivers/misc as part of an TPL
1199 build, for those that support building in TPL (not all drivers do).
1201 config TPL_ENV_SUPPORT
1202 bool "Support an environment"
1204 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1206 config TPL_GPIO_SUPPORT
1207 bool "Support GPIO in TPL"
1209 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1210 GPIOs allow U-Boot to read the state of an input line (high or
1211 low) and set the state of an output line. This can be used to
1212 drive LEDs, control power to various system parts and read user
1213 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1214 for example. Enable this option to build the drivers in
1215 drivers/gpio as part of an TPL build.
1217 config TPL_I2C_SUPPORT
1220 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1223 config TPL_LIBCOMMON_SUPPORT
1224 bool "Support common libraries"
1226 Enable support for common U-Boot libraries within TPL. See
1227 SPL_LIBCOMMON_SUPPORT for details.
1229 config TPL_LIBGENERIC_SUPPORT
1230 bool "Support generic libraries"
1232 Enable support for generic U-Boot libraries within TPL. See
1233 SPL_LIBGENERIC_SUPPORT for details.
1235 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1236 bool "Support MPC8XXX DDR init"
1238 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1239 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1241 config TPL_MMC_SUPPORT
1245 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1247 config TPL_NAND_SUPPORT
1248 bool "Support NAND flash"
1250 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1253 bool "Support PCI drivers"
1255 Enable support for PCI in TPL. For platforms that need PCI to boot,
1256 or must perform some init using PCI in SPL, this provides the
1257 necessary driver support. This enables the drivers in drivers/pci
1258 as part of a TPL build.
1260 config TPL_PCH_SUPPORT
1261 bool "Support PCH drivers"
1263 Enable support for PCH (Platform Controller Hub) devices in TPL.
1264 These are used to set up GPIOs and the SPI peripheral early in
1265 boot. This enables the drivers in drivers/pch as part of a TPL
1268 config TPL_RAM_SUPPORT
1269 bool "Support booting from RAM"
1271 Enable booting of an image in RAM. The image can be preloaded or
1272 it can be loaded by TPL directly into RAM (e.g. using USB).
1274 config TPL_RAM_DEVICE
1275 bool "Support booting from preloaded image in RAM"
1276 depends on TPL_RAM_SUPPORT
1278 Enable booting of an image already loaded in RAM. The image has to
1279 be already in memory when TPL takes over, e.g. loaded by the boot
1282 config TPL_RTC_SUPPORT
1283 bool "Support RTC drivers"
1285 Enable RTC (Real-time Clock) support in TPL. This includes support
1286 for reading and setting the time. Some RTC devices also have some
1287 non-volatile (battery-backed) memory which is accessible if
1288 needed. This enables the drivers in drivers/rtc as part of an TPL
1291 config TPL_SERIAL_SUPPORT
1292 bool "Support serial"
1296 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1299 config TPL_SPI_FLASH_SUPPORT
1300 bool "Support SPI flash drivers"
1302 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1306 bool "Support loading from SPI flash"
1307 depends on TPL_SPI_FLASH_SUPPORT
1309 Enable support for loading next stage, U-Boot or otherwise, from
1310 SPI NOR in U-Boot TPL.
1312 config TPL_SPI_SUPPORT
1313 bool "Support SPI drivers"
1315 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1318 config TPL_YMODEM_SUPPORT
1319 bool "Support loading using Ymodem"
1320 depends on TPL_SERIAL_SUPPORT
1322 While loading from serial is slow it can be a useful backup when
1323 there is no other option. The Ymodem protocol provides a reliable
1324 means of transmitting U-Boot over a serial line for using in TPL,
1325 with a checksum to ensure correctness.
1329 config SPL_AT91_MCK_BYPASS
1330 bool "Use external clock signal as a source of main clock for AT91 platforms"
1331 depends on ARCH_AT91
1334 Use external 8 to 24 Mhz clock signal as source of main clock instead
1335 of an external crystal oscillator.
1336 This option disables the internal driving on the XOUT pin.
1337 The external source has to provide a stable clock on the XIN pin.
1338 If this option is disabled, the SoC expects a crystal oscillator
1339 that needs driving on both XIN and XOUT lines.