Re: [OpenOCD-user] FT2232 device

[Trampas S. <tr...@gm...>]

I have used the FTDI programming tool to name the FT2232H device "Misfit"

Using Zadig the composite device is using the usbccgp driver:
[image: Inline image 2]

Interface 0 of the device is using WinUSB
[image: Inline image 3]

interface 1 is using FTDIBUS serial driver:
[image: Inline image 4]


Here is my interface configuration script:

interface ftdi

ftdi_device_desc "Misfit (Interface 0)"
ftdi_vid_pid 0x0403 0x6010

transport select swd

#ftdi_layout_init first word is initial data level, second is direction for
direction a "1" is output, "0" is input
#
ftdi_layout_init 0x0030 0x1F3b
ftdi_layout_signal LED -ndata 0x0800
ftdi_layout_signal LED2 -ndata 0x1000

ftdi_layout_signal nTRST -data 0x0010
ftdi_layout_signal nSRST -noe 0x0020

ftdi_layout_signal SWD_EN -data 0x0200


When I try and connect using OpenOCD I get the following errors:


C:\Program Files\GNU ARM
Eclipse\OpenOCD\0.10.0-201601101000-dev\bin>openocd_old.exe -f "C:\Program
Files\GNU ARM
Eclipse\OpenOCD\0.10.0-201601101000-dev\scripts\interface\ftdi\misfit_swd.cfg"
-f "C:\Program Files\GNU ARM
Eclipse\OpenOCD\0.10.0-201601101000-dev\scripts\board\atmel_samd21g18.cfg"
GNU ARM Eclipse 64-bits Open On-Chip Debugger
0.10.0-dev-00287-g85cec24-dirty (2016-01-10-10:13)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : FTDI SWD mode enabled
Warn : Interface already configured, ignoring
none separate
adapter speed: 400 kHz
cortex_m reset_config sysresetreq
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6010, description
'Misfit (Interface 0)' and serial '*'


>From looking at the code it appears that it looks for the devices with
matching VID/PID's and then looks for matching description.  For the
FT2232H I think (not confirmed) that there should be three devices reported
with the same VID/PID (the composite, Interface 0, Interface 1). From what
I have read the order that these devices are parsed is not fixed, ie
interface 2 could be the first device which would print out the "Error:
libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" as it does not have
WinUSB driver.  However the code should eventually find the correct
interface and work, but does not seem to.

I am trying to get the code to build on windows at the moment to include
more information when the description does not match, it seems that on
windows the description is not consistent for example in Zadig it as shown
above, however in device manager it is shown as:
[image: Inline image 5]

I have tried both "Misfit" and "Misfit (Interface 0)", but neither works.

I would appreciate any help or suggestions..  Until then I am trying to
compile under cygwin so I can add more diagnostic messages to figure out
what is going on.  Not the only guides I found for compiling on windows are
very old, version 0.5, and it appears a lot has changed since then.

Thanks



On Sun, Jul 31, 2016 at 4:25 PM, Trampas Stern <tr...@gm...> wrote:

> I have a FT2232 device I am trying to use where the first channel is JTAG
> and second is used for debug UART.
>
> When I configure the first channel for WinUSB driver OpenOCD can not
> connect. When I configure the parent of the composite device to use WinUSB
> OpenOCD will connect but I loose the UART/com port.   I was wondering if I
> am missing something or if it is even possible to use the second port on
> the FT2232 with OpenOCD connected to first port?
>
> Thanks
> Trampas
>