From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200
Date: Tue, 23 Nov 2004 17:51:12 +0100 [thread overview]
Message-ID: <41A36A80.2070608@imc-berlin.de> (raw)
In-Reply-To: <20041123164253.C38A7C1430@atlas.denx.de>
Wolfgang Denk wrote:
> In message <41A35A7E.1020605@imc-berlin.de> you wrote:
>
>>is there a standard way in U-Boot to prevent to the startup code from relocating
>>into RAM?
>
> No. U-Boot will always relocate itself to RAM. Well, nearly always -
> in any halfway sane implementation.
>
>
>>I know that arm920t figures out the currebt address. compares it to _TEXT_BASE
>>and decides wether to relocate or not.
>>
>>relocate: /* relocate U-Boot to RAM */
>> adr r0, _start /* r0 <- current position of code */
>> ldr r1, _TEXT_BASE /* test if we run from flash or RAM */
>> cmp r0, r1 /* don't reloc during debug */
>
>
> I wish that code was never written.
Why is that so bad? It makes it possible to debug U-Boot with just loading the
image into RAM using BDI2000.
> All CPUs always relocate the code to RAM. This is the general case.
> Anything else is not supported.
But how would you debug U-Boot?
I though the common way is to disabled relocation and memsetup, load that U-Boot
image with an BDI2000 into RAM and execute it - skipping the init code...
--
Steven
next prev parent reply other threads:[~2004-11-23 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 14:11 [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 Steven Scholz
2004-11-23 15:42 ` Steven Scholz
2004-11-23 16:42 ` Wolfgang Denk
2004-11-23 16:51 ` Steven Scholz [this message]
2004-11-23 17:18 ` Wolfgang Denk
2004-11-23 15:45 ` Wolfgang Denk
2004-11-23 15:51 ` Steven Scholz
2004-11-23 16:52 ` Wolfgang Denk
2004-11-23 17:01 ` Steven Scholz
2004-11-23 17:23 ` Wolfgang Denk
2004-11-24 12:54 ` Steven Scholz
2004-11-24 15:06 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-11-24 7:46 Friedrich, Lars
2004-11-24 10:26 ` Wolfgang Denk
2004-11-24 10:54 Paugam Luc
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=41A36A80.2070608@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--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.