History log of /external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
4777624b69b3b223a5d3c3abe86000783f6c0e96 06-May-2015 Tom Wai-Hong Tam <waihong@google.com> faft: Use mode_aware_reboot instead of reboot_warm and reboot_cold

This change removes reboot_warm, reboot_cold, reboot_warm_trigger,
and reboot_cold_trigger from FAFT framework and uses the new
mode_award_reboot method which does the same job.

BUG=chrome-os-partner:16231
TEST=Ran some of the affected FAFT tests on Jerry.

Change-Id: I9f0d1fd3416c7e4a624a915507dfa9c97f16d3e0
Reviewed-on: https://chromium-review.googlesource.com/269764
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.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/site_tests/firmware_TryFwB/firmware_TryFwB.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/site_tests/firmware_TryFwB/firmware_TryFwB.py
2e18b8a280bb0597db59b62878b1585d76ee6739 21-Nov-2014 Daisuke Nojiri <dnojiri@chromium.org> fix firmware tests for vboot2

vboot2 stays in slot B as long as it's good and valid. some tests such as
RollbackFirmware fail because they assume the firmware prefers slot A, thus,
expect mainfw_act is A after reboot.

vboot1 firmware should not be affected by this change.

BUG=chrome-os-partner:32193
BRANCH=ToT
TEST=Ran faft on Nyan Blaze and Kitty

Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>
Change-Id: I116c13772dd2158c330dbcf7a8002c0fbb4fc3a3
Reviewed-on: https://chromium-review.googlesource.com/231378
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
57c059860b30cf3e9cde1940e9d02e0477c92694 26-Jun-2014 Daisuke Nojiri <dnojiri@chromium.org> vboot2: adjust expectation based on the new firmware selection behavior

vboot2 selects firmware based on fw_try_next value and continues to use the slot
until the next update. Autoupdate uses whichever inactive slot to try out a new
image while vboot1 always writes a new image to slot B.

TEST=Ran firmware_* tests against Blaze with USE=+/-vboot2.
BUG=none
BRANCH=none
Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>

Change-Id: I586235bcc5ca52282fe9652b51e5dd311b4fac4c
Reviewed-on: https://chromium-review.googlesource.com/205988
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Daisuke Nojiri <dnojiri@chromium.org>
Tested-by: Daisuke Nojiri <dnojiri@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
b3b23205345e1611024003ff2e402d9e0f08c7a7 13-May-2014 Yusuf Mohsinally <mohsinally@google.com> Converting firmware_TryFwB to use new FirmwareTest class.

The new FirmwareTest class does not require the traditional dict of objects
that FAFTSequence required.

1. Converted the test to use the new flat function call style.

BUG=chromium:371185
TEST=Manually ran this test at desk against wolf device.

Change-Id: I6d5fe640f746ee81763e3e606cb1125a3110b658
Reviewed-on: https://chromium-review.googlesource.com/199530
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
1f115ae9ee3c043e9577e7ce9872dc99323fdcb3 07-Nov-2013 Yusuf Mohsinally <mohsinally@chromium.org> Correctly using initialize() rather than setup() for FAFT tests.

FAFT tests have been using setup() (which is run once at autotest init), when
it should have instead used initialize() for running code before each
test case is run.

BUG=chromium:267175
TEST=Ran tests manually against Pit device to ensure that these changes did not
introduce problems.

Change-Id: If0e76e12b9f40249154d7b95a1375b2787a56304
Reviewed-on: https://chromium-review.googlesource.com/176024
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.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/site_tests/firmware_TryFwB/firmware_TryFwB.py
d4340315f76fcae9a5e9430d0446705f4f8fa7b7 17-Jul-2013 Tom Wai-Hong Tam <waihong@chromium.org> FAFT: Rename the module faftsequence to faft_classes

For preparing the future refactoring that splitting FAFTSequence into
multiple meaningful small classes, changes the original module name
faftsequence to faft_classes.

BUG=chrome-os-partner:21118
TEST=Manual
Ran the affected test cases, firmware_FAFTSetup, on Spring and passed.

Change-Id: I662cfc8d37a54711d7c52ff5322ed28a9a759ffe
Reviewed-on: https://gerrit.chromium.org/gerrit/62642
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
d43aa9b4568e0b1283d6ff535b87446b14a6e3b9 16-Nov-2012 Chun-ting Chang <ctchang@chromium.org> Classify methods in FAFTClient

