From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Tue, 5 Feb 2013 11:40:56 -0600 Subject: [U-Boot] changing bootcmd environment In-Reply-To: (from ratheendran.s@gmail.com on Mon Feb 4 22:54:52 2013) Message-ID: <1360086056.26462.9@snotra> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 02/04/2013 10:54:52 PM, Ratheendran R wrote: > Dear All, > > I am using u-boot given by our Samsung based s3c2416 board vendor > which > support SD CARD based boot,I am trying to change the boot command > variable > adding few more steps to it from the serial console. The problem is > I am > not able to add all the steps to the bootcmd variable into the > environment,it is truncated midway.so can any one share your valuable > experience in fixing this issue. > > I am trying the below command.. > > setenv bootcmd "sleep 1;nand scrub ;sleep 1;nand erase;sleep 1;movi > read > 3800000# 40000 c0000000 ;sleep 1;nand write c0000000 0 40000;sleep > 1;movi > read kernel c0000000;sleep 1;nand write c0000000 40000 200000;sleep > 1;movi > read 3600000# 3800000 c0000000 ;sleep 1; nand write.yaffs c0000000 > 400000 > 35db4c0; sleep1; movi read 3600000# 3800000 c0000000; nand write.yaffs > c0000000 6000000 35db4c0" Using "nand scrub" in this manner is totally wrong. Even without scrubbing, erasing and rewriting NAND on each boot is not a good idea. It also indicates you're using an old U-Boot, as for a while now full-chip erase commands have to be written as "nand erase.chip". Plus I don't see a "movi" command in mainline U-Boot. Maybe you should be asking your board vendor for support? Why do you need all those sleep commands? You could shorten your bootcmd quite a bit by removing them... -Scott