This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: redboot does not start in ram mode


Please copy your replies to the list so that all may benefit.  Private 
email support is available with a contract from MLB Associates.

On Fri, 2004-07-09 at 07:55, Martin Laabs wrote:
> On Fri, Jul 09, 2004 at 07:34:50AM -0600, Gary Thomas wrote:
> > On Fri, 2004-07-09 at 07:25, Martin Laabs wrote:
> > > On Fri, Jul 09, 2004 at 10:40:01AM +0200, Andrew Lunn wrote:
> > > > On Thu, Jul 08, 2004 at 10:54:55PM +0200, Martin Laabs wrote:
> 
> > You should be able to just:
> >   RedBoot> load -m xm
> >   RedBoot> go
> 
> I tried this several times but I got errors in transmission.
> (I send the redboot.img file and also tried with .elf)
> 

This is the preferred way to download programs.  What sort of errors did
you get?  

> > Note: I explicitly did *not* use:
> >   -r - this option tells RedBoot to download binary data without any
> >        interpretation of the format.  If you are downloading an 
> >        executable, this option would cause incorrect results.
> 
> I dowloaded the .bin file with the -r and -b option.
> 
> 
> > What does 'arm-elf-objdump -h <redboot.ELF>" show?  (where <redboot.ELF>
> > is the name of the ELF image that you built)?  This will show exactly
> > how the program has been linked and where it should be loaded.
> 
> All sections expect .debug_* and .note.arm.indent are
> locatetd from 0x10200000-0x10257094:
> 
> ------------------------------:<-----------------------
> redboot.elf:     file format elf32-bigarm
> 
> Sections:
> Idx Name          Size      VMA       LMA       File off  Algn
> 
>   0 .debug_aranges 000030c8  00000000  00000000  0003f098  2**3
>                   CONTENTS, READONLY, DEBUGGING
>   1 .debug_pubnames 000063e1  00000000  00000000  00042160  2**0
>                   CONTENTS, READONLY, DEBUGGING
>   2 .debug_info   0008b8b1  00000000  00000000  00048541  2**0
>                   CONTENTS, READONLY, DEBUGGING
> [...]
>   8 .fixed_vectors 00000140  10200020  10200020  0012bb20  2**5
>                   CONTENTS, READONLY
>   9 .rom_vectors  00000040  10220000  10220000  00008000  2**0
>                   CONTENTS, ALLOC, LOAD, READONLY, CODE
>  10 .text         00029f40  10220040  10220040  00008040  2**5
>                   CONTENTS, ALLOC, LOAD, READONLY, CODE
> [...]
>  17 .bss          000165c8  10257094  10257094  0003f094  2**4
>                   ALLOC
>  18 .debug_ranges 00000e58  00000000  00000000  0012bc60  2**0
>                   CONTENTS, READONLY, DEBUGGING
> 
> ----------------------:<------------------------------------
> 
> Are the problems coming from the .debug sections that are not
> in the ram? Does the loader therefore produce errors when I try
> to download it without the -r and -b option?

.debug sections are used by GDB - they are never loaded with a program.

Did you try:
  RedBoot> go 0x10220040
which would be the entry point for such a program.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]