All of lore.kernel.org
 help / color / mirror / Atom feed
From: rudresh <rudresh.tk@lntemsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] saveenv command erases flash u-boot
Date: Tue, 24 Feb 2009 03:46:33 -0800 (PST)	[thread overview]
Message-ID: <22180261.post@talk.nabble.com> (raw)
In-Reply-To: <1ba63b520902240156n15e613f0x61f2fd7be460d85c@mail.gmail.com>


i fix this issue with the help of all u-boot USERS, Thanks for helping .. 
This problem occurred because of u-boot.bin size taking 2 sector of Flash,
and less space for Environment(few bytes in 2nd sector) . Then i incremented
one sector in config env address , shown below.
#define CFG_ENV_ADDR		(CFG_MONITOR_BASE + 0x60000) // before
CFG_MONITOR_BASE+0x40000

This help's me to solve this problem

Thanks
Rudresh



Frank Svendsb?e wrote:
> 
> Hi Norbert,
> I just looked at your comment in the gmane archive. You shouldn't
> hardcode a new CONFIG_ENV_ADDR. Instead, you should correct the
> CONFIG_SYS_MONITOR_LEN, which is the number of bytes the U-Boot
> image uses rounded up to the next flash sector address.
> 
> Maybe we should define this in terms of new CONFIG variables, say
> CONFIG_SYS_FLASH_SECT_SIZE and
> CONFIG_SYS_NUM_U_BOOT_SECTS, and then compute the new *_LEN
> based on these? Alternatively, we can avoid using defines and instead make
> it
> a "const volatile unsigned long". Then we could use a post build
> script to extract
> the image length from u-boot.map and compare it with u-boot.bin. If the
> value
> extracted from the map file is less than the u-boot.bin size, we could
> generate
> an error/warning. Any comments?
> 
> Best regards,
> Frank
> 
> On Tue, Feb 24, 2009 at 10:09 AM, Norbert van Bolhuis
> <nvbolhuis@aimvalley.nl> wrote:
>> rudresh wrote:
>>> i'm using u-boot -1.3.0 in MPC8313 evaluation board, it having a NAND ,
>>> NOR
>>> Flash , u-boot stored in NOR flash. when i do the saveenv , reset
>>> command
>>> the u-boot is erased. i'm not able to fix ?this issue. ?help me to fix
>>> this
>>> issue
>>>
>>> Thanks
>>> Rudresh
>>>
>>>
>>>
>>>
>>
>> I had a similar problem, see:
>>
>> http://article.gmane.org/gmane.comp.boot-loaders.u-boot/51703/match=config%5fenv%5faddr+incorrect+mpc8313erdb+h
>>
>> ---
>> N. van Bolhuis.
>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 
> 

-- 
View this message in context: http://www.nabble.com/saveenv-command-erases-flash-u-boot-tp22156928p22180261.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

  reply	other threads:[~2009-02-24 11:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23  7:56 [U-Boot] saveenv command erases flash u-boot rudresh
2009-02-23  8:11 ` Michael Lawnick
2009-02-23 11:40   ` rudresh
2009-02-23 12:24     ` Michael Lawnick
2009-02-23  9:34 ` Wolfgang Denk
2009-02-23 11:46   ` rudresh
2009-02-23 12:04     ` Wolfgang Denk
2009-02-24  9:09 ` Norbert van Bolhuis
2009-02-24  9:56   ` Frank Svendsbøe
2009-02-24 11:46     ` rudresh [this message]
2009-02-24 12:01     ` Norbert van Bolhuis
2009-02-24 13:07       ` Frank Svendsbøe

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=22180261.post@talk.nabble.com \
    --to=rudresh.tk@lntemsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.