now that I have read TFM... I find that the easier way to do this, rather than installing hush and using && would have been to
define setenv x mmcinit setenv y .... setenv z bootm setenv bootcmd run x y z in which case y would only run if x succeeded. but I like hush and don't regret doing it David In article <memo.20091021160842.44...@postmaster+dexdyne.com.cix.co.uk>, from_denx_ub...@dexdyne.com (David Collier) wrote: > *From:* "David Collier" <from_denx_ub...@dexdyne.com> > *To:* u-boot@lists.denx.de > *Date:* Wed, 21 Oct 2009 16:08 +0100 (BST) > > If I boot this unit, then remove the SD card it booted from and > reset it, > it happily boots some Linux image which is lying around in memory. > > It even does it after a short power-off power-on sequence. > > I think that's horrible behaviour. > > I was told I could use && instead of ; between the commands in the > bootcmd string to stop this, but that barfed, and then I was told > that > maybe && only existed if "scripting is enabled" > > Could anyone please talk me through the steps of either > > 1. doing what it takes to enable this && feature, so that if it > fails to > find the card, it doesn't go on and try to boot. > > or > > 2. something else that will do it, such as so effectively buggering > up an > image that has been booted from that it will never be re-used > > :-) > > TVM > > David Collier > > www.dexdyne.com > _______________________________________________ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > David Collier www.dexdyne.com _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
