diff options
| author | Hung-Te Lin <hungte@chromium.org> | 2018-08-24 12:24:49 +0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2018-08-31 11:19:59 -0700 |
| commit | 75e3c5bb621cf26d7fd774a6603e224ad4120f59 (patch) | |
| tree | ac7473c8f871a5811ee3521f260cec50b9de8372 /tests/futility | |
| parent | 8d8acddf86a76702438aff5f2f8f57df3ff73dd8 (diff) | |
| download | vboot-75e3c5bb621cf26d7fd774a6603e224ad4120f59.tar.gz | |
futility: cmd_update: Add 'mainfw_act' system property
Add the system property 'mainfw_act'.
In both vboot1 and vboot2, the try-rw update process will need to figure out
what is current (active) firmware slot, which is the "mainfw_act" system
property.
BUG=chromium:875551
TEST=make futil; tests/futility/run_test_scripts.sh $(pwd)/build/futility
futility --debug update -i IMAGE --sys_prop 0;
futility --debug update -i IMAGE --sys_prop 1;
BRANCH=None
Change-Id: Ie745726107bff416549ba095a3defdd4cc98d32d
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1183652
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'tests/futility')
| -rwxr-xr-x | tests/futility/test_update.sh | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/futility/test_update.sh b/tests/futility/test_update.sh index e06bbc59..873a6f56 100755 --- a/tests/futility/test_update.sh +++ b/tests/futility/test_update.sh @@ -67,6 +67,8 @@ test_update() { cmp "${TMP}.emu" "${expected}" } +# --sys_props: mainfw_act, [wp_hw, wp_sw] + # Test Full update. test_update "Full update" \ "${FROM_IMAGE}" "${TMP}.expected.full" \ |