okay, i found 'out_ep' and 'in_ep' in ftdi context struct, but why they are
not used for reset ?


2013/8/6 Anton Smirnov <[email protected]>

> Hello. I'm having an issue with libftdi and i have suspection about
> endpoints numbers.
>
> But start from the beginning, error:
>
> 08-06 16:32:16.328: WARN/System.err(15547): ftdi_usb_open_dev()
> 08-06 16:32:16.328: WARN/System.err(15547):
> usb_detach_kernel_driver_np()libusb: 0.029116 debug
> [libusb_detach_kernel_driver] interface 0
> 08-06 16:32:16.328: WARN/System.err(15547): ftdi claim interface ...
> 08-06 16:32:16.328: WARN/System.err(15547): libusb-compat debug:
> usb_claim_interface: interface 0
> 08-06 16:32:16.328: WARN/System.err(15547): libusb: 0.030246 debug
> [libusb_claim_interface] interface 0
> 08-06 16:32:16.328: WARN/System.err(15547): claiming interface using fd = 4
> 08-06 16:32:16.328: WARN/System.err(15547): ftdi_usb_reset ...
> 08-06 16:32:16.328: WARN/System.err(15547): libusb-compat debug:
> usb_control_msg: RQT=40 RQ=0 V=0 I=0 len=0 timeout=300
> 08-06 16:32:16.328: WARN/System.err(15547): libusb: 0.031222 debug
> [libusb_get_next_timeout] next timeout in 0.300000s
> 08-06 16:32:16.328: WARN/System.err(15547): libusb: 0.031527 debug
> [libusb_handle_events_timeout_completed] doing our own event handling
> 08-06 16:32:16.328: WARN/System.err(15547): libusb: 0.032046 debug
> [handle_events] poll() 2 fds with timeout in 300ms
> 08-06 16:32:16.328: WARN/System.err(15547): libusb: 0.033023 debug
> [handle_events] poll() returned 1
> 08-06 16:32:16.338: WARN/System.err(15547): libusb: 0.033389 debug
> [reap_for_handle] urb type=2 status=-32 transferred=0
> 08-06 16:32:16.338: WARN/System.err(15547): libusb: 0.033755 debug
> [handle_control_completion] handling completion status -32
> 08-06 16:32:16.338: WARN/System.err(15547): libusb: 0.034091 debug
> [handle_control_completion] unsupported control request
> 08-06 16:32:16.338: WARN/System.err(15547): libusb: 0.034366 debug
> [usbi_handle_transfer_completion] transfer 0x2915e0 has callback 0x5ccb4
> 08-06 16:32:16.338: WARN/System.err(15547): libusb: 0.034732 debug
> [ctrl_transfer_cb] actual_length=0
>
> trying to define the reason i found that the next endpoints numbers are
> used by default:
> from (usb.h):
> #define USB_ENDPOINT_IN 0x80
> #define USB_ENDPOINT_OUT 0x00
>
> from ftdi.h:
> #define FTDI_DEVICE_OUT_REQTYPE (USB_TYPE_VENDOR | USB_RECIP_DEVICE |
> USB_ENDPOINT_OUT)
> #define FTDI_DEVICE_IN_REQTYPE (USB_TYPE_VENDOR | USB_RECIP_DEVICE |
> USB_ENDPOINT_IN)
>
> actual endpoint numbers:
> 08-06 16:32:16.328: WARN/System.err(15547): avrdude: usbdev_open(): using
> read endpoint 0x81
> 08-06 16:32:16.328: WARN/System.err(15547): avrdude: usbdev_open(): using
> write endpoint 0x02
>
> the problem is that i'm having different endpoints values and it's FTDI
> device definitely.
> since there is no way to set endpoints for my usb device i have the next
> question.
>
> 1. Why endpoints have such values by default?
> 2. How should i change them for libftdi correctly as i can't see any
> methods for this?
>
> Thanks in advance,
> Anton.
>
>
>


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to [email protected]   

Reply via email to