From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] changing bootcmd environment
Date: Tue, 5 Feb 2013 11:40:56 -0600 [thread overview]
Message-ID: <1360086056.26462.9@snotra> (raw)
In-Reply-To: <CALM_QrWsqsNSNZTtEqrpHaksNWKRUX-dRNMXrhqDkF9ajxf+Yw@mail.gmail.com> (from ratheendran.s@gmail.com on Mon Feb 4 22:54:52 2013)
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
next prev parent reply other threads:[~2013-02-05 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 4:54 [U-Boot] changing bootcmd environment Ratheendran R
2013-02-05 7:11 ` Ramesh K Khokhani
2013-02-05 17:40 ` Scott Wood [this message]
2013-02-06 4:25 ` Ratheendran R
2013-02-06 18:35 ` Scott Wood
2013-02-07 6:08 ` Ratheendran R
2013-02-07 17:49 ` Scott Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1360086056.26462.9@snotra \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox