Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / b1106b5d0255114f63476825e3ee3864d3318fed
commitb1106b5d0255114f63476825e3ee3864d3318fed[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Fri Jan 29 13:44:42 2021 -0600
committerZane Shelley <zshelle@us.ibm.com>Tue Feb 02 16:06:55 2021 -0600
treea2ffa95416bd11752f3aa412265747e4086ff58a
parentd26298b1204afb31ffdb0386679b4eeb89b7b9d5 [diff]
refactor __captureSignatureList() with new BinFileWriter class

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I57635c26cc255da6f5213e66938770cb71490d2f
2 files changed
tree: a2ffa95416bd11752f3aa412265747e4086ff58a
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .gitignore
  8. cli.cpp
  9. cli.hpp
  10. LICENSE
  11. listener.cpp
  12. listener.hpp
  13. main.cpp
  14. main_nl.cpp
  15. MAINTAINERS
  16. meson.build
  17. meson_options.txt
  18. README.md
README.md

Hardware Diagnostics for POWER Systems

In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.

Aditional details TBD.

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