• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 399 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.

Task_sleep() doesn't return on am1705

Sergei Sergeyuk
Intellectual 370 points

Other Parts Discussed in Thread: AM1705, SYSBIOS

Hello, all.

I have am1705 device; FC 3.20.2.29; XDC 3.22.2.27; IPC 1.23.3.31 and SysBios 6.32.3.47; XDIAS 7.10.0.06

Simple example SYS/BIOS -> Task Mutex example.

I can see the timer runs. The Clock_getTicks returns the correct values.

But the Task_sleep() doesn't return.

The statuses of both tasks are 'blocked'.

There are two timers in my application. The first is "runmode_Auto" + 24000 period and the second is "runmode_User" + 0xFFFFFFFF period.

What's wrong? Should I initialize additional one timer?

  • 0
    TI__Mastermind 20805 points

    Hi Sergei --

    This is very strange.  If Clock_getTicks() is returning correct values, then your timer and Clock sub-system should be working.  Task_sleep() should sleep for 'n' Clock ticks.  What value are you passing to Task_sleep()?   Can you look at ROV and see the state of the tasks?   They should say 'blocked', but they should also indicate what they are blocked on and what the timeout is.  The value in ()'s should be the number of ticks remaining before the sleep expires.  Do these make any sense?

     

  • 0 in reply to Karl Wechsler
    Intellectual 370 points

    The re-installation of sysbios have solved the problem.

    Thank you.