commit | ff76b6b4ab9081d67d1e70d22e3ed5cb52aba758 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Nov 18 13:54:26 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Nov 18 20:40:17 2020 +0000 |
tree | 97f82de162c76c0eadcd7da1c8874d700eed6dba | |
parent | 584f179eaeb2ab3ad8fc9725666b4d1b33594473 [diff] |
pdbg util to get FSI target Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I9cd110fe43b1274c0e738c8b3e127c6c95760869
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.
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