public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marcel <korgull@home.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] {Spam?} u-boot relocation
Date: Sun, 26 Dec 2010 22:09:58 +0100	[thread overview]
Message-ID: <201012262209.58646.korgull@home.nl> (raw)
In-Reply-To: <4D17A125.4040907@emk-elektronik.de>

On Sunday, December 26, 2010 09:10:13 pm Reinhard Meyer wrote:
> > I defined CONFIG_SYS_SDRAM_BASE and CONFIG_SYS_SDRAM_SIZE but I gave them
> > the same address and size as my previous PHYS_SDRAM and PHYS_SDRAM_SIZE.
> 
> Give them the *correct* values; however I assume they are correct.
> 
> CONFIG_SYS_TEXT_BASE must be set to the address u-boot is loaded to by the
> initial bootstrap (or directly the NOR address if it is starting from
> there).

I guess that's the case because bootstrap boots u-boot.

> U-boot will relocate itself to top of RAM. Therefore CONFIG_SYS_TEXT_BASE
> should not be near top of RAM to avoid overlap.

Since I don't understand this, I guess there may be more to this.
In my case CONFIG_SYS_TEXT_BASE is 0x73F00000

I get this :

 U-Boot 2010.12-09749-g8da60f4-dirty (Dec 26 2010 - 20:44:27)

U-Boot code: 73F00000 -> 73F3F7AC  BSS: -> 73F51B8C
CPU: AT91SAM9G45
Crystal frequency:       12 MHz
CPU clock        :      400 MHz
Master clock     :  133.333 MHz
monitor len: 00051B8C
ramsize: 08000000
TLB table at: 77ff0000
Top of RAM usable for U-Boot at: 77ff0000
Reserving 326k for U-Boot at: 77f9e000
Reserving 384k for malloc() at: 77f3e000
Reserving 24 Bytes for Board Info at: 77f3dfe8
Reserving 144 Bytes for Global Data at: 77f3df58
New Stack Pointer is: 77f3df50
RAM Configuration:
Bank #0: 70000000 128 MiB
relocation Offset is: 0409e000

How is 0409e000 near top of my RAM ?
How does it get this value ?


> > It doesn't change anything so far, so I must have missed some things I
> > guess. I'll continue reading and hope I find something. I do however
> > feel  like I'm wasting my time on this one.
> 
> I have the same frustration sometimes, however changes are not done to
> frustrate people but to make things better and more straightforward.
> Progress sometimes means making significant changes to get rid of
> ballast...
> 
> Best Regards,
> Reinhard

I know changes are for the better and that's why I try to keep in line with 
git. It's not always easy as I travel a lot and sometimes there are 2-3 months 
between updates. That's sometimes so long that things get broken, like this 
time.

Since I follow the list only when I' back in my home county I miss out a great 
deal of the communication. I just update from git and hope for the best and 
start working from there. I probably was quite unfortunate with my timing this 
time.

Thanks for your reply. I'm not sure yet if I get things correct but any clue 
certainly helps.

Best regards,
Marcel

  reply	other threads:[~2010-12-26 21:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-26 12:28 [U-Boot] {Spam?} u-boot relocation Marcel
2010-12-26 13:38 ` Reinhard Meyer
2010-12-26 19:05   ` Marcel
2010-12-26 20:10     ` Reinhard Meyer
2010-12-26 21:09       ` Marcel [this message]
2010-12-27 10:02         ` Albert ARIBAUD
2010-12-28 16:48           ` Simon Glass
2010-12-30 19:38             ` Marcel
2010-12-30 22:34               ` Marcel

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=201012262209.58646.korgull@home.nl \
    --to=korgull@home.nl \
    --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