Welcome to the OpenBMC wiki!

Come join us!Jump in Discord and say hello! Tons of good info and links to mail/chat channels:https://github.com/openbmc/docs#openbmc-documentation

Also, feel free to use #openbmc-meeting for side discussions, but check that a working group in not already using it for a weekly meeting for a specific time.

HOWTO - OpenBMC Development Starter

Continuous-Integration

OpenBMC is based on theYocto project. The image recipe we use is calledobmc-phosphor-image, so building is done as usual in Yocto by runningbitbake obmc-phosphor-image.

There is a convenientsetup script that allows for easy environment configuration for any of the supported targets. You can sourcesetup without arguments to get the full list. There is one special target calledqemuarm that builds OpenBMC for QEMU. Other listed targets are for real hardware.

If you use multiple targets, you will need to clear the configuration directory each time you switch to another target before runningsetup:

rm -rf build/conf

You may skip this step if you've been always using just a single target or are building from scratch.

Examples follow:

The qemu target is ‘qemuarm’:

$ cd openbmc$ . setup qemuarm$ bitbake obmc-phosphor-image

The Palmetto target ispalmetto:

$ cd openbmc$ . setup palmetto$ bitbake obmc-phosphor-image

The Zaius target iszaius.

$ cd openbmc$ . setup zaius$ bitbake obmc-phosphor-image

Once you are done with the build process, images can be found in the following path:

/openbmc/build/tmp/deploy/images