Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi guys,
I have connected with a USB A/B cable from my LINUX host to my ARM. On my ARM, I have loaded g_ether, usbnet, cdc_subset and mii:
***************************************
# lsmod
Module Size Used by Not tainted
cdc_subset 476 0
usbnet 10470 1 cdc_subset
mii 2872 1 usbnet
g_ether 23528 0
af_packet 15388 2
enc28j60 13992 0
unix 16952 10
********************************************
and have ifconfig'd usb0:
***********************************************
usb0 Link encap:Ethernet HWaddr 4E:72:14:45:30:F9
inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
***********************************************
On by LINUX host, I've also loaded g_ether:
************************************************
cytan@ubuntu:/usr/share/wireshark$ lsmod | grep cdc
cdc_ether 13536 0
cdc_subset 12885 0
usbnet 26212 2 cdc_ether,cdc_subset
cytan@ubuntu:/usr/share/wireshark$ lsmod | grep g_ether
g_ether 49416 0
dummy_hcd 23509 1 g_ether
Unfortunately pinging my ARM gadget 192.168.2.10 with my host, there is no route to the gadget. Similarly the other way around. Note: I've also added a default gateway to my ARM: route add default gw 192.168.2.5
I checked that the host is actually seeing the gadget by checking
/sys/kernel/debug/usb/devices
Hi malek,
Unbelievable, my 3.5 month old ASUS just had a hard drive crash! Fortunately, I actually have backup of the linux partition before the drive complete gave out. But I don't have a LINUX box to run my ARM cross compiler right now and will only have it when I RMA the ASUS.
However, just for your info my ARM is running LINUX 2.6.39.4 and the host is running UBUNTU 11.10.
Reading from your link about rndis, do I actually need a USB hub between my ARM and my LINUX host? Is a simple USB A/B cable is not sufficient?
Also another interesting observation is that running ethtool on the ARM gives "LINK: no". Any thoughts?
Another interesting data point: I connected the ARM to my MacBook Pro and ran ethtool on the ARM and I get a Link: yes! Unfortunately, I don't think there is RNDIS available on the Mac. Any words of wisdom?
I don't know why usbnet is not working on my LINUX box (it's still being repaired). BUT usbnet works without any changes on WinXP with linux.inf driver from http://code.google.com/p/beagleboard...name=linux.inf loaded.
OK, I got my Ubuntu box back and it also requires use_eem=0 for the gadget to be recognized. It shows up as a USB2 device and needs to be configured using system setup-> network. For some reason using ifconfig on the command line is not sufficient because it keeps getting reset, i.e. gets disconnected on the Ubuntu box.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.