I have multiple BBAI64 and tried to copy a Yocto-based image onto the EMMC. Unfortunately, I did something wrong and now when booting the original beaglebone-debian [bbai64-debian-11.7-minimal-arm64-2023-05-03-4gb.img.xz] from SDCARD it can not access the EMMC anymore… The EMMC device (mmcblk0) is not available anymore (it doesn’t show with lsblk, and is not showing in /dev. Therefore, the corresponding flasher doesn’t work anymore.
During boot-up the following additional messages compared to a working BBAI64 are shown on the console:
Hi @bernd sadly i haven’t seen that issue before, any chance do you have the serial adapter so we can see what u-boot does at startup? Wondering if it’s detecting the wrong board, and thus doing the wrong pinmux…
You mentioned that the mmcblk0 device doesn’t even show up in /dev. That means it’s not responding at all.
If you do see /dev/mmcblk0, but just don’t see any partitions for it, then you can rewrite the partition(s) and filesystem(s) manually if you absolutely had to (google-searche for fdisk usages).
Usually that’s unnecessary if you have an ISO of what’s supposed to be in the eMMC since ISO images should include everything that goes into the flash including partition table and filesystem formatting. This is why making a direct transfer of an ISO to /dev/mmcblk0 using dd works.
But like I said, if /dev/mmcblk0 is not even showing up, that suggests the processor is failing to get a response from the flash chip. Whether that’s dead eMMC chip, bad solder joints, or a problem in the TDA4VM, the result is the same.