Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / d09aea5472ef7f91ba9cba16decd4c6674792534
commitd09aea5472ef7f91ba9cba16decd4c6674792534[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Tue May 25 10:01:55 2021 +0930
committerJoel Stanley <joel@jms.id.au>Tue May 25 13:50:10 2021 +0000
treee0cc71c27cc38acb0a5b0376adc28bb5f12d0ca0
parent60e37ef4f8fa0977267fc60e96328da730c9dce8 [diff]
u-boot-aspeed: Move to SDK v00.04.00

This rebases on the latest SDK release. Notably this release includes
support for the A3 and disables debug backdoors in line with the
defaults in the A3 silicon.

Changes kept downstream from ASPEED's SDK in the OpenBMC branch:

Eddie James (1):
      ARM: dts: Aspeed: Tacoma and Rainier: Add eMMC nodes and parameters

Joel Stanley (15):
      board: ast2600: Disable eSPI early init by default
      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
      ast2600: Modify SPL SRAM layout
      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: Add config for SPL MMC boot with FIT signature verification

Changes in the ASPEED SDK when moving from v00.03.03 include the branch
of fixes that were backported for FIT support, plus the following
changes from the ASPEED team:

Bing-Hua Wang (3):
      configs: evb-ast2500-spl_defconfig: Use platform.S DDR init
      ast2500: spl: Skip SPI timing calibration
      ast2500: Fix VRAM size detection

Chia-Wei Wang (2):
      ast2600: Disable backdoor to align A3 design
      ast2600: Enable UART Debug based on FWSPIMISO

Chia-Wei, Wang (4):
      board: ast2600: Add eSPI early init sequence
      board: ast2600-intel: Add Intel EGS CRB support
      aspeed: ast2600: Fix incorrect chip revision ID
      board: ast2600: Enable eSPI early init by default

Chin-Ting Kuo (4):
      sdhci: ast2600: HS200 support porting
      mmc: Enable SDMA feature when boot from eMMC
      uart: Fix UART1 route problem on A3
      spi-nor: Porting MT25Q02G flash part

Dylan Hung (18):
      cmd:aspeed: fix missing setting for the tx single packet
      cmd:aspeed: change broadcom id matching
      cmd:aspeed: add support of broadcom 54210/54213 test
      cmd:aspeed: refactor phy internal loopback
      cmd:aspeed: fix typo
      cmd:aspeed: remove redundant debug print
      cmd:aspeed: skip deselect package for I350 IOP issue
      cmd:aspeed: add NCSI_VERBOSE_TEST (default off)
      cmd:aspeed: add 100ms for phy ready
      cmd:aspeed: bug fixed of the length decoding of the dramtest
      arm:dts: revise ast2600 mac1/2 rgmii delay setting
      net:phy: add phy-mode support on broadcom 5461 series
      cmd:aspeed: add phy tx/rx delay control arguments
      cmd:aspeed: add bcm54615, rtl8211f and marvell88e15 delay setting
      cmd:aspeed: restore default page
      ram:aspeed: revise coding style
      ram:aspeed: refactor coding style
      arm:dts: revise rgmii tx/rx delay

Fugang Duan (1):
      net: phy: realtek: add rx delay support for RTL8211F

Jamin Lin (1):
      Add evb-ast2600-obmc-emmc-cot_defconfig config to support AST2600 emmc secure boot for OpenBMC

Johnny Huang (6):
      otp: fix a1 program issue
      otp: fix otp cmd stuck
      otp: update version number to 1.0.2
      otp: add AST2600A3
      secure boot: fix public key exponent
      otp: update print otp image

Ryan Chen (3):
      AST2600:platform.S for AST2600A3 fix for reset. it will apply for AST2600A1/A2/A3
      ast2600:ddr: fix memory bandwidth issue
      sdram : ast2600

Troy Lee (2):
      config: ast2600: support OpenBMC boot from eMMC image
      config: ast2600-evb for openbmc boot command update

chin-ting_kuo (1):
      Revert "mmc: Enable SDMA feature when boot from eMMC"

The previous version of v2019.04-aspeed-openbmc is kept in the branch
archive/v2019.04-aspeed-openbmc-3.

Change-Id: Ie492bdbfaec32c3e3e0caf8d4fa1806fcd1febec
Signed-off-by: Joel Stanley <joel@jms.id.au>
1 file changed
tree: e0cc71c27cc38acb0a5b0376adc28bb5f12d0ca0
  1. .github/
  2. meta-alibaba/
  3. meta-amd/
  4. meta-ampere/
  5. meta-arm/
  6. meta-aspeed/
  7. meta-asrock/
  8. meta-bytedance/
  9. meta-evb/
  10. meta-facebook/
  11. meta-fii/
  12. meta-google/
  13. meta-hpe/
  14. meta-hxt/
  15. meta-ibm/
  16. meta-ingrasys/
  17. meta-inspur/
  18. meta-intel-openbmc/
  19. meta-inventec/
  20. meta-lenovo/
  21. meta-microsoft/
  22. meta-nuvoton/
  23. meta-openembedded/
  24. meta-openpower/
  25. meta-phosphor/
  26. meta-portwell/
  27. meta-qualcomm/
  28. meta-quanta/
  29. meta-raspberrypi/
  30. meta-security/
  31. meta-supermicro/
  32. meta-wistron/
  33. meta-x86/
  34. meta-xilinx/
  35. meta-yadro/
  36. poky/
  37. bitbake ⇨ poky/bitbake/
  38. LICENSE ⇨ poky/LICENSE
  39. meta ⇨ poky/meta
  40. meta-poky ⇨ poky/meta-poky/
  41. meta-skeleton ⇨ poky/meta-skeleton
  42. oe-init-build-env ⇨ poky/oe-init-build-env
  43. scripts ⇨ poky/scripts/
  44. .gitignore
  45. .gitreview
  46. .templateconf
  47. MAINTAINERS
  48. openbmc-env
  49. OWNERS
  50. README.md
  51. setup
README.md

OpenBMC

Build Status

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