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_RAW_IMAGE_SUPPORT
58 bool "Support SPL loading and booting of RAW images"
59 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
60 default y if !TI_SECURE_DEVICE
62 SPL will support loading and booting a RAW image when this option
63 is y. If this is not set, SPL will move on to other available
64 boot media to find a suitable image.
66 config SPL_LEGACY_IMAGE_SUPPORT
67 bool "Support SPL loading and booting of Legacy images"
68 default y if !TI_SECURE_DEVICE
70 SPL will support loading and booting Legacy images when this option
71 is y. If this is not set, SPL will move on to other available
72 boot media to find a suitable image.
74 config SPL_SYS_MALLOC_SIMPLE
76 prompt "Only use malloc_simple functions in the SPL"
78 Say Y here to only use the *_simple malloc functions from
79 malloc_simple.c, rather then using the versions from dlmalloc.c;
80 this will make the SPL binary smaller at the cost of more heap
81 usage as the *_simple malloc functions do not re-use free-ed mem.
83 config TPL_SYS_MALLOC_SIMPLE
85 prompt "Only use malloc_simple functions in the TPL"
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 TPL binary smaller at the cost of more heap
90 usage as the *_simple malloc functions do not re-use free-ed mem.
93 bool "Enable SDRAM location for SPL stack"
95 SPL starts off execution in SRAM and thus typically has only a small
96 stack available. Since SPL sets up DRAM while in its board_init_f()
97 function, it is possible for the stack to move there before
98 board_init_r() is reached. This option enables a special SDRAM
99 location for the SPL stack. U-Boot SPL switches to this after
100 board_init_f() completes, and before board_init_r() starts.
102 config SPL_STACK_R_ADDR
103 depends on SPL_STACK_R
104 hex "SDRAM location for SPL stack"
105 default 0x82000000 if ARCH_OMAP2PLUS
107 Specify the address in SDRAM for the SPL stack. This will be set up
108 before board_init_r() is called.
110 config SPL_STACK_R_MALLOC_SIMPLE_LEN
111 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
112 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
115 Specify the amount of the stack to use as memory pool for
116 malloc_simple after switching the stack to DRAM. This may be set
117 to give board_init_r() a larger heap then the initial heap in
118 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
120 config SPL_SEPARATE_BSS
121 bool "BSS section is in a different memory region from text"
123 Some platforms need a large BSS region in SPL and can provide this
124 because RAM is already set up. In this case BSS can be moved to RAM.
125 This option should then be enabled so that the correct device tree
126 location is used. Normally we put the device tree at the end of BSS
127 but with this option enabled, it goes at _image_binary_end.
129 config SPL_DISABLE_BANNER_PRINT
130 bool "Disable output of the SPL banner 'U-Boot SPL ...'"
132 If this option is enabled, SPL will not print the banner with version
133 info. Selecting this option could be useful to reduce SPL boot time
134 (e.g. approx. 6 ms slower, when output on i.MX6 with 115200 baud).
136 config SPL_DISPLAY_PRINT
137 bool "Display a board-specific message in SPL"
139 If this option is enabled, U-Boot will call the function
140 spl_display_print() immediately after displaying the SPL console
141 banner ("U-Boot SPL ..."). This function should be provided by
144 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
145 bool "MMC raw mode: by sector"
146 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER ||ARCH_MX6 || \
147 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
148 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
149 OMAP44XX || OMAP54XX || AM33XX || AM43XX
151 Use sector number for specifying U-Boot location on MMC/SD in
154 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
155 hex "Address on the MMC to load U-Boot from"
156 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
157 default 0x50 if ARCH_SUNXI
158 default 0x75 if ARCH_DAVINCI
159 default 0x8a if ARCH_MX6
160 default 0x100 if ARCH_UNIPHIER
161 default 0x140 if ARCH_MVEBU
162 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
163 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
164 OMAP54XX || AM33XX || AM43XX
165 default 0x4000 if ARCH_ROCKCHIP
167 Address on the MMC to load U-Boot from, when the MMC is being used
168 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
170 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
171 bool "MMC Raw mode: by partition"
173 Use a partition for loading U-Boot when using MMC/SD in raw mode.
175 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
176 hex "Partition to use to load U-Boot from"
177 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
180 Partition on the MMC to load U-Boot from when the MMC is being
183 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
184 bool "MMC raw mode: by partition type"
185 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
187 Use partition type for specifying U-Boot partition on MMC/SD in
188 raw mode. U-Boot will be loaded from the first partition of this
191 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
192 hex "Partition Type on the MMC to load U-Boot from"
193 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
195 Partition Type on the MMC to load U-Boot from, when the MMC is being
198 config SPL_CRC32_SUPPORT
202 Enable this to support CRC32 in FIT images within SPL. This is a
203 32-bit checksum value that can be used to verify images. This is
204 the least secure type of checksum, suitable for detected
205 accidental image corruption. For secure applications you should
206 consider SHA1 or SHA256.
208 config SPL_MD5_SUPPORT
212 Enable this to support MD5 in FIT images within SPL. An MD5
213 checksum is a 128-bit hash value used to check that the image
214 contents have not been corrupted. Note that MD5 is not considered
215 secure as it is possible (with a brute-force attack) to adjust the
216 image while still retaining the same MD5 hash value. For secure
217 applications where images may be changed maliciously, you should
218 consider SHA1 or SHA256.
220 config SPL_SHA1_SUPPORT
225 Enable this to support SHA1 in FIT images within SPL. A SHA1
226 checksum is a 160-bit (20-byte) hash value used to check that the
227 image contents have not been corrupted or maliciously altered.
228 While SHA1 is fairly secure it is coming to the end of its life
229 due to the expanding computing power avaiable to brute-force
230 attacks. For more security, consider SHA256.
232 config SPL_SHA256_SUPPORT
233 bool "Support SHA256"
237 Enable this to support SHA256 in FIT images within SPL. A SHA256
238 checksum is a 256-bit (32-byte) hash value used to check that the
239 image contents have not been corrupted. SHA256 is recommended for
240 use in secure applications since (as at 2016) there is no known
241 feasible attack that could produce a 'collision' with differing
242 input data. Use this for the highest security. Note that only the
243 SHA256 variant is supported: SHA512 and others are not currently
246 config SPL_FIT_IMAGE_TINY
247 bool "Remove functionality from SPL FIT loading to reduce size"
249 default y if MACH_SUN50I || MACH_SUN50I_H5
251 Enable this to reduce the size of the FIT image loading code
252 in SPL, if space for the SPL binary is very tight.
254 This removes the detection of image types (which forces the
255 first image to be treated as having a U-Boot style calling
256 convention) and skips the recording of each loaded payload
257 (i.e. loadable) into the FDT (modifying the loaded FDT to
258 ensure this information is available to the next image
261 config SPL_CPU_SUPPORT
262 bool "Support CPU drivers"
264 Enable this to support CPU drivers in SPL. These drivers can set
265 up CPUs and provide information about them such as the model and
266 name. This can be useful in SPL since setting up the CPUs earlier
267 may improve boot performance. Enable this option to build the
268 drivers in drivers/cpu as part of an SPL build.
270 config SPL_CRYPTO_SUPPORT
271 bool "Support crypto drivers"
273 Enable crypto drivers in SPL. These drivers can be used to
274 accelerate secure boot processing in secure applications. Enable
275 this option to build the drivers in drivers/crypto as part of an
278 config SPL_HASH_SUPPORT
279 bool "Support hashing drivers"
283 Enable hashing drivers in SPL. These drivers can be used to
284 accelerate secure boot processing in secure applications. Enable
285 this option to build system-specific drivers for hash acceleration
286 as part of an SPL build.
288 config SPL_DMA_SUPPORT
289 bool "Support DMA drivers"
291 Enable DMA (direct-memory-access) drivers in SPL. These drivers
292 can be used to handle memory-to-peripheral data transfer without
293 the CPU moving the data. Enable this option to build the drivers
294 in drivers/dma as part of an SPL build.
296 config SPL_DRIVERS_MISC_SUPPORT
297 bool "Support misc drivers"
299 Enable miscellaneous drivers in SPL. These drivers perform various
300 tasks that don't fall nicely into other categories, Enable this
301 option to build the drivers in drivers/misc as part of an SPL
302 build, for those that support building in SPL (not all drivers do).
304 config SPL_ENV_SUPPORT
305 bool "Support an environment"
307 Enable environment support in SPL. The U-Boot environment provides
308 a number of settings (essentially name/value pairs) which can
309 control many aspects of U-Boot's operation. Normally this is not
310 needed in SPL as it has a much simpler task with less
311 configuration. But some boards use this to support 'Falcon' boot
312 on EXT2 and FAT, where SPL boots directly into Linux without
313 starting U-Boot first. Enabling this option will make env_get()
314 and env_set() available in SPL.
317 bool "Support save environment"
318 depends on SPL_ENV_SUPPORT
319 select SPL_MMC_WRITE if ENV_IS_IN_MMC
321 Enable save environment support in SPL after setenv. By default
322 the saveenv option is not provided in SPL, but some boards need
323 this support in 'Falcon' boot, where SPL need to boot from
324 different images based on environment variable set by OS. For
325 example OS may set "reboot_image" environment variable to
326 "recovery" inorder to boot recovery image by SPL. The SPL read
327 "reboot_image" and act accordingly and change the reboot_image
328 to default mode using setenv and save the environemnt.
330 config SPL_ETH_SUPPORT
331 bool "Support Ethernet"
332 depends on SPL_ENV_SUPPORT
334 Enable access to the network subsystem and associated Ethernet
335 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
336 link rather than from an on-board peripheral. Environment support
337 is required since the network stack uses a number of environment
338 variables. See also SPL_NET_SUPPORT.
340 config SPL_EXT_SUPPORT
341 bool "Support EXT filesystems"
343 Enable support for EXT2/3/4 filesystems with SPL. This permits
344 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
345 filesystem from within SPL. Support for the underlying block
346 device (e.g. MMC or USB) must be enabled separately.
348 config SPL_FAT_SUPPORT
349 bool "Support FAT filesystems"
352 Enable support for FAT and VFAT filesystems with SPL. This
353 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
354 filesystem from within SPL. Support for the underlying block
355 device (e.g. MMC or USB) must be enabled separately.
357 config SPL_FPGA_SUPPORT
360 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
361 provide software-configurable hardware which is typically used to
362 implement peripherals (such as UARTs, LCD displays, MMC) or
363 accelerate custom processing functions, such as image processing
364 or machine learning. Sometimes it is useful to program the FPGA
365 as early as possible during boot, and this option can enable that
368 config SPL_GPIO_SUPPORT
371 Enable support for GPIOs (General-purpose Input/Output) in SPL.
372 GPIOs allow U-Boot to read the state of an input line (high or
373 low) and set the state of an output line. This can be used to
374 drive LEDs, control power to various system parts and read user
375 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
376 for example. Enable this option to build the drivers in
377 drivers/gpio as part of an SPL build.
379 config SPL_I2C_SUPPORT
382 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
383 I2C works with a clock and data line which can be driven by a
384 one or more masters or slaves. It is a fairly complex bus but is
385 widely used as it only needs two lines for communication. Speeds of
386 400kbps are typical but up to 3.4Mbps is supported by some
387 hardware. I2C can be useful in SPL to configure power management
388 ICs (PMICs) before raising the CPU clock speed, for example.
389 Enable this option to build the drivers in drivers/i2c as part of
392 config SPL_LIBCOMMON_SUPPORT
393 bool "Support common libraries"
395 Enable support for common U-Boot libraries within SPL. These
396 libraries include common code to deal with U-Boot images,
397 environment and USB, for example. This option is enabled on many
398 boards. Enable this option to build the code in common/ as part of
401 config SPL_LIBDISK_SUPPORT
402 bool "Support disk paritions"
404 Enable support for disk partitions within SPL. 'Disk' is something
405 of a misnomer as it includes non-spinning media such as flash (as
406 used in MMC and USB sticks). Partitions provide a way for a disk
407 to be split up into separate regions, with a partition table placed
408 at the start or end which describes the location and size of each
409 'partition'. These partitions are typically uses as individual block
410 devices, typically with an EXT2 or FAT filesystem in each. This
411 option enables whatever partition support has been enabled in
412 U-Boot to also be used in SPL. It brings in the code in disk/.
414 config SPL_LIBGENERIC_SUPPORT
415 bool "Support generic libraries"
417 Enable support for generic U-Boot libraries within SPL. These
418 libraries include generic code to deal with device tree, hashing,
419 printf(), compression and the like. This option is enabled on many
420 boards. Enable this option to build the code in lib/ as part of an
423 config SPL_MMC_SUPPORT
427 Enable support for MMC (Multimedia Card) within SPL. This enables
428 the MMC protocol implementation and allows any enabled drivers to
429 be used within SPL. MMC can be used with or without disk partition
430 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
431 this option to build the drivers in drivers/mmc as part of an SPL
435 bool "MMC/SD/SDIO card support for write operations in SPL"
436 depends on SPL_MMC_SUPPORT
439 Enable write access to MMC and SD Cards in SPL
442 config SPL_MPC8XXX_INIT_DDR_SUPPORT
443 bool "Support MPC8XXX DDR init"
445 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
446 random-access memory) on the MPC8XXX family within SPL. This
447 allows DRAM to be set up before loading U-Boot into that DRAM,
450 config SPL_MTD_SUPPORT
451 bool "Support MTD drivers"
453 Enable support for MTD (Memory Technology Device) within SPL. MTD
454 provides a block interface over raw NAND and can also be used with
455 SPI flash. This allows SPL to load U-Boot from supported MTD
456 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
457 to enable specific MTD drivers.
459 config SPL_MUSB_NEW_SUPPORT
460 bool "Support new Mentor Graphics USB"
462 Enable support for Mentor Graphics USB in SPL. This is a new
463 driver used by some boards. Enable this option to build
464 the drivers in drivers/usb/musb-new as part of an SPL build. The
465 old drivers are in drivers/usb/musb.
467 config SPL_NAND_SUPPORT
468 bool "Support NAND flash"
470 Enable support for NAND (Negative AND) flash in SPL. NAND flash
471 can be used to allow SPL to load U-Boot from supported devices.
472 This enables the drivers in drivers/mtd/nand as part of an SPL
475 config SPL_NET_SUPPORT
476 bool "Support networking"
478 Enable support for network devices (such as Ethernet) in SPL.
479 This permits SPL to load U-Boot over a network link rather than
480 from an on-board peripheral. Environment support is required since
481 the network stack uses a number of environment variables. See also
485 config SPL_NET_VCI_STRING
486 string "BOOTP Vendor Class Identifier string sent by SPL"
488 As defined by RFC 2132 the vendor class identifier field can be
489 sent by the client to identify the vendor type and configuration
490 of a client. This is often used in practice to allow for the DHCP
491 server to specify different files to load depending on if the ROM,
492 SPL or U-Boot itself makes the request
493 endif # if SPL_NET_SUPPORT
495 config SPL_NO_CPU_SUPPORT
496 bool "Drop CPU code in SPL"
498 This is specific to the ARM926EJ-S CPU. It disables the standard
499 start.S start-up code, presumably so that a replacement can be
500 used on that CPU. You should not enable it unless you know what
503 config SPL_NOR_SUPPORT
504 bool "Support NOR flash"
506 Enable support for loading U-Boot from memory-mapped NOR (Negative
507 OR) flash in SPL. NOR flash is slow to write but fast to read, and
508 a memory-mapped device makes it very easy to access. Loading from
509 NOR is typically achieved with just a memcpy().
511 config SPL_XIP_SUPPORT
515 Enable support for execute in place of U-Boot or kernel image. There
516 is no need to copy image from flash to ram if flash supports execute
517 in place. Its very useful in systems having enough flash but not
518 enough ram to load the image.
520 config SPL_ONENAND_SUPPORT
521 bool "Support OneNAND flash"
523 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
524 a type of NAND flash and therefore can be used to allow SPL to
525 load U-Boot from supported devices. This enables the drivers in
526 drivers/mtd/onenand as part of an SPL build.
529 bool "Activate Falcon Mode"
530 depends on !TI_SECURE_DEVICE
533 Enable booting directly to an OS from SPL.
534 for more info read doc/README.falcon
538 hex "addr, where OS is found"
539 depends on SPL_NOR_SUPPORT
541 Specify the address, where the OS image is found, which
546 config SPL_PCI_SUPPORT
547 bool "Support PCI drivers"
549 Enable support for PCI in SPL. For platforms that need PCI to boot,
550 or must perform some init using PCI in SPL, this provides the
551 necessary driver support. This enables the drivers in drivers/pci
552 as part of an SPL build.
554 config SPL_PCH_SUPPORT
555 bool "Support PCH drivers"
557 Enable support for PCH (Platform Controller Hub) devices in SPL.
558 These are used to set up GPIOs and the SPI peripheral early in
559 boot. This enables the drivers in drivers/pch as part of an SPL
562 config SPL_POST_MEM_SUPPORT
563 bool "Support POST drivers"
565 Enable support for POST (Power-on Self Test) in SPL. POST is a
566 procedure that checks that the hardware (CPU or board) appears to
567 be functionally correctly. It is a sanity check that can be
568 performed before booting. This enables the drivers in post/drivers
569 as part of an SPL build.
571 config SPL_RESET_SUPPORT
572 bool "Support reset drivers"
575 Enable support for reset control in SPL.
576 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
577 by using the generic reset API provided by driver model.
578 This enables the drivers in drivers/reset as part of an SPL build.
580 config SPL_POWER_SUPPORT
581 bool "Support power drivers"
583 Enable support for power control in SPL. This includes support
584 for PMICs (Power-management Integrated Circuits) and some of the
585 features provided by PMICs. In particular, voltage regulators can
586 be used to enable/disable power and vary its voltage. That can be
587 useful in SPL to turn on boot peripherals and adjust CPU voltage
588 so that the clock speed can be increased. This enables the drivers
589 in drivers/power, drivers/power/pmic and drivers/power/regulator
590 as part of an SPL build.
592 config SPL_RAM_SUPPORT
593 bool "Support booting from RAM"
594 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
596 Enable booting of an image in RAM. The image can be preloaded or
597 it can be loaded by SPL directly into RAM (e.g. using USB).
599 config SPL_RAM_DEVICE
600 bool "Support booting from preloaded image in RAM"
601 depends on SPL_RAM_SUPPORT
602 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
604 Enable booting of an image already loaded in RAM. The image has to
605 be already in memory when SPL takes over, e.g. loaded by the boot
608 config SPL_RTC_SUPPORT
609 bool "Support RTC drivers"
611 Enable RTC (Real-time Clock) support in SPL. This includes support
612 for reading and setting the time. Some RTC devices also have some
613 non-volatile (battery-backed) memory which is accessible if
614 needed. This enables the drivers in drivers/rtc as part of an SPL
617 config SPL_SATA_SUPPORT
618 bool "Support loading from SATA"
620 Enable support for SATA (Serial AT attachment) in SPL. This allows
621 use of SATA devices such as hard drives and flash drivers for
622 loading U-Boot. SATA is used in higher-end embedded systems and
623 can provide higher performance than MMC , at somewhat higher
624 expense and power consumption. This enables loading from SATA
625 using a configured device.
627 config SPL_SERIAL_SUPPORT
628 bool "Support serial"
632 Enable support for serial in SPL. This allows use of a serial UART
633 for displaying messages while SPL is running. It also brings in
634 printf() and panic() functions. This should normally be enabled
635 unless there are space reasons not to. Even then, consider
636 enabling USE_TINY_PRINTF which is a small printf() version.
638 config SPL_SPI_FLASH_SUPPORT
639 bool "Support SPI flash drivers"
641 Enable support for using SPI flash in SPL, and loading U-Boot from
642 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
643 the SPI bus that is used to connect it to a system. It is a simple
644 but fast bidirectional 4-wire bus (clock, chip select and two data
645 lines). This enables the drivers in drivers/mtd/spi as part of an
646 SPL build. This normally requires SPL_SPI_SUPPORT.
649 bool "Support loading from SPI flash"
650 depends on SPL_SPI_FLASH_SUPPORT
652 Enable support for loading next stage, U-Boot or otherwise, from
653 SPI NOR in U-Boot SPL.
655 config SPL_SPI_SUPPORT
656 bool "Support SPI drivers"
658 Enable support for using SPI in SPL. This is used for connecting
659 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
660 more details on that. The SPI driver provides the transport for
661 data between the SPI flash and the CPU. This option can be used to
662 enable SPI drivers that are needed for other purposes also, such
666 bool "Driver support for thermal devices"
668 Enable support for temperature-sensing devices. Some SoCs have on-chip
669 temperature sensors to permit warnings, speed throttling or even
670 automatic power-off when the temperature gets too high or low. Other
671 devices may be discrete but connected on a suitable bus.
673 config SPL_USB_HOST_SUPPORT
674 bool "Support USB host drivers"
676 Enable access to USB (Universal Serial Bus) host devices so that
677 SPL can load U-Boot from a connected USB peripheral, such as a USB
678 flash stick. While USB takes a little longer to start up than most
679 buses, it is very flexible since many different types of storage
680 device can be attached. This option enables the drivers in
681 drivers/usb/host as part of an SPL build.
683 config SPL_USB_SUPPORT
684 bool "Support loading from USB"
685 depends on SPL_USB_HOST_SUPPORT
687 Enable support for USB devices in SPL. This allows use of USB
688 devices such as hard drives and flash drivers for loading U-Boot.
689 The actual drivers are enabled separately using the normal U-Boot
690 config options. This enables loading from USB using a configured
693 config SPL_USB_GADGET_SUPPORT
694 bool "Suppport USB Gadget drivers"
696 Enable USB Gadget API which allows to enable USB device functions
699 if SPL_USB_GADGET_SUPPORT
702 bool "Support USB Ethernet drivers"
704 Enable access to the USB network subsystem and associated
705 drivers in SPL. This permits SPL to load U-Boot over a
706 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
707 than from an onboard peripheral. Environment support is required
708 since the network stack uses a number of environment variables.
709 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
711 config SPL_DFU_SUPPORT
712 bool "Support DFU (Device Firmware Upgarde)"
713 select SPL_HASH_SUPPORT
714 select SPL_DFU_NO_RESET
715 depends on SPL_RAM_SUPPORT
717 This feature enables the DFU (Device Firmware Upgarde) in SPL with
718 RAM memory device support. The ROM code will load and execute
719 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
720 selected device partition from host-pc using dfu-utils.
721 This feature is useful to flash the binaries to factory or bare-metal
722 boards using USB interface.
725 bool "DFU device selection"
726 depends on SPL_DFU_SUPPORT
730 depends on SPL_DFU_SUPPORT && SPL_RAM_SUPPORT
732 select RAM/DDR memory device for loading binary images
733 (u-boot/kernel) to the selected device partition using
734 DFU and execute the u-boot/kernel from RAM.
738 config SPL_USB_SDP_SUPPORT
739 bool "Support SDP (Serial Download Protocol)"
741 Enable Serial Download Protocol (SDP) device support in SPL. This
742 allows to download images into memory and execute (jump to) them
743 using the same protocol as implemented by the i.MX family's boot ROM.
746 config SPL_WATCHDOG_SUPPORT
747 bool "Support watchdog drivers"
749 Enable support for watchdog drivers in SPL. A watchdog is
750 typically a hardware peripheral which can reset the system when it
751 detects no activity for a while (such as a software crash). This
752 enables the drivers in drivers/watchdog as part of an SPL build.
754 config SPL_YMODEM_SUPPORT
755 bool "Support loading using Ymodem"
756 depends on SPL_SERIAL_SUPPORT
758 While loading from serial is slow it can be a useful backup when
759 there is no other option. The Ymodem protocol provides a reliable
760 means of transmitting U-Boot over a serial line for using in SPL,
761 with a checksum to ensure correctness.
764 bool "Support ARM Trusted Firmware"
767 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
768 is loaded by SPL (which is considered as BL2 in ATF terminology).
769 More detail at: https://github.com/ARM-software/arm-trusted-firmware
771 config SPL_ATF_NO_PLATFORM_PARAM
772 bool "Pass no platform parameter"
775 While we expect to call a pointer to a valid FDT (or NULL)
776 as the platform parameter to an ATF, some ATF versions are
777 not U-Boot aware and have an insufficiently robust parameter
778 validation to gracefully reject a FDT being passed.
780 If this option is enabled, the spl_atf os-type handler will
781 always pass NULL for the platform parameter.
783 If your ATF is affected, say Y.
785 config SPL_AM33XX_ENABLE_RTC32K_OSC
786 bool "Enable the RTC32K OSC on AM33xx based platforms"
789 Enable access to the AM33xx RTC and select the external 32kHz clock
794 depends on SUPPORT_TPL
797 If you want to build TPL as well as the normal image and SPL, say Y.
801 config TPL_BOARD_INIT
802 bool "Call board-specific initialization in TPL"
804 If this option is enabled, U-Boot will call the function
805 spl_board_init() from board_init_r(). This function should be
806 provided by the board.
809 string "Linker script for the TPL stage"
812 The TPL stage will usually require a different linker-script
813 (as it runs from a different memory region) than the regular
814 U-Boot stage. Set this to the path of the linker-script to
817 May be left empty to trigger the Makefile infrastructure to
818 fall back to the linker-script used for the SPL stage.
820 config TPL_NEEDS_SEPARATE_TEXT_BASE
821 bool "TPL needs a separate text-base"
825 Enable, if the TPL stage should not inherit its text-base
826 from the SPL stage. When enabled, a base address for the
827 .text sections of the TPL stage has to be set below.
829 config TPL_NEEDS_SEPARATE_STACK
830 bool "TPL needs a separate initial stack-pointer"
834 Enable, if the TPL stage should not inherit its initial
835 stack-pointer from the settings for the SPL stage.
838 hex "Base address for the .text section of the TPL stage"
839 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
841 The base address for the .text section of the TPL stage.
844 int "Maximum size (in bytes) for the TPL stage"
848 The maximum size (in bytes) of the TPL stage.
851 hex "Address of the initial stack-pointer for the TPL stage"
852 depends on TPL_NEEDS_SEPARATE_STACK
854 The address of the initial stack-pointer for the TPL stage.
855 Usually this will be the (aligned) top-of-stack.
857 config TPL_BOOTROM_SUPPORT
858 bool "Support returning to the BOOTROM (from TPL)"
860 Some platforms (e.g. the Rockchip RK3368) provide support in their
861 ROM for loading the next boot-stage after performing basic setup
864 Enable this option, to return to the BOOTROM through the
865 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
866 boot device list, if not implemented for a given board)
868 config TPL_DRIVERS_MISC_SUPPORT
869 bool "Support misc drivers in TPL"
871 Enable miscellaneous drivers in TPL. These drivers perform various
872 tasks that don't fall nicely into other categories, Enable this
873 option to build the drivers in drivers/misc as part of an TPL
874 build, for those that support building in TPL (not all drivers do).
876 config TPL_ENV_SUPPORT
877 bool "Support an environment"
879 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
881 config TPL_I2C_SUPPORT
884 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
887 config TPL_LIBCOMMON_SUPPORT
888 bool "Support common libraries"
890 Enable support for common U-Boot libraries within TPL. See
891 SPL_LIBCOMMON_SUPPORT for details.
893 config TPL_LIBGENERIC_SUPPORT
894 bool "Support generic libraries"
896 Enable support for generic U-Boot libraries within TPL. See
897 SPL_LIBGENERIC_SUPPORT for details.
899 config TPL_MPC8XXX_INIT_DDR_SUPPORT
900 bool "Support MPC8XXX DDR init"
902 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
903 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
905 config TPL_MMC_SUPPORT
909 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
911 config TPL_NAND_SUPPORT
912 bool "Support NAND flash"
914 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
916 config TPL_RAM_SUPPORT
917 bool "Support booting from RAM"
919 Enable booting of an image in RAM. The image can be preloaded or
920 it can be loaded by TPL directly into RAM (e.g. using USB).
922 config TPL_RAM_DEVICE
923 bool "Support booting from preloaded image in RAM"
924 depends on TPL_RAM_SUPPORT
926 Enable booting of an image already loaded in RAM. The image has to
927 be already in memory when TPL takes over, e.g. loaded by the boot
930 config TPL_SERIAL_SUPPORT
931 bool "Support serial"
935 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
938 config TPL_SPI_FLASH_SUPPORT
939 bool "Support SPI flash drivers"
941 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
945 bool "Support loading from SPI flash"
946 depends on TPL_SPI_FLASH_SUPPORT
948 Enable support for loading next stage, U-Boot or otherwise, from
949 SPI NOR in U-Boot TPL.
951 config TPL_SPI_SUPPORT
952 bool "Support SPI drivers"
954 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for
957 config TPL_YMODEM_SUPPORT
958 bool "Support loading using Ymodem"
959 depends on TPL_SERIAL_SUPPORT
961 While loading from serial is slow it can be a useful backup when
962 there is no other option. The Ymodem protocol provides a reliable
963 means of transmitting U-Boot over a serial line for using in TPL,
964 with a checksum to ensure correctness.