All of lore.kernel.org
 help / color / mirror / Atom feed
From: calvin <mailofpooja@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: GOT pointer in U-boot
Date: Sat, 06 Nov 2004 17:40:33 +0530	[thread overview]
Message-ID: <cmif0k$kq6$1@sea.gmane.org> (raw)
In-Reply-To: <20041105142243.0D34FC1430@atlas.denx.de>

Wolfgang Denk wrote:
> In message <cmfvr3$61o$1@sea.gmane.org> you wrote:
>
> You will need to dig into the GCC / ld documentation  if  you  really
> want  to  understand  what's  going on there. [On the other hand it's
> usually safe to ignore this; the relevant problems have already  been
> solved for MIPS and the other supported architectures.]
> 

Thanks for your time Wolfgang.

But Even if I ignore GOT pointer my problem still persists. The problem 
of bootloader trying to jump to an address which does not exist.

I compile for ROM version(config.mk) the code downloads in flash but 
when it relocates itself to SDRAM, the address it tries to jump is a 
"valid" SDRAM address but I don't see that address anywhere in 
u-boot.dis. All the addresses in u-boot.dis are relative to the 
TEXT_BASE I have given in ROM version.

Do I need to make some changes in linker file ? For the same board and 
YAMON bootloader the disassembled file has initial flash addresses and 
then SDRAM addresses for opcodes after the code is relocated. I am not 
expecting the same from u-boot but I am unable to understand u-boot 
policy regarding this.


Thanks and regards,
Pooja


> Best regards,
> 
> Wolfgang Denk
> 

  reply	other threads:[~2004-11-06 12:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 13:39 [U-Boot-Users] GOT pointer in U-boot calvin
2004-11-05 14:22 ` Wolfgang Denk
2004-11-06 12:10   ` calvin [this message]
2004-11-06 13:30     ` [U-Boot-Users] " 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='cmif0k$kq6$1@sea.gmane.org' \
    --to=mailofpooja@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 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.