openpower-pnor-code-mgmt: srcrev bump 0d2f932124..e499446423

Lei YU (25):
      Add repo specific items in .gitignore
      Refactor: Split item_updater to common and ubi
      Refactor: Move watch to ubi
      Refactor: Move determinId to ubi
      Refactor: Remove unused isLowestPriority()
      Refactor: Split Activation into common and ubi
      Refactor: Move serialize to ubi
      Refactor: Make createActivation() common
      Static layout: Generate tar.gz for static layout pnor
      Static layout: Add dummy item_updater
      Static layout: Read PNOR VERSION using pflash
      Static layout: Add dummy activation_static
      Static layout: Implement PNOR code update
      Static layout: Implement gard reset
      Static layout: Implement factory reset
      Static layout: Use pflash to get partitions to clear
      Static layout: Do not update PNOR when host is on
      Static layout: Do not crash on empty PNOR
      test: Fix parallel build error on tests
      test: Add sources of static PNOR
      test: Add test for GetVersions()
      test: Add test for getPartsToClear
      Refactor: Fix issues found by cppcheck
      Install services to systemd unit dir
      Refactor: Use hiomapd instead of mboxd

(From meta-openpower rev: 847e65d7734035384e227003a685a32242f6e233)

Change-Id: If8ef37077f6f8b40962ef3f09dff3778303cdf2f
Signed-off-by: Andrew Geissler <>
Signed-off-by: Andrew Geissler <>
1 file changed
tree: c9a426a58205a0c9836a40b354f0a1c89a6c3385
  1. .github/
  2. meta-arm/
  3. meta-aspeed/
  4. meta-evb/
  5. meta-facebook/
  6. meta-google/
  7. meta-hxt/
  8. meta-ibm/
  9. meta-ingrasys/
  10. meta-inspur/
  11. meta-intel/
  12. meta-inventec/
  13. meta-mellanox/
  14. meta-nuvoton/
  15. meta-openembedded/
  16. meta-openpower/
  17. meta-phosphor/
  18. meta-portwell/
  19. meta-qualcomm/
  20. meta-quanta/
  21. meta-raspberrypi/
  22. meta-security/
  23. meta-x86/
  24. meta-xilinx/
  25. poky/
  26. .gitignore
  27. .gitreview
  28. .templateconf
  30. openbmc-env
  32. setup


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
sudo dnf groupinstall "C Development Tools and Libraries"

2) Download the source

git clone
cd openbmc

3) Target your hardware

Any build requires an environment variable known as TEMPLATECONF to be set to a hardware target. You can see all of the known targets with find meta-* -name local.conf.sample. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet


As an example target Palmetto

export TEMPLATECONF=meta-ibm/meta-palmetto/conf

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

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.

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

Features In Progress

  • OpenCompute Redfish Compliance
  • User management
  • Virtual media
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.