From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm: wrong Relocation and not cleared BSS
Date: Sun, 31 Oct 2010 08:44:43 +0100 [thread overview]
Message-ID: <4CCD1E6B.9040609@denx.de> (raw)
In-Reply-To: <20101030150050.03E811522C0@gemini.denx.de>
Hello Wolfgang,
Wolfgang Denk wrote:
> Dear Albert ARIBAUD,
>
> In message <4CCC1F6C.7040603@free.fr> you wrote:
>> Could people with ARM NAND-based boards on the list test their own board >
>> with Alexander's DEBUG and printf() added, and see what this gives on >
>> their board?
>
> Here the results from tx25:
Thanks for doing this. I also made such a log for Alexander
on 27.10.2010 in u-boot%irc.freenode.org (couldn;t find this
in the history :-( ) after we foun out, that on his board
nand_chip resist on the old address before relocation ...
and I said to him, that it works fine on this board,
and ... we came to the opinion, that it maybe is a
toolchain issue ... IIRC he uses gcc-4.5x ... and
he wanted to try ELDK-4.2 ...
> U-Boot 2010.12-rc1-00026-g0c0892b-dirty (Oct 30 2010 - 16:55:43)
>
> U-Boot code: 81200000 -> 812291A0 BSS: -> 812322A0
> CPU: Freescale i.MX25 at 399 MHz
>
> monitor len: 000322A0
> ramsize: 02000000
> TLB table at: 81ff0000
> Top of RAM usable for U-Boot at: 81ff0000
> Reserving 200k for U-Boot at: 81fbd000
> Reserving 1024k for malloc() at: 81ebd000
> Reserving 24 Bytes for Board Info at: 81ebcfe8
> Reserving 92 Bytes for Global Data at: 81ebcf8c
> New Stack Pointer is: 81ebcf88
> RAM Configuration:
> Bank #0: 80000000 32 MiB
> relocation Offset is: 00dbd000
> monitor flash len: 000291A0
> Now running in RAM - U-Boot at: 81fbd000
> NAND: 128 MiB
> ## nand_chip: 81fe91a0
Yep, that look good, and I don;t think it is a code problem.
Alexander, did you tried (as you thought to do)
ELDK-4.2 with gcc-4.2.x ? Are you sure your toolchain works
correct with -pie?
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2010-10-31 7:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 13:08 [U-Boot] arm: wrong Relocation and not cleared BSS Alexander Holler
2010-10-30 13:36 ` Albert ARIBAUD
2010-10-30 13:45 ` Alexander Holler
2010-10-30 13:57 ` Albert ARIBAUD
2010-10-30 14:07 ` Alexander Holler
2010-10-30 14:39 ` Wolfgang Denk
2010-10-30 16:01 ` Albert ARIBAUD
2010-10-30 16:10 ` Wolfgang Denk
2010-10-30 14:37 ` Wolfgang Denk
2010-10-30 14:36 ` Wolfgang Denk
2010-10-31 10:59 ` Alexander Holler
2010-10-31 11:58 ` Wolfgang Denk
2010-10-31 12:21 ` Albert ARIBAUD
2010-10-31 16:18 ` Alexander Holler
2010-10-30 15:00 ` Wolfgang Denk
2010-10-30 17:21 ` Albert ARIBAUD
2010-10-30 18:01 ` Wolfgang Denk
2010-10-31 7:44 ` Heiko Schocher [this message]
2010-10-30 15:15 ` Darius Augulis
2010-10-30 16:44 ` Albert ARIBAUD
2010-10-30 20:03 ` Alexander Holler
2010-10-30 20:51 ` Alexander Holler
2010-10-31 7:47 ` Heiko Schocher
2010-11-02 5:39 ` V, Aneesh
2010-11-02 5:58 ` V, Aneesh
2010-11-02 6:32 ` Albert ARIBAUD
2010-11-02 7:18 ` V, Aneesh
2010-11-02 7:37 ` [U-Boot] Bad page state in process 'swapper' sywang
2010-11-02 7:44 ` Albert ARIBAUD
2010-11-02 8:13 ` sywang
2010-11-02 8:44 ` Wolfgang Denk
2010-11-02 8:40 ` Wolfgang Denk
2010-11-03 2:29 ` sywang
2010-11-02 7:41 ` [U-Boot] arm: wrong Relocation and not cleared BSS Albert ARIBAUD
2010-11-02 8:53 ` V, Aneesh
2010-11-02 9:04 ` Albert ARIBAUD
2010-10-31 7:43 ` Heiko Schocher
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=4CCD1E6B.9040609@denx.de \
--to=hs@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox