README.SPL 3.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697
  1. Generic SPL framework
  2. =====================
  3. Overview
  4. --------
  5. To unify all existing implementations for a secondary program loader (SPL)
  6. and to allow simply adding of new implementations this generic SPL framework
  7. has been created. With this framework almost all source files for a board
  8. can be reused. No code duplication or symlinking is necessary anymore.
  9. How it works
  10. ------------
  11. The object files for SPL are built separately and placed in the "spl" directory.
  12. The final binaries which are generated are u-boot-spl, u-boot-spl.bin and
  13. u-boot-spl.map.
  14. A config option named CONFIG_SPL_BUILD is enabled by Kconfig for SPL.
  15. Source files can therefore be compiled for SPL with different settings.
  16. For example:
  17. ifeq ($(CONFIG_SPL_BUILD),y)
  18. obj-y += board_spl.o
  19. else
  20. obj-y += board.o
  21. endif
  22. obj-$(CONFIG_SPL_BUILD) += foo.o
  23. #ifdef CONFIG_SPL_BUILD
  24. foo();
  25. #endif
  26. The building of SPL images can be enabled by CONFIG_SPL option in Kconfig.
  27. Because SPL images normally have a different text base, one has to be
  28. configured by defining CONFIG_SPL_TEXT_BASE. The linker script has to be
  29. defined with CONFIG_SPL_LDSCRIPT.
  30. To support generic U-Boot libraries and drivers in the SPL binary one can
  31. optionally define CONFIG_SPL_XXX_SUPPORT. Currently following options
  32. are supported:
  33. CONFIG_SPL_LIBCOMMON_SUPPORT (common/libcommon.o)
  34. CONFIG_SPL_LIBDISK_SUPPORT (disk/libdisk.o)
  35. CONFIG_SPL_I2C_SUPPORT (drivers/i2c/libi2c.o)
  36. CONFIG_SPL_GPIO_SUPPORT (drivers/gpio/libgpio.o)
  37. CONFIG_SPL_MMC_SUPPORT (drivers/mmc/libmmc.o)
  38. CONFIG_SPL_SERIAL_SUPPORT (drivers/serial/libserial.o)
  39. CONFIG_SPL_SPI_FLASH_SUPPORT (drivers/mtd/spi/libspi_flash.o)
  40. CONFIG_SPL_SPI_SUPPORT (drivers/spi/libspi.o)
  41. CONFIG_SPL_FAT_SUPPORT (fs/fat/libfat.o)
  42. CONFIG_SPL_EXT_SUPPORT
  43. CONFIG_SPL_LIBGENERIC_SUPPORT (lib/libgeneric.o)
  44. CONFIG_SPL_POWER_SUPPORT (drivers/power/libpower.o)
  45. CONFIG_SPL_NAND_SUPPORT (drivers/mtd/nand/raw/libnand.o)
  46. CONFIG_SPL_DRIVERS_MISC_SUPPORT (drivers/misc)
  47. CONFIG_SPL_DMA_SUPPORT (drivers/dma/libdma.o)
  48. CONFIG_SPL_POST_MEM_SUPPORT (post/drivers/memory.o)
  49. CONFIG_SPL_NAND_LOAD (drivers/mtd/nand/raw/nand_spl_load.o)
  50. CONFIG_SPL_SPI_LOAD (drivers/mtd/spi/spi_spl_load.o)
  51. CONFIG_SPL_RAM_DEVICE (common/spl/spl.c)
  52. CONFIG_SPL_WATCHDOG_SUPPORT (drivers/watchdog/libwatchdog.o)
  53. Debugging
  54. ---------
  55. When building SPL with DEBUG set you may also need to set CONFIG_PANIC_HANG
  56. as in most cases do_reset is not defined within SPL.
  57. Estimating stack usage
  58. ----------------------
  59. With gcc 4.6 (and later) and the use of GNU cflow it is possible to estimate
  60. stack usage at various points in run sequence of SPL. The -fstack-usage option
  61. to gcc will produce '.su' files (such as arch/arm/cpu/armv7/syslib.su) that
  62. will give stack usage information and cflow can construct program flow.
  63. Must have gcc 4.6 or later, which supports -fstack-usage
  64. 1) Build normally
  65. 2) Perform the following shell command to generate a list of C files used in
  66. SPL:
  67. $ find spl -name '*.su' | sed -e 's:^spl/::' -e 's:[.]su$:.c:' > used-spl.list
  68. 3) Execute cflow:
  69. $ cflow --main=board_init_r `cat used-spl.list` 2>&1 | $PAGER
  70. cflow will spit out a number of warnings as it does not parse
  71. the config files and picks functions based on #ifdef. Parsing the '.i'
  72. files instead introduces another set of headaches. These warnings are
  73. not usually important to understanding the flow, however.