Gitiles
Code Review Sign In
gerrit.openbmc.org / premsjha / op-build / 8da41019a8bf59179d4255c66a93c03259355dce
commit8da41019a8bf59179d4255c66a93c03259355dce[log] [tgz]
authorRoland Veloz <rveloz@us.ibm.com>Thu Feb 17 11:24:08 2022 -0600
committerRoland Veloz <rveloz@us.ibm.com>Fri Feb 18 09:33:24 2022 -0600
tree579514bf49b7f8ac8962ed5f3469d956fb807025
parent320fd34523d54ae364c3746e759f42ca8655eedd [diff]
Adding files hbicore.syms and hbotStringFile to the PNOR scratch dir

Adding files hbicore.syms and hbotStringFile to the PNOR scratch dir
so LID files can be created from these files. hbicore.syms will be LID
file 81e00686 and hbotStringFile file will be LID file 81e00685.

RTC: 295909
Signed-off-by: Roland Veloz <rveloz@us.ibm.com>
1 file changed
tree: 579514bf49b7f8ac8962ed5f3469d956fb807025
  1. ci/
  2. dl/
  3. doc/
  4. openpower/
  5. output/
  6. buildroot
  7. .gitignore
  8. .gitmodules
  9. .travis.yml
  10. CONTRIBUTING.md
  11. LICENSE
  12. NOTICE
  13. op-build
  14. op-build-env
  15. README.md
README.md

OpenPOWER Firmware Build Environment

The OpenPOWER firmware build process uses Buildroot to create a toolchain and build the various components of the PNOR firmware, including Hostboot, Skiboot, OCC, Petitboot etc.

Documentation

https://open-power.github.io/op-build/

See the doc/ directory for documentation source. Contributions are VERY welcome!

Development

Issues, Milestones, pull requests and code hosting is on GitHub: https://github.com/open-power/op-build

See CONTRIBUTING.md for howto contribute code.

Building an image

To build an image for a Blackbird system:

git clone --recursive git@github.com:open-power/op-build.git
cd op-build
./op-build p10ebmc_defconfig && ./op-build

There are also default configurations for other platforms in openpower/configs/. Current POWER9 platforms include Witherspoon, Boston (p9dsu), Romulus, and Zaius.

Buildroot/op-build supports both native and cross-compilation - it will automatically download and build an appropriate toolchain as part of the build process, so you don't need to worry about setting up a cross-compiler. Cross-compiling from a x86-64 host is officially supported.

The machine your building on will need Python 2.7, GCC 6.2 (or later), and a handful of other packages (see below).

Dependencies for 64-bit Ubuntu/Debian systems

  1. Install Ubuntu (>= 18.04) or Debian (>= 9) 64-bit.

  2. Enable Universe (Ubuntu only):

     sudo apt-get install software-properties-common
 sudo add-apt-repository universe

  3. Install the packages necessary for the build:

     sudo apt-get install cscope ctags libz-dev libexpat-dev \
   python language-pack-en texinfo gawk cpio xxd \
   build-essential g++ git bison flex unzip \
   libssl-dev libxml-simple-perl libxml-sax-perl libxml-parser-perl libxml2-dev libxml2-utils xsltproc \
   wget bc rsync

Dependencies for 64-bit Fedora systems

  1. Install Fedora (>= 25) 64-bit.

  2. Install the packages necessary for the build:

     sudo dnf install gcc-c++ flex bison git ctags cscope expat-devel patch \
   zlib-devel zlib-static texinfo "perl(bigint)" "perl(XML::Simple)" \
   "perl(YAML)" "perl(XML::SAX)" "perl(Fatal)" "perl(Thread::Queue)" \
   "perl(Env)" "perl(XML::LibXML)" "perl(Digest::SHA1)" "perl(ExtUtils::MakeMaker)" \
   "perl(FindBin)" "perl(English)" "perl(Time::localtime)" \
   libxml2-devel which wget unzip tar cpio python bzip2 bc findutils ncurses-devel \
   openssl-devel make libxslt vim-common lzo-devel python2 rsync hostname