> On Sep 28, 2015, at 16:43 , Robert Nelson <[email protected]> wrote: > > On Mon, Sep 28, 2015 at 11:11 PM, Rick Mann <[email protected]> wrote: >> Robert, do you think it would be possible to write a bash script that could >> "preflight" uEnv.txt to let you know if it would successfully boot? More >> than once this weekend, while trying to downgrade to 3.8, I left uEnv.txt in >> a bad state and U-boot couldn't continue. It seems that all those mistakes >> could've been caught by a script before booting. >> >> I just don't know how easy it would be to maintain such a script, as U-boot >> changed, it would have to change. > > #!/bin/bash > > . /boot/uEnv.txt > > if [ ! -d "/boot/dtbs/${uname_r}/" ] ; then > echo "invalid uname_r in /boot/uEnv.txt" > fi
Heh, it's more than that. For example, I had a dtb= set that it couldn't find, so it choked on that. I also have to remember to switch between 3.8-style capemgr enable/disable and 4.1-style. Those kinds of things. I might try to figure something out. Is it possible to get at the U-boot environment (bootcmd, find_ftd, uname_boot, etc?) from the logged-in bash shell after boot is complete? -- Rick Mann [email protected] -- 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.
