[riot-devel] Systick on the STM32s
hauke.petersen at fu-berlin.de
Mon Sep 1 13:47:06 CEST 2014
I put a copy of this mail to the devel-mailing list, so others can use
this information as well. Hope thats ok?!
We do not use the Systick-timer for two simple reasons at the moment:
1. RIOT uses a tick-less scheduling paradigm, which means that we do not
have a regular system tick that wakes up the scheduler to see if a new
task needs to be scheduled. But this is what the Systick-timer is
originally designed for... You can refer to  for more information on
2. RIOTs hwtimer needs best to be able to set more than 1 timeout in
parallel, so the peripheral timers with more multiple capture/compare
channels provide a better base for efficient implementation than the
But you are certainly ok with using the Systick timer for your specific
implementation, there is no reason not to use it...
On 29.08.2014 09:03, Somaraju Abhinav wrote:
> could somebody please tell me if there is any reason not to use the
> Systick on the STM32. I see a comment that says it is not used by
> RIOT. However, several peripheral libraries of the STM use it for
> timeouts. So, is it okay if I enable it?
> The contents of this e-mail and any attachments are confidential
> to the intended recipient. They may not be disclosed to or used
> by or copied in any way by anyone other than the intended recipient.
> If this e-mail is received in error, please immediately notify
> the sender and delete the e-mail and attached documents.
> Please note that neither the sender nor the sender's company
> accept any responsibility for viruses and it is your responsibility
> to scan or otherwise check this e-mail and any attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel