• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 387 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.

edma3 problem or bios task sleep problem

angou-Cheng
Prodigy 30 points
Other Parts Discussed in Thread: OMAP-L137

Hi,

I can build and run edma3_lld_01_11_03_01 sample application on omap-l137 evm.

Incidently, a line TSK_sleep(100) was inserted after edma3init(). It's still OK.

Since the app will be a template for moving to dsplink application, I deleted the statically created task "echo" 

and create it dynamically. Then I found the app suspend at TSK_sleep(100) without return.

When I restore the statically created task, every thing become OK again.

Anyone know why?

  • 0
    TI__Mastermind 20805 points

    Can you use the ROV tool (available n CCSv5.x using Tools->ROV menu while in debug mode) to look at the state of the different threads?   I suspect that you have created a new task with high priority and that the new task doesn't block by calling SEM_pend() or similar API.   You can use ROV and see the state of the threads.   You can also see the system tick.   I suspect that you will find that your task that calls TSK_sleep() is in the 'ready' state but cannot run because the higher priority task never yields the processor. 

    You can also use ROV to monitor the system tick in the 'TSK' view.   You should see the time changing between breakpoints.

    ROV is documented in the DSP/BIOS User's Guide.

    -Karl-