diff options
| author | Hung-Te Lin <hungte@chromium.org> | 2019-03-11 15:39:14 +0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-03-12 10:38:56 -0700 |
| commit | 304aa429c1a04cda3ab2ce37b9e31af84405bfca (patch) | |
| tree | 52d1c3694afa911a7f98b415f596aa1ac7f7aacc /scripts/image_signing/set_channel.sh | |
| parent | 2798b3bf39a3204385887c705ccfebc78fd07e48 (diff) | |
| download | vboot-304aa429c1a04cda3ab2ce37b9e31af84405bfca.tar.gz | |
futility: updater: Unit test for preserving sections using FMAP flags
In CL:1495054 the updater has different logic when the firmware image
has FMAP_AREA_PRESERVE in FMAP flags. This needs to be verified in unit
test.
The new test tries to set 010=0x08 (FMAP_AREA_PRESERVE) in RO_VPD area flag
but not RW_VPD, with RO and RW VPD both being provisioned in source
(from) image. The legacy path would update both while the new path will
only update RO, so we can make sure the flag-based preservation is
working as expected.
BUG=chromium:936768
TEST=make futil; tests/futility/run_test_scripts.sh $(pwd)/build/futility
BRANCH=None
Change-Id: I07d232444344397b80344ccc9b56f8af3256e043
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1514452
Reviewed-by: Joel Kitching <kitching@chromium.org>
Diffstat (limited to 'scripts/image_signing/set_channel.sh')
0 files changed, 0 insertions, 0 deletions