On Mon, Sep 8, 2014 at 8:22 PM, Jason Lange <j.b.la...@gmail.com> wrote: > > > On Mon, Sep 8, 2014 at 4:25 AM, Robert Nelson <robertcnel...@gmail.com> > wrote: >> >> >> u-boot older then: v2014.07 (with my patch) >> >> /uEnv.txt (in fat partition) loads /boot/uEnv.txt (in ext4 partition) >> >> u-boot newer then: v2014.07 (with my patch) >> >> u-boot finds /boot/uEnv.txt in any partition (1 -> 7) >> >> Regards, > > > So, the ext4 /uEnv.txt is just cruft?
If the "ext4" is the only partition the "/uEnv.txt" is there for old boot-loaders. Basically, my goal is to stay compatible with Angstrom's 2013.06.20 release. My "images" should boot from microSD if the Angstrom 2013.06.20 release is flashed to eMMC.. Between last week's release and the July one, we had regressed on that goal. But we got those bugs worked out.. u-boot's actually searching for a few different boot files 1: microsd: Partition 1: /uEnv.txt /boot.scr /boot/boot.scr Parition 1->7 /boot/uEnv.txt 2: eMMC Partition 1: /uEnv.txt /boot.scr /boot/boot.scr Parition 1->7 /boot/uEnv.txt I've also been adding lots of debugging info to u-boot to help users hints: (here's my current wip off v2014.10-rc2, the last two debug lines before the kernel goes off should really help users..) mmc0 is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 Checking for: /uEnv.txt ... Checking for: /boot.scr ... Checking for: /boot/boot.scr ... Checking for: /boot/uEnv.txt ... gpio: pin 55 (gpio 55) value is 1 799 bytes read in 53 ms (14.6 KiB/s) Loaded environment from /boot/uEnv.txt Checking if uname_r is set in /boot/uEnv.txt... gpio: pin 56 (gpio 56) value is 1 Running uname_boot ... loading /boot/vmlinuz-3.14.17-ti-r18.1 ... 6937752 bytes read in 438 ms (15.1 MiB/s) loading /boot/dtbs/3.14.17-ti-r18.1/am335x-boneblack.dtb ... 64941 bytes read in 119 ms (532.2 KiB/s) debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait fixrtc quiet] ... debug: [bootz 0x82000000 - 0x88000000] ... Kernel image @ 0x82000000 [ 0x000000 - 0x69dc98 ] ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Device Tree to 8ffed000, end 8ffffdac ... OK Starting kernel ... Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.