Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 5a58d7c16264a6b18d2844abe61dc3617a8ce590
commit5a58d7c16264a6b18d2844abe61dc3617a8ce590[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Mon May 19 09:59:05 2025 -0500
committerZane Shelley <zshelle@us.ibm.com>Mon May 19 10:00:51 2025 -0500
tree7845a48465990609f93dc2645963b7356b04820b
parent34b0ce19b894e4e1b56d33134898a5919d8e2e48 [diff]
RAS data: callout update for P10/P11 PB_STATION_FIRs

Bits 16:21 of PB_STATION_FIR_EN1, PB_STATION_FIR_EN4,
PB_STATION_FIR_ES1, and PB_STATION_FIR_ES4 were changed to callout the
chip instead of level 2 support.

Change-Id: I60fab2bf7ae017696ccc410d54e8aab45518e3d1
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
2 files changed
tree: 7845a48465990609f93dc2645963b7356b04820b
  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