From: DaveKucharczyk <david.kucharczyk@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Memory test post relocation
Date: Fri, 14 Nov 2014 07:18:58 -0700 (MST) [thread overview]
Message-ID: <1415974738890-196181.post@n7.nabble.com> (raw)
In-Reply-To: <20141114092016.75296355@lilith>
Hi Albert,
Thanks for the great information.
Albert ARIBAUD (U-Boot) wrote
> Baaad, bad. The first time you change something in your code, your
> relocation offset might change and this will make U-Boot crash and burn in
> interesting ways.
>
> Just define CONFIG_SYS_TEXT_BASE to some low address and let relocation
> happen. You can find your actual relocation address in the global data
> structure.
If I set CONFIG_SYS_TEXT_BASE to a low address then I can't run a memory
test starting at the lowest address because that's where the U-Boot code
will be.
I think the best thing would be to run a memory test on the full 2GB before
relocation happens. Is that possible?
Albert ARIBAUD (U-Boot) wrote
> How do you know the lowest address used by your stack during your memory
> test?
I know the address of the stack pointer from DEBUG message...
I erroneously thought that was the beginning of the stack. The stack expands
down form that address, but how much? I don't see a global data stack size
variable.
Before, we have #define CONFIG_STACKSIZE (128 * 1024) set in the header
file.
Basically what is the best way to run the memory test? If I can run it
before relocation then it would make things very simple.
--
View this message in context: http://u-boot.10912.n7.nabble.com/Memory-test-post-relocation-tp196088p196181.html
Sent from the U-Boot mailing list archive at Nabble.com.
next prev parent reply other threads:[~2014-11-14 14:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 22:19 [U-Boot] Memory test post relocation DaveKucharczyk
2014-11-14 8:20 ` Albert ARIBAUD
2014-11-14 14:18 ` DaveKucharczyk [this message]
2014-11-14 14:27 ` Fabio Estevam
2014-11-14 14:34 ` DaveKucharczyk
2014-11-14 15:21 ` Albert ARIBAUD
2014-11-14 15:54 ` DaveKucharczyk
2014-11-14 16:07 ` DaveKucharczyk
2014-11-14 17:50 ` Albert ARIBAUD
2014-11-14 17:51 ` Albert ARIBAUD
2014-11-14 18:41 ` DaveKucharczyk
2014-11-14 20:20 ` DaveKucharczyk
2014-11-14 22:22 ` DaveKucharczyk
2014-11-15 12:13 ` Albert ARIBAUD
2014-11-15 12:26 ` Albert ARIBAUD
2014-11-15 12:37 ` Albert ARIBAUD
2014-11-14 16:15 ` 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=1415974738890-196181.post@n7.nabble.com \
--to=david.kucharczyk@gmail.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