| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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
|
|
Include the socsec-sign class after the conditional assignments to
ensure the values we might assign are considered by the functions of
socsec-sign.
Without this, u-boot-aspeed-sdk do_deploy logs show:
```
DEBUG: Executing python function sstate_task_prefunc
DEBUG: Python function sstate_task_prefunc finished
DEBUG: Executing shell function do_deploy
Copying u-boot-nodtb binary...
Warning: Invalid socsec signing key - SPL verified boot won't be available
```
Adjusting the location of the include gives:
```
DEBUG: Executing python function sstate_task_prefunc
DEBUG: Python function sstate_task_prefunc finished
DEBUG: Executing shell function do_deploy
Copying u-boot-nodtb binary...
check header PASS
Found PEM header at position 381
check integrity PASS
```
Change-Id: I15cac4c315a6ceaeb69b0c02ba0b7d05e54f6e15
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
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
|
|
Allow configurations to override the SPL signing key if necessary, but
provide a default in case they don't. The provided key is intended a
low-security key.
Change-Id: I756271970b0a55409e40dbd06f1245ada6a3cb73
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8135871ae0e3b360aff7d878f7cf04a2504f2dd0
|
|
Add a development (insecure, also known as 'imprint') key to
u-boot-aspeed-sdk that can be used through socsec for signing the SPL on
ASPEED AST2600 devices.
The keypair was generated according to socsec's documentation, using:
$ openssl genrsa -out rsa_oem_dss_key.pem 4096
$ openssl rsa -in rsa_oem_dss_key.pem -pubout \
-out rsa_pub_oem_dss_key.pem
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: I9c03ed9603d7362e033862dd1e5138ba7164f13d
|
|
Add the necessary build infrastructure to allow ASPEED AST2600 devices
to use socsec to sign the U-boot SPL, allowing Aspeed's Verified Boot to
validate it.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: I7b38a59596819982f0a222812fcc64dfb91e104f
|
|
Generate a default environment to boot an eMMC based on a txt
file. Populate the generated environment image into the eMMC.
(From meta-aspeed rev: fdc603c73b2dc8851ce2d1684e9c71a5ce51a5b8)
Change-Id: I93944b183b7907202b02854e931593d62603ae77
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The u-boot.inc from upstream has been moved into this repository as
its upstream version is no longer compatible with openbmc/u-boot.
See commit 9052e5b for more details.
Some notes on attempting to get upstream to work. Got to issue 3 and
decided that instead of trying to cherry-pick in specific fixes from
upstream, we're going to need a full rebase. Until this is possible, I
think our best option is to just use the .inc from the working version
of poky which is what u-boot-aspeed.inc is.
1) Build directory (B) def moved to common .inc
Define BUILD directory in u-boot-common-aspeed-sdk_2019.04.inc
recipes-bsp/u-boot/u-boot-common-aspeed-sdk_2019.04.inc
+B = "${WORKDIR}/build"
2) Support in Makefile for new u-boot-initial-env file
Pull in the following commit:
https://github.com/u-boot/u-boot/commit/bdaa73a5b3923257add182b4ab8058dbfa33421b
Available in my fork:
https://github.com/geissonator/u-boot/tree/v2019.04-aspeed-openbmc-u-boot-initial-env-fix
3) CONFIG_DEFAULT_DEVICE_TREE needed
| arm-openbmc-linux-gnueabi-objcopy --gap-fill=0xff -j .text -j .secure_text -j .secure_data -j .rodata -j .hash -j .data -j .got -j .got.plt -j .u_boot_list -j .rel.dyn -j .binman_sym_table -j .text_rest -j .dtb.init.rodata -j .efi_runtime -j .efi_runtime_rel -O binary u-boot u-boot-nodtb.bin
| make -f /home/andrewg/Code/openbmc/build/tmp/work/witherspoon_tacoma-openbmc-linux-gnueabi/u-boot-aspeed-sdk/1_v2019.04+gitAUTOINC+58583dd97d-r0/git/scripts/Makefile.build obj=arch/arm/dts dtbs
| test -e arch/arm/dts/unset.dtb || ( \
| echo >&2; \
| echo >&2 "Device Tree Source is not correctly specified."; \
| echo >&2 "Please define 'CONFIG_DEFAULT_DEVICE_TREE'"; \
| echo >&2 "or build with 'DEVICE_TREE=<device_tree>' argument"; \
| echo >&2; \
(From meta-aspeed rev: cd159fccefe991336e798da35ed5a2b0abf27e62)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I1d28bd1125fe5acb1e644a751e44c65772892d0c
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The recipe was first created with the make target set to
u-boot.bin because there were some compilation errors.
These errors are not seeing anymore. By removing the u-boot.bin
target and allowing it to be the default (all), other targets
like u-boot-spl.bin can be automatically built based on the
defconfig.
(From meta-aspeed rev: 08e8e7430606d712d8ab3630cbdc650f71caf280)
Change-Id: If643afcfe6a9cdea63dd0d8011f6f2af8e287079
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This is a fork that is based on ASPEED's 2019.04 SDK fork. The goal is
to move to a mainline based tree, but while that work is underway, this
allows ast2600 support to move forward.
This gains support for NC-SI, and uses kconfig for the default
boot command allowing us to drop the patch to aspeed-common.h.
Machines will need to indicate which device tree to use. If possible we
should look to having a few common device trees, but for now they are
machine specific. The AST2600 is configured to use the ast2600a1-evb
device tree, which will also work on the a0 variant.
(From meta-aspeed rev: 22ccf4648a776c458300c97a6d001a843b2b5c9b)
Change-Id: Ib21dc9962761aac3f3148fe4908439b975545e1e
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>
|
