Why RTEMS timeslice is not as configured.

[Fernando Nicodemos]

No. Any ideas on how to check it accurately? Is it possible to check
against an osciloscope measure?

*Fernando G. Nicodemos*
*Diretor de Pesquisa e Desenvolvimento

***®*NCB - Sistemas **Embarcados Ltda.*
*23° 09’ 24.87”S**     45° 47’ 26.49”W*
São José dos Campos - SP - Brasil
t.:+55 (12) *3905.2243*                *
www.ncb.ind.br*

*AVISO:* Esta mensagem pode conter informações privilegiadas e seu conteúdo
é confidencial. É endereçada somente para destinatários conhecidos. Se você
não for um destinatário conhecido, não está autorizado a distribuir,
divulgar, imprimir, copiar e se utilizar desta mensagem e seu conteúdo.


2013/7/8 Chris Johns <chrisj at rtems.org>

> Fernando Nicodemos wrote:
>
>> Dears,
>>
>> I configured 4 equal Tasks in RTEMS and the table as follows:
>>
>> rtems_task_create(
>> Task_name[ 0 ],
>> 2,
>> RTEMS_MINIMUM_STACK_SIZE * 2,
>> RTEMS_PREEMPT | RTEMS_TIMESLICE | RTEMS_ASR | RTEMS_INTERRUPT_LEVEL(0),
>> RTEMS_GLOBAL,
>> &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.
>>
>> Any ideas what is missing for this extra time?
>>
>>
> Did you check the timer is operating at the correct frequency ?
>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20130711/dbc07b9a/attachment-0001.html>