In article <610d18d1f0bb204d8ab39bb1c42187e8041e7...@lonmlvem09.e2k.ad.ge.com>, nick.thomp...@gefanuc.com (Thompson, Nick (GE EntSol, Intelligent Platforms)) wrote:
> *From:* "Thompson, Nick (GE EntSol, Intelligent Platforms)" > <nick.thomp...@gefanuc.com> > *To:* <from_denx_ub...@dexdyne.com>, <u-boot@lists.denx.de> > *Date:* Wed, 21 Oct 2009 16:39:18 +0100 > > > -----Original Message----- > > From: u-boot-boun...@lists.denx.de > > [mailto:u-boot-boun...@lists.denx.de] On Behalf Of David Collier > > Sent: 21 October 2009 16:08 > > To: u-boot@lists.denx.de > > Subject: [U-Boot] stopping u-boot from booting an old image in > > RAM. > > > > 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 > > Probably a simple mw (memory write) to the entry point of linux, > before > You attempt to reload the image, would do the trick? > > Usage: > mw [.b, .w, .l] address value [count] > > Nick. so something like #define CONFIG_BOOTCOMMAND \ "mmcinit ; mw 0x10400000 55 ; ext2load mmc 0:1 0x10400000 /boot/uImage ; bootm 0x10400000" ???? That looks simple enough David Collier www.dexdyne.com _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot