> The concern I have is thatin the future if changes are made on the eMMC boot
> record as shipped it might screw up the boot of the uSD. Perhaps the best
> way to do this is just to zap the eMMC. No one is going to need the Angstrom
> code anyway and if they ever do they can recreate.
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.
It will "only" try to bootup from the microSD if it contains a small
fat partition with a "uEnv.txt" file with the variable "uenvcmd"
defined. Otherwise it always boots off eMMC.
By default it expects these 2 files and a dtbs directory in the fat partition
/zImage
/initrd.img
/dtbs/*.dtb
So if you make sure your ARCH distro has those 2 (or 3 files) saved to
the fat partition. Your uEnv.txt is as simple as:
uenvcmd=run loadimage; run loadfdt; run mmcargs; bootz ${loadaddr} - ${fdtaddr}
If you want to load /zImage * /dtbs/*black*.dtb and boot...
You can see the u-boot patch here:
https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.04/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
It also solves the "i inserted a blank/formated/etc microSD and now
the board won't boot" problem..
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
