Re: Forcing a USB device to "ugen"

[Robert Swindells <rjs%fdy2.co.uk@localhost>]

Jason Thorpe <thorpej%me.com@localhost> wrote:
> I have a device based on the FTDI FT2232C:
>
> [ 11113285.311079] uftdi1 at uhub1 port 2 configuration 1 interface 0
> [ 11113285.311079] uftdi1: SecuringHardware.com (0x0403) Tigard V1.1 (0x6010), rev 2.00/7.00, addr 3
> [ 11113285.311079] ucom1 at uftdi1 portno 1
> [ 11113285.311079] uftdi2 at uhub1 port 2 configuration 1 interface 1
> [ 11113285.311079] uftdi2: SecuringHardware.com (0x0403) Tigard V1.1 (0x6010), rev 2.00/7.00, addr 3
> [ 11113285.311079] ucom2 at uftdi2 portno 2
>
> It's a combo device that, in addition to a standard TTL-level UART,
> has a bunch of break-out headers for doing things like SPI, SWD, and
> JTAG (in my case, I need to use JTAG for programming some Atmel
> CPLDs).  I should be able to do this with OpenOCD
> (pkgsrc/devel/openocd), but libfdti1 fails to find the device because
> libusb1 only deals in "ugen".

I thought that all FTDI devices provided JTAG etc. functionality, just
that the pins are not connected to anything in some devices.

What would be wrong with attaching an ugen to interface 1 instead of
an ucom in the ftdi driver itself?