[usbproxy] Re: Can't get usb-mitm running
- From: Dominic Spill <dominicgs@xxxxxxxxx>
- To: usbproxy@xxxxxxxxxxxxx
- Date: Fri, 24 Jun 2016 23:19:42 +0100
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.
So I tried to compile the latest code from git following the included
instructions.
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.
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
correctly.
This is the process I used to patch the module:
-download kernel source from
https://github.com/beagleboard/linux/tree/4.4.9-ti-rt-r25
-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+
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.
Other related posts:
