AI-64 Update bricked device

I booted into an SD image TDA4VM Debian 11.3 2022-06-14 10GB SD XFCE , then followed the Update software on BeagleBone AI-64 page here
[ - update-ai64]

Factory Image update (without reflashing)…

sudo apt update
sudo apt install --only-upgrade bb-j721e-evm-firmware generic-sys-mods
sudo apt upgrade

Update U-Boot:

to ensure only tiboot3.bin is in boot0, the pre-production image we tried to do more in boot0, but failed…

sudo /opt/u-boot/bb-u-boot-beagleboneai64/
sudo /opt/u-boot/bb-u-boot-beagleboneai64/
sudo reboot

and now my device halts (only viewable via UART debug) with:

board_fit_image_post_process: processing image: addr=70000000, size=39864, os=arm-trusted-firmware
board_fit_image_post_process: matched image for ID 0
board_fit_image_post_process: processing image: addr=9e800000, size=374648, os=tee
board_fit_image_post_process: matched image for ID 1
board_fit_image_post_process: processing image: addr=a0000000, size=176304, os=DM
board_fit_image_post_process: matched image for ID 3
board_fit_image_post_process: processing image: addr=80080000, size=162096, os=U-Boot
board_fit_image_post_process: matched image for ID 2
board_fit_image_post_process: processing image: addr=ffffffff, size=10103, os=
Unsupported OS image.. Jumping nevertheless..
loaded - jumping to U-Boot...
init_env from device 17 not supported!
jump_to_image_no_args: jumping to address 41010000
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.5(release):e0d9fdb
NOTICE:  BL31: Built : 20:08:51, Jan  7 2022

U-Boot SPL 2021.01-g3419da0b (Jan 13 2022 - 15:29:57 +0000)
Model: Texas Instruments K3 J721E SoC
Board: BBONEAI-64-B0- rev B0
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.5.0--v2021.05 (Terrific Llam')
ti_i2c_eeprom_am6_parse_record: Ignoring record id 17
Trying to boot from MMC1 

I’ve tried re-flashing the SD again with the same results. I’m afraid this was a $200 mistake, and I misunderstood the posting for tiboot3.bin.

Any help appreciated, I cannot find any posting that help me here.
– Don C. :grimacing:

Yeap, your boot0 in the eMMC is too old… This is why i’ve told users to run:

sudo /opt/u-boot/bb-u-boot-beagleboneai64/
sudo /opt/u-boot/bb-u-boot-beagleboneai64/
sudo reboot

The quickest fix is to blank out boot0 on the eMMC…

Since you have the serial boot log, stop u-boot with the “space” key…

run emmc_erase_boot0

Or use a newer flasher images with the microSD and follow this order:

Finger on both boot and reset:
Insert power
lift finger on reset
wait till led lights
lift finger on boot.


1 Like

I must have done something out of order, thanks @RobertCNelson for getting me out of my hole and back on track with ‘boot & reset’. uboot and kernel 5.10 are new to me.

The order I used to recover, with fresh (bbai64-debian-11.3-xfce-arm64-2022-06-14-10gb.img.xz) SD card inserted:

  1. ‘boot & reset’ (see @RobertCNelson post above)
  2. run emmc_erase_boot0 (from serial port window after hitting ‘space’ to interrupt u-boot)
  3. reboot
  4. apt update
  5. apt upgrade
  8. reboot

Best regards,
– Don C.

Reference for push buttons:

Current system reference manual: BeagleBone_AI-64_System_Reference_Manual-0.0.3.pdf
Page 43

I’m having similar problem. It appears my unit is bricked, but the solution above doesn’t work for me.

If I boot with an SD it goes thru boot cycle but eventually just prints several lines of:

Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.

This repeats over and over for 30 or secs before finally erroring out with:

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/mmcblk1p2 does not exist. Dropping to a shell!

Now if boot without an SD card, I get nothing at all from serial debug…

Another curious issue is I notice no LED activity during any of this (perhaps LEDs don’t flash during SDCard boot?)

Is there any uboot commands I can to check if eMMC is ok?

Nevermind…don’t want to delete my above post in case some else searches for similar.

What I did to solve was this:

  1. Boot with SD card inserted

  2. Press space to break uboot

  3. Eject SD Card

  4. Type boot cmd

  5. Boot into Linux via eMMC, login then run

sudo /opt/u-boot/bb-u-boot-beagleboneai64/
sudo /opt/u-boot/bb-u-boot-beagleboneai64/
sudo reboot