FAFT: Support new GBB flags
The new GBB flag GBB_FLAG_FORCE_DEV_BOOT_FASTBOOT_FULL_CAP is new added.
It is default ON and FAFT should disable it at the beginning.
BUG=chromium:527484
TEST=Ran a FAFT test.
Change-Id: I12ab5ce61bf01e7045a46dc26da0c4c18fffa5a0
Reviewed-on: https://chromium-review.googlesource.com/295896
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
diff --git a/server/cros/vboot_constants.py b/server/cros/vboot_constants.py
index dd8c77a..d130bc8 100644
--- a/server/cros/vboot_constants.py
+++ b/server/cros/vboot_constants.py
@@ -133,6 +133,12 @@
GBB_FLAG_ENTER_TRIGGERS_TONORM = 0x00000040
GBB_FLAG_FORCE_DEV_BOOT_LEGACY = 0x00000080
GBB_FLAG_FAFT_KEY_OVERIDE = 0x00000100
+GBB_FLAG_DISABLE_EC_SOFTWARE_SYNC = 0x00000200
+GBB_FLAG_DEFAULT_DEV_BOOT_LEGACY = 0x00000400
+GBB_FLAG_DISABLE_PD_SOFTWARE_SYNC = 0x00000800
+GBB_FLAG_DISABLE_LID_SHUTDOWN = 0x00001000
+GBB_FLAG_FORCE_DEV_BOOT_FASTBOOT_FULL_CAP = 0x00002000
+
# VbSharedData flags, copied from:
# vboot_reference/firmware/include/vboot_struct.h