diff options
author | Vadim Bendebury <vbendeb@google.com> | 2017-02-28 17:52:23 -0800 |
---|---|---|
committer | chrome-bot <chrome-bot@chromium.org> | 2017-03-02 16:50:05 -0800 |
commit | b1afdd76bc3f7b35a2cdca817684ebe224a4c9a9 (patch) | |
tree | 454b243ceeb6c687de114463cbcc4bd4f622c81f /board/sweetberry | |
parent | 899fba96494e022f8e083611c328e7b57cf18079 (diff) | |
download | chrome-ec-b1afdd76bc3f7b35a2cdca817684ebe224a4c9a9.tar.gz |
g: enhance flash INFO api
Flash INFO access API presently is hardcoded to access the endorsement
space. To enable INFO map based rollback protection one needs to be
able to access different areas of the INFO.
The FLASH REGION3 register used by the API is in fact used for NVMEM
flash accesses too, so it is better to leave it alone and use REGION6
for the purpose of accessing of the INFO space.
The API now requires the user to specify flash offset and region size,
the size must be power of 2, the offset must be aligned at size, and
the region must not spill beyond the INFO space address range.
BRANCH=cr50
BUG=b:35774863
TEST=with the rest of the patches applied it is possible to erase the
base word in the info map segment;
reading of the endorsement space at startup still works fine.
Change-Id: I008165ee9e11a7b49985d2b30683509cf6699431
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/447965
Reviewed-by: Nagendra Modadugu <ngm@google.com>
Reviewed-by: Mary Ruthven <mruthven@chromium.org>
Diffstat (limited to 'board/sweetberry')
0 files changed, 0 insertions, 0 deletions