Beaglebone Black Cannot Boot Debian

General Discussion
1

Hello everyone,

I am trying to copy a Beaglebone Black Rev C’s eMMC image to another BBB’s eMMC. I have succesfully made a copy image from first BBB’s eMMC to an microSD card. When i tried to copy this image (which has been installed into microSD card) to the other BBB’s I first noticed that it couldn’t boot, because the user Led blinking process was not supposed to be. First the Heart bite Led starts and continuesly running and it can’t process further. ,
Then I decided to checked the sequence by connecting through seral debug line and I got a message like below.

U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img


U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)

I2C:   ready
DRAM:  512 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0
gpio: pin 53 (gpio 53) value is 1




Card did not respond to voltage select!
mmc0(part 0) is current device
Card did not respond to voltage select!
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 1
reading uEnv.txt
1699 bytes read in 5 ms (331.1 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from uEnv.txt
Importing environment from mmc ...
Checking if uenvcmd is set ...
gpio: pin 56 (gpio 56) value is 1
Running uenvcmd ...
reading zImage
4103240 bytes read in 226 ms (17.3 MiB/s)
reading initrd.img
2952642 bytes read in 165 ms (17.1 MiB/s)
reading /dtbs/am335x-boneblack.dtb
25926 bytes read in 9 ms (2.7 MiB/s)
Kernel image @ 0x82000000 [ 0x000000 - 0x3e9c48 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Using Device Tree in place at 88000000, end 88009545

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.378493] omap2_mbox_probe: platform not supported
[    0.533012] tps65217-bl tps65217-bl: no platform data provided
[    1.565724] omap_i2c 4819c000.i2c: controller timed out
[    2.577453] omap_i2c 4819c000.i2c: controller timed out
[    2.589146] bone-capemgr bone_capemgr.9: slot #0: No cape found
[    3.595015] omap_i2c 4819c000.i2c: controller timed out
[    4.606881] omap_i2c 4819c000.i2c: controller timed out
[    4.618441] bone-capemgr bone_capemgr.9: slot #1: No cape found
[    5.624312] omap_i2c 4819c000.i2c: controller timed out
[    6.636048] omap_i2c 4819c000.i2c: controller timed out
[    6.647736] bone-capemgr bone_capemgr.9: slot #2: No cape found
[    7.653734] omap_i2c 4819c000.i2c: controller timed out
[    8.665346] omap_i2c 4819c000.i2c: controller timed out
[    8.677033] bone-capemgr bone_capemgr.9: slot #3: No cape found
[    8.691757] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[    8.701368] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[    8.708113] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[    8.725654] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed
[    8.788638] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[    8.800361] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[    8.807647] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
Loading, please wait...
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/disk/by-uuid/743fc136-abc4-460b-8479-226d74756374 does not exist.  Dropping to a shell!
modprobe: module i8042 not found in modules.dep
modprobe: module ehci-hcd not found in modules.dep
modprobe: module uhci-hcd not found in modules.dep
modprobe: module ohci-hcd not found in modules.dep
ox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

I have two questions about this process.

Firstly, I’d like to make the second BBB to turn back to the first manufactured image. But even try to copy the first debian image (the latest release) which was downloaded on internet the same problem occured. (first situation when I first have it :))

Secondly, I have checked the directories on the third BBB (which has a bootable image installed) i couldn’t find a root folder under - cd /home. Is it neccessary to have a root directory on cd /home to boot a new image file from SD or eMMC?

Looking forward to hearing from you,

Aykut Arabacıoğlu

2

Force booting from the microSD, then mount the eMMC and update “uenvcmd” and /etc/fstab on the eMMC replacing “743fc136-abc4-460b-8479-226d74756374” with what your eMMC partition actually iss…

root@BeagleBone:~# ls -lha /dev/disk/by-uuid/*
lrwxrwxrwx 1 root root 15 Nov  4 01:49 /dev/disk/by-uuid/a6747c27-ddae-4216-af07-9e45490702aa -> ../../mmcblk0p1

