Skip to first unread message
Alvin Mites
Jan 13, 2016, 12:47:10 PM1/13/16
to BeagleBoard
I've been tinkering with these boards since their release, I recently pulled 2 of them out of storage to setup a mini weather station for my house.
Trouble is I can't access them and wondering if I'm just missing the elusive obvious
2 boards (1 rev b, 1 rev c)
I've tried powering them via external DC adapter / usb
tried flashing them multiple times with various versions of Robert's ubuntu flasher image & console sd driven
they will flash blue lights like their working
going so far is running through the cylon lights and then holding steady like they've finished correctly
but neither will register on my network through ethernet or be accessible through usb
ssh: connect to host 192.168.7.2 port 22: Connection timed out
I'm running ubuntu on my host system and can see them through
lsusb
Bus 005 Device 004: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB Ethernet/RNDIS Gadget
I have added the udev rules
any ideas? seems like I've forgotten a simple step in the months since I last tinkered with one of these boards
thank you in advance
Robert Nelson
Jan 13, 2016, 12:50:39 PM1/13/16
to Beagle Board
Alvin Mites
Jan 15, 2016, 12:51:05 AM1/15/16
to BeagleBoard
enp2s0 Link encap:Ethernet HWaddr ac:22:0b:50:f7:9f
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::ae22:bff:fe50:f79f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2889641 errors:0 dropped:0 overruns:0 frame:0
TX packets:1673505 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1982567319 (1.9 GB) TX bytes:378878135 (378.8 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:34078 errors:0 dropped:0 overruns:0 frame:0
TX packets:34078 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6480482 (6.4 MB) TX bytes:6480482 (6.4 MB)
virbr0 Link encap:Ethernet HWaddr 52:54:00:1d:bf:8a
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
virbr0-nic Link encap:Ethernet HWaddr 52:54:00:1d:bf:8a
BROADCAST 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:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Alvin Mites
Jan 15, 2016, 12:53:06 AM1/15/16
to BeagleBoard
oops wire was loose -- guessing you're looking for
enxd05fb8fd9b00 Link encap:Ethernet HWaddr d0:5f:b8:fd:9b:00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36 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:5894 (5.8 KB) TX bytes:0 (0.0 B)
Soapy Smith
Jan 25, 2016, 1:05:45 PM1/25/16
to BeagleBoard
I've always seen marginal success in USB connectivity with BBB. I recently acquired a couple of BBG, at first I thought these were solid, but now I am seeing problems.
There is a difference seen in the host computer from the shell command ifconfig -a.
Here is ifconfig -a for a working BBG:
eth0 Link encap:Ethernet HWaddr 6c:0b:84:09:f9:de
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::6e0b:84ff:fe09:f9de/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:982290 errors:0 dropped:0 overruns:0 frame:0
TX packets:613548 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1196203986 (1.1 GB) TX bytes:107826806 (107.8 MB)
Interrupt:20 Memory:f7100000-f7120000
eth1 Link encap:Ethernet HWaddr ec:24:b8:f6:e1:7c
inet addr:192.168.7.1 Bcast:192.168.7.255 Mask:255.255.255.0
inet6 addr: fe80::ee24:b8ff:fef6:e17c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:64 errors:0 dropped:0 overruns:0 frame:0
TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10319 (10.3 KB) TX bytes:15361 (15.3 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:30214 errors:0 dropped:0 overruns:0 frame:0
TX packets:30214 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3210722 (3.2 MB) TX bytes:3210722 (3.2 MB)
Now here is a different BBG flashed with the exact same image Debian 8.2:
eth0 Link encap:Ethernet HWaddr 6c:0b:84:09:f9:de
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::6e0b:84ff:fe09:f9de/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:982671 errors:0 dropped:0 overruns:0 frame:0
TX packets:613978 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1196254756 (1.1 GB) TX bytes:107922637 (107.9 MB)
Interrupt:20 Memory:f7100000-f7120000
eth4 Link encap:Ethernet HWaddr 68:c9:0b:ed:25:23
inet6 addr: fe80::6ac9:bff:feed:2523/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6487 (6.4 KB) TX bytes:12510 (12.5 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:30316 errors:0 dropped:0 overruns:0 frame:0
TX packets:30316 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3218638 (3.2 MB) TX bytes:3218638 (3.2 MB)
The obvious difference is seen at eth4 for the non-working versus eth1 for the working board.
eth1 (the working board) is getting an inet address.
eth4 (the non-working board) is not getting an inet address.
The BBG which does not connect will keep trying over and over.
I am using Ubuntu 14.04.
Regards,
Greg
Robert Nelson
Jan 25, 2016, 1:15:33 PM1/25/16
to Beagle Board
ps.. the "eth1" vs "eth4" is a udev issue that "you" need to fix on your host*..
The BBG (on the other end of the usb cable) can't tell your host how
to name it. (ethX)..
* /etc/udev/rules.d/70-persistent-net.rules
So your first BBG will get eth1, second eth2, third eth3, etc...
Robert Nelson
Jan 25, 2016, 1:18:01 PM1/25/16
to Beagle Board
BBG runs the dhcp server that hands out the 192.168.7.1 ip address to
your ubuntu host...
Soapy Smith
Jan 25, 2016, 1:42:22 PM1/25/16
to BeagleBoard
sudo dhclient eth2 (or whatever is obviously the BBG from looking at ifconfig)
There is one line return and then nothing happens (after entering password due to sudo).
On a healthy board, at the first "sudo dhclient ethX", there is a quick line feed and no messages.
The second time, I get
RTNETLINK answers: File exists
Robert Nelson
Jan 25, 2016, 1:45:40 PM1/25/16
to Beagle Board
On Mon, Jan 25, 2016 at 12:42 PM, Soapy Smith <soapy...@comcast.net> wrote:
> sudo dhclient eth2 (or whatever is obviously the BBG from looking at
> ifconfig)
>
> There is one line return and then nothing happens (after entering password
> due to sudo).
"nothing happens"... on success, yes "nothing happens"..
> sudo dhclient eth2 (or whatever is obviously the BBG from looking at
> ifconfig)
>
> There is one line return and then nothing happens (after entering password
> due to sudo).
check:
sudo ifconfig -a
>
> On a healthy board, at the first "sudo dhclient ethX", there is a quick line
> feed and no messages.
> The second time, I get
> RTNETLINK answers: File exists
Soapy Smith
Jan 25, 2016, 2:00:52 PM1/25/16
to BeagleBoard
My mistake, I wasn't clear at all. Allow me to restate...
There is one line return after issuing the command sudo dhclient eth2, and then the shell locks up.
There is no message returned. Only a blinking cursor and nothing further happens.
Let's see if I can paste in what it looks like:
user@host:~$ sudo dhclient eth2
(blinking cursor here)
Reply all
Reply to author
Forward
0 new messages