On Jan 28, 2009, at 3:21 PM, Mustafa Hammad wrote: > Dear Dr. > > I am trying to study the nesC concurrency model with TinyOS 1.x. > I have developed a basic program with a very long-time task and a > very short-time timer. I have noticed that when the task starts > executing, the timer-fired event will not preempt the running task. > > By studying the TinyOS timer component code, I found that the timer- > fired event is fired from a task. So this task can’t preempt the > program’s task. > > By checking some other events, I also found they are fired from tasks. > Would you please let me know if we can conclude that: > In the developer level, program’s tasks can’t be preempted by > program’s events? >
Please read the tinyos programming manual, or the nesC paper. It goes into greater detail. There is a distinction between a hardware event (an interrupt) and a nesC program event. What you care about is the keyword "async". Phil _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
