OpenBMC major repository have been updated to Kernel 5.15.xx .
ASpeed SDK have updated to SDK v8.1 , and also updated Kernel to 5.15.xx
Romulus 2600 try to sync romulus project and aspeed sdk in the same page
Romulus2600 have updated related recipe update! can fork it and try it !
the status of build image test is like the following table
op515 + op_uboot ==> qemu test OK
ast515 + op_uboot ==> qemu test OK
ast515 + ast_uboot ==> qemu fail(uboot fail)
if have interest to cowork about training courses and bmc porting projects , can mail codingcoffee.01@gmail.com
The roadmap of romulus2600 is developing , if have any suggestion , please also mail to codingcoffee.01@gmail.com or leave it as issues ! Tks a lot!
This is fork from OpenBMC , Major target is for OpenBMC Training Courses !
We set Romulus AST2600 (Romulus porting to AST2600) is major projects !
Also use OpenBMC Raspberry Pi as 2 nd project !
have interest on Training courses , please visit
https://www.steamcourses.org/blog/239611/openbmc_series_courses1
https://www.steamcourses.org/blog/239612/openbmc_series_courses2
https://www.steamcourses.org/blog/239613/openbmc_series_courses1-1
or mail to sales@astar-tek.com
want to build romulus2600
Please type :
. setup romulus2600 build
Romulus2600 reference binary release:
https://gitlab.com/CodingCoffee-01/openbmc_research_release.git
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.
- 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"
git clone git@github.com:openbmc/openbmc.git
cd openbmc
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:
centriq2400-rep f0b fp5280g2
gsj hr630 hr855xg2
lanyang mihawk msn
neptune nicole olympus
olympus-nuvoton on5263m5 p10bmc
palmetto qemuarm quanta-q71l
romulus s2600wf stardragon4800-rep2
swift tiogapass vesnin
witherspoon witherspoon-tacoma yosemitev2
zaius
Once you know the target (e.g. romulus), source the setup script as follows:
. setup romulus
For evb-ast2500, please use the below command to specify the machine config,
because the machine in meta-aspeed layer is in a BSP layer and does not
build the openbmc image.
TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env
bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
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.
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.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
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.
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
Dive deeper into OpenBMC by opening the docs repository.
The Technical Steering Committee (TSC) guides the project. Members are:
- Brad Bishop (chair), IBM
- Nancy Yuen, Google
- Sai Dasari, Facebook
- James Mihm, Intel
- Sagar Dharia, Microsoft
- Supreeth Venkatesh, Arm