Hello everybody.
Just got my BBG and I’m not able to connect to the internal server via eth.
PC is laptop with Win10, on BBG is power LED shining and USR LEDs are blinking. BBG is directly connect to laptom via eth cable. This laptom is older one (HP ProBook4530s) after complete reinstal.
In network setting I assigned static adres in IPv4 protocol (192.168.7.254/255.255.255.0) and the result is still the same:
Pinging 192.168.7.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.7.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
LEDs on both eth connector are “dead” so there is no communication but in device manager there is Linux USB Ethernet/RNDIS Gadget and in properties it says that device is working properly.
I’ve also tried to instal new FTDI drivers, eject BBG, turn off firewall but without any succes.
Thank you for any suggestion
BR
Petr
On Fri, 11 Nov 2016 13:27:53 -0800 (PST), Petr Šefara
<torquizze@gmail.com> declaimed the
following:
PC is laptop with Win10, on BBG is power LED shining and USR LEDs are
blinking. BBG is directly connect to laptom via eth cable. This laptom is
older one (HP ProBook4530s) after complete reinstal.
Try going through a router/switch rather than direct -- or try using a
cross-over cable instead of a straight cable.
So . . .
Ethernet/RNDIS gadget (g_ether)
… or on host side, usbnet and random hwaddr
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.252
network 192.168.7.0
gateway 192.168.7.1
This is what a stock system should be setup as for USB ethernet. So, on the Windows host under “Network Connections” for the RDNIS gadget driver should set the IP address as 192.168.7.1. Then the same netmask as above. Which Windows calls “Subnet mask”.
Additionally, I’ve experienced problems in the past with variosu version of Windows where you’ll need to do a manual Windows update to pull in a driver for the RNDIS software device. Don’t ask me why, because I do not know why. But I would not worry about this unless it still does not work as I described above.
By the way, on a stock debian image on the beaglebones. DHCP will be enabled. So unless your laptop has a DHCP server running on it ( not very likely or easy to setup on Windows ). You’re going to need a router between the laptop and a beaglebone. IF You want to use ethernet, and if you do not have other means to connect to the beaglebone, to change some configuration files. Like a serial debug cable, have g_serial setup and running properly, or booting from an sdcard, then mounting the eMMC long enough to edit files.