summaryrefslogtreecommitdiff
path: root/util/build.mk
diff options
context:
space:
mode:
authorAlec Berg <alecaberg@chromium.org>2014-08-14 18:31:05 -0700
committerchrome-internal-fetch <chrome-internal-fetch@google.com>2014-08-26 23:06:23 +0000
commite913bc15b8a631757b362da09fc1385a7f509def (patch)
tree166afea132ba5e162988cb5346eeb48ba054d1a8 /util/build.mk
parentb22c10ce2e5d8186cff4623dbf6fb18ee6a62017 (diff)
downloadchrome-ec-e913bc15b8a631757b362da09fc1385a7f509def.tar.gz
samus: add host commands for flashing zinger RW
This adds a new host commmand for sending RW updates to PD devices. The host command has a variety of sub-commands for performing the update, including: erase RW, reboot, write new hash, write flash. To program zinger RW, you should send host commands in this order: write new hash to all 0's reboot (zinger boots into RO since RW hash doesn't match) erase RW write flash write new hash to match contents of RW reboot This also adds an ectool command to write a new RW. Just pass it the RW .flat or .bin file. BUG=chrome-os-partner:31361 BRANCH=none TEST=ectool --dev=1 --interface=lpc flashpd 0 0 zinger.RW.flat Change-Id: Ia81615001b83ad7ee69b1af2bf1d7059177cde04 Signed-off-by: Alec Berg <alecaberg@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/213239 Reviewed-by: Randall Spangler <rspangler@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 0cd5cbecc8..f0e3c6c17e 100644
--- a/util/build.mk
+++ b/util/build.mk
@@ -16,7 +16,7 @@ comm-objs+=comm-lpc.o
else
comm-objs+=comm-i2c.o
endif
-ectool-objs=ectool.o ectool_keyscan.o misc_util.o ec_flash.o $(comm-objs)
+ectool-objs=ectool.o ectool_keyscan.o misc_util.o ec_flash.o $(comm-objs) ../common/sha1.o
lbplay-objs=lbplay.o $(comm-objs)
burn_my_ec-objs=ec_flash.o $(comm-objs) misc_util.o