From: Angelos Manousarides <amanous@inaccessnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Dynamic location of the environment sector
Date: Thu, 22 Jun 2006 14:02:45 +0300 [thread overview]
Message-ID: <449A78D5.1040607@inaccessnetworks.com> (raw)
In-Reply-To: <20060622104442.BC2DF3525C5@atlas.denx.de>
Wolfgang Denk wrote:
> In message <449A6F42.9090509@inaccessnetworks.com> you wrote:
>
> The only effect of this is to put the environment into a separate
> linker section. You can do this, but you don't have to. You can make
> this work without this setting es well. Just configure your linker
> script correctly.
>
>
>>My board is not on the first #if, so it felt back to the last #else,
>>thus placing the env_size and environment in the wrong order.
>
>
> This is an error in your linker script then.
My linker script is :
.text :
{
cpu/pxa/start.o (.text)
. = env_offset ;
common/environment.o (.text)
*(.text)
/**(EXCLUDE_FILE (common/environment.o) .text)*/
}
env_offset is defined at common/environment.c, and this is the defined
used by other boards as well.
BUT:
$ arm-linux-objdump -d common/environment.o
common/environment.o: file format elf32-littlearm
Disassembly of section .text:
00000000 <env_size>:
0: 00 80 00 00 ....
00000004 <environment>:
4: 85 6f 43 92 62 6f 6f 74 64 65 6c 61 79 3d 35 00
.oC.bootdelay=5.
14: 62 61 75 64 72 61 74 65 3d 31 31 35 32 30 30 00
baudrate=115200.
...
How can this be correct? All the defines are for offset 0 of this file,
but at 0 is the env_size. I also did a hexedit of the u-boot.bin and the
environment indeed starts at 0x4004 :
00004000 00 80 00 00 85 6F 43 92 62 6F 6F 74 64 65 6C 61
Regards,
Angelos Manousaridis
next prev parent reply other threads:[~2006-06-22 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 11:55 [U-Boot-Users] Dynamic location of the environment sector Angelos Manousarides
2006-06-14 14:31 ` Wolfgang Denk
2006-06-21 10:48 ` Angelos Manousarides
2006-06-21 14:11 ` Wolfgang Denk
2006-06-21 17:16 ` Angelos Manousarides
2006-06-21 17:21 ` Angelos Manousarides
2006-06-21 20:47 ` Wolfgang Denk
2006-06-21 20:46 ` Wolfgang Denk
2006-06-22 10:21 ` Angelos Manousarides
2006-06-22 10:44 ` Wolfgang Denk
2006-06-22 11:02 ` Angelos Manousarides [this message]
2006-06-26 14:57 ` Angelos Manousarides
2006-06-26 21:10 ` Wolfgang Denk
2006-06-27 9:20 ` Angelos Manousarides
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=449A78D5.1040607@inaccessnetworks.com \
--to=amanous@inaccessnetworks.com \
--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