Re: [OpenOCD-devel] Bug#793214: openocd: OpenRD Ultimate unsupported since removal of ft2232 (so >=0.8.0)

[Andreas F. <and...@gm...>]

On Wed, Aug 10, 2016 at 4:55 AM, Benjamin Rodgers <
ben...@ve...> wrote:

> This issue appears to be affecting me as well while trying to connect to a
> DreamPlug.
>
>
Interesting. Different hardware but both use the feroceon target (rare) and
both use "ftdi_channel 1" (rare). I wonder which is the key to the problem.


>
> I compiled OpenOCD 0.9.0 from source first without "--enable-legacy-ft2232_libftdi"
> to confirm no change in behavior, and then with "--enable-legacy-ft2232_libftdi".
> With a couple caveats, it's actually working now.
>
>

>
> Caveat 2:  When I don't have a serial connection open (screen /dev/ttyUSB0
> 115200), everything works great.  When I do, OpenOCD periodically chokes.
> This may be related to my hardware configuration (Debian Jessie as set up
> by Vagrant debian/jessie64 running on VirtualBox on a Mac), but I'm
> mentioning it just in case others experience similar behavior.
>
> > Error: ftdi_write_data: usb bulk write failed
> > Error: couldn't write MPSSE commands to FT2232
> > Polling target feroceon.cpu failed, trying to reexamine
> > Info : Embedded ICE version 0
> > Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
> > For reference, the telltale
>
>
This symptom was common with the ft2232 adapter driver (for several
reasons) and was part of the motivation for the full rewrite. We will not
fix issues with the deprecated ft2232 driver upstream, in fact we have a
patch pending to purge it completely. Now that we know that the same setup
works with ft2232 but not with ftdi, let's focus on getting the latter
working.


>
> On Thu, 23 Jul 2015 00:57:21 +0200 Andreas Fritiofson <
> an...@fr...> wrote:
> > On Wed, 22 Jul 2015 14:17:31 +0100 Philip Hands <ph...@ha...> wrote:
> > > I notice that running openocd causes the /dev/ttyUSB0 device to
> disapear,
> > > so it's certainly doing something, even if it's not very useful.
> >
> > OpenOCD detaches the kernel driver on the selected interface (FTDI
> channel)
> > which might serve a serial port if so configured. Do you really have a
> tty
> > on the same interface/channel as the JTAG circuitry? Channel A *should*
> be
> > unaffected by OpenOCD if "ftdi_channel 1" is selected.
>
> With the legacy driver "/dev/ttyUSB0" is no longer disappearing upon
> running OpenOCD.  It was disappearing with the FTDI driver.
>
>
Can you send the output of "lsusb -v -d 0x9e88:0x9e8f" and whatever adds to
"dmesg" after plugging in the adapter and starting openocd (beginning with
the line "new full-speed USB device number...")?


> For reference, here is the output of OpenOCD with the FTDI driver.
>

> > vagrant@jessie:~/a/openocd-0.9.0$ src/openocd -f
> tcl/board/sheevaplug.cfg -s tcl
>

Please add "-d" to get a verbose log. Also, if you compile from source
anyway, use the git master if possible (for easier matching the log to the
code).

Regards,
Andreas Fritiofson