From: Magnus Lilja <lilja.magnus@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Uboot md crash on PDK
Date: Tue, 14 Apr 2009 22:31:22 +0200 [thread overview]
Message-ID: <59b21cf20904141331o7cc6fb0ai6c170e4f74e3994e@mail.gmail.com> (raw)
In-Reply-To: <528f13590904141319y586a436awdfa1325d81bcbe4f@mail.gmail.com>
2009/4/14 alfred steele <alfred.jaquez@gmail.com>:
> Thanks!
> But should a crash happen if i am trying to read a non-reserved memory
> which ?0x100000 is.
That's up to the hardware (i.e. i.MX31), I don't know the details but
crashing seems perfectly fine with me (or generating a data abort
interrupt).
> Can you tell me how do you choose a address in CSDO RAM to be
> appropiate for loading uImage and execute it.
Any address within the range of the mounted RAM is fine, as long as
you don't load it to where U-boot is residing in RAM, also avoid
loading it to where the kernel parameters are passed.
And could you please stop top-posting.
Best regards, Magnus
>
> -Alfred.
>
> On Mon, Apr 13, 2009 at 12:24 PM, Magnus Lilja <lilja.magnus@gmail.com> wrote:
>> 2009/4/13 alfred steele <alfred.jaquez@gmail.com>:
>>> Hi Magnus,
>>>
>>> For that matter, I can dump memory between 0x0000 and 0x00000100
>>> though. However memory dump at ?0x100000 also fails.
>>>
>>> Can you point out which pages in the Reference manual point to the same?
>>
>> Chapter 2-1 "Memory map". in MCIMX31RM "Reference Manual".
>>
>> Regards, Magnus
>>
>
next prev parent reply other threads:[~2009-04-14 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 17:13 [U-Boot] Uboot md crash on PDK alfred steele
2009-04-09 17:53 ` Magnus Lilja
2009-04-13 13:53 ` alfred steele
2009-04-13 17:24 ` Magnus Lilja
2009-04-14 20:19 ` alfred steele
2009-04-14 20:31 ` Magnus Lilja [this message]
2009-04-14 21:02 ` alfred steele
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=59b21cf20904141331o7cc6fb0ai6c170e4f74e3994e@mail.gmail.com \
--to=lilja.magnus@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 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.