192.168.7.2 works on SD card, but not from eMMC

GoogleGroups
1

Hello Everyone,

I am having an issue with my BeagleBone Black when I move the OS from the SD card to the eMMC on board. Here are the steps I use and results, please let me know if you see the problem.

  1. Download the latest image from beagleboard.org
    1a. Flash it to an SD card
  2. Use the “power/user” button to boot the SD card via power adapter. (however, it also boots from the SD card as long as it’s just in there)
  3. Connect the USB Cable, windows creates the 192.168.7.1 interface and I can SSH to 192.168.7.2 and everything works fine.
  4. Reboot to check it, works fine again
  5. Uncomment the flashing line in side of the /boot/uEnv.txt
cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
6. Reboot, watch the lights flash while it is flashing eMMC
7. Remove the SD card
8. Boot the beaglebone
9. Windows doesn't even make a sound like it normally does when attaching a USB device and the BeagleBone Black is not available.

If I reflash and go back, it starts working again as long as I boot from the SD card.

As a secondary note, here is my df -h output. I am not sure if it is booting correctly now the eMMC and because the SD card is in, it is working properly.

root@beaglebone:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 99M 8.4M 91M 9% /run
/dev/mmcblk0p1 3.3G 3.0G 35M 99% /
tmpfs 247M 4.0K 247M 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 247M 0 247M 0% /sys/fs/cgroup
tmpfs 50M 0 50M 0% /run/user/1000
root@beaglebone:~#

Any thoughts or debugging steps would be greatly appreciated.

Cheers,

Gregg

2

I think this is fixed, one of the things that happens after the eMMC
flash and reboot.. it does take 30 seconds to a full minute on the
first bootup to regenerate the host ssh key's...

Also it might be something we've already fixed, can you double check with:

https://rcn-ee.net/rootfs/bb.org/testing/2016-10-23/

Regards,

3

Robert,

Thanks for your reply. The version I installed was from the beaglebone.org site (so might need an update). It was the file named “bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img” that had the problem. I doubt it was just still booting as it seems to go into “reflashing” mode after it boots the second time.

I just finished installing the 2016-10-23 image seems to flash correctly, but once I boot it… I get some activity on the lights for about 20 seconds (no USB connection) and then all 4 lights go solid and it just sits and won’t respond.

Any thoughts on what that might be?

Thanks for the help.

Gregg

4

odd..

Can you please go into a little more detail so i can replicate it..

Which image did you download, how did you flash it to the microSD and
I asume you just plugged in the microSD and let it flash the eMMC
correct?

You then removed the microSD before the final booting?

Regards,

5

Robert,

Yes, thanks for your replay.

  1. I downloaded the image from https://rcn-ee.net/rootfs/bb.org/testing/2016-10-23/lxqt-4gb/ and specifically I downloaded the file named bone-debian-8.6-lxqt-4gb-armhf-2016-10-23-4gb.img.xz from there

  2. I used Win32ImageWriter to write it to a 16 gig sandisk card.

  3. I booted the OS by holding down the power/user button next to the ethernet port and waited until the four lights turned on in the swipe pattern.

  4. Modified the uEnv.txt file

  5. I rebooted and held the button down again, waiting until the “swipe” pattern occured and

  6. After releasing the button, it took ~30-35 seconds to start flashing, indicated by a back and forth light pattern.

  7. Once it was completed (blinking lights),

  8. I took out the card,

  9. unpowered the beaglebone and

  10. then powered it back up.

  11. Once it powered up, I got the “heart beat” light, some minor disk activity or load (but not like when a full OS boot happens), and then all lights come on solid.

Please let me know what you would like me todo next. Currently I am working off of the SD card directly, which makes booting my system a little annoying, but workable for the moment. I have another SD card I can do tests with now too.

This board is a rev A6 if that matters.

Thanks,

Gregg

6

A6? that only has a 2GB eMMC...

The lxqt-4gb images take up 3.3Gb of space..

Grab the iot image:

https://rcn-ee.net/rootfs/bb.org/testing/2016-10-30/iot/

( i had disabled the lxqt-2gb, has it hasn't been really tested to fit
in 2gb for awhile.. )

Regards,

7

Derp, I feel a little stupid now. Thanks!

Cheers,

Gregg

8

I am having the same symptom with BBB rC. I am trying to install a -bone mainline kernel.

I tried 4 of the latest images. When I use a ti kernel ssh works. As soon as I install a -bone kernel 192.168.7.2 stops working.

I installed identical images on uSD/eMMC. Works ok from SD card. eMMc conflicts with ssh.

My Linux PC ifconfig says:

enp0s29f7u7u4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::6b49:8ea0:67b:599d prefixlen 64 scopeid 0x20
ether 04:a3:16:ec:bb:c9 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 24 bytes 7714 (7.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions

BeagleBone ifconfig says:

usb0 Link encap:Ethernet HWaddr 04:a3:16:ec:bb:c0
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
inet6 addr: fe80::6a3:16ff:feec:bbc0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:50 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13512 (13.1 KiB) TX bytes:12833 (12.5 KiB)

Install info is:

root@beaglebone:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.4 (jessie)
Release: 8.4
Codename: jessie

root@beaglebone:~# uname -a
Linux beaglebone 4.4.53-bone16 #1 Tue Mar 14 05:36:36 UTC 2017 armv7l GNU/Lin

Is there a standard image for Beaglebone using a 4.x mainline kernel?

What is causing the problem?