Regards,

3

Hello Robert,

First of all, thank you for your quick reply.

Actually I’m a newbie right now for the Beaglebone Community. What do you mean by “mount eMMC?”. Can you explain the procedure step by step?

My last status is like this ;

  • I have a first Beaglebone with an image which I can reach from its’ eMMC. (There are some Device Tree setups and codes in it which I don’t actually know what was made on that Beaglebone so I just wanted to copy the bootable image to an microSD to write that image on the second BBB with microSD to eMMC write procedure.)
  • I have succesfully booted my second Beaglebone with a previous Debian version so as I result I can boot my BBB with eMMC image. ( With only OS nothing has added. )
  • I have a microSD with a image which i got an image from my editted first beaglebone with this tutorial (BeagleBone Black Extracting eMMC contents - eLinux.org) ( exactly with the /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh script.)
  • What I can’t do is when I try to insert microSD to second Beaglebone and try to boot the editted image, the BBB cannot do that process.

So as a newbie could you please explain the procedure a bit simple for me :slight_smile:

Regards,

Aykut Arabacıoğlu

4

That page is 6 years too old and broken…

Boot with microSD, run lsblk to figure out the name of microSD and eMMC:

In my case:

debian@bbb-pwr01-ser09:~$ lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0      179:0    0 29.8G  0 disk 
└─mmcblk0p1  179:1    0 29.8G  0 part /        <-microSD
mmcblk1      179:8    0  1.8G  0 disk          <-eMMC
mmcblk1boot0 179:16   0    1M  1 disk 
mmcblk1boot1 179:24   0    1M  1 disk

If my eMMC had a valid partition i’d simply run: (it might have 1 or 2)

mkdir disk1
mount /dev/mmcblk1p1 ./disk1/

mkdir disk2
mount /dev/mmcblk1p2 ./disk2/

Then go inside disk1/disk2 and edit/fix uEnv.txt and fstab to match your

debian@bbb-pwr01-ser09:~$ ls -lha /dev/disk/by-uuid/*
lrwxrwxrwx 1 root root 15 Nov  6 16:47 /dev/disk/by-uuid/11be5f32-4769-473a-a746-355aa0132f0f -> ../../mmcblk0p1

Regards,

5

Hello Robert,

We cannot boot from the microSD. That was the major problem.

What we done, we have booted the BBB from the eMMC, then placed the microSD to its plug on BBB and follow the steps you suggested. When we used the “lsblk” command we saw

mmcblk1boot0 179:8 0 16M 1 disk
mmcblk1boot1 179:16 0 16M 1 disk
mmcblk0 179:24 0 14.5G 0 disk
mqmmcblk0p1 179:25 0 14.5G 0 part
mmcblk1 179:0 0 3.6G 0 disk
mqmmcblk1p1 179:1 0 3.6G 0 part /

Then we followed the “mkdir disk1” and “mount /dev/mmcblk1p1 ./disk1/” commands.

After that we used “ls -lha /dev/disk1/by-uuid/” command and got :

total 0
drwxr-xr-x 2 root root 80 Aug 1 14:23 .
drwxr-xr-x 6 root root 120 Jan 1 2000 …
lrwxrwxrwx 1 root root 15 Aug 1 14:23 c75faa94-f585-4962-8381-9415e45892fd → …/…/mmcblk0p1
lrwxrwxrwx 1 root root 15 Aug 1 14:13 c78f7d5a-e32b-403b-9ce8-a4f8f955bda1 → …/…/mmcblk1p1

After those we can reach the disk1 and got these files :

bbb-uEnv.txt dev ID.txt media opt run sys var
bin etc lib mnt proc sbin tmp
boot home lost+found nfs-uEnv.txt root srv usr

But after these steps we cannot open the bbb-uEnv.txt or nfs-uEnv.txt. Could you please guide us?

Regards,

Aykut Arabacıoğlu