2011-09-18 22:09:42 +02:00
|
|
|
config BR2_TARGET_UBOOT
|
2010-06-12 12:42:49 +02:00
|
|
|
bool "U-Boot"
|
2008-03-11 19:26:07 +01:00
|
|
|
help
|
|
|
|
Build "Das U-Boot" Boot Monitor
|
|
|
|
|
2019-12-27 16:35:34 +01:00
|
|
|
https://www.denx.de/wiki/U-Boot
|
|
|
|
|
2009-01-02 12:18:09 +01:00
|
|
|
if BR2_TARGET_UBOOT
|
2015-07-16 21:19:04 +02:00
|
|
|
choice
|
|
|
|
prompt "Build system"
|
2018-04-24 18:34:10 +02:00
|
|
|
default BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG if BR2_TARGET_UBOOT_LATEST_VERSION
|
2015-07-16 21:19:04 +02:00
|
|
|
default BR2_TARGET_UBOOT_BUILD_SYSTEM_LEGACY
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
|
|
|
|
bool "Kconfig"
|
|
|
|
help
|
2018-04-01 07:08:41 +02:00
|
|
|
Select this option if you use a recent U-Boot version (2015.04
|
|
|
|
or newer), so that we use the Kconfig build system.
|
2015-07-16 21:19:04 +02:00
|
|
|
|
2018-04-24 18:34:10 +02:00
|
|
|
config BR2_TARGET_UBOOT_BUILD_SYSTEM_LEGACY
|
|
|
|
bool "Legacy"
|
|
|
|
help
|
|
|
|
Select this option if you use an old U-Boot (older than
|
|
|
|
2015.04), so that we use the old build system.
|
|
|
|
|
2015-07-16 21:19:04 +02:00
|
|
|
endchoice
|
|
|
|
|
|
|
|
if BR2_TARGET_UBOOT_BUILD_SYSTEM_LEGACY
|
2009-01-03 01:02:07 +01:00
|
|
|
config BR2_TARGET_UBOOT_BOARDNAME
|
2010-06-12 12:42:49 +02:00
|
|
|
string "U-Boot board name"
|
2009-01-03 01:02:07 +01:00
|
|
|
help
|
|
|
|
One of U-Boot supported boards to be built.
|
2018-04-01 07:08:41 +02:00
|
|
|
This will be suffixed with _config to meet U-Boot standard
|
|
|
|
naming. See boards.cfg in U-Boot source code for the list of
|
|
|
|
available configurations.
|
2015-07-16 21:19:04 +02:00
|
|
|
endif
|
2009-01-03 01:02:07 +01:00
|
|
|
|
2009-01-02 12:18:09 +01:00
|
|
|
choice
|
|
|
|
prompt "U-Boot Version"
|
|
|
|
help
|
2009-01-08 15:58:51 +01:00
|
|
|
Select the specific U-Boot version you want to use
|
|
|
|
|
2013-05-06 23:07:46 +02:00
|
|
|
config BR2_TARGET_UBOOT_LATEST_VERSION
|
2021-10-09 10:28:55 +02:00
|
|
|
bool "2021.10"
|
2013-04-24 09:14:53 +02:00
|
|
|
|
2013-05-06 23:07:46 +02:00
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_VERSION
|
2013-11-11 17:23:23 +01:00
|
|
|
bool "Custom version"
|
2013-05-06 23:07:46 +02:00
|
|
|
help
|
|
|
|
This option allows to use a specific official versions
|
2011-07-11 22:46:17 +02:00
|
|
|
|
2010-06-12 13:18:04 +02:00
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_TARBALL
|
|
|
|
bool "Custom tarball"
|
|
|
|
|
2011-07-11 22:46:12 +02:00
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_GIT
|
|
|
|
bool "Custom Git repository"
|
|
|
|
|
2013-09-02 22:07:55 +02:00
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_HG
|
|
|
|
bool "Custom Mercurial repository"
|
|
|
|
|
2016-03-29 19:22:57 +02:00
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_SVN
|
|
|
|
bool "Custom Subversion repository"
|
|
|
|
|
2009-01-02 12:18:09 +01:00
|
|
|
endchoice
|
|
|
|
|
2013-05-06 23:07:46 +02:00
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE
|
|
|
|
string "U-Boot version"
|
|
|
|
depends on BR2_TARGET_UBOOT_CUSTOM_VERSION
|
|
|
|
|
2010-06-12 13:18:04 +02:00
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION
|
|
|
|
string "URL of custom U-Boot tarball"
|
2013-09-02 22:07:56 +02:00
|
|
|
depends on BR2_TARGET_UBOOT_CUSTOM_TARBALL
|
|
|
|
|
2016-03-29 19:22:57 +02:00
|
|
|
if BR2_TARGET_UBOOT_CUSTOM_GIT || BR2_TARGET_UBOOT_CUSTOM_HG || BR2_TARGET_UBOOT_CUSTOM_SVN
|
2013-09-02 22:07:56 +02:00
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_REPO_URL
|
|
|
|
string "URL of custom repository"
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION
|
|
|
|
string "Custom repository version"
|
|
|
|
help
|
2018-04-01 07:08:41 +02:00
|
|
|
Revision to use in the typical format used by
|
|
|
|
Git/Mercurial/Subversion E.G. a sha id, a tag, branch, ..
|
2010-06-12 13:18:04 +02:00
|
|
|
|
|
|
|
endif
|
|
|
|
|
2010-06-12 13:24:49 +02:00
|
|
|
config BR2_TARGET_UBOOT_VERSION
|
2009-01-02 12:18:09 +01:00
|
|
|
string
|
2021-10-09 10:28:55 +02:00
|
|
|
default "2021.10" if BR2_TARGET_UBOOT_LATEST_VERSION
|
2013-09-02 22:07:55 +02:00
|
|
|
default BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE \
|
|
|
|
if BR2_TARGET_UBOOT_CUSTOM_VERSION
|
2010-06-12 13:18:04 +02:00
|
|
|
default "custom" if BR2_TARGET_UBOOT_CUSTOM_TARBALL
|
2013-09-02 22:07:55 +02:00
|
|
|
default BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION \
|
2016-03-29 19:22:57 +02:00
|
|
|
if BR2_TARGET_UBOOT_CUSTOM_GIT || BR2_TARGET_UBOOT_CUSTOM_HG || BR2_TARGET_UBOOT_CUSTOM_SVN
|
2009-01-02 12:18:09 +01:00
|
|
|
|
2015-04-18 22:27:42 +02:00
|
|
|
config BR2_TARGET_UBOOT_PATCH
|
|
|
|
string "Custom U-Boot patches"
|
uboot: fix custom patch dir legacy handling
Commit 3e3fef39e71ed0426130b36aa00e4630ebb537ae added new and improved
patch handling, with BR2_TARGET_UBOOT_PATCH. This was in addition to
the existing BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR option, that only
handled directories.
Later, commit 21b25d28fc7af3bb1b2c55e4a46e0d067ebc0081 moved the old
BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR to legacy options. But on the way,
bad things happened:
* The original option was a string, while the one added to Config.in.legacy
is a bool. This results in a warning from defconfigs that actually define
the old BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR (because a string is not a valid
value for a bool), but it does not result in the legacy option being
selected. Consequently, BR2_LEGACY is not selected either.
* The advice at the top of Config.in.legacy to add a hidden WRAP option
to select BR2_LEGACY was not heeded.
* The advice at the top of Config.in.legacy to use the old string
option as the default for the new string option was not heeded. In
this case, the variable was not just renamed, as the old option
supported directories only, while the new one supports files too.
But since the old option is a subset of the new option, it can still
be used to set a useful default.
So, this mod turns the legacy option back to a string, adds a hidden
bool WRAP option to set BR2_LEGACY when the string is non emoty, and
uses the legacy option to set the default for the new option.
Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-20 04:10:12 +01:00
|
|
|
default BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR if BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR != "" # legacy
|
2015-04-18 22:27:42 +02:00
|
|
|
help
|
|
|
|
A space-separated list of patches to apply to U-Boot.
|
|
|
|
Each patch can be described as an URL, a local file path,
|
|
|
|
or a directory. In the case of a directory, all files
|
|
|
|
matching *.patch in the directory will be applied.
|
|
|
|
|
|
|
|
Most users may leave this empty
|
|
|
|
|
2015-07-16 21:19:04 +02:00
|
|
|
if BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
|
|
|
|
choice
|
|
|
|
prompt "U-Boot configuration"
|
|
|
|
default BR2_TARGET_UBOOT_USE_DEFCONFIG
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_USE_DEFCONFIG
|
|
|
|
bool "Using an in-tree board defconfig file"
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_USE_CUSTOM_CONFIG
|
|
|
|
bool "Using a custom board (def)config file"
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_BOARD_DEFCONFIG
|
|
|
|
string "Board defconfig"
|
|
|
|
depends on BR2_TARGET_UBOOT_USE_DEFCONFIG
|
|
|
|
help
|
|
|
|
Name of the board for which U-Boot should be built, without
|
|
|
|
the _defconfig suffix.
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_CONFIG_FILE
|
|
|
|
string "Configuration file path"
|
|
|
|
depends on BR2_TARGET_UBOOT_USE_CUSTOM_CONFIG
|
|
|
|
help
|
|
|
|
Path to the U-Boot configuration file.
|
2017-10-06 15:46:33 +02:00
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_CONFIG_FRAGMENT_FILES
|
|
|
|
string "Additional configuration fragment files"
|
|
|
|
help
|
|
|
|
A space-separated list of configuration fragment files,
|
|
|
|
that will be merged to the main U-Boot configuration file.
|
2015-07-16 21:19:04 +02:00
|
|
|
endif
|
|
|
|
|
2015-10-03 21:44:13 +02:00
|
|
|
config BR2_TARGET_UBOOT_NEEDS_DTC
|
|
|
|
bool "U-Boot needs dtc"
|
|
|
|
select BR2_PACKAGE_HOST_DTC
|
|
|
|
help
|
|
|
|
Select this option if your U-Boot board configuration
|
|
|
|
requires the Device Tree compiler to be available.
|
|
|
|
|
boot/uboot: support building U-Boot with Python 3.x
U-Boot versions newer than 2020.01 use Python 3.x instead of Python
2.x in various scripts.
We already had the BR2_TARGET_UBOOT_NEEDS_PYLIBFDT and
BR2_TARGET_UBOOT_NEEDS_PYELFTOOLS options, but depending on the U-Boot
version, we now need to indicate if Python 2.x or Python 3.x should be
used.
In addition, it turns out that some U-Boot configurations need a
Python interpreter, without needing pylibfdt or pyelftools. Some of
our defconfigs were abusing the BR2_TARGET_UBOOT_NEEDS_PYLIBFDT option
to make sure a Python interpreter was built.
To solve this issue, we introduce a choice, that let the users specify
what, if any, host python version is needed. The default is 'no', to
preserve the previous behaviour, unless any of the pylibfdt or the
pyelftools options is enabled, in which case we hide the 'no' option,
and use python 2 by default. This dfault is guaranteed by the order of
options in the choice.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
[yann.morin.1998@free.fr:
- explicitly make the choice a bool
- make BR2_TARGET_UBOOT_NEEDS_PYTHON a blind option
- introduce the 'no' option in the choice
- reword the commit log accordingly
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-05-02 23:28:08 +02:00
|
|
|
config BR2_TARGET_UBOOT_NEEDS_PYTHON
|
|
|
|
bool
|
|
|
|
|
|
|
|
choice
|
|
|
|
bool "U-Boot needs host Python"
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_NEEDS_PYTHON_NONE
|
|
|
|
bool "no"
|
|
|
|
depends on !BR2_TARGET_UBOOT_NEEDS_PYTHON
|
|
|
|
help
|
|
|
|
Select this option if U-Boot does not need any
|
|
|
|
host python to build.
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_NEEDS_PYTHON2
|
|
|
|
bool "python 2.x"
|
|
|
|
help
|
|
|
|
Select this option if U-Boot needs a host Python 2.x
|
|
|
|
interpreter. This is the case for some U-Boot
|
|
|
|
configurations, prior to U-Boot 2020.01.
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_NEEDS_PYTHON3
|
|
|
|
bool "python 3.x"
|
|
|
|
help
|
|
|
|
Select this option if U-Boot needs a host Python 3.x
|
|
|
|
interpreter. This is the case for some U-Boot
|
|
|
|
configurations, after U-Boot 2020.01.
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
2017-07-12 21:29:03 +02:00
|
|
|
config BR2_TARGET_UBOOT_NEEDS_PYLIBFDT
|
|
|
|
bool "U-Boot needs pylibfdt"
|
boot/uboot: support building U-Boot with Python 3.x
U-Boot versions newer than 2020.01 use Python 3.x instead of Python
2.x in various scripts.
We already had the BR2_TARGET_UBOOT_NEEDS_PYLIBFDT and
BR2_TARGET_UBOOT_NEEDS_PYELFTOOLS options, but depending on the U-Boot
version, we now need to indicate if Python 2.x or Python 3.x should be
used.
In addition, it turns out that some U-Boot configurations need a
Python interpreter, without needing pylibfdt or pyelftools. Some of
our defconfigs were abusing the BR2_TARGET_UBOOT_NEEDS_PYLIBFDT option
to make sure a Python interpreter was built.
To solve this issue, we introduce a choice, that let the users specify
what, if any, host python version is needed. The default is 'no', to
preserve the previous behaviour, unless any of the pylibfdt or the
pyelftools options is enabled, in which case we hide the 'no' option,
and use python 2 by default. This dfault is guaranteed by the order of
options in the choice.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
[yann.morin.1998@free.fr:
- explicitly make the choice a bool
- make BR2_TARGET_UBOOT_NEEDS_PYTHON a blind option
- introduce the 'no' option in the choice
- reword the commit log accordingly
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-05-02 23:28:08 +02:00
|
|
|
select BR2_TARGET_UBOOT_NEEDS_PYTHON
|
2017-07-12 21:29:03 +02:00
|
|
|
help
|
|
|
|
Select this option if your U-Boot board configuration
|
|
|
|
requires the Python libfdt library to be available.
|
|
|
|
|
2019-04-18 15:23:31 +02:00
|
|
|
config BR2_TARGET_UBOOT_NEEDS_PYELFTOOLS
|
|
|
|
bool "U-Boot needs pyelftools"
|
boot/uboot: support building U-Boot with Python 3.x
U-Boot versions newer than 2020.01 use Python 3.x instead of Python
2.x in various scripts.
We already had the BR2_TARGET_UBOOT_NEEDS_PYLIBFDT and
BR2_TARGET_UBOOT_NEEDS_PYELFTOOLS options, but depending on the U-Boot
version, we now need to indicate if Python 2.x or Python 3.x should be
used.
In addition, it turns out that some U-Boot configurations need a
Python interpreter, without needing pylibfdt or pyelftools. Some of
our defconfigs were abusing the BR2_TARGET_UBOOT_NEEDS_PYLIBFDT option
to make sure a Python interpreter was built.
To solve this issue, we introduce a choice, that let the users specify
what, if any, host python version is needed. The default is 'no', to
preserve the previous behaviour, unless any of the pylibfdt or the
pyelftools options is enabled, in which case we hide the 'no' option,
and use python 2 by default. This dfault is guaranteed by the order of
options in the choice.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
[yann.morin.1998@free.fr:
- explicitly make the choice a bool
- make BR2_TARGET_UBOOT_NEEDS_PYTHON a blind option
- introduce the 'no' option in the choice
- reword the commit log accordingly
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-05-02 23:28:08 +02:00
|
|
|
select BR2_TARGET_UBOOT_NEEDS_PYTHON
|
2019-04-18 15:23:31 +02:00
|
|
|
help
|
|
|
|
Select this option if your U-Boot board configuration
|
|
|
|
requires the Python pyelftools library to be available.
|
|
|
|
This is used by some rockchip SOCs for elf parsing.
|
|
|
|
For example: rk3399 soc boards.
|
|
|
|
|
2016-10-16 09:42:22 +02:00
|
|
|
config BR2_TARGET_UBOOT_NEEDS_OPENSSL
|
|
|
|
bool "U-Boot needs OpenSSL"
|
|
|
|
help
|
|
|
|
Select this option if your U-Boot board configuration
|
|
|
|
requires OpenSSL to be available on the host. This is
|
|
|
|
typically the case when the board configuration has
|
|
|
|
CONFIG_FIT_SIGNATURE enabled.
|
|
|
|
|
2018-07-28 22:11:52 +02:00
|
|
|
config BR2_TARGET_UBOOT_NEEDS_LZOP
|
|
|
|
bool "U-Boot needs lzop"
|
|
|
|
help
|
|
|
|
Select this option if your U-Boot board configuration
|
|
|
|
requires lzop to be available on the host. This is typically
|
|
|
|
the case when the board configuration has CONFIG_SPL_LZO
|
|
|
|
enabled.
|
|
|
|
|
2017-12-03 22:48:07 +01:00
|
|
|
config BR2_TARGET_UBOOT_NEEDS_ATF_BL31
|
|
|
|
bool "U-Boot needs ATF BL31"
|
|
|
|
depends on BR2_TARGET_ARM_TRUSTED_FIRMWARE
|
2017-12-08 14:13:38 +01:00
|
|
|
depends on !BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_AS_BL33
|
2017-12-03 22:48:07 +01:00
|
|
|
select BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31
|
|
|
|
help
|
|
|
|
Some specific platforms (such as Allwinner A64/H5)
|
|
|
|
encapsulate the BL31 part of ATF inside U-Boot. This option
|
|
|
|
makes sure ATF gets built prior to U-Boot, and that the BL31
|
|
|
|
variable pointing to ATF's BL31 binary, is passed during the
|
|
|
|
Buildroot build.
|
|
|
|
|
2018-11-11 22:39:42 +01:00
|
|
|
choice
|
|
|
|
prompt "U-Boot ATF BL31 format"
|
|
|
|
default BR2_TARGET_UBOOT_NEEDS_ATF_BL31_BIN
|
2019-02-06 22:21:15 +01:00
|
|
|
depends on BR2_TARGET_UBOOT_NEEDS_ATF_BL31
|
2018-11-11 22:39:42 +01:00
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_NEEDS_ATF_BL31_BIN
|
|
|
|
bool "bl31.bin"
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_NEEDS_ATF_BL31_ELF
|
|
|
|
bool "bl31.elf"
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
2020-01-19 01:28:05 +01:00
|
|
|
config BR2_TARGET_UBOOT_NEEDS_OPTEE_TEE
|
|
|
|
bool "U-Boot needs OPTEE TEE"
|
|
|
|
depends on BR2_TARGET_OPTEE_OS_CORE
|
|
|
|
help
|
|
|
|
Some platforms (such as Rockchip) encapsulate the TEE inside
|
|
|
|
U-Boot. This option makes sure optee-os gets built prior to
|
|
|
|
U-Boot, and that the TEE variable pointing to OPTEE's
|
|
|
|
tee.elf, is passed during the Buildroot build.
|
|
|
|
|
2021-01-11 10:01:11 +01:00
|
|
|
config BR2_TARGET_UBOOT_NEEDS_OPENSBI
|
|
|
|
bool "U-Boot needs OpenSBI"
|
|
|
|
depends on BR2_TARGET_OPENSBI
|
|
|
|
help
|
|
|
|
Some RISC-V platforms (such as SiFive HiFive Unleashed)
|
|
|
|
encapsulate the OpenSBI firmware image inside U-Boot.
|
|
|
|
This option makes sure OpenSBI gets built prior to U-Boot,
|
|
|
|
and that the OpenSBI variable pointing to OpenSBI binary,
|
|
|
|
is passed during the Buildroot build.
|
|
|
|
|
2021-09-12 07:09:06 +02:00
|
|
|
config BR2_TARGET_UBOOT_NEEDS_IMX_FIRMWARE
|
|
|
|
bool "U-Boot needs firmware-imx"
|
|
|
|
depends on BR2_PACKAGE_FIRMWARE_IMX
|
|
|
|
depends on BR2_PACKAGE_FIRMWARE_IMX_NEEDS_DDR_FW || \
|
|
|
|
BR2_PACKAGE_FIRMWARE_IMX_NEEDS_HDMI_FW
|
|
|
|
help
|
2021-09-12 14:03:03 +02:00
|
|
|
Some i.MX8 platforms (such as i.MX8 M, i.MX 8M Mini, i.MX 8M
|
|
|
|
Nano) encapsulate NXP specific firmware (DDR, HDMI) inside
|
|
|
|
U-Boot.
|
2021-09-12 07:09:06 +02:00
|
|
|
This option makes sure that the i.MX firmwares are copied into
|
|
|
|
the U-Boot source directory.
|
|
|
|
|
2016-09-02 14:26:26 +02:00
|
|
|
menu "U-Boot binary format"
|
2012-08-09 20:11:09 +02:00
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_FORMAT_AIS
|
|
|
|
bool "u-boot.ais"
|
|
|
|
help
|
|
|
|
AIS (Application Image Script) is a format defined by TI.
|
|
|
|
It is required to load code/data on OMAP-L1 processors.
|
|
|
|
u-boot.ais contains U-Boot with the SPL support.
|
2010-07-26 16:14:41 +02:00
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_FORMAT_BIN
|
|
|
|
bool "u-boot.bin"
|
2016-09-02 14:26:26 +02:00
|
|
|
default y
|
2010-07-26 16:14:41 +02:00
|
|
|
|
2021-06-16 07:03:39 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_DTB
|
|
|
|
bool "u-boot.dtb"
|
|
|
|
|
2017-02-13 14:59:33 +01:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_DTB_BIN
|
|
|
|
bool "u-boot-dtb.bin"
|
|
|
|
|
2020-10-04 15:10:49 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_NAND_BIN
|
|
|
|
bool "u-boot-nand.bin"
|
2015-07-14 17:14:01 +02:00
|
|
|
|
2020-10-04 15:10:49 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_ELF
|
|
|
|
bool "u-boot.elf"
|
2018-07-05 21:24:29 +02:00
|
|
|
|
2012-03-18 23:04:51 +01:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_IMG
|
|
|
|
bool "u-boot.img"
|
|
|
|
|
2020-10-04 15:10:49 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_DTB_IMG
|
|
|
|
bool "u-boot-dtb.img"
|
2019-12-03 22:36:22 +01:00
|
|
|
|
2013-09-26 16:41:25 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_IMX
|
|
|
|
bool "u-boot.imx"
|
|
|
|
|
2020-10-04 15:10:49 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_DTB_IMX
|
|
|
|
bool "u-boot-dtb.imx"
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_FORMAT_ITB
|
|
|
|
bool "u-boot.itb"
|
2011-12-01 16:04:58 +01:00
|
|
|
|
2010-07-26 16:14:41 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_KWB
|
|
|
|
bool "u-boot.kwb (Marvell)"
|
2018-04-01 07:08:35 +02:00
|
|
|
depends on BR2_arm
|
2010-07-26 16:14:41 +02:00
|
|
|
|
2015-03-29 18:10:46 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_NAND
|
2015-07-11 14:10:56 +02:00
|
|
|
bool "u-boot.nand (Freescale i.MX28)"
|
2018-04-01 07:08:35 +02:00
|
|
|
depends on BR2_arm
|
2015-03-29 18:10:46 +02:00
|
|
|
help
|
2018-04-01 07:08:41 +02:00
|
|
|
This is Freescale i.MX28 BootStream format (.sb), with a
|
|
|
|
header for booting from a NAND flash.
|
2015-03-29 18:10:46 +02:00
|
|
|
|
2019-08-04 14:22:52 +02:00
|
|
|
U-Boot includes an mxsboot tool to generate this format,
|
2015-03-29 18:10:46 +02:00
|
|
|
starting from 2011.12.
|
|
|
|
|
2018-04-01 07:08:41 +02:00
|
|
|
There are two possibilities when preparing an image writable
|
|
|
|
to NAND flash:
|
|
|
|
1) The NAND was not written at all yet or the BCB (Boot
|
|
|
|
Control Blocks) is broken. In this case, the NAND image
|
|
|
|
'u-boot.nand' needs to written.
|
2015-03-29 18:10:46 +02:00
|
|
|
2) The NAND flash was already written with a good BCB. This
|
|
|
|
applies after 'u-boot.nand' was correctly written. There is no
|
2018-04-01 07:08:41 +02:00
|
|
|
need to write the BCB again. In this case, the bootloader can
|
|
|
|
be upgraded by writing 'u-boot.sb'.
|
2015-03-29 18:10:46 +02:00
|
|
|
|
|
|
|
To satisfy both cases, the 'u-boot.nand' image obtained from
|
2018-04-01 07:08:41 +02:00
|
|
|
mxsboot as well as the U-Boot make target 'u-boot.sb' are
|
|
|
|
copied to the binaries directory.
|
2015-03-29 18:10:46 +02:00
|
|
|
|
|
|
|
See doc/README.mxs (or doc/README.mx28_common before 2013.07)
|
|
|
|
|
|
|
|
if BR2_TARGET_UBOOT_FORMAT_NAND
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_FORMAT_NAND_PAGE_SIZE
|
|
|
|
int "NAND page size"
|
|
|
|
default 2048
|
|
|
|
help
|
|
|
|
The NAND page size of the targets NAND flash in bytes as a
|
|
|
|
decimal integer value.
|
|
|
|
|
|
|
|
The value provided here is passed to the -w option of mxsboot.
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_FORMAT_NAND_OOB_SIZE
|
|
|
|
int "NAND OOB size"
|
|
|
|
default 64
|
|
|
|
help
|
|
|
|
The NAND OOB size of the targets NAND flash in bytes as a
|
|
|
|
decimal integer value.
|
|
|
|
|
|
|
|
The value provided here is passed to the -o option of mxsboot.
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_FORMAT_NAND_ERASE_SIZE
|
|
|
|
int "NAND erase size"
|
|
|
|
default 131072
|
|
|
|
help
|
|
|
|
The NAND eraseblock size of the targets NAND flash in bytes as
|
|
|
|
a decimal integer value.
|
|
|
|
|
|
|
|
The value provided here is passed to the -e option of mxsboot.
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
2020-10-04 15:10:49 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_SB
|
|
|
|
bool "u-boot.sb (Freescale i.MX28)"
|
|
|
|
depends on BR2_arm
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_FORMAT_SD
|
|
|
|
bool "u-boot.sd (Freescale i.MX28)"
|
|
|
|
depends on BR2_arm
|
|
|
|
help
|
|
|
|
This is Freescale i.MX28 SB format, with a header for booting
|
|
|
|
from an SD card.
|
|
|
|
|
|
|
|
U-Boot includes an mxsboot tool to generate this format,
|
|
|
|
starting from 2011.12.
|
|
|
|
|
|
|
|
See doc/README.mxs (or doc/README.mx28_common before 2013.07)
|
|
|
|
|
2020-10-07 16:49:42 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_STM32
|
|
|
|
bool "u-boot.stm32"
|
|
|
|
depends on BR2_arm
|
|
|
|
|
2013-07-24 11:50:14 +02:00
|
|
|
config BR2_TARGET_UBOOT_FORMAT_CUSTOM
|
|
|
|
bool "Custom (specify below)"
|
|
|
|
help
|
|
|
|
On some platforms, the standard U-Boot binary is not called
|
|
|
|
u-boot.bin, but u-boot<something>.bin. If this is your case,
|
2016-09-02 14:26:26 +02:00
|
|
|
you should select this option and specify the correct name(s)
|
2013-07-24 11:50:14 +02:00
|
|
|
in BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME.
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME
|
2016-09-02 14:26:26 +02:00
|
|
|
string "U-Boot binary format: custom names"
|
2013-07-24 11:50:14 +02:00
|
|
|
depends on BR2_TARGET_UBOOT_FORMAT_CUSTOM
|
|
|
|
help
|
2016-09-02 14:26:26 +02:00
|
|
|
In case the U-Boot binary for the target platform is not among
|
2018-04-01 07:08:41 +02:00
|
|
|
the default names, one or more custom names can be listed
|
|
|
|
here.
|
2016-09-02 14:26:26 +02:00
|
|
|
Use space to separate multiple names.
|
|
|
|
Example:
|
2013-07-24 11:50:14 +02:00
|
|
|
u-boot_magic.bin
|
|
|
|
|
2016-09-02 14:26:26 +02:00
|
|
|
endmenu
|
|
|
|
|
2012-05-17 12:11:31 +02:00
|
|
|
config BR2_TARGET_UBOOT_OMAP_IFT
|
2018-04-01 07:08:35 +02:00
|
|
|
bool "produce a .ift signed image (OMAP)"
|
2012-05-17 12:11:31 +02:00
|
|
|
depends on BR2_TARGET_UBOOT_FORMAT_BIN
|
|
|
|
depends on BR2_arm || BR2_armeb
|
|
|
|
select BR2_PACKAGE_HOST_OMAP_U_BOOT_UTILS
|
|
|
|
help
|
|
|
|
Use gpsign to produce an image of u-boot.bin signed with
|
|
|
|
a Configuration Header for booting on OMAP processors.
|
|
|
|
This allows U-Boot to boot without the need for an
|
|
|
|
intermediate bootloader (e.g. x-loader) if it is written
|
|
|
|
on the first sector of the boot medium.
|
|
|
|
This only works for some media, such as NAND. Check your
|
|
|
|
chip documentation for details. You might also want to
|
|
|
|
read the documentation of gpsign, the tool that generates
|
|
|
|
the .ift image, at:
|
|
|
|
https://github.com/nmenon/omap-u-boot-utils/blob/master/README
|
|
|
|
|
|
|
|
if BR2_TARGET_UBOOT_OMAP_IFT
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_OMAP_IFT_CONFIG
|
|
|
|
string "gpsign Configuration Header config file"
|
|
|
|
help
|
|
|
|
The Configuration Header (CH) config file defines the
|
|
|
|
desired content of the CH for the signed image.
|
|
|
|
It usually contains external RAM settings and
|
|
|
|
possibly other external devices initialization.
|
|
|
|
The omap-u-boot-utils software contains example
|
|
|
|
configuration files for some boards:
|
|
|
|
https://github.com/nmenon/omap-u-boot-utils/tree/master/configs
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
2012-03-18 23:04:50 +01:00
|
|
|
config BR2_TARGET_UBOOT_SPL
|
2014-12-13 00:16:05 +01:00
|
|
|
bool "Install U-Boot SPL binary image"
|
2012-03-18 23:04:50 +01:00
|
|
|
depends on !BR2_TARGET_XLOADER
|
|
|
|
help
|
2014-12-13 00:16:05 +01:00
|
|
|
Install the U-Boot SPL binary image to the images
|
|
|
|
directory.
|
|
|
|
SPL is a first stage bootloader loaded into internal
|
|
|
|
memory in charge of enabling and configuring the
|
|
|
|
external memory (DDR), and load the u-boot program
|
|
|
|
into DDR.
|
2012-03-18 23:04:50 +01:00
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_SPL_NAME
|
2017-11-18 10:28:47 +01:00
|
|
|
string "U-Boot SPL/TPL binary image name(s)"
|
2014-05-29 23:13:02 +02:00
|
|
|
default "spl/u-boot-spl.bin"
|
2012-03-18 23:04:50 +01:00
|
|
|
depends on BR2_TARGET_UBOOT_SPL
|
|
|
|
help
|
2017-11-18 10:28:47 +01:00
|
|
|
A space-separated list of SPL/TPL binaries, generated during
|
|
|
|
u-boot build. For most platform SPL name is spl/u-boot-spl.bin
|
|
|
|
and TPL name is tpl/u-boot-tpl.bin but not always. SPL name is
|
|
|
|
MLO on OMAP and SPL on i.MX6 for example.
|
2012-03-18 23:04:50 +01:00
|
|
|
|
2015-07-14 17:16:02 +02:00
|
|
|
config BR2_TARGET_UBOOT_ZYNQ_IMAGE
|
|
|
|
bool "Generate image for Xilinx Zynq"
|
|
|
|
depends on BR2_arm
|
|
|
|
depends on BR2_TARGET_UBOOT_SPL
|
|
|
|
depends on BR2_TARGET_UBOOT_FORMAT_DTB_IMG
|
|
|
|
help
|
2016-03-09 22:30:32 +01:00
|
|
|
Generate the BOOT.BIN file from U-Boot's SPL. The image
|
|
|
|
boots the Xilinx Zynq chip without any FPGA bitstream.
|
|
|
|
A bitstream can be loaded by the U-Boot. The SPL searchs
|
|
|
|
for u-boot-dtb.img file so this U-Boot format is required
|
|
|
|
to be set.
|
2015-07-14 17:16:02 +02:00
|
|
|
|
2018-07-25 16:35:36 +02:00
|
|
|
config BR2_TARGET_UBOOT_ZYNQMP
|
|
|
|
bool "Boot on the Xilinx ZynqMP SoCs"
|
|
|
|
depends on BR2_aarch64
|
|
|
|
help
|
|
|
|
Enable options specific to the Xilinx ZynqMP family of SoCs.
|
|
|
|
|
|
|
|
if BR2_TARGET_UBOOT_ZYNQMP
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_ZYNQMP_PMUFW
|
|
|
|
string "PMU firmware location"
|
|
|
|
depends on BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
|
|
|
|
help
|
|
|
|
Location of a PMU firmware binary.
|
|
|
|
|
|
|
|
If not empty, instructs the U-Boot build process to generate
|
|
|
|
a boot.bin (to be loaded by the ZynqMP boot ROM) containing
|
|
|
|
both the U-Boot SPL and the PMU firmware in the
|
|
|
|
Xilinx-specific boot format.
|
|
|
|
|
|
|
|
The value can be an absolute or relative path, and will be
|
|
|
|
used directly from where it is located, or an URI
|
|
|
|
(e.g. http://...), and it will be downloaded and used from
|
|
|
|
the download directory.
|
|
|
|
|
|
|
|
If empty, the generated boot.bin will not contain a PMU
|
|
|
|
firmware.
|
|
|
|
|
|
|
|
This feature requires U-Boot >= 2018.07.
|
|
|
|
|
2020-06-26 17:59:56 +02:00
|
|
|
config BR2_TARGET_UBOOT_ZYNQMP_PM_CFG
|
|
|
|
string "PMU configuration location"
|
|
|
|
depends on BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
|
|
|
|
help
|
|
|
|
Location of a PMU configuration file.
|
|
|
|
|
|
|
|
If not empty, Buildroot will convert the PMU configuration
|
|
|
|
file into a loadable blob and pass it to U-Boot. The blob gets
|
|
|
|
embedded into the U-Boot SPL and is used to configure the PMU
|
|
|
|
during board initialization.
|
|
|
|
|
|
|
|
Unlike the PMU firmware, the PMU configuration file is unique
|
|
|
|
to each board configuration. A PMU configuration file can be
|
|
|
|
generated by building your Xilinx SDK BSP. It can be found in
|
|
|
|
the BSP source, for example at
|
|
|
|
./psu_cortexa53_0/libsrc/xilpm_v2_4/src/pm_cfg_obj.c
|
|
|
|
|
|
|
|
Leave this option empty if your PMU firmware has a hard-coded
|
|
|
|
configuration object or you are loading it by any other means.
|
|
|
|
|
|
|
|
This feature requires U-Boot >= v2019.10.
|
|
|
|
|
2018-07-25 16:35:38 +02:00
|
|
|
config BR2_TARGET_UBOOT_ZYNQMP_PSU_INIT_FILE
|
|
|
|
string "Custom psu_init_gpl file"
|
|
|
|
depends on BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
|
|
|
|
help
|
|
|
|
On ZynqMP the booloader is responsible for some basic
|
|
|
|
initializations, such as enabling peripherals and
|
|
|
|
configuring pinmuxes. The psu_init_gpl.c file (and,
|
|
|
|
optionally, psu_init_gpl.h) contains the code for such
|
|
|
|
initializations.
|
|
|
|
|
|
|
|
Although U-Boot contains psu_init_gpl.c files for some
|
|
|
|
boards, each of them describes only one specific
|
|
|
|
configuration. Users of a different board, or needing a
|
|
|
|
different configuration, can generate custom files using the
|
|
|
|
Xilinx development tools.
|
|
|
|
|
|
|
|
Set this variable to the path to your psu_init_gpl.c file
|
|
|
|
(e.g. "board/myboard/psu_init_gpl.c"). psu_init_gpl.h, if
|
|
|
|
needed, should be in the same directory. U-Boot will build
|
|
|
|
and link the user-provided file instead of the built-in one.
|
|
|
|
|
|
|
|
Leave empty to use the files provided by U-Boot.
|
|
|
|
|
|
|
|
This feature requires commit
|
|
|
|
6da4f67ad09cd8b311d77b2b04e557b7ef65b56c from upstream
|
|
|
|
U-Boot, available from versions after 2018.07.
|
|
|
|
|
2018-07-25 16:35:36 +02:00
|
|
|
endif
|
|
|
|
|
2015-10-20 13:32:20 +02:00
|
|
|
config BR2_TARGET_UBOOT_ALTERA_SOCFPGA_IMAGE_CRC
|
2017-02-13 16:33:29 +01:00
|
|
|
bool "CRC image for Altera SoC FPGA (mkpimage)"
|
2015-10-20 13:32:20 +02:00
|
|
|
depends on BR2_arm
|
2017-02-13 16:33:29 +01:00
|
|
|
depends on BR2_TARGET_UBOOT_SPL || BR2_TARGET_UBOOT_FORMAT_DTB_BIN
|
2015-10-20 13:32:20 +02:00
|
|
|
help
|
2017-02-13 16:33:29 +01:00
|
|
|
Pass the U-Boot image through the mkpimage tool to enable
|
2015-10-20 13:32:20 +02:00
|
|
|
booting on the Altera SoC FPGA based platforms.
|
|
|
|
|
2017-02-13 16:33:29 +01:00
|
|
|
On some platforms, it's the SPL that needs to be passed
|
|
|
|
through mkpimage. On some other platforms there is no SPL
|
|
|
|
because the internal SRAM is big enough to store the full
|
|
|
|
U-Boot. In this case, it's directly the full U-Boot image
|
|
|
|
that is passed through mkpimage.
|
|
|
|
|
|
|
|
If BR2_TARGET_UBOOT_SPL is enabled then
|
|
|
|
BR2_TARGET_UBOOT_SPL_NAME is converted by mkpimage using
|
|
|
|
header version 0.
|
|
|
|
|
|
|
|
Otherwise the full u-boot-dtb.bin is converted using
|
|
|
|
mkpimage header version 1.
|
|
|
|
|
|
|
|
In either case the resulting file will be given a .crc
|
|
|
|
extension.
|
|
|
|
|
2017-04-05 05:45:51 +02:00
|
|
|
if BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
|
|
|
|
|
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_DTS_PATH
|
|
|
|
string "Device Tree Source file paths"
|
|
|
|
help
|
|
|
|
Space-separated list of paths to device tree source files
|
|
|
|
that will be copied to arch/ARCH/dts/ before starting the
|
|
|
|
build.
|
|
|
|
|
|
|
|
To use this device tree source file, the U-Boot configuration
|
|
|
|
file must refer to it.
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
2019-04-26 17:19:46 +02:00
|
|
|
config BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS
|
|
|
|
string "Custom make options"
|
|
|
|
help
|
|
|
|
List of custom make options passed at build time. Can be
|
|
|
|
used for example to pass a DEVICE_TREE= value.
|
|
|
|
|
2009-01-08 15:58:54 +01:00
|
|
|
endif # BR2_TARGET_UBOOT
|