Howdy all,
I am stuck in Windows development-host land and want to be able to
connect the Beagleboard with just one wire.
I grabbed Koen's 2.6.28-r17 demo image from
http://www.angstrom-distribution.org/demo/beagleboard/
It appears to be the last available with RNDIS instead of the
'Composite Gadget'.
I built an SD card with it, the 2.6.28-r17 modules and the 'stable'
demo image file system. Works great with my Ethernet/USB hub combo.
Just about every time I plug in only the USB cable, the Beagleboard
boots, Windows finds the 'Linux RNDIS' device and the Beagleboard gets
a kernel fault from a NULL pointer and hangs.
Messing with this for way too long has led me to a strange state...
I have disabled ALL of the other protocols on the Windows RNDIS gadget
driver and assigned '192.168.0.2' to the TCP/IP Properties.
This has resolved the issue.
I don't know if the NULL pointer was coming from the DHCP request or
one of the other protocols, but its gone now!
best regards,
- Dan (the one-wire man)
P.S. UltraVNC attaches to the X server over the '425.9' Mbit
connection and just flys!
P.S.S. Off to build a 'current' 2.6.29 kernel with RNDIS instead of
Composite Gadget. Should work now...
The current 2.6.29 kernel has all gadgets as modules, so you can just do 'rmmod g_cdc ; modprobe g_ether' the get rndis (or edit /etc/default/usb* to make g_ether the default).
regards,
Koen
The current 2.6.29 kernel has all gadgets as modules, so you can just
do 'rmmod g_cdc ; modprobe g_ether' the get rndis (or edit /etc/
default/usb* to make g_ether the default).
Hi Koen and others,
Does any place exist collecting all the new major features included in the
Angstrom feeds? I mean - Now I "by random" hear about this new smart feature
because I follow the BeagleBoard list closely, but a lot of people might
miss this single topic 
Or put in other words: How would you recommend a random developer out there
(i.e. me to figure out if I should upgrade to a newer Angstrom release
or not? I would of cause like to keep up, but do not want to upgrade every
day "just for fun", and trying to check for "important" updates looking in
the OE GIT tree i.e. once a week or every 14 days are found nearly
impossible (due the great activity, which I can only encourage
Any hints on how to best possible keeping up the phase?
Best regards and thanks in advance
Søren
Op 23 jun 2009, om 21:51 heeft Søren Steen Christensen het volgende geschreven:
The current 2.6.29 kernel has all gadgets as modules, so you can just
do 'rmmod g_cdc ; modprobe g_ether' the get rndis (or edit /etc/
default/usb* to make g_ether the default).
Hi Koen and others,
Does any place exist collecting all the new major features included in the
Angstrom feeds? I mean - Now I "by random" hear about this new smart feature
because I follow the BeagleBoard list closely, but a lot of people might
miss this single topic
Or put in other words: How would you recommend a random developer out there
(i.e. me to figure out if I should upgrade to a newer Angstrom release
or not? I would of cause like to keep up, but do not want to upgrade every
day "just for fun", and trying to check for "important" updates looking in
the OE GIT tree i.e. once a week or every 14 days are found nearly
impossible (due the great activity, which I can only encourage
Any hints on how to best possible keeping up the phase?
Hire an intern
regards,
Koen
…setting USB_MODE=“networking” in /etc/defaults/usb-gadget does the trick.
It does seem odd that the device comes up but then is not ‘ready’:
[ 325.059326] ADDRCONF(NETDEV_UP): usb0: link is not ready
I have to manually ‘ifdown usb0’ and then ‘ifup usb0’
…but sometimes is comes up just fine.
strange…