| 19bfb6ea468c34e1b44842033eb784c2ef3eed42 |
|
20-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Move wait_for_client and wait_for_client_offline to ModeSwitcher
These two methods are tightly related to ModeSwitcher. This change
helps it to be derived to different implementations.
BUG=chrome-os-partner:39744
TEST=Ran some of the effected FAFT tests.
Change-Id: Id9be1decec3ebc5a843a30b3070a2352546423eb
Reviewed-on: https://chromium-review.googlesource.com/294773
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
/external/autotest/server/site_tests/firmware_TPMKernelVersion/firmware_TPMKernelVersion.py
|
| 0430288e1ea7c2976db8612c595223dc2a220563 |
|
14-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Abstract the firmware screen bypass logic to FwBypasser class
Introduces a new FwBypasser class which abstract the firmware bypass
behaviors, like:
- bypass_dev_mode
- bypass_dev_boot_usb
- bypass_rec_mode
- trigger_dev_to_rec
- trigger_rec_to_dev
- trigger_dev_to_normal
The FwBypasser is created in ModeSwitcher and its methods are also
exposed to ModeSwitcher too.
It merges the delay of waiting dev screen into the firmware screen,
simplifies the USB replug logic, moves some not-frequently-used
methods to the tests.
BUG=chrome-os-partner:16231
TEST=Ran suites faft_lv1, faft_lv2, faft_lv3, and faft_lv4 on Samus.
Change-Id: Ie46924d1122b9ff78625ca0d562747e04a0f826d
Reviewed-on: https://chromium-review.googlesource.com/271282
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Tom Tam <waihong@google.com>
Commit-Queue: Tom Tam <waihong@google.com>
/external/autotest/server/site_tests/firmware_TPMKernelVersion/firmware_TPMKernelVersion.py
|
| eeed7fb22ebdabb9454ee6020072559532796c0d |
|
08-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Install Autotest dependency automatically
FAFT tests used to explicitly to install Autotest dependency when
booting into an USB image as it may not have Autotest there. It
makes a bit confusion if it is needed or not. This change removes
this confusion by always installing Autotest dependency when the
original connection to DUT is lost, meaning that a new RPC
connection has to be established, furthermore better to ensure
Autotest dependency is also there.
BUG=chrome-os-partner:16231
TEST=Removed the Autotest directory from the USB stick, ran
firmware_RecoveryButton test, and checked Autotest reinstalled.
Change-Id: I6cfc4f0bf3fb6b5386115a9464bb042059849bb5
Reviewed-on: https://chromium-review.googlesource.com/270101
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/site_tests/firmware_TPMKernelVersion/firmware_TPMKernelVersion.py
|
| eabe8051fc4b0112529d9e93bd35e5d951a452b8 |
|
07-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Simplify test flows by using wait_for_dut_up=True
It modifies test flows to reuse the mode_aware_reboot method to
wait for DUT up, not to do duplicated works.
BUG=chrome-os-partner:16231
TEST=Ran all affected FAFT tests on Jerry.
Change-Id: I55ec5b5b6dd8181a8ba56838ad6cecfe544a111b
Reviewed-on: https://chromium-review.googlesource.com/270014
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_TPMKernelVersion/firmware_TPMKernelVersion.py
|
| 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_TPMKernelVersion/firmware_TPMKernelVersion.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_TPMKernelVersion/firmware_TPMKernelVersion.py
|
| 8d99c1b07fe3a8eacd69a151cc2e9a9724bb2c40 |
|
04-Dec-2014 |
Danny Chan <dchan@google.com> |
Automate test case 1.2.4 Check Kernel version in TPM is not corrupted.
Description: Booting in dev mode does not corrupt kernel and firmware
version stored in the TPM.
Setup Steps:
1. Install the Chrome OS Test image on DUT.
2. Install test firmware (BIOS and EC)
3. Check the device is in developer mode
4. Prepare USB with latest Chrome OS
Test Steps:
5. Go to VT2
6. Run stop tcsd
7. Run tpmc read 0x1008 0x0d
8. Boot to Chrome OS from USB
9. Go to terminal and Run crossystem tpm_kernver and tpm_fwver
Verification Steps:
1.Output of "tpmc read 0x1008 0x0d" should display
1 4c 57 52 47 1 0 1 0 0 0 0 0
Mark test fail if output look something like
1 4c 57 52 47 ff ff ff ff 0 0 0 0
2. Output of "crossystem tpm_kernver and tpm_fwver" should report
something like 0x00010001,
Mark test failed if return (error) or 0xFFFFFFFF
BUG=None
TEST=None
Change-Id: I6d623a6be19d07a090a7f038cae6233328107781
Reviewed-on: https://chromium-review.googlesource.com/233027
Trybot-Ready: danny chan <dchan@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: danny chan <dchan@chromium.org>
Commit-Queue: danny chan <dchan@chromium.org>
/external/autotest/server/site_tests/firmware_TPMKernelVersion/firmware_TPMKernelVersion.py
|