• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 711 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

the use of TSK_yield

xue han
Prodigy 150 points

Whether to use TSK_yield in hardware interrupt to make taskA always takes precedence over taskB performed ，even before the hardware interrupt， taskB was  performed. After the hardware interrupt  performed , taskA is ready .whether it will be able to first execution taskA and taskB will be protected

  • 0
    TI__Mastermind 26780 points

    Xue,

    If I understand correctly, you want task A to run whenever it is readied by the hardware interrupt, preempting task B that is running.  If this is correct, you can just assign task A to a higher priority versus task B.  There would be no need to call TSK_yield().

    Is that what you are asking?  If not, please provide more details to your question...

    Scott

  • 0 in reply to ScottG
    Prodigy 150 points

    You understand correctly,and I want to know how can I test? taskA execution speed quickly, only few microseconds, I tried to print information or breakpoint to run, sometimes see phenomenon is not correct?thank you!

  • 0 in reply to xue han
    TI__Mastermind 26780 points

    Xue,

    Have you looked at the “Instrumentation” chapter in the DSP/BIOS User’s Guide (http://www.ti.com/lit/ug/spru423h/spru423h.pdf)?  The execution graph is a nice tool for looking at the execution sequence of different threads:



    Other alternatives could be to use LOG to write messages to a log to track when the higher priority task is running, or to toggle I/O bits when the tasks are running and look at the sequence on an oscope or logic analyzer.

    Scott

  • 0 in reply to ScottG
    Prodigy 150 points

    Hi,

         I want to use the execution sequence in CCS3.3,but I found the threads which are created dynamic did not show in it.And I can't found what I want to see.Many of the threads is always unkown,for example the tskImgAcq thread.what should I do?

  • 0 in reply to xue han
    TI__Guru* 96960 points

    As you noted, dynamically created are not supported in the execution graph.

    Todd