Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-libhei / 9096b63c9accf1f29c2b3e08870c1792bfec3389
commit9096b63c9accf1f29c2b3e08870c1792bfec3389[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Tue Apr 11 13:46:05 2023 -0500
committerZane Shelley <zshelle@us.ibm.com>Tue Apr 11 13:46:05 2023 -0500
tree578ecfe919976c74939114ee5c03ad09280ee08e
parent94db72a9842935ce3de114f8c17df3ba986a6056 [diff]
Remove deprecated chip data XML

The chip data XML format has been replaced with the chip data JSON. The
XML is no longer needed and has been removed.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I050354aae96846b53f587dd94aba630c54a72e58
155 files changed
tree: 578ecfe919976c74939114ee5c03ad09280ee08e
  1. chip_data/
  2. src/
  3. subprojects/
  4. test/
  5. .clang-format
  6. .eslintignore
  7. .gitignore
  8. .prettierignore
  9. .prettierrc.yaml
  10. buildinfo.hpp.in
  11. LICENSE
  12. meson.build
  13. meson_options.txt
  14. OWNERS
  15. README.md
README.md

openpower-libhei: Hardware Error Isolation for POWER Systems

This library is a common, portable code base for isolating errors reported by hardware registers on POWER Systems chips.

The primary consumers (and requirements drivers) will be:

Core API

See the primary API definitions for details on how to use this library.

Integration

This library can be integrated into a user application's source (either imported, or as a git subtree/submodule) or built as static library.

User Application Requirements and APIs

  • The process to access hardware register data will vary per user application. Therefore, this library will declare the hardware access user APIs, but each user application must implement the APIs for their own environment.
  • This library will not contain data regarding hardware specific information. Instead, that information will be provided by the user application in the form of the Chip Data Files.
  • Tracing, or logging, methods will vary per user application. Therefore, this library will declare the tracing/logging user APIs, but each user application must implement the APIs for their own environment.

Environment configuration

  • __HEI_ENABLE_HW_WRITE: When defined, it will allow hardware write support. Note that the Chip Data Files will contain rules for clearing and masking register bits. Both of which will require modifying hardware registers, which is not allowed by user applications like OpenBMC or FSP firmware.

Development Notes

  • The Hostboot environment only supports up to C++14. Therefore, this library cannot use anything newer at this time.
  • Hostboot has a very limited environment. It does not include libc or libstdc++. However, Hostboot has implemented select functions from those libraries as needed. For details, you can reference src/include/ in the POWER Systems Hostboot firmware.

Building

For a standard OpenBMC release build, you want something like:

meson -Dtests=disabled <build_dir>
ninja -C <build_dir>
ninja -C <build_dir> install

For a test / debug build, a typical configuration is:

meson -Dtests=enabled <build_dir>
ninja -C <build_dir> test