OpenBMC

OpenBMC is an open software framework to build a complete Linux image for a Board Management Controller (BMC).

OpenBMC uses the Yocto Project as the underlying building and distro generation framework.

Board	Description
Wedge	A 40G OS-agnostic TOR switch
Yosemite	An open source modular chassis for high-powered microservers
Lightning	A flexible NVMe JBOF
Wedge100	A 32x100G TOR switch
Backpack LC/FC	Linecard and fabric card in a 128x100G modular open switch
Backpack CMM	Chassis management module in a 128x100G modular open switch
Tioga Pass	A dual-socket compute platform
YosemiteV2	A refresh of Yosemite
Bryce Canyon	Disk Storage platform
Grand Canyon	Disk Storage platform

Contents

This repository includes 3 set of layers:

• OpenBMC Common Layer - Common packages and recipes can be used in different types of BMC.
• BMC System-on-Chip (SoC) Layer - SoC specific drivers and tools. This layer includes the bootloader (u-boot) and the Linux kernel. Both the bootloader and Linux kernel shall include the hardware drivers specific for the SoC.
• Board Specific Layer - Board specific drivers, configurations, and tools. This layer defines how to configure the image. It also defines what packages to be installed for an OpenBMC image for this board. Any board specific initialization and tools are also included in this layer.

File structure

The Yocto naming pattern is used in this repository. A “meta-layer“ is used to name a layer or a category of layers. And recipe-abc is used to name a recipe. The project will exist as a meta layer itself! Within the Yocto Project’s distribution call this project meta-openbmc.

The recipes for OpenBMC common layer are found in common.

The BMC SoC layer and board specific layer are grouped together based on the vendor/manufacturer name. For example, all Facebook boards specific code should be in meta-facebook. Likewise, meta-aspeed includes source code for Aspeed SoCs.

How to build

Note: In the instruction set below, references to for some of the steps is an example only and need to be replaced with the respective platform when setting up for a different platform.

1. Set up the build environment based on the Yocto Project’s Quick Start Guide.

2. Clone the OpenBMC repository and other open source repositories:

   $ git clone -b helium https://github.com/facebook/openbmc.git
   $ cd openbmc
   $ ./sync_yocto.sh

3. Initialize a build directory for the platform to build. In the openbmc directory:

   $ source openbmc-init-build-env wedge

   Choose between wedge, wedge100, yosemite, or any of the other platforms listed in the meta-facebook directory. After this step, you will be dropped into a build directory, openbmc/build.

4. Start the build within the build directory: In general to build for the platform:

   $ bitbake <platform>-image

   The build process automatically fetches all necessary packages and builds the complete image. The final build results are in openbmc/build/tmp/deploy/images/<platform>. The root password will be 0penBmc, you may change this in the local configuration.

Build Artifacts

• u-boot.bin - This is the u-boot image for the board.
• uImage - This the Linux kernel for the board.
• -image-.cpio.lzma.u-boot - This is the rootfs for the board.
• flash- - This is the complete flash image including u-boot, kernel, and the rootfs.

Kernel & U-Boot Development

By default, OpenBMC build process fetches and build Linux kernel and U-boot directly from GitHub repository.

• To make local kernel changes and build with the modified kernel:

In the build directory, run

$ devtool modify linux-aspeed

or

$ devtool modify u-boot

This will create local Linux package under /workspace/sources/linux-aspeed for development

• To go back to default recipes, run

  $ devtool reset linux-aspeed

FAQ

1- BMC will take care of the controlling the system / fan based on the sensor/device status (I assume it may even shutdown in case of multiple failures or high temperature). How can we debug such issues? Is there any event/critical logs maintained in the the BMC? Can we have list of files which we can be looked into in case of such issues?

Answer: To debug those issues, you will have to refer to the logs. A: For Rest api related issues, please look at the rest logs under /tmp/ (example: /tmp/rest.log). B: For FSCD related issues, please look at the fscd logs for /var/log/ (example: /var/log/fscd.log). C: For mTerm log (data from the X86 CPU side), please look at /var/log/mTerm.log (it’s usually /var/log/mTerm_wedge.log on most platform). D: Some persistent log also go to /mnt/data/ partition. E: For everything else, look at /var/log/messages.

2. How do we configure the BMC sensor thresholds for fan / temp / others ? Do we have any command which can be used from the OpenBmc shell?

A- For fan RPM, you can run set_fan_speed.sh to change it (use get_fan_speed.sh to read the value back) from the OpenBMC shell. Some platforms, especially storage/compute ones, use fan-util. Those scripts are under /usr/local/bin on the BMC. Please keep in mind that fscd process will change the fan speed RPM based so your changed values won’t stay for long unless you turn off the watchdog and kill fscd. if you want to change the temperature threshold, you will have to modify the codes and build a new BMC image.

How can I contribute?

If you have an application that can be used by different BMCs, you can contribute your application to the OpenBMC common layer.

If you are a BMC SoC vendor, you can contribute your SoC specific drivers to the BMC SoC layer.

If you are a board vendor, you can contribute your board specific configurations and tools to the Board specific layer. If the board uses a new BMC SoC that is not part of the BMC SoC layer, the SoC specific driver contribution to the BMC SoC layer is also required.

License

OpenBMC is Apache licensed, as found in the LICENSE file.