U-boot and Trying to Flash the BBAI-64 when the eMMC is Faulty...

Is there a way to ssh to the board outside of using the TTL to USB connector?

Seth

P.S. It registers w/ my system as unknown and not by beagleboneAI-64 or Beagle or anything else. I think I can take it from here. I just need to install it first.

No sir,

The eMMC does not boot w/ that image. I am going to try some things and report back…

Seth

P.S. Everything is back to normal. Thank you, sir.

It was a microSD image…

1 Like

Oh…and Okay,

I flashed it to SD Card. First, did the 1 - 3 picks, picked the wrong one, and then rebooted.

The board does not use that image, like you have stated, for the eMMC. It boots fine after getting it to flash to SD Card w/ a Sandisk class 10 card. I see my other classes of SD Cards are not 10 like the Sandisk. Thank you.

Seth

Just git pulled meta-ti and the device trees for ai64 have been removed.

#@TYPE: Machine
#@NAME: BeagleBone AI-64 (A72)
#@DESCRIPTION: Machine configuration for the BeagleBone AI-64 board (A72 core)

require conf/machine/include/j721e.inc

UBOOT_MACHINE = "j721e_evm_a72_config"

PREFERRED_PROVIDER_virtual/kernel = "linux-bb.org"

KERNEL_DEVICETREE = " \
ti/k3-j721e-beagleboneai64.dtb \
ti/k3-j721e-common-proc-board.dtb \
ti/k3-j721e-evm-csi2-ov5640.dtbo \
ti/k3-j721e-evm-fusion.dtbo \
ti/k3-j721e-evm-gesi-exp-board.dtbo \
ti/k3-j721e-evm-quad-port-eth-exp.dtbo \
ti/k3-j721e-evm-virt-mac-client.dtbo \
ti/k3-j721e-sk-csi2-ov5640.dtbo \
ti/k3-j721e-sk-csi2-rpi-imx219.dtbo \
ti/k3-j721e-sk-fusion.dtbo \
ti/k3-j721e-sk-rpi-hdr-ehrpwm.dtbo \
ti/k3-j721e-sk.dtb \
"

Were those not relevant, it does have a general purpose .dtb.

1 Like

Thank you!