| 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>
/external/autotest/server/cros/faft/config/kunimitsu.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>
/external/autotest/server/cros/faft/config/kunimitsu.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>
/external/autotest/server/cros/faft/config/kunimitsu.py
|