This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: ec555 memory map, bootcode
- From: <bob dot koninckx at o-3s dot com>
- To: "Meulendijks, J." <Meulendijks at WT dot TNO dot NL>
- Cc: "'bob dot koninckx at o-3s dot com'" <bob dot koninckx at o-3s dot com>, "'Andrew Lunn'" <andrew at lunn dot ch>, "'ecos-discuss at sources dot redhat dot com'" <ecos-discuss at sources dot redhat dot com>
- Date: Thu, 25 Nov 2004 06:01:54 -0500
- Subject: RE: [ECOS] ec555 memory map, bootcode
I am pretty sure that what you want to do will involve a _lot_
of rework and testing. Since you wont be using redboot, your
app will have to take care of _all_ interrupt processing.
(that's why Gary suggested to use the option to copy vectors).
But then you need write access to memory at 0x100, 0x200 etc
... Unfortunately, I mapped the internal flash there. First
thing to do would be modifications to the memory map and
memory controller setup.
Just curious, why don't you use redboot?
Bob
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss