On Tue, Jan 14, 2020, 8:29 AM Matthew J Fletcher wrote:
> Free running counter is only 32khz, so ages in cpu time at 200mhz. There
> is a nanosecond IEEE 1588 unit on the network interface
>
> I've identified at least 6 timers going at 10ms, only 1-in-1000
> invocations seem take more than a
Free running counter is only 32khz, so ages in cpu time at 200mhz. There is
a nanosecond IEEE 1588 unit on the network interface
I've identified at least 6 timers going at 10ms, only 1-in-1000 invocations
seem take more than a tick to run,.. they are all started in the same
second but with ra
On Tue, Jan 14, 2020 at 7:37 AM Matthew J Fletcher wrote:
> Of course without nanoseconds support in the BSP measuring the timer
> callback duration is difficult as most calls will be less than a tick.
>
Yeah, you can't use the clock services from rtems in that case since they
don't have a high
Of course without nanoseconds support in the BSP measuring the timer
callback duration is difficult as most calls will be less than a tick.
On Tue, 14 Jan 2020 at 08:41, Matthew J Fletcher wrote:
> Ok,
>
> So first step is to create a wrapper that all timers fire through, then an
> array to coun
Ok,
So first step is to create a wrapper that all timers fire through, then an
array to count the number of invocations per timer_id, after that some per
timer_id time accounting.
Will let you know if its anything outside my application.
On Mon, 13 Jan 2020 at 15:01, Joel Sherrill wrote:
>
>
