firmware_test: verify the cr50 console works
Boards like poppy have support for the cr50 console, but you still need
a reworked servo for the console to work. You should still be able to
run firmware_FAFTSetup even if you dont have the right servo rework.
This change will verify the cr50 console during setup. If the cr50
console controls exist, but the cr50 console doesn't work then it will
remove the cr50 attribute from the test object.
BUG=none
BRANCH=none
TEST=Use a servo v2 without the glados rework. Start servo with sudo
servod -b poppy. Run firmware_FAFTSetup
Change-Id: I9c59fe925d1e4843b008e8916b55be14468be20b
Signed-off-by: Mary Ruthven <mruthven@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/518342
diff --git a/server/cros/faft/firmware_test.py b/server/cros/faft/firmware_test.py
index 88b3c32..73cd18d 100644
--- a/server/cros/faft/firmware_test.py
+++ b/server/cros/faft/firmware_test.py
@@ -676,6 +676,9 @@
self.servo.set('cr50_console_capture', 'on')
self.cr50_console_file = os.path.join(self.resultsdir,
'cr50_console.txt')
+ # Check that the console works before declaring the cr50 console
+ # connection exists.
+ self.servo.get('ccd_lock')
self.cr50 = chrome_cr50.ChromeCr50(self.servo)
except error.TestFail as e:
if 'No control named' in str(e):
