diff options
author | Mulin Chao <mlchao@nuvoton.com> | 2017-05-05 17:38:56 +0800 |
---|---|---|
committer | chrome-bot <chrome-bot@chromium.org> | 2017-05-12 20:58:09 -0700 |
commit | f9c201e93c45f008b79ce63c1ec276ede05146f0 (patch) | |
tree | b8c8f927e2ce59370b00dedc12129b45d308aa46 /board/eve/board.h | |
parent | a30bb73e783cac43d9d7583a38bfe72bb2d41478 (diff) | |
download | chrome-ec-stabilize-9554.B.tar.gz |
npcx: flash: Add write-protect support for internal flash of npcx7 ecstabilize-9554.B
In order to support write-protect mechanism for the internal flash
of npcx7 ec, WP_IF, bit 5 of DEV_CTL4, is used to achieve this by
controlling the WP_L pin of internal flash. During ec initialization
or any utilities related to access status registers, we'll protect them
if WP_L is active. Please notice the type of WP_IF is R/W1S. It means we
only can unlock write protection of internal flash by rebooting ec.
This CL also includes:
1. Add protect_range array of npcx7's internal flash (W25Q80) for
write-protect mechanism.
2. Add bypass of bit 7 of DEVCNT.
BRANCH=none
BUG=none
TEST=No build errors for all boards using npcx5 series. (Besides gru)
Build poppy board and upload FW to platform. No issues found.
Passed flash write-protect checking on npcx796f evb.
Change-Id: I0e669ce8b6eaebd85e062c6751e1f3dd809e21e2
Signed-off-by: Mulin Chao <mlchao@nuvoton.com>
Reviewed-on: https://chromium-review.googlesource.com/501727
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'board/eve/board.h')
0 files changed, 0 insertions, 0 deletions