Different tick interval with the same application between RTEMS 4.10.0 and 4.10.2?

[Joel Sherrill]

On 05/21/2012 08:49 AM, Fabrício de Novaes Kucinskis wrote:
>
> Hi all,
>
> We've just upgraded our development environment from RTEMS 4.10.0 to 
> RTEMS 4.10.2. As always, an interesting issue has raised! ;-)
>
> We use the ERC32 and SIS BSPs. After the upgrade, a simple test 
> application that prints a clock once per second started to print the 
> clock values almost two times faster on SIS. The application gets the 
> number of ticks per second and uses it in the rtems_task_wake_after 
> directive.
>
When on any simulator, there is always the possibility that somehow the 
fast idle mode
in the clock driver got turned on.
>
> To determine if the issue was on SIS or RTEMS, we run in the 4.10.2 
> environment the previous version of the test, compiled with RTEMS 
> 4.10.0, and the task runs once per second. Also, the number of ticks 
> per second reported in both versions is the same.
>

Is this once per second in simulated or real time?

Set a break point at Clock_isr and see if it is doing the fast idle mode.


> Looking at the release notes, we've found a number of changes/fixes 
> related with ticks and time since 4.10.0. But it seems that none of 
> them is related to what I report here.
>
I looked at the diff files and the only changes are fixing bugs
related to nanoseconds since last tick when you ask on the
edge of a tick interrupt occurring.
>
> Is this something to be expected when upgrading? Am I missing some 
> change in the configuration?
>
> Thanks in advance and best regards,
>
> Fabrício de Novaes Kucinskis.
>


-- 
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...
URL: <http://lists.rtems.org/pipermail/users/attachments/20120521/c5719f93/attachment-0001.html>