blob: c283dcff62dffc80c6426f41d546aa472cd7a8d5 [file] [log] [blame]
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +00001Generic SPL framework
2=====================
3
4Overview
5--------
6
7To unify all existing implementations for a secondary program loader (SPL)
8and to allow simply adding of new implementations this generic SPL framework
9has been created. With this framework almost all source files for a board
10can be reused. No code duplication or symlinking is necessary anymore.
11
12
13How it works
14------------
15
Masahiro Yamadac01f87c2014-08-05 15:25:06 +090016The object files for SPL are built separately and placed in the "spl" directory.
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +000017The final binaries which are generated are u-boot-spl, u-boot-spl.bin and
18u-boot-spl.map.
19
Masahiro Yamadac01f87c2014-08-05 15:25:06 +090020A config option named CONFIG_SPL_BUILD is enabled by Kconfig for SPL.
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +000021Source files can therefore be compiled for SPL with different settings.
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +000022
23For example:
24
25ifeq ($(CONFIG_SPL_BUILD),y)
Masahiro Yamadac01f87c2014-08-05 15:25:06 +090026obj-y += board_spl.o
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +000027else
Masahiro Yamadac01f87c2014-08-05 15:25:06 +090028obj-y += board.o
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +000029endif
30
Masahiro Yamadac01f87c2014-08-05 15:25:06 +090031obj-$(CONFIG_SPL_BUILD) += foo.o
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +000032
33#ifdef CONFIG_SPL_BUILD
Wolfgang Denk04e5ae72011-09-11 21:24:09 +020034 foo();
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +000035#endif
36
37
Masahiro Yamadac01f87c2014-08-05 15:25:06 +090038The building of SPL images can be enabled by CONFIG_SPL option in Kconfig.
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +000039
Peter Meerwaldfd3d28e2012-02-02 12:51:03 +000040Because SPL images normally have a different text base, one has to be
41configured by defining CONFIG_SPL_TEXT_BASE. The linker script has to be
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +000042defined with CONFIG_SPL_LDSCRIPT.
43
44To support generic U-Boot libraries and drivers in the SPL binary one can
45optionally define CONFIG_SPL_XXX_SUPPORT. Currently following options
46are supported:
47
48CONFIG_SPL_LIBCOMMON_SUPPORT (common/libcommon.o)
49CONFIG_SPL_LIBDISK_SUPPORT (disk/libdisk.o)
50CONFIG_SPL_I2C_SUPPORT (drivers/i2c/libi2c.o)
51CONFIG_SPL_GPIO_SUPPORT (drivers/gpio/libgpio.o)
52CONFIG_SPL_MMC_SUPPORT (drivers/mmc/libmmc.o)
53CONFIG_SPL_SERIAL_SUPPORT (drivers/serial/libserial.o)
54CONFIG_SPL_SPI_FLASH_SUPPORT (drivers/mtd/spi/libspi_flash.o)
55CONFIG_SPL_SPI_SUPPORT (drivers/spi/libspi.o)
56CONFIG_SPL_FAT_SUPPORT (fs/fat/libfat.o)
57CONFIG_SPL_LIBGENERIC_SUPPORT (lib/libgeneric.o)
Simon Schwarz682b3a82011-09-14 15:30:54 -040058CONFIG_SPL_POWER_SUPPORT (drivers/power/libpower.o)
Simon Schwarz12c2f1e2011-09-14 15:30:16 -040059CONFIG_SPL_NAND_SUPPORT (drivers/mtd/nand/libnand.o)
Po Liu66099162014-01-10 10:10:58 +080060CONFIG_SPL_DRIVERS_MISC_SUPPORT (drivers/misc)
Simon Schwarz3a0d60c2011-09-28 05:00:27 +000061CONFIG_SPL_DMA_SUPPORT (drivers/dma/libdma.o)
Heiko Schocher18e8ff12011-11-01 20:00:28 +000062CONFIG_SPL_POST_MEM_SUPPORT (post/drivers/memory.o)
Heiko Schocher435199f2011-11-01 20:00:29 +000063CONFIG_SPL_NAND_LOAD (drivers/mtd/nand/nand_spl_load.o)
Christian Riesch32b11272011-12-09 09:47:35 +000064CONFIG_SPL_SPI_LOAD (drivers/mtd/spi/spi_spl_load.o)
Pavel Machekc57b9532012-08-30 22:42:11 +020065CONFIG_SPL_RAM_DEVICE (common/spl/spl.c)
Heiko Schochera09f9642013-08-19 16:38:58 +020066CONFIG_SPL_WATCHDOG_SUPPORT (drivers/watchdog/libwatchdog.o)
Allen Martind22650a2012-04-19 07:58:57 +000067
Tom Rinif8e754d2012-08-15 07:23:20 +000068
69Debugging
70---------
71
72When building SPL with DEBUG set you may also need to set CONFIG_PANIC_HANG
73as in most cases do_reset is not defined within SPL.
Tom Rinic3567d82012-08-15 07:23:21 +000074
75
76Estimating stack usage
77----------------------
78
79With gcc 4.6 (and later) and the use of GNU cflow it is possible to estimate
80stack usage at various points in run sequence of SPL. The -fstack-usage option
81to gcc will produce '.su' files (such as arch/arm/cpu/armv7/syslib.su) that
82will give stack usage information and cflow can construct program flow.
83
84Must have gcc 4.6 or later, which supports -fstack-usage
85
861) Build normally
872) Perform the following shell command to generate a list of C files used in
88SPL:
89$ find spl -name '*.su' | sed -e 's:^spl/::' -e 's:[.]su$:.c:' > used-spl.list
903) Execute cflow:
91$ cflow --main=board_init_r `cat used-spl.list` 2>&1 | $PAGER
92
93cflow will spit out a number of warnings as it does not parse
94the config files and picks functions based on #ifdef. Parsing the '.i'
95files instead introduces another set of headaches. These warnings are
96not usually important to understanding the flow, however.