Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 4d3f093a72e94689d60f0d198cb3c245afe80023
commit4d3f093a72e94689d60f0d198cb3c245afe80023[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Mon Apr 01 09:06:52 2024 -0500
committerZane Shelley <zshelle@us.ibm.com>Mon Apr 01 09:08:36 2024 -0500
tree180e8f814ba4f7ede6bc7a528f2c390a09fefc7a
parent169c4d7880884c9756b230a9e270bcfacffc121a [diff]
Revert "Add level 2 callout to TI logs"

This reverts commit 60cb2e4277759661f9054d263cc877dc7fa406ed.

Change-Id: I707dcb5502ac43c38ad80f13e60afb2d09cbf711
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
1 file changed
tree: 180e8f814ba4f7ede6bc7a528f2c390a09fefc7a
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .eslintignore
  8. .gitignore
  9. .prettierignore
  10. .prettierrc.yaml
  11. buildinfo.hpp.in
  12. cli.cpp
  13. cli.hpp
  14. config.h.in
  15. LICENSE
  16. listener.cpp
  17. listener.hpp
  18. main.cpp
  19. main_nl.cpp
  20. meson.build
  21. meson.options
  22. OWNERS
  23. 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