[ECOS] problem building application

Eric de Jong list_ericdejong_10@gmx.net
Wed May 21 17:08:00 GMT 2003


Aaron,

>> I dont think I should get a compiled file size of 1.2M with a hello world
>> program.  Should I?

In my environment I get the file 'a.out' as a result after linking. With the
command "objdump -h a.out" (arm-elf-objdump) I can see the size of each section
and where they will be loaded (LMA and VMA addresses). The size of my a.out is
1.31MB. Here is the output of objdump -h:

$ arm-ecos-elf-objdump -h a.out

a.out:     file format elf32-littlearm

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .debug_aranges 00001fb8  00000000  00000000  000343c4  2**0
                  CONTENTS, READONLY, DEBUGGING
  1 .debug_pubnames 00006735  00000000  00000000  0003637c  2**0
                  CONTENTS, READONLY, DEBUGGING
  2 .debug_info   000b27ef  00000000  00000000  0003cab1  2**0
                  CONTENTS, READONLY, DEBUGGING
  3 .debug_abbrev 00012bd2  00000000  00000000  000ef2a0  2**0
                  CONTENTS, READONLY, DEBUGGING
  4 .debug_line   00026ca0  00000000  00000000  00101e72  2**0
                  CONTENTS, READONLY, DEBUGGING
  5 .debug_frame  00006ee0  00000000  00000000  00128b14  2**2
                  CONTENTS, READONLY, DEBUGGING
  6 .debug_str    0000f43f  00000000  00000000  0012f9f4  2**0
                  CONTENTS, READONLY, DEBUGGING
  7 .fixed_vectors 00000140  00000020  00000020  000000a0  2**5
                  ALLOC
  8 .vectors      00000040  00012000  00012000  000000a0  2**0
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  9 .boot         00000004  00012040  00012040  000000e0  2**0
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
 10 .romtext      00000000  00012044  00012044  0013ee33  2**0
                  CONTENTS
 11 .text         0001f950  00012044  00012044  000000e4  2**2
                  CONTENTS, ALLOC, LOAD, CODE
 12 .fini         00000000  00031994  00031994  0013ee33  2**0
                  CONTENTS
 13 .bss          000069d0  00031994  00031994  0001fa34  2**5
                  ALLOC
 14 .rodata       00003dfc  02040000  02040000  0001fa34  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
 15 .rodata1      00000000  02043dfc  02043dfc  0013ee33  2**0
                  CONTENTS
 16 .fixup        00000000  02043dfc  02043dfc  0013ee33  2**0
                  CONTENTS
 17 .gcc_except_table 00000070  02043dfc  02043dfc  00023830  2**2
                  CONTENTS, ALLOC, LOAD, DATA
 18 .data         00010b24  02043e6c  02043e6c  000238a0  2**2
                  CONTENTS, ALLOC, LOAD, DATA
 19 .comment      00000786  00000000  00000000  0013ee33  2**0
                  CONTENTS, READONLY
 20 .debug_ranges 00000b00  00000000  00000000  0013f5b9  2**0
                  CONTENTS, READONLY, DEBUGGING

Maybe this will clarify a few things for you.
Does your redboot contain a gdb-stub? try connecting gdb (arm-elf-gdb or
arm-gdb-insight) to your target board and load your program with gdb (insight).
You can see the load addresses and errors in the command window.

Eric



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss



More information about the Ecos-discuss mailing list