public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dave Littell <littelld@verizon.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PPC440Epx Sequoia Flash-based size limitation?
Date: Thu, 13 Mar 2008 20:33:39 -0500	[thread overview]
Message-ID: <47D9D5F3.60201@verizon.net> (raw)

Hi all,

I'm working on an AMCC PPC440EPx platform that is similar to the AMCC
Sequoia under U-Boot 1.3.1.  I've copied the Sequoia board and
configuration as a starting point, but I've run into a problem with the
size of the flash-based portion of U-Boot.  I've added code to
initdram() that results in the addition of 3-4 dozen assembly
instructions.  Now the board hangs after a very few tftp (or even ping)
commands.  However, if I remove the code I added, there's no problem
with tftp, etc.  I've narrowed it down to the point where I can make the
difference between a working and non-working load by adding just a few
instructions to initdram().  Some boundary or limit is being crossed
somewhere...

I'm sure I've overrun something somewhere but I'm afraid I'm not
literate enough in the magic of the .lds file (which is unmodified from
the Sequoia platform) to understand what adding so few instructions to
the flash-based portion of U-boot might have broken.

I've searched the FAQ and mailing list archives, all to no avail.  Does
anyone have any suggestions other that "write tighter code"?  ;-)


Thanks,
Dave

             reply	other threads:[~2008-03-14  1:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  1:33 Dave Littell [this message]
2008-03-14  6:22 ` [U-Boot-Users] PPC440Epx Sequoia Flash-based size limitation? Stefan Roese
2008-03-15  2:38   ` Dave Littell
2008-03-15  2:51   ` Dave Littell
2008-03-14  7:13 ` Niklaus Giger

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=47D9D5F3.60201@verizon.net \
    --to=littelld@verizon.net \
    --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