This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Redboot network setup
- To: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Subject: Re: [ECOS] Redboot network setup
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Thu, 20 Sep 2001 18:32:47 +0100
- Cc: 'Robin Farine' <acnrf at dial dot eunet dot ch>,"Ecos-List (E-mail)" <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat UK Ltd.
- References: <B1F6452C89AFD411AE0800A0CC734C230150C2@EMAIL1>
Fabrice Gautier wrote:
>
> > -----Original Message-----
> > From: Jonathan Larmour [mailto:jlarmour@redhat.com]
> > Subject: Re: [ECOS] Redboot network setup
> >
> >
> > Fabrice Gautier wrote:
> > >
> > > (gdb) load
> > > Loading section .rom_vectors, size 0x40 lma 0x20000
> > >
> > > Error: Remote communication error: Connection reset by peer.
> > >
> >
> > Perhaps it uses more than 0x20000 bytes of RAM. Try updating
> > the RAM MLT
> > file to reserve 0x30000 instead.
> >
>
> I already update from 0x10000 and according to
> $ arm-elf-size redboot.elf
> text data bss dec hex filename
> 74124 1108 40732 115964 1c4fc redboot.elf
> and
> $ arm-elf-objdump -h redboot.elf
> ...
> 12 .data 00000454 00000800 2401218c 00020800 2**2
> CONTENTS, ALLOC, LOAD, DATA
> 13 .bss 00009f1c 00000c54 00000c54 00000c54 2**4
> ALLOC
>
> this should not be the problem... except if it's using memory outside the
> mempry map....
RAM should go from 0 upwards on all ARM targets or things will almost
certainly break. You can debug the GDB protocol, and see at exactly what
address it goes wrong at, then try writing to that address by hand
yourself.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine