Why RTEMS timeslice is not as configured.
joel.sherrill at OARcorp.com
Tue Jul 9 14:42:37 UTC 2013
On 7/8/2013 2:59 PM, Fernando Nicodemos wrote:
> I configured 4 equal Tasks in RTEMS and the table as follows:
> Task_name[ 0 ],
> RTEMS_MINIMUM_STACK_SIZE * 2,
> RTEMS_PREEMPT | RTEMS_TIMESLICE | RTEMS_ASR | RTEMS_INTERRUPT_LEVEL(0),
> &Task_id[ 0 ]
> They will operate in round-robin.
> #define CONFIGURE_MICROSECONDS_PER_TICK 10000
> #define CONFIGURE_TICKS_PER_TIME_SLICE 50
> The result should show a timeslice of 500 milisseconds, but what i see
> in osciloscope is more then 500ms, exactly 834ms. This code is running
> in a ERC32 development kit from Atmel.
Where are the pins being written in the code to measure this?
> Any ideas what is missing for this extra time?
What speed is the erc32?
I am curious if the assumed CPU speed is different from your actual
> *Fernando G. Nicodemos*
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill at OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users