[U-Boot] changing bootcmd environment

[Ratheendran R]

Thanks Scott for your valuable feedback & suggestion.

I am using the board which is uses SD Card boot & NAND boot options,SD CARD
boot is used to write firmware to be  NAND flash and used only to update
the firmware to NAND.

MOVI command may be added by the board vendor to support SD CARD
boot,curently I am having to work around by updating the config file and
recompiling the u-boot code.

Ratheendran



On Tue, Feb 5, 2013 at 11:10 PM, Scott Wood <scottwood at freescale.com> wrote:

> 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
>