We have PPC machine and use QNX 6.5.0 with CODESYS 3.5 patch 4.We have a system tickrate of 50 microseconds.
Can CODESYS 3.5 patch 4 run on such a tickrate?
It is also observed that in a normal system kernel trace , 9 tasks are running under Codesys process .Three of them follow FIFO Scheduling and others follow Round robin. the " schedule(PID 4)” task of 150f priority goes regularly into nanosleep, then becomes ready, runs and then goes to nanosleep again . The task(PID 7) with 23f priority is blocked on semaphore and decrements the semaphore once the scheduler increments the semaphore, and then becomes ready to run. It then runs before getting blocked on a semaphore again. this cycle continues.
In a Unhealthy system it has been observed that schedule(4) task goes into nanosleep state and does not come out of it. The task(7) is also continuously blocked on a semaphore.
Thus the system behaves in an unstable manner.
Is the above phenomenon due to a low tick rate.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have PPC machine and use QNX 6.5.0 with CODESYS 3.5 patch 4.We have a system tickrate of 50 microseconds.
Can CODESYS 3.5 patch 4 run on such a tickrate?
It is also observed that in a normal system kernel trace , 9 tasks are running under Codesys process .Three of them follow FIFO Scheduling and others follow Round robin. the " schedule(PID 4)” task of 150f priority goes regularly into nanosleep, then becomes ready, runs and then goes to nanosleep again . The task(PID 7) with 23f priority is blocked on semaphore and decrements the semaphore once the scheduler increments the semaphore, and then becomes ready to run. It then runs before getting blocked on a semaphore again. this cycle continues.
Thus the system behaves in an unstable manner.
Is the above phenomenon due to a low tick rate.