There are too many methods in FAFTClient, so this CL is to classify them into
several groups: ec, bios, kernel. Methods which can be put into one of the
target group should be renamed with format _[group name]_[method name].
For example, dump_firmware should be modified to bios_dump. To call methods in
FAFTClient, use [group name].[method name].

BUG=chromium-os:36429
TEST=run firmware update tests

Change-Id: I7ead01246121b454c0a9f29e10bd026a77925e4f
Reviewed-on: https://gerrit.chromium.org/gerrit/38186
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Chun-Ting Chang <ctchang@chromium.org>
Tested-by: Chun-Ting Chang <ctchang@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
700c9fd170eab25bcd60e56ac9b5f3c40b87d6f1 15-Nov-2012 Tom Wai-Hong Tam <waihong@chromium.org> faft: Support tests running in EC WP'ed and add a new test suite for them

In order to check EC WP behavior, we enables EC WP at the beginning of tests,
runs the same tests on normal mode, and restores the original EC WP state.

This new test suite (suite:faft_ec_wp) now contains all faft_lv1 and faft_lv2
test cases.

BUG=chrome-os-partner:15835
TEST=run_remote_tests --board link --remote dut suite:faft_ec_wp

Change-Id: I91096d463ce8ad0503e021b5d81b53a3d95116dc
Reviewed-on: https://gerrit.chromium.org/gerrit/38114
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
b09a04183cf7017eb4b30ad28f5f81f1204c36b3 06-Nov-2012 Vic Yang <victoryang@chromium.org> faft: Fix lint warning and error

This includes removing unnecessary 'pass' and unused argumenets.

BUG=chrome-os-partner:35902
TEST=Check tests still work.

Change-Id: Ifb9ac8348e7e26e2ea1a10b9c7e509f817e117b9
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/37424
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
ebf4094ae637680bfcfbf4d43a36e9dd7b1a4e54 05-Nov-2012 Tom Wai-Hong Tam <waihong@chromium.org> faft: Ensure DevMode and TryFwB tests going back to their original modes

The DevMode and TryFwB tests may not go back to their original modes
on test failures, like DevMode may end with a different mode, TryFwB
may end with firmware B booting. This CL is to add a check to ensure
these tests going back.

BUG=chromium-os:35902
TEST=run_remote_tests.sh --board link --remote dut DevMode TryFwB/control$

Change-Id: If312fdc53a5210e29c42042e56d18a78df2ffd68
Reviewed-on: https://gerrit.chromium.org/gerrit/37334
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
893bcc0871678b7ba9f70ac1f189e19db8c8db18 02-Nov-2012 Tom Wai-Hong Tam <waihong@chromium.org> faft: Unify all USB disk setup code in a new method setup_usbkey()

This CL adds a new method setup_usbkey() in FAFTSequence class, which
helps all USB disk related setup and check. Its usage:

If the test requires USB key (Chrome OS test image inside) and muxes to host:
self.setup_usbkey(usbkey=True, host=True)

If the test requires USB key (Chrome OS test image inside) and muxes to DUT:
self.setup_usbkey(usbkey=True, host=False)

If the test does not requires USB key:
self.setup_usbkey(usbkey=False)

BUG=chromium-os:35902
TEST=run the FAFT suite:
$ run_remote_tests.sh --board link --remote dut suite:faft_bios

Change-Id: If6eb94ee52f612df568c4f2f07a7acbbdd0a0b66
Reviewed-on: https://gerrit.chromium.org/gerrit/37193
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
f93f702b4e2b59bab22cde8d4d05b35a31520f6a 31-Oct-2012 Vic Yang <victoryang@chromium.org> faft: Move FAFT checkers to a separate module

BUG=chrome-os-partner:35902
TEST=Run FAFT suites and check they still work fine.

Change-Id: Idfb60632b67e7bc92b4ae12a60269e00c7b90b77
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/36989
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
fd590c94039af41dcfe0cecb28a1a97ddfb978b2 25-Nov-2011 Tom Wai-Hong Tam <waihong@chromium.org> Introduce setup_tried_fwb() for setting up tried_fwb state.

Also reuse run_faft_step() in setup_dev_mode().

BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
servo_vid=0x18d1 servo_pid=0x5001" firmware_TryFwB

Change-Id: I33dd859cec259baf5082fe2550008a264d3bc5e0
Reviewed-on: https://gerrit.chromium.org/gerrit/12111
Reviewed-by: Todd Broch <tbroch@chromium.org>
Reviewed-by: Rajesh Chenna <rchenna@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
9b75bc090bbc5f79cd5e36204b1fb0c40185d3c3 10-Nov-2011 Tom Wai-Hong Tam <waihong@chromium.org> Make FAFT test cases support running in both normal and dev modes.

