[ECOS] Installing Redboot/eCos on the Atmel EB40(A) (Solved)
Ian McKee
mrianmckee@hotmail.com
Wed Dec 10 21:40:00 GMT 2003
Thanks Dirk and Ricardo,
Like you suggested, my problem was that I was building for the EB40, not the
EB40A, which is the dev board actually in my posession. I now have redboot
installed on the Flash alongside Angel and I'll start trying to do things
with eCos!
-Ian
>have you really tried building for the EB40A target, not for the EB40, that
>has a completely different memory layout?
>If you are using ecos 2.0, there is no EB40A support included. You have to
>get the latest CVS (or an ftp snapshot from
>-------- Original Message --------
>Subject: [ECOS] Installing Redboot/eCos on the Atmel EB40(A) (10-Dez-2003
>6:25)
>From: mrianmckee@hotmail.com
>To: ecos-discuss@sources.redhat.com
>
> > Hi All,
> >
> > I'm new to both the eCos/Redboot community and the Arm community, so
>please
> >
> > bear with me and my noob questions. :)
> >
> > I am trying to learn how to use the GNU toolchain to develop embedded
> > software for the ARM target, because 1) I prefer open-source tools and
>2)
> > although buying an IDE (GNU or non-GNU) would be easier, it sure would
>be
> > expensive! I have GNU tools experience with non-embedded *nix software
>and
> >
> > with the embedded Atmel AVR target.
> >
> > Towards this end I am trying to install Redboot/Ecos on my Atmel EB40A
> > board, and as I understand it the first thing I need to do is get
>Redboot
> > into Flash according to these instructions:
> >
> > http://ecos.sourceware.org/ecos/docs-latest/ref/at91.html
> >
> > I can successfully build the Redboot RAM, ROM, and RAMROM images using
>the
> > eCos graphical configtool, but when I follow the instructions at the
>above
> > URL, this is what my session looks like:
> >
> > [oberheim@localhost bin]$ pwd
> > /home/oberheim/ecos/ecos-work/redboot_RAM/redboot_RAM_install/bin
> > [oberheim@localhost bin]$ ls
> > redboot.bin redboot.elf redboot.img redboot.srec
> > [oberheim@localhost bin]$ arm-elf-gdb redboot.elf
> > GNU gdb 5.3 (eCosCentric)
> > Copyright 2002 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and you
> > are
> > welcome to change it and/or distribute copies of it under certain
> > conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB. Type "show warranty" for
>details.
> > This GDB was configured as "--host=i686-pc-linux-gnu
>--target=arm-elf"...
> > (gdb) tar rdi s=/dev/ttyS0
> > Angel Debug Monitor (serial) 1.04 (Advanced RISC Machines SDT 2.5) for
> > AT91EB40A (1.00)
> > Angel Debug Monitor rebuilt on Feb 03 2002 at 16:09:59
> > Serial Rate: 9600
> > Connected to ARM RDI target.
> > (gdb) set $cpsr=0xd3
> > (gdb) load
> > Loading section .rom_vectors, size 0x40 lma 0x2020000
> > RDI_write: data abort, no memory at specified address?
> > RDI_write: data abort, no memory at specified address?
> > Memory access error while loading section .rom_vectors.
> > (gdb) doh
> > Undefined command: "doh". Try "help".
> > (gdb)
> >
> > After a bit of googling I suspect that these RDI_write errors occur
>because
> >
> > the RAM image is being loaded into an address which does not physically
> > exist. Is this correct? What can I do to get past this error?
> >
> > My development box is an up-to-date RedHat 8.0 box, with the latest eCos
> > distribution. Please let me know if any more information would be
>useful
> > to
> > help resolve my problem. Also let me know if this is the proper venue
>for
> >
> > this question, or if I should post somewhere else.
> >
> > I'd really like to get started developing on this ARM platform and I'll
> > appreciate any input you all can give me!
> >
> > -Ian McKee
> >
_________________________________________________________________
Take advantage of our best MSN Dial-up offer of the year  six months
@$9.95/month. Sign up now! http://join.msn.com/?page=dept/dialup
--
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