summaryrefslogtreecommitdiff
path: root/tests/futility/test_update.sh
diff options
context:
space:
mode:
authorHung-Te Lin <hungte@chromium.org>2018-08-21 18:01:57 +0800
committerchrome-bot <chrome-bot@chromium.org>2018-08-31 05:22:45 -0700
commit8c3a895e7f7ecef9147ffd8b421626db97216d6f (patch)
treeb639a5f77df0e76f672dcb4328a2e6d37a861d5c /tests/futility/test_update.sh
parent6de8d9a5b1a84a7ed93eda6bdb11dcd4995d110a (diff)
downloadvboot-8c3a895e7f7ecef9147ffd8b421626db97216d6f.tar.gz
futility: cmd_update: Process FMAP and parse image version
Add `find_firmware_section` and `firmware_section_exists` utility functions to manipulate FMAP based sections easily. It is used by parsing of image version strings, which helps indicating the firmware versions going to be updated. BUG=chromium:875551 TEST=make futil; futility update -i /build/eve/firmware/image.bin tests/futility/run_test_scripts.sh $(pwd)/build/futility BRANCH=None Change-Id: I458fa8c31c45dbbd29614c3d6ccd586e46a3ed0b Signed-off-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1183649 Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'tests/futility/test_update.sh')
-rwxr-xr-xtests/futility/test_update.sh4
1 files changed, 3 insertions, 1 deletions
diff --git a/tests/futility/test_update.sh b/tests/futility/test_update.sh
index 6aa12ceb..c7ade51a 100755
--- a/tests/futility/test_update.sh
+++ b/tests/futility/test_update.sh
@@ -8,6 +8,7 @@ TMP="$me.tmp"
# Test data files
LINK_BIOS="${SCRIPTDIR}/data/bios_link_mp.bin"
+LINK_VERSION="Google_Link.2695.1.133"
# Work in scratch directory
cd "$OUTDIR"
@@ -15,5 +16,6 @@ cd "$OUTDIR"
set -o pipefail
# Test command execution.
-"${FUTILITY}" update
+"${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