--------- Original Message --------
To: "usbproxy@xxxxxxxxxxxxx" <usbproxy@xxxxxxxxxxxxx>
Oggetto: [usbproxy] Re: Can't get usb-mitm running
Data: 25/06/16 00:20
On 10 June 2016 at 16:49, blinkin <blinkin@xxxxxxxx> wrote:
> Hello, I purchased a BeagleBone Black and tried to get USBProxy running
following your instructions. I tried to use the provided release image but
it doesn't boot from that image. (Maybe the board boots correctly but
there's no ssh server and no way to reach it from the outside? I'm waiting
for the usb serial cable I just purchased to be sure...)
I've never had trouble with the SD card booting, so I'm not sure how to help
with this. There should be an SSH server running, listening on the
ethernet interface, when you boot it. It will attempt to get an IP
address via DHCP.
I don't have access to my router dhcp logs, so I couldn't know what was the
IP address assigned to the board. I eventually managed to get a shell by
purchasing an USB-to-serial cable and then configured a static IP.
> So I tried to compile the latest code from git following the included
> The code compiles correctly on the latest debian image provided by
beagleboard.org (8.4 jessie, kernel 4.4.9-rt-r25)and usb-mitm starts but I
step on the same problem that user potjaune encountered in the git issue #50
(error mounting gadgetfs: no such device).
This issue was closed because the user was able to boot from the supplied
image without needing to build a kernel module.
I wasn't as lucky as potjaune, so the issue persisted for me. Eventually I
discovered that the kernel module g_multi (the one providing eth over usb
connectivity to the board) must be disabled. after that, the gadgetfs module
can be loaded and /dev/gadgetfs mounted. You may want to add "sudo modprobe
-r g_multi" to the instructions for using USBProxy on newest versions of the
board (mine is debian 8.4).
After disabling that module USBProxy starts, but it relays a few packets
correctly and then hangs completely on the write() at line 302 in
HostPRoxy_GadgetFS.cpp, in function send_data(). The last packet is
transmitted correctly to the host but the write() never returns and
the board is completely blocked, needing a reboot to work again. The host
receives correctly the packet but after that it sends three new requests,
one every 5 seconds (the last one being set_Configuration), and then,
getting no response from the blocked board, writes in the kernel log:
[xxx] usb 1-2: can't set config #1, error -110
However after facing this I managed to get the release image to work, so I
did not go any further in what seems to be another instance of issue #53.
Using the release image I can happily get also the latest version of
USBProxy up and running, so I think the incompatibility between a new
install and the relese image is in the OS configuration. I can replicate the
kernel modules configuration by looking at the lsmod output, but if you have
any advice about other config changes you made to get USBProxy working on
the release image I would be grateful.
> The issue has been marked closed without any information about how to
prevent the error for other users. I understood that the issue is related to
the patch for the gadgetfs module, but I am not sure if I patched it
> This is the process I used to patch the module:
> -download kernel source from
> -patch the file drivers/usb/gadget/legacy/inode.c by hand, since the
line numbers are no longer the same
I have no idea if this patch is still valid for kernel 4.0+
After trying both the patched and vanilla modules, i found no differences so
the patch is not needed anymore.
> Last, to overcome these problems, I tought about using a kernel that
doesn't need the patch, the 3.15 (as you say, that should be ok), but it's
not present in the official beagleboard repository, where can I find it?
I have no idea, that's why the release image is still in use, even though
the kernel is old.
ZE-Light e ZE-Pro: servizi zimbra per caselle con dominio email.it, per tutti
Idee regalo classiche o alternative? Trova l'offerta migliore in un click
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=13327&d=28-6