board-support.txt 1.7 KB

1234567891011121314151617181920212223242526272829303132333435
  1. Creating your own board support
  2. ===============================
  3. Creating your own board support in Buildroot allows users of a
  4. particular hardware platform to easily build a system that is known to
  5. work.
  6. To do so, you need to create a normal Buildroot configuration that
  7. builds a basic system for the hardware: toolchain, kernel, bootloader,
  8. filesystem and a simple Busybox-only userspace. No specific package
  9. should be selected: the configuration should be as minimal as
  10. possible, and should only build a working basic Busybox system for the
  11. target platform. You can of course use more complicated configurations
  12. for your internal projects, but the Buildroot project will only
  13. integrate basic board configurations. This is because package
  14. selections are highly application-specific.
  15. Once you have a known working configuration, run +make
  16. savedefconfig+. This will generate a minimal +defconfig+ file at the
  17. root of the Buildroot source tree. Move this file into the +configs/+
  18. directory, and rename it +MYBOARD_defconfig+.
  19. It is recommended to use as much as possible upstream versions of the
  20. Linux kernel and bootloaders, and to use as much as possible default
  21. kernel and bootloader configurations. If they are incorrect for your
  22. platform, we encourage you to send fixes to the corresponding upstream
  23. projects.
  24. However, in the mean time, you may want to store kernel or bootloader
  25. configuration or patches specific to your target platform. To do so,
  26. create a directory +board/MANUFACTURER+ and a subdirectory
  27. +board/MANUFACTURER/BOARDNAME+ (after replacing, of course,
  28. MANUFACTURER and BOARDNAME with the appropriate values, in lower case
  29. letters). You can then store your patches and configurations in these
  30. directories, and reference them from the main Buildroot configuration.