From: "Andreas Bießmann" <andreas@biessmann.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Boot failure with a AT91RM9200 based custom board
Date: Wed, 17 Aug 2016 13:03:34 +0200 [thread overview]
Message-ID: <6bb8a416bbfd3f4facce996959977d01@biessmann.de> (raw)
In-Reply-To: <CAGWZb2j50_ZW=N8d0gvAE_iK-ahv2kLxBVrWiMiHDFXBuZutVg@mail.gmail.com>
Hi Peter,
On 2016-08-17 11:31, Peter Kardos wrote:
> On Mon, Aug 15, 2016 at 10:43 PM, Andreas Bie?mann
> <andreas@biessmann.org> wrote:
>
>> Dear Peter,
>>
>> On 12.08.16 02:24, Peter Kardos wrote:
<snip>
>>> RAM Configuration:
>>> Bank #0: 20000000 64 MiB
>>>
>>> DRAM: 64 MiB
>>> initcall: 1000b424
>>> New Stack Pointer is: 23f23ed0
>>> initcall: 1000b6ac
>>> initcall: 1000b640
>>> Relocation Offset is: 13f84000
>>> Relocating to 23f84000, new gd at 23f23ef0, sp at 23f23ed0
>>
>> Could you please check, if the RAM initialisation is working
>> properly?
>> AFAIR there was some problem with the u-boot RAM initialisation
>> for this
>> board but never fixed (shame on me). Some set of known data and
>> read
>> back before relocation should do the check.
>
> Yeah, this is my guess as well, as things seem to work up to this
> point (continue exec from RAM).
>
> Thanks for the pointer, i'll have a look at the init magic and compare
> it with the old from v1.1.4.
Would be great if you come with a solution, so I could fix the
at91rm9200ek board too.
> I guess the easiest way would be to mod the relocation routine and
> read back what was written...
sounds good as a quick test
Andreas
prev parent reply other threads:[~2016-08-17 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 0:24 [U-Boot] Boot failure with a AT91RM9200 based custom board Peter Kardos
2016-08-15 20:43 ` Andreas Bießmann
[not found] ` <CAGWZb2j50_ZW=N8d0gvAE_iK-ahv2kLxBVrWiMiHDFXBuZutVg@mail.gmail.com>
2016-08-17 11:03 ` Andreas Bießmann [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=6bb8a416bbfd3f4facce996959977d01@biessmann.de \
--to=andreas@biessmann.org \
--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.