diff options
| author | Dan Shi <dshi@chromium.org> | 2015-07-06 14:12:12 -0700 |
|---|---|---|
| committer | ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> | 2015-07-08 01:44:13 +0000 |
| commit | d6a6c927248ce16c9467dfa3f170349520cc5bc9 (patch) | |
| tree | 4b5a0557c7b8aaf12c993e44724b322ab3195563 | |
| parent | 806cc814917209f9bc8eab1d94a78f8d828aa2c5 (diff) | |
| download | chrome-ec-d6a6c927248ce16c9467dfa3f170349520cc5bc9.tar.gz | |
Add jerry to the list of BOARDS_STM32 as a short-term fix
Board jerry was removed from the list in CL 276524. The board share the same
overlay as pinky. So ideally user can call flash_ec with board set to pinky.
This applies to other veyron boards in BUG 505003 as well.
However, servo in the lab runs on ToT, and it only updates firmware of the dut
by calling flash_ec with board name retrieved from the overlay file. Also, lab
has a tool to check the servod's board and the dut's board. That is, if we
change servod to return board name pinky for servo connected to a jerry dut,
the lab script will raise a warning that the servod is running with a wrong
board.
Before we have a good design to really address the issue, I'd like to add jerry
back to flash_ec so the board can run FAFT in the lab.
BUG=chromium:505003
BRANCH=None
TEST=None
Change-Id: I155e79710f2731701af0acdfeab6089701cf52a8
Reviewed-on: https://chromium-review.googlesource.com/283494
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
| -rwxr-xr-x | util/flash_ec | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/util/flash_ec b/util/flash_ec index 97c0a33fc0..a7eef4efc2 100755 --- a/util/flash_ec +++ b/util/flash_ec @@ -50,12 +50,16 @@ BOARDS_LM4=( samus ) +# TODO(crbug.com/505003): Remove jerry, which is only present +# as a short-term fix until servod overlays for non-ToT boards +# are working in the test lab. BOARDS_STM32=( big blaze discovery glados_pd honeybuns + jerry kitty kunimitsu_pd llama |