On Tue, 3 Mar 2009, Jon Smirl wrote:
> On Tue, Mar 3, 2009 at 9:58 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote:
> > On Tue, 3 Mar 2009, Jon Smirl wrote:
> > This is the problem: The jtag program tries to do an unnecessary
> > Set-Config. If that call were removed from the program then it ought
> > to work just fine. If the Set-Config call were allowed to proceed, it
> > would mess up your terminal connection anyway.
>
> libftdi ftdi_usb_open_dev() appears to work as it was meant to....
> First use of the device by urjtags fails...
>
> ioctl(3, USBDEVFS_SUBMITURB, 0x7fff9c5185c0) = -1 ENOENT (No such file
> or directory)
> write(1, "usb bulk -2\n", 12usb bulk -2
> ) = 12
> write(1, "seq_purge(): ftdi_read_data() fa"..., 59seq_purge():
> ftdi_read_data() failed: usb bulk read failed
> ) = 59
>
>
> From urjtag....
>
> static int
> seq_purge( struct ftdi_context *fc, int purge_rx, int purge_tx )
> {
> int r;
> unsigned char buf;
>
> #ifndef LIBFTDI_UNIMPLEMENTED
> if ((r = ftdi_usb_purge_buffers( fc )) < 0)
> printf( _("%s(): ftdi_usb_purge_buffers() failed: %s\n"),
> __FUNCTION__, ftdi_get_error_string( fc ) );
> if (r >= 0) if ((r = ftdi_read_data( fc, &buf, 1 )) < 0)
> printf( _("%s(): ftdi_read_data() failed: %s\n"),
> __FUNCTION__, ftdi_get_error_string( fc ) );
> #else /* not yet available */
There's not enough information here to tell what's going on. To get
more details you should build a kernel with CONFIG_USB_DEBUG enabled
and also turn on usbcore's usbfs_snoop module parameter. In addition
it wouldn't hurt to use usbmon while testing the program.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
