On Wed, Apr 30, 2014 at 1:22 AM, Doug <[email protected]> wrote: >>> Oh those days are coming! Trust me, you'll enjoy the way i setup the >>> bootloader flashed to the eMMC in the new default debian based image. >>> It'll make things for Arch and other distro's much easier to control >>> boot, without messing with the eMMC. > > Robert, > > I am not sure what you are saying here. In one sentence you are saying > something about flashing a bootloader to the eMMC and then in the last > sentence saying not messing with the eMMC. Does the Debian uSD install > change something on the eMMC?
This is in reference to CircuitCo changing over the production boards from Angstrom to my Debian image. Which is occurring right now. So newer boards will have an update u-boot in eMMC that is a little more user friendly then the older Angstrom image. > > I am trying to come up with the best approach in distributing an Archlinux > image on uSD. that will boot without user intervention. We know that zeroing > the first 1M of blk1 will permanently fix it. Another less harmful and > reversible method is to mount blk1p1 and rename MLO to MLO.keep or > anything other than just MLO. You can rename it back and have it boot from > eMMC if you desire. > > I don't like the idea of configuring this to work (if we can) using the > current blk1p1 (eMMC boot) because that could change in the future. Our > application does not care about the eMMC at all. I wish there was no eMMC > even there. It would be great if they could make a version without it at a > cheaper or same price rather than the increase we are going to see with rev > C. It would have been as simple as putting a jumper on the board to set the > default boot. > > I think the approach we will tak is the renaming of the eMMC MLO file. A > couple of scripts distributed with our image would either turn it off or on > so the user would have the option one way or the other. YUK!!! I'm very disappointed, it is not a solution to "touch" the eMMC just to make your microSD image work. You have the knowledge to build a Archlinux image from scratch yet you can't debug u-boot/uEnv.txt over a serial connection? 1: u-boot source + patch is available 2: u-boot binary: tells you it's "boot script order" : type "printenv" 3: "uEnv.txt" is documented in so many places Disappointed, -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
