OK, I tried something slightly different but it doesn't boot.
fsload $addr uImage || chpart nand0,1 || fsload $addr uImage && bootm $addr
I can tell it didn't find uImage in the first partition and that it switched over to the second partition (b/c mtddevnum changes). Then it loaded uImage from the second partition, but then I get a prompt back.
Any suggestions??
Thanks,
Matt
-----Original Message----- From: wd@denx.de [mailto:wd@denx.de] Sent: Thursday, May 31, 2007 10:02 AM To: Matt Gessner Cc: u-boot-users@lists.sourceforge.net Subject: Re: [U-Boot-Users] bootcmd
In message 131AF8573CF31945B5B11E4201D3F1E142BC78@mail3.Avidyne.com
you
wrote:
setenv addr 20000000 fsload $addr uImage || fsload $addr uImage.new && bootm $addr
If the bootloader can't find uImage, try to find uImage.new.
Does that make sense? I'm using u-boot 1.2.0.
Sure, why not? Just enable the hush shell in your board config file.
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de "There are three principal ways to lose money: wine, women, and en- gineers. While the first two are more pleasant, the third is by far the more certain." -- Baron Rothschild, ca. 1800