• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 126 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.

AWR1843BOOST: Doubt with how the task are getting scheduled in the MRR_Lab07

Tanoop Rajan
Intellectual 271 points
Part Number: AWR1843BOOST
Other Parts Discussed in Thread: SYSBIOS

I was just debugging the MRR lab_07 using the  RTOS analyzer when I noticed a peculiar behavior.
Currently, 2 tasks are running in the MSS(R4 cortex)


1.MmwDemo_mboxReadTask()  and  2.ti_sysbios_knl_Idle_loop__E()

ie a task to read the mailbox with the items that are filled from DSS and output them this task is executed  on every MmwDemo_mboxCallback 
after this task is over the core goes into lower priority Idle_task and the Mbox_read task again waits for the semaphore which is only released on the callback and happens only on the next cycle 


But after trying to visualize this behavior on Execution Graph I am getting the following behavior ....ie even before completing the MmwDemo_mboxReadTask() the scheduler is called for a brief time and it schedules the lower priority Idle Task but again the MmwDemo_mboxReadTask() preempts the Idle Task   although all these things happen within few us(microseconds) I was curious with the behavior

  • 0
    TI__Mastermind 27205 points

    Hello Tanoop,

    This kind of behavior happens generally in code, when in the readtask function you would ideally be waiting for something else.
    The way you can debug this, is if you can find out after which line of code does it move into the idle task.
    This will provide more clarity as also there are case statements in the readtask function, so you will need to identify for which switch case this is happening as well.

    Regards,
    Saswat Kumar