| b18f084ff820ae06bdbc1f455b4dc35965c9f195 |
26-Jan-2016 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Change the spi_voltage config of Celes to pp3300
It makes flashrom able to detect the SPI flash on servo v3.
BUG=None
TEST=Manually call host.firmware_install() which sets the spi_voltage value.
Change-Id: I64ef50e3400cb5165f22aa12e6c412d869ccf22a
Reviewed-on: https://chromium-review.googlesource.com/323824
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
onfig/celes.py
|
| 932c89ed4c1b8a3890d159fdffa7df867f66cb8b |
26-Jan-2016 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Change the spi_voltage config of Benjo to pp3300
It makes flashrom able to detect the SPI flash on servo v3.
BUG=chrome-os-partner:49736
TEST=Manually call host.firmware_install() which sets the spi_voltage value.
Change-Id: I8dadc8c9d94bc577ae27a58e1cea4577b33b0881
Reviewed-on: https://chromium-review.googlesource.com/323822
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
onfig/banjo.py
|
| cd3babf90f4217ac273d81f437dfafbb60d64abf |
25-Jan-2016 |
Kaiyen Chang <kaiyen.chang@intel.com> |
Umaro: add FAFT config
BUG=chrome-os-partner:49576
TEST=none
Change-Id: I3c49e512da8d122b0ce77dbbc04f79361519dc48
Signed-off-by: Kaiyen Chang <kaiyen.chang@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/323328
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
onfig/umaro.py
|
| 32075c167a2d4252802645c46378b5d5bea91ae6 |
20-Jan-2016 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Record the RO firmware ID
It is common that the RO version is different with the RW version
once the lab FAFT only updates the RW portion. Better to record
both RW and RO firmware IDs.
BUG=chromium:555709
TEST=Ran a FAFT test and checked the following messages:
17:15:40 INFO | autoserv| System info:
17:15:40 INFO | autoserv| {'ec_version': 'lulu_v1.1.2323-8b1aa45',
17:15:40 INFO | autoserv| 'hwid': 'LULU D25-A2F-A4Q-Q5D',
17:15:40 INFO | autoserv| 'ro_fwid': 'Google_Lulu.6301.136.16',
17:15:40 INFO | autoserv| 'rw_fwid': 'Google_Lulu.6301.136.44',
17:15:40 INFO | autoserv| 'servod_version': 'servod 0.0.1-c76375e'}
Change-Id: I9ae9b8812cab9806f0eec6fe1eec1ecf3b642990
Reviewed-on: https://chromium-review.googlesource.com/322486
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
irmware_test.py
|
| 07a848f9faddc3302cf46e7d3238adcbabfaca6c |
13-Jan-2016 |
Scott <scollyer@chromium.org> |
faft: Modified Plankton class used for console/servo access
Previous version of /servo/plankton.py contained two similar Plankton
classes which served similar purposes. This was noted in CL314252 with
the statement that combining the two Plankton classes would be done
in a separate CL.
This change also includes changes to the two plankton based tests that
were built upon the original Plankton class. The tests themselves weren't
modified, however they are now built upon the combined plankton class
which means they also need to inherit the firwareTest class.
BRANCH=none
BUG=chrome-os-partner:49297
TEST=Manual
Connected Plankton to Samus and ran both tests to ensure that they
correctly accessed the servod methods that are required.
Change-Id: I8ada7cbadc1f3cf60ac1830c28e14e4c2e5cb7e0
Signed-off-by: Scott Collyer <scollyer@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/321403
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
irmware_test.py
|
| fc95aa4ffbb004acd91efb0819d7bb809e2a8ff8 |
09-Jan-2016 |
Keith Tzeng <keith.tzeng@quantatw.com> |
Sentry: Add faft config for Sentry
Inherit the Kunimitsu config.
BUG=chrome-os-partner:48950
TEST=none
Change-Id: Id1056e40876ea26a5a7dedb7aa9a96b5eb65c7c5
Reviewed-on: https://chromium-review.googlesource.com/321033
Commit-Ready: Keith Tzeng <keith.tzeng@quantatw.com>
Tested-by: Keith Tzeng <keith.tzeng@quantatw.com>
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
onfig/sentry.py
|
| 1a35aede1b323a4dd83371d140fd2cfc3868bfb2 |
05-Jan-2016 |
Duncan Laurie <dlaurie@chromium.org> |
glados/chell: Update FAFT configuration
The differences from samus continue to grow so change the config
for glados/chell to be a standalone config.
Some EC capabilities are changed:
"doubleboot" - this EC does a double boot due to pmic reset
"peci" - no PECI on this EC
"adc_ectemp" - no EC temp via ADC on this EC
"usb", "smart_usb_charge" - Glados and Chell EC have USB port power
control done by the board config and does not support the host commands.
BUG=chrome-os-partner:46117
TEST=pass FAFT on chell
Change-Id: I503aee6eb634fe7661f84fd4dd00475b142d12e7
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/321172
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/glados.py
|
| 94bc431637f401932a0d2d27e0be3842a08a84ac |
15-Dec-2015 |
Icarus Sparry <icarus.w.sparry@intel.com> |
autotest: firmware_ECBootTime race fix
Some systems run the EC code out of ram, rather than flash. There is a
new requirement that these system have their power cut to ensure that
the ram version of the read-only code is not tampered with. So these
systems do a double boot of the EC, once by themselves and once by
asking the PMIC to power cycle the EC.
The ECBootTime test asks the EC to do a "reboot ap-off" to reboot. It
then looks for the string "Inits done" on the EC console. It then sends
the command "powerbtn" to get the EC to boot the AP.
On systems which do this double boot the "Inits done" string is shown by
the first boot. The "powerbtn" may or may not be sent whilst the EC is
being power cycled by the PMIC, and hence it might be lost, leaving the
AP powered down. The rest of the test then times out and the test fails.
Using a string which is shown only in the second boot fixes the race
between the "powerbtn" command and the second boot.
It has the nice side effect of also making the measurement on "EC boot
time", which appears to want to measure the time between the "powerbtn"
command and the first spark of life of the AP, more accurate.
BRANCH=None
BUG=chrome-os-partner:48564
TEST=successfully run "test_that -b kunimitsu $IP firmware_ECBootTime"
Change-Id: I471074fd4f0168bb77191cf74e51f49db095fc8d
Signed-off-by: Icarus Sparry <icarus.w.sparry@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/318630
Commit-Ready: Icarus W Sparry <icarus.w.sparry@intel.com>
Tested-by: Icarus W Sparry <icarus.w.sparry@intel.com>
Tested-by: Naveenkrishna Ch <naveenkrishna.ch@intel.com>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
onfig/kunimitsu.py
|
| 17db75d231183c0983f2e9758bec704f40a356f2 |
25-Dec-2015 |
Anson Tseng <anson.tseng@intel.com> |
Setzer: Add FAFT config
BUG=None
BRANCH=master
TEST=None
Change-Id: I49a519c12f643864635b0ad8160a5ed86c857836
Signed-off-by: Anson Tseng <anson.tseng@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/319678
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/setzer.py
|
| fe06ed8afdd7323a1f3ee60c746b5c0335c659c0 |
06-Nov-2015 |
Scott <scollyer@chromium.org> |
faft: Add USB Type C PD infrastructure
Added support for Type C PD testing via the usbpd console. For case
where the usbpd console is the same as the ec console (glados, plankton, etc),
the usbpd conosle is assigned to be the same as the ec console.
Added changes to access both Plankton and a PD capable DUT (samus, glados, ..)
at the same time. The plankton servo host is only started if plankton servo
arguments are detected in the args section of the test script command line.
Inluded one example test PDConnect that disconnects then reconnects via
changing the dualrole setting, and verifies that a new PD contract is established.
BRANCH=none
BUG=chromium:561007
TEST=Manual
Tested both samus to plankton and glados to plankton cases using my own local machine.
Change-Id: Ic51173f02e9932f5c1d907288037bea54c8f1c3d
Signed-off-by: Scott Collyer <scollyer@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/314252
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
onfig/DEFAULTS.py
onfig/samus.py
irmware_test.py
|
| 11ba48fc6503a8e8ce72c85f53b3af593aa778d8 |
18-Dec-2015 |
Shelley Chen <shchen@chromium.org> |
FAFT: increasing wait for firmware screen on samus
Observing issue with many FAFT tests on samus where
the enter after a ctrl-D is not registered because
keystroke was issued before the recovery screen comes up.
BUG=none
BRANCH=none
TEST=Ran firmware_DevMode and firmware_RollbackFirmware
on samus
Change-Id: I3c05230ab9e94ddf248272d166468a20c1416f7b
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/319243
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
onfig/samus.py
|
| 895ea325b79047a2a534be8d3350dad56c275bcc |
07-Dec-2015 |
Naveen Krishna Chatradhi <naveenkrishna.ch@intel.com> |
autotest: config: modify overrides for kunimitsu
Previously the config values for Kunimitsu were copied from Samus.
Now they are a stand-alone set of overrides.
BRANCH=none
BUG=chrome-os-partner:43707
TEST=emerge-kunimitsu autotest; run faft suite on kunimitsu board.
Change-Id: Ide1a2f12fee0e35479b44a2ee7f3702f5b2b48e1
Signed-off-by: Naveen Krishna Chatradhi <naveenkrishna.ch@intel.com>
Signed-off-by: Icarus Sparry <icarus.w.sparry@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/316500
Commit-Ready: Naveenkrishna Ch <naveenkrishna.ch@intel.com>
Tested-by: Naveenkrishna Ch <naveenkrishna.ch@intel.com>
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/kunimitsu.py
|
| a7db9b5519c73ad922c8926ecb0c4d30a376dbfc |
05-Dec-2015 |
Danny Chan <dchan@google.com> |
Add power_action to run_shutdown_process to skip power_key presses.
- if pre_power_action is lid_open:yes, the subsequent power_key presses
will result in turning DUT off which will cause the last test in
firmware_FwScreenCloseLid to fail.
BUG=chrome-os-partner:48216
TEST=Run firmware_FwScreenCloseLid and firmware_FwScreenPressPower on link.
Change-Id: I2bf7fdb5049fa72d2ca5f18c1d254de7eadb0c12
Reviewed-on: https://chromium-review.googlesource.com/315776
Commit-Ready: danny chan <dchan@chromium.org>
Tested-by: danny chan <dchan@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
irmware_test.py
|
| f50217fda422cc6d6e4261e74dbc580a9281ee4c |
25-Nov-2015 |
Milton Chiang <milton.chiang@mediatek.com> |
Oak: Add FAFT config
BUG=None
TEST=test_that -b oak DUT_IP suite:faft_bios
Change-Id: I1a27b6ed0e7b39f5b7a2ec3f673043561bb313ab
Signed-off-by: Milton Chiang <milton.chiang@mediatek.com>
Reviewed-on: https://chromium-review.googlesource.com/313968
Tested-by: SJ Huang <sj.huang@mediatek.com>
Tested-by: YH Huang <yh.huang@mediatek.com>
Reviewed-by: SJ Huang <sj.huang@mediatek.com>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: YH Huang <yh.huang@mediatek.com>
onfig/oak.py
|
| b195ef32e2eb3f64515cf5f60d0ca487a8fd12f0 |
17-Nov-2015 |
Shawn Nematbakhsh <shawnn@google.com> |
glados: Increase boot-to-FW-screen delays
Glados can take slightly longer to boot to FW screens, so increase the
relevant delays.
BUG=chrome-os-partner:46969
BRANCH=None
TEST=Run FAFT on glados, verify that we never get stuck at the
mode-switch confirmation screen.
Change-Id: I27aa8645e4a205949a7ba4da96329077ab3daf96
Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/312833
Commit-Ready: Shawn N <shawnn@chromium.org>
Tested-by: Shawn N <shawnn@chromium.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
onfig/glados.py
|
| b745ebf71fe976442c0dd9191a63a47778b6952d |
16-Nov-2015 |
Daisuke Nojiri <dnojiri@chromium.org> |
increase default ping time out to 30 seconds
This change sets default ping time out to 30 seconds.
Boards in an early development stage may take longer to bring up the ethernet
port. This change saves those devices from failing in tests because
bypass_rec_mode hits esc+refresh+power prematurely.
According to the log posted to the referenced bug, the dut takes more than
20 seconds to bring up the eth0 port, thus causing FAFT to hit
esc+refresh+power to (mistakenly) bypass the new 'broken' screen.
BUG=chrome-os-partner:47469
BRANCH=tot
TEST=none
Change-Id: I91a615935b7d498b0f39f0b033a2d325f0bdee9d
Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/312754
Tested-by: Yidi Lin <yidi.lin@mediatek.com>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
onfig/DEFAULTS.py
|
| 567be413c29e0ed1e454caa7ca681bce57bd2f02 |
11-Nov-2015 |
Luke_Yin@asus.com <Luke_Yin@asus.com> |
Terra: Add FAFT config
BUG=chrome-os-partner:47134
TEST=None
Change-Id: Ic2da76545ffbd3798ea7b010e78922173ed29ccc
Signed-off-by: Luke_Yin@asus.com <Luke_Yin@asus.com>
Reviewed-on: https://chromium-review.googlesource.com/311934
Commit-Ready: Guang-Chuen Yin <Luke_Yin@asus.com>
Tested-by: Guang-Chuen Yin <Luke_Yin@asus.com>
Tested-by: Huki Huang <huki.huang@intel.com>
Reviewed-by: Kaiwen Gu <kaiwengu@chromium.org>
Reviewed-by: Huki Huang <huki.huang@intel.com>
onfig/terra.py
|
| 942b5ca334fa208a04c58aba65bd1963767011e6 |
11-Nov-2015 |
Kevin Cheng <kevin.cheng@intel.com> |
Edgar: Add FAFT config
BUG=chrome-os-partner:46825
TEST=none
Change-Id: I2193691c7cb9c3aa06f0bf94a7ef18286704b334
Reviewed-on: https://chromium-review.googlesource.com/312150
Commit-Ready: Kevin Cheng <kevin.cheng@intel.com>
Tested-by: Kevin Cheng <kevin.cheng@intel.com>
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
onfig/edgar.py
|
| cea96baa3a9ca9755088f1585dba94b266125083 |
06-Nov-2015 |
Danny Chan <dchan@google.com> |
Disble firmware_FwScreenPressPower for DUT without power button.
BUG=chromium-os-partner:44099
TEST=Execute on Mickey
Change-Id: Id321f81b82bc25f271ccd54a40bc8a8cb8961fd8
Reviewed-on: https://chromium-review.googlesource.com/310888
Commit-Ready: danny chan <dchan@chromium.org>
Tested-by: danny chan <dchan@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
onfig/DEFAULTS.py
onfig/mickey.py
|
| 0a15dbfc1d7a321e29486524569699b977a13380 |
05-Nov-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
Samus: Increase the time of servo_prog_state_delay
Sometime the current 5 seconds servo_prog_state_delay are not enough.
It causes flashrom failed due to ME's interference. Double its value
for safe.
BUG=chromium:534882
TEST=Running the following Python script on Samus.
import common
from autotest_lib.server.hosts import servo_host
sh = servo_host.create_servo_host(SAMUS_DUT_IP, {})
sh._servo.program_bios(FIRMWARE_PATH)
Change-Id: Id65b14287c55677e11ee4701548ae8dcd25366f3
Reviewed-on: https://chromium-review.googlesource.com/310876
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
onfig/samus.py
|
| b063ec05a427d566ac882f9620c84e614a7e6073 |
02-Nov-2015 |
Ryan Lin <ryan.lin@intel.com> |
GLaDOS/Chell: Add faft config
BUG=chrome-os-partner:46117
TEST=none
Change-Id: Ia31e81105b1897d988d62442616b6554391ca69b
Signed-off-by: Ryan Lin <ryan.lin@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/310182
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/chell.py
onfig/glados.py
|
| 76bed2f01aae6332e888faae6bc1f36dedb12de6 |
29-Oct-2015 |
Daisuke Nojiri <dnojiri@chromium.org> |
bypass broken screen after attempting to bypass insert screen
This patch integrates broken screen bypass code with insert screen bypass
code.
It means we first attempt to bypass the insert screen and waits for a
ping connection. If the dut is running on old firmware, it should boot and
respond to ping. If it doesn't, it implies the dut is running on the new
firmware and stuck at the broken screen. Then, we take the broken screen
bypass action.
This is needed for the boards which have to run on both tot firmware and
branched firmware.
BUG=chromium:501060,chrome-os-partner:46752
BRANCH=tot
TEST=test_that -b veyron_jerry suite:faft_bios
Change-Id: I5bccb57ace1511f49522849c5ab8c1a3cf99d54d
Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/309558
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
tils/mode_switcher.py
|
| c64702f8088571e9cf9877e8e775c69b95a02904 |
26-Oct-2015 |
Shelley Chen <shchen@chromium.org> |
FAFT: removing delay print statement
Print statement was inadvertently left in from
previous checkin. Removing it.
BUG=None
BRANCH=None
TEST=Ran FAFT test and didn't see output anymore.
Change-Id: I975712d873d6cae853cd05ce24664248088040f6
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/309027
Reviewed-by: danny chan <dchan@chromium.org>
irmware_test.py
|
| 57108980ee6107c9257d567a8d85388af33561a2 |
22-Oct-2015 |
Daisuke Nojiri <dnojiri@chromium.org> |
fix tests broken for revised recovery process
This introduces BrokenScreenBypasser, a class derived from
CtrlDBypasser, which can bypass the new 'broken' screen, and uses it to
fix tests broken because of the revised recovery process.
BUG=chromium:501060,chrome-os-partner:46752
BRANCH=tot
TEST=test_that -b veyron_jerry suite:faft_bios
Change-Id: I17b46440819c459e61ac51a6de465c8e30fea0a5
Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/308820
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
onfig/DEFAULTS.py
tils/mode_switcher.py
|
| 530490a25d656468ade45a4e165e683846ccd403 |
21-Oct-2015 |
Shelley Chen <shchen@chromium.org> |
FAFT: pulling wake* common code into firmware_test
Pulling delayed, wake_by_power_button,
wake_by_lid_switch, suspend_as_reboot into
firmware_test as it's common to both
firmware_DevModeStress and firmware_ECWakeSource.
Also increased WAKE_DELAY to 10, which is needed
for gnawty.
BUG=chromium:259640
BRANCH=none
TEST=tested on gnawty
Change-Id: Ib699f325b6d88980a1e028b770bcd0ea7febd166
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/307837
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
irmware_test.py
|
| c0781c4988c2ad6bd3b56be567f966ae3124661c |
05-Oct-2015 |
Shelley Chen <shchen@chromium.org> |
FAFT: Adding new test firmware_ECLidShutdown
This tests the functionality of the
GBB_FLAG_DISABLE_LID_SHUTDOWN flag.
BUG=chromium:446525
BRANCH=none
TEST=tested on veyron_jerry and samus
Change-Id: I06f8f654513212bdf129c981f9dab9f12c9c54d1
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/304190
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
irmware_test.py
|
| 58e5dd3b600081607d5ecb514d9bf3ebea83c533 |
17-Oct-2015 |
Roshan Pius <rpius@google.com> |
autotest: Create RpcServerTracker for Host objects.
Create a generic RpcServerTracker which can be used by any host object
to start and manage RPC server connections. The RPCServerTracker uses
the associated host object to start the required XML/JSON RPC server on the
DUT and forwards the port from the AutoTest Server to Brillo/Cros DUT.
This CL basically ports over most of the RPC server connection
management code from CrosHost into a separate class so that it can be
reused by AdbHost as well.
AdbHost modifies the |host.rpc_port_forward/disconnect| method to forward the
RPC connection from the AdbHost to Brillo DUT using 'adb forward'.
Related Change:
1. Add a |verbose| flag to the |host.run| method in AdbHost so that we can
reuse the |host.run_background| method already implemented by SshHost.
BUG=brillo:24338381
TEST=Ran network_WiFi_SimpleConnect.wifi_check11g on both dragonboard
and cros DUT.
`test_that $host --board=panther network_WiFi_SimpleConnect.wifi_check11g`
Change-Id: I7e44cbd5897871f01f320cb57377a28491571478
Reviewed-on: https://chromium-review.googlesource.com/307163
Commit-Ready: Roshan Pius <rpius@chromium.org>
Tested-by: Roshan Pius <rpius@chromium.org>
Reviewed-by: Roshan Pius <rpius@chromium.org>
pc_proxy.py
|
| 8fb6210e049848bf730f8743727c7419100376cc |
19-Oct-2015 |
Kaiyen Chang <kaiyen.chang@intel.com> |
Wizpig: add FAFT config
BUG=chrome-os-partner:42916
TEST=none
Change-Id: I3b3b2de628e19841051bae7b078d77acad54fb4b
Signed-off-by: Kaiyen Chang <kaiyen.chang@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/307040
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
onfig/wizpig.py
|
| d64f43423dd25e3e5a32e6562b5bf6fe3ad5a872 |
15-Oct-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Set the spi_voltage on veyron boards to a correct value
The spi_voltage on veryon boards should be pp3300.
BUG=chromium:534882
TEST=Called host.firmware_install() and checked it uses the correct value.
Change-Id: I72515fcdd2418a2c93108e8395bdf0d8e6741924
Reviewed-on: https://chromium-review.googlesource.com/306268
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
onfig/veyron.py
|
| f3e1bc436b527ff67b32ead82e08edddef4e3590 |
15-Oct-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Set a proper config name
When giving a platform with its family, like veyron_jerry, it
failed to find a proper config and falled back to the DEFAULT one.
This change is to fix this issue by removing the family name.
BUG=chromium:534882
TEST=Called host.firmware_install() and checked it uses a proper config.
Change-Id: I6218db0dfb3fcaae7c47590405fbd15447b1fd20
Reviewed-on: https://chromium-review.googlesource.com/306267
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
onfig/config.py
|
| e34a1ffc7fe3b2ccdae1ee1a51ba532dc4b71921 |
15-Oct-2015 |
Shelley Chen <shchen@chromium.org> |
FAFT: Setting correct voltage for Gnawty
Updating Gnawty config with correct voltage
values.
BUG=none
BRANCH=none
TEST=ran firmware_Mosys on Gnawty w/ servo3
(test uses flashrom to get platform values)
Change-Id: I5f125eb741d0a8fc4b57871925e256ced9bc835e
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/306171
Reviewed-by: danny chan <dchan@chromium.org>
onfig/gnawty.py
|
| 252a344987273b8fb608272e2a7cea172c7e6388 |
05-Oct-2015 |
Jack Lai <jack.lai@intel.com> |
FAFT: Update Buddy config
1.The config mode_switcher_type replaces keyboard_dev.
2.Add temperature detection for ec capability.
BUG=chrome-os-partner:42449
TEST=Run FAFT on Buddy
Change-Id: I97f8eec40eafe7b8ea91fba49b49558f656c8988
Signed-off-by: Jack Lai <jack.lai@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/303209
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/buddy.py
|
| 4fb817bad9a896f5d08265c1bcdcf197f248a42e |
13-Oct-2015 |
Shelley Chen <shchen@chromium.org> |
FAFT: Fixing conflict between crossystem/fwtool
Upon OS bootup, fwtool will run (through init)
and will access NVRAM. For FAFT testing, crossystem
will detect that the OS boots up (through adb devices)
and will also try to access NVRAM through crossystem.
Adding a 30 second delay at OS bootup to avoid this
conflict.
BUG=chrome-os-partner:46253
BRANCH=none
TEST=Ran suite:faft_dev_ryu
Change-Id: I4e382cc356e3c8ff5a72cab7bfa510b6a05ac653
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/305234
Reviewed-by: danny chan <dchan@chromium.org>
tils/mode_switcher.py
|
| a8d4a106f84f6a65750b7b20d55200ab9a57041f |
10-Oct-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
firmware_programmer: Set usbpd_reset to on during running flashrom
On Samus or other devices with USB PD, should make usbpd_reset to on
during running flashrom. Otherwise, the ME comes back on and tries to
write something to SPI flash that it might get confused.
Also add a FAFT config to define this wait time after changing the
servo state for programming, in order to ensure the ME turns off
gracefully.
BUG=chromium:538125
TEST=Running the following Python script:
import common
from autotest_lib.server.hosts import servo_host
sh = servo_host.create_servo_host(SAMUS_DUT_IP, {})
sh._servo.program_bios(FIRMWARE_PATH)
Change-Id: Ia4187c1589475b5113014c85d562f35d904344fc
Reviewed-on: https://chromium-review.googlesource.com/305230
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
onfig/DEFAULTS.py
onfig/samus.py
|
| b1a8601683815deaa44a912647534dbe1a37f643 |
25-Sep-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Reboot DUT after prioritize the kernel A/B
After prioritize ther kernel A/B, should reboot the DUT to make it
effective.
BUG=None
TEST=Made the kernel B boot and ran firmware_UpdateKernelVersion test.
Change-Id: I65b8e32fabfe6965e77b830d6ce792cb18da3a6d
Reviewed-on: https://chromium-review.googlesource.com/302452
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
irmware_test.py
|
| 6de388377cb690c70ad2e846b2c3c2bd516d41ef |
06-Oct-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Increase the firmware screen timing numbers on Sumo
The default firmware screen timing numbers are not enough and fails
the mode switching. This change increase them.
BUG=chrome-os-partner:44257
TEST=Ran firmware_DevMode and firmware_TPMExtend tests over 50 times each.
Change-Id: Ic4b0ef2f32c548a679de96a47a087c8573f372a2
Reviewed-on: https://chromium-review.googlesource.com/304277
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
onfig/sumo.py
|
| 57633521dfffd178525755ad0cb884d4956ad684 |
04-Sep-2015 |
Shelley Chen <shchen@chromium.org> |
FAFT: Ryu reboot into dev/normal mode
Implementing reboot into normal and dev modes on Ryu.
This involves the following steps:
- adb reboot bootloader (put machine into fastboot mode)
- fastboot oem un/lock
- push power button
- device will wipe for ~30 mins
- fastboot continue
BUG=chromium:527484
BRANCH=none
TEST=ran firmware_DevMode on Ryu
Change-Id: I653d27276e5b5d06e84bc2fc2801d71e2c44a330
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/297421
tils/mode_switcher.py
|
| 74709cb49125c3dc3abf0757770bdb556738f30c |
01-Oct-2015 |
david <david_wu@quantatw.com> |
Lars: Add faft config for Lars
Inherit the Kunimitsu config.
BUG=chrome-os-partner:45943
TEST=none
Change-Id: I5323dc092b6d271292cfd2a7cb02ce06103da141
Signed-off-by: David Wu <David_Wu@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/303258
Commit-Ready: David Wu <david_wu@quantatw.com>
Tested-by: David Wu <david_wu@quantatw.com>
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/lars.py
|
| 9a10b9bfa8a160ca306e8f4ad9666c555ab3f94b |
28-Sep-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Record the servod version
It is easier to tell what version the servod is running in order to
clarify if the servod is too old.
BUG=chromium:529504
TEST=Ran a FAFT test and checked the log and the resulted keyval file.
Change-Id: I9b555ae7360a5888b09d007b138633b1bd789498
Reviewed-on: https://chromium-review.googlesource.com/302673
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Todd Broch <tbroch@chromium.org>
irmware_test.py
|
| fef9adeb8ae56344c48f9f53c69395637f495197 |
23-Sep-2015 |
Bernie Thompson <bhthompson@chromium.org> |
FAFT: Braswell systems should inherit Strago
BUG=None
TEST=None
Change-Id: I797f566982d07b15ce1d6ade1a47410da4a02b83
Reviewed-on: https://chromium-review.googlesource.com/302407
Commit-Ready: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/celes.py
onfig/strago.py
onfig/ultima.py
|
| 04b4530b6f87a77df0dee8beafd00734fe117cfa |
23-Sep-2015 |
JaniceLi <Janice.Li@quantatw.com> |
Reks: Add FAFT config for reks
BUG=chrome-os-partner:45562
TEST=None
Change-Id: I052f79acfaa8ff8b11c6fc22783f7d9e612f1920
Reviewed-on: https://chromium-review.googlesource.com/301850
Commit-Ready: Keith Tzeng <keith.tzeng@quantatw.com>
Tested-by: Keith Tzeng <keith.tzeng@quantatw.com>
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/reks.py
|
| 060bd1c9709d8ea9ec53974b58be33c44a16e416 |
22-Sep-2015 |
smile chen <smile_chen@wistron.com> |
buddy:Removed 'smart_usb_charge' from the ec capability.
Modify buddy.py ec_capability = ['x86' , 'usb']
BUG=chrome-os-partner:45119
BRANCH=none
TEST=Confirm test item of EC "firmware_ECUsbPorts" is pass.
Change-Id: I2e1dfe8bb299edf55a366dab858f520d95499f5f
Signed-off-by: smile chen <smile_chen@wistron.com>
Reviewed-on: https://chromium-review.googlesource.com/300844
Commit-Ready: Smile Chen <SMILE_CHEN@WISTRON.COM>
Tested-by: Smile Chen <SMILE_CHEN@WISTRON.COM>
Reviewed-by: Mohammed Habibulla <moch@google.com>
Reviewed-by: Jack Lai <jack.lai@intel.com>
onfig/buddy.py
|
| c2fe654413c3f007c8d20d26f5714d32b33df992 |
17-Sep-2015 |
Suresh Rajashekara <sureshraj@chromium.org> |
Arkham: Add initial FAFT config
BUG=chrome-os-partner:34513
BRANCH=none
TEST="test_that --board=arkham 100.96.48.117 f:.*firmware_FAFTSetup/control"
Change-Id: Icf6ac88c917237049ad31ae221ee6acebad12ae3
Signed-off-by: Suresh Rajashekara <sureshraj@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/300550
Reviewed-by: danny chan <dchan@chromium.org>
onfig/arkham.py
|
| c620bb7a9a49a9ac4a2147a4f71d46186feb586d |
14-Sep-2015 |
David Hendricks <dhendrix@chromium.org> |
veyron_brain: Increase powerup_ready to 15 seconds
Shutting down can take a long time. The workaround is to increase
powerup_ready time so that firmware_ConsecutiveBoot does not attempt
to power the system back on too early.
BUG=chrome-os-partner:45309
BRANCH=firmware-veyron
TEST=firmware_ConsecutiveBoot passes more reliably.
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Change-Id: I6789528f65f23d4d47c899d9e7e5cc979343266e
Reviewed-on: https://chromium-review.googlesource.com/299551
onfig/brain.py
|
| fc0c77097ba960aa1e2a6388770fea905ab0d4a7 |
11-Sep-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Simplify reading/modifying GBB flags
The original code reads the GBB flags multiple time. Reading GBB
flags is slow on embedded devices. This change reduces the number
of reads.
BUG=None
TEST=Ran a FAFT test to exercise the change.
Change-Id: Ib8ec6c9db8ef83fa5e60fb18073fafcaf10cf269
Reviewed-on: https://chromium-review.googlesource.com/299390
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
irmware_test.py
|
| e01cc1289c9fac5b979950068a0fd931bde9c4fd |
26-Aug-2015 |
Naveen Krishna Chatradhi <naveenkrishna.ch@intel.com> |
Kunimitsu: Add FAFT config for Kunimitsu
This based on Samus values
BRANCH=none
BUG=chrome-os-partner:43707
TEST=emerge-kunimitsu autotest and run FAFT
Change-Id: I4fb058eeec7e9e544a099be3534bfa504427aecc
Signed-off-by: Naveen Krishna Chatradhi <naveenkrishna.ch@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/295893
Commit-Ready: Naveenkrishna Ch <naveenkrishna.ch@intel.com>
Tested-by: Naveenkrishna Ch <naveenkrishna.ch@intel.com>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
onfig/kunimitsu.py
|
| d0cbb6651494fc15f407d7ac1e5d089c38e207b8 |
10-Sep-2015 |
Danny Chan <dchan@google.com> |
Change default wait timeout.
- change wait time form default 180 to 60 for all control
- wait 10 seconds instead of 5 before pressing power switch.
BUG=None
TEST=None
Change-Id: Id96f47efecf820698d29368076db9a51a7d9fbad
Reviewed-on: https://chromium-review.googlesource.com/298159
Commit-Ready: danny chan <dchan@chromium.org>
Tested-by: danny chan <dchan@chromium.org>
Reviewed-by: Kalin Stoyanov <kalin@chromium.org>
onfig/DEFAULTS.py
|
| 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>
tils/faft_checkers.py
|
| 46ebbb1ee25320a2fe6330edb13a062eec7ef7bb |
28-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Support new GBB flags
The new GBB flag GBB_FLAG_FORCE_DEV_BOOT_FASTBOOT_FULL_CAP is new added.
It is default ON and FAFT should disable it at the beginning.
BUG=chromium:527484
TEST=Ran a FAFT test.
Change-Id: I12ab5ce61bf01e7045a46dc26da0c4c18fffa5a0
Reviewed-on: https://chromium-review.googlesource.com/295896
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
irmware_test.py
|
| 3dbc70ac3c58465b4c35b5d09ab10d0e28abde7f |
20-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Implement basic methods of ModeSwitcher for Ryu
This ModeSwitcher does some basic methods, like waiting DUT online/offline.
More changes will be added to support the rest.
BUG=chromium:527484
TEST=Ran some FAFT tests on Ryu.
Change-Id: I085ae9ed9c8fec5b773e3f9c6d6506bc008de5ba
Reviewed-on: https://chromium-review.googlesource.com/294774
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
tils/mode_switcher.py
|
| d92648a934493bc050cd2789b8bbe051426929aa |
25-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Add Ryu FAFT config
Add Ryu FAFT config file.
BUG=chromium:527484
TEST=None, this config will be used later.
Change-Id: I60c722701d9e3980ad1020320f586b7168025e35
Reviewed-on: https://chromium-review.googlesource.com/295567
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
onfig/ryu.py
|
| 2e3db4a5e9179d2a4f8f01b885884bf64b664646 |
27-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Don't restore the GBB flags for speed-up
Setting up and restoring the GBB flags take a lot of time. For
speed-up purpose, don't restore it.
BUG=None
TEST=Ran a FAFT test to verify nothing broken.
Change-Id: I142d43121c7779d949a730b8efc2c3761b9b728f
Reviewed-on: https://chromium-review.googlesource.com/295771
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
irmware_test.py
|
| 0d2b8931ea8b186225e76c545c257859ae1f43bf |
27-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Modify the GBB flags directly on the image
Don't call the set_gbb_flags script which may not exists on all
boards. Modify the GBB flags directly on the raw firmware image.
BUG=chromium:527484
TEST=Ran a FAFT test to verify the GBB flags changed.
Change-Id: Ibf6aef9ce19e17b2d132c75c0bb5ea5b762d87bb
Reviewed-on: https://chromium-review.googlesource.com/295770
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
irmware_test.py
|
| 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>
irmware_test.py
tils/mode_switcher.py
|
| 0c0181d41467e3b6ab725ff4a2870eb53ab85a79 |
19-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Unify wait_for_kernel_up to wait_for_client
These two methods are similar and would be easily confused. Unify
them into one.
BUG=chrome-os-partner:39744
TEST=Ran some of the effected FAFT tests.
Change-Id: Ic3318db780c5b6fd5d9f9f18c468b2063805e7e3
Reviewed-on: https://chromium-review.googlesource.com/294772
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
irmware_test.py
tils/mode_switcher.py
|
| e1d5e66392a398106a5a384a2fa31b177c07b9cc |
25-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Remove backup directory which is no longer used
This backup directory is created tempoarily to store the firmware
image. After sending the file to server, the directory is no longer
used and should be removed.
BUG=None
TEST=Ran a FAFT test, verified the backup directory was removed.
Change-Id: I3a1007a7d32cf92f415a6dd221e0492e4b7911be
Reviewed-on: https://chromium-review.googlesource.com/295566
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
irmware_test.py
|
| 91faa0fe02ac7306ca12701c302310b1ffb4f3e4 |
22-Aug-2015 |
David Hendricks <dhendrix@chromium.org> |
veyron_brain: Increase hold_pwr_button_poweroff time
Non-laptop Veyrons need to hold the power button for a time
determined by the RK808 PMIC (PWRON_LP_OFF_TIME) which is
6 seconds by default. We'll define hold_pwr_button_poweroff
as 7 seconds to give some margin.
BUG=chrome-os-partner:44275
BRANCH=firmware-veyron
TEST=FAFT runs on veyron_mickey now.
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Change-Id: I5b91414bfe126fb5cd7101147d027d998cc9c7a2
Reviewed-on: https://chromium-review.googlesource.com/295188
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
Commit-Queue: David Hendricks <dhendrix@chromium.org>
onfig/brain.py
|
| a88f8b671f52768245b17e3f91973874ec22d790 |
21-Aug-2015 |
David Hendricks <dhendrix@chromium.org> |
veyron_brain: Define custom hold_pwr_button_poweron
The RK808 has a long power button debounce time. Consequently
non-laptop Veyrons need to use a longer power button hold time
than the default SHORT_DELAY.
BUG=chrome-os-partner:44275
BRANCH=firmware-veyron
TEST=firmware_ConsecutiveBoot passes on veyron_mickey now
Change-Id: I2cddb6353bb17121326b2e2b0f06361eb6078673
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/295187
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
onfig/brain.py
|
| 25d703a846f3a717dd8a65997aee0ddfd6afe440 |
21-Aug-2015 |
David Hendricks <dhendrix@chromium.org> |
FAFT: Use power_key() where appropriate to power on DUT
Some platforms need a longer power button press than others when
turning on. This is particularly true for platforms that do not
have an EC since the EC will hold the power on signal for the host/AP
for as long as needed (which may exceed the SHORT_DELAY used by
power_short_press()). Platforms without an EC need to be able to
define their own power on hold time.
This patch does a few small things to address that:
- Add hold_pwr_button_poweron in FAFT config to be used as the power
button hold time.
- Rename hold_pwr_button to hold_pwr_button_poweroff to be more
explicit about its usage.
- In cases where an EC is not used, replace power_short_press() with
power_key() and pass hold_pwr_button_poweron as its argument.
BUG=chrome-os-partner:44275
BRANCH=firmware-veyron
TEST=firmware_ConsecutiveBoot now passes on mickey (with follow-up
patch to define hold_pwr_button_poweron)
Change-Id: Ie26f254f0cde0ef083f5db3caf51b2c85b622a77
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/295186
onfig/DEFAULTS.py
irmware_test.py
|
| e6adca4984389bc6fd46f7e5d7a45aec43f884fd |
13-Aug-2015 |
Julius Werner <jwerner@chromium.org> |
faft: Fix lsb-release check for test image
We've been checking for test images in the CHROMEOS_RELEASE_DESCRIPTION
field, which is not actually the correct way to do it (official images
just always contain the word "test" there for no apparent reason, even
if they're actually dev or base images).
This patch makes it check CHROMEOS_RELEASE_TRACK instead which seems to
be consistent on both official and developer-built images for this.
BUG=chromium:519889
TEST=None
Change-Id: I9a83c796e3394bc6ec2a008776eb8bb8ef296739
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/293337
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
irmware_test.py
|
| 059ba41ff293544e05740019ce0d7d19c6ee08e4 |
13-Aug-2015 |
Keith Tzeng <keith.tzeng@quantatw.com> |
Ultima: Add FAFT config for ultima
BUG=chrome-os-partner:43821
TEST=None
Change-Id: Ic40989e53ef06259aa13ce4eb5902deb7c1985c0
Reviewed-on: https://chromium-review.googlesource.com/293098
Reviewed-by: Shawn N <shawnn@chromium.org>
Commit-Queue: Keith Tzeng <keith.tzeng@quantatw.com>
Tested-by: Keith Tzeng <keith.tzeng@quantatw.com>
onfig/ultima.py
|
| f49e4f7dba36cf7162130058b340f21245bcd4dc |
05-Jun-2015 |
jiazi Yang <Tomato_Yang@asus.com> |
mickey: Add board mickey config
Add mickey.py base on brain(without EC)
BUG=chrome-os-partner:41077
BRANCH=veyron
TEST=ran firmware_ECPowerButton test on mickey,
passed with the message "TEST_NA: Nothing needs
to be tested on this device"
Change-Id: I3da31b68119fa306824853144b7e469aeead3aac
Signed-off-by: jiazi Yang <Tomato_Yang@asus.com>
Reviewed-on: https://chromium-review.googlesource.com/275441
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Julius Werner <jwerner@chromium.org>
onfig/mickey.py
|
| 292b75579500333e12bc916560e7f60ac5bb8df3 |
13-Jul-2015 |
Jack Lai <jack.lai@intel.com> |
Buddy: Add faft config for Buddy
BUG=chrome-os-partner:41544
TEST=Test firmware_FAFTSetup on Buddy
Change-Id: I5ce652d5c86426cf2bba50d6d3fd4374dbc7b655
Signed-off-by: Jack Lai <jack.lai@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/284961
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/buddy.py
|
| e5dfee960cfcf5a24845150a87945ef14e88441c |
29-Jul-2015 |
David Huang <David.Huang@quantatw.com> |
Gandof: Add smart_usb_charge for gandof support smart_usb_charge
BUG=chrome-os-partner:43175
TEST=Ran FAFT on gandof
Change-Id: Ibda258534aaaa3f772638c1aa45934f9f9528732
Signed-off-by: David Huang <David.Huang@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/289071
Reviewed-by: Shawn N <shawnn@chromium.org>
Tested-by: David Wu <david_wu@quantatw.com>
Commit-Queue: David Wu <david_wu@quantatw.com>
onfig/gandof.py
|
| a6cf37ea6d933407c391239bc60b2e489e52dd49 |
30-Jun-2015 |
Icarus Sparry <icarus.w.sparry@intel.com> |
Increase time before inserting USB drive
Some FAFT tests enter recovery mode via crossystem,
and these require a longer delay to remove and insert
the media
BUG=chrome-os-partner:41647
TEST="test_that -b cyan $IP firmware_UserRequestRecovery" passes
Change-Id: I6b145bfaca7fdd0acb7040970e854e31949f18de
Signed-off-by: Icarus Sparry <icarus.w.sparry@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/282393
Reviewed-by: danny chan <dchan@chromium.org>
onfig/cyan.py
|
| 71eef0d90fb052444abee5249419a19068d70e47 |
28-Jul-2015 |
Danny Chan <dchan@google.com> |
Make consecutive reboot more reliable.
- Make default wait up time from 180s to 60s.
- Retry power button press in the even that the device is slow on
shutdown and not able to register the power button press event.
- Decrease power up wait time from 10s to 5s to reduct 5k reboot test
time by 6 hours.
Change-Id: I46ee9b9553ad699ac449e34234bc49680ab208ac
Reviewed-on: https://chromium-review.googlesource.com/289215
Tested-by: danny chan <dchan@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: danny chan <dchan@chromium.org>
onfig/DEFAULTS.py
|
| 5cd5bdf6dca5283b6dd8fe09b200c3ae84dc4fb3 |
21-Jul-2015 |
Anson Tseng <anson.tseng@intel.com> |
Celes: Add FAFT config for Celes
BUG=chrome-os-partner:42787
TEST=None
Change-Id: Ib5f15f84514e5f6576e25be3941f62db108ba418
Signed-off-by: Anson Tseng <anson.tseng@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/286971
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/celes.py
|
| d2bef8464097494fa2dc93483e42ed3f774aa418 |
22-Jul-2015 |
Kumar, Gomathi <gomathi.kumar@intel.com> |
[autotest] : Add config file for strago
BUG=chrome-os-partner:43060
TEST=Ran FAFT on strago
Change-Id: I97059815139d1d637720bbaa9d76e58f1ec50e11
Signed-off-by: Kumar, Gomathi <gomathi.kumar@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/287496
Reviewed-by: Icarus W Sparry <icarus.w.sparry@intel.com>
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/strago.py
|
| 63920b7de6db11c656795822bf771c8de8d17d65 |
01-Jul-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Increase timeout of waiting DUT sshable to 3 minutes
Jetsteam devices take longer time than others to initialize network interfaces
and start sshd. Increase the timeout to 3 minutes to solve this issue. It
doesn't affect other devices on normal test cases.
BUG=chrome-os-partner:34513
TEST=Ran firmware_DevMode on Whirlwind passed.
Change-Id: Ibe5b3a36ccd29046ca2f3c4caab07e5767a99579
Reviewed-on: https://chromium-review.googlesource.com/283130
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Wai-Hong Tam <waihong@chromium.org>
irmware_test.py
|
| 18c4e1643b3ac6f6a201e2008020cdae8c590a7d |
07-Jul-2015 |
Julius Werner <jwerner@chromium.org> |
faft: Reset TPM from test image, remove install shim logic
Since it's now possible to clear the TPM from a normal test image booted
in recovery mode, there is no more need to have an extra factory install
shim at hand. This patch removes all FAFT code related to install shims
and instead adds a reboot_and_reset_tpm() function that can be used with
the same normal test image that most faft_lv3 tests require.
BUG=None
TEST=Ran affected tests on Jerry.
Change-Id: I594dcd84080f0c5999188ff796f7dce149338212
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/283973
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/DEFAULTS.py
irmware_test.py
|
| ecd1f1e976ee9b069c8ee6c3904ed9dcc5e86e92 |
22-Jun-2015 |
David Hendricks <dhendrix@chromium.org> |
veyron: Rejigger FAFT configs for EC/non-EC devices
This factors out common Veyron config settings into veyron.py and
creates pinky.py and brain.py as reference configurations for EC
vs. non-EC devices. Existing Chromebooks will inherit settings from
pinky.py and other devices will inherit from brain.py.
BUG=none
BRANCH=veyron
TEST=ran firmware_ECPowerButton test on Speedy successfully, and
on Brain it erred out with the message "TEST_NA: Nothing needs to
be tested on this device"
Change-Id: I123e8508f7c80bea99a1039e4cc39188345c9c63
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/281023
Reviewed-by: Julius Werner <jwerner@chromium.org>
onfig/brain.py
onfig/gus.py
onfig/jaq.py
onfig/jerry.py
onfig/mighty.py
onfig/minnie.py
onfig/pinky.py
onfig/speedy.py
onfig/thea.py
onfig/veyron.py
|
| 2ce67609d476299dd19eceeb126da5ab51bcbfd9 |
12-Jun-2015 |
Bennett Chan <bennett.chan@intel.com> |
Add Cyan FAFT config
BUG=chrome-os-partner:40686
TEST=Run FAFT
Change-Id: I5fc3214037eef058d6dd9f4b10ead840ba905a0e
Signed-off-by: Bennett Chan <bennett.chan@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/277360
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Reviewed-by: Icarus W Sparry <icarus.w.sparry@intel.com>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
onfig/cyan.py
|
| 5fc040957b1a9fafd1f94a8e755b7f76f0d6c8c4 |
13-Jun-2015 |
Kaiyen Chang <kaiyen.chang@intel.com> |
Heli: add faft config for heli
BUG=chrome-os-partner:41289
TEST=none
Change-Id: I5e8b78b6dad40de3dad895b384bf03bf3b5f9c77
Signed-off-by: Kaiyen Chang <kaiyen.chang@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/277375
Reviewed-by: Marc Jones <marc.jones@se-eng.com>
onfig/heli.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>
onfig/DEFAULTS.py
onfig/alex.py
onfig/jecht.py
onfig/jetstream.py
onfig/lumpy.py
onfig/monroe.py
onfig/ninja.py
onfig/panther.py
onfig/stumpy.py
onfig/sumo.py
onfig/zako.py
onfig/zgb.py
tils/faft_checkers.py
|
| f9ded098bc87317cc0058823894f4bc4914cb9b9 |
19-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Implement Jetstream ModeSwitcher logic
This change adds the Jetstream ModeSwitcher implementation and
uses the new jetstream FAFT config as parent.
BUG=chrome-os-partner:16231,chrome-os-partner:39744
TEST=Ran suite:faft_lv1 and suite:faft_lv2 on Whirlwind. Some tests
failed and will be fixed by some future CLs.
Change-Id: I23c71ba86889a132cb54c7be169b0c9010880052
Reviewed-on: https://chromium-review.googlesource.com/272432
Tested-by: Tom Tam <waihong@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
onfig/jetstream.py
onfig/storm.py
onfig/whirlwind.py
tils/mode_switcher.py
|
| ed4d67be4d0faa1a267d33e86905df1153d78333 |
19-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Create ModeSwitcher and FwBypasser according to FAFT config
Two new FAFT configs are added:
- mode_switcher_type: either 'physical_button_switcher' or
'keyboard_dev_switcher',
- fw_bypasser_type: so far only 'ctrl_d_bypasser'
FAFT checks these configs to create proper ModeSwitcher and FwBypasser.
BUG=chrome-os-partner:39744
TEST=Ran suites faft_lv1 and faft_lv2 on Samus.
Change-Id: I6a93dc6729aec571e4fc5a0e0a4468eadcbfa771
Reviewed-on: https://chromium-review.googlesource.com/272304
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Tom Tam <waihong@google.com>
Commit-Queue: Tom Tam <waihong@google.com>
onfig/DEFAULTS.py
onfig/alex.py
onfig/lumpy.py
onfig/stumpy.py
onfig/zgb.py
irmware_test.py
tils/mode_switcher.py
|
| 5c093f03bd1275a70fc878e75c382842d4261307 |
20-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Always unplug USB before booting and plug it on firmware screen
The original test logic is to verify the legacy recovery mode behavior:
- if dev_mode ON, directly boot to USB stick if presented;
- if dev_mode OFF,
- the old models need users to remove and insert the USB;
- the new models directly boot to the USB.
Always unplugging USB before booting does not verify this legacy behavior
but it simplifies the test logic.
BUG=chrome-os-partner:16231
TEST=Ran firmware_RecoveryButton on Samus.
Change-Id: Ifeff59acdff78262240978ede9b4dd736a4802af
Reviewed-on: https://chromium-review.googlesource.com/272303
Tested-by: Tom Tam <waihong@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
tils/mode_switcher.py
|
| b0314a0ab7b590cb0b25b80513673eb157f7b5e9 |
19-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Fix FAFT config between_usb_plug -> usb_plug
A previous CL forgot to change this config.
BUG=chrome-os-partner:16231
TEST=Ran firmware_SelfSignedBoot on Samus
Change-Id: I4caa5c364a2733135e768114e9699e8872b3aa74
Reviewed-on: https://chromium-review.googlesource.com/272302
Tested-by: Tom Tam <waihong@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
irmware_test.py
|
| 004a8cd96f2c9bc228ca9d58428e88d36fc36307 |
19-May-2015 |
Christopher Wiley <wiley@chromium.org> |
Remove reference to local_dash from firmware_test.py
This tool is being deprecated.
BUG=brillo:1067
TEST=None
Change-Id: Ia0d65ba1b749f798a0ecf24d80cee4ad07effecf
Reviewed-on: https://chromium-review.googlesource.com/272215
Tested-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
irmware_test.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>
onfig/DEFAULTS.py
onfig/link.py
onfig/nyan.py
onfig/parrot.py
onfig/rambi.py
irmware_test.py
tils/mode_switcher.py
|
| 3dea40e52bc58e7b19b890e2e17b3a4816227c1f |
13-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Simplify Alex/ZGB flow which needs a transition state to enter dev mode
Treats this special case in a new FAFT config: need_dev_transition.
BUG=chrome-os-partner:16231
TEST=None, new devices don't use this logic.
Change-Id: Iff9dbe644f09dd3fe5bf6c2e05d2a2c513db3e82
Reviewed-on: https://chromium-review.googlesource.com/271281
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>
onfig/DEFAULTS.py
onfig/alex.py
onfig/zgb.py
irmware_test.py
|
| 93b5c096a0247ed3be70f16fb4b5e4d4866953e5 |
13-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Call servo to toggle recovery switch
Don't directly set the servo fields. Call the servo layer to toggle
recovery switch. And also remove the out-dated hold_cold_reset config.
BUG=chrome-os-partner:16231
TEST=Ran firmware_DevMode on Samus.
Change-Id: I88b945cdfc037c08b6615169806e53ed846fcdc9
Reviewed-on: https://chromium-review.googlesource.com/270765
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>
onfig/DEFAULTS.py
tils/mode_switcher.py
|
| 651dbf7acb7e698f4969aa2171c5a9c89c619c15 |
13-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Eliminate the board variant of handling broken_rec_mode
This change refines the logic of switching from dev mode to normal mode,
and uses the power state controller to handle the board variant of
recovery button.
BUG=chrome-os-partner:16231
TEST=Ran firmware_DevMode on Samus.
Change-Id: I06a06507e95b61ff4eaf39cf3b2b37a80a4ccc5d
Reviewed-on: https://chromium-review.googlesource.com/270764
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>
onfig/DEFAULTS.py
onfig/stout.py
tils/mode_switcher.py
|
| d7a0d05665faa4ee5621b906efeb6e718b9ed1a8 |
13-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Unify ModeSwitcher APIs to support sync_before_boot
This change refines the time of calling sync_before_boot() to the entries
of main APIs. It helps some later refactoring.
BUG=chrome-os-partner:16231
TEST=Ran the affected tests, e.g. firmware_TPMExtend, firmware_EventLog,
firmware_RecoveryButton, firmware_DevMode, etc.
Change-Id: I0705bf7c01ae2e8bd94e64b1f6b0ab84ab36f790
Reviewed-on: https://chromium-review.googlesource.com/270763
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>
irmware_test.py
tils/mode_switcher.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>
tils/faft_checkers.py
tils/mode_switcher.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>
irmware_test.py
pc_proxy.py
tils/mode_switcher.py
|
| 34a7703cb939660adc2ae8beb2144ced17b6dedc |
07-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Encapsulte the firmware screen skipping logic in ModeSwitcher
For encapsulating the behavior of skipping firmware screen, e.g.
requiring unplug and plug USB, the variants should not be hard-
coded in tests. We keep this logic in the mode_aware_reboot method
of ModeSwitcher.
BUG=chrome-os-partner:16231
TEST=Ran the affected FAFT tests, firmware_CorruptBothFwBodyAB,
firmware_CorruptBothFwSigAB, firmware_CorruptBothKernelAB,
firmware_RollbackFirmware, and firmware_RollbackKernel on Jerry.
Change-Id: Ifefe2ffe7b4b642383970e82ee3823f19700f15e
Reviewed-on: https://chromium-review.googlesource.com/270015
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
tils/mode_switcher.py
|
| 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>
irmware_test.py
tils/mode_switcher.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>
irmware_test.py
|
| a704f184b788093ddbde169f7120607af84271f7 |
06-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Introduce mode_aware_reboot to unify all reboot methods
We try to unify all the reboot methods in FAFT to this single one
method: mode_award_reboot. This is the first change of this work.
It removes sync_and_warm_reboot and sync_and_cold_reboot from FAFT
framework and use the new mode_award_reboot instead.
BUG=chrome-os-partner:16231
TEST=Ran some of the affected FAFT tests on Jerry.
Change-Id: I0c389f8dc50fb914390fdf930989553c45f00b23
Reviewed-on: https://chromium-review.googlesource.com/269763
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: Tom Tam <waihong@google.com>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
irmware_test.py
tils/mode_switcher.py
|
| 854be2c1ff224aa97532118f561377c21ac68c2c |
04-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: parrot: Remove the hack that fixes reboot issue when entering dev mode
The issue (http:crosbug.com/p/16231), i.e. Parrot not rebooting after
entering dev mode when Servo connected, was fixed. So no longer needs
this hack.
BUG=chrome-os-partner:16231
TEST=None
Change-Id: I540d779242ec53a3d9480f6544d9bc247f7e5eb4
Reviewed-on: https://chromium-review.googlesource.com/268843
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
tils/mode_switcher.py
|
| b43a9a5c0273d51053cd54d12d5c368f2da74d2f |
04-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Deprecate the broken_warm_reset FAFT config
There are 3 boards using this broken_warm_reset FAFT config to work
around the warm reset problem. Parrot fix is moved to servod, check:
https://chromium-review.googlesource.com/269138
Butterfly and Stout are not supported currently. If we add support of
them, the changes will go the servod, not FAFT.
So it is safe to deprecate the broken_warm_reset FAFT config.
BUG=chrome-os-partner:39744
TEST=None
CQ-DEPEND=CL:269138
Change-Id: Ib48056dccb1506140aba8d16a0a1c05fb0ed1810
Reviewed-on: https://chromium-review.googlesource.com/269139
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
onfig/DEFAULTS.py
onfig/butterfly.py
onfig/parrot.py
onfig/stout.py
irmware_test.py
|
| da6c6ba556ebb2b810dd7450860609d6725afb1d |
01-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Support waiting DUT online after mode switching
A new argument wait_for_dut_up added to reboot_to_mode method. If
wait_for_dut_up=True, wait DUT online again. If wait_for_dut_up=False,
do the reboot and mode switching sequence only and may need more
operations to pass the firmware screen.
Also change most of the tests to use the default wait_for_dut_up=True
way, it helps porting these tests to different mode switching
implementations, like using dev and rec buttons.
BUG=chrome-os-partner:39744
TEST=Ran the affected test cases, like firmware_DevMode,
firmware_RecoveryButton, firmware_SelfSignedBoot, etc.
Change-Id: I723d43efe65e731d8a26b94822c094a9de8e8f11
Reviewed-on: https://chromium-review.googlesource.com/268859
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
irmware_test.py
tils/mode_switcher.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>
irmware_test.py
tils/faft_checkers.py
tils/mode_switcher.py
|
| 21709ce6a4facca585f4570943c18b7cf550c6c4 |
04-May-2015 |
Keith Tzeng <keith.tzeng@quantatw.com> |
faft_config: Add Orco board config
Copy from enguarde and rename the string.
BUG=chrome-os-partner:39186
TEST=None
BRANCH=None
Change-Id: I3c99238cec4e5c2d69f2c09dd260ce720289dcbc
Reviewed-on: https://chromium-review.googlesource.com/268941
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Keith Tzeng <keith.tzeng@quantatw.com>
Tested-by: Keith Tzeng <keith.tzeng@quantatw.com>
onfig/orco.py
|
| f2de4debd08a4825542fd4fd848ccd6b4fb000f8 |
01-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Implement the ModeSwitcher class
This is the first change of the ModeSwitcher refactoring. It
introduces a new class ModeSwitcher to do normal, dev, and rec
mode switching sequence. The triggering logic mostly keeps the
same or does a minor modification from the original one.
BUG=chrome-os-partner:39744
TEST=Ran firmware_DevMode and firmware_RecoveryButton on Jerry.
These two tests cover major changes on switching to normal, dev,
and rec modes.
Change-Id: I96b435c6df7a9f4c80aaab5d1fa4a062aa7699bf
Reviewed-on: https://chromium-review.googlesource.com/268794
Tested-by: Tom Tam <waihong@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
irmware_test.py
tils/mode_switcher.py
|
| 408c995796074681102313315b4ee6726a6b5392 |
29-Apr-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Remove Ctrl-U logic and eliminate press_key methods from FAFT framework
Once servo supports simluating all the key combinations in
https://chromium-review.googlesource.com/#/c/267813/
, the special Ctrl-U logic is no longer needed. As a result, the
press_key methods in FAFT framework layer can be eliminated.
Tests now call the servo key simlution methods directly, like other
non-FAFT tests.
BUG=chrome-os-partner:39653
CQ-DEPEND=CL:267813
TEST=Deploy the above change to servod. Run the affected tests, e.g.
firmware_DevMode,
firmware_DevBootUSB,
firmware_DevScreenTimeout,
firmware_SelfSignedBoot, and
firmware_SoftwareSync.
Change-Id: Ib0af6ac85a518cc508ab33cb072f816c057a6cc2
Reviewed-on: https://chromium-review.googlesource.com/268312
Tested-by: Tom Tam <waihong@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
irmware_test.py
|
| e1518fd21b45e86378c033c22d50639d7c275401 |
24-Apr-2015 |
ChromeOS Developer <Tim-Chen@quantatw.com> |
faft_config: Add Thea board config
Copy from jaq and rename the string.
BUG=chrome-os-partner:38537
TEST=None
BRANCH=None
Change-Id: Ie20a3b700e980a695bc8bf3c22c6ce2e12a0140a
Signed-off-by: Tim Chen <Tim-Chen@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/266965
Reviewed-by: Katie Roberts-Hoffman <katierh@chromium.org>
onfig/thea.py
|
| 242b7acbfba3199a739b83ca1ed29ae23d9c02fb |
13-Apr-2015 |
david <david_wu@quantatw.com> |
Gandof: Add faft config for Gandof
Inherit the Auron config.
BUG=none
TEST=none
Change-Id: I1a644148f163e6ad025bb58e19767a4b2c0afb4f
Signed-off-by: David Wu <David_Wu@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/265402
Reviewed-by: Ryan Lin <ryan.lin@intel.com>
Reviewed-by: Shawn N <shawnn@chromium.org>
Commit-Queue: David Wu <david_wu@quantatw.com>
Tested-by: David Wu <david_wu@quantatw.com>
onfig/gandof.py
|
| aaeafa5e97da85209f32558639ce0daafacbc4b0 |
25-Mar-2015 |
Ted Kuo <tedkuo@ami.com.tw> |
Ninja, Sumo: Add config settings for FAFT
BUG=None
TEST=Tested firmware_FAFTSetup on Ninja and Sumo
BRANCH=None
Signed-off-by: Ted Kuo <tedkuo@ami.com.tw>
Change-Id: Icad2b8d8e9355d2e8e4706e69c7b6490c06c713d
Reviewed-on: https://chromium-review.googlesource.com/262353
Reviewed-by: Shawn N <shawnn@chromium.org>
Commit-Queue: Ted Kuo <tedkuo@ami.com.tw>
Tested-by: Ted Kuo <tedkuo@ami.com.tw>
onfig/ninja.py
onfig/sumo.py
|
| 8734903b632b600b3e94cbc7094d980f3edd356d |
09-Mar-2015 |
ZhengShunQian <zhengsq@rock-chips.com> |
minnie: faft: add config derived from veyron
BUG=chrome-os-partner:37486
TEST=run firmware_FAFTSetup on minnie
Change-Id: I9d96b204e0199a14a88326177c69065ea3c1d615
Signed-off-by: ZhengShunQian <zhengsq@rock-chips.com>
Reviewed-on: https://chromium-review.googlesource.com/257315
Reviewed-by: Julius Werner <jwerner@chromium.org>
Tested-by: Jiazi Yang <Tomato_Yang@asus.com>
onfig/minnie.py
|
| 2a26fafcafc6c0c6947344b45d7e20ba31ea6590 |
03-Mar-2015 |
Julius Werner <jwerner@chromium.org> |
faft: Fix detection for locally-built test images on USB stick
CL:254432 (faft: Make sure the USB stick in servo matches the board
under test) accidentally broke the USB image verification for test
images that are built by developers locally. Sorry about that (I've
avoided wasting time on a full build_image for so long that I forgot
people actually do that). This patch should once again match both kinds
of images.
BUG=chromium:463574
TEST=None (since my test_that seems to be broken for unrelated reasons
right now).
Change-Id: I092ee54ac1560200dee025e4f67bb59ab2a1407c
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/255628
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: Icarus W Sparry <icarus.w.sparry@intel.com>
Tested-by: Icarus W Sparry <icarus.w.sparry@intel.com>
irmware_test.py
|
| 7cfba80eb4bb0a40208ef5ca1daf7bbc8b6a48ed |
27-Feb-2015 |
Gediminas Ramanauskas <gedis@google.com> |
veyron: increasing confirm_screen delay
BUG=chrome-os-partner:37080
TEST=faft_ec
Change-Id: Id0df502902d9673002a8807b23486eb768bd90a2
Reviewed-on: https://chromium-review.googlesource.com/254430
Reviewed-by: danny chan <dchan@chromium.org>
Tested-by: Gediminas Ramanauskas <gedis@chromium.org>
Commit-Queue: Gediminas Ramanauskas <gedis@chromium.org>
onfig/veyron.py
|
| dc535dfe1f95fe8ec4b95b02ffc12ed0fb40f83c |
27-Feb-2015 |
Julius Werner <jwerner@chromium.org> |
faft: Make sure the USB stick in servo matches the board under test
It's surprisingly easy to accidentally run FAFT with a wrong USB stick
plugged in. As long as it's any kind of test image, the pre-test checks
will pass... and when running tests that boot from USB, the fact that
the dev keys are a single keyset shared across all boards (unlike
(pre-)MP keys) means that ARM boards will happily try to boot x86
kernels and other nonsense like that, with results that look very much
like real test failures.
This patch adds a simple check to assert_test_image_in_usb_disk() to
make sure that the image on the USB stick is for the same board as the
image currently booted on the DUT (from local storage), which should
catch at least the most simple of mix-ups.
BUG=chrome-os-partner:37128
TEST=Ran firmware_RecoveryButton on a Jerry. Succeeded with a Jerry
image and failed with a Falco image plugged in.
Change-Id: Ifa5576afdec1bdd29ee872dcc8e987717138b97d
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/254432
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| 6f2ed14cfd36fe2f7aff9d80014746fa90dec1e8 |
19-Feb-2015 |
Julius Werner <jwerner@chromium.org> |
faft: Allow enable_rec_mode_and_reboot() to switch USB state
Several helper functions that wrap enable_rec_mode_and_reboot() (most
importantly enable_dev_mode_and_reboot()) change the USB state before
calling it to make the DUT either boot right into recovery mode from
that stick or ensure that it will halt at the recovery screen. This is a
problem when these functions are called while the DUT is already booted
from USB, since enable_rec_mode_and_reboot() tries to sync the root file
system before actually rebooting -- if you have already pulled out the
USB stick from under it at this point, this sync will fail and result in
exceptions.
This change adds an optional usb_state parameter to
enable_rec_mode_and_reboot() and makes it do the switch itself at the
right time (after the DUT is powered off) when provided. All helper
functions calling it in this manner are updated to use the new
functionality.
BUG=None
TEST=Ran firmware_RecoveryButton on a Jerry.
Change-Id: I0420af8b86d6995ad9cd93d2cda5fead1f421687
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/251053
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| 9687e0b64e3853a63e627753c3871f4c0d08878d |
17-Feb-2015 |
Danny Chan <dchan@google.com> |
Increase wait time before pressing power.
- Add faft config powerup_ready in DEFAULTS.py and set to 10 seconds.
- Mighty require 10 seconds before pressing power button to start.
BUG=None
TEST=Run against Mighty
Change-Id: If8fb899764697d71fe5d1064b47f4e7c59604ba8
Reviewed-on: https://chromium-review.googlesource.com/250470
Tested-by: danny chan <dchan@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: danny chan <dchan@chromium.org>
onfig/DEFAULTS.py
|
| 19388f1cf77f1b71945d33c5fe2f48b241ee89c5 |
11-Feb-2015 |
David Hendricks <dhendrix@chromium.org> |
storm: Add initial FAFT config
BUG=chrome-os-partner:34513
BRANCH=none
TEST=none
Change-Id: I4d6c2005ef990bf67869cf31d093e7b3943ef56b
Reviewed-on: https://chromium-review.googlesource.com/248402
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: David Hendricks <dhendrix@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
onfig/storm.py
|
| c2f7cd4ed2d1c737193148b53363edee63e7c1a1 |
04-Feb-2015 |
ZhengShunQian <zhengsq@rock-chips.com> |
faft_config: Add Jaq and Gus board config
Jaq and Gus is the variants Mighty/Veyron
BUG=chrome-os-partner:36303
TEST=None
BRANCH=None
Change-Id: I69adbc34f3b1d3a31df11a0047b165889a6509d9
Signed-off-by: ZhengShunQian <zhengsq@rock-chips.com>
Reviewed-on: https://chromium-review.googlesource.com/245941
Reviewed-by: Katie Roberts-Hoffman <katierh@chromium.org>
onfig/gus.py
onfig/jaq.py
|
| 2eedc9fcd1f8605f8da11adc593a2a3a7529f468 |
05-Feb-2015 |
david <david_wu@quantatw.com> |
Banjo: Add faft config for Banjo
Inherit the rambi config.
BUG=None
TEST=None
Change-Id: Ied18d2ed1f42404afa2ab4720af0c13cd86a45fc
Signed-off-by: David Wu <David_Wu@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/246456
Tested-by: David Wu <david_wu@quantatw.com>
Reviewed-by: Shawn N <shawnn@chromium.org>
Commit-Queue: Ryan Lin <ryan.lin@intel.com>
onfig/banjo.py
|
| fdddbbb16647d8552d7f8e941108f9df8bb074ba |
28-Jan-2015 |
Marc Jones <marc.jones@se-eng.com> |
cid: fix autotest config whitespace
Some whitespace errors crept in the cid config.
BUG=chrome-os-partner:35841
TEST=emerge-$BOARD autotest autotest-tests
BRANCH=None
Change-Id: I633ee6014ffe67bd6719a7bcb05b5db505051406
Signed-off-by: Marc Jones <marc.jones@se-eng.com>
Reviewed-on: https://chromium-review.googlesource.com/243853
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/cid.py
|
| a61fcd08e2d0581120736af31da275598f9e838d |
27-Jan-2015 |
Marc Jones <marc.jones@se-eng.com> |
lulu: Add lulu autotest config
Lulu references the Auron autotest config
BUG=chrome-os-partner:35841
TEST=emerge-lulu autotest autotest-tests
BRANCH=None
Change-Id: I8180b50621f2686afc4c34beb6ae1eabaa9214bf
Signed-off-by: Marc Jones <marc.jones@se-eng.com>
Reviewed-on: https://chromium-review.googlesource.com/243852
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/lulu.py
|
| 2e0c567bafbfe6dc47650fe08e6aa43a6eb08ee0 |
23-Jan-2015 |
ren kuo <ren.kuo@quantatw.com> |
Rikku: add FAFT config of rikku
BUG=none
TEST=none
Change-Id: I5c88d99e61b537b43f173751f7453c697b767ded
Signed-off-by: Ren Kuo <ren.kuo@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/242737
Reviewed-by: Zhuo-hao Lee <zhuo-hao.lee@intel.com>
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/rikku.py
|
| a8434196709a559e75b73f8c98a5cd353f19572a |
23-Jan-2015 |
Marc Jones <marc.jones@se-eng.com> |
cid: Add cid autotest config
Cid references the Auron autotest config
BUG=chrome-os-partner:35841
TEST=None
BRANCH=None
Change-Id: I39fe4cbf205babb9b5208ba04c9ecd902eaa41a8
Signed-off-by: Marc Jones <marc.jones@se-eng.com>
Reviewed-on: https://chromium-review.googlesource.com/242777
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
onfig/cid.py
|
| d2de5082f2158ba8eae8b2e935598c614f8ce297 |
14-Jan-2015 |
david <david_wu@quantatw.com> |
Guado: Add faft config for Guado
BUG=chrome-os-partner:35418
TEST=none
Change-Id: I8b2a6077843008329bc850c00c192827443c224a
Signed-off-by: David Wu <David_Wu@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/240699
Reviewed-by: Shawn N <shawnn@chromium.org>
Commit-Queue: David Wu <david_wu@quantatw.com>
Tested-by: David Wu <david_wu@quantatw.com>
onfig/guado.py
|
| 8a6018ee0b2fd79b9d8cdbbff3e1350c7e784d3e |
15-Jan-2015 |
Kaiyen Chang <kaiyen.chang@intel.com> |
Tidus: Add faft config for Tidus
BUG=chrome-os-partner:35423
TEST=none
Change-Id: Ibef04afe5f297ac907c4888e8de0a8a3d508fcd6
Signed-off-by: Kaiyen Chang <kaiyen.chang@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/240691
Reviewed-by: Shawn N <shawnn@chromium.org>
onfig/tidus.py
|
| ef4b95a2e39e60f99089efb5553d03a5211fa647 |
14-Jan-2015 |
david <david_wu@quantatw.com> |
FAFT: Add config settings for jecht for FAFT tests
Inherit the panther config.
BUG=chrome-os-partner:35418
TEST=none
Change-Id: I054cd398181d11b7c6111bdf1780be35b2052070
Signed-off-by: David Wu <David_Wu@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/240633
Reviewed-by: Shawn N <shawnn@chromium.org>
Commit-Queue: David Wu <david_wu@quantatw.com>
Tested-by: David Wu <david_wu@quantatw.com>
Reviewed-by: Kaiyen Chang <kaiyen.chang@intel.com>
Commit-Queue: Kaiyen Chang <kaiyen.chang@intel.com>
Tested-by: Kaiyen Chang <kaiyen.chang@intel.com>
onfig/jecht.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>
irmware_test.py
tils/faft_checkers.py
|
| b575242a8f8d8e5f67350f20701f3a9b73a33504 |
10-Jan-2015 |
Steve Fung <stevefung@chromium.org> |
FAFT: handle mmc devices correctly in blocking_sync calls
For devices using mmc rather than [s]ata, the firmware_test library
should be using the `mmc` tool rather than hdparm.
BUG=chromium:435715
TEST=run firmware_FAFTSetup autotest case, doesn't crash with hdparm error
CQ-DEPEND=I1ccb01ec0b30aef58a3cb1b0b1f6724233fc1d08
Change-Id: I06c8d8fcd3f2fbdc0b023c3d085321b326ceece5
Reviewed-on: https://chromium-review.googlesource.com/240024
Reviewed-by: Gwendal Grignou <gwendal@chromium.org>
Commit-Queue: Stephen Fung <stevefung@chromium.org>
Tested-by: Stephen Fung <stevefung@chromium.org>
irmware_test.py
|
| 89ecd18df53df9162d07a1e514fb997b0e8d7bac |
06-Jan-2015 |
ZhengShunQian <zhengsq@rock-chips.com> |
veyron: faft: set wp_voltage to pp3300
To enable write protect, the hardware write protect pin should be
asserted with 3.3v. So set wp_voltage to 'pp3300' in veyron.py.
The original value of wp_voltage is 'off' which results in fails of
firmware_DevMode tests.
One can reproduce by doing:
$ dut-control fw_wp_vref:off
$ dut-control fw_wp_en:on
$ dut-control fw_wp:on
$ dut-control ec_uart_cmd:"flashwp disable"
$ dut-control ec_uart_cmd:"reboot"
TEST=enable then disable write protect through dut-control
BUG=chrome-os-partner:34435,chrome-os-partner:34806
BRANCH=None
Change-Id: If0f409ad05d41d1feaa828b729bba82ee0f92666
Signed-off-by: ZhengShunQian <zhengsq@rock-chips.com>
Reviewed-on: https://chromium-review.googlesource.com/238676
Reviewed-by: Julius Werner <jwerner@chromium.org>
onfig/veyron.py
|
| 9ece2c6fb01d4c29d23a7238def15bdf656c885c |
12-Dec-2014 |
Julius Werner <jwerner@chromium.org> |
Add firmware_EventLog test to verify event log generation and timestamps
This patch adds a new faft_lv4 test to validate the functionality of the
firmware event log. It will boot the system in normal, developer and
recovery mode, verifying that the right events are logged for each. It
also tests a suspend/resume cycle, allowing either the ACPI events used
on x86 boards or the userspace Sleep/Wake events introduced with Spring
and Pit. (We can't check for 'FW Wake' because not all not-x86 boards
have a resume component in firmware.) The events are correlated to the
test section they were generated in by their timestamps, so this also
confirms that accurate timestamps are generated.
CQ-DEPEND=CL:238467
BUG=chrome-os-partner:34108
TEST=Tested on Falco (ToT), Blaze (ToT) and Pi (release). Pi failed in
the expected manner because U-Boot is missing RTC support (and all
timestamps are added as 2000-00-00). Blaze failed because its
timestamps' months are off by one... turns out the RTC driver code was
incorrectly copied from the 0-based-month-using kernel to our
1-based-month-using coreboot.
Change-Id: I2760080030468ed71dd0b7359ac69a269f6ab47a
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/238078
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/DEFAULTS.py
onfig/alex.py
onfig/lumpy.py
onfig/nyan.py
onfig/pi.py
onfig/pit.py
onfig/skate.py
onfig/snow.py
onfig/spring.py
onfig/stumpy.py
onfig/zgb.py
|
| 1c07eced42fb8839c8791fd52a895457a1d36f55 |
17-Dec-2014 |
ZhengShunQian <zhengsq@rock-chips.com> |
FAFT: add mighty and speedy board support
mighty and speedy derivate from veyron
BUG=chrome-os-partner:33269
TEST=run firmware_DevMode, verify there isn't any platform error
Change-Id: I182b3be6a104b235ec864af34ccc9c5d1edfa085
Reviewed-on: https://chromium-review.googlesource.com/236300
Reviewed-by: Katie Roberts-Hoffman <katierh@chromium.org>
Tested-by: Shunqian Zheng <zhengsq@rock-chips.com>
Commit-Queue: Shunqian Zheng <zhengsq@rock-chips.com>
onfig/mighty.py
onfig/speedy.py
|
| 545c08a63a85a33c17c4e4ced578baf2055e8d6b |
09-Dec-2014 |
Danny Chan <dchan@google.com> |
Remove thermal ec capability.
BUG=chrome-os-partner:34359
TEST=None
Change-Id: If57c683600374fe5bc023101161ebbeeb05fd197
Reviewed-on: https://chromium-review.googlesource.com/234211
Trybot-Ready: danny chan <dchan@chromium.org>
Tested-by: danny chan <dchan@chromium.org>
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: danny chan <dchan@chromium.org>
onfig/auron.py
|
| 682a6d6a8f607fb70a7812194202826e1e6e85cc |
21-Nov-2014 |
Daisuke Nojiri <dnojiri@chromium.org> |
sets mainfw_act to A before running a firmware test
vboot2 does not prefer a particular slot. if slot B is found good and
valid, it keeps booting on B. due to this new behavior some tests such
as CorruptBothFwBodyAB leave the target booting on slot B. Thus, some
tests such as CorruptFwBodyA fail when running back-to-back.
BUG=chrome-os-partner:32193
BRANCH=ToT
TEST=ran faft successfully on nyan kitty
Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>
Change-Id: I0ff8697b913bf74ba3127a3f57cdc42be1e47e23
Reviewed-on: https://chromium-review.googlesource.com/231377
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| 9a658daba9ca14601688527c2047b94f6a4d9b85 |
13-Nov-2014 |
Yen Lin <yelin@nvidia.com> |
kitty: add FAFT config file for kitty
Add FAFT config file for kitty
BUG=chrome-os-partner:33063
TEST=pass firmware_FAFTSetup test
Change-Id: I1e8cad3dd1946ed7db238d560c9e7a77e19445f4
Signed-off-by: Yen Lin <yelin@nvidia.com>
Reviewed-on: https://chromium-review.googlesource.com/229613
Reviewed-by: Mohammed Habibulla <moch@chromium.org>
onfig/kitty.py
|
| 0313339e1765ad964544232d64c1657c34cbce16 |
18-Nov-2014 |
David Hendricks <dhendrix@chromium.org> |
FAFT: add initial veyron_* board support
This adds veyron and the current derivatives (pinky and jerry).
BUG=chrome-os-partner:33407
BRANCH=none
TEST=tests run on pinky (successfully or not is another matter...)
Change-Id: I3b7a64891a85842681a6ce8e8da917fd14072dc8
Reviewed-on: https://chromium-review.googlesource.com/230330
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
Commit-Queue: David Hendricks <dhendrix@chromium.org>
onfig/jerry.py
onfig/pinky.py
onfig/veyron.py
|
| 1c39625ee305972bd41fbd6d700f1c806ff6cbad |
14-Nov-2014 |
eddylu <eddylu@ami.com.tw> |
FAFT: Add config settings for cranky for FAFT tests
BUG=None
TEST=Ran firmware_FAFTSetup on cranky.
Change-Id: I0f948fb1a5e2ac17c7484c55aa02f2a6967c86b5
Reviewed-on: https://chromium-review.googlesource.com/229762
Reviewed-by: Shawn Nematbakhsh <shawnn@chromium.org>
Commit-Queue: 元亨 盧 <eddylu@ami.com.tw>
Tested-by: 元亨 盧 <eddylu@ami.com.tw>
onfig/cranky.py
|
| 101b0b26778060c13e6fbceddc92f21734f2878f |
06-Nov-2014 |
Danny Chan <dchan@google.com> |
wait for boot_id in full_power_off_and_on.
- This change is to address firmware_ConsecutiveBoot test failure
with ConnectionError. Without this change, the call to
wait_for_client_offline will timeout after 60 seconds and throw
ConnectionError exception.
BUG=None
TEST=None
Change-Id: I61dec99adf8fec7a931f85647d60ffad8cae2be6
Reviewed-on: https://chromium-review.googlesource.com/228194
Tested-by: danny chan <dchan@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: danny chan <dchan@chromium.org>
irmware_test.py
|
| b8bec437931313c6d6065474fc9544e6d40d122e |
23-Oct-2014 |
Pan Sheng-Liang <Sheng-Liang.Pan@quantatw.com> |
FAFT: Add config settings for paine for FAFT tests
Inherit the auron config.
BUG=chrome-os-partner:33198
TEST=None
Change-Id: I6fecb974831cbca9044841353e71dce8a42c4476
Signed-off-by: Pan Sheng-Liang <Sheng-Liang.Pan@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/225031
Reviewed-by: Shawn Nematbakhsh <shawnn@chromium.org>
onfig/paine.py
|
| 836492dfec8403aed139a1b14e66684aff4f37f9 |
21-Oct-2014 |
Tim-Chen <Tim-Chen@quantatw.com> |
FAFT: Add config settings for yuna for FAFT tests
Inherit the auron config.
BUG=chrome-os-partner:33073
TEST=None
Change-Id: Icddb512305d4a591e62e4a569f1f33610413f6cc
Signed-off-by: Tim Chen <Tim-Chen@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/224599
Reviewed-by: Shawn Nematbakhsh <shawnn@chromium.org>
onfig/yuna.py
|
| b3abc438e7eb0f2eef06b0351af3ca6727fab779 |
08-Oct-2014 |
Duncan Laurie <dlaurie@chromium.org> |
faft: Wait for system to respond to ping before attempting ssh
In the course of faft testing there are a lot of random test failures
due to ssh timeouts which declare the DUT to be unresponsive, but when
looking at the host everything is fine. These tests will typically
pass with subsequent re-runs.
When debugging this I found that the wait_for_kernel_up() function
is not really waiting for the kernel to be up and is attempting to
initiate a ssh connection immediately after resetting or powering up
the device.
While this seems to work most of the time where ssh will eventually
connect it occasionally times out and does not connect and the test
will be declared to fail.
Under worst-case conditions the system will be in developer mode and
run EC+PD software sync and have a slow to connect network and can
take a minute before it is responsive.
It seems that adding a ping check with a generous timeout in the
wait_for_kernel_up() function increases the reliability of the tests
and does not seem to have a downside except if a device is actually
failed it can take longer to be considered a failure.
The function does not abort if the ping check fails, it will print a
warning and then attempt to ssh -- all in order to continue the
existing behavior in case ping fails but ssh is functional.
BUG=chrome-os-partner:30832
TEST=run suite:faft_bios on samus and get 100% pass rate
Change-Id: Ibfdf2d5ac1f3e3311b98ba36abdad12f892f3df5
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/222011
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| 10eb618d5336f1bd6f4cd4c135ea93d1e3a880bf |
08-Oct-2014 |
Duncan Laurie <dlaurie@chromium.org> |
faft: Create a lockfile on test init and remove it on cleanup
In order to remove possible interference from outside utilities
add a lockfile that is present during FAFT testing and cleaned up
when FAFT is done.
This is going to be used by chromeos-setgoodkernel which operates
on GPT 30 seconds after boot, and also runs chromeos-firmwareupdate
with --mode=bootok. Depending on the test being run either of
these actions can interfere with FAFT testing and lead to inconstent
results and makes it very difficult to debug test failures.
BUG=chrome-os-partner:30832
TEST=run suite:faft_bios on samus, check that lockfile is created
during test init and removed in test cleanup step.
Change-Id: I3f483110d3dcdd14eaa55c1a59aa1387cd38c617
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/222010
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
irmware_test.py
|
| af61c1fb249fe2e0702eba0385cb07f368d6eb68 |
08-Oct-2014 |
Duncan Laurie <dlaurie@chromium.org> |
faft: firmware_test: Add support for logging USBPD UART
With the Samus (and future) platforms there is the possibility
of a second embedded controller uart from servo. In order to
assist with debugging test failures log this if it is advertised
to exist in the ec_capability for a platform.
BUG=chrome-os-partner:30832
TEST=run suite:faft_bios on samus and check that usbpd_uart.txt
is produced and contains the console log from the PD MCU.
Change-Id: I57ed94a30840ec0c4ff16789c0b1b16aba346eca
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/221989
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/samus.py
irmware_test.py
|
| 725a32d39197c209f17dbefcc1a6e21c71a7211d |
22-Sep-2014 |
Duncan Laurie <dlaurie@chromium.org> |
samus: Remove 'thermal' from supported EC interface
Samus does not use the old-style fan/thermal control interface
on the EC so this particular test does not work.
We should add support for the new interface, but for the moment
I am more interested in having FAFT pass on Samus.
BUG=chrome-os-partner:30832
TEST=run suite:faft_ec on samus
Change-Id: Ifead84cea8cf9b1fc336f45122811aaf2001fe5e
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/219213
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
onfig/samus.py
|
| 5bee610032835a130b14892b29c70d867639ea43 |
16-Sep-2014 |
Ryan Lin <ryan.lin@intel.com> |
faft: Ensure blocking sync is called before reboot
Ensure blocking sync is called before all of servo-triggered reset,
whether warm or cold.
Also, add command 'hdparm' to blocking_sync() to make sure that TUR
has to be sent to SSD for checking the status.
BUG=chrome-os-partner:31300
TEST=Ran FAFT
Change-Id: Ic5e4d98e4b0d6246106f6de94a153562793dde71
Signed-off-by: Ryan Lin <ryan.lin@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/218560
Reviewed-by: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
irmware_test.py
|
| 77222c6dc519ce83a5aaee1852d3b0d4e5cf383b |
22-Sep-2014 |
Marc Jones <marc.jones@se-eng.com> |
Candy: Add Candy autotest config
Candy references the Rambi config.
BUG=chrome-os-partner:32179
TEST=None
Branch=None
Change-Id: Iff1c6e3a7d780baa35039919ed97adb517625e5c
Signed-off-by: Marc Jones <marc.jones@se-eng.com>
Reviewed-on: https://chromium-review.googlesource.com/219350
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/candy.py
|
| ba464086497293a6b597a5188932e9bc4f097199 |
08-Sep-2014 |
Bernie Thompson <bhthompson@chromium.org> |
FAFT: Add config settings for Auron for FAFT tests
This is a clone of the slippy config.
BUG=chrome-os-partner:31590
TEST=None
Change-Id: I71cd37cc371332031a9b9f32bf9eaa70d6e6dc38
Reviewed-on: https://chromium-review.googlesource.com/217011
Reviewed-by: Mohammed Habibulla <moch@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
onfig/auron.py
|
| e04dd43e822ffcbbd95d982e6ce1544e318ef4a9 |
27-Aug-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Adding a check that dut is down during full power cycle.
Currently it presses the power button, wait and presses again. We don't
confirm that the DUT is actually down. This might be a problem if there
is an infrastructure issues where the system doesn't actually turn off.
Keeping the sleep, since there might be a need that we wait for a
minimum amount of time for the device to shutdown fully.
TEST=ran at desk against winky
BUG=chromium:408297
DEPLOY=test_importer
Change-Id: I732aaff5aaf1024f0de10fb90d3e8a107e13e341
Reviewed-on: https://chromium-review.googlesource.com/214593
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| 1bacc9661de528d838294d0c517905f4ded7f632 |
14-Aug-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Replacing sync and sleep with a blocking sync call.
Currently we call sync and then sleep for expected time required. This
seems to be problematic in situations when the expected sleep time is
too short.
Instead we are faking a blocking sync by calling sync twice. The first
time its called, it returns before the sync is complete, but the
subsequent call should wait for the first one to complete.
Also, removed the sync faft config value since its not used anymore.
BUG=chromium:239034,chromium:31300
TEST=ran tests at desk
Change-Id: I0b122f80a62fd5a1442b7b3c8e205e1a78bf4a59
Reviewed-on: https://chromium-review.googlesource.com/212492
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/DEFAULTS.py
irmware_test.py
|
| 5dca4e7893cc5a1545a3657aaed5798930ec54f7 |
22-Jul-2014 |
Ricky Liang <jcliang@chromium.org> |
Add common.py
We have a 'import common' in config.py but there is not such module.
The common module is suppose to set up sys.path for autotest_lib.*.
BUG=None
TEST=Run `python -c import config` in server/cros/faft/config directory.
Change-Id: Ie90feabf684e5a43b00b396cdb7af90fe9615036
Reviewed-on: https://chromium-review.googlesource.com/208925
Tested-by: Ricky Liang <jcliang@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Queue: Ricky Liang <jcliang@chromium.org>
onfig/common.py
|
| 4cc163978a0af5bace4c65df81ea98b360132c1e |
23-Jul-2014 |
Duncan Laurie <dlaurie@chromium.org> |
faft: Add config for Samus platform
This is based on slippy with added smart usb control via EC.
BUG=chrome-os-partner:30832
TEST=test_that -b samus dut firmware_FAFTSetup
Change-Id: I8a9d49a3f8e2f5b02d1c6faca6b927c7207e01ea
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/209359
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/samus.py
|
| cab6be36a26c73dd4e6fa2f85ba48f50cfd92aca |
17-Jul-2014 |
J. Richard Barnette <jrbarnette@chromium.org> |
Purge the last vestiges of ServoTest
This class has been slated for removal for nearly two years. All
that remained was a stub with a two-line initialize() method, so,
time to finish the job.
BUG=chromium:215491
TEST=Run FAFTSetup on link
Change-Id: If349e1d335c038c28c8ce65a7dc1ab5dd7f59e32
Reviewed-on: https://chromium-review.googlesource.com/208733
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
irmware_test.py
|
| 5d1522e5231065d4372b2a6c5d752143a5074e9e |
10-Jul-2014 |
Danny Chan <dchan@google.com> |
File cleanup for presubmit hook.
-Add missing docstring.
BUG=chromium:389247
TEST=None
Change-Id: I844fb2845dfb48f4d9b3d082a4f221319d992d05
Reviewed-on: https://chromium-review.googlesource.com/207246
Reviewed-by: danny chan <dchan@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: danny chan <dchan@chromium.org>
Tested-by: danny chan <dchan@chromium.org>
onfig/alex.py
onfig/butterfly.py
onfig/lumpy.py
onfig/panther.py
onfig/parrot.py
onfig/pi.py
onfig/pit.py
onfig/skate.py
onfig/snow.py
onfig/spring.py
onfig/stout.py
onfig/stumpy.py
onfig/zako.py
onfig/zgb.py
|
| 1437ad5dc23e70f3fc8d643adf33818d5460aede |
30-Jun-2014 |
Danny Chan <dchan@google.com> |
File cleanup for presumbit hook.
- Fix logging warning.
BUG=chromium:389247
TEST=None
Change-Id: If0a0133346978811e8a48ca023d3f59ddc29d4f5
Reviewed-on: https://chromium-review.googlesource.com/206302
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: danny chan <dchan@chromium.org>
Commit-Queue: danny chan <dchan@chromium.org>
irmware_test.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>
irmware_test.py
|
| ccdf2a85574eef54b0d5e49e501ee5a3489adbe3 |
02-Jul-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Removing faft_classes.py.
All tests have been converted to the new style faft classes in firmware_test.py
and nothing depends on faft_classes code anymore.
BUG=chromium:371185
TEST=None
Change-Id: I6edd85b68779c44cc90f526e511bc6765430f68b
Reviewed-on: https://chromium-review.googlesource.com/206309
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <yusufm@gmail.com>
Tested-by: Yusuf Mohsinally <yusufm@gmail.com>
aft_classes.py
|
| a57ff841026d6878e4ecbf993efd994638fde879 |
05-Jun-2014 |
J. Richard Barnette <jrbarnette@chromium.org> |
Make FAFT use standard interfaces for recovery mode.
This changes the FAFT enable_rec_mode_and_reboot() method for
booting devices in recovery mode to use the standard servod
interface for the operation.
BUG=chrome-os-partner:29974,chrome-os-partner:29473,chromium:326738
TEST=FAFTSetup on link, quawks
Change-Id: I73a5b30f81a5c9b2592bc9bbe5285b3dd8f750a5
Reviewed-on: https://chromium-review.googlesource.com/202721
Reviewed-by: Dan Shi <dshi@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Richard Barnette <jrbarnette@chromium.org>
aft_classes.py
irmware_test.py
|
| 64ee3a7f9105e8819abf9e14f5a767a23d836823 |
26-Jun-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Remove unused variable next_step.
This variable is a legacy from the old style faft classes, and now causes an
exception when this code is executed. Removing it.
BUG=chromium:389196
TEST=At desk, ran firmware_FAFTSetup successfully, and also ran it while
putting the device in a bad state. Recovery routine worked fine as well.
Change-Id: I17cba74b0b801319dfc5c9dfcd422e35bf40ca0d
Reviewed-on: https://chromium-review.googlesource.com/205786
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| 4b6af0dd6228d3f43573c8a9fafc18260b668eed |
05-Jun-2014 |
J. Richard Barnette <jrbarnette@chromium.org> |
Convert all boards to use the servod 'power_state' control.
All boards now provide the standard board-independent interface for
power off, power on, recovery mode, and cold reset operations.
BUG=chromium:342875,chromium:326738
TEST=Pending
Change-Id: Ic68017a598df3745347ceff90cc8d8faf8e344fe
Reviewed-on: https://chromium-review.googlesource.com/202720
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Kris Rambish <krisr@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Richard Barnette <jrbarnette@chromium.org>
aft_classes.py
irmware_test.py
|
| f3e6e8f6166daf17a950d35e79fe0f3d58575124 |
05-Jun-2014 |
Derek Basehore <dbasehore@chromium.org> |
Add dark_resume_capable flag for link
The change the added the dark_resume_capable flag did not add it for link.
BUG=chromium:288206
TEST=run kernel_daily_regression suite in the lab
Change-Id: I3259ff7280dfb7ecd0f56141c47b6010fa597784
Reviewed-on: https://chromium-review.googlesource.com/202660
Reviewed-by: Sameer Nanda <snanda@chromium.org>
Commit-Queue: Derek Basehore <dbasehore@chromium.org>
Tested-by: Derek Basehore <dbasehore@chromium.org>
onfig/link.py
|
| 9887e6feddf79ff8981e39a1957303ba65879e56 |
03-Jun-2014 |
Vic Yang <victoryang@chromium.org> |
FAFT: Add ctrl-D to common methods
This adds ctrl-D to setup_dev_mode() and also provides option to press
ctrl-D when cold/warm rebooting.
BUG=chrome-os-partner:29210
TEST=Check corresponding dev screen is skipped.
Change-Id: I231b5e19c8d1da5c84c09cc4ceb6383ddc082a53
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/202458
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
irmware_test.py
|
| e1c53ade5eb08630029b40221f7d8ac030f2ab16 |
02-Jun-2014 |
Vic Yang <victoryang@chromium.org> |
nyan: Set wp_voltage to open drain
On Nyan, the write protect reference voltage is directly fed to
+1.8V_SPI rail. This, however, causes problem on AP boot. Let's set this
to open-drain.
BUG=chrome-os-partner:29210,chrome-os-partner:29270
TEST=Check FAFT can enable firmware write protect
Change-Id: I561825662c2a5f44a0a2c759f0d8c5b4d5e47fac
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/202382
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: David Hendricks <dhendrix@chromium.org>
onfig/nyan.py
|
| 15c2dcbdcc125d5be186ff18bd3a593c9afc2af3 |
02-Jun-2014 |
Vic Yang <victoryang@chromium.org> |
FAFT: split wp_voltage and spi_voltage in FAFT config
The write protect reference voltage and SPI voltage are not necessarily
the same. Make them two separate options so that we can configure them
to be different.
BUG=chrome-os-partner:29210
TEST=Grep 'vref' and check each one is using the correct config value.
Change-Id: I5cc30ea364f482a0febd66bfd99d857630bfa401
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/202381
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: David Hendricks <dhendrix@chromium.org>
onfig/DEFAULTS.py
onfig/link.py
onfig/rambi.py
onfig/slippy.py
|
| 6efb4479f0f359f4b17d3d0a37f49c5087c4f6e9 |
29-May-2014 |
david <david_wu@quantatw.com> |
Mccloud: Add faft config for Mccloud
BUG=chrome-os-partner:28942
TEST=none
Change-Id: I198be2ba28e6470f26544d6fbf42ad91863e2bf1
Signed-off-by: David Wu <David_Wu@quantatw.com>
Reviewed-on: https://chromium-review.googlesource.com/202051
Commit-Queue: David Wu <david_wu@quantatw.com>
Tested-by: David Wu <david_wu@quantatw.com>
Reviewed-by: Shawn Nematbakhsh <shawnn@chromium.org>
onfig/mccloud.py
|
| 0a77ddc3ba80974a8a0b7863bdf037a52c9b852d |
29-May-2014 |
David Hendricks <dhendrix@chromium.org> |
nyan*: Reduce dev_screen and firmware_screen delays
Nyan's display comes up faster than the default settings. We need
to reduce these delays so that FAFT doesn't miss the screens as
it's transitioning modes.
BUG=chrome-os-partner:29210
TEST=firmware_DevScreenTimeout passes on Big
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Change-Id: Ibcf19b515fdebc7c9913ce62c788a1966e582b32
Reviewed-on: https://chromium-review.googlesource.com/202047
Reviewed-by: Tom Warren <twarren@nvidia.com>
Reviewed-by: Vic Yang <victoryang@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
Commit-Queue: David Hendricks <dhendrix@chromium.org>
onfig/nyan.py
|
| 8d23f241c6a227f61a989d4aca3c4efddf55958f |
30-May-2014 |
Vic Yang <victoryang@chromium.org> |
FAFT: Add missing wait_for_kernel_up call when changing GBB flags
After changing GBB flags, if a reboot is needed, we must wait for the
client to come up again before continuing.
BUG=chrome-os-partner:29210
TEST=Run a test and see GBB changed
Change-Id: Ib99a681ff29baffcd4e94926842babcf85897090
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/202209
Reviewed-by: David Hendricks <dhendrix@chromium.org>
irmware_test.py
|
| f426f531138e6794bf7e4012b6e799bd4acd964c |
30-May-2014 |
David Hendricks <dhendrix@chromium.org> |
Delay between setting hostevent and pressing power button
This adds a short delay (200ms) in enable_rec_mode_and_reboot
between setting the hostevent flag for recovery mode and pressing
the power button. This is intended to give the EC enough time
to receive and process the command, which may be especially long
if buffered DMA input is enabled.
BUG=chrome-os-partner:29210
TEST=Big boots into recovery mode more reliably.
Signed-off-by: David Hendricks <dhedndrix@chromium.org>
Change-Id: I006bf15e01e73f25a0295d2bbd20ca88493d2d24
Reviewed-on: https://chromium-review.googlesource.com/202225
Commit-Queue: David Hendricks <dhendrix@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Vic Yang <victoryang@chromium.org>
Tested-by: Vic Yang <victoryang@chromium.org>
aft_classes.py
irmware_test.py
|
| 2460162e708ba9c2ad5756787dd5ac718aa9eb90 |
28-May-2014 |
David Hendricks <dhendrix@chromium.org> |
Use warm_reset when rebooting into recovery mode
This replaces the EC console command "reboot ap-off" by asserting
warm_reset to keep the AP off. We are able to remove a delay and
also avoid a race condition in case the AP boots fast enough to
reach vboot init before the EC commands can be entered.
BUG=chrome-os-partner:29200
TEST=enable_rec_mode_and_reboot puts Big into recovery mode reliably
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Change-Id: Icc6babcdbd73c4c0b23a99548af1c0d639f4af66
Reviewed-on: https://chromium-review.googlesource.com/201785
Commit-Queue: David Hendricks <dhendrix@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Vic Yang <victoryang@chromium.org>
Tested-by: Vic Yang <victoryang@chromium.org>
aft_classes.py
irmware_test.py
|
| b15dbd5968eb838295a69c01b6ac00b964914a7a |
27-May-2014 |
David Hendricks <dhendrix@chromium.org> |
nyan: Decrease ec_boot_to_console override further
300ms was a bit too conservative, it seems. The EC's "Console
is enabled" message shows up at around 120ms, but the AP begins
vboot init at around 324ms. So commands like "reboot ap-off" need
to be entered even sooner to avoid contending with vboot.
BUG=chrome-os-partner:29200
TEST=firmware_RecoveryButton succeeds more reliably on Nyan
Change-Id: Ie973f034023d22f0300c3d12154b1577ec65c6e1
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/201720
Reviewed-by: Vic Yang <victoryang@chromium.org>
onfig/nyan.py
|
| a8a2a555f8cb17c261aebf8a5e3135b19128a7e2 |
23-May-2014 |
David Hendricks <dhendrix@chromium.org> |
nyan: Fix syntax of ec_capability
There shouldn't be perens there, and whatever it's doing is causing
autotest to not process the following line.
BUG=chrome-os-partner:24835
BRANCH=nyan
TEST=ec_boot_to_console on Nyan gets properly overridden to 0.3
Change-Id: I2b950a51b57cc69d29360989a73bc4a9d293954a
Reviewed-on: https://chromium-review.googlesource.com/201341
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: David Hendricks <dhendrix@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: shikha shrivastava <shikhas@nvidia.com>
onfig/nyan.py
|
| 8d348e011c84bf1cc960703281c876f8e2d84560 |
22-May-2014 |
Vic Yang <victoryang@chromium.org> |
firmware_test: fix error message
When a test image is not found in the USB disk, the error message is
incorrect and misleads people. Let's fix this.
BUG=chrome-os-partner:24835
TEST=None
Change-Id: Ic49ae28ea3bfbd044de7fae226984fd0c59285be
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/201150
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| 4576eef576abb1e53c619f3abaa48a0b1b240130 |
21-May-2014 |
David Hendricks <dhendrix@chromium.org> |
nyan: Add charging capability
This makes it so that the firmware_ECCharging test will run.
BUG=chrome-os-partner:28316
BRANCH=nyan
TEST=firmware_ECCharging now runs on nyan instead of err'ing out
Change-Id: I976bcfb88b05ec5fb6dc8e0e7d8f94e0d210a771
Reviewed-on: https://chromium-review.googlesource.com/200675
Commit-Queue: David Hendricks <dhendrix@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Vic Yang <victoryang@chromium.org>
onfig/nyan.py
|
| ed9b9df177137c216494303305eb223aaab1e9db |
20-May-2014 |
David Hendricks <dhendrix@chromium.org> |
nyan*: Shorten ec_boot_to_console
The default ec_boot_to_console value is 1.2s. At this point in the
AP's boot time, Depthcharge may have already run and put the EC
in a mode that FAFT does not expect.
Nyan's EC shows "Console is enabled" about 120ms into boot, so this
sets ec_boot_to_console at 300ms to be a bit conservative.
BUG=chrome-os-partner:24835
BRANCH=none
TEST=Watched EC console (on Big) during enable_rec_mode_and_reboot
to make sure sequence occurred in expected order.
Change-Id: Icf6d44964f6efa8cb0d9aef2e5139169137360c3
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/200511
Reviewed-by: Vic Yang <victoryang@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/nyan.py
|
| 0cc0462df0ae109c3313d0d8e966851db4ad3d5d |
20-May-2014 |
David Hendricks <dhendrix@chromium.org> |
nyan*: Add missing docstring
This just gets rid of an annoying pylint error when uploading.
BUG=none
BRANCH=none
TEST="repo upload" no longer fails with pylint errors.
Change-Id: I59559a19237f463dfd60f7be04faa63618be575a
Signed-off-by: David Hendricks <dhendrix@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/200510
Reviewed-by: Vic Yang <victoryang@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/nyan.py
|
| cae7902c34d173826c288d7407ea7c6178bb34fd |
14-May-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Fixing call to do_reboot_action.
1. Fixed 2 calls to do_reboot_action, which needed to provide the args as tuple.
2. Removed subprocess import since it was not doing anything.
BUG=chromium:371185
TEST=Ran firmware_TryFwB/control.ec_wp (which hit the issue) at desk on peppy
Change-Id: I254758d575415038ac3c4e784cf7e3c3bb11a6f5
Reviewed-on: https://chromium-review.googlesource.com/199843
Reviewed-by: Vic Yang <victoryang@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| 1b7a48b6c4e7cd007039a22d47667ea126240aad |
13-May-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Adding a sync at end of initialization.
This sync seems to resolve a number of occurances of BadStatusLine errors when
running FAFT tests under moblab and possibly in the real lab.
BUG=chromium:239034
TEST=Ran firmware_FAFTSetup at desk on wolf and ran on moblab instance against
peppy device.
Change-Id: Ib01eba5be6672284e66995d49fb33abb9a4d2920
Reviewed-on: https://chromium-review.googlesource.com/199454
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
aft_classes.py
irmware_test.py
|
| 8b377eb0528c632e4cb2d888f7388faf764f9987 |
13-May-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
FAFT rework : remove unused function and rename private functions.
Continuing changes for FAFT rework: chromium:371185
1. Removing the unused/broken install_test_image function and
related vars/functions/calls.
2. Renamed various functions that should be private to FAFT.
BUG=chromium:371185
TEST=Ran at desk against a wolf device a modified version of
fimrware_FAFTSetup which uses the new scheme.
Change-Id: Iaf2ff01e6bf93921f141e0cf03489700dd69d35d
Reviewed-on: https://chromium-review.googlesource.com/199428
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| ab1b5fc3918ca226dda7d39487dedc24b5efe20b |
08-May-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
FAFT rework: remove having to provide FAFT steps in special dict object.
Continuing changes for FAFT rework: chromium:371185
1. Removed functions specific to handling of the faft step template object,
including the function that processed the invidual steps in that object.
2. Renamed cold_reboot and warm_reboot functions to better reflect their
purpose and to open up adding new reboot functions which can be used by
firmware tests.
3. Replaced occurances of functions which relied on the old faft steps object
with bare function calls.
4. Created a get_bootid function out of the code which was previously in the
step processing function.
BUG=chromium:371185
TEST=Ran at desk against a wolf device a modified version of
fimrware_FAFTSetup which uses the new scheme.
Change-Id: I8a48dd128c6b5b293b26db166de4d4732aa17c59
Reviewed-on: https://chromium-review.googlesource.com/198864
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| 401a78ec33574a6b22db9fbe47c69183ce40da04 |
09-May-2014 |
Shawn Nematbakhsh <shawnn@chromium.org> |
faft: quawks: Configure WP pin as open drain
Configure servo-controlled WP pin on Quawks as open drain.
BUG=chrome-os-partner:27967
TEST=Pass firmware_RONormal_Boot on Quawks.
Change-Id: Ie6857895be891ffb778b50d9525bb947db8d9902
Reviewed-on: https://chromium-review.googlesource.com/199150
Commit-Queue: Shawn Nematbakhsh <shawnn@chromium.org>
Tested-by: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/quawks.py
|
| 05c3c558c1dadb05195c84c10bf8e2c21048096f |
08-May-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Initial version of FAFT rework class.
This is the first stage of the reworking on faft code. Details on the faft
rework are outlined in chromium:371185.
- A straight copy of the faft_classes.py file to firmware_test.py.
- Change name FAFTSequence to FirmwareTest, no logic changes.
- Copyright date change.
BUG=chromium:371185
TEST=Manually run suite:faft_bios at desk through test_that.
Change-Id: I22262e650101928ee34a08632153004bf26b6ccc
Reviewed-on: https://chromium-review.googlesource.com/198778
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
irmware_test.py
|
| 04be2bd5e4666a5c253e9c30ab20555e04286032 |
08-May-2014 |
Ilja H. Friedel <ihf@chromium.org> |
Autotest: Change logging.warn() to logging.warning().
logging.warn() is deprecated. See
http://bugs.python.org/issue13235
Substitution was performed via
~/cros/src/third_party/autotest/files$ find ./ -type f | xargs sed -i 's/logging.warn(/logging.warning(/'
BUG=None.
TEST=There should be one-- and preferably only one --obvious way to do it.
Change-Id: Ie5665743121a49f7fbd5d1f47896a7c65e87e489
Reviewed-on: https://chromium-review.googlesource.com/198793
Commit-Queue: Ilja Friedel <ihf@chromium.org>
Tested-by: Ilja Friedel <ihf@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
aft_classes.py
|
| 6f14c44b09decb0feec1890908c5e92995d98cf9 |
05-May-2014 |
Mohammed Habibulla <moch@chromium.org> |
Tricky: Add faft config for Tricky
BUG=none
TEST=none
Change-Id: Icf133987a9158e1c62f39575db6a522698a3d285
Reviewed-on: https://chromium-review.googlesource.com/198249
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Mohammed Habibulla <moch@chromium.org>
Tested-by: Mohammed Habibulla <moch@chromium.org>
onfig/tricky.py
|
| cb7a3945a33a561db8e08ee66ec53598854172dc |
23-Apr-2014 |
David Hendricks <dhendrix@chromium.org> |
FAFT: Add Big and Blaze configs
BUG=chrome-os-partner:28249
BRANCH=none
TEST=Ran tests on Big, logs no longer show failure to find CrOS EC
Change-Id: I4b7f67629d0487cd60a68e91230b71891ff50a60
Reviewed-on: https://chromium-review.googlesource.com/196576
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: David Hendricks <dhendrix@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
onfig/big.py
onfig/blaze.py
|
| 1b67c2262820266277210e56a7baf1a2d96c7d55 |
06-Apr-2014 |
Shawn Nematbakhsh <shawnn@chromium.org> |
rambi: Decrease EC boot-to-console delay
Decrease ec_boot_to_console from 1.2s to 0.3s. This fixes a bug where EC_IN_RW
incorrectly stays high after cold-reset + reboot, due to the EC entering RW
before we reboot.
BUG=chrome-os-partner:27728, chrome-os-partner:26554
TEST=Pass FW FAFT suite on Rambi.
Change-Id: I74edb6ea021e6553119966f63024b766bfec02b4
Reviewed-on: https://chromium-review.googlesource.com/193367
Commit-Queue: Shawn Nematbakhsh <shawnn@chromium.org>
Tested-by: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/rambi.py
|
| 6727ed07dc0866af544332f15f04896f1379f4c6 |
24-Mar-2014 |
ChromeOS Developer <dparker@chromium.org> |
FAFT: Add more rambi follower board configs.
BUG=None
TEST=None
Change-Id: Ie4b8856f736a854b12864c4cf96622967629d7c5
Reviewed-on: https://chromium-review.googlesource.com/191221
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Dave Parker <dparker@chromium.org>
Tested-by: Dave Parker <dparker@chromium.org>
onfig/enguarde.py
onfig/expresso.py
onfig/gnawty.py
onfig/kip.py
onfig/quawks.py
onfig/swanky.py
|
| 4be897b5160dcb875a4daa63416a7821f5f5bbe8 |
06-Mar-2014 |
Katie Roberts-Hoffman <katierh@google.com> |
Add FAFT config for skate
Copied from spring for starters.
BUG=chrome-os-partner:26526
TEST=manually run faft
Signed-off-by: Katie Roberts-Hoffman <katierh@chromium.org>
Change-Id: Ie62d234fbde74a981644ec3cf240dc3fc49fbbe6
Reviewed-on: https://chromium-review.googlesource.com/188967
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Katie Roberts-Hoffman <katierh@chromium.org>
Tested-by: Katie Roberts-Hoffman <katierh@chromium.org>
onfig/skate.py
|
| 388f89448cf805ead4aae24d333bfa341f8606b0 |
25-Feb-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Add FAFT config file for Pi.
Adding a required faft config file for Pi. This is a direct copy of the
Pit config file.
BUG=chromium-os-partner:25503
TEST=Manual run of faft suites
Change-Id: Ia5b0cb76e9b5217d34e011f555dfb00fd5f421ac
Signed-off-by: Yusuf Mohsinally <mohsinally@google.com>
Reviewed-on: https://chromium-review.googlesource.com/187733
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/pi.py
|
| cd3a6b2c6faca4ab77aacb304e3510032ad146a4 |
24-Feb-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Disable update-engine in initialize of FAFTSequence.
No tests require update-engine and it is started in the cleanup step,
but there is no corresponding stop in initialize. Adding this for
symmetry.
BUG=None
TEST=Manually ran faft suite at desk
Change-Id: I47995b7141a2896a196decc7516c3c2a9c24e27d
Reviewed-on: https://chromium-review.googlesource.com/187672
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
aft_classes.py
|
| 8ea1991940d4080f6f0d35701912c921934183b2 |
19-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
Unset FAFT state checker during cleanup
Some tests set state_checker for convenience, and these checker don't
necessarily apply to the cleanup steps and may cause negative failure
during cleanup. To prevent that, let's unset state checker before
performing cleanup steps.
BUG=chrome-os-partner:25971
TEST=Run test on Rambi
Change-Id: I5a22aec75c5a404f8e7ecc263c8df72a6f71a871
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/186962
Reviewed-by: Mohammed Habibulla <moch@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
aft_classes.py
|
| 6dbcf9de4a5285feeef7f64ed4c4bc5cc9e309c7 |
17-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
Add firmware_FAFTPrepare test
This test is used to prepare the device for faster FAFT tests.
BUG=None
TEST=Run the test. Check GBB flags and kernel B are updated.
Change-Id: Id0e92b47066407f27d84c9dcde368c00e6a52e47
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/186860
aft_classes.py
|
| da434ba6d0ecc724d6e3d036ecb5f8b720164f86 |
12-Feb-2014 |
Shawn Nematbakhsh <shawnn@chromium.org> |
clapper/glimmer/squawks/winky: Add FAFT configs
Add board-specific FAFT configs for these Rambi-like platforms
BUG=None
TEST=Run FAFT on Squawks
Change-Id: Ide015a0e70eb33b9b7f038106bb8c4e71a754ac6
Reviewed-on: https://chromium-review.googlesource.com/186173
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Shawn Nematbakhsh <shawnn@chromium.org>
Commit-Queue: Shawn Nematbakhsh <shawnn@chromium.org>
onfig/clapper.py
onfig/glimmer.py
onfig/squawks.py
onfig/winky.py
|
| a0f5a5698213c75eb0a70910ab2a2d97e4275efd |
13-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
Restart update-engine at last of FAFT cleanup
We should complete all steps that involve a reboot before restarting
update-engine. Otherwise it'd be stopped again.
BUG=chromium:248129
TEST=Run a test and check update-engine is still running.
Change-Id: Ibe8abfc6553e2261699fa2d9b656199375bab513
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/186342
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
aft_classes.py
|
| 6f59efa78ba6765b5ebf1d847865ae5a18bbe019 |
12-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
Add use_u_boot attribute to FAFT config
This attribute indicates whether U-boot or depthcharge is used for a
platform.
BUG=None
TEST=Lint
Change-Id: I5d0c3781221cff900f5c4e587c797c58839047c2
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/186041
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/DEFAULTS.py
onfig/link.py
onfig/snow.py
onfig/spring.py
|
| bc1c0f49d70d4fc090e8714b1c8eaa19dda53bcc |
12-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
faft: restore developer mode status after a test
If we change developer mode status during a test, we should restore it
after the test is done.
BUG=chromium:215787
TEST=Switch to dev mode and run firmware_ECBootTime. Check the device is
in dev mode after the test.
Change-Id: If5e862cc811b93522d0b3fc2131ecc4e3607f15a
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/186072
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
aft_classes.py
|
| 3232cef2773bf72e6f4d12a3c7d08c35a54079ff |
07-Feb-2014 |
Gediminas Ramanauskas <gedis@google.com> |
Zako: Add faft config for Zako
BUG=none
TEST=none
Change-Id: Id611f29129fdd83634bf308715137e6251b3eb95
Reviewed-on: https://chromium-review.googlesource.com/185330
Reviewed-by: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Gediminas Ramanauskas <gedis@chromium.org>
Tested-by: Gediminas Ramanauskas <gedis@chromium.org>
onfig/zako.py
|
| 4edbc07eedd2f14d107a160d1adfa85ce345e4d7 |
11-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
faft: also check the integrity of rootfs when checking kernel
Checking kernel alone is not enough to make sure the kernel is bootable.
We also need to check if the rootfs is good. Comparing the two rootfs
copies takes too long, so we only check if the kernel is good enough to
pass dmverity check.
BUG=None
TEST=Zero out part of rootfs B and run firmware_CorruptKernelA.
Change-Id: I475464e49d8cc2ae770b8f0952735603a89bc24f
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/185811
aft_classes.py
|
| 1591894dda8f423338838f7262e57968798764c5 |
10-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
faft: restore GBB flags after tests finished
This saves the GBB flags before changing them for FAFT tests, and
restores them after the tests are done.
BUG=chromium:215787
TEST=Run a test and check the GBB flags are restored.
Change-Id: I00442fa9e5113a7ecdc22a23507ef8fa92631c5a
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/185544
aft_classes.py
|
| 6244d8ac830cf5a39762ad1908cb67d10934cf0a |
07-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
faft: restart update-engine after a FAFT test is done
update-engine must be running in order for the device to pass "Verify"
step in the lab. We need to restart it after the test is done.
BUG=chromium:251872
TEST=Run a test and check update-engine status after.
Change-Id: I892150654f36244cfe8e23fcb5214b1c8548c16f
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/185118
Reviewed-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
aft_classes.py
|
| 9393284f7bb4acfc9b82a11da18232df0b06f965 |
07-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
faft: Add methods to backup and restore kernel attributes
Some FAFT tests change kernel attributes like priority or tries flags.
We should restore them when the tests are done. Let's add methods to
backup and restore the attributes.
BUG=chromium:215787
TEST=Use the added methods in firmware_CgptState and check kernel
attributes are restored.
Change-Id: Id9d962483e6da0b209e35a9d6fe9ca4fa7505d77
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/185351
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
aft_classes.py
|
| 33ef9e0a5bb70f07c27bd9ccb2a90614f2788da5 |
07-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
faft: Add methods to backup and restore kernel
To make sure the kernel does not get changed when running a test, we
need methods to backup and restore the kernel partition.
BUG=chromium:215787
TEST=zero out kernel B and run firmware_CorruptKernelA. Check kernel B
is all zero after the test.
Change-Id: I80d4226416c53b952dc9550d045780d048bb5cef
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/185320
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
aft_classes.py
|
| 997865916c14b3035c1e806a2408e81393b9b685 |
28-Jan-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
rambi: Extend dev screen delay
Booting to dev screen takes longer than 4 seconds, and this causes test
failures. Let's extend it to 7 seconds.
BUG=chrome-os-partner:25211
TEST=Check the delay in test log
Change-Id: I83eff120445a9b4477a25b316ea1e5a46291657b
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/184111
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/rambi.py
|
| 0695ad28ef916bb21a81d18ca0c278bfd7705f71 |
21-Jan-2014 |
Mohammed Habibulla <moch@chromium.org> |
Update switch to dev mode for devices that require recovery button press
Panther/Monroe require recovery button press to switch to dev mode
(instead of pressing the enter key)
BUG=none
TEST=firmware_FAFTSetup runs
Change-Id: I0d84c5a2a9f57d7c60cc359a11e2b8505081ff6a
Reviewed-on: https://chromium-review.googlesource.com/183347
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Mohammed Habibulla <moch@google.com>
Commit-Queue: Mohammed Habibulla <moch@google.com>
onfig/DEFAULTS.py
onfig/monroe.py
onfig/panther.py
aft_classes.py
|
| 5c3baf688df7cf7802ca70f379af004e68d9e330 |
24-Jan-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
Add FAFT config for Rambi
This is needed for FAFT to run on Rambi.
BUG=chrome-os-partner:25211
TEST=Run FAFT on Rambi
Change-Id: I2f87a3ae6d16354c615e3949bda227cfcf110f79
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/183627
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/rambi.py
|
| c37468dae55040c30b630fa5add582c94df5cc8d |
21-Jan-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Additional logging to clarify FAFT tests.
Added some logging to help debug which FAFT tasks are being run.
BUG=None
TEST=Ran manually at desk
Change-Id: I2bdd587019525a35c42e6005b95ae69ff7eebe25
Reviewed-on: https://chromium-review.googlesource.com/183342
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
aft_classes.py
|
| 103441a0d4b3095c0be1e180686e65a97ebede80 |
15-Jan-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Refactoring FAFT keypress code and adding usbkm232 interface.
Cleaned up code to breakout keyboard handlers into thier own classes.
And added support to send keystrokes via usbkm232 cable, which is
required for devices that do not have an internal keyboard.
BUG=None
TEST=Manual testing at desk
Change-Id: Iae13632447695e16e1fa1ce7d29deb41dc48a7fb
Reviewed-on: https://chromium-review.googlesource.com/182539
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/DEFAULTS.py
onfig/parrot.py
onfig/stout.py
aft_classes.py
|
| 2a8c64f6da2f1ae0fd688a26de85cc30a0afecb2 |
06-Dec-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Adding a faft config file for Monroe board.
Needed for faft runs. Shawn will checkin servo side changes.
BUG=chrome-os-partner:24421
TEST=None
Change-Id: I6b48710ae885ed851838bc2da60f5f1b6be9ddb9
Reviewed-on: https://chromium-review.googlesource.com/179099
Reviewed-by: Shawn Nematbakhsh <shawnn@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/monroe.py
|
| 8d19e3c0d735d6784d6d8db650524918ace1fce5 |
21-Nov-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Add dynamic names for FAFT xmlrpc server logfiles.
Each time the server is instantiated, the logfile is overwritten.
There are cases where it is important to see what the root cause is
for random failures that happen during a test suite run.
This change only effects faft xmlrpc server instantiations. The files
are about 1.5k each. And systems are regularly reimaged, so these files
should not cause problems for storage space.
Also fixed a minor doc nit from last checkin.
BUG=None
TEST=Manual run at desk
Change-Id: I9f9bf265d4f7d66a15001e0cd5143d710be3766d
Reviewed-on: https://chromium-review.googlesource.com/177641
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
pc_proxy.py
|
| fff89d6d2366af30bbfd10b8a5293363cf665361 |
19-Nov-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Adding ability to log output when starting xmlrpc server.
The ability to see the output when xmlrpc servers are started was
broken recently and if the command errors out, there is no debugging
information that we can see.
BUG=chromium:320184
TEST=Manually ran against DUT at desk
Change-Id: I20a98927b0866a7e2a724941ee7988d177007c39
Reviewed-on: https://chromium-review.googlesource.com/177281
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
pc_proxy.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>
tils/faft_checkers.py
|
| 0abd78573234bea1cd6a248058a96f2c735d4175 |
13-Nov-2013 |
Mohammed Habibulla <moch@chromium.org> |
Panther: Add faft config for Panther
BUG=chrome-os-partner:23512
TEST=test_that -b panther <IP addr> firmware_FAFTSetup
Change-Id: I32ddf773435a30bc4423e55c9ccbd046999366af
Reviewed-on: https://chromium-review.googlesource.com/176674
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Mohammed Habibulla <moch@chromium.org>
Tested-by: Mohammed Habibulla <moch@chromium.org>
onfig/panther.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>
aft_classes.py
|
| 445f75238ef45afa79b82a6b31bdaf5eefe34a90 |
30-Oct-2013 |
Gabe Black <gabeblack@chromium.org> |
Add a nyan.py file which has the nyan platform overrides.
This is a copy of the spring file with the the name of the board changed out.
BUG=None
TEST=Reinstalled autotest and ran tried to run FAFT for nyan. It no longer
complains that nyan doesn't have a Google EC even though it does.
Change-Id: Ifd466a144f1df0dbf44496c012fdec2612fdd67e
Signed-off-by: Gabe Black <gabeblack@google.com>
Reviewed-on: https://chromium-review.googlesource.com/175038
Reviewed-by: Todd Broch <tbroch@chromium.org>
Commit-Queue: Gabe Black <gabeblack@chromium.org>
Tested-by: Gabe Black <gabeblack@chromium.org>
onfig/nyan.py
|
| 3177ca9a2169d1f048ca8ebc2ae9b2e8f0e28978 |
04-Oct-2013 |
Gediminas Ramanauskas <gedis@google.com> |
Adding FAFT config for Leon
BUG=none
TEST=FAFTSetup passes
Change-Id: I3d55b07fd5bac39e87e7fc9edaec9d12ae9994a7
Reviewed-on: https://chromium-review.googlesource.com/171925
Reviewed-by: Mohammed Habibulla <moch@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Gediminas Ramanauskas <gedis@chromium.org>
Tested-by: Gediminas Ramanauskas <gedis@chromium.org>
onfig/leon.py
|
| 5c7d1bff7e22a39e29ede0ea11686d8984d472ce |
04-Oct-2013 |
Yusuf Mohsinally <mohsinally@chromium.org> |
Add hasattr check for _old_ec_wp.
If there is a failure in the setup routine before this attribute is set, the
teardown routine will result in a attribute not found error. To prevent this,
we check if the attribute has ever been set.
BUG=None
TEST=Manual at desk run with spring device
Change-Id: I391a46b0e19a232ccba74530937b124fa14fcfde
Reviewed-on: https://chromium-review.googlesource.com/171757
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
aft_classes.py
|
| b714af08fdea1954f956c898e0f1accc845d3754 |
01-Oct-2013 |
Mohammed Habibulla <moch@chromium.org> |
Add config settings for Wolf for FAFT tests
BUG=none
TEST=manual tests on Wolf device
Change-Id: I2d113b063540380e36bf29adedf179cf8685fa44
Reviewed-on: https://chromium-review.googlesource.com/171443
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Mohammed Habibulla <moch@google.com>
Commit-Queue: Mohammed Habibulla <moch@google.com>
onfig/wolf.py
|
| 161e1c148fbaec37390c96a11e1529c5ab26862b |
17-Sep-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Reflect the method name change of rpc_disconnect
A recent refactoring changes the method name from xmlrpc_disconnect
to rpc_disconnect. This CL is to reflect this change.
BUG=chrome-os-partner:22751
TEST=Run firmware_DevModeStress passed on Spring.
Change-Id: I100922e620514dba96102477141e9a2bf446aee5
Reviewed-on: https://chromium-review.googlesource.com/169841
Reviewed-by: Vic Yang <victoryang@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Wai-Hong Tam <waihong@chromium.org>
pc_proxy.py
|
| 2b1ef4fe8ad8722989cc5a9f78a8edca8c28a5c0 |
19-Jul-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Introduce FAFTClientProxy to setup RPC smartly
This CL seprates the RPC setup stuffs to a new class FAFTClientProxy.
It reuses SiteHost XMLRPC related methods. It is also smart enough to:
- postpone the RPC connection to the first class method call;
- reconnect to the RPC server in case connection lost, e.g. reboot;
- always call the latest RPC proxy object.
BUG=chrome-os-partner:21118;chromium-os:215491
TEST=Manual
Ran the affected test cases, firmware_FAFTSetup, on Spring and passed.
Change-Id: I0d35881a270ed6d4a69cc60045d1d3e3a608b964
Reviewed-on: https://chromium-review.googlesource.com/62645
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Wai-Hong Tam <waihong@chromium.org>
aft_classes.py
pc_proxy.py
|
| 1d58c53d984e3dc0fe22f48c70edbed1c2ecbb44 |
27-Aug-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Use better naming for FAFTConfig and get_usbdisk_path_on_dut
The Config imported from faft config is renamed to FAFTConfig.
And the method get_dut_usb_dev is renamed to get_usbdisk_path_on_dut.
BUG=None
TEST=Manual
Ran firmware_SelfSignedBoot test on Spring and passed.
Change-Id: Icb528bec584a8fa813d98e5fe661913a44f90391
Reviewed-on: https://chromium-review.googlesource.com/67047
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
aft_classes.py
|
| 386712c1ce8fcf5b9e3a20b8fdde1bb9b29edc1c |
18-Jul-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Separate FAFTClient setup out from ServoTest to a new class FAFTBase
This is part of the refactoration. Make ServoTest only contain the servo
related functions. Will add the logging mechamism there.
The FAFTClient setup fuctions are now moved to a new class FAFTBase.
BUG=chrome-os-partner:21118;chromium-os:215491
TEST=Manual
Ran the affected test cases, firmware_FAFTSetup, on Spring and passed.
Change-Id: I92cac84b04d323949f086346e5d74c4bad3b1dbb
Reviewed-on: https://chromium-review.googlesource.com/62644
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
aft_classes.py
|
| f3833c7a823fef77412684bcf4c1b7ea883b864d |
23-Aug-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Adding 'platform' attribute to config object
Tests expect this attribute to exist. In order not to break the existing
tests, add the 'platform' attribute back. But long term its not certain
if this should be the place for this attribute, since its not config
exactly.
BUG=None
TEST=None
Change-Id: I77504f3e89830464c750aa5a15d5b17394c68deb
Reviewed-on: https://gerrit.chromium.org/gerrit/66802
Commit-Queue: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@google.com>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/config.py
|
| fc187827caf47a3035d2d2b762730ab8d179b3c5 |
23-Aug-2013 |
Vadim Bendebury <vbendeb@chromium.org> |
Fix usb device detection for ARM devices
The code in server.cros.faft.faft_classes.get_dut_usb_dev() uses
command 'ls /dev/sd[a-z]*' ran on the DUT with the USB stick connected
and disconnected, to determine the USB stick device. on ARM platforms
there is no other sd devices, so the shell command fails, causing test
exception and leaving the USB stick powered off.
This change makes the wildcard more broad, so that there are devices
reported by the ls command in both cases.
BUG=chrome-os-partner:21659
TEST=manual
. the following autotest does not fail on Pit anymore:
$ ~/trunk/src/scripts/run_remote_tests.sh --board=peach_pit --use_emerged \
--servo --remote=192.168.1.11 firmware_SelfSignedBoot
Change-Id: If7f1acbc91314af4133263c5d463bb621368be1a
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/66750
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
aft_classes.py
|
| 5dd414fd6c5b51e2c8a4163a0e2c044c6ca8b09b |
23-Aug-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Fix to pit platform config override file.
Removing invalid 'self'.
BUG=None
TEST=None
Change-Id: I2caaa67bf0f738995c4ef63f2e69d47642f26d3d
Reviewed-on: https://gerrit.chromium.org/gerrit/66727
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/pit.py
|
| a39f97038dfa865c7bfcea2625d516d098207066 |
16-Aug-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Refactoring config settings for devices in FAFT tests.
Created a new config system for faft tests which allow for a default file of
settings and override file for each board that requires it.
The default and override files contain a class called 'Values', in which
the config attributes are stored. The class allows for inheritence of config
values from to better organize related board settings.
The new config system provides for one 'Config' class which is the main
interface to settings for all tests. It does a cascading search, for the
requested attribute, first checking a platform specific overrides, and then
through the defaults.
Modified FAFTSequence to contain one attribute 'faft_config' which replaces
self.client_attr and self.delay which it made available to tests.
BUG=None
TEST=Manual runs of various tests at desk on link device
Change-Id: I06da7be07364d5d99bdf6b204d628ad849f8d617
Reviewed-on: https://gerrit.chromium.org/gerrit/66006
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@google.com>
onfig/DEFAULTS.py
onfig/alex.py
onfig/butterfly.py
onfig/config.py
onfig/faft_client_attribute.py
onfig/faft_delay_constants.py
onfig/falco.py
onfig/link.py
onfig/lumpy.py
onfig/parrot.py
onfig/peppy.py
onfig/pit.py
onfig/slippy.py
onfig/snow.py
onfig/spring.py
onfig/stout.py
onfig/stumpy.py
onfig/zgb.py
aft_classes.py
|
| a67e2e04780c142cd1b9c968fc620aed999f9524 |
10-Aug-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Adding missing __init__.py.
BUG=None
TEST=None
Change-Id: I7676a4b0a8fdfbe62ba020708ddd17b0e0e3c874
Reviewed-on: https://gerrit.chromium.org/gerrit/65390
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
onfig/__init__.py
|
| 08ba2458dc306fd51eb0b1c4d741f36288dfd45e |
09-Aug-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Adding a missed __init__.py file for faft/utils/ dir.
BUG=None
TEST=None
Change-Id: Iac95d8c98822e5222625e730c13946b7b8662698
Reviewed-on: https://gerrit.chromium.org/gerrit/65384
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Reviewed-by: Dennis Jeffrey <dennisjeffrey@chromium.org>
tils/__init__.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>
_init__.py
onfig/faft_client_attribute.py
onfig/faft_delay_constants.py
aft_classes.py
tils/faft_checkers.py
|