This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Sv: Vs: Timer interrupts and scheduler
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: "Stephen Mose Aaskov" <sma at 2m dot dk>
- Cc: <ecos-discuss at sources dot redhat dot com>
- Date: 24 Sep 2002 23:48:55 +0100
- Subject: [ECOS] Re: Sv: Vs: Timer interrupts and scheduler
- References: <004c01c262ea$950b24c0$016d100a@2m.dk><m3r8fk3i4u.fsf@ecoscentric.com><00b001c263c7$dc507fa0$016d100a@2m.dk><00c801c263d0$1a8d2400$016d100a@2m.dk>
"Stephen Mose Aaskov" <sma@2m.dk> writes:
> I guess what Iīm really looking for here is how to make the system clock tick.
>
> I have a test application running on my target board that starts up
> twp threads, each having a loop flashing some LEDīs and a call to
> cyg_thread_dealy().
Start off by getting the kernel test programs working. They were
written to help bring up new ports. If you think the clock is not
working, run the clocktruth test.
>
> When started the first resumed thread is run, then interrupted by the second thread.
> After that a context switch to the idle thread is performed and nothing else happends.
>
> Iīm using the multi level queue scheduler with timeslicing, and the
> observed behaviour makes my think that a system timer nessecary for
> decing when to slice time isnīt updated.
It certainly sounds to me like the timer is not working properly. If
you have LEDs, try flashing them in the HAL_CLOCK_* macros to see if
they are being called. You also need to check that you are programming
the interrupt controller correctly.
--
Nick Garnett - eCos Kernel Architect
http://www.eCosCentric.com/
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss