- Fri Dec 19, 2014 10:26 am
#5173
Haven't test how the conflicts is handled, since it is a single thread, my guess is the second timer will not get fired before the previous task completes.
number of a timer only indicate where the timers struct stored in a array. lower number doesn't have any privilege.
GeoNomad wrote:zeroday wrote:
tmr.alarm is not a hardware interrupt. it's a chain of Timer(soft I think, from SDK).
all timers alarm will handled one by one. not simultaneously.
Thanks. I was guessing that was the case.
Any idea how it handles conflicts when one timer has not completed its task and a second timer fires? Is it purely a queue or stack?
Are lower number timers more likely to be accurately timed, then?
Just trying to pre-empt the kinds of difficult to debug problems that come up if you make the wrong assumptions...
Haven't test how the conflicts is handled, since it is a single thread, my guess is the second timer will not get fired before the previous task completes.
number of a timer only indicate where the timers struct stored in a array. lower number doesn't have any privilege.
