By default, very simple ones (although there are extensions for threading or adding priorities and the like). Very grossly speaking, TinyOS is a loop that executes tasks, posted on a queue, that can only be interrupted only be interrupts (such as hardware timers). If there are no tasks, TinyOS can sleep until it receives an interrupt, in which case it needs to potentially process the task queue again.
Mapping? What mapping? Take one down, pass it around, 99 tasks of code on the wall... (T2 operates differently than T1 and uses per-task buckets, but the same principles apply). You can see all the details (albeit it takes a bit of sifting) simply by viewing the generated app.c source file. HTH, Paul _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
