Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-bmc-code-mgmt / 70d72f8dc99a93cd574bc51dd012a5070e8e685a
commit70d72f8dc99a93cd574bc51dd012a5070e8e685a[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Wed Mar 23 13:15:05 2022 -0500
committerAdriana Kobylak <anoo@linux.ibm.com>Mon Apr 11 20:59:38 2022 +0000
tree1bcfb5b5b5a60f6853c8300f9db569095ce666b0
parent047f60e01adec4f7c0819a321ccde97e3ecb25b4 [diff]
side-switch: introduce new bmc update feature

This is the first commit in a series which will introduce a feature
within phosphor-bmc-code-mgmt that users can optionally install on their
systems to cause a side-switch boot.

A side-switch boot is a boot of a system in which the BMC detects that
the user has requested the alternate image on the flash chip be booted
from. The detection is done by looking at the available images, their
priorities, and the running image. If a higher priority image is
available on the non-running side, then it should be switched to. This
feature utilizes the one-time auto-power-on service to cause an
automatic boot of the system after the bmc side switch occurs.

At a high level, a service will be put into the obmc-host-start@.target
which runs before any other services in that target. It will launch the
executable being created in this series of commits. That application
will determine if a side switch is needed, and if so it will:
- Initiate and wait for a chassis power off of the system
- Set the one-time auto-power-on policy to AlwaysOn
- Issue a reboot to the BMC

But why did the user not just reboot the BMC themselves when they
installed the new image? There are use cases (at least on IBM systems)
where the user of the system wants to switch to the alternate image in
flash, but they want to defer that until someone reboots the BMC
manually OR the next time the user starts a boot of the system.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I58a914ec2c3f3cf15ac41a02725e9a800dffcf30
5 files changed
tree: 1bcfb5b5b5a60f6853c8300f9db569095ce666b0
  1. mmc/
  2. side-switch/
  3. static/
  4. subprojects/
  5. test/
  6. ubi/
  7. usb/
  8. xyz/
  9. .clang-format
  10. .gitignore
  11. .shellcheck
  12. activation.cpp
  13. activation.hpp
  14. detect-slot-aspeed
  15. download_manager.cpp
  16. download_manager.hpp
  17. download_manager_main.cpp
  18. elog-errors.hpp
  19. flash.hpp
  20. force-reboot.service.in
  21. gen-bios-tar
  22. image_manager.cpp
  23. image_manager.hpp
  24. image_manager_main.cpp
  25. image_verify.cpp
  26. image_verify.hpp
  27. images.cpp
  28. images.hpp
  29. item_updater.cpp
  30. item_updater.hpp
  31. item_updater_helper.hpp
  32. item_updater_main.cpp
  33. LICENSE
  34. MAINTAINERS
  35. meson.build
  36. meson_options.txt
  37. msl_verify.cpp
  38. msl_verify.hpp
  39. obmc-flash-bmc
  40. obmc-flash-bmc-setenv@.service.in
  41. obmc-flash-host-bios@.service.in
  42. openssl_alloc.cpp
  43. openssl_alloc.hpp
  44. OWNERS
  45. README.md
  46. reboot-guard-disable.service.in
  47. reboot-guard-enable.service.in
  48. reset-cs0-aspeed
  49. serialize.cpp
  50. serialize.hpp
  51. software.conf
  52. sync-once.sh
  53. sync_manager.cpp
  54. sync_manager.hpp
  55. sync_manager_main.cpp
  56. sync_watch.cpp
  57. sync_watch.hpp
  58. synclist
  59. usr-local.mount.in
  60. utils.cpp
  61. utils.hpp
  62. version.cpp
  63. version.hpp
  64. watch.cpp
  65. watch.hpp
  66. xyz.openbmc_project.Software.BMC.Updater.service.in
  67. xyz.openbmc_project.Software.Download.service.in
  68. xyz.openbmc_project.Software.Sync.service.in
  69. xyz.openbmc_project.Software.Version.service.in
README.md

phosphor-bmc-code-mgmt

Phosphor BMC Code Management provides a set of system software management applications. More information can be found at Software Architecture

To Build

To build this package, do the following steps:

  1. meson build
  2. ninja -C build

To clean the repository run rm -r build.