This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: ec555 memory map, bootcode
- From: "Meulendijks, J." <Meulendijks at WT dot TNO dot NL>
- To: "'bob dot koninckx at o-3s dot com'" <bob dot koninckx at o-3s dot com>
- Cc: "'ecos-discuss at sources dot redhat dot com'" <ecos-discuss at sources dot redhat dot com>
- Date: Mon, 29 Nov 2004 16:15:38 +0100
- Subject: RE: [ECOS] ec555 memory map, bootcode
Ok, is it also possible to configure eCos to run on 1000Hz instead of the
default 100Hz on the ec555 ? Or does this setup makes the overhead to big? I
already tried this setup but I experienced some weird things.
Jeroen
-----Original Message-----
From: Bob Koninckx [mailto:bob.koninckx@o-3s.com]
Sent: zondag 28 november 2004 09:37
To: Meulendijks, J.
Cc: 'ecos-discuss@sources.redhat.com'
Subject: RE: [ECOS] ec555 memory map, bootcode
We use a timebase interrupt for doing that.
Bob
On Fri, 2004-11-26 at 13:32, Meulendijks, J. wrote:
> Because I'm implementing eCos in a product that already has its own bootcode.
> And _all_ interrupt processing is already taken care off.
> By the way I got eCos running now. I modified the memory map and memory
> controller setup. And modified a couple of register values and now its working
> :-)
>
> But now I look at the system clock which is running on 10ms (100 Hz), but I
want
> to have a clock that runs on 1ms (1000 Hz) Can this be done (on the mpc555)
> _without_ disrupting the system clock. I already read on the discussion list
> that a couple of parts of eCos depend on the 10ms clock.
>
> Thanks in advance.
>
> -----Original Message-----
> From: bob.koninckx@o-3s.com [mailto:bob.koninckx@o-3s.com]
> Sent: donderdag 25 november 2004 12:02
> To: Meulendijks, J.
> Cc: 'bob.koninckx@o-3s.com'; 'Andrew Lunn';
> 'ecos-discuss@sources.redhat.com'
> 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