image_types_gbmc_dynamic: Move image descriptor to end

We have cases where the image only gets partially flashed due to
interruptions in the process. This causes the hoth descriptor validation
scheme to think there is a valid image, even though a full checksum
validation would fail. When an update process tries to activate this
image, it has to go through an extra powercycle in order to have hoth
invalidate it. Once invalidated it will then flash it correctly.

If we just ensure the image is always invalid before being fully
flashed, we don't need to worry about ever misidentifying it.

Tested: Built and verified a rome / spr / tpu image to show valid
offsets + size in the u-boot / kernel and newly injected descriptor
space near the end of the image.

Fusion-Link: https://fusion2.corp.google.com/f53aaa90-bc8b-3ca8-a31c-b27d977628d8
Fusion-Link: https://fusion2.corp.google.com/b475264f-f029-3fd6-a847-f65cc67fc6be
Fusion-Link: https://fusion2.corp.google.com/8f24e37f-9899-30aa-a357-ea7fec6ec85f
Fusion-Link: https://fusion2.corp.google.com/36679082-8f48-3309-90c8-4d1dc24c3ea0

Platforms-Affected: All
Google-Bug-Id: 427819900
Change-Id: I8a1f710d09218f7622d6c69173860397d8478764
Signed-off-by: William A. Kennington III <wak@google.com>
(cherry picked from commit 1fd823e6ae90904bf027cc20cb84e8446c3062e4)
1 file changed
tree: f0241e1516ff4a3974de62c1753658f592735d12
  1. classes/
  2. conf/
  3. dynamic-layers/
  4. recipes-bsp/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-google/
  10. recipes-kernel/
  11. recipes-phosphor/
  12. recipes-support/
  13. recipes-tpm1/
  14. recipes-tpm2/
  15. LICENSE
  16. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.