Hello, I need some help to restore my eMMC on my BeagleBone Black.
I’ve been running my BBB from a write protected SD-card and to make sure it wouldn’t boot from the onboard eMMC, I erased the the first part of the disk by running command:
Thank you, but the problem is that my Beaglebone don’t recognize my eMMC drive anymore. When I run the ‘fdisk -l’ command I just list my SD-Card(/dev/mmcblk0).
Thank you for your answer @RobertCNelson.
One thing I didn’t mention is that I have a custom cape mounted on my BeagleBone, I just realized that I can access the ‘/dev/mmcblk1’ when the cape is not mounted. When I investigate the schematics of the cape I can see that pin P8.24(MMC1_DAT1) and pin P8.25(MMC1_DAT0) is connected as ‘Digital In’-signals. Perhaps this is the problem? If so, is there any way around this?
If those pins are being used by your cape then no. If you have a custom device tree that is just setting them to digital in, but they are not being used then yes, modify the device tree to not set those pins.
Those pins are not used but the custom cape have some pull-up resistors that is holding them in high state(+3.3V). I have tried to set this pins to GND on the cape, but it seems like they must float free for the eMMC to be found by the kernel…?
Have I maybe chosen the wrong kernel for the BeagleBone Black? Have I chosen a build for BeagleBone AI?
$ cat /proc/version
Linux version 5.4.38-ti-r8 (voodoo@x4-am57xx-beagle-x15-2gb) (gcc version 8.3.0 (Debian 8.3.0-6)) #1buster SMP PREEMPT Sat May 9 09:53:15 UTC 2020
This is what’s making me wonder: (voodoo@x4-am57xx-beagle-x15-2gb)
I would certainly make sure you have the correct image. Don’t download one that starts am57xx. You would need one that starts bone. At least for newer versions.
But it appears you using something pretty old with Debian 8, so it might be that the image was the same for both boards. The main differences would be in the devicetree being loaded.
All right, thank you for your explanation.
Is there any good method to update my current image? Would it be sufficient to just update the kernel or would it be better to start from the beginning with a newer image built for AM335x?
(This is assuming it’s not using the ancient layout with a separate FAT boot partition (which beagleboard images haven’t used since the kernel 3.8 days I think); those can be made unbootable by marking the boot partition as non-bootable using fdisk, or by renaming the MLO file on it.)
Beware that even merely having a PCB trace connected to one of the eMMC pins can already degrade signal integrity on that line to the point of causing eMMC communication errors, so it may be prudent to cut those two cape header pins instead.