I had this 10mS cycle time issue with a multithreaded application awhile
back. Turned out the kernel was built with 100Hz base ticks, not 1kHz. Do
"cat /proc/timer_list" and have a look at the available timer resolutions
on your system, pause() can't work at any lower resolution than the kernel
ti
Hi,
No, the sleeps don't seem to wait more than 10ms. No matter what value I put
there greater than 10 ms, the cyclic_task() is being executed around 10ms. I
have also digital outputs toggling in the cyclic_task() and the output
frequency on oscilloscope is always around 50Hz. This I find quite
On 28 January 2016 08:54, quoth Paul Mulligan:
> When using multi-threading, such that the function which calls the
> cyclic_task() is running in a separate detached thread from the main
> thread, the pause function blocks forever and a signal is never
> received as below.
[...]
> Also, I tried
Hi ,
I am writing my applications based on the examples that come with the Master
installation.
The cyclic_task() is executed every time on reception of a timer signal by
calling the pause() blocking function. This works if using just one thread.
When using multi-threading, such that the function