summaryrefslogtreecommitdiff
path: root/board/kevin
diff options
context:
space:
mode:
authorVadim Bendebury <vbendeb@chromium.org>2019-12-18 16:14:36 -0800
committerCommit Bot <commit-bot@chromium.org>2019-12-19 02:01:24 +0000
commitc4e8fffe2024108ed4373f910a5b68291aa3802e (patch)
treec1ebb980e657865ac92b537e34c58ec98c13ec19 /board/kevin
parentfa6119dc2cd69e711e9127241c2736e57706321c (diff)
downloadchrome-ec-c4e8fffe2024108ed4373f910a5b68291aa3802e.tar.gz
SQA images should allow support rollback to 0.0.22
Rolling back to 0.0.22 requires erasing the INFO1 rollback protection space, as current RW level is at two, and 0.0.22 is at one. The only way to erase INFO1 is to run a node locked prod signed 0.3.22 image. But 0.3.22 will destroy board ID along with the rollback spaces AND it is not capable of rollback, so to roll back to a lower than 0.3.22 version one still needs to run the SQA image. 0.3.22 will not allow to restore the Board ID either. Another problem is that SQA image would update the rollback INFO1 space, thus again preventing 0.0.22 from running. This patch alleviates the situation by allowing the SQA images to write Board ID fields and preventing SQA images from updating rollback space in INFO1. BRANCH=cr50 BUG=b:146522336 TEST=with the new image was able to downgrade a device from 0.4.24 to 0.0.22 Change-Id: I8babf15ae32036dc612ae9c808c773a2b3355762 Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1975092 Reviewed-by: Andrey Pronin <apronin@chromium.org>
Diffstat (limited to 'board/kevin')
0 files changed, 0 insertions, 0 deletions