diff options
author | Dino Li <Dino.Li@ite.com.tw> | 2018-04-10 11:37:53 +0800 |
---|---|---|
committer | chrome-bot <chrome-bot@chromium.org> | 2018-04-10 19:13:29 -0700 |
commit | 3a96c3cec4754abf953709b4f19c03a062c4d04a (patch) | |
tree | d8a66184da51c50449097a457b5822ba044c0389 /COMMIT-QUEUE.ini | |
parent | 3a9b89116fd0b3e358706f9c5822d4ee944978b6 (diff) | |
download | chrome-ec-3a96c3cec4754abf953709b4f19c03a062c4d04a.tar.gz |
iteflash: Continue call ftdi_read_data() until all data is read
We found a symptom that iteflash always programming EC failed
on a specific host machine.
For this failed case, it is caused by the incomplete read from
ftdi_read_data(). For example, we want to read 32 bytes by just
call ftdi_read_data() one time, but ftdi_read_data() may return
(number of bytes read) 10 or 20 but just not 32.
This change will call ftdi_read_data() again and again until all
data is read.
Change draw_spinner() function to use fprintf().
We will show percentage increase from 0 percent to 100 percen
during verifying.
Change of flash_ec script:
Move operations of reinitialize ftdi_i2c interface to cleanup()
and we won't miss them if programming is failed.
BUG=none
BRANCH=none
TEST=To run iteflash on that host machine and flashing is done.
Change-Id: Ifa374652870737c8231fce5a699abe033a1f0237
Signed-off-by: Dino Li <Dino.Li@ite.com.tw>
Reviewed-on: https://chromium-review.googlesource.com/979903
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Vijay P Hiremath <vijay.p.hiremath@intel.com>
Tested-by: Jett Rink <jettrink@chromium.org>
Reviewed-by: Vijay P Hiremath <vijay.p.hiremath@intel.com>
Reviewed-by: Jett Rink <jettrink@chromium.org>
Diffstat (limited to 'COMMIT-QUEUE.ini')
0 files changed, 0 insertions, 0 deletions