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.
31 string "Linker script for the SPL stage"
32 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
34 The SPL stage will usually require a different linker-script
35 (as it runs from a different memory region) than the regular
36 U-Boot stage. Set this to the path of the linker-script to
40 bool "Call board-specific initialization in SPL"
42 If this option is enabled, U-Boot will call the function
43 spl_board_init() from board_init_r(). This function should be
44 provided by the board.
46 config SPL_BOOTROM_SUPPORT
47 bool "Support returning to the BOOTROM"
49 Some platforms (e.g. the Rockchip RK3368) provide support in their
50 ROM for loading the next boot-stage after performing basic setup
53 Enable this option, to return to the BOOTROM through the
54 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
55 boot device list, if not implemented for a given board)
57 config SPL_BOOTCOUNT_LIMIT
58 bool "Support bootcount in SPL"
59 depends on SPL_ENV_SUPPORT
61 On some boards, which use 'falcon' mode, it is necessary to check
62 and increment the number of boot attempts. Such boards do not
63 use proper U-Boot for normal boot flow and hence needs those
64 adjustments to be done in the SPL.
66 config SPL_RAW_IMAGE_SUPPORT
67 bool "Support SPL loading and booting of RAW images"
68 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
69 default y if !TI_SECURE_DEVICE
71 SPL will support loading and booting a RAW image when this option
72 is y. If this is not set, SPL will move on to other available
73 boot media to find a suitable image.
75 config SPL_LEGACY_IMAGE_SUPPORT
76 bool "Support SPL loading and booting of Legacy images"
77 default y if !TI_SECURE_DEVICE
79 SPL will support loading and booting Legacy images when this option
80 is y. If this is not set, SPL will move on to other available
81 boot media to find a suitable image.
83 config SPL_SYS_MALLOC_SIMPLE
85 prompt "Only use malloc_simple functions in the SPL"
87 Say Y here to only use the *_simple malloc functions from
88 malloc_simple.c, rather then using the versions from dlmalloc.c;
89 this will make the SPL binary smaller at the cost of more heap
90 usage as the *_simple malloc functions do not re-use free-ed mem.
92 config TPL_SYS_MALLOC_SIMPLE
94 prompt "Only use malloc_simple functions in the TPL"
96 Say Y here to only use the *_simple malloc functions from
97 malloc_simple.c, rather then using the versions from dlmalloc.c;
98 this will make the TPL binary smaller at the cost of more heap
99 usage as the *_simple malloc functions do not re-use free-ed mem.
102 bool "Enable SDRAM location for SPL stack"
104 SPL starts off execution in SRAM and thus typically has only a small
105 stack available. Since SPL sets up DRAM while in its board_init_f()
106 function, it is possible for the stack to move there before
107 board_init_r() is reached. This option enables a special SDRAM
108 location for the SPL stack. U-Boot SPL switches to this after
109 board_init_f() completes, and before board_init_r() starts.
111 config SPL_STACK_R_ADDR
112 depends on SPL_STACK_R
113 hex "SDRAM location for SPL stack"
114 default 0x82000000 if ARCH_OMAP2PLUS
116 Specify the address in SDRAM for the SPL stack. This will be set up
117 before board_init_r() is called.
119 config SPL_STACK_R_MALLOC_SIMPLE_LEN
120 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
121 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
124 Specify the amount of the stack to use as memory pool for
125 malloc_simple after switching the stack to DRAM. This may be set
126 to give board_init_r() a larger heap then the initial heap in
127 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
129 config SPL_SEPARATE_BSS
130 bool "BSS section is in a different memory region from text"
132 Some platforms need a large BSS region in SPL and can provide this
133 because RAM is already set up. In this case BSS can be moved to RAM.
134 This option should then be enabled so that the correct device tree
135 location is used. Normally we put the device tree at the end of BSS
136 but with this option enabled, it goes at _image_binary_end.
138 config SPL_DISABLE_BANNER_PRINT
139 bool "Disable output of the SPL banner 'U-Boot SPL ...'"
141 If this option is enabled, SPL will not print the banner with version
142 info. Selecting this option could be useful to reduce SPL boot time
143 (e.g. approx. 6 ms slower, when output on i.MX6 with 115200 baud).
145 config SPL_DISPLAY_PRINT
146 bool "Display a board-specific message in SPL"
148 If this option is enabled, U-Boot will call the function
149 spl_display_print() immediately after displaying the SPL console
150 banner ("U-Boot SPL ..."). This function should be provided by
153 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
154 bool "MMC raw mode: by sector"
155 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
156 ARCH_MX6 || ARCH_MX7 || \
157 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
158 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
159 OMAP44XX || OMAP54XX || AM33XX || AM43XX
161 Use sector number for specifying U-Boot location on MMC/SD in
164 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
165 hex "Address on the MMC to load U-Boot from"
166 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
167 default 0x50 if ARCH_SUNXI
168 default 0x75 if ARCH_DAVINCI
169 default 0x8a if ARCH_MX6 || ARCH_MX7
170 default 0x100 if ARCH_UNIPHIER
171 default 0x140 if ARCH_MVEBU
172 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
173 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
174 OMAP54XX || AM33XX || AM43XX
175 default 0x4000 if ARCH_ROCKCHIP
177 Address on the MMC to load U-Boot from, when the MMC is being used
178 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
180 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
181 bool "MMC Raw mode: by partition"
183 Use a partition for loading U-Boot when using MMC/SD in raw mode.
185 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
186 hex "Partition to use to load U-Boot from"
187 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
190 Partition on the MMC to load U-Boot from when the MMC is being
193 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
194 bool "MMC raw mode: by partition type"
195 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
197 Use partition type for specifying U-Boot partition on MMC/SD in
198 raw mode. U-Boot will be loaded from the first partition of this
201 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
202 hex "Partition Type on the MMC to load U-Boot from"
203 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
205 Partition Type on the MMC to load U-Boot from, when the MMC is being
208 config SPL_CRC32_SUPPORT
212 Enable this to support CRC32 in FIT images within SPL. This is a
213 32-bit checksum value that can be used to verify images. This is
214 the least secure type of checksum, suitable for detected
215 accidental image corruption. For secure applications you should
216 consider SHA1 or SHA256.
218 config SPL_MD5_SUPPORT
222 Enable this to support MD5 in FIT images within SPL. An MD5
223 checksum is a 128-bit hash value used to check that the image
224 contents have not been corrupted. Note that MD5 is not considered
225 secure as it is possible (with a brute-force attack) to adjust the
226 image while still retaining the same MD5 hash value. For secure
227 applications where images may be changed maliciously, you should
228 consider SHA1 or SHA256.
230 config SPL_SHA1_SUPPORT
235 Enable this to support SHA1 in FIT images within SPL. A SHA1
236 checksum is a 160-bit (20-byte) hash value used to check that the
237 image contents have not been corrupted or maliciously altered.
238 While SHA1 is fairly secure it is coming to the end of its life
239 due to the expanding computing power avaiable to brute-force
240 attacks. For more security, consider SHA256.
242 config SPL_SHA256_SUPPORT
243 bool "Support SHA256"
247 Enable this to support SHA256 in FIT images within SPL. A SHA256
248 checksum is a 256-bit (32-byte) hash value used to check that the
249 image contents have not been corrupted. SHA256 is recommended for
250 use in secure applications since (as at 2016) there is no known
251 feasible attack that could produce a 'collision' with differing
252 input data. Use this for the highest security. Note that only the
253 SHA256 variant is supported: SHA512 and others are not currently
256 config SPL_FIT_IMAGE_TINY
257 bool "Remove functionality from SPL FIT loading to reduce size"
259 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
261 Enable this to reduce the size of the FIT image loading code
262 in SPL, if space for the SPL binary is very tight.
264 This removes the detection of image types (which forces the
265 first image to be treated as having a U-Boot style calling
266 convention) and skips the recording of each loaded payload
267 (i.e. loadable) into the FDT (modifying the loaded FDT to
268 ensure this information is available to the next image
271 config SPL_CPU_SUPPORT
272 bool "Support CPU drivers"
274 Enable this to support CPU drivers in SPL. These drivers can set
275 up CPUs and provide information about them such as the model and
276 name. This can be useful in SPL since setting up the CPUs earlier
277 may improve boot performance. Enable this option to build the
278 drivers in drivers/cpu as part of an SPL build.
280 config SPL_CRYPTO_SUPPORT
281 bool "Support crypto drivers"
283 Enable crypto drivers in SPL. These drivers can be used to
284 accelerate secure boot processing in secure applications. Enable
285 this option to build the drivers in drivers/crypto as part of an
288 config SPL_HASH_SUPPORT
289 bool "Support hashing drivers"
293 Enable hashing drivers in SPL. These drivers can be used to
294 accelerate secure boot processing in secure applications. Enable
295 this option to build system-specific drivers for hash acceleration
296 as part of an SPL build.
298 config SPL_DMA_SUPPORT
299 bool "Support DMA drivers"
301 Enable DMA (direct-memory-access) drivers in SPL. These drivers
302 can be used to handle memory-to-peripheral data transfer without
303 the CPU moving the data. Enable this option to build the drivers
304 in drivers/dma as part of an SPL build.
306 config SPL_DRIVERS_MISC_SUPPORT
307 bool "Support misc drivers"
309 Enable miscellaneous drivers in SPL. These drivers perform various
310 tasks that don't fall nicely into other categories, Enable this
311 option to build the drivers in drivers/misc as part of an SPL
312 build, for those that support building in SPL (not all drivers do).
314 config SPL_ENV_SUPPORT
315 bool "Support an environment"
317 Enable environment support in SPL. The U-Boot environment provides
318 a number of settings (essentially name/value pairs) which can
319 control many aspects of U-Boot's operation. Normally this is not
320 needed in SPL as it has a much simpler task with less
321 configuration. But some boards use this to support 'Falcon' boot
322 on EXT2 and FAT, where SPL boots directly into Linux without
323 starting U-Boot first. Enabling this option will make env_get()
324 and env_set() available in SPL.
327 bool "Support save environment"
328 depends on SPL_ENV_SUPPORT
329 select SPL_MMC_WRITE if ENV_IS_IN_MMC
331 Enable save environment support in SPL after setenv. By default
332 the saveenv option is not provided in SPL, but some boards need
333 this support in 'Falcon' boot, where SPL need to boot from
334 different images based on environment variable set by OS. For
335 example OS may set "reboot_image" environment variable to
336 "recovery" inorder to boot recovery image by SPL. The SPL read
337 "reboot_image" and act accordingly and change the reboot_image
338 to default mode using setenv and save the environment.
340 config SPL_ETH_SUPPORT
341 bool "Support Ethernet"
342 depends on SPL_ENV_SUPPORT
344 Enable access to the network subsystem and associated Ethernet
345 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
346 link rather than from an on-board peripheral. Environment support
347 is required since the network stack uses a number of environment
348 variables. See also SPL_NET_SUPPORT.
350 config SPL_EXT_SUPPORT
351 bool "Support EXT filesystems"
353 Enable support for EXT2/3/4 filesystems with SPL. This permits
354 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
355 filesystem from within SPL. Support for the underlying block
356 device (e.g. MMC or USB) must be enabled separately.
358 config SPL_FAT_SUPPORT
359 bool "Support FAT filesystems"
362 Enable support for FAT and VFAT filesystems with SPL. This
363 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
364 filesystem from within SPL. Support for the underlying block
365 device (e.g. MMC or USB) must be enabled separately.
367 config SPL_FPGA_SUPPORT
370 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
371 provide software-configurable hardware which is typically used to
372 implement peripherals (such as UARTs, LCD displays, MMC) or
373 accelerate custom processing functions, such as image processing
374 or machine learning. Sometimes it is useful to program the FPGA
375 as early as possible during boot, and this option can enable that
378 config SPL_GPIO_SUPPORT
381 Enable support for GPIOs (General-purpose Input/Output) in SPL.
382 GPIOs allow U-Boot to read the state of an input line (high or
383 low) and set the state of an output line. This can be used to
384 drive LEDs, control power to various system parts and read user
385 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
386 for example. Enable this option to build the drivers in
387 drivers/gpio as part of an SPL build.
389 config SPL_I2C_SUPPORT
392 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
393 I2C works with a clock and data line which can be driven by a
394 one or more masters or slaves. It is a fairly complex bus but is
395 widely used as it only needs two lines for communication. Speeds of
396 400kbps are typical but up to 3.4Mbps is supported by some
397 hardware. I2C can be useful in SPL to configure power management
398 ICs (PMICs) before raising the CPU clock speed, for example.
399 Enable this option to build the drivers in drivers/i2c as part of
402 config SPL_LIBCOMMON_SUPPORT
403 bool "Support common libraries"
405 Enable support for common U-Boot libraries within SPL. These
406 libraries include common code to deal with U-Boot images,
407 environment and USB, for example. This option is enabled on many
408 boards. Enable this option to build the code in common/ as part of
411 config SPL_LIBDISK_SUPPORT
412 bool "Support disk paritions"
414 Enable support for disk partitions within SPL. 'Disk' is something
415 of a misnomer as it includes non-spinning media such as flash (as
416 used in MMC and USB sticks). Partitions provide a way for a disk
417 to be split up into separate regions, with a partition table placed
418 at the start or end which describes the location and size of each
419 'partition'. These partitions are typically uses as individual block
420 devices, typically with an EXT2 or FAT filesystem in each. This
421 option enables whatever partition support has been enabled in
422 U-Boot to also be used in SPL. It brings in the code in disk/.
424 config SPL_LIBGENERIC_SUPPORT
425 bool "Support generic libraries"
427 Enable support for generic U-Boot libraries within SPL. These
428 libraries include generic code to deal with device tree, hashing,
429 printf(), compression and the like. This option is enabled on many
430 boards. Enable this option to build the code in lib/ as part of an
433 config SPL_MMC_SUPPORT
437 Enable support for MMC (Multimedia Card) within SPL. This enables
438 the MMC protocol implementation and allows any enabled drivers to
439 be used within SPL. MMC can be used with or without disk partition
440 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
441 this option to build the drivers in drivers/mmc as part of an SPL
445 bool "MMC/SD/SDIO card support for write operations in SPL"
446 depends on SPL_MMC_SUPPORT
449 Enable write access to MMC and SD Cards in SPL
452 config SPL_MPC8XXX_INIT_DDR_SUPPORT
453 bool "Support MPC8XXX DDR init"
455 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
456 random-access memory) on the MPC8XXX family within SPL. This
457 allows DRAM to be set up before loading U-Boot into that DRAM,
460 config SPL_MTD_SUPPORT
461 bool "Support MTD drivers"
463 Enable support for MTD (Memory Technology Device) within SPL. MTD
464 provides a block interface over raw NAND and can also be used with
465 SPI flash. This allows SPL to load U-Boot from supported MTD
466 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
467 to enable specific MTD drivers.
469 config SPL_MUSB_NEW_SUPPORT
470 bool "Support new Mentor Graphics USB"
472 Enable support for Mentor Graphics USB in SPL. This is a new
473 driver used by some boards. Enable this option to build
474 the drivers in drivers/usb/musb-new as part of an SPL build. The
475 old drivers are in drivers/usb/musb.
477 config SPL_NAND_SUPPORT
478 bool "Support NAND flash"
480 Enable support for NAND (Negative AND) flash in SPL. NAND flash
481 can be used to allow SPL to load U-Boot from supported devices.
482 This enables the drivers in drivers/mtd/nand as part of an SPL
485 config SPL_NET_SUPPORT
486 bool "Support networking"
488 Enable support for network devices (such as Ethernet) in SPL.
489 This permits SPL to load U-Boot over a network link rather than
490 from an on-board peripheral. Environment support is required since
491 the network stack uses a number of environment variables. See also
495 config SPL_NET_VCI_STRING
496 string "BOOTP Vendor Class Identifier string sent by SPL"
498 As defined by RFC 2132 the vendor class identifier field can be
499 sent by the client to identify the vendor type and configuration
500 of a client. This is often used in practice to allow for the DHCP
501 server to specify different files to load depending on if the ROM,
502 SPL or U-Boot itself makes the request
503 endif # if SPL_NET_SUPPORT
505 config SPL_NO_CPU_SUPPORT
506 bool "Drop CPU code in SPL"
508 This is specific to the ARM926EJ-S CPU. It disables the standard
509 start.S start-up code, presumably so that a replacement can be
510 used on that CPU. You should not enable it unless you know what
513 config SPL_NOR_SUPPORT
514 bool "Support NOR flash"
516 Enable support for loading U-Boot from memory-mapped NOR (Negative
517 OR) flash in SPL. NOR flash is slow to write but fast to read, and
518 a memory-mapped device makes it very easy to access. Loading from
519 NOR is typically achieved with just a memcpy().
521 config SPL_XIP_SUPPORT
525 Enable support for execute in place of U-Boot or kernel image. There
526 is no need to copy image from flash to ram if flash supports execute
527 in place. Its very useful in systems having enough flash but not
528 enough ram to load the image.
530 config SPL_ONENAND_SUPPORT
531 bool "Support OneNAND flash"
533 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
534 a type of NAND flash and therefore can be used to allow SPL to
535 load U-Boot from supported devices. This enables the drivers in
536 drivers/mtd/onenand as part of an SPL build.
539 bool "Activate Falcon Mode"
540 depends on !TI_SECURE_DEVICE
543 Enable booting directly to an OS from SPL.
544 for more info read doc/README.falcon
548 hex "addr, where OS is found"
549 depends on SPL_NOR_SUPPORT
551 Specify the address, where the OS image is found, which
558 default "tpl/u-boot-with-tpl.bin" if TPL
561 Payload for SPL boot. For backward compability, default to
562 u-boot.bin, i.e. RAW image without any header. In case of
563 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
566 config SPL_PCI_SUPPORT
567 bool "Support PCI drivers"
569 Enable support for PCI in SPL. For platforms that need PCI to boot,
570 or must perform some init using PCI in SPL, this provides the
571 necessary driver support. This enables the drivers in drivers/pci
572 as part of an SPL build.
574 config SPL_PCH_SUPPORT
575 bool "Support PCH drivers"
577 Enable support for PCH (Platform Controller Hub) devices in SPL.
578 These are used to set up GPIOs and the SPI peripheral early in
579 boot. This enables the drivers in drivers/pch as part of an SPL
582 config SPL_POST_MEM_SUPPORT
583 bool "Support POST drivers"
585 Enable support for POST (Power-on Self Test) in SPL. POST is a
586 procedure that checks that the hardware (CPU or board) appears to
587 be functionally correctly. It is a sanity check that can be
588 performed before booting. This enables the drivers in post/drivers
589 as part of an SPL build.
592 bool "Support reset drivers"
595 Enable support for reset control in SPL.
596 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
597 by using the generic reset API provided by driver model.
598 This enables the drivers in drivers/reset as part of an SPL build.
600 config SPL_POWER_SUPPORT
601 bool "Support power drivers"
603 Enable support for power control in SPL. This includes support
604 for PMICs (Power-management Integrated Circuits) and some of the
605 features provided by PMICs. In particular, voltage regulators can
606 be used to enable/disable power and vary its voltage. That can be
607 useful in SPL to turn on boot peripherals and adjust CPU voltage
608 so that the clock speed can be increased. This enables the drivers
609 in drivers/power, drivers/power/pmic and drivers/power/regulator
610 as part of an SPL build.
612 config SPL_POWER_DOMAIN
613 bool "Support power domain drivers"
615 Enable support for power domain control in SPL. Many SoCs allow
616 power to be applied to or removed from portions of the SoC (power
617 domains). This may be used to save power. This API provides the
618 means to control such power management hardware. This enables
619 the drivers in drivers/power/domain as part of a SPL build.
621 config SPL_RAM_SUPPORT
622 bool "Support booting from RAM"
623 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
625 Enable booting of an image in RAM. The image can be preloaded or
626 it can be loaded by SPL directly into RAM (e.g. using USB).
628 config SPL_RAM_DEVICE
629 bool "Support booting from preloaded image in RAM"
630 depends on SPL_RAM_SUPPORT
631 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
633 Enable booting of an image already loaded in RAM. The image has to
634 be already in memory when SPL takes over, e.g. loaded by the boot
637 config SPL_RTC_SUPPORT
638 bool "Support RTC drivers"
640 Enable RTC (Real-time Clock) support in SPL. This includes support
641 for reading and setting the time. Some RTC devices also have some
642 non-volatile (battery-backed) memory which is accessible if
643 needed. This enables the drivers in drivers/rtc as part of an SPL
646 config SPL_SATA_SUPPORT
647 bool "Support loading from SATA"
649 Enable support for SATA (Serial AT attachment) in SPL. This allows
650 use of SATA devices such as hard drives and flash drivers for
651 loading U-Boot. SATA is used in higher-end embedded systems and
652 can provide higher performance than MMC , at somewhat higher
653 expense and power consumption. This enables loading from SATA
654 using a configured device.
656 config SPL_SERIAL_SUPPORT
657 bool "Support serial"
661 Enable support for serial in SPL. This allows use of a serial UART
662 for displaying messages while SPL is running. It also brings in
663 printf() and panic() functions. This should normally be enabled
664 unless there are space reasons not to. Even then, consider
665 enabling USE_TINY_PRINTF which is a small printf() version.
667 config SPL_SPI_FLASH_SUPPORT
668 bool "Support SPI flash drivers"
670 Enable support for using SPI flash in SPL, and loading U-Boot from
671 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
672 the SPI bus that is used to connect it to a system. It is a simple
673 but fast bidirectional 4-wire bus (clock, chip select and two data
674 lines). This enables the drivers in drivers/mtd/spi as part of an
675 SPL build. This normally requires SPL_SPI_SUPPORT.
678 bool "Support loading from SPI flash"
679 depends on SPL_SPI_FLASH_SUPPORT
681 Enable support for loading next stage, U-Boot or otherwise, from
682 SPI NOR in U-Boot SPL.
684 config SPL_SPI_SUPPORT
685 bool "Support SPI drivers"
687 Enable support for using SPI in SPL. This is used for connecting
688 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
689 more details on that. The SPI driver provides the transport for
690 data between the SPI flash and the CPU. This option can be used to
691 enable SPI drivers that are needed for other purposes also, such
695 bool "Driver support for thermal devices"
697 Enable support for temperature-sensing devices. Some SoCs have on-chip
698 temperature sensors to permit warnings, speed throttling or even
699 automatic power-off when the temperature gets too high or low. Other
700 devices may be discrete but connected on a suitable bus.
702 config SPL_USB_HOST_SUPPORT
703 bool "Support USB host drivers"
705 Enable access to USB (Universal Serial Bus) host devices so that
706 SPL can load U-Boot from a connected USB peripheral, such as a USB
707 flash stick. While USB takes a little longer to start up than most
708 buses, it is very flexible since many different types of storage
709 device can be attached. This option enables the drivers in
710 drivers/usb/host as part of an SPL build.
712 config SPL_USB_SUPPORT
713 bool "Support loading from USB"
714 depends on SPL_USB_HOST_SUPPORT
716 Enable support for USB devices in SPL. This allows use of USB
717 devices such as hard drives and flash drivers for loading U-Boot.
718 The actual drivers are enabled separately using the normal U-Boot
719 config options. This enables loading from USB using a configured
722 config SPL_USB_GADGET_SUPPORT
723 bool "Suppport USB Gadget drivers"
725 Enable USB Gadget API which allows to enable USB device functions
728 if SPL_USB_GADGET_SUPPORT
731 bool "Support USB Ethernet drivers"
733 Enable access to the USB network subsystem and associated
734 drivers in SPL. This permits SPL to load U-Boot over a
735 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
736 than from an onboard peripheral. Environment support is required
737 since the network stack uses a number of environment variables.
738 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
740 config SPL_DFU_SUPPORT
741 bool "Support DFU (Device Firmware Upgarde)"
742 select SPL_HASH_SUPPORT
743 select SPL_DFU_NO_RESET
744 depends on SPL_RAM_SUPPORT
746 This feature enables the DFU (Device Firmware Upgarde) in SPL with
747 RAM memory device support. The ROM code will load and execute
748 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
749 selected device partition from host-pc using dfu-utils.
750 This feature is useful to flash the binaries to factory or bare-metal
751 boards using USB interface.
754 bool "DFU device selection"
755 depends on SPL_DFU_SUPPORT
759 depends on SPL_DFU_SUPPORT && SPL_RAM_SUPPORT
761 select RAM/DDR memory device for loading binary images
762 (u-boot/kernel) to the selected device partition using
763 DFU and execute the u-boot/kernel from RAM.
767 config SPL_USB_SDP_SUPPORT
768 bool "Support SDP (Serial Download Protocol)"
770 Enable Serial Download Protocol (SDP) device support in SPL. This
771 allows to download images into memory and execute (jump to) them
772 using the same protocol as implemented by the i.MX family's boot ROM.
775 config SPL_WATCHDOG_SUPPORT
776 bool "Support watchdog drivers"
778 Enable support for watchdog drivers in SPL. A watchdog is
779 typically a hardware peripheral which can reset the system when it
780 detects no activity for a while (such as a software crash). This
781 enables the drivers in drivers/watchdog as part of an SPL build.
783 config SPL_YMODEM_SUPPORT
784 bool "Support loading using Ymodem"
785 depends on SPL_SERIAL_SUPPORT
787 While loading from serial is slow it can be a useful backup when
788 there is no other option. The Ymodem protocol provides a reliable
789 means of transmitting U-Boot over a serial line for using in SPL,
790 with a checksum to ensure correctness.
793 bool "Support ARM Trusted Firmware"
796 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
797 is loaded by SPL (which is considered as BL2 in ATF terminology).
798 More detail at: https://github.com/ARM-software/arm-trusted-firmware
800 config SPL_ATF_NO_PLATFORM_PARAM
801 bool "Pass no platform parameter"
804 While we expect to call a pointer to a valid FDT (or NULL)
805 as the platform parameter to an ATF, some ATF versions are
806 not U-Boot aware and have an insufficiently robust parameter
807 validation to gracefully reject a FDT being passed.
809 If this option is enabled, the spl_atf os-type handler will
810 always pass NULL for the platform parameter.
812 If your ATF is affected, say Y.
814 config SPL_AM33XX_ENABLE_RTC32K_OSC
815 bool "Enable the RTC32K OSC on AM33xx based platforms"
818 Enable access to the AM33xx RTC and select the external 32kHz clock
823 depends on SUPPORT_TPL
826 If you want to build TPL as well as the normal image and SPL, say Y.
830 config TPL_BOARD_INIT
831 bool "Call board-specific initialization in TPL"
833 If this option is enabled, U-Boot will call the function
834 spl_board_init() from board_init_r(). This function should be
835 provided by the board.
838 string "Linker script for the TPL stage"
841 The TPL stage will usually require a different linker-script
842 (as it runs from a different memory region) than the regular
843 U-Boot stage. Set this to the path of the linker-script to
846 May be left empty to trigger the Makefile infrastructure to
847 fall back to the linker-script used for the SPL stage.
849 config TPL_NEEDS_SEPARATE_TEXT_BASE
850 bool "TPL needs a separate text-base"
854 Enable, if the TPL stage should not inherit its text-base
855 from the SPL stage. When enabled, a base address for the
856 .text sections of the TPL stage has to be set below.
858 config TPL_NEEDS_SEPARATE_STACK
859 bool "TPL needs a separate initial stack-pointer"
863 Enable, if the TPL stage should not inherit its initial
864 stack-pointer from the settings for the SPL stage.
867 hex "Base address for the .text section of the TPL stage"
868 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
870 The base address for the .text section of the TPL stage.
873 int "Maximum size (in bytes) for the TPL stage"
877 The maximum size (in bytes) of the TPL stage.
880 hex "Address of the initial stack-pointer for the TPL stage"
881 depends on TPL_NEEDS_SEPARATE_STACK
883 The address of the initial stack-pointer for the TPL stage.
884 Usually this will be the (aligned) top-of-stack.
886 config TPL_BOOTROM_SUPPORT
887 bool "Support returning to the BOOTROM (from TPL)"
889 Some platforms (e.g. the Rockchip RK3368) provide support in their
890 ROM for loading the next boot-stage after performing basic setup
893 Enable this option, to return to the BOOTROM through the
894 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
895 boot device list, if not implemented for a given board)
897 config TPL_DRIVERS_MISC_SUPPORT
898 bool "Support misc drivers in TPL"
900 Enable miscellaneous drivers in TPL. These drivers perform various
901 tasks that don't fall nicely into other categories, Enable this
902 option to build the drivers in drivers/misc as part of an TPL
903 build, for those that support building in TPL (not all drivers do).
905 config TPL_ENV_SUPPORT
906 bool "Support an environment"
908 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
910 config TPL_I2C_SUPPORT
913 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
916 config TPL_LIBCOMMON_SUPPORT
917 bool "Support common libraries"
919 Enable support for common U-Boot libraries within TPL. See
920 SPL_LIBCOMMON_SUPPORT for details.
922 config TPL_LIBGENERIC_SUPPORT
923 bool "Support generic libraries"
925 Enable support for generic U-Boot libraries within TPL. See
926 SPL_LIBGENERIC_SUPPORT for details.
928 config TPL_MPC8XXX_INIT_DDR_SUPPORT
929 bool "Support MPC8XXX DDR init"
931 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
932 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
934 config TPL_MMC_SUPPORT
938 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
940 config TPL_NAND_SUPPORT
941 bool "Support NAND flash"
943 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
945 config TPL_RAM_SUPPORT
946 bool "Support booting from RAM"
948 Enable booting of an image in RAM. The image can be preloaded or
949 it can be loaded by TPL directly into RAM (e.g. using USB).
951 config TPL_RAM_DEVICE
952 bool "Support booting from preloaded image in RAM"
953 depends on TPL_RAM_SUPPORT
955 Enable booting of an image already loaded in RAM. The image has to
956 be already in memory when TPL takes over, e.g. loaded by the boot
959 config TPL_SERIAL_SUPPORT
960 bool "Support serial"
964 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
967 config TPL_SPI_FLASH_SUPPORT
968 bool "Support SPI flash drivers"
970 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
974 bool "Support loading from SPI flash"
975 depends on TPL_SPI_FLASH_SUPPORT
977 Enable support for loading next stage, U-Boot or otherwise, from
978 SPI NOR in U-Boot TPL.
980 config TPL_SPI_SUPPORT
981 bool "Support SPI drivers"
983 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
986 config TPL_YMODEM_SUPPORT
987 bool "Support loading using Ymodem"
988 depends on TPL_SERIAL_SUPPORT
990 While loading from serial is slow it can be a useful backup when
991 there is no other option. The Ymodem protocol provides a reliable
992 means of transmitting U-Boot over a serial line for using in TPL,
993 with a checksum to ensure correctness.