Arm Community
Site
Search
User
Site
Search
User
Support forums
Arm Development Studio forum
Temporarily block SYSTICK interrupt (but not lose it)
Locked
Locked
Replies
4 replies
Subscribers
119 subscribers
Views
10064 views
Users
0 members are here
Options
Share
More actions
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
Temporarily block SYSTICK interrupt (but not lose it)
David Clark
over 12 years ago
Note: This was originally posted on 18th May 2010 at
http://forums.arm.com
CM3 core... I'd like to temporarily block the SYSTICK interrupt (and *only* the SYSTICK interrupt) from firing.
The desired behavior is that if the SYSTICK interrupt would have fired, I'd like it to be "pended", so that as soon as the critical section is over and the interrupt is "re-enabled", it fires.
At first I thought this might be the TICKINT bit in the SYSTICK Control & Status Register (0xE000E010), but from the documentation, it seems that if this bit is clear and the timer reaches 0, the interrupt won't even be pended, i.e., it would be "lost". Am I correct in this?
I know about PRIMASK & BASEPRI, but I don't want to isolate by level and I don't want to disable all interrupts...
I simply want to prevent the SYSTICK ISR from running in between "point A" and "point B", but I don't want to "lose" the interrupt, I'd just like to "pend it" if it would occur between "point A" and "point B".
Thanks.
0
Quote