[U-Boot] changing bootcmd environment

[U-Boot] changing bootcmd environment

[Ratheendran R]

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"

Thanks in Advance,
Ratheendran

[U-Boot] changing bootcmd environment

[Ramesh K Khokhani]

Hi Ratheendran,

Can you tell us how much u-boot can store? Every time truncated at same location?

Send me stored string .

Regards,
Ramesh

-----Original Message-----
From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Ratheendran R
Sent: Tuesday, February 05, 2013 10:25 AM
To: u-boot at lists.denx.de
Subject: [U-Boot] changing bootcmd environment

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"

Thanks in Advance,
Ratheendran

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Information contained and transmitted by this e-mail is confidential and proprietary to iGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailadmin at igate.com <mailto:mailadmin@igate.com>. iGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of iGATE. iGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While iGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about iGATE please visit www.igate.com <http://www.igate.com>.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[U-Boot] changing bootcmd environment

[Scott Wood]

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

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

[U-Boot] changing bootcmd environment

[Scott Wood]

On 02/05/2013 10:25:41 PM, Ratheendran R wrote:
> 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.

Every time you boot?

And you should never use "nand scrub" in an automated way.

-Scott

[U-Boot] changing bootcmd environment

[Ratheendran R]

Thanks Scott

SD Card boot only to write firmware to NAND flash.

*'And you should never use "nand scrub" in an automated way.'
*
what is better way of doing this, since I am using with an old uboot..

-Ratheendran

On Thu, Feb 7, 2013 at 12:05 AM, Scott Wood <scottwood@freescale.com> wrote:

> On 02/05/2013 10:25:41 PM, Ratheendran R wrote:
>
>> 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.
>>
>
> Every time you boot?
>
> And you should never use "nand scrub" in an automated way.
>
> -Scott
>

[U-Boot] changing bootcmd environment

[Scott Wood]

On 02/07/2013 12:08:19 AM, Ratheendran R wrote:
> Thanks Scott
> 
> SD Card boot only to write firmware to NAND flash.
> 
> *'And you should never use "nand scrub" in an automated way.'
> *
> what is better way of doing this, since I am using with an old uboot..

Just remove the scrub command and use normal erase.

-Scott