This is the
new software for the EduMip project. I am not so sure about how root has anything to do right now w/ u-boot and I may not be able to reenact the issue.
I might be out.
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh was the file in question for handling the SD Card to eMMC install then.
There may be some files in
/opt/scripts. It may be a long shot but maybe there is a file in those files that is creating the eMMC build from the SD Card.
P.S. Maybe listing the contents of the /opt/scripts/tools dir. and the /opt/scripts dir. could make me remember?
ls -la /opt/scripts/tools && ls -la /opt/scripts
That output may prove useful to me so far. This is an odd circumstance that I did not know could happen w/ the BBB or BBBlue b/c of older libs, u-boot, and the kernels.
If you have the SD Card and you want to keep its contents, okay.
Maybe backup the contents of the SD Card, copy it to another SD Card, and then try to erase some eMMC first few bytes. I remember there was/is a fellow that taught me about an issue during this time.
sudo blkdiscard /dev/mmcblk1 # Or whatever the eMMC name is on that image...
Maybe also give the output of…
ls -la /dev/mmc*
Be careful to not have a backup in case the system cruds out.
When you say,
And the one form the root directory, I have not known there to be a uEnv.txt file in
But, it is acting like, from what I see,
loadxrd is causing the issue of it building to eMMC from SD Card.
I need to research older u-boot (if it is still around). Also, in the meantime, try to research u-boot and files associated w/
loadximage, loadxfdt, loadxrd, loadEnvtxt.
I will try but I cannot promise anything now. I am not well versed in uboot or changes along the way (sort of). But yes sir, I think the idea of things being compliant w/ Debian 2014-05-14 u-boot can shed light on this issue.
I researched some. I am not familiar w/ kernel 5.3.x at all. Researching kernel 5.3.x will help and learning what u-boot versioning is used via your UART0 debug header will also help in u-boot prompts.
One thing I do no get:
You are on kernel 5.3.x w/out a dtb in uEnv.txt
There is something else going on I cannot discuss for some reasoning
Did you make the image yourself? It looks and feels like a beagleboard.org image but the case of root having authority of the uEnv.txt files via u-boot is new to me.