diff options
| author | Vadim Bendebury <vbendeb@chromium.org> | 2019-05-15 15:08:40 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-05-17 18:37:33 -0700 |
| commit | 8a411be5297f9886e6ee8bf1fdac7fe6b7e53667 (patch) | |
| tree | c56bc864353bb72102cc70e48a1080c445ded405 /util | |
| parent | cd45a75e8c0dea45b94dc530fde7c86cc698fd2d (diff) | |
| download | chrome-ec-8a411be5297f9886e6ee8bf1fdac7fe6b7e53667.tar.gz | |
g: do not destroy manufacturing space by flasherase
When modifying flasherase behavior last time around, it was mistakenly
presumed that the manufacture_space field was set during Chrome OS
device manufacturing. In fact it is set during chip manufacture and
should be preserved.
BRANCH=none
BUG=b:132720245
TEST=using a device with H1 with cert seeds present:
- install CR50_DEV=1 image containing this patch
- install a recent prod image (it is not yet running, as its
version is lower than the ToT)
- on Cr50 console run
. flasherase
. rollback
- observe the released image start and successfully complete TPM
manufacture process.
Change-Id: Id028ffc51bb69810a0564c915b1be944ff5f1d89
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1615422
Reviewed-by: Mary Ruthven <mruthven@chromium.org>
Diffstat (limited to 'util')
0 files changed, 0 insertions, 0 deletions