summaryrefslogtreecommitdiff
path: root/util/build.mk
diff options
context:
space:
mode:
authorVincent Palatin <vpalatin@chromium.org>2012-05-30 20:14:14 +0000
committerGerrit <chrome-bot@google.com>2012-05-31 16:28:06 -0700
commitfbfd828b9a28f4e91fc100ef9e474f590acc7989 (patch)
tree1716fca236e7e28ea5762380808385d6522d7ec4 /util/build.mk
parent26b4a9e1a0b104a16154eb03f9d3ea4fab134252 (diff)
downloadchrome-ec-fbfd828b9a28f4e91fc100ef9e474f590acc7989.tar.gz
simple and self-contained EC flashing tool
This produces a host binary running on the application processor and which is able to re-flash th EC firmware over the AP-to-EC link (either LPC or I2C). The payload (ie the EC firmware) to use is embedded inside the flasher binary. This is just aimed at testing and developer upgrade. The auto-update flow is using flashrom. Signed-off-by: Vincent Palatin <vpalatin@chromium.org> BUG=None TEST=build for link/daisy/snow/bds and tests On Snow, run burn_my_ec from the serial console and see that the EC was correctly re-flashed. Change-Id: I7f90e773678a7ef3d8dc6dbacf54e80f3294607b Reviewed-on: https://gerrit.chromium.org/gerrit/24236 Reviewed-by: David Hendricks <dhendrix@chromium.org> Tested-by: Vincent Palatin <vpalatin@chromium.org> Reviewed-by: Randall Spangler <rspangler@chromium.org> Commit-Ready: Vincent Palatin <vpalatin@chromium.org>
Diffstat (limited to 'util/build.mk')
-rw-r--r--util/build.mk2
1 files changed, 1 insertions, 1 deletions
diff --git a/util/build.mk b/util/build.mk
index 28257b5903..fc021471f2 100644
--- a/util/build.mk
+++ b/util/build.mk
@@ -6,7 +6,7 @@
# Host tools build
#
-host-util-bin=ectool lbplay
+host-util-bin=ectool lbplay burn_my_ec
ifeq ($(CONFIG_LPC),y)
host-util-common=comm-lpc
else