VxWorks auxiliary timer question

[David Fletcher]

I have an ISR connected to the system auxilary clock, which is set at
1ms
rate. The processing inside the ISR consists of simple calculations and
periodically a msgQSend to kick off a task to get the real work done.
Unfortunately after an arbitrary number of timer clicks the timer stops
calling the ISR. I am able to keep the timer running by making a
call
to sysAuxClkDisable and then sysAuxClkEnable at the entry of the ISR.

There are quite a few other tasks in the system, but none of them use
any
of the sysAuxClk* calls. I saw the earlier post suggesting that high
speed msgQ* calls could cause this, but simply removing the call in my
code has no effect on my current problem.

Any suggestions on what might cause an ISR to stop would be much
appreciated.

- William Stubbs
Raytheon

[john_...@my-deja.com]

David,

Are you certain that the timer is still running? The disable/enable
sequence will restart the timer hardware if it had stopped for some
reason. Perhaps there is a case when you are not servicing a timer
interrupt and resetting things before the next interrupt is fired; this
could result in the timer going into an error state since an interrupt
was missed.

Just a thoughy,

John...

In article <3937C565...@ssd.ray.com>,

Sent via Deja.com http://www.deja.com/
Before you buy.