diff options
| author | Shamile Khan <shamile.khan@intel.com> | 2015-09-25 16:27:42 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2015-09-29 14:42:05 -0700 |
| commit | 1092919c51101cdbee266f21a493d95c7f0cd77c (patch) | |
| tree | 418255eb04279dfa0a45cea572669d93e547bcff /include | |
| parent | 9104bd94bb7a4da3088d73a22b97364b077616b1 (diff) | |
| download | chrome-ec-1092919c51101cdbee266f21a493d95c7f0cd77c.tar.gz | |
mec1322: Ensure flash operation has completed before returning.
When flashrom performs a flash read following an erase and we do not
wait in between for the erase to complete, we read 0x00 instead of
0xFF. Flashrom detects this and does not proceed further. Inserting
a wait after erase solves this issue.
Also added a wait following a flash write operation to preempt future
issues, and moved spi_flash_wait() calls from Host Command APIs to
lower level spi_flash_* functions.
BUG=chrome-os-partner:43160
BRANCH=none
TEST=Manually tested on Kunimitsu FAB3.
flashrom -p ec -w ec.bin is successful
Signed-off-by: Shamile Khan <shamile.khan@intel.com>
Change-Id: I00925aa2da3709a6f3e73a40543b079112906e0a
Signed-off-by: Shamile Khan <shamile.khan@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/302683
Reviewed-by: Shawn N <shawnn@chromium.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions