[Bug 1000084] New: RedBoot ignores LOAD section attribute when determining ELF file address range

[bugzilla at ecoscentric dot com]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000084

           Summary: RedBoot ignores LOAD section attribute when determining
                    ELF file address range
           Product: eCos
           Version: CVS
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: normal
         Component: RedBoot
        AssignedTo: gary@mlbassoc.com
        ReportedBy: jld@ecoscentric.com
         QAContact: ecos-bugs@sources.redhat.com


RedBoot appears to ignore the LOAD section attribute when calculating/reporting 
the address range of an ELF image just downloaded. Stripping the ELF image does 
not necessarily workaround this problem since some sections without the LOAD 
attribute can remain. The address range reported when downloading an ELF image 
and when downloading the equivalent SREC file can therefore differ. This, in 
turn, affects the way in which the downloaded image is written to Flash 
using "fis create <name>".

For example, RedBoot will report that the following stripped ELF image starts 
at address zero following download:

$ m68k-elf-objdump -h thread_gdb

thread_gdb:     file format elf32-m68k

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .fixed_vectors 00000380  00000000  00000000  00002000  2**0
                  ALLOC
  1 .vectors      0000002e  00010000  00010000  00002000  2**0
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  2 .text         00005530  00010030  00010030  00002030  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  3 .fini         00000000  00015560  00015560  00007a74  2**0
                  CONTENTS
  4 .rodata1      00000000  00015560  00015560  00007a74  2**0
                  CONTENTS
  5 .rodata       00000346  00015560  00015560  00007560  2**0
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  6 .fixup        00000000  000158a8  000158a8  00007a74  2**0
                  CONTENTS
  7 .gcc_except_table 00000000  000158a8  000158a8  00007a74  2**0
                  CONTENTS
  8 .data         000001cc  000158a8  000158a8  000078a8  2**2
                  CONTENTS, ALLOC, LOAD, DATA
  9 .sbss         00000000  00015a74  00015a74  00007a74  2**0
                  CONTENTS
 10 .bss          0000a65c  00015a74  00015a74  00007a74  2**2
                  ALLOC



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.