I will ask Mark to run the klatency -t 2 test. I do not have a system
or even a piece of a system right now so I can't run anything. Sorry. :(
What happens if I call start on a timer that is already running? Will
it change the timing at all or ignore the start?
Is this correct:
rtdm_timer_start(&timer, 2000000, 125000, RTDM_TIMERMODE_ABSOLUTE);
The behavior I want is to start my timer in 2ms and have it fire every
125us. The timer itself will use rtdm_timer_stop_in_handler() to stop
Am I making any mistakes here?
On Mar 12, 2009, at 7:12 AM, Gilles Chanteperdrix wrote:
> Steven Seeger wrote:
>> Is an RTDM timer going to run at a priority higher than any scheduled
>> realtime thread?
>> How accurate is the timing?
>> We are seeing the timer running at 125us periodic rate being called
>> much too quickly. At least, I think we are. I can't personally use
>> anything for a little over a week.
> Yes a timer runs in interrupt context. This is the same design as
> VxWorks, RTLinux, RTAI and most known OSes.
> I do not understand what you mean by "too quickly", but do you get the
> same phenomenon with the klatency -t 2 test?
Xenomai-core mailing list