Closed dpeddi closed 2 years ago
interesting reading: https://sourceforge.net/p/libusb/mailman/message/35965754/
Trying now with your Debian-USBProxy.img.xz but I get same issue...
interesting reading: https://sourceforge.net/p/libusb/mailman/message/35965754/
That is indeed interesting. I'm also experiencing these errno=22 errors with a simple usb<->rs232 device :(
libusb: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 64
libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
libusb: debug [handle_events] poll() 3 fds with timeout in 60000ms
libusb: debug [handle_events] poll() returned 1
libusb: debug [reap_for_handle] urb type=3 status=0 transferred=2
libusb: debug [handle_bulk_completion] handling completion status 0 of bulk urb 1/1
libusb: debug [handle_bulk_completion] last URB in transfer --> complete!
libusb: debug [usbi_handle_transfer_completion] transfer 0x22fe600 has callback 0xb6bbfbd9
libusb: debug [sync_transfer_cb] actual_length=2
libusb: debug [libusb_free_transfer] transfer 0x22fe600
libusb: debug [libusb_alloc_transfer] transfer 0x22fe600
libusb: debug [libusb_submit_transfer] transfer 0x22fe600
libusb: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 64
gadgetfs: 1 events received
Sending ACK
LibUSB> 40 09 10 00 00 00 00 00
libusb: error [submit_bulk_transfer] submiturb failed error -1 errno=22
libusb: debug [submit_bulk_transfer] first URB failed, easy peasy
libusb: debug [libusb_free_transfer] transfer 0x22fe600
Transfer error receiving on EP81 (xfertype 2): Input/Output Error
Which board and kernel are you using?
debian@beaglebone:~$ cat /proc/device-tree/model
TI AM335x BeagleBone Black
debian@beaglebone:~$
debian@beaglebone:~$ uname -a
Linux beaglebone 4.9.52-ti-r64 #1 SMP PREEMPT Sat Sep 30 00:11:40 UTC 2017 armv7l GNU/Linux
debian@beaglebone:~$
cat /proc/device-tree/model TI AM335x BeagleBone Black root@beaglebone:~# root@beaglebone:~# uname -a Linux beaglebone 4.4.88-ti-r125 #1 SMP Thu Sep 21 19:23:24 UTC 2017 armv7l GNU/Linux root@beaglebone:~# ^C
thank you... probably I have another issue as well: [ 369.615003] musb_g_ep0_irq 804: SETUP packet len 0 != 8 ?
this seems gadgetfs related
dpeddi [23:15:44] 15 Transmit and 15 Receive Endpoints other than the mandatory Control Endpoint 0.
dpeddi [23:17:24] lsusb -vv | grep -i endpointaddress| grep IN | wc -l 9
dpeddi [23:17:31] lsusb -vv | grep -i endpointaddress| grep OUT | wc -l 6
dpeddi [23:28:46] i've upgraded to debian 9.1
dpeddi [23:28:57] and now in dmesg i get : [ 90.309997] musb_g_ep0_irq 804: SETUP packet len 0 != 8 ?
dpeddi [23:37:21] a guy posted a patch "https://www.spinics.net/lists/linux-usb/msg97114.html"
dpeddi [23:37:30] probably never applied to "http://elixir.free-electrons.com/linux/v4.4.88/source/drivers/usb/musb/musb_gadget_ep0.c"
dpeddi [23:41:09] but since my setup packet is 0 there isn't so much to dump :-(
From what I saw on IRC, you already got to the point where you got "SETUP packet len 0 != 8". How come you didn't experience the errno=22 error then? You used an older version of USBProxy?
No i haven't got... I wrong... What i found produce just a dump and wont solve.
I'm trying to skip loading into gadgetfs of some interfaces: for example i'm not interested in the usb_storage this device provide... where i should look to avoid the notification of such interface?
tnx
Sorry for not responding to this in a timely manner. @dpeddi are you still experiencing this issue?
Currently i'm busy in other projects. I don't have any more an usbproxy compatible hardware.
Ok. I'm sorry I couldn't get to this in time. I am going to close this issue at this time. If you do get usbproxy compatible hardware again and would like to explore this issue, just tag me!
Hi,
I followed https://gimx.fr/wiki/index.php?title=Bbb_sniffer guide to setup my environment.
I'm trying to analize the stream between my host and this device, but after starting usb-mitm, it produce a lot of errors and finally exit with abort. The log is really long to be attached, but probably the issue is on start.. so i would procede step by step.
I've added some printf and I can see that opening and writing complete correctly on the first interface while the other one fails.
Just for confirmation I've changed
for (ifc_idx=0;ifc_idx<ifc_count;ifc_idx++) {
to:for (ifc_idx=1;ifc_idx<ifc_count;ifc_idx++) {
But opening on interface >1 still doesn't work..
on the host