From: DaveKucharczyk <david.kucharczyk@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Memory test post relocation
Date: Thu, 13 Nov 2014 15:19:20 -0700 (MST) [thread overview]
Message-ID: <1415917160763-196088.post@n7.nabble.com> (raw)
We have 2GB?s of RAM starting at 0x70000000 on our Freescale MX53 based
board.
With old U-Boot we defined TEXT_BASE at the bottom of RAM at 0x70600000 and
CONFIG_SKIP_RELOCATE_UBOOT, presumably so that we can run memory tests all
the way to the top of RAM (this was brought over from the mx53loco board and
precedes me). Why else would CONFIG_SKIP_RELOCATE_UBOOT be set?
In new U-Boot we are not skipping relocation. I define CONFIG_SYS_TEXT_BASE
= 0xeff89000 so that relocation offset is 0x00000000.
I run with DEBUG on to doublecheck where things get setup?
I run a memory test from 0x70000000 to 0xefe88cb0, but I get a mismatch fail
at 0xefe88aa4.
Shouldn?t I be able to run mem test all the way to the stack? I don?t see
anything else being setup under the stack.
--
View this message in context: http://u-boot.10912.n7.nabble.com/Memory-test-post-relocation-tp196088.html
Sent from the U-Boot mailing list archive at Nabble.com.
next reply other threads:[~2014-11-13 22:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 22:19 DaveKucharczyk [this message]
2014-11-14 8:20 ` [U-Boot] Memory test post relocation Albert ARIBAUD
2014-11-14 14:18 ` DaveKucharczyk
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=1415917160763-196088.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