Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

2016-11-05 Thread Andreas Fritiofson
On Sat, Nov 5, 2016 at 11:49 AM, Andreas Fritiofson < andreas.fritiof...@gmail.com> wrote: > > Well, I assume other people have successfully used that config file before > Specifically https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751372#40

Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

2016-11-05 Thread Andreas Fritiofson
On Thu, Oct 27, 2016 at 2:35 PM, Arnaud Patard wrote: > Hi, > I've modified the > /usr/share/openocd/scripts/interface/ftdi/sheevaplug.cfg file to use > ftdi_channel 0 and not 1. With that change, I was able to use openocd, > Well, I assume other people have

Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

2016-10-27 Thread Rtp
Hi, Wanted to try a new uboot on my guruplug server with openocd 0.9.0-1+b1 and my SheevaPlug JTAGKey FT2232D device. I got very similar bug. I've modified the /usr/share/openocd/scripts/interface/ftdi/sheevaplug.cfg file to use ftdi_channel 0 and not 1. With that change, I was able to use

Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

2016-09-17 Thread David Madore
On Sat, Sep 17, 2016 at 11:18:20PM +0300, Paul Fertser wrote: > Hm, can't see anything good about it... Ah, sorry, as I mentioned, behaviour is somewhat erratic even with openocd-0.5.0. This log is definitely good (I was able to upload U-Boot). Maybe the comparison between the two can be

Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

2016-09-17 Thread Paul Fertser
On Fri, Sep 16, 2016 at 11:59:59PM +0200, David Madore wrote: > Open On-Chip Debugger 0.5.0 (2016-09-16-09:33) ... > Error: 217 472 core.c:945 jtag_examine_chain_check(): JTAG scan chain > interrogation failed: all zeroes > Error: 218 472 core.c:946 jtag_examine_chain_check(): Check JTAG

Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

2016-09-16 Thread David Madore
On Fri, Sep 16, 2016 at 06:25:27PM +0300, Paul Fertser wrote: > In this case it would help to see -d3 output. Attached are the output of /tmp/openocd-0.5.0/src/openocd -s /tmp/openocd-0.5.0/tcl -f /tmp/openocd-0.5.0/tcl/board/sheevaplug.cfg -d3 ("openocd-good.log"), which is version 0.5.0-1

Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

2016-09-16 Thread Paul Fertser
On Fri, Sep 16, 2016 at 12:22:12PM +0200, David Madore wrote: > > The error you report seems to be fixed post-0.8.0, but before 0.9.0, > > in v0.8.0-142-geab9af1 . So it looks as if you're trying to use 0.9.0 > > with scripts from 0.8.0. > > Ah, indeed, PEBCK for that part, I forgot to pass a -s

Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

2016-09-16 Thread David Madore
On Fri, Sep 16, 2016 at 11:13:53AM +0300, Paul Fertser wrote: > On Fri, Sep 16, 2016 at 09:55:21AM +0200, David Madore wrote: > > A SheevaPlug JTAGKey FT2232D (USB identifiers 9e88:9e8f) being > > Please also provide lsusb -vvv data for this device. Bus 003 Device 002: ID 9e88:9e8f Device

Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

2016-09-16 Thread Paul Fertser
Hello, On Fri, Sep 16, 2016 at 09:55:21AM +0200, David Madore wrote: > A SheevaPlug JTAGKey FT2232D (USB identifiers 9e88:9e8f) being Please also provide lsusb -vvv data for this device. > worked fine with it: ... > Error: JTAG scan chain interrogation failed: all zeroes No, this doesn't look

Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

2016-09-16 Thread David Madore
Package: openocd Version: 0.8.0-4 (I am reporting this against openocd version 0.8.0-4 because that is what is found in Debian jessie, currently stable, but I also tried 0.9.0-1+b1, the version currently in sid.) A SheevaPlug JTAGKey FT2232D (USB identifiers 9e88:9e8f) being connected, version