Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / dcd861cd47dea2e0ccd7f010568f0a23b3f705ec
commitdcd861cd47dea2e0ccd7f010568f0a23b3f705ec[log] [tgz]
authorBrad Bishop <bradleyb@fuzziesquirrel.com>Tue Sep 24 21:16:09 2019 -0400
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Thu Sep 26 21:13:15 2019 -0400
tree203218ff9ecd5b8945532640b94a1653ee7072c8
parent0ccee0236941550f7555cfc0bb86630dd36365cb [diff]
phosphor: image_types_phosphor: flash overrides

Add an override based on FLASH_SIZE, for use with the hardcoded offsets
that exist when building raw flash images.

This lets us have different flash layouts for different size flash
modules that can be shared between machines.

The existing 32MiB layouts are unchanged:
  partition: size: offset

  u-boot: 384 KiB (0 KiB)
  u-boot-env: 128 KiB (384 KiB)
  kernel/FIT: 4352 KiB (512 KiB)
  rootfs: 23808 KiB (4864 KiB)
  rwfs: 4MiB (28672 KiB)

The new layout is as follows:
  partition: size: offset

  u-boot: 896 KiB (0 KiB)
  u-boot-env: 128 KiB (896 KiB)
  kernel/FIT: 9 MiB (1 MiB)
  rootfs: 86 MiB (10 MiB)
  rwfs: 32MiB (96 MiB)

(From meta-phosphor rev: 9e84ca2ad4aa7f864bb53faa6f21ae580d64d07d)

Change-Id: I4edf302d4e738b31906cd03459ad6f2f44c3c749
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2 files changed
tree: 203218ff9ecd5b8945532640b94a1653ee7072c8
  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-lenovo/
  14. meta-mellanox/
  15. meta-microsoft/
  16. meta-nuvoton/
  17. meta-openembedded/
  18. meta-openpower/
  19. meta-phosphor/
  20. meta-portwell/
  21. meta-qualcomm/
  22. meta-quanta/
  23. meta-raspberrypi/
  24. meta-security/
  25. meta-x86/
  26. meta-xilinx/
  27. meta-yadro/
  28. poky/
  29. bitbake ⇨ poky/bitbake/
  30. LICENSE ⇨ poky/LICENSE
  31. meta ⇨ poky/meta
  32. meta-poky ⇨ poky/meta-poky/
  33. meta-skeleton ⇨ poky/meta-skeleton
  34. oe-init-build-env ⇨ poky/oe-init-build-env
  35. scripts ⇨ poky/scripts/
  36. .gitignore
  37. .gitreview
  38. .templateconf
  39. MAINTAINERS
  40. openbmc-env
  41. README.md
  42. 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 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

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-ibm/meta-witherspoon/conf
Romulusmeta-ibm/meta-romulus/conf

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.

Contact