Thank you for the clarification. I also was not setting uenvboot in my uEnv.txt. This was causing some confusion on my part. Now the board attempts to load the kernel.
Now the board gets to the kernel and hangs after "Loading Kernel Image ...". I'll report back when/if I get this sorted out. On Fri, Mar 18, 2016 at 2:25 AM William Hermans <[email protected]> wrote: > Just to make things perhaps a little clearer . . . > > william@beaglebone:~$ pwd > /home/william > william@beaglebone:~$ ls / > ID.txt boot etc lib media nfs-uEnv.txt proc run selinux > sys *uEnv.txt* usr > bin dev home lost+found mnt opt root sbin srv > tmp uEnv.txt.save var > > > On Fri, Mar 18, 2016 at 2:11 AM, William Hermans <[email protected]> > wrote: > >> Oh, and if you're using the eMMC only, you need to have uEnv,txt located >> in the first partition at root of the "drive". So in laymen terms . . . >> >> /uEnv.txt - Not /boot/uEnv.txt or anywhere else *unless* you modify >> uboots code before compiling. >> >> On Fri, Mar 18, 2016 at 2:08 AM, William Hermans <[email protected]> >> wrote: >> >>> *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 a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/CYFyolL6Zm8/unsubscribe. > To unsubscribe from this group and all its topics, 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.
