From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] [PATCH V2] arm: arm926ejs: use ELF relocations
Date: Tue, 05 Oct 2010 10:41:35 +0200 [thread overview]
Message-ID: <4CAAE4BF.3030306@free.fr> (raw)
In-Reply-To: <4CAAE2C5.4040304@denx.de>
Le 05/10/2010 10:33, Heiko Schocher a ?crit :
> Hello Reinhard,
>
> Reinhard Meyer wrote:
>> I _think_ the linker file needs a .align there:
>>
>> (.data ends with a non-aligned address!)
>
> actually trying on the tx25 board, and I see a hang after
> the dram output too:
>
> DRAM: 32 MiB
>
> I inserted a breakpoint in start.S at clear_bss, never reached...
>
> Maybe the fixloop
>
> start.S:
> [...]
> fixnext:
> str r1, [r0]
> add r2, r2, #8 /* each rel.dyn entry is 8 bytes */
> cmp r2, r3
> ble fixloop
> #endif
> #endif /* #ifndef CONFIG_SKIP_RELOCATE_UBOOT */
>
> clear_bss:
>
> never reaches a end ... but just debugging it ...
>
> register dump in fixloop:
>
> TX25>ti;r
> Core number : 0
> Core state : debug mode (ARM)
> Debug entry cause : Single Step
> Current PC : 0x812000d8
> Current CPSR : 0x800000d3 (Supervisor)
> GPR00: 81fbe020 81fbe1a0 81224364 812285cc
> GPR04: 81ebdf88 81ebdf8c 81fe6ac8 81fbe000
> GPR08: 00000017 00dbe000 812285cc 00000000
> GPR12: 00000000 81ebdf88 812006f4 812000d8
> PC : 812000d8 CPSR: 800000d3
> TX25>
>
> r2 and r3 are a multiple of 8, so this must end, but never
> see it ending ...
Ihe loop exit test is a ble, not a bne, so even if r2 or r3 were not
properly aligned, this should still exit eventually.
A reason why it would not, though, is if the loop trashes the code in
RAM. That can happen if e.g. TEXT_BASE is wrong (my bad). In two hour's
time I will build (not test) for tx25 and then do a quick check on the
content of .rel.dyn and .dynsym in the resulting u-boot.
> bye,
> Heiko
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-10-05 8:41 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 6:31 [U-Boot] [RFC] [PATCH V2] arm: arm926ejs: use ELF relocations Albert Aribaud
2010-10-05 6:45 ` Wolfgang Denk
2010-10-05 7:05 ` Reinhard Meyer
2010-10-05 7:23 ` Reinhard Meyer
2010-10-05 7:52 ` Reinhard Meyer
2010-10-05 8:33 ` Heiko Schocher
2010-10-05 8:41 ` Albert ARIBAUD [this message]
2010-10-05 9:00 ` Heiko Schocher
2010-10-05 9:10 ` Reinhard Meyer
2010-10-05 9:15 ` Heiko Schocher
2010-10-05 9:19 ` Reinhard Meyer
2010-10-05 9:29 ` Heiko Schocher
2010-10-05 9:33 ` Reinhard Meyer
2010-10-05 9:39 ` Reinhard Meyer
2010-10-05 10:11 ` Albert ARIBAUD
2010-10-05 10:36 ` Reinhard Meyer
2010-10-05 10:49 ` Graeme Russ
2010-10-05 11:01 ` Reinhard Meyer
2010-10-05 11:18 ` Albert ARIBAUD
2010-10-05 10:33 ` Albert ARIBAUD
2010-10-05 10:40 ` Wolfgang Denk
2010-10-05 11:10 ` Albert ARIBAUD
2010-10-05 11:17 ` Reinhard Meyer
2010-10-05 11:46 ` Albert ARIBAUD
2010-10-05 13:18 ` Reinhard Meyer
2010-10-05 13:24 ` Graeme Russ
2010-10-05 13:36 ` Albert ARIBAUD
2010-10-05 14:06 ` Reinhard Meyer
2010-10-05 11:43 ` Wolfgang Denk
2010-10-05 10:20 ` Albert ARIBAUD
2010-10-05 8:27 ` Wolfgang Denk
2010-10-05 8:38 ` Reinhard Meyer
2010-10-05 8:50 ` Albert ARIBAUD
2010-10-05 8:59 ` Reinhard Meyer
2010-10-05 7:07 ` Wolfgang Denk
2010-10-05 7:40 ` Heiko Schocher
2010-10-05 8:32 ` Albert ARIBAUD
2010-10-05 8:02 ` Wolfgang Denk
2010-10-05 9:25 ` Heiko Schocher
2010-10-05 9:32 ` Albert ARIBAUD
2010-10-05 12:07 ` Heiko Schocher
2010-10-05 12:52 ` 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=4CAAE4BF.3030306@free.fr \
--to=albert.aribaud@free.fr \
--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.