diff options
author | Vadim Bendebury <vbendeb@chromium.org> | 2018-09-05 18:02:53 -0700 |
---|---|---|
committer | chrome-bot <chrome-bot@chromium.org> | 2018-09-27 19:44:25 -0700 |
commit | 72cd97f4b84e0076099b4a15698fc28e807e00f8 (patch) | |
tree | 226c0335f265d140113e5d3407658e62690c742f /include | |
parent | 80769acb65ddf155170b3d119fd88ec0623e68ed (diff) | |
download | chrome-ec-72cd97f4b84e0076099b4a15698fc28e807e00f8.tar.gz |
iteflash: add ability to program ITE chips over CCD
It is necessary to be able to program ITE chips using Cr50 as the USB
to I2C bridge when Closed Case Debugging (CCD) is enabled.
The existing iteflash utility already implements all logic of
translating programming commands into sequences of I2C transactions,
all what's missing is the ability to send I2C transactions over Cr50
instead of FTDI.
This patch adds a new command line option for the iteflash utility, -c
for ccd. When given, the utility instead of opening an FTDI connection
tries to find a Cr50 USB endpoint for the I2C bridge.
A common structure is introduced to communicate the properties of the
interface down the stack, such that at the lowest level, when I2C
commands need to be synthesized the correct interface is used.
Another addition is using a special I2C address to send command to
Cr50 to trigger generation of the ITE EC sync sequence (not yet
supported on the Cr50 side, implemented in the following patches).
BRANCH=none
BUG=b:75976718
TEST=verified that iteflash still operates properly - updated the EC
image on the dragonegg board. No Cr50 tests yet.
Change-Id: Ibcc052b86021c0c4b4dbccadc3fded3100c92ccf
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1212525
Reviewed-by: Scott Collyer <scollyer@chromium.org>
Reviewed-by: Jett Rink <jettrink@chromium.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions