[U-Boot] About mtest on boot

[Érico Porto]

Oh, found the Memory Management section, thanks! And it also explains that
stuff should be written after 0x0000 2000 because of the exception vector -
actually, I thinks this is a bit bigger here in my system, but now makes
sense why I was also getting crashes at the beginning of the memory!

Érico V. Porto


On Mon, Jan 23, 2012 at 12:45 PM, Wolfgang Denk <wd at denx.de> wrote:

> Dear =?ISO-8859-1?Q?=C9rico_Porto?=,
>
> Please stop top posting / full quoting.
>
> In message <CAG1KTJebU-QhhH2=
> iBFOjSJJvAynH4hRfuzoBnwZ20UZq-5JLw at mail.gmail.com> you wrote:
> >
> > Ok, this makes sense, but I think you mean:
>
> No, I mean what I mean, not what you think I mean.
>
> > memory start at 0x00000000
> >
> > mtest {
> > start address: right after (malloc area+global data + stack)
> > end address: relocaddr
> > }
> >
> > memory end at 0x08000000
>
> Wrong.
>
> Assuming you have a simple configuration (no pRAM, no log buffer, no
> video buffer etc.) then the memory map (as explained in the README,
> btw) is like that:
>
> top of RAM (in your case 0x08000000 - 1)
> ...     U-Boot code, data and bss
> relocaddr
> ...     Malloc Arena
> ...     Board Info Data and permanent copy of global data
> ...     Stack (growing downward)
>
>
> Depending on the size of your malloc arena you need to stay far enough
> away from relocaddr;  try with 1 MB or more.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> For every complex problem, there is a solution that is simple,  neat,
> and wrong.                                           -- H. L. Mencken
>