Config.in 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524
  1. config BR2_TARGET_UBOOT
  2. bool "U-Boot"
  3. help
  4. Build "Das U-Boot" Boot Monitor
  5. if BR2_TARGET_UBOOT
  6. choice
  7. prompt "Build system"
  8. default BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG if BR2_TARGET_UBOOT_LATEST_VERSION
  9. default BR2_TARGET_UBOOT_BUILD_SYSTEM_LEGACY
  10. config BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
  11. bool "Kconfig"
  12. help
  13. Select this option if you use a recent U-Boot version (2015.04
  14. or newer), so that we use the Kconfig build system.
  15. config BR2_TARGET_UBOOT_BUILD_SYSTEM_LEGACY
  16. bool "Legacy"
  17. help
  18. Select this option if you use an old U-Boot (older than
  19. 2015.04), so that we use the old build system.
  20. endchoice
  21. if BR2_TARGET_UBOOT_BUILD_SYSTEM_LEGACY
  22. config BR2_TARGET_UBOOT_BOARDNAME
  23. string "U-Boot board name"
  24. help
  25. One of U-Boot supported boards to be built.
  26. This will be suffixed with _config to meet U-Boot standard
  27. naming. See boards.cfg in U-Boot source code for the list of
  28. available configurations.
  29. endif
  30. choice
  31. prompt "U-Boot Version"
  32. help
  33. Select the specific U-Boot version you want to use
  34. config BR2_TARGET_UBOOT_LATEST_VERSION
  35. bool "2018.07"
  36. config BR2_TARGET_UBOOT_CUSTOM_VERSION
  37. bool "Custom version"
  38. help
  39. This option allows to use a specific official versions
  40. config BR2_TARGET_UBOOT_CUSTOM_TARBALL
  41. bool "Custom tarball"
  42. config BR2_TARGET_UBOOT_CUSTOM_GIT
  43. bool "Custom Git repository"
  44. config BR2_TARGET_UBOOT_CUSTOM_HG
  45. bool "Custom Mercurial repository"
  46. config BR2_TARGET_UBOOT_CUSTOM_SVN
  47. bool "Custom Subversion repository"
  48. endchoice
  49. config BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE
  50. string "U-Boot version"
  51. depends on BR2_TARGET_UBOOT_CUSTOM_VERSION
  52. config BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION
  53. string "URL of custom U-Boot tarball"
  54. depends on BR2_TARGET_UBOOT_CUSTOM_TARBALL
  55. if BR2_TARGET_UBOOT_CUSTOM_GIT || BR2_TARGET_UBOOT_CUSTOM_HG || BR2_TARGET_UBOOT_CUSTOM_SVN
  56. config BR2_TARGET_UBOOT_CUSTOM_REPO_URL
  57. string "URL of custom repository"
  58. default BR2_TARGET_UBOOT_CUSTOM_GIT_REPO_URL \
  59. if BR2_TARGET_UBOOT_CUSTOM_GIT_REPO_URL != "" # legacy
  60. config BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION
  61. string "Custom repository version"
  62. default BR2_TARGET_UBOOT_CUSTOM_GIT_VERSION \
  63. if BR2_TARGET_UBOOT_CUSTOM_GIT_VERSION != "" # legacy
  64. help
  65. Revision to use in the typical format used by
  66. Git/Mercurial/Subversion E.G. a sha id, a tag, branch, ..
  67. endif
  68. config BR2_TARGET_UBOOT_VERSION
  69. string
  70. default "2018.07" if BR2_TARGET_UBOOT_LATEST_VERSION
  71. default BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE \
  72. if BR2_TARGET_UBOOT_CUSTOM_VERSION
  73. default "custom" if BR2_TARGET_UBOOT_CUSTOM_TARBALL
  74. default BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION \
  75. if BR2_TARGET_UBOOT_CUSTOM_GIT || BR2_TARGET_UBOOT_CUSTOM_HG || BR2_TARGET_UBOOT_CUSTOM_SVN
  76. config BR2_TARGET_UBOOT_PATCH
  77. string "Custom U-Boot patches"
  78. default BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR if BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR != "" # legacy
  79. help
  80. A space-separated list of patches to apply to U-Boot.
  81. Each patch can be described as an URL, a local file path,
  82. or a directory. In the case of a directory, all files
  83. matching *.patch in the directory will be applied.
  84. Most users may leave this empty
  85. if BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
  86. choice
  87. prompt "U-Boot configuration"
  88. default BR2_TARGET_UBOOT_USE_DEFCONFIG
  89. config BR2_TARGET_UBOOT_USE_DEFCONFIG
  90. bool "Using an in-tree board defconfig file"
  91. config BR2_TARGET_UBOOT_USE_CUSTOM_CONFIG
  92. bool "Using a custom board (def)config file"
  93. endchoice
  94. config BR2_TARGET_UBOOT_BOARD_DEFCONFIG
  95. string "Board defconfig"
  96. depends on BR2_TARGET_UBOOT_USE_DEFCONFIG
  97. help
  98. Name of the board for which U-Boot should be built, without
  99. the _defconfig suffix.
  100. config BR2_TARGET_UBOOT_CUSTOM_CONFIG_FILE
  101. string "Configuration file path"
  102. depends on BR2_TARGET_UBOOT_USE_CUSTOM_CONFIG
  103. help
  104. Path to the U-Boot configuration file.
  105. config BR2_TARGET_UBOOT_CONFIG_FRAGMENT_FILES
  106. string "Additional configuration fragment files"
  107. help
  108. A space-separated list of configuration fragment files,
  109. that will be merged to the main U-Boot configuration file.
  110. endif
  111. config BR2_TARGET_UBOOT_NEEDS_DTC
  112. bool "U-Boot needs dtc"
  113. select BR2_PACKAGE_HOST_DTC
  114. help
  115. Select this option if your U-Boot board configuration
  116. requires the Device Tree compiler to be available.
  117. config BR2_TARGET_UBOOT_NEEDS_PYLIBFDT
  118. bool "U-Boot needs pylibfdt"
  119. help
  120. Select this option if your U-Boot board configuration
  121. requires the Python libfdt library to be available.
  122. config BR2_TARGET_UBOOT_NEEDS_OPENSSL
  123. bool "U-Boot needs OpenSSL"
  124. help
  125. Select this option if your U-Boot board configuration
  126. requires OpenSSL to be available on the host. This is
  127. typically the case when the board configuration has
  128. CONFIG_FIT_SIGNATURE enabled.
  129. config BR2_TARGET_UBOOT_NEEDS_ATF_BL31
  130. bool "U-Boot needs ATF BL31"
  131. depends on BR2_TARGET_ARM_TRUSTED_FIRMWARE
  132. depends on !BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_AS_BL33
  133. select BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31
  134. help
  135. Some specific platforms (such as Allwinner A64/H5)
  136. encapsulate the BL31 part of ATF inside U-Boot. This option
  137. makes sure ATF gets built prior to U-Boot, and that the BL31
  138. variable pointing to ATF's BL31 binary, is passed during the
  139. Buildroot build.
  140. menu "U-Boot binary format"
  141. config BR2_TARGET_UBOOT_FORMAT_AIS
  142. bool "u-boot.ais"
  143. help
  144. AIS (Application Image Script) is a format defined by TI.
  145. It is required to load code/data on OMAP-L1 processors.
  146. u-boot.ais contains U-Boot with the SPL support.
  147. config BR2_TARGET_UBOOT_FORMAT_BIN
  148. bool "u-boot.bin"
  149. default y
  150. config BR2_TARGET_UBOOT_FORMAT_DTB_BIN
  151. bool "u-boot-dtb.bin"
  152. config BR2_TARGET_UBOOT_FORMAT_DTB_IMG
  153. bool "u-boot-dtb.img"
  154. config BR2_TARGET_UBOOT_FORMAT_DTB_IMX
  155. bool "u-boot-dtb.imx"
  156. config BR2_TARGET_UBOOT_FORMAT_IMG
  157. bool "u-boot.img"
  158. config BR2_TARGET_UBOOT_FORMAT_IMX
  159. bool "u-boot.imx"
  160. config BR2_TARGET_UBOOT_FORMAT_NAND_BIN
  161. bool "u-boot-nand.bin"
  162. config BR2_TARGET_UBOOT_FORMAT_KWB
  163. bool "u-boot.kwb (Marvell)"
  164. depends on BR2_arm
  165. config BR2_TARGET_UBOOT_FORMAT_ELF
  166. bool "u-boot.elf"
  167. config BR2_TARGET_UBOOT_FORMAT_SB
  168. bool "u-boot.sb (Freescale i.MX28)"
  169. depends on BR2_arm
  170. config BR2_TARGET_UBOOT_FORMAT_SD
  171. bool "u-boot.sd (Freescale i.MX28)"
  172. depends on BR2_arm
  173. help
  174. This is Freescale i.MX28 SB format, with a header for booting
  175. from an SD card.
  176. U-boot includes an mxsboot tool to generate this format,
  177. starting from 2011.12.
  178. See doc/README.mxs (or doc/README.mx28_common before 2013.07)
  179. config BR2_TARGET_UBOOT_FORMAT_NAND
  180. bool "u-boot.nand (Freescale i.MX28)"
  181. depends on BR2_arm
  182. help
  183. This is Freescale i.MX28 BootStream format (.sb), with a
  184. header for booting from a NAND flash.
  185. U-boot includes an mxsboot tool to generate this format,
  186. starting from 2011.12.
  187. There are two possibilities when preparing an image writable
  188. to NAND flash:
  189. 1) The NAND was not written at all yet or the BCB (Boot
  190. Control Blocks) is broken. In this case, the NAND image
  191. 'u-boot.nand' needs to written.
  192. 2) The NAND flash was already written with a good BCB. This
  193. applies after 'u-boot.nand' was correctly written. There is no
  194. need to write the BCB again. In this case, the bootloader can
  195. be upgraded by writing 'u-boot.sb'.
  196. To satisfy both cases, the 'u-boot.nand' image obtained from
  197. mxsboot as well as the U-Boot make target 'u-boot.sb' are
  198. copied to the binaries directory.
  199. See doc/README.mxs (or doc/README.mx28_common before 2013.07)
  200. if BR2_TARGET_UBOOT_FORMAT_NAND
  201. config BR2_TARGET_UBOOT_FORMAT_NAND_PAGE_SIZE
  202. int "NAND page size"
  203. default 2048
  204. help
  205. The NAND page size of the targets NAND flash in bytes as a
  206. decimal integer value.
  207. The value provided here is passed to the -w option of mxsboot.
  208. config BR2_TARGET_UBOOT_FORMAT_NAND_OOB_SIZE
  209. int "NAND OOB size"
  210. default 64
  211. help
  212. The NAND OOB size of the targets NAND flash in bytes as a
  213. decimal integer value.
  214. The value provided here is passed to the -o option of mxsboot.
  215. config BR2_TARGET_UBOOT_FORMAT_NAND_ERASE_SIZE
  216. int "NAND erase size"
  217. default 131072
  218. help
  219. The NAND eraseblock size of the targets NAND flash in bytes as
  220. a decimal integer value.
  221. The value provided here is passed to the -e option of mxsboot.
  222. endif
  223. config BR2_TARGET_UBOOT_FORMAT_CUSTOM
  224. bool "Custom (specify below)"
  225. help
  226. On some platforms, the standard U-Boot binary is not called
  227. u-boot.bin, but u-boot<something>.bin. If this is your case,
  228. you should select this option and specify the correct name(s)
  229. in BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME.
  230. config BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME
  231. string "U-Boot binary format: custom names"
  232. depends on BR2_TARGET_UBOOT_FORMAT_CUSTOM
  233. help
  234. In case the U-Boot binary for the target platform is not among
  235. the default names, one or more custom names can be listed
  236. here.
  237. Use space to separate multiple names.
  238. Example:
  239. u-boot_magic.bin
  240. endmenu
  241. config BR2_TARGET_UBOOT_OMAP_IFT
  242. bool "produce a .ift signed image (OMAP)"
  243. depends on BR2_TARGET_UBOOT_FORMAT_BIN
  244. depends on BR2_arm || BR2_armeb
  245. select BR2_PACKAGE_HOST_OMAP_U_BOOT_UTILS
  246. help
  247. Use gpsign to produce an image of u-boot.bin signed with
  248. a Configuration Header for booting on OMAP processors.
  249. This allows U-Boot to boot without the need for an
  250. intermediate bootloader (e.g. x-loader) if it is written
  251. on the first sector of the boot medium.
  252. This only works for some media, such as NAND. Check your
  253. chip documentation for details. You might also want to
  254. read the documentation of gpsign, the tool that generates
  255. the .ift image, at:
  256. https://github.com/nmenon/omap-u-boot-utils/blob/master/README
  257. if BR2_TARGET_UBOOT_OMAP_IFT
  258. config BR2_TARGET_UBOOT_OMAP_IFT_CONFIG
  259. string "gpsign Configuration Header config file"
  260. help
  261. The Configuration Header (CH) config file defines the
  262. desired content of the CH for the signed image.
  263. It usually contains external RAM settings and
  264. possibly other external devices initialization.
  265. The omap-u-boot-utils software contains example
  266. configuration files for some boards:
  267. https://github.com/nmenon/omap-u-boot-utils/tree/master/configs
  268. endif
  269. config BR2_TARGET_UBOOT_SPL
  270. bool "Install U-Boot SPL binary image"
  271. depends on !BR2_TARGET_XLOADER
  272. help
  273. Install the U-Boot SPL binary image to the images
  274. directory.
  275. SPL is a first stage bootloader loaded into internal
  276. memory in charge of enabling and configuring the
  277. external memory (DDR), and load the u-boot program
  278. into DDR.
  279. config BR2_TARGET_UBOOT_SPL_NAME
  280. string "U-Boot SPL/TPL binary image name(s)"
  281. default "spl/u-boot-spl.bin"
  282. depends on BR2_TARGET_UBOOT_SPL
  283. help
  284. A space-separated list of SPL/TPL binaries, generated during
  285. u-boot build. For most platform SPL name is spl/u-boot-spl.bin
  286. and TPL name is tpl/u-boot-tpl.bin but not always. SPL name is
  287. MLO on OMAP and SPL on i.MX6 for example.
  288. config BR2_TARGET_UBOOT_ZYNQ_IMAGE
  289. bool "Generate image for Xilinx Zynq"
  290. depends on BR2_arm
  291. depends on BR2_TARGET_UBOOT_SPL
  292. depends on BR2_TARGET_UBOOT_FORMAT_DTB_IMG
  293. help
  294. Generate the BOOT.BIN file from U-Boot's SPL. The image
  295. boots the Xilinx Zynq chip without any FPGA bitstream.
  296. A bitstream can be loaded by the U-Boot. The SPL searchs
  297. for u-boot-dtb.img file so this U-Boot format is required
  298. to be set.
  299. config BR2_TARGET_UBOOT_ZYNQMP
  300. bool "Boot on the Xilinx ZynqMP SoCs"
  301. depends on BR2_aarch64
  302. help
  303. Enable options specific to the Xilinx ZynqMP family of SoCs.
  304. if BR2_TARGET_UBOOT_ZYNQMP
  305. config BR2_TARGET_UBOOT_ZYNQMP_PMUFW
  306. string "PMU firmware location"
  307. depends on BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
  308. help
  309. Location of a PMU firmware binary.
  310. If not empty, instructs the U-Boot build process to generate
  311. a boot.bin (to be loaded by the ZynqMP boot ROM) containing
  312. both the U-Boot SPL and the PMU firmware in the
  313. Xilinx-specific boot format.
  314. The value can be an absolute or relative path, and will be
  315. used directly from where it is located, or an URI
  316. (e.g. http://...), and it will be downloaded and used from
  317. the download directory.
  318. If empty, the generated boot.bin will not contain a PMU
  319. firmware.
  320. This feature requires U-Boot >= 2018.07.
  321. config BR2_TARGET_UBOOT_ZYNQMP_PSU_INIT_FILE
  322. string "Custom psu_init_gpl file"
  323. depends on BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
  324. help
  325. On ZynqMP the booloader is responsible for some basic
  326. initializations, such as enabling peripherals and
  327. configuring pinmuxes. The psu_init_gpl.c file (and,
  328. optionally, psu_init_gpl.h) contains the code for such
  329. initializations.
  330. Although U-Boot contains psu_init_gpl.c files for some
  331. boards, each of them describes only one specific
  332. configuration. Users of a different board, or needing a
  333. different configuration, can generate custom files using the
  334. Xilinx development tools.
  335. Set this variable to the path to your psu_init_gpl.c file
  336. (e.g. "board/myboard/psu_init_gpl.c"). psu_init_gpl.h, if
  337. needed, should be in the same directory. U-Boot will build
  338. and link the user-provided file instead of the built-in one.
  339. Leave empty to use the files provided by U-Boot.
  340. This feature requires commit
  341. 6da4f67ad09cd8b311d77b2b04e557b7ef65b56c from upstream
  342. U-Boot, available from versions after 2018.07.
  343. endif
  344. config BR2_TARGET_UBOOT_ALTERA_SOCFPGA_IMAGE_CRC
  345. bool "CRC image for Altera SoC FPGA (mkpimage)"
  346. depends on BR2_arm
  347. depends on BR2_TARGET_UBOOT_SPL || BR2_TARGET_UBOOT_FORMAT_DTB_BIN
  348. help
  349. Pass the U-Boot image through the mkpimage tool to enable
  350. booting on the Altera SoC FPGA based platforms.
  351. On some platforms, it's the SPL that needs to be passed
  352. through mkpimage. On some other platforms there is no SPL
  353. because the internal SRAM is big enough to store the full
  354. U-Boot. In this case, it's directly the full U-Boot image
  355. that is passed through mkpimage.
  356. If BR2_TARGET_UBOOT_SPL is enabled then
  357. BR2_TARGET_UBOOT_SPL_NAME is converted by mkpimage using
  358. header version 0.
  359. Otherwise the full u-boot-dtb.bin is converted using
  360. mkpimage header version 1.
  361. In either case the resulting file will be given a .crc
  362. extension.
  363. menuconfig BR2_TARGET_UBOOT_ENVIMAGE
  364. bool "Environment image"
  365. help
  366. Generate a valid binary environment image from a text file
  367. describing the key=value pairs of the environment.
  368. The environment image will be called uboot-env.bin.
  369. if BR2_TARGET_UBOOT_ENVIMAGE
  370. config BR2_TARGET_UBOOT_ENVIMAGE_SOURCE
  371. string "Source files for environment"
  372. help
  373. Text files describing the environment. Files should have
  374. lines of the form var=value, one per line. Blank lines and
  375. lines starting with a # are ignored.
  376. Multiple source files are concatenated in the order listed.
  377. config BR2_TARGET_UBOOT_ENVIMAGE_SIZE
  378. string "Size of environment"
  379. help
  380. Size of envronment, can be prefixed with 0x for hexadecimal
  381. values.
  382. config BR2_TARGET_UBOOT_ENVIMAGE_REDUNDANT
  383. bool "Environment has two copies"
  384. help
  385. Some platforms define in their U-Boot configuration that the
  386. U-Boot environment should be duplicated in two locations (for
  387. extra safety). Check your U-Boot configuration for the
  388. CONFIG_ENV_ADDR_REDUND and CONFIG_ENV_SIZE_REDUND settings to
  389. see if this is the case for your platform.
  390. If it is the case, then you should enable this option to
  391. ensure that the U-Boot environment image generated by
  392. Buildroot is compatible with the "redundant environment"
  393. mechanism of U-Boot.
  394. endif # BR2_TARGET_UBOOT_ENVIMAGE
  395. config BR2_TARGET_UBOOT_BOOT_SCRIPT
  396. bool "Generate a U-Boot boot script"
  397. help
  398. Generate a U-Boot boot script, given a file listing U-Boot
  399. commands to be executed at boot time. The generated boot
  400. script will be called 'boot.scr'.
  401. if BR2_TARGET_UBOOT_BOOT_SCRIPT
  402. config BR2_TARGET_UBOOT_BOOT_SCRIPT_SOURCE
  403. string "U-Boot boot script source"
  404. help
  405. Source file to generate the U-Boot boot script.
  406. endif
  407. if BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
  408. config BR2_TARGET_UBOOT_CUSTOM_DTS_PATH
  409. string "Device Tree Source file paths"
  410. help
  411. Space-separated list of paths to device tree source files
  412. that will be copied to arch/ARCH/dts/ before starting the
  413. build.
  414. To use this device tree source file, the U-Boot configuration
  415. file must refer to it.
  416. endif
  417. endif # BR2_TARGET_UBOOT