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.
22 string "Linker script for the SPL stage"
23 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
26 The SPL stage will usually require a different linker-script
27 (as it runs from a different memory region) than the regular
28 U-Boot stage. Set this to the path of the linker-script to
32 bool "Call board-specific initialization in SPL"
34 If this option is enabled, U-Boot will call the function
35 spl_board_init() from board_init_r(). This function should be
36 provided by the board.
38 config SPL_BOOTROM_SUPPORT
39 bool "Support returning to the BOOTROM"
41 Some platforms (e.g. the Rockchip RK3368) provide support in their
42 ROM for loading the next boot-stage after performing basic setup
45 Enable this option, to return to the BOOTROM through the
46 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
47 boot device list, if not implemented for a given board)
49 config SPL_RAW_IMAGE_SUPPORT
50 bool "Support SPL loading and booting of RAW images"
51 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
52 default y if !TI_SECURE_DEVICE
54 SPL will support loading and booting a RAW image when this option
55 is y. If this is not set, SPL will move on to other available
56 boot media to find a suitable image.
58 config SPL_LEGACY_IMAGE_SUPPORT
59 bool "Support SPL loading and booting of Legacy images"
60 default y if !TI_SECURE_DEVICE
62 SPL will support loading and booting Legacy images 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_SYS_MALLOC_SIMPLE
68 prompt "Only use malloc_simple functions in the SPL"
70 Say Y here to only use the *_simple malloc functions from
71 malloc_simple.c, rather then using the versions from dlmalloc.c;
72 this will make the SPL binary smaller at the cost of more heap
73 usage as the *_simple malloc functions do not re-use free-ed mem.
75 config TPL_SYS_MALLOC_SIMPLE
77 prompt "Only use malloc_simple functions in the TPL"
79 Say Y here to only use the *_simple malloc functions from
80 malloc_simple.c, rather then using the versions from dlmalloc.c;
81 this will make the TPL binary smaller at the cost of more heap
82 usage as the *_simple malloc functions do not re-use free-ed mem.
85 bool "Enable SDRAM location for SPL stack"
87 SPL starts off execution in SRAM and thus typically has only a small
88 stack available. Since SPL sets up DRAM while in its board_init_f()
89 function, it is possible for the stack to move there before
90 board_init_r() is reached. This option enables a special SDRAM
91 location for the SPL stack. U-Boot SPL switches to this after
92 board_init_f() completes, and before board_init_r() starts.
94 config SPL_STACK_R_ADDR
95 depends on SPL_STACK_R
96 hex "SDRAM location for SPL stack"
97 default 0x82000000 if ARCH_OMAP2PLUS
99 Specify the address in SDRAM for the SPL stack. This will be set up
100 before board_init_r() is called.
102 config SPL_STACK_R_MALLOC_SIMPLE_LEN
103 depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
104 hex "Size of malloc_simple heap after switching to DRAM SPL stack"
107 Specify the amount of the stack to use as memory pool for
108 malloc_simple after switching the stack to DRAM. This may be set
109 to give board_init_r() a larger heap then the initial heap in
110 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
112 config SPL_SEPARATE_BSS
113 bool "BSS section is in a different memory region from text"
115 Some platforms need a large BSS region in SPL and can provide this
116 because RAM is already set up. In this case BSS can be moved to RAM.
117 This option should then be enabled so that the correct device tree
118 location is used. Normally we put the device tree at the end of BSS
119 but with this option enabled, it goes at _image_binary_end.
121 config SPL_DISPLAY_PRINT
122 bool "Display a board-specific message in SPL"
124 If this option is enabled, U-Boot will call the function
125 spl_display_print() immediately after displaying the SPL console
126 banner ("U-Boot SPL ..."). This function should be provided by
129 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
130 bool "MMC raw mode: by sector"
131 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER ||ARCH_MX6 || \
132 ARCH_ROCKCHIP || ARCH_MVEBU || ARCH_SOCFPGA || \
133 ARCH_AT91 || ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || \
134 OMAP44XX || OMAP54XX || AM33XX || AM43XX
136 Use sector number for specifying U-Boot location on MMC/SD in
139 config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
140 hex "Address on the MMC to load U-Boot from"
141 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
142 default 0x50 if ARCH_SUNXI
143 default 0x75 if ARCH_DAVINCI
144 default 0x8a if ARCH_MX6
145 default 0x100 if ARCH_UNIPHIER
146 default 0x140 if ARCH_MVEBU
147 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
148 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
149 OMAP54XX || AM33XX || AM43XX
150 default 0x4000 if ARCH_ROCKCHIP
152 Address on the MMC to load U-Boot from, when the MMC is being used
153 in raw mode. Units: MMC sectors (1 sector = 512 bytes).
155 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
156 bool "MMC Raw mode: by partition"
158 Use a partition for loading U-Boot when using MMC/SD in raw mode.
160 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
161 hex "Partition to use to load U-Boot from"
162 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
165 Partition on the MMC to load U-Boot from when the MMC is being
168 config SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
169 bool "MMC raw mode: by partition type"
170 depends on DOS_PARTITION && SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION
172 Use partition type for specifying U-Boot partition on MMC/SD in
173 raw mode. U-Boot will be loaded from the first partition of this
176 config SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE
177 hex "Partition Type on the MMC to load U-Boot from"
178 depends on SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE
180 Partition Type on the MMC to load U-Boot from, when the MMC is being
183 config SPL_CRC32_SUPPORT
187 Enable this to support CRC32 in FIT images within SPL. This is a
188 32-bit checksum value that can be used to verify images. This is
189 the least secure type of checksum, suitable for detected
190 accidental image corruption. For secure applications you should
191 consider SHA1 or SHA256.
193 config SPL_MD5_SUPPORT
197 Enable this to support MD5 in FIT images within SPL. An MD5
198 checksum is a 128-bit hash value used to check that the image
199 contents have not been corrupted. Note that MD5 is not considered
200 secure as it is possible (with a brute-force attack) to adjust the
201 image while still retaining the same MD5 hash value. For secure
202 applications where images may be changed maliciously, you should
203 consider SHA1 or SHA256.
205 config SPL_SHA1_SUPPORT
210 Enable this to support SHA1 in FIT images within SPL. A SHA1
211 checksum is a 160-bit (20-byte) hash value used to check that the
212 image contents have not been corrupted or maliciously altered.
213 While SHA1 is fairly secure it is coming to the end of its life
214 due to the expanding computing power avaiable to brute-force
215 attacks. For more security, consider SHA256.
217 config SPL_SHA256_SUPPORT
218 bool "Support SHA256"
222 Enable this to support SHA256 in FIT images within SPL. A SHA256
223 checksum is a 256-bit (32-byte) hash value used to check that the
224 image contents have not been corrupted. SHA256 is recommended for
225 use in secure applications since (as at 2016) there is no known
226 feasible attack that could produce a 'collision' with differing
227 input data. Use this for the highest security. Note that only the
228 SHA256 variant is supported: SHA512 and others are not currently
231 config SPL_FIT_IMAGE_TINY
232 bool "Remove functionality from SPL FIT loading to reduce size"
234 default y if MACH_SUN50I || MACH_SUN50I_H5
236 Enable this to reduce the size of the FIT image loading code
237 in SPL, if space for the SPL binary is very tight.
239 This removes the detection of image types (which forces the
240 first image to be treated as having a U-Boot style calling
241 convention) and skips the recording of each loaded payload
242 (i.e. loadable) into the FDT (modifying the loaded FDT to
243 ensure this information is available to the next image
246 config SPL_CPU_SUPPORT
247 bool "Support CPU drivers"
249 Enable this to support CPU drivers in SPL. These drivers can set
250 up CPUs and provide information about them such as the model and
251 name. This can be useful in SPL since setting up the CPUs earlier
252 may improve boot performance. Enable this option to build the
253 drivers in drivers/cpu as part of an SPL build.
255 config SPL_CRYPTO_SUPPORT
256 bool "Support crypto drivers"
258 Enable crypto drivers in SPL. These drivers can be used to
259 accelerate secure boot processing in secure applications. Enable
260 this option to build the drivers in drivers/crypto as part of an
263 config SPL_HASH_SUPPORT
264 bool "Support hashing drivers"
268 Enable hashing drivers in SPL. These drivers can be used to
269 accelerate secure boot processing in secure applications. Enable
270 this option to build system-specific drivers for hash acceleration
271 as part of an SPL build.
273 config SPL_DMA_SUPPORT
274 bool "Support DMA drivers"
276 Enable DMA (direct-memory-access) drivers in SPL. These drivers
277 can be used to handle memory-to-peripheral data transfer without
278 the CPU moving the data. Enable this option to build the drivers
279 in drivers/dma as part of an SPL build.
281 config SPL_DRIVERS_MISC_SUPPORT
282 bool "Support misc drivers"
284 Enable miscellaneous drivers in SPL. These drivers perform various
285 tasks that don't fall nicely into other categories, Enable this
286 option to build the drivers in drivers/misc as part of an SPL
287 build, for those that support building in SPL (not all drivers do).
289 config SPL_ENV_SUPPORT
290 bool "Support an environment"
292 Enable environment support in SPL. The U-Boot environment provides
293 a number of settings (essentially name/value pairs) which can
294 control many aspects of U-Boot's operation. Normally this is not
295 needed in SPL as it has a much simpler task with less
296 configuration. But some boards use this to support 'Falcon' boot
297 on EXT2 and FAT, where SPL boots directly into Linux without
298 starting U-Boot first. Enabling this option will make env_get()
299 and env_set() available in SPL.
302 bool "Support save environment"
303 depends on SPL_ENV_SUPPORT
305 Enable save environment support in SPL after setenv. By default
306 the saveenv option is not provided in SPL, but some boards need
307 this support in 'Falcon' boot, where SPL need to boot from
308 different images based on environment variable set by OS. For
309 example OS may set "reboot_image" environment variable to
310 "recovery" inorder to boot recovery image by SPL. The SPL read
311 "reboot_image" and act accordingly and change the reboot_image
312 to default mode using setenv and save the environemnt.
314 config SPL_ETH_SUPPORT
315 bool "Support Ethernet"
316 depends on SPL_ENV_SUPPORT
318 Enable access to the network subsystem and associated Ethernet
319 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
320 link rather than from an on-board peripheral. Environment support
321 is required since the network stack uses a number of environment
322 variables. See also SPL_NET_SUPPORT.
324 config SPL_EXT_SUPPORT
325 bool "Support EXT filesystems"
327 Enable support for EXT2/3/4 filesystems with SPL. This permits
328 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
329 filesystem from within SPL. Support for the underlying block
330 device (e.g. MMC or USB) must be enabled separately.
332 config SPL_FAT_SUPPORT
333 bool "Support FAT filesystems"
336 Enable support for FAT and VFAT filesystems with SPL. This
337 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
338 filesystem from within SPL. Support for the underlying block
339 device (e.g. MMC or USB) must be enabled separately.
341 config SPL_FPGA_SUPPORT
344 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
345 provide software-configurable hardware which is typically used to
346 implement peripherals (such as UARTs, LCD displays, MMC) or
347 accelerate custom processing functions, such as image processing
348 or machine learning. Sometimes it is useful to program the FPGA
349 as early as possible during boot, and this option can enable that
352 config SPL_GPIO_SUPPORT
355 Enable support for GPIOs (General-purpose Input/Output) in SPL.
356 GPIOs allow U-Boot to read the state of an input line (high or
357 low) and set the state of an output line. This can be used to
358 drive LEDs, control power to various system parts and read user
359 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
360 for example. Enable this option to build the drivers in
361 drivers/gpio as part of an SPL build.
363 config SPL_I2C_SUPPORT
366 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
367 I2C works with a clock and data line which can be driven by a
368 one or more masters or slaves. It is a fairly complex bus but is
369 widely used as it only needs two lines for communication. Speeds of
370 400kbps are typical but up to 3.4Mbps is supported by some
371 hardware. I2C can be useful in SPL to configure power management
372 ICs (PMICs) before raising the CPU clock speed, for example.
373 Enable this option to build the drivers in drivers/i2c as part of
376 config SPL_LIBCOMMON_SUPPORT
377 bool "Support common libraries"
379 Enable support for common U-Boot libraries within SPL. These
380 libraries include common code to deal with U-Boot images,
381 environment and USB, for example. This option is enabled on many
382 boards. Enable this option to build the code in common/ as part of
385 config SPL_LIBDISK_SUPPORT
386 bool "Support disk paritions"
388 Enable support for disk partitions within SPL. 'Disk' is something
389 of a misnomer as it includes non-spinning media such as flash (as
390 used in MMC and USB sticks). Partitions provide a way for a disk
391 to be split up into separate regions, with a partition table placed
392 at the start or end which describes the location and size of each
393 'partition'. These partitions are typically uses as individual block
394 devices, typically with an EXT2 or FAT filesystem in each. This
395 option enables whatever partition support has been enabled in
396 U-Boot to also be used in SPL. It brings in the code in disk/.
398 config SPL_LIBGENERIC_SUPPORT
399 bool "Support generic libraries"
401 Enable support for generic U-Boot libraries within SPL. These
402 libraries include generic code to deal with device tree, hashing,
403 printf(), compression and the like. This option is enabled on many
404 boards. Enable this option to build the code in lib/ as part of an
407 config SPL_MMC_SUPPORT
411 Enable support for MMC (Multimedia Card) within SPL. This enables
412 the MMC protocol implementation and allows any enabled drivers to
413 be used within SPL. MMC can be used with or without disk partition
414 support depending on the application (SPL_LIBDISK_SUPPORT). Enable
415 this option to build the drivers in drivers/mmc as part of an SPL
418 config SPL_MPC8XXX_INIT_DDR_SUPPORT
419 bool "Support MPC8XXX DDR init"
421 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
422 random-access memory) on the MPC8XXX family within SPL. This
423 allows DRAM to be set up before loading U-Boot into that DRAM,
426 config SPL_MTD_SUPPORT
427 bool "Support MTD drivers"
429 Enable support for MTD (Memory Technology Device) within SPL. MTD
430 provides a block interface over raw NAND and can also be used with
431 SPI flash. This allows SPL to load U-Boot from supported MTD
432 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
433 to enable specific MTD drivers.
435 config SPL_MUSB_NEW_SUPPORT
436 bool "Support new Mentor Graphics USB"
438 Enable support for Mentor Graphics USB in SPL. This is a new
439 driver used by some boards. Enable this option to build
440 the drivers in drivers/usb/musb-new as part of an SPL build. The
441 old drivers are in drivers/usb/musb.
443 config SPL_NAND_SUPPORT
444 bool "Support NAND flash"
446 Enable support for NAND (Negative AND) flash in SPL. NAND flash
447 can be used to allow SPL to load U-Boot from supported devices.
448 This enables the drivers in drivers/mtd/nand as part of an SPL
451 config SPL_NET_SUPPORT
452 bool "Support networking"
454 Enable support for network devices (such as Ethernet) in SPL.
455 This permits SPL to load U-Boot over a network link rather than
456 from an on-board peripheral. Environment support is required since
457 the network stack uses a number of environment variables. See also
461 config SPL_NET_VCI_STRING
462 string "BOOTP Vendor Class Identifier string sent by SPL"
464 As defined by RFC 2132 the vendor class identifier field can be
465 sent by the client to identify the vendor type and configuration
466 of a client. This is often used in practice to allow for the DHCP
467 server to specify different files to load depending on if the ROM,
468 SPL or U-Boot itself makes the request
469 endif # if SPL_NET_SUPPORT
471 config SPL_NO_CPU_SUPPORT
472 bool "Drop CPU code in SPL"
474 This is specific to the ARM926EJ-S CPU. It disables the standard
475 start.S start-up code, presumably so that a replacement can be
476 used on that CPU. You should not enable it unless you know what
479 config SPL_NOR_SUPPORT
480 bool "Support NOR flash"
482 Enable support for loading U-Boot from memory-mapped NOR (Negative
483 OR) flash in SPL. NOR flash is slow to write but fast to read, and
484 a memory-mapped device makes it very easy to access. Loading from
485 NOR is typically achieved with just a memcpy().
487 config SPL_XIP_SUPPORT
491 Enable support for execute in place of U-Boot or kernel image. There
492 is no need to copy image from flash to ram if flash supports execute
493 in place. Its very useful in systems having enough flash but not
494 enough ram to load the image.
496 config SPL_ONENAND_SUPPORT
497 bool "Support OneNAND flash"
499 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
500 a type of NAND flash and therefore can be used to allow SPL to
501 load U-Boot from supported devices. This enables the drivers in
502 drivers/mtd/onenand as part of an SPL build.
505 bool "Activate Falcon Mode"
506 depends on !TI_SECURE_DEVICE
509 Enable booting directly to an OS from SPL.
510 for more info read doc/README.falcon
514 hex "addr, where OS is found"
515 depends on SPL_NOR_SUPPORT
517 Specify the address, where the OS image is found, which
522 config SPL_PCI_SUPPORT
523 bool "Support PCI drivers"
525 Enable support for PCI in SPL. For platforms that need PCI to boot,
526 or must perform some init using PCI in SPL, this provides the
527 necessary driver support. This enables the drivers in drivers/pci
528 as part of an SPL build.
530 config SPL_PCH_SUPPORT
531 bool "Support PCH drivers"
533 Enable support for PCH (Platform Controller Hub) devices in SPL.
534 These are used to set up GPIOs and the SPI peripheral early in
535 boot. This enables the drivers in drivers/pch as part of an SPL
538 config SPL_POST_MEM_SUPPORT
539 bool "Support POST drivers"
541 Enable support for POST (Power-on Self Test) in SPL. POST is a
542 procedure that checks that the hardware (CPU or board) appears to
543 be functionally correctly. It is a sanity check that can be
544 performed before booting. This enables the drivers in post/drivers
545 as part of an SPL build.
547 config SPL_POWER_SUPPORT
548 bool "Support power drivers"
550 Enable support for power control in SPL. This includes support
551 for PMICs (Power-management Integrated Circuits) and some of the
552 features provided by PMICs. In particular, voltage regulators can
553 be used to enable/disable power and vary its voltage. That can be
554 useful in SPL to turn on boot peripherals and adjust CPU voltage
555 so that the clock speed can be increased. This enables the drivers
556 in drivers/power, drivers/power/pmic and drivers/power/regulator
557 as part of an SPL build.
559 config SPL_RAM_SUPPORT
560 bool "Support booting from RAM"
561 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
563 Enable booting of an image in RAM. The image can be preloaded or
564 it can be loaded by SPL directly into RAM (e.g. using USB).
566 config SPL_RAM_DEVICE
567 bool "Support booting from preloaded image in RAM"
568 depends on SPL_RAM_SUPPORT
569 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
571 Enable booting of an image already loaded in RAM. The image has to
572 be already in memory when SPL takes over, e.g. loaded by the boot
575 config SPL_RTC_SUPPORT
576 bool "Support RTC drivers"
578 Enable RTC (Real-time Clock) support in SPL. This includes support
579 for reading and setting the time. Some RTC devices also have some
580 non-volatile (battery-backed) memory which is accessible if
581 needed. This enables the drivers in drivers/rtc as part of an SPL
584 config SPL_SATA_SUPPORT
585 bool "Support loading from SATA"
587 Enable support for SATA (Serial AT attachment) in SPL. This allows
588 use of SATA devices such as hard drives and flash drivers for
589 loading U-Boot. SATA is used in higher-end embedded systems and
590 can provide higher performance than MMC , at somewhat higher
591 expense and power consumption. This enables loading from SATA
592 using a configured device.
594 config SPL_SERIAL_SUPPORT
595 bool "Support serial"
597 Enable support for serial in SPL. This allows use of a serial UART
598 for displaying messages while SPL is running. It also brings in
599 printf() and panic() functions. This should normally be enabled
600 unless there are space reasons not to. Even then, consider
601 enabling USE_TINY_PRINTF which is a small printf() version.
603 config SPL_SPI_FLASH_SUPPORT
604 bool "Support SPI flash drivers"
606 Enable support for using SPI flash in SPL, and loading U-Boot from
607 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
608 the SPI bus that is used to connect it to a system. It is a simple
609 but fast bidirectional 4-wire bus (clock, chip select and two data
610 lines). This enables the drivers in drivers/mtd/spi as part of an
611 SPL build. This normally requires SPL_SPI_SUPPORT.
613 config SPL_SPI_SUPPORT
614 bool "Support SPI drivers"
616 Enable support for using SPI in SPL. This is used for connecting
617 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
618 more details on that. The SPI driver provides the transport for
619 data between the SPI flash and the CPU. This option can be used to
620 enable SPI drivers that are needed for other purposes also, such
624 bool "Driver support for thermal devices"
626 Enable support for temperature-sensing devices. Some SoCs have on-chip
627 temperature sensors to permit warnings, speed throttling or even
628 automatic power-off when the temperature gets too high or low. Other
629 devices may be discrete but connected on a suitable bus.
631 config SPL_USB_HOST_SUPPORT
632 bool "Support USB host drivers"
634 Enable access to USB (Universal Serial Bus) host devices so that
635 SPL can load U-Boot from a connected USB peripheral, such as a USB
636 flash stick. While USB takes a little longer to start up than most
637 buses, it is very flexible since many different types of storage
638 device can be attached. This option enables the drivers in
639 drivers/usb/host as part of an SPL build.
641 config SPL_USB_SUPPORT
642 bool "Support loading from USB"
643 depends on SPL_USB_HOST_SUPPORT
645 Enable support for USB devices in SPL. This allows use of USB
646 devices such as hard drives and flash drivers for loading U-Boot.
647 The actual drivers are enabled separately using the normal U-Boot
648 config options. This enables loading from USB using a configured
651 config SPL_USB_GADGET_SUPPORT
652 bool "Suppport USB Gadget drivers"
654 Enable USB Gadget API which allows to enable USB device functions
657 if SPL_USB_GADGET_SUPPORT
659 config SPL_USBETH_SUPPORT
660 bool "Support USB Ethernet drivers"
662 Enable access to the USB network subsystem and associated
663 drivers in SPL. This permits SPL to load U-Boot over a
664 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
665 than from an onboard peripheral. Environment support is required
666 since the network stack uses a number of environment variables.
667 See also SPL_NET_SUPPORT and SPL_ETH_SUPPORT.
669 config SPL_DFU_SUPPORT
670 bool "Support DFU (Device Firmware Upgarde)"
671 select SPL_HASH_SUPPORT
672 select SPL_DFU_NO_RESET
673 depends on SPL_RAM_SUPPORT
675 This feature enables the DFU (Device Firmware Upgarde) in SPL with
676 RAM memory device support. The ROM code will load and execute
677 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
678 selected device partition from host-pc using dfu-utils.
679 This feature is useful to flash the binaries to factory or bare-metal
680 boards using USB interface.
683 bool "DFU device selection"
684 depends on SPL_DFU_SUPPORT
688 depends on SPL_DFU_SUPPORT && SPL_RAM_SUPPORT
690 select RAM/DDR memory device for loading binary images
691 (u-boot/kernel) to the selected device partition using
692 DFU and execute the u-boot/kernel from RAM.
696 config SPL_USB_SDP_SUPPORT
697 bool "Support SDP (Serial Download Protocol)"
699 Enable Serial Download Protocol (SDP) device support in SPL. This
700 allows to download images into memory and execute (jump to) them
701 using the same protocol as implemented by the i.MX family's boot ROM.
704 config SPL_WATCHDOG_SUPPORT
705 bool "Support watchdog drivers"
707 Enable support for watchdog drivers in SPL. A watchdog is
708 typically a hardware peripheral which can reset the system when it
709 detects no activity for a while (such as a software crash). This
710 enables the drivers in drivers/watchdog as part of an SPL build.
712 config SPL_YMODEM_SUPPORT
713 bool "Support loading using Ymodem"
715 While loading from serial is slow it can be a useful backup when
716 there is no other option. The Ymodem protocol provides a reliable
717 means of transmitting U-Boot over a serial line for using in SPL,
718 with a checksum to ensure correctness.
721 bool "Support ARM Trusted Firmware"
724 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
725 is loaded by SPL (which is considered as BL2 in ATF terminology).
726 More detail at: https://github.com/ARM-software/arm-trusted-firmware
728 config SPL_ATF_NO_PLATFORM_PARAM
729 bool "Pass no platform parameter"
732 While we expect to call a pointer to a valid FDT (or NULL)
733 as the platform parameter to an ATF, some ATF versions are
734 not U-Boot aware and have an insufficiently robust parameter
735 validation to gracefully reject a FDT being passed.
737 If this option is enabled, the spl_atf os-type handler will
738 always pass NULL for the platform parameter.
740 If your ATF is affected, say Y.
744 depends on SUPPORT_TPL
747 If you want to build TPL as well as the normal image and SPL, say Y.
752 string "Linker script for the TPL stage"
755 The TPL stage will usually require a different linker-script
756 (as it runs from a different memory region) than the regular
757 U-Boot stage. Set this to the path of the linker-script to
760 May be left empty to trigger the Makefile infrastructure to
761 fall back to the linker-script used for the SPL stage.
763 config TPL_NEEDS_SEPARATE_TEXT_BASE
764 bool "TPL needs a separate text-base"
768 Enable, if the TPL stage should not inherit its text-base
769 from the SPL stage. When enabled, a base address for the
770 .text sections of the TPL stage has to be set below.
772 config TPL_NEEDS_SEPARATE_STACK
773 bool "TPL needs a separate initial stack-pointer"
777 Enable, if the TPL stage should not inherit its initial
778 stack-pointer from the settings for the SPL stage.
781 hex "Base address for the .text section of the TPL stage"
782 depends on TPL_NEEDS_SEPARATE_TEXT_BASE
784 The base address for the .text section of the TPL stage.
787 int "Maximum size (in bytes) for the TPL stage"
791 The maximum size (in bytes) of the TPL stage.
794 hex "Address of the initial stack-pointer for the TPL stage"
795 depends on TPL_NEEDS_SEPARATE_STACK
797 The address of the initial stack-pointer for the TPL stage.
798 Usually this will be the (aligned) top-of-stack.
800 config TPL_BOOTROM_SUPPORT
801 bool "Support returning to the BOOTROM (from TPL)"
803 Some platforms (e.g. the Rockchip RK3368) provide support in their
804 ROM for loading the next boot-stage after performing basic setup
807 Enable this option, to return to the BOOTROM through the
808 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
809 boot device list, if not implemented for a given board)
811 config TPL_DRIVERS_MISC_SUPPORT
812 bool "Support misc drivers in TPL"
814 Enable miscellaneous drivers in TPL. These drivers perform various
815 tasks that don't fall nicely into other categories, Enable this
816 option to build the drivers in drivers/misc as part of an TPL
817 build, for those that support building in TPL (not all drivers do).
819 config TPL_ENV_SUPPORT
820 bool "Support an environment"
822 Enable environment support in TPL. See SPL_ENV_SUPPORT for details.
824 config TPL_I2C_SUPPORT
827 Enable support for the I2C bus in TPL. See SPL_I2C_SUPPORT for
830 config TPL_LIBCOMMON_SUPPORT
831 bool "Support common libraries"
833 Enable support for common U-Boot libraries within TPL. See
834 SPL_LIBCOMMON_SUPPORT for details.
836 config TPL_LIBGENERIC_SUPPORT
837 bool "Support generic libraries"
839 Enable support for generic U-Boot libraries within TPL. See
840 SPL_LIBGENERIC_SUPPORT for details.
842 config TPL_MPC8XXX_INIT_DDR_SUPPORT
843 bool "Support MPC8XXX DDR init"
845 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
846 SPL_MPC8XXX_INIT_DDR_SUPPORT for details.
848 config TPL_MMC_SUPPORT
852 Enable support for MMC within TPL. See SPL_MMC_SUPPORT for details.
854 config TPL_NAND_SUPPORT
855 bool "Support NAND flash"
857 Enable support for NAND in TPL. See SPL_NAND_SUPPORT for details.
859 config TPL_SERIAL_SUPPORT
860 bool "Support serial"
862 Enable support for serial in TPL. See SPL_SERIAL_SUPPORT for
865 config TPL_SPI_FLASH_SUPPORT
866 bool "Support SPI flash drivers"
868 Enable support for using SPI flash in TPL. See SPL_SPI_FLASH_SUPPORT
871 config TPL_SPI_SUPPORT
872 bool "Support SPI drivers"
874 Enable support for using SPI in TPL. See SPL_SPI_SUPPORT for