public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Justin Waters <justin.waters@timesys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Help command broken on AT91SAM9G10-EK
Date: Fri, 13 Nov 2009 17:10:40 -0500	[thread overview]
Message-ID: <1258150240.30127.204.camel@jjw-linux> (raw)
In-Reply-To: <1258148344.8365.386.camel@localhost.localdomain>

Peter,

On Fri, 2009-11-13 at 16:39 -0500, Peter Tyser wrote:
> My guess is that somehow the end of u-boot command section is getting
> corrupted.  Perhaps the editenv patches, etc increase the size of your
> image such there's an overlap in sections that isn't reported as an
> error?  Or is the stack above the U-boot image in RAM?  Or malloc pool,
> etc?
> If you look at other commands near help (eg exit or test) in your
> System.map file, do they have the same issues as as 'help'?  Seems fishy
> that the u-boot command table is near the end of the u-boot image, and
> you're seeing issues specifically with the end of the u-boot command
> table.
> 

Brilliant.  I removed a couple of commands (USB, in particular), and it
seems to be working fine.  No garbled messages, no system halt.

I'll look into this some more on Monday.  It seems to only affect the
9261/9G10 family.  Everything works fine on the 9G20 and 9263.

Thank you for your help!  editenv is a really nice addition, by the way.

> Best,
> Peter

Thanks,
Justin

  reply	other threads:[~2009-11-13 22:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13 16:10 [U-Boot] Help command broken on AT91SAM9G10-EK Justin Waters
2009-11-13 16:49 ` Tom
2009-11-13 16:50 ` Peter Tyser
2009-11-13 17:01   ` Justin Waters
2009-11-13 17:50     ` Peter Tyser
2009-11-13 21:24       ` Justin Waters
2009-11-13 21:39         ` Peter Tyser
2009-11-13 22:10           ` Justin Waters [this message]
2009-11-13 22:37             ` Justin Waters

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=1258150240.30127.204.camel@jjw-linux \
    --to=justin.waters@timesys.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