* [ECOS] arm-elf-objdump
@ 2004-07-26 15:55 Aravind B
2004-07-27 10:02 ` Nick Garnett
0 siblings, 1 reply; 4+ messages in thread
From: Aravind B @ 2004-07-26 15:55 UTC (permalink / raw)
To: ecos
>Aravind B <arvindb@cranessoftware.com> writes:
> hi,
> i am trying to convert .elf file to .hex file.
> But i am getting BFD: stYsHp0e: warning: allocated section `.bss' not
>in
> segment.
> Since the BSS should not be part of the hex file, it is not at all
> clear why this message is being generated. What options are you giving
> objcopy?
I am using fololowing option to generate .hex file:
arm-elf-objcopy -O ihex $(EXECUTABLE).elf $(EXECUTABLE).hex
> Note that it is just a warning, maybe the resulting HEX file is
> correct.
> after running the command arm-elf-objdump -h i have got the following
> information
>
> Sections:
> Idx Name Size VMA LMA File off Algn
> 0 .rom_vectors 00000040 40000000 40000000 00008000 2**0
> CONTENTS, ALLOC, LOAD, READONLY, CODE
> 1 .text 0002cea8 40000040 40000040 00008040 2**2
> CONTENTS, ALLOC, LOAD, READONLY, CODE
> 2 .fini 00000000 4002cee8 4002cee8 0004868c 2**0
> CONTENTS
> 3 .rodata 0000c614 4002cee8 4002cee8 00034ee8 2**2
> CONTENTS, ALLOC, LOAD, READONLY, DATA
> 4 .rodata1 00000000 400394fc 400394fc 0004868c 2**0
> CONTENTS
> 5 .fixup 00000000 400394fc 400394fc 0004868c 2**0
> CONTENTS
> 6 .gcc_except_table 00000000 400394fc 400394fc 0004868c 2**0
> CONTENTS
> 7 .fixed_vectors 00000140 10000020 10000020 000486a0 2**5
> CONTENTS, READONLY
> 8 .data 0000068c 10008000 400394fc 00048000 2**2
> CONTENTS, ALLOC, LOAD, DATA
> 9 .bss 00033318 1000868c 1000868c 0005068c 2**5
> ALLOC
> 10 .comment 00000a9e 00000000 00000000 0005068c 2**0
> CONTENTS, READONLY
>
>
> i want to know why i am getting this warning. is there a way to get
> rid of this warning
> I'm not sure what you are trying to do with this executable.
I have got 4 flash each 8MB in size.I have .hex file of size 9.2MB.I
want to split the .hex file so that it can be downloaded on to the
flash.
> If you are converting to hex in order to program ROMs or FLASHes via a
> programmer then presumably this is a stand-alone executable. In that
> case .fixed_vectors should be located at 0x00000020, not
> 0x10000020. Otherwise interrupts and exceptions will not work.
>What target are you using?
I am using arm9 altera excalibur board.
> What class of ARM CPU does it have?
arm922t
>--
> Nick Garnett eCos Kernel Architect
> http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ECOS] arm-elf-objdump
2004-07-26 15:55 [ECOS] arm-elf-objdump Aravind B
@ 2004-07-27 10:02 ` Nick Garnett
0 siblings, 0 replies; 4+ messages in thread
From: Nick Garnett @ 2004-07-27 10:02 UTC (permalink / raw)
To: Aravind B; +Cc: ecos
Aravind B <arvindb@cranessoftware.com> writes:
> >Aravind B <arvindb@cranessoftware.com> writes:
>
> > hi,
> > i am trying to convert .elf file to .hex file.
> > But i am getting BFD: stYsHp0e: warning: allocated section `.bss' not
> >in
> > segment.
> > Since the BSS should not be part of the hex file, it is not at all
> > clear why this message is being generated. What options are you giving
> > objcopy?
> I am using fololowing option to generate .hex file:
> arm-elf-objcopy -O ihex $(EXECUTABLE).elf $(EXECUTABLE).hex
>
> > Note that it is just a warning, maybe the resulting HEX file is
> > correct.
> > after running the command arm-elf-objdump -h i have got the following
> > information
> >
> > Sections:
> > Idx Name Size VMA LMA File off Algn
> > 0 .rom_vectors 00000040 40000000 40000000 00008000 2**0
> > CONTENTS, ALLOC, LOAD, READONLY, CODE
> > 1 .text 0002cea8 40000040 40000040 00008040 2**2
> > CONTENTS, ALLOC, LOAD, READONLY, CODE
> > 2 .fini 00000000 4002cee8 4002cee8 0004868c 2**0
> > CONTENTS
> > 3 .rodata 0000c614 4002cee8 4002cee8 00034ee8 2**2
> > CONTENTS, ALLOC, LOAD, READONLY, DATA
> > 4 .rodata1 00000000 400394fc 400394fc 0004868c 2**0
> > CONTENTS
> > 5 .fixup 00000000 400394fc 400394fc 0004868c 2**0
> > CONTENTS
> > 6 .gcc_except_table 00000000 400394fc 400394fc 0004868c 2**0
> > CONTENTS
> > 7 .fixed_vectors 00000140 10000020 10000020 000486a0 2**5
> > CONTENTS, READONLY
> > 8 .data 0000068c 10008000 400394fc 00048000 2**2
> > CONTENTS, ALLOC, LOAD, DATA
> > 9 .bss 00033318 1000868c 1000868c 0005068c 2**5
> > ALLOC
> > 10 .comment 00000a9e 00000000 00000000 0005068c 2**0
> > CONTENTS, READONLY
> >
> >
> > i want to know why i am getting this warning. is there a way to get
> > rid of this warning
> > I'm not sure what you are trying to do with this executable.
> I have got 4 flash each 8MB in size.I have .hex file of size 9.2MB.I
> want to split the .hex file so that it can be downloaded on to the
> flash.
I see less than 256k of loadable sections. If your hex file is coming
out to 9MB then there is obviously something wrong. You still have
your memory map messed up. I suggest you take a look as some other
targets and work out what is wrong. Re-read and pay more attention to
the following paragraph:
> > If you are converting to hex in order to program ROMs or FLASHes via a
> > programmer then presumably this is a stand-alone executable. In that
> > case .fixed_vectors should be located at 0x00000020, not
> > 0x10000020. Otherwise interrupts and exceptions will not work.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ECOS] arm-elf-objdump
2004-07-26 9:10 Aravind B
@ 2004-07-26 9:41 ` Nick Garnett
0 siblings, 0 replies; 4+ messages in thread
From: Nick Garnett @ 2004-07-26 9:41 UTC (permalink / raw)
To: Aravind B; +Cc: ecos
Aravind B <arvindb@cranessoftware.com> writes:
> hi,
> i am trying to convert .elf file to .hex file.
> But i am getting BFD: stYsHp0e: warning: allocated section `.bss' not in
> segment.
Since the BSS should not be part of the hex file, it is not at all
clear why this message is being generated. What options are you giving
objcopy?
Note that it is just a warning, maybe the resulting HEX file is correct.
> after running the command arm-elf-objdump -h i have got the following
> information
>
> Sections:
> Idx Name Size VMA LMA File off Algn
> 0 .rom_vectors 00000040 40000000 40000000 00008000 2**0
> CONTENTS, ALLOC, LOAD, READONLY, CODE
> 1 .text 0002cea8 40000040 40000040 00008040 2**2
> CONTENTS, ALLOC, LOAD, READONLY, CODE
> 2 .fini 00000000 4002cee8 4002cee8 0004868c 2**0
> CONTENTS
> 3 .rodata 0000c614 4002cee8 4002cee8 00034ee8 2**2
> CONTENTS, ALLOC, LOAD, READONLY, DATA
> 4 .rodata1 00000000 400394fc 400394fc 0004868c 2**0
> CONTENTS
> 5 .fixup 00000000 400394fc 400394fc 0004868c 2**0
> CONTENTS
> 6 .gcc_except_table 00000000 400394fc 400394fc 0004868c 2**0
> CONTENTS
> 7 .fixed_vectors 00000140 10000020 10000020 000486a0 2**5
> CONTENTS, READONLY
> 8 .data 0000068c 10008000 400394fc 00048000 2**2
> CONTENTS, ALLOC, LOAD, DATA
> 9 .bss 00033318 1000868c 1000868c 0005068c 2**5
> ALLOC
> 10 .comment 00000a9e 00000000 00000000 0005068c 2**0
> CONTENTS, READONLY
>
>
> i want to know why i am getting this warning. is there a way to get rid
> of this warning
>
I'm not sure what you are trying to do with this executable. If
you are converting to hex in order to program ROMs or FLASHes via a
programmer then presumably this is a stand-alone executable. In that
case .fixed_vectors should be located at 0x00000020, not
0x10000020. Otherwise interrupts and exceptions will not work.
What target are you using? What class of ARM CPU does it have? What is
it's memory layout?
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ECOS] arm-elf-objdump
@ 2004-07-26 9:10 Aravind B
2004-07-26 9:41 ` Nick Garnett
0 siblings, 1 reply; 4+ messages in thread
From: Aravind B @ 2004-07-26 9:10 UTC (permalink / raw)
To: ecos
hi,
i am trying to convert .elf file to .hex file.
But i am getting BFD: stYsHp0e: warning: allocated section `.bss' not in
segment.
after running the command arm-elf-objdump -h i have got the following
information
Sections:
Idx Name Size VMA LMA File off Algn
0 .rom_vectors 00000040 40000000 40000000 00008000 2**0
CONTENTS, ALLOC, LOAD, READONLY, CODE
1 .text 0002cea8 40000040 40000040 00008040 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
2 .fini 00000000 4002cee8 4002cee8 0004868c 2**0
CONTENTS
3 .rodata 0000c614 4002cee8 4002cee8 00034ee8 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
4 .rodata1 00000000 400394fc 400394fc 0004868c 2**0
CONTENTS
5 .fixup 00000000 400394fc 400394fc 0004868c 2**0
CONTENTS
6 .gcc_except_table 00000000 400394fc 400394fc 0004868c 2**0
CONTENTS
7 .fixed_vectors 00000140 10000020 10000020 000486a0 2**5
CONTENTS, READONLY
8 .data 0000068c 10008000 400394fc 00048000 2**2
CONTENTS, ALLOC, LOAD, DATA
9 .bss 00033318 1000868c 1000868c 0005068c 2**5
ALLOC
10 .comment 00000a9e 00000000 00000000 0005068c 2**0
CONTENTS, READONLY
i want to know why i am getting this warning. is there a way to get rid
of this warning
thanking in advance
Aravind
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-07-27 8:55 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-07-26 15:55 [ECOS] arm-elf-objdump Aravind B
2004-07-27 10:02 ` Nick Garnett
-- strict thread matches above, loose matches on Subject: below --
2004-07-26 9:10 Aravind B
2004-07-26 9:41 ` Nick Garnett
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).