All of lore.kernel.org
 help / color / mirror / Atom feed
From: himbA <goavr@email.si>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] mtest
Date: Fri, 02 Apr 2004 17:46:55 +0200	[thread overview]
Message-ID: <406D8AEF.5010301@email.si> (raw)
In-Reply-To: <20040402124435.3ECD2C109F@atlas.denx.de>

Wolfgang Denk wrote:
> In message <406D56A5.2090102@email.si> you wrote:
> 
>>at bootup uboot displays
>>U-Boot code: A3F00000 -> A3F177B8  BSS: -> A3F1BAD8
>>
>>Is there some uboot relevant stuff between 
>>0xa3efffff - 0xa3dfffff that I run over when doing 
>>mtest on all 63Mb? Code and stack seem to be safe.
> 
> 
> What do you think where the stack and the malloc  arena  is  in  your
> configuration?
> 

I thought code starts at _TEXT_BASE (0xA3F00000) 
and stack is from  0xA3F177B8 to 0xA3F1BAD8 
(u-boot header display suggested so). Your 
question was in place and I checked the start.S 
once again to find out that after reset and 
relocate we setup stack below _TEXT_BASE and not 
above. I corrected the CFG_MEMTEST_END to be just 
below malloc and stack.

  Thanks!

regards, himba

-- 
..because under Linux "if something is possible in 
principle,
then it is already implemented or somebody is 
working on it".
							--LKI

  reply	other threads:[~2004-04-02 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02  7:33 [U-Boot-Users] mtest himbA
2004-04-02  8:33 ` Wolfgang Denk
2004-04-02  9:12   ` himbA
2004-04-02 11:21     ` Wolfgang Denk
2004-04-02 12:03       ` himbA
2004-04-02 12:44         ` Wolfgang Denk
2004-04-02 15:46           ` himbA [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-02 13:02 VanBaren, Gerald
2004-04-05  6:57 ` himbA

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=406D8AEF.5010301@email.si \
    --to=goavr@email.si \
    --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.