Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-bmc-code-mgmt / a84f06d2e4217fff40c63ffbe9ef7608a1238bd4
commita84f06d2e4217fff40c63ffbe9ef7608a1238bd4[log] [tgz]
authorAdriana Kobylak <anoo@us.ibm.com>Tue Jan 18 15:41:57 2022 +0000
committerAdriana Kobylak <anoo@us.ibm.com>Mon Jan 31 20:25:39 2022 +0000
treee0d5d69e998b31a0df5822f262796986bff98baf
parent0cd6d84b0a58a950e691835f3241395d4628a6d4 [diff]
updater: Introduce the concept of flash id

There is a desire to be able to upload and update the same image to the
BMC. This would require to generate different version ids for each, not
tied to the version string. In order to correlate a version with the
persistent data on flash, introduce the concept of flash id.

Flash id is the name or id of the flash location where the image was
flashed, it could be a volume name, partition name, mtd device name,
etc.

Use the updater version Path property for the flash id value. A d-bus
property is needed so that obmc-flash-bmc can save the value once it
determines the location to flash the new image. The version Path
property is empty when the BMC boots up, and it's set to the image path
in /tmp/ when an image is uploaded. This change will set the Path
property to the location where the image resides when the BMC boots up,
and it'll update the Path property from /tmp/ to the location on flash
for an uploaded image once that image was successfully written to flash.

The ubi volume names are based on the uploaded version id, keep this the
same for simplicity, the flash id would then be the version id of the
uploaded image (which would eventually be a random number). The mmc
partitions are named rofs-a/rofs-b, so the flash id would be "a" or "b".

Tested: Verified the Path property was set to the version id on ubi and
to "a" or "b" on mmc.

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