Re: Odd Time of Day Reported with Ticker

2016-01-20 Thread Joel Sherrill
On Wed, Jan 20, 2016 at 12:38 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > > On 19/01/16 16:44, Joel Sherrill wrote: > >> >> >> On Tue, Jan 19, 2016 at 9:15 AM, Sebastian Huber < >> sebastian.hu...@embedded-brains.de > sebastian.hu...@embedded-brains.de>> wrote: >> >> >> >>

Re: Odd Time of Day Reported with Ticker

2016-01-19 Thread Sebastian Huber
On 19/01/16 16:44, Joel Sherrill wrote: On Tue, Jan 19, 2016 at 9:15 AM, Sebastian Huber > wrote: On 19/01/16 16:08, Joel Sherrill wrote: On Tue, Jan 19, 2016 at 8:57 AM, Sebastian Huber mailto:sebastian.hu...@embedded-bra

Re: Odd Time of Day Reported with Ticker

2016-01-19 Thread Joel Sherrill
On Tue, Jan 19, 2016 at 9:15 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > > On 19/01/16 16:08, Joel Sherrill wrote: > >> >> >> On Tue, Jan 19, 2016 at 8:57 AM, Sebastian Huber < >> sebastian.hu...@embedded-brains.de > sebastian.hu...@embedded-brains.de>> wrote: >> >> >> >>

Re: Odd Time of Day Reported with Ticker

2016-01-19 Thread Sebastian Huber
On 19/01/16 16:08, Joel Sherrill wrote: On Tue, Jan 19, 2016 at 8:57 AM, Sebastian Huber > wrote: On 19/01/16 15:39, Joel Sherrill wrote: The tasks are delaying 500, 1000, and 1500 ticks with nanoseconds_per_tick = 1000.

Re: Odd Time of Day Reported with Ticker

2016-01-19 Thread Joel Sherrill
On Tue, Jan 19, 2016 at 8:57 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > > On 19/01/16 15:39, Joel Sherrill wrote: > >> The tasks are delaying 500, 1000, and 1500 ticks with >> nanoseconds_per_tick = 1000. Delay operations are guaranteed to be a >> minimum of the reque

Re: Odd Time of Day Reported with Ticker

2016-01-19 Thread Sebastian Huber
On 19/01/16 15:39, Joel Sherrill wrote: The tasks are delaying 500, 1000, and 1500 ticks with nanoseconds_per_tick = 1000. Delay operations are guaranteed to be a minimum of the requested amount and this is not being honored. For the ticks based services this is not true, you wait to the

Re: Odd Time of Day Reported with Ticker

2016-01-19 Thread Joel Sherrill
On Jan 19, 2016 3:53 AM, "Sebastian Huber" < sebastian.hu...@embedded-brains.de> wrote: > > The problem is that you set the time via rtems_clock_set() in Init(). The you wait via rtems_task_wake_after(5s in ticks). With a rtems_task_wake_after(n) you wait to the n-th next tick, thus your wait inter

Re: Odd Time of Day Reported with Ticker

2016-01-19 Thread Sebastian Huber
The problem is that you set the time via rtems_clock_set() in Init(). The you wait via rtems_task_wake_after(5s in ticks). With a rtems_task_wake_after(n) you wait to the n-th next tick, thus your wait interval is slightly less than 5s in most cases. On 18/01/16 00:19, Joel Sherrill wrote: Hi

Re: Odd Time of Day Reported with Ticker

2016-01-18 Thread Joel Sherrill
I reproduced this on psim but it is happening on a custom x86 BSP. I appreciate a BSP specific fix for psim but want to know the general pattern if this is something we need to address over and over. On Mon, Jan 18, 2016 at 12:28 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: >

Re: Odd Time of Day Reported with Ticker

2016-01-17 Thread Sebastian Huber
Which BSP is affected by this? On 18/01/16 00:19, Joel Sherrill wrote: Hi With the recent clock changes, I am noticing that on some BSPs ticker is reporting times 4, 9, 14, ... instead of 5, 10, 15. It looks like the time is 4.999 when it should simply be 5 so ticker just reports 4. Given