public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nitin Mahajan <nitinm76@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] bootcounter implementation for OMAP3
Date: Tue, 9 Mar 2010 21:04:23 -0800 (PST)	[thread overview]
Message-ID: <806215.16680.qm@web50105.mail.re2.yahoo.com> (raw)
In-Reply-To: <m2zl2hfm11.fsf@ohwell.denx.de>

Hello,

--- On Tue, 9/3/10, Detlev Zundel <dzu@denx.de> wrote:

> From: Detlev Zundel <dzu@denx.de>
> Subject: Re: [U-Boot] bootcounter implementation for OMAP3
> To: nitinm76 at yahoo.com
> Cc: u-boot at lists.denx.de
> Date: Tuesday, 9 March, 2010, 10:52 PM
> Hi Nitin,
> 
> >> You are writing a 32 bit entity to an non 32-bit
> aligned address.
> >> Although I do not know the omap too well, this can
> be a problem on
> >> any architecture.
> >> 
> >> Can you write 32-bot to that exact address from
> within the U-Boot
> >> commandline with e.g. "mm"?
> >
> > That was the basic mistake I think. I was trying to
> write to a non 32
> > bit aligned address. This got solved, but I have some
> new errors
> > saying this
> 
> Ok, thanks for the confirmation.
> 
> > ## Error: environment overflow, "stdin" deleted?
> ? ? ? ? ? ? ? ?
> ? ? ? ? ? ?
> ???
> > ## Error: environment overflow, "stdout" deleted?
> ? ? ? ? ? ? ? ?
> ? ? ? ? ? ? ? 
> > ## Error: environment overflow, "stderr" deleted
> > ## Error: environment overflow, "bootcount" deleted 
> 
> [dzu at pollux u-boot-testing (master)]$ git grep "environment
> overflow"
> common/cmd_nvedit.c:? ? ? ? ?
> ? printf ("## Error: environment overflow, \"%s\"
> deleted\n", name);
> tools/env/fw_env.c:? ? ? ? ?
> ? ? ? ? ???"Error:
> environment overflow, \"%s\" deleted\n",
> 
> > Does that mean the size allocated for env is smaller
> compared to the
> > actual contents in env file.? I am new to u-boot.
> Can you give some
> > pointers on this?
> 
I just increased the size in my board specific configuration file. Now this feature of bootlimit and altbootcmd works for me on OMAP3.

Thanks for your time. 

I was just wondering how to recover from errors such as bad CRC on uImage, where boot loader is not able to start booting the kernel for any reason.

In such case how to fallback to a different kernel.

-Nitin


> Only you can answer what you have defined for your
> configuration.
> 
> Cheers
> ? Detlev
> 
> -- 
> He who can properly define and divide is to be considered a
> god.
> ? ? ? ? ? ? ? ?
> ? ? ? ? ? ? ? ?
> ? ? ? ? -- Plato
> --
> DENX Software Engineering GmbH,? ? ? MD:
> Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich,? Office: Kirchenstr.5, D-82194
> Groebenzell, Germany
> Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email:
> dzu at denx.de
> 


      New Email names for you! 
Get the Email name you&#39;ve always wanted on the new @ymail and @rocketmail. 
Hurry before someone else does!
http://mail.promotions.yahoo.com/newdomains/aa/

  reply	other threads:[~2010-03-10  5:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09  3:46 [U-Boot] bootcounter implementation for OMAP3 Nitin Mahajan
2010-03-09  8:33 ` Detlev Zundel
2010-03-09 11:53   ` Nitin Mahajan
2010-03-09 17:22     ` Detlev Zundel
2010-03-10  5:04       ` Nitin Mahajan [this message]
2010-03-10  6:28         ` Wolfgang Denk

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=806215.16680.qm@web50105.mail.re2.yahoo.com \
    --to=nitinm76@yahoo.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