commit 2bc87f8eee613ebb8296b12626f34aaa5362e60b
author Tom Wai-Hong Tam <waihong@chromium.org> Wed Jul 25 16:27:00 2012 +0800
committer Gerrit <chrome-bot@google.com> Wed Jul 25 05:22:59 2012 -0700
tree dcbd879632393e349123ec2703079ccd697e7c15
parent 1e40fa10e9aafc7ff954b855c2e9dbbea1024add

faft: Disable the GBB_FLAG_FORCE_DEV_SWITCH_ON on starting FAFT

Because this GBB flag forces to boot dev mode and we can't switch the
device back to normal mode. It hurts many FAFT test cases. So disable it
by default.

BUG=chromium-os:32874
TEST=Run firmware_TryFwB/control.dev passed.

Change-Id: Ic9747604d9c709241bcb772900bc2391239baed3
Reviewed-on: https://gerrit.chromium.org/gerrit/28370
Reviewed-by: Vic Yang <victoryang@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>

server/cros/faftsequence.py

diff --git a/server/cros/faftsequence.py b/server/cros/faftsequence.py
index c021430..b6e04ed 100644
--- a/server/cros/faftsequence.py
+++ b/server/cros/faftsequence.py
@@ -243,6 +243,13 @@
         if not self._remote_infos['faft']['used']:
             raise error.TestError('The use_faft flag should be enabled.')
 
+        gbb_flags = self.faft_client.get_gbb_flags()
+        if (gbb_flags & self.GBB_FLAG_FORCE_DEV_SWITCH_ON):
+            logging.info('Disable the GBB_FLAG_FORCE_DEV_SWITCH.')
+            self.faft_client.run_shell_command(
+                    '/usr/share/vboot/bin/set_gbb_flags.sh 0x%x' %
+                    (gbb_flags ^ self.GBB_FLAG_FORCE_DEV_SWITCH_ON))
+
         self.register_faft_template({
             'state_checker': (None),
             'userspace_action': (None),