Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / e0ba7fb831e558bdeae8e79e889e33a361eed538
commite0ba7fb831e558bdeae8e79e889e33a361eed538[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Wed Jul 06 14:51:03 2022 -0500
committerAndrew Geissler <andrew@geissonator.com>Thu Jul 14 18:40:33 2022 +0000
treec2beed8a7c22d587a1f9b74390b91cba2a48c748
parent4e8400d6d9de722679fa9f1f57024e40eb4444d0 [diff]
phosphor-state-manager: srcrev bump 1e91dc6357..b4cbfac10b

Corey-Hardesty (1):
      Host reboot configuration support

Corey-Hardesty (1):
      Define new 'obmc-chassis-blackout@.target'

"obmc-chassis-blackout@.target" was added to ensure the system can
recognize when it has entered a blackout state. This target is to be
called from chassis-state-manager when determining the initial state
of the chassis and finds that it experienced a power blackout.
Chassis-state-manager does this by checking the status of the pgood
pin along with the last known power state of the system to determine
if the target should be applied. If the last known power state was
"powered on" and the pgood pin is false, the chassis experienced a
blackout. To accommodate for any discrepencies across the systemd
services and targets may be added such as resetting host-state-sensors
or powering off leds to ensure the system stays in a predictable state.

Change-Id: I0832cd6300e9a1742c9ec2a9c5f68890b4e11918
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Corey Hardesty <corey.hardesty@icloud.com>
2 files changed
tree: c2beed8a7c22d587a1f9b74390b91cba2a48c748
  1. .github/
  2. meta-amd/
  3. meta-ampere/
  4. meta-aspeed/
  5. meta-asrock/
  6. meta-bytedance/
  7. meta-evb/
  8. meta-facebook/
  9. meta-fii/
  10. meta-google/
  11. meta-hpe/
  12. meta-ibm/
  13. meta-ingrasys/
  14. meta-inspur/
  15. meta-intel-openbmc/
  16. meta-inventec/
  17. meta-nuvoton/
  18. meta-openembedded/
  19. meta-openpower/
  20. meta-phosphor/
  21. meta-qualcomm/
  22. meta-quanta/
  23. meta-raspberrypi/
  24. meta-security/
  25. meta-supermicro/
  26. meta-tyan/
  27. meta-wistron/
  28. meta-yadro/
  29. poky/
  30. bitbake ⇨ poky/bitbake/
  31. LICENSE ⇨ poky/LICENSE
  32. meta ⇨ poky/meta
  33. meta-poky ⇨ poky/meta-poky/
  34. meta-skeleton ⇨ poky/meta-skeleton
  35. oe-init-build-env ⇨ poky/oe-init-build-env
  36. scripts ⇨ poky/scripts/
  37. .eslintrc.json
  38. .gitignore
  39. .gitreview
  40. .templateconf
  41. openbmc-env
  42. OWNERS
  43. README.md
  44. setup
README.md

OpenBMC

Build Status

OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.

Setting up your OpenBMC project

1) Prerequisite

See the Yocto documentation for the latest requirements

Ubuntu

$ sudo apt install git python3-distutils gcc g++ make file wget \
    gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2

Fedora

$ sudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio
hostname file diffutils diffstat lz4 wget zstd rpcgen patch

2) Download the source

git clone https://github.com/openbmc/openbmc
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:

bletchley               mihawk                  swift
dl360poc                mori                    tatlin-archive-x86
e3c246d4i               mtjade                  tiogapass
ethanolx                nicole                  transformers
evb-ast2500             olympus-nuvoton         vegman-n110
evb-ast2600             on5263m5                vegman-rx20
evb-npcm750             p10bmc                  vegman-sx20
f0b                     palmetto                witherspoon
fp5280g2                quanta-q71l             witherspoon-tacoma
g220a                   romulus                 x11spi
gbs                     s2600wf                 yosemitev2
gsj                     s6q                     zaius
kudo                    s7106
lannister               s8036

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

. setup romulus

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:

  • Roxanne Clarke, IBM
  • Nancy Yuen, Google
  • Sai Dasari, Facebook
  • Terry Duncan, Intel
  • Sagar Dharia, Microsoft
  • Samer El-Haj-Mahmoud, Arm

Contact