Make the test cases, which are dev mode independent, to support running in
both normal mode and dev mode. These test cases will first prepare the system
in normal mode or dev mode and run the original tests.

BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a \
"xml_config=$OVERLAY_XML servo_vid=0x18d1 servo_pid=0x5001" control.faft

Change-Id: I5cc73de275a65c3bb0920e977d3ab5104bfacd1b
Reviewed-on: https://gerrit.chromium.org/gerrit/11461
Reviewed-by: Todd Broch <tbroch@chromium.org>
Reviewed-by: Rajesh Chenna <rchenna@chromium.org>
Tested-by: Rajesh Chenna <rchenna@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
2c50dff8cafad24f45a43c9a2c896afc887bd832 11-Nov-2011 Tom Wai-Hong Tam <waihong@chromium.org> Refactor FAFT test case by introducing a new method run_faft_step().

BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a \
"xml_config=$OVERLAY_XML servo_vid=0x18d1 servo_pid=0x5001" control.faft

Change-Id: Icd7763017eec9a0460ce01569b760ec1df983051
Reviewed-on: https://gerrit.chromium.org/gerrit/11510
Reviewed-by: Todd Broch <tbroch@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
a9c1a50d1f5acaca1d7410dd9d07455531d4ac34 09-Nov-2011 Tom Wai-Hong Tam <waihong@chromium.org> Disable dev mode by default and some refactoring.

Refactoring includes:
- Add setup_dev_mode() to ensure the system in the normal/dev mode.
- Move wait_fw_screen_and_ctrl_d() to FAFTSequence base class.
- Move delay timing to FAFTSequence base class.
- Increase the USB unplug and plug delay in order to see the INSERT screen.

BUG=chromium-os:22712
TEST=manaul run on Kaen
$ run_remote_tests.sh --remote=$REMOTE_IP -a \
"xml_config=servo_tegra2_kaen_overlay.xml \
servo_vid=0x18d1 servo_pid=0x5001" firmware_DevMode
$ run_remote_tests.sh --remote=$REMOTE_IP -a \
"xml_config=servo_tegra2_kaen_overlay.xml \
servo_vid=0x18d1 servo_pid=0x5001" firmware_DevTriggerRecovery
$ run_remote_tests.sh --remote=$REMOTE_IP -a \
"xml_config=servo_tegra2_kaen_overlay.xml \
servo_vid=0x18d1 servo_pid=0x5001" firmware_RecoveryButton

Change-Id: I7e2c0d91bb315a41863a68f35b15b6e2d65f2eba
Reviewed-on: https://gerrit.chromium.org/gerrit/11430
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
f1e34973ad1af93bbc2b24f6d9eaa267176e3e71 02-Nov-2011 Tom Wai-Hong Tam <waihong@chromium.org> Use hardware reboot instead of software reboot as FAFT default reboot action.

We don't use software reboot as default because the time of software reboot
is various. It is hard to determine the delay time of firmware screen showed.
So we use hardware reboot instead.

BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_UserRequestRecovery

Change-Id: I6f1f60b7b30ec05f2e1fdc83078dc30f6a764873
Reviewed-on: https://gerrit.chromium.org/gerrit/11040
Reviewed-by: Todd Broch <tbroch@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
e0550de479199ef836845efa97afb3556d679158 02-Nov-2011 Tom Wai-Hong Tam <waihong@chromium.org> Rename function name from confirm_normal_boot to ensure_normal_boot.

Since these functions are not just confirming it. They are taking actions
to ensure it.

BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_TryFwB
run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_DevMode
run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_CorruptFwA
run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_CorruptFwB
run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_UserRequestRecovery
run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_RecoveryButton

Change-Id: Ic1c38ac0fd860120c216114eb77d49b3245f5efa
Reviewed-on: https://gerrit.chromium.org/gerrit/11038
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py
e8559171c135f436e6094cfb8c15f4ddf80b4a78 22-Sep-2011 Tom Wai-Hong Tam <waihong@chromium.org> Implement a test case for setting firmware B boot.

BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_TryFwB

Change-Id: I360b794b74459e3241488de8aff2206026a7c38c
Reviewed-on: http://gerrit.chromium.org/gerrit/8119
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_TryFwB/firmware_TryFwB.py