From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ppc: How to get uboot (relocated) start address in RAM
Date: Fri, 15 Jan 2010 10:35:54 +0100 [thread overview]
Message-ID: <m2r5proglh.fsf@ohwell.denx.de> (raw)
In-Reply-To: <4B4F90D0.90604@RuggedCom.com> (Richard Retanubun's message of "Thu, 14 Jan 2010 16:46:56 -0500")
Hi Richard,
> I a world post-ppc-relocation-patch, with gd->reloc_off removed,
>
> I seem to have lost my way of figuring out uboot's address in RAM at run time.
> Previously, I am able to use (gd->reloc_off+CONFIG_SYS_MONITOR_BASE) to get the answer.
>
> Knowing the address is very useful for debuggging uboot using gdb.
>
> The only spot that works now is the dest_addr variable in lib_ppc/board.c::board_init_r
>
> debug ("Now running in RAM - U-Boot at: %08lx\n", dest_addr);
>
> But the dest_addr is not saved into a global data variable.
>
> Is it ok if I submit a patch that copies this dest_addr to gd->relocaddr
> (currently only used by CONFIG_AMIGAONEG3SE) and print it as part of bdinfo?
Actually I also realised lately that the missing reloc_off makes
debugging harder :(
> Or is there a better method I am missing?
I did not come around looking into it more closely, but your approach
seems to be a good plan. Can you please cook up a patch so we can have
a look at it?
Thanks
Detlev
--
.. the tools we are trying to use and the language we or notation we are using
to express or record our thoughts, are the major factors determining what we
can think or express at all!
-- Edsger W. Dijkstra
--
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
prev parent reply other threads:[~2010-01-15 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 21:46 [U-Boot] ppc: How to get uboot (relocated) start address in RAM Richard Retanubun
2010-01-15 9:35 ` Detlev Zundel [this message]
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=m2r5proglh.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--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