mpreboot: collect bmc dump

When a mpreboot is started, it indicates the host firmware has
encountered a critical failure. At times, the BMC firmware could be
involved in this error. Collect a BMC dump in parallel with the mpreboot
so that the BMC team will also have some debug data in these scenarios.

This is a "best attempt" type situation so do not let the failure of
generating a BMC dump, impact the overall mpreboot flow.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ie628953ce002b6afdc43fb7012de780c2f208826
1 file changed
tree: cfef694f7ee72dafa90a1f16c1fcb1715e877c24
  1. extensions/
  2. procedures/
  3. service_files/
  4. test/
  5. .clang-format
  6. .gitignore
  7. .shellcheck
  8. cfam_access.cpp
  9. cfam_access.hpp
  10. ext_interface.cpp
  11. ext_interface.hpp
  12. filedescriptor.cpp
  13. filedescriptor.hpp
  14. LICENSE
  15. MAINTAINERS
  16. meson.build
  17. meson_options.txt
  18. nmi_interface.cpp
  19. nmi_interface.hpp
  20. nmi_main.cpp
  21. OWNERS
  22. p10_cfam.hpp
  23. p9_cfam.hpp
  24. proc_control.cpp
  25. README.md
  26. registration.hpp
  27. targeting.cpp
  28. targeting.hpp
  29. temporary_file.cpp
  30. temporary_file.hpp
  31. util.cpp
  32. util.hpp
README.md

Contains procedures that interact with the OpenPower nest chipset.

To Build

To build this package, do the following steps:

    1. meson builddir
    2. ninja -C builddir

To build with phal feature:
    1. meson builddir -Dphal=enabled -Dopenfsi=enabled
    2. ninja -C builddir

To clean the repository run `ninja -C builddir/ clean`.