[U-Boot] {Spam?} u-boot relocation

Marcel korgull at home.nl
Sun Dec 26 22:09:58 CET 2010


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


More information about the U-Boot mailing list