Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 169c4d7880884c9756b230a9e270bcfacffc121a
commit169c4d7880884c9756b230a9e270bcfacffc121a[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Mon Apr 01 09:06:49 2024 -0500
committerZane Shelley <zshelle@us.ibm.com>Mon Apr 01 09:08:31 2024 -0500
tree05eedac734daa36cb4104a3e0e4497c4328b4ee1
parent216ff9f1e5b1563c571aa41ff7412420d00a0c01 [diff]
Revert "Fix TI level 2 callout to use FFDCFormat::JSON instead of Custom"

This reverts commit 216ff9f1e5b1563c571aa41ff7412420d00a0c01.

Change-Id: Ied752866f76a83b8da4d7577d363175a6f06c475
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
1 file changed
tree: 05eedac734daa36cb4104a3e0e4497c4328b4ee1
  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