• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 56 subscribers
  • Views 877 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Z-Stack OSAL Event/Message

Arash Azarmi
Intellectual 885 points

Hi TI

When there are more than a message passed with a single OSAL event?
There is a while in message handilng part of ProcessEvent() function, Meaning there is more than a message with a single event. 
Doesn't each single message, if OSAL decides to, issue an event? 

  • 0
    TI__Genius 10650 points
    HI Arash, I am not sure I completely understand the question, can you please describe it a little more.
    This link may also help you understand the concept of events and messages in OSAL processors.wiki.ti.com/.../06_-_OSAL_and_HAL.pdf
    Regards
  • 0 in reply to Suyash Jain
    Intellectual 885 points
    Hi Suyash,
    Thanks for the doc. In GenericApplication code there is app_ProcessEvent(event) function. In this function command messages are dequeued by calling osal_msg_receive() and then handled.
    My understanding was 1 message--> 1 Event. But in sample code once application is notified of 1 event, it process's a Queue of messages in it's ProcessEven() function.
    My question is OSAL issues one event for each message it receives, or it ques messages and then issue an event for that que?
  • 0 in reply to Arash Azarmi
    Guru 735625 points

    Your question is confusing. If you can explain it better or provide the real case how you use it, I can explain more to you.

  • 0 in reply to YiKai Chen
    Intellectual 885 points 
    uint16 GenericApp_ProcessEvent( uint8 task_id, uint16 events )
{

  if ( events & SYS_EVENT_MSG )
  {
    MSGpkt = (afIncomingMSGPacket_t *)osal_msg_receive( GenericApp_TaskID );
    while ( MSGpkt )
    { ...
          // Next
      MSGpkt = (afIncomingMSGPacket_t *)osal_msg_receive( GenericApp_TaskID );
    }

    // return unprocessed events
    return (events ^ SYS_EVENT_MSG);
  }

    In handling SYS_EVENT_MSG we process a queue of messages(see while() and //Next). My understanding was 1 message arrives===> OSAL issues one associated event.
    But here messages are queued and at some point OSAL issues SYS_EVENT_MSG for a queue of messages. I don't get why the message queue is used here.

  • 0 in reply to Arash Azarmi
    Guru 735625 points

    There are different kinds of system event. Osal creates a message queue to put different system event in it and application can process it in GenericApp_ProcessEvent.