I tried the image “am335x-ubuntu-22.04.3-console-armhf-2023-09-21-4gb.img.xz” that I found on this website: Index of /rootfs/ubuntu-armhf-22.04-console-v5.10-ti/2023-09-21
Initially, it booted successfully from the SD Card, so I decided to make it flashable. I uncommented the line “cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh” in /boot/uEnv.txt.
After rebooting and reflashing the eMMC, the system no longer starts. I thought it might be a hardware issue, so I tried it on another device, but the same problem occurred. There is no output on the serial port, and some LEDs are on (please refer to the attached picture).
I have also attached the log of the flashing process. Could it be a faulty firmware issue? Your assistance would be greatly appreciated.
reflashing.txt (24.6 KB)
Solved: I just put an older stable Debian image onto the SD card and then pressed the ‘SD’ button while powering it on. It’s booting now! Phew!
So what’s really weird about this, (and we were talking over email…) so for clarity…
How did the am57xx or ‘beaglebone-ai’ became the default…
mounting… https://rcn-ee.com/rootfs/ubuntu-armhf-22.04-console-v5.10-ti/2023-09-21/am335x-ubuntu-22.04.3-console-armhf-2023-09-21-4gb.img.xz right now…
Mounted… looking at the out-of-box default…
The enable-beagle-flasher is pretty simple, i guess we make it detect the platform and only offer a few examples…
if ! id | grep -q root; then
echo "enable-beagle-flasher must be run as root:"
echo "sudo enable-beagle-flasher"
if [ -f /etc/default/beagle-flasher ] ; then
sed -i -e 's:/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh:/usr/sbin/init-beagle-flasher:g' /boot/uEnv.txt
sed -i -e 's:#cmdline=init:cmdline=init:g' /boot/uEnv.txt
systemctl enable beagle-flasher-init-shutdown.service || true
systemctl disable grow_partition.service || true
echo "log: enable-beagle-flasher"
echo "log: media is now setup to flash other media"
echo "log: Shutdown system and this flasher will run on next startup"
echo "log: enable-beagle-flasher"
echo "log: Please setup /etc/default/beagle-flasher, for the BBB or BBAI..."
echo "log: #BBB: sudo cp -v /etc/beagle-flasher/beaglebone-black-microsd-to-emmc /etc/default/beagle-flasher"
echo "log: #BBAI: sudo cp -v /etc/beagle-flasher/bbai-microsd-to-emmc /etc/default/beagle-flasher"
echo "log: and rerun..."
Thank you Robert.
I ran a test again using the raw image, booted on the SD Card
root@ubuntu:/home/ubuntu# cat /etc/default/beagle-flasher
log: media is now setup to flash other media
log: Shutdown system and this flasher will run on next startup
Since the file
/etc/default/beagle-flasher already existed on the initial image, there was no indication displayed to execute the example script with the command
sudo cp -v /etc/beagle-flasher/beaglebone-black-microsd-to-emmc /etc/default/beagle-flasher (as is part of the else condition). As
/etc/default/beagle-flasher is initially a copy of
/etc/beagle-flasher/bbai-microsd-to-emmc, I suppose that it resulted in the wrong flasher being executed.
Maybe the platform should be detected in the script and the right copy of the flasher should be done?
Hope it helps,
PS: Also after making things working with the “cp -v /etc/beagle-flasher/beaglebone-black-microsd-to-emmc /etc/default/beagle-flasher” the power button does not shut down the system.
Out of the box, all you need to run is:
sudo enable-beagle-flasher folllowed by a
I’m still confused, please double check the sha256sum of the file…
voodoo@hestia:~/Downloads$ sha256sum am335x-ubuntu-22.04.3-console-armhf-2023-09-21-4gb.img.xz
I’m looking at mounted version of am335x-ubuntu-22.04.3-console-armhf-2023-09-21-4gb.img.xz and the default settings of /etc/default/beagle-flasher is correct…
and looking at teh jenkins build job:
Log: RootStock-NG.sh complete
sudo ./setup_sdcard.sh --img-4gb am335x-ubuntu-22.04.3-console-armhf-2023-09-21 --dtb beaglebone --distro-bootloader --enable-cape-universal --optional-uboot-uio-pru --enable-bypass-bootup-scripts
Backup version of u-boot (MLO): /opt/backup/uboot/
'./u-boot/bb-u-boot-am335x-evm/MLO' -> '/tmp/tmp.UA8VtAv9jJ/disk/opt/backup/uboot/MLO'
Backup version of u-boot (u-boot.img): /opt/backup/uboot/
'./u-boot/bb-u-boot-am335x-evm/u-boot.img' -> '/tmp/tmp.UA8VtAv9jJ/disk/opt/backup/uboot/u-boot.img'
making ping/ping6 setuid root
'/tmp/tmp.UA8VtAv9jJ/disk/etc/beagle-flasher/beaglebone-black-microsd-to-emmc' -> '/tmp/tmp.UA8VtAv9jJ/disk/etc/default/beagle-flasher'
It was my mistake! I downloaded the am57xx-ubuntu-22.04.3-console-armhf-2023-09-21-4gb.img.xz instead of the am335x-ubuntu-22.04.3-console-armhf-2023-09-21-4gb.img.xz.
Will try afterworks with the am335x-ubuntu-22.04.3-console-armhf-2023-09-21-4gb.img.xz and will keep you posted.
Thank you, Vlad
I downloaded the correct image (am335x-ubuntu-22.04.3-console-armhf-2023-09-21-4gb.img.xz) and conducted a test. It is now functioning as expected!
The power button is still not effective, but that’s okay.
Thank you very much for your assistance!
I ended up flashing a
to EMMC and that saved my day. Thanks.
I also just fell into that trap with the latest minimal debian 11.8 snapshot for the BBBlue.
It’s good to hear that it can be unbricked again.