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