LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mihir Punjabi <mihir124@yahoo.com>
To: u-boot@lists.denx.de, linuxppc-dev@lists.ozlabs.org,
	Linuxppc-embedded@ozlabs.org
Cc: mihir124@yahoo.com
Subject: Value of .bootpg and TEXT_BASE for ppc440 in U-Boot
Date: Tue, 17 Nov 2009 22:13:09 -0800 (PST)	[thread overview]
Message-ID: <848341.27696.qm@web51701.mail.re2.yahoo.com> (raw)

Hi,

I am currently trying to port U-Boot onto a board with PPC440x5. My board has 16MB of flash whose base address is 0xFC000000.

I have set ".bootpg" in u-boot.lds to 0xFCFFF000 (End of Flash - 4 KB) and "TEXT_BASE" in config.mk to 0xFCF80000 (End of Flash - 512 KB). I obtained an error saying "Not enough room for program headers (allocated 3, need 4)"

I get the above error even if I set ".bootpg" to 0xFCF80000 (End of Flash - 512 KB) & "TEXT_BASE" to 0xFCF00000 (End of Flash - 1 MB) - I know these are high values, but just wanted to ensure that enough space is available.
But, I still got the same error.

Can someone tell me what the problem here is? Is my understanding that ".bootpg" should be at a value (End of Flash - 4 KB) wrong?

Further, I harcoded the "SIZEOF_HEADERS" in u-boot.lds to 1024, reverted ".bootpg" to 0xFCFFF000 & "TEXT_BASE" to 0xFCF80000.

I obtained the following error:
cpu/ppc4xx/resetvec.o:(.resetvec+0x0): relocation truncated to fit: R_PPC_REL24 against symbol `_start_440' defined in .bootpg section in cpu/ppc4xx/start.o

Please let me know what exactly should .bootpg & TEXT_BASE be set to?

I am suspecting these 2 values because my code compiles successfully if I:
1) Set TEXT_BASE to 0xFFFC0000
2) Remove the hardcoding of "SIZEOF_HEADERS" & 
3) Set .bootpg to 0xFFFFF000 (set by all ppc440 boards)

Thanks and Regards,
Mihir Punjabi



      

                 reply	other threads:[~2009-11-18  6:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=848341.27696.qm@web51701.mail.re2.yahoo.com \
    --to=mihir124@yahoo.com \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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