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"
212 Say Y here to only use the *_simple malloc functions from
213 malloc_simple.c, rather then using the versions from dlmalloc.c;
214 this will make the TPL binary smaller at the cost of more heap
215 usage as the *_simple malloc functions do not re-use free-ed mem.
218 bool "Enable SDRAM location for SPL stack"
220 SPL starts off execution in SRAM and thus typically has only a small
221 stack available. Since SPL sets up DRAM while in its board_init_f()
222 function, it is possible for the stack to move there before
223 board_init_r() is reached. This option enables a special SDRAM
224 location for the SPL stack. U-Boot SPL switches to this after
225 board_init_f() completes, and before board_init_r() starts.
227 config SPL_STACK_R_ADDR
228 depends on SPL_STACK_R
229 hex "SDRAM location for SPL stack"
230 default 0x82000000 if ARCH_OMAP2PLUS
232 Specify the address in SDRAM for the SPL stack. This will be set up
233 before board_init_r() is called.
235 config SPL_STACK_R_MALLOC_SIMPLE_LEN
236 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
237 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
240 Specify the amount of the stack to use as memory pool for
241 malloc_simple after switching the stack to DRAM. This may be set
242 to give board_init_r() a larger heap then the initial heap in
243 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
245 config SPL_SEPARATE_BSS
246 bool "BSS section is in a different memory region from text"
248 Some platforms need a large BSS region in SPL and can provide this
249 because RAM is already set up. In this case BSS can be moved to RAM.
250 This option should then be enabled so that the correct device tree
251 location is used. Normally we put the device tree at the end of BSS
252 but with this option enabled, it goes at _image_binary_end.
254 config SPL_BANNER_PRINT
255 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
258 If this option is enabled, SPL will print the banner with version
259 info. Disabling this option could be useful to reduce TPL boot time
260 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
262 config TPL_BANNER_PRINT
263 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
266 If this option is enabled, SPL will not print the banner with version
267 info. Disabling this option could be useful to reduce SPL boot time
268 (e.g. approx. 6 ms faster, when output on i.MX6 with 115200 baud).
271 depends on ARM && !ARM64
272 bool "Allows initializing BSS early before entering board_init_f"
274 On some platform we have sufficient memory available early on to
275 allow setting up and using a basic BSS prior to entering
276 board_init_f. Activating this option will also de-activate the
277 clearing of BSS during the SPL relocation process, thus allowing
278 to carry state from board_init_f to board_init_r by way of BSS.
280 config SPL_DISPLAY_PRINT
281 bool "Display a board-specific message in SPL"
283 If this option is enabled, U-Boot will call the function
284 spl_display_print() immediately after displaying the SPL console
285 banner ("U-Boot SPL ..."). This function should be provided by
288 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
289 bool "MMC raw mode: by sector"
290 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
291 ARCH_MX6 || ARCH_MX7 || \
292 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
293 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
294 OMAP44XX || OMAP54XX || AM33XX || AM43XX
296 Use sector number for specifying U-Boot location on MMC/SD in
299 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
300 hex "Address on the MMC to load U-Boot from"
301 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
302 default 0x50 if ARCH_SUNXI
303 default 0x75 if ARCH_DAVINCI
304 default 0x8a if ARCH_MX6 || ARCH_MX7
305 default 0x100 if ARCH_UNIPHIER
306 default 0x140 if ARCH_MVEBU
307 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
308 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
309 OMAP54XX || AM33XX || AM43XX || ARCH_K3
310 default 0x4000 if ARCH_ROCKCHIP
312 Address on the MMC to load U-Boot from, when the MMC is being used
313 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
315 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
316 bool "MMC Raw mode: by partition"
318 Use a partition for loading U-Boot when using MMC/SD in raw mode.
320 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
321 hex "Partition to use to load U-Boot from"
322 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
325 Partition on the MMC to load U-Boot from when the MMC is being
328 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
329 bool "MMC raw mode: by partition type"
330 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
332 Use partition type for specifying U-Boot partition on MMC/SD in
333 raw mode. U-Boot will be loaded from the first partition of this
336 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
337 hex "Partition Type on the MMC to load U-Boot from"
338 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
340 Partition Type on the MMC to load U-Boot from, when the MMC is being
343 config SPL_CRC32_SUPPORT
345 default y if SPL_LEGACY_IMAGE_SUPPORT
347 Enable this to support CRC32 in uImages or FIT images within SPL.
348 This is a 32-bit checksum value that can be used to verify images.
349 For FIT images, this is the least secure type of checksum, suitable
350 for detected accidental image corruption. For secure applications you
351 should consider SHA1 or SHA256.
353 config SPL_MD5_SUPPORT
357 Enable this to support MD5 in FIT images within SPL. An MD5
358 checksum is a 128-bit hash value used to check that the image
359 contents have not been corrupted. Note that MD5 is not considered
360 secure as it is possible (with a brute-force attack) to adjust the
361 image while still retaining the same MD5 hash value. For secure
362 applications where images may be changed maliciously, you should
363 consider SHA1 or SHA256.
365 config SPL_SHA1_SUPPORT
370 Enable this to support SHA1 in FIT images within SPL. A SHA1
371 checksum is a 160-bit (20-byte) hash value used to check that the
372 image contents have not been corrupted or maliciously altered.
373 While SHA1 is fairly secure it is coming to the end of its life
374 due to the expanding computing power available to brute-force
375 attacks. For more security, consider SHA256.
377 config SPL_SHA256_SUPPORT
378 bool "Support SHA256"
382 Enable this to support SHA256 in FIT images within SPL. A SHA256
383 checksum is a 256-bit (32-byte) hash value used to check that the
384 image contents have not been corrupted. SHA256 is recommended for
385 use in secure applications since (as at 2016) there is no known
386 feasible attack that could produce a 'collision' with differing
387 input data. Use this for the highest security. Note that only the
388 SHA256 variant is supported: SHA512 and others are not currently
391 config SPL_FIT_IMAGE_TINY
392 bool "Remove functionality from SPL FIT loading to reduce size"
394 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
395 default y if ARCH_IMX8M
397 Enable this to reduce the size of the FIT image loading code
398 in SPL, if space for the SPL binary is very tight.
400 This removes the detection of image types (which forces the
401 first image to be treated as having a U-Boot style calling
402 convention) and skips the recording of each loaded payload
403 (i.e. loadable) into the FDT (modifying the loaded FDT to
404 ensure this information is available to the next image
407 config SPL_CPU_SUPPORT
408 bool "Support CPU drivers"
410 Enable this to support CPU drivers in SPL. These drivers can set
411 up CPUs and provide information about them such as the model and
412 name. This can be useful in SPL since setting up the CPUs earlier
413 may improve boot performance. Enable this option to build the
414 drivers in drivers/cpu as part of an SPL build.
416 config SPL_CRYPTO_SUPPORT
417 bool "Support crypto drivers"
419 Enable crypto drivers in SPL. These drivers can be used to
420 accelerate secure boot processing in secure applications. Enable
421 this option to build the drivers in drivers/crypto as part of an
424 config SPL_HASH_SUPPORT
425 bool "Support hashing drivers"
429 Enable hashing drivers in SPL. These drivers can be used to
430 accelerate secure boot processing in secure applications. Enable
431 this option to build system-specific drivers for hash acceleration
432 as part of an SPL build.
434 config TPL_HASH_SUPPORT
435 bool "Support hashing drivers in TPL"
439 Enable hashing drivers in SPL. These drivers can be used to
440 accelerate secure boot processing in secure applications. Enable
441 this option to build system-specific drivers for hash acceleration
442 as part of an SPL build.
444 config SPL_DMA_SUPPORT
445 bool "Support DMA drivers"
447 Enable DMA (direct-memory-access) drivers in SPL. These drivers
448 can be used to handle memory-to-peripheral data transfer without
449 the CPU moving the data. Enable this option to build the drivers
450 in drivers/dma as part of an SPL build.
452 config SPL_DRIVERS_MISC_SUPPORT
453 bool "Support misc drivers"
455 Enable miscellaneous drivers in SPL. These drivers perform various
456 tasks that don't fall nicely into other categories, Enable this
457 option to build the drivers in drivers/misc as part of an SPL
458 build, for those that support building in SPL (not all drivers do).
460 config SPL_ENV_SUPPORT
461 bool "Support an environment"
463 Enable environment support in SPL. The U-Boot environment provides
464 a number of settings (essentially name/value pairs) which can
465 control many aspects of U-Boot's operation. Normally this is not
466 needed in SPL as it has a much simpler task with less
467 configuration. But some boards use this to support 'Falcon' boot
468 on EXT2 and FAT, where SPL boots directly into Linux without
469 starting U-Boot first. Enabling this option will make env_get()
470 and env_set() available in SPL.
473 bool "Support save environment"
474 depends on SPL_ENV_SUPPORT
475 select SPL_MMC_WRITE if ENV_IS_IN_MMC
477 Enable save environment support in SPL after setenv. By default
478 the saveenv option is not provided in SPL, but some boards need
479 this support in 'Falcon' boot, where SPL need to boot from
480 different images based on environment variable set by OS. For
481 example OS may set "reboot_image" environment variable to
482 "recovery" inorder to boot recovery image by SPL. The SPL read
483 "reboot_image" and act accordingly and change the reboot_image
484 to default mode using setenv and save the environment.
486 config SPL_ETH_SUPPORT
487 bool "Support Ethernet"
488 depends on SPL_ENV_SUPPORT
490 Enable access to the network subsystem and associated Ethernet
491 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
492 link rather than from an on-board peripheral. Environment support
493 is required since the network stack uses a number of environment
494 variables. See also SPL_NET_SUPPORT.
497 bool "Support EXT filesystems"
499 Enable support for EXT2/3/4 filesystems with SPL. This permits
500 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
501 filesystem from within SPL. Support for the underlying block
502 device (e.g. MMC or USB) must be enabled separately.
505 bool "Support FAT filesystems"
508 Enable support for FAT and VFAT filesystems with SPL. This
509 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
510 filesystem from within SPL. Support for the underlying block
511 device (e.g. MMC or USB) must be enabled separately.
514 bool "Support write for FAT filesystems"
516 Enable write support for FAT and VFAT filesystems with SPL.
517 Support for the underlying block device (e.g. MMC or USB) must be
520 config SPL_FPGA_SUPPORT
523 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
524 provide software-configurable hardware which is typically used to
525 implement peripherals (such as UARTs, LCD displays, MMC) or
526 accelerate custom processing functions, such as image processing
527 or machine learning. Sometimes it is useful to program the FPGA
528 as early as possible during boot, and this option can enable that
531 config SPL_GPIO_SUPPORT
532 bool "Support GPIO in SPL"
534 Enable support for GPIOs (General-purpose Input/Output) in SPL.
535 GPIOs allow U-Boot to read the state of an input line (high or
536 low) and set the state of an output line. This can be used to
537 drive LEDs, control power to various system parts and read user
538 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
539 for example. Enable this option to build the drivers in
540 drivers/gpio as part of an SPL build.
542 config SPL_I2C_SUPPORT
545 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
546 I2C works with a clock and data line which can be driven by a
547 one or more masters or slaves. It is a fairly complex bus but is
548 widely used as it only needs two lines for communication. Speeds of
549 400kbps are typical but up to 3.4Mbps is supported by some
550 hardware. I2C can be useful in SPL to configure power management
551 ICs (PMICs) before raising the CPU clock speed, for example.
552 Enable this option to build the drivers in drivers/i2c as part of
555 config SPL_LIBCOMMON_SUPPORT
556 bool "Support common libraries"
558 Enable support for common U-Boot libraries within SPL. These
559 libraries include common code to deal with U-Boot images,
560 environment and USB, for example. This option is enabled on many
561 boards. Enable this option to build the code in common/ as part of
564 config SPL_LIBDISK_SUPPORT
565 bool "Support disk partitions"
568 Enable support for disk partitions within SPL. 'Disk' is something
569 of a misnomer as it includes non-spinning media such as flash (as
570 used in MMC and USB sticks). Partitions provide a way for a disk
571 to be split up into separate regions, with a partition table placed
572 at the start or end which describes the location and size of each
573 'partition'. These partitions are typically uses as individual block
574 devices, typically with an EXT2 or FAT filesystem in each. This
575 option enables whatever partition support has been enabled in
576 U-Boot to also be used in SPL. It brings in the code in disk/.
578 config SPL_LIBGENERIC_SUPPORT
579 bool "Support generic libraries"
581 Enable support for generic U-Boot libraries within SPL. These
582 libraries include generic code to deal with device tree, hashing,
583 printf(), compression and the like. This option is enabled on many
584 boards. Enable this option to build the code in lib/ as part of an
587 config SPL_DM_MAILBOX
588 bool "Support Mailbox"
590 Enable support for Mailbox within SPL. This enable the inter
591 processor communication protocols tobe used within SPL. Enable
592 this option to build the drivers in drivers/mailbox as part of
595 config SPL_MMC_SUPPORT
598 select HAVE_BLOCK_DEVICE
600 Enable support for MMC (Multimedia Card) within SPL. This enables
601 the MMC protocol implementation and allows any enabled drivers to
602 be used within SPL. MMC can be used with or without disk partition
603 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
604 this option to build the drivers in drivers/mmc as part of an SPL
608 bool "Tiny MMC framework in SPL"
609 depends on SPL_MMC_SUPPORT
612 Enable MMC framework tinification support. This option is useful if
613 if your SPL is extremely size constrained. Heed the warning, enable
614 this option if and only if you know exactly what you are doing, if
615 you are reading this help text, you most likely have no idea :-)
617 The MMC framework is reduced to bare minimum to be useful. No malloc
618 support is needed for the MMC framework operation with this option
619 enabled. The framework supports exactly one MMC device and exactly
620 one MMC driver. The MMC driver can be adjusted to avoid any malloc
621 operations too, which can remove the need for malloc support in SPL
622 and thus further reduce footprint.
625 bool "MMC/SD/SDIO card support for write operations in SPL"
626 depends on SPL_MMC_SUPPORT
629 Enable write access to MMC and SD Cards in SPL
632 config SPL_MPC8XXX_INIT_DDR_SUPPORT
633 bool "Support MPC8XXX DDR init"
635 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
636 random-access memory) on the MPC8XXX family within SPL. This
637 allows DRAM to be set up before loading U-Boot into that DRAM,
640 config SPL_MTD_SUPPORT
641 bool "Support MTD drivers"
643 Enable support for MTD (Memory Technology Device) within SPL. MTD
644 provides a block interface over raw NAND and can also be used with
645 SPI flash. This allows SPL to load U-Boot from supported MTD
646 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
647 to enable specific MTD drivers.
649 config SPL_MUSB_NEW_SUPPORT
650 bool "Support new Mentor Graphics USB"
652 Enable support for Mentor Graphics USB in SPL. This is a new
653 driver used by some boards. Enable this option to build
654 the drivers in drivers/usb/musb-new as part of an SPL build. The
655 old drivers are in drivers/usb/musb.
657 config SPL_NAND_SUPPORT
658 bool "Support NAND flash"
660 Enable support for NAND (Negative AND) flash in SPL. NAND flash
661 can be used to allow SPL to load U-Boot from supported devices.
662 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
668 Enable support for loading payloads from UBI. See
669 README.ubispl for more info.
672 config SPL_UBI_LOAD_BY_VOLNAME
673 bool "Support loading volumes by name"
675 This enables support for loading UBI volumes by name. When this
676 is set, CONFIG_SPL_UBI_LOAD_MONITOR_VOLNAME can be used to
677 configure the volume name from which to load U-Boot.
679 config SPL_UBI_MAX_VOL_LEBS
680 int "Maximum number of LEBs per volume"
683 The maximum number of logical eraseblocks which a static volume
684 to load can contain. Used for sizing the scan data structure.
686 config SPL_UBI_MAX_PEB_SIZE
687 int "Maximum PEB size"
690 The maximum physical erase block size.
692 config SPL_UBI_MAX_PEBS
693 int "Maximum number of PEBs"
696 The maximum physical erase block size. If not overridden by
697 board code, this value will be used as the actual number of PEBs.
699 config SPL_UBI_PEB_OFFSET
700 int "Offset to first UBI PEB"
703 The offset in number of PEBs from the start of flash to the first
704 PEB part of the UBI image.
706 config SPL_UBI_VID_OFFSET
707 int "Offset to VID header"
710 config SPL_UBI_LEB_START
711 int "Offset to LEB in PEB"
714 The offset in bytes to the LEB within a PEB.
716 config SPL_UBI_INFO_ADDR
717 hex "Address to place UBI scan info"
720 Address for ubispl to place the scan info. Read README.ubispl to
721 determine the required size
723 config SPL_UBI_VOL_IDS
724 int "Maximum volume id"
727 The maximum volume id which can be loaded. Used for sizing the
730 config SPL_UBI_LOAD_MONITOR_ID
731 int "id of U-Boot volume"
734 The UBI volume id from which to load U-Boot
736 config SPL_UBI_LOAD_MONITOR_VOLNAME
737 string "volume name of U-Boot volume"
738 depends on SPL_UBI_LOAD_BY_VOLNAME
740 The UBI volume name from which to load U-Boot
742 config SPL_UBI_LOAD_KERNEL_ID
743 int "id of kernel volume"
744 depends on SPL_OS_BOOT && SPL_UBI
746 The UBI volume id from which to load the kernel
748 config SPL_UBI_LOAD_ARGS_ID
749 int "id of kernel args volume"
750 depends on SPL_OS_BOOT && SPL_UBI
752 The UBI volume id from which to load the device tree
754 config UBI_SPL_SILENCE_MSG
755 bool "silence UBI SPL messages"
758 Disable messages from UBI SPL. This leaves warnings
763 config SPL_NET_SUPPORT
764 bool "Support networking"
766 Enable support for network devices (such as Ethernet) in SPL.
767 This permits SPL to load U-Boot over a network link rather than
768 from an on-board peripheral. Environment support is required since
769 the network stack uses a number of environment variables. See also
773 config SPL_NET_VCI_STRING
774 string "BOOTP Vendor Class Identifier string sent by SPL"
776 As defined by RFC 2132 the vendor class identifier field can be
777 sent by the client to identify the vendor type and configuration
778 of a client. This is often used in practice to allow for the DHCP
779 server to specify different files to load depending on if the ROM,
780 SPL or U-Boot itself makes the request
781 endif # if SPL_NET_SUPPORT
783 config SPL_NO_CPU_SUPPORT
784 bool "Drop CPU code in SPL"
786 This is specific to the ARM926EJ-S CPU. It disables the standard
787 start.S start-up code, presumably so that a replacement can be
788 used on that CPU. You should not enable it unless you know what
791 config SPL_NOR_SUPPORT
792 bool "Support NOR flash"
794 Enable support for loading U-Boot from memory-mapped NOR (Negative
795 OR) flash in SPL. NOR flash is slow to write but fast to read, and
796 a memory-mapped device makes it very easy to access. Loading from
797 NOR is typically achieved with just a memcpy().
799 config SPL_XIP_SUPPORT
803 Enable support for execute in place of U-Boot or kernel image. There
804 is no need to copy image from flash to ram if flash supports execute
805 in place. Its very useful in systems having enough flash but not
806 enough ram to load the image.
808 config SPL_ONENAND_SUPPORT
809 bool "Support OneNAND flash"
811 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
812 a type of NAND flash and therefore can be used to allow SPL to
813 load U-Boot from supported devices. This enables the drivers in
814 drivers/mtd/onenand as part of an SPL build.
817 bool "Activate Falcon Mode"
818 depends on !TI_SECURE_DEVICE
821 Enable booting directly to an OS from SPL.
822 for more info read doc/README.falcon
826 hex "addr, where OS is found"
827 depends on SPL_NOR_SUPPORT
829 Specify the address, where the OS image is found, which
836 default "tpl/u-boot-with-tpl.bin" if TPL
839 Payload for SPL boot. For backward compatibility, default to
840 u-boot.bin, i.e. RAW image without any header. In case of
841 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
845 bool "Support PCI drivers"
847 Enable support for PCI in SPL. For platforms that need PCI to boot,
848 or must perform some init using PCI in SPL, this provides the
849 necessary driver support. This enables the drivers in drivers/pci
850 as part of an SPL build.
852 config SPL_PCH_SUPPORT
853 bool "Support PCH drivers"
855 Enable support for PCH (Platform Controller Hub) devices in SPL.
856 These are used to set up GPIOs and the SPI peripheral early in
857 boot. This enables the drivers in drivers/pch as part of an SPL
860 config SPL_POST_MEM_SUPPORT
861 bool "Support POST drivers"
863 Enable support for POST (Power-on Self Test) in SPL. POST is a
864 procedure that checks that the hardware (CPU or board) appears to
865 be functionally correctly. It is a sanity check that can be
866 performed before booting. This enables the drivers in post/drivers
867 as part of an SPL build.
870 bool "Support reset drivers"
873 Enable support for reset control in SPL.
874 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
875 by using the generic reset API provided by driver model.
876 This enables the drivers in drivers/reset as part of an SPL build.
878 config SPL_POWER_SUPPORT
879 bool "Support power drivers"
881 Enable support for power control in SPL. This includes support
882 for PMICs (Power-management Integrated Circuits) and some of the
883 features provided by PMICs. In particular, voltage regulators can
884 be used to enable/disable power and vary its voltage. That can be
885 useful in SPL to turn on boot peripherals and adjust CPU voltage
886 so that the clock speed can be increased. This enables the drivers
887 in drivers/power, drivers/power/pmic and drivers/power/regulator
888 as part of an SPL build.
890 config SPL_POWER_DOMAIN
891 bool "Support power domain drivers"
893 Enable support for power domain control in SPL. Many SoCs allow
894 power to be applied to or removed from portions of the SoC (power
895 domains). This may be used to save power. This API provides the
896 means to control such power management hardware. This enables
897 the drivers in drivers/power/domain as part of a SPL build.
899 config SPL_RAM_SUPPORT
900 bool "Support booting from RAM"
901 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
903 Enable booting of an image in RAM. The image can be preloaded or
904 it can be loaded by SPL directly into RAM (e.g. using USB).
906 config SPL_RAM_DEVICE
907 bool "Support booting from preloaded image in RAM"
908 depends on SPL_RAM_SUPPORT
909 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
911 Enable booting of an image already loaded in RAM. The image has to
912 be already in memory when SPL takes over, e.g. loaded by the boot
915 config SPL_REMOTEPROC
916 bool "Support REMOTEPROCS"
918 Enable support for REMOTEPROCs in SPL. This permits to load
919 a remote processor firmware in SPL.
921 config SPL_RTC_SUPPORT
922 bool "Support RTC drivers"
924 Enable RTC (Real-time Clock) support in SPL. This includes support
925 for reading and setting the time. Some RTC devices also have some
926 non-volatile (battery-backed) memory which is accessible if
927 needed. This enables the drivers in drivers/rtc as part of an SPL
930 config SPL_SATA_SUPPORT
931 bool "Support loading from SATA"
933 Enable support for SATA (Serial AT attachment) in SPL. This allows
934 use of SATA devices such as hard drives and flash drivers for
935 loading U-Boot. SATA is used in higher-end embedded systems and
936 can provide higher performance than MMC , at somewhat higher
937 expense and power consumption. This enables loading from SATA
938 using a configured device.
940 config SPL_SATA_RAW_U_BOOT_USE_SECTOR
941 bool "SATA raw mode: by sector"
942 depends on SPL_SATA_SUPPORT
944 Use sector number for specifying U-Boot location on SATA disk in
947 config SPL_SATA_RAW_U_BOOT_SECTOR
948 hex "Sector on the SATA disk to load U-Boot from"
949 depends on SPL_SATA_RAW_U_BOOT_USE_SECTOR
951 Sector on the SATA disk to load U-Boot from, when the SATA disk is being
952 used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
954 config SPL_SERIAL_SUPPORT
955 bool "Support serial"
959 Enable support for serial in SPL. This allows use of a serial UART
960 for displaying messages while SPL is running. It also brings in
961 printf() and panic() functions. This should normally be enabled
962 unless there are space reasons not to. Even then, consider
963 enabling USE_TINY_PRINTF which is a small printf() version.
965 config SPL_SPI_FLASH_SUPPORT
966 bool "Support SPI flash drivers"
968 Enable support for using SPI flash in SPL, and loading U-Boot from
969 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
970 the SPI bus that is used to connect it to a system. It is a simple
971 but fast bidirectional 4-wire bus (clock, chip select and two data
972 lines). This enables the drivers in drivers/mtd/spi as part of an
973 SPL build. This normally requires SPL_SPI_SUPPORT.
975 if SPL_SPI_FLASH_SUPPORT
977 config SPL_SPI_FLASH_TINY
978 bool "Enable low footprint SPL SPI Flash support"
979 depends on !SPI_FLASH_BAR
980 default y if SPI_FLASH
982 Enable lightweight SPL SPI Flash support that supports just reading
983 data/images from flash. No support to write/erase flash. Enable
984 this if you have SPL size limitations and don't need full
985 fledged SPI flash support.
987 config SPL_SPI_FLASH_SFDP_SUPPORT
988 bool "SFDP table parsing support for SPI NOR flashes"
989 depends on !SPI_FLASH_BAR && !SPL_SPI_FLASH_TINY
991 Enable support for parsing and auto discovery of parameters for
992 SPI NOR flashes using Serial Flash Discoverable Parameters (SFDP)
993 tables as per JESD216 standard in SPL.
996 bool "Support loading from SPI flash"
998 Enable support for loading next stage, U-Boot or otherwise, from
999 SPI NOR in U-Boot SPL.
1001 endif # SPL_SPI_FLASH_SUPPORT
1003 config SPL_SPI_SUPPORT
1004 bool "Support SPI drivers"
1006 Enable support for using SPI in SPL. This is used for connecting
1007 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
1008 more details on that. The SPI driver provides the transport for
1009 data between the SPI flash and the CPU. This option can be used to
1010 enable SPI drivers that are needed for other purposes also, such
1014 bool "Driver support for thermal devices"
1016 Enable support for temperature-sensing devices. Some SoCs have on-chip
1017 temperature sensors to permit warnings, speed throttling or even
1018 automatic power-off when the temperature gets too high or low. Other
1019 devices may be discrete but connected on a suitable bus.
1021 config SPL_USB_HOST_SUPPORT
1022 bool "Support USB host drivers"
1023 select HAVE_BLOCK_DEVICE
1025 Enable access to USB (Universal Serial Bus) host devices so that
1026 SPL can load U-Boot from a connected USB peripheral, such as a USB
1027 flash stick. While USB takes a little longer to start up than most
1028 buses, it is very flexible since many different types of storage
1029 device can be attached. This option enables the drivers in
1030 drivers/usb/host as part of an SPL build.
1032 config SPL_USB_STORAGE
1033 bool "Support loading from USB"
1034 depends on SPL_USB_HOST_SUPPORT && !(BLK && !DM_USB)
1036 Enable support for USB devices in SPL. This allows use of USB
1037 devices such as hard drives and flash drivers for loading U-Boot.
1038 The actual drivers are enabled separately using the normal U-Boot
1039 config options. This enables loading from USB using a configured
1042 config SPL_USB_GADGET
1043 bool "Suppport USB Gadget drivers"
1045 Enable USB Gadget API which allows to enable USB device functions
1050 config SPL_USB_ETHER
1051 bool "Support USB Ethernet drivers"
1053 Enable access to the USB network subsystem and associated
1054 drivers in SPL. This permits SPL to load U-Boot over a
1055 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
1056 than from an onboard peripheral. Environment support is required
1057 since the network stack uses a number of environment variables.
1058 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
1061 bool "Support DFU (Device Firmware Upgrade)"
1062 select SPL_HASH_SUPPORT
1063 select SPL_DFU_NO_RESET
1064 depends on SPL_RAM_SUPPORT
1066 This feature enables the DFU (Device Firmware Upgrade) in SPL with
1067 RAM memory device support. The ROM code will load and execute
1068 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
1069 selected device partition from host-pc using dfu-utils.
1070 This feature is useful to flash the binaries to factory or bare-metal
1071 boards using USB interface.
1074 bool "DFU device selection"
1079 depends on SPL_DFU && SPL_RAM_SUPPORT
1081 select RAM/DDR memory device for loading binary images
1082 (u-boot/kernel) to the selected device partition using
1083 DFU and execute the u-boot/kernel from RAM.
1087 config SPL_USB_SDP_SUPPORT
1088 bool "Support SDP (Serial Download Protocol)"
1090 Enable Serial Download Protocol (SDP) device support in SPL. This
1091 allows to download images into memory and execute (jump to) them
1092 using the same protocol as implemented by the i.MX family's boot ROM.
1095 config SPL_WATCHDOG_SUPPORT
1096 bool "Support watchdog drivers"
1097 imply SPL_WDT if !HW_WATCHDOG
1099 Enable support for watchdog drivers in SPL. A watchdog is
1100 typically a hardware peripheral which can reset the system when it
1101 detects no activity for a while (such as a software crash). This
1102 enables the drivers in drivers/watchdog as part of an SPL build.
1104 config SPL_YMODEM_SUPPORT
1105 bool "Support loading using Ymodem"
1106 depends on SPL_SERIAL_SUPPORT
1108 While loading from serial is slow it can be a useful backup when
1109 there is no other option. The Ymodem protocol provides a reliable
1110 means of transmitting U-Boot over a serial line for using in SPL,
1111 with a checksum to ensure correctness.
1114 bool "Support ARM Trusted Firmware"
1117 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
1118 is loaded by SPL (which is considered as BL2 in ATF terminology).
1119 More detail at: https://github.com/ARM-software/arm-trusted-firmware
1121 config SPL_ATF_NO_PLATFORM_PARAM
1122 bool "Pass no platform parameter"
1125 While we expect to call a pointer to a valid FDT (or NULL)
1126 as the platform parameter to an ATF, some ATF versions are
1127 not U-Boot aware and have an insufficiently robust parameter
1128 validation to gracefully reject a FDT being passed.
1130 If this option is enabled, the spl_atf os-type handler will
1131 always pass NULL for the platform parameter.
1133 If your ATF is affected, say Y.
1135 config SPL_AM33XX_ENABLE_RTC32K_OSC
1136 bool "Enable the RTC32K OSC on AM33xx based platforms"
1139 Enable access to the AM33xx RTC and select the external 32kHz clock
1143 bool "Support OP-TEE Trusted OS"
1146 OP-TEE is an open source Trusted OS which is loaded by SPL.
1147 More detail at: https://github.com/OP-TEE/optee_os
1151 depends on SUPPORT_TPL
1154 If you want to build TPL as well as the normal image and SPL, say Y.
1159 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
1163 This option enables TPL to write handoff information. This can be
1164 used to pass information like the size of SDRAM from TPL to U-Boot
1165 proper. The information is also available to SPL if it is useful
1168 config TPL_BOARD_INIT
1169 bool "Call board-specific initialization in TPL"
1171 If this option is enabled, U-Boot will call the function
1172 spl_board_init() from board_init_r(). This function should be
1173 provided by the board.
1176 string "Linker script for the TPL stage"
1178 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
1179 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
1181 The TPL stage will usually require a different linker-script
1182 (as it runs from a different memory region) than the regular
1183 U-Boot stage. Set this to the path of the linker-script to
1186 May be left empty to trigger the Makefile infrastructure to
1187 fall back to the linker-script used for the SPL stage.
1189 config TPL_NEEDS_SEPARATE_TEXT_BASE
1190 bool "TPL needs a separate text-base"
1194 Enable, if the TPL stage should not inherit its text-base
1195 from the SPL stage. When enabled, a base address for the
1196 .text sections of the TPL stage has to be set below.
1198 config TPL_NEEDS_SEPARATE_STACK
1199 bool "TPL needs a separate initial stack-pointer"
1203 Enable, if the TPL stage should not inherit its initial
1204 stack-pointer from the settings for the SPL stage.
1206 config TPL_TEXT_BASE
1207 hex "Base address for the .text section of the TPL stage"
1208 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
1210 The base address for the .text section of the TPL stage.
1213 int "Maximum size (in bytes) for the TPL stage"
1217 The maximum size (in bytes) of the TPL stage.
1220 hex "Address of the initial stack-pointer for the TPL stage"
1221 depends on TPL_NEEDS_SEPARATE_STACK
1223 The address of the initial stack-pointer for the TPL stage.
1224 Usually this will be the (aligned) top-of-stack.
1226 config TPL_BOOTROM_SUPPORT
1227 bool "Support returning to the BOOTROM (from TPL)"
1229 Some platforms (e.g. the Rockchip RK3368) provide support in their
1230 ROM for loading the next boot-stage after performing basic setup
1233 Enable this option, to return to the BOOTROM through the
1234 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1235 boot device list, if not implemented for a given board)
1237 config TPL_DRIVERS_MISC_SUPPORT
1238 bool "Support misc drivers in TPL"
1240 Enable miscellaneous drivers in TPL. These drivers perform various
1241 tasks that don't fall nicely into other categories, Enable this
1242 option to build the drivers in drivers/misc as part of an TPL
1243 build, for those that support building in TPL (not all drivers do).
1245 config TPL_ENV_SUPPORT
1246 bool "Support an environment"
1248 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
1250 config TPL_GPIO_SUPPORT
1251 bool "Support GPIO in TPL"
1253 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1254 GPIOs allow U-Boot to read the state of an input line (high or
1255 low) and set the state of an output line. This can be used to
1256 drive LEDs, control power to various system parts and read user
1257 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1258 for example. Enable this option to build the drivers in
1259 drivers/gpio as part of an TPL build.
1261 config TPL_I2C_SUPPORT
1264 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
1267 config TPL_LIBCOMMON_SUPPORT
1268 bool "Support common libraries"
1270 Enable support for common U-Boot libraries within TPL. See
1271 SPL_LIBCOMMON_SUPPORT for details.
1273 config TPL_LIBGENERIC_SUPPORT
1274 bool "Support generic libraries"
1276 Enable support for generic U-Boot libraries within TPL. See
1277 SPL_LIBGENERIC_SUPPORT for details.
1279 config TPL_MPC8XXX_INIT_DDR_SUPPORT
1280 bool "Support MPC8XXX DDR init"
1282 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1283 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
1285 config TPL_MMC_SUPPORT
1289 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
1291 config TPL_NAND_SUPPORT
1292 bool "Support NAND flash"
1294 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
1297 bool "Support PCI drivers"
1299 Enable support for PCI in TPL. For platforms that need PCI to boot,
1300 or must perform some init using PCI in SPL, this provides the
1301 necessary driver support. This enables the drivers in drivers/pci
1302 as part of a TPL build.
1304 config TPL_PCH_SUPPORT
1305 bool "Support PCH drivers"
1307 Enable support for PCH (Platform Controller Hub) devices in TPL.
1308 These are used to set up GPIOs and the SPI peripheral early in
1309 boot. This enables the drivers in drivers/pch as part of a TPL
1312 config TPL_RAM_SUPPORT
1313 bool "Support booting from RAM"
1315 Enable booting of an image in RAM. The image can be preloaded or
1316 it can be loaded by TPL directly into RAM (e.g. using USB).
1318 config TPL_RAM_DEVICE
1319 bool "Support booting from preloaded image in RAM"
1320 depends on TPL_RAM_SUPPORT
1322 Enable booting of an image already loaded in RAM. The image has to
1323 be already in memory when TPL takes over, e.g. loaded by the boot
1326 config TPL_RTC_SUPPORT
1327 bool "Support RTC drivers"
1329 Enable RTC (Real-time Clock) support in TPL. This includes support
1330 for reading and setting the time. Some RTC devices also have some
1331 non-volatile (battery-backed) memory which is accessible if
1332 needed. This enables the drivers in drivers/rtc as part of an TPL
1335 config TPL_SERIAL_SUPPORT
1336 bool "Support serial"
1340 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
1343 config TPL_SPI_FLASH_SUPPORT
1344 bool "Support SPI flash drivers"
1346 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
1350 bool "Support loading from SPI flash"
1351 depends on TPL_SPI_FLASH_SUPPORT
1353 Enable support for loading next stage, U-Boot or otherwise, from
1354 SPI NOR in U-Boot TPL.
1356 config TPL_SPI_SUPPORT
1357 bool "Support SPI drivers"
1359 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
1362 config TPL_YMODEM_SUPPORT
1363 bool "Support loading using Ymodem"
1364 depends on TPL_SERIAL_SUPPORT
1366 While loading from serial is slow it can be a useful backup when
1367 there is no other option. The Ymodem protocol provides a reliable
1368 means of transmitting U-Boot over a serial line for using in TPL,
1369 with a checksum to ensure correctness.
1373 config SPL_AT91_MCK_BYPASS
1374 bool "Use external clock signal as a source of main clock for AT91 platforms"
1375 depends on ARCH_AT91
1378 Use external 8 to 24 Mhz clock signal as source of main clock instead
1379 of an external crystal oscillator.
1380 This option disables the internal driving on the XOUT pin.
1381 The external source has to provide a stable clock on the XIN pin.
1382 If this option is disabled, the SoC expects a crystal oscillator
1383 that needs driving on both XIN and XOUT lines.