Problem with ticker.exe for or1ksim/OpenRISC BSP

[Jennifer Averett]

> -----Original Message-----
> From: devel [mailto:devel-bounces at rtems.org] On Behalf Of Hesham
> Moustafa
> Sent: Thursday, July 17, 2014 4:58 AM
> To: rtems-devel at rtems.org
> Subject: Problem with ticker.exe for or1ksim/OpenRISC BSP
> 
> Hi,
> 
> I am trying to get ticker.exe working properly for or1ksim BSP but there is a
> problem. When I run ticker, I only get the following output
> 
> "*** BEGIN OF TEST CLOCK TICK ***
> TA1  - rtems_clock_get_tod - 09:00:00   12/31/1988
> TA2  - rtems_clock_get_tod - 09:00:00   12/31/1988
> TA3  - rtems_clock_get_tod - 09:00:00   12/31/1988"
> 
> And nothing else. I tried to debug this issue using the following methods:
> 
> 1- Set a break point at "put_name( Task_name[ task_index ], FALSE );"
> line, it always reach this point (with different task ids each time) but does not
> produce any output.

>From the output:  put_name is hit and produces the first three lines,
If it is hit a fourth time then rtems_task_wake_after is waking the tasks, the timer
is  working (time may still be off), and I would check if it was getting to the console
next.   

However, if it doesn't reach it a fourth time the context switch is probably not 
occurring correctly.

> 2- Set a break point at _Watchdog_Tickle function, and it's reached every
> time and decreasing the interval successfully.
> 
> 3- Set a break point at _Watchdog_Remove function, and it's always reached
> every time I hit continue.
> 
> 4- Set a break point at "status = rtems_clock_get_tod( &time );" at ticker.c,
> and time.second is always 0, never incremented. I though
> Clock_driver_nanoseconds_since_last_tick is the problem, so I made it
> return a static value to test it (12345 for example), but I got the same
> problem.
> 
> Please note that the previous break points always reached when I hit
> continue every time, the timer interrupt keeps arising and do its work never
> stops, and the problem enters IDLE task.
> 
> I would appreciate any hints or solutions regarding this problem.
> 
> Thanks,
> Hesham
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel