{"id":18694265,"url":"https://github.com/9elements/openbmc","last_synced_at":"2025-11-08T11:30:44.954Z","repository":{"id":41176059,"uuid":"388874893","full_name":"9elements/openbmc","owner":"9elements","description":null,"archived":false,"fork":false,"pushed_at":"2024-05-08T08:40:25.000Z","size":118942,"stargazers_count":0,"open_issues_count":6,"forks_count":0,"subscribers_count":9,"default_branch":"rebased_sbp1","last_synced_at":"2025-02-16T19:09:48.459Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/9elements.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2021-07-23T17:18:37.000Z","updated_at":"2022-01-13T21:10:02.000Z","dependencies_parsed_at":"2023-09-22T23:44:17.143Z","dependency_job_id":"24830c15-bcbc-4d75-80ef-35ae2827404b","html_url":"https://github.com/9elements/openbmc","commit_stats":null,"previous_names":[],"tags_count":188,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/9elements%2Fopenbmc","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/9elements%2Fopenbmc/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/9elements%2Fopenbmc/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/9elements%2Fopenbmc/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/9elements","download_url":"https://codeload.github.com/9elements/openbmc/tar.gz/refs/heads/rebased_sbp1","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":239552379,"owners_count":19657901,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-07T11:09:11.040Z","updated_at":"2025-11-08T11:30:44.893Z","avatar_url":"https://github.com/9elements.png","language":"Python","readme":"# OpenBMC\n\n[![Build Status](https://jenkins.openbmc.org/buildStatus/icon?job=latest-master)](https://jenkins.openbmc.org/job/latest-master/)\n\nOpenBMC is a Linux distribution for management controllers used in devices such\nas servers, top of rack switches or RAID appliances. It uses\n[Yocto](https://www.yoctoproject.org/),\n[OpenEmbedded](https://www.openembedded.org/wiki/Main_Page),\n[systemd](https://www.freedesktop.org/wiki/Software/systemd/), and\n[D-Bus](https://www.freedesktop.org/wiki/Software/dbus/) to allow easy\ncustomization for your platform.\n\n## Setting up your OpenBMC project\n\n### 1) Prerequisite\n\nSee the\n[Yocto documentation](https://docs.yoctoproject.org/ref-manual/system-requirements.html#required-packages-for-the-build-host)\nfor the latest requirements\n\n#### Ubuntu\n\n```sh\nsudo apt install git python3-distutils gcc g++ make file wget \\\n    gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2\n```\n\n#### Fedora\n\n```sh\nsudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio \\\n    hostname file diffutils diffstat lz4 wget zstd rpcgen patch\n```\n\n### 2) Download the source\n\n```sh\ngit clone https://github.com/openbmc/openbmc\ncd openbmc\n```\n\n### 3) Target your hardware\n\nAny build requires an environment set up according to your hardware target.\nThere is a special script in the root of this repository that can be used to\nconfigure the environment as needed. The script is called `setup` and takes the\nname of your hardware target as an argument.\n\nThe script needs to be sourced while in the top directory of the OpenBMC\nrepository clone, and, if run without arguments, will display the list of\nsupported hardware targets, see the following example:\n\n```text\n$ . setup \u003cmachine\u003e [build_dir]\nTarget machine must be specified. Use one of:\n\nbletchley               mori                    s8036\ndl360poc                mtjade                  swift\ne3c246d4i               mtmitchell              tatlin-archive-x86\nethanolx                nicole                  tiogapass\nevb-ast2500             olympus-nuvoton         transformers\nevb-ast2600             on5263m5                vegman-n110\nevb-npcm750             p10bmc                  vegman-rx20\nf0b                     palmetto                vegman-sx20\nfp5280g2                qcom-dc-scm-v1          witherspoon\ng220a                   quanta-q71l             witherspoon-tacoma\ngbs                     romed8hm3               x11spi\ngreatlakes              romulus                 yosemitev2\ngsj                     s2600wf                 zaius\nkudo                    s6q\nlannister               s7106\n```\n\nOnce you know the target (e.g. romulus), source the `setup` script as follows:\n\n```sh\n. setup romulus\n```\n\n### 4) Build\n\n```sh\nbitbake obmc-phosphor-image\n```\n\nAdditional details can be found in the [docs](https://github.com/openbmc/docs)\nrepository.\n\n## OpenBMC Development\n\nThe OpenBMC community maintains a set of tutorials new users can go through to\nget up to speed on OpenBMC development out\n[here](https://github.com/openbmc/docs/blob/master/development/README.md)\n\n## Build Validation and Testing\n\nCommits submitted by members of the OpenBMC GitHub community are compiled and\ntested via our [Jenkins](https://jenkins.openbmc.org/) server. Commits are run\nthrough two levels of testing. At the repository level the makefile `make check`\ndirective is run. At the system level, the commit is built into a firmware image\nand run with an arm-softmmu QEMU model against a barrage of\n[CI tests](https://jenkins.openbmc.org/job/CI-MISC/job/run-ci-in-qemu/).\n\nCommits submitted by non-members do not automatically proceed through CI\ntesting. After visual inspection of the commit, a CI run can be manually\nperformed by the reviewer.\n\nAutomated testing against the QEMU model along with supported systems are\nperformed. The OpenBMC project uses the\n[Robot Framework](http://robotframework.org/) for all automation. Our complete\ntest repository can be found\n[here](https://github.com/openbmc/openbmc-test-automation).\n\n## Submitting Patches\n\nSupport of additional hardware and software packages is always welcome. Please\nfollow the\n[contributing guidelines](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md)\nwhen making a submission. It is expected that contributions contain test cases.\n\n## Bug Reporting\n\n[Issues](https://github.com/openbmc/openbmc/issues) are managed on GitHub. It is\nrecommended you search through the issues before opening a new one.\n\n## Questions\n\nFirst, please do a search on the internet. There's a good chance your question\nhas already been asked.\n\nFor general questions, please use the openbmc tag on\n[Stack Overflow](https://stackoverflow.com/questions/tagged/openbmc). Please\nreview the\n[discussion](https://meta.stackexchange.com/questions/272956/a-new-code-license-the-mit-this-time-with-attribution-required?cb=1)\non Stack Overflow licensing before posting any code.\n\nFor technical discussions, please see [contact info](#contact) below for Discord\nand mailing list information. Please don't file an issue to ask a question.\nYou'll get faster results by using the mailing list or Discord.\n\n### Will OpenBMC run on my Acme Server Corp. XYZ5000 motherboard?\n\nThis is a common question, particularly regarding boards from popular COTS\n(commercial off-the-shelf) vendors such as Supermicro and ASRock.  You can see\nthe list of supported boards by running `. setup` (with no further arguments) in\nthe root of the OpenBMC source tree.  Most of the platforms supported by OpenBMC\nare specialized servers operated by companies running large datacenters, but\nsome more generic COTS servers are supported to varying degrees.\n\nIf your motherboard is not listed in the output of `. setup` it is not currently\nsupported.  Porting OpenBMC to a new platform is a non-trivial undertaking,\nideally done with the assistance of schematics and other documentation from the\nmanufacturer (it is not completely infeasible to take on a porting effort\nwithout documentation via reverse engineering, but it is considerably more\ndifficult, and probably involves a greater risk of hardware damage).\n\n**However**, even if your motherboard is among those listed in the output of\n`. setup`, there are two significant caveats to bear in mind.  First, not all\nports are equally mature -- some platforms are better supported than others, and\nfunctionality on some \"supported\" boards may be fairly limited.  Second, support\nfor a motherboard is not the same as support for a complete system -- in\nparticular, fan control is critically dependent on not just the motherboard but\nalso the fans connected to it and the chassis that the board and fans are housed\nin, both of which can vary dramatically between systems using the same board\nmodel.  So while you may be able to compile and install an OpenBMC build on your\nsystem and get some basic functionality, rough edges (such as your cooling fans\nrunning continuously at full throttle) are likely.\n\n## Features of OpenBMC\n\n### Feature List\n\n- Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog\n- Full IPMI 2.0 Compliance with DCMI\n- Code Update Support for multiple BMC/BIOS images\n- Web-based user interface\n- REST interfaces\n- D-Bus based interfaces\n- SSH based SOL\n- Remote KVM\n- Hardware Simulation\n- Automated Testing\n- User management\n- Virtual media\n\n### Features In Progress\n\n- OpenCompute Redfish Compliance\n- Verified Boot\n\n### Features Requested but need help\n\n- OpenBMC performance monitoring\n\n## Finding out more\n\nDive deeper into OpenBMC by opening the [docs](https://github.com/openbmc/docs)\nrepository.\n\n## Technical Steering Committee\n\nThe Technical Steering Committee (TSC) guides the project. Members are:\n\n- Roxanne Clarke, IBM\n- Nancy Yuen, Google\n- Patrick Williams, Meta\n- Terry Duncan, Intel\n- Sagar Dharia, Microsoft\n- Samer El-Haj-Mahmoud, Arm\n\n## Contact\n\n- Mail: openbmc@lists.ozlabs.org\n  [https://lists.ozlabs.org/listinfo/openbmc](https://lists.ozlabs.org/listinfo/openbmc)\n- Discord: [https://discord.gg/69Km47zH98](https://discord.gg/69Km47zH98)\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2F9elements%2Fopenbmc","html_url":"https://awesome.ecosyste.ms/projects/github.com%2F9elements%2Fopenbmc","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2F9elements%2Fopenbmc/lists"}