[ECOS] Re: Sv: Vs: Timer interrupts and scheduler

[Nick Garnett]

"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