I was informed that the following is invoked by U-Boot:
env import -t -r $loadaddr $filesize
I’m not sure what the flags do and have so far been unable to find documentation for them. But I believe this is acting on an environment that has been loaded in a previous command.
What is the previous step to load this? In other words, where is U-Boot looking for the uEnv.txt?
The Partition 2.0 document was vague (to me) on this point. Probably makes sense in some context.
It isn’t clear to me from this page either. It seems to imply that it will search for it on /boot of the root filesystem. My one and only bootable partition is EXT4 so it would require calling ext4load (I believe). The output is trying to do something with the MMC but never finds what it is looking for. I’m not sure which image it is trying to load. Surprised there isn’t a message somewhere saying “Trying to load environment” or “Trying to load Kernel” or whatever.
Using U-Boot 2017.01.
`
=> boot
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
** File not found boot.scr **
** Unrecognized filesystem type **
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
** Invalid partition 2 **
** First descriptor is NOT a primary desc on 1:1 **
switch to partitions #0, OK
mmc1(part 0) is current device
** No partition table - mmc 1 **
** First descriptor is NOT a primary desc on 1:1 **
switch to partitions #0, OK
mmc1(part 0) is current device
** First descriptor is NOT a primary desc on 1:1 **
SD/MMC found on device 1
** No partition table - mmc 1 **
Error: “bootcmd_nand0” not defined
starting USB…
USB0: Port not available.
cpsw Waiting for PHY auto negotiation to complete…
`