My Beagle Bone Black works fine after flashing, BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.
I tried to install a recent image and so, I tried to flash the below image:
am335x-eMMC-flasher-debian-11.7-xfce-armhf-2023-09-02-4gb, and then, when I connect over serial to see what is happening, I get the following messages
"
Begin: Running /scripts/local-block … done.
Begin: Running /scripts/local-block … done.
Begin: Running /scripts/local-block … done.
Begin: Running /scripts/local-block … done.
Begin: Running /scripts/local-block … done.
Begin: Running /scripts/local-block … done.
Begin: Running /scripts/local-block … done.
Begin: Running /scripts/local-block … done.
done.
Gave up waiting for root file system device. Common problems:
Boot args (cat /proc/cmdline)
Check rootdelay= (did the system wait long enough?)
Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell!
BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.
"
I have attached the complete log file taken from putty.
My Beagle Bone Black does not get detected over USB as well.
Please share any suggestions on how to proceed further.
Did you write that image directly to the eMMC, or are you using a microSD to ‘flash’ it?
Edit, with that old bootloader … U-Boot 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500) hold the ‘s2’ button and toggle reset, should force it to read from microSD.
On my beagle bone black, I am able to flash EMMC image
“BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img”. This works fine.
I am able to boot from micro SD card using the image
“bone-debian-9.5-iot-armhf-2018-10-07-4gb.img”. This too works fine.
But when I try to boot the board from a micro SD Card with image
am335x-eMMC-flasher-debian-11.7-xfce-armhf-2023-09-02-4gb, I get stuck at:
"Begin: Running /scripts/local-block … done.
done.
Gave up waiting for root file system device. Common problems:
Boot args (cat /proc/cmdline)
Check rootdelay= (did the system wait long enough?)
Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell!
BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash)
Enter ‘help’ for a list of built-in commands."
And when I try to boot the board from a micro SD Card with image,
am335x-ubuntu-24.04.1-console-armhf-2025-02-26-4gb.img, I get stuck at:
"
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f85b000, end 8ffff4c1 … OK
Loading Device Tree to 8f824000, end 8f85a711 … OK
Starting kernel …
[ 0.168349] l3-aon-clkctrl:0000:0: failed to disable
[ 12.661319] debugfs: Directory ‘49000000.dma’ with parent ‘dmaengine’ already present!
[ 12.707088] gpio-of-helper ocp:cape-universal: Failed to get gpio property of ‘P8_03’
[ 12.707119] gpio-of-helper ocp:cape-universal: Failed to create gpio entry
[ 13.427190] omap_voltage_late_init: Voltage driver support not added
Gave up waiting for root file system device. Common problems:
Boot args (cat /proc/cmdline)
Check rootdelay= (did the system wait long enough?)
Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell!
BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3.1) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.
(initramfs)
"
I am not able to understand why some images get stuck at initramfs and some just works fine.