Ah yes I forgot you could prescale the 32bit private timer!
Simon
On 10/07/15 10:50, rakendra thapa wrote:
Hi Simon,
You can also use a 32-bit timer lets say running at 50MHz and use
pre-scale of 50 so that you get tick at every 1us.
Thanks and Regards,
Rakendra
On Fri, Jul 10, 2015 at 2:
Hi Simon,
You can also use a 32-bit timer lets say running at 50MHz and use pre-scale
of 50 so that you get tick at every 1us.
Thanks and Regards,
Rakendra
On Fri, Jul 10, 2015 at 2:40 PM, Simon Vincent
wrote:
> Ok maybe I will leave timers alone for a couple of weeks and redo them
> once the
Ok maybe I will leave timers alone for a couple of weeks and redo them
once the new timers hit master.
I hope to make all the Zynq port code available in a few weeks.
Simon
On 10/07/15 09:53, Kaspar Schleiser wrote:
Hey,
On 07/10/15 10:32, Simon Vincent wrote:
Currently the issue I get with
Hey,
On 07/10/15 10:32, Simon Vincent wrote:
> Currently the issue I get with multiple timers is that calls to
> hwtimer_arch_now do not specify a timer. So you call hwtimer_arch_now
> and get a value. If you then use this to set a delay there are problems
> as when you request this delay it co
Hi Kaspar,
On 09/07/15 20:09, Kaspar Schleiser wrote:
Hey,
On 07/09/15 18:52, Simon Vincent wrote:
- RIOT only supports 32 bit timers?
You should implement the periph/timer interface. Using defines in
periph_conf.h, you can set a "max value", e.g., 0x for 16 bit
timers. Don't bother with
Hey,
On 07/09/15 18:52, Simon Vincent wrote:
> - RIOT only supports 32 bit timers?
You should implement the periph/timer interface. Using defines in
periph_conf.h, you can set a "max value", e.g., 0x for 16 bit
timers. Don't bother with hwtimer, that will be phased out soon, and
also there's a
Hi,
I am porting RIOT to a new platform and I have been having lots of
problems with getting the timers working. I have gone through all the
timer code and I think I understand how RIOT uses timers and found a few
problems/limitations.
*Limitations*
Am I correct in thinking:
- RIOT only supp