commit	160599b3e5e9c4b2603fc27fe7b0b67ad97dda45	[log] [tgz]
author	Joel Stanley <joel@jms.id.au>	Wed Apr 21 16:20:10 2021 +0930
committer	Joel Stanley <joel@jms.id.au>	Thu Apr 29 00:41:53 2021 +0000
tree	4219e8391a85f718d48c2ca2219a2104dc7d9542
parent	593f2bd8afb67661ab1d399c7d7d3d436e8ebac4 [diff]

u-boot-aspeed: Update to SDK v00.03.03 and HACE support

This updates the OpenBMC u-boot tree to use ASPEED's latest SDK, and
adds support for FIT verification including use of the HACE to perform
SHA calculations on the ast2600.

The changes come in three categories; fixes backported and sent to
ASPEED for merging in a future SDK release, patches carried that are
specific to OpenBMC, and the new FIT and HACE support.

Note that this does not remove the legacy image support from the SPL, so
there is no dependency on the changes to load u-boot as a FIT.

Fixes backported from upstream and set to ASPEED:

Harald Seiler (1):
      common: hash: Remove a debug printf statement

Heinrich Schuchardt (2):
      fit: check return value of fit_image_get_data_size()
      image-fit: fit_check_format check for valid FDT

Jean-Jacques Hiblot (1):
      spl: fit: don't load the firmware twice

Joel Stanley (4):
      hw_sha: Fix coding style errors
      hash: Allow for SHA512 hardware implementations
      net/ncsi: Remove debugging
      fit: Use hash.c to call SHA code

Patrick Doyle (1):
      rsa: reject images with unknown padding

Reuben Dowle (1):
      Add support for SHA384 and SHA512

Simon Glass (3):
      image: Be a little more verbose when checking signatures
      image: Return an error message from fit_config_verify_sig()
      image: Check hash-nodes when checking configurations

Patches carried in the OpenBMC fork:

Eddie James (3):
      ARM: dts: Aspeed: Tacoma and Rainier: Add eMMC nodes and parameters
      arch: ARM: Aspeed: Add SPL eMMC partition boot support
      configs: Add AST2600 SPL eMMC configuration

Joel Stanley (11):
      dts: ast2600-evb: Enable FSI masters
      tools: Add script for generating recovery image
      configs: Add OpenBMC spl defconfig for AST2600 boards
      clk: ast2600: Add divisor settings for 100MHz PLL
      ram: ast2600: Enable device tree based DDR config
      ast2600: tacoma: Run DDR at 1333
      ast2600: Allow selection of SPL boot devices
      config: ast2600: Reduce SPL image size
      ast2600: Modify SPL SRAM layout
      config: ast2600: Enable FIT signature verification
      clk: aspeed: Add HACE yclk to ast2600

Features added for FIT verification and HACE support:

Joel Stanley (10):
      configs/ast2600: Make early malloc pool larger
      crypto: Add driver for Aspeed HACE
      ast2600: Enable HACE probing in SPL
      ast2600: Add HACE to device tree
      ast2600: spl: Add ASPEED_LOADERS option
      ast2600: spl: Support common boot loader features
      config: ast2600: Configure common MMC SPL loader
      configs: ast2600: Enable FIT SHA512 support
      ast2600: Configure u-boot load size
      configs: ast2600: Use non-a1 config for openbmc spl emmc

Change-Id: I4e5a1adb6e2bf17823b042c31b151bfdad9d3175
Signed-off-by: Joel Stanley <joel@jms.id.au>

meta-aspeed/recipes-bsp/u-boot/u-boot-common-aspeed-sdk_2019.04.inc[diff]

1 file changed

tree: 4219e8391a85f718d48c2ca2219a2104dc7d9542

README.md

OpenBMC

The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your server platform.

Setting up your OpenBMC project

1) Prerequisite

Ubuntu 14.04

sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat

Fedora 28

sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake \
    rpcgen perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum
sudo dnf groupinstall "C Development Tools and Libraries"

2) Download the source

git clone git@github.com:openbmc/openbmc.git
cd openbmc

3) Target your hardware

Any build requires an environment set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called setup and takes the name of your hardware target as an argument.

The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:

$ . setup <machine> [build_dir]
Target machine must be specified. Use one of:

centriq2400-rep         f0b                     fp5280g2
gsj                     hr630                   hr855xg2
lanyang                 mihawk                  msn
neptune                 nicole                  olympus
olympus-nuvoton         on5263m5                p10bmc
palmetto                qemuarm                 quanta-q71l
romulus                 s2600wf                 stardragon4800-rep2
swift                   tiogapass               vesnin
witherspoon             witherspoon-tacoma      yosemitev2
zaius

Once you know the target (e.g. romulus), source the setup script as follows:

. setup romulus build

For evb-ast2500, please use the below command to specify the machine config, because the machine in meta-aspeed layer is in a BSP layer and does not build the openbmc image.

TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env

4) Build

bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

OpenBMC Development

The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here

Build Validation and Testing

Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.

Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.

Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.

Submitting Patches

Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.

Bug Reporting

Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.

Questions

First, please do a search on the internet. There's a good chance your question has already been asked.

For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.

For technical discussions, please see contact info below for Discord and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or Discord.

Features of OpenBMC

Feature List

Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
Full IPMI 2.0 Compliance with DCMI
Code Update Support for multiple BMC/BIOS images
Web-based user interface
REST interfaces
D-Bus based interfaces
SSH based SOL
Remote KVM
Hardware Simulation
Automated Testing
User management
Virtual media

Features In Progress

OpenCompute Redfish Compliance
Verified Boot

Features Requested but need help

OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Technical Steering Committee

The Technical Steering Committee (TSC) guides the project. Members are:

Brad Bishop (chair), IBM
Nancy Yuen, Google
Sai Dasari, Facebook
James Mihm, Intel
Sagar Dharia, Microsoft
Supreeth Venkatesh, Arm

Contact

Mail: openbmc@lists.ozlabs.org https://lists.ozlabs.org/listinfo/openbmc
Discord: https://discord.gg/69Km47zH98