Hello @DonTrustee ,
This may sound odd. Try to put the same images and same u-boot variants on the different mediums.
So, for instance, one would have kernel 4.19.x on the eMMC w/ u-boot 2019-10 and then the same for the SD Card.
B/c of what I described earlier, timing, development, and so on, u-boot and
kernels need to be similar if not the same if using the eMMC w/ kernel 4.19.x.
Seth
P.S. At least, from my perspective, this idea was the truth. So, from me, I say use Kernel 4.19.x and kernel 4.19.x w/ u-boot 2019-xx or whatever but have them the same for u-boot and kernel on eMMC and SD Card.
Maybe I am not making myself clear enough…
eMMC: kernel 4.19.x and u-boot 2019.10
and then…
SD Card: kernel 4.19.x and u-boot 2019.10
and so on…
W/ the updated images w/ different u-boot and kernels, beagleboard.org from what I have seen now handles the automatic source code that changes u-boot variants upon reboot or booting again after shutting down.
But since you have an older model of the image on eMMC, circa kernel 4.19.x or before which may have been Buster or an earlier Debian Distro, the source code to automatically handle u-boot variants is not automatically installed and pushed through…
I do not want to advise you on this matter, e.g. as not backing up data, while listening to me, may create an unbootable eMMC w/ all your old software/hardware unworkable.
I can keep trying to make you understand. Also, if you want…
Show this set of output from these commands:
1. ./var/scripts/tools/version.sh # This is on the eMMC
2. sudo apt install bb-beagle-version && ./bb-beagle-version # SD Card
a. number 2 is for the SD Card if you are using a newer image, 5.10.x w/ Bullseye
I will keep trying here as I have had this issue and overcame it a while back but it is persistent to specific people b/c of them using different u-boot variants on eMMC and SD Card circa kernel 4.19.x.