>
> *It also seems that u-boot will try to took for uEnv.txt in several
> partitions, and seeing some "** Unable to read file uEnv.txt **" messages
> are ok.  Is this correct?*
>

No. If you have an sdcard inserted at boot it will always load the first
and second stage boot loaders from eMMC, but it will always look to the
first partition on the sdcard for uEnv.txt.

The only exception is if S2 is depressed at boot time, then the first and
second stage boot loader will be "attempted" from the sdcard first, but
uEnv.txt will still be expected to exist on the sdcard.

Many people ( yours truly included ) have in the past bemoaned this
behavior of uboot. When having a blank sdcard inserted at boot.

On Thu, Mar 17, 2016 at 10:50 PM, David Hinkes <[email protected]>
wrote:

> Thanks for the response, I appreciate it.
>
>
>> > Questions:
>> > (1) What are the requirements for the location of uEnv.txt?
>>
>> Look at the flow:
>>
>>
>> http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/am335x_evm.h;h=6ebe0b3866f9b137472cc080c9eb8f1e38233186;hb=df61a74e6845ec9bdcdd48d2aff5e9c2c6debeaa#l130
>>
>> /uEnv.txt in the first partition...
>>
>
> I tried that and no luck.
>
> I realized that I configured u-boot with am335x_boneblack_defconfig and
> instead of am335x_evm_defconfig.
>
> It also seems that u-boot will try to took for uEnv.txt in several
> partitions, and seeing some "** Unable to read file uEnv.txt **" messages
> are ok.  Is this correct?
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to