diff options
| author | Jonathan McDowell <noodles@earth.li> | 2017-08-27 19:12:21 +0100 |
|---|---|---|
| committer | Spencer Oliver <spen@spen-soft.co.uk> | 2017-10-03 11:20:18 +0100 |
| commit | f95f8b70fbd0f7e9c91a2d9006b1abb2dd07ebf2 (patch) | |
| tree | f459c087ec0f0bb713cc81920ef7cd7b1d45d887 /tcl/interface | |
| parent | e8b6aaa8e59208aea6cead31760895d67c1226ee (diff) | |
| download | riscv-openocd-f95f8b70fbd0f7e9c91a2d9006b1abb2dd07ebf2.zip riscv-openocd-f95f8b70fbd0f7e9c91a2d9006b1abb2dd07ebf2.tar.gz riscv-openocd-f95f8b70fbd0f7e9c91a2d9006b1abb2dd07ebf2.tar.bz2 | |
tcl/interface/ftdi/sheevaplug: Fix FTDI channel configuration
The migration from the old ft2232 driver to the new generic ftdi driver
ended up breaking support for the SheevaPlug device. The old driver
defaulted to channel 1, but numbered the channels 1 to 4. The new driver
starts at 0. The SheevaPlug JTAG is on interface A (interface B is the
serial console), so it should be using channel 0. Fix this. Confirmed
as working; serial console remains available and a new u-boot image can
be transferred across using the JTAG link.
See also Debian Bug#837989; https://bugs.debian.org/837989
Change-Id: I4ac2bfeb0d1e7e99d70fa47dc55f186e6af2c542
Signed-off-by: Jonathan McDowell <noodles@earth.li>
Reviewed-on: http://openocd.zylin.com/4206
Reviewed-by: Paul Fertser <fercerpav@gmail.com>
Tested-by: jenkins
Diffstat (limited to 'tcl/interface')
| -rw-r--r-- | tcl/interface/ftdi/sheevaplug.cfg | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tcl/interface/ftdi/sheevaplug.cfg b/tcl/interface/ftdi/sheevaplug.cfg index f299f27..625aad3 100644 --- a/tcl/interface/ftdi/sheevaplug.cfg +++ b/tcl/interface/ftdi/sheevaplug.cfg @@ -7,7 +7,7 @@ interface ftdi ftdi_device_desc "SheevaPlug JTAGKey FT2232D B" ftdi_vid_pid 0x9e88 0x9e8f -ftdi_channel 1 +ftdi_channel 0 ftdi_layout_init 0x0608 0x0f1b ftdi_layout_signal nTRST -data 0x0200 |