diff options
author | Hung-Te Lin <hungte@chromium.org> | 2018-08-21 18:34:04 +0800 |
---|---|---|
committer | chrome-bot <chrome-bot@chromium.org> | 2018-08-31 05:22:46 -0700 |
commit | 09c1c22dff11a588e9f27c57c4574930f2e168dd (patch) | |
tree | 782d7f4f3b680001084906ab071c8a74be7b36c3 /tests/futility | |
parent | 8c3a895e7f7ecef9147ffd8b421626db97216d6f (diff) | |
download | vboot-09c1c22dff11a588e9f27c57c4574930f2e168dd.tar.gz |
futility: cmd_update: Access system firmware using external flashrom
To manipulate the firmware contents on device, we need to access the
flash chipset (usually via SPI) on system. The `host_flashrom` provides
a way to call external program "flashrom" for reading and writing
firmware. So the `update_firmware` can now load "system current
firmware" using flashrom.
Note in the future we may want to statically link the flashrom as
library so there won't be external dependency.
BUG=chromium:875551
TEST=make futil; futility update -i IMAGE
tests/futility/run_test_scripts.sh $(pwd)/build/futility
BRANCH=None
Change-Id: I52f2d4fe4fe4dd660f762a5a75e3367820717e19
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1183650
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'tests/futility')
-rwxr-xr-x | tests/futility/test_update.sh | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/tests/futility/test_update.sh b/tests/futility/test_update.sh index c7ade51a..aaf46904 100755 --- a/tests/futility/test_update.sh +++ b/tests/futility/test_update.sh @@ -16,6 +16,6 @@ cd "$OUTDIR" set -o pipefail # Test command execution. -"${FUTILITY}" update -i "${LINK_BIOS}" | - grep "RO:${LINK_VERSION}, RW/A:${LINK_VERSION}, RW/B:${LINK_VERSION}" -"${FUTILITY}" --debug update -i "${LINK_BIOS}" | grep 8388608 + +# The updater is now currently always loading system firmware using flashrom(8) +# and can't be tested until an emulation interface is implemented. |