Rtems #define CONFIGURE_MICROSECONDS_PER_TICK
Joel.Sherrill at OARcorp.com
Wed Oct 16 10:03:12 UTC 2013
This looks like a benchmark test (tmXX) and they do not include the clock device driver. This you are specifying a parameter that impacts a component not in the program.
FWIW why is the put time call specifying clock tick? It appears to be benchmarking a preempting semaphore release which has no need of a clock tick.
Oscar Siby <sibyo at student.chalmers.se> wrote:
Im working with a xilinx virtex 5 board running a leon 3 core,my rtems
version is 4.10.0 built from source.
My predicament is that when i change the CONFIGURE_MICROSECONDS_PER_TICK it
does not seem to change anything, here is the code of two of my tasks.
rtems_task High_task(rtems_task_argument argument)
end_time = benchmark_timer_read();
rtems_task_delete( RTEMS_SELF );
rtems_task Low_task(rtems_task_argument argument)
puts( "*** END OF TEST 25 ***" );
rtems_test_exit( 0 );
I have tried with all kinds of values for CONFIGURE_MICROSECONDS_PER_TICK
but the put_time values is still always in the same range. Is the
benchmark_timer running on a different timer/clock ?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users