| 3e92b8e9041fa7bb44dc9285e2c415eb611697a9 |
|
07-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Remove do_reboot_action and use the single-entry reboot method
This change further unifies more calls, which use do_reboot_action,
to adapt the new mode_aware_reboot method.
BUG=chrome-os-partner:16231
TEST=Ran all affected FAFT tests on Jerry.
Change-Id: I74120fe091cc06a910c1e31f09fdf748a2bb028d
Reviewed-on: https://chromium-review.googlesource.com/270013
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_ECWriteProtect/firmware_ECWriteProtect.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_ECWriteProtect/firmware_ECWriteProtect.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_ECWriteProtect/firmware_ECWriteProtect.py
|
| 8f359c3b8dfcae210e5fae8f378b558a1cc3d3b2 |
|
16-May-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Converting firmware_ECWriteProtect 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 peppy
Change-Id: Ibb7c94eaae5a492bd378e1395b773a1dd245394a
Reviewed-on: https://chromium-review.googlesource.com/200152
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_ECWriteProtect/firmware_ECWriteProtect.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_ECWriteProtect/firmware_ECWriteProtect.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_ECWriteProtect/firmware_ECWriteProtect.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_ECWriteProtect/firmware_ECWriteProtect.py
|
| a051510c53dbbd01f768a2546098ec73ba325221 |
|
07-May-2013 |
Vic Yang <victoryang@chromium.org> |
Suppress EC console for FAFT EC tests
For EC tests, suppress EC console output so that they don't interfere
with our tests.
BUG=None
TEST=Run firmware_ECBattery on Spring
Change-Id: Iff312951d056d3f8a3d54b26896f83100209a4ad
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/50245
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/firmware_ECWriteProtect.py
|
| 5c8f8670ff46c6b3523fb2ea49a520186240b603 |
|
18-Jan-2013 |
Vadim Bendebury <vbendeb@chromium.org> |
Fix EC UART interactions
When FAFT is running on a setup where the servo board is controlled by
a Beaglebone board, many EC tests fail because the expected output
from the EC console is not received in the allotted time.
Actually, there is no need to limit the time when the test is waiting
for the response: if the expected response comes, the wait stops right
there, so the timeout does not matter. If the response does not show
up, a few extra seconds will not make things much worse.
This change deprecates the timeout parameter, all uses of
send_command_get_output() will run with the same previously set
timeout. By default the timeout is set to 3s in the servod package
(https://gerrit.chromium.org/gerrit/41568).
If some tests need a longer timeout, or there is a point in specifying
a short timeout, it still could be done using the `ec_uart_timeout'
control.
BUG=chromium-os:22475
TEST=manual
. successfully ran the following tests in two setups, with local and
remote servos:
firmware_ECAdc
firmware_ECBattery
firmware_ECBootTime
firmware_ECCharging
firmware_ECKeyboard
firmware_ECPeci
firmware_ECPowerG3
firmware_ECSharedMem
firmware_ECThermal
firmware_ECUsbPorts
firmware_ECWakeSource
firmware_ECWatchdog
firmware_ECWriteProtect
firmware_FAFTSetup
Change-Id: I0da2f9a0924574846a6c7650e996576a7d2b76aa
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/41618
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/firmware_ECWriteProtect.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_ECWriteProtect/firmware_ECWriteProtect.py
|
| 0bd8486b5e1c3b481d96736d8d56f8e85125442c |
|
26-Nov-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Use super-class FAFTSequence setup for EC write-protection setting
FAFTSequence supports EC write-protection setup. Use it instead of doing
the same thing in the test.
BUG=chrome-os-partner:15835
TEST=run_remote_tests --board link --remote dut ECWriteProtect/control$
Change-Id: Ib1931b70706df73085f8cf10a69d7e32282e525a
Reviewed-on: https://gerrit.chromium.org/gerrit/38642
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_ECWriteProtect/firmware_ECWriteProtect.py
|
| 44204b3e74e1ee85a19e330894e731ef554c0a6d |
|
20-Nov-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Support EC write protect on non-Chrome-EC devices
On non-Chrome-EC devices, we use flashrom as a single interface to set
write protection for different chips. This CL supports this function
such that we can run suite:faft_ec_wp on non-Chrome-EC devices.
BUG=chrome-os-partner:15835
TEST=mock the flashrom in DUT and run suite:faft_ec_wp, see it executed.
Change-Id: I0745a2cf05656ba84099847d3eb63c924027fd90
Reviewed-on: https://gerrit.chromium.org/gerrit/38363
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_ECWriteProtect/firmware_ECWriteProtect.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_ECWriteProtect/firmware_ECWriteProtect.py
|
| 52116d46f6908f602ad243b3ba0ed7396900d4f4 |
|
05-Nov-2012 |
Vic Yang <victoryang@chromium.org> |
faft: Support multiple action call
We used to use lambda function to do multiple calls at once, which
causes loss in test log. Let's add support for multiple action call.
BUG=chrome-os-partner:35902
TEST=Pass firmware_ECWriteProtect and check multiple actions are
actually called.
Change-Id: I484f44a11974875f29bfd01e6544c1b0237b08eb
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/37347
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/firmware_ECWriteProtect.py
|
| 624bc729d4ba44cc374ddfc23108810ef8a9e889 |
|
05-Nov-2012 |
Vic Yang <victoryang@chromium.org> |
firmware_ECWriteProtect: Unprotect EC before testing
If EC is already write protected, unprotect it before starting write
protection test.
BUG=chrome-os-partner:15835
TEST=Write protect EC and start the test. Check the test unprotect EC
and pass.
Change-Id: Ia5252629ea19b670e4fce0365a0d1c2382ad1001
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/37346
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/firmware_ECWriteProtect.py
|
| bb92e6c1ec6789228ef3122f3bf1ae2364b0dd2e |
|
30-Oct-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Chrome EC class supports a reboot method
So far, we do a EC reboot by either sending a EC command or using client
side ectool. This CL make Chrome EC class provide a single interface
to require EC reboot. Several reboot types are supported:
default: EC soft reboot;
'hard': EC hard/cold reboot;
'ap-off': Leave AP off after EC reboot (by default, EC turns
AP on after reboot if lid is open).
BUG=chromium-os:35254
TEST=run_remote_tests.sh --board link --remote dut FAFTSetup
Change-Id: Iabbd87ee7f06b8ef361bd56016fadc9696517cec
Reviewed-on: https://gerrit.chromium.org/gerrit/36862
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_ECWriteProtect/firmware_ECWriteProtect.py
|
| 25d1f63d1a7d261edafaecf79e8eef8a3eafade9 |
|
01-Nov-2012 |
Vadim Bendebury <vbendeb@chromium.org> |
Do not try write protecting the EC if wp_boot == 1
In case the DUT has the hardware write protection enabled (the WP
screw is installed), the EC write protection action could not be
undone unless the screw is removed.
Do not run the firmware_ECWriteProtect test in case the system is
write protected in HW. Also, remove the ensure_fw_a_boot() method not
used by anyone.
BUG=chrome-os-partner:15835
TEST=manual
. run the following test
~/trunk/src/scripts/run_remote_tests.sh --board=link --servo \
--remote=192.168.1.2 firmware_ECWriteProtect/control.dev
with and without the write protect screw installed. The test passes
in both cases.
Change-Id: I2e42a7057f2d615456b158d5edd0b3f8a7febca7
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/37123
Reviewed-by: Vic Yang <victoryang@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/firmware_ECWriteProtect.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_ECWriteProtect/firmware_ECWriteProtect.py
|
| 01d5e57a6bbe304c026ce2801e7e744d23694a91 |
|
23-Oct-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Refactor the one time setup methods of FAFT
This CL makes all the one time setup states in a single place. It'd be easy
to add more in the future. And wrap the class level variable in methods to
prevent mis-used.
BUG=chromium-os:34392
TEST=run a test suite to see the GBB flag setup only run once:
run_remote_tests.sh --board daisy --remote dut control.faft_lv1
Change-Id: I113cd04777231bbde8e3f924c0661b0412ac36ec
Reviewed-on: https://gerrit.chromium.org/gerrit/36303
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_ECWriteProtect/firmware_ECWriteProtect.py
|
| dbaba8f38dcdf98595105e36f177153c02b27e0e |
|
17-Oct-2012 |
Vic Yang <victoryang@chromium.org> |
faft: Skip checking GBB flags after the first test finished
There is no need to set GBB flags at the beginning of every test. We
just need to set them when running the first test. This saves us about
8 seconds per test.
BUG=chromium-os:34392
TEST=Run a test suite. Check GBB flags is only set in the first test.
Change-Id: Ib23e1326d208634e7331ff2bb54000529d11afb0
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/35811
/external/autotest/server/site_tests/firmware_ECWriteProtect/firmware_ECWriteProtect.py
|
| 6019a1a0c375bee346b183921d3edf5f098d3f68 |
|
12-Oct-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Refactor Chrome EC related methods into a class
So far the Chrome EC related methods are quite distributed across tests.
We should have a single place to control all the Chrome EC functions.
This CL does the first step to refactor the UART command methods into
the ChromeEC class.
BUG=chromium-os:35254
TEST=run_remote_tests.sh --board link --remote dut suite:faft_ec
Change-Id: If148170bcf6801a2a33f666b8a5a7fadc47f3243
Reviewed-on: https://gerrit.chromium.org/gerrit/35403
Reviewed-by: Vic Yang <victoryang@chromium.org>
Reviewed-by: Mike Truty <truty@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_ECWriteProtect/firmware_ECWriteProtect.py
|
| 41859a60694f31a5f7dc8d76585f93a3a7265ff5 |
|
03-Oct-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Change the return type of send_uart_command_get_ouput to a literal struct
We are going to move the method send_uart_command_get_output to servod. FAFT
will call it via a RPC, which only accepts literal structures. The original
return type re.MatchObject is not a literal structure.
This change is to change the return type of send_uart_command_get_ouput to
a list of tuples, each of which contains the entire matched string and all
the subgroups of the match.
This change also restricts the argument regex_list to be an explicit list.
BUG=chromium-os:34787
TEST=run_remote_tests.sh --remote $DUT suite:faft_ec
Change-Id: Ic247fd65109d7ad4b716611b3cc6728665b1309c
Reviewed-on: https://gerrit.chromium.org/gerrit/34609
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_ECWriteProtect/firmware_ECWriteProtect.py
|
| 6ec46e3ef11a31c23917e1c1b8a661bb39949cef |
|
05-Oct-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Move all constants of verified boot out to a module
It slims the FAFTSequence class and makes other non-FAFT tests reuse these
vboot constants.
BUG=chromium-os:32147
TEST=run the following tests passed:
run_remote_tests.sh --board link --remote dut control.faft_lv2
run_remote_tests.sh --board link --remote dut control.faft_lv3
Change-Id: I524d1ff2046e1e1826359c939f2d918426707141
Reviewed-on: https://gerrit.chromium.org/gerrit/34739
Reviewed-by: Mike Truty <truty@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/firmware_ECWriteProtect.py
|
| fa47407a2de9b579ac98c87c40c2117c334248a4 |
|
07-Sep-2012 |
Chun-ting Chang <ctchang@chromium.org> |
Backup firmware in tests which will modify firmware
Use backup_firmware() (in faftsequence) before testing, and restore_firmware()
(in faftsequence) after testing.
BUG=chromium-os:33641
CQ-DEPEND=32504
TEST=run_remote_tests.sh --servo [test]
Change-Id: I5fd927f4855df9d5ddb5fc3e458f4c83be244b51
Reviewed-on: https://gerrit.chromium.org/gerrit/32528
Reviewed-by: Tom Wai-Hong Tam <waihong@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_ECWriteProtect/firmware_ECWriteProtect.py
|
| fc700b5d2aa218357936661918f36f0d1a778595 |
|
13-Sep-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Change the action tuple to support error_msg
We used the format of action tuple before, like (function, arg1, arg2, ...).
We want to specify the error_msg such that an user knows better why the test
is failed. So this CL changes the action tuple to (function, args, error_msg).
The args and error_msg are optional. The args is either a value or a tuple
if multiple arguments.
BUG=chromium-os:22598
TEST=run_remote_tests.sh --remote=$DUT control.faft_lv1
run_remote_tests.sh --remote=$DUT control.faft_lv2
run_remote_tests.sh --remote=$DUT -a "new_ec=foo" control.faft_lv3
When a test fails, it returns somethings like:
13:31:58 INFO | FAIL firmware_CorruptFwBodyB.dev firmware_Corrupt
FwBodyB.dev timestamp=1347600718 localtime=Sep 14 13:31:58 Not succe
ed: calling <bound method firmware_CorruptFwBodyB.crossystem_checker of <firmwar
e_CorruptFwBodyB.firmware_CorruptFwBodyB object at 0x2d1f490>> with args ({'trie
d_fwb': '1', 'mainfw_act': 'B'},) returning False
Change-Id: I5f016da443ccc8c067a4621e6bf881ef99bdd481
Reviewed-on: https://gerrit.chromium.org/gerrit/33290
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_ECWriteProtect/firmware_ECWriteProtect.py
|
| e3c7243cfdf904f884f895c38b596d19bb1d4ad0 |
|
05-Sep-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Move PREAMBLE_USE_RO_NORMAL to FAFTSequence
This flag is used frequently. Move it to FAFTSequence.
BUG=chromium-os:34147
TEST=Run the following tests:
$ run_remote_test.sh --remote=$IP CorruptFwBodyA/control$
$ run_remote_test.sh --remote=$IP CorruptFwBodyB/control$
$ run_remote_test.sh --remote=$IP CorruptBothFwBodyAB/control$
$ run_remote_test.sh --remote=$IP SoftwareSync/control$
$ run_remote_test.sh --remote=$IP RONormalBoot/control$
$ run_remote_test.sh --remote=$IP UpdateECBin/control$
$ run_remote_test.sh --remote=$IP ECWriteProtect/control$
Change-Id: I96930dfb4405a3108204054aa74a177042e1d3ec
Reviewed-on: https://gerrit.chromium.org/gerrit/32204
Reviewed-by: Mike Truty <truty@chromium.org>
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_ECWriteProtect/firmware_ECWriteProtect.py
|
| 3e82e36c455b2ac4e62f37f31856cfd0f119b809 |
|
05-Sep-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Unify ro_normal_checker method in FAFTSequence
We define a common used ro_normal_checker method in FAFTSequence. It
also checks the VbSharedData flags and active EC firmware for the
All-A/All-B/All-RO design on Chrome EC devices.
BUG=chromium-os:34147
TEST=Run the following tests:
$ run_remote_test.sh --remote=$IP RONormalBoot/control$
$ run_remote_test.sh --remote=$IP UpdateECBin/control$
$ run_remote_test.sh --remote=$IP ECWriteProtect/control$
Change-Id: Iee3104d0da1931aa21d256e0245eb706f4e080e1
Reviewed-on: https://gerrit.chromium.org/gerrit/32203
Reviewed-by: Mike Truty <truty@chromium.org>
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_ECWriteProtect/firmware_ECWriteProtect.py
|
| 38d4885a9bc1ecbc1dd4d2399c55ff8e9bb2949e |
|
28-Aug-2012 |
Vic Yang <victoryang@chromium.org> |
faft: Add a new test of EC write protect under software sync
This test starts with RO normal mode and enables EC write protect. Software sync
supposed to write protect the entire EC flash, so we expect the following
write protect flags:
- wp_gpio_asserted
- ro_at_boot
- ro_now
- all_now
These flags are checked under following situations:
- Cold reset. RO normal.
- Cold reset. Two stop.
- Cold reset by ectool. Two stop.
At the end of the test, write protect is deactivated and firmware is restored to
RO normal mode.
Signed-off-by: Vic Yang <victoryang@chromium.org>
BUG=chrome-os-partner:13229
TEST=Test passed on snow.
Change-Id: I821f8e6fe58702d94a09d8eb685e73fb17dfac29
Reviewed-on: https://gerrit.chromium.org/gerrit/31552
Commit-Ready: Vic Yang <victoryang@chromium.org>
Reviewed-by: Vic Yang <victoryang@chromium.org>
Tested-by: Vic Yang <victoryang@chromium.org>
/external/autotest/server/site_tests/firmware_ECWriteProtect/firmware_ECWriteProtect.py
|