| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Might as well have it in one place instead of duplicating it between both.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Id87649691c93d0dbdc08d2484ca59a85cb54a3eb
|
|
The 32MB and 64MB NOR environments are the same configuration, so use
the one file.
The AST2600 NOR layout is the same size as the others so it can use the
same file too.
Change-Id: I6ee3fbf0d68104bcc684c2536fe85c5aec76c409
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
OpenBMC places kernel at offset 512 if the flash size is 32MB,
but it was defined as 1024 in the present defconfig.
This patch corrects the offset if the flash size is set to 32MB.
Signed-off-by: Howard Chiu <howard_chiu@aspeedtech.com>
Change-Id: I05749eda519cc1660921e111a36be74cb121fa68
|
|
Previously, the u-boot-fw-utils-aspeed-sdk build didn't take *.cfg files
in SRC_URI into account at all, leading to problematic mismatches
between fw_{set,print}env's configuration and that of u-boot itself
(such as discrepancies in their respective notions of what the default
environment should be).
With this change the fw-utils build uses the same do_configure as the
regular u-boot build, so the two packages can more easily be built with
a single consistent configuration.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ia83768597b6b75dc00425bdc23f216274d87e0ae
|
|
When using 64M flash, the config of u-boot CONFIG_ENV_SIZE and
CONFIG_ENV_OFFSET is wrong. The config file fw_env.config is wrong, too.
Modify them according to the 64M flash dts file.
Before correcting these errors, when we used setenv to set environment
variables in u-boot, we could not use fw_printenv to get them. The
reverse is also the same. Because they set different offset and size.
Tested:
1. Use commands in u-boot:
setenv test value
saveenv
After BMC starts, use fw_printenv can get "test=value"
2. Use the command to change the value of "test"
fw_setenv test v
We can get "test=v" in u-boot by printenv.
Signed-off-by: zhanghaicheng <zhanghch05@inspur.com>
Change-Id: I9eccf6abe743253b6f8c344a8b8648e68ab52019
|
|
Move u-boot-aspeed-sdk to use u-boot.inc from poki instead our own. We
still need our own one for old u-boot-aspeed, so keep it as is.
Tested: Build image for AST2500-based machine with
u-boot-aspeed-sdk_2019.04, verified that it boots up and fw-utils
installed to the image properly.
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: Ia5fecdedc94e9550196420884a727e7d87b313d4
|
|
This fixes some build errors we faced due to add new ast2500-based
platform.
* Allow to redefine input env file.
* Backport providing "u-boot-default-env" from u-boot.inc
* PROVIDES += "u-boot-fw-utils" is not enough, add also RPROVIDES
Last two changes allows to exclude from build modern libubootenv which
somewhy doesn't work for us.
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I33f152c572f6c0b4d8b608375b252290efacd1ea
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8135871ae0e3b360aff7d878f7cf04a2504f2dd0
|
|
Create a fw_env.config for eMMC with a redundant environment
based on the mmc distro feature. The environment is located in
the first eMMC partition in the User Data area.
(From meta-aspeed rev: 3aa2db46e8097aa0a9627684686ca56b5d6b9872)
Change-Id: I6e768e308f03513c6cf394a0adc7110d17322d49
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The configuration was not set at all, leaving us with the default
configuration file from u-boot.
This sets it to the u-boot environment partition, /dev/mtd2.
(From meta-aspeed rev: fc48e308dd25b99535a5412cbbdf1fcd66238a9b)
Change-Id: Ied346a6c15f0068b8ab54cec02bc89bf9e553127
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Start by copying oe-core recipes-bsp/u-boot/ into the Aspeed BSP. The
uboot recipes in oe-core master currently point to 2019.07 u-boot and
the Aspeed SDK branch being pointed to by this patch is based on uboot
upstream 2019.04. There weren't any changes in oe-core going from
2019.04 to 2019.07 so thats OK.
After copying the oe-core recipes, fix up SRC_URI, HOMEPAGE, and a
couple other variables to point at the Aspeed u-boot fork.
The current aspeed-master-v2019.04 tip and evb-ast2600_defconfig will produce
a uboot binary but make returns non-zero:
CFGCHK u-boot.cfg
Error: You must add new CONFIG options using Kconfig
The following new ad-hoc CONFIG options were detected:
CONFIG_RAM
Please add these via Kconfig instead. Find a suitable Kconfig
file and add a 'config' or 'menuconfig' option.
make: *** [Makefile:1010: all] Error 1
As such the utility of this recipe is limited until the above issue is
addressed.
The Aspeed SDK is intended to be the basis for Aspeed G6 bringup.
(From meta-aspeed rev: fe03326ee328718a79138062a0db374c0685a9c7)
Change-Id: I266dc10dd8549c024ec7012da5e576a2436d195b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
