| c7bdb7579baeeb7957001310cbd4dba63c4c43b3 |
|
25-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Use fwtool instead of ectool for DUT using a host
On Ryu, the ectool doesn't exist. Use the fwtool instead.
BUG=chromium:527484
TEST=Ran the firmware_SoftwareSync which uses this method.
Change-Id: Ib9f88b5242ad1a2b86b7f14f426f85e8327a0d28
Reviewed-on: https://chromium-review.googlesource.com/295569
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
/external/autotest/server/cros/faft/utils/faft_checkers.py
|
| 2ae4244b71f60e808107434f944a120719e1e438 |
|
20-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Deprecate FAFT config keyboard_dev
The new config mode_switcher_type replaces it. Change all tests to
use mode_switcher_type instead.
BUG=chrome-os-partner:39744
TEST=Ran firmware_DevTriggerRecovery on Samus and Whirlwind.
Change-Id: I14d563e4e87307be858ba661ac0046435983f91d
Reviewed-on: https://chromium-review.googlesource.com/272434
Tested-by: Tom Tam <waihong@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
/external/autotest/server/cros/faft/utils/faft_checkers.py
|
| 69a7d658b794cdbd2ada1544ba80ad798155fab6 |
|
08-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Fix mode_aware_reboot under recovery mode and suppress logging
Under normal and dev mode, the mode_aware_reboot works fine to bypass
the next firmwre screen to enter either the same mode or recovery
mode. However, under recovery mode, there are 3 possible modes on the
next boot, i.e. normal, dev, and recovery modes. We should try to
both press Ctrl-D and replug USB.
This change also skips the unnecessary logging messages when checking
the current mode.
BUG=chrome-os-partner:16231
TEST=Ran firmware_CorruptBothFwSigAB on both normal and dev modes on Jerry.
Change-Id: I42b426a45779c3a9c65f8fe8ce3a0c572ffc9cb2
Reviewed-on: https://chromium-review.googlesource.com/270102
Trybot-Ready: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
/external/autotest/server/cros/faft/utils/faft_checkers.py
|
| 0cc9a4fe28f221cfc73bb35c30fa79338c4b43f1 |
|
01-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Refactor setup_mode and restore_mode
The change moves and splits the original logic on setup_dev_mode and
restore_dev_mode to FAFTCheckers and ModeSwitcher. It is also enhanced
to support setting up all firmware modes, including recovery. They are
now methods in ModeSwitcher as they are highly related to mode
switching.
BUG=chrome-os-partner:39744
TEST=Switched DUT to normal mode and ran firmware_DevMode. Then
switched DUT to dev mode and run firmware_DevMode. Checked DUT
restored to the original mode state.
Change-Id: I16314d18b785da59473df3ef5e02f7fe8f2693b0
Reviewed-on: https://chromium-review.googlesource.com/268858
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
/external/autotest/server/cros/faft/utils/faft_checkers.py
|
| 3edea989126b84d38135371e780184694892a55a |
|
30-Dec-2014 |
Shelley Chen <shchen@chromium.org> |
autotest: Add fw_tries_checker function for handling fwb_tries in vboot2
The firmware_FWtries test uses the fwb_tries field to switch between FW A and B,
which is only supported by vboot1. Adding fw_tries_checker function so that if
it detects that we are in vboot2, it ignores the tried_fwb flag (because this
flag has no meaning in vboot2). If it detects that we are checking the
fwb_tries field, then it tried to check the fw_try_count field instead for
vboot2.
BUG=chrome-os-partner:33451 (portion of it)
TEST=test_that --board=veyron_pinky <ip> firmware_FWtries
test_that --board=veyron_pinky <ip> firmware_CorruptFwBodyA
test_that --board=veyron_pinky <ip> firmware_RollbackFirmware
test_that --board=veyron_pinky <ip> firmware_CorruptFwSigB
test_that --board=veyron_pinky <ip> firmware_UpdateFirmwareVersion
test_that --board=veyron_pinky <ip> firmware_CorruptFwBodyB
test_that --board=veyron_pinky <ip> firmware_TryFwB
test_that --board=veyron_pinky <ip> firmware_CorruptFwSigA
test_that --board=nyan_blaze <ip> firwmare_FWtries
test_that --board=nyan_blaze <ip> firwmare_CorruptFwBodyA
test_that --board=nyan_blaze <ip> firwmare_CorruptFwSigB
test_that --board=nyan_blaze <ip> firwmare_CorruptFwBodyB
test_that --board=nyan_blaze <ip> firwmare_TryFwB
test_that --board=nyan_blaze <ip> firwmare_CorruptFwSigA
* All veyron testing with vboot2, nyan testing with vboot1. Tests included
above are all passing with code change. No new failures detected with
modification.
Change-Id: I91bfa5c3419287a7910360d19932ba26c806e4db
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/238071
Reviewed-by: Julius Werner <jwerner@chromium.org>
/external/autotest/server/cros/faft/utils/faft_checkers.py
|
| b557fecd26339e0e8194cfc350b7d2b5a24fd3a1 |
|
11-Nov-2013 |
Yusuf Mohsinally <mohsinally@chromium.org> |
Adding a test for crossystem output of TPM versions.
Automating testcase '1.1.9 TPM_version_in_Crossystem [tcm:6762253]'. Which also
entailed appending the DEFAULT.py device config for expected values. The board
specific config will have to be updated as needed for their own expected values.
Also, added 2 minor logging messages to faft crossystem checkers to print the
compared values on success as wel.
BUG=None
TEST=Manually ran tests against spring device at desk.
Change-Id: I1d09157fa0a0bdcfc87efee9cf5dbfb7d53b0e77
Reviewed-on: https://chromium-review.googlesource.com/176400
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/cros/faft/utils/faft_checkers.py
|
| 73c28f3abd6ec8de4dc5a8e6afca1d5e83eb59c7 |
|
03-Aug-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Reorginazing FAFT (server side) files.
Initial reorganization step while moves FAFT (autotest/server)
files over to packages. Naming and other cleanup will be performed
in additional CLs.
BUG=None
TEST=built and ran faft tests at desk against Link
Change-Id: I83712620c0e6816ec08b9afdf8c227a800734ea6
Reviewed-on: https://gerrit.chromium.org/gerrit/64408
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/cros/faft/utils/faft_checkers.py
|