From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6qsabresd: Add basic support
Date: Fri, 13 Apr 2012 18:14:07 +0200 [thread overview]
Message-ID: <4F8850CF.1010201@googlemail.com> (raw)
In-Reply-To: <CAOMZO5DyeLLkMTP5scVO9Ht0wYZG3_m8BuB=p2iOcTPma8S+5Q@mail.gmail.com>
On 13.04.2012 17:56, Fabio Estevam wrote:
> On Wed, Apr 11, 2012 at 6:36 PM, Wolfgang Denk<wd@denx.de> wrote:
>
>> Does testing just the first 64 KiB of RAM make any sense? Not to me.
>
> Ok, I will expand the mtest range.
>
>> BTW: where are the exception vectors located?
>
> I don't know actually, but would like to learn about it. Looked at the
> generated u-boot.map and could not find it out.
>
> Stefano,
>
> Can you please help me to find a safer DDR location for performing
> mtest on mx6? I think we probably have the same issues on other i.MX
> processors as well. Do you know how can I locate the address range
> that the exception vectors occupy?
Regarding the exception vectors:
I would think that the code of the U-Boot exception vectors are located at
#define CONFIG_SYS_TEXT_BASE 0x17800000
and
#define CONFIG_LOADADDR 0x10800000
after relocation using
http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=blob;f=arch/arm/cpu/armv7/start.S;h=ef08a55abc2c6189062c9d87c36d5d042139017c;hb=HEAD#l37
and
http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=blob;f=arch/arm/cpu/u-boot.lds;h=e49ca0c5522912ba8849182105cf141e04d0c6b3;hb=HEAD#l36
So as long as we don't have the MMU enabled, these vectors aren't used
at all. I would expect that the BootRom exception vectors at address
0x00000000 are used, instead.
I might be wrong, so people please correct me ;)
Best regards
Dirk
next prev parent reply other threads:[~2012-04-13 16:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 15:28 [U-Boot] [PATCH] mx6qsabresd: Add basic support Fabio Estevam
2012-04-11 19:49 ` Wolfgang Denk
2012-04-11 20:15 ` Fabio Estevam
2012-04-11 21:36 ` Wolfgang Denk
2012-04-13 15:56 ` Fabio Estevam
2012-04-13 16:14 ` Dirk Behme [this message]
2012-04-13 22:36 ` Fabio Estevam
2012-04-13 23:04 ` Fabio Estevam
2012-04-14 5:36 ` Dirk Behme
2012-04-14 14:41 ` stefano babic
2012-04-14 15:24 ` Fabio Estevam
2012-04-14 15:28 ` Fabio Estevam
2012-04-14 16:00 ` stefano babic
2012-04-14 20:15 ` Wolfgang Denk
2012-04-15 8:56 ` stefano babic
2012-04-14 20:14 ` Wolfgang Denk
2012-04-14 20:13 ` Wolfgang Denk
2012-04-15 9:02 ` stefano babic
2012-07-11 6:23 ` Dirk Behme
2012-07-11 8:08 ` Fabio Estevam
2012-04-12 8:23 ` Marek Vasut
2012-04-12 10:52 ` Stefano Babic
2012-09-11 3:56 ` Fabio Estevam
2012-09-11 4:27 ` stefano babic
2012-09-11 5:39 ` Dirk Behme
2012-09-11 14:43 ` Eric Nelson
2012-09-11 15:07 ` Otavio Salvador
2012-09-11 22:10 ` stefano babic
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=4F8850CF.1010201@googlemail.com \
--to=dirk.behme@googlemail.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.