Re: Uable to connect to the BeagleBone Black

52 views

Skip to first unread message

骥野

unread,

Feb 13, 2017, 10:15:36 AM2/13/17

to Jason Kridner, beagl...@googlegroups.com

Already do so.

On Feb 13, 2017, at 11:04, Jason Kridner <jkri...@beagleboard.org> wrote:

Cc beagl...@googlegroups.com and I will reply.

On Mon, Feb 13, 2017 at 9:56 AM ?? <T.J....@hotmail.com> wrote:

Hi Jason,

I was trying to reconnect my BBB via usb this morning. Everything works fine yesterday. I can log into the BBB via Putty but today, I can’t login via SSH. I did ping 192.168.7.2 it does not work. I also see two LEDs flashing when I plug the BBB and after a little while the LED 3 turns off. I think there’s some eMMc configure issue going on.

I wonder if I can get any suggestion from you.

Best regards,

Jiye

Jason Kridner

unread,

Feb 13, 2017, 10:24:24 AM2/13/17

to 骥野, beagl...@googlegroups.com

below...

On Mon, Feb 13, 2017 at 10:13 AM 骥野 <t.j....@hotmail.com> wrote:

Already do so.

thanks for having the list in cc.

On Feb 13, 2017, at 11:04, Jason Kridner <jkri...@beagleboard.org> wrote:

Cc beagl...@googlegroups.com and I will reply.

On Mon, Feb 13, 2017 at 9:56 AM ?? <T.J....@hotmail.com> wrote:

Hi Jason,

I was trying to reconnect my BBB via usb this morning. Everything works fine yesterday. I can log into the BBB via Putty but today, I can’t login via SSH. I did ping 192.168.7.2 it does not work. I also see two LEDs flashing when I plug the BBB and after a little while the LED 3 turns off. I think there’s some eMMc configure issue going on.

The most common failure mode for the network connection once drivers are installed properly is a lack of the board providing a DHCP lease. This represents an issue with the flash imaged that wasn't caught on some versions. The work-around is to either wait a long time for the DHCP lease to work or manually assign your computer the IP address 192.168.7.1 (mask 255.255.255.252, no gateway) on that interface.

USR3 should stop blinking once the system boot becomes stable. USR3 is the eMMC access indicator by default. USR0 should continue to blink in a heartbeat fashion. The default LED modes are shown on https://beagleboard.org/getting-started.

You can confirm the issue by using a serial adapter to capture the kernel log. Alternatively, there is a virtual serial adapter that should be functioning fine if your drivers were installed properly. Log in and store the output of 'dmesg' and 'journalctl' to see if the issue can be shown.

I wonder if I can get any suggestion from you.

Work with serial access for the time-being and provide a log so that we can suggest a better long-term fix to avoid the issue, which I suspect is related to not providing your host with a DHCP lease.

Please be sure to provide the image version stored in ID.txt or /etc/dogtag.

Best regards,

Jiye

骥野

unread,

Feb 13, 2017, 11:42:53 AM2/13/17

to Jason Kridner, beagl...@googlegroups.com

Hi Jason,

You are right after a long time of wait I can log into the BBB again. I use the ‘dmesg’ and 'journalctl', I found the following:

>>is interface usb0 up and configured?: Cannot assign requested address

can't open '/var/lib/misc/udhcpd.leases': No such file or directory

Feb 13 14:49:07 beaglebone udhcpd[1176]: Starting very small Busybox based DHCP server: udhcpd.

Feb 13 14:49:07 beaglebone systemd[1]: Started LSB: Start busybox udhcpd at boot time.

Feb 13 14:49:08 beaglebone sh[759]: Starting udhcpd (via systemctl): udhcpd.service.

Feb 13 14:49:08 beaglebone systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE

Feb 13 14:49:08 beaglebone systemd[1]: lightdm.service: Unit entered failed state.

Feb 13 14:49:08 beaglebone systemd[1]: lightdm.service: Failed with result 'exit-code'.

Line 2:

Failed to bind UDP listener socket

Feb 13 14:49:37 beaglebone connmand[817]: Failed to bind TCP listener socket

Feb 13 14:49:37 beaglebone connmand[817]: DHCP server: option_code 1 option_value 255.255.255.0

Feb 13 14:49:37 beaglebone connmand[817]: DHCP server: option_code 3 option_value 192.168.0.1

Feb 13 14:49:37 beaglebone connmand[817]: DHCP server: option_code 6 option_value 192.168.0.1

Feb 13 14:49:37 beaglebone connmand[817]: tether {create} index 5 type 1 <ETHER>

Feb 13 14:49:37 beaglebone connmand[817]: tether {update} flags 4098 <DOWN>

Feb 13 14:49:37 beaglebone connmand[817]: tether {newlink} index 5 address BE:D6:BC:C1:14:58 mtu 1500

Feb 13 14:49:37 beaglebone connmand[817]: tether {newlink} index 5 operstate 2 <DOWN>

Feb 13 14:49:37 beaglebone connmand[817]: tether {add} address 192.168.0.1/24 label tether family 2

Feb 13 14:49:37 beaglebone connmand[817]: tether {update} flags 102467 <UP,RUNNING,LOWER_UP>

Feb 13 14:49:37 beaglebone connmand[817]: tether {newlink} index 5 address BE:D6:BC:C1:14:58 mtu 1500

Feb 13 14:49:37 beaglebone connmand[817]: tether {newlink} index 5 operstate 0 <UNKNOWN>

Feb 13 14:49:37 beaglebone connmand[817]: tether {add} route 192.168.0.0 gw 0.0.0.0 scope 253 <LINK>

Feb 13 14:49:37 beaglebone connmand[817]: tether {add} route fe80:: gw :: scope 0 <UNIVERSE>

Feb 13 14:49:37 beaglebone connmand[817]: wlan0 {newlink} index 4 address 40:A5:EF:0E:E7:25 mtu 1500

Line 3:

Using interface wlan0 with hwaddr 40:a5:ef:0e:e7:25 and ssid "BeagleBone-792D"

Feb 13 14:49:38 beaglebone wpa_supplicant[1027]: WPS: Converting push_button to virtual_push_button for WPS 2.0 compliance

Feb 13 14:49:38 beaglebone kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Feb 13 14:49:38 beaglebone kernel: device wlan0 entered promiscuous mode

Feb 13 14:49:38 beaglebone connmand[817]: wlan0 {add} route fe80:: gw :: scope 0 <UNIVERSE>

Feb 13 14:49:38 beaglebone connmand[817]: wlan0 {update} flags 102403 <UP,LOWER_UP>