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

RTX flags etc

In the Keil help section it seems to imply that each task name gets its own individual 16bit flag ie. as in os_evt_set (0x0004, id2); and os_evt_set (0x0004, id3); if so, how does os_evt_wait_or (0x0004, 0xffff); know which task's flag it belongs too? Or am I misinterpretting the help file. I seem to think that all tasks share a common 16bit flag and that the os_evt_wait_or and os_evt_wait_and are used to select which individual or group of flags is of interest. Can someone put me straight. Thanks.

Parents
  • You are right. I made two tasks into a simple flip-flop using the same flag values and they work fine. I had the wrong idea that "os_evt_wait_or" was like reading a global flag, but no, it appears to be associated with the task name (TID) of the function it is used inside. so every function has a 16bit flag. far more than I will ever need. but hey...

Reply
  • You are right. I made two tasks into a simple flip-flop using the same flag values and they work fine. I had the wrong idea that "os_evt_wait_or" was like reading a global flag, but no, it appears to be associated with the task name (TID) of the function it is used inside. so every function has a 16bit flag. far more than I will ever need. but hey...

Children